GPRS Basics

CHAPTER 1
CHAPTER 2
CHAPTER 3
CHAPTER 4
CHAPTER 5
Cellular Infrastructure Group
ISSUE 1 REVISION 3
CP07 INTRODUCTION TO GPRS
FOR TRAINING PURPOSES ONLY
ISSUE 1 REVISION 3
ISSUE 1 REVISION 3
CP07 Introduction to GPRS
E Motorola 1993, 1994, 1995, 1996, 1997, 1998, 1999 All Rights Reserved Printed in the U.K.
EMOTOROLA LTD. 2001
CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY
ISSUE 1 REVISION 3
Copyrights, notices and trademarks

Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs, including the exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or disclosed only in accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies or omissions in this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey license under its patent rights of others.
Trademarks
and MOTOROLA are trademarks of Motorola Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Tandem, Integrity, Integrity S2, and Non-Stop-UX are trademarks of Tandem Computers Incorporated. X Window System, X and X11 are trademarks of the Massachusetts Institute of Technology. Looking Glass is a registered trademark of Visix Software Ltd. OSF/Motif is a trademark of the Open Software Foundation. Ethernet is a trademark of the Xerox Corporation. Wingz is a trademark and INFORMIX is a registered trademark of Informix Software Ltd. SUN, SPARC, and SPARCStation are trademarks of Sun Microsystems Computer Corporation. IBM is a registered trademark of International Business Machines Corporation. HP is a registered trademark of Hewlett Packard Inc. EMOTOROLA LTD. 2001
ii
ISSUE 1 REVISION 3
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Important notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First aid in case of electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Artificial respiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Burns treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warning labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specific warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Laser radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lifting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Do not ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Toxic material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Human exposure to radio frequency energy (PCS1900 only) . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum permitted exposures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum permitted exposure ceilings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power density measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Beryllium health and safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Health issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inhalation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Skin contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Eye contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handling procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disposal methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product life cycle implications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Caution labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specific cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fibre optics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2001
1 1 1 1 2 2 3 3 3 3 4 4 4 5 5 5 5 6 6 6 6 6 6 6 7 7 7 7 8 8 8 8 9 10 10 10 11 11 11 11 12 12 12 12 12 13 13 13 13 13 13
iii
ISSUE 1 REVISION 3
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special handling techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola GSM manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tandem OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaleable OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Category number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Catalogue number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ordering manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14 14 14 15 15 15 15 16 16 16 17 17 17
Chapter 1 GSM Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Evolution of GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase 2+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Station System (BSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Station (MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Services Switching Centre (MSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Home Location Register (HLR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Visitor Location Register (VLR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment Identity Register (EIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authentication Centre (AUC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Echo Canceller (EC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interworking Function (IWF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations and Maintenance Centre Radio (OMC-R) . . . . . . . . . . . . . . . . . . . . . . Interworking Function (IWF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeslot Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM Channel Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.4 Kbps Data Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Voice and Data through GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data connection through GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
11 12 12 12 12 14 14 14 16 16 16 16 16 16 16 16 18 110 110 112 114 116 118
Chapter 2 GPRS Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Todays use of Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Future Data Usage and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Industry Convergence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit and Packet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
i
21 22 24 26 28
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Circuit Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Datagrams and Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Datagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Permanent Virtual Circuit (PVC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Symbian and Bluetooth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Symbian . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bluetooth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wireless Application Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gateway GSN (GGSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serving GPRS Support Node (SGSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Control Unit (PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSC, HLR and VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gateway GPRS Support Node (GGSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serving GPRS Support Node (SGSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Control Unit (PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Mobile Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
210 212 214 214 214 214 216 216 216 218 220 222 222 222 222 222 224 224 224 226 228
Chapter 3 Terrestrial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity at the GGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Tunnelling Protocol (GTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Datagram Protocol (UDP) Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmission Control Protocol (TCP) Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet Protocol (IP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity at the SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subnetwork Dependent Convergence Protocol (SNDCP) . . . . . . . . . . . . . . . . . . . . . . . . SNDCP Service Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Link Control (LLC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Station System GPRS Protocol (BSSGP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSGP Virtual Connection Identifier (BVCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frame Relay Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
31 32 32 34 34 34 38 310 312 314 316 318 320
Chapter 4 Air Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Broadcast Control Channel (PBCCH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Common Control Channel (PCCCH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Dedicated Control Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2001
i
41 42 42 42 44 44
ISSUE 1 REVISION 3
Allocation of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release of PDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiframe Structure for PDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink Resource Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uplink Resource Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fixed Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Mobility Managment State Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Idle to Ready . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ready to Standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standby to Ready . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standby to Idle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ready to Idle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timing Advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity at the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Link Control (RLC) Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Medium Access Control (MAC) Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Physical Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Coding Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coding Scheme CS-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coding Scheme 2 (CS-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coding Scheme 3 (CS-3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coding Scheme 4 (CS-4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity at the GPRS MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Precedence Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delay Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reliability Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46 46 48 410 412 412 414 416 416 416 416 418 418 420 422 424 424 426 428 430 430 430 432 432 434 436 436 438 440
Chapter 5 GPRS Signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP Context Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS PDP Context Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network-Requested PDP Context Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging for GPRS Downlink Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Transfer MS Originated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Transfer MS Terminated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink Packet Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release of the Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
51 52 54 56 56 58 510 512 514 514 514 514
Chapter 6 Future Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
i
61
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Mobile Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSCSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced General Packet Radio Service (EGPRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced Data Rates for GSM Evolution (EDGE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UMTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Benefits of UMTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UMTS Future Vision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
62 64 66 68 610 614 616
Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A ......................................................................... B ......................................................................... C ......................................................................... D ......................................................................... E ......................................................................... F ......................................................................... G ......................................................................... I .......................................................................... L ......................................................................... M ......................................................................... N ......................................................................... P ......................................................................... Q ......................................................................... R ......................................................................... S ......................................................................... T ......................................................................... U ......................................................................... V .........................................................................
i
Glos1 Glos2 Glos3 Glos5 Glos6 Glos7 Glos8 Glos9 Glos10 Glos11 Glos12 Glos13 Glos15 Glos16 Glos17 Glos19 Glos20 Glos21
EMOTOROLA LTD. 2001
vii
ISSUE 1 REVISION 3
viii
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
General information
General information
Important notice
If this manual was obtained when you attended a Motorola training course, it will not be updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied under normal operational circumstances, to support a major software release, then corrections will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs).
Purpose
Motorola Global System for Mobile Communications (GSM) Technical Education manuals are intended to support the delivery of Technical Education only and are not intended to replace the use of Customer Product Documentation. WARNING Failure to comply with Motorolas operation, installation and maintenance instructions may, in exceptional circumstances, lead to serious injury or death. These manuals are not intended to replace the system and equipment training offered by Motorola, although they can be used to supplement and enhance the knowledge gained through such training.
About this manual
EMOTOROLA LTD. 2001
General information
ISSUE 1 REVISION 3
Cross references
Throughout this manual, cross references are made to the chapter numbers and section names. The section name cross references are printed bold in text. This manual is divided into uniquely identified and numbered chapters that, in turn, are divided into sections. Sections are not numbered, but are individually named at the top of each page, and are listed in the table of contents.
Text conventions
The following conventions are used in the Motorola GSM manuals to represent keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows: CTRL-c ALT-f | CR or RETURN Press the Control and c keys at the same time. Press the Alt and f keys at the same time. Press the pipe symbol key. Press the Return (Enter) key. The Return key is identified with the symbol on both the X terminal and the SPARCstation keyboards. The SPARCstation keyboard Return key is also identified with the word Return.
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
First aid in case of electric shock
First aid in case of electric shock

Warning
WARNING Do not touch the victim with your bare hands until the electric circuit is broken. Switch off. If this is not possible, protect yourself with dry insulating material and pull or push the victim clear of the conductor.
Artificial respiration
In the event of an electric shock it may be necessary to carry out artificial respiration. Send for medical assistance immediately.
Burns treatment
If the patient is also suffering from burns, then, without hindrance to artificial respiration, carry out the following: 1. 2. 3. Do not attempt to remove clothing adhering to the burn. If help is available, or as soon as artificial respiration is no longer required, cover the wound with a dry dressing. Do not apply oil or grease in any form.
EMOTOROLA LTD. 2001
Reporting safety issues
ISSUE 1 REVISION 3
Reporting safety issues

Introduction
Whenever a safety issue arises, carry out the following procedure in all instances. Ensure that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises: 1. 2. 3. 4. Make the equipment concerned safe, for example, by removing power. Make no further attempt to tamper with the equipment. Report the problem directly to GSM MCSC +44 (0)1793 430040 (telephone) and follow up with a written report by fax +44 (0)1793 430987 (fax). Collect evidence from the equipment under the guidance of the MCSC.
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Warnings and cautions
Warnings and cautions

Introduction
The following describes how warnings and cautions are used in this manual and in all manuals of the Motorola GSM manual set.
Warnings
Definition
A warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, or ill health. This includes hazards introduced during maintenance, for example, the use of adhesives and solvents, as well as those inherent in the equipment.
Example and format

WARNING Do not look directly into fibre optic cables or optical data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.
Cautions
Definition
A caution means that there is a possibility of damage to systems, or individual items of equipment within a system. However, this presents no danger to personnel.
Example and format

CAUTION Do not use test equipment that is beyond its calibration due date when testing Motorola base stations.
EMOTOROLA LTD. 2001
General warnings
ISSUE 1 REVISION 3
General warnings
Introduction
Observe the following warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola GSM manuals. Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola GSM manuals, violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Warning labels
Personnel working with or operating Motorola equipment must comply with any warning labels fitted to the equipment. Warning labels must not be removed, painted over or obscured in any way.
Specific warnings
Warnings particularly applicable to the equipment are positioned on the equipment and within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other warnings given in text, on the illustrations and on the equipment.
High voltage
Certain Motorola equipment operates from a dangerous high voltage of 230 V ac single phase or 415 V ac three phase mains which is potentially lethal. Therefore, the areas where the ac mains power is present must not be approached until the warnings and cautions in the text and on the equipment have been complied with. To achieve isolation of the equipment from the ac supply, the mains input isolator must be set to off and locked. Within the United Kingdom (UK) regard must be paid to the requirements of the Electricity at Work Regulations 1989. There may also be specific country legislation which need to be complied with, depending on where the equipment is used.
RF radiation
High RF potentials and electromagnetic fields are present in the base station equipment when in operation. Ensure that all transmitters are switched off when any antenna connections have to be changed. Do not key transmitters connected to unterminated cavities or feeders. Refer to the following standards: S S ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz. CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10kHz to 300GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.
6
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
General warnings
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible person must ensure that adequate lifting facilities are available. Where provided, lifting frames must be used for these operations. When equipments have to be manhandled, reference must be made to the Manual Handling of Loads Regulations 1992 (UK) or to the relevant manual handling of loads legislation for the country in which the equipment is used.
Do not ...
... substitute parts or modify equipment. Because of the danger of introducing additional hazards, do not install substitute parts or perform any unauthorized modification of equipment. Contact Motorola if in doubt to ensure that safety features are maintained.
Battery supplies
Do not wear earth straps when working with standby battery supplies.
Toxic material
Certain Motorola equipment incorporates components containing the highly toxic material Beryllium or its oxide Beryllia or both. These materials are especially hazardous if: S S S Beryllium materials are absorbed into the body tissues through the skin, mouth, or a wound. The dust created by breakage of Beryllia is inhaled. Toxic fumes are inhaled from Beryllium or Beryllia involved in a fire.
See the Beryllium health and safety precautions section for further information.
EMOTOROLA LTD. 2001
Human exposure to radio frequency energy (PCS1900 only)
ISSUE 1 REVISION 3

Introduction
This equipment is designed to generate and radiate radio frequency (RF) energy. It should be installed and maintained only by trained technicians. Licensees of the Federal Communications Commission (FCC) using this equipment are responsible for insuring that its installation and operation comply with FCC regulations designed to limit human exposure to RF radiation in accordance with the American National Standards Institute IEEE Standard C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz.
Definitions
This standard establishes two sets of maximum permitted exposure limits, one for controlled environments and another, that allows less exposure, for uncontrolled environments. These terms are defined by the standard, as follows:
Uncontrolled environment
Uncontrolled environments are locations where there is the exposure of individuals who have no knowledge or control of their exposure. The exposures may occur in living quarters or workplaces where there are no expectations that the exposure levels may exceed those shown for uncontrolled environments in the table of maximum permitted exposure ceilings.
Controlled environment
Controlled environments are locations where there is exposure that may be incurred by persons who are aware of the potential for exposure as a concomitant of employment, by other cognizant persons, or as the incidental result of transient passage through areas where analysis shows the exposure levels may be above those shown for uncontrolled environments but do not exceed the values shown for controlled environments in the table of maximum permitted exposure ceilings.
Maximum permitted exposures

The maximum permitted exposures prescribed by the standard are set in terms of different parameters of effects, depending on the frequency generated by the equipment in question. At the frequency range of this Personal Communication System equipment, 1930-1970MHz, the maximum permitted exposure levels are set in terms of power density, whose definition and relationship to electric field and magnetic field strengths are described by the standard as follows:
Power density (S)

Power per unit area normal to the direction of propagation, usually expressed in units of watts per square metre (W/m2) or, for convenience, units such as milliwatts per square centimetre (mW/cm2). For plane waves, power density, electric field strength (E) and magnetic field strength (H) are related by the impedance of free space, 377 ohms. In particular,
2 S + E + 377 377
H2 where E and H are expressed in units of V/m and A/m, respectively, and S in units of W/m 2. Although many survey instruments indicate power density units, the actual quantities measured are E or E2 or H or H2.
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Maximum permitted exposure ceilings

Within the frequency range, the maximum permitted exposure ceiling for uncontrolled environments is a power density (mW/cm2) that equals f/1500, where f is the frequency expressed in MHz, and measurements are averaged over a period of 30 minutes. The maximum permitted exposure ceiling for controlled environments, also expressed in mW/cm 2, is f/300 where measurements are averaged over 6 minutes. Applying these principles to the minimum and maximum frequencies for which this equipment is intended to be used yields the following maximum permitted exposure levels: Uncontrolled Environment 1930MHz Ceiling 1970MHz Controlled Environment 1930MHz 1970MHz
1.287mW/cm 2 1.313mW/cm 2 6.433mW/cm 2 6.567mW/cm 2
If you plan to operate the equipment at more than one frequency, compliance should be assured at the frequency which produces the lowest exposure ceiling (among the frequencies at which operation will occur). Licensees must be able to certify to the FCC that their facilities meet the above ceilings. Some lower power PCS devices, 100 milliwatts or less, are excluded from demonstrating compliance, but this equipment operates at power levels orders of magnitude higher, and the exclusion is not applicable. Whether a given installation meets the maximum permitted exposure ceilings depends, in part, upon antenna type, antenna placement and the output power to which this equipment is adjusted. The following example sets forth the distances from the antenna to which access should be prevented in order to comply with the uncontrolled and controlled environment exposure limits as set forth in the ANSI IEEE standards and computed above.
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Example calculation
For a base station with the following characteristics, what is the minimum distance from the antenna necessary to meet the requirements of an uncontrolled environment? Transmit frequency Base station cabinet output power, P Antenna feeder cable loss, CL Antenna input power Pin Antenna gain, G Using the following relationship: G + 4p r W Pin
2
1930MHz +39.0 dBm (8 watts) 2.0dB PCL = +39.02.0 = +37.0dB (5watts) 16.4dBi (43.65)
Where W is the maximum permissible power density in W/m2 and r is the safe distance from the antenna in metres, the desired distance can be calculated as follows: r+
GPin + 43.65 5 + 1.16m 4p W 4p 12.87

where W = 12.87 W/m2 was obtained from table listed above and converting from mW/cm 2 to W/m2. NOTE The above result applies only in the direction of maximum radiation of the antenna. Actual installations may employ antennas that have defined radiation patterns and gains that differ from the example set forth above. The distances calculated can vary depending on the actual antenna pattern and gain.
Power density measurements

While installation calculations such as the above are useful and essential in planning and design, validation that the operating facility using this equipment actually complies will require making power density measurements. For information on measuring RF fields for determining compliance with ANSI IEEE C95.1-1991, see IEEE Recommended Practice for the Measure of Potentially Hazardous Electromagnetic Fields - RF and Microwave, IEEE Std C95.3-1991. Copies of IEEE C95.1-1991 and IEEE C95.3-1991 may be purchased from the Institute of Electrical and Electronics Engineers, Inc., Attn: Publication Sales, 445 Hoes Lane, P.O. Box 1331, Piscattaway, NJ 08855-1331, (800) 678-IEEE or from ANSI, (212) 642-4900. Persons responsible for installation of this equipment are urged to consult these standards in determining whether a given installation complies with the applicable limits.
Other equipment
Whether a given installation meets ANSI standards for human exposure to radio frequency radiation may depend not only on this equipment but also on whether the environments being assessed are being affected by radio frequency fields from other equipment, the effects of which may add to the level of exposure. Accordingly, the overall exposure may be affected by radio frequency generating facilities that exist at the time the licensees equipment is being installed or even by equipment installed later. Therefore, the effects of any such facilities must be considered in site selection and in determining whether a particular installation meets the FCC requirements.
10
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Beryllium health and safety precautions

Introduction
Beryllium (Be), is a hard silver/white metal. It is stable in air, but burns brilliantly in Oxygen. With the exception of the naturally occurring Beryl ore (Beryllium Silicate), all Beryllium compounds and Beryllium metal are potentially highly toxic.
Health issues
Beryllium Oxide is used within some components as an electrical insulator. Captive within the component it presents no health risk whatsoever. However, if the component should be broken open and the Beryllium Oxide, which is in the form of dust, released, there exists the potential for harm.
Inhalation
Inhalation of Beryllium Oxide can lead to a condition known as Berylliosis, the symptoms of Berylliosis are similar to Pneumonia and may be identified by all or any of the following: Mild poisoning causes fever, shortness of breath, and a cough that produces yellow/green sputum, or occasionally bloodstained sputum. Inflammation of the mucous membranes of the nose, throat, and chest with discomfort, possibly pain, and difficulty with swallowing and breathing. Severe poisoning causes chest pain and wheezing which may progress to severe shortness of breath due to congestion of the lungs. Incubation period for lung symptoms is 220 days. Exposure to moderately high concentrations of Beryllium in air may produce a very serious condition of the lungs. The injured person may become blue, feverish with rapid breathing and raised pulse rate. Recovery is usual but may take several months. There have been deaths in the acute stage. Chronic response. This condition is more truly a general one although the lungs are mainly affected. There may be lesions in the kidneys and the skin. Certain features support the view that the condition is allergic. There is no relationship between the degree of exposure and the severity of response and there is usually a time lag of up to 10 years between exposure and the onset of the illness. Both sexes are equally susceptible. The onset of the illness is insidious but only a small number of exposed persons develop this reaction.
First aid
Seek immediate medical assistance. The casualty should be removed immediately from the exposure area and placed in a fresh air environment with breathing supported with Oxygen where required. Any contaminated clothing should be removed. The casualty should be kept warm and at rest until medical aid arrives.
EMOTOROLA LTD. 2001
11
ISSUE 1 REVISION 3
Skin contact
Possible irritation and redness at the contact area. Persistent itching and blister formations can occur which usually resolve on removal from exposure.
First aid
Wash area thoroughly with soap and water. If skin is broken seek immediate medical assistance.
Eye contact
May cause severe irritation, redness and swelling of eyelid(s) and inflammation of the mucous membranes of the eyes.
First aid
Flush eyes with running water for at least 15 minutes. Seek medical assistance as soon as possible.
Handling procedures
Removal of components from printed circuit boards (PCBs) is to take place only at Motorola approved repair centres. The removal station will be equipped with extraction equipment and all other protective equipment necessary for the safe removal of components containing Beryllium Oxide. If during removal a component is accidently opened, the Beryllium Oxide dust is to be wetted into a paste and put into a container with a spatula or similar tool. The spatula/tool used to collect the paste is also to be placed in the container. The container is then to be sealed and labelled. A suitable respirator is to be worn at all times during this operation. Components which are successfully removed are to be placed in a separate bag, sealed and labelled.
Disposal methods
Beryllium Oxide or components containing Beryllium Oxide are to be treated as hazardous waste. All components must be removed where possible from boards and put into sealed bags labelled Beryllium Oxide components. These bags must be given to the safety and environmental adviser for disposal. Under no circumstances are boards or components containing Beryllium Oxide to be put into the general waste skips or incinerated.
Product life cycle implications

Motorola GSM and analogue equipment includes components containing Beryllium Oxide (identified in text as appropriate and indicated by warning labels on the equipment). These components require specific disposal measures as indicated in the preceding (Disposal methods) paragraph. Motorola will arrange for the disposal of all such hazardous waste as part of its Total Customer Satisfaction philosophy and will arrange for the most environmentally friendly disposal available at that time.
12
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
General cautions
General cautions
Introduction
Observe the following cautions during operation, installation and maintenance of the equipment described in the Motorola GSM manuals. Failure to comply with these cautions or with specific cautions elsewhere in the Motorola GSM manuals may result in damage to the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other cautions given in text, on the illustrations and on the equipment.
Fibre optics
The bending radius of all fibre optic cables must not be less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices that are vulnerable to static discharge. Although the damage caused by static discharge may not be immediately apparent, CMOS devices may be damaged in the long term due to static discharge caused by mishandling. Wear an approved earth strap when adjusting or handling digital boards. See Devices sensitive to static for further information.
EMOTOROLA LTD. 2001
13
Devices sensitive to static
ISSUE 1 REVISION 3
Devices sensitive to static

Introduction
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of insulation that is susceptible to damage from electrostatic charge. Such a charge applied to the leads of the device could cause irreparable damage. These charges can be built up on nylon overalls, by friction, by pushing the hands into high insulation packing material or by use of unearthed soldering irons. MOS devices are normally despatched from the manufacturers with the leads shorted together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic foam. Provided the leads are shorted it is safe to handle the device.
Special handling techniques

In the event of one of these devices having to be replaced observe the following precautions when handling the replacement: S S S S S S Always wear an earth strap which must be connected to the electrostatic point (ESP) on the equipment. Leave the short circuit on the leads until the last moment. It may be necessary to replace the conductive foam by a piece of wire to enable the device to be fitted. Do not wear outer clothing made of nylon or similar man made material. A cotton overall is preferable. If possible work on an earthed metal surface. Wipe insulated plastic work surfaces with an anti-static cloth before starting the operation. All metal tools should be used and when not in use they should be placed on an earthed surface. Take care when removing components connected to electrostatic sensitive devices. These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to electrostatic damage. However PCBs should be handled with care, preferably by their edges and not by their tracks and pins, they should be transferred directly from their packing to the equipment (or the other way around) and never left exposed on the workbench.
14
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Motorola GSM manual set

Introduction
The following manuals provide the information needed to operate, install and maintain the Motorola GSM equipment.
Generic manuals
The following are the generic manuals in the GSM manual set, these manuals are release dependent:
Category number
GSM-100-101 GSM-100-201 GSM-100-311 GSM-100-313 GSM-100-320 GSM-100-321 GSM-100-403 GSM-100-423 GSM-100-501 GSM-100-521 GSM-100-523 GSM-100-503 GSM-100-721
Name
System Information: General Technical Description: OMC in a GSM System Technical Description: BSS Implementation Technical Description: BSS Command Reference Installation & Configuration: GSM System Configuration Installation & Configuration: BSS Optimization Maintenance Information: Alarm Handling at the OMC Maintenance Information: Device State Transitions Maintenance Information: BSS Field Troubleshooting Maintenance Information: GSM Statistics Application Software Release Notes: BSS/RXCDR
Catalogue number
68P02901W01 68P02901W31 68P02901W36 68P02901W23 68P02901W17 68P02901W43 68P02901W26 68P02901W57 68P02901W51 68P02901W56 68P02901W72
Operating Information: GSM System Operation 68P02901W14 Technical Description: OMC Database Schema 68P02901W34
Tandem OMC
The following Tandem OMC manuals are part of the GSM manual set for systems deploying Tandem S300 and 1475:
Category number
GSM-100-202 GSM-100-712
Name
Operating Information: OMC System Administration Software Release Notes: OMC System
Catalogue number
68P02901W13 68P02901W71
EMOTOROLA LTD. 2001
15
ISSUE 1 REVISION 3
Scaleable OMC
The following Scaleable OMC manuals replace the equivalent Tandem OMC manuals in the GSM manual set:
Category number
GSM-100-202 GSM-100-413 GSM-100-712
Name
Catalogue number
Operating Information: Scaleable OMC System 68P02901W19 Administration Installation & Configuration: Scaleable OMC Clean Install Software Release Notes: Scaleable OMC System 68P02901W47 68P02901W74
Related manuals
The following are related Motorola GSM manuals:
Category number
GSM-001-103 GSM-002-103 GSM-005-103 GSM-008-403
Name
System Information: BSS Equipment Planning System Information: DataGen System Information: Advance Operational Impact Installation & Configuration: Expert Adviser
Catalogue number
68P02900W21 68P02900W22 68P02900W25 68P02900W36
Service manuals
The following are the service manuals in the GSM manual set, these manuals are not release dependent. The internal organization and makeup of service manual sets may vary, they may consist of from one to four separate manuals, but they can all be ordered using the overall catalogue number shown below:
Category number
GSM-100-020 GSM-100-030 GSM-105-020 GSM-106-020 GSM-201-020 GSM-202-020 GSM-101-SERIES GSM-103-SERIES GSM-102-SERIES GSM-200-SERIES
Name
Service Manual: BTS Service Manual: BSC/RXCDR Service Manual: M-Cell2 Service Manual: M-Cell6 Service Manual: M-Cellcity Service Manual: M-Cellaccess ExCell4 Documentation Set ExCell6 Documentation Set TopCell Documentation Set M-Cellmicro Documentation Set
Catalogue number
68P02901W37 68P02901W38 68P02901W75 68P02901W85 68P02901W95 68P02901W65 68P02900W50 68P02900W70 68P02901W80 68P02901W90
EMOTOROLA LTD. 2001
16
ISSUE 1 REVISION 3
Category number
The category number is used to identify the type and level of a manual. For example, manuals with the category number GSM-100-2xx contain operating information.
Catalogue number
The Motorola 68P catalogue number is used to order manuals.
Ordering manuals
All orders for Motorola manuals must be placed with your Motorola Local Office or Representative. Manuals are ordered using the catalogue number. Remember, specify the manual issue required by quoting the correct suffix letter.
EMOTOROLA LTD. 2001
17
ISSUE 1 REVISION 3
18
EMOTOROLA LTD. 2001
Chapter 1
GSM Review
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
ii
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Chapter 1 GSM Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Evolution of GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase 2+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Station System (BSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Station (MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Services Switching Centre (MSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Home Location Register (HLR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Visitor Location Register (VLR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment Identity Register (EIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authentication Centre (AUC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Echo Canceller (EC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interworking Function (IWF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations and Maintenance Centre Radio (OMC-R) . . . . . . . . . . . . . . . . . . . . . . Interworking Function (IWF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeslot Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM Channel Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.4 Kbps Data Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Voice and Data through GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data connection through GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
11 12 12 12 12 14 14 14 16 16 16 16 16 16 16 16 18 110 110 112 114 116 118
EMOTOROLA LTD. 2001
iii
ISSUE 1 REVISION 3
iv
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Objectives
Objectives
On completion of this chapter the student should be able to: S S S Explain the Evolution of GSM. State the functions of the GSM Network entities. Explain GSM Channel Coding and Data connection through GSM.
EMOTOROLA LTD. 2001
11
The Evolution of GSM
ISSUE 1 REVISION 3

Phase 1
At the launch of GSM in 1991, the initial services offered were only the basic requirements of telephony and emergency calls. Data, Short Message Service and a limited set of supplementary services were also fully defined and began to appear in networks progressively over the following months and years.
Phase 2
Development continued with the Specifications and in 1995 they were frozen for a second time and called the Phase 2 Specifications. Phase 2 mobile phones appeared in the market place in the following year. The Phase 2 Specifications included the following: S S S S S S S Group 3 FAX Half rate speech Enhanced full rate speech Hierarchical cells Improved cell selection and reselection Second cipher algorithm More Supplementary Services
Phase 2+
Development of the specifications still continued after Phase 2 but releases of the new specifications were referred to as Phase 2+. The purpose of this terminology was to indicate a progression towards Third Generation Systems. Phase 2+ is not a single release but a phased yearly release of developing features and services. Among the more significant developments included in Phase 2+ are: S S S S S S S 14.4kbps user data High Speed Circuit Switched Data General Packet Radio Service SIM Application Toolkit Voice Group Call Service CAMEL (Intelligent Networks) Support of Optimal Routing
12
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Evolution of GSM
1990 Phase 1: Basic Services 1995 Phase 2: Enhanced Voice Enhanced Services Increased Capacity 1996 Phase 2+: Increased Data Rates Increased User Functionality
Basic Telephony
Emergency Services
SMS Your dinner is in the dog
Data Services: 3009600 bps Supplementary services: Call forwarding Call barring
GSM 900 Microcells
Macro cell Macro cell
GSM 900 Macrocells DCS 1800 Macrocells
Pico Cells
Micro cell
Pico Cells
CPO7_1_1
EMOTOROLA LTD. 2001
13
Network Architecture
ISSUE 1 REVISION 3
Base Station System (BSS)
The BSS is a collective term for the RXCDR, BSC and BTSs. The philosophy behind the BSS is that it takes full responsibility for all radio aspects of GSM, removing these functions from the MSC.
Base Station Controller (BSC)

A number of BTSs will be connected to and controlled by a BSC. The BSCs main function is control of BTSs and switching functions.
Remote Transcoder (RXCDR)

The RXCDR provides the interface between the MSC and BSS. Speech within the PSTN is at a rate of 64 kbps and this is also true within the MSC. The RXCDR reduces this rate to 13 kbps for transmission over the Air Interface.
Base Transceiver Station (BTS)

This network element the radio transceivers that communicate with mobile phones, and antenna system and supporting hardware and software.
Mobile Station (MS)

The MS is the collective term given to the ME and SIM combination.
Mobile Equipment (ME)

This is the physical hardware of the mobile phone.
Subscriber Identity Module (SIM)

The SIM is a smart card that is inserted into the mobile phone and provides the users identity. The SIM supports: S S S S User identification Location information Security Ciphering functions.
14
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Network Management Centre
NMC NSS OMCS
OMCR RXCDR
BSC
BTS
BTS
BTS
Mobile Station (MS)
CPO7_1_2
EMOTOROLA LTD. 2001
15
Mobile Services Switching Centre (MSC)
ISSUE 1 REVISION 3

The MSC is the heart of the fixed infrastructure and is effectively a telephone exchange for GSM mobile calls. It is responsible for: S S S Making the appropriate connections to establish telephone calls Linking the GSM network into the PSTN Billing
Home Location Register (HLR)

The HLR provides a permanent record of all subscribers who belong to the home network. There is one HLR per network.
Visitor Location Register (VLR)

The VLR holds subscriber details temporarily whilst a user is within a particular geographical area. The VLR therefore holds records for subscribers of the home network and subscribers from other networks. There is usually one VLR per MSC covering typically the area of a city.
Equipment Identity Register (EIR)

The EIR is concerned with the security features of the Mobile Equipment. That is, a stolen MS may be recorded in the EIR and prevented from accessing the network.
Authentication Centre (AUC)

The AUC is concerned with security and ciphering.
Echo Canceller (EC)

The EC will provide cancellation of up to 68 milliseconds of delay and prevent any echo due to combining of signals from 4 wires to 2 wires.
Interworking Function (IWF)

The IWF provides an interface between GSM and other networks involved in the transport of user data.
Operations and Maintenance Centre Radio (OMC-R)

The OMC-R is a centralised control point from which the performance of the network can be remotely monitored and controlled. There will normally be one OMC-R per regional area on the network.
16
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
NSS VLR IWF Data Networks RXCDR
AUC HLR
MSC PSTN
EIR
EC
BSC
BTS
BTS
BTS
Mobile Station (MS)
CPO7_1_3
EMOTOROLA LTD. 2001
17
ISSUE 1 REVISION 3

The interconnection of the MSC with certain networks requires adaptation of the GSM transmission peculiarities to those of the partner network. These adaptations are the Interworking Function (IWF). In basic terms the IWF is a transmission and protocol adaptation equipment. It enables interconnection with networks such as PSPDNs (PacketSwitched Public Data Networks) or CircuitSwitched Public Data Networks (CSPDNs), but also exists when the partner network is simply the PSTN or the ISDN. The IWF also incorporates a modem bank, which may be used when, for example, the GSM Data Terminal Equipment (DTE) exchanges data with a land DTE connected via an analogue modem. The IWF function can be incorporated as part of the MSC or performed by separate equipment.
18
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Other Network Server
Base Station System
VLR
IWF
AUC HLR
MSC
EIR
CPO7_1_4
EC
EMOTOROLA LTD. 2001
19
Channel Combinations
ISSUE 1 REVISION 3
The different logical channels can be combined into one frame to allow a saving in the frequency spectrum. Common combinations include: S S S S Traffic Combination BCCH Combination DCCH Combination Combined Channel Combination TCH/FACCH + SACCH BCCH + CCCH SDCCH + SACCH BCCH + CCCH + SDCCH + SACCH
Timeslot Allocation
Some channel combinations can be sent on any timeslot but others have dedicated timeslots, the table opposite lists the restrictions.
110
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Combination Timeslots
Combination Traffic Broadcast Dedicated Combined
Timeslot Any 0, 2, 4, 6 but 0 first Any 0 only
BCCH CCCH TS0
SDCCH TS1
TFC TS2
TFC TS3
TFC TS4
TFC TS5
TFC TS6
TFC TS7
CPO7_1_5
EMOTOROLA LTD. 2001
111
GSM Channel Coding
ISSUE 1 REVISION 3
GSM Channel Coding

The process of passing speech and data over the air interface is complicated and involves many subprocesses that are essential to GSM. Without them the received signal would be full of errors and unintelligible, as the radio path is a very hostile environment to our sequence of ones and zeros. Before the actual radio path characteristics are dealt with we must first look at what can be done to the speech prior to radio transmission, the treatment of data is not exactly the same, but is very similar. The process can be broken down into 6 simple blocks: S S S S S S Digitising and Source coding conversion of speech into digital. Channel Coding application of forward error correction techniques and block convolutional coding. Bit interleaving spreading the information across many timeslots to improve the robustness of the radio signal to noise. Ciphering security of the radio signal to eaves droppers. Burst Formatting format the information into the bursts transmitted in the timeslots. Modulation positioning the information onto a carrier medium that can be used on a radio link.
112
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
GSM Channel Coding
GSM Channel Coding
MS
Data input
Tx and antenna
8 timeslots 270.8 kbps Digitising and Source Encoding 13 kbps 22.8 kbps 33.8 kbps Modulation
Channel Coding
Bit interleaving
Burst Formatting
Ciphering
CPO7_1_6
EMOTOROLA LTD. 2001
113
14.4 Kbps Data Rate
ISSUE 1 REVISION 3
14.4 Kbps Data Rate

We already know that GSM supports a user rate of 9.6 kbps resulting in a 12 kbps radio interface rate and the aim of this work item was to improve on that with a minimal amount of changes to the current specifications. 14.4 kbps can be achieved by changing the puncturing scheme used during the channel coding sequence and by transmitting 290 bits (288 bits of user data) every 20ms as opposed to 240 bits. The 2 remaining bits are for status and control information. This results in a radio interface rate of 14.5 kbps instead of 12 kbps but due to the puncturing scheme maintains a rate of 22.8 kbps over the Air Interface.
114
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
14.4 Kbps Data Rate
Channel Coding Sequence
GSM at present 12 kbps (9.6 kbps user rate)

240 bits Block Code 240 + 4 244 bits Half rate Convolutional Code 488 bits Puncturing 488 32 22.8 kbps 456 bits
Phase 2+ 14.5 kbps (14.4 kbps user rate)

290 bits Block Code 290 + 4 294 bits Half rate Convolutional Code 588 bits Puncturing 588 132 22.8 kbps 456 bits
CPO7_1_7
EMOTOROLA LTD. 2001
115
Voice and Data through GSM
ISSUE 1 REVISION 3

The most familiar method of transferring data to most people is by using the PSTN (to make the connecton to the receiving party) and a modem (to make the connection to the PSTN). Although data is digital and the PSTN is digital, the local loop connecting the fixed subscriber to the PSTN is analogue. The modem converts the digital data to analogue in order to carry it to the PSTN. This little bit of basic theory is very applicable to GSM simply because when a GSM subscriber is transferring data over GSM there is a high probability that the other end of the link will be a PSTN connection to a modem. Other types of data transfer (e.g. a digital connection to a Packet Network) are very similar.
Mobile user data connection

A modem is still required because the PSTN accepts at its input, audio signals. It would be reasonable to assume that the GSM network might be situated between the modem and the PSTN. This might have been possible in GSM but presented technical difficulties. Instead GSM was designed to fit between the laptop and the modem. The entire GSM link is inserted between the laptop and modem.
116
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Voice and data through GSM
DCE Data and Control Analogue 3.1 kHz DTE ADC 64 kbps ADC PSTN
Analogue 3.1 kHz
DCE/modem
GSM
MS
DTE
DTE
CPO7_1_8
EMOTOROLA LTD. 2001
117
Data connection through GSM
ISSUE 1 REVISION 3

The output from the laptop is a maximum of 9.6kbps of data and RS232 control signals. The control signals must also be carried to the modem and increase the bit-rate to 12kbps. Typically a Data Card inserted into a PCMCIA slot of the laptop will convert these signals (data and control) into a 12kbps serial bit stream for connecting to a mobile phone. The mobile phone adds on bits for error protection and transmits across the Air Interface at 33.8kbps. This occupies one complete timeslot, as does a normal voice link. At the BSS (BTS/BSC) the error protection bits are removed and the 12kbps of data are transferred to the XCDR at 16kbps (as with speech, a padding process for transfer over E1 links). The XCDR rate adapts this to 64kbps (padding) for transfer to the MSC. Finally the MSC relays the signal to a GSM network entity known as the interworking function (IWF). This contains a Rate Adapter which will remove the 64kbps padding, reconvert the serial 12kbps into the original 9.6kbps data plus control signals and feed to the modem (also situated in the IWF). When connecting to other networks e.g. ISDN or a Packet Network the arrangement is very similar but the DCE is not a modem but ISDN connector or a Packet Assembler/Dissembler (PAD). These alternative DCEs are again situated in the IWF and rate adaptation through the GSM network is unchanged.
118
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
PSTN
9.6 kbps Modem
IWF Rate Adapter 12 (64) kbps MSC 12 (64) kbps RXCDR 12 (16) kbps BSC
DTE 12 (16) kbps 9.6 kbps Data and control

DTE
CPO7_1_9
12 kbps PCMCIA 12 (33.8) kbps
BTS
EMOTOROLA LTD. 2001
119
ISSUE 1 REVISION 3
120
EMOTOROLA LTD. 2001
Chapter 2
GPRS Outline
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
ii
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Chapter 2 GPRS Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Todays use of Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Future Data Usage and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Industry Convergence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit and Packet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Datagrams and Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Datagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Permanent Virtual Circuit (PVC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Symbian and Bluetooth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Symbian . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bluetooth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wireless Application Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gateway GSN (GGSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serving GPRS Support Node (SGSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Control Unit (PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSC, HLR and VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gateway GPRS Support Node (GGSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serving GPRS Support Node (SGSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Control Unit (PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Mobile Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
21 22 24 26 28 210 212 214 214 214 214 216 216 216 218 220 222 222 222 222 222 224 224 224 226 228
EMOTOROLA LTD. 2001
iii
ISSUE 1 REVISION 3
iv
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Objectives
Objectives
On completion of this chapter the student should be able to: S S S S S Explain the difference between Circuit and Packet switching. State how Virtual Circuits are created. Explain the impact of Industry convergence toward Internet Protocol (IP). Explain the structure and function of a WAP network. Identify the GPRS entities and explain their functions.
EMOTOROLA LTD. 2001
21
Todays use of Data
ISSUE 1 REVISION 3
Todays use of Data

GSM was designed from the ground up for data transmission as well as voice, but takeup has been slow. Wireless data currently produces a mere 2% of GSM network revenues (Finland has the highest, with 5%). Yet at the same time more people are becoming mobile and by the end of the decade they will represent 30% of the workforce. The need for faster, cheaper, smarter and bettermanaged services clearly exists with the key service being the mobile intranet i.e. secure wireless access to the corporate environment over the Internet. There are four main reasons for the slow takeup of wireless data systems: S S S S The notebook PC/phone link was (and still is) proprietary, so the PC card is expensive. Voice and data required a user to use two devices, and carrying a phone about is irrelevant to a datacentric worker. The transfer rate of 9.6kbit/s, albeit with robust error correction, was perceived as too low and the cost of mobile email and faxing as too high. The industry was not marketing a true solution mobile data involves a convergence of communications and computing technologies, and until recently users had to apply the glue themselves.
22
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Todays use of Data
Todays use of Data
S S S S S
13% of network traffic Data users are mainly premium subscribers. SMS a small, growing number of products. Difficult to use (handset, PC connection). Cost circuit based technology. Low data rate Speed of 9.6 kbps or 14 kbps
EMOTOROLA LTD. 2001
23
Future Data Usage and Applications
ISSUE 1 REVISION 3

The introduction of any mobile multimedia services will be driven by actual user needs. For personal communications services to reach the hopedfor penetration rates of 7080 per cent, services must have massmarket appeal: they need to be easy to use and costjustifiable. With the fantastic growth in Internet / Intranet usage, however, demand is already growing for higher speeds in order to access corporate resources while on the move. This type of multimedia application demands high peak bitrates in short bursts, while the information is downloaded, in one direction. Another potential multimedia application is simultaneous voice and data, for example, for PC application sharing or shared whiteboard. Although this type of application does not require particularly high bit-rates, it does require realtime, continuous operation because of its voice content.
24
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Data growth how much and why
90 80 70 60 50 40 30 20 10 0 1995 2000 2005 Analysis High Tele Finland Analysis low
Consensus of forecasts is that data will form at least 20% of GSM traffic by 2005. This implies at least 15 x todays data volume
Source: Motorola
CP07_2_02
EMOTOROLA LTD. 2001
25
Industry Convergence
ISSUE 1 REVISION 3
Voice and data are converging and starting to be carried on the same networks, but opinions vary on how quickly this is happening and what impact it will have on the IT and telcos. Businesses are wondering what benefits it will bring and how soon they should add voice to their data networks. Today the volume of data in telecomms networks has surpassed voice, Within 4 years the big US telcos are predicting that 99% of telecomms traffic will be data. Already there have been many merges, acquisitions and alliances spanning telecomms and IT as leading companies jostle for position, once such example is the partnership between Motorola & Cisco. Many of the recent merges and acquisitions have been brought about by telecomms equipment companies buying up the IT companies that make Internet Protocol (IP) telephony products. These products allow data to be carried cheaply over networks based on the IP protocol used on the internet. They can also be used to carry Voice over IP (VOIP) by converting it into small packets of data. In this way more voice calls can be sent down a single line. Examples of such acquisitions include Alcatel buying Xylan, Nortels purchase of Bay Networks, Lucent acquiring Ascend and Nokia buying Ipsilon. It is estimated that full IP networks will not be deployed until 2 years time. Some of the mission elements include: S S S S Voice gateways End to end control QoS support (except when sent over another standard e.g. ATM) Network management facilities
One of the main benefits to the customer is that of reduced network infrastructure costs because there will be no need for separate data and telecomms networks.
26
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Computer
internet access electronic mail real time images multimedia mobile computing
Mobility High speed services
Media
streaming audio video on demand interactive video services TV/Radio / Data contribution & distribution
IP
Mobility Wideband services
Mobility Personal services
Telecommunication
ISDN services video telephony wideband data services
CP07_2_07
EMOTOROLA LTD. 2001
27
Circuit and Packet Switching
ISSUE 1 REVISION 3

The advantages of transferring data using packet switching as opposed to circuit switching have long been recognised. Circuit switching provides a fixed bandwidth channel over a unique path from user to user for the duration of the call. It is therefore inefficient when dealing with bursty or Variable Bit Rate (VBR) traffic (e.g. data) as the maximum required bit rate must be maintained throughout the duration of the call therefore leaving resources under-utilised for much of the time. Packet switching can be used for data traffic that is generated in bursts and is therefore ideal for Variable Bit Rate data transport. The paths taken by successive packets may not be the same. Overhead information is added to the data to enable the network to route it correctly and the recipient has to assemble the packets in the correct sequence. Delays are also incurred when packets queue at switches. For constant bit rate voice and video it can cause a relatively high delay as well as uncertain queuing delays. GSM has, until GPRS, used circuit switched connections. A bi-directional traffic channel is established and therefore chargeable, to the user for the duration of the call whether traffic is actually being transferred or not. Consider as an example the inefficiency of using the Internet and downloading large quantities of data. The uplink, though barely being used, is nevertheless an available resource, which is being charged. Packet switching divides the data into individual, limited size containers (packets) and sends them through the network along communication lines being shared by other channels.
28
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Circuit Switching A complete resource allocated to an individual device
Packet Switching Devices share the available resources
Its All Mine!
Which exit did you say?
EMOTOROLA LTD. 2001
29
Circuit Switching
ISSUE 1 REVISION 3
Circuit Switching
The diagram shows separate paths (circuits) AB and AC that are created through a Circuit Switched Data Network (CSDN). In this example, the paths are 64kb/s channels (timeslots) provided within an E1 TDM frame that operates at 2.048 Mb/s; the timeslots are switched at the switching nodes in order to create the required paths. The circuits are permanently provisioned and operate at fixed data rates (64kb/s); Nx64kb/s circuits could also be provisioned for higher bandwidth applications. Note that a duplex path (i.e. A/B and B/A) is provided. Circuit switching takes place at the OSI physical layer, and there is no provision for error control or flow control. However, circuit switched paths are protocol transparent they provide basic pipes for transmission. The same DTE interface (X.21 in this example) is usually required at each end of the circuit. Circuit switched paths are generally suitable for applications that require a fixed, short delay e.g. voice and video. The bandwidth available is permanently dedicated to the circuit and the paths are non-blocking. However, this is wasteful for many data applications which are bursty by nature, or which involve a short request / long response.
210
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Circuit Switching
Circuit Switching
CSDN
Physical L1
Physical
Physical
Physical
Physical
CP07_2_04
EMOTOROLA LTD. 2001
211
Packet Switching
ISSUE 1 REVISION 3
Packet Switching
In a Packet Switched Data Network (PSDN), data to be transmitted is first segmented by the source DTE into message units called packets. Each packet includes the network addresses of the source and destination DTEs. On receipt of each packet, the Packet Switch Exchange (PSE) stores it while inspecting the destination address; each PSE has a routing table specifying the outgoing link(s) to be used for each destination network address. The PSE then forwards the packet on the appropriate link at the rate of that link. This method of working is known as storeandforward . A number of packets may arrive simultaneously at a PSE on different incoming links for forwarding on the same outgoing link. Packets may therefore experience unpredictably long delays. (To prevent this, a maximum length is specified for each packet). The PSDN has a meshed topology that offers multiple alternate routes for packets. In the diagram, there are two alternate routes between any pair of PSEs. The PSDN therefore provides a resilient networking service. As packet networks use storeandforward, the two communicating DTEs can have different access speeds to the network. The transmission links between PSEs are better utilised because users only occupy bandwidth when data is being sent and a number of such users can therefore share the available transmission bandwidth. This technique is known as statistical multiplexing a statistical gain is achieved because it is unlikely that all users will be transmitting at the same time. On packet switched networks, error control and flow control are performed on each link. Error control ensures that packets are delivered errorfree and in sequence, and flow control provides a method of reducing congestion during busy periods. Overheads for these functions are carried by each packet and employed by each PSE at OSI Layers 2 and 3. Packet switching can achieve equipment economies because many DTEs can be connected to a single PSDN access equipment. Packets switching matches the characteristics of many data applications (occasional, bursty transfer of data). Its statistical nature means that it is efficient. It does not offer a constant, lowdelay performance and is not therefore suitable for delay sensitive applications e.g. voice and video.
212
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Packet Switching
Packet Switching
B
a c PSE
a c a b a c
Data Packet where:
PSDN
PSE
b c a d
c = destination address a = source address
PSE
PSE
Higher Layers X.25 LAP.B Physical
D
L3 L2 L1 X.25 LAP.B Physical X.25 LAP.B Physical X.25 LAP.B Physical
Higher Layers X.25 LAP.B Physical

CP07_2_05
EMOTOROLA LTD. 2001
213
Datagrams and Virtual Circuits
ISSUE 1 REVISION 3

The two types of service normally supported by a PSDN are known as datagram and virtual circuit services.
Datagrams
The datagram service is normally used for the transmission of short, singlepacket messages. Each packet that enters the network is treated as a selfcontained entity with no relationship to other packets. The packets can be therefore be forwarded over different routes to the same destination. Datagrams provide a connectionless service.
Virtual Circuit
The virtual circuit service is used when a message contains multiple packets. It is a connectionoriented service. Before any data packets are sent, the source DTE sends a call request packet to PSE1 (see diagram) containing the network address of the destination DTE and a reference number called the Virtual Circuit Identifier (VCI). PSE 1 notes the VCI and forwards the packet through the network according to the information contained in its routing table. It assigns a new VCI to the route PSE1 PSE2, and updates its routing table as shown. At PSE2, another VCI is assigned to the call request packet before it is forwarded on the outgoing link to the destination DTE. Assuming that the call is accepted, an appropriate response packet is returned to the calling DTE. At this point, a virtual circuit (VC) exists between the two DTEs. During the subsequent data transfer phase, all data packets relating to the call DTE1 DTE2 are assigned the same VCIs along the virtual circuit. In this way, the source and destination DTEs can readily distinguish between packets arriving on the same link that relate to different calls multiple calls are thereby multiplexed on to the same link. All packets take the same route across the network and should therefore arrive in sequence. The network addresses are only required in the initial call request and call accept packets.
Permanent Virtual Circuit (PVC)

When the data transfer phase is complete, a cleardown packet is sent and the VCIs are released. If DTE1 frequently requires to communicate with DTE2, the VC may be left permanently established this is known as a PVC. This can be more economical since the cost of the call will usually be based on the quantity of data transferred, not the duration, although the user must pay for the PVC facility.
214
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Virtual Circuits
PSE1 1 2 DTE1 VCI(1) VCI(2)
PSE2 1 2 DTE2 VCI(3)
Virtual Circuit Routing Table PSE1 IN VCI(1) / Link(1) VCI(2) / Link(2) OUT VCI(2) / Link(2) VCI(1) / Link(1) Routing Table PSE2 IN VCI(2) / Link(1) VCI(3) / Link(2) OUT VCI(3) / Link(2) VCI(2) / Link(1)
CP07_2_06
EMOTOROLA LTD. 2001
215
Symbian and Bluetooth
ISSUE 1 REVISION 3

Symbian
Symbian was launched in 1998 and is a joint venture between some of the leading mobile and PDA manufacturers (Ericsson, Motorola, Nokia, Panasonic and Psion). Symbian owns, licenses, develops and supports EPOC technology which provides software, application frameworks and development tools for Wireless Information Devices such as Communicators and Smartphones. The EPOC technology includes customisable user interfaces, colour support, fitforpurpose application suites, advanced Internet connectivity and PC connectivity software. It is their thirdgeneration operating system for mobile ROMbased computing. It is multitasking, 32bit OS supporting a penbased GUI and networking capabilities. It is componentbased and can be scaled from relatively large configurations for a fully functional handheld computer, to small configurations for embedded applications. EPOC is optimised for lowpower, compact machines, and longrunning, missioncritical, applications.
Bluetooth
Bluetooth is an open specification for wireless communications of data and voice. It is based on a lowcost shortrange radio link, built into a 9 x 9 mm microchip, and is designed to replace cables which are currently used to connect peripheral terminals and devices. Bluetooth technology enables connection of mobile computers, digital cellular phones, handheld devices, network access points and other mobile devices via wireless shortrange radio links unimpeded by lineofsight restrictions. Products are likely to become available at the end of 1999. Bluetooth technology will increase the ease and breadth of wireless connectivity. Users will be able to automatically receive email on their notebook computers via the digital cellular phones in their pockets or synchronise their primary PC with their handheld computer.
216
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Symbian
Symbian
Links applications
WAP
Links Internet
Bluetooth
Links devices
CP07_2_08
EMOTOROLA LTD. 2001
217
Wireless Application Protocol
ISSUE 1 REVISION 3

Both the wireless data market and the Internet are evolving network technologies, which are growing very quickly and are continuously reaching new customers. The Wireless Application Protocol (WAP) is positioned at the convergence of these two technologies resulting in the WAP Forums efforts to promote industry wide specifications for technology useful in developing applications and services that operate over wireless communication networks. An application framework and network protocols have been specified for wireless devices such as mobile phones, pagers and personal digital assistants (PDAs). The effort is aimed at enabling operators, manufacturers and content developers to meet the challenges in building advanced differentiated services and implementations in a fast and flexible manner. The WAP Forum originally consisted of the manufacturers Ericsson, Motorola and Nokia together with the software house Unwired Planet but there are now many more companies with a vested interest in mobile data systems. WAP is being promoted as a major breakthrough that will achieve universal Internet based information access on wireless devices and as such allow software developers to be able to write once for all networks worldwide. In addition, operators will be able to implement gateways that work with many brands of phones and all applications and content. Also, handset manufacturers will be able to make high volume, and thus low cost handsets, which can be implemented into all networks. The Wireless Application Environment (WAE) is undertaking to build a generalpurpose application environment based fundamentally on the World Wide Web (www) technologies and philosophies. The WAE architecture includes all elements of the WAP architecture related to application specification and execution. To date, the WAE architecture is predominately focused on the clientside aspects of WAPs system architecture, namely items relating to user agents. Such an approach has worked particularly well with a browser (a class of user agent) model such as that used in the WWW. The Internet and the WWW were the inspiration behind significant elements of the WAE specification and consequently, a similar approach is used within the WAE.
218
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Objectives of the WAP Forum

S S S S Bring internet content and advanced data services to cellular phones and other wireless terminals. Create a global wireless specification that will work across differing wireless network technologies. Enable the creation of content and applications that scale across a very wide range of bearer networks and device types. Embrace and extend existing standards and technology wherever appropriate.
Client
Gateway
Origin Server
Encoded Request
Request
Common Gateway Interface Scripts
WAE User Agent
Encoders and Decoders
Encoded Content
Content
Content
CP7_2_08a
EMOTOROLA LTD. 2001
219
GPRS
ISSUE 1 REVISION 3
GPRS
GPRS is a set of new GSM bearer services that provides packet mode transmission within the PLMN and interworks with external networks whilst not preventing the users operation of other GSM services. GPRS will allow the service subscriber to send and receive data in an endtoend packet transfer mode, without utilising network resources in circuit switched mode. This enables a more cost effective and efficient use of network resources for applications displaying one or more of the following characteristics: S S S Intermittent, bursty data transmissions, where the time between successive transmissions greatly exceeds the average transfer delay. Frequent transmissions of small volumes of data (e.g. less than 500 octets) occurring at a rate of up to several transactions per minute. Infrequent transmissions of larger volumes of data (e.g. several kilobytes) occurring at a rate of up to several transactions per hour.
220
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
GPRS
GPRS Network Entities
MSC
BTS
Abis
BTS
BSC
GDS (Motorola) Gb Frame Relay Gr
PCU
Gs
HLR
SGSN
Gn
TCP/IP Backbone Gn Gn
SGSN
To another PLMN
Gp
GGSN
Gi
PDN
Net103_1_2
EMOTOROLA LTD. 2001
221
Infrastructure
ISSUE 1 REVISION 3
Infrastructure
At present, the GSM network is based on circuit switched connections and thus radical modifications to the architecture will be required to support the packet switching technology of GPRS. However, the primary and familiar physical characteristics of the air interface will remain largely intact although a series of new GPRS radio channels has been defined. The most significant addition to the infrastructure will be the GPRS Support Nodes (GSN) which will act in parallel with MSCs to supply traffic to the BSS.
Gateway GSN (GGSN)

The GGSN will interface between the BSS and various packet switched networks, (in much the same way that an MSC forms an interface between the BSS and the PSTN). The role of GSNs has been likened to that of routers in other data networks. The GGSN can best be compared to carrying out a similar task to that of the Gateway MSC and provides the functionality of the IWF.
Serving GPRS Support Node (SGSN)

The Serving GPRS Support Node (SGSN) offers very similar functionality to that of the MSC in a GSM network.
Packet Control Unit (PCU)

The PCU attaches to existing the Base Station Controller (BSC). The PCU is responsible for all functions of GPRS radio protocols and communications with the SGSN.
MSC, HLR and VLR

The MSC and VLR are utilised for initial registration and contacting GPRS MSs but are not needed when routing GPRS data. The HLR holds information about the subscription details and the AUC is required for authentication and ciphering. The EIR can be used for authenticating MS hardware.
222
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Infrastructure
GPRS Network Entities
MSC
BTS
Abis
BTS
BSC
GDS (Motorola) Gb Frame Relay Gr
PCU
Gs
HLR
SGSN
Gn
TCP/IP Backbone Gn Gn
SGSN
To another PLMN
Gp
GGSN
Gi
PDN
Net103_1_2
EMOTOROLA LTD. 2001
223
GPRS network elements
ISSUE 1 REVISION 3

Gateway GPRS Support Node (GGSN)
The GGSN is the node that is accessed by the Packet Data Network (PDN) due to appropriate evaluation of the Packet Data Protocol (PDP) address (e.g. X.25 or IP address). The GGSN is linked to the external PDNs via the Gi interface or to GPRS networks in different Public Land Mobile Networks (PLMN) via the Gp interface. As such, the GGSN is the first point of interconnection. The GGSN may also connect to the Home Location Register (HLR) which allows routing information to be passed back down to the GGSN which in turn allows the Packet Data Units (PDU) to be tunnelled towards the MS. With regards to network access, the GGSN can provide message screening functionality to assist in security as well as providing a means of collecting network data for charging purposes. On the other side of the GGSN, the Gn interface provides the connection towards the Serving GPRS Support Node (SGSN). PDUs will be carried on this interface by means of encapsulation into an IP datagram. This allows both X.25 and IP PDUs to be carried in the similar formats across the GPRS network.
Serving GPRS Support Node (SGSN)

The SGSN is the node that is serving the MS and as such, the SGSN deals with both mobility management and security. The SGSN will establish a PDP context to allow PDUs to be transferred between the MS and the GGSN that the MS is currently utilising. To maximise the efficiency of the connection, data compression techniques may be activated between the SGSN and the MS. The SGSN will connect with the MSC/VLR of the GSM network via the Gs interface. This will be used to deal with GPRS/GSM interactions when the same resource is being utilised by both technologies. The Gd interface provides a connection towards the Short Message Service-Centre (SMSC) as the GPRS bearer is able to support SMS PointtoPoint messages. If an Equipment Identity Register (EIR) is supported in the network, the SGSN will link to it via the Gf interface. Depending upon routing requirements, the PDUs will pass from the SGSN down to the Packet Control Unit (PCU) which is located at the BSS. This connection is made via the Gb interface.
224
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Gateway GPRS Support Node Functionality

S S S S S Transport Layer Routing Protocol Support PDU Tunnelling Screening Data/Packet Counting Address Mapping, Routing Tables
Serving GPRS Support Node Functionality

S S S S S S Mobility Management Ciphering Compression GSM Circuit Switched Interactions BSS Queue Management Data Packet Counting
EMOTOROLA LTD. 2001
225
ISSUE 1 REVISION 3

The new BSS functionality for GPRS mainly resides at the Packet Control Unit (PCU). The PCU includes the handling of frame relay, Network Services Signalling, BSSGP signalling, routing of signalling messages, Radio Link Control (RLC) and Media Access Control (MAC) preload and transferring of user data. User data is routed to the PCU via the CCU uplink from the BTS to the BSC and then over E1 to the PCU. At the PCU the RLC Blocks are reformulated in Logical Link Control (LLC) frames and forwarded to the SGSN. BSSGP signalling and NS signalling shall occur between the PCU and the SGSN using frame relay protocol. There is also signalling between existing functional process at the BSC such as the BSP and the PCU via the E1 Span, as well as between the PCU and Channel Coders.
226
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
MSC
G PRS core network

RXCDR A Interface SGSN
BSC
GDS
PCU
A-bis interface
BTS
BTS
CP07_2_17a
EMOTOROLA LTD. 2001
227
GPRS Mobile Stations
ISSUE 1 REVISION 3

A GPRS MS can operate in one of three modes of operation. The mode of operation will depend upon the services that the MS is attached to, i.e., only GPRS or both GSM and GPRS. The three different modes of operation are defined in terms of mobile classes and can be defined as such: S Class A will support simultaneous attach, simultaneous activation, simultaneous monitor, simultaneous invocation and simultaneous traffic. Thus the subscriber using a Class A MS can make and/or receive calls on the two services simultaneously subject to the QoS requirements. Class B will support simultaneous attach, simultaneous activation, simultaneous monitor. It will, however, only support limited simultaneous invocation such that GPRS virtual circuits will not be cleared down due to the presence of circuit switched traffic. Under such circumstances, the GPRS virtual connection is then busy or held. A Class B MS will not support simultaneous traffic. The subscriber can make or receive calls on either of the two services sequentially but not simultaneously. The selection of the appropriate service is performed automatically. Class C will support only nonsimultaneous attach, i.e. alternate use only. If both services are supported, then a Class C MS can make and/or receive calls from only the manually or default selected service. The status of the service not selected is detached or not reachable. In addition, the ability of a Class C MS to receive and transmit SMS messages is optional.
It should be noted that nonvoice only MSs do not have to (but may) support emergency calls.
228
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
GPRS MS Class Capabilities
Class A
Class B
Class C
Data
Voice
Data
Voice
Data
Voice
At the same time
Automatically at different times
User or Service Provider selects
CP07_2_18
EMOTOROLA LTD. 2001
229
ISSUE 1 REVISION 3
230
EMOTOROLA LTD. 2001
Chapter 3
Terrestrial Interfaces
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
ii
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Chapter 3 Terrestrial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity at the GGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Tunnelling Protocol (GTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Datagram Protocol (UDP) Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmission Control Protocol (TCP) Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet Protocol (IP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity at the SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subnetwork Dependent Convergence Protocol (SNDCP) . . . . . . . . . . . . . . . . . . . . . . . . SNDCP Service Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Link Control (LLC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Station System GPRS Protocol (BSSGP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSGP Virtual Connection Identifier (BVCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frame Relay Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
31 32 32 34 34 34 38 310 312 314 316 318 320
EMOTOROLA LTD. 2001
iii
ISSUE 1 REVISION 3
iv
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Objectives
Objectives
On completion of this chapter the student should be able to: S S State the GPRS Protocols. Explain the functions of the GPRS Protocols.
EMOTOROLA LTD. 2001
31
Activity at the GGSN
ISSUE 1 REVISION 3

GPRS Tunnelling Protocol (GTP)
The GPRS Tunnelling Protocol (GTP) is used between the GPRS Support Nodes (GSN)within the GPRS backbone network. This protocol provides a tunnel or path, for the signalling and data transfer procedures necessary for the transfer of multiprotocol packets. Two planes are specified for the GTP: The Signalling Plane GTP specifies a tunnel control and management protocol that allows the SGSN to provide GPRS network access for a MS. Signalling is used to create, modify and delete tunnels. The Transmission Plane GTP uses the tunnelling mechanism to provide a service for carrying user data packets. The choice of path is dependent on whether the user data to be tunnelled required a reliable link or not. The GTP is only implemented by the GGSN and the SGSN and as such no other entity need be aware of GTP. In fact, the GPRS MS connected to the SGSN will be unaware of the presence of GTP.
32
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
GPRS Application Protocols
Application IP/X.25 Relay SNDCP LLC Relay RLC MAC GSM RF MS Um RLC MAC GSM RF BSS BSSGP Network Service L1 Bis Gb SNDCP LLC BSSGP Network Service L1 Bis SGSN GTP TCP/UDP IP L2 L1 Gn GTP TCP/UDP IP IP/X25
L2 L1 GGSN
CPO7_4_1
Gi
EMOTOROLA LTD. 2001
33
ISSUE 1 REVISION 3
At the GGSN, the next stage is the encapsulation of the TPDU with either UDP or TCP. Currently, UDP is the only path protocol defined to transfer GTP signalling messages and is the recommended choice for the establishment of a connectionless path for connectionless TPDUs. For reliable connection orientated paths, TCP is used for TPDUs. It should be noted that both UDP and TCP use the services of IP.
User Datagram Protocol (UDP) Header

The UDP Header was discussed earlier and comprises of a Source Port, Destination Port, Length Indicator and Checksum. With regards to signalling request messages, the UDP Destination Port is set to 3386 which is reserved currently for GTP. The Source Port will be locally allocated by the sending SGN. For signalling response messages, the Destination Port will be the same as the Source port for the corresponding request message and the Source Port will be set once again to 3386. In the case of encapsulated TPDUs in connectionless mode, the UDP Destination Port will be set to 3386 and the Source Port will once again be locally allocated. The signalling message or TPDU along with the UDP Header is then passed down to the IP layer where an IP header is added.
Transmission Control Protocol (TCP) Header

Once again, the TCP Header has already been discussed earlier. In the case of TPDUs (Transport layer Packet Data Units) being tunnelled across the Gn interface, the Destination Port will be set to 3386 and the Source port will be set locally by the sending GSN. This, too, will be passed down to the IP Layer where once again, an IP Header will be added.
Internet Protocol (IP)

In the GPRS Phase 1, IPv4 will be the networking technology upon which GTP tunnelling shall be based. The IP address used for routing purposes will be independent of the Public Internet and as such be considered as a GPRS Intranet linking all the GSNs in the network. Therefore, when encapsulated data is passed down to the IP Layer from either UDP or TCP, the source and destination IP addresses will correspond to the IP address of the subsequent GSNs to which the data/signalling message should be tunnelled. This information is carried in the IP header and routing is determined in accordance with standard IPv4 practices.
34
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Internet Protocol (IP) Encapsulation
IP/X25
GTP
PDU
GTP
UDP/ TCP UDP/ TCP
PDU
TCP/UDP IP
GTP
PDU
IP
GTP
PDU
L2
L1
Gn
GGSN
CPO7_4_2
EMOTOROLA LTD. 2001
35
ISSUE 1 REVISION 3
In summary, a packet from an external data network will be encapsulated at the GGSN with the GTP Header, UDP or TCP Header and IP Header. If the resulting IP datagram is larger than the Maximum Transfer Unit (MTU) on the first link, fragmentation of the IP datagram will occur. This will be performed by the GGSN. It is desirable that the IP datagram be no larger than the path MTU value to ensure a quicker and more reliable connection. If fragmentation does occur, it is the IP Layer of the SGSN that will reassemble the fragments of the initial datagram before passing up the data to either TCP or UDP.
36
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Internet Protocol (IP) Encapsulation
IP/X25
GTP
PDU
GTP
UDP/ TCP UDP/ TCP
PDU
TCP/UDP IP
GTP
PDU
IP
GTP
PDU
L2
L1
Gn
GGSN
CPO7_4_3
EMOTOROLA LTD. 2001
37
Activity at the SGSN
ISSUE 1 REVISION 3

Data and signalling messages arrive at the SGSN via the Gn interface. The IP datagrams are collected by the IP Layer and are reassembled if fragmentation has occurred either at the GGSN or at any subsequent IP router along the Gn interface. Any additional processes are carried out at this layer before the payload is passed up to either UDP or TCP. The use of IP is indicated in the Type Field in the IP Header and is dependent upon whether a connectionless or connection orientated path is required. At the UDP/TCP layer, more processes are carried out such as determining the checksum value before this payload is passed up to GTP. Once again, the exact destination to which the payload is sent in GTP is determined by the Destination Port address. At the GTP Layer, the GTP Header is stripped off resulting in the PDU being ready for onward transmission across the Gb interface towards the BSS. As such, the PDU can be said to have been tunnelled across the Gn interface. To traverse across the Gb interface, the PDU requires further modification. This is carried out by the Subnetwork Dependent Convergence Protocol (SNDCP), the Logical Link Control (LLC) Protocol and the Base Station System GPRS Protocol (BSSGP) before being carried towards the BSS via a Frame Relay network. Therefore, to explain the actions of the SGSN, we shall once again discuss the role of the above protocols with regards to a PDU traversing the GPRS network.
38
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
L2 L1 GGSN
CPO7_4_4
Gi
EMOTOROLA LTD. 2001
39
Subnetwork Dependent Convergence Protocol (SNDCP)
ISSUE 1 REVISION 3

Network layer protocols are intended to be capable of operating over services derived from a wide variety of subnetworks and data links. GPRS supports several network layer protocols providing protocol transparency for the users of the service. Introduction of new Network Layer protocols will, therefore, be possible without changing any of the lower GPRS protocols. Therefore, all functions related to the transfer of Network Layer Protocol Data Units (NPDUs) are carried out in a transparent way by the GPRS network entities SNDCP. The set of protocol entities sitting above SNDCP consists of commonly used network protocols. These all use the same SNDCP entity, which then performs multiplexing of data coming from different sources before being sent via the services, provided by the LLC Layer. The Network Service Access Point Identifier (NSAPI) acts as an index for the appropriate Packet Data Protocol (PDP) which is using the services of SNDCP. Each active NSAPI uses the services provided by the SAPI in the LLC Layer and as such several NSAPIs may be associated with the same SAPI.
310
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Packet Data Protocol
Packet Data Protocol
Packet Data Protocol NPDU
NSAPI SNDCP
SNPDU SAPI LLC
CPO7_4_5
EMOTOROLA LTD. 2001
311
SNDCP Service Functions
ISSUE 1 REVISION 3

The following functions are performed by SNDCP: S Transmission and reception of NPDUs in acknowledged and unacknowledged LLC mode. In acknowledged mode, the receipt of data shall be confirmed at the LLC layer, and the data shall be transmitted and received in order per NSAPI. In unacknowledged mode, the receipt of data shall not be confirmed at the SNDCP layer nor at the LLC layer. Transmission and reception between the MS and SGSN of variablelength NPDUs. Transmission and reception of NPDUs between the SGSN and MS according to the negotiated QoS profile. Segmentation and reassemble. The outputs of the compression functions are segmented to the maximum length of LLPDU. This is independent of the particular Network Layer protocol being used. Transfer of the minimum amount of data possible between the SGSN and MS through compression techniques. Compression of redundant protocol control information (e.g. TCP/IP header) at the transmitting entity and decompression at the receiving entity. Compression may be performed independently for each QoS delay class and precedence class. If several network layers use the same QoS delay class and precedence class, then one common compressor may be used for these network layers.
S S S
S S
312
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Network layer
Header
Data
NPDU
SNDCP
Control Compression
Data Compression
Segmentation
SNDCP
SNDCP Header
Segmented NPDU
SNDATA PDU/ SNUNIDATA PDU
LLC
CP07_4_6
LLC Header
SNDATA PDU/SNUNIDATA PDU
FCS
LLC Frame
EMOTOROLA LTD. 2001
313
Logical Link Control (LLC)
ISSUE 1 REVISION 3

The LLC Layer provides a highly reliable logical connection between the SGSN and the MS and as such spans both the Gb and Um interfaces. In addition, the LLC has been designed to be independent of the underlying radio interface protocols in order to allow for the introduction of alternative GPRS radio solutions at a later date. The Logical Link Control layer supports: S Service primitives allowing the transfer of SNDCP Protocol Data Units (SNPDUs) between the Subnetwork Dependent Convergence layer and the Logical Link Control layer. Procedures for transferring LLPDUs between the MS and SGSN. Procedures for unacknowledged pointtopoint delivery of LLPDUs between the MS and the SGSN. Procedures for acknowledged, reliable pointtopoint delivery of LLPDUs between the MS and SGSN. Procedures for pointtomultipoint delivery of LLPDUs from the SGSN to the MS. Procedures for detecting and recovering from lost or corrupted LLPDUs. Procedures for flow control of LLPDUs between the MS and the SGSN. Procedures for ciphering of LLPDUs. The procedures are applicable to both unacknowledged and acknowledged LLPDU delivery.
S S S S S S S
The layer functions are organised in such a way that ciphering resides immediately above the RLC/MAC layer in the MS and immediately above the BSSGP layer in the SGSN.
314
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Logical Link Control (LLC) Frame
Address Field 1
Control Field 136
Information Field n #
FCS 3 Octets
# Maximum = 1520 octets

CP07_4_7
EMOTOROLA LTD. 2001
315
Base Station System GPRS Protocol (BSSGP)
ISSUE 1 REVISION 3

The protocol architecture, which lies between the BSS and the SGSN, is based upon Frame Relay, which utilises virtual circuits allowing data to be multiplexed from several MSs. Sitting on top of the Frame Relay protocols is another GPRS specific protocol called the Base Station System GPRS Protocol (BSSGP). The primary functions of the BSSGP include the provision of radiorelated information, which is to be used by the Radio Link Control (RLC), and Medium Access Control (MAC) functions. In addition, the BSSGP must also provide the functionality to enable two physically distinct nodes, an SGSN and a BSS, to operate node management control functions. The figure opposite illustrates the users of BSSGP. Here we can see that it is not only the Logical Link Control (LLC) that utilises BSSGP but also GPRS Mobility Management (GMM) and Network Management (NM) at the SGSN. The functions of GMM deal with paging and radio status requests, whilst the NM functions deal with such aspects as flow control and resets. At the BSS, a Relay (RL) provides the functions for controlling the transfer of LLC frames between the RLC/MAC Layer and the BSSGP Layer.
316
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Base Station System GPRS Protocol (BSSGP) Interfaces
Service Model in a BSS

Relay GMM NM
Service Model in a SGSN

LLC GMM NM
RLC/MAC
BSSGP
BSSGP
Network Service
Network Service
CPO7_4_8
EMOTOROLA LTD. 2001
317
BSSGP Virtual Connection Identifier (BVCI)
ISSUE 1 REVISION 3

BSSGP Virtual Connections (BVC) provide communication paths between the BSSGP entities at the SGSN and the BSS. Each BVC is used in the transport of the BSSGP PDUs between peer PointToPoint (PTP) functional entities and peer signalling functional entities. A PTP functional entity is responsible for PTP user data transmission and as such there is one PTP functional entity per cell. Each BVC is identified by means of a BSSGP Virtual Connection Identifier (BVCI) which has endtoend significance across the Gb interface and as such, each BVCI is unique between two Network Service (NS) entities. At the SGSN, the BVCIs associated with PTP functional entities are dynamically configured where as for signalling functions, the BVCIs are configured statically and set to 0000 hex.
318
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Gb addressing
BSS #1
BVCI=2 NSVCI=a NSVCI=b BVCI=3 DLCI=137 NSVCI=a DLCI=16 PTP Cell 1 DLCI=98 NSVCI=b DLCI=17
SGSN BVCI=2
E1
Bearer Channel = 5
Bearer Channel = 1
E1
NSVCI=e DLCI=16
BVCI=3
PTP Cell 2 NSEI=1
NSVCI=c DLCI=51 NSVCI=d DLCI=43
Bearer Channel = 2 E1 Frame relay network
NSEI=1 BVCI=0
Signalling
BVCI=0
BSS #2
BVCI=2 NSVCI=e DLCI=16 PTP Cell 1 NSEI=2 NSVCI=f DLCI=259 Signalling BVCI=0
Bearer Channel = 3 Bearer Channel = 6 E1

NSVCI=c DLCI=21 NSVCI=d DLCI=302 NSVCI=f DLCI=511 BVCI=0 BVCI=2
Bearer Channel = 4 E1
E1
NSEI=2
CP07_4_9
EMOTOROLA LTD. 2001
319
Frame Relay Operation
ISSUE 1 REVISION 3

Frame Relay provides virtual connections between devices attached to the network, with each of the virtual circuits being uniquely identified at each frame relay interface by a Data Link Connection Identity 2 octet (DLCI). In practice, the frame is relayed on a DLCI to the first Frame Relay Switch and there, a number of processes are carried out: S S S Frame Check Sequence (FCS) analysed Frame Length checked DLCI checked
If any of the above processes are not carried out successfully, the link is refused otherwise, the DLCI is accepted. The Frame Relay Switch then looks at the routing table to determine the correct route upon which to relay the frame. The DLCI is then changed to reflect the new DLCI value for the new link. As a result, the FCS, which works across the address as well as the information field, is recalculated. In the case of GPRS, Permanent Virtual Circuit (PVCs) are used to map the various inputs at a SGSN to the outputs at the BSS and visa versa. Circuits between users should be treated as Network Service Virtual Circuits (NSVC) which have a specific Network Service Virtual Circuits Identify (NSVCI).
320
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Gb addressing
BSS #1
BVCI=2 NSVCI=a NSVCI=b BVCI=3 DLCI=137 NSVCI=a DLCI=16 PTP Cell 1
SGSN BVCI=2
Bearer Channel = 5
DLCI=98 NSVCI=b DLCI=17
E1
NSVCI=e DLCI=16
BVCI=3
PTP Cell 2 NSEI=1
NSVCI=c DLCI=51 NSVCI=d DLCI=43
Bearer Channel = 2 E1 Frame relay network
NSEI=1 BVCI=0
Signalling
BVCI=0
BSS #2
BVCI=2 NSVCI=e DLCI=16 PTP Cell 1 NSEI=2 NSVCI=f DLCI=259 Signalling BVCI=0
Bearer Channel = 3 Bearer Channel = 6 E1

NSVCI=c DLCI=21 NSVCI=d DLCI=302 NSVCI=f DLCI=511 BVCI=0 BVCI=2
E1
NSEI=2
CP07_4_9
EMOTOROLA LTD. 2001
321
ISSUE 1 REVISION 3
322
EMOTOROLA LTD. 2001
Chapter 4
Air Interface
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
ii
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Chapter 4 Air Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Broadcast Control Channel (PBCCH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Common Control Channel (PCCCH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Dedicated Control Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocation of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release of PDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiframe Structure for PDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink Resource Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uplink Resource Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fixed Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Mobility Managment State Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Idle to Ready . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ready to Standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standby to Ready . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standby to Idle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ready to Idle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timing Advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity at the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Link Control (RLC) Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Medium Access Control (MAC) Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Physical Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Coding Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coding Scheme CS-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coding Scheme 2 (CS-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coding Scheme 3 (CS-3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coding Scheme 4 (CS-4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity at the GPRS MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Precedence Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delay Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reliability Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
41 42 42 42 44 44 46 46 48 410 412 412 414 416 416 416 416 418 418 420 422 424 424 426 428 430 430 430 432 432 434 436 436 438 440
EMOTOROLA LTD. 2001
iii
ISSUE 1 REVISION 3
iv
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Objectives
Objectives
On completion of this chapter the student should be able to: S S S S State the GPRS Logical Channels. State the types and explain the Resource Allocation methods. Explain how Timing Advance is achieved in the GPRS system. State the Coding Schemes and Quality of Service criteria.
EMOTOROLA LTD. 2001
41
Logical Channels
ISSUE 1 REVISION 3
Logical Channels
A new set of logical channels has been defined for use with GPRS.
Packet Broadcast Control Channel (PBCCH)

The PBCCH broadcasts packet data system information and follows the same predefined rules for mapping onto physical channels as the BCCH. The existence of the PBCCH is indicated on the BCCH and should it not be allocated then the packet system information will be in the BCCH.
Packet Common Control Channel (PCCCH)

The Packet Common Control Channel (PCCCH)
The PCCCH is very similar in make up to the CCCH and when not allocated in a cell, packet transfer can be initiated by the CCCH.
Packet Random Access Control Channel (PRACH)

The PRACH is uplink only, and is used by an MS to initiate uplink transfer for sending data or signalling information. The access burst used on the PRACH is also used to obtain timing advance information.
Packet Paging Channel (PPCH) Downlink only

The PPCH is used to page an MS prior to a MS terminated data transfer. The PPCH uses paging groups to allow for Discontinuous Reception (DRX) and follows exactly the same predefined rules as is done by the PCH. MSs in both circuit switching and packet switching modes can be paged although this is only applicable for GPRS MSs class A and B. Further to this an MS engaged in a packet switched transfer can be paged on a Packet Associated Control Channel (PACCH).
Packet Access Grant Channel (PAGCH)

The PAGCH is downlink only and is used during the establishment of packet transfer to send resource assignment messages. Should the MS be currently involved in a packet transfer then the resource assignment messages can be sent on the PACCH.
Packet Notification Channel (PNCH)

The PNCH is downlink only to send a Point to Multipoint-Multicast (PTM-M) notification to a group of MSs prior to the PTM-M packet transfer taking place. This notification is in the form of a resource assignment message. Insert SYS02_1_13b with the addition of the GPRS channels below.
42
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Logical Channels
GSM Control Channels

LOGICAL CHANNELS
COMMON CHANNELS
DEDICATED CHANNELS
BROADCAST CHANNELS
COMMON CONTROL CHANNELS
DEDICATED CONTROL CHANNELS
TRAFFIC CHANNELS
FCCH
SCH
BCCH
PCH
RACH AGCH
SDCCH SACCH FACCH
TCH/F
TCH/H
CPO7_3_01
GPRS Specific Logical Channels

LOGICAL CHANNELS
COMMON CHANNELS
DEDICATED CHANNELS
BROADCAST CHANNELS
TRAFFIC CHANNELS
PBCCH Broadcast
PNCH PPCH PRACH PAGCH Paging Random Access Notification Access Grant
PACCH Resource Assignment
PTCCH Timing Advance
PDTCH Data Traffic Channel

CPO7_3_02
EMOTOROLA LTD. 2001
43
Logical Channels
ISSUE 1 REVISION 3
Packet Dedicated Control Channels

Packet Associated Control Channel (PACCH)
PACCH conveys signalling information related to an MS, e.g. acknowledgements and Power control information. It also carries resource assignment and reassignment messages, comprising the assignment of a capacity for a PDTCH(s) and for further occurrences of PACCH. The PACCH shares resources with the PDTCHs that are currently assigned to one MS. An MS that is currently involved in packet transfer can be paged for circuit switched services on PACCH.
Packet Timing advance Control Channel (PTCCH) (uplink and downlink) (U/D)
S S Uplink Random access bursts are used to allow estimation of timing advance. Downlink Transmits timing advance information to several MSs.
One PTCCH/D is paired with several PTCCH/Us.
Packet Traffic Channels

Packet Data Traffic Channel (PDTCH).
Used for data transfer and is mapped directly onto one physical channel. Temporarily dedicated to one MS or a group of MSs. One MS may use multiple PDTCHs in parallel for individual packet transfer. Up to eight PDTCHs, each with different timeslots, can be allocated to one MS at the same time or to a group of MSs in the case of Point-to-Multipoint-Multicast messages (PTM-M).
44
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Logical Channels
Logical Channel Directions
Packet Broadcast Control Channel (PBCCH)
PBCCH
Packet Common Control Channels (PCCCH)
PRACH
PPCH
PAGCH
PNCH
Packet Dedicated Control Channels
Packet Traffic Channel
PTCCH
PACCH
PDTCH
CPO7_3_03
EMOTOROLA LTD. 2001
45
Allocation of Resources
ISSUE 1 REVISION 3
A cell supporting GPRS may allocate resources on one or several physical channels in order to support the GPRS traffic. Those physical channels shared by the GPRS MSs are taken from a common pool of physical channels available in the cell. This allocation of physical channels to circuit switched services and GPRS is carried out dynamically according to the capacity on demand principles. The capacity on demand principles refer to the fact that PDCHs need not be permanently allocated in order to support GPRS and the way in which the network allocates available resources as required. Common control signalling that is required by GPRS in the initial phase of packet transfer is conveyed on the PCCCH, when allocated, or on the CCCH. This saves on GPRS specific capacity for the operator. Should the last available PCCCH be allocated then the MS would perform cell re-selection. At least one PDCH, acting as the master, carries the PCCCH as well as PDTCH and PACCH. Other PDCHs, acting as slaves, are used for user data transfer and for dedicated signalling.
Release of PDCH
The fast release of PDCH is an important feature to enable the dynamic sharing of the physical radio resources between packet and circuit switched servics. To enable this three PDCH release options are available: S S S Wait for all assignments to terminate on that PDCH. Individuaklly notify all the users that have assignments on that PDCH. Broadcast the notification about de-allocation.
46
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
GPRS Timeslot Configurations
Example A 0 1 2 3 4 5 6 7
BCCH TCH TCH SW SW RES RES RES BCCH CARRIER TCH TCH TCH TCH TCH TCH TCH TCH CARRIER 2
Example B
BCCH TCH TCH TCH TCH TCH TCH TCH BCCH CARRIER SW SW SW RES RES RES RES RES CARRIER 2
Example C
BCCH TCH TCH TCH TCH TCH TCH TCH BCCH CARRIER SW SW SW SW SW SW SW SW CARRIER 2
CPO7_3_08
EMOTOROLA LTD. 2001
47
Multiframe Structure for PDCH
ISSUE 1 REVISION 3

The multiframe structure for PDCH consists of 52 TDMA frames, divided into 12 blocks of 4 frames (radio blocks) and 4 idle frames. This multiframe can be looked at as two 26 frame multiframes on the GSM network, numbered from 0 to 51. It has a duration of 240ms and 25.5 multiframes are counted as a superframe.
48
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
TDMA Frame
TDMA frame
3 4
5 6
NB NBNB NB
Radio Block
B0
B1
B2 T
B3
B4
B5
B6
B7
B8 T
B9
B10 B11 I
240ms
CP07_3_5
EMOTOROLA LTD. 2001
49
Downlink Resource Allocation
ISSUE 1 REVISION 3

Downlink resources are allocated to the MS via the Packet Downlink Assignment message. This message will detail all the timeslots that the MS may receive data on for this particular transaction. Each complete data transfer is allocated a Temporary Block Flow (TBF), known by its identifier, the Temporary Flow Identifier (TFI). The TFI is part of each Uplink/Downlink RLC Data Block and is composed of 7 bits in the Uplink and 5 bits in the Downlink. The TFI for a particular MS is also specified in the Packet Downlink Assignment message. The MS then has to receive and decode all the RLC/MAC blocks on its allocated timeslots to ascertain if the TFI contained in the block is the TFI allocated to the MS. When the MS identifies a block containing its allocated TFI the MS will decode and process the data block.
410
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Downlink RLC data block with MAC header

Bit 8 7 Payload Type PR 6 5 RRBP 4 S/P 3 TFI M 2 USF 1 FBI E E MAC header Octet 1 Octet 2 Octet 3 (optional) . . . Octet M (optional) Octet M+1 . . . Octet N-1 Octet N (if present)
CP07_3_Downlink
BSN Length indicator . . . Length indicator RLC data spare
spare
Uplink RLC data block with MAC header

Bit 8 7 6 5 4 3 Payload Type Countdown Value TFI BSN Length indicator . . . Length indicator TLLI 2 SI 1 R TI E E MAC header Octet 1 Octet 2 Octet 3 (optional) . . . Octet M (optional) Octet M+1 \ Octet M+2 } (optional) Octet M+3 / Octet M+4 / Octet M+5 . . . Octet N-1 Octet N CP07_3_Uplink (if present)
411
RLC data spare

EMOTOROLA LTD. 2001
spare
CP07: Introduction to GPRS
Uplink Resource Allocation
ISSUE 1 REVISION 3

Allocation of resources on the Uplink is vital, as the data transmissions from 2 MS could collide. There are 2 methods of implementing Uplink Resource allocation at present. 1. Fixed Allocation of Uplink Resources. 2. Dynamic Allocation of Uplink Resources.
Fixed Allocation
Fixed allocation use the Packet Uplink Assignment message to communicate a detailed fixed uplink resource allocation to the MS. The fixed allocation consists of a start frame, timeslot assignment and blocks assignment. The MS waits until the start frame and then transmits on radio blocks on those assigned. This information is passed to the MS in the form of an ALLOCATION_BITMAP, which represents uplink radio blocks, each bit representing one radio block or an entire block period. Each bit indicated whether the mobile station is permitted to transmit during the corresponding uplink radio block or radio block period. An MS receiving a fixed allocation can transmit on the uplink without having to monitor the downlink to see if blocks are free (this is normally indicated by the USF). If the current allocation is not sufficient, the MS may request additional resources in one of the assigned uplink blocks. The number of blocks an MS requests in the initial and subsequent allocation requests can only account for the number of data and control blocks it intends to send. The MS cannot request additional blocks for the retransmission of erroneous blocks.
412
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
PDTCH Fixed Allocation
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
B0
B1
B2
B3
B4
B5
B6
B7
B8
B9
B10
B11
B0
B1
B2
B3
B4
B5
B6
B7
B8
B9
B10
B11
= MS assigned blocks + timeslots

CP07_3_6
EMOTOROLA LTD. 2001
413
ISSUE 1 REVISION 3
Dynamic Allocation
The dynamic allocation of Uplink resources is based upon the use of the Uplink State Flag (USF). The USF forms part of each downlink Data or Control Block that is sent. The USF is transmitted in the downlink to indicate an invitation to transmit to mobiles. A mobile is allocated a number of uplink time-slots (shared with other mobiles) and each is told when they may be allowed to transmit. Although up to the maximum 8 time-slots may be allocated, this would require the phone to have a duplexer. The USF has a fixed length of 3 bits, so that up to 7 MS can be distinguished on a particular timeslot. A MS having multiple timeslots allocated may have different USFs allocated for each timeslot. A USF value of 111 is used to denote that the next uplink block is reserved for PRACHs. Once the MS detects its USF in the downlink RLC Data Blick it will transmit on the next uplink block or the next 4 uplink blocks dependent upon the value of the USF_GRANULARITY. The USF_GRANULARITY is also included in the Packet Uplink Assignment. The USF_GRANULARITY has two values, 0 and 1. If the USF_GRANULARITY is set to 0 the MS will transmit on the next uplink block following the appearance of its USF value. If the USF_GRANULARITY is set to 1 the MS will transmit on the next four uplink blocks following the appearance of its USF. In the diagram opposite two MSs have been allocated uplink resources dynamically. MS 1 will look for a USF value of 5 on timeslot 6 and a USF value of 3 on timeslot 7. MS 2 will look for a USF value of 4 on timeslot 6 and a USF value of 2 on timeslot 7. Following the appearance of these respective values each MS will transmit on the next available uplink block.
414
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
PDTCHs Dynamic Allocation
LLC FH RLC/MAC BH Information BCS BH Information BCS BH Information BCS Information Field FCS
NB
NB
NB
NB
DL TS6
UL DL TS7
UL
CPO7_3_07
EMOTOROLA LTD. 2001
415
GPRS Mobility Managment State Diagram
ISSUE 1 REVISION 3

Looking at the state diagram, it can be seen that the model is similar at both the Mobile Station (MS) and the Serving GPRS Support Node (SGSN).
Idle to Ready
When moving from an Idle State to a Ready State a mobile must first perform a GPRS Attach. If successful this will make the mobile known to the network, i.e. SGSN. If unsuccessful the mobile will fall back to the Idle State. Following the attach sequence a MM context is said to be active at the MS and the SGSN. Once in the Ready State, a PDP context may be activated which allows the MS to establish a packet data session with the associated packet data networks (PDNs). In particular this will associate a PDN address within the MS and the GGSN. With a valid PDP context it is possible to transfer Protocol Data Units (PDUs). Once the transmission of PDUs has finished then a Ready Timer is started (which starts with a default value, but may be changed by the SGSN). Both the MS and SGSN should be using the same value. Whilst in this state the MS will perform both Cell and Routing Area updates.
Ready to Standby
A move from a Ready State to Standby State will follow the expiry of the Ready Timer or a Force to Standby from an MS or SGSN. Alternatively if a problem is encountered on the RLC/MAC interface, then the MS could enter the Standby State. Whilst in this state only Routing Area Updates will be performed.
Standby to Ready
Once there are PDUs to transmit/receive the MS and SGSN will enter the Ready State. To enable this a PDP context must have been activated.
416
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
GMM State Models for MS and SGSN
Idle
Idle
GPRS Attach
GPRS Detach
GPRS Attach
GPRS Detach or Cancel Location
Ready
Standby timer expiry Ready timer expiry or force to standby PDU transmission Standby timer expiry or Cancel Location
Ready
Ready timer expiry or force to standby or PDU abnormal RLC reception condition
Standby
CPOy_3_09
Standby
EMOTOROLA LTD. 2001
417
ISSUE 1 REVISION 3
Standby to Idle
Once in the Standby State a second timer is started and when this expires or a MAP message, Cancel Location is received from the HLR, then the return to the Idle State is performed and the MM context are removed from the MS, SGSN, and GGSN.
Ready to Idle
Either a GPRS detach or a Cancel location would change the state from Ready to Idle and in doing so, both MM and PDP contexts would be removed as the MS is no longer connected to the GPRS network.
418
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
GMM State Models for MS and SGSN
Idle
Idle
GPRS Attach
GPRS Detach
GPRS Attach
GPRS Detach or Cancel Location
Ready
Standby timer expiry Ready timer expiry or force to standby PDU transmission Standby timer expiry or Cancel Location
Ready
Ready timer expiry or force to standby or PDU abnormal RLC reception condition
Standby
CPOy_3_09
Standby
EMOTOROLA LTD. 2001
419
Mobile Identity
ISSUE 1 REVISION 3
Mobile Identity
The mobile equipment is still identified at the highest level by its own unique IMSI, as this is used to identify individual records in the location registers. However, ETSI have defined a new identifier, the P-TMSI (Packet-TMSI) which is known to the SGSN (which is the supporting node for the mobile equipment in the GPRS network). The P-TMSI is in turn used by the mobile equipment to derive another value, the Temporary Logical Link Identifier (TLLI) as seen opposite. The TLLI can be derived from one of three sources: 1. 2. A Local TLLI derived using the P-TMSI from the SGSN, as it is already attached to the system. A Foreign TLLI as seen by the currently attached SGSN, as this TLLI was generated as a result of a connection to another SGSN and the mobile as moved into a cell supported by the current (or new) SGSN. A random TLLI could be chosen by the mobile in the absence of a valid PTMSI in order to determine a TLLI value.
3.
420
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Mobile Identity
Mobile Identity
Identity IMSI P-TMSI TLLI TLLI
GPRS Network
MS
P-TMSI
TLLI
CPO7_3_11
EMOTOROLA LTD. 2001
421
Timing Advance
ISSUE 1 REVISION 3
Timing Advance
The MSs initial Timing Advance (TA) is calculated on the Access Burst as for GSM. The estimated timing advance value is passed to the MS via the Packet Immediate Assignment. The MS uses this value until continuous timing advance provides a new value. In continuous timing advance the mobile sends in a special access burst in an idle slot for the network to derive the timing advance. In the downlink the network sends a timing advance via the Packet Associated Control Channel (PACCH), which is transmitted during the idle timeslots of the 52 frame multiframe. Timing Advance Index (TAI) gives the MS the position to send the access burst. For example TAI = 1 refers to idle timeslot 2. The network will then update the MS timing advance in the next Timing Advance Message and also the next 3 TA messages. The MS only has to read the message once.
422
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Timing Advance
Timing Advance
52-multiframe number n: Uplink TA=0 B0 B1 B2 0 B3 B4 B5 1 TA message 1 Downlink 52-multiframe number n+1 Uplink TA=2 B0 B1 B2 4 B3 B4 B5 5 Downlink TA message 1 52-multiframe number n+2 Uplink TA=4 B0 B1 B2 8 B3 B4 B5 9 Downlink TA message 2 52-multiframe number n+3 Uplink TA=6 B0 B1 B2 12 B3 B4 B5 13 Downlink TA message 2 52-multiframe number n+4 Uplink TA=2 TA=8 B0 B1 B2 16 B3 B4 B5 17 Downlink TA message 3 52-multiframe number n+5 Uplink TA=10 B0 B1 B2 20 B3 B4 B5 21 Downlink TA message 3 52-multiframe number n+6 Uplink TA=12 B0 B1 B2 24 B3 B4 B5 25 Downlink TA message 3 52-multiframe number n+7 Uplink TA=14 B0 B1 B2 28 B3 B4 B5 29 Downlink TA message 4 B0 B11 = Radio blocks idle bursts are numbered from 0 to 31
B6
B7
B8
TA = 1 2 B9 TA message 1
B10
B11
B6
B7
B8
TA = 3 6 B9 B10 TA message 1 TA = 5 10 B9 B10 TA message 2 TA = 7 14 B9 B10 TA message 2 TA = 9 18 B9 B10 TA message 3 TA = 11 22 B9 B10 TA message 3 TA = 13 26 B9 B10 TA message 4 TA = 15 30 B9 B10 TA message 4
B11
B6
B7
B8
B11
11
B6
B7
B8
B11
15
B6
B7
B8
B11
19
B6
B7
B8
B11
23
B6
B7
B8
B11
27
B6
B7
B8
B11
31
CPO7_3_12
EMOTOROLA LTD. 2001
423
Activity at the BSS
ISSUE 1 REVISION 3
Activity at the BSS

Data and signalling messages arrive at the BSS via the Gb interface and by using the Network Service / Frame Relay. The frames arriving at the Packet Control Unit (PCU) pass through BSSGP where the information and signalling messages are separated into LLC frames, GPRS Mobility Management (GMM) information and Network Management (NM) information. With regards to data and signalling messages destined for the GPRS MS, the LLC frames pass through a Relay entity (LLC Relay) before entering the Radio Link Control (RLC) and Medium Access Layer (MAC), respectively. The RLC/MAC layer provides services for information transfer over the physical layer of the GPRS interface. These functions include backward error correction procedures enabled by selective retransmission of erroneous blocks of data. The MAC function arbitrates access to the shared medium between a multitude of MSs and the GPRS network.
Radio Link Control (RLC) Layer

The RLC function is responsible for the transfer of PDUs from the LLC layer and the MAC function, segmentation/re-assembly of LLC PDUs into/from RLC data blocks and backward error correction. The RLC data block consists of an RLC Header, and RLC Data Field and spare bits. Each RLC data block may be encoded using any of the available channel coding schemes CS-1, CS-2, CS-3 and CS-4 and as such, will effect the degree of segmentation and subsequent re-assembly. If the contents of an LLC PDU do not fill an entire RLC data block, the beginning of the next LLC PDU will be used to fill the remaining bit positions. However, if the LLC PDU was the last in the current transmission block, the RLC data block will be completed by the insertion of spare bits. The structure of the RLC Data Blocks are dependent upon the transmission direction; i.e. Uplink or Downlink.
424
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Activity at the BSS
L2 L1 GGSN Gi
CPO7_3_13
EMOTOROLA LTD. 2001
425
Medium Access Control (MAC) Layer
ISSUE 1 REVISION 3

The main function of the MAC layer is the control of multiple MSs sharing a common resource on the GPRS air interface. The RLC data block is passed down to the MAC layer where a MAC header is added. The format of the MAC header is dependent upon the direction of data transfer. The fields in the MAC header are:USF S/P RRBP Uplink State Flag is used to indicate which MS is allocated the GPRS resource.
Supplementary/Polling bit is used to indicate whether the RRBP field is active. Relative Reserved Block Period is used to specify that a single uplink block is being used as a Packet Associated Control Channel (PACCH). defines the type information in the payload area, that is either data or signalling. Stall Indicator is used to signal whether the transmission has stalled. is sent by the mobile (uplink) to the network so that it can calculate the number of radio blocks remaining in the current uplink allocation of resources. Retry bit which indicates whether the MS transmitted the Channel.
Payload Type SI Countdown Value
426
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
2 SI R
1 Uplink
Payload Countdown Value Type
RLC/MAC Block MAC Header RLC Header RLC Data Unit RLC Data Block Spare
Payload RRBP S/P Type 8 7 6 5 4 3
USF 2 1
Downlink
RLC/MAC Block MAC Header Control Header RLC/MAC Signalling Information RLC/MAC Control Block
CPO7_3_14
EMOTOROLA LTD. 2001
427
The Physical Layer
ISSUE 1 REVISION 3
The Physical Layer

The Physical Layer can be subdivided into two layers, the Physical RF Layer and the Physical Link Layer. The Physical RF Layer performs modulation of the physical waveforms and demodulation of the received wave form into a sequence of bits which are transferred to the Physical Link Layer. The Physical Link Layer provides the services for information transfer over a physical channel between the MS and the GPRS network. Functions at this layer include: S Forward Error Correction (FEC) coding which allows for the detection and correction of transmitted code words and the indication of code words which cannot be corrected. Rectangular interleaving of one radio block over four bursts in consecutive TDMA frames. Procedures for detecting physical link congestion. Synchronisation procedures in addition to adjusting timing advance parameters. Monitoring and evaluation procedures for radio link signal quality. Cell selection and re-selection procedures. Transmitter power control procedures. Battery power conservation procedures such as Discontinuous Reception (DRx).
S S S S S S S
428
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
The Physical Layer
L2 L1 GGSN
CPO7_4_1
Gi
EMOTOROLA LTD. 2001
429
Channel Coding Schemes
ISSUE 1 REVISION 3

Four different channel coding schemes have been defined for GPRS.
Coding Scheme CS-1

For Coding Scheme 1 (CS-1), 40 bits are used for the Block Check Sequence (BCS) to increase protection. These and USF (3 bits), Header and Data (181 bits). In addition, 4 tail bits are passed through a 1/2 rate convolutional encoder resulting in a protocol 456 bit payload. Therefore, when using CS-1, the data rate is equal to: 181bits/20ms = 9.05kbps
Coding Scheme 2 (CS-2)

For Coding Scheme 2 (CS-2) only 16 bits are used for the BCS but in this case, a CRC code is used. Other differences between CS-2 and CS-1 include the use of a 6 bit USF to increase robustness during transmission over the air interface. Once again 4 tail bits are added to the sequence prior to passing through a 1/2 rate convoluted encoder. The result of this is a bit stream of 588 bits /20ms but this needs to be reduced to 456 bits to bring it in line with GSM burst structures. Therefore, 132 bits are punctured and this sequence is seen in the diagram overleaf. It should be noted that the USF bits (12 bits after encoding) are not punctured. Therefore, when using CS-2, the data rate is equal to: 268 bits/20ms = 13.4kbps
430
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Coding Scheme CS-1

3 USF 181 Header and data + 40 BCS 224 bits
4 tail bits rate 1/2 convolutional coding 6 456 bits
Coding Scheme CS-2

6 USF 268 Header and data 16 BCS 294 bits
Puncturing (132 bits) - see below 12 456 bits
Punctured bits
1 2
. . .
15 16
17 18
19 20 21 22 23
. . . 587
Last
588
(Except 12 specific bits)
First
EMOTOROLA LTD. 2001
431
ISSUE 1 REVISION 3

The process used in CS-3 is almost identical to that of CS-2 other than the degree of puncturing. In this case, the Header and Data is made up of 312 bits and after encoding (with USF, BCS and tail bits) the result is 676 bits. This is punctured once again to the 456 bits required by the GSM burst structure. The puncturing sequence used can be seen opposite. Therefore, when using CS-3, the data rate will be equal to: 312 bits/20ms = 15.6kbps

For Coding Scheme 4 (CS-4) there is no FEC applied to the data and as such, there is more capacity for user information. In this case, we see that the BCS is made up of 16bits, using a CRC code and the USF has been extended to 12 bits for robustness. Therefore, using this scheme it is possible to carry 428 bits of header and data. Thus, the data rate for CS-4 is equal to: 428 bits/20ms = 21.4kbps
432
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Coding Scheme CS-3

6 USF 312 Header and Data 16 BCS 338 bits
Puncturing (220 bits) 12 456 bits

Punctured bits
. . . 15
First
16 17
. . . 21
22 23
...
27 28 29
. . . 669 670 671 672673 674 675 676

Last
CP07_3_CS3
Coding Scheme CS-4

12 USF 428 Header and Data 16
BCS
456 bits
No Coding
12 456 bits
CP07_3_CS4
EMOTOROLA LTD. 2001
433
Activity at the GPRS MS
ISSUE 1 REVISION 3

At the GPRS MS, the PDUs pass through the protocol stack in the reverse order. The four consecutive air interface bursts are re-assembled and passed to the RLC/MAC Layer. Once all the RLC data blocks for a particular LLC PDU have been received, the LLC frame is re-assembled and passed up to the LLC Layer. Here, the FCS is calculated and any re-transmissions are activated if necessary, otherwise the payload area is passed up to the SNDCP layer.
434
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Application IP/X.25 PDU
SNDCP
SNDCP Segmented PDU
LLC
LLC SNDCP Segmented PDU FCS Segmented / re-assembly
RLC
R L C R MAC L C Burst 114 bits
RLC DATA
MAC
RLC DATA Burst Burst 114 bits Burst 114 bits
GSM RF
114 bits
CP07_3_18
EMOTOROLA LTD. 2001
435
Quality of Service
ISSUE 1 REVISION 3
Quality of Service
A Quality of Service (QoS) profile is associated with each PDP context and is considered to be a single parameter with multiple data transfer attributes. These are defined as: S S S S S Precedence Class Delay Class Reliability Class Peak Throughput Class Mean Throughput Class
There are many possible QoS profiles defined by these various attributes and as such, a PLMN may only support a limited number. During the QoS profile negotiation, it is possible for an MS request a value for each of the QoS attributes, including the HLR stored subscribed default values. Quality of service parameters are usually negotiated at subscription or during call set-up. The network will negotiate each attribute to a level that is in accordance with the available GPRS resources.
Precedence Class
The Service Precedence indicates the relative importance of maintaining the service commitments under abnormal conditions such as congestion or limited resources. The Precedence Class defines 3 different levels: High, Normal and Low.
436
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Quality of Service
QoS Profile
Precedence Class
High/Normal/Low
Delay
4 Delay Classes
Reliability Defined
5 Classes
Throughput
Peak & Mean
EMOTOROLA LTD. 2001
437
Delay Class
ISSUE 1 REVISION 3
Delay Class
Although GPRS is not defined as a store and forward system, it does have inherent delays within its equipment and the supporting protocols. The amount by which SDUs may be delayed in the network is specified as one of four classes as shown in the figure opposite. The delays specified do include the following:S S S radio channel access delay (uplink or downlink) radio channel transit delay (uplink/downlink) GPRSnetwork delay (multiple hops)
But is NOT inclusive of external network delays. Whilst the mean transfer delay is specified for the different classes, a 95-percentile delay is also specified, which is the maximum time delay that 95-percent of SDUs will be delivered across the interface (as opposed to specifying a time delay for 100% transmission). Delay is measured from: S S the Gi interface for the fixed network
and/or the R interface associated with a MS
438
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Delay Class
Delay Class
Delay Class 1. (Predicitive) 2. (Predicitive) 3. (Predicitive) 4. (Best Effort)
Delay (maximum values) SDU size: 128 octets SDU size: 1024 octets Mean Transfer 95 percentile Mean Transfer 95 percentile Delay (sec) Delay (sec) Delay (sec) Delay (sec) <0.5 <5 <50 <1.5 <25 <250 Unspecified
CP07_3_19
<2 <15 <75
<7 <75 <375
EMOTOROLA LTD. 2001
439
Reliability Class
ISSUE 1 REVISION 3
Reliability Class
Data reliability is defined in terms of residual error rates for the following cases: S S S S Probability of data loss Probability of data delivered out of sequence Probability of duplicate data delivery Probability of corrupt data
The Reliability Class specifies the requirements of the various network protocol layers of GTP, LLC and RLC. The transmissin modes associated with these layers are used to define the 5 Reliability Classes.
440
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Reliability Class
Reliability Class
Reliability Class
GTP Mode
LLC Frame Mode
LLC Data
RLC Block Mode
Traffic Type
Acknowledged
Acknowledged
Protected
Acknowledged
Non real-time traffic, errorsensitive application that cannot cope with data loss. Non real-time traffic, errorsensitive application that can cope with infrequent data loss. Non real-time traffic, errorsensitive application that can cope with data loss, GMM/SM and SMS. Real-time traffic, error-sensitive application that can cope with data loss. Real-time traffic, error nonsensitive application that can cope with data loss.
Unacknowledged
Acknowledged
Protected
Acknowledged
Unacknowledged
Unacknowledged
Protected
Acknowledged
Unacknowledged
Unacknowledged
Protected
Unacknowledged
Unacknowledged
Unacknowledged Unprotected Unacknowledged
Note: For real-time traffic, the QoS profile also requires appropriate settings for delay and throughput
CP07_3_20
EMOTOROLA LTD. 2001
441
Reliability Class
ISSUE 1 REVISION 3
442
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Reliability Class
Peak and Mean
Mean Peak 1 2 3 4 5 6 7 8 9 8 kb/s Currently supported 16 kb/s by GPRS 32 kb/s 64 kb/s 128 kb/s 256 kb/s 512 kb/s 1,024 Mb/s 2,048 Mb/s UMTS
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 0.22 bits/s 0.44 bits/ 1.11 bits/s 2.22 bits/s 4.4 bits/s 11.1 bits/s 22.2 bits/s 44 bits/s 111 bits/s 222 bits/s 440 bits/s 1.11 kb 2.22 kb 4.4 kb 11.1 kb 22.2 kb 44 kb 111kb/s + 1 extra called 31
CPO7_3_21
Best effort
EMOTOROLA LTD. 2001
443
Reliability Class
ISSUE 1 REVISION 3
444
EMOTOROLA LTD. 2001
Chapter 5
GPRS Signalling
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
ii
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Chapter 5 GPRS Signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP Context Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS PDP Context Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network-Requested PDP Context Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging for GPRS Downlink Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Transfer MS Originated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Transfer MS Terminated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink Packet Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release of the Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
51 52 54 56 56 58 510 512 514 514 514 514
EMOTOROLA LTD. 2001
iii
ISSUE 1 REVISION 3
iv
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Objectives
Objectives
On completion of this chapter the student should be able to: S S S S Explain the GPRS Attach/Detach signalling. Explain the GPRS Paging signalling for downlink transfer. Explain the GPRS PDP Context activation procedure. Explain the GPRS MS Packet transfer procedure.
EMOTOROLA LTD. 2001
51
GPRS Attach
ISSUE 1 REVISION 3
GPRS Attach
The procedure as shown opposite details a combined GPRS and IMSI attach. Taking each state in turn: 1. 2. The MS initiates the procedure by issuing an Attach Request The New SGSN sees from the RAI sent by the MS that it was previously attached to the Old SGSN, therefore the New SGSN sends an Identity Request message to the Old SGSN. The response back from the Old SGSN will include the IMSI and Authentication Triplets. If the MS is unknown to the New and Old SGSNs, then an Identity Request is sent, and the response should contain its IMSI. Authentication and ciphering procedures may be initiated to ensure MS and data security. A further check can be made of the MS against its IMEI. If the SGSN has changed since the MNS was last attached to the network, the Routing Area (RA) update is needed: a. b. c. d. e. f. 7. The SGSN sends an Update Location to the HLR. The HLR send Cancel Locatoin to Old SGSN. The Old SGSN acknowledges before removing Mobility Managmenet (MM) and PDP contexts. The HLR saends Inserts Subscriber Information to the New SGSN. The New SGSN acknowledges and creates a new MM context. HLR updates its own records and returns an akcnowledgement to the New SGSN.
3. 4. 5. 6.
The VLR is updated if the Gs interface is installed. a. b. The SGSN sends a Location Updating Request message to the VLR. If the LA update is inter-MSC: S S S S S c. d. The new VLR sends Update Location to the HLR. The HLR sends a Cancel Location to the old VLR. The old VLR acknowledges with Canel Location Ack. The HLR sends Insert Subscriber Data to the new VLR. The VLR acknowledges with Insert Subscription Data Ack.
After finishing the inter-MSC location update procedures, the HLR responds with Update Location Ack to the new VLR. The VLR responds with Location Updating Accept to the SGSN.
8. 9. 10. 11.
The SGSN sends an Attach Accept to the MS. If P-TMSI or VLR TMSI was changed, the MS acknowledges the received TMSI(s) with Attach Complete. If VLR TMSI was changed, the SGSN confirms the VLR TMSI re-allocation by sending TMSI Reallocatoin Complete to the VLR. If the Attach Request cannot be accepted, the SGSN returns an Attach Reject message to the MS. CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2001
52
ISSUE 1 REVISION 3
GPRS Attach
Attach
MS
BSS
New SGSN
Old SGSN
GGSN
EIR
New MSC/VLR
HLR
Old MSC/VLR
1. Attach Request 2. Identification Request 2. Identification Response 3. Identity Request 3. Identity Response 4. Authentication 5. IMEI Check 6a. Update Location 6b. Cancel Location 6c. Cancel Location Ack 6d. Insert Subscriber Data 6e. Insert Subscriber Data Ack 6f. Update Location Ack 7a. Location Updating Request 7b. Update Location 7c. Cancel Location Ack 7d. Cancel Location Ack 7e. Insert Subscriber Data 7f. Insert Subscriber Data Ack 7g. Update Location Ack 7h. Location Updating Accept 8. Attach Accept 9. Attach Complete 10. TMSI Reallocation Complete
CP07_5_1
EMOTOROLA LTD. 2001
53
GPRS Detach
ISSUE 1 REVISION 3
GPRS Detach
With respect to the diagrams shown opposite we should consider the three defined detach procedures. The top diagram on the opposite page details the Detach procedure that is initiated by the MS. 1. 2. 3. 4. The MS initiates by sending Detach Request If GPRS detach then the PDP context needs to be deleted in the GGSN. If IMSI detach, the SGSN sends IMSI detach to the VLR. If the MS wants to remain IMSI attached and is doing a GPRS detach, the SGSN sends a GPRS Detach indication message to the VLR. The VLR removes the association with the SGSN and handles paging and locatin updating without going via the SGSN. If the Switch Off parameter indicated that the MS was being switched off, then the Detach Accept is not sent.
5.
If the detach is initiated by the SGSN, then the sequence is similar to that above, except that the initial message detailed in 1 above is started by the SGSN. Stages 2 and 4 above are used as shown in the middle diagram on the opposite page. The detach sequence could be started by the HLR as shown in bottom diagram on the oppsite page, by the use of a Cancel Location MAP message. Following the Cancel Location message, the procedure is much the same as for the SGSN initiated Detach procedure.
54
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
GPRS Detach
Detach
MS
BSS
SGSN
GGSN
MSC/VLR
HLR
1. Detach Request 2. Delete PDP Context Request 2. Delete PDP Context Response 3. IMSI Detach Indication 4. GPRS Detach Indication 5. Detach Accept
MS
BSS
SGSN
GGSN
MSC/VLR
HLR
1. Detach Request 2. Delete PDP Context Request 2. Delete PDP Context Response 3. IMSI Detach Indication 4. Detach Accept
MS
BSS
SGSN
GGSN
MSC/VLR
HLR
1. Cancel Location 2. Detach Request 3. Delete PDP Context Request 3. Delete PDP Context Response 4. GPRS Detach Indication 5. Detach Accept 6. Cancel Location Ack
CP07_5_2
EMOTOROLA LTD. 2001
55
PDP Context Activation
ISSUE 1 REVISION 3

MS PDP Context Activation
1. The MS sends an Activate PDP Context Request message to the SGSN. The MS uses the PDP Address field in this message to indicate whether it requires the use of a static PDP address or whether it requires the use of a dynamic PDP address. The MS leaves PDP address empty to request a dynamic PDP address. The MS may use the Access Point Name field to select a reference point to a certain external network. Access Point Name is a logical name referring to the external packet data network that the subscriber wishes to connect to. Security functions may be executed. The Security function: Guards against unauthorised GPRS service usage (authentication and service request validation) Provides user identity confidentiality (temporary identifiction and ciphering) Provides user data confidentiality (ciphering) 3. The SGSN validates the Activate PDP Context Request. If no GGSN address can be derived then the SGSN rejects the PDP context activation request. If a GGSN address can be derived, the SGSN creates a TID for the requested PDP context by combining the IMSI stored in the MM context with the NSAPI received from the MS. If the MS requests a dynamic address, then the SGSN lets a GGSN allocate the dynamic address. The SGSN sends a Create PDP Context Request message to the affected GGSN. The GGSN creates a new entry in its PDP context table. The new entry allows the GGSN to route PDP PDUs between the SGSN and the external PDP network. The GGSN then returns a Create PDP Context Response message to the SGSN. The Create PDP Context messages are sent over the GPRS backbone network. 4. The SGSN inserts the NSAPI along with the GGSN address in its PDP context. If the MS has requested a dynamic address, the PDP address received from the GGSN is inserted in the PDP context. The SGSN selects a Radio Priority Level based on QoS Negotiated, and returns an Activate PDP Context Accept message to the MS. The SGSN is now able to route PDP PDUs between the GGSN and the MS.
2.
56
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
MS PDP Context Activation
MS
SGSN 1. Activate PDP Context Request 2. Security Functions
GGSN
3. Create PDP Context Request 3. Create PDP Context Response 4. Activate PDP Context Accept
CP07_5_4
EMOTOROLA LTD. 2001
57
Network-Requested PDP Context Activation
ISSUE 1 REVISION 3

This procedure allows the GGSN to initiate the activation of a PDP context. When receiving a PDP PDU the GGSN checks if a PDP context is established for that PDP address. If no PDP context has been previously established the GGSN may try to deliver the PDP PDU by initiating this procedure. To support Network-Requested PDP Context Activation the GGSN has to have static PDP information about the PDP address. The network operator may implement the following techniques to prevent unnecessary enquires to the HLR: S Implementation of the Mobile station Not Reachable for GPRS flag (MNRG) technique in GGSN, SGSN, and HLR that will prevent the GGSN from trying to contact the MS when its switched off or out of coverage area. The GGSN may reject or discard PDP PDUs as a result of previous unsuccessful delivery attempts. The GGSN may store the address of the SGSN with which the GGSN established the last PDP context. This would prevent an enquiry to the HLR.
S S
The Successful Network-Requested PDP Context Activation is illustrated on the opposing page and the steps are as follows: 1. When receiving a PDP PDU the GGSN determines if the Network-Requested PDP Context Activation procedure has to be initiated. The GGSN may store subsequent PDUs received for the same PDP address. The GGSN may send a Send Routeing Information for GPRS message to the HLR. If the HLR determines that the request can be served, it acknowledges the message to the GGSN. If the SGSN address is present the GGSN sends a PDU Notification Request message to the SGSN indicated by the HLR. Otherwise, the GGSN sets the MNRG flag for that MS. The SGSN returns a PDU Notification Response message to the GGSN in order to acknowledge that it shall request the MS to activate the PDP context indicated with PDP Address. The SGSN sends a Request PDP Context Activation message to request the MS to activate the indicated PDP context. The PDP context is activated with the PDP Context Activation procedure, described earlier.
2.
3.
4. 5.
58
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
MS
SGSN
HLR
GGSN 1. PDP PDU
2. Send Routing Info for GPRS 2. Send Routing Info for GPRS Ack 3. PDU Notification Request 3. PDU Notification Response 4. Request PDP Context Activation 5. PDP Context Activation Procedure
CP07_5_6
EMOTOROLA LTD. 2001
59
Paging for GPRS Downlink Transfer
ISSUE 1 REVISION 3

An MS has to be paged by the SGSN before a downlink transfer can occur. The paging process is shown opposite and detailed below: 1. 2. 3. 4. The SGSN receives Protocol Data Units (PDUs) for an MS from the network and pages the MS. The SGSN sends a BSSGP Paging Request to the BSS serving the MS. The BSS pages the MS with one Paging Request message in each cell belonging to the addressed routeing area, Upon receipt of the paging message, the MS shall respond with either any single valid LLC frame (e.g., a Receive Ready or Information frame) that implicitly is interpreted as a page response message by the SGSN. When responding, the MS changes MM state to READY. Upon reception of the LLC frame, the BSS adds an identifier of the cell and sends the LLC frame to the SGSN. The SGSN shall then consider the LLC frame to be an implicit paging response message and stop the paging response timer.
5.
510
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
GPRS Paging Area
MS
BSS
SGSN 1. PDP PDU 2. Paging Request
3. GPRS Page Request 4. Any LLC Frame 5. Any LLC Frame
CP07_5_3
EMOTOROLA LTD. 2001
511
Packet Transfer MS Originated
ISSUE 1 REVISION 3

An MS initiates a packet transfer by making a Packet Channel Request on PRACH or RACK The network responds on PAGCH or AGCH respectively. It is possible to use one or two phase packet access method. In the one phase access, the Packet Channel Request is responded by the network with the Packet Immediate Assignment reserving the resources on PDCH(s) for uplink transfer of a number of Radio blocks. The reservation is done accordingly to the information about the requested resources that is comprised in the Packet Channel Request. On RACH, there is only one cause value available for denoting GPRS and the network can assign uplink resources on 1 or 2 PDCHs. On PRACH, the Packet Channel Request may contain more adequate information about the requested resources and, consequently, uplink resources on one or several PDCHs can be assigned by using the Packet Immediate Assignment message. In the two phase access, the Packet Channel Request is responded with the Packet Immediate Assignment which reserves the uplink resources for transmitting the Packet Resource Request. The Packet Resource Request message carries the complete description of the requested resources for the uplink transfer. Thereafter, the network responds with the Packet Resource Assignment reserving resources for the uplink transfer. The Packet Immediate Assignment and the Packet Resource Assignment messages include Timing Advance (TA) and Power Control (PC) information. If there is no response to the Packet Channel Request within predefined time period, the MS makes a retry after a random backoff time. The Packet Uplink Assignment message includes the list of PDCHs and the corresponding USF value for a particular MS. A unique TFI is also allocated and is included in each RLC data and control block relating to that TBF. The MS monitors the USFs on the allocated PDCHs and transmits Radio Blocks on those, which currently bear the USF value reserved for use by that particular MS. Because each Radio Block includes an identifier (TFI), all received Radio Blocks are correctly associated with a particular LLC frame and a particular MS, which makes the protocol highly robust. Therefore, by altering the state of the USF, different PDCHs can be opened or closed dynamically for certain MSs thus providing a flexible reservation mechanism. The channel reservation algorithm can also be implemented on an assignment basis allowing individual MSs to transmit for a predetermined amount of time without interruptions. The MS may also be able to use the uplink resources for as long as there is queued data sitting above on the RLC/MAC Layer. This can comprise of a number of LLC frames.
512
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
MS originated packet transfer
MS
Network
PACKET CHANNEL REQUEST (PRACH or RACH)
IMMEDIATE ASSIGNMENT (PAGCH or AGCH)
PACKET RESOURCE REQUEST (PACCH)
PACKET RESOURCE ASSIGNMENT (PACCH)
CP07_5_7
EMOTOROLA LTD. 2001
513
Packet Transfer MS Terminated
ISSUE 1 REVISION 3

Packet Paging
The Network initiates packet transfer to an MS that is in Standby state by sending a Packet Paging Request on the downlink PPCH or PCH. The MS responds to the Packet Paging Request by initiating a procedure for page response. The RLC/MAC Packet Paging Response message contains TLLI, as well as a complete LLC frame including also TLLI. After the Packet Paging Response, the mobility management state of the MS is Ready.
Downlink Packet Transfer

Transmission of a packet to an MS in the Ready state is initiated by the Network using the Packet Resource Assignment message. In case there is PCCCH allocated in the cell, the Packet Resource Assignment is transmitted on PAGCH. In case there is no PCCCH allocated in the cell, the Packet Resource Assignment is transmitted on AGCH. The Packet Resource Assignment message includes the list of PDCH(s) that will be used for downlink transfer as well as the PDCH carrying the PACCH. The Timing Advance and Power Control information is also included, if available. Otherwise, the MS may be requested to respond with an Access Burst. Multiplexing the Radio blocks destined for different MSs on the same PDCH downlink is enabled with an identifier, e.g. TFI, included in each Radio Block. The interruption of data transmission to one MS is possible. The network sends the Radio blocks belonging to one Temporary Block Flow on downlink on the assigned downlink channels. The sending of Packet Ack/Nack is obtained by the occasional network initiated polling of the MS. The MS sends the Packet Ack/Nack message in a reserved Radio Block that is allocated together with polling. Unassigned USF value is used in the downlink Radio Block that corresponds to the reserved uplink Radio blocks. Further, if the MS wants to send some additional signalling or uplink data, it may be indicated in the Packet Ack/Nack message.
Release of the Resources

The release of the resources is initiated by the network by terminating the downlink transfer and polling the MS for a final Packet Ack/Nack. It is possible for the network to change the current downlink assignment. The first way to obtain that would be to terminate the current Temporary Block Flow, and after the MS starts to monitor the PCCCH, initiate a new one with a new assignment. The second method would be to explicitly change the downlink assignment by using the Packet Resource Reassignment which then has to be acknowledged by the MS in an immediate reserved block period on the uplink. The handling of TFI and USF is steered with the same timer that runs on both the MS and the network side after the last RLC Data Block is sent to the MS. When it expires, the current assignment becomes invalid for the MS and both USF and TFI can be reused by the network. Further, USF and TFI may be reused already upon the reception of the final Packet Ack/Nack from the MS.
514
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
MS terminated packet transfer

PAGING MS Network
PACKET PAGING REQUEST (PPCH or PCH)
PACKET CHANNEL REQUEST (RACH or PRACH)
PACKET IMMEDIATE ASSIGNMENT (PAGCH or AGCH)
UPLINK TBF LLC FRAME (PACCH)
CP07_5_8
RESOURCE ASSIGNMENT
MS
PACCH PAGCH AGCH
Network
PACKET RESOURCE ASSIGNMENT
CP07_5_9
DATA TRANSFER
MS
DATA BLOCK DATA BLOCK DATA BLOCK DATA BLOCK DATA BLOCK (polling) Temporary Packet Ack/Nack
Network
CP07_5_10
EMOTOROLA LTD. 2001
515
ISSUE 1 REVISION 3
516
EMOTOROLA LTD. 2001
Chapter 6
Future Enhancements
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
ii
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Chapter 6 Future Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSCSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced General Packet Radio Service (EGPRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced Data Rates for GSM Evolution (EDGE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UMTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Benefits of UMTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UMTS Future Vision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
61 62 64 66 68 610 614 616
EMOTOROLA LTD. 2001
iii
ISSUE 1 REVISION 3
iv
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Objectives
Objectives
On completion of this chapter the student should be able to: S S S Explain the concept of HSCSD. Explain the concept of EGPRS and EDGE. Explain the benefits of UMTS and how they will be introduced.
EMOTOROLA LTD. 2001
61
Mobile Evolution
ISSUE 1 REVISION 3
Mobile Evolution
UMTS is an ETSI term for a Third Generation (3G) mobile telecommunication service. Over recent years, mobile telephony evolutions have become known as:
First Generation
In the early 1980s the First Generation were the Worlds first public mobile telephone services such as AMPS (US), TACS (UK) and NMT (Scandinavia). These systems were analogue, provided national coverage (though from complete in most cases) and offered limited services.
Second Generation
GSM is by far the Worlds primary Second Generation system. Designed by a joint effort from manufacturers, regulators and service suppliers from many (European) countries, GSM became a European and then a global standard. CDMA systems now under the collective term of cdmaOne are the other major Second Generation technology. Globally, arguments about which was superior became largely academic because GSM was deployed first (early 1990s) and rapidly gained universal acceptance (with the exception of the US and Japan). CDMA has been launched more recently (mid 1990s) and has shown remarkable uptake and growth. In late 1998 there are an estimated 12 million CDMA users and over a 100 million GSM users. Second Generation Systems offer: S S S S S Open standards (arguable for CDMA) Digital technology (near) National coverage and roaming Voice and data (limited rates) Supplementary Services
Third Generation
The Worlds leading telecommunication authorities such as the International Telecommunications Union (ITU), ETSI and others are formulating specifications for the next generation of mobile telecommunication devices and networks. Within ETSI this network is known as the Universal Mobile Telecommunication System UMTS and is data focused.
62
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Mobile Evolution
Mobile Evolution
UMTS
2G
GSM GSM 900 Operator GSM 1800
GPRS
EDGE
3G
Packet data Support
CP07_6_1
EMOTOROLA LTD. 2001
63
HSCSD
ISSUE 1 REVISION 3
HSCSD
It is intended that HSCSD will use the 14.4kbps channel coding option and that it will additionally use multiple timeslots. To see how this might operate requires a basic knowledge of the physical structure of a traffic channel on the Air interface. The uplink and downlink of a GSM traffic channel take place on different frequencies. Also the uplink and downlink timeslots occur at different times in the 8 timeslot frame. Additionally when engaged in a traffic channel a GSM mobile station must constantly be monitoring downlink power levels from neighbouring cells as part of the handover process. Over an 8 timeslot frame therefore a mobile will: S S S Receive a downlink burst Transmit an uplink burst Monitor a downlink transmission from a neighbouring cell
2 Timeslots
One restriction that HSCSD places upon multiple timeslot links is that the timeslots allocated must be consecutive. As can be seen from the diagram the use of two timeslots is relatively simple to implement. The mobile is still able to run through its standard routine of receive, transmit, monitor a neighbour within an 8 timeslot frame. With 3 or more timeslots being used there is an overlap between the receive and transmit times and implementation of this involves substantial hardware changes in the mobile station., i.e. the use of a RF duplexor. (at first sight it looks as if there is no overlap when using 3 timeslots but there is due to the timing advance applied to the uplink).
64
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
HSCSD
HSCSD
Mobile Rx 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
Measure a Neighbour
Measure a Neighbour
0 Mobile Tx
Data Rate 28.8 kbps
CP07_6_2
EMOTOROLA LTD. 2001
65
Enhanced General Packet Radio Service (EGPRS)
ISSUE 1 REVISION 3

It is proposed that EGPRS will offer eight additional coding schemes. The lower layers of the user data plane, which has been specifically designed for GPRS operation is reflected in the protocol, stack comprising Physical, RLC/MAC and LLC layers. While the LLC layer can be used without modifications when EDGE functionality is introduced, it is necessary to modify the RLC/MAC layer to support features such as efficient multiplexing and link adaptation. The basic modifications needed for EDGE consider the form of the data blocks that are being transferred across the radio interface. For EGPRS, several combinations of interleaving and coding have been proposed where as in the current GPRS proposals, the interleaving depth is set to four bursts. Link adaptation offers mechanisms for choosing the best modulation and coding alternative for the current radio link. In GPRS, only the coding scheme can be altered between two consecutive LLC frames however, with EGPRS a refined link adaptation concept can be utilised which allows both coding and modulation schemes to be changed to suit the given radio link. In addition, link adaptation should allow seamless switching between the two modulation schemes to such an extent that in EGPRS, the Uplink State Flag (USF) information can be modulated using BOQAM and the user data by QOQAM. BOQAM is used here for the broadcast purposes and facilitates the characteristics of being robust and therefore available in the whole GSM coverage area. Six coding schemes have been specified for 8PSK with regards EGPRS and these can be seen opposite. It is assumed that each communication link will be able to choose the modulation and coding combination that achieves the highest throughput for that particular link quality. For example, users with a low C/I ratio will be allowed to perform a link adaptation towards GMSK as opposed to 8PSK. This link adaptation between GMSK and 8PSK should be seamless since both modulation schemes utilise the same symbol rate of 270.833ksps.
66
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Service Name EGPRS PCS1 EGPRS PCS2 EGPRS PCS3 EGPRS PCS4 EGPRS PCS5 EGPRS PCS6
Code Rate 0.326 0.496 0.596 0.756 0.829 1.00
Modulation 8PSK 8PSK 8PSK 8PSK 8PSK 8PSK
Gross Rate 69.2kbp 69.2kbp 69.2kbp 69.2kbp 69.2kbp 69.2kbp
Radio Interface Rate* 22.8kbps 34.3kbps 41.25kbps 51.6kbps 57.35kbps 69.2kbps
* The ratio interface rate includes signalling overhead in the RLC/MAC layer
CP07_6_3
EMOTOROLA LTD. 2001
67
Enhanced Data Rates for GSM Evolution (EDGE)
ISSUE 1 REVISION 3

Enhanced Data Rates for GSM Evolution (EDGE) is a proposed modification to the modulation scheme utilised by GSM (i.e. Gaussian Minimum Shift Keying). This change will drastically increase the bit rates available to end users for the purpose of data transfer. It is envisaged that the enhanced modulation techniques will make it possible to maintain a good quality link by automatically adapting to the radio interference conditions and thereby provide the highest possible rate. The exact implementation and technical details are still being discussed in various ETSI feasibility studies but there are certain factors that one can almost assume to be near completion. Two additional modulation schemes have been proposed and these are Quaternary Offset Quadrature Amplitude Modulation (QOQAM) and Binary Offset Quadrature Amplitude Modulation (BOQAM). These two new modulation schemes will both result in symbol rates of 361.111 kbps but QOQAM will offer a higher bit rate as it supports 2 bits / symbol. Wherever possible, EDGE adopts the GSM standards so as to minimise the changes required by manufactures and operators who wish to support this new technology. This includes maintaining the same frequency plan, meaning that 200kHz will still separate carriers. In addition, the TDMA structure supported by GSM will remain intact at eight timeslots per frame. Also, the relationship between logical and physical channels will remain unchanged. The feasibility study carried out by ETSI on EDGE proposes that it will be able to support both circuit switched services: transparent and nontransparent in addition to the packet based GPRS. These three new services will be called: ECSD T ECSD NT EGPRS Enhanced Circuit Switched Data Transparent. Enhanced Circuit Switched Data Nontransparent. Enhanced General Packet Radio Service.
68
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
EDGE and GSM Comparison
UMTS (2Mbps) EDGE EGPRS GPRS HSCSD Data Rates GSM Data 14.4kbps GSM Data 9.6kbps Packet Data Circuit Switched Data
CP07_6_4
EMOTOROLA LTD. 2001
69
UMTS
ISSUE 1 REVISION 3
UMTS
UMTS (Universal Mobile Telecommunications System) is the European member of the IMT2000 family of Third Generation cellular mobile standards. UMTS will enter the market at a time when fixedmobile integration is becoming a reality, the telecoms, computer and media industries have converged on Internet Protocol (IP) as a shared standard and data accounts for a significant proportion of the traffic carried by mobile networks. UMTS Requirements include: S S S S Small, low cost pocket terminals Worldwide roaming A single system for residential, Office, Cellular and Satellite environments High Speed Data Vehicular 144 kb/s Pedestrian 384 kb/s Indoor 2Mb/s UMTS will support data rates of up to 2Mb/s and new multimedia applications over a new wideband air interface based on CDMA techniques. Services will be supported by a wide range of terminals tailored to the requirements of voice, data and multimedia services.
610
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
UMTS
UMTS System Configuration
PSTN
GMSC Circuit Switched up to 64kbit/s BSC Gb VAS Server SGSN RNC Node B BTS
A HLR AUC MSC
Internet GGSN PSDN
Packet Switched up to 2 Mbit/s
CP07_6_5
EMOTOROLA LTD. 2001
611
UMTS
ISSUE 1 REVISION 3
UMTS will encompass more than just cellular systems, evolving from GSM and embracing fixed networks and other wireless and wireline access technologies. Services will be globally available, delivered over the mobile, satellite or fixed networks that provides the best accessibility for the consumers specific location. The current vision of most operators is that UMTS will exist as islands of coverage with data services supported by GPRS in areas of lower traffic density. If data demand is sufficient it may be economical to upgrade such areas to EDGE, rather than deploy WCDMA. Despite the apparent attractions of deploying EDGE as an incremental solution, operators will need to deploy UMTSas only WCDMA can support the high traffic densities encountered in the core of mature networks. The initial release of the EDGE standard is aimed at increasing the capacity and speed of GPRS data services. The second phase of the EDGE standard will support packet voice using Voice over IP (VoIP) techniques.
612
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
UMTS
UMTS Islands of Coverage
EDGE
WCDMA Med QoS
WCDMA High QoS
GSM/GPRS
CPO7_6_6
EMOTOROLA LTD. 2001
613
User Benefits of UMTS
ISSUE 1 REVISION 3

In line with subscribers increasing expectations of GSM systems, UMTS will of course provide a very high quality of service in all environments. This will be further enhanced by the implementation of the Adaptive MultiRate (AMR) codec. In addition, users will benefit from:
Seamless global roaming

The implementation of the Virtual Home Environment will give users the same seamless service regardless of serving network type. This means that users can access their personalised service profile through any network from any terminal, optimise the display of information and simplify access to the key services that they use most. This programmable personality will be stored in the SIM card, and this will allow the same user interface to be available on any phone anywhere in the world.
High speed data services

The UMTS network will provide costeffective data transmission with the flexibility to remain online at all times, whilst only paying for the amount of data received or transmitted. Terminals will always be connected to the network, emails could be received as soon as they are sent and access to the Intranet and Internet will be immediately available all the time with no setup delay. All this will be available at even higher data rates than those offered by GPRS systems.
Multimedia services
New multimedia services will include video conferencing, interactive entertainment, and video transport in the case of an emergency or disaster. Multimedia technology will also make it possible to offer electronic magazines or newspapers complete with graphics and video clips.
New innovative applications

The involvement of new Value Added Service Providers in the UMTS commercial model provides the opportunity for a wide range of new applications to be offered. Examples are supplementary features for traditional voice callers such as location based services.
Telematics
Building on GPRS services, UMTS will support machine to machine communications in applications such as vending machine monitoring.
Increased integration between fixed and mobile telephony services

The increased integration of these services offers users both an increase in ease of use and increased affordability.
Increased choice of services

The opening up of the market for service provision and the simplification of service creation will provide users with an increased range of services from which to select. The increase in competition in the market is also expected to ensure that these services are offered to the user at an affordable.
614
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
UK3G Vision
Global
Satellite
Suburban Urban InBuilding
MacroCell
MicroCell
PicoCell
HomeCell
Audio/vis Terminal
CPO7_6_7
EMOTOROLA LTD. 2001
615
UMTS Future Vision
ISSUE 1 REVISION 3
UMTS Future Vision

The UMTS core network will be based upon a broadband network carrying IPbased traffic. An ATM network could provide the quality of service necessary for reliable and efficient transport of multimedia data. Due to the need to support legacy interconnect options to the cell site for many years, Frame Relay remains an attractive option to maximise the efficiency of the BTS backhaul links. The key changes in the UMTS architecture are that: S The NSS has moved to an efficient packetbased transport, using lowcost standard packet switches to route the call and signalling traffic. This also requires changes to the peripherals, such as the voice mail system, which now operates in a packetbased voicetranscoded (and thus higher voice quality) mode. The transcoding and datainterworking functions have moved to the periphery of the network, where it connects with other networks.
In the future UMTS network, the functions required to control the mobile network are server based and the underlying broadband network carries out the switching functions. The core platforms are built upon a common hardware and software architecture allowing functions to be distributed as required.
616
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
UMTS Future Vision
UMTS Future Vision
Service Provider
Service Mgmt
PSTN
PDN
TIPHON
HLR, SLR GMSC CAMEL Server SIM Server
Circuit Gateway
GGSN Packet Gateway UMTS Server
NMC
Application Server InBuilding System
Broadband Network BSC/RNC Server
Corporate
BTS
GSM BTS
Dual Mode BTS
UMTS BTS
TIPHON = Telephony and Internal Protocol Harmonization over Networks
CPO7_6_8
EMOTOROLA LTD. 2001
617
UMTS Future Vision
ISSUE 1 REVISION 3
618
EMOTOROLA LTD. 2001
Glossary of Terms
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
ii
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A ......................................................................... B ......................................................................... C ......................................................................... D ......................................................................... E ......................................................................... F ......................................................................... G ......................................................................... I .......................................................................... L ......................................................................... M ......................................................................... N ......................................................................... P ......................................................................... Q ......................................................................... R ......................................................................... S ......................................................................... T ......................................................................... U ......................................................................... V .........................................................................
i
Glos1 Glos2 Glos3 Glos5 Glos6 Glos7 Glos8 Glos9 Glos10 Glos11 Glos12 Glos13 Glos15 Glos16 Glos17 Glos19 Glos20 Glos21
EMOTOROLA LTD. 2001
iii
ISSUE 1 REVISION 3
iv
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
A
On completion of this chapter the student should be able to: AA APN ATM Anonymous Access Access Point Name Asynchronous Transfer Mode
access delay: The value of elapsed time between an access request and a successful access (source: ITUT X.140). access protocol: a defined set of procedures that is adopted at an interface at a specified reference point between a user and a network to enable the user to employ the services and/or facilities of that network (source: ITUT I.112). accuracy: A performance criterion that describes the degree of correctness with which a function is performed. (The function may or may not be performed with the desired speed.) (source: ITUT I.350).
EMOTOROLA LTD. 2001
Glos1
ISSUE 1 REVISION 3
B
BCS BEC BH Block Check Sequence Backward Error Correction Block Header
BSSGP Virtual Connection (BVC): An endtoend virtual communication path between remote Network Service user entities. BSSGP Virtual Connection Identifier (BVCI): The identifier of a BVC, having endtoend significance across the Gb interface. Block period: A block period is the sequence of four timeslots on a PDCH used to convey one radio block. BG BSSAP+ BSSGP Border Gateway Base Station System Application Part + Base Station System GPRS Protocol
basic service: The telecommunication services excluding the supplementary services (source: GSM 01.04). bearer service: A type of telecommunication service that provides the capability for the transmission of signals between usernetwork interfaces (source: GSM 01.04, ITUT I.112). best effort service: A service model which provides minimal performance guarantees, allowing an unspecified variance in the measured performance criteria.
Glos2
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
C
CS CU CCU CGI CS CLNP CLNS CONS Coding Scheme Cell Update Channel Codec Unit Cell Global Identification Circuit Switched Connectionless network protocol Connectionless network service Connectionoriented network service
calling user: Entity which originates a call to the General Packet Radio Service (GPRS). connectionless service: A service which allows the transfer of information among service users without the need for endtoend call establishment procedures (source: ITUT I.113). connectionlessmode transfer: The terms message, datagram, transaction mode and connectionfree have been used in the literature to describe variations on the same basic theme: the transmission of a unit of data in a single, selfcontained operation without establishing, maintaining, and releasing a connection. (Connectionlessmode transmission) is the transmission of a single unit of data from a source serviceaccesspoint to one or more destination serviceaccesspoint(s) without establishing a connection. A connectionlessmode service allows an entity to initiate such a transmission by the performance of a single service access. In contrast to a connection, an instance of the use of a connectionlessmode service does not have a clearly distinguishable lifetime. In addition, the connectionlessmode service, unless otherwise explicitly determined, has the following fundamental characteristics: a) no dynamic peertopeer agreement is involved in an instance of the service; b) all of the information required to deliver a unit of data (destination address, quality of service selection, options, etc.) is presented to the layer providing the connectionlessmode service, together with the user data to be transmitted, in a single service access. The layer providing the connectionlessmode service is not required to relate this access to any other service access. As a result of these fundamental characteristics it may also be true that c) each unit of data transmitted is entirely selfcontained and can be routed independently; d) copies of a unit of data can be transmitted to a number of destination addresses. NOTE: Connectionlessmode transfer normally implies that the service a) does not provide confirmed delivery of SDUs, b) does not guarantee delivery of SDUs, c) does not guarantee maintenance of SDU sequencing and d) does not guarantee elimination of SDUs.
EMOTOROLA LTD. 2001
Glos3
ISSUE 1 REVISION 3
connectionmode transfer: A connection is an association established for the transfer of data between two or more peerentities. This association is established between the peerentities themselves and between each entity and the next lower layer. The ability to establish a connection and to transfer data over it is provided to the entities in a given layer by the next lower layer as a connectionmode service. An instance of the use of a connectionmode service by peerentities proceeds through three distinct phases of operation: a) b) c) connection establishment; data transfer; and connection release.
NOTE: Connectionmode transfer normally implies that the service a) provides confirmed delivery of SDUs, b) provides ordered, insequence delivery of SDUs and c) will not duplicate SDUs. conversational service: An interactive service which provides for bidirectional communication by means of realtime (no storeandforward) endtoend information transfer from user to user (source: ITUT I.113).
Glos4
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
D
DNS Domain Name System demand service: A type of telecommunication service in which the communication path is established almost immediately, in response to a user request effected by means of usernetwork signalling (source: GSM 01.04, ITUT I.112). dependability: A performance criterion that describes the degree of certainty (or surety) with which a function is performed regardless of speed or accuracy, but within a given observational interval (source: ITUT I.350). destination user: Entity to which calls to the General Packet Radio Service (GPRS) are directed.
EMOTOROLA LTD. 2001
Glos5
ISSUE 1 REVISION 3
E
extra SDU delivery probability: The ratio of total (unrequested) extra service data units (SDUs) to total service data units received by a destination user in a specified sample (source: ITUT X.140). NOTE: data unit. the term user information unit has been replaced by the term service
Glos6
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
F
functional group: A set of functions that may be performed by a single equipment (source: ITUT I.112).
EMOTOROLA LTD. 2001
Glos7
ISSUE 1 REVISION 3
G
GGSN GMM/SM GSN GTP GPRS GSN Gateway GPRS Support Node GPRS Mobility Management and Session Management GPRS Support Node GPRS Tunnelling Protocol General packet radio service GPRS support node
GPRS MS class The term GPRS MS class refers to the different mobile station implementations and the different modes of operation possible for GPRS, see GSM 02.60. In this ETS, the expression that a mobile station belongs to a certain GPRS MS class (A, B or C) is used to denote the case that a mobile station is currently operating according to the RR procedures specified for the particular GPRS MS class. The GPRS MS class, to which a mobile station belongs, depends on the GSM services to which the mobile station is currently attached, i.e., GSM GPRS services, GSM circuit switched services including SMS, or both, and to the extent a simultaneous invocation of these services is possible. The GPRS MS class a mobile station belongs to may shift in time. GPRS multislot class The term GPRS multislot class refers to the different mobile station capabilities to transmit and receive on different combinations of multiple PDCHs. The multislot classes are defined in GSM 05.02. Note that the mobile station may indicate different multislot classes for circuit mode services and for GPRS (see GSM 04.08). Different multislot class mobile stations are capable of supporting different medium access modes. guaranteed service: A service model which provides highly reliable performance, with little or no variance in the measured performance criteria. GTPFlow: A GTP flow is defined by the unidirectional virtual aggregation of GPDUs and/or signalling messages related to one or more GTP tunnels. A GTP flow is identified by a Flow Label included in the GTP header. The meaning of the Flow Label is transparent for the transmitter side, only the receiver may evaluate the Flow Label. GTP tunnel: A GTP tunnel is defined by two associated PDP Contexts in different GSN nodes and is identified with a Tunnel ID. A GTP tunnel is necessary to forward packets between an external packet data network and a MS user.
Glos8
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
I
IP IETF IPv4 IPv6 ISP Internet protocol Internet Engineering Task Force Internet Protocol version 4 Internet Protocol version 6 Internet Service Provider
interactive service: A service which provides the means for bidirectional exchange of information between users. Interactive services are divided into three classes of services: conversational services, messaging services and retrieval services (source: ITUT I.113). interface: The common boundary between two associated systems (source: GSM 01.04, ITUT I.112).
EMOTOROLA LTD. 2001
Glos9
ISSUE 1 REVISION 3
L
LLC Logical Link Control
Glos10
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
M
MAC MNRF MNRG MNRR Medium Access Control Mobile station Not Reachable Flag Mobile station Not Reachable for GPRS flag Mobile station Not Reachable Reason
mean bit rate: A measure of throughput. The average (mean) bit rate available to the user for the given period of time (source: ITUT I.210). mean transit delay: The average transit delay experienced by a (typically) large sample of PDUs within the same service category. messaging service: An interactive service which offers usertouser communication between individual users via storage units with storeandforward, mailbox and/or message handling, (e.g., information editing, processing and conversion) functions (source: ITUT I.113). mobile station: Equipment intended to access a set of GSM PLMN telecommunication services. Services may be accessed while the equipment capable of surface movement within the GSM system area is in motion or during halts at unspecified points (source: GSM 01.04). mobile termination: The part of the mobile station which terminates the radio transmission to and from the network and adapts terminal equipment capabilities to those of the radio transmission (source GSM 01.04).
EMOTOROLA LTD. 2001
Glos11
ISSUE 1 REVISION 3
N
NSDU NGAF NS Network service data unit NonGPRS Alert Flag Network Service
Network Service Virtual Connection (NSVC): An endtoend virtual communication path between Network Service peer entities. Network Service Virtual Connection (NSVCI) Identifier: The identifier of an NSVC having endtoend significance across the Gb interface. Network Service Virtual Link (NSVL): A virtual communication path between the BSS or the SGSN and the intermediate network, or between the BSS and the SGSN in case of direct pointtopoint configuration. Network Service Virtual Link Identifier (NSVLI): The identifier of an NSVL, having local significance at the BSS or SGSN. Network Service Virtual Connection Group: Groups NSVCs together which provide communication between the same peer NS entities. This grouping has local significance at the BSS or SGSN. NSAPI Network layer Service Access Point Identifier. For each SNPDU the NSAPI is an index to the PDP context of the PDP that is using the services provided by the SNDCP layer. NSS Network SubSystem
network connection: An association established by a network layer between two users for the transfer of data, which provides explicit identification of a set of network data transmissions and agreement concerning the services to be provided by the set (source: ITUT X.213 / ISOIEC 8348). network operator: Entity which provides the network operating elements and resources for the execution of the General Packet Radio Service (GPRS). network service data unit (NSDU): A unit of data passed between the user and the GPRS network across a Network Service Access Point (NSAP). network termination: A functional group on the network side of a usernetwork interface (source: ITUT I.112).
Glos12
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
P
PACCH PAGCH PBCCH PC PCCCH PDCH PDTCH PDU PL PNCH PPCH PRACH PTMSI PCU PDCH PDN PDP PDU PPF PTM PTP PVC PLMN Packet Associate Control Channel Packet Access Grant Channel Packet Broadcast Control Channel Power Control Packet Common Control Channel Packet Data Channel Packet Data Traffic Channel Protocol Data Unit Physical Link Packet Notification Channel (for PTMM on PCCCH) Packet Paging Channel Packet Random Access Channel Packet TMSI Packet Control Unit Packet Data CHannel Packet Data Network Packet Data Protocol, e.g., IP or X.25 [33] Protocol Data Unit Paging Proceed Flag Point To Multipoint Point To Point Permanent Virtual Circuit Public land mobile network
Packet idle mode: (only applicable for mobile stations GPRS of class A, B or C): In this mode, the mobile station is prepared to transfer LLC PDUs on packet data physical channels. The mobile station is not allocated any radio resource on a packet data physical supporting channel; it listens to the PBCCH and PCCCH or, if those are not provided by the network, to the BCCH and the CCCH. Packet transfer mode: (only applicable for mobile stations supporting GPRS of class A, B or C): In this mode, the mobile station is prepared to transfer LLC PDUs on packet data physical channels, see clause 5. The mobile station is allocated radio resource on one or more packet data physical channels for the transfer of LLC PDUs. packet: An information unit identified by a label at layer 3 of the OSI reference model (source: ITUT I.113). A network protocol data unit (NPDU). packet data protocol (PDP): Any protocol which transmits data as discrete units known as packets, e.g., IP, or X.25. packet transfer mode: Also known as packet mode. A transfer mode in which the transmission and switching functions are achieved by packet oriented techniques, so as
EMOTOROLA LTD. 2001
Glos13
ISSUE 1 REVISION 3
to dynamically share network transmission and switching resources between a multiplicity of connections (source: ITUT I.113). peak bit rate: A measure of throughput. The maximum bit rate offered to the user for a given time period (to be defined) for the transfer of a bursty signal (source: ITUT I.210). (The maximum user information transfer rate achievable by a user for a single service data unit transfer.) PLMN Operator: Public Land Mobile Network operator. The entity which offers a GPRS. pointtopoint (PTP): A value of the service attribute communication configuration, which denotes that the communication involves only two network terminations. pointtopoint (PTP) service: A service type in which data is sent from a single network termination to another network termination. predictive service: A service model which provides reliable performance, but allowing a specified variance in the measured performance criteria. protocol: A formal set of procedures that are adopted to ensure communication between two or more functions within the within the same layer of a hierarchy of functions (source: ITUT I.112). protocol data unit (PDU): In the reference model for OSI, a unit of data specified in an (N)protocol layer and consisting of (N)protocol control information and possibly (N)user data (source: ITUT X.200 / ISOIEC 74981).
Glos14
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
Q
QoS Quality of service quality of service: The collective effect of service performances which determine the degree of satisfaction of a user of the service (ITUT E.800). The set of performance parameters that can be directly observed and measured at the point at which the service is accessed by the user. There are three criteria by which performance is measured: speed, accuracy and dependability (source: ITUT I.350).
EMOTOROLA LTD. 2001
Glos15
ISSUE 1 REVISION 3
R
RA RAC RAI RLC Routeing Area Routeing Area Code Routeing Area Identity Radio Link Control
Radio block: A radio block is the sequence of four normal bursts carrying one RLC/MAC protocol data unit. (The one exception is a radio block occasionally used on PACCH consisting of a sequence of four access bursts, each carrying a repetition of one short RLC/MAC block.) RLC/MAC block: A RLC/MAC block is the protocol data unit exchanged between RLC/MAC entities, see clause 10. RLC/MAC control block: A RLC/MAC control block is the part of a RLC/MAC block carrying a control message between RLC/MAC entities. RLC data block: A RLC data block is the part of a RLC/MAC block carrying user data or upper layers signalling data. reference configuration: A combination of functional groups and reference points that shows possible network arrangements (source: GSM 01.04, ITUT I.112). reference point: A conceptual point at the conjunction of two nonoverlapping functional groups (source: GSM 01.04, ITUT I.112). residual error rate: A parameter describing service accuracy. The frequency of lost SDUs, and of corrupted or duplicated network SDUs delivered at the usernetwork interface. retrieval service: An interactive service which provides the capability of accessing information stored in data base centres. The information will be sent to the user on demand only. The information is retrieved on an individual basis, i.e., the time at which an information sequence is to start is under the control of the user (source ITUT I.113).
Glos16
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
S
SAP SVC SDU SGSN SM SMSC SMSGMSC SMSIWMSC SNPDU SNDC SNDCP Service access point Switched virtual circuit Service data unit Serving GPRS Support Node Short Message Short Message service Service Centre Short Message Service Gateway MSC Short Message Service Interworking MSC SNDCP PDU SubNetwork Dependent Convergence SubNetwork Dependent Convergence Protocol
SDU error probability: The ratio of total incorrect service data units (SDUs) to total successfully transferred service data units plus incorrect service data units in a specified sample (source: ITUT X.140). NOTE: the source document term user information unit has been replaced by the term service data unit. SDU loss probability: The ratio of total lost service data units (SDUs) to total transmitted service data units in a specified sample (source: ITUT X.140). NOTE: the source document term user information unit has been replaced by the term service data unit. SDU misdelivery probability: The ratio of total misdelivered service data units (SDUs) to total service data units transferred between a specified source and destination user in a specified sample (source: ITUT X.140). NOTE: the source document term user information unit has been replaced by the term service data unit. SDU transfer delay: The value of elapsed time between the start of transfer and successful transfer of a specified service data unit (SDU) (source: ITUT X.140). NOTE: the source document term user information unit has been replaced by the term service data unit. SDU transfer rate: The total number of successfully transferred service data units (SDUs) in a transfer sample divided by the input/output time for that sample. The input/output time is the larger of the input time or the output time for the sample (source: ITUT X.140). NOTE: the source document term user information unit has been replaced by the term service data unit. service access point (SAP): In the reference model for OSI, the points through which services are offered to an adjacent higher layer (source: GSM 01.04, ITUT X.200 / ISOIEC 74981). service attribute: A specified characteristic of a telecommunication service (source: ITUT I.112). NOTE: the value(s) assigned to one or more service attributes may be used to distinguish that telecommunications service from others.
EMOTOROLA LTD. 2001
Glos17
ISSUE 1 REVISION 3
service bit rate: The bit rate that is available to a user for the transfer of user information (source: ITUT I.113). service category or service class: A service offered to the users described by a set of performance parameters and their specified values, limits or ranges. The set of parameters provides a comprehensive description of the service capability. service data unit (SDU): In the reference model for OSI, an amount of information whose identity is preserved when transferred between peer (N+1)layer entities and which is not interpreted by the supporting (N)layer entities (source: ITUT X.200 / ISOIEC 74981). service delay: The time elapsed from the invocation of the service request, to the corresponding service request indication at the Service Receiver, indicating the arrival of application data. service model: A general characterisation of services based upon a QoS paradigm, without specifying the actual performance targets. service provider: Entity which offers the General Packet Radio Service (GPRS) for subscription. The network operator may be the service provider. service receiver: The entity which receives the service request indication primitive, containing the SDU. service request: This is defined as being one invocation of the service through a service request primitive. service requester: The entity which requests the initiation of a GPRS operation, through a service request. service subscriber: Entity which subscribes to the General Packet Radio Service (GPRS) service. signalling: The exchange of information specifically concerned with the establishment and control of connections, and with management, in a telecommunications network (source: ITUT I.112). simultaneous use of services: The concurrent use of a GSM circuitmode service (voice or data) and GSM packetmode services (GPRS) by a single mobile station. speed: A performance criterion that describes the time interval required to perform a function or the rate at which the function is performed. (The function may or may not be performed with the desired accuracy.) (source: ITUT I.350).
Glos18
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
T
TA TBF TFI Timing Advance Temporary Block Flow Temporary Frame Identity
Temporary Block Flow (TBF): A Temporary Block Flow (TBF) is a physical connection used by the two RR peer entities to support the unidirectional transfer of LLC PDUs on packet data physical channels. TCAP TCP TID TRAU TLLI Transaction Capabilities Application Part Transmission Control Protocol Tunnel Identifier Transcoder and Rate Adaptor Unit Temporary link level identity
teleaction service: A type of telecommunication service that uses short messages, requiring a low transmission rate, between the user and the network (source: ITUT I.112). telecommunication service: That which is offered by a PLMN operator or service provider to its customers in order to satisfy a specific telecommunication requirement. (source: GSM 01.04, ITUT I.112). Telecommunication services are divided into two broad families: bearer services and teleservices (source: ITUT I.210). teleservice: A type of telecommunication service that provides the complete capability, including terminal equipment functions, for communication between users according to protocols established by agreement between Administrations (source: GSM 01.04, ITUT I.112). terminal equipment: Equipment that provides the functions necessary for the operation of the access protocols by the user (source: GSM 01.04). A functional group on the user side of a usernetwork interface (source: ITUT I.112). throughput: A parameter describing service speed. The number of data bits successfully transferred in one direction between specified reference points per unit time (source: ITUT I.113). transit delay: A parameter describing service speed. The time difference between the instant at which the first bit of a protocol data unit (PDU) crosses one designated boundary (reference point), and the instant at which the last bit of the PDU crosses a second designated boundary (source: ITUT I.113).
EMOTOROLA LTD. 2001
Glos19
ISSUE 1 REVISION 3
U
UDP User Datagram Protocol Uplink State Flag (USF): The Uplink State Flag (USF) is used on PDCH channel(s) to allow multiplexing of uplink Radio blocks from different mobile stations. user access or user network access: The means by which a user is connected to a telecommunication network in order to use the services and/or facilities of that network (source: GSM 01.04, ITUT I.112). usernetwork interface: The interface between the terminal equipment and a network termination at which interface the access protocols apply (source: ITUT I.112). useruser protocol: A protocol that is adopted between two or more users in order to ensure communication between them (source: ITUT I.112).
Glos20
EMOTOROLA LTD. 2001
ISSUE 1 REVISION 3
V
variable bit rate service: A type of telecommunication service characterised by a service bit rate specified by statistically expressed parameters which allow the bit rate to vary within defined limits (source: ITUT I.113).
EMOTOROLA LTD. 2001
Glos21
ISSUE 1 REVISION 3
Glos22
EMOTOROLA LTD. 2001

GPRS Basics

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

GPRS Basics

Cargado por

Copyright:

Formatos disponibles

CHAPTER 1

Cellular Infrastructure Group

CP07 INTRODUCTION TO GPRS

FOR TRAINING PURPOSES ONLY

CP07 INTRODUCTION TO GPRS

FOR TRAINING PURPOSES ONLY

CP07 INTRODUCTION TO GPRS

CP07 Introduction to GPRS

EMOTOROLA LTD. 2001

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

Copyrights, notices and trademarks

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

Chapter 1 GSM Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2 GPRS Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

Chapter 3 Terrestrial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 4 Air Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

Chapter 5 GPRS Signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 6 Future Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

62 64 66 68 610 614 616

EMOTOROLA LTD. 2001

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

About this manual

EMOTOROLA LTD. 2001

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

Special key sequences

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

First aid in case of electric shock

First aid in case of electric shock

EMOTOROLA LTD. 2001

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

Reporting safety issues

Reporting safety issues

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

Warnings and cautions

Warnings and cautions

Example and format

Example and format

EMOTOROLA LTD. 2001

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

EMOTOROLA LTD. 2001

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

Human exposure to radio frequency energy (PCS1900 only)

Human exposure to radio frequency energy (PCS1900 only)

Maximum permitted exposures

Power density (S)

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

Human exposure to radio frequency energy (PCS1900 only)

Maximum permitted exposure ceilings

1.287mW/cm 2 1.313mW/cm 2 6.433mW/cm 2 6.567mW/cm 2

EMOTOROLA LTD. 2001

CP07: Introduction to GPRS FOR TRAINING PURPOSES ONLY