GPRS Overview

Cellular Infrastructure Group
GPRS-300-101
GSN Software Release 1
SYSTEM INFORMATION GPRS OVERVIEW
68P02903W01-C
GPRS-300-101 GSN Software Release 1
System Information GPRS Overview
E Motorola 1999 - 2001 All Rights Reserved Printed in the U.K.
3rd May 01
System Information: GPRS Overview 68P02903W01-C
GPRS-300-101
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 registered trademarks of Motorola Inc. M-Cell and Taskfinder are trademarks of Motorola Inc. All other brands and corporate names are trademarks of their respective owners.
ii
3rd May 01
GPRS-300-101
Issue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First aid in case of electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Human exposure to radio frequency energy (PCS1900 only) . . . . . . . . . . . . . . . . . . . . . . Beryllium health and safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola GSM manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GMR amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GMR amendment record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 2 4 5 6 7 9 12 14 15 16 19 20
Chapter 1 Introduction to GPRS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to GPRS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding information in this category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola GPRS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of GPRS customer support manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How does the coding system work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Order number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Classification number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sub category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribution of Motorola manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How do manual updates work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to order manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Descriptions of GPRS publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
11 11 11 13 13 14 14 14 15 15 15 16 17 17 18 18 18 19 19 19 19 19 110 110 111 111 111 111 111 111 112 112 112 112
3rd May 01
iii
GPRS-300-101
Other documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Third-party documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . References, documents, and authors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
113 113 113 113
Chapter 2 Introduction to Motorola GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit switched transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cost efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSN Complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS in a GSM system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serving nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table of GPRS features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standards compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customer support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Assistance Centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customer Network Resolution Centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
21 21 21 22 22 22 22 22 24 24 24 25 25 25 25 26 26 26 27 27 28 28 28 28 29 210 210 210 210 213 213 213 213
Chapter 3 GPRS functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN performance and capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
i
31 31 31 32 32 32 32 34 34 34
3rd May 01
GPRS-300-101
GGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN performance and capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CGF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HA Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster performance and capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G performance and capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Control Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional GPRS elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LIAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Billing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RADIUS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CNR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35 35 35 36 37 37 37 38 38 38 38 38 39 39 39 310 310 311 311 312 313 314 314 315 315 315 316 316 317 317 318 318 318 318 319 319 319 320 320 320 320 320 321 321 321
Chapter 4 GPRS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
41 41 41
3rd May 01
GPRS-300-101
GPRS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagram of GPRS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of GPRS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagram of GPRS protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmission and signalling planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of GPRS protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ga interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ga description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ga protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GTP Prime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L1/L2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ga signalling PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb signalling PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gi interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gi description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gi protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP and L1/L2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gn interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gn description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gn protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UDP, IP and L1/L2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gn signalling PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gp interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gp description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gp protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gp signalling PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gr interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gr description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gr protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gr signalling PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
42 42 42 43 44 44 44 44 46 47 47 47 48 48 48 49 49 49 410 410 410 412 413 414 414 414 415 415 415 416 417 418 418 419 420 420 420 421 422 422 422 423 423 424 424 424 426 426 426 426 426 428 428 429
3rd May 01
GPRS-300-101
Gc interface alternative (Gn/Gr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gn/Gr description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gn/Gr protocol stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
430 430 430 430
Chapter 5 Network access and structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN network structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN backbones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS network structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS centralized system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS backbone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transparent access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-transparent access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributed access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN domain names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Domain name structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN network management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN address pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static and dynamic IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal and external address assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Address Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
51 51 51 52 52 52 53 54 54 54 55 55 57 57 57 58 58 59 59 510 510 510 511 511 511 511 512 513 513
Chapter 6 Mobility and session management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of chapter content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . State transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . State timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attach procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detach procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purge procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
61 61 61 62 62 62 64 65 67 67 67 68 610
3rd May 01
vii
GPRS-300-101
Location management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location update description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-SGSN routeing area update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-SGSN routeing area update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Insert subscriber data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete subscriber data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic roaming management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Roaming attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HGGSN PDP context activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Roaming detach and purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transparent roaming RAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility management security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User identity confidentiality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Session management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet data protocol states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static and dynamic PDP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP context activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP context deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other mobility-related functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet routeing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encapsulation and tunnelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GRE tunnelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Relay function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V.42bis data compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User-selectable APN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quality of Service (QoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
611 611 611 612 612 613 614 614 614 614 615 615 616 617 618 619 620 620 620 620 621 621 621 622 623 623 625 625 625 626 626 627 627 627 628 628
Chapter 7 GPRS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Charging Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CGF description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDR generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Charging Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lawful Intercept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LI description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LIAN architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LIAN-to-GSN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LI performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LI management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LI security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii
i
71 71 71 72 72 73 73 77 710 710 710 711 712 712 712 712
3rd May 01
GPRS-300-101
Network management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event and alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load and database management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operator access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Password protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Domain name security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
713 713 713 714 714 715 715 716 716 717 717 717 717 718 718 718 718
Chapter 8 GPRS hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSN cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communications cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expansion cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet interior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN module components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Card functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN redundant power supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sun Netra t 1125 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sun Netra st D1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminal Concentrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection to CommHub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chassis modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supervisor Engine module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Route Switch Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10/100BASE-T switch module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
81 81 81 82 82 83 83 83 84 84 84 85 87 89 89 89 89 810 810 811 811 811 812 812 813 814 814 814 814 815 816 816
3rd May 01
ix
GPRS-300-101
OMC-G hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enterprise 3500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Edge 6300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware scaleability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Minimum GSN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum GSN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
817 817 817 818 819 819 819 820 820 820 820
Chapter 9 GPRS equipment specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSN cabinet specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sun Netra t 1125 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sun Netra st D1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . micro Annex x1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
91 91 91 92 93 94 95 95 95 95 96
Chapter 10 Software release features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software release 1.6.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software release 1.6.1.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
101 101 101 102 102 102 103 104 104 105 105 106 106 106 107 107 107 108 108
Chapter 11 Glossary of technical terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . .

Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x
i
111
3rd May 01
GPRS-300-101
A ......................................................................... B ......................................................................... C ......................................................................... D ......................................................................... E ......................................................................... F ......................................................................... G ......................................................................... H ......................................................................... I .......................................................................... K ......................................................................... L ......................................................................... M ......................................................................... N ......................................................................... O ......................................................................... P ......................................................................... Q ......................................................................... R ......................................................................... S ......................................................................... T ......................................................................... U ......................................................................... V ......................................................................... W ........................................................................ X, Y, Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112 115 118 1112 1115 1117 1119 1122 1123 1126 1127 1129 1132 1134 1135 1140 1141 1143 1147 1149 1150 1151 1152
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I1
3rd May 01
xi
GPRS-300-101
xii
3rd May 01
GPRS-300-101
Issue status of this manual
Issue status of this manual

Introduction
The following shows the issue status of this manual since it was first released.
Version information
The following lists the versions of this manual in order of manual issue: Manual issue O A B C Date of issue 15th Dec 99 14th Jul 00 1st Mar 01 3rd May 01 Remarks Original Issue GSN Software Release 1.6.1.1 A Issue GSN Software Release1.6.1.3 B Issue GSN Software Release 1.6.1.4.30 C Issue GSN Software Release 1.6.1.4.40
Resolution of Service Requests

The following Service Requests are now resolved in this manual: Service Request N/A GMR Number N/A Remarks
3rd May 01
General information
GPRS-300-101
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) manuals are intended to instruct and assist personnel in the operation, installation and maintenance of the Motorola GSM equipment and ancillary devices. It is recommended that all personnel engaged in such activities be properly trained by Motorola. 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

The manual contains an overview of the General Packet Radio Service (GPRS), as implemented by Motorola. The manual also contains a description of the Motorola document set, specifications for Motorola entities, a summary of Motorola software release features and a Glossary of technical terms and acronyms. This manual supports the following Motorola GPRS equipment: S S S S S Serving GPRS Support Node (SGSN). Gateway GPRS Support Node (GGSN). Integrated Support Server (ISS). Communications Hub (CommHub). Operations and Management Centre GPRS (OMC-G).
3rd May 01
GPRS-300-101
General information
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: CTRLc ALTf | 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.
3rd May 01
First aid in case of electric shock
GPRS-300-101
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.
3rd May 01
GPRS-300-101
Reporting safety issues
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. 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 Customer Network Resolution Centre +44 (0)1793 565444 (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 Customer Network Resolution Centre.
4.
3rd May 01
Warnings and cautions
GPRS-300-101
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.
3rd May 01
GPRS-300-101
General warnings
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.
3rd May 01
General warnings
GPRS-300-101
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.
3rd May 01
GPRS-300-101
Human exposure to radio frequency energy (PCS1900 only)

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.
3rd May 01
GPRS-300-101
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 6.567mW/cm 2
1.287mW/cm 2 1.313mW/cm 2 6.433mW/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.
10
3rd May 01
GPRS-300-101
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 + 4pr W Pin
2
1930 MHz +39.0 dBm (8 watts) 2.0 dB PCL = +39.02.0 = +37.0 dB (5watts) 16.4 dBi (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 + 4pW 43.65 5 + 1.16m 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.
3rd May 01
11
Beryllium health and safety precautions
GPRS-300-101

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 2-20 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.
12
3rd May 01
GPRS-300-101
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.
3rd May 01
13
General cautions
GPRS-300-101
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.
14
3rd May 01
GPRS-300-101
Devices sensitive to static
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.
3rd May 01
15
Motorola GSM manual set
GPRS-300-101

Introduction
The following manuals provide the information needed to operate, install and maintain the Motorola GSM and GSM Packet Radio Service (GPRS) equipment.
Generic GSM manuals

The following are the generic manuals in the GSM manual set, these manuals are release dependent: Classification number GSM-100-101 GSM-100-201 GSM-100-202 GSM-100-311 GSM-100-313 GSM-100-320 GSM-100-321 GSM-100-403 GSM-100-423 GSM-100-413 GSM-100-501 GSM-100-520 GSM-100-521 GSM-100-523 GSM-100-503 GSM-100-721 GSM-100-712 Name System Information: General . . . . . . . . . . . . . . . . . . . Operating Information: GSM System Operation . . . Operating Information: OMC-R System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Description: OMC-R in a GSM System . . Technical Description: OMC-R Database Schema . Technical Description: BSS Implementation . . . . . . . Technical Description: BSS Command Reference . Installation & Configuration: GSM System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: BSS Optimization . . . . Installation & Configuration: OMC-R Clean Install . . Maintenance Information: Alarm Handling at the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance Information: BSS Timers . . . . . . . . . . . Maintenance Information: Device State Transitions Maintenance Information: BSS Field Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance Information: GSM Statistics Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Release Notes: BSS/RXCDR . . . . . . . . . . Software Release Notes: OMC-R System . . . . . . . . Order number 68P02901W01 68P02901W14 68P02901W19 68P02901W31 68P02901W34 68P02901W36 68P02901W23 68P02901W17 68P02901W43 68P02901W47 68P02901W26 68P02901W58 68P02901W57 68P02901W51 68P02901W56 68P02901W72 68P02901W74
Related GSM manuals

The following are related Motorola GSM manuals: Classification number GSM-001-103 GSM-002-103 GSM-002-703 GSM-005-103 GSM-008-403 GSM-008-703 GSM-006-202 GSM-006-413 GSM-006-712
16
Name System Information: BSS Equipment Planning . . . . System Information: DataGen . . . . . . . . . . . . . . . . . . Software Release Notes: DataGen . . . . . . . . . . . . . . System Information: GSM Advance Operational Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: Network Health Analyst Software Release Notes: Network Health Analyst . Operating Information: OMC-R System Administration (OSI) . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: OSI Clean Install . . . . . Software Release Notes: OMC-R OSI System . . . .
Order number 68P02900W21 68P02900W22 68P02900W76 68P02900W25 68P02900W36 68P02900W77 68P02901W10 68P02901W39 68P02901W70
3rd May 01
GPRS-300-101
Generic GPRS manuals

The following are the generic manuals in the GPRS manual set, these manuals are release dependent: Classification number GPRS-300-101 GPRS-300-202 GPRS-300-222 GPRS-300-311 GPRS-300-313 GPRS-300-321 GPRS-300-423 GPRS-300-413 GPRS-300-501 GPRS-300-503 GPRS-300-722 GPRS-300-712 Name System Information: GPRS Overview . . . . . . . . . . . . Operating Information: OMC-G System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating Information: GSN System Administration Technical Description: OMC-G in a GPRS System . Technical Description: OMC-G Database Schema . Technical Description: GSN Command Reference . Installation & Configuration: GSN Clean Install . . . . Installation & Configuration: OMC-G Clean Install . Maintenance Information: Alarm Handling at the OMC-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance Information: GSN Statistics Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Release Notes: GSN System . . . . . . . . . . Software Release Notes: OMC-G System . . . . . . . . Order number 68P02903W01 68P02903W03 68P02903W37 68P02903W29 68P02903W46 68P02903W18 68P02903W47 68P02903W04 68P02903W19 68P02903W20 68P02903W76 68P02903W70
Related GPRS manuals

The following are related Motorola GPRS manuals: GPRS-001-103 GPRS-005-103 System Information: GPRS Equipment Planning . . 68P02903W02 System Information: GSN Advance Operational Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W38
3rd May 01
17
GPRS-300-101
BSS service manuals

The following are the Motorola Base Station service manuals, 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: Classification number GSM-100-020 GSM-100-030 GSM-105-020 GSM-106-020 GSM-201-020 GSM-202-020 GSM-203-020 GSM-206-020 GSM-205-020 GSM-204-020 GSM-207-020 GSM-208-020 GSM-101-SERIES GSM-103-SERIES GSM-102-SERIES GSM-104-SERIES GSM-200-SERIES Name Service Manual: BTS . . . . . . . . . . . . . . . . . . . . . . . . . . Service Manual: BSC/RXCDR . . . . . . . . . . . . . . . . . . Service Manual: M-Cell2 . . . . . . . . . . . . . . . . . . . . . . . Service Manual: M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . Service Manual: M-Cellcity and M-Cellcity+ . . . . . . . Service Manual: M-Cellaccess . . . . . . . . . . . . . . . . . . Service Manual: Horizonmicro . . . . . . . . . . . . . . . . . . Service Manual: Horizoncompact . . . . . . . . . . . . . . . Service Manual: Horizonmacro Indoor . . . . . . . . . . . Service Manual: Horizonmacro Outdoor . . . . . . . . . . Service Manual: Horizonoffice . . . . . . . . . . . . . . . . . . Service Manual: Horizonmacro 12 Carrier Outdoor ExCell4 Documentation Set . . . . . . . . . . . . . . . . . . . . ExCell6 Documentation Set . . . . . . . . . . . . . . . . . . . . TopCell Documentation Set (GSM900) . . . . . . . . . . . TopCell Documentation Set (DCS1800) . . . . . . . . . . M-Cellmicro Documentation Set . . . . . . . . . . . . . . . . . Order number 68P02901W37 68P02901W38 68P02901W75 68P02901W85 68P02901W95 68P02901W65 68P02902W36 68P02902W15 68P02902W06 68P02902W12 68P02902W46 68P02902W66 68P02900W50 68P02900W70 68P02901W80 68P02902W80 68P02901W90
GPRS service manuals

The following are the Motorola GPRS service manuals, these manuals include the Packet Control Unit (PCU) service manual which becomes part of the BSS for GPRS: Classification number GPRS-301-020 GPRS-302-020 Name Order number
Service Manual:GPRS Support Nodes (GSN) . . . . . 68P02903W05 Service Manual: Packet Control Unit (PCU) . . . . . . . 68P02903W10
Classification number
The classification number is used to identify the type and level of a manual. For example, manuals with the classification number GSM-100-2xx contain operating information.
Order number
The Motorola 68P order (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 order (catalogue) number. Remember, specify the manual issue required by quoting the correct suffix letter.
18
3rd May 01
GPRS-300-101
GMR amendment
GMR amendment
Introduction to GMRs
Changes to a manual that occur after the printing date are incorporated into the manual using General Manual Revisions (GMRs). GMRs are issued to correct Motorola manuals as and when required. A GMR has the same identity as the target manual. Each GMR is identified by a number in a sequence that starts at 01 for each manual at each issue. GMRs are issued in the form of loose leaf pages, with a pink instruction sheet on the front.
GMR procedure
When a GMR is received, check on the GMR amendment record page of this manual that previous GMRs, if any, have been incorporated. If not, contact your administrator or Motorola Local Office to obtain the missing GMRs. Remove and replace pages in this manual, as detailed on the GMR pink instruction sheet.
3rd May 01
19
GMR amendment record
GPRS-300-101
GMR amendment record

Instructions
When a GMR is inserted in this manual, the amendment record below must be filled in to record the insertion. Retain the pink instruction sheet that accompanies each GMR and insert it in a suitable place in this manual for future reference.
Amendment record
Record the insertion of GMRs in this manual in the following table:
GMR number 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Incorporated by (signature)
Date
20
3rd May 01
Chapter 1
Introduction to GPRS documentation
3rd May 01
GPRS-300-101
ii
3rd May 01
GPRS-300-101
Chapter 1 Introduction to GPRS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to GPRS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding information in this category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola GPRS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of GPRS customer support manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How does the coding system work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Order number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Classification number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sub category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribution of Motorola manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How do manual updates work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to order manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Descriptions of GPRS publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Third-party documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . References, documents, and authors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
11 11 11 13 13 14 14 14 15 15 15 16 17 17 18 18 18 19 19 19 19 19 110 110 111 111 111 111 111 112 112 112 112 112 113 113 113 113
3rd May 01
iii
GPRS-300-101
iv
3rd May 01
GPRS-300-101

About this manual
This manual supports Motorolas GPRS equipment. It contains an overview of the GPRS, as implemented by Motorola, and includes: S S S S S S S S S S S An introduction to Motorola GPRS documentation (this chapter). Introduction to Motorola GPRS. GPRS functional description. GPRS interfaces. GPRS network access and structure. Mobility and session management. Services provided by GPRS. GPRS hardware. GPRS equipment specifications. A summary of Motorola GPRS software release features. A glossary of technical terms and acronyms.
The information is intended for use by all GPRS operations and maintenance staff.
Finding information in this category

This category GPRS-300-101 covers the Motorola GPRS equipment and is arranged in the following chapters.
Chapter 1
Introduction to GPRS Documentation
This chapter contains listings of the manuals supplied to customers. It also includes a description of the Motorola documentation system and a brief summary of the contents of each document. Refer to Motorola GPRS documentation. In addition, other documents available to Motorola customers are listed. Refer to Other documents.
Chapter 2
Introduction to Motorola GPRS
This chapter provides a general introduction to GPRS, its role in a Global System for Mobile Communication (GSM) network, and Motorolas implementation of the GPRS standard.
Chapter 3
GPRS Functional Description
This chapter describes the network elements that make up the Motorola GPRS.
Chapter 4
GPRS Interfaces
This chapter lists the interfaces and protocols that allow GPRS network entities to communicate with each other and external systems.
3rd May 01
11
GPRS-300-101
Chapter 5
GPRS Network Access and Structure
This chapter describes the GPRS network structure and user access to the network.
Chapter 6
Mobility and Session Management
This chapter describes the Mobility Management and Session Management functions that enable a GPRS system to track the current location of a Mobile Station (MS) and determine the network node to which a message is to be forwarded.
Chapter 7
GPRS Services
This chapter describes GPRS services not related to mobility or session management.
Chapter 8
GPRS Hardware
This chapter describes the scaleability and hardware components of the GPRS network elements.
Chapter 9
GPRS Equipment Specifications
This chapter lists the environmental and physical specifications for the GPRS hardware components.
Chapter 10
Software Release Features
This chapter summarizes the main features of the Motorola GPRS software releases.
Chapter 11
Glossary of Technical Terms and Abbreviations
This chapter lists the Motorola GPRS terms and acronyms used throughout the manual set.
12
3rd May 01
GPRS-300-101
Motorola GPRS documentation
Motorola GPRS documentation

Overview of GPRS customer support manuals
This is a guide to the Motorola GPRS customer support manuals. It describes how the manuals are referenced, what manuals are available and how to obtain them. The Motorola GPRS equipment is supported by a range of documentation that provides the required information for a customer to manage, operate and maintain the GPRS system, as implemented by Motorola. This documentation is provided in the form of task-oriented system manuals and hardware product manuals. Further details of the Motorola GPRS customer support manuals are provided in the following sections: S S S S Documentation coding. Distribution of Motorola manuals. Descriptions of GPRS publications. Other documents.
3rd May 01
13
Documentation coding
GPRS-300-101
How does the coding system work?
All manuals have two codes associated with them, an Order number and a Classification number: S S The 68P... catalogue number is a unique identifier, which is used for ordering purposes. The classification number (for example GPRS-300-202) identifies the type of manual, the overall manual set to which it belongs, the type of information it contains, and the user it is aimed at.
Order number
The Order number is an eleven character Motorola code, which starts with 68P... for technical manuals. It is the part number that is used when ordering Motorola hardcopy manuals. An additional suffix letter at the end of the order number to indicate the issue status of the manual. Note that this starts at O for original then A, B, C and so on. For software dependent manuals, the issue suffix letter corresponds to each major software release. Other manuals, such as hardware service manuals, are re-issued as and when required and are not linked to a particular software release. Some other manuals contain cumulative release information that is backward compatible, or cover more than one release. Therefore, these manuals do not conform to the above suffix letter criteria. A typical issue history for a software dependent manual with the identifying Order number 68P02900W15 (an example only) is shown in the following table: Order Number 68P02900W15-O 68P02900W15-A 68P02900W15-B 68P02900W15-C 68P02900W15-D 68P02900W15-E 68P02900W15-F Date of issue 3rd Oct 94 30th Dec 94 1st Sep 95 31st May 96 17th Dec 96 29th Aug 97 27th Apr 98 Remarks Original issue Software Release 1.2.2.x Issue A Software Release 1.2.3.x Issue B Software Release 1.3.0.x Issue C Software Release 1.4.0.x Issue D Software Release 1.4.1.x Issue C Software Release GSR2 (1.5.0.x) Issue D Software Release GSR3 (1.5.1.x)
Example
The Order number (for this example 68P02900W15-F) can be divided into three parts, as follows: 1. 2. The first three characters (68P) identifies the item as a technical manual. The second eight characters (02900W15) are allocated from a sequential list of numbers, which are in effect unique identity numbers. However, these may be allocated in blocks for specific manual sets. The final letter is the issue suffix as described above. System Information: GPRS Overview 68P02903W01-C
3rd May 01
3.
14
GPRS-300-101
Classification number
The Motorola GPRS customer support manuals provide technical information, in a combination of different categories and levels, for the various users of the Motorola GPRS equipment. The Classification number consists of three or more letters and two groups of three numbers (for example GPRS-300-202). Sometimes the number ends with an additional letter, this indicates that the manual is one of two or more individually identified volumes. The example below illustrates the elements of the numbering system and uses all the possible components a Classification number can have. GPRS - 300 - 202A System Variant Category Sub category Information Level Volume Figure 1-1 Example breakdown of GPRS publication number In the example, the components of the publication number have the meanings detailed below: Component System Variant Category Sub category Information level Volume Description GPRS 300 = Generic GPRS manual set 2 = Operating information 0 = System 2 = OMC system administration A = The first of two or more alphabetically identified volumes
Details of the various components of the Classification number are given in the sections that follow.
System
GSM900, DCS1800 and PCS1900 are all implementations of the GSM standard, operating on different frequency bands. They are all identified as part of the global GSM system, as indicated by the letters GSM.
Variant
The variant is indicated by the middle three numbers (GPRS-300-202) of the Classification number code, as shown below. Some variants, such as 003, 004, and 006 are not listed as they are reserved for internal Motorola use.
3rd May 01
15
GPRS-300-101
001: Planning
Guides to designing, specifying and planning a BSS network.
002: DataGen
Guide to the optional tool for creating databases for the BSS.
Category
The first digit of the last group of the Classification number code (GPRS-300-202) indicates the category of information, as follows: Category 1 2 3 4 5 6 7 Description System Information Operating Information Technical Description Installation and Configuration Maintenance Information Parts Information Software Release Notes
Category 1: What it is.

Provides general information on the subject system or subsystem.
Category 2: How to use it.

Contains information required by operational staff using the Motorola GPRS equipment. Includes operating procedures, functional tests and remedial action within the capability of the operational staff.
Category 3: How it works.

Contains the technical description, including principles of design, operation, function and interrelation of the various parts of the equipment. Physical construction is also included where necessary.
Category 4: How to prepare it for use.

Contains installation and commissioning information, and configuration details, to enable the Motorola GPRS equipment to be installed, brought into use and optimized.
Category 5: How to maintain it.

Provides maintenance information to enable the user to troubleshoot, repair and maintain the Motorola GPRS equipment.
Category 6: What it consists of.

Provides detailed parts information.
Category 7: How to update it.

Contains details of new software releases.
16
3rd May 01
GPRS-300-101
Sub category
The second digit of the last group of the Classification number code (GPRS-300-202) indicates the sub category. There are a number of sub categories which define the manual subject, as follows: Sub category 0 1 2 3 Description System Operations and Maintenance Centre (OMC) Base Station System (BSS) or Base Transceiver Station (BTS) when separate manuals produced Base Station Controller (BSC)
Information level
The third digit of the last group of the Classification number code (GPRS-300-202) indicates the level of information. The information contained in each category is arranged into three levels, as shown, so that users are only supplied with the information at the level they require. Information level 1 2 3 Description System operation OMC system administration Engineering staff (Planning and field)
3rd May 01
17
Distribution of Motorola manuals
GPRS-300-101
Distribution of Motorola manuals

How do manual updates work?
Up-issuing a manual
For each new major software release, certain release dependent manuals are revised and re-issued. When this happens, the issue suffix letter of the Order number increments by one letter of the alphabet. Other manuals, such as hardware service manuals, are up-issued as and when required and do not follow the above suffix letter rules, but are sequentially lettered from O for Original, followed by A, B and so on.
General Manual Revisions (GMRs)

GMRs are produced to update and correct manuals when required. A GMR may be produced for release dependent manuals when a software point release is issued. For all manuals, GMRs are produced to incorporate minor technical changes and to correct any errors. An updated version of the documentation CD-ROM is produced when the GMRs are incorporated in the manuals. Motorola Order Fulfilment maintain a database of customers. Any customer who has ordered manuals for a particular release will be supplied automatically with GMRs, as and when they are produced. Similarly, any customer who has ordered a documentation CD-ROM for a particular software load will be supplied automatically with the GMR version of that CD-ROM. Where a documentation CD-ROM is supplied free of charge, as part of the software load package, an updated CD-ROM will be supplied, when available, by Motorola Controlled Roll Out (CRO) Group.
How to order manuals

Motorola manuals for customers must be ordered through the Motorola Local Office or Representative. Manuals are ordered using the Order number. Remember to specify the manual issue required by quoting the correct suffix letter, which relates to the software load supplied.
18
3rd May 01
GPRS-300-101
Descriptions of GPRS publications

NOTE These descriptions are generic and not specific to any software release version.
68P02903W01
System Information: GPRS Overview (GPRS-300-101)
This manual provides a high-level view of Motorolas implementation of GPRS. It includes hardware and functional descriptions of the elements in a GPRS system, and explains how these elements work together to provide packet data services to subscribers in a GSM network. The GPRS Overview manual also includes a description of the Motorola document set, a summary of Motorola software release features, and a glossary. This glossary is the reference for all technical terms and acronyms in the GPRS customer documents described in this section.
68P02903W02
System Information: GPRS Equipment Planning (GPRS-001-103)
The manual describes how to select Motorola GPRS Support Node (GSN) equipment for GPRS systems. It includes minimum and maximum configuration descriptions, and a planning example. In addition, the manual provides a detailed description of the Gb and Gr interfaces.
68P02903W03
Operating Information: OMC-G System Administration (GPRS-300-202)
The manual describes the System Management features of the OMC-G for both UNIX and NT platforms. In addition, it provides instructions for system startup and shutdown, database management, and Network Information Services. Finally, the manual includes details on disaster recovery and troubleshooting OMC-G UNIX and Windows NT problems.
68P02903W04
Installation & Configuration: OMC-G Clean Install (GPRS-300-413)
The manual provides the staging and on-site procedures for the installation and configuration of the OMC-G. The procedures consist of the preparation of the hardware, and the loading and configuration of the system software.
3rd May 01
19
GPRS-300-101
68P02903W05
Service Manual: GPRS Support Node (GSN) (GPRS-301-020)
The manual contains hardware service information for the GSN. The manual is intended for customers who install, maintain, troubleshoot, and manage the GSN Complex. The manual includes the following documentation: S S 68P02903W06 Technical Description Describes GSN Complex hardware and cabinets, including specifications. 68P02903W07 Installation and Configuration Gives instructions on how to install and configure the GSN shipment of hardware, including preparing the site, installing the hardware modules in the rack, commissioning Motorola and third-party hardware, and verifying the connectivity of the installed GSN Complex. Also, instructions for decommissioning the GSN Complex are given. S 68P02903W08 Maintenance Information Gives procedures for maintaining and troubleshooting the GSN Complex cabinets and modules. Also, this manual includes Field Replacement Unit (FRU) procedures for GSN Complex components, including: S Communications Hub (CommHub). Integrated Support Server (ISS) Cluster. Serving GPRS Support Node (SGSN). Gateway GPRS Support Node (GGSN).
68P02903W09 Parts Information. This manual lists available GSN upgrades, spares, and ordering information, including: Factory-fitted options. Suggested spares. FRUs. Additional replacement parts.
68P02903W10
Service Manual: Packet Control Unit (PCU) (GPRS-302-020)
The manual contains hardware service information for the GPRS PCU, including: S S 68P02903W11 Technical Description. Describes PCU hardware and cabinets, including specifications. 68P02903W12 Installation and Configuration. Gives instructions on how to install and configure the PCU shipment of hardware, including preparing the site, installing the PCU in the cabinet, connecting cables and power. Also, instructions for decommissioning the PCU cabinet are given. S 68P02903W13 Maintenance Information. Gives procedures for maintaining and troubleshooting the PCU cabinets and modules. Also, this manual includes FRU procedures for PCU chassis components and connections. S 68P02903W14 Parts Information. This manual lists available PCU parts, FRUs, and ordering information.
110
3rd May 01
GPRS-300-101
68P02903W18
Technical Description: GSN Command Reference (GPRS-300-321)
This manual describes the commands and parameters used to operate and configure the GSN Complex, including: S S Entering GGSN, Shelf Manager, CommHub, and ISS Complex commands through a command line interface (CLI) via a telnet session. Viewing and configuring SGSN, GGSN, Shelf Manager, CommHub, and ISS Cluster parameters through the OMC-G GUI.
68P02903W19
Maintenance Information: GSN Alarm Handling at the OMC-G (GPRS-300-501)
This manual describes the alarms raised by the GSN in response to monitored network and system events. The initial chapter provides general information on the structure of this manual. The remaining chapters provide alarm information, with each chapter covering the alarms for a specific element of the GSN.
68P02903W20
Maintenance Information: GSN Statistics Application (GPRS-300-503)
This manual contains information on the statistics related to the GSN in the Motorola GPRS network. It provides a detailed description of all the statistics and their uses. Procedures for monitoring performance statistics at the OMC-G are included.
68P02903W29
Technical Description: OMC-G in a GPRS System (GPRS-300-311)
This manual gives an overview of GPRS and its role in the operation and maintenance of the GPRS system. The manual describes the OMC-G hardware, configuration, processes, applications, and interface. The management features of the OMC-G are described, including load, configuration, fault and performance management, and Gb link connectivity.
68P02903W37
Operating Information: GSN System Administration (GPRS-300-222)
The focus of this manual is on the system administration of the ISS Cluster in the GSN Complex. In addition, some system administration information is also provided for monitoring and maintaining the GGSN, CommHub and Shelf Manager.
68P02903W38
System Information: GSN Advance Operational Impact (GPRS-005-103)
This manual provides customers with advanced information on planned Motorola GPRS features, including: S S Advance information on a per feature basis for major Motorola releases. A library of feature specific information for the GPRS product.
The information is provided to help customers in planning any staff impact due to the contents of the release, and in the preparation of test plans in advance of product delivery.
3rd May 01
111
GPRS-300-101
68P02903W46
Technical Description: OMC-G Database Schema (GPRS-300-313)
This manual describes the OMC-G Performance Management database schema. The database provides storage and retrieval facilities for managing the processed raw statistics from the SGSN. The manual also includes a brief description of the alarm database view which enables users to focus on specific data from the alarm event log.
68P02903W47
Installation & Configuration: GSN Clean Install (GPRS-300-423)
This manual describes how to perform a clean software installation of a GSN Complex. It does not describe hardware installation procedures. Some procedures permit, but are not limited to, the use of the OMC-G.
68P02903W70
Software Release Notes: GPRS OMC-G System (GPRS-300-712)
This manual contains software release notes and upgrade information for the OMC-G.
68P02903W76
Software Release Notes: GSN System (GPRS-300-722)
This manual contains software release notes and upgrade information for the GSN.
112
3rd May 01
GPRS-300-101
Other documents
Other documents
Introduction
The manuals listed in the following sections are supplied to customers where appropriate.
Third-party documents
Third-party documents supplied include: S S S S S CISCO. Sun. Lynx OS. Force. Dell.
References, documents, and authors

Table 1-1 relates references to documents and authors. Although few of the listed documents are referred to in this overview, many of the listed documents may be of general background interest. Table 1-1 References, documents, and authors [Ref] 1 Document title/document id/version/release date GSM 01.33: Digital cellular telecommunications system (Phase 2+); Lawful Interception requirements for GSM, Version 7.0.0 (formerly known as GSM 10.20). GSM 01.61: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS) ciphering algorithm requirements, Version 6.0.0. GSM 2.33: Digital cellular telecommunications system (Phase 2+); Lawful Interception stage 1, Version 7.0.0. GSM 02.60: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service description; Stage 1, Version 6.2.0. GSM 03.03: Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification, Version 6.4.0. GSM 03.07: Digital cellular telecommunications system; Restoration procedures, Version 5.0.0. GSM 03.20 : Digital cellular telecommunications system (Phase2+); Security related network functions , Version 6.1.0. Author(s) ETSI
ETSI
ETSI
ETSI
ETSI
6 7
ETSI ETSI
3rd May 01
113
Other documents
GPRS-300-101
[Ref] 8
Document title/document id/version/release date GSM 03.22 (ETS 300 930): Digital cellular telecommunications system (Phase 2+); Functions related to Mobile Station (MS) in idle mode and group receive mode. GSM 03.33 (ETS 300 927): Digital cellular telecommunications system (Phase 2+); Lawful Interception Stage 2, Version 7.1.0. GSM 03.40 (ETS 300 930): Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS); Point-to-Point (PP). GSM 03.60: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service Description; Stage 2, Version 6.7.0. GSM 03.64: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Overall description of the GPRS radio interface; Stage 2, Version 6.1.0. GSM 04.04: Digital cellular telecommunications system (Phase 2+); Layer 1; General requirements, Version 5.1.0. GSM 04.07 (ETS 300 939): Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects, Version 6.4.0. GSM 04.08: Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification, Version 6.8.0. GSM 04.60: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Mobile Station (MS) Base Station Sub-System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol, Version 6.2.0.
Author(s) ETSI
10
ETSI
11
ETSI
12
ETSI
13
ETSI
14
ETSI
15
ETSI
16
ETSI
17
GSM 04.64: Digital cellular telecommunications ETSI system (Phase 2+); General Packet Radio Service (GPRS); Mobile Station-Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) Layer Specification, Version 6.7.0. GSM 04.65: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Mobile Station (MS) Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP), Version 6.7.0. ETSI
18
19
GSM 05.02: Digital cellular telecommunications ETSI system (Phase 2+); Multiplexing and multiple access on the radio path, Version 6.2.0. GSM 05.03: Digital cellular telecommunications system (Phase 2+); Channel Coding, Version 6.0.0. ETSI
20
114
3rd May 01
GPRS-300-101
Other documents
[Ref] 21
Document title/document id/version/release date GSM 05.05: Digital cellular telecommunications system (Phase 2+); Radio transmission and reception, Version 5.2.0. GSM 05.08 Digital cellular telecommunications system (Phase 2+); Radio Sub-system link control, Version 5.1.0. GSM 05.10 Digital cellular telecommunications system (Phase 2+); Radio subsystem synchronization, Version 5.10. GSM 07.60 Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Mobile Station (MS) supporting GPRS, Version 6.2.0. GSM 08.14: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Base Station System (BSS) Serving GPRS Support Node (SGSN) interface; Gb interface layer 1, Version 6.0.0. GSM 08.16: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Base Station System (BSS) Serving GPRS Support Node (SGSN) interface; Network Services, Version 6.3.0. GSM 08.18: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Base Station System (BSS) Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP), Version 6.7.0. GSM 08.60 (ETS 300 737): Digital cellular telecommunications system (Phase 2+); In-band control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels. GSM 09.02: Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification, Version 6.4.0. GSM 09.16: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) Visitors Location Register (VLR); Gs interface network service specification, Version 6.0.0. GSM 09.18: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) Visitors Location Register (VLR); Gs interface layer 3 specification, Version 6.2.0.
Author(s) ETSI
22
ETSI
23
ETSI
24
ETSI
25
ETSI
26
ETSI
27
ETSI
28
ETSI
29
ETSI
30
ETSI
31
ETSI
32
GSM 09.60: Digital cellular telecommunications ETSI system (Phase 2+); General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface, Version 6.7.0.
3rd May 01
115
Other documents
GPRS-300-101
[Ref] 33
Document title/document id/version/release date GSM 09.61: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Interworking between the Public Land Mobile Network (PLMN) supporting GPRS and Packet Data Networks (PDN), Version 6.3.0. GSM 10.18: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); O & M in GPRS, Version 0.2.0. GSM 10.60: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Project scheduling and open issues, Version 5.3.0.
Author(s) ETSI
34
ETSI
35
ETSI
36
GSM 12.00: Digital cellular telecommunications ETSI system (Phase 2); Network Management (NM) Part 1: Object and structure of Network Management; prETS 300 612-1; Final Draft; August 1996. GSM 12.06: Digital cellular telecommunications system (Phase 2); SGSN Network configuration management; prETS 300 617; Final Draft; June 1996. GSM 12.08: Digital cellular telecommunications system (Phase 2); Subscriber and equipment trace, Version 5.1.0. GSM 12.15: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); GPRS Charging, Version 7.1.0. I.130: Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN. E.164: The international public telecommunications numbering plan. Q.65: The unified functional methodology for the characterization of services and network capabilities. Q.922: ISDN data link layer specification for frame mode bearer services. Q.933: Integrated services digital network (ISDN) digital subscriber signaling system No. 1 (DSS 1) Signalling specifications for frame mode switched and permanent virtual connection control and status monitoring. V.42 bis: Data compression procedures for data circuit-terminating equipment (DCE) using error correcting procedures. X.3: Packet assembly/disassembly facility (PAD) in a public data network. ETSI
37
38
ETSI
39
ETSI
40
ITU-T
41 42
ITU-T ITU-T
43 44
ITU-T ITU-T
45
ITU-T
46
ITU-T
116
3rd May 01
GPRS-300-101
Other documents
[Ref] 47
Document title/document id/version/release date
Author(s)
X.25: Interface between Data Terminal Equipment ITU-T (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit. X.121: International numbering plan for public data networks. X.137: Availability performance values for public data networks when providing international packet switched services. X.733: Information technology Open Systems Interconnection Systems Management; Alarm reporting function. X.734: Information technology Open Systems Interconnection Systems Management: Event report management function. ETS 300 019-1-2: Equipment Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment Part 1-2: Classification of environmental conditions Transportation. ETS 300 019-1-3: Equipment Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment Part 1-3: Classification of environmental conditions Stationary use at weather protected locations. ETS 300 287: Integrated Services Digital Network (ISDN), CCITT Signalling System 7 Transaction Capabilities Application Part (TCAP) Version 2. ETS 300 753 019-1-3: Equipment Engineering (EE); Environmental. RFC 768: User Datagram Protocol. RFC 791: Internet Protocol. RFC 792: Internet Control Message Protocol. RFC 793: Transmission Control Protocol. RFC 854: TELNET Protocol Specification. RFC 1034: Domain Names Concepts and Facilities. RFC 1035: Domain Names Implementation and Specifications. RFC 1144: Compressing TCP/IP Headers for Low-Speed Serial Links. RFC 1305: Network Time Protocol (Version 3) Specification, Implementation and Analysis. ITU-T ITU-T
48 49
50
ITU-T
51
ITU-T
52
ETSI
53
ETSI
54
ETSI
55 56 57 58 59 60 61 62 63 64 65
ETSI IETF IETF IETF IETF IETF IETF IETF IETF IETF
RFC 1155: Structure and Identification of IETF Management Information for TCP/IP-based Internets.
3rd May 01
117
Other documents
GPRS-300-101
[Ref] 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80
Document title/document id/version/release date RFC 1157: A Simple Network Management Protocol (SNMP). RFC 1825: Security Architecture for the Internet Protocol. RFC 1826: IP Authentication Header. RFC 1827: IP Encapsulating Security Payload (ESP). RFC 1212: Concise MIB Definitions. RFC 1215: A Convention for Defining Traps for use with the SNMP. RFC 2178: OSPF Version 2. RFC 2200: Internet Official Protocol Standards. G.703, Physical/electrical characteristics of hierarchical digital interfaces.
Author(s) IETF
RFC 1631: The IP Network Address Translator (NAT). IETF IETF IETF IETF IETF IETF IETF IETF ITU-T
G.704, Synchronous frame structures used at 1544, ITU-T 6312, 2048, 8448 and 44736 kbit/s hierarchical levels. Q751.1, Network Element Management Information Model For the Message Transfer Part. Q752, Monitoring and Measurements for Signalling System 7 Networks. IREG 33, Permanent Reference Document: GPRS Roaming Guidelines. Version 3.0.0. IREG 34, Permanent Reference Document: Inter-PLMN Backbone Guidelines Digital. Version 0.11. IREG 35, Permanent Reference Document: End-to-End Functional Capability Specification for Inter-PLMN GPRS Roaming. ITU-T ITU-T GSM Association GSM Association
81
GSM Association
118
3rd May 01
Chapter 2
Introduction to Motorola GPRS
3rd May 01
GPRS-300-101
ii
3rd May 01
GPRS-300-101
Chapter 2 Introduction to Motorola GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit switched transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cost efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSN Complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS in a GSM system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serving nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table of GPRS features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standards compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customer support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Assistance Centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customer Network Resolution Centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
21 21 21 22 22 22 22 22 24 24 24 25 25 25 25 26 26 26 27 27 28 28 28 28 29 210 210 210 210 213 213 213 213
3rd May 01
iii
GPRS-300-101
iv
3rd May 01
GPRS-300-101
Chapter overview
Chapter overview
What is in this chapter
This chapter provides a general introduction to General Packet Radio Service (GPRS), its role in a Global System for Mobile Communication (GSM) network, and Motorolas implementation of the GPRS standard.
How this chapter is structured

The chapter is divided into the following sections: S S S S S S Overview of GSM. Overview of GPRS. GPRS infrastructure. GPRS in a GSM system. Table of GPRS features. Customer support.
3rd May 01
21
Overview of GSM
GPRS-300-101
Overview of GSM
Introduction
GSM is a digital cellular radio network that operates in over 200 countries world-wide providing almost complete coverage of Western Europe, the Americas and Asia. This section gives a brief overview of GSM to provide background for the remainder of this guide which describes how GPRS provides packet switching within GSM.
GSM features
Telephony is the basic service supported by GSM, where speech is encoded and transmitted as a digital stream. GSM has been designed for both data and voice transmissions. A variety of data services, including High Speed Circuit Switched Data (HSCSD), enable GSM users to send and receive data at rates up to 9600 bps. A modem is not required between a user and a GSM network, since GSM is a digital network. However, an audio modem is required inside the GSM network to interoperate with Plain Old Telephone Service (POTS). A unique GSM feature not found in older analog systems is the Short Message Service (SMS); a bi-directional service for short alphanumeric (up to 160 bytes) messages. These messages are transported in a store-and-forward fashion. For example, with a point-to-point SMS, a data message can be sent to another subscriber and a receipt acknowledgement returned to the sender. SMS can also be used in cell-broadcast mode to send messages, such as traffic updates or news updates, and can also be stored in a SIM card for later retrieval. Additional data services include Group 3 facsimile (ITU-T recommendation T.30), supported by use of an appropriate fax adapter. Supplementary services built upon teleservices or bearer services to meet GSM Phase 1 specifications, include several forms of call forwarding and call barring of outgoing or incoming calls. Other supplementary services such as caller identification, call waiting and multi-party conversations services are defined within the GSM Phase 2 specifications. For detailed information about GSM, see the manual, System Information: General (GSM-100-101).
Circuit switched transmission

GSM is primarily a circuit switched system. Circuit switching is the use of a dedicated circuit between a user and an end system. This circuit is reserved for the length of time the user requires communication with the end system. During this time, the bandwidth allocated for that circuit is dedicated or continuously occupied and cannot be accessed by other users. This bi-directional traffic channel is therefore chargeable to the user for the duration of the call, whether or not traffic is actually being transmitted. For this reason, circuit switched data is more suitable for applications such as voice and video which require a fixed, short delay.
GSM infrastructure
A GSM network includes the following subsystems: S S S S
22
Base Station Subsystem (BSS). Network Subsystem (NSS). Location registers. Operations and Maintenance Centre-Radio (OMC-R). System Information: GPRS Overview 68P02903W01-C
3rd May 01
GPRS-300-101
Overview of GSM
BSS
The Base Station Subsystem (BSS) controls the radio link to the Mobile Station (MS). The BSS consists of the Base Transceiver Station (BTS) and the Base Station Controller (BSC). The BTS contains radio transceivers that define a cell and handle radio-link protocols with the MS. The BSC, which connects the MS to the MSC, manages radio-channel setup, frequency hopping, and handovers for one or more BTSs.
NSS
The Network Subsystem (NSS) provides call routeing and roaming capabilities for a single PLMN in GSM. The main elements of the NSS are the Mobile Switching Centre (MSC) and the Visitor Location Register (VLR). The MSC provides the connection to fixed networks and the functions necessary to manage a mobile subscriber. The VLR contains information required for call control and providing services for each mobile currently located in its geographical area.
Location registers
The location registers manage subscriber data and keep track of the location of an MS as it roams around the network. The location registers are the Home Location Register (HLR), the Equipment Identity Register (EIR), and the Authentication Centre (AuC). The HLR contains administrative information for each subscriber registered in a corresponding GSM network, including the current location of the mobile. The EIR is a security register with a database containing a list of all valid mobile equipment on the network, and the current location of each mobile station. The AuC is a subscriber authentication register with a protected database that contains a copy of the secret key stored in each subscriber SIM card. The key is used for authentication and encryption over the radio channel.
Operations and Maintenance Centre-Radio (OMC-R)

The OMC-R provides network operators with the capability to manage and monitor the radio aspects of both a GSM and GPRS network.
3rd May 01
23
Overview of GPRS
GPRS-300-101
Overview of GPRS
Introduction
GPRS is a new standard that provides packet switching within a GSM network. This section provides a brief description of the purpose and benefits of GPRS.
GPRS standard
GSM has been developed as a cellular telephony system supporting circuit-switched data transfer. However, transmitting some types of data using circuit switching can be slow and costly due to excessive bandwidth requirements for a connection. As a result, the European Telecommunications Standards Institute (ETSI) developed the GPRS standard for transmitting packet switched data over GSM networks. GPRS allows MSs to send and receive data in end-to-end packet transfer mode while still being able to use other circuit switched GSM services. Strict separation between the radio sub-system and network sub-system is maintained, allowing the network sub-system to be reused with other radio access technologies. Figure 2-1 shows the GPRS logical architecture according to the GSM 03.60 standard.
SMS-GMSC SMS-IWMSC E
Signalling interfaces Signalling and data transfer interfaces
SMS-C
MSC/VLR
HLR
Gd A Gs Gr Gc
TE
MT
Um
BSS
Gb
SGSN
Gn
GGSN
Gi
PDN
TE
Gn SGSN Gp
Gf EIR
GGSN Other PLMN
Figure 2-1 GPRS logical architecture

24
3rd May 01
GPRS-300-101
Overview of GPRS
Packet switching
GPRS supports packet switching within GSM. Unlike circuit switching, packet switching does not require a dedicated channel. Instead, the computer connected to a mobile station sends and receives bursts, or packets, of data through the network along communication lines shared with other channels. The data is sent in the form of discrete packets, each with a header containing source and destination routeing information. In this way, packets from many different transmissions may be multiplexed over the same circuit. The paths taken by successive packets may not be the same. However, the routeing information contained in the header of each packet ensures that the packets reach their destination where they are reassembled into the correct sequence. This is similar to a conventional postal system. A user packages and posts a letter, which enters the mail system, is sorted from other letters, and then delivered to its final destination. In this way, the transfer of the letter through the network uses the same bandwidth shared by all users.
IP capability
The implementation of GPRS brings Internet Protocol (IP) capability to the GSM network, enabling connection to a wide range of public and private data networks using industry standard data protocols such as Transmission Control Protocol/Internet Protocol (TCP/IP). The Internet relies exclusively on packet switching.
Types of data
The GPRS system is designed to support intermittent and bursty data transfers as well as transmission of larger volumes of data. When sending packet switched data, a radio channel is occupied only for the duration of the data transmission instead of continuously over a permanent connection, as in circuit-switched technology. This efficiency optimizes network and radio resource usage making GPRS ideal for data applications such as email and Internet access. Data transmissions suitable for GPRS have the following characteristics: S S S Intermittent, bursty transmissions where the time between successive transmissions greatly exceeds the average transfer delay. Frequent (several per minute) transmissions of less than 500 octets of data. Infrequent (several per hour) transmissions of several kilobytes of data.
Cost efficiency
In a GPRS environment, a user pays only for the traffic volume sent, and not for reserved bandwidth. In other words, charging is based upon the volume of data transmitted. In this way, GPRS makes applications such as web-browsing, remote telemetry, and email available to a large market using the basic GSM infrastructure already available in many countries.
3rd May 01
25
GPRS infrastructure
GPRS-300-101
GPRS infrastructure
Introduction
The addition of GPRS functions required a major modification to the GSM architecture. These changes involved the addition of new GPRS radio channels and the following subsystems. S S S GSN Complex. Packet Control Unit (PCU). Operations and Maintenance Centre-GPRS (OMC-G).
For a more detailed description of the GPRS infrastructure, refer to Chapter 3, GPRS functional description.
GSN Complex
The GSN Complex works with the PCU and OMC-G to provide GPRS functionality to a GSM network. The GPRS Support Node (GSN), Integrated Support Server (ISS) Cluster and CommHub together form a GSN Complex. These are described below:
GSN
GPRS introduces two new network nodes into the GSM Public Land Mobile Network (PLMN): the Serving GPRS Support Node (SGSN) and the Gateway GSN (GGSN), known together as the GSN. The GSN works in parallel with the MSCs to supply traffic to the BSS. The SGSN provides functions similar to that of the MSC in a GSM network. The primary role of the SGSN is to maintain a logical data link with each MS, providing a reliable data channel as the MS moves between cells. The SGSN also supports the billing of traffic data. The GGSN interfaces between the BSS and other Packet Data Networks (PDNs) in a manner similar to the way in which an MSC forms an interface between the BSS and the PSTN in GSM. It directs downlink packets to the SGSN serving the MS, allowing the mobile system to move freely within the coverage area of its home PLMN. The GGSN also forwards packets from an MS to external data networks, and handles the billing of traffic data. The GSN Complex is a scalable entity. SGSNs and GGSNs may be incrementally added to the Complex as demands for capacity increase. This philosophy may be followed until the maximum configuration for a complex is reached. GSN Complexes may be networked together within a single PLMN and across different PLMNs.
ISS Cluster
The ISS Cluster provides the following network functions: S S S S S
26
Domain Name Service (DNS) which maps logical names to network layer Internet Protocol (IP) addresses. Network Time Protocol (NTP) server which synchronizes time across all GSN components in the data network. Network File Server (NFS) which provides long-term storage for network configuration information, charging data information and network statistics. Charging Gateway Function (CGF) which collects and stores subscriber accounting data for collection by a Billing System (BS). High Availability (HA) disk array which provides long-term data storage. System Information: GPRS Overview 68P02903W01-C
3rd May 01
GPRS-300-101
GPRS infrastructure
CommHub
The CommHub is the backbone of the GSN Complex. It provides routeing and switching functions within the GSN, using a LAN to interconnect the SGSN and GGSN. In addition, the CommHub provides IP routeing within the GPRS backbone (Intranet), WAN interfaces using common backbone technologies (Frame Relay), and IP security functions (IP address filtering).
PCU
The Packet Control Unit (PCU) is the primary component that adds GPRS functionality to a GSM BSS. The BSS provides Radio Frequency (RF) control and transmission for GPRS mobile devices. The PCU attaches to the existing GSM Base Station Controller (BSC) and communicates with the SGSN. All BSS components, including the PCU, are managed by the existing OMC-R.
OMC-G
The OMC-G controls and monitors the GSN Complex. It provides a Graphical User Interface (GUI) for analyzing the events, alarms and statistics in one or several GSN Complexes.
3rd May 01
27
GPRS in a GSM system
GPRS-300-101

Introduction
GPRS is designed to integrate into a GSM system. It shares some elements with GSM and adds other new elements designed specifically for GPRS. This section describes how GPRS fits into a GSM system.
Mobile terminals
GSM subscribers require a new type of mobile end point, known as a Mobile Station (MS) to access GPRS service. Existing GSM mobile terminals cannot packetize traffic directly or handle the enhanced air interface. An MS is able to support both GPRS and GSM services and can take different forms, depending on the users requirements. For example, an MS can be a laptop computer, Personal Digital Assistant (PDA) or mobile phone with keypad.
Base stations
All traffic from an MS, whether voice or data, is transported over the air interface to the BTS, and from the BTS to the BSC, in the same manner as a standard GSM message. The GSM BTS and BSC both require a software upgrade to handle GPRS. GPRS packet data traffic is separated from GSM voice and circuit-switched data at the BSC. GSM traffic is sent to the MSC as usual, while GPRS traffic is sent to the PCU, a new component that adds GPRS functionality to the BSS. The PCU segments Logical Link Control (LLC) frames into Radio Link Control (RLC) packets for transmission to the MS by the BSC, and reverses the process for RLC packets received from the BSC for transmission to the SGSN. The PCU also manages timeslot allocation and packet scheduling. New software enables the OMC-R to manage all base station components, including the PCU, for both GPRS and GSM traffic.
28
3rd May 01
GPRS-300-101
Serving nodes
The PCU transfers the packets to the SGSN. The SGSN is a GPRS component that fulfills a role similar to that of the MSC in the GSM system. The SGSN delivers packets to and from MSs in its service area, and tracks the location of the MSs. As an MS moves from one SGSN coverage area to another, the SGSNs communicate with each other and update the user location. The GGSNs are connected to the SGSN via the GPRS backbone. The GGSN acts as a logical interface between MSs and the Internet and other outside GPRS networks. It maintains routeing information used to tunnel PDUs to the serving SGSN, allowing the MS to move freely within the coverage area. The GGSN also collects charging information and forwards it to a billing system. The OMC-G manages all GSN Complex components which include the SGSNs, GGSNs, CommHub and ISS Cluster. Figure 2-2 shows GPRS elements integrated into a GSM network.
SMS-GMSC SMS-IWMSC EIR MSC AuC NSS VLR HLR SMS-C
GSN COMPLEX
CommHub
OMC-G
MS
BTS
BSC BSS
PCU
SGSN GSN
GGSN
PDN
OMC-R
ISS Cluster
Billing System
GPRS connections in this release GSM connections Other PLMN
Figure 2-2 GPRS in a GSM network
3rd May 01
29
Table of GPRS features
GPRS-300-101

Introduction
This section describes the standards compliance for this release and provides a table listing the 1614 GPRS features and services.
Standards compliance
Release 1614 is compatible with the standards approved by Special Mobile Group 31 (SMG 31). A system that is SMG 31-compatible retains some SMG 29 approved specifications but can interwork with SGM 31-compliant MSs and radio access networks. The following specifications are SMG 31 compliant in this release: 04.08 04.64 04.65 08.18 Radio layer 3. Logical Link Control. (LLC). SubNetwork Dependent Convergence Protocol (SNDCP). BSS Gb layer 3.
SMG 29 is the highest level of approval available for the following specifications and consequently these cannot be SMG 31 compliant: 03.60 09.60 09.02 GPRS service description. GPRS Tunnelling Protocol (GTP). Mobile Application Part (MAP).
For more details about these specifications, see References, documents and authors.
Feature table
Table 2-1 maps the GPRS features and services for Release 1.6.1.4 to the GPRS infrastructure elements. It also lists the chapter of this manual in which the item is described. Table 2-1 Features map Chapter Feature O M CG S G S N G G S N H L R Comm Hub I S S
SGSN - PCU connection 4 4 4 4 Gb interface Gb over Frame Relay Port-level Gb link load balancing GSN aggregate Gb on an E1 span Gi interface Transparent and non-transparent access Direct connection X X X X X X
GGSN - PDN connection 4 5 4 X X X

3rd May 01
210
GPRS-300-101
Chapter
Feature
O M CG
S G S N
G G S N
H L R
Comm Hub
I S S
SGSN - GGSN connection 4 6 Gn Interface Inter-SGSN handover X X X
SGSN - HLR connection 4 4 Gr interface SS7-link load balancing and sharing Gp interface Inter-PLMN roaming X X X X
SGSN - VPLMN connection 4 6 X X
Mobility and session management 6 6 6 6 MS attach and detach Location updates PDP context activation and deactivation User-selectable APN X X X X X X X X X X X
Network management 7 7 Operations and maintenance Network security X X X X X X
Charging data collection 3 7 Charging Gateway Function Account metering and collection X X X X X X
Network access control 7 5 7 Lawful intercept Network controlled screening Authentication X X X X X X X
Address translation and mapping 3 5 Domain Name Service (infrastructure) Network Address Translation X X
Packet routeing and transfer 6 5 6 6 PTP-CLNS GPRS backbone Encapsulation and tunnelling V.42bis data compression X X X X X X X
3rd May 01
211
GPRS-300-101
Chapter
Feature
O M CG
S G S N
G G S N
H L R
Comm Hub
I S S
System service 3 Network Time Protocol server X
Non-functional features 8 6 6 2 GSN scalability Operation as Class C mobile Best Effort QoS profile class SMG 31 compatibility X X X X X X X X X X X X X X
212
3rd May 01
GPRS-300-101
Customer support
Customer support
Introduction
This section provides a description of the following Motorola services available to support GPRS customers who require technical assistance: S S Motorola Technical Assistance Centre (TAC). Customer Network Resolution Centre (CNRC).
Technical Assistance Centre

The TAC is a central registry for hardware equipment swap service, problem reports, fault management and emergency support. It is also a tracking facility, providing statistics and reports for all reported problems. Where applicable, the TAC can provide technical assistance for customers 24 hours a day, seven days a week.
Customer Network Resolution Centre

The CNRC logs calls through a service management system to track and manage progress towards resolution for each call. It provides historical trend analysis and performance reporting. All non-software defects are resolved by the CNRC. Software defects requiring software code change are escalated to the relevant development team. Where applicable, the CNRC can provide technical assistance for customers 24 hours a day, seven days a week.
3rd May 01
213
Customer support
GPRS-300-101
214
3rd May 01
Chapter 3
GPRS functional description
3rd May 01
GPRS-300-101
ii
3rd May 01
GPRS-300-101
Chapter 3 GPRS functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN performance and capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN performance and capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CGF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HA Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster performance and capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G performance and capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Control Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
31 31 31 32 32 32 32 34 34 34 35 35 35 36 37 37 37 38 38 38 38 38 39 39 39 310 310 311 311 312 313 314 314 315 315 315 316 316 317 317 318 318 318 318 319 319 319
3rd May 01
iii
GPRS-300-101
Additional GPRS elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LIAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Billing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RADIUS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CNR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
320 320 320 320 320 321 321 321
iv
3rd May 01
GPRS-300-101
Chapter overview
Chapter overview
This chapter describes the functions of the components that make up the Motorola General Packet Radio System (GPRS).

This chapter is divided into the following sections: S S S S S S S Serving GPRS Support Node (SGSN). Gateway GPRS Support Node (GGSN). Integrated Support Server (ISS Cluster). Communications Hub (CommHub). Operations and Maintenance Centre-GPRS (OMC-G). Packet Control Unit (PCU). Additional GPRS elements.
3rd May 01
31
SGSN
GPRS-300-101
SGSN
Introduction
The primary role of the SGSN is to maintain a logical data link with each Mobile Station (MS), providing a reliable and secure data channel as the MS moves between cells. The SGSN performs location tracking for each MS within its service area. The SGSN also mediates access to network resources and provides charging data. This section includes: S S S S S SGSN description. SGSN functions. SGSN performance and capacity. SGSN availability. SGSN security.
SGSN description
In order to access GPRS services, an MS must make its presence known to the network by requesting a GPRS attach. This operation establishes a logical link between the MS and the SGSN, and makes the MS available for the following: S S Paging via the SGSN. Access to Internet Service Provider (ISP) services.
During a GPRS attach, the SGSN establishes a mobility management context containing information pertaining to mobility and security for the MS. In order to send and receive GPRS data, the MS initiates a Packet Data Protocol (PDP) context activation. At PDP context activation, the SGSN establishes a PDP context with the GGSN for use by the GPRS subscriber. This operation makes the MS known in the GGSN, and internetworking with external data networks can then begin across the Gi interface. Subscription information is stored in the internal Home Location Register (HLR), where the mapping between an MS identifier and the Public Data Network (PDN) address is located. This register acts as a database from which the SGSNs can ask whether a new MS in its area is allowed to join the GPRS network.
SGSN functions
The functions provided by the SGSN are: S S S S S S
32
Control Function (CF). Transmission Function (TF). Signalling Function (SF). Operations, Administration, Management and Provisioning (OAMP) function. Relay function. Lawful Intercept (LI) function. System Information: GPRS Overview 68P02903W01-C
3rd May 01
GPRS-300-101
SGSN
CF
The CF provides signalling between the SGSN and other GPRS network components, including the following: S S S S Attach. Detach. PDP context activation. PDP context deactivation.
TF
The TF provides encryption service and Protocol Data Unit (PDU) transfer capabilities between the GGSN and MSs. The TF is divided into two functions: S The Upper TF (UTF) provides access between SGSNs and GGSNs across the Gn interface. It also provides encryption to protect the privacy of information being transmitted over a GPRS network The Lower TF (LTF) provides access between SGSNs and Base Station Systems (BSS) across the Gb interface. This interface enables MSs to access a GPRS network. Each SGSN interfaces with one or more BSS as shown in Figure 3-1.
Serving GPRS Support Node (SGSN) Gb Interface
PCU
PCU
BSC
BSC
Base Transceiver Stations
Base Transceiver Stations
BSS 1
BSS 2
Figure 3-1 Transmission function Gb interface
SF
The SF provides SS7 Mobile Application Part (MAP) signalling capabilities between the SGSN and HLR. SS7 is an ITU standard that defines the procedures and protocol by which network entities in the PSTN establish wireless communication over digital signalling networks.
3rd May 01
33
SGSN
GPRS-300-101
OAMP function
In terms of the SGSNs functional manageability over SNMP, the SGSN is known to the OMC-G through the SGSN OAMP Agent. The SNMP OAMP agent is the sole access point for all SGSN functional management services. Within the SGSN, the Agent acts as a multiplexer of the management requests it receives from the OMC-G to appropriate subagents (TF and CF) that manage the GSN resources.
Relay function
The SGSN generates SGSN-Charging Detail Records (S-CDRs) and Mobility Management-Charging Detail Records (M-CDRs) to support the charging functionality. The S-CDRs and M-CDRs are generated, collected, and then sent to the Charging Gateway Function (CGF). For more details about the CGF, see Charging Function.
LI function
The SGSN generates signaIling and data records for an intercepted transmission and sends these reports to the Lawful Intercept Administration Node (LIAN). The CF generates most signalling records, called Intercept Related Information (IRI) reports, and the TF generates one IRI and all the data records, called Intercept Data Product (IDP) reports. For more details, see Lawful Intercept.
SGSN performance and capacity

An SGSN chassis can support up to three SGSNs. Each SGSN is made up of three cards (LTF, UTF and CF) and can support: S S S 2,000 pps. 10,000 attached subscribers. 12,000 PDP context activations.
For a description of the SGSN modules, see SGSN hardware.
SGSN availability
The SGSN provides the following availability features: S S S S S N+M redundancy (generally N+1). The redundant unit is a cold standby that requires manual recabling and powering on to be brought into service. E1 redundancy provided by Dual E1 PMCs on the UTF(Gn) and SF cards. Automatic power supply and fan module redundancy. Both modules are hot-swappable in a 2+1 configuration. Configuration files are stored on a fully mirrored High Availability (HA) disk array. All cards are protected by current-limiting circuitry to prevent single card failure from causing system failure.
SGSN security
Access to each SGSN module (LTF, UTF, and CF) is password protected.
34
3rd May 01
GPRS-300-101
GGSN
GGSN
Introduction
The GGSN interworks with external packet-switched networks providing context management and generating charging data. This section includes: S S S S S GGSN description. GGSN functions. GGSN performance and capacity. GGSN availability. GGSN security.
GGSN description
The GGSN provides a fixed point gateway interface to external network address mapping, routeing, GTP tunnelling and metering. It provides Gi and Gn communication protocols for signalling and transmission data and is connected to SGSNs via an IP-based GPRS backbone network. The Gi interface provides access between MS subscribers and devices attached to one or more external PDNs as shown in Figure 3-2. The PDP used between the MS and external devices is IPv4. The GGSN contains routeing information for attached GPRS users. This routeing information is used to tunnel packets over the Gn interface to an MS that is attached to an SGSN. The GGSN also collects charging information from the GPRS network and transfers the information to a network operator billing system, by way of a centralized CGF located in the ISS Cluster.
Gi GGSN Gn SGSN CommHub Gi Packet Data Network
Gn
ISS
Internet
Figure 3-2 GGSN interfaces
3rd May 01
35
GGSN
GPRS-300-101
GGSN functions
Gateway function
A gateway is a generic term for a device that provides a translation function between two dissimilar networks. In GPRS, the GGSN translates between the external PDN on the Gi interface, and the internal GPRS Tunnelling Protocol (GTP) on the Gn interface. The connection with the external PDN may be direct over a leased line or indirect via the CommHub. The gateway role of the GGSN is to: S Provide the GGSN transmission function for traffic uplink and downlink. Uplink provides GPRS network access to external hosts that wish to communicate with mobile subscribers. The GGSN acts as a fixed relay point between external hosts and mobile subscribers. Downlink directs mobile terminated packets to the SGSN currently serving the MS, allowing the mobile subscriber to move freely within the coverage area of its home network, or a foreign network. Provide GTP encapsulation and decapsulation. Provide basic routeing. Support private and public IP address types, both static and dynamic. Provide IP pool management (configured within the GGSN).
S S S S
OAMP functions
The management and service role of the GGSN is to: S Provide connection to a centralised OMC-G as a single point of administration, to eliminate site visits. The GGSN can alert a network operator of any performance fluctuation before critical conditions occur, allowing proactive resolution while the system stays online. Enable immediate servicing which minimizes downtime and impact on network availability. The GGSN has field-replaceable components and LEDs for quick status indication. Allow simplified management of routers using the Cisco Web browser management interface (CiscoWorks and CiscoView). Provide processing of activation, modification and deactivation. Download the Access Point Name (APN) Profile database. The APN profile database is a script of PDN inter-working procedures and parameters. APN profiles are used via GGSN equipment to determine the handling of individual PDN access requests from mobile subscribers. The APN profiles are managed centrally within the OMC-G and distributed to the GGSNs as configuration data. A single GGSN may support multiple APN profiles, allowing the GGSN to access several different external data networks in a variety of inter-working scenarios. In addition, a single APN profile may be shared by multiple GGSNs to allow multiple GPRS network access points to the same external network.
S S S
Charging functions
The charging role of the GGSN is to collect and forward GGSN-Charging Detail Records (G-CDRs) to the CGF.
36
3rd May 01
GPRS-300-101
GGSN
GGSN performance and capacity

The GGSN provides the following high performance features: S S S S S S S S Up to 200 Kpps fast switching performance. Up to 25 Kpps GTP fast switching performance. Up to 1 Gbps backplane performance. Support for high-density configurations. Support for high-bandwidth media. Up to 90,000 PDP contexts. Up to 1024 APN profiles. Cisco IOS software support.
GGSN availability
The GGSN uses a Cisco 7206VXR platform that provides the following availability features: S S S S S S N+1 redundancy within a Motorola GPRS Support Node (GSN) Complex. Six slots for port adapter cards. Online insertion and removal of port adapters. Seamless upgrades to higher density port adapter cards without rebooting or taking the system off-line. Load-sharing to extend individual power supply life. Dual sources of prime power. Each power supply has its own power cord, reducing risks associated with the failure of Uninterruptible Power Supply (UPS) systems or building power. Dual power supplies that share the current, ensuring automatic cut-over in case of failure. System flash memory for fast, reliable software and micro-code upgrades. Fast boot.
S S S
GGSN security
Access control lists may be configured on the GGSN to provide IP address filtering. IP Security (IPSec) with hardware accelerator will be supported in a future release.
3rd May 01
37
ISS Cluster
GPRS-300-101
ISS Cluster
Introduction
The Integrated Support Server (ISS Cluster) provides the following network functions: S S S S S Charging Gateway Function (CGF). Domain Name Service (DNS). Network Time Protocol (NTP) server. Network File Server (NFS). High Availability (HA) disk array.
CGF
The CGF provides the storage for real-time collection of CDRs. The CGF application resides on the ISS platform within the GSN Complex. It provides GPRS network operators with a secure and reliable mechanism to collect and transfer billing records to their external subscriber billing system. The CGF receives charging information from resident SGSN and GGSN nodes and stores the CDRs on a local, high availability disc storage system to prevent loss or corruption of the CDRs. The information is subsequently transferred to the CGF for storage based on batch identity. Upon batch closure, these files are transferred to the customers billing system for generating subscriber billing. Since the transfer of the billing records is not performed on a real time basis, the CGF enhances the reliability of the delivery of the billing records. Both the ISS and high availability disc storage system have secondary units which provide backup if the primary unit fails. A single CGF handles all CDRs generated within a typical GSN complex distribution (for example, 18 SGSNs, four GGSNs and 180,000 active subscribers). This feature is compliant with the GSM 03.60 and GSM 12.15 (Release 98 SMG 28) standards.
DNS
The DNS maps logical names to network layer Internet Protocol (IP) addresses. A DNS server is required in a GPRS network to convert logical equipment names to their corresponding IP network address. For example, host.where.here to 123.444.88.5. Motorola provides a centralized DNS management facility for the administration of DNS data. The DNS includes a Graphical User Interface (GUI) to configure and validate the database. This allows for real-time changes to IP addresses and authentication of DNS update requests from remote nodes. This infrastructure DNS provides one-to-one mapping of GPRS equipment interface names to assigned IP addresses. These names should be visible only within the telecom GPRS domain, and not generally accessible to external PDN hosts (for example corporate, service provider or Internet). However, other GPRS networks can be granted access to an internal DNS.
NTP server
The NTP server synchronizes time across all GSN components in the data network by correlating management information across the GSN system so that all GPRS components operate using a common time base. The reference time is obtained from the Public Land Mobile Network (PLMN) IP network or from the Internet. Accurate timing is needed to time stamp traffic statistics, fault logs and charging records.
38
3rd May 01
GPRS-300-101
ISS Cluster
NFS
The NFS stores disk filesystems which are accessed by the SGSNs and Shelf Manager as needed. This client/server relationship consists of: S S S NFS server. NFS client. NFS protocol.
NFS server
In order for the NFS server to export a filesystem to another network entity, the system administrator must edit a configuration file and specify the following: S S S The full pathname of the directory to be exported. The client machines that will have access to the exported directory. Any access restrictions.
At system start up time, a system-dependent program is invoked that opens and reads the information in the configuration file. This program then informs the servers operating system kernel about the permissions applicable to each exported file hierarchy. Special background processes are invoked and wait to receive client NFS requests to access the servers filesystems. After this process is complete, the server is ready to accept client requests to access its filesystems.
NFS client
NFS clients gain access to server files by mounting the servers exported filesystems. The mount process results in integrating the remote filesystem into the clients filesystem tree. An enhanced client-side service automatically and transparently mounts and unmounts filesystems on an as-needed basis. From the user perspective, this creates an environment where server filesystems are continuously accessible.
NFS protocol
The NFS protocol is used to communicate between the NFS server and NFS client over the network. The protocol consists of a set of remote procedures enabling clients to manipulate remote files and directories on server systems as if they were local. Using the NFS protocol routines, clients send requests for file operations to servers, and servers respond by attempting to perform the operation (provided the user has proper permission) and then sending back successful results or error values.
HA Disk Array
The HA Disk Array provides reliable, long-term storage for network configuration, software loads, charging data information and network statistics.
ISS Cluster performance and capacity

Each ISS Cluster can support a GSN with the following maximum configuration: S S S 18 SGSNs. 4 GGSNs. 180,000 active subscribers.
3rd May 01
39
ISS Cluster
GPRS-300-101
ISS Cluster availability

The Cluster nodes (Sun Netra t 1125s) and the HA Disk Arrays (Netra st D1000s) are mirror configured. The Sun Netra t 1125 is used to support the ISS functions within the GSN Complex (DNS, NTP, CGF). In the event of a disk failure, the mirror configuration ensures the data remains available.
ISS Cluster security

Access to the ISS is password protected.
310
3rd May 01
GPRS-300-101
CommHub
CommHub
Introduction
The CommHub is an off-the-shelf router/switch provided by Cisco Systems. An IP switching platform, the CommHub is the central connection point for all communication within GSN elements, and between the GSN and outside entities. This section includes: S S S S CommHub description. CommHub functions. CommHub availability. CommHub security.
3rd May 01
311
CommHub
GPRS-300-101
CommHub description
The CommHub modules select the most suitable route between a source and a destination, then forward data packets to that destination. The modules perform their own processing and Input/Output (I/O). Each module has a specific function in the routeing process. Figure 3-3 shows the CommHub modules and how they connect to other system components. These are described below.
OMC-G collocated
COMMHUB
ISS Cluster
Backplane SGSN-CF Supervisor Engine SF
10/100 BASE-T Module
SGSN-UTF
Route Switch Module VIP2
SGSN-LTF E1 I/O Module GGSN
PDN, WAN and/or other PLMN gateway
OMC-G non-collocated
Figure 3-3 CommHub modules and connections
Supervisor Engine III (SE) module

The SE monitors and controls modules in the CommHub and is responsible for all frame switching and forwarding functions in the CommHub. It enables full access to the 3.6 Gbps backplane. Both the Route Switch Module (RSM) and 10/100BASE-T modules are controlled through the SE. The SE also provides the CommHub with the ability to display alarms and statistics for the individual modules.
312
3rd May 01
GPRS-300-101
CommHub
Route Switch Module

A RSM can be configured as either a bridge or a router for Local Area Networks (LANs) or Wide Area Networks (WANs). In a LAN, an RSM connects to local systems and performs routeing and bridging between segments within the CommHub chassis and local networks. In a WAN, an RSM with VIP2/serial modules connect to remote systems, as shown in Figure 3-3. When configured as a LAN bridge, an RSM module forwards data packets at the data link layer between interfaces. For IP protocols, the interfaces are connected to networks that have the same IP subnet address. When configured as a LAN router, an RSM module forwards data packets at the network layer between interfaces. For IP protocols, the interfaces are connected to networks that have different IP subnet addresses.
VIP2 module
The RSM supports a Catalyst VIP2 module. The Catalyst VIP2 provides direct external network connections through a variety of media with the same port adapters used on Cisco 7200/7500 series routers.
10/100 BASE-T switch module

10/100 BASE-T modules are used in association with the SE to connect components to the Ethernet. The SE manages one or more 10/100 BASE-T switch modules.
CommHub functions
The CommHub provides connectivity and backbone IP router functions.
Connectivity function
The CommHub provides the following connectivity: S LAN connection between: S An SGSN and a GGSN. An SGSN and/or GGSN and the ISS Cluster. OMC-G and the SGSNs, GGSNs, and ISS Cluster.
WAN connection (via the RSM) between the GGSN and external data networks.
Backbone IP router function

The CommHub provides the functions of the backbone IP router, including indirect data paths between the PLMN Intranet nodes (GGSN or SGSN) using the Gn interface. Three GSN configurations exist for physical channels associated with the Gn interface: S S S LAN using 100BASE-T Ethernet. Frame Relay point-to-point using a Public Switched Telephone Network (PSTN) leased E1 link. Frame Relay network using E1 Permanent Virtual Circuit (PVC).
The CommHub function routes user data and control messages between GGSNs and external CommHubs or hosts, using the Gi interface. The CommHub implements inter-domain IP routeing protocols and provides increased fan-out capability between the GGSN and external network gateways.
3rd May 01
313
CommHub
GPRS-300-101
CommHub availability
The CommHub provides the following availability features: S S 1+1 fully redundant internal cards. Power supply and SE are hot-swap capable.
CommHub security
The CommHub performs IP network security functions. For example, it can perform packet address filtering so that only those packets addressed to an MS sub-network are accepted. A network operator may configure the access control lists to meet their security policy requirements.
314
3rd May 01
GPRS-300-101
OMC-G
OMC-G
Introduction
The OMC-G provides a GUI functionality to perform analysis of the events, alarms and statistics of a GSN Complex. This section includes: S S S S S OMC-G description. OMC-G functions. OMC-G performance and capacity. OMC-G availability. OMC-G security.
OMC-G description
The OMC-G enables network operators to equip, configure and maintain the SGSN, GGSN, CommHub, and ISS Cluster. A single OMC-G supports an entire GSN Complex. The OMC-G, along with the OMC-R (see Packet Control Unit), performs operations and maintenance functions at a regional level. These OMCs are subordinate to the Network Management Centre (NMC) which operates at a network-wide level. Administrative tools are provided to perform load management of GSN operation code and off-line preparation of configuration data. The OMC-G does not use Command Line Interface (CLI) commands to interact with management functions. Figure 3-4 shows the OMC-G in a GPRS network.
NMC
OMC-R
OMC-G
BTS
BSC
PCU
CommHub
E1
CommHub
Frame Relay
SGSN
GGSN
ISS Cluster
Figure 3-4 OMC-G in a GPRS system
3rd May 01
315
OMC-G
GPRS-300-101
OMC-G functions
The OMC-G provides the following functions for the GSN Complex:
Fault management
The alarm window is the centre of the OMC-G fault management application and provides the OMC operator with an alarm list. Through the alarm window, the operator can acknowledge the event, determine the source of the alarm, and take corrective action to resolve the problem.
Configuration management
The OMC-G Navigator and parameter views enable operators to view and modify configuration parameters for GSN Complex entities.
Load and database management

The OMC-G load management application provides the ability to install, delete, or download the software or database. It also enables uploading of the database. In addition, the Swap Code Load feature allows a GGSN, SGSN, Shelf Manager or SF to swap to a new software load when the Network Entity (NE) restarts.
Performance management
The OMC-G performance management application enables an operator to view both on-demand (polled) and background statistics for the GSN. On-demand statistics enable a user to view current GSN values in the network and create a real-time display of a statistic for a specific GSN. Background statistics are files containing historical information. The OMC-G collects backgrounds statistics from the GSN at fifteen minute intervals, then parses them into the Informix database from which they can later be retrieved for network analysis.
Security management
OMC-G security management oversees user authentication and control of operator access. Authentication is achieved by a validity check of the username/password combination entered by the operator when logging on to the system.
Online help
Context sensitive online help is available from the OMC-G GUI.
OMC-G performance and capacity

An OMC-G can support: S S S S S
316
10 alarms per second and bursts of 40 alarms per second for 40 minutes. Up to 18,000 individual statistics every 15 minutes. A maximum of one million PDP contexts. Up to three simultaneous PDP contexts for each subscriber. A maximum of 100 SGSNs. System Information: GPRS Overview 68P02903W01-C
3rd May 01
GPRS-300-101
OMC-G
OMC-G availability
The OMC-G provides the following availability features: S S S S Redundant cooling fans. Hot-pluggable redundant power supplies and drives which enables component replacement without powering down the server. Redundant load balancing network cards which eliminates a single point of failure. Dynamic Reconfiguration, Alternate Pathing and system management tools which provide the OMC-G server with high availability, performance and reduced down-time. The combination of the SUN Solaris operating environment and modular hardware contribute to expanded performance and capacity.
OMC-G security
The OMC-G provides network access security through the Profile Editor tool which can be configured to: S S S Create user IDs. Create regions and restrict the user ID access to selected regions of the network. Users can be assigned read-write, read-only, or no access to a region. Create command groups and restrict the user ID access to the commands available in each region.
3rd May 01
317
Packet Control Unit
GPRS-300-101
Packet Control Unit

Introduction
The Packet Control Unit (PCU) adds GPRS radio channel control functions to the GSM Base Station System (BSS). This section describes: S S S S S BSS. OMC-R. PCU description. PCU interfaces. PCU availability.
BSS
The BSS is the interface between the MS and the SGSN, providing Radio Frequency (RF) control and transmission for GPRS MSs. A BSS is not provided as part of Motorolas standard GPRS solution because some network operators may prefer to add GPRS functionality to their existing BSSs. However, Motorola can provide a BSS as an option. A standard BSS in a GPRS network consists of the following components:
PCU
The PCU is a GPRS-specific component that integrates the Gb interface with existing Motorola GSM equipment. The PCU is described in more detail below.
BSC
The Base Site Controller (BSC) is collocated with the PCU and provides the central routeing and distribution point for GPRS signalling and data. It routes information to the Base Transceiver Station (BTS), PCU and SGSN.
BTS
The BTS is responsible for assigning timeslots for either circuit-switched calls or for GPRS. Radio timeslots can be dynamically switched between circuit-switched mode (TCH or SDCCH/8) and GPRS (PDCH) modes, under the control of the radio subsystem software. The BTS and PCU work in unison to perform GPRS radio functions. The PCU allocates and de-allocates the radio resources.
OMC-R
The PCU is managed as an extension to the BSS by the Operations and Maintenance Centre-Radio (OMC-R). The OMC-R provides network operators with the capability to manage and monitor the radio aspects of both a GSM and GPRS network. Software in the OMC-R manages the GPRS PCU and the new GPRS features in the BSC and BTS. Operations and maintenance link BSC GPRS signalling link
OMC-R
PCU
Figure 3-5 PCU management from the OMC-R

318
3rd May 01
GPRS-300-101
Packet Control Unit
PCU description
The PCU is the physical and logical interface for GPRS packet data traffic to and from the BSS. The PCU attaches to the Base Station Controller (BSC) and services the entire BSC. Each BSS can be equipped with one PCU. The PCU interconnects with the SGSN over a Frame Relay network or a direct connection. The Gb interface can be routed directly to the SGSN or though the BSC. A remote transcoder can be used in conjunction with the BSC to concentrate GPRS traffic from several PCUs onto a single Gb link.
PCU interfaces
The PCU has two interfaces one to the BSC and the other to the SGSN.
BSC-PCU interface
The BSC-PCU interface carries user data and signalling information between the PCU and BTS via the BSC, providing the following GPRS functions: S S S Time-slot allocation and packet scheduling on the air interface to provide efficient use of spectrum resources. Error detection resulting in the retransmission of unacknowledged Radio Link Control (RLC) data blocks. Radio channel management including power control, timing advance, and system information message generation.
PCU-SGSN interface
The PCU and SGSN use Frame Relay and Base Station System GPRS Protocol (BSSGP) to exchange user data and signalling information. The signalling data is used for flow control and congestion management. On the downlink side, the PCU uses the Quality of Service (QoS) information contained within each Logical Link Control (LLC) frame to determine how to buffer and schedule the GPRS data. The PCU--SGSN interface provides the following functions across the Gb interface: S Segments LLC frames from the SGSN into Radio Link Control/Media Access Control (RLC/MAC) blocks. These blocks are then sent to the MSs by the BSC over the air interface. Reconstructs LLC frames from RLC/MAC blocks generated by an MS, then sends the frames on to the SGSN. The GPRS software performs the protocol conversion required between Frame Relay and RLC/MAC.
PCU availability
The PCU provides the following availability features: S S S Hot-swappable cards. Redundant power supplies. Control and monitoring provided by the Hot Swap Controller (HSC) board associated with each processor board.
3rd May 01
319
Additional GPRS elements
GPRS-300-101

Introduction
The following elements perform an important role in GPRS, but are not part of the standard GPRS package. They are either optional equipment available through Motorola or must be purchased independently: S S S S S S Lawful Intercept Administration Node (LIAN). Home Location Register (HLR). Billing System. Remote Authentication Dial-In User Service (RADIUS) server. Mobile Station (MS). Cisco Network Registrar (CNR).
LIAN
The LIAN is not provided as part of the Motorola standard solution, but is available as an option. The LIAN supports the administration of the GPRS Lawful Intercept function. Lawful intercept provides operators with the capability to track and monitor signalling information for a particular mobile. It duplicates the signalling information for an MS being intercepted in the PLMN and sends the information to the requesting law enforcement agency. The Motorola LIAN is developed on a Sun Netra server platform. The LIAN server is configured with a single 300 MHz UltraSPARC-IIt processor and a 9.1 GB internal disk. Motorolas client is based on an NT solution.
HLR
The HLR is not provided by Motorola. The HLR is a database containing the information required to establish a connection to and from a GPRS subscriber or other publicly available service within the network. For each MS, the HLR database stores the International Mobile Station Identifier (IMSI) which identifies the MS, and the Mobile Subscriber Integrated Services Digital Network (MSISDN) number which a user must dial to reach the MS. The HLR database also contains the current location of the MS, and the available services and service levels. One HLR contains the subscriber information for an entire network including radio (GSM) and data (GPRS). It can be implemented as a distributed database. For a roaming MS, the HLR may be located in a different PLMN than the current SGSN. The HLR is accessible from the SGSN via the Gr interface and from the GGSN via the alternate Gc (Gn/Gr) interface.
Billing System
The Billing System is not provided by Motorola. The Billing System generates customer bills, billing statistics and billing reports. It interconnects to the Charging Gateway Function (CGF) of a GSN which provides storage for real-time collection of CDRs.
320
3rd May 01
GPRS-300-101
RADIUS server
The RADIUS server is not provided by Motorola. The RADIUS server acts as a security gateway to the PLMN and authenticates and authorizes all remote access. The RADIUS server is accessed during PDP context activation. The GGSN functions as a client of the PLMN RADIUS server. The GGSN is responsible for passing user information to a designated RADIUS server and acting on any response. User authentication is performed by a series of communications exchanges between the GGSN and the RADIUS server. Once a user is authenticated, the GGSN provides user access to a specific network resource, (for example, the Internet). When a user initiates a PLMN ISP access (indicated by the APN), the GGSN behaves as a RADIUS authentication client.
MS
MSs are not provided as part of Motorolas standard GPRS solution, but those manufactured by Motorola are available as an option. The Motorola GPRS system also supports MSs manufactured by most other major telecommunications corporations. An MS consists of a hand-held Mobile Equipment (ME) terminal, containing a smart card known as the Subscriber Identity Module (SIM). The SIM contains subscriber identification data which allow the user to access GPRS services. Each MS has a unique identifier which is registered with the HLR. MSs are carried by subscribers. A subscriber is the person who is authenticated during the attach/activation procedures and is usually accessing the GPRS system through an employer or an ISP. Subscribers have two identitiesa GSM identity which is managed at the HLR, and an optional IP identity which is managed at a RADIUS server. Identity management is performed at the OMC-G. Before access can be granted, the subscriber must be authenticated and authorized. In addition, network-controlled screening can be implemented to restrict subscriber access to a set of external servers based on address and type of application. This enables network operators to provide higher access security for GPRS subscribers. This release supports Class C mode of operation. In Class C mode an MS can make or receive calls from GPRS only.
CNR
The CNR is not provided as part of Motorolas standard GPRS solution, but is available as an option. The CNR is a centralized DNS management facility for internal DNS and DHCP data administration. This management facility provides a GUI to configure and validate the database, as well as dynamic DNS and secure DNS features. The DNS and DHCP can be installed centrally within a single zone, or distributed among several zones.
Access Point Name (APN) Domain Name Service (DNS)

The APN DNS maps logical access point names to one or more GGSN IP addresses. An APN is an identifier for a PDN that is configured on, and accessible from, a GGSN. It is used to specify the PDN to which an MS wishes to connect. The APN can be a label or a fully qualified domain name according to DNS naming conventions as specified in GSM 03.03. To support inter-PLMN roaming, the internal GPRS DNS function translates the APN into the IP address of the GGSN. An APN can be mapped to several GGSN IP addresses, and the same IP address can be mapped to multiple APNs. These APN names are not generally accessible to external PDN hosts (for example corporate, ISP or Internet). However, other GPRS networks can be granted access to an internal DNS.
3rd May 01
321
GPRS-300-101
Dynamic Host Configuration Protocol (DHCP)

DHCP provides a method of dynamically assigning temporary IP addresses and configuration parameters to IP hosts or clients in an IP network. Using DHCP, the CNR can automatically allocate reusable IP addresses and additional configuration parameters for client operations, and enable the configuration of parameters not directly related to the IP protocol. The CNR is a full-featured, scaleable server installed on the Sun hardware platform. Separate hardware platforms can be used for APN DNS and DHCP services.
CNR features
Table 3-1 lists the DNS features provided by the CNR. Table 3-1 DNS features provided by the CNR Feature Classless inaddr.arpa (zones) Description Supports a wide variety of network topologies and DNS zone structures. Supports the use of the best practices described in RFC 2317 (but does not automatically generate the large number of alias records suggested by the RFC). Allows DNS clients and DHCP servers to dynamically update DNS with new IP address and DNS name mappings. Able to hide the sub-zone hierarchy for all zones delegated by a server. Allows for import of DNS information in the BIND zone file format. Transfers incremental changes in a DNS zone during a zone transfer. Configurable as an internal root DNS server. Primary DNS server notifies secondary DNS servers of changes to zone information. Allows control of physical memory size used by the DNS server. Also, allows DNS cache data to be preserved across system or server restarts. Pre-configured with names and addresses of the Internet root name servers. Forwards DNS queries for specified domains to internal DNS servers. Rotates the order of multiple A records (address records) under one name, for successive queries under that name. Supports SRV records, including dynamic DNS update of SRV records. Sorts multiple addresses (A records) when a DNS resolver (client), DNS server and target reside on a common subnet.
Dynamic updates
DNS sub-zone hiding Import zone files Incremental zone transfers Internal root Notify Persistent cache
Pre-configured root (server) Resolution exception (Selective forwarding) Round robin
SRV records Subnet sorting
Table 3-2 provides a list of DHCP features provided by the CNR.

322
3rd May 01
GPRS-300-101
Table 3-2 DHCP features provided by the CNR Feature BOOTP and dynamic BOOTP Description The BOOTP assigns addresses and configuration information to clients, based upon a client MAC address. Dynamic BOOTP dynamically assigns IP addresses, and shares an IP address pool with the DHCP server. Allows customization of an IP address, DHCP options, and domain name based upon a clients MAC address. Allows an administrator to configure new DHCP options. Supports the DHCP relay agent option. Supports DHCP Safe Failover protocol. Updates the DNS server with two records each in the forward and reverse zones. Allows users to customize the handling of DHCP packets that are being processed by the DHCP server. Selects DNS names as follows: As requested by the client (end-user controlled). As specified in the directory entry for the client. Synthesized from a MAC address. Reads client information from a directory and update it with lease data. Supports DHCP server systems with multiple network interfaces. Pings the network before an IP address is offered to a DHCP client. Supports three allocation methods: automatic, dynamic and manual. Allows an administrator to create DHCP address pools containing addresses from multiple logical subnets on the same physical network. Generates an email notice when the threshold of available addresses on one or more subnets is exceeded. Address pools for different IP subnets can have different subnet masks.
Class of service (client and client-class) DHCP custom options DHCP relay agent option DHCP safe failover Dynamic DNS updates Extension points Flexible name options
LDAP directory support Multiple network interfaces PING before lease (offer) Supports all DHCP allocation methods Secondary subnets
Utilization alerts
Variable-length subnet masks
3rd May 01
323
GPRS-300-101
324
3rd May 01
Chapter 4
GPRS interfaces
3rd May 01
GPRS-300-101
ii
3rd May 01
GPRS-300-101
Chapter 4 GPRS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagram of GPRS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of GPRS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagram of GPRS protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmission and signalling planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of GPRS protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ga interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ga description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ga protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GTP Prime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L1/L2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ga signalling PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb signalling PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gi interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gi description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gi protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP and L1/L2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gn interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gn description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gn protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UDP, IP and L1/L2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gn signalling PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gp interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gp description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gp protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gp signalling PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
41 41 41 42 42 42 43 44 44 44 44 46 47 47 47 48 48 48 49 49 49 410 410 410 412 413 414 414 414 415 415 415 416 417 418 418 419 420 420 420 421 422 422 422 423 423
3rd May 01
iii
GPRS-300-101
Gr interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gr description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gr protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gr signalling PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gc interface alternative (Gn/Gr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gn/Gr description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gn/Gr protocol stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
424 424 424 426 426 426 426 426 428 428 429 430 430 430 430
iv
3rd May 01
GPRS-300-101
Chapter overview
Chapter overview
This chapter lists the interfaces and protocols that allow GPRS network entities to communicate with each other and external systems.

This chapter is divided into the following sections: S S S S S S S S S GPRS interfaces. GPRS protocol stack. Ga interface. Gb interface. Gi interface. Gn interface. Gp interface. Gr interface. Gc interface alternative (Gn/Gr).
3rd May 01
41
GPRS interfaces
GPRS-300-101
GPRS interfaces
Introduction
This section includes a: S S Diagram of GPRS interfaces. List of GPRS interfaces.
Diagram of GPRS interfaces

Figure 4-1 shows the interfaces between GPRS network entities and between external entities in GSM and other outside networks.
SMSGMSC SMSIWMSC SMSC
E Gd
MSC/VLR
HLR
Gc A Gs Gr CommHub Gn TE R MS Um BSS Gb SGSN Gn Gi Gi PDN TE Gi
GGSN Ga CGF
Ga Gp Gf
Billing System
GGSN EIR Other PLMN
Figure 4-1 GPRS interfaces
42
3rd May 01
GPRS-300-101
GPRS interfaces
List of GPRS interfaces

Table 4-1 lists the interfaces shown in Figure 4-1. The table specifies between which network entities the interfaces provide connectivity. Table 4-1 GPRS interfaces Interface Ga Entity Charging Gateway Function (CGF) Packet Control Unit (PCU) Home Location Register (HLR) Short Message Service (SMS) Equipment Identity Register (EIR) Public Data Network (PDN) Internal GGSN External GGSN Home Location Register (HLR) MSC/VLR GPRS entity SGSN GGSN SGSN GGSN Notes For more details, see Ga interface.
Gb Gc
For more details, see Gb interface. The Gc interface is not supported in the current release. For an alternative, see Gc interface alternative (Gn/Gr). The Gd interface is not supported in the current release. The Gf interface is not supported in the current release.
Gd Gf
SGSN SGSN
Gi Gn Gp Gr Gs
CommHub For more details, see Gi interface. SGSN SGSN SGSN SGSN For more details, see Gn interface. For more details, see Gp interface. For more details, see Gr interface. The Gs interface is not supported in the current release.
3rd May 01
43
GPRS protocol stack
GPRS-300-101
GPRS protocol stack

Introduction
This section describes the protocol stack for the GPRS transmission and signalling planes. More details about the individual protocols are available in the following sections describing the interfaces for which the protocols provide connectivity. This section includes: S S S Diagram of GPRS protocol stack. Transmission and signalling planes. List of GPRS protocols.
Diagram of GPRS protocol stack

The GPRS protocol stack is shown in Figure 4-2.
MS BSS SGSN GGSN End System
Um App IP
Gb
Gn
Gi App Relay IP
Relay SNDCP LLC RLC MAC GSM RF Relay RLC BSSGP MAC Network Service GSM RF L1 SNDCP LLC BSSGP Frame Network Relay Service E1 L1 GTP UDP IP L2 L1 GTP IP UDP IP Internet L2 L1 L2 L1 L2 L1 IP
Figure 4-2 GPRS protocol stack
Transmission and signalling planes

The GPRS protocols provide control and data transfer functions over the transmission and signalling planes.
Transmission plane
In any GPRS system, thousands of MSs may attempt to gain access to the system at the same time that thousands more are sending millions of packets through the data pipes. The transmission plane provides effective control of these simultaneous transmissions. The transmission plane consists of a layered protocol stack to transfer user information with information transfer control procedures such as flow control, error detection, error correction and error recovery.
44
3rd May 01
GPRS-300-101
GPRS protocol stack
Signalling plane
The signalling plane consists of protocols for control and support of the transmission plane functions as follows: S S S S S Controls GPRS network access connections, such as attaching to and detaching from the GPRS network. Controls the attributes of an established network access connection, such as activation of a Packet Data Protocol (PDP) address. Controls the routeing path of an established network connection in order to support user mobility. Controls the assignment of network resources to meet changing user demands. Provides supplementary services.
Message flow
A significant part of the control and data transfer functions are the messages flowing back and forth between nodes. Figure 4-3 is an example of a message sequence. For more examples, see the Mobility and Session Management chapter of this manual.
MS
BSS Um Gb
SGSN
GGSN Gn
Activate PDP Context Request Activate PDP Context Response
Create PDP Context Request Create PDP Context Response
Figure 4-3 Example of message flow
3rd May 01
45
GPRS protocol stack
GPRS-300-101
List of GPRS protocols

Table 4-2 describes the functional entities shown in Figure 4-2. Table 4-2 Functional entities in the GPRS protocol stack Acronym BSSGP GTP GTP IP NS Name Base Station System GPRS Protocol GPRS Tunnelling Protocol GTP Prime Internet Protocol Network Service Description For more details, see Gb interface. For more details, see Gn interface and Gp interface. The GTP protocol is not shown in Figure 4-2. For details, see Ga interface. For more details, see Gi interface and Gn interface. For more details, see Gb interface. Frame Relay (FR) is used by the NS layer in the Gb interface protocol stack. This function relays: LLC PDUs in the BSS, between the Um and Gb interfaces. PDP PDUs in the SGSN, between the Gb and Gn interfaces. IP packets between the Gn and Gi interfaces. For more details, see Ga interface and Gn interface.
Relay
Relay
UDP
User Datagram Protocol
For details about the following protocols that provide connectivity across the radio interface, see System Information: General (GSM-100-101): S S S S S Subnetwork Dependent Convergence Protocol (SNDCP). Logical Link Control (LLC). GSM Radio Frequency (GSM RF). Media Access Control (MAC). Radio Link Control (RLC).
46
3rd May 01
GPRS-300-101
Ga interface
Ga interface
Introduction
This section includes: S S S S S S S Ga description. Ga protocol stack. GPRS Tunnelling Protocol Prime (GTP). User Datagram Protocol (UDP). Internet Protocol (IP). Layer 1/Layer 2 (L1/L2). Ga signalling Packet Date Units (PDUs).
The Ga interface supports forwarding Call Detail Records (CDRs) to the Billing System in compliance with GSM 12.15, Version 7.1.0, Release 1998.
Ga description
The Ga interface (see Figure 4-4) provides connectivity between the CGF and the SGSN and GGSN. The Ga interface is defined by GTP, also referred to as Enhanced GTP. The CGF aggregates and reliably stores subscriber accounting data created by the SGSN and GGSN. This accounting information is cached locally and subsequently transferred to the CGF for storage based on batch identity. After the batch closure, the data is transferred from the CGF to the Billing System.
HLR
Gr CommHub
Gi Gn Gi
BSS BTS BSC PCU
Gb SGSN
Gn GGSN
Gi
PDN
TE
Gp
Ga
Ga
Billing CGF
GGSN
System
Other PLMN
Figure 4-4 Ga interface
3rd May 01
47
Ga interface
GPRS-300-101
Ga protocol stack
Figure 4-5 shows the Ga protocol stack.
Ga
GTP UDP IP L2 L1 GSN
GTP UDP IP L2 L1 CF
Figure 4-5 Ga protocol stack
GTP Prime
The GTP protocol operates on the Ga interface. The protocol delivers GPRS CDRs to the CGF from the SGSN and GGSN. GTP is derived from the GPRS Tunnelling Protocol (GTP) which is used for packet data tunnelling in the GPRS backbone network. GTP provides the following functions: S S CDR transfer mechanism between the CGF and GPRS nodes that generate CDRs. Echo messaging to detect communication failures between the GPRS entities handling CDRs.
The purpose of the duplication prevention support of GTP is to reduce the number of duplicate CDRs sent to the Billing System. This reduces the effort required to check for duplicate CDRs.
UDP
GTP Prime runs on UDP. UDP is a transaction-oriented protocol that promotes minimal transport layer service. Delivery and duplication protection are not guaranteed by UDP. UDP provides the following two services over IP: checksum of data, and multiplexing by port numbers. UDP is defined in RFC 768.
48
3rd May 01
GPRS-300-101
Ga interface
IP
The Ga interface uses IP which is the most widely used internetworking protocol. IP version 4 is defined in IETF RFC 791 (September 1981). IP moves datagrams through an interconnected set of networks by passing datagrams from one Internet module to another until the destination is reached. The Internet modules reside in hosts and gateways in the Internet system. The datagrams are routed from one Internet module to another through individual networks based on the interpretation of an Internet address. IP deals with addresses, not names or routes. It is the task of higher level protocols to map names to IP addresses while the Internet Protocol maps IP addresses to local network addresses. It is the task of lower level protocols to map from local network addresses to routes. An IP address is a fixed length of four octets (32 bits). When routeing messages from one Internet module to another, datagrams may have to traverse a network whose maximum package size is smaller than the size of the datagram. To overcome this situation, IP fragments a package, transmits it, then reassembles it at its destination.
L1/L2
L1 is the physical layer. This layer specifies the mechanical, electrical, functional and procedural characteristics required to access the physical medium. L2 is the network access layer. This layer specifies how the network is used to exchange data from the layer above (IP) and the layer below (physical). Numerous standards have been defined for this layer including wide area networks (for example, X.25 and FR) and local area networks (for example, Fast Ethernet).
Ga signalling PDUs
GTP provides the following signalling PDUs: S S S S NODE ALIVE G-PDU. DATA RECORD TRANSFER G-PDU. ECHO REQUEST. ECHO RESPONSE.
3rd May 01
49
Gb interface
GPRS-300-101
Gb interface
Introduction
This section includes: S S S S S S Gb description. Gb protocol stack. Base Station Subsystem GPRS Protocol (BSSGP). Network Service. L1. Gb signalling PDUs.
The Gb interface is defined by BSSGP in compliance with GSM 08.14, 08.16 and 08.18.
Gb description
The Gb interface (see Figure 4-6) provides connectivity between the SGSN and multiple PCUs. It allows many users to be multiplexed over a common physical resource. GPRS signalling and user data may be sent on the same physical resources.
HLR
Gr
CommHub
Gi Gn Gi
BSS BTS BSC PCU
Gb
SGSN
Gn GGSN Gi PDN TE
Gp
Ga
Ga
Billing CGF GGSN System
Other PLMN
Figure 4-6 Gb interface
Infrastructure sharing
To facilitate cost effective transmission, Gb supports infrastructure sharing to enable the operator to carry A interface (circuit-switched) and Gb interface (packet) traffic on a single E1, using a point-to-point connection. As GPRS traffic increases, one or more span lines can be dedicated to GPRS traffic. The network supports a direct connection between the PCU and the SGSN to accommodate this change.
410
3rd May 01
GPRS-300-101
Gb interface
Aggregated links
The aggregated links feature allows a network operator to aggregate a number of Gb interfaces over fractional E1 into one single E1 span. This is achieved by means of installing third-party Digital Access Cross-connect Systems (DACS) between the PCUs and the SGSN. With this configuration, one single E1 span on the SGSN can support multiple PCUs. This is a more economic GSN operating model.
Load balancing on port-level Gb

Load balancing on the port-level Gb link allows multiple Gb links to be load balanced and shared amongst the E1 ports on the Gb interface card. It is introduced to provide a higher SGSN-PCU link availability which improves the overall network availability. With the introduction of Gb link load balancing and sharing, the GPRS core network availability between the PCU and the SGSN is greatly enhanced, thus providing more robust end-to-end network connectivity. The load balancing/sharing can be implemented between the SGSN and PCU on Point to Point (E1 span) or FR. When configuring this feature in the GSN, a pair of DS0 links can be configured on two different E1 physical ports in the same Gb card, providing the redundant connectivity to each PCU. A maximum of 12 PCUs can be supported by each SGSN. Signalling and data traffic from several MSs is then shared among the configured pairs of E1 links, with all the traffic from one MS being handled by a single E1 link. The load shared traffic is also load balanced automatically by the SGSN/PCU software.
Flow control
The BSSGP layer is the flow control mechanism within the SGSN. To transfer packets between the SGSN and the BSS, the BSSGP layer uses an address split into three parts: the cell identity, Quality of Service (QoS), and MS Identification. These three address parts are used to create queues and contexts dynamically for both the SGSN and BSS. The flow control mechanism operation is based upon these queues and contexts. The QoS and MS identity are used to address queues in the SGSN, for packet transfer from the BSS to the SGSN only. A cell context in the BSS consists of one queue for Link Layer Control (LLC) packets per cell and QoS priority level. Signalling uses its own queue context with the highest priority level. The cell context in the BSS is allocated for each cell supporting GPRS. For each new GPRS cell introduced into the BSS coverage area, a new cell context is allocated. Cell contexts may then be released after a time if the context has not been active, or when cell parameters are modified.
3rd May 01
411
Gb interface
GPRS-300-101
Gb protocol stack
Figure 4-7 shows the protocol stack for the MS-to-SGSN signalling plane. These protocols are described below. This section is concerned with the lower levels of the protocol stack, the SGSN BSS layers. The higher level radio interface protocols are described in System Information: General (GSM-100-101). These are the GPRS Mobility Management and Session Management (GMM/SM) protocol, and the Logical Link Control (LLC) protocol. SNDCP (shown in Figure 4-2) is part of the GMM/SM protocol.
Um Gb
GMM/SM
GMM/SM
LLC Relay RLC RLC MAC MAC BSSGP Network Service
LLC
BSSGP
Network Service
GSM RF
GSM RF
L1
L1
MS
SGSN
Figure 4-7 Gb protocol stack
412
3rd May 01
GPRS-300-101
Gb interface
BSSGP
The Gb interface uses the BSSGP protocol over FR to connect the SGSN with one or more PCUs. BSSGP is specified in GSM 08.18. BSSGP provides radio-related information used by the Radio Link Control (RLC) and MAC functions. The BSSGP also enables the SGSN and BSS to operate node management control functions. The main functions of BSSGP are to: S S S S Provide a connectionless link between the SGSN and the BSS. Transfer data (unconfirmed) between the SGSN and the BSS. Handle paging requests from the SGSN to the BSS. Support multiple layer 2 links between the SGSN and one BSS.
The BSSGP does not perform error correction. Figure 4-8 shows the functions that use the BSSGP protocol.
SERVICE MODEL IN A SGSN LLC GMM NM
GMM
NM
BSSGP
BSSGP
NETWORK SERVICE
Figure 4-8 BSSGP service model
3rd May 01
413
Gb interface
GPRS-300-101
Network Service
The Network Service (NS) layer transports BSSGP PDUs. The NS depends upon the FR connection between the BSS and SGSN. The NS may multi-hop and traverse a network of FR switching nodes. The NS is specified in GSM 08.16. The FR access environment includes all the hardware and software used to connect the SGSN sites internal computing environment to the FR service. The FR access hardware consists of one or more E1 interface boards. A local loop connection is required to access a FR network. A Service Access Point (SAP) and a switch are required for the SGSN. The following characteristics apply to the FR connection: S S S S S The maximum FR information field size is 1,600 octets. The FR address length is 2 octets. The BSS and SGSN both use FR Data Terminal Equipment (DTE) functionality; the SGSN can also use Data Communications Equipment (DCE) functionality. FR uses Permanent Virtual Circuits (PVCs). One or more FR PVCs are used between one SGSN and one BSS to transport BSSGP PDUs.
L1
L1 is the physical layer. This layer specifies the mechanical, electrical, functional and procedural characteristics required to access the physical medium.
Gb signalling PDUs
The BSSGP provides the following signalling PDUs as defined in GSM 08.18: S S S S S S S S S S S S S S
414
DL-UNITDATA. UL-UNITDATA. PAGING PS. PAGING CS. LLC-DISCARDED. FLOW-CONTROL-BVC. FLOW-CONTROL-BVC-ACK. BVC-BLOCK. BVC-BLOCK-ACK. BVC-UNBLOCK. BVC-UNBLOCK-ACK. BVC-RESET. BVC-RESET-ACK. STATUS. System Information: GPRS Overview 68P02903W01-C
3rd May 01
GPRS-300-101
Gi interface
Gi interface
Introduction
This section includes: S S S Gi description. Gi protocol stack. IP and L1/L2.
The Gi interface is defined in compliance with GSM 09.61.
Gi description
The Gi interface connects a GPRS network to an external Packet Data Network (PDN). The interface functionality for the Motorola GPRS is shared between the CommHub and the GGSN (see Figure 4-9). The Gi interface is defined by the Internet Protocol (IP). The E1 and fractional E1 interfaces are supported on the Gi interface.
HLR
Gr CommHub
Gn BSS BTS BSC PCU
Gi-i
Gi-e
Gb SGSN
Gn
GGSN
PDN
TE
Gi-e
Gp Ga Ga
Other PLMN
Figure 4-9 The Gi interfaces The Gi interface provides the following two alternatives for connecting to a PDN. The GGSN can support both types of connections at the same time. S S Directly from the GGSN. Indirectly from the GGSN through the CommHub.
3rd May 01
415
Gi interface
GPRS-300-101
Direct connection
The direct connection feature enables a GPRS network to bypass the CommHub and connect directly with a PDN using the External Gi (Gi-e) interface on the GGSN. In this release, Motorolas implementation of the direct connection feature uses a leased line. A leased line is a dedicated connection from a customers place of business, through a service provider network, to a remote network. By bypassing the CommHub, the direct connection feature can provide faster, more efficient access to the PDN for small numbers of authorized subscribers who wish to access limited amounts of data. For example, a courier requesting a corporate network for information about the next pickup. Direct connection is not suitable for large numbers of subscribers, large amounts of data or network-initiated connections. A direct connection can be configured with redundant links to improve the availability and reliability of the feature.
Indirect connection
The indirect connection feature connects the GGSN to a PDN through the internal Gi (Gi-i) interface on the GGSN and the Gi-e interface on the CommHub. This type of connection is suitable for all supported situations and amounts of data. One or more physical IP ports at the GGSN can be associated with the internal Gi interface. The GGSN can be configured as multiple logical Gi-i interfaces each with a unique IP address or as multiple physical Gi-i interfaces each having a unique IP address. Multiplexing between the Gi-i interfaces is performed via the GGSN routeing function. The required number of physical communication ports at the CommHub is determined by: S S The required number of external network interface connection end-points. The aggregate required capacity of all the individual external network interface connection end-points.
Gi protocol stack
Figure 4-10 shows the protocol stack for the Gi interface.
MS App IP SNDCP LLC RLC MAC GSM RF Relay IP GTP IP UDP IP L2 L1 L2 L1 Internet L2 L1 IP Um Gi End System App
Figure 4-10 Gi interface protocol stack

416
3rd May 01
GPRS-300-101
Gi interface
IP and L1/L2
For a description of the Gi protocols (IP and L1/L2), see Ga interface.
3rd May 01
417
Gn interface
GPRS-300-101
Gn interface
Introduction
This section includes: S S S S S Gn description. Gn protocol stack. GPRS Tunnelling Protocol (GTP). UDP, IP and L1/L2. Gn signalling PDUs.
The Gn interface is defined in compliance with GSM 09.60.
418
3rd May 01
GPRS-300-101
Gn interface
Gn description
The Gn interface is present at both the SGSN and GGSN (see Figure 4-11). One or more physical IP ports at the GSN can be associated with the Gn interface. The Gn interface is configured as multiple logical IP hosts, with the GSN containing multiple unique IP addresses. These IP interfaces, or logical hosts use separate physical interfaces. Each physical interface port uses a unique IP address. Multiplexing between the IP interfaces is performed at the IP routeing level. The software protocols and physical connection between the GGSN and the SGSN, are defined by the Gn interface standard. One or more physical IP ports on the GSN may be associated with the Gn interface. The GPRS Tunnelling Protocol (GTP) operates over UDP/IP to provide both signalling (control) and data transfer functions between two GSNs (see Figure 4-11). The CommHub provides high bandwidth connectivity between the GSN nodes.
HLR
Gr
CommHub
Gi
Gn
BSS BTS BSC PCU Gb SGSN
Gi
Gn
GGSN Gi PDN TE
Ga Gp
Ga
Other PLMN
Figure 4-11 The Gn interface
3rd May 01
419
Gn interface
GPRS-300-101
Gn protocol stack
Figure 4-12 shows the protocol stack for the Gn interface.
Gn
GTP UDP IP L2 L1
GTP UDP IP L2 L1
SGSN
GGSN
Figure 4-12 Gn protocol stack SGSN-to-GGSN
GTP
The GPRS Tunnelling Protocol (GTP) tunnels user data and control signalling between GGSN and SGSN in the GPRS backbone network. It allows multiprotocol packets to be tunnelled through the GPRS backbone network between GSNs. All Point-to-Point (PTP), Packet Data Protocol (PDP) PDUs are encapsulated by the GPRS Tunnelling Protocol. GTP defines both signalling (control) and transmission (data) transfer functions. In the signalling plane, GTP specifies a tunnel control and management protocol which allows the SGSN to provide GPRS network access for a MS. Signalling is used to create, modify and delete tunnels. In the transmission plane, GTP uses a tunnelling mechanism to provide a service for carrying user data packets. The choice of path is dependent on whether or not the user data to be tunnelled requires a reliable link. GTP operates over the UDP/IP stacks on the Gn interface. The GTP protocol is implemented only by SGSNs and GGSNs. No other systems need to be aware of GTP. GPRS MSs are connected to an SGSN without being aware of GTP. GTP is specified in GSM 09.60.
UDP, IP and L1/L2

For a description of UDP, IP, and L1/L2see Ga interface.
420
3rd May 01
GPRS-300-101
Gn interface
Gn signalling PDUs
GTP provides the following signalling Gn PDUs: S S S S S S S S S S S S S ECHO REQUEST. ECHO RESPONSE. CREATE PDP CONTEXT REQUEST. CREATE PDP CONTEXT RESPONSE. UPDATE PDP CONTEXT REQUEST. UPDATE PDP CONTEXT RESPONSE. DELETE PDP CONTEXT REQUEST. DELETE PDP CONTEXT RESPONSE. ERROR INDICATION. SGSN CONTEXT REQUEST. SGSN CONTEXT RESPONSE. SGSN CONTEXT ACKNOWLEDGE. T-PDU.
3rd May 01
421
Gp interface
GPRS-300-101
Gp interface
Introduction
This section includes: S S S Gp description. Gp protocol stack. Gp signalling PDUs.
The Gp interface is defined in compliance with GSM 09.60.
Gp description
The Gp interface allows GPRS subscribers to roam between different GSM networks by enabling network services between independent co-operating GPRS PLMNs. This interface communicates between the SGSN in one PLMN and the GGSN in the other PLMN (see Figure 4-13). The inter-PLMN functions provided by the Gp interface are routeing and leased-line security.
HLR
Gr CommHub
Gi Gn Gi
BSS Gb BTS BSC PCU SGSN
Gn GGSN Gi
PDN
TE
Ga
Gp
Ga
Other PLMN
Figure 4-13 The Gp interface

422
3rd May 01
GPRS-300-101
Gp interface
Gp protocol stack
Figure 4-14 shows the protocol stack for the Gp interface. This is identical to the Gn protocol stack but, whereas Gn enables communication within one PLMN, Gp enables communication between two different PLMNs.
Gp
GTP UDP IP L2 L1
GTP UDP IP L2 L1
SGSN
GGSN in External PLMN
Figure 4-14 Gp protocol stack PLMN-to-PLMN For a description of the protocols in the Gp protocol stack, see Gn interface.
Gp signalling PDUs
GTP provides the following Gp signalling PDUs: S S S S S S S S S S S S S ECHO REQUEST. ECHO RESPONSE. CREATE PDP CONTEXT REQUEST. CREATE PDP CONTEXT RESPONSE. UPDATE PDP CONTEXT REQUEST. UPDATE PDP CONTEXT RESPONSE. DELETE PDP CONTEXT REQUEST. DELETE PDP CONTEXT RESPONSE. ERROR INDICATION. SGSN CONTEXT REQUEST. SGSN CONTEXT RESPONSE. SGSN CONTEXT ACKNOWLEDGE. T-PDU.
3rd May 01
423
Gr interface
GPRS-300-101
Gr interface
Introduction
This section includes: S S S S S S S S S Gr description. Gr protocol stack. SS7 Message Transfer Part Level 1 (MTP1). SS7 Message Transfer Part Level 2 (MTP2) SS7 Message Transfer Part Level 3 (MTP3) Signalling Connection Control Part (SCCP). SS7 Transaction Capabilities Application Part (TCAP). Mobile Application Part (MAP). Gr signalling PDUs.
The Gr interface is defined in compliance with GSM 09.02.
Gr description
The Gr interface provides connectivity between an SGSN and an HLR. The interface connects an SGSN to an HLR using common SS7 physical links which terminate at a remote Signalling Transfer Point (STP). This provides access to all nodes in the SS7 network, including the Home Location Registers (HLRs) of both local and foreign PLMNs. The HLR is the main data store for GPRS subscriber information. It is a large, permanent database that contains the list of subscribers with the services and service levels available to each subscriber. The HLR does not retain contexts. These are deleted when a mobile detaches from the network.
424
3rd May 01
GPRS-300-101
Gr interface
SS7 load balancing

SS7 link load balancing and sharing provides a higher link availability for the Gr interface, thus overall network availability is enhanced. When configuring this feature in the GSN, one pair of DS0 links are configured on two different E1 physical ports on the same SS7 card, providing the redundant DS0 link. Signalling traffic between the SGSN and the HLR are load shared between the configured pairs of the DS0 links. The load shared traffic is also balanced automatically by the SGSN software.
HLR
Gr
CommHub
Gi Gn BSS BTS BSC PCU Gi
Gb SGSN
Gn GGSN Gi
PDN
TE
Gp
Ga
Ga
Other PLMN
Figure 4-15 The Gr interface
3rd May 01
425
Gr interface
GPRS-300-101
Gr protocol stack
Figure 4-16 shows the protocol stack for the Gr interface.
Gr
MAP TCAP SCCP MTP3 MTP2 MTP1
MAP TCAP SCCP MTP3 MTP2 MTP1
SGSN
HLR
Figure 4-16 Gr protocol stack
MTP1
MTP1 defines the physical and electrical characteristics of the signalling links of the SS7 network. Signalling links use DS-0 channels and carry raw signalling data at a rate of 56 kbps (T1) or 64 kbps (E1).
MTP2
MTP2 provides link-layer functionality. It ensures that the two end points of a signalling link can exchange signalling messages reliably. It incorporates capabilities such as error checking, flow control, and sequence checking.
MTP3
MTP3 extends the functionality provided by MTP2 by providing network layer functionality. MTP3 ensures that messages can be delivered between signalling points across the SS7 network regardless of whether they are directly connected, even if the signalling links and signalling transfer points fail. The protocol includes the functions and procedures necessary both to inform the remote parts of the signalling network of the consequences of a fault, and to reconfigure the routeing of messages through the signalling network. It also includes capabilities such as node addressing, routeing, alternate routeing, and congestion control. Collectively, MTP2 and MTP3 are referred to as the Message Transfer Part (MTP). MTP is responsible for the reliable transport of signalling messages across the SS7 network.
SCCP
SCCP provides enhancements to MTP3 by providing connectionless and connection-oriented network services, and address translation capabilities. The SCCP enhancements to MTP provide a network service equivalent to the OSI Network layer 3. SCCP provides two major services that are not available in the MTP application addressing and incremental routeing.
426
3rd May 01
GPRS-300-101
Gr interface
Application addressing
SCCP is able to address applications within a signalling point. The MTP can only receive and deliver messages from a node as a whole; it does not deal with software applications within a node. While MTP network-management messages and basic call-setup messages are addressed to a node as a whole, other messages are used by separate applications (referred to as subsystems) within a node. Examples of subsystems are 800 call processing, calling-card processing, Advanced Intelligent Network (AIN), and Custom Local-Area Signalling Services (CLASS) services (for example, repeat dialling and call return). The SCCP allows these subsystems to be addressed explicitly.
Incremental routeing
SCCP is able to perform incremental routeing using Global Title Translation (GTT). GTT frees originating signalling points from the burden of having to know every potential destination to which they might have to route a message. A switch can originate a query, for example, and address it to an STP along with a request for GTT. The receiving STP can then examine a portion of the message, make a determination as to where the message should be routed, and then perform the routeing. For example, calling-card queries (used to verify that a call can be properly billed to a calling card) must be routed to a Service Control Point (SCP) designated by the company that issued the calling card. Rather than maintaining a nationwide database detailing where such queries should be routed (based on the calling-card number), switches generate queries addressed to their local Signalling Transfer Points (STP). The STPs, using GTT, select the correct destination to which the message should be routed. STPs must maintain a database that enables them to determine where a query should be routed. GTT effectively centralizes the problem and places it in a node (the STP) that has been designed to perform this function. In performing GTT, an STP does not need to know the exact final destination of a message. It can, instead, perform intermediate GTT, in which it uses its tables to find another STP further along the route to the destination. That STP, in turn, can perform the final GTT, routeing the message to its actual destination. Intermediate GTT minimizes the need for STPs to maintain extensive information about distant nodes. GTT is also used at the STP to share the load between peer SCPs in both normal and failure scenarios. In these cases, when messages arrive at an STP for final GTT and routeing to a database, the STP can select from among the available redundant SCPs. It can select an SCP on either a priority basis (referred to as primary backup) or a load basis where the load is equalized across all available SCPs (referred to as load sharing). In the GPRS implementation, GTT is performed on the International Mobile Subscriber Identity (IMSI) to determine the SS7 point code of the HLR. This function can be performed at the SGSN, the STP, or both (for example, partial GTT).
3rd May 01
427
Gr interface
GPRS-300-101
TCAP
TCAP defines the messages and protocol used to communicate between applications (deployed as subsystems) in nodes. It is used for database services such as calling card, 800, and switch-to-switch services including repeat dialling and call return. TCAP enables the deployment of advanced intelligent network services by supporting the non-circuit related information exchange between signalling points using the SCCP connectionless service. A TCAP message is composed of two sublayers; the transaction portion which controls and manages the exchange of information between the application entities, and the component portion which contains the actual dialogue associated with remote operation. TCAP messages use SCCP for transport because they must be delivered to individual applications within the nodes they address. The TCAP packet types are: S S S S S S S Unidirectional. Query with permission. Query without permission. Response. Conversation with permission. Conversation without permission. Abort.
MAP
MAP protocol controls the mapping of Logical Link Control (LLC) frames onto the GSM physical channel. MAP enables entities within the same PLMN to communicate with each other and with different PLMNs. To perform this function, MAP uses the TCAP and the connectionless classes (0 or 1) of SCCP. MAP initiates different operations and accepts the return of results or the return of application-specific errors. Extensions to the MAP protocol handle GPRS requirements. New MAP variants support the Gr interface in accordance with GSM 09.02. MAP provides the following services: S S Supports Mobility Management (MM) functions such as location registration and cancellation, location area update, MS deregistration, and identification. Supports basic services such as retrieval of subscriber data during call set-up, MS page/search, access management, handover to new cell, purge, authentication, and security management. Provides operation and management-related functions such as fault recovery.
428
3rd May 01
GPRS-300-101
Gr interface
Gr signalling PDUs
MAP provides the following Gr signalling PDUs: S S S S S S S MAP_CANCEL_LOCATION. MAP_PURGE_MS. MAP_SEND_AUTHENTICATION_INFO. MAP_UPDATE_GPRS_LOCATION. MAP_RESET. MAP_ACTIVATE_TRACE_MODE. MAP_DEACTIVATE_TRACE_MODE.
3rd May 01
429
Gc interface alternative (Gn/Gr)
GPRS-300-101
Gc interface alternative (Gn/Gr)

Introduction
This section provides the following information about Motorolas alternative to the Gc interface: S S Gn/Gr description. Gn/Gr protocol stacks.
Gn/Gr description
Gc is an optional GPRS interface that is not currently supported. In this release traffic between the GGSN and HLR is routed via the SGSN using the Gn and Gr interfaces. The GTP and MAP-based GGSN-to-HLR signalling plane (Gc alternative) uses GTP to tunnel signalling messages between the GGSN and the SGSN in the GPRS backbone network. The Interworking function in the SGSN provides interworking between GTP and MAP for the GGSN-to-HLR signalling.
Gn/Gr protocol stacks

Figure 4-17 shows the protocol stack for the GGSN-to-HLR signalling plane across the Gn and Gr interfaces.
Gn Interworking MAP GTP GTP TCAP MAP Gr
TCAP
UDP
UDP
SCCP
SCCP
IP
IP
MTP3
MTP3
L2
L2
MTP2
MTP2
L1
L1
L1
L1
GGSN
SGSN
HLR
Figure 4-17 Gr/Gn (Gc alternative) protocol stack For a description of each protocol in Figure 4-17, see Gn interface and Gr interface.
430
3rd May 01
Chapter 5
Network access and structure
3rd May 01
GPRS-300-101
ii
3rd May 01
GPRS-300-101
Chapter 5 Network access and structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN network structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN backbones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS network structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS centralized system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS backbone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transparent access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-transparent access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributed access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN domain names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Domain name structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN network management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLMN address pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static and dynamic IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal and external address assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Address Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
51 51 51 52 52 52 53 54 54 54 55 55 57 57 57 58 58 59 59 510 510 510 511 511 511 511 512 513 513
3rd May 01
iii
GPRS-300-101
iv
3rd May 01
GPRS-300-101
Chapter overview
Chapter overview
This chapter describes the GPRS network structure and user access to the network.

This chapter is divided into the following sections: S S S S S Public Land Mobile Network (PLMN) network structure. GPRS network structure. Subscriber access. PLMN domain names. PLMN addresses.
3rd May 01
51
PLMN network structure
GPRS-300-101

Introduction
This section provides information on the structure of a Public Land Mobile Network (PLMN) including: S S PLMN description. PLMN backbones.
PLMN description
A PLMN is a network that provides land mobile communication services to the public. A PLMN is identified by its country ID and network ID. Internetworking is required to enable communication between a Mobile Station (MS) and a fixed system. A GSM PLMN provides service in the GSM-allocated frequency bands and according to the GSM specifications. A PLMN is composed of multiple GPRS Network Operators (GNOs) connected to each other and to other subsystems over long haul links (for example, the BSS and support subsystems). The traffic is carried via E1 trunks. Figure 5-1 shows a PLMN network.
PLMN Network
GNO 1
GNO 2
GNO 3
Complex A1
Complex A2
Complex B1 Complex B2
Complex C1 Complex C2
Chassis 1 Chassis 2 Card 1 Card 2 Card 3 Card 4 Card 5
Chassis 4 Chassis 3
Card 7 Card 6
Figure 5-1 PLMN network

52
3rd May 01
GPRS-300-101
PLMN backbones
Functionally, the PLMN network is interconnected via the following three backbones: S The IP WAN backbone carries all intra-PLMN IP traffic between site networks over long haul WAN links, including the following: S Gn traffic between a GSN (SGSN) in one complex and a GSN (GGSN) in a different complex. Infrastructure management traffic between a GSN, a remote OMC-G and a remote Billing System. Subscriber management traffic between a GSN and a support subsystem.
The Frame Relay (FR) backbone carries FR traffic for the Gb interface, between the Digital Access and Cross Connect System (DACS) at the site network and the Packet Control Unit (PCU) at the Base Station System (BSS). The Signalling System 7 (SS7) backbone carries all the SS7 traffic between PLMN SS7 nodes and the GSN. Specifically, this backbone carries Gr (MAP) traffic between the GSN and Home Location Register (HLR).
3rd May 01
53
GPRS network structure
GPRS-300-101

Introduction
This section describes the structure of the GPRS network, including: S S S GPRS centralized system. Site network. GPRS backbone.
GPRS centralized system

A GPRS PLMN provides mobile data service in the GSM-allocated frequency bands and according to the GSM specifications. In this release, Motorolas GPRS is a centralised system with GSN equipment located at a small number of large central sites to service an entire network coverage area. Figure 5-2 illustrates a centralized configuration using three large GSN sites serving the network.
Internet
SGSN/GGSN
SGSN/GGSN
SGSN
BSS BSS BSS BSS
BSS
BSS
BSS
BSS
Figure 5-2 Centralized GPRS system
54
3rd May 01
GPRS-300-101
Site network
A Site network is a GSN site composed of multiple GSNs connected together on E1 trunks. A GSN site is identified by a name. Functionally, the GSN site is interconnected via the following backbones: S The IP LAN backbone carries all intra-site IP traffic between GSNs at a site. It also carries traffic to any collocated servers and management stations. Specifically, the IP LAN backbone carries the following: Gn traffic between a GSN (the SGSN) and another collocated GSN (GGSN). Infrastructure management traffic between a GSN and a collocated OMC-G, and a collocated billing system. Subscriber management traffic between a GSN and a collocated server.
The traffic on the IP LAN backbone is carried on multiple 100 BASE-T Ethernet links. S The DACS backbone carries the E1 traffic terminating at a given site. Specifically, this backbone cross-connects the following traffic: Gb (BSSGP) traffic between GSN and BSS. Gr (MAP) traffic between GSN and HLR.
GSN Complex
A GSN Complex is composed of multiple GSN subsystem components (SGSN, GGSN, CG and ISS) connected to a CommHub (LAN switch). Physically, these GSN Complexes may be collocated with other GSN Complexes and accessed using the LAN backbone. The GSN Complexes may also be remotely located, whereby access is via other GSN Complexes using a WAN interface.
Internet access network

An Internet access network provides access to the Internet, an Intranet and an ISP. This network is connected to the GSN Complex.
GPRS backbone
The GPRS backbone enables the GPRS network operator to provide GPRS services, switching, billing and other network maintenance operation within the GPRS network. The backbone interface also performs the tunnelling and routing, thereby acting as a central connection point for all communication within GSN elements and the outside network.
Intra-PLMN backbone
Motorolas GPRS uses an intra-PLMN backbone (see Figure 5-3) to allow GGSNs and SGSNs within the same PLMN to communicate with each other. The intra-PLMN backbone is a private IP network for GPRS data and signalling where access control is applied for a specific level of security. The GPRS backbone uses IP as the transport mechanism. The CommHub provides the basic switching at the IP level. All intra-GSN Complex traffic is provided through the CommHub. To provide a wide range of GPRS data connections, each GSN node communicates with many other peer GSNs. The IP backbone reduces the number of physical interfaces and channels that are required to be supported by the GSN node.
3rd May 01
55
GPRS-300-101
Inter-PLMN backbone
The inter-PLMN backbone provides connectivity between one GPRS PLMN and another GPRS PLMN. The inter-PLMN backbone network is selected through a roaming agreement. In this release, the inter-PLMN backbone is a leased line.
Packet Data Network
Gi
Inter-PLMN Backbone (E1 and leased lines)
Gi
Gp
Gp
GGSN
GGSN
IntraPLMN Backbone
IntraPLMN Backbone
SGSN
SGSN
SGSN
PLMN A
PLMN B
Figure 5-3 Intra- and inter-PLMN backbone networks
Linking to external PDNs

The gateway IP router function is also used to route user data and control messages between the GGSNs and any external IP routers or hosts. The CommHub implements the inter-domain IP routing protocols and is used to provide increased fanout capability between the GGSN and external network gateways. It acts only as an IP network relay. The gateway IP router is also used to perform some IP network security functions, such as packet address filtering, so that only packets addressed to an MS subnetwork are accepted. Packets directly addressed to one of the GSNs or to some other IP subnetwork are discarded. This prevents the gateway IP router from being used to directly access the GSNs or as a relay between two external (non-GPRS) IP networks.
56
3rd May 01
GPRS-300-101
Subscriber access
Subscriber access
Introduction
Network access is the means by which a subscriber is connected to a telecommunication network in order to use the services and/or facilities of that network. An access protocol is a defined set of procedures that enables the subscriber to employ the services and/or facilities of the network. Every GPRS subscriber is a GSM subscriber requiring a Subscriber Identification Module (SIM) card for authentication. A subscriber may also be an IP subscriber requiring a username and password combination for additional authentication. A subscriber can have managed or unmanaged access. Managed access is available for customers who use a RADIUS server and these customers can be billed for individual service. Unmanaged access depends upon GSM subscriber management procedures and it may not be possible to bill customers for individual services. Subscriber network access occurs from the mobile side of the GPRS network. The fixed network interface may support multiple access protocols to external data networks, for example IP. The set of access protocols to be supported is determined by the PLMN operator. Individual PLMN administrators may require specific access-control procedures in order to limit the set of users permitted to access the network, or to restrict the capabilities of individual subscribers, for example by limiting the type of service available to a subscriber. Subscribers may have one of the following types of access: S S S Transparent. Non-transparent. Distributed.
Transparent access
Access is transparent when a subscriber does not sent any authentication request information at PDP context activation, and the GGSN does not take part in the user authentication and authorization process. Transparent access on the Gi interface allows the GPRS network to interface with an external Packet Data Network (PDN) which is defined by the Gi interface standard. This service enables a GPRS subscriber to obtain a dynamic IP address locally to gain access to a PDN. Transparent access enables a GPRS network to provide network services that reside outside the Gi interface. These services may include: S S S S S Information services. Financial services. Accessing external servers. ISP firewalls. Domain Name Service (DNS).
3rd May 01
57
Subscriber access
GPRS-300-101
Non-transparent access
Access is non-transparent if a separate authentication and authorization is required at the GGSN before a subscriber can be given access to the customers network by the GGSN. The non-transparent access mode allows an MS to connect to the Internet, an Intranet or ISP for services such as email and DNS. This service includes: S User authentication. With non-transparent access, the MS sends authentication request information at PDP context activation and the GGSN forwards this information to a RADIUS server during the user authentication/authorisation process. S Dynamic IP addressing. This feature allows GPRS subscribers to retrieve dynamic IP addresses from an external DHCP server. The authentication and addressing functions are provided by the RADIUS protocol and Dynamic Host Configuration Protocol (DHCP).
Distributed access
Access is distributed if the subscriber can access different GSN sites using the same subscriber identifier. Figure 5-4 shows distributed access in a GPRS network.
Figure 5-4 Distributed access

58
3rd May 01
GPRS-300-101
PLMN domain names
PLMN domain names

Introduction
This section describes the PLMN domain name structure illustrated in Figure 5-5 including: S S S Domain name structure. PLMN servers. PLMN network management.
World
GPRS net com mccxxx aol org...
Internet Domains
mncxx
Local APNs Private

PLMN Vancouver Toronto com
Standard APNs
net aol org...
PLMN Network
Toronto Vancouver
APN Extensions
Figure 5-5 PLMN network view
3rd May 01
59
PLMN domain names
GPRS-300-101
Domain name structure

The PLMN is identified by the GPRS network ID and the GPRS country ID. For network access, the GPRS PLMN is identified by the following domain name: mncxx.mccxxx.gprs where, xxx and xx are substituted by the assigned numbers. Within this domain, there are three main sub-domains: S Customers with Internet domain names. These are identified by their top level domain on the Internet. For customers with these Internet domain names, the remaining structure mirrors the Internet domain name structure. Customers without Internet domain names. These are identified by domain private. PLMN equipment. These are identified by the domain plmn.
S S
While the GPRS domain names are mirrored from Internet domain names to construct a globally unique customer ID, these name properties are not related to their Internet name properties. The relationship between an Internet domain name and a GPRS domain name is incidental. An additional hierarchical level is added at the lowest level of the customer domain. This level is identified by the site at which this customer has a Gi interface, and consists of Access Point Names (APNs). An APN is used by a PLMN operator to identify IP access points connected to a GPRS system. An APN is also a DNS name resolved by the SGSN during a PDP context activation procedure. For example, if an Internet Service Provider (ISP) were to have Gi interfaces in both Vancouver and Toronto, its APNs are as follows (APNs may or may not include the trailing operator ID mncxx.mccxxx.gprs): S S S isp.com.mncxx.mccxxx.gprs van.isp.com.mncxx.mccxxx.gprs tor.isp.com.mncxx.mccxxx.gprs
PLMN servers
The PLMN may contain servers to assist in the management of IP subscribers and IP addresses. A server managed by the PLMN includes one set per PLMN, and logically belongs at the OMC-G with network and subscriber management functions. The Network Access Server (NAS), RADIUS, internal DNS and DHCP servers are run, managed and controlled by the customer. These servers must be accessible from the public Internet or from the customer links.
PLMN network management

The OMC-G manages all PLMN network management functions including planning, configuration, fault detection, diagnostics, performance and security.
510
3rd May 01
GPRS-300-101
PLMN addresses
PLMN addresses
Introduction
This section describes types of PLMN addresses and how the network uses addresses, including: S S S S S PLMN address pools. Types of addresses. Static and dynamic IP addresses. Internal and external address assignment. Network Address Translation (NAT).
PLMN address pools

A service provider requires the following three address pools: S S S Infrastructure Pool A non-contiguous pool of 8-bit block Classless Inter-Domain Routeing (CIDR) addresses for infrastructure equipment. PLMN Pool A non-contiguous pool of 16-bit (or larger) block CIDR addresses for assignment to customers. IP Pool An optional non-contiguous pool of 8-bit block CIDR address that is exposed to the Internet.
The IP pool must contain public IP addresses to prevent collisions with a customers internal addresses. The PLMN pool can be a private address space. Where Internet access is required, a NAT with IP Pool addresses is used. IP pool addresses are public IP addresses with Public IP access. They are used for NAT access from PLMN pool addresses. These addresses are recommended for distribution as follows: S S S One class C address from IF pool per complex. One class C address from IP pool per complex. Four pools of class B addresses from PLMN pool per complex, with further subnetting of 11-bits to allow five subnetted pools per GTP function.
Types of addresses
Private IP address
The Internet Corporation for Assigned Names and Numbers (ICANN) has reserved the following three blocks of the IP address space for private Internets: 10.0.0.0 to 10.255.255.255 172.16.0.0 to 172.31.255.255 192.168.0.0 to 192.168.255.255 These addresses are not guaranteed to be unique and for this reason, their usage should be restricted to private domains.
3rd May 01
511
PLMN addresses
GPRS-300-101
Public IP address
Any IP Address that has been registered with ICANN is the public IP address. This address should not conflict with other IP users.
Public access to an IP address

A public IP address does not imply that it is accessible from the public Internet. However, if access is provided to it then there would be no conflict. All PLMN addresses should not be accessible from the Internet or subscribers, for security reasons.
Customer addresses
A customer requires the following two address pools: S S CS pool a pool of 8-bit to 11-bit CIDR addressable blocks assigned to subscribers of this customer. CIP pool a non-contiguous pool of single to 8-bit block CIDR addressable public IP addresses assigned to this customer, and accessible from the public Internet. CS pools map onto blocks and CIP Pools may (if used) map onto links.
The address pools are related to PLMN pools as follows: S S S CS pools can be extracted from PLMN pool. CS pools can be extracted from customers public IP addresses. CS pools can be extracted from customer private addresses, with the restriction that customer must take the responsibility to route private addresses to and from the CH link to which this address is mapped. CIP pools may be extracted from IP pool. CIP pools may be extracted from the customers own address, whereby the customer takes responsibility for routeing those packets to and from the CH links to which they map.
S S
Static and dynamic IP addresses

An IP address may be assigned at the time of installation or the time of initial configuration. This address is static since it cannot be used when the host (to whom this address has been assigned) is not operational. While this is a reasonable solution for hosts that are operational most of the time or whose number is small, scarce resources are under-utilized if millions of subscribers are assigned addresses that are not being used. Hence, the address is assigned only for the operational life of the host and such use of IP addresses is considered dynamic. For GPRS, all PLMN entities have static IP addresses. Subscriber addresses may be static or dynamic.
Static address management

Management of static addresses must be successfully performed at the time the host is initially configured. This assignment is performed to ensure that the packets are routed correctly. No other overhead exists once the assignment is complete.
Dynamic address management

Dynamic addresses need to be assigned when an IP access is initiated and released when an IP access is closed. Further assignment is limited by routeing requirements.
512
3rd May 01
GPRS-300-101
PLMN addresses
Internal and external address assignment

PLMN internal address assignment
Address assignment selected by the PLMN is considered internal. The overhead for managing this address assignment is dependent upon the implementation. For GSN implementation, the overhead is at the time of network configuration only.
PLMN external address assignment

Address assignment selected by the customer is considered external, and is managed via the DHCP. The overhead for managing this address assignment is dependent upon DHCP requirements. At the time of customer configuration, acceptable addresses must be negotiated. During use, this control must be exercised using DHCP. The address lease must be renewed periodically.
Network Address Translation

NAT enables a network operator to configure the mapping of an IP address from an external IP address to an internal IP address, and vice versa. The address translation is performed by the CommHub at the Gi interface through the OMC-G administration platform. By providing this feature, a network operator can structure MS IP addresses independent of the external IP network address structure. This provides the flexibility for address assignment. All IP addresses coming from the PDN to mobile termination are translated from an external IP address to an internal IP address within the GPRS network. This allows the GPRS network to configure their IP address independent from the external network. To minimize the need for public IP addresses, the PLMN may implement NAT for its own PLMN pool or for the customer address pools, or both. For GSN implementation, the expected compression of an IP address is as much as 1000 to 4000 times. The software on the GGSN provides NAT functionality to reduce the number of address classes assigned by the Internet Assigned Numbers Authority (IANA). This allows the reuse of routable address classes by translating non-routable Intranet address schemes into routable, unique address schemes. Private address networks are then able to access other IANA-registered networks without registration of private Intranet subnet addresses. In this way, renumbering of current address schemes to support Internet host system requirements is not required. The NAT converts and registers private Intranet addresses before packets are forwarded to a public Internet. The NAT router is the conversion point for translation of addressing schemes.
3rd May 01
513
PLMN addresses
GPRS-300-101
514
3rd May 01
Chapter 6
Mobility and session management
3rd May 01
GPRS-300-101
ii
3rd May 01
GPRS-300-101
Chapter 6 Mobility and session management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of chapter content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . State transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . State timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attach procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detach procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purge procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location update description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-SGSN routeing area update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-SGSN routeing area update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Insert subscriber data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete subscriber data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic roaming management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Roaming attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HGGSN PDP context activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Roaming detach and purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transparent roaming RAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility management security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User identity confidentiality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Session management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet data protocol states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static and dynamic PDP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP context activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP context deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other mobility-related functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet routeing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encapsulation and tunnelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GRE tunnelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Relay function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V.42bis data compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User-selectable APN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quality of Service (QoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
61 61 61 62 62 62 64 65 67 67 67 68 610 611 611 611 612 612 613 614 614 614 614 615 615 616 617 618 619 620 620 620 620 621 621 621 622 623 623 625 625 625 626 626 627 627 627 628 628
3rd May 01
iii
GPRS-300-101
iv
3rd May 01
GPRS-300-101
Overview of chapter content
Overview of chapter content

This chapter describes the Mobility Management and Session Management functions that enable a GPRS system to track the current location of a Mobile Station (MS) and determine the network node to which a message is to be forwarded.

This chapter describes: S S S S S S S S Mobility states. Mobility functions. Location management. Subscriber management. Basic roaming management. Mobility management security. Session management. Other mobility-related functions. NOTE This release of Motorolas GPRS supports Class C MS operations only.
3rd May 01
61
Mobility states
GPRS-300-101
Mobility states
Introduction
This section describes the Mobility Management (MM) functions that enable a GPRS system to track the current location of a MS within the Public Land Mobile Network (PLMN). This section describes: S S S Mobility states. State transitions. State timers.
Mobility states
GPRS mobility management can be in one of three states: IDLE, STANDBY, or READY. Movement from one state to the next is dependent on the current state and the event concerned. Timers monitor the duration of each state.
IDLE state
In GPRS IDLE state, the subscriber is not attached to the GPRS mobility management function but the MS may receive Point-To-Point Multicast (PTM-M) transmissions. Point-To-Point (PTP) and Point-To-Multipoint Group (PTM-G) data transfers to and from the MS and subscriber paging are not possible in the IDLE state. In addition, the MS and SGSN do not hold MM contexts in the IDLE state and subscriber-related mobility management procedures are not performed.
62
3rd May 01
GPRS-300-101
Mobility states
STANDBY state
In STANDBY state, the subscriber is attached to the GPRS mobility management function. The MS and SGSN have established MM contexts for the subscriber International Mobile Subscriber Identity (IMSI). The MS may receive Point-to-MultipointMulticast (PTM-M) and PTM-G data. Pages for PTP or PTM-G data or signalling information may be received. It is also possible to receive pages for the Coding Scheme (CS) services via SGSN. PTP data reception and transmission, and PTM-G data transmission, are not possible in this state. The MS performs GPRS Routeing Area (RA) and GPRS cell selection and reselection locally. The MS executes mobility management procedures to inform the SGSN when it has entered a new RA. The MS does not inform the SGSN on the change of cell in the same RA. Therefore, the location information in the SGSN MM context contains only the GPRS Routeing Area Identity (RAI) for the MSs in STANDBY state. The MS may initiate activation or deactivation of Packet Data Protocol (PDP) contexts while in STANDBY state. A PDP context is activated before data is transmitted or received for this PDP context. The SGSN may need to send data or signalling information to an MS in the STANDBY state. The SGSN sends a paging request in the routeing area where the MS is located if the Paging Proceed Flag (PPF) is set. When the PPF is cleared, paging is not carried out. The MM state in the MS is changed to READY when the the MS responds to the page, and in the SGSN when the page response is received. The MM state in the MS is changed to READY when data or signalling information is sent from the MS and, accordingly, the MM state in the SGSN is changed to READY when data or signalling information is received from the MS. The MS or the network may initiate the GPRS detach procedure to move to the IDLE state. When the mobile reachable timer expires, the SGSN may perform an implicit detach in order to return the MM contexts in the SGSN to the IDLE state. The MM and PDP contexts may be deleted at this point.
3rd May 01
63
Mobility states
GPRS-300-101
READY state
An MS is in READY state when it has successfully performed a GPRS attach. In READY state, the SGSN MM context corresponds to the STANDBY MM context, extended by the location information for the subscriber on cell level. The MS performs mobility management procedures to provide the network with the actual selected cell. GPRS cell selection and reselection is done locally by the MS, or may optionally be controlled by the network. An identifier of the cell is included in the BSS GPRS Protocol (BSSGP) header of the data packet from the MS. The MS may send and receive PTP Packet Data Units (PDUs) in this state. The network initiates no GPRS pages for an MS in READY state. Pages for other services may be performed via the SGSN. The SGSN transfers downlink data to the Base Station Subsystem (BSS) responsible for the actual GPRS cell of the subscriber. The MS may receive PTM-M and PTM-G data while in READY state and may also activate or de-activate PDP contexts while in this state. Regardless of whether a radio resource is allocated to a subscriber, the MM context remains in the READY state, even when there is no data being communicated. The READY state is supervised by a timer. An MM context moves from READY state to STANDBY state when the READY timer expires. In order to move from READY state to IDLE state, the MS initiates the GPRS detach procedure.
State transitions
Transition from state to state is determined by two factors: the current state of the MS (IDLE, STANDBY, or READY) and the event occurring (for example, GPRS attach). Figure 6-1 shows the state transitions which are described below.
GPRS ATTACH IDLE GPRS DETACH READY PDU TRANSMISSION READY TIMER EXPIRY STANDBY
MM STATE MODEL OF MS
GPRS ATTACH IDLE GPRS DETACH or CANCEL LOCATION READY
READY TIMER EXPIRY STANDBY PDU RECEPTION
IMPLICIT DETACH or CANCEL LOCATION
MM STATE MODEL OF SGSN
Figure 6-1 Functional mobility management state model

64
3rd May 01
GPRS-300-101
Mobility states
Moving from IDLE to READY

GPRS attach: The MS requests access, and a logical link to an SGSN is initiated. MM contexts are established at the MS and SGSN.
Moving from STANDBY to IDLE

Implicit Detach: The MM and PDP contexts in the SGSN return to the IDLE and INACTIVE state. The MM and PDP contexts in the SGSN may be deleted. The GGSN PDP contexts are deleted. Cancel location: The SGSN receives a MAP cancel location message from the HLR, and removes the MM and PDP contexts.
Moving from STANDBY to READY

PDU transmission: The MS sends an Logical Link Control (LLC) PDU to the SGSN, possibly in response to a page. PDU reception: The SGSN receives an LLC PDU from the MS.
Moving from READY to STANDBY

READY timer expiry: The MS and the SGSN MM contexts return to STANDBY state. Abnormal Radio Link Control (RLC) condition: The SGSN MM context returns to STANDBY state in case of delivery problems on the radio interface, or in the case of irrecoverable disruption of a radio transmission.
Moving from READY to IDLE

GPRS detach: The MS or the network requests that the MM contexts return to the IDLE state, and that the PDP contexts return to the INACTIVE state. The SGSN may delete the MM and PDP contexts. The PDP contexts in the GGSN must be deleted. Cancel location: The SGSN receives a MAP cancel location message from the HLR, and removes the MM and PDP contexts.
State timers
READY timer function
The READY timer function maintains the READY timer in the MS and SGSN and controls the time an MS remains in the READY state. The READY timer is reset and begins running in the MS when an LLC PDU is transmitted, and in the SGSN when an LLC PDU is correctly received. When the READY timer expires, the MS and SGSN MM contexts return to STANDBY state. The length of the READY timer must be the same in the MS and SGSN. The initial length of the READY timer must be defined by a default value. Only the SGSN may change the length of the READY timer. It does this by transmitting a new value in the attach accept or Routeing Area Update (RAU) accept. When the READY timer length is set to all ones (binary), the READY timer function is deactivated, that is, the timer no longer runs and the MS remains in the READY state.
3rd May 01
65
Mobility states
GPRS-300-101
Periodic RA update timer function

The periodic RA update timer function monitors the periodic RA update procedure in the MS. The length of the periodic RA update timer is sent in the routeing area update accept or attach accept message. The periodic RA update timer is unique within an RA. Upon expiry of the periodic RA update timer, the MS starts a periodic routeing area update procedure. The periodic RA update procedure (or other appropriate update procedure) starts as soon as the MS returns to GPRS coverage. If the MS is out of the coverage area when the periodic RA update timer expires, the periodic RA update procedure restarts as soon as the MS returns to a cell that supports GPRS. If the MS lost GPRS coverage, but the periodic RA update timer did not expire while out of the coverage area, the MS does not perform the periodic RA update procedure when it returns to a cell that supports GPRS.
Mobile reachable timer function

The mobile reachable timer function monitors the periodic RA update procedure in the SGSN. The mobile reachable timer must be slightly longer than the periodic RA update timer used by the MS. The mobile reachable timer is stopped when the READY state is entered. The mobile reachable timer is reset and started when the state returns to STANDBY. When the mobile reachable timer expires, the SGSN clears the Paging Proceed Flag (PPF). Typically, this causes the SGSN to stop sending GPRS paging or CS paging messages to the MS. PPF is set when the next activity from the MS is detected. When an MS first registers in an SGSN, the PPF is set.
66
3rd May 01
GPRS-300-101
Mobility functions
Mobility functions
Introduction
The mobility functions are: S S S Attach procedure. Detach procedure. Purge procedure.
Attach procedure
An attach procedure is a series of actions that enable an MS to connect (attach) to the network and start using the GPRS service. A subscriber may wish to connect to the GPRS network to access the Internet or a corporate database. GPRS has two types of attach procedures: a standard attach and an extended attach. These methods are described below.
Standard attach
A standard attach occurs when a subscriber wants to access the GPRS network from within the same coverage area that it last used the GPRS service. Each coverage area is associated with a different SGSN. The PLMN becomes aware of the MS when a subscriber first turns on the MS. Once it is turned on, the MS sends the SGSN a request to attach to the GPRS network. If the MS is within the area of the same SGSN to which it was previously attached, the SGSN returns an attach accept. The MS is now in READY state and able to activate PDP contexts. If this is the first time an MS has requested an attach, prior to sending the attach accept, the SGSN constructs a Mobility Management (MM) context for the MS. The MM context is information about the MS that is stored in the SGSN. This information includes the current location of the MS. On the basis of the information in the MM context, the GPRS system is able to transfer data to and from the MS. The SGSN stores the MM context and is able to use it again the next time the MS requests an attach, thereby reducing the time required to perform subsequent attaches. The SGSN retains the MM context until an extended attach is requested.
3rd May 01
67
Mobility functions
GPRS-300-101
Extended attach
An extended attach is required when the coverage area from which an MS is requesting an attach is different from the one it was in the last time it used the GPRS service. In an extended attach, when the SGSN in the new coverage area receives an attach request from an MS, it notifies the HLR of the new location of the MS. The HLR contains administrative information for each subscriber registered in the GPRS network including the current location of the MS and the identity of the last SGSN to which it was attached. When the HLR receives the new location information, it cancels the MM context in the old SGSN and forwards the subscriber data to the new SGSN. The information in the HLR now shows that the MS is associated with the new SGSN. The attach procedure is shown in Figure 6-2.
MS BSS NEW SGSN OLD SGSN GGSN HLR
ATTACH REQUEST IDENTITY REQUEST IDENTITY RESPONSE AUTHENTICATION UPDATE LOCATION CANCEL LOCATION CANCEL LOCATION ACK INSERT SUBSCRIBER DATA INSERT SUBSCRIBER DATA ACK UPDATE LOCATION ACK ATTACH ACCEPT ATTACH COMPLETE
Figure 6-2 Attach procedure
Detach procedure
The detach procedure terminates a connection between an MS and a GPRS network. A detached MS can no longer send or receive data over the network. An MS can be detached from the GPRS network by the SGSN, the HLR or by disconnecting itself. These three methods are described below.
68
3rd May 01
GPRS-300-101
Mobility functions
MS-initiated detach
An MS initiates a detach when a subscriber turns off the MS, either accidentally or because access to the GPRS network is no longer required. The network detects when an MS has been turned off and the SGSN sends the GGSN a request to delete the PDP context. In most cases, when the GGSN acknowledges the request the detach is complete. In some network situations, the SGSN also sends a detach accept to the MS. Figure 6-3 shows an MS-initiated detach.
MS BSS DETACH REQUEST DELETE PDP CONTEXT REQUEST DELETE PDP CONTEXT RESPONSE DETACH ACCEPT SGSN GGSN
Figure 6-3 MS-initiated GPRS detach procedure
Network-initiated detach
The GPRS network can initiate a detach either explicitly or implicitly: S S An explicit detach occurs when the network explicitly requests a detach. In the event of an explicit detach, the SGSN sends a detach request to the MS. An implicit detach occurs when the network detaches the MS without sending a detach request to notify the MS. An implicit detach can be due to the mobile reachable timer expiring, or an irrecoverable radio error causing the logical link to disconnect.
A network-initiated detach can be generated by either the SGSN or the HLR. SGSN-initiated detach An SGSN can initiate a detach for a number of network-associated reasons. When such a situation occurs, the SGSN sends a detach request to the MS. The detach request includes a detach type which indicates whether, after the detach is complete, the MS needs to initiate a new attach with a new PDP context. The SGSN also sends the GGSN a request to delete the PDP context of the MS and the GGSN acknowledges the request. Finally, the MS sends a detach acceptance to the SGSN and the detach procedure is complete. Figure 6-4 shows an SGSN-initiated detach.
3rd May 01
69
Mobility functions
GPRS-300-101
MS
BSS DETACH REQUEST
SGSN
GGSN
DELETE PDP CONTEXT REQUEST DELETE PDP CONTEXT RESPONSE DETACH ACCEPT
Figure 6-4 SGSN-initiated GPRS detach procedure HLR-initiated detach The HLR can initiate a detach for network operation reasons. When the HLR initiates a detach, it immediately requests that the SGSN delete the subscribers MM context and the GGSN delete the subscribers PDP context. When the MM and PDP contexts have been deleted, the SGSN sends a detach request to the MS informing it that it has been detached from the system. The detachment procedure is complete when the MS responds with an acknowledgement. Figure 6-5 shows an HLR-initiated detach.
MS BSS SGSN GGSN CANCEL LOCATION DETACH REQUEST DELETE PDP CONTEXT REQUEST DELETE PDP CONTEXT RESPONSE 5. DETACH ACCEPT CANCEL LOCATION ACK HLR
Figure 6-5 HLR-initiated GPRS detach procedure
Purge procedure
A purge procedure involves the SGSN informing the HLR that it has deleted the PDP context of a detached MS, and the HLR acknowledging the deletion. A purge occurs after each implicit or explicit detach of an MS. The purge procedure is shown in Figure 6-6.
SGSN PURGE MS PURGE MS ACK HLR
Figure 6-6 Purge procedure

610
3rd May 01
GPRS-300-101
Location management
Location management
Introduction
The location management function provides mechanisms for cell and PLMN selection, network knowledge of the routeing area for MSs in STANDBY state, and network knowledge of both the routeing area and cell identity for MSs in READY state. This section includes: S S S S Location update description. Cell update. Intra-SGSN routeing area update. Inter-SGSN routeing area update.
Location update description

The PLMN provides information for the MS to be able to detect when it has entered a new cell or a new RA, and when to perform periodic RA updates. The MS detects that it has entered a new cell by comparing the new cell identity with the cell identity stored in the MM context of the MS. The MS detects that it has entered a new RA by periodically comparing the RAI stored in its MM context with that received from the new cell. The MS considers hysteresis in signal strength measurements. When the MS camps on a new cell, which may be in a new RA, one of the following actions takes place: S S S A cell update. An intra-routeing area update. An inter-routeing area update.
Details about these actions are provided in the following pages. In all cases the MS stores the new cell identity in its MM context. When the MS enters a new PLMN, the MS either performs a routeing area update, or enters IDLE state. Routeing area update request messages are sent unciphered, since in the inter-SGSN routeing area update case, the new SGSN needs to process the request.
3rd May 01
611
Location management
GPRS-300-101
Cell update
A cell update takes place when the MS enters a new cell inside the current RA and the MS is in READY state. When the RA has changed, a routeing area update is executed instead of a cell update. The MS performs the cell update procedure by sending the SGSN an uplink LLC frame of any type that contains the identity of the MS. In the SGSN direction, the BSS adds the cell global identity including Routeing Area Code (RAC) and Location Area Code (LAC) to all BSSGP frames (see GSM 08.18). A cell update is any correctly received and valid LLC PDU carried inside a BSSGP PDU containing a new identifier of the cell. The SGSN records the change of cell of this MS, and further traffic directed towards the MS is conveyed over the new cell.
Intra-SGSN routeing area update

A routeing area update takes place either when a GPRS-attached MS detects that it has entered a new RA, the periodic RA update timer has expired, or a suspended MS is not resumed by the BSS. The SGSN detects that it is an intra-SGSN routeing area update by noticing that it also handles the old RA. In this case, the SGSN has the necessary information about the MS, and there is no need to inform the GGSNs or the HLR about the new MS location. A periodic RA update is always an intra-SGSN routeing area update. If a routeing area update procedure fails a maximum allowable number of times, or if the SGSN returns a routeing area update reject message, the MS enters IDLE state. The intra-SGSN routeing area update procedure is shown in Figure 6-7.
MS BSS ROUTEING AREA UPDATE REQUEST SGSN
ROUTEING AREA UPDATE ACCEPT
ROUTEING AREA UPDATE COMPLETE
Figure 6-7 Intra-SGSN routeing area update procedure
612
3rd May 01
GPRS-300-101
Location management
Inter-SGSN routeing area update

Inter-SGSN handover allows GPRS mobile subscribers to move between two cells serviced by different SGSNs without disrupting the established GPRS sessions. When a GPRS MS on one cell moves in the direction of another cell, it sends an RAU to the new cell. When the SGSN connected to the new cell confirms the new RAU the MS can continue to send data. By providing a continuous session, this feature gives an an improved level of service to subscribers. It enhances the quality of service offered by allowing the MSs to move to another SGSN without disrupting the GPRS session when a handover becomes necessary. Inter-SGSN handover enables GPRS users to deploy applications that require continuing services within a large geographic area. If the RAU procedure fails a maximum allowable number of times, or when the SGSN returns a routeing area update reject (cause) message, the MS enters IDLE state. The inter-SGSN routeing area update procedure is shown in Figure 6-8.
MS BSS NEW SGSN OLD SGSN GGSN HLR
ROUTEING AREA UPDATE REQUEST SGSN CONTEXT REQUEST SGSN CONTEXT RESPONSE
SGSN CONTEXT ACKNOWLEDGE
UPDATE PDP CONTEXT REQUEST UPDATE PDP CONTEXT RESPONSE UPDATE LOCATION CANCEL LOCATION CANCEL LOCATION ACK INSERT SUBSCRIBER DATA INSERT SUBSCRIBER DATA ACK UPDATE LOCATION ACK
ROUTEING AREA UPDATE ACCEPT ROUTEING AREA UPDATE COMPLETE
Figure 6-8 Inter-SGSN routeing area update procedure
3rd May 01
613
Subscriber management
GPRS-300-101
Subscriber management
Introduction
The subscriber management function provides a mechanism to inform the GPRS nodes about changes of the GPRS subscription data for a specific GPRS subscriber. Whenever the GPRS subscription data is changed for a GPRS subscriber in the HLR, and the changes affect the GPRS subscription data stored in the SGSN, the following procedures inform the SGSN of the changes: S S Insert subscriber data. Delete subscriber data.
Insert subscriber data

The insert subscriber data procedure is used to add or modify GPRS subscription data in the SGSN. In addition to the insertion and modification of general GPRS subscription data for the GPRS subscriber, the HLR may request the insertion or modification of one or several new or existing PDP contexts in the SGSN. The insert subscriber data procedure is shown in Figure 6-9.
SGSN INSERT SUBSCRIBER DATA INSERT SUBSCRIBER DATA ACK HLR
Figure 6-9 Insert subscriber data procedure
Delete subscriber data

The delete subscriber data procedure is used to remove GPRS subscription data from the SGSN. In addition to the deletion of general GPRS subscription data for a GPRS subscriber, the HLR may request the deletion of one or several PDP contexts from the SGSN. The delete subscriber data procedure is shown in Figure 6-10.
SGSN DELETE SUBSCRIBER DATA DELETE SUBSCRIBER DATA ACK HLR
Figure 6-10 Delete subscriber data procedure

614
3rd May 01
GPRS-300-101
Basic roaming management

Introduction
An authenticated Class C MS can roam from its Home PLMN (HPLMN) to another cooperating PLMN, called the Visited PLMN (VPLMN), using the GPRS Tunnelling Protocol (GTP) across the Gp interface. The HPLMN and VPLMN have a common agreement regarding subscriptions and tariffs for visiting MSs. The transfer of Call Detail Records (CDRs) from one PLMN to another is supported via the TAP procedure (see GSM 03.60). In this release, Motorolas implementation of inter-PLMN roaming uses leased lines to connect the PLMNs via the E1 ports on the CommHub RSMs (see Figure 5-3 and Figure 6-11). A leased line is a single point-to-point connection reserved by a service provider for a clients sole use. The leased lines provide security for the interface. This section describes: S S S S Roaming attach. Home GGSN (HGGSN) PDP context activation. Roaming detach and purge. Transparent roaming RAU.
HPLMN
HGGSN
RSM
Gi interface PDN
HSGSN GSN Complex HHLR
VHLR Gp interfaces via leased lines on E1 interface
VSGSN
RSM GSN Complex
VPLMN
Figure 6-11 Roaming configuration
3rd May 01
615
GPRS-300-101
Roaming attach
An MS requesting a GPRS attach to a VPLMN is recognized as being from another PLMN by the Visited SGSN (VSGSN). The VSGSN passes the request on to the Home HLR (HHLR). From this point, the procedure follows the standard attach procedure as described in Mobility Functions. The inter-PLMN roaming attach procedure is shown in Figure 6-12.
MS ATTACH REQUEST IDENTITY REQUEST BSS VSGSN HGGSN
IDENTITY RESPONSE
AUTHENTICATION
UPDATE LOCATION
INSERT SUBSCRIBER DATA
INSERT SUBSCRIBER DATA ACK
UPDATE LOCATION ACK
ATTACH ACCEPT
Figure 6-12 Roaming attach procedure
616
3rd May 01
GPRS-300-101
HGGSN PDP context activation

The MS sends a request for PDP context activation to the VSGSN. The DNS resolves the APN into an IP address of the HGGSN. The VSGSN forwards the request to the HGGSN for PDP Context Activation. The PDP context activation to the HGGSN procedure is shown in Figure 6-13.
MS BSS VSGSN HGGSN
ACTIVATE PDP CONTEXT REQUEST CREATE PDP CONTEXT REQUEST
CREATE PDP CONTEXT RESPONSE ACTIVATE PDP CONTEXT ACCEPT
Figure 6-13 HGGSN PDP context activation procedure
3rd May 01
617
GPRS-300-101
Roaming detach and purge

An MS leaves a VPLMN by either requesting to be detached, switching off or by a time-out default when an MS roams outside the VPLMN coverage area without an explicit detach. In any of these situations, the VSGSN sends the HGGSN a request to delete the PDP context. After an MS successfully detaches, the VSGSN sends a purge message to the HHLR. The purge message informs the HHLR that the MM and PDP contexts have been deleted from the VSGSN. In some network situations, the VSGSN also sends a detach accept to the MS. The roaming detach and purge procedure for an MS is shown in Figure 6-14.
MS BSS DETACH REQUEST DELETE PDP CONTEXT REQUEST VSGSN HGGSN HHLR
DELETE PDP CONTEXT RESPONSE
PURGE MS
PURGE MS ACK
Figure 6-14 Roaming detach/purge procedure
618
3rd May 01
GPRS-300-101
Transparent roaming RAU

Transparent roaming Routeing Area Update (RAU) enables MSs to move between the two PLMNs without disrupting the established GPRS sessions. When a GPRS MS in one PLMN moves in the direction of another PLMN, it sends an RAU request to the VPLMN. When the VSGSN confirms the new RAU, the MS can continue to send data. The inter-SGSN routeing area update procedure is shown in Figure 6-15.
MS BSS VSGSN HSGSN HGGSN HHLR
ROUTEING AREA UPDATE REQUEST SGSN CONTEXT REQUEST SGSN CONTEXT RESPONSE
SGSN CONTEXT ACKNOWLEDGE
UPDATE PDP CONTEXT REQUEST UPDATE PDP CONTEXT RESPONSE UPDATE LOCATION CANCEL LOCATION CANCEL LOCATION ACK
INSERT SUBSCRIBER DATA INSERT SUBSCRIBER DATA ACK UPDATE LOCATION ACK
ROUTEING AREA UPDATE ACCEPT ROUTEING AREA UPDATE COMPLETE
Figure 6-15 Transparent roaming RAU
3rd May 01
619
Mobility management security
GPRS-300-101
Mobility management security

Introduction
The security function of MM provides: S S Subscriber authentication. User identity confidentiality.
Subscriber authentication
The procedures for performing subscriber authentication are executed from the SGSN where the authentication triplets are stored. The authentication procedure is shown in Figure 6-16.
MS BSS SGSN HLR
SEND AUTHENTICATION INFO SEND AUTHENTICATION INFO ACK AUTHENTICATION REQUEST AUTHENTICATION RESPONSE
Figure 6-16 Authentication procedure
User identity confidentiality

A Temporary Logical Line Identity (TLLI) identifies a GPRS user. The relationship between the TLLI and IMSI is known only in the MS and the SGSN.
620
3rd May 01
GPRS-300-101
Session management
Session management
Introduction
Session Management determines the network node to which a message is forwarded. It also determines the underlying services used to reach the GSN, using the destination address of the message. The routing function selects the transmission path for the next hop in the route. Data transmission between GSNs may occur across external data networks that provide their own internal routing functions such as Frame Relay (FR) or Asynchronous Transfer Mode (ATM). Session Management has the following states and functions: S S S S Packet data protocol states. Static and dynamic PDP addresses. PDP context activation. PDP context deactivation.
Packet data protocol states

A GPRS subscription contains the subscription of one or more PDP addresses. Each PDP address is described by an individual PDP context in the MS, the SGSN, and the GGSN. Every PDP context exists independently in one of two PDP states. The PDP state indicates whether the PDP address is activated for data transfer or not. All PDP contexts of a subscriber are associated with the same MM context for the IMSI of that subscriber.
INACTIVE state
The INACTIVE state indicates that the data service for a certain PDP address is not activated. The PDP context contains no routeing or mapping information to process PDUs related to that PDP address. No data can be transferred. A subscriber changing location does not cause an update for the PDP context in INACTIVE state even if the subscriber is attached to the GPRS MM. Otherwise, mobile-terminated PTP packets received in INACTIVE state invoke error procedures in the GGSN relevant to the external network protocol; for example, an IP packet is discarded and an Internet Control Message Protocol (ICMP) packet (error notification) is returned to the source of the received packet. Other error procedures may be introduced on the application level, but this is outside the scope of this manual. The MS initiates the movement from INACTIVE to ACTIVE state by initiating the PDP context activation procedure.
3rd May 01
621
Session management
GPRS-300-101
ACTIVE state
In ACTIVE state, the PDP context for the PDP address in use is activated in the MS, SGSN, and GGSN. The PDP context contains mapping and routeing information for transferring PDUs for that particular PDP address between the MS and GGSN. The ACTIVE state is permitted only when the mobility management state of the subscriber is STANDBY or READY. An active PDP context for an MS is moved to the INACTIVE state when the deactivation procedure is initiated (see Figure 6-17). All active PDP contexts for an MS are moved to the INACTIVE state when the MM state changes to IDLE.
ACTIVATE PDP CONTEXT INACTIVE DE-ACTIVATE PDP CONTEXT or MM STATE CHANGE TO IDLE ACTIVE
Figure 6-17 Functional PDP state model
Static and dynamic PDP addresses

PDP addresses can be either static or dynamic: S S Static PDP addresses are permanent addresses assigned to an MS by the Home Public Land Mobile Network (HPLMN) operator. Dynamic PDP addresses are temporary addresses assigned to an MS by the HPLMN operator when a PDP context is activated.
The HPLMN operator defines in the subscription whether a dynamic HPLMN or Visited Public Land Mobile Network (VPLMN) PDP address can be used. For every IMSI, zero, one, or more dynamic PDP address per PDP type can be assigned. For every IMSI, zero, one, or more static PDP addresses per PDP type can be subscribed to. When dynamic addressing is used, it is the responsibility of the GGSN to allocate and release the dynamic PDP address.
622
3rd May 01
GPRS-300-101
Session management
PDP context activation

An MS in STANDBY or READY state can initiate a PDP context at any time. A PDP context is a GPRS connectivity function that enables a virtual connection from an MS to an external network end-point to be established and managed. The internal properties of a PDP context specify the basic requirements of each end-point in the connection. To initiate PDP context activity, an MS sends the SGSN a PDP context activation request along with related data such as the Tunnel Identifier (TID), PDP type, and Network Layer Service Access Point Identifier (NSAPI). The SGSN validates the PDP context request by comparing the received data with the PDP context subscription records. Through this process, it can determine the applicable GGSN address. The SGSN then creates a PDP context request message and sends it to the GGSN. The GGSN returns a create PDP context response message to the SGSN. This message includes routeing data for the exchange of information between the SGSN and the GGSN. When it receives the message from the GGSN, the SGSN sends the MS an activated PDP context acceptance, along with the NSAPI and GGSN address. This completes the PDP context activation procedure and the SGSN is now able to route PDUs between the GGSN and the MS. An MS can issue another request before it receives the accept message for an earlier request to activate or deactivate a PDP context. However, only one PDP context request can be outstanding for every NSAPI. The PDP context activation procedure is shown in Figure 6-18. MS SGSN
ACTIVATE PDP CONTEXT REQUEST CREATE PDP CONTEXT REQUEST CREATE PDP CONTEXT RESPONSE
GGSN
ACTIVATE PDP CONTEXT ACCEPT
Figure 6-18 PDP context activation procedure
PDP context deactivation

PDP context deactivation can be initiated by either the MS or the SGSN. A PDP context contains information relevant only to the attached MS and its session and therefore has no value once the MS is detached.
3rd May 01
623
Session management
GPRS-300-101
MS-initiated PDP context deactivation

When an MS is ready to deactivate PDP context activity, it sends a request to the SGSN. The SGSN then requests the GGSN to delete all PDP contexts for the MS. The GGSN returns a message to the SGSN when the PDP contexts have been deleted. The SGSN then sends a message to the MS accepting the PDP context deactivation. The PDP context deactivation procedure initiated by an MS is shown in Figure 6-19. MS SGSN
DE-ACTIVATE PDP CONTEXT REQUEST DELETE PDP CONTEXT REQUEST DELETE PDP CONTEXT RESPONSE DE-ACTIVATE PDP CONTEXT ACCEPT
GGSN
Figure 6-19 PDP context deactivation initiated by an MS
SGSN-initiated PDP context deactivation

When an SGSN wants to deactivate PDP context activity for a specific MS, it sends a request to the GGSN to delete all PDP contexts for the MS. The GGSN returns a message to the SGSN when the PDP contexts have been deleted. The SGSN then sends an message to the MS which responds by accepting the PDP context deactivation. The PDP context deactivation procedure initiated by an SGSN is shown in Figure 6-20. MS SGSN GGSN
DELETE PDP CONTEXT REQUEST DELETE PDP CONTEXT RESPONSE DE-ACTIVATE PDP CONTEXT REQUEST DE-ACTIVATE PDP CONTEXT ACCEPT
Figure 6-20 PDP context deactivation initiated by an SGSN
624
3rd May 01
GPRS-300-101
Other mobility-related functions

Introduction
This section describes: S S S S S S S S Packet routeing. Encapsulation and tunnelling. GRE tunnelling. V.42bis data compression. User-selectable Access Point Node (APN). Relay function. Packet transmission. Quality of Service.
Packet routeing
Packets can be routed between an MS and an external network and between different MSs using: S Direct access where the packets routed to customers as in any peer-to-peer IP network. This is possible with public IP addresses for subscribers and customers only. Route-based indirect access where the GSN uses a routeing scheme based upon the subscriber IP address and the GGSN onto to which this block is mapped. This scheme may be based upon the APN.
The PDP PDUs are routed and transferred between the MS and the GGSN as N-PDUs. The maximum size of each N-PDU is 1500 octets. When the MS or the GGSN receives a PDP PDU that is not larger than the maximum N-PDU size, the PDP PDU is routed and transferred as one N-PDU. When the MS or the GGSN receives a PDP PDU that is larger than the maximum N-PDU size, the PDP PDU is segmented, discarded, or rejected, depending on the PDP type. The PDP in the MS may limit the maximum size of the PDUs that are routed and transferred for reasons such as MS memory limitations. Between the SGSN and the MS, PDP PDUs are transferred with Sub-Network Dependent Convergence Protocol (SNDCP). Between the SGSN and the GGSN, PDP PDUs are routed and transferred with User Datagram Protocol/Internet Protocol (UDP/IP). GTP transfers data through tunnels. A tunnel is identified by its TID and a GSN address.
3rd May 01
625
GPRS-300-101
Encapsulation and tunnelling

User data is transferred transparently from the MS and the external data networks by a method known as encapsulation and tunnelling. The encapsulation and tunnelling method equips data packets with GPRS-specific protocol information for transfer between the MS and GGSN. This transparent transfer method lessens the requirement for the GPRS PLMN to interpret external data protocols and enables easy introduction of additional interworking protocols for the future. Encapsulation is the addition of address and control information to a data unit for routeing packets within and between the PLMN(s). Decapsulation is the removal of the addressing and control information from a packet to reveal the original data unit. Encapsulation and decapsulation are performed between GSNs, and between the SGSN and the MS. GPRS transparently transports PDP PDUs between external networks and MSs. All PDP PDUs are encapsulated and decapsulated for GPRS routeing purposes. Encapsulation functionality exists at the MS, SGSN, and GGSN. The function allows PDP PDUs to be delivered to, and associated with, the correct PDP context in the MS, the SGSN, or the GGSN. Two different encapsulation schemes are used: one for the GPRS backbone network between two GSNs, and the other for the GPRS connection between SGSN and MS.
GSN-to-GSN encapsulation
Between two GSNs, the GPRS backbone network encapsulates a PDP PDU with a GTP header, and inserts this GTP PDU in a TCP or UDP PDU that again is inserted within an IP PDU. The IP and GTP PDU headers contain the GSN addresses and Terminal Equipment Identifier (TEI) necessary to uniquely address a GSN PDP context.
SGSN-to-MS encapsulation
Between the SGSN and MS, SNDCP encapsulation requires that the MS be attached to GPRS, and that the PDP context activation procedure have been executed. If the GPRS-attach or PDP context activation procedures cannot be executed successfully, uplink-bound PDP PDUs are discarded in the MS. With this type of encapsulation, an SGSN or MS PDP context is uniquely addressed with a Temporary Logical Link Identity (TLLI) and a Network Layer Service Access Point Identifier (NSAPI) pair. A TLLI is derived from the Packet-Temporary Mobile Subscriber Identifier (P-TMSI). A NSAPI is assigned when the MS initiates the PDP context activation function.
GRE tunnelling
GRE enables a virtual point-to-point connection across a public network for multiple protocols. The GRE tunnels IP and non-IP protocols, while IP Security (IPSec) supports IP protocols only. An IP packet is placed within the GRE header, and encapsulated within an IP datagram. When a tunnel is terminated at Customer Provided Equipment (CPE), the customer address space and routeing information remains independent of other customer (or service provider) address space and routeing information. When configured at the router, the GRE tunnel appears as a point-to-point connection.
626
3rd May 01
GPRS-300-101
Relay function
The relay function of a network node transfers the PDP PDUs received from the incoming link to the appropriate outgoing link. At the SGSN and GGSN, the relay function stores all valid PDP PDUs until they are forwarded to the next network node. This maximum holding time is implementation dependent, and can be influenced by the PDP type, the QoS of the PDP PDU, the resource load status, and by buffer conditions. The discarding protects resources from useless transfer attempts, especially the radio resource. Impacts on user protocol operation by a holding time that is too short must be avoided. The SGSN and GGSN relay functions add sequence numbers to PDP PDUs received from SNDCP and from the Gi reference point, respectively. The SGSN relay function may perform resequencing of PDP PDUs before passing the PDP PDUs to SNDCP. The GGSN relay function may perform resequencing of PDP PDUs before passing the PDP PDUs to the Gi reference point.
V.42bis data compression

Data compression is a technique used to compress SNDCP user data. V.42bis is an ITU-T standard that provides data compression as an extension of the V.42 protocol for error correction. The theoretical maximum compression for V.42bis is 4:1. In GPRS, V.42bis provides data compression between an MS and the SGSN for up to 1000 subscribers per SGSN (3,000 per SGSN chassis). The compression function optimises the use of the radio path capacity by transmitting as little of the PDU as possible while preserving the information contained within it. Compression may be performed independently for each PDP context. The compression parameters are negotiated between the MS and the SGSN. V.42bis compression can be negotiated separately for each PDP context.
User-selectable APN
When an MS is attached to a GPRS network, it can choose to use the default APN or to select a different preconfigured APN from a list sent to it by the HLR. The user-selectable APN feature gives an MS the ability to select from this list. An APN is an identifier for a PDN that is configured on, and accessible from, a GGSN. It is used to specify the PDN to which an MS wishes to connect. The APN can be a label or a fully qualified domain name according to DNS naming conventions as specified in GSM 03.03.
3rd May 01
627
GPRS-300-101
Packet transmission
GPRS uses the Point-to-Point Connectionless Network Service (PTP-CLNS) transmission mode. Connectionless-mode transmission is the transmission of a single unit of data from a source Service Access Point (SAP) to another destination SAP without establishing a physical connection. This allows the GPRS service provider to provide network services that do not require end-to-end acknowledgement. These services are usually one-way and point-to-point oriented. PTP-CLNS is ideal for typical bursty packet-based applications such as accessing information stored in a remote data centre (for example, weather reports, traffic reports, or stock quotes), storing and forwarding messages, and handling transaction or telemetry messages. The PTP-CLNS service has the following characteristics: S S No dynamic peer-to-peer agreement is involved in an instance of the service. A single services access is used to present information to the layer providing the connectionless-mode service. This information includes a unit of user data and the information required to deliver the user data such as the destination address, quality of service selection, and options. Each unit of data transmitted is entirely self-contained and can be routed independently.
Connectionless-mode transfer does not: S S S Provide confirmed delivery of Service Data Units (SDUs). Guarantee delivery of SDUs. Guarantee maintenance of SDU sequencing.
Quality of Service (QoS)

The Motorola GPRS system currently supports best effort for the QoS profiles defined in GSM 03.60, Version 6.2.0 (1997). This is achieved through a combination of: S S S S S S Proprietary software. Proportional adaptive scheduling algorithms. Virtual adaptive queuing. Flow control. Admission control. Network transport mechanisms.
A default QoS profile is stored in the HLR and downloaded to the SGSN during an attach procedure. The QoS profile is negotiated between the SGSN and MS at the time of PDP context activation. An MS can request a specific value for each QoS attribute, including the HLR default values. The SGSN negotiates a value for each attribute to match available resources, as well as any limits set within the SGSN.
628
3rd May 01
Chapter 7
GPRS services
3rd May 01
GPRS-300-101
ii
3rd May 01
GPRS-300-101
Chapter 7 GPRS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Charging Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CGF description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDR generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Charging Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lawful Intercept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LI description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LIAN architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LIAN-to-GSN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LI performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LI management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LI security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event and alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load and database management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operator access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Password protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Domain name security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
71 71 71 72 72 73 73 77 710 710 710 711 712 712 712 712 713 713 713 714 714 715 715 716 716 717 717 717 717 718 718 718 718
3rd May 01
iii
GPRS-300-101
iv
3rd May 01
GPRS-300-101
Chapter overview
Chapter overview
This chapter describes the GPRS services that support the administration of a GPRS network.

This chapter describes the following functions performed within the GPRS system. S S S S Charging Function. Lawful Intercept. Network management. GPRS security.
3rd May 01
71
Charging Function
GPRS-300-101
Charging Function
Introduction
A customer is the entity that settles the charges for use of access from the GPRS network. In the simplest case, the customer and the subscriber may be the same entity. More likely, the customer is an Internet Service Provider (ISP) or a corporation and the subscriber is one of its users. This section describes how charging information is generated for use of the GPRS network by a customer, including: S S S Charging Gateway Function (CGF) description. Call Detail Record (CDR) generation. Charging Gateway (CG).
72
3rd May 01
GPRS-300-101
Charging Function
CGF description
The CGF transfers charging information from the Serving GPRS Support Node (SGSN) and Gateway GPRS Support Node (GGSN) to a network operators Billing System (BS)/mediation device. The term BS is used to refer to either a Billing System or a mediation device. The CGF is designed as a centralized separate network element known as the CG. The CG interface to the GSNs uses the GTP Prime (GTP) protocol. The CG collects CDRs from the GPRS Support Nodes (GSNs) and stores them in a persistent memory until they are successfully transferred to the BS. The primary aspects of the CGF are: S S Metering and CDR generation. CG Processing and CDR transferring to the BS.
Metering refers to the measurement of individual CDR metrics in the SGSN and GGSN. For example, the number of uplink and downlink PDU octets transferred, the time of attachment, and the cell ID at the time of activation. CDR generation refers to the gathering of individual CDR metrics into a closed CDR which is then transferred to the CG. CG processing and transfer refers to the processing of CDRs received from the GSNs and then transferring the CDRs to the BS. The architecture of the CG is illustrated in Figure 7-1.
Text SGSN
GTP
OMCG
TELNET
CG
GTP
FTP
BS
GGSN Text Text
RAID
Figure 7-1 Charging Gateway architecture
CDR generation
The GSN continuously collects CDR metrics (charging information) about each MS in its area. When a trigger event occurs (for example, a PDP context deactivation request) the GSN gathers the CDR metrics and forms a closed record. The CDR closure triggers are defined in GSM 12.15. Each closed CDR is transferred to the CG using GTP. Each SGSN and GGSN supports its own GTP interface to the CG. Three types of CDRs are generated: S S S GGSN-CDR (G-CDR). SGSN-CDR (S-CDR). Mobility management-CDR (M-CDR).
3rd May 01
73
Charging Function
GPRS-300-101
G-CDR
A G-CDR is generated by the GGSN and contains charging information related to any external data network use by an MS. The GGSN, along with the SGSN, also generates charging information on the use of GPRS network resources. Table 7-1 lists the G-CDR data available for each PDP context. Table 7-1 G-CDR data Field Record type Network initiated PDP context Anonymous access indicator Served IMSI Collected (y/n) Y N Description GPRS GGSN PDP context record. Present when this is a network-initiated PDP context. A network-initiated PDP context is not supported. Set to true to indicate anonymous access and that the Served IMSI is not supplied. IMSI of the served party (when the Anonymous Access Indicator is FALSE or not supplied). The IPv4 address of the GGSN used. PDP context identifier used to identify this PDP context in different records created by GSNs. List of SGSN addresses used during this record. The logical name of the connected access point to the external packet data network IP. PDP address, IPv4. List of PDP addresses of the remote host or DTE, IPv4 addresses. Indicates whether served PDP address is dynamically allocated during PDP context activation. Value is FALSE. A list of changes in charging conditions for this PDP context, each time-stamped. Charging conditions are used to categorize traffic volumes, such as per tariff period. Initial and changed QoS and corresponding data values are listed. Data volumes are in octets above the GTP layer, and are separated for uplink and downlink traffic. Time stamp when this record was opened. Duration of this record in the GGSN. The reason for release of the record from this GGSN. A more detailed reason for release of the connection.
3rd May 01
N Y
GGSN address Charging ID
Y Y
SGSN address Access Point Name PDP type Served PDP address Remote PDP address Dynamic address flag
Y Y Y Y N Y
List of traffic data volumes
Record opening time Duration Cause for record closing Diagnostics
Y Y Y N
74
GPRS-300-101
Charging Function
Field Record sequence number Node ID Record extensions Local record sequence number
Collected (y/n) Y Y Y Y
Description Partial record sequence number, only present in case of partial records. Name of the recording entity. The IPv4 address of the GGSN. Holds NPDU uplink and downlink packet counts. Consecutive record number created by this node. The number is allocated sequentially including all CDR types.
S-CDR
An S-CDR is generated by the SGSN and contains charging information related to the use of the radio network by an MS. Like the GGSN, the SGSN also generates charging information on the use of GPRS network resources. Table 7-2 lists the S-CDR data available for each PDP context. Table 7-2 S-CDR data Field Record type Network initiated PDP context Anonymous access indicator Served IMSI Collected (y/n) Y N Description GPRS SGSN PDP context record. Present when this is a network-initiated PDP context. A network-initiated PDP context is not supported. Set to true to indicate anonymous access and that the Served IMSI is not supplied. IMSI of the served party (when the Anonymous Access Indicator is FALSE or not supplied). The IMEI of the MS, if available. The IPv4 address of the current SGSN. The mobile station classmark employed. Routing area at the time of the record creation. Location area code at the time of the record creation. The cell identity at the time of the record creation. PDP context identifier used to identify this PDP context in different records created by GSNs. The IPv4 address of the GGSN currently used. The GGSN address is always the same for an activated PDP. The logical name of the connected access point, to the external packet data network.
N Y
Served IMEI SGSN address MS classmark Routing area Local Area Code Cell identity Charging ID
Y Y N Y Y Y Y
GGSN address used
Access Point Name
3rd May 01
75
Charging Function
GPRS-300-101
Field PDP type Served PDP address List of traffic data volumes
Collected (y/n) Y Y Y
Description PDP type, IPv4 address. PDP address of the served IMSI, an IPv4 address. Lists changes in charging conditions for this PDP context, each time-stamped. Charging conditions are used to categorize traffic volumes, such as per QoS/tariff period. Initial and changed QoS and corresponding data values are listed. Data volumes are in octets above the SNDCP layer, and separated for uplink and downlink traffic. Time stamp when PDP context activation is created in the SGSN or record opening time on following partial records. Duration of this record in the SGSN. Present when this is first record after SGSN change. The reason for release of record from this SGSN. A more detailed reason for release of the connection. Partial record sequence number in this SGSN. Only present in case of partial records. Name of the recording entity. The IPv4 address of the SGSN. Holds NPDU uplink and downlink packet counts. Consecutive record number created by this node. The number is allocated sequentially including all CDR types.
Record opening time
Duration SGSN change Cause for record closing Diagnostics Record sequence number Node ID Record extensions Local record sequence number
Y Y Y N Y
Y Y Y
76
3rd May 01
GPRS-300-101
Charging Function
M-CDR
An M-CDR is used to collect charging information related to the mobility management of a GPRS MS in the SGSN. Table 7-3 lists the M-CDR data available for each MM context. Table 7-3 M-CDR data Field Record type Served IMSI Served IMEI SGSN address MS classmark Routing area Local Area Code Cell identity Change of location Record opening time Duration SGSN change Cause for record closing Diagnostics Record sequence number Node ID Record extensions Local record sequence number Collected (y/n) Y Y Y Y N Y Y Y Y Y Y Y Y N Y IMSI of the MS. The IMEI of the ME, if available. The IP address of the current SGSN. The mobile station classmark employed. Routing area at the time of the record creation. Location area code at the time of record creation. Cell ID at the time of the record creation. A list of changes in Routing Area Identity, each time-stamped. Time-stamp when this record was opened. Duration of this record. Present when this is first record after SGSN change. The reason for release of the record in this SGSN. A more detailed reason for release of the connection. Partial record sequence number in this SGSN, only present in case of partial records. Name of the recording entity. The IPv4 address of the SGSN. A set of network/manufacturer specific extensions to the record. Consecutive record number created by this node. The number is allocated sequentially including all CDR types. Description GPRS SGSN mobility management record.
Y N Y
Charging Gateway
The CG collects CDRs from the GSNs and stores them in a persistent memory until they are successfully transferred to the BS. CG processing involves generating Billing Transfer files which are transferred to the BS, and audit files which are retained by the network operator.
3rd May 01
77
Charging Function
GPRS-300-101
Billing Transfer files and audit files

The CG stores processed charging data records in files called Billing Transfer files. The files are stored on a Redundant Array of Independent Disks (RAID) and are protected at all times. Each file contains one type of ASN.1 encoded records (S-CDR, M-CDR or G-CDR) that originate from a single GSN. In addition to the Billing Transfer files, the following three types of audit files are generated: S S S Audit Detail file. Audit Summary file. Audit Transfer Status file.
These files audit the charging data and File Transfer Protocol (FTP) transfer status, providing a record of the CDR data processed by the CG. Audit data is in ASCII format.
CG processing
The CG uses GTP Prime (GTP) to collect charging data records from each GSN. The records are stored in raw Billing Transfer files before they are processed. This minimizes data loss in the event of failure. The raw Billing Transfer files are closed based on a time trigger or volume trigger, both of which are configurable from the OMC-G. The closed file is processed to generate a Billing Transfer file which is transferred to the Billing System. The processing includes: S S S S S Decoding each record. Detecting missing and duplicate records based on a local record sequence number. Generating detailed audit records. ASN.1 encoding. Generating a summary record for each Billing Transfer file.
The missing and duplicate record detection mechanism is on a per file basis and assumes that the records collected are in order. Based on the transfer frequency, Billing Transfer files are pushed to the Billing System using FTP. The files are renamed in the destination directory once the transfer is successful. Only renamed files can be used for billing purposes. Files that are transferred successfully are stored on the CG for 24 hours before they are deleted. Any file that is not transferred during the current transfer process run is scheduled for the following run. Audit files are stored on the RAID for the number of days configured by the GPRS operator. One day before the end of the configured storage period, the OMC-G receives an alarm indicating that old audit files are going to be removed the following day. The next day, the OMC-G receives another alarm indicating that the old audit files have been removed.
Operations and management

CG configuration is file-based. The parameters that are configurable on the CG relate to GTP, audit file and raw Billing Transfer file closure, and the BS interface. Alarms are sent to the OMC-G to report FTP failure, GTP path failure, file operation failure and audit file removal.
78
3rd May 01
GPRS-300-101
Charging Function
Availability and reliability

The CG operates within the HA framework provided by the ISS Cluster. The CG always operates on a physical host that is mastering a logical host. If a hardware, software or application failure occurs, the CG software restarts on the same physical node or, as the result of a switchover, on the standby node. All charging related data such as CDRs, audit data, and logging data is stored in files on the RAID. Since files are RAID-protected at all times, and power supplies and fans are redundant, a single point of failure of an individual component (for example, a disk, power supply, or fan) should not affect the availability of the CDR files. In the event of a CG failure, some charging data may be lost. This is the data that is acknowledged over GTP but has not been successfully written to the raw BS Transfer files. All other files such as Audit Detail, Audit Summary, Audit Transfer Status, and BS Transfer files are derived from the raw BS Transfer files. To ensure availability and reliability in the event of CG failures in the middle of file operations, all the audit and BS Transfer files are opened and written into the active directories. Once the files are closed, they are moved to the ready directories. A raw BS Transfer file is purged only after the corresponding audit detail file and BS Transfer file are moved to the ready directories and Audit Summary record is written to the Audit Summary file. After the CG restarts, all the audit detail files and BS Transfer files in the active directories are removed and the raw BS Transfer files are reprocessed.
3rd May 01
79
Lawful Intercept
GPRS-300-101
Lawful Intercept
Introduction
This section includes: S S S S S S Lawful Intercept (LI) description. Lawful Intercept Administration Node (LIAN) architecture. LIAN-to-GSN interface. LI performance. LI management. LI security.
LI description
LI provides the ability to track and monitor signalling information and user data for a particular MS. It detects the user data for an MS being intercepted in the PLMN and duplicates this data, along with the signalling information, and forwards it to the requesting Law Enforcement Agency (LEA). Motorolas GPRS LI is composed of an administration function and delivery functions in a single elementthe LIAN. The LIAN supports the administration of GPRS LI requests and the delivery of data to external LEAs. In this release, intercept requests are entered using the Graphical User Interface (GUI) on the LIAN. The LIAN consists of: S S Administration Function (ADMF). Delivery Function (DF).
ADMF
The ADMF function of the LIAN: S S Interfaces with all the LEAs that may require interception with the customer Public Land Mobile Network (PLMN). Interfaces to all the SGSNs in a customers GPRS infrastructure equipment.
DF
The Delivery Function of the LIAN provides the filtering, formatting and forwarding capabilities. The LIAN incorporates two Delivery Functions as shown in Figure 7-2. S S DF2 Intercept Related Information (IRI). DF3 Intercept Data Product (IDP).
The LIAN receives the requested IRI or IDP from the SGSN and forwards it to the requesting LEA after suitable formatting and filtering.
710
3rd May 01
GPRS-300-101
Lawful Intercept
LIAN architecture
Figure 7-2 shows Motorolas LI architecture with the ADMF and two Delivery Functions combined into the LIAN.
OMCG
O&M Management
LIAN LEA client

LI Request to select SGSNs
ADMF
SGSN
SGSN LEA client DF2 LEA client

Intercept Results
SGSN IP Backbone
LI Response IDP and/or IRI
DF3
LI Manager
SGSN
GSM PLMN
Figure 7-2 LIAN architecture The ADMF function in the LIAN receives a request from a LEA client to intercept a specific GPRS mobile IRI or IDP, or both. Logging of all intercept request commands remain within the LIAN. The request is processed by the ADMF into a lawful intercept request for transmission to SGSNs in the GPRS PLMN. This LIAN element resides within the PLMN at a centralized GSN Complex. When an SGSN detects the presence of a target within its domain, IRI or IDP information is then intercepted. If a LEA client requests both IRI and IDP interception, the target MS data (IDP) and signalling (IRI) packets are duplicated at the SGSN and forwarded to the DFs. The DFs filter and format the received information for delivery to the requesting LEAs. IDP and IRI are not stored on the LIAN disk file system, but may be retained for a short time if the LIAN cannot reach the LEA. The IDP and IRI from each source node (SGSN) are maintained in separate files identified by the International Mobile Subscriber Identity (IMSI). Transfer of the IDP and IRI to the LEA is provided over non-secure data links for example, File Transfer Protocol (FTP).
3rd May 01
711
Lawful Intercept
GPRS-300-101
LIAN-to-GSN interface
Control messages are sent from the LIAN ADMF to the GSN requesting information on a specific subscriber. These control messages contain the identity of the target (IMSI) and information on whether the IDP, IRI, or both is provided. This interface is also used to transfer the IDP and IRI from the GSNs to the LIAN. The IDP consists of all MS originated and MS-terminated user data. The method for delivering the IDP is based on duplication of user packets at the GSN. Information about the following GPRS events are recorded by the SGSN as a part of the IRI: S S S S S GPRS attach and detach. PDP context activation. PDP context deactivation. Cell update. RA update.
The LIAN ADMF sends control messages to all SGSNs within the PLMN since it does not know which SGSN may be servicing a particular IMSI at any given time. Each SGSN maintains a Lawful Intercept list of IMSIs and associated intercept requests until the request is cancelled by the ADMF.
LI performance
The LIAN provides support for up to 200 simultaneously active Lawful Intercept requests. It supports a minimum of 64 kbps dial-up link for access to a LEA client. The LIAN also supports IP interfaces capable of collectively transferring a peak throughput of 3000 kbit/s. Flow control exists between the LIAN and SGSN. Any SGSN that exceeds a predefined threshold, alerts the LIAN. The SGSN is capable of buffering 500 kb of IRI events and 3.5 MB of IDP events. The LIAN can store a minimum of 12 GB of IRI and IDP data before it needs to forward the data to the LEA.
LI management
LI is managed and configured through the Interception Management System (IMS) using the LIAN GUI. Two parametersthe LIAN IP address and port numberare configured on the SGSN using the OMC-G console. The OMC-G has no other connection with the Lawful Intercept function.
LI security
Login security is provided at the LIAN console to restrict access to authorized personnel. For security purposes, SGSN involvement in the interception of data and signalling information is transparent and cannot be monitored from a GPRS network.
712
3rd May 01
GPRS-300-101
Network management
Network management
Introduction
Network management involves determining how the GPRS network is to be organized, configured and managed. This includes providing subscriber access to resources, managing names and addresses, and monitoring performance, capacity, reliability and security. The Operations and Maintenance Centre-GPRS (OMC-G) is the operator interface to the GPRS Complexes. The OMC-G has a GUI interface running on Simple Network Management Protocol (SNMP). The SNMP management interface enables a network operator to provide: S S S S S S S Fault management. Event and alarm handling. Configuration management. Load and database management. Performance management. User access control. Online help.
Fault management
The OMC-G fault management application provides the following functionality: S S S S S S S S S S S Alarm window. View of alarms/events from the SGSN, GGSN, ISS Cluster and CommHub. Handling/unhandling of alarms. Clearing of alarms. Removal of cleared alarms. Subscription to specified alarms and events. Filtering of specified alarms and events. Alarm and event history reporting. Map view. Tabular view. Support for regions.
The OMC-G administrator can subdivide the network into one or more regions, defined as one or more SGSNs, GGSNs, ISS Clusters and CommHubs. The alarm window is the centre of the OMC-G fault management application and provides the OMC-G operator with an alarm list. Any alarm is acknowledged by the operator before taking corrective action to resolve the problem. With an alarm selected, menu options and mouse options are context sensitive and provide the operator with a direct path towards resolving the problem. Alarms are displayed based upon operator subscription criteria that can be re-sorted and reformatted in tabular form to suit operator preferences. The tabular view provides a summary view of outstanding alarms, displaying the source of the alarms with operator selectable fields such as alarm count and severity. The navigator window can be configured to provide an extended summary view of the system alarm status by displaying alarm-related icons within the navigation display. Both the alarm window and tabular view is accessed from menu options at the OMC-G workspace, from the navigator, as well as geographic and topology maps.
3rd May 01
713
Network management
GPRS-300-101
Event and alarm handling

Once an alarm is identified, an OMC-G operator can register ownership of the fault as an indication to other OMC-G operators that the problem is being examined. Comments can be logged with that alarm so that other operators are informed of the steps undertaken to resolve the alarm. Table 7-4 shows the possible states for an alarm: Table 7-4 OMC-G event/alarm states Alarm status New Seen Description Indicates that the operator has not acknowledged the alarm. Indicates that the alarm has been acknowledged, no further action has been taken and the fault has yet to be rectified. Indicates that the operator is attempting to rectify the fault that has caused the alarm. Indicates that the fault has been rectified, or cleared by the operator.
Handling Cleared
Configuration management
The OMC-G Configuration Management user interface consists of the OMC-G navigator and parameter views, accessed at the OMC-G workspace. This provides GUI support to create GSN default parameters. A GSN can also be deleted via the GUI. The OMC-G provides the following features for configuration management: S S S S S S Navigator. Parameters. Tables. Maps. Data export. Configuration.
Access from the OMC-G to the ISS Cluster and CommHub is provided for configuration management activities. The OMC-G GUI also provides support for Gb link (SGSN-to-PCU) and Gr link (SGSN-to-HLR) configuration. GSN parameters can be viewed and modified via the appropriate parameter view. The OMC-G supports propagation of one or more SGSN parameter values to one or more SGSNs. Similarly, it is possible to propagate one or more GGSN parameter values to one or more GGSNs.
714
3rd May 01
GPRS-300-101
Network management
Load and database management

The OMC-G load management applications are options within the load management menu of the navigator, map and tabular views. The following functionality is provided: S S S S S S S Installation of software load/database. Deletion of software load/database. Download of software load/database. Progress display of software load/database download. Activation (swap) of new software load/database. Upload of database. Progress display of database upload.
Performance management
The OMC-G performance management application provides the ability to collect, view, and export both standard and custom statistics for the GSN Complex. These statistics can be either on-demand or polled.
On-demand statistics view

The GSN statistics attributes are viewed on-demand through the SGSN performance parameter view and the GGSN performance parameter view. Both can be invoked via the OMC-G navigator application.
Polled statistics
Polled GSN statistics attributes enable an operator to create a real-time display of a statistic for a specific GSN. The statistic is displayed in graphical form and is updated periodically depending on the polling interval which can be changed by the operator. The graph can be launched from the display menu on any of the following OMC-G applications: S S S S S S Navigator. Map. Tabular view. Alarm window. Event window. SGSN and GGSN parameter views.
Background statistics
Statistic values are collected by the GSN as files, independent of on-demand or polled viewing. These files are sent to the OMC-G in 15-minute intervals, and displayed in graphical and tabular formats. Custom statistics can be derived from raw statistics and performance management reports can be scheduled.
3rd May 01
715
Network management
GPRS-300-101
User access control

Access control is administered by a security administrator.
Online help
Context sensitive online help is available from the OMC-G GUI.
716
3rd May 01
GPRS-300-101
GPRS security
GPRS security
Introduction
This section describes the following security features available for this release: S S S S S S Operator access control. MS access control. MS authentication. Encryption. Password protection. Domain name security.
Operator access control

The OMC-G security management tools enable an individual PLMN to oversee operator authentication and control operator access. Operator authentication is achieved by a validity check of the username/password combination as entered by the user. The security administrator controls user access. Operator access to the OMC-G system is controlled through the Profile Editor application. The Profile Editor contains a list of the users currently configured to use the OMC-G, and the regions and command groups to which these users have access. Users can be assigned read-write, read-only or no access to regions. They can also be assigned or denied access to command groups. The Profile Editor enables an operator to create, configure or delete regions and command groups for use within the OMC-G. A region is an administrator-defined subset of network entities which are within the scope of control of the OMC-G. There may be many regions in a given network. A network component may be in more than one region at the same time. A command grouping is an administrator-defined set of commands. The Profile Editor contains a list of all available devices which the operator uses to allocate devices to a region or remove them from a region. In the same way, the Profile Editor also contains a list of all available command actions which the operator uses to allocate or remove command actions from one or more command groups. Security event files can be stored and later exported to an external system.
MS access control
Individual PLMN administrations may require specific access-control procedures in order to limit the set of users permitted to access the network or to restrict the capabilities of individual users, for example by limiting the type of service available to an individual MS. By defining and configuring screening parameters through an access control list on the OMC-G, MS access can be restricted to the type of application or a set of external servers based on address. Access control lists are configured to support a customers security policy. With this network-controlled screening feature, the network operator can provide a higher access security for the GPRS subscribers.
3rd May 01
717
GPRS security
GPRS-300-101
MS authentication
Authentication enables the SGSN to check whether or not an MS is authorized to use the GPRS network. This improves security by protecting against unauthorised and unlawful use of the network. The authentication function is performed in association with the GPRS Attach and inter-SGSN Routeing Area Update (RAU) mobility management procedures. When authentication is requested, the SGSN sends the MS an authentication and ciphering response message containing challenge information. The MS processes this information then generates a signed response message which it sends back to the SGSN. The SGSN checks the validity of the response and, if correct, allows the attach or RAU procedure to continue.
Encryption
Encryption is a method of protecting the privacy of information being transmitted over a network. This feature can be enabled or disabled on the SGSN via the OMC-G and applies not to individual MSs, but to all MSs that support encryption and are being served by a specific SGSN. The SGSN determines whether or not an MS in its serving area supports encryption by either reading the Attach Request message from the MS or retrieving information during the Routeing Area Update (RAU) procedure. To provide encryption, Motorola has implemented an efficient hardware solution on the GPRS Encryption Module (GEM), a PCI Mezzanine Card (PMC) on the Upper Transmission Function (UTF) module in the SGSN chassis. Encryption works in association with the authentication function. An MS begins encryption after it sends an Authentication and Ciphering response message to the SGSN. The SGSN begins encryption when it receives the valid Authentication and Ciphering response message from the MS. Encryption involves applying the GPRS Encryption Algorithm (GEA) to the signalling message and user data to preserve the confidentiality of the message. Decryption is used to reverse the process and restore the information to its original form so it can be understood.
Password protection
Access to Network Elements is restricted using password protection.
Domain name security

For security, a separate Access Point Name (APN) Domain Name Service (DNS) server is required to maintain public subscriber naming information. It does not contain any address for the GPRS infrastructure equipment. The internal DNS server contains proprietary information, which requires restricted access to internal addresses by end-systems outside a network operator infrastructure. For this reason, internal DNS servers in the Motorola GPRS system do not provide logical name-to-IP address mappings for subscribers.
718
3rd May 01
Chapter 8
GPRS hardware
3rd May 01
GPRS-300-101
ii
3rd May 01
GPRS-300-101
Chapter 8 GPRS hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSN cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communications cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expansion cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet interior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN module components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Card functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN redundant power supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sun Netra t 1125 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sun Netra st D1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminal Concentrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection to CommHub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chassis modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supervisor Engine module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Route Switch Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10/100BASE-T switch module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enterprise 3500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Edge 6300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware scaleability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Minimum GSN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum GSN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
81 81 81 82 82 83 83 83 84 84 84 85 87 89 89 89 89 810 810 811 811 811 812 812 813 814 814 814 814 815 816 816 817 817 817 818 819 819 819 820 820 820 820
3rd May 01
iii
GPRS-300-101
iv
3rd May 01
GPRS-300-101
Chapter overview
Chapter overview
This chapter describes the scaleability and hardware components of the GPRS infrastructure.

This chapter is divided into the following sections: S S S S S S S S GPRS Service Node (GSN) cabinets. Serving GSN (SGSN) hardware. Gateway GSN (GGSN) hardware. Integrated Support Server (ISS) Cluster hardware. Communications Hub (CommHub) hardware. Operations and Maintenance Centre-GPRS (OMC-G) hardware. Base Station System (BSS) hardware. Scaleability of GPRS hardware components.
3rd May 01
81
GSN cabinets
GPRS-300-101
GSN cabinets
Introduction
The four major network entities (SGSN, GGSN, CommHub, ISS) that make up a GSN Complex are located in one of the following types of cabinet: S S Communications cabinet. Expansion cabinet.
Figure 8-1 shows a basic configuration with one communications cabinet and one attached expansion cabinet.
COMMUNICATIONS CABINET EXPANSION CABINET
HA DISK ARRAY SGSN CHASSIS (SPARE)
ISS CLUSTER
CLUSTER NODE HA DISK ARRAY CLUSTER NODE
EMPTY GGSN BAY GGSN (SPARE) GGSN (ACTIVE)
COMMHUB SGSN CHASSIS (ACTIVE)
Figure 8-1 GSN basic package (fully assembled)
82
3rd May 01
GPRS-300-101
GSN cabinets
Communications cabinet
Each GSN Complex has one communications cabinet which contains: S S One CommHub (Cisco 5500). Two ISS Clusters (active and spare), each containing: S S S S One cluster node (Sun Netra t 1125). One High Availability (HA) Disk Array (Sun Netra st D1000). One terminal concentrator.
One or more E1 or 100BASE-T links to interface to an OMC-G or Billing System via the ISS Cluster. Up to 30 E1 links to external Packet Data Networks (PDNs) and Gn interfaces that are not collocated. Up to four 100BASE-T links for collocated GSN Complexes. Five 100BASE-T links for each ISS Cluster.
Expansion cabinet
The GSN Complex is an entity that can be scaled. Each GSN Complex has one or more expansion cabinets to which cards can be added to increase performance, capacity or functionality. Additional expansion cabinets can be added to the complex as demands for capacity increase, until the maximum configuration for a complex is reached. A basic expansion cabinet contains: S S S S S S S Two SGSN chassis (active and spare). Two GGSNs (active and spare). One empty slot for a future GGSN. Interfaces to twelve E1 ports on the Gb card. HLR SS7 interfaces. Gi port functionality provided by the GGSN via the Cisco 7206 IP Router. Interface to Sun Netras two 100BASE-T ports.
Cabinet interior
The interiors of both the communications cabinet and the expansion cabinet contain the following: S S S Standard 532 mm (19) chassis (shelf) racks with pre-installed runners. An A4 document pocket on the inside of the door to hold instructions for cabinet assembly and installation, and also tool requirements and safety information. Remote power switching provided by a power input distribution mounting bracket with one remote AC power input switching panel for each GSN.
Data cable and power cable entry can be from either the top or bottom of the cabinet, with top entry recommended for data cables and bottom entry recommended for power cables. Data and power cables use different entry points to keep them separate.
3rd May 01
83
SGSN hardware
GPRS-300-101
SGSN hardware
Introduction
The SGSN maintains a logical data link with each MS, providing a reliable and secure data channel as the MS moves between cells. This section describes: S S S SGSN chassis. SGSN modules. SGSN module components.
SGSN chassis
The Motorola SGSN is contained within a 16-slot CompactPCI (Peripheral Component Interconnect) equipment chassis. The chassis has the following features: S S S S S S S S An alarm module. A power distribution module. Three fan/power supply sleds (one for redundancy). Up to 16 digital modules (dependent on customer requirements). High performance bus standard capable of data transfer rates of over 260 MB per second. Self-contained card assembly with independent bus and power supplies. Three 350-W power supplies. Hot swappable backplane supporting rear transition modules (TM-PIMC-0001s).
A single 16 slot CompactPCI chassis may contain up to three SGSNs. A maximum of 18 SGSNs (distributed over six chassis) may be configured per GSN Complex. A basic SGSN chassis contains two SGSNs (active and spare). The recommended digital modules for each SGSN chassis in the GSN expansion cabinet contains: S S S S One Signalling Function (SF) card. Up to three SGSNs. Each SGSN consists of one each Gn, Gb, and CF card. Two System Switch Processor (SSP) cards. Two Hot Swap Controller (HSC) cards.
Figure 8-2 shows three SGSNs installed in a chassis with one SF card and SSP cards. The SSP cards provide active and spare Shelf Manager functionality.
84
3rd May 01
GPRS-300-101
SGSN hardware
Active and Spare SSPs
CF, Gb, Gn
SF SPARES (Slots 2-3) CF Gb Gn HSC HSC CF Gb Gn COVER PLATE
532 mm
FAN/POWER SUPPLY SLED
Figure 8-2 SGSN chassis
SGSN modules
SGSN functionality resides on three main modules in the SGSN chassis: S S S Control Function (CF). Gb. Gn.
The following cards in the SGSN chassis support the CF and TF cards. S S S SF. SSP. HSC Bridge.
3rd May 01
85
SGSN hardware
GPRS-300-101
CF module
The CF module is responsible for mobility management and generation of Mobility Call Detail Records (M-CDR). It also sends signalling messages between the SGSN and other GPRS network components, and control messages to and from the TF modules. In addition, the CF module generates statistics and maintains high availability of software processes. The CF module is made up of the following components: S S S S One MCPN750 card. One TM-PIMC-0001 transition module. Two PIM-0101 PCI Mezzanine Cards (PMC). One SanDisk 48 M compact flash memory card.
Gn card
The Gn card performs the SGSN communication protocol functions for a single Gn interface. It supports LLC and SNDCP to the MSs and GTP to the GGSN, and is also responsible for generating SGSN-Call Detail Records (S-CDRs) and providing encryption. The card communicates with the Gb and CF cards, and with the GGSN through the CommHub using 10/100BASE-T Ethernet. The Gn card is made up of the following components: S S S S S One MCPN750 card. One TM-PIMC-0001 transition module. One PIM-0101 PMC interface module. One Field Programmable Gate Array (FPGA) PMC encryption module. One SanDisk 48 M compact flash memory card.
Gb card
The Gb card performs the SGSN communication protocol functions for the Gb interface to provide MSs with access to the GPRS network through the BSS. It supports BSSGP, Network Services and Frame Relay protocols. Four E1 ports on the PMCs provide connectivity to remotely located BSSs. The card communicates with the PCU via E1, and with the CF, Gn card, and ISS through the CommHub using 10/100BASE-T Ethernet. The Gb card is made up of the following components: S S S S S One MCPN750 card. One TM-PIMC-0001 transition module. Two PIM-0101 PMC interface modules. Two Dual PIM-0100 E1 PMC modules. One SanDisk 48 M compact flash memory card.
SF card
The SF card provides SS7 MAP signalling capabilities between the SGSN and Home Location Register (HLR) using E1, and also communicates with the CF module through the CommHub using 10/100BASE-T. The SF card is made up of the following components: S S S S S
86
One MCPN750 card. One TM-PIMC-0001 transition module. Two PIM-0101 PMC interface module (E1). Two PMC/860 PCI mezzanine cards. One SanDisk 48 M compact flash memory card. System Information: GPRS Overview 68P02903W01-C
3rd May 01
GPRS-300-101
SGSN hardware
SSP cards
The SSP cards provide Shelf Manager functionality. The Shelf Manager performs load management and configuration management of the CF, Gb, Gn and SF modules within the SGSN chassis. Each of the two system processor cards in the chassis are made up of the following components: S S One MCP750-HA system processor card. One SanDisk 48 MB compact flash memory.
HSC Bridge card

The HSC Bridge card contains a hot swap controller and a transparent PCI-to-PCI bridge which allow a Service Switching Point (SSP) to be linked to a second separate cPCI bus.
SGSN module components

The following components make up the SGSN modules described in the previous section:
MCPN750 card
The MCPN750 processor is a non-system slot card with the following hardware features: S S S S S S 256 MB RAM. 1 MB, 16-bit flash memory on board (socket). Additional 8 MB, 16-bit flash memory (surface mount). One 10/100BASE-T fast Ethernet port. One Asynchronous serial port (console). Hot swappable.
The MCPN 750 card can hold two PMC modules.
FPGA PMC encryption module

The FPGA PMC module provides encryption services for GPRS. The encryption module fits into the lower PMC slot on the Gn card and has the following hardware features: S S S Field programmable gate array. Programmable two-clock generator with a user application clock. 1Mbyte of flash memory.
Dual E1 PIM-0100 PMC module

The Dual E1 PMC fits into the PMC slots on the Gb and SF cards and performs all of the physical layer termination of E1 links to the PCUs or HLR. It also provides E1 timeslot multiplexing/demultiplexing. The processor driving the two E1 links on the module is a Motorola MCP860 PowerQUICC running at 66 MHz. The dual E1 PMC module is placed on the non-system processor board and has the following hardware features: S S S S S 87 MIPS @ 66 MHz. 16 MB shared EDO DRAM. 256 KB fast SRAM. 2 MB Flash PROM. Two E1 interfaces.
3rd May 01
87
SGSN hardware
GPRS-300-101
TM-PIMC-0001 transition module

The TM-PIMC-0001 Transition module has the following hardware features: S S One rear 10/100BASE-T port. Hot swappable when the MCPN750 non-system board with which it communicates is removed.
The transition module holds two PMC interface modules and one SanDisk compact flash memory card.
PIM-0101 PMC interface module

The PIM-0101 PMC interface module is placed on the transition module to provide rear E1 connectivity for PMC modules fitted to the associated non-system SGSN slot processors. The PMC interface module has the following features: S S Two fused 120 ohm RJ45 (or T43) ports for E1 interfaces. One asynchronous serial RJ45 port for debug purposes.
SanDisk compact flash memory card

The SanDisk 48 M compact flash memory card has 48 MB of flash memory and is placed on the transition module.
88
3rd May 01
GPRS-300-101
GGSN hardware
GGSN hardware
Introduction
The GGSN directs downlink packets to the SGSN serving the MS, allowing the mobile subscriber to move freely within the coverage area of its home PLMN or a foreign PLMN. This section describes: S S S S GGSN chassis. Card functions. Interface support. GGSN redundant power supplies.
GGSN chassis
The GGSN resides on the Cisco 7206VXR chassis equipped with fast Ethernet cards. A single GSN Complex supports a maximum of two GGSN modules, configured in a N+1 capacity arrangement. Each module supports up to 25,000 packets per second. Figure 8-3 is a front view of the GGSN chassis showing the six configurable slots. The rear of the chassis is fitted with dual power supplies to support hot-swapping, load-sharing and redundant power.
FAST ETHERNET or E1 PORTS
PORT ADAPTOR LEVER PC CARD SLOTS AUXILIARY PORT CONSOLE PORT
I/O CONTROLLER
FAST ETHERNET PORT
Figure 8-3 GGSN chassis
Card functions
The GGSN functionality is provided by:
I/O controller
The I/O controller in slot 0 comes with an optional Fast Ethernet PA with an RJ45 connector.
3rd May 01
89
GGSN hardware
GPRS-300-101
100BASE-T Fast Ethernet Port Adapter (PA) card

The 100BASE-T Fast Ethernet PA card or E1 (for direct connect GGSN) in Slot 1 is configured as either a Gi or a Gn interface. Slot 2 is a spare PA. S S The Gi interface provides access to external packet data networks. The Gn interface uses GPRS Tunnel Protocol (GTP) to provide signalling and data communication between the SGSN and GGSN.
Slots 3 to 6 remain empty until they are required for future expansion.
Interface support
The GGSN hardware is capable of supporting the following interfaces: S S Fast Ethernet. E1, fractional E1.
GGSN redundant power supplies

Figure 8-4 shows the rear panel of the GGSN, including the redundant power supplies.
AC-INPUT RECEPTACLE POWER SUPPLY FILLER PLATE
CHASSIS GROUNDING RECEPTACLES
INTERNAL FANS POWER SWITCH NETWORK PROCESSING ENGINE
AC-INPUT POWER SUPPLY
Figure 8-4 GGSN rear panel
810
3rd May 01
GPRS-300-101
ISS Cluster hardware

Introduction
An ISS Cluster contains the following components: S S S Two Sun Netra t 1125s. Two Sun Netra st D1000s. Terminal concentrator.
The Sun Netra t 1125s and st D1000s are configured to be fully mirrored, hot standby. Each Sun Netra is connected to the CommHub using Ethernet.
Sun Netra t 1125

Two Sun Netra t 1125s (one primary and one secondary) are stacked together in the GSN Communications cabinet to provide cluster node functionality such as Domain Name Service (DNS) server, Network Time Protocol (NTP) server, Network File Server (NFS), and Charging Gateway Function (CGF). The Sun Netra t 1125 chassis has the following cards: S S One Dual Ultra SCSI I/O card. One Quad Fast Ethernet (QFE) card.
A Sun Netra t 1125 is shown in Figure 8-5.
Figure 8-5 Front view of the Sun Netra t 1125
3rd May 01
811
GPRS-300-101
Sun Netra st D1000

Two Sun Netra st D1000s provide the High Availability (HA) disk array functionality. The HA disk array provides reliable long-term storage for network configuration, software storage, charging data information and network statistics. Figure 8-6 shows the Sun Netra st D1000s HA Disk Arrays. Two fully mirrored Sun Netra st D1000s provide storage for the ISS. In this release, the Netra st D1000s have 5 disks. These HA Disk Arrays are stacked together in a communications cabinet to supply the following storage capacities for each array: S S S Up to 218.4 GB of disk capacity. Incremental increases in disk capacity of 18.2 GB. Hot swap and redundant disk drives.
Figure 8-6 Front view of the Sun Netra st D1000
Terminal Concentrator
The Sun Enterprise Cluster Terminal Concentrator provides console access to the Netra t 1125s via a Telnet connection. The terminal concentrator hardware is a Bay Networks micro Annex x1, commonly referred to as a micro Annex. Figure 8-7 shows the rear view of the Terminal Concentrator.
Figure 8-7 Terminal Concentrator

812
3rd May 01
GPRS-300-101
Connection to CommHub
The Sun Netra platform is connected to the CommHub via fast Ethernet 100BASE-T (see Figure 8-8).
100BASE-T Ethernet Network 100BASE-T Ethernet Network
CommHub
Netra t 1125 qfe0 qfe1 ttya com A node 0 qfe3 qfe3 hme0 hme0 c1 UltraSCSI Disk Array #1 Hot spare D1000 Null Ethernet Cable Null Ethernet Cable ttya RS232 Terminal Concentrator
Netra t 1125 qfe0 RS232 com A ttya node 1 qfe3 hme0 c1 UltraSCSI c2 qfe1
c2
UltraSCSI D1000
Disk Array #2 Hot spare
UltraSCSI
Figure 8-8 ISS Cluster
3rd May 01
813
CommHub hardware
GPRS-300-101
CommHub hardware
Introduction
The CommHub hardware consists of a chassis installed with special purpose modules (cards). It uses standard Cisco Supervisor and Internetwork Operating System (IOS) software pre-installed in the modules. This section describes the: S S S S S CommHub chassis. Chassis modules. Supervisor Engine (SE) module. Route Switch Module (RSM) fitted with VIP2 module. 10/100BASE-T switch module.
CommHub chassis
The CommHub chassis, as shown in Figure 8-9, is a Catalyst 5500 LAN switch manufactured by Cisco Systems, Inc. The Cisco Catalyst 5500 chassis has 13 slots and supports the hot-swapping of power supplies and cooling fans. The Catalyst 5500 has a gigabit Ethernet-ready architecture that scales to more than 50 Gbps and throughput of tens of millions of packets or cells per second (pps). The switching backplane supports 3.6 Gbps.
TWO SUPERVISOR ENGINES RSM WITH VIP2 MODULE THREE 100BASE-T MODULES RSM WITH VIP MODULE THREE 100BASE-T MODULES
TWO POWER MODULES
Figure 8-9 Catalyst 5500 chassis
Chassis modules
In the GSN architecture, the Catalyst 5500 is configured as an Ethernet switch while the fast Ethernet ports are configured as switched 10/100BASE-TX (half-duplex) interfaces. The CommHub is also configured as a router. Table 8-1 lists the modules in the CommHub chassis.
814
3rd May 01
GPRS-300-101
CommHub hardware
Table 8-1 CommHub modules Equipment Route Switch Module (RSM) fitted with VIP2 module E1 Circuit Supervisor Engine III (SE) 10/100BASE-T Fast Ethernet switching module Cooling Fans Net flow module Power supply modules Module (cards) per system 2 4 2 26 2 2 2 Interfaces (ports) per module n/a 8 n/a 24 n/a n/a n/a
Supervisor Engine module

The SE module manages a Catalyst 5500 and enables the CommHub to display alarms and statistics for the individual modules. Both the RSM and 10/100BASE-T modules are controlled through the SE. The SE has a network management processor, two 100 Mbit/s Fast Ethernet uplinks, 16 MB of DRAM, 256 KB of NVRAM and 4 MB of on-board flash memory. Figure 8-10 shows the SE module.
CONSOLE AND AUXILIARY PORTS
STATUS LEDs
SWITCH LOAD DISPLAY
PCMCIA SLOTS
UPLINK PORTS
RESET BUTTON
Figure 8-10 SE module
3rd May 01
815
CommHub hardware
GPRS-300-101
Route Switch Module

The RSM is a single card fitted with a VIP2 module that accommodates two E1/PRI serial port modules. The two E1/PRI serial port adapters plug into the VIP2 of the single RSM to provide E1 circuit emulation. Each serial port adapter provides eight E1 ports with individual port LEDs for indicating data activity. The RSM/VIP2 is a double-wide module that occupies two consecutive Catalyst 5500 slots. The Catalyst VIP2-40 has 2-MB SRAM and 32-MB DRAM. Figure 8-11 shows the RSM with two 8-port E1/PRI port adaptors. 8-port E1/PRI port adaptor
Module status LED
Link status LEDs
Status LED CPU HALT and ENABLED LEDs
Reset Flash card LEDs Flash card slots
AUX port Console port
Tx and Rx LEDs for Channels 0 and 1
Figure 8-11 RSM with two 8-port E1/PRI port adaptors
10/100BASE-T switch module

10/100BASE-T Switch modules, as shown in Figure 8-12, connect GPRS components to Ethernet and provide intelligence for filtering out Ethernet violations. The 10/100BASE-T fast Ethernet modules may be added to the CommHub in increments, as required. Each 10/100BASE-T Fast Ethernet switching module provides 24 ports and up to 100 Mbps of bandwidth per port. Status LED for module 24 ports
2 status LEDs for each port
Figure 8-12 10/100BASE-T Switch module

816
3rd May 01
GPRS-300-101
OMC-G hardware
OMC-G hardware
Introduction
The OMC-G provides network operators with the capability to manage and monitor the data aspects of the network. The hardware for the OMC-G consists of: S S Sun Enterprise 3500 (OMC-G system server). Dell Power Edge 6300/6400 server (OMC-G functionality server).
Enterprise 3500
The OMC-G system server is composed of: S S S S S S S S S S Sun Enterprise 3500. Sun monitor. Sun keyboard. Mouse with keyboard connection. One floppy drive. One CD drive. One 4mm DDS 3 DAT tape drive. Four 400 MHz CPUs. Eight removable hard drives (9 GB FCAL). A 100BASE-T Ethernet connection to the CommHub for GSN configuration and monitoring.
Figure 8-13 shows two front views of the E3500, one with the door closed and one with it open.
Sun ENTERPRISE 3500 FLOPPY
CD Omcg1
GRILL
DOOR LOCK
Figure 8-13 Front views of the Sun Enterprise 3500
3rd May 01
817
OMC-G hardware
GPRS-300-101
Power Edge 6300

The OMC-G functionality server is composed of: S Dell Power Edge 6300/6400. S S S One floppy drive. One CD drive. Four 18GB removable hard drives. Four 400 MHz CPUs. 1 GB memory.
One 19 Trinitron monitor. Keyboard. Mouse.
The server has a 100BASE-T Ethernet connection to the CommHub for GSN configuration and monitoring. Figure 8-14 shows the front view of the Dell server.
FLOPPY DRIVE* CD DRIVE* POWER/BUSY/FAIL LEDs* *BEHIND DOOR POWER LED* LEDs Dell logo HARD DRIVE
HARD DRIVE
LOCK/UNLOCK*
POWER/BUSY/FAIL LEDs
HARD DRIVES
HARD DRIVES
Figure 8-14 Front view of Dell Power Edge 6300 server
818
3rd May 01
GPRS-300-101
BSS hardware
BSS hardware
Introduction
The BSS provides Radio Frequency (RF) control and transmission for both GPRS and GSM mobile devices. The Motorola BSS is optional equipment as some customers may prefer to add GPRS functionality to their existing BSSs.
BSS components
A BSS consists of the following components: S Packet Control Unit (PCU). The PCU is made up of a number of digital modules contained within a chassis. The PCU adds GPRS radio channel control functions to the GSM BSS. S Base Transceiver Station (BTS). The BTS is made up of the radios, antennas, and interface modules that provide the air interface between the BSS and an MS. S Base Site Controller (BSC). The BSC is made up of a number of digital modules contained within a chassis. It controls and manages the associated BTSs in the BSS and interfaces with the OMC-R. S Operations & Management CentreRadio (OMC-R). The OMC-R is made up of a system processor and an operator workstation. The system processor handles all operations and maintenance communication with the BSS components, and the workstation provides a GUI interface for managing the BSS.
3rd May 01
819
Hardware scaleability
GPRS-300-101
Hardware scaleability
Introduction
Hardware scaleability allows networks to add to the GPRS system as demand increases. The network entity can be scaled from a minimum network configuration up to the maximum capacity limits. Each entity in a GPRS network has a capacity factor built in, to calculate the maximum capacity supported on the GSN Complex. This capability allows a network to start from as small as 10K subscribers, and expand up to the maximum capacity of the GSN Complex (180K subscribers), thus minimising and spreading out the capital investment. This architecture is modular and can be scaled to grow as the subscriber base and usage increases, so once the capacity limit on a GSN Complex has been reached a new complex can be added. Scaleability is implemented in compliance with the GSM recommendation (GSM 03.60) for GPRS. The minimum and maximum GSN configurations are described below.
Minimum GSN configuration

The GSN Complex minimum configuration includes one GGSN, one SGSN, one ISS Cluster and a CommHub.
Maximum GSN configuration

As the network grows, the number of GGSNs can be scaled to the maximum of five. The number of SGSNs for each SGSN chassis can be scaled up to three and the number of SGSN chassis can be scaled to 6+1. The ISS Cluster and CommHub do not need to be expanded as the GSN Complex grows to the maximum configuration. In this release, the capacity of the GGSN and the SGSN are as follows:
GGSN
Each GGSN (Cisco 7206VXR switch platform) can support up to 90,000 PDP contexts and 25,000 packets per second (pps) based on a packet size of 256 bytes. The number of GGSNs in the GSN Complex may grow up to the maximum of five. The availability impact of having only two operational GGSNs may cause customers to deploy more than 2+1 GGSNs.
SGSN
Each SGSN supports 12K subscribers, 10K PDP contexts and 2K PPS. Each chassis may support three SGSNs. Therefore, each SGSN chassis with the maximum of three SGSNs can support up to 36K subscribers, 30K PDP and 6K PPS. As the network continues to grow, the number of SGSN chassis can be increased to a maximum of 6+1 (6 operation and 1 redundant SGSN). With 6+1 SGSN chassis, the network operator can support up to 216K subscribers, 180K PDP contexts and 36K PPS. The number of PDP contexts supported is based on the total number of subscribers, including roaming subscribers from other PLMNs.
820
3rd May 01
Chapter 9
GPRS equipment specifications
3rd May 01
GPRS-300-101
ii
3rd May 01
GPRS-300-101
Chapter 9 GPRS equipment specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSN cabinet specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sun Netra t 1125 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sun Netra st D1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . micro Annex x1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
91 91 91 92 93 94 95 95 95 95 96
3rd May 01
iii
GPRS-300-101
iv
3rd May 01
GPRS-300-101
Chapter Overview
Chapter Overview
This chapter lists the environmental and physical specifications for the GPRS hardware components, not including the PCU. For the Motorola PCU specifications, see System Information: General (GSM-100-101). For details about the capacities of the GPRS components, including the minimum and maximum hardware configurations, see System Information: GPRS Equipment Planning (GPRS-001-103)

This chapter provides specifications for the: S S S S S GPRS Service Node (GSN) cabinet. Serving GSN (SGSN). Gateway GSN (GGSN). Integrated Support Server (ISS) Cluster. Communications Hub (CommHub).
3rd May 01
91
GSN cabinet specifications
GPRS-300-101
GSN cabinet specifications

Physical specifications for the GSN cabinet, together with the overall environmental and operating specifications for the GSN Complex are listed in Table 9-1. Table 9-1 GSN Complex cabinet/system physical specifications Category Dimensions (per cabinet) Weight Mounting Input voltage (Nominal) Temperature Relative humidity Shock and vibration Acoustic noise (system) Regulatory requirements Specifications H 1900 mm x W 600 mm x D 875 mm. 138 kg: unladen. 337 kg: laden (max. per cabinet). Floor mounted (bolted), collocated, and fastened together. 100 to 240 V AC, 50/60 Hz . Operating: 5 C to 35 C. Operating: 5% to 85%, at 35 C. ETS 300 019 -1-3 Class 3.1. ETS 300 753, Class 3.1. as applicable to Telecommunications Equipment rooms (attended). Safety: EN60950, IEC 950. Emissions: EN50081-1. Immunity: EN50082-2, ETS 300 342-3.
92
3rd May 01
GPRS-300-101
SGSN specifications
SGSN specifications
The SGSN is housed in a Motorola CompactPCI CPX8216 chassis. Table 9-2 lists the physical and electrical specifications for the SGSN chassis which are in addition to the system specifications listed in Table 9-1. Table 9-2 Motorola CompactPCI CPX8216 physical specifications Category Dimensions Weight Mounting Slots Specifications H 533.4 mm x W 482.6 mm x D 435 mm. 13.6 kg: without cards or peripherals installed. 31.85 kg: with peripherals and CPU installed. Per EIA Standard RS-310-C in 19 inch rack with mounting flanges. Sixteen hot swap-capable 4HP CompactPCI slots, providing: S Two CPU slots. S S Backplane Two HSC/bridge slots. Twelve non-system processor slots with twelve rear I/O slots.
8-slot, 64-bit CompactPCI domains. 1 CPU slot, 1 HSC/bridge slot, and 6 rear I/O slots per domain. 100 240 V AC. ~12 5 A Output: Maximum 350 W @ 50 C. +5 V, 30 A. +3.3 V, 28 A. +12 V, 14 A. 12 V, 1 A.
Power supplies/fans 3 - bays (front accessible). Nominal input voltage Nominal input current Power supply
3rd May 01
93
GGSN specifications
GPRS-300-101
GGSN specifications
The GGSN module resides on the 7206VXR chassis made by Cisco Systems. Table 9-3 lists the GGSN specifications which are in addition to the system environmental specifications listed in Table 9-1. Table 9-3 Cisco 7206VXR chassis physical specifications Category Dimensions Weight Nominal AC input voltage. Nominal input current rating AC input frequency rating AC input cable DC output power DC voltages supplied and maximum, steady-state current ratings Specifications H 133.4 mm x W 426.7 mm x D 431.8 mm. 22.7 kg (fully loaded). 100 240 V AC. ~5 2.1 A. 50/60 Hz. 18 AWG three-wire cable, with a three lead IEC-320 receptacle at each end. 260 W max. (single or dual power supply configuration). +5.2 V @ 30 A. +12.2 V @ 9 A. 12.0 V @ 1.5 A. +3.5 V @ 13 A. ~80 cfm.
Airflow
94
3rd May 01
GPRS-300-101
ISS Cluster specifications
ISS Cluster specifications

The ISS Cluster functions reside on three separate chassis. Table 9-4, Table 9-5 and Table 9-6 list the physical specifications for these chassis. These specifications are in addition to the system environmental specifications in Table 9-1.
Sun Netra t 1125

Table 9-4 lists the specifications for the ISS chassis which provides the following services: Domain Name Server, Network Time Server, Network File Server, and Charging Gateway Function. Table 9-4 Sun Netra t 1125 physical specifications Category Dimensions AC input DC output Operating temperature Valid Input H 431.8 mm x W 431.8 mm x D 496.1 mm. 100 V AC to 240 V AC nominal. ~5.5 2.8 A. 325 W (maximum). Operating: 5 C to 40 C. Short term operating: 5 C to 55 C.
Sun Netra st D1000

Table 9-5 lists the specifications for the High Availability (HA) disk array. Table 9-5 Sun Netra st D1000 physical specifications Category Dimensions Weight AC power requirements Operating temperature Specification H 17.5 cm x W 44.94 cm x D 53.24 cm. 23.4 kg without disk drives. 32.3 kg fully loaded. 100 V AC to 240 V AC nominal. ~5.0 2.1 A. Operating: 5 C to 40 C. Short term operating: 5 C to 55 C.
micro Annex x1
Table 9-6 list the physical specifications for the Terminal Concentrator. Table 9-6 micro Annex x1 specifications Category Dimensions Weight AC power requirements Specification H 63.5 mm x W 330 mm x D 241 cm. 2.3 kg . 90 V AC to 130 V AC, 1.0 A. 80 V AC to 260 V AC, 0.5 A. Frequency: 47 to 63 Hz.
3rd May 01
95
CommHub specifications
GPRS-300-101
CommHub specifications
The physical specifications for the CommHub, which are in addition to the system environmental specifications of Table 9-1, are listed in Table 9-7. Table 9-7 Cisco Catalyst 5500 physical specifications Category Dimensions Weight Specification H 625 mm x W 431 mm x D 460 mm (550 mm including cable guide). 22.75 kg (chassis only). 1.36 kg to 2.27 kg (each module). 65.65 kg fully configured chassis with 13 switching modules and two power supplies. 13 Plus two for power supplies. 1100 W maximum. 1100 W maximum configuration. 750 W typical with maximum configuration. 1571 W. 100 to 240 V AC. 47 to 63 Hz. 16 A max at 100 to 127 V AC, 8 A max at 200 to 240 V AC with full configuration (maximum of 1.8 kVA). +15.15 V at 200 A. +12 V at 6 A. +24 V at 2 A. 285 cubic feet per minute through system fan assembly.
Slots Power supply output System power dissipation System heat dissipation AC input voltage AC frequency AC input current
Power supply output
Airflow
96
3rd May 01
Chapter 10
Software release features
3rd May 01
GPRS-300-101
ii
3rd May 01
GPRS-300-101
Chapter 10 Software release features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software release 1.6.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software release 1.6.1.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISS Cluster features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommHub features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-G features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
101 101 101 102 102 102 103 104 104 105 105 106 106 106 107 107 107 108 108
3rd May 01
iii
GPRS-300-101
iv
3rd May 01
GPRS-300-101
Chapter Overview
Chapter Overview
This chapter summarizes the new features and added functionality provided by each major release of the GPRS software after the original 1.6.1.1 release.

This chapter describes the new features in the following software releases: S S Software release 1.6.1.3. Software release 1.6.1.4.
3rd May 01
101
Software release 1.6.1.3
GPRS-300-101

Introduction
This tables in this section list the new features in the 1.6.1.3 release of the GPRS software.
SGSN features
Table 10-1 lists the 1.6.1.3 features for the SGSN.
Table 10-1 SGSN features implemented in Release 1.6.1.3 Feature Shelf Manager Description The Shelf Manager is a new function that performs load and configuration management of the CF, TF and SF cards within the SGSN chassis. The SGSN authenticates subscriber information using triplets generated by the HLR. The following functions and interfaces are compliant with European Telecommunications Standards Institute (ETSI) standards according to Special Mobile Group (SMG) 29. With SMG 29 compliance, service providers can interwork a Motorola GPRS network with another vendors GPRS infrastructure in the PLMN. Gb. SNDCP. LLC. BSSGP. NS. The SF application handles the Gr interface between the SGSN and Home Location Register (HLR). The Gr interface enables the internal subscriber management database to be replaced by the HLR, allowing GPRS and GSM subscriber management to be integrated. The SF supports the following mobility procedures: Update Location. Cancel Location. Purge MS. Send Authentication. Subscriber Data Modification. MAP Subscriber Tracing. A control script provides a user interface to the HLR to enable an operator to start, stop, monitor the status, reload the database, and set the log level of the HLR. This release accepts Routing Area Update (RAU) requests from a foreign SGSN. RAU requests enable a subscriber to receive continuous service when travelling between areas served by different SGSNs in a GPRS network. A flow control function is implemented on the Gb interface.
3rd May 01
Authentication SMG 29 compliance
SS7 Function (SF)
SF mobility support
User interface to the HLR Intra-PLMN mobility
Gb flow control
102
GPRS-300-101
Feature SGSN charging support LI signalling Network-initiated deactivation CPU usage Log server Alarms HA polling
Description The restart counter in the Local Record Sequence Number is always set to zero. All optional fields are now included. A signalling interface from the SGSN to the LIAN server provides an interception facility for law enforcement agencies. Phase 2 of the network-initiated deactivation feature is implemented (support by PDPActivation and GGSNErrorIndication). CPU usage monitoring capabilities are supported in HA. The log server logs and forwards alarms to the OMC-G. Initial Gb and Gr alarms available. The High Availability (HA) supervisory process polls the SGSN applications to verify that they are still operational.
GGSN features
The GGSN is a standard Cisco product with enhancements incorporated by Motorola. Table 10-2 describes only features incorporated by Motorola. For details about any new Cisco features implemented in this release, see the Cisco GGSN release notes. Table 10-2 GGSN features implemented in Release 1.6.1.3 Feature GTP Description GTP encapsulation/decapsulation: Create PDP Context. Delete PDP Context. Uplink data traffic. Downlink data traffic. Access Point management using Access Point Names (APN). RADIUS authentication. Dynamic IP allocation via DHCP interface. ICMP messages for Destination Unreachable. This release is compliant with SMG27 GTP protocol specification.
Network access
SMG compliance
3rd May 01
103
GPRS-300-101
ISS Cluster features

Table 10-3 lists the 1.6.1.3 features for the ISS.
Table 10-3 ISS Cluster features implemented in Release 1.6.1.3 Feature Arbitrary hostnames Automated software installation Disk configuration flexibility Description The Cluster nodes, terminal concentrator and logical host may be assigned arbitrary names. The software installation for the Sun Cluster is fully automated. SCSI disk replacement is automatic. Configurable disk counts and positioning. The local disks for the Netra t 1125s are mirrored. The Netra t 1125s are configured as mediators for the shared disks. Simplified administration and improved maximum capacity. Alarm conditions logged to both a message file and the console, and SNMP traps sent to the OMC-G. Network Time Protocol (NTP) and network configuration can be changed after installation. The shared High Availability (HA) Network File Server (NFS) can be expanded across additional disks after installation. New tools display the status of the ISS Cluster (top-level), SDS-controlled disks, and the D1000 disk arrays. Collects billing records and transfers them to an external Billing System. Performs load and configuration management of the CF, TF and SF cards within the SGSN chassis.
Alarm condition monitoring Post-installation changes
Monitoring Charging Gateway Function Shelf Manager
CommHub features
Table 10-4 lists the 1.6.1.3 feature for the CommHub. Table 10-4 CommHub features implemented in Release 1.6.1.3 Feature IOS Version 12.07T Description New CommHub software supports the E1 port adapter.
104
3rd May 01
GPRS-300-101
OMC-G features
Table 10-5 lists the 1.6.1.3 features for the OMC-G. Table 10-5 OMC-G features implemented in Release 1.6.1.3 Feature Fault management Load management Description GPRS alarms can be viewed, handled, logged and printed. SGSN and GGSN software can be installed, deleted, downloaded and swapped. SGSN and GGSN databases can be uploaded and updated. The SGSN, SF and SM can be configured using Graphical User Interface (GUI) forms. SGSN and GGSN online (real-time) statistics can be viewed and a report generated. OMC-G users can be added and deleted. Online help provided to support OMC-G applications. A tool for comparing PCU and SGSN configuration data to ensure that the Gb link is correctly configured.
Configuration Online statistics User profiles Online help Gb link data export tool
PCU features
For details about new features for the Motorola PCU, see the 1613 release of System Information: General (GSM-100-101).
3rd May 01
105
GPRS-300-101

Introduction
This tables in this section list the new features in the 1.6.1.4 release of the GPRS software.
SGSN features
Table 10-6 lists the 1.6.1.4 features for the SGSN. Table 10-6 SGSN features implemented in Release 1.6.1.4 Feature Encryption Gp interface Description This release provides hardware and software encryption for signalling messages and user data sent over the air interface. The SGSN supports the Gp interface enabling limited roaming between two independent co-operating PLMN networks. In addition to signalling, the SGSN is now able to intercept data thereby providing a full lawful intercept function. The direct connection feature is an alternative method of connection that enables a GPRS network to bypass the CommHub and connect directly to a PDN over a leased line. OAMP management has been added for alarms and statistics generated across the Gr interface between the SF and the HLR. In addition, SF parameters can now be configured through the OMC-G GUI. The SF supports dual configuration mode: OAMP and TCL. SGSN supports MSISDN from an MS. The TF supports charging and complete S-CDR. The TF functions have been split onto two modules Lower TF (LTF) and Upper TF (UTF). The LTF module performs the SGSN communication protocol functions for the Gb interface. The UTF module performs the same functions for the Gn interface and also provides hardware encryption. The SGSN is compatible with SMG 31. HLR reset is supported. The SGSN supports Phase 3 of Network-Initiated Deactivation feature. The SGSN performs network deactivation when the Inter-RAU fails due to a GGSN Update Location error or QoS reduction on active CF PDP contexts. Any PDU that cannot fit into the PCU buffer will be discarded. Provides v.42bis data compression between an MS and an SGSN for up to 1000 subscribers in an SGSN (30,000 in an SGSN chassis).
Full lawful intercept Direct connect
SF OAMP management
SF dual configuration mode MS ISDN TF charging support TF card split
SMG 31 compliance HLR reset Network initiated deactivation
BSSGP BVC flow control design change V.42bis data compression
User-selectable Access Enables an MS to select a specific APN from those available Point Name (APN) in the Home Location Register (HLR).
3rd May 01
106
GPRS-300-101
GGSN features
The GGSN is a standard Cisco product with enhancements incorporated by Motorola. Table 10-7 describes only features incorporated by Motorola. For details about any new Cisco features implemented in this release, see the Cisco GGSN release notes. Table 10-7 GGSN features implemented in Release 1.6.1.4 Feature SMG 31 compliance Description The GGSN is compliant with SMG 31.
ISS Cluster features

Table 10-8 lists the 1.6.1.4 features for the ISS. Table 10-8 ISS features implemented in Release 1.6.1.4 Feature CNR 3.5.3 Description New CNR software release.
Sun Cluster Version 2.2 New Sun Cluster software release. BS transfer merge BS transfer files can be merged into a small set of larger files one file for each CDR type. This option is used only when transferring to a BS that cannot accept a large number of files for input.
CommHub features
No new CommHub features have been introduced in this release.
3rd May 01
107
GPRS-300-101
OMC-G features
Table 10-9 lists the 1.6.1.4 features for the OMC-G. Table 10-9 OMC-G features implemented in Release 1.6.1.4 Feature OMC-G platform SGSN alarms ISS alarms Cisco alarms Alarm filtering Alarm comment field Propagation Description The OMC-G UNIX server is a standalone unit. SGSN fault management actions executable from the OMC-G GUI. Support for ISS alarms provided. Additional GGSN and CommHub alarms supported. Subscriptions can be set up to block all alarms or events that match predefined criteria. A field is available in which users can enter alarm comments. The value of selected configuration parameters can be modified and propagated to one or more objects of the same type within the GPRS network. SGSN configuration data for the Gb link can be exported and saved for comparison with the corresponding data from the PCU to ensure that the link is correctly configured. Network access can be controlled by creating user profiles that have permission to access only those commands and regions for which they are authorized. Statistics are retrieved at a predefined interval from the Network Elements and stored in a relational database for 14 days. Load management support provided for the Shelf Manager and SS7 functions. The OMC-G manages the Gr interface between the SGSN SS7 Function and the HLR. Alarms can be received and parameters configured to enable the administration of the SGSN Lawful Intercept Relay Function. A simplified view of the event log database is provided to allow users to focus on specific alarm event data while screening out the underlying database tables. Support for exporting statistics to a higher level management system such as Metrica. Tool for implementing large-scale network changes. The database propagates changes from a planning system out to a network of SGSNs.
Configuration Management data export User profiles, regions and command groups Background statistics
SM and SS7 load management SF management Lawful Intercept support Event log
Statistics export DataBase (DB) Generator tool
PCU features
For details about new features for the Motorola PCU, see the 1614 release of System Information: General (GSM-100-101).
108
3rd May 01
Chapter 11
Glossary of technical terms and abbreviations
3rd May 01
GPRS-300-101
ii
3rd May 01
GPRS-300-101
Chapter 11 Glossary of technical terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . .

Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A ......................................................................... B ......................................................................... C ......................................................................... D ......................................................................... E ......................................................................... F ......................................................................... G ......................................................................... H ......................................................................... I .......................................................................... K ......................................................................... L ......................................................................... M ......................................................................... N ......................................................................... O ......................................................................... P ......................................................................... Q ......................................................................... R ......................................................................... S ......................................................................... T ......................................................................... U ......................................................................... V ......................................................................... W ........................................................................ X, Y, Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
111 112 115 118 1112 1115 1117 1119 1122 1123 1126 1127 1129 1132 1134 1135 1140 1141 1143 1147 1149 1150 1151 1152
3rd May 01
iii
GPRS-300-101
iv
3rd May 01
GPRS-300-101
Numbers
Numbers
# 10/100BASE-T Number. An Ethernet implementation in which the physical medium is an unshielded twisted pair of wires capable of carrying data at both 10 and 100 Mbps on the same port. First generation mobile network. The initial category of mobile wireless networks which uses analog technology only. Second generation mobile network. Generic term referring to the category of mobile wireless networks that first implemented digital technology. GSM is an example of a 2G mobile network standard. Second generation plus mobile network. Generic term referring to the category of mobile wireless technology that supports data rates higher than 2G. GPRS is an example of a 2G+ mobile network standard. Third generation mobile network. Generic term referring to the category of next-generation mobile networks. UMTS is an example of a 3G mobile network standard. As used in this manual set, the term applies to the European 4-wire 2.048 Mbit/s digital line or link which can carry 30 A-law PCM channels or 120 16 kbit/s GSM channels. 4 Generation Language.
1G mobile network 2G mobile network
2G+ mobile network
3G mobile network
2 Mbit/s link
4GL
3rd May 01
111
GPRS-300-101
A
A interface AA AAA AA-TID AB Abis interface ABT ac,AC ACK ACSE Interface between MSC and BSS. Anonymous Access. Authentication, Authorization and Accounting Anonymous Access-Tunnel IDentifier. Access Burst. Used by the MS to access the BTS and start a call. Interface between a remote BSC and BTS. Abort. Alternating Current ACKnowledgement. Associated Control Service Element. One of 3 Application Service Elements that reside in the application layer of the OSI protocol stack and act as an interface to the lower layer protocols. ADvanced Communications Control Protocol. A data link protocol used to provide point-to-point and point-to-multipoint transmission of data frames that contain error control information. ADCCP is similar to HDLC. ADMinistration Function. An LI function that interfaces with the LEAs and GSNs, and keeps concurrent interception activities separate. Abbreviated Dialling Number. A telephone service feature that enables a user to access a network by dialling less numbers than standard. Adaptive Differential Pulse Code Modulation. A form of PCM that produces a digital signal with a lower bit rate than standard PCM. Acoustic Echo Control. In a system, the reduction of the power level of an echo, or the elimination of an echo. Automatic Frequency Control. A device or circuit that maintains the frequency of an oscillator within the specified limits with respect to a reference frequency. Absolute Frame Number. Automatic Gain Control. A process or means by which gain is automatically adjusted in a specified manner as a function of a specified parameter such as received Access Grant CHannel. A GSM common control channel used to assign MS to a SDCCH or a TCH. In the client-server model, the part of the system that performs information preparation and exchange on behalf of a client or server application. Advanced Intelligent Network. The radio link between the BTS and the MS. Notification that a rising or falling threshold has been crossed.
ADCCP
ADMF
ADN
ADPCM
AEC AFC
AFN AGC
AGCH agentp
AIN Air interface Alarm
112
3rd May 01
GPRS-300-101
AMA
Automatic Message Accounting (processor). A service feature that automatically records data regarding user-dialled calls. American National Standards Institute. Voluntary organization that acts as a facilitator for developing US and international business standards. Advance Operational Impact. Application Programming Interface. Means of communication between two programs to give one program transparent access to the other. Access Point Name. Identifies the PDN to which an MS wishes to connect. The internal DNS function translates the APN into the IP address of the GGSN. The highest of 7 protocol layers in the OSI model. It performs application services and issues requests to the Presentation Layer. The GPRS application data such as email that is carried on GPRS carrier timeslots from all of the MSs in a cell. Overall design and structure of a network or communications system. The architecture influences the capabilities and limitations of the system. Absolute Radio Frequency Channel Number. An integer which defines the absolute RF channel number. Automatic ReQuest for retransmission. Address Resolution Protocol. A TCP/IP protocol that dynamically binds a Network Layer IP address to a Data Link Layer physical hardware address such as an Ethernet address. Association Control Service Element. An ASE which provides an AP with the means to establish and control an association with another AP in a remote network entity. Maps directly onto the Presentation layer. American Standard Code for Information Interchange. An ANSI standard where each alphabetic, numeric or special character is represented by a 8-bit (7 bits plus parity) binary number. Application Service Element. A coherent set of integrated functions used to communicate with an application entity. Application Specific Entity (TCAP). Abstract Syntax Notation One. A formal notation used for describing data transmitted by telecommunications protocols. Asynchronous Transfer Mode. A network technology based on transferring data in cells or packets of a fixed size. ATTach. Are You Alive. A heartbeat request. Authentication Centre.
ANSI,
AOI API
APN
Application Layer
Applied Load Architecture
ARFCN ARQ ARP
ASCE
ASCII
ASE ASE ASN.1 ATM ATT (flag) AYA AuC
3rd May 01
113
GPRS-300-101
Authentication and authorization Autonomous system
A method of verifying the identity of a user, validating a service request, and authorizing the users use of the service. A collection of networks under a common administration sharing a common routeing strategy. An autonomous system is assigned a unique 16-bit number by the IANA.
114
3rd May 01
GPRS-300-101
B
B Interface Backbone Backplane Bandwidth Bc Interface between MSC and VLR. A LAN or WAN that interconnects bridges, switches and routers. The main data bus within a device. A measure of the range of frequencies occupied by a signal. Committed Burst size.The maximum amount of data (in bits) that the network agrees to transfer, under normal conditions, during a time interval Tc. Broadcast Control CHannel. A GSM control channel used to broadcast general information about a BTS site on a per cell or sector basis. Beryllium. Burst Excess size. The maximum amount of uncommitted data (in bits) in excess of Bc that a Frame Relay network can attempt to deliver during a specified interval. The network delivers this data with a lower probability of success than the Bc size. Backward Explicit Congestion Notification. Bit set by a Frame Relay network in frames that are travelling in the opposite direction opposite to frames passing through a congested path. Bit Error Rate. A measure of signal quality in the GSM system. A service model providing minimum performance guarantees, allowing an unspecified variance in the measured performance criteria. Board Failure. Border Gateway. Router that communicates with routers in other autonomous systems. Border Gateway Protocol. An Internet protocol that enables groups of routers to share routeing information so that efficient, loop-free routes can be established. BGP is commonly used within and between ISPs. Busy Hour. In a communications system, the sliding 60-minute period that carries the maximum total traffic load in a 24-hour period. Binary digit. A character used to represent one of the two states or digits (0 or 1) in the binary numbering system. Bits per second. A measure of data transmission speed the number of bits transmitted in one second. Boot Load. Also known as download. BLock Error Rate. Full rate traffic channel. Bit Number. Number that identifies the position of a particular bit period within a timeslot. Traffic slowdown resulting from too many network nodes trying to access a server node at the same time.
BCCH
Be Be
BECN
BER Best effort
BFL, BRDFAIL BG BGP
BH
bit bit/s BL BLER Bm BN Bottleneck
3rd May 01
115
GPRS-300-101
Br BRI
Burst rate. Basic Rate Interface. The basic ISDN configuration which consists of two B-channels that can carry voice or data at the rate of 64 Kbps, and one D-channel, which carries call-control information. A device that interconnects local or remote networks forming a single logical network. Bridges operate at the physical and link layers of the OSI reference model. A device that can provide the functions of a bridge or router, or both concurrently. A bridge/router can route one or more protocols and bridge all other traffic. Billing System. Bearer Service. A type of telecommunication service that provides the capability for the transmission of signals between user-network interfaces. The PLMN connection type used to support a bearer service may be identical to that used to support other types of telecommunication service. Base Station Controller. A network component in the GSM PLMN that provides the control functions and physical links between the MSC and BTS. Billing System Frequency. Base Site control Processor (at BSC). Base Station System. Radio-related functions provided by the BTS and BSC in a GSM network. The BSS can also contain a PCU to enable packet-switching in a GSM system. BSS Application Part. Protocol for LAPD or LAPB signalling links on the A-interface. BSS GPRS Protocol. Provides radio-related information and performs node management functions between the SGSN and the BSS. Base Station System Management Application Part. Call processing protocol for A-interface messages exchanged between the MSC and BSS. Block Serial Tunnelling. Base Transceiver Station. A network component in the GSM PLMN which serves one cell, and is controlled by a BSC. The BTS contains one or more transceivers. Area in a device for temporary storage of data in transit. A buffer can accommodate differences in processing speeds between devices by storing data blocks until they are ready to be processed. A period of modulated carrier less than one timeslot. The physical content of a timeslot. An uneven pattern of data transmission. The physical pathway used to communicate between the CPU, memory and various input and output devices. BSSGP Virtual Connection. A data and signalling communication path across the Gb interface between remote BSSGP entities.
Bridge
Bridge/router
BS BS
BSC
BSFREQ BSP BSS
BSSAP BSSGP
BSSMAP
BSTUN BTS
Buffer
Burst Bursty traffic Bus BVC
116
3rd May 01
GPRS-300-101
BVCI Byte
BSSGP Virtual Connection Identifier. A sequence of adjacent binary digits (usually 8) operated upon as a unit. A byte is the smallest addressable unit of information in a data store or memory.
3rd May 01
117
GPRS-300-101
C
C Interface C7 CA CA Cabinet CAI CAMEL Card CB Interface between MSC and HLR/AUC. See SS7. Cell Allocation. The radio frequency channels allocated to a particular cell. Central Authority. Upright frame in which standard equipment can be installed. Charge Advice Information. Customised Applications for Mobile Enhanced Logic. A printed circuit assembly. Cell Balancer. Process that balances the cells configured for GPRS across PRPs. In the event of a PRP outage, the process sends messages indicating that GPRS service is unavailable to the appropriate Cell Resource Machines for the cells that could not be moved to an IN Service PRP. Cell Broadcast CHannel. The channel used to broadcast messages to all MSs in a specific cell. Common Control CHannel(s). A class of GSM control channels used to control paging and grant access. Includes AGCH, PCH, and RACH. Cluster Configuration Database. Control CHannel. Channels that carry system management messages. Comit Consultatif International Tlgraphique et Tlphonique. This term has been superseded by ITU-TSS (International Telecommunications Telecommunications Sector). Channel Coder-decoder (Coding) Unit. Performs channel coding and radio channel measurement functions. Call Detail Record. Record written to a database for use in postprocessing activities, primarily billing and network analysis. Compact Disk-Read Only Memory. An RF coverage area. At an omni-site, cell is synonymous with site; at a sectored site, cell is synonymous with sector. This differs from analog systems where cell is taken to mean the same thing as site European Committee for Electrotechnical Standardization. Confrence des administrations Europennes des Postes et Telecommunications, CCITT G.703/704 based European digital transmission facility (2.048 Mbit/s). Circuit Error Rate Monitor. Identifies discontinuity in a circuit. Control Function. CF performs the SGSN mobility and session management functions, and OAMP functions for the GSN module. Charging Gateway. CG collects and stores subscriber accounting data for collection by a Billing System.
3rd May 01
CBCH CCCH
CCD CCH CCITT
CCU CDR
CD-ROM Cell
CENELEC CEPT
CERM CF
CG
118
GPRS-300-101
CGF CGN Channel
Charging Gateway Function. CDR Generating Node. A means of one-way transmission. A defined sequence of periods (for example, timeslots) in a TDMA system; a defined frequency band in an FDMA system; a defined sequence of periods and frequency bands in a frequency hopped system. An equipment shelf with slots that accept modules and cards. Carrier-to-Interface ratio. Circuit Identity Code. A unique identifier for the terrestrial portion of a circuit path. Classless Inter-Domain Routeing. An newer IP addressing scheme that replaces the system based on Classes A, B, and C with one that allows a single IP address to designate many unique IP addresses. Coaxial Interconnect Module (also called T43). Unintelligible data produced using encryption. Committed Information Rate. A specified amount of guaranteed bandwidth (measured in bit/s) on a Frame Relay service. A communications channel between two or more points. Ciphering Key Sequence Number. Custom Local-Area Signalling Services. Voice only class of MS access. Voice and data class of MS access. Data only class of MS access. Command Line Interface. Software interface in which commands are entered on the keyboard as opposed to selecting items from a menu. Calling Line Identification Presentation. A supplementary service that enables a called party to identify the caller. Calling Line Identification Restriction. A supplementary service that allows a caller to withhold their identity from the called party. Clock. Connectionless Manager. Coordinates global control over the BSS by handling all connectionless messages including global resets, load limiting and circuit blocking. ConnectionLess Network Service. Packet-switched network in which each packet of data is independent and contains complete address and control information. This minimizes the effect of individual line failure and distributes the load more efficiently across the network. CLNS does not require a circuit to be established before data is transmitted. The Sun Netra t 1125 component of the ISS Cluster. Configuration Management. Enables operators to perform network configuration tasks and to maintain details of the network configuration at the OMC-G or OMC-R.
Chassis C/I CIC CIDR
CIM Ciphertext CIR
Circuit CKSN CLASS Class A Class B Class C CLI
CLIP CLIR
CLK CLM
CLNS
Cluster node CM
3rd May 01
119
GPRS-300-101
CMD CMM CMIP CMIS
CoMmanD. Channel Mode Modify. Message sent to an MS to request a channel mode change. Common Management Information Protocol. An OSI standard protocol used with CMIS. Common Management Information Service. An OSI network management service interface that monitors and controls heterogeneous networks. Common Management Information Service Element. Complementary Metal-Oxide Semiconductor. High-speed integrated circuit used in processors. CMOS uses little power and therefore generates little heat. Cisco Network Registrar. A Cisco product that provides DNS server capabilities to the GSN. Customer Network Resolution Centre. Carbon Dioxide. COder-DECoder. A speech coding unit that converts speech into a digital format for radio broadcast, and vice versa. Change of Location. Placed together; two or more items together in the same place. COMMunications. Communications Hub. Provides Ethernet switching and IP routeing for the GSN complex local networking and GSN complex E1 interfaces to the public data network. Communications Link. A cabinet holding the CommHub and ISS Cluster equipment. See cPCI. A service that allows transfer of information among service users without end-to-end call establishment procedures.
CMISE CMOS
CNR CNRC CO2 CODEC CoL Collocated COMM, Comms CommHub
CommsLink Communications cabinet Compact PCI
CONP CONS
Connection-Oriented Network Protocol. Connection-Oriented Network Service. An OSI protocol for packet-switched networks that exchange information over a virtual circuit. Control of Substances Hazardous to Health. 1999 health regulations. Call Processing. Process in the BTS that controls the MS-to-BSS-to-MS signalling link, MS originated and terminated calls, and inter-BSS and inter-BTS handovers. Customer Provided Equipment. Compact Peripheral Component Interconnect, a set of standards that define a common card cage, power supplies, and processor boards. Compact PCI. CCCH Paging Manager. Processes the paging messages sent from the SGSN to the BSC/BTS.
COSHH CP
CPE cPCI
CPGM
1110
3rd May 01
GPRS-300-101
CPU CPX8216 CR
Central Processing Unit. The portion of a computer that controls the interpretation and execution of instructions. SGSN chassis hardware model. Connection Request. An SCCP Connection Request message is sent form the BSS to the MSC to establish a connection. Cyclic Redundancy Check. Method for checking the accuracy of a digital transmission over a communications link. Cell Resource Manager. The CRM allocates and activates timeslots and subchannels on the available carriers. Controlled Roll Out. A customer site implementation of a new product, software release, or combination of products/releases. Circuit Switched. A method of providing a physical pathdedicated to a single connection between two end-points in a network, for the duration of the connection. Coding Scheme. Coding Scheme-1 (9.05 kbit/s per TCH). Coding Scheme-2 (13.4 kbit/s per TCH). Coding Scheme-1 (15.6 kbit/s per TCH). Coding Scheme-1 (21.4 kbit/s per TCH). CAMEL Service Environment. Code Storage Facility Processor (at BSC and BTS). A GPROC device that facilitates the propagation of new software with reduced system downtime. Central Statistics Process. The statistics process in the BSC. Control. Closed User Group. A supplementary service used to create a unique group whose members are authorized to receive or place calls over a specific interface.
CRC CRM CRO
CS
CS CS-1 CS-2 CS-3 CS-4 CSE CSFP
CSP CTL CUG
3rd May 01
1111
GPRS-300-101
D
D Interface DACS DataGen Datagram Interface between VLR and HLR. Digital Access Cross-connect System. Sysgen Builder System. A Motorola offline BSS binary object configuration tool. Logical block of data sent as a network layer unit over a transmission medium without first establishing a virtual circuit. IP datagrams are the primary information units in the Internet. The second layer in the OSI protocol stack model. It responds to service requests from the Network Layer and issues service requests to the Physical Layer. Decibel. A unit of power ratio measurement. Database. Dummy Burst. A period of carrier less than one timeslot whose modulation is a defined sequence that carries no useful information. A dummy burst fills a timeslot with an RF signal when no information is to be delivered to a channel. Data Bus Ready. DataBase Management System. A collection of programs that enable a user to store, modify and extract information from a database. Direct Current. Dedicated Control CHannel. A class of GSM control channels used to set up calls and report measurements. Includes SDCCH, FACCH, and SACCH. Data Circuit terminating Equipment or Data Communication Equipment. A device that communicates with a DTE device in RS-232C communications. Data Communications Network. A DCN connects Network Elements with internal mediation functions or mediation devices to the Operations Systems. DataGen Data Store. Store area for DataGen input and output files. Discard Eligibility. Applying an encryption algorithm in reverse to restore data to its original form. A transmission circuit installed between two sites in a private network and open, or available, at all times. Entry in a routeing table that redirects any frames for which the table has no listing for the next hop. DETach. Delivery Function. Decision Feedback Equalizer. A receiver component/function that results in a sharp BER threshold by using error feedback. Data Gathering Tool. Collects data relevant to a specific problem and copies it to tape or file, together with a problem description. The data is then sent to Motorola for analysis.
3rd May 01
Data Link Layer
dB DB DB
DBB DBMS
DC, dc DCCH
DCE
DCN
DDS DE Decryption Dedicated line Default route DET DF DFE DGT
1112
GPRS-300-101
DHCP
Dynamic Host Configuration Protocol. A protocol for assigning dynamic IP addresses to devices on a network. Dynamic addressing enables a device to have a different IP address each time it connects to the network. Discrete high- and low-voltage signals that represent 1s and 0s. Analog signals can be converted to digital signals using a CODEC. Data Link (layer). The second lowest layer in the OSI reference model. DownLink. A physical link from the BTS towards the MS (BTS transmits, MS receives). Data Link Connection. Data Link Connection Identifier. In Frame Relay transmission, the 13-bit field that defines the destination address of a packet. DownLink Segmenter. The DLS segments LLC frames into RLC data blocks to be transmitted over the air interface. Data Link Service Process. Handles messages for a Operation and Maintenance Processor and a shelf GPROC. Digital Link Signalling Processor. Control channel. ISDN terminology applied to mobile service. Directory Number. Data Network Identifier Code. A CCITT code where the first 4 digits indicate the international data number, the next 3 digits are the country code, and the final digit is the network code. Domain Name Service. A service that translates from logical domain or equipment names to IP addresses. Data PROCessor board (in PCU). Dynamic RAM. A memory technology characterized by high density and low power. Data Rate Converter board. Provides data and protocol conversion between PLMN and destination network for 8 circuits (p/o IWF). Digital Radio Interface. Part of the BSS. Provides encoding/decoding and encryption/decryption for radio channels. Digital Radio Interface Module. A DRI with extra memory. Discontinuous Receiver/Reception. A means of saving battery power by periodically and automatically switching the MS receiver on and off. Digital Service Zero (0). A single 64 kbit/s timeslot on a T1digital interface. Digital Signal Processor. A specialized, programmable computer processing unit that can perform high-speed mathematical processing. Digital Subscriber Signalling. An ISDN user network interface method of signalling. Direct Transfer Application Part.
Digital signals
DL DL DLC DLCI
DLS DLSP DLSP Dm DN DNIC
DNS DPROC DRAM DRC
DRI
DRIM DRX
DS0 DSP
DSS DTAP
3rd May 01
1113
GPRS-300-101
DTE
Data Terminal Equipment. An end instrument that converts user information into signals for transmission, or reconverts the received signals into user information. Data Transfer Rate. Discontinuous Transmission. A method of saving battery power and reducing interference by automatically switching the transmitter off when no data or speech is being sent. Digital Video Decoder. Routeing that adjusts automatically to changes in network topology or traffic.
DTR DTx
DVD Dynamic routeing
1114
3rd May 01
GPRS-300-101
E
E1 European designation for T1. Wide-area digital transmission scheme that carries data at a rate of 2.048 Mbit/s. E1 lines can be leased for private use from common carriers. Interface between MSC and MSC. Error Correction Code. The Motorola European Cellular Infrastructure Division. Explicit Call Transfer. Enhanced Data for GSM Evolution. An extension to the GSM standard that provides higher speed access. Equipment Engineering. Electrically Erasable Programmable Read-Only Memory. EPROM that can be erased using electrical signals applied to specific pins. See also EPROM. This is the true load carried by a cell from all of the mobiles after the Applied Load has been wrapped by the GPRS protocols and weighted by the expected BLER, V.42 bis data compression, and TCP/IP header compression. Enhanced Full Rate. A voice coding algorithm. Exterior Gateway Protocol. Internet routeing protocol by which gateways exchange information about which systems they can reach. Enhanced GPRS. Enhanced Integrated Design (Disk) Electronics. Equipment Identity Register. Contains a centralized database for validating the IMEI. Electromagnetic Compatibility society. An IEEE group that develops standards and performs other functions designed to enhance electromagnetic compatibility. Wrapping a data unit with a protocol header containing address and control information. Applying a specific algorithm to data in order to alter the appearance of the data and prevent other devices from reading the information. Erasable Programmable Read-Only Memory. Nonvolatile memory chips that are programmed after manufacture and can be erased and reprogrammed. See Also EEPROM. International (dimensionless) unit of traffic intensity defined as the ratio of time a facility is occupied to the time it is available for occupancy. One erlang is equal to 36 CCS. In the US this is also known as a traffic unit (TU). ERRor. Encoding Scheme. Electrostatic Discharge. Encapsulating Security Payload. Electro-static Point. Connection point on the equipment for an anti-static wrist strap.
E Interface ECC ECID ECT EDGE EE EEPROM
Effective Load
EFR EGP
EGPRS EIDE EIR EMC
Encapsulation Encryption
EPROM
Erlang
ERR ES ESD ESP ESP
3rd May 01
1115
GPRS-300-101
Ethernet ETR ETS ETSI Expansion cabinet
A LAN standard network protocol that uses radio frequency signals carried by coaxial cables. ETSI Technical Report. European Telecommunication Standard. European Telecommunications Standards Institute. An organization that produces telecommunications standards. A cabinet holding the GSN equipment, including the GGSN chassis and SGSN chassis.
1116
3rd May 01
GPRS-300-101
F
F Interface FBM Interface between MSC and EIR. Flow control Buffer Management. A functional unit that resides on the PRP and controls buffer capacity for each cell and mobile. This allows the incoming data from the SGSN to match the air throughput. Federal Communications Commission. US government agency that controls electronic transmission standards. Frequency Correction CHannel. A GSM broadcast control channel that carries information for MS frequency correction. Frame Check Sum. The extra characters added to a frame for error detection and correction. Fibre Distributed Data Interface. LAN technology that permits data transfer on fibre-optic cable at up to 100 Mbps. Frequency Division Multiple Access. Each physical channel occupies one carrier frequency and requires a separate transmitter. Forward Error Correction. Forward Explicit Congestion Notification. The bit that informs the DTE receiving the frame that there was congestion in the path followed by the frame. Front End Processor. An OMC driver that stores data about all the sites in the system in its own database. Field Effect Transistor. Frequency Hopping. The repeated switching of frequencies during radio transmission, according to a specified algorithm. Frequency Hopping Index. A security system that enforces an access control policy between a network and the Internet. A special type of EEPROM that provides non-volatile storage and can be electrically erased and reprogrammed. Method for ensuring that a transmitting device does not overwhelm a receiving device with data. Fault Management. Frequency Modulation. Fault Management Initiated Clear. Field Programmable Gate Array. Fully Qualified Domain Name. Period of RF carrier less than one timeslot whose modulation bit stream allows frequency correction to be performed easily within an MS burst. FR Frame Frame Relay. A packet-switching protocol for connecting devices on a WAN at high speeds. Set of bits that form an elementary block of data to be sent over a communications channel. A frame usually contains its own control information. Frame relay Permanent virtual circuit.
FCC FCCH FCS FDDI FDMA
FEC FECN
FEP FET FH FHI Firewall Flash Flow control FM FM FMIC FPGA FQDN
FrPvc
3rd May 01
1117
GPRS-300-101
FRF FRU FSN FTAM FTD FTP FU
Frame Relay Forum. Field Replaceable Unit. Forward Sequence Number. File Transfer Access and Management. File Transit Delay. File Transfer Protocol. A client-server protocol that allows a user on one computer to transfer files to and from another Functional Unit.
1118
3rd May 01
GPRS-300-101
G
G Interface Ga Gateway Interface between VLR and VLR. Interface between the CGF and SGSN, and the CGF and GGSN. Device that performs protocol-conversion to interconnect networks that have different, incompatible communications protocols. Gigabyte. Interface between the SGSN and PCU (BSS). Card that performs the SGSN communication protocol functions for a single Gb interface. Also called LTF module. The cable that carries GPRS user data and signalling information between the PCU and SGSN using Frame Relay over E1. Gb Manager. Gigabits per second (equivalent to 1000 Mbps). GGSN-Call Detail Record. GDS Channel Identifier (16kbit/s resource used for data). Interface between the CommHub and HLR. Generator CoMmanD (CoMmanD Generator). GPRS Data Link. GPRS Data Stream. The GSLs are provisioned over one or two E1s between the BSC and PCU. Each GDS LAPD channel uses 64 kbit/s of bandwidth on an E1. This LAPD link carries out-of-band GPRS signalling information, PCU statistics, and other PCU O&M information such as software code loads. The GDS TRAU is provisioned by the network operator over one to ten E1s between the BSC and PCU. These E1s carry GPRS user data. GPRS Encryption Module. GSN CommHub firewall screening. GGSN-CONTROL, GGSN-GiPROC, GGSN-GNPROC integrated functions Gateway GPRS Support Node. A GPRS network entity that serves as the mobile wireless gateway between an SGSN and PDNs. GGSN-CONTROL function. GGSN Gi Processor. GGSN Gn Processor. Giga-Hertz (10). Reference point between a GGSN and an external PDN. General Manual Revision. GPRS Mobility Management (see MM). Gateway Mobile-services Switching Centre.
GB, Gbyte Gb Gb card Gb link
GBM Gbps G-CDR GCI Gc GCMD GDL GDS GDS LAPD (GSL)
GDS TRAU
GEM Gg gg GGSN
GGSN-CONTROL GGSN-GiPROC GGSN-GNPROC GHz Gi GMR GMM GMSC
3rd May 01
1119
GPRS-300-101
GMT Gn Gn card GND GOS G-PDU
Greenwich Mean Time. Interface between two GSNs within the same PLMN. Card that performs the SGSN communication protocol functions for a single Gn interface. Also called UTF module. GrouND. Grade Of Service. A traffic statistic defined as the percentage of calls that have a probability of Busy or Queueing Delay. GTP-Packet Data Unit. A GTP packet that contains a T-PDU encapsulated by a GTP header. G-PDUs are transmitted between GSNs in a GTP tunnel. Interface between two GSNs in different PLMNs. Generic Processor board. General Packet Radio Service. An ETSI standard that defines the implementation of packet data services on a GSM network. GPRS-Attach is performed when the MS indicates its presence to the PLMN for the purpose of using the GPRS PTP service. GPRS-Detach is performed when the MS indicates to the PLMN that the MS is no longer using the GPRS services. Global Positioning by Satellite. A system for determining position on the surface of the Earth by comparing radio signals from several satellites. Gb Router. Interface between an SGSN and an HLR. The cable that carries information between the SGSN and HLR. Generic Route Encapsulation. Interface between an SGSN and an MSC/VLR. GPRS Signalling Link. Groupe Spcial Mobile (the committee). Global System for Mobile communications (the system). A 2Gdigital mobile telephone system standardized by ETSI. GSM Radio Frequency. GPRS Support Node. The combined functions provided by the SGSN and GGSN. GSNs and an ISS Cluster connected to a single CommHub. GSM System Release. Global Title Address Information. Global Title Indication. Gb Transmit Manager or Gateway Transmit Manager. GPRS Tunnelling Protocol. Protocol that handles the flow of packet data and signalling information between the SGSN and GGSN. GTP Prime.
Gp GPROC GPRS
GPRS-Attach
GPRS-Detach GPS
GR Gr Gr link GRE Gs GSL GSM GSM GSMRF GSN GSN Complex GSR GTAI GTI GTM GTP
GTP
1120
3rd May 01
GPRS-300-101
GTP tunnel
A tunnel, referenced by a TID and defined by 2 associated PDP contexts, used to communicate between an external PDN and an MS. A GTP tunnel is created each time an SGSN sends a Create PDP Context Request. Global Title Translation. Period at the beginning and end of timeslot during which MS transmission is attenuated. Graphical User Interface. The graphics-based user interface that an application provides that allows users to pull down menus, point and click, or otherwise choose commands or actions. GateWay Manager. GateWaY (MSC/LR) interface to PSTN.
GTT Guard period GUI
GWM GWY
3rd May 01
1121
GPRS-300-101
H
HA HADA HA Disk Array High Availability. High Availability Disk Array. This term is now superseded. See HA Disk Array. High Availability Disk Array. A Sun Netra D1000 that provides reliable, long-term storage for network configuration, software loads, charging data information and network statistics. High Availability Network File System. Interface between HLR and AUC. High level Data Link Control. ITU-TSS link layer protocol standard for point-to-point and multi-point communications. High bit-rate Digital Subscriber Line. A data transmission mechanism that supports duplex high speed digital communication (at E1 rates) on one or more unshielded twisted pair lines. High Layer Compatibility. The HLC can carry information defining the higher layer characteristics of a teleservice active on the terminal. Home Location Register. The register where the current location and all subscriber parameters of an MS are permanently stored. Home Location Register Service. Able to replace a card in a hardware device without turning it off or losing functionality. Home PLMN. Hot Swap Controller. HLR Subscriber Management. HA Standby Router Protocol. High-Speed Serial Interface. A de facto standard for high-speed serial communications over WAN links. Hardware. 2048 superframes. The longest recurrent time period of the frame structure.
HA NFS H Interface HDLC HDSL
HLC
HLR
HLRS Hot-swappable HPLMN HSC HSM HSRP HSSI HW Hyperframe
1122
3rd May 01
GPRS-300-101
I
IA IAM Incoming Access. A supplementary service that allows a member of a CUG to receive calls from outside the CUG. Initial Address Message. A message sent in the forward direction that contains information about addresses, signalling, service-class, user and network facilities, and call-originator or call-receiver identity. Internet Assigned Numbers Authority. Internet Corporation for Assigned Names and Numbers. Internet Control Message Protocol. In TCP/IP, the collection of messages exchanged by IP modules in both hosts and gateways to report errors, problems and operating information. Identifier. Integrated Drive Electronics. Intercept Data Product. All user data sent or received by a Lawful Intercept target. Integrated Digital Network. A network that uses both digital transmission and digital switching. Information Element (signalling). International Electrotechnical Commission. Institution of Electrical Engineers. Institute of Electrical and Electronic Engineers. Committees that develop and propose computer standards that define the physical and data link protocols of communication networks. Internet Engineering Task Force. The main standards organization for the Internet. Interim European Telecommunication Standard. Internet Hosted Octet Stream. International Mobile station Equipment Identity. Electronic serial number that uniquely identifies an MS as an assembly of equipment. Interception Management System. The software function that manages a LIAN. International Mobile Subscriber Identity. A unique identifier stored in the SIM of an MS. The common boundary between two associated systems. A world-wide TCP/IP network made up of several large backbone networks connecting to countless regional and local networks. The 32-bit address assigned to hosts using TCP/IP. The general term used to describe the inter-operation of networks, services, and supplementary services. A recording period of time in which a statistic is pegged. Internetworking Operating System. Input/Output.
IANA ICANN ICMP
ID IDE IDP IDN IE IEC IEE IEEE
IETF I-ETS IHOS IMEI
IMS IMSI Interface Internet
Internet address Interworking Interval IOS I/O
3rd May 01
1123
GPRS-300-101
IP IP
Initialization Process. Process responsible for bringing up the site from a reset. Internet Protocol. Standard protocol designed for use in interconnected systems of packet-switched computer communications networks. IP deals only with packets. Inter-Process Communication. Exchange of data between one process and another, either within the same computer or over a network. IP Security. A framework of open standards that provides data confidentiality, integrity, and authentication between participating peers. Indicator Ready. Intercept Related Information. Collection of GPRS signalling information associated with telecommunications services involving an LI target. For example, GPRS Attach Request, Modify PDP Context Request, or Cell Update Request. Industry Standard Architecture. A 16-bit bus design used for Intel-based personal computers. Integrated Services Digital Network. A standard for providing digital connections between user-network interfaces over public telephone networks. Integrated Systems Management. International Organisation for Standardization. A world-wide federation of national standards bodies. Internet Service Provider. Commercial organization that provides Internet access to individuals and organizations. Integrated Support Server. The ISS resides on a Sun Netra t 1125 and performs the CGF, DNS, NTP, and NFS functions for the GSN. The ISS Cluster comprises the ISS plus the HA Disk Array and Terminal Concentrator. ISDN User Part. An upper-layer application supported by SS7 for connection setup and teardown. Information Transfer Capability. A GSM Bearer Capability Element that supports terminal adaptation function to Interworking control procedures. International Telecommunication Union. An organization established by the United Nations to set international telecommunications standards and allocate frequencies for specific uses. ITU Telecommunications standardization sector. The standardization functions of this body were previously performed by CCITT, a group within the ITU. InterWorking Function. A network functional entity which provides network interworking, service interworking, supplementary service interworking or signalling interworking. It may be a part of one or more logical or physical entities in a GSM PLMN.
IPC
IPSec
IRDY IRI
ISA ISDN
ISM ISO ISP ISS
ISS Cluster ISUP ITC
ITU
ITU-T
IWF
1124
3rd May 01
GPRS-300-101
IWMSC IWU
InterWorking MSC. An MSSC used to deliver data to or from an SGSN. InterWorking Unit. Unit where the digital-to-analog and analog-to-digital conversion takes place within a GSM network.
3rd May 01
1125
GPRS-300-101
K
k kbit kbit/s kbyte Kc kg kHz kph kW kilo (10-3). kilobit. 1 kbit is1,024 bits for technical purposes; 1,000 bits for general purposes. kilobits per second. A transmission rate expressed in thousands of bits per second. kilobyte. A transmission rate expressed in thousands of bytes per second. Ciphering key. A sequence of symbols that controls enciphering and deciphering. kilogram. kilo-Hertz (10-3). Kilometres per hour. kilo-Watt.
1126
3rd May 01
GPRS-300-101
L
L1 L2 L3 L3MM L4 L5 L6 L7 LA LAC LAI Layer 1. The first layer of a communications protocol.See Physical layer. Layer 2. The second layer of a communications protocol. See Data Link layer. Layer 3. Third layer of a communications protocol. See Network layer. Layer 3 Mobility Management. Layer 4. The fourth layer of a communications protocol. See Transport layer. Layer 5. The fifth layer of a communications protocol. See Session layer. Layer 6. The sixth layer of a communications protocol. See Presentation layer. Layer 7. The seventh layer of a communications protocol. See Application layer. Location Area. An area in which an MS may move freely without updating the location register. Location Area Code. Part of the LAI. The operator-defined code that identifies the location area. Location Area Identity. The information indicating the location area in which a cell is located. The LAI data on the SIM is continuously updated to reflect the current location of the MS. Local Area Network. A group of devices that share a common communications line and the resources of a single processor or server within a small geographic area such as an office building. Link Access Protocol Balanced. The balanced-mode, enhanced version of HDLC. Link Access Protocol D-channel (Data). A protocol that operates at layer 2 of the OSIarchitecture. Used to convey information between layer 3 entities across the FR network. The D-channel carries signalling information for circuit switching. Link Access Protocol-GPRS. A level of the OSI reference model. Each layer performs certain tasks to move the information. Protocols within the layers define the tasks for networks, but not how the software accomplishes the tasks. Liquid Crystal Display. An alphanumeric display on computers and other devices using liquid crystal sealed between two pieces of glass. Law Enforcement Agency. A body authorized by law to intercept transmissions on a GPRS PLMN. Computer nodes located at LEA sites and containing secure tunnelling software for providing a secure communication link for IRI and IDP data transfer from the LIAN. A transmission line reserved by a communications carrier for the private use of a customer.
LAN
LAPB LAPD
LAP-G Layer
LCD
LEA LEA clients
Leased line
3rd May 01
1127
GPRS-300-101
LED
Light-Emitting Diode. A semiconductor device that emits light when connected in a circuit. LEDs are frequently used to indicate hardware equipment status. Lawful Intercept. A function that provides the ability to track and monitor signalling information and user data for a particular MS. Lawful Intercept Administration Node. The node from which LI is managed. The LIAN consists of the administrative function (ADMF) and two delivery functions (IRI and IDP). A physical or logical connection between two points. Lawful Intercept Relay Function. Logical Link Control. The upper part of layer 2 (data link layer) in the OSI reference model. Logical Link GPRS Mobility Management. Logical Link Short Message Service. Local Management Interface. A Frame Relay specification that defines a method of exchanging status information between devices such as routers. A method of spreading server traffic over multiple links to relieve congestion. List of Required Parts. Localized Service Area. Link Stations Signalling Unit (Part of MTP transport system). Lower Transmission Function. Gb interface communication protocol functions. Location Update. An event initiated by the MS when it detects that it has entered a new location area.
LI
LIAN
Link LIRF LLC LLGMM LLSMS LMI
Load balancing LORP LSA LSSU LTF LU
1128
3rd May 01
GPRS-300-101
M
M MAC Mega 10-6. Media Access Control. MAC includes the functions related to the management of the common transmission resources, including packet data physical channels and their radio link connections. Mobile Allocation Channel Number. Mobile Application Part (of SS7). The inter-networking signalling between MSCs and LRs and EIRs. Mobile Application Part Processor. Megabit. One million binary bits. Megabyte. One million binary bytes. Megabits per second. A bit rate expressed in millions of binary bits per second. Mobile Country Code. The first three digits of the IMSI, used to identify the country. M-CDR Collection Function. Motorola Customer Data Format used by DataGen for simple data entry and retrieval. Mobility management-Call Detail Record. Motorola Computer Group. Main Control Processor. M-CDR Transfer Function. Mediation Device. A device that allows the OSI processor to communicate between the NMC and the OMCs (OMC-G and OMC-R) for network configuration, events and alarms. Mobile Equipment. Equipment intended to access a set of GSM PLMN and/or DCS telecommunications services, but which does not contain subscriber-related information. A group of physical slices that the system sees as a single, logical device. Metadevices increase storage capacity and data availability. MultiFrame. In PCM systems, a set of consecutive frames in which the position of each frame can be identified by reference to a multiframe alignment signal. Mega-Hertz (10-6). Management Information Base. A database holding all the information about all the resources managed by the OMC-G or OMC-R. The MIB is accessed by the OMC using SNMP. A cell in which the base station antenna is generally mounted below rooftop level. Radio wave propagation is by diffraction and scattering around buildings, the main propagation is within street canyons. minute(s). micro-second (106).
MACN MAP MAPP Mb, Mbit MB, Mbyte Mbps, Mbit/s MCC MCCF MCDF M-CDR MCG MCP MCTF MD
ME
Metadevice
MF
MHz MIB
Microcell
min ms
3rd May 01
1129
GPRS-300-101
MLS
MultiLayer Switching. Scales Layer 3 performance to high performance link speeds by extending the MLS concept, introduced in Cisco IOS software, to LAN switching hardware. Mobility Management. Functions that track the current location of an MS including authorization, location updating, IMSI attach/detach, periodic registration, ID confidentiality, paging and handover. Man-Machine Interface. The method by which a userinterfaces with software through a terminal. Multiple Serial Interface Link (one of two T1 links) on the MSI board. Mobile Network Code. The fourth, fifth and optionally sixth digits of the IMSI, used to identify the network. Mobile station Not Reachable for GPRS (flag). Mobile station Not Reachable Reason. Mobile Originated. Metal Oxide Semiconductor. Motorola Abis Interface. A self-contained, separable assembly of electronic parts and software such as the three-card set that makes up the SGSN. Memorandum of Understanding. A document that sets out the broad parameters of an understanding as well as the general responsibilities and obligations of each party in the proposed venture. MasterPROCessor board (in PCU). Mobile Station. The GSM/GPRS subscriber unit used to access network services. GPRS supports three classes of MS Class A, Class B and Class C. Mobile Switching Centre. A telephone switching service that controls calls between telephone and data systems. millisecond (.001 second). Multiple Serial Interface board. Intelligent interface to two 2 Mbit/s digital links. Mobile Station Identification Number. The part of the IMSI identifying the MS within its home network. Mobile Station International ISDN number. Published mobile number that uniquely defines the MS as an ISDN terminal. It consists of 3 parts: The Country Code, the National Destination Code, and the Subscriber Number. Mobile Station Roaming Number. A number assigned by the MSC to service and track a visiting subscriber. Message Signal Unit. Part of the MTP transport system. A signal unit containing a service information octet and a signalling information field which is retransmitted by the signalling link control, if it is received in error. Mobile Terminal. A subscriber unit in a mobile system. See the entry for MS the MT specific to GPRS. Mobile Terminated. Describes a call or short message destined for an MS.
3rd May 01
MM
MMI MMS MNC MNRG MNRR MO MOS Mobis Module MoU
MPROC MS
MSC msec MSI MSIN MSISDN
MSRN MSU
MT MT
1130
GPRS-300-101
MTBF
Mean Time Between Failures. An indicator of expected system reliability calculated on a statistical basis from the known failure rates of various system components. MTBF is usually expressed in hours. Message Transfer Link. The 64 kbit/s PCM timeslot used to convey the SS7 signalling information on the A interface. Mobile-To-Mobile (call). Message Transfer Part. The part of the SS7 protocol that transfers signalling messages and performs associated functions such as error control and signalling link security. MTP consists of three layers MTP1, MTP2 and MTP3. Message Transfer Part One. SS7 physical layer that defines the physical, electrical, and functional characteristics of the digital signalling link. Message Transfer Part Two. SS7 data link layer that exercises flow control, message sequence validation, error checking, and retransmission. Message Transfer Part Three. SS7 network level that provides messages between signalling points in the network, helping control traffic when congestion or failures occur. Mobile Terminated Point-to-Point messages. Transmission of a short message from a message handling system to an MS. A method of broadcasting where copies of a packet are delivered only to a subset of all possible destinations. Two types of multiframe are defined in the system: a 26-frame multiframe with a period of 120 ms and a 51-frame multiframe with a period of 3060/13 ms. Multiplexer. A device that combines multiple inputs into an aggregate signal to be transported via a single transmission channel.
MTL MTM MTP
MTP1
MTP2
MTP3
MT/PP Multicast Multiframe
MUX
3rd May 01
1131
GPRS-300-101
N
N/W NAI NAK NAT NB NC0 NC1 NC2 NCO NCH Network. Nature of Address Identification. Negative Acknowledgment. Network Address Translation. Normal Burst. A period of modulated carrier less than a timeslot. Network Cell reselection mode 0. Network Control Option 1. Network Control Option 2. Network Control Option. Notification CHannel. Part of the downlink element of the CCCH reserved for voice group and/or voice broadcast calls and notification messages. National Destination Code. Part of the MSISDN. Network Element. A network component managed by the OMC-G or OMC-R. Norme Europennes de Telecommunications. A protocol layer that responds to service requests from the Transport Layer and issues service request to the Data Link Layer. This layer provides network routeing, flow control, segmentation/desegmentation, and error control functions. NetFlow Feature Card. Network File System. A file system distributed over a computer network. Also, a file system, on a single computer, that contains the low-level networking files for an entire network. The NFS server provides reliable long-term storage for network configuration, software storage, charging data information, and network statistics. Network Indicator. Network Interface Board. A circuit card that provides network access. Network Interface Card. A circuit board that enables a computer to be attached to a network. Network Information Service. A function that allows centralised control of network information. For example hostnames, IP addresses and passwords. Network Management. All activities that control, monitor, and record the use and performance of resources in a telecommunications network. Newton metres. Network Management Centre. The highest-level management node in a network, linked to subordinate OMC nodes. Non-Maskable Interrupt.
NDC NE NET Network layer
NFFC NFS
NFS server
NI NIB NIC NIS
NM
Nm NMC NMI
1132
3rd May 01
GPRS-300-101
NMSI Node NP NS NS-VC NS-VCI NS-VL NS-VLI NSAP
National Mobile Station Identification number. The MNC and MSIN combined. A point of connectivity. Numbering Plan. Network Service. Network Service-Virtual Circuit NS-VC Identifier. Network Service-Virtual Link. NS-VL Identifier. Network Service Access Point. A registration specifying the desired listening criteria of an application. The registration is limited to a particular CPU and port number. Criteria can include DNICs, national numbers, subaddress ranges, protocol IDs and extended addresses. NSAP Identifier. Network Service Entity Identifier. Identifier of an NS entity. Network SubSystem. Network Service Virtual Circuit. A logical circuit that connects the NSE peers between the SGSN and the PCU. The NSVC has significance across the network and is therefore configured identically at both the SGSN and PCU. NSVC Identifier. Uniquely identifies one NSVC. There is a one-to-one mapping between the NSVCI and DLCI. Name and Time Function. Network Time Protocol. A protocol that synchronizes the time of GSN components with reference to radio, atomic or other clocks located on the Internet. Non-Volatile Random Access Memory. Static random access memory converted into non-volatile storage either by using a permanently-connected battery or by saving its contents to EEPROM before powering off and reloading when power is restored. NVRAM Run Control. Nano-Watt (10-9).
NSAPI NSEI NSS NSVC
NSVCI NTF NTP
NVRAM
NVRAMRC nW
3rd May 01
1133
GPRS-300-101
O
OAMP OA&M O&M OID OIR OMAP OMC Operation, Administration, Maintenance and Provisioning. Operation, Administration & Monitoring. Operations and Maintenance. Object Identifier. Online Insertion and Removal. Operations and Maintenance Application Part of SS7 (previously OAMP). Operations and Maintenance Centre. The OMC provides dynamic O&M monitoring and control of the PLMN nodes operating in the geographical area controlled by the specific OMC. Operations and Maintenance Centre GPRS. The OMC-G provides an interface for managing the GSN functions of a GPRS network. Operations and Maintenance Centre Radio. For GPRS, the OMC-R provides an interface for managing the PCU. Italso manages all GSM functions. Out Of Service. Operating System. Open Systems Interconnection. A seven-layer reference model for defining communication between points in a telecommunications network. Open Shortest Path First. Interior Gateway protocol for TCP/IP. Uses an algorithm that calculates routes for packets based on a number of factors including least number of hops,speed of transmission lines, and congestion delays.
OMC-G
OMC-R
OOS OS OSI
OSPF
1134
3rd May 01
GPRS-300-101
P
P1 P2 P3 PA PACCH Packet Problem report, level 1 emergency priority. Problem report, level 2 high priority. Problem report, level 3 medium priority. Port Adapter. Packet Associated Control CHannel. A sequence of bits, including data and control signals, transmitted as a single logical block over a packet-switched network. A network in which data is transmitted in packets. The packets are sent individually over the best available network connection and then reassembled at the destination to form a complete message. The process of routeing and transferring data using addressed packets so a channel is occupied only during transmission and is then available to other traffic. Packet Assembler/Disassembler. A hardware device that allows a data terminal not set up for packet switching to use a packet switching network. The PAD assembles data into packets for transmission and disassembles the packets on arrival. Packet Access Grant CHannel. The procedure by which a GSM PLMN fixed infrastructure attempts to reach an MS within its location area, before any other network-initiated procedure can take place. A computer program that determines the syntactic structure of a sentence or string of symbols in a computer language. Port Address Translation. PCU processor Bridge Board. Allows an MPROC to be linked to a separate bus. Packet Broadcast Control CHannel. Personal Computer. A general-purpose microcomputer designed to be operated by one person at a time. Power Control. Point Code. PCU Control Authority. A PCU software process that maintains a list containing the status of each device and software process at the site. Parallel Channel Adapter. Printed Circuit Board. Packet Common Control CHannel. Paging CHannel. A GSM common control channel used to send paging messages to the MSs. Physical Channel. The medium over which information is carried such as the air interface or Ethernet. Packet Control Interface.
Packet-switched network
Packet switching
PAD
PAGCH Paging
Parser PAT PBB PBCCH PC PC PC pCA
PCA PCB PCCCH PCH PCHN PCI
3rd May 01
1135
GPRS-300-101
PCI
Peripheral Component Interconnect. A high-performance internal interconnect bus used for data transfer to peripheral controller components. PCU Configuration Management. A process that distributesdatabase changes performed at the BSC to the PCU boards. Pulse Code Modulation. Technique for converting an analog signal with an infinite number of possible values into discrete binary digital words that have a finite number of values. Personal Computer Memory Card International Association. The organization that developed the standard for a card that can be plugged into a specially-designed bus and be operational without further system modification. Personal Communications Service. The FCC term used to describe a set of digital cellular technologies being deployed in the US. PCS works over GSM, CDMA and North American TDMA air interfaces. Packet Control Unit. A BSS component that provides GPRS with packet scheduling over the air interface with the MS, and packet segmentization and packetization across the Frame Relay link with the SGSN. Empty equipment chassis in which the PCU hardware modules will be housed. PCU chassis complete with PCU modules. Protocol Discriminator. The first octet of the packet header that identifies the protocol used to transport the frame. Packet Data Channel. PDCH carries a combination of PBCCH and PDTCH logical channels. Public Data Network. Packet-switched network that provides customers with wide area network services, usually for a fee. Packet Data Protocol. Network protocol used by external PDNs to communicate with a GPRS network. A set of information used by MSs and GSNs to identify the wireless session. Packet Data Traffic CHannel. Protocol Data Unit. OSI terminology for packet. A PDU is a data object exchanged by protocol machines within a given layer of the OSI protocol model. It contains both protocol control information and user data. A single incremental action modifying the value of a statistic. Modifying a statistical value. Performance. PCU Fault Collection Process. PCU Fault Transaction/Translation Process. Process to which all PCU alarms are reported. Packet Handler. Process that assembles and disassembles packets. Packet Handler Interface.
pCM
PCM
PCMCIA
PCS
PCU
PCU chassis PCU unit PD PDCH PDN PDP PDP context PDTCH PDU
Peg Pegging Perf pFCP pFTP PH PHI
1136
3rd May 01
GPRS-300-101
Physical layer
The OSI protocol layer that performs services requested by the Data Link Layer including establishing and terminating connections. PMC Interface Module. PCI Industrial Computers Manufacturing Group. Packet Interface Control Processor. A PCU hardware component used for interfacing with the SGSN and BSC. Packet Internet Groper. A utility that sends a packet to a specific IP address to see if the component is alive. Primarily used to troubleshoot Internet connections. Phase Lock Loop. A mechanism whereby timing information is transferred within a data stream and the receiver derives the signal element timing by locking its local clock source to the received timing information. Public Land Mobile Network. The mobile communications network that uses earth-based stations (as opposed to satellites). PCI Mezzanine Card. Plugin Memory/E1. Plugin Memory/T1. Packet Notification CHannel. Point of Interconnection (with PSTN). Method of controlling the transmission sequence by requiring each device on a multipoint line to wait until the polling processor requests it to transmit. Post Office Protocol version 3. Plain Old Telephone Service. The existing conventional analog telephone service. Point-to-Point. PCI (Peripheral Component Interconnect) to PCI Bridge. A board that allows an MPROC to be linked to a separate bus. Parts per billion. Power PC. Packet Paging CHannel. Paging Proceed Flag. Parts per million (x 10-6). Packets per second. Point-to-Point Protocol. Protocol that provides router-to-router and host-to-network connections over both synchronous and asynchronous circuits. Problem Report. Packet Random Access CHannel. The protocol layer that responds to service requests from the Application Layer and issues service requests to the Session Layer. It relieves the Application Layer of concern regarding syntactical differences in data representation within end-user systems.
PIM PICMG PICP Ping
PLL
PLMN
PMC PM/E1 PM/T1 PNCH POI Polling
POP3 POTS PP PPB ppb PPC PPCH PPF ppm pps PPP
PR PRACH Presentation layer
3rd May 01
1137
GPRS-300-101
PRI
Primary Rate Interface. In North America, PRI is split into 23B channels and one 64Kbps D channel and delivered over the same physical link as a T1. In Europe, PRI is split into 30 B channels and one 64Kbps D channel, and delivered over a single E1 link. A cell which is already optimized in the network and has a collocated neighbour whose cell boundary follows the boundary of the said cell. The primary cell has a preferred band equal to the frequency type of the coincident cell. Packet Resource Manager. A process that performs all RLC/MAC functions and realises UL/DL power control and timing advance. Programmable Read-Only Memory. A storage device that, after being written once, becomes a read-only memory. A formal set of procedures for transmitting data between functions within the same layer of a hierarchy of functions. Related layers of protocol software that function together to implement a particular communications architecture. Packet Resource Process(or). A PCU hardware component that provides radio-related processing and manages the packet resources at the PCU. Packet Switched. A method in which network nodes are interconnected by circuits that allow routing of packets over several different routes. Periodic Supervision of Accessibility. A fault management function that sends messages to Network Elements requesting information on their current state. PCU System Audit Process. A PCU process that periodically monitors the soft devices to maintain the reliability of the system. Presentation Services Access Point. Packet Switched Data Network. Power Supply and Fan unit. PCU Switch Manager. Platform Shelf Management. PCU System Processor. Packet Switched Public Data Network. Public data communications network. x.25 links required for NE to OMC communications will probably be carried by PSPDN. Public Switched Telephone Network. The worldwide standard analog land line telephone network. Power Supply Unit. Packet Traffic CHannel. Point-To-Multipoint. Point-To-Multipoint Group. Point-To-Multipoint Multicast. Packet-TMSI. Point-To-Point.
3rd May 01
Primary Cell
PRM
PROM Protocol Protocol stack PRP
PS
PSA
pSAP
PSAP PSDN PSF pSM PSM PSP PSPDN
PSTN PSU PTCH PTM PTM-G PTM-M P-TMSI PTP
1138
GPRS-300-101
PTP-M PTP-CLNS PVC
Point-To-Point-Multicast. PTP-ConnectionLess Network Service. Permanent Virtual Circuit. A permanently established virtual circuit. A PVC saves the time associated with establishing and taking down a circuit. Power.
PWR
3rd May 01
1139
GPRS-300-101
Q
QFE card QoS Quad FastEthernet card. Provides network connections on Cluster nodes. Quality of Service. The collective effect of service performances which determine a users degree of satisfaction. An ordered list of packets waiting to be forwarded over a routeing interface.
Queue
1140
3rd May 01
GPRS-300-101
R
RA RAB RAC RACCH RACH RADIUS RAI RAID Routeing Area. Random Access Burst. Data sent on the RACH. Routeing Area Code. Random Access Control CHannel. A common control channel used to originate a call or respond to a page. Random Access CHannel. Service used by MSs to request network access. Remote Access Dial-In User Service. Routeing Area Identity. Redundant Array of Independent Disks. A method of storing the same data in different places on multiple hard drives to improve performance and fault-tolerance. Random Access Memory. The temporary memory that a computer uses to hold the current instructions and data. All data in RAM is lost when the computer is turned off. RANDom number (used for authentication). Routeing Area Update. Radio Channel Unit. Part of the BSS. Contains transceiver, digital control circuits, and power supply. Requirements DataBase. Spare. A redundant device becomes active if the primary unit fails. REQuest. A Motorola DataGen utility for producing an MMI script from a binary object database. Radio Frequency. Requesting Function. Request for Comments. Documents used for communicating standards, specifications, and other information about the Internet. Registered Jack-45. An eight-wire connector commonly used to connect computers on an Ethernet LAN. Radio Link Control. Air interface transmission layer which processes the transfer of PDUs from the LLC layer. Radio Link Protocol. An ARQ protocol used to transfer user data between an MT and IWF. See GSM 04.22. Remote Monitoring. A subset of SNMP MIB II that exchanges network monitoring data between network monitors and console systems. A protocol-dependent device that connects subnetworks. Routers can break down very large networks into manageable subnetworks but introduce longer delays and have slower throughput rates than bridges. A MAC-layer bridge that uses network layer methods to determine the topology of a network.
RAM
RAND RAU RCU RDB Redundant REQ Revgen RF RF RFC
RJ-45 RLC RLP RMON
Router
Routeing bridge
3rd May 01
1141
GPRS-300-101
Routeing table RS-232 RSL RSM RST RSLP RTC RTD RTF RTS
Table that keeps track of routes to specific network destinations. Recommended Standard-232C. A standard interface for connecting serial devices. Radio Signalling Link. Interface used for signalling between the BSC and BTSs. Route Switch Module. Reset. Radio System Link Processor. Remote Tuned Combiner. Channel combiner used to fine-tune the cavities to the correct frequency. RLC-block-equivalent Transit Delay. Receive Transmit Function. Request To Send. A handshaking signal used with some communication links to indicate that data is ready for transmission. Receive (uplink). Remote transcoder. Transcoder used at sites located away from the BSC.
Rx RXCDR
1142
3rd May 01
GPRS-300-101
S
S/W (or SW) SABM SACCH SoftWare. Set Asynchronous Balanced Mode Slow Associated Control CHannel. A GSM control channel used by the MS for reporting RSSI and signal quality measurements. Service Access Point. In the reference model for OSI, SAPs of a layer are defined as gates through which services are offered to an adjacent higher layer. Service Access Point Indicator (identifier). The OSI term for the component of a network address that identifies the individual application on a host that is sending or receiving a packet. Capable of being scaled to accommodate increased traffic. SGSN-Call Detail Record. Synchronization CHannel. A GSM broadcast control channel used to carry information for frame synchronization of MSs and identification of base stations. S-CDR Collection Function. Signalling Connection Control Part. An SS7 protocol level that provides connectionless and connection-oriented network services, and addressing services. Service Control Point. A signalling point, or SS7 node. Small Computer System Interface. A parallel interface standard for attaching peripheral devices to computers. S-CDR Transfer Function. Stand-alone Dedicated Control CHannel. A GSM control channel where the majority of call setup occurs. Used for MS to BTS communications before the MS is assigned to TCH. Signalling Data Link. Solstice DiskSuite. Sun Microsystems software that provides the HA NFS function in the ISS Cluster. Service Data Unit. An amount of information that has its identity preserved when transferred between peer layers and which is not interpreted by the supporting layers. Supervisor Engine. Signalling End Point. An organization through which a subscriber obtains GSM/GPRS telecommunications services. The layer of the OSI reference model that coordinates communication between systems, maintains sessions, and performs security, logging and administrative functions. Signalling Function. Serving GPRS Support Node. The SGSN provides the control, transmission, OAMP, and charging functions. Empty CPX8216 equipment chassis in which the SGSN hardware module and cards will be housed.
SAP
SAPI
Scaleable S-CDR SCH
SCCF SCCP
SCP SCSI SCTF SDCCH
SDL SDS SDU
SE SEP Service provider Session layer
SF SGSN SGSN chassis
3rd May 01
1143
GPRS-300-101
SGSN-CF SGSN-CONTROL SGSN-GBPROC SGSN-GNPROC SGSN module
SGSN-Control Function (card). SGSN-CONTROL function. SGSN-Gb Processor. SGSN-Gn Processor. A 3-card set of equipment contained within an SGSN chassis. The set contains one Control Function card, one Gn card, and one Gb card. SGSN-Operations And Maintenance Processor. SGSN-Transmission Function (card). SGSN chassis complete with one SF module, one to three SGSN modules, and two system processor cards. The Shelf Manager module is composed of a system processor card and a HSC bridge card. The Shelf Manager performs the bus control functions in the SGSN chassis, enabling the communication between non-system slot cards over the cPCI bus. It also performs the shelf level O&M functions including relaying shelf alarms to the OMC-G and software load management (BOOTP). Each SGSN chassis contains two Shelf Manager modules (4 cards in total). Subscriber Identity Module. A removable module within an MS that contains all information for that subscriber. Signalling Link Code. Signalling Link Set. Session Management. Facilitates the transfer of PDP contexts. Special Mobile Group. The group responsible for developing mobile networking technologies such as GSM and GPRS. Short Message Identifier Structure of Management Information. Rules in RFC 1155that specify how managed objects in the MIB are defined. Short Message Service. A globally-accepted wireless service that enables the transmission of alphanumeric messages between mobile subscribers and external systems such as e-mail, paging, and voice-mail systems. Short Message Service-Centre. SMS-Gateway Mobile Switching Centre. SMS-InterWorking Mobile Switching Centre. Station Management. An ANSI FDDI specification that defines how ring stations are managed. SubNetwork-Protocol Data Unit. SeND. SubNetwork Dependent Convergence Protocol. Simple Network Management Protocol. The protocol governing network management and the monitoring of network devices and their functions. Signalling Point.
SGSN-OAMP SGSN-TF SGSN unit Shelf Manager
SIM SLC SLS SM SMG SMI SMI SMS
SMS-C SMS-GMSC SMS-IWMSC SMT SN-PDU SND SNDCP SNMP
SP
1144
3rd May 01
GPRS-300-101
SPAN Spare A module
Switched Port Analyzer. Monitors traffic on any port for analysis by a network analyzer or RMON probe. The Spare A module (card) is a field replacement module (card) for CF, Gb or C7 modules. It consists of a non-system slot card and two dual E1 PMCs. The Spare B module (card) is a field replacement module (card) for the Gn module. It consists of a non-system slot card and one PMC encryption module. Single Point Of Failure. Service Request. Static RAM. Signed RESponse. An authentication and ciphering response. Supplementary Service. A modification of, or a supplement to, a basic telecommunications service. Signalling System 7. An ITU-T protocol standard also referred to as C7. SS7 is used in public networks to establish connections between switches. A card that provides the logical interface to the HLR, MSC/VLR, and SM-SC. SGSN-delivered Short message Mobile Originated - Call Detail Record. SGSN-delivered Short message Mobile Terminated - Call Detail Record. SubSystem Number. System Switch Processor. A card that acts as an Ethernet switch and passes data between all system cards and to any other switches connected to the system.. Service Switching Point. An element of SS7 that performs call origination, termination or tandem switching. A set of detailed technical guidelines used as a means of establishing uniformity in an area of hardware or software development. Signalling Transfer Point. Packet switch that routes SS7 messages based on routeing information obtained by a service switching point. Hierarchical clock reference in the PSTN network, where 1 represents the highest possible quality of clocking. Serial Tunnelling. Sun Microsystems components located in the ISS Cluster. HA Disk Array located in the ISS Cluster. Provides reliable long-term storage for network configuration, software storage, charging data information and network statistics. Located in the ISS Cluster. Provides CG and CNR functionality. Sun Microsystems UNIX Operating System. 51 traffic/associated control multiframes or 26 broadcast/common control multiframes (period 6.12s).
Spare B module
SPOF SR SRAM SRES SS SS7
SS7 card S-SMO-CDR S-SMT-CDR SSN SSP
SSP Standard
STP
Stratum STUN Sun Cluster Sun Netra t D1000
Sun Netra t 1125 SunOS Superframe
3rd May 01
1145
GPRS-300-101
Super user SVC
User account that can access all files, regardless of protection settings, and control all user accounts. Switched Virtual Circuit. A virtual circuit or connection that is established dynamically in response to a signalling request message. Software. Process of taking incoming traffic from one interface and delivering it through another. Card that manages the CF, TF (Gn and Gb), and SF modules in the SGSN chassis.
SW Switching System processor
1146
3rd May 01
GPRS-300-101
T
T1 TAC TAP TBD TBF Tc North American point-to-point communications circuit for voice and data transmissions. Also see E1. Technical Assistance Centre. Transferred Accounts Procedure. To Be Determined. Temporary Block Flow. Committed rate measurement interval.The time interval during which a user can send Bc and Be amounts of data. In general, Tc is computed as Tc=Bc/CIR. Tc is not a periodic time interval but used only to measure incoming data. Terminal Concentrator. Transaction Capabilities Application Part (SS7). Traffic CHannel. GSM logical channels that carry either encoded speech or user data. Transmission Control Protocol. One of the main protocols in a TCP/IP network. TCP enables two hosts to establish a connection and exchange streams of data. TCP guarantees delivery of data and that packets will be delivered in the same order in which they were sent. TCP over Internet Protocol. A suite of communications protocols used to connect hosts on the Internet. Time Division Multiplexing. A type of multiplexing that combines data streams by assigning each stream a different time slot in a set. Time Division Multiple Access. A method of dividing a transmission channel to be shared by multiple users through the assignment of time slots. Tariff Data Volume. Terminal Equipment. Equipment that provides the functions necessary for the operation of the access protocols by the user. Terminal Equipment Identifier. Standard terminal emulation protocol used for remote terminal connections, enabling users to log in to remote systems and use resources as if they were connected to a local system. Terminal equipment that provides console access to the ISS. Transmission Function. Trivial File Transfer Protocol. A simplified version of the TCP/IP file transfer protocol that allows the transfer of files from one computer to another over a network. A trigger point that, when crossed, causes an alarm or event report to be sent to the OMC-G or OMC-R. The amount of data transferred over a connection during a specific time period, usually measured as characters per second.
TC TCAP TCH TCP
TCP/IP TDM
TDMA
TDV TE
TEI Telnet
Terminal Concentrator TF TFTP
Threshold Throughput
3rd May 01
1147
GPRS-300-101
TID Timeslot
Tunnel IDentifier. Identifier for a GTP tunnel. The TID contains an MM Context ID and a NAPI. The multiplex subdivision in which voice and signalling bits are sent over the air. Each RF carrier is divided into 8 timeslots. A signal sent by the BTS to the MS. It enables the MS to advance the timing of its transmission to the BTS so as to compensate for propagation delay. Temporary Logical Link Identity. Transition Module. Temporary Mobile Subscriber Identity. A temporary code used to identify an MS. The TMSI is assigned using encryption after the HLR has identified the MS. Table of Contents. A logical characterization of how the devices on a network are connected. Tunnelling Protocol Data Unit. A packet originating from an MS or network node in an external PDN. The T-PDU is encapsulated with a GTP header (making it a G-PDU) so it can be transmitted in a GTP tunnel. Channels that carry user speech or data. The protocol layer that responds to service requests from the Session Layer and issues service requests to the Network Layer. It provides transparent transfer of data between end users, relieving the upper layers from any concern with providing reliable and cost-effective data transfer. Transcoder Rate Adapter Unit. Timeslot Resource Shifter. Time Service. A server maintaining and distributing the correct time and date over a computer network. TimeSlot. Trau SynchronizatioN process at PCU. Time To Live. Field in an IP header that indicates how long a packet is considered valid. TeleTYpe (refers to any terminal). The encapsulation of one protocol within another to transport it across a backbone that does not support the original protocol. Transmit/Transmitter (downlink).
Timing advance
TLLI TM TMSI
TOC Topology T-PDU
Traffic channels Transport layer
TRAU TRS TS TS TSN TTL TTY Tunnelling
Tx
1148
3rd May 01
GPRS-300-101
U
UDP User Datagram Protocol. A TCP/IP protocol that allows an application on one machine to send a datagram to an application on another machine. User Datagram Protocol/Transmission Control Protocol. UNIX File System. UpLink. Physical link from the MS towards the BTS (MS transmits, BTS receives). UpLink Concatenator. Air interface between a BTS and MS. Universal Mobile Telecommunications System. A 3G wireless telecommunications system with standards developed by the Third Generation Partnership Project (3GPP). Open platform, multi-user, multi-tasking operating system. Uninterruptible Power Supply. Power system designed to protect mission-critical networks against power-outages, brownouts, power surges and spikes. Universal Serial Bus.A serial bus standard that delivers power to peripherals on the bus and eliminates separate power cords. Universal Time Coordinated. Upper Transmission Function. Gn interface communication protocol functions.
UDP/TCP UFS UL ULC Um UMTS
UNIX UPS
USB
UTC UTF
3rd May 01
1149
GPRS-300-101
V
V V.42 V.42bis VC VCC Volt. A unit of electrical force. An ITU-T protocol for error correction. A standard that provides data compression as an extension of the V.42 protocol. Virtual Circuit. Service enabling two end points to communicate as though connected by a physical circuit. Virtual Channel Connection. Logical circuit that carries data between two end points. Sometimes called a Virtual Circuit Connection. Versatile Interface Processor 2. A T1/E1 serial module. Virtual Local Area Network. Group of devices on different LAN segments that are logically configured to communicate as if they are attached to the same wire. Visitor Location Register. A temporary register for subscriber information for a visiting subscriber. Often a part of the MSC. VLAN Membership Policy Server. Visited PLMN. A PLMN to which an MS has roamed from its HPLMN. Virtual Private Network. Connection that has the appearance and many of the advantages of a dedicated link but occurs over a shared network. Virtual Template. A logical interface configured with generic information for a purpose or configuration common to specific users, plus router-dependent information. VLAN Trunking Protocol. Protocol used for connecting two or more Cisco switches and providing load-sharing. It maintains VLAN configuration consistency throughout the network.
VIP2 VLAN
VLR VMPS VPLMN VPN
VT
VTP
1150
3rd May 01
GPRS-300-101
W
W WAN Watt. Measurement of the rate of energy flow. Wide Area Network. A communications network that spans a large geographical area and usually incorporates two or more LANs. World Wide Web. An Internet-based hypertext system.
WWW
3rd May 01
1151
X, Y, Z
GPRS-300-101
X, Y, Z
X.25 XID CCITT specification and protocols for public packet-switched networks. Exchange Identifier. An identifier that allows two nodes to recognize each other ad to establish link and node characteristics for communicating. X terminal window.
X-Term
1152
3rd May 01
Index
3rd May 01
GPRS-300-101
ii
3rd May 01
GPRS-300-101
Numbers
10/100BASET, 313, 810, 816
A
Abbreviations A, 112 B, 115 C, 118 D, 1112 E, 1115 F, 1117 G, 1119 H, 1122 I, 1123 K, 1126 L, 1127 M, 1129 N, 1132 Numbers, 111 O, 1134 P, 1135 Q, 1140 R, 1141 S, 1143 T, 1147 U, 1149 V, 1150 W, 1151 X, 1152 Account metering, 73 Active state, 622 Addresses assignment, 513 customer, 512 dynamic, 512 dynamic PDP, 622 PLMN address pools, 511 private IP, 511 public IP, 512 static, 512 static PDP, 622 translation, 513 ADMF, 710 IDP and IRI, 710, 711 Aggregated links, 411 Alarms, 714 APN Domain Name Service, 321 profile database, 36 security, 718 userselectable, 627
3rd May 01
iii
GPRS-300-101
Application addressing by SCCP, 427 Architecture of GPRS network, 54 Attach procedure extended, 68 roaming, 616 standard, 67 Audit files, 78 Authentication nontransparent access, 58 of MS, 718 RADIUS server, 321 subscriber procedure, 620 Availability CommHub, 314 GGSN, 37 ISS Cluster, 310 OMCG, 317 PCU, 319 SGSN, 34
B
Backbone DACS, 55 interPLMN, 56 intraPLMN, 55 IP LAN, 55 router, 313 Beryllium, safety issues, 12 Best effort QoS, 628 Billing System, 320 Billing transfer files, 78 BSC description, 318 hardware, 819 BSS BSC, 318 BTS, 318 description, 23, 318 hardware, 819 PCU, 318 separation of GPRS traffic, 28 BSSGP, description, 413 BTS description, 318 hardware, 819
C
Cabinets communications, 83 expansion, 83 interior, 83 specifications, 92
iv
3rd May 01
GPRS-300-101
Capacity GGSN, 37 ISS Cluster, 39 OMCG, 316 SGSN, 34 Catalyst 5500 chassis, 814 specifications, 96 Cautions, in documentation, 6 CDR GCDR, 74 generation, 73 MCDR, 77 SCDR, 75 Cell update, 612 Centralized system, 54, 55 CGF connection to Billing System, 320 description, 26, 38, 73 GGSN role, 36 Chapter descriptions, 11 Charging See also CGF and Charging Gateway cost efficiency of GPRS, 25 Charging Gateway availability, 79 Billing Transfer and Audit files, 78 configuration, 78 description, 77 processing, 78 Chassis CommHub, 814 GGSN, 89 ISS Cluster, 811, 812 OMCG, 817 SGSN , 84 Circuit switching, 22 Cisco 7206VXR, 37, 89 specifications, 94 Cisco Catalyst 5500, 814 specifications, 96 Class C mode, 321 CNR APN DNS, 321 description, 321 DHCP, 322 features, 322
3rd May 01
GPRS-300-101
CommHub 10/100BASET module, 313 availability, 314 Catalyst 5500 chassis, 814 connections, 312 description, 27, 312 features in 1.6.1.3, 104 features in 1.6.1.4, 107 RSM, 313 SE module, 312 security, 314 VIP2, 313 CommHub chassis 10/100BASET module, 816 RSM module, 816 SE module, 815 specifications, 96 CommHub functions backbone router, 313 connectivity, 313 Communications cabinet, 83 Compact flash card, 88 CompactPCI, specifications, 93 Compliance references, 113 with standards, 210 Compression, 627 Configuration management, description, 316, 714 Connection direct, 416 indirect, 416 Connectivity as a CommHub function, 313 OMCG in a GPRS system, 315 Control Function description, 33 hardware, 86 Cross references in documentation, 3 Customer Network Resolution Center, 213
D
DACS, 411, 55 Data, suitable for GPRS, 25 Database management, 715 Delete subscriber data, 614 Detach description, 68 MSinitiated procedure, 69 networkinitiated procedure, 69 roaming, 618
vi
3rd May 01
GPRS-300-101
DHCP, 322 Direct connection, 416 Distributed access, 58 DNS. See Domain name Documentation about this manual, 2 amendments, 19 classification number, 15 coding system, 14 cross references, 3 distribution, 18 document numbering, 14 list of GSM manuals, 16 list of GSMrelated manuals, 16 ordering, 14, 18 purpose of manuals, 2 text conventions, 3 version, 1 warnings and cautions, 6 Domain name APN DNS server, 718 DNS description, 26, 38 structure, 510 Dual E1 PIM0100 PMC module, 87 Dynamic IP addressing, 58, 512 PDP addresses, 622
E
Encapsulation, 626 Encryption description, 718 hardware, 87 Enterprise 3500 chassis, 817 ETSI, 24 Events, handling, 714 Expansion cabinet, 83 Extended attach, 68
F
Fault management description, 316 functionality, 713 Features 1.6.1.3, 102 1.6.1.4, 106 First aid, for electric shock, 4
3rd May 01
vii
GPRS-300-101
Flash card, 88 Flow control, 411 FPGA PMC encryption module, 87 Frame Relay, 46, 53
G
GCDR, 74 Ga description, 47 protocol stack, 48 signalling PDUs, 49 Gateway function, description, 36 Gb card, 86 description, 410 protocol stack, 412 signalling PDUs, 414 Gc alternative description, 430 protocol stack, 430 General Manual Revisions, 19 GGSN availability, 37 capacity, 37 description, 35 direct connect, 416 features in 1.6.1.3, 103 features in 1.6.1.4, 107 hardware, 89 role in GPRS, 29 security, 37 specifications, 94 GGSN chassis 100BASET card, 810 description, 89 I/O controller, 89 interface support, 810 power supplies, 810 specifications, 94 GGSN functions charging, 36 gateway, 36 OAMP, 36 GGSN hardware maximum configuration, 820 physical description, 89 Gi description, 415 protocol stack, 416
viii
3rd May 01
GPRS-300-101
Glossary of technical terms A, 112 B, 115 C, 118 D, 1112 E, 1115 F, 1117 G, 1119 H, 1122 I, 1123 K, 1126 L, 1127 M, 1129 N, 1132 Numbers, 111 O, 1134 P, 1135 Q, 1140 R, 1141 S, 1143 T, 1147 U, 1149 V, 1150 W, 1151 X, 1152 Gn card, 86 description, 419 protocol stack, 420 signalling PDUs, 421 Gp description, 422 protocol stack, 423 signalling PDUs, 423 GPRS architecture, 54 cost efficiency, 25 customer support, 213 data suitable for, 25 description, 24 features, list of, 210 hardware descriptions, 81 integration into GSM, 28 security, 717 standards, 24 GPRS infrastructure GSN Complex, 26 OMCG, 27 PCU, 27
3rd May 01
ix
GPRS-300-101
GPRS publications GPRS Equipment Planning, 19 GPRS Overview, 19 GSN Advance Operational Impact, 111 GSN Alarm Handling at the OMCG, 111 GSN Clean Install, 112 GSN Command Reference, 111 GSN Service Manual, 110 GSN Software Release Notes, 112 GSN Statistics Application, 111 GSN System Administration, 111 OMCG Clean Install, 19 OMCG Software Release Notes, 112 OMCG System Administration, 19 OMCG Database Schema, 112 OMCG in a GPRS System, 111 PCU Service Manual, 110 thirdparty, 113 Gr description, 424 protocol stack, 426 signalling PDUs, 429 GRE, tunnelling, 626 GSM features, 22 infrastructure, 22 integration of GPRS, 28 list of generic manuals, 16 list of related manuals, 16 GSN cabinet hardware, 82 cabinet specifications, 92 description, 26 GSN Complex architecture, 55 CommHub, 27 description, 26 GSN, 26 hardware, 82 ISS Cluster, 26 maximum configuration, 820 minimum configuration, 820 GTP description, 420 purpose, 420 GTP Prime (GTP), description, 48
H
HA description, 26 disk array, 39
x
3rd May 01
GPRS-300-101
Hardware BSS, 819 CommHub, 814 GGSN, 89 GSN cabinets, 82 ISS Cluster, 811 OMCG, 817 scaleability, 820 SGSN, 84 specification tables, 92 Help, online, 716 HGGSN detach and purge, 618 PDP context activation, 617 HLR description, 320 detaching from network, 610 request from SGSN, 32 HSC Bridge cards, 87
I
I/O controller, 89 Idle state, 62 Idle to Ready transition, 65 IMSI, 320 Inactive state, 621 Incremental routeing, 427 Indirect connection, 416 Infrastructure sharing, 410 Insert subscriber data, 614 Installation manuals GSN Clean Install, 112 OMCG Clean Install, 19 InterPLMN backbone, 56 InterSGSN RAU, 613 Interception Management System, 712 Interception of messages, 710 Interfaces BSCPCU, 319 diagram of, 42 Ga, 47 Gb, 410 Gc alternative, 430 Gi, 415 Gn, 418 Gp, 422 Gr, 424 GSN to LIAN, 712 list of, 43 PCUSGSN, 319
3rd May 01
xi
GPRS-300-101
Internet access network, 55 IntraPLMN backbone, 55 IntraSGSN RAU, 612 IP capability, 25 description, 49 dynamic addressing, 58 ISS Cluster availability, 310 capacity, 39 CGF, 26 description, 26, 38 DNS, 26 features in 1.6.1.3, 104 features in 1.6.1.4, 107 HA, 26 hardware, 811 NFS, 26 NTP, 26 security, 310 specifications, 95 st D1000s chassis, 812 t 1125 chassis, 811 terminal concentrator, 812 ISS Cluster functions CGF, 38 DNS, 38 HA disk array, 39 NFS, 39 NTP, 38
L
L1, description, 49, 414 L2, description, 49 Lawful Intercept ADMF, 710 delivery functions, 710 description, 34, 710 interface to GSN, 712 LIAN, 320, 711 management, 712 performance, 712 security, 712 LIAN architecture, 711 description, 320 interface to GSN, 712 purpose, 710 security, 712 Links, to external PDNs, 56 Load and database management, 316
xii
3rd May 01
GPRS-300-101
Load balancing on portlevel Gb, 411 SS7, 425 Load management, 715 Location management cell update, 612 interSGSN RAU, 613 intraSGSN RAU, 612 location update, 611 Location registers HLR, 320 in GSM, 23
M
MCDR, 34, 77 Maintenance Information manuals GSN Alarm Handling at the OMCG, 111 GSN Statistics Application, 111 Manuals coding system, 14 list of generic GSM, 16 list of GSMrelated, 16 ordering, 18 MAP, description, 428 MCPN750 card, 87 Message flow, 45 Metering, 73 Mobile reachable timer, 66 Mobile terminal. See MS Mobility functions attach procedure, 67 detach procedure, 68 HGGSN PDP context activation, 617 location management, 611 purge procedure, 610 roaming attach procedure, 616 roaming detach/purge, 618 roaming management, 615 roaming RAU, 619 subscriber management, 614 Mobility management functions, 67 security, 620 state timers, 65 state transitions, 64 state types, 62 Mobility states idle, 62 ready, 64 standby, 63
3rd May 01
xiii
GPRS-300-101
Modes of operation, Class C, 321 MS access security, 717 authentication, 718 comparison, 28 delete subscriber data, 614 description, 321 detaching from network, 69 ID confidentiality, 620 insert subscriber data, 614 location update, 611 network access, 57 PDP context activation, 623 PDP context deactivation, 624 subscriber authentication, 620 MSISDN, 320 MTP1, MTP2, MTP3, 426
N
NAT, description, 513 Network management configuration, 714 database management, 715 faults, 713 loading software, 715 performance, 715 Network structure centralized, 54 GPRS backbone, 55 site, 55 Network Subsystem, 23 Networkinitiated detach HLRinitiated, 610 SGSNinitiated, 69 NFS description, 26, 39 protocol, 39 Nontransparent access, 58 NS, description, 414 NTP, description, 26, 38
O
OAMP functions of GGSN, 36 of SGSN, 34
xiv
3rd May 01
GPRS-300-101
OMCG availability, 317 capacity, 316 connections to network, 315 description, 27, 315 event and alarm handling, 714 fault management, 713 features in 1.6.1.3, 105 features in 1.6.1.4, 108 hardware, 817 help, 716 MS access to network, 717 network management functions, 713 performance management, 715 security, 317 user access, 716, 717 OMCG chassis Enterprise 3500, 817 Power Edge 6300, 818 OMCG functions configuration management, 316, 714 fault management, 316, 713 load and database management, 316, 715 online help, 316 performance, 715 performance management, 316 security management, 316 OMCR description, 23, 318 hardware, 819 support for GPRS, 28 Online help, description, 316, 716 Operating Information manuals GSN System Administration, 111 OMCG System Administration, 19 Ordering documentation, 14
P
Packet switching, description, 25 Packets routeing, 625 transmission, 628 Passwords, 718 PCItoPCI bridge, 87 PCU availability, 319 description, 27, 28, 319 features in 1.6.1.3, 105 features in 1.6.1.4, 108 hardware, 819 interfaces, 319
3rd May 01
xv
GPRS-300-101
PDN, linking to external, 56 PDP active state, 622 addresses, 622 inactive state, 621 PDP context activation, 32, 623 MSinitiated deactivation, 624 roaming, 617 SGSNinitiated deactivation, 624 PDU Ga signalling, 49 Gb signalling, 414 Gn signalling, 421 Gp signalling, 423 Gr signalling, 429 Performance management, 316, 715 Periodic RAU timer, 66 PIM0101 PMC interface module, 88 PLMN address assignment, 513 address pools, 511 address translation, 513 addresses, 511 backbones, 53 description, 52, 59 domain name structure, 510 network management, 510 servers, 510 types of addresses, 511 PMC modules Dual E1, 87 FPGA, 87 Power Edge 6300, 818 Problem Reports resolved, 1 Protocol stack diagram of , 44 Ga, 48 Gb, 412 Gc alternative, 430 Gi, 416 Gn, 420 Gp, 423 Gr, 426
xvi
3rd May 01
GPRS-300-101
Protocols BSSGP, 413 DHCP, 322 Frame Relay, 53 GTP Prime, 48 IP, 25, 49, 417, 420, 423 GTP, 420, 423 L1, 49, 414, 417, 420, 423 L2, 49, 417, 420, 423 list of, 46 MAP, 428 MTP1, 426 MTP2, 426 MTP3, 426 NS, 414 PDP, 621 SCCP, 426 TCAP, 428 UDP, 48, 420, 423 PTPCLNS, 628 Purge procedure, 610 roaming, 618
Q
Quality of Service, 628
R
Radiation safety issues, 9 RADIUS server, description, 321 Ready state, 64 Ready timer, 65 Ready to Idle transition, 65 Ready to Standby transition, 65 References, 113 Relay function, description, 34, 627 Release 1.6.1.3, 102 1.6.1.4, 106 Roaming attach, 616 description, 615 detach and purge, 618 PDP context activation, 617 transparent RAU, 619 Route Switch Module description, 313 hardware, 816
3rd May 01
xvii
GPRS-300-101
Routeing, packets, 625 Routeing Area Update interSGSN, 613 intraSGSN, 612 roaming, 619 timer, 66 RSM, 313
S
SCDR, 34, 75 Safety issues beryllium, 12 first aid for electric shock, 4 reporting, 5 RF radiation, 9 static discharge, 15 SanDisk compact flash, 88 SAP, 628 Scaleability, 820 SCCP application addressing, 427 description, 426 incremental routeing, 427 Security authentication procedure, 620 CommHub, 314 encryption, 718 GGSN, 37 ISS Cluster, 310 Lawful Intercept, 712 MS access to network, 717 MS authentication, 718 OMCG access, 317, 716, 717 passwords, 718 public subscriber names, 718 SGSN, 34 user ID confidentiality, 620 Security management, description, 316 Service manuals GSN, 110 PCU, 110 Serving nodes, 29 Session Management, description, 621 SF card, 86
xviii
3rd May 01
GPRS-300-101
SGSN availability, 34 capacity, 34 cards, nonsystem, 87 description, 32 detaching from network, 69 features in 1.6.1.3, 102 features in 1.6.1.4, 106 hardware, 84 PDP context deactivation, 624 RAU, 612 role in GPRS, 29 security, 34 SGSN card components compact flash, 88 Dual E1 PIM10100 PMC, 87 FPGA PMC encryption, 87 MCPN750, 87 PIM0101 PMC interface, 88 TMPIMC0001 transition, 88 SGSN chassis CF card, 86 SSP cards, 87 description, 84 Gb card, 86 Gn card, 86 HSC Bridge cards, 87 SF card, 86 specifications, 93 SGSN functions CF, 33 SF, 33 LI, 34 OAMP, 34 relay, 34 TF, 33 SGSN hardware CF card, 86 Gb card, 86 Gn card, 86 maximum configuration, 820 Shelf. See SGSN chassis Shelf Management, 87 Signalling Ga PDUs, 49 Gb PDUs, 414 Gn PDUs, 421 Gp PDUs, 423 Gr PDUs, 429 plane, 45 Signalling function, description, 33 SIM card, 321 Site network, 55
3rd May 01
xix
GPRS-300-101
SMG 31 compliance, 210 Software release features 1.6.1.3, 102 1.6.1.4, 106 Software Release Notes GSN, 112 OMCG, 112 Specifications CommHub chassis, 96 GGSN chassis, 94 GSN cabinet, 92 ISS Cluster, 95 SGSN chassis, 93 SS7, load balancing, 425 SSP, 87 Standards compliance in this release, 210 references, 113 Standby state, 63 Standby to Idle transition, 65 Standby to Ready transition, 65 Static addresses, 512, 622 Static discharge, safety issues, 15 Statistics background, 715 ondemand, 715 polled, 715 Subscriber access distributed, 58 nontransparent, 58 transparent, 57 Subscriber management delete subscriber data, 614 insert subscriber data, 614 Sun Netra st D1000 hardware, 812 specifications, 95 Sun Netra t 1125 hardware, 811 specifications, 95 Supervisor engine description, 312 hardware, 815 System Information manuals GPRS Equipment Planning, 19 GPRS Overview, 19 GSN Advance Operational Impact, 111
T
TCAP, description, 428
xx
3rd May 01
GPRS-300-101
Technical Assistance Center, 213 Technical Description manuals GSN Command Reference, 111 OMCG Database Schema, 112 OMCG in a GPRS System, 111 Technical support, 213 Terminal concentrator, 812 Text conventions in documentation, 3 TF LTF, description, 33 UTF, description, 33 Time Server. See NTP Timers mobile reachable, 66 periodic RAU, 66 ready, 65 TLLI, 620 TMPIMC0001 transition module, 88 Transmission circuit switched, 22 of packets, 628 packet switched, 25 plane, 44 Transparent access, 57 Transparent RAU, roaming, 619 Tunnelling GRE, 626 standard, 626
U
UDP, description, 48 Updates to manuals, General Manual Revisions, 18 User identity, confidentiality, 620 Userselectable APN, 627
V
V.42bis data compression, 627 Version of document, 1 VIP2 , description, 313
W
Warnings, in documentation, 6
3rd May 01
xxi
CHAPTER 1 INTRODUCTION TO GPRS DOCUMENTATION
CHAPTER 2 INTRODUCTION TO MOTOROLA GPRS
CHAPTER 3 GPRS FUNCTIONAL DESCRIPTION
CHAPTER 4 GPRS INTERFACES
CHAPTER 5 NETWORK ACCESS AND STRUCTURE
CHAPTER 6 MOBILITY AND SESSION MANAGEMENT
CHAPTER 7 GPRS SERVICES
CHAPTER 8 GPRS HARDWARE
CHAPTER 9 GPRS EQUIPMENT SPECIFICATIONS
CHAPTER 10 SOFTWARE RELEASE FEATURES
CHAPTER 11 GLOSSARY
INDEX
GPRS-300-101
GSN Software Release 1
68P02903W01-C

GPRS Overview

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

GPRS Overview

Încărcat de

Drepturi de autor:

Formate disponibile

Cellular Infrastructure Group

SYSTEM INFORMATION GPRS OVERVIEW

GPRS-300-101 GSN Software Release 1

System Information GPRS Overview

E Motorola 1999 - 2001 All Rights Reserved Printed in the U.K.

System Information: GPRS Overview 68P02903W01-C

Copyrights, notices and trademarks

System Information: GPRS Overview 68P02903W01-C

Chapter 1 Introduction to GPRS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GPRS Overview 68P02903W01-C

113 113 113 113

Chapter 2 Introduction to Motorola GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3 GPRS functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GPRS Overview 68P02903W01-C

Chapter 4 GPRS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GPRS Overview 68P02903W01-C

System Information: GPRS Overview 68P02903W01-C

430 430 430 430

Chapter 5 Network access and structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 6 Mobility and session management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GPRS Overview 68P02903W01-C

Chapter 7 GPRS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GPRS Overview 68P02903W01-C

Chapter 8 GPRS hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GPRS Overview 68P02903W01-C

Chapter 9 GPRS equipment specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 10 Software release features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 11 Glossary of technical terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GPRS Overview 68P02903W01-C

System Information: GPRS Overview 68P02903W01-C

System Information: GPRS Overview 68P02903W01-C

Issue status of this manual

Issue status of this manual

Resolution of Service Requests

System Information: GPRS Overview 68P02903W01-C

About this manual

System Information: GPRS Overview 68P02903W01-C

Special key sequences

System Information: GPRS Overview 68P02903W01-C

First aid in case of electric shock

First aid in case of electric shock

System Information: GPRS Overview 68P02903W01-C

Reporting safety issues

Reporting safety issues

System Information: GPRS Overview 68P02903W01-C

Warnings and cautions

Warnings and cautions

Example and format

Example and format

System Information: GPRS Overview 68P02903W01-C

System Information: GPRS Overview 68P02903W01-C

System Information: GPRS Overview 68P02903W01-C

Human exposure to radio frequency energy (PCS1900 only)

Human exposure to radio frequency energy (PCS1900 only)

Maximum permitted exposures

Power density (S)

System Information: GPRS Overview 68P02903W01-C

Human exposure to radio frequency energy (PCS1900 only)

Maximum permitted exposure ceilings

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

System Information: GPRS Overview 68P02903W01-C

Human exposure to radio frequency energy (PCS1900 only)

Power density measurements