GPRS Overview

For:rrobot
Printed on:Tue, Mar 21, 2000 09:11:06

From book:68P02903W01-O-UK-FT
Document:tabs1
Last saved on:Tue, Mar 21, 2000 09:10:59
Document:tabs2
Document:cover
Document:cover (back)
Document:spine1
Document:spine1 (back)
Document:spine2
Document:spine2 (back)
Document:insidecover-legal
Document:toc
Document:Introduction
( ...)
CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5
INTRODUCTION TO GPRS INTRODUCTION TO PCU GENERAL GSN GENERAL GPRS FUNCTIONAL
DOCUMENTATION MOTOROLA GPRS DESCRIPTION DESCRIPTION DESCRIPTION
CHAPTER 6 CHAPTER 7 CHAPTER 8 CHAPTER 9 INDEX
CABINET OVERVIEW GPRS SPECIFICATIONS SOFTWARE FEATURES GLOSSARY
Cellular Infrastructure Group
GPRS-300-101
GSM Software Release 4.1
SYSTEM INFORMATION
GPRS OVERVIEW
FIELD TRIAL
68P02903W01-O
GPRS-300-101
GSM Software
Release 4.1
SYSTEM
INFORMATION
GPRS OVERVIEW
FIELD TRIAL
68P02903W01-O
SYSTEM INFORMATION
GPRS OVERVIEW
GPRS-300-101
GSM Software Release 4.1
System Information
GPRS Overview
E Motorola 1999
All Rights Reserved
Printed in the U.K.
15th Sep 99 System Information: GPRS Overview i

68P02903W01-O
FIELD TRIAL
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
, MOTOROLA and M-Cell are trademarks of Motorola Inc.

OSF/1, Motif, UNIX and the X device are registered trademarks in the United States and other
countries, IT DialTone and the Open Group are trademarks of The Open Group.
X Window System, X and X11 are trademarks of the Massachusetts Institute of Technology.
Looking Glass is a registered trademark of Visix Software Ltd.
Ethernet is a trademark of the Xerox Corporation.
Wingz is a trademark and INFORMIX is a registered trademark of Informix Software Ltd.
SUN, SPARC, and SPARCStation are trademarks of Sun Microsystems Computer Corporation.
IBM is a registered trademark of International Business Machines Corporation.
HP is a registered trademark of Hewlett Packard Inc.
Netscape and Netscape Navigator are registered trademarks of Netscape Communications
Corporation in the United States and other countries. Netscape’s logo and product and service names
are also trademarks of Netscape Communications Corporation, which may be registered in other
countries.
Windows NT is a registered trademark of Microsoft Corporation.
ii 15th Sep 99
System Information: GPRS Overview
68P02903W01-O
FIELD TRIAL
GPRS-300-101
Issue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
First aid in case of electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Human exposure to radio frequency energy (PCS1900 only) . . . . . . . . . . . . . . . . . . . . . . 9
Beryllium health and safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Motorola GSM manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
GMR amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
GMR amendment record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 1
Introduction to GPRS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Introduction to GPRS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
About this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
Motorola GPRS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
Overview of GPRS customer support manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
Documentation coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
How does the coding system work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
Order number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
Classification number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5
Sub category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Information level3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Distribution of Motorola manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
How do manual updates work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
How to order manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
Descriptions of GPRS publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
68P02903W01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
68P02903W02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
68P02903W03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
68P02903W04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
68P02903W05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
68P02903W10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
68P02903W15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
68P02903W16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11
68P02903W70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11
68P02903W74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11
68P02903W75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11
15th Sep 99 System Information: GPRS Overview iii

68P02903W01-O
FIELD TRIAL
GPRS-300-101
Other documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
Third-party documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
References, documents, and authors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
Chapter 2
Introduction to Motorola GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
Overview of chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
Overview of the GPRS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
About the overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Introduction to GPRS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
GPRS architecture overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
GPRS radio subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
GPRS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
GSN in GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5
GPRS network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
Overview of GPRS network elements (GSR4.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
Introduction to GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
GSN system components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11
Non-GSN system components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
GPRS network subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13
Physical links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
Physical links structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
The E1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
OMC-G interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–15
Standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
GSN interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
IP interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
Other interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–17
Network protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–20
GPRS application protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–20
SGSN-BSS BSSGP protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–20
Other network protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–23
Chapter 3
PCU general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Introduction to the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
PCU system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Overview of PCU in the GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
PCU summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
PCU environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
PCU description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
PCU purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
PCU hardware architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5
PCU configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
Data and signalling paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
PCU hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
iv 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101
PCU interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–15

GPRS BSS interface overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–15
PCU interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16
PCU system and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
System and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
PCU processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Chapter 4
GSN general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
GSN chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
Chapter structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
GSN system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
GSN overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
GSN in GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3
GSN software architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
GGSN and SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
GSN peripheral devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7
GSN system functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
GSN management from the OMC-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
SGSN description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
SGSN description structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
SGSN functions overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
SGSN architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
Functional entities and hardware mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–13
GGSN description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
GGSN functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
GGSN architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
GSN CommHub description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
GSN CommHub description structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
GSN CommHub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
GSN CommHub hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
GSN CommHub modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19
ISS description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
ISS description structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
ISS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
ISS hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
ISS functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–23
Network topology structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–23
Speech transcoder functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–23
BSS serial data transmission links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26
Coded transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29
GSN standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–31
GSN standardized interfaces structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–31
Standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–31
SGSN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–32
GSN CommHub interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–36
Chapter 5
GPRS functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
Overview of GPRS functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
15th Sep 99 System Information: GPRS Overview v

68P02903W01-O
FIELD TRIAL
GPRS-300-101
Channel groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2

Radio channel groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
PCCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
PBCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
PTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
Multiframe structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Mapping packet data logical channels onto physical channels . . . . . . . . . . . . . . . 5–4
Allocation of resources to GRPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
Burst structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Burst overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Timing advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7
Medium access control and radio link control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9
Channel coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–11
Channel coding overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–11
Channel coding schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–11
Coding scheme 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
Coding scheme 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–13
Coding scheme 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Coding scheme 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15
Mobility management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Mobility management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Definition of mobility management states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
IDLE (GPRS) state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
STANDBY state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–17
READY state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–17
IDLE/STANDBY/ READY state functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–18
STANDBY timer function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
READY timer function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Periodic RA update timer function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–21
Mobile reachable timer function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–21
Session management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–22
Session management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–22
Definition of packet data protocol states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–22
PDP context activation, modification, and de-activation functions . . . . . . . . . . . . 5–24
PDP context activation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–25
Network-requested PDP context activation procedures . . . . . . . . . . . . . . . . . . . . . 5–27
Successful network-requested PDP context activation procedure . . . . . . . . . . . . 5–28
Unsuccessful network-requested PDP context activation procedure . . . . . . . . . . 5–29
Anonymous access PDP context activation procedure . . . . . . . . . . . . . . . . . . . . . 5–32
Modification procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–34
PDP context modification procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–34
PDP context de-activation initiated by MS procedure . . . . . . . . . . . . . . . . . . . . . . . 5–35
PDP context de-activation initiated by GGSN procedure . . . . . . . . . . . . . . . . . . . . 5–36
Anonymous access PDP context de-activation initiated by MS procedure . . . . . 5–37
Anonymous access PDP context de-activation initiated by GGSN procedure . . 5–38
Packet routeing and transfer function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–39
Relay function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–39
Packet terminal adaptation function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Encapsulation function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Chapter 6
Cabinet overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Overview of cabinets and enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1
Cabinets and enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1
vi 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101
PCU cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2

PCU cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
PCU chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3
PCU chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3
GSN complex cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4
GSN complex cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4
GSN shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5
GSN shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5
GSN Commhub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
GSN Commhub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
GSN ISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7
GSN ISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7
Chapter 7
GPRS specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
GPRS specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1
Specifications overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1
OMC-G specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
GPRS OMC-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
GSN specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–10
GSN chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–10
PCU specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–11
PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–11
Motorola MCP750 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–11
General description of PCU functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–12
PCU board descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–13
PCU processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–15
GSN CommHub specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–17
GSN CommHub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–17
GSN ISS specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–20
GSN ISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–20
GSN HADA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–21
Chapter 8
Software features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Software features GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
Introduction to GPRS software features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
PCU features: GSR4 supplemental release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–3
Point-to-point GPRS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–3
GPRS radio channel allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–5
Medium access mode – fixed/dynamic allocation . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6
Support of MS classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–7
GPRS coding schemes CS-1 and CS-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8
Dynamic adaptation of coding schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–9
Two phase packet access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–10
Frequency hopping of PDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–11
Power, interface, balancing, and sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–12
Power control: uplink/downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–12
Gb interface (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–13
PCU load balancing and sharing (Gb and BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–14
15th Sep 99 System Information: GPRS Overview vii

68P02903W01-O
FIELD TRIAL
GPRS-300-101
OMC-G GSR4 supplemental release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–15

GPRS OMC-R (PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–15
DataGen support for GPRS (supplemental) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–20
Software features GSN: GRPS IP network backbone features . . . . . . . . . . . . . . . . . . . . 8–21
GSN features summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–21
GPRS IP network backbone features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–22
Time server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–23
GPRS backbone (Gn) (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–24
PDN interface (Gi) (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–26
GSN packet data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–29
TCP/IP header compression; V.42bis data compression . . . . . . . . . . . . . . . . . . . . 8–29
QoS profile classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–30
Ciphering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–31
Secure tunnelling (Gi) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–32
GSN mobility management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–33
Attach support: class A, B, C mobile stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–33
Inter-SGSN handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–35
HLR interface (Gr) (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–36
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–37
PTP-CLNS (static IPv4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–38
GPRS charging features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
Account metering and collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
Charging gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–41
GPRS network support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Lawful intercept – phase 1 (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
GSN OA&M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–44
SNMP management interface (TCP/IP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–44
GSN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–45
PCU interface (Gb) (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–45
Software features OMC-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–46
OMC-G features summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–46
OMC workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–47
Introduction to the OMC-G workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–47
Using the OMC-G workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–47
Feature traceability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–47
Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–48
Introduction to the OMC-G navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–48
Using the OMC-G navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–48
Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–49
Introduction to the OMC-G map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–49
Using the OMC-G map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–49
Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–50
Introduction to the OMC-G table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–50
Using the OMC-G table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–50
Parameter views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–52
Introduction to the OMC-G parameter view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–52
Using the OMC-G parameter view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–52
viii 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101
Alarm Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–53

Introduction to the OMC-G alarm display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–53
Using the OMC-G alarm display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–53
Audible indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–54
Introduction to the OMC-G audible indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–54
Using the OMC-G audible indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–54
Alarm printing service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–55
Introduction to the OMC-G alarm printing service . . . . . . . . . . . . . . . . . . . . . . . . . . 8–55
Using the OMC-G alarm printing service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–55
User profile editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–56
Introduction to the OMC-G user profile editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–56
Using the OMC-G user profile editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–56
Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–57
Introduction to OMC-G help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–57
Using the OMC-G help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–57
Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–58
Introduction to OMC-G configuration management . . . . . . . . . . . . . . . . . . . . . . . . . 8–58
View and modify SGSN/GGSN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–58
Sanity check an SGSN/GGSN database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–59
Compare PCU and SGSN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–60
Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–61
Introduction to OMC-G performance management . . . . . . . . . . . . . . . . . . . . . . . . . 8–61
Viewing SGSN/GGSN statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–61
Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–62
Introduction to OMC-G fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–62
Using OMC-G fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–62
Load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–63
Introduction to OMC-G load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–63
Using OMC-G load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–63
Chapter 9
Glossary of technical terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . i
Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
A ......................................................................... 9–2
B ......................................................................... 9–4
C ......................................................................... 9–6
D ......................................................................... 9–10
E ......................................................................... 9–12
F ......................................................................... 9–13
15th Sep 99 System Information: GPRS Overview ix

68P02903W01-O
FIELD TRIAL
GPRS-300-101
G ......................................................................... 9–14
H ......................................................................... 9–17
I .......................................................................... 9–18
K ......................................................................... 9–20
L ......................................................................... 9–21
M ......................................................................... 9–22
N ......................................................................... 9–24
O ......................................................................... 9–25
P ......................................................................... 9–26
Q ......................................................................... 9–28
R ......................................................................... 9–29
S ......................................................................... 9–30
T ......................................................................... 9–32
U ......................................................................... 9–34
V ......................................................................... 9–35
W ........................................................................ 9–36
X ......................................................................... 9–37
Z ......................................................................... 9–38
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–1
x 15th Sep 99
68P02903W01-O
FIELD TRIAL
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 Date of Remarks

issue issue
O 15th Sep 99 Original issue Field Trial – Software release GSR 4.1
Resolution of
Problem Reports
The following Problem Reports are now resolved in this manual:
Problem GMR Remarks

Report Number
N/A N/A
15th Sep 99 System Information: GPRS Overview 1

68P02903W01-O
FIELD TRIAL
General information GPRS-300-101
General information
Important notice
NOTE
This manual has been supplied by Motorola to support the field trial GSM
Software Release 4.1 (GPRS). This stage of product development is not
supported by the Motorola Customer Network Resolution Centre.
The product is still undergoing development and testing by Motorola. While
every effort has been made by Motorola to ensure accuracy of information, this
manual is provided without warranty of any kind. In no event shall Motorola or
its agents be liable for loss of profits, loss of use or data, interruption of
business, or for indirect, special, incidental, or consequential damages of any
kind that arise from any error or omission
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 Motorola’s 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. The information is
intended for use by all GPRS operations and maintenance personnel.
This manual supports the following Motorola GPRS equipment:
SGSN.
GGSN.
ISS.
GSN CommHub.
2 15th Sep 99
68P02903W01-O
FIELD TRIAL
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:
CTRL–c Press the Control and c keys at the same time.

ALT–f Press the Alt and f keys at the same time.
| Press the pipe symbol key.
CR or RETURN 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.

68P02903W01-O
FIELD TRIAL
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. Do not attempt to remove clothing adhering to the burn.
2. If help is available, or as soon as artificial respiration is no longer required, cover
the wound with a dry dressing.
3. Do not apply oil or grease in any form.
4 15th Sep 99
68P02903W01-O
FIELD TRIAL
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. Make the equipment concerned safe, for example, by removing power.
2. Make no further attempt to tamper with the equipment.
3. Report the problem directly to your local Motorola office
4. Collect evidence from the equipment under the guidance of the Customer Network
Resolution Centre.

68P02903W01-O
FIELD TRIAL
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.
6 15th Sep 99
68P02903W01-O
FIELD TRIAL
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 customer’s 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 ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human
Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz.
S 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.

68P02903W01-O
FIELD TRIAL
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 Beryllium materials are absorbed into the body tissues through the skin, mouth, or
a wound.
S The dust created by breakage of Beryllia is inhaled.
S Toxic fumes are inhaled from Beryllium or Beryllia involved in a fire.
See the Beryllium health and safety precautions section for further information.
8 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 Human exposure to radio frequency energy (PCS1900 only)
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,
S + E + 377
2
H2
377
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.

68P02903W01-O
FIELD TRIAL
Human exposure to radio frequency energy (PCS1900 only) 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 Controlled Environment

1930MHz 1970MHz 1930MHz 1970MHz
Ceiling 1.287mW/cm 2 1.313mW/cm 2 6.433mW/cm 2 6.567mW/cm 2
If you plan to operate the equipment at more than one frequency, compliance should be
assured at the frequency which produces the lowest exposure ceiling (among the
frequencies at which operation will occur).
Licensees must be able to certify to the FCC that their facilities meet the above ceilings.
Some lower power PCS devices, 100 milliwatts or less, are excluded from demonstrating
compliance, but this equipment operates at power levels orders of magnitude higher, and
the exclusion is not applicable.
Whether a given installation meets the maximum permitted exposure ceilings depends, in
part, upon antenna type, antenna placement and the output power to which this
equipment is adjusted. The following example sets forth the distances from the antenna
to which access should be prevented in order to comply with the uncontrolled and
controlled environment exposure limits as set forth in the ANSI IEEE standards and
computed above.
10 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 Human exposure to radio frequency energy (PCS1900 only)
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 1930MHz
Base station cabinet output power, P +39.0 dBm (8 watts)
Antenna feeder cable loss, CL 2.0dB
Antenna input power Pin P–CL = +39.0–2.0 = +37.0dB (5watts)
Antenna gain, G 16.4dBi (43.65)
Using the following relationship:
G + 4pr W
2
Pin
Where W is the maximum permissible power density in W/m2 and r is the safe distance
from the antenna in metres, the desired distance can be calculated as follows:
r+ ǸGPin + Ǹ 43.65 5 + 1.16m

4pW 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 licensee’s 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.

68P02903W01-O
FIELD TRIAL
Beryllium health and safety precautions GPRS-300-101
Beryllium health and safety precautions
Introduction
Beryllium (Be), is a hard silver/white metal. It is stable in air, but burns brilliantly in
Oxygen.
With the exception of the naturally occurring Beryl ore (Beryllium Silicate), all Beryllium
compounds and Beryllium metal are potentially highly toxic.
Health issues
Beryllium Oxide is used within some components as an electrical insulator. Captive within
the component it presents no health risk whatsoever. However, if the component should
be broken open and the Beryllium Oxide, which is in the form of dust, released, there
exists the potential for harm.
Inhalation
Inhalation of Beryllium Oxide can lead to a condition known as Berylliosis, the symptoms
of Berylliosis are similar to Pneumonia and may be identified by all or any of the
following:
Mild poisoning causes fever, shortness of breath, and a cough that produces
yellow/green sputum, or occasionally bloodstained sputum. Inflammation of the mucous
membranes of the nose, throat, and chest with discomfort, possibly pain, and difficulty
with swallowing and breathing.
Severe poisoning causes chest pain and wheezing which may progress to severe
shortness of breath due to congestion of the lungs. Incubation period for lung symptoms
is 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 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 Beryllium health and safety precautions
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.

68P02903W01-O
FIELD TRIAL
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 customer’s 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 15th Sep 99
68P02903W01-O
FIELD TRIAL
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 Always wear an earth strap which must be connected to the electrostatic point
(ESP) on the equipment.
S 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.
S Do not wear outer clothing made of nylon or similar man made material. A cotton
overall is preferable.
S If possible work on an earthed metal surface. Wipe insulated plastic work surfaces
with an anti-static cloth before starting the operation.
S All metal tools should be used and when not in use they should be placed on an
earthed surface.
S 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.

68P02903W01-O
FIELD TRIAL
Motorola GSM manual set GPRS-300-101
Motorola GSM manual set
Introduction
The following manuals provide the information needed to operate, install and maintain the
Motorola GSM equipment.
Generic manuals
The following are the generic manuals in the GSM manual set, these manuals are
release dependent:
Classification
number Name Order number
GSM-100-101 System Information: General . . . . . . . . . . . . . . . . . . . 68P02901W01
GSM-100-201 Operating Information: GSM System Operation . . . 68P02901W14
GSM-100-202 Operating Information: Scaleable OMC System
Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W19
GSM-100-311 Technical Description: OMC in a GSM System . . . . 68P02901W31
GSM-100-313 Technical Description: OMC Database Schema . . . 68P02901W34
GSM-100-320 Technical Description: BSS Implementation . . . . . . . 68P02901W36
GSM-100-321 Technical Description: BSS Command Reference . 68P02901W23
GSM-100-403 Installation & Configuration: GSM System
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W17
GSM-100-423 Installation & Configuration: BSS Optimization . . . . 68P02901W43
GSM-100-413 Installation & Configuration: Scaleable OMC
Clean Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W47
GSM-100-501 Maintenance Information: Alarm Handling at
the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W26
GSM-100-520 Maintenance Information: BSS Timers . . . . . . . . . . . 68P02901W58
GSM-100-521 Maintenance Information: Device State Transitions 68P02901W57
GSM-100-523 Maintenance Information: BSS Field
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W51
GSM-100-503 Maintenance Information: GSM Statistics
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W56
GSM-100-721 Software Release Notes: BSS/RXCDR . . . . . . . . . . 68P02901W72
GSM-100-712 Software Release Notes: Scaleable OMC System . 68P02901W74
Index of Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02900W81
Related manuals
The following are related Motorola GSM manuals:
Classification
GSM-001-103 System Information: BSS Equipment Planning . . . . 68P02900W21
GSM-002-103 System Information: DataGen . . . . . . . . . . . . . . . . . . 68P02900W22
GSM-002-703 Software Release Notes: DataGen . . . . . . . . . . . . . . 68P02900W76
GSM-005-103 System Information: Advance Operational Impact . 68P02900W25
GSM-008-403 Installation & Configuration: Network Health Analyst 68P02900W36
GSM-008-703 Software Release Notes: Network Health Analyst . 68P02900W77
GSM-006-202 Operating Information: OMC System
Administration (OSI) . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W10
GSM-006-413 Installation & Configuration: OSI Clean Install . . . . . 68P02901W39
GSM-006-712 Software Release Notes: OMC OSI System . . . . . . 68P02901W70
16 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 Motorola GSM manual set
Service manuals
The following are the service manuals in the GSM manual set, these manuals are not
release dependent. The internal organization and makeup of service manual sets may
vary, they may consist of from one to four separate manuals, but they can all be ordered
using the overall catalogue number shown below:
Classification
GSM-100-020 Service Manual: BTS . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W37
GSM-100-030 Service Manual: BSC/RXCDR . . . . . . . . . . . . . . . . . . 68P02901W38
GSM-105-020 Service Manual: M-Cell2 . . . . . . . . . . . . . . . . . . . . . . . 68P02901W75
GSM-106-020 Service Manual: M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . 68P02901W85
GSM-201-020 Service Manual: M-Cellcity . . . . . . . . . . . . . . . . . . . . . 68P02901W95
GSM-202-020 Service Manual: M-Cellaccess . . . . . . . . . . . . . . . . . . 68P02901W65
GSM-203-020 Service Manual: M-Cellarena . . . . . . . . . . . . . . . . . . . 68P02902W36
GSM-206-020 Service Manual: M-Cellarena macro . . . . . . . . . . . . . . . 68P02902W15
GSM-205-020 Service Manual: Horizonmacro Indoor . . . . . . . . . . . 68P02902W06
GSM-204-020 Service Manual: Horizonmacro Outdoor . . . . . . . . . . 68P02902W12
GSM-207-020 Service Manual: Horizonoffice . . . . . . . . . . . . . . . . . . 68P02902W46
GSM-101-SERIES ExCell4 Documentation Set . . . . . . . . . . . . . . . . . . . . 68P02900W50
GSM-103-SERIES ExCell6 Documentation Set . . . . . . . . . . . . . . . . . . . . 68P02900W70
GSM-102-SERIES TopCell Documentation Set (GSM900) . . . . . . . . . . . 68P02901W80
GSM-104-SERIES TopCell Documentation Set (DCS1800) . . . . . . . . . . 68P02902W80
GSM-200-SERIES M-Cellmicro Documentation Set . . . . . . . . . . . . . . . . . 68P02901W90
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.

68P02903W01-O
FIELD TRIAL
GMR amendment GPRS-300-101
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.
18 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 GMR amendment record
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 Incorporated by (signature) Date

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

68P02903W01-O
FIELD TRIAL
GMR amendment record GPRS-300-101
20 15th Sep 99
68P02903W01-O
FIELD TRIAL
Chapter 1
Introduction to GPRS
documentation

68P02903W01-O
FIELD TRIAL
GPRS-300-101
ii 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101
Chapter 1
Introduction to GPRS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Introduction to GPRS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
About this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
Motorola GPRS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
Overview of GPRS customer support manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
Documentation coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
How does the coding system work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
Order number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
Classification number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5
Sub category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Information level3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Distribution of Motorola manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
How do manual updates work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
How to order manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
Descriptions of GPRS publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
68P02903W01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
68P02903W02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
68P02903W03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
68P02903W04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
68P02903W05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
68P02903W10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
68P02903W15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
68P02903W16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
68P02903W39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11
68P02903W70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11
68P02903W74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11
68P02903W75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11
Other documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
Third-party documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
References, documents, and authors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12

68P02903W01-O
FIELD TRIAL
GPRS-300-101
iv 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 Introduction to GPRS documentation
Introduction to GPRS documentation
About this
manual
This manual supports the following Motorola General Packet Radio Service (GPRS)
equipment:
S Packet Control Unit (PCU).
S Servicing GPRS Support Node (SGSN).
S Gateway GPRS Support Node (GGSN).
S Integrated Support Server (ISS).
S GPRS Support Node Communications Hub (GSN CommHub).
This manual contains an overview of the GPRS, as implemented by Motorola, and
includes:
S An introduction to Motorola GPRS.
S PCU General Description.
S GSN General Description.
S GPRS Functional Description.
S Cabinet Overview.
S GPRS Specifications.
S A summary of Motorola GPRS software release features.
S A glossary of technical terms and acronyms.
The information is intended for use by all GPRS operations and maintenance staff.
About this
chapter
This chapter contains listings of the manuals supplied to customers. This chapter also
includes a description of the Motorola documentation system and includes a brief
summary of the contents of each document. Other documents available to Motorola
customers are also listed.
15th Sep 99 System Information: GPRS Overview 1–1

68P02903W01-O
FIELD TRIAL
Motorola GPRS documentation GPRS-300-101
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 Documentation coding.
S Distribution of Motorola manuals.
S Description of GPRS publications.
S Manual listings.
1–2 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Documentation coding
Documentation coding
How does the

coding system
work?
All manuals have two codes associated with them, an Order number and a Classification
number:
S The 68P... catalogue number is a unique identifier, which is used for ordering
purposes.
S 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 Date of issue Remarks

68P02900W15-O 3rd Oct 94 Original issue – Software Release 1.2.2.x
68P02900W15-A 30th Dec 94 Issue A – Software Release 1.2.3.x
68P02900W15-B 1st Sep 95 Issue B – Software Release 1.3.0.x
68P02900W15-C 31st May 96 Issue C – Software Release 1.4.0.x
68P02900W15-D 17th Dec 96 Issue D – Software Release 1.4.1.x
68P02900W15-E 29th Aug 97 Issue C – Software Release GSR2 (1.5.0.x)
68P02900W15-F 27th Apr 98 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. The first three characters (68P) identifies the item as a technical manual.
2. 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.
3. The final letter is the issue suffix as described above.

68P02903W01-O
FIELD TRIAL
Documentation coding 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 Description
System GPRS
Variant 300 = Generic GPRS manual set
Category 2 = Operating information
Sub category 0 = System
Information level 2 = OMC system administration
Volume 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.
1–4 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Documentation coding
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 Description
1 System Information
2 Operating Information
3 Technical Description
4 Installation and Configuration
5 Maintenance Information
6 Parts Information
7 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.

68P02903W01-O
FIELD TRIAL
Documentation coding 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 Description

0 System
1 Operations and Maintenance Centre (OMC)
2 Base Station System (BSS) or Base Transceiver
Station (BTS) when separate manuals produced
3 Base Station Controller (BSC)
Information
level3
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 Description
level
1 System operation
2 OMC system administration
3 Engineering staff (Planning and field)
1–6 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Distribution of Motorola manuals
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.

68P02903W01-O
FIELD TRIAL
Descriptions of GPRS publications 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)

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. The information is
intended for use by all GPRS operations and maintenance personnel.
68P02903W02
System Information: GPRS Equipment Planning (GPRS-001-103)

The manual contains an overview of the GPRS Equipment Planning. The manual
contains planning information for the GPRS system. The manual outlines the planning
process, and provides GPRS network statistics and configuration descriptions. The
manual includes planning examples and recommended guidelines.
68P02903W03
Operating Information: OMC-G System Administration (GPRS-300-202)

This manual is in a preliminary form. As a result it is both incomplete and lacking in a lot
of detail. However it contains the following material, an introduction to OMC-G and
details on the System Management features of OMC-G.
In addition, information is given on OMC-G for UNIX, System start-up and shutdown and
X.25 management. The manual also contains information on the Network Information
Services, File system backup and restore. Finally, a Troubleshooting Guide is included
which includes details on how to troubleshoot 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.
1–8 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Descriptions of GPRS publications
68P02903W05
Service Manual: GPRS Support Node (GSN) (GPRS-301-020)
The manual contains hardware service information for the GPRS packet control unit
(GSN). The manual is intended for customers who install, maintain, troubleshoot, and
manage the GPRS Support Node. The manual includes the following documentation in
one loose leaf binder:
S 68P02903W06 Technical Description
Describes GSN architecture, infrastructure, communication services, interfaces
and protocols, and specifications.
S 68P02903W07 Installation and Configuration
Gives instructions on how to install and configure the GSN shipment of hardware,
including installing the hardware modules in the rack, configuring Motorola and
third-party hardware, and verifying the connectivity of the installed GSN.
S 68P02903W08 Maintenance Information
Gives procedures for operating, monitoring, maintaining, and troubleshooting the
hardware modules in the GSN, including:
– GSN start up and shut down procedures.
– Maintaining the GSN Communications Hub (CommHub).
– Maintaining the Domain Name Server (DNS).
– Maintaining the Time Server (TS).
– Monitoring ISS alarms.
– Maintaining the GGSN and SGSN using log files, statistics, and alarms.
S 68P02903W09 Parts Information.
An illustrated manual listing available GSN options and spares and ordering
information, including:
– Factory-fitted options.
– Field-fitted options and tools.
– Spares.
68P02903W10
Service Manual: Packet Control Unit (PCU) (GPRS-302-020)
The manual contains hardware service information for the GPRS packet control unit. It
consists of one loose leaf binder containing the following:
S 68P02903W11 Technical Description.
S 68P02903W12 Installation and Configuration.
S 68P02903W13 Maintenance Information.
S 68P02903W14 Parts Information.
68P02903W15
Technical Description: PCU Command Reference (GPRS-302-321)
The manual contains descriptions of the PCU-specific commands and parameters used
within GPRS and those BSS commands and parameters that have been modified to
include PCU features.

68P02903W01-O
FIELD TRIAL
Descriptions of GPRS publications GPRS-300-101
68P02903W16
Maintenance Information: PCU Alarm Handling at the OMC-R
(GPRS-302-501)
The manual includes PCU alarm reference information. In addition, alarm diagnostics
information and procedures are included to resolve fault conditions from the Operations
and Maintenance Centre-Radio (OMC-R).
68P02903W17
Maintenance Information: PCU Statistics Application (GPRS-302-503)
The manual contains information on the statistics related to the PCU in the Motorola
GPRS network. It describes the statistical measurements generated by the Base Station
System (BSS) and Packet Control Unit (PCU) in response to monitored network and
system events. The statistics include statistical measurements defined in the GSM
Technical Specification 12.04, plus additional Motorola-defined statistics.
68P02903W18
Technical Description: GSN Command Reference (GPRS-300-321)
The manual contains descriptions of the GSN commands and parameters used within
the GPRS.
68P02903W19
Maintenance Information: GSN Alarm Handling at the OMC-G
(GPRS-300-501)
The manual includes GSN alarm reference information. In addition, alarm diagnostics
information and procedures are included to resolve fault conditions from the Operations
and Maintenance Centre for the GPRS (OMC-G).
68P02903W20
Maintenance Information: GSN Statistics Application (GPRS-300-503)
The 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. A
brief description of the network interfaces, links, and protocols is also provided. The MMI
commands used to perform statistical operations (enabling, disabling, and displaying) are
also identified and described.
68P02903W29
Technical Description: OMC-G in a GPRS System (GPRS-300-311)
The manual presents an overview of of the OMC-G, and its role in the operation and
maintenance of the GPRS System.
68P02903W30
Operating Information: GPRS System Operation (GPRS-300-201)
The manual provides information on procedures required to perform............system
operation.
1–10 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Descriptions of GPRS publications
68P02903W39
Supplementary Information: Impact of GSR4.1 on the OMC-R

(GPRS-300-210)
The manual contains supplementary information, GSR4.1 changes, for W14 (PCU Parts
Information), W17 (PCU Statistics Application), W19 (GSN Alarm Handling at the
OMC-G), and W34 (OMC Database Schema). Revision bars denote the GPRS
information.
68P02903W70
Software Release Notes: GPRS OMC-G System (GPRS-300-712)

The manual contains software release notes and upgrade guides.
68P02903W74
Software Release Notes: OMC-R System (GSR4.1) (GPRS-302-712)

The manual contains software release notes relating to the OMC-R.
68P02903W75
Software Release Notes: BSS/PCU System (GSR4.1) (GPRS-302-721)

The manual contains software release notes relating to the BSS and PCU.

68P02903W01-O
FIELD TRIAL
Other documents GPRS-300-101
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 CISCO.
S Sun.
S Lynx OS.
S Force.
References,
documents, and
authors
Table 1-1 relates references to documents and authors. Although few of the listed
documents are referred to in the this overview, many of the listed documents may be of
general background interest.
Table 1-1 References, documents, and authors

[Ref #] Document title/document id/version/release date Author(s)
1 GSM 01.04 (ETR 350): ”Digital cellular ETSI
telecommunications system (Phase 2+); Abbreviations
and acronyms”, version 5.0.0, March 96
2 GSM 01.33: ”Digital cellular telecommunications system ETSI
(Phase 2+); Lawful Interception requirements for GSM”,
version 7.0.0
3 SM 01.61: ”Digital cellular telecommunications system ETSI
(Phase 2+); GPRS ciphering algorithm requirements”,
version 6.0.1
(Phase 2+);
Lawful Interception – Stage 1”; Version 7.0.0, 1998-03
(Phase 2+); General Packet Radio Service (GPRS);
Service description; Stage 1” Version 6.1.1
6 GSM 03.03 (ETS 300 927): ”Digital cellular ETSI
telecommunications system (Phase 2+); Numbering,
addressing and identification”, version 5.0.0, March 1996
telecommunications system (Phase 2+); Lawful
Interception – stage 2”, version 1.1.3, Release 98
(Phase 2+); Restoration procedures”, Version 5.0.0,
November 1996
1–12 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Other documents

telecommunications system; Functions related to Mobile
Station (MS) in idle mode and group receive mode”
telecommunications system” ETSI
Service Description; Stage 2”, Version 6.2.0
Point to Multipoint Multicast Service Description; Stage
2”, Version 0.7.1
Point to Multipoint Group Service Point to Multipoint-
Groupast Stage 2 Description”, version none
(Phase 2+); Overall description of the General Packet
Radio Service (GPRS) radio interface; Stage 2”, version
6.1.0
15 GSM 04.04 Digital cellular telecommunications system; ETSI
Layer 1; General requirements, (GSM 04.04 version
5.1.0
telecommunications system (Phase 2+); Mobile radio
interface signalling layer 3; General aspects”, version
6.2.0
(Phase 2+); Mobile radio interface layer 3 specification”,
version 6.2.0
Service: MS-BSS interface; Radio Link Control/Medium
Access Control (RLC/MAC) protocol”, version 6.2.0
(Phase 2+); General Packet Radio Service Point to
Multipoint-Multicast Stage 3 description, version none
(Phase 2+); General Packet Radio Service Point to
Multipoint-Groupcast Stage 3 description, version none
21 GSM 04.64: ”Digital cellular telecommunications system; ETSI
(Phase 2+), General Packet Radio Service (GPRS);
Mobile Station-Serving GPRS Support Node
(MS-SGSN) Logical Link Control (LLC) Layer
Specification”, version 6.2.0
Subnetwork Mobile Station (MS) – Serving GRPS
Support Node (SGSN); Subnetwork Dependent
Convergence Protocol (SNDCP)”, version 6.2.1

68P02903W01-O
FIELD TRIAL

(GSM Radio Access Phase 3); Multiplexing and multiple
access on the radio path”, version 6.2.0
(GSM Radio Access Phase 3); Channel Coding”, version
6.0.0, 1998-01
(Phase 2+); Radio Transmission and Receptions”,
version 5.2.0, July 1996
26 GSM 05.08 ”Digital cellular telecommunications system ETSI
(GSM Radio Access Phase 3); Radio Sub-system link
control” version 5.1.0, July 1996
(Phase 2+); Radio Sub-system Synchronization”, version
5.10, May 1996
(Phase 2+); General requirements on Mobile Stations
supporting GPRS”; version 6.2.1
(Phase 2+); Mobile Switching Center – Base Station
System (MSC-BSS) interface: Layer 3 specification”,
version .6.3, September 1997
BSS-SGSN interface Gb Interface Layer 1”, version
6.3.0
(PHASE 2+); General Packet Radio Service (GPRS);
Base Station System (BSS) – Serving GPRS Support
Node (SGSN) interface; Network Services”, version
6.3.0
(Phase 2+) General Packet Radio Service (GPRS);
Base Station System (BSS) – Serving GPRS Support
Node (SGSN); BSS GPRS Protocol (BSSGP)”, version
6.3.0
telecommunications system (Phase 2+); Inband control
of remote transcoders and rate adaptors for Enhanced
Full Rate (EFR) and full rate traffic channels”
telecommunications system (Phase 2+); Mobile
Application Part (MAP) specification”, version 6.2.0
telecommunications system (Phase 2+); SGSN-MSC,
Gs Interface Layer 2”, version 6.0.1
SGSN-MSC; Gs Interface Layer 3”, version 6.2.0
1–14 15th Sep 99

68P02903W01-O
FIELD TRIAL

GPRS Tunnelling Protocol (GTP) across the Gn and Gp
Interface”, version 6.2.2
Interworking between the Public Land Mobile Network
(PLMN) supporting GPRS and Packet Data Networks
(PDN)”, version 6.3.0
(Phase 2+) General Packet Radio Service (GPRS) O&M
in GPRS”, version 0.2.0, 1997-11
(Phase 2+) General Packet Radio Service (GPRS)
Project scheduling and open issues”, version 5.3.0,
1997-10
(Phase 2) Network Management (NM) Part 1: Object
and structure of Network Management (GSM 12.00)”;
prETS 300 612-1; Final Draft; August 1996
(Phase 2) SGSM Network configuration management
(GSM 12.06)”; prETS 300 617; Final Draft; June 1996
(Phase 2) Subscriber and equipment trace”;version
5.1.1, release 1996
(Phase 2)
(Phase 2) GPRS Charging”; version 6.1.0
46 CCITT Recommendations I.130: ”General modelling ETSI
methods – Method for the characterization of
telecommunication services supported by an ISDN and
network capabilities of an ISDN”
47 CCITT Recommendation E.164: ”Numbering plan for the ETSI
ISDN era”
48 CCITT Recommendation Q.65: ”Methodology – Stage 2 ETSI
of the method for the characterization of services
supported by an ISDN”
49 ITU-T Q.922: ”ISDN data link layer specification for ITU-T
frame mode bearer services.”, 2/92
50 ITU-T Q.933: ”Digital Subscriber Signalling System No. ITU-T
1 (DSS 1) – Signalling specification for frame mode
basic call control”, 10/95
51 CCITT Recommendation V.42 bis: ”Data communication ETSI
over the telephone network – Data compression
procedures for data circuit-terminating equipment (DCE)
using error correction procedures”

68P02903W01-O
FIELD TRIAL

52 CCITT Recommendation X.3: ”Packet assembly ETSI
disassembly facility (PAD) in a public data network”
53 CCITT Recommendation X.25: ”Interface between data ETSI
terminal equipment (DTE) and data circuit-terminating
equipment (DCE) for terminals operating in the packet
mode and connected to public data networks by
dedicated circuit”
54 CCITT Recommendation X.121: ”International ETSI
Numbering Plan for Public Data Networks”
55 CCITT Recommendation X.137: ”Availability ETSI
Performance Values for Public Data Networks When
Providing International Packet Switched Services”;
Melbourne, 1988
56 CCITT Recommendation X.733: ”System Management ETSI
Event Reporting Function”
57 CCITT Recommendation X.734: ”System Management ETSI
Alarm Reporting Function”
58 prETS 300 019-1-2: ”Equipment Engineering (EE); ETSI
Environmental conditions and environmental tests for
telecommunications equipment Part 1-2: Classification of
environmental conditions Transportation”; Edition 1;
February 1992
59 prETS 300 019-1-3: ”Equipment Engineering (EE); ETSI
Environmental conditions and environmental tests for
telecommunications equipment Part 1-3: Classification of
environmental conditions Stationary use at weather
protected locations”; Edition 1; February 1992
60 prETS 300 753 019-1-3: ”Equipment Engineering (EE); ETSI
Environmental
61 IETF RFC 768 (1980): ”User Datagram Protocol” (STD ETSI
6)
62 IETF RFC 791 (1981): ”Internet Protocol” (STD 5) ETSI
63 IETF RFC 792 (1981): ”Internet Control Message ETSI
Protocol” (STD 5)
64 IETF RFC 793 (1981): ”Transmission Control Protocol” ETSI
(STD 7)
65 IETF RFC 854 (1981): ”TELNET” ETSI
66 IETF RFC 1034: ”Domain names – concepts and ETSI
facilities”
67 IETF RFC 1035: ”Domain names – implementation and ETSI
specifications”
68 IETF RFC 1144: ”Compressing TCP/IP Headers for ETSI
Low-Speed Serial Links”
69 IETF RFC 1305: ”Network Time Protocol Specification, ETSI
Implementation and Analysis”
70 IETF RFC 1155: ”SMI” ETSI
71 IETF RFC 1157: ”SNMP” ETSI
1–16 15th Sep 99

68P02903W01-O
FIELD TRIAL

72 IETF RFC 1631: ”The IP Network Address Translator ETSI
(NAT)”
73 IETF RFC 1825: ”Security Architecture for the Internet ETSI
Protocol”
74 IETF RFC 1826: ”IP Authentication Header” ETSI
75 IETF RFC 1827: ”IP Encapsulating Security Payload ETSI
(ESP)”
76 IETF RFC 1212: ”MIB Definition” IETF
77 IETF RFC 1215: ”Trap Definition” IETF
78 IETF RFC 220: ”Internet Official Protocol Standards”, IETF
June 1997 (STD)
79 Recommendation G.703, ”Physical/Electrical ITU-T
Characteristics of Hierarchical Digital Networks”, Sept.
1991.
80 Recommendation G.704, ”Synchronous Frame ITU-T
Structures Used at Primary and Secondary Hierarchical
Levels”, Oct. 1991.

68P02903W01-O
FIELD TRIAL
1–18 15th Sep 99

68P02903W01-O
FIELD TRIAL
Chapter 2
Introduction to Motorola GPRS

68P02903W01-O
FIELD TRIAL
GPRS-300-101
ii 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101
Chapter 2
Introduction to Motorola GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Overview of chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
Overview of the GPRS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
About the overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Introduction to GPRS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
GPRS architecture overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
GPRS radio subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
GPRS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
GSN in GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5
GPRS network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
Overview of GPRS network elements (GSR4.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
Introduction to GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
GSN system components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11
Non-GSN system components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
GPRS network subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13
Physical links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
Physical links structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
The E1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
OMC-G interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–15
Standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
GSN interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
IP interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
Other interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–17
Network protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–20
GPRS application protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–20
SGSN-BSS BSSGP protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–20
Other network protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–23

68P02903W01-O
FIELD TRIAL
GPRS-300-101
iv 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 Chapter overview
Chapter overview
Overview of
chapter
This chapter addresses the following aspects of GPRS:
S Overview of GPRS network.
S GPRS network elements.
S Physical links.
S Standardized interfaces.
S Network protocols.

68P02903W01-O
FIELD TRIAL
Overview of the GPRS network GPRS-300-101
Overview of the GPRS network

About the
overview
The General Packet Radio Service (GPRS) overview comprises the following items:
S Introduction to GPRS services.
S GPRS architecture overview.
S GPRS radio subsystem.
S GPRS system.
S GSN in GPRS.
S GSN system functions.
S GSN management from the OMC-G.
This section attempts to provide an overall picture of where the GPRS fits into existing
facilities, and to indicate of the direction of future development of GPRS.
Introduction to
GPRS services
In contrast to the Global System for Mobile communications (GSM) service model, which
offers telephony on demand, the GPRS service model offers a wireless Wide Area
Network/Local Area Network (WAN/LAN). This opens up a new market to operators and
new applications to users. GPRS supports a wide range of applications, from low-volume
intermittent telemetry, to web browsing via interactive remote server sessions, to the
transfer of larger amounts of data.
GPRS is designed as one service to fit many roles. From the user viewpoint, the main
characteristics of the service are:
S The data rates available on demand go from a low number of octets, to over 120
kbit/s (with a maximum raw rate of 171 kbit/s). GPRS is both low and high speed.
S It is affordable to log on to GPRS and stay connected for a long time. The user is
charged only when data is transmitted. GPRS operates rather like an office
Personal Computer (PC), switched on in the morning, and switched off at night.
S Initial application response times are much faster than circuit-switched services,
since service provision is continuous, but the user service usage is discontinuous.
GPRS waits for the stroke of a key to spring into life. GPRS does not have to set
up a call every time the user demands services.
S Several connections can be active at the same time, allowing the user to access
Internet Protocol (IP) and X.25 networks during a voice call.
The coverage of GPRS will be as seamless as is GSM today. The GSM Memorandum of
Understanding (MoU) has marked GPRS as an essential service for all GSM networks to
support by the year 2000. Ubiquitous coverage is foreseen within the first years of GPRS
operation. Full roaming capabilities have been standardized, and inter-Public Land Mobile
Network (PLMN) handovers are possible. User data is ciphered before transmission.
GPRS mobile stations will become available to the market in a variety of configurations.
The Mobile Station (MS) configurations range from the GPRS-only MS, via the MS that
can operate either voice and other existing GSM services, or GPRS, but not both in
parallel, to the MS that can fully operate GPRS and existing GSM services at the same
time. All MS configurations will be able to use the popular Short Message Service (SMS).
GPRS enables the user to select the Quality of Service (QoS) best suited to current
needs. User-selectable QoS parameters include data rate, data packet delay,
error-correction capabilities, and the importance of the connection relative to other
connections.
2–2 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Overview of the GPRS network
GPRS
architecture
overview
In order to support GPRS, a GSM network needs to be enhanced with two new
functional network elements (see Figure 2-1 and Figure 2-2):
S The Serving GPRS Support Node (SGSN).
S The Gateway GPRS Support Node (GGSN).
The SGSN is the GPRS equivalent to the Mobile Switching Centre/Visitor Location
Register (MSC/VLR). The SGSN controls user access to the GPRS network in terms of
subscription checking and the overall traffic load situation. The SGSN authenticates the
MSs, and keeps track of their whereabouts.
The GGSN is the GPRS equivalent to the shared InterWorking Function (IWF). The
GGSN connects the GPRS network to external private or public networks. A GPRS
network may contain just about any number of SGSNs and GGSNs, which allows the
GPRS Support Node (GSN) to scale to the needs of the operator. SGSNs and GGSNs
are connected with an IP-based GPRS backbone network. The backbone provides
connectivity for roaming GPRS users.
The SGSN is at the core of the GPRS network, connecting the radio subsystem with the
backbone network. The SGSN is also connected to the GSM C7 signalling network. This
connectivity allows the SGSN to access subscription information in the Home Location
Register (HLR), and SMS delivery via the efficient GPRS radio channels.
GPRS can be deployed without any changes to the MSC/VLR, unless the network
operator wants to deploy the optional SGSN to MSC/VLR interface. This interface
supports the exchange of location information, and it allows the MSC/VLR to page via the
SGSN. Although optional, most of the operators will want to have this interface because
it allows class B mobiles to receive incoming circuit switched calls when the device is
sending or receiving data packets. (Class B mobiles, which can operate in either the
normal GSM circuit switched mode or the GPRS mode, are expected to be the most
popular class of mobile.)
The GPRS phase 1 standards define interworking with IP-based and X.25-based packet
data networks, but other packet data networks can easily be supported. All that is
needed is an operator with a business case to offer a certain protocol to its subscribers.
The GPRS network subsystem is designed to be independent of the radio subsystem.
This allows a variety of radio interface technologies, including GSM 900 / 1800 / 1900,
Enhanced Data rates for GSM Evolution (EDGE), Univeral Mobile Telecommunications
Systems (UMTS), and even satellite radios.
GPRS radio
subsystem
The SGSN is connected to a Base Station Subsystem (BSS) supporting GPRS by the
Base Station System GPRS Protocol (BSSGP), using the Network Service (NS).
BSSGP supports the connectionless transfer of Logical Link Control (or Lower Layer
Compatibility)(LLC) frames between the BSS and SGSN, providing a signalling and user
data interface between the radio interface Radio Link Control/Medium Access Control
(RLC/MAC) and the SGSN. It also supports a limited set of node management functions.
The Network Service (NS), which may be deployed as a point-to-point link or over an
entire (sub)network, is divided between GPRS specific management functions, such as
load sharing between physical connections, and off-the-shelf transmission functionality
provided by frame relay. Based on FRF1.1, frame relay provides transmission rates
across the SGSN to BSS interface of up to 50 Mbit/s (compare with High-Speed Serial
Interface(HSSI). The NS could be replaced in later years with higher-rate technologies,
like Asynchronous Transfer Mode (ATM), without affecting BSSGP.

68P02903W01-O
FIELD TRIAL
GPRS system
General Packet Radio Service (GPRS) is a Global System for Mobile communications
(GSM) service that enables mobile subscribers to send data packets over GSM radio
channels to external data networks.
The main benefit of GPRS is that it reserves radio resources specifically for times when
there is something to send. The same radio resource is shared by every Mobile Station
(MS) in a cell, providing effective use of scarce resources. GPRS facilitates several
applications, such as telemetry, train control systems, interactive data access, toll road
charging systems, and Internet browsing using the World Wide Web (www).
Figure 2-1 is an example of a GPRS system. In Figure 2-1, ISS is the Internet
(Integrated) Support Server, and GSN CommHub is the GSN Communications Hub.
MS MS MS MS
RADIO NETWORK
INFRASTRUCTURE
GGSN (REDUNDANT)
GGSN
ISS (STAND-BY)
ISS (ACTIVE)
GSN SHELF
HADA (STAND-BY) (REDUNDANT)
HADA (ACTIVE)
LOCAL AREA
NETWORK
GSN COMMHUB GSN SHELF
PC
GLOBAL INTERNET
Figure 2-1 Example of a GPRS system
2–4 15th Sep 99

68P02903W01-O
FIELD TRIAL
GSN in GPRS
The GPRS Support Node (GSN) complex is the main element in the GPRS
infrastructure. It is a high-performance, broadband packet-switching node that provides
connection and interworking with various data networks, mobility management, and
delivery of data packets to mobile stations (see Figure 2-2).
MS MS MS MS
BSS
E1
GGSN (REDUNDANT)
GGSN
ISS (STAND-BY)
ISS (ACTIVE)
GSN SHELF
HADA (ACTIVE)
LOCAL AREA
NETWORK
PC
GSN COMPLEX
GLOBAL INTERNET
Figure 2-2 Example of a GPRS support node complex
All GSNs must implement the Gn interface protocols in order to communicate with other
GSNs in the same Public Land Mobile Network (PLMN). A limited internal Home Location
Register (HLR) function within the Serving GPRS Support Node (SGSN) is provided for
basic subscriber management purposes.

68P02903W01-O
FIELD TRIAL
Frames and channels

To transfer LLC frames between the MS and the BSS, the BSS relies on the RLC/MAC
function, defined in GSM 04.08, in a new radio specification, GSM 04.60, and in updated
versions of the 03, 04, and 05 series specifications.
Seven new control channels are introduced to support the transfer of user data over a
Packet Data Traffic Channel (PDCH). The Packet Broadcast Control CHannel (PBCCH),
to take one example, broadcasts GPRS system information for the cell. Once the MS
has read the message, it can interact with the BSS and its GPRS Common Control
CHannels (PCCCH), or select cells autonomously, or report its radio environment to the
BSS to enable it determine control movements.
Depending upon the configuration of the cell, some of the new control channels may be
mapped onto existing control channels. This allows the BSS to co-ordinate MS signalling
between circuit switched service and packet data service. For example, the Packet
Paging CHannel (PPCH) may be mapped onto the Paging CHannel (PCH), thereby
allowing a GPRS MS to be attached to the GPRS transmission plane via the SGSN,
while still being able to receive (and respond to) circuit-switched paging requests from
the Mobile Switching Centre (MSC).
The limited radio spectrum necessary to support PDCHs may be statically assigned in
the cell or dynamically allocated, allowing TDMA timeslots to be shared between
circuit-switched and packet-switched services.
Dynamic and fixed allocation modes

The MS supports the operation of the RLC/MAC function in two modes: dynamic and
fixed allocation. However, the BSS has the option to implement dynamic or fixed
allocation modes: the choice is up to the manufacturer and operator.
In dynamic mode, the BSS radio scheduler multiplexes MSs over 1 to 8 timeslots. Up to
8 users can send data over a single timeslot through the manipulation of 8 access flags
per timeslot. An MS capable of transmitting on more than 2 timeslots may have to listen
on all timeslots for its access flag even when sending; that is it has to be capable of true
duplex operation (violating a fundamental design principle in existing GSM). The dynamic
mode of operation provides the best possible service performance for an MS, but at a
heavy cost in terms of new hardware design and battery consumption. Additionally, the
access flags have to be broadcast everywhere in the cell with enough power to enable all
mobiles can hear them; this prevents effective use of downlink power control for an MS.
In fixed allocation mode, the BSS radio scheduler also multiplexes MSs over 1 to 8
timeslots, but does this by providing a precise schedule to the MS, indicating when it can
transmit data. After the fixed assignment is completed, the MS or BSS must agree on a
new schedule. The fixed assignment mode of operation does not force the MS to send
and receive at the same time because it does not have to listen for dynamically changing
access flags. It also allows a BSS to operate downlink power control as effectively as
existing circuit mode services. For mobiles capable of transmitting on 1 or 2 timeslots,
fixed allocation allows simultaneous transmission and reception. For mobiles capable of
transmitting on more timeslots, a half duplex operation can be used that allows operation
on up to 8 timeslots using a mobile no more complex that a 2 timeslot mobile, however
this mobile can only transmit or receive in any Time Division Multiple Access (TDMA)
frame, not both.
2–6 15th Sep 99

68P02903W01-O
FIELD TRIAL
Performance
The (raw) performance of the radio interface depends on the selected Coding Scheme
(CS). Four have been defined (CS1 = 9.05 kbit/s, CS2 = 13.4 kbit/s, CS3 = 15.6, CS4 =
21.4 kbit/s). Only CS1 and CS2 are supported in the first release of the product.
Recently, standardization work was initiated to exceed these raw data rates. The
Enhanced Data rates for GSM Evolution (EDGE) work item promises to increase the
information that can be transmitted across the radio interface through the development of
a new modulation scheme. Enhanced GPRS (EGPRS) will be able to support data rates
per timeslot of between 11.2 kbit/s to 65.2 kbit/s.
GPRS phase 2
GPRS phase 2 was originally defined as a clean-up phase, and as a place to work on
features that were interesting, but not commercially pressing. Items postponed to phase
2 included point-to-multipoint services.
In the meantime, UMTS has gathered considerable momentum, and has changed the
way GPRS phase 2 will be developed. While a clean-up of GPRS phase 1 will still be
required, phase 2 promises to be more exciting than originally imagined.
GPRS phase 2 is intended to be the vehicle for transforming the GSM network
architecture from a structure based around a centralized MSC, which collocates
switching and services, to a highly distributed architecture, which decouples switching
and services through the use of a client/server model.
An MS communicates directly with a set of network servers supporting traditional
teleservices, supplementary services, and to-be-defined future services. The transport of
information is done over the GPRS packet-switched platform. The central task of GPRS
phase 2 is to become UMTS.
On the network side, a series of enhancements to the GPRS platform will be required,
such as the ability to carry voice and multimedia, and to connect to legacy networks, like
Integrated Services Digital Network (ISDN). On the radio side, the new UMTS interface
will have to be accommodated across the Gb-interface.
Feature overview
The GPRS Point-To-Point ConnectionLess Network Service (PTP-CLNS) is a new GSM
feature.
PTP-CLNS is based upon the Open Standard Interface (OSI) standards and the
widely-used Internet Protocol (IP) standards.
The IP network layer specifies the interface between the user and a network, and it
includes the switching/routeing and the route discovery operations.
The connectionless service allows the transfer of information, called data packets,
among service users without the need for end-to-end call establishment procedures (see
GSM 0.260 for a complete description).
The PTP-CLNS teleservice is very good for bursty applications that use small packets
(less than 500 octets). In these applications, the time between successive transmissions
greatly exceeds the average transfer delay.
A typical bursty packet based application could:
S Access information stored in a remote data centre.
S Store and forward messages.
S Handle transaction or telemetry messages.

68P02903W01-O
FIELD TRIAL
New features
The new features to be implemented with PTP-CLNS are listed below. See sections 6. 2.
1 and 6. 2. 2 of the GSM 10.60 standard for a complete list of services and features that
the standards community expects to be available in first and second phases of GPRS.
Whenever possible, the name used in the standards is used to describe the feature.
S Account metering and collection.
S Addressing (dynamic and static IP).
S Authentication.
S Domain Name Server (DNS).
S Dynamic allocation of radio resources between circuit switched and packet
services.
S GPRS radio channels.
S Half-duplex mobiles.
S Lawful intercept.
S Load balancing and sharing (Gb interface).
S Mobile devices.
S PDN (IP) interworking.
S Mobile-to-mobile routeing.
S Network Address Translation (NAT).
S Network transport (TCP/IP) protocol.
S Non-transparent access (Gi).
S OMC tool: Gb link configurator tool.
S Operations and maintenance centre (OMC).
S Quality of Service (QoS).
S Secure tunnelling (Gi).
S Security.
S Standard GPRS interfaces and protocols.
S Time Server (TS).
S Transparent access (Gi).
The Phase I requirements will be implemented in the first release of the GPRS product.
Note that the OMC-G has a software tool, called the Gb Link Configurator, that
configures parameters within the SGSN and the Packet Control Unit (PCU). This tool can
be used only on Motorola BSS equipment.
2–8 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GPRS network elements
GPRS network elements
Overview of
GPRS network
elements
(GSR4.1)
Figure 2-3 shows the basic major components of GPRS in a much-simplified form.
Introduction to GPRS amplifies this figure in a more realistic way in Figure 2-4.
In Figure 2-3 the acronyms are as follows:
S MS is Mobile Subscriber, System, or Station.
S BSS is Base Station Subsystem.
S GSN is GPRS Service or Support Node.
S PDN is Public Data Network.
S I/O is Input/Output.
S OMC-G is Operations and Maintenance Centre-GPRS.
S GPRS is General Packet Radio System.
LOCAL GSN
MS BSS GSN GLOBAL INTERNET
PDN
I/O I/O
CONTROL
OMC-G
Figure 2-3 Basic major GPRS components

68P02903W01-O
FIELD TRIAL
GPRS network elements GPRS-300-101
Introduction to
GPRS
The General Packet Radio Service (GPRS) network elements are:
S The Base Station System (BSS).
S The Operations and Maintenance Centre-GPRS (OMC-G).
Refer to Figure 2-4 for detail. In Figure 2-4, TE is Terminal Equipment, EIR is Equipment
Identity Register, and RXCDR is the Remote XCoDeR (where X=trans).
MS
MSC/VLR BSS
Gb
RXCDR SGSN
Gs EIR
Gp
SMS
OMC-R GGSN
OTHER PLMN
Gp Gi
HLR
Gi
MS
Gi
BSS Gb
Gn OMC-G
Gn
SGSN
Gb
MS BSS
Gi
GGSN PDN
MS Gb Gn
BSS SGSN TE
Figure 2-4 GPRS network elements
2–10 15th Sep 99

68P02903W01-O
FIELD TRIAL
GSN system
components
GPRS is implemented in the GSM network through the Serving GPRS Support Node
(SGSN) and the Gateway GPRS Support Node (GGSN). These components are housed
in a GSN cabinet with a GSN CommHub and Internet Support Server (ISS) (see
Figure 2-2).
Other components of the GPRS system are the OMC-G, the base station (BSS), and the
Mobile Stations (MSs).
OMC-G
The OMC-G is a Windows NT server with software applications that manage GPRS
components. System operators use the OMC-G to configure and monitor system
components and view performance data.
GPRS base station subsystem

The BSS is located at one or more base sites selected to provide a radio frequency (RF)
link between the GPRS network infrastructure and mobile subscribers throughout the
operational area. A BSS consists of three components:
S Base Station Controller (BSC), the main control.
S Base Station Transceiver (BTS), the radio; many BTSs are connected to a BSC.
S Packet Control Unit (PCU), the board connecting a BSC to an SGSN; many PCUs
are connected to a BSC.
Mobile station
MSs are devices used by subscribers to send and receive data over the GPRS
infrastructure.
GPRS service node

The following components comprise the GSN, which is the central connection point for:
S The GSN CommHub in a GPRS system. It provides LAN connectivity between
GPRS components through Ethernet, and WAN connectivity to data networks
outside a GPRS system.
S The ISS, which provides GPRS system components with the current time, domain
name translation, and network information.
S The GGSN, which provides GPRS network access to external hosts so they can
communicate with MSs. It decapsulates and forwards external data network
packets to the appropriate data network, and handles the billing of traffic data.
S The SGSN, which detects and tracks new GPRS MSs in its service area, and
provides a reliable, secure data channel as the MS moves between cells.

68P02903W01-O
FIELD TRIAL
GPRS network elements GPRS-300-101
Non-GSN system
components
In addition to what are termed GSN system components, which form the core of the
GPRS, there are a number of other non-GSN system components that are GPRS
network elements (see Figure 2-4):
S Equipment Identity Register (EIR).
S Home Location Register (HLR).
S Mobile Switching Centre/Visitor Location Register (MSC/VLR).
S Operations and Maintenance Centre-Radio subsystems (OMC-R).
S Packet Data Network (PDN).
S Remote XCoDeR (RXCDR), where X=trans.
S Short Message Service (SMS).
S Terminal Equipment (TE).
Each of the non-GSN system components is described briefly below.
Equipment identity register

The Equipment Identity Register (EIR) provides a database that holds information related
to mobile equipment. This information is retrieved by the SGSN to enable location of
stolen mobile equipment, and to monitor mobile station misbehaviour.
Home location register

The Home Location Register (HLR) contains GPRS subscription data and routeing
information, and functions in a similar way to its role in GSM.
The internal Home Location Register is a simple data store that resides in the SGSN,
and contains subscriber data required for GPRS operation.
When an MS attaches to the GPRS network, a location update message is received from
the SGSN, and the internal HLR provides the SGSN with subscriber information. The
internal HLR can hold data for up to 50,000 subscribers.
The operator can view, add, modify, and delete subscriber data by editing the America
Standard Code for Information Interchchange (ASCII) HLR data file.
Mobile switching centre/visitor location register

The Mobile Switching Centre/Visitor Location Register (MSC/VLR) functions in a similar
way to its role in GSM. However, new functionality enables the the exchange of local
information and paging via the SGSN. It also allows Class B mobiles to receive circuit
switched calls when the device is sending or receiving data packets.
Operations and maintenance centre for radio subsystems

The Operations and Maintenance Centre-Radio subsystems (OMC-R) continues to
function as for GSM. However, new functions enable it to manage the new GPRS
features within the BTS and BSC. OMC-R also manages the Packet Control Unit (PCU).
The OMC-G is able to manage the SGSN, GGSN, ISS, and GSN CommHub in order to
support a complete GPRS subsystem.
Packet data network

The Packet Data Network (PDN) supports the transmission of data packets across the
GPRS network.
2–12 15th Sep 99

68P02903W01-O
FIELD TRIAL
Remote transcoder
The Remote XCoDeR (RXCDR), where X=trans, functions in a similar way to its role in
GSM.
Short message service

The Short Message System (SMS) functions in a similar way to its role in GSM.
Terminal equipment
The Terminal Equipment (TE) receives or transmits data packets from/across the packet
data network.
GPRS network
subsystem
GPRS reuses much of the existing GSM functionality and protocols, especially in the
signalling plane.
The transmission plane introduces a number of new protocols. The application running in
the MS uses IP or X.25 to communicate with the remote application. IP and X.25 packets
are encapsulated in GPRS protocol PDUs, and transported transparently through the
GPRS network. This transport method is known as tunnelling, and it protects the GPRS
network by isolating the user packets from the GPRS protocols.
On the MS to SGSN segment, the SubNetwork Dependent Convergence Protocol
(SNDCP) compresses and segments the user packets before transmission on the GPRS
radio. The Logical Link Control (LLC) protocol protects the user packets with reliable
retransmissions mechanisms and ciphering. LLC is an optimized HDLC-type protocol,
supporting a large transmit window and selective retransmission of missing packets.
SGSNs and GGSNs are interconnected with the IP-based GPRS backbone network.
User packets are transported with the User Datagram Protocol (UDP) or Transmission
Control Protocol (TCP) protocol depending on the selected Quality of Service. The GPRS
Tunnelling Protocol (GPT) is responsible for encapsulation of user packets. GTP is also a
signalling protocol used to coordinate the SGSN and GGSN operation, for example to
establish and release user data connections.
The SGSN to HLR signalling interface is MAP GSM 09.02, as enhanced for GPRS. The
SMS MSC to HLR and SMS MSC to SGSN interfaces are also according to GSM 09.02;
they have been enhanced for more optimal GPRS operation, but it is possible to use
pre-GPRS versions of GSM 09.02 for SMS over GPRS services, so no changes are
required to the SMS MSCs.
The optional SGSN to MSC/VLR interface is similar to GSM A interface. The BSSAP+
protocol contains the message definitions. BSSAP+ uses the connectionless services of
Signalling Connection Control Part (SCCP). The SGSNs and MSC/VLRs may be
connected either with direct links, or via C7 signalling transit point nodes.

68P02903W01-O
FIELD TRIAL
Physical links GPRS-300-101
Physical links
Physical links
structure
The structure of GPRS physical links is simple:
S E1 interface.
S OMC-G interface.
The E1 interface
There is an E1 interface between the BSS and the GSN cabinets (see Figure 2-5) via the
PCU.
MS MS MS MS
BSS
E1
GGSN (REDUNDANT)
GGSN
ISS (STAND-BY)
ISS (ACTIVE)
GSN SHELF
HADA (ACTIVE)
LOCAL AREA
NETWORK
PC
OMC-G GSN COMPLEX
GLOBAL INTERNET
Figure 2-5 GPRS Support Node to BSS physical interface

Functionally the PCU may be regarded as part of the BSS. (Physically the PCU is
housed in a dedicated cabinet associated with, and cabled to, the BSS.)
The GSN E1 connections to the BSS are actually between the SGSN and the PCU.
2–14 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Physical links
E1 interface PCU to BSC

Figure 2-6 shows the physical E1 connections from the PCU to the BSC. In Figure 2-6:
S MSI is a Multiple Serial Interface board.
S DPROC is a Data PROCessor board.
S PICP is a Packet Interface Control Processor board.
S E1PMC is an E1 PCI Mezzanine Card (board).
BSC
E1PMC
DPROC
DPROC
(PICP)
(PICP)
MSI
MSI
E1PMC
The number of MSI links
needed is dependent on the
PCU capacity. All MSIs can
reside in a single BSC PCU
chassis even in expanded
systems.
Figure 2-6 PCU to BSC connection utilizing E1 links (four shown)
OMC-Rs interface with the GSN via the BSC (see Figure 2-4).
OMC-G interface
Figure 2-5 shows the physical control interface from the OMC-G via the Local Area
Network (LAN).
This interface is by 100 BaseT Ethernet connection. The interface is used to support the
provision of load management, configuration management, fault management, and
performance management of the SGSN.
Configuration management of the SGSN can be performed by Single Network
Management Protocol (SNMP) protocol and Man-Machine Interface (MMI) commands at
the SGSN.
GSN CommHub connectivity

The GSN CommHub provides LAN connection over the Ethernet to all the GPRS
components and WAN connection to data networks outside the GPRS system, such as
the Internet.

68P02903W01-O
FIELD TRIAL
Standardized interfaces GPRS-300-101
Standardized interfaces
GSN interfaces
The GSN relies on well-defined interfaces between system components. This section
describes GSN IP and frame relay interfaces, and their associated protocols, as listed in
Table 2-1.
Table 2-1 Protocols associated with GSN system interfaces

Interface Name Applica Trans- Network Data-Link Physical
-tion port Layer Layer Layer
Layer Layer
GGSN to Gn GTP UDP IP Ethernet/ Backbone
SGSN MAC
BSS to Gb BSSGP - - FR E1
SGSN
GPRS to Um - - IP SND CP/ GSMRF
MS LLC/RLCI/
MAC
GGSN to Gi - - IP FR E1
PDN ATM OC3
IP interfaces
Gi interface
This interface exists only in the GGSN and transfers information between a GSN and an
external Public Data Network (PDN).
The Gi interface uses Internet Protocol (IP), Border Gateway Protocol (BGP), and
Exterior Gateway Protocol (EGP).
Gn interface
This interface connects GSNs that are in the same Public Land Mobile Network (PLMN).
One or more physical ports on the GSN may be associated with the Gn interface. GPRS
Tunnelling Protocol (GTP) operates over User Datagram Protocol/Internet Protocol
(UDP/IP) and Transmission Control Protocol/Internet Protocol (TCP/IP) stacks, and
defines both signalling and data transfer functions between GSNs.
The Gn interface uses GTP, User Datagram Protocol (UDP), and IP protocols.
Um interface
The Um interface exists between the MS and GPRS fixed network part, and provides
packet data services over the radio to the MS. The Mobile Terminal (MT) part of the MS
is used to access the GPRS services through this interface.
The Um interface uses Link Access Protocol-GPRS (LAP-G) protocol and SubNetwork
Dependent Convergence Protocol (SNDCP).
OMC-G interface
The OMC-G interface (E1) connects the OMC-G to the GPRS Support Node (GSN), and
supports file transfer, event reporting, and remote login procedures.
The OMC-G interface uses Simple Network Management Protocol (SNMP), UDP, and IP
protocols.
2–16 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Standardized interfaces
Frame relay interface

The frame relay interface (Gb) connects the SGSN and BSS, allowing the exchange of
signalling information and user data. The Gb interface allows many users to be
multiplexed over the same physical resource. Resources are given to a user when
activity is initiated (data is given or received), and are re-allocated immediately
afterwards.
A frame relay SGSN to BSS connection is a virtual circuit known as a Data Link
Connection (DLC). Each DLC has an identifying number called a Data Link Connection
Identifier (DLCI). Because the DLCI is different at the SGSN and the BSS, the network
administrator needs to know both DLCIs for each DLC being provisioned across a frame
relay network. The routeing tables in each frame relay switch take care of routeing the
frames to the proper destination, alternately reading and assigning DLCI values in the
control portion of the frames, as appropriate.
No frame relay network is required in GSN configurations where the PCU is collocated
with the SGSN, or where the SGSN and PCUs are physically interconnected.
The Gb interface uses Base Station Subsystem GPRS Protocol (BSSGP), Network
Service (NS), Frame Relay (FR), and E1 protocols.
Other interfaces
Five other standard interfaces need brief description:
S Gd.
S Gf.
S Gp.
S Gr.
S Gs.
Gd interface
Gd is the interface SGSN-SMS-GMSC or SMS-IWMSC that carries the Mobile
Application Protocol (MAP), Transaction Capabilities Application Protocol (TCAP),
Signalling Connection Control Protocol (SCCP), Message Transfer Protocol 3 (MTP3),
Message Transfer Protocol 2 (MTP2), and Layer 1 (L1) protocols.
The Gd interface uses the common C7 physical links which terminate at a remote
Signalling Transfer Point (STP). This provides access to all nodes in the C7 network,
including the SMS-Service Centres (SMS-SC) of both the local and foreign PLMNs.
The SMS-SC forwards short messages to the SGSN upon receiving an SGSN address
from the HLR. The actual ability of the GSN to deliver the messages is determined by the
number of 64 kbit/s links between the GSN and SMS-SC. The messages are carried as
normal packets though the SGSN, and should be considered as part of the actual load
on a the network.
This interface is not supported in the Field Trial release of the SGSN, but will be provided
in a future release.
Gf interface
Gf is the interface between the SGSN and the Equipment Identity Register (EIR) that
enables the retrieval of information related to the mobile equipment. The SGSN uses
such information to find stolen mobile equipment and to monitor mobile station
misbehaviour.

68P02903W01-O
FIELD TRIAL
Standardized interfaces GPRS-300-101
Gp interface
Gp is an inter-GPRS-PLMN interface that connects two independent GPRS networks for
the purpose of message exchange.
The Gp interface is equivalent to the Gn interface, and is present on both the SGSN and
GGSN. The Gn GTP tunnels are associated with a local GSN, whereas the Gp GTP
tunnels are associated with a foreign GSN (the GSN IP address is in a different domain).
Since GTP packets travel outside the PLMN intranet, the SGSNs and GGSNs must have
access to a Gateway IP router. For security reasons, the Gateway IP router should have
a dedicated path to each authorized foreign PLMN, such that GTP packets do not travel
over a public IP network (such as the Internet). The Gateway IP router may be
configured with a firewall function, to allow packets only from authorized IP domains
(foreign PLMNs) and to the GTP UDP/TCP port numbers.
Gr interface
Gr is the interface that enables the SGSN access the HLR.
The Gr and Gc interfaces use the common C7 physical links which terminate at a remote
Signalling Transfer Point (STP). This provides access to all nodes in the C7 network,
including the Home Location Registers (HLR) of both the local and foreign PLMNs.
In order to determine the C7 point code of the HLR, an SCCP Global Title Translation
(GTT) must be performed on the International Mobile Subscriber Identity (IMSI). This
function may be performed in either the SGSN, the STP, or both (in the case of partial
GTT). If performed within the SGSN, the GTT tables are configured via O&M functions
with the appropriate translations.
The MAP and C7 software will be acquired from a third-party software vendor. Some
changes may be required to MAP message formats to accommodate GPRS functions.
MAP is specified in GSM 09.02.
In Trial release of the SGSN, the Gr interface is replaced by an internal database lookup.
Information typically stored in an HLR will be instead stored locally within a GPRS
register in the SGSN. This is necessary, since it is unlikely that the necessary HLR
upgrades will be in place for initial GPRS trials.
The Gr interface will be supported in GA release of the SGSN product. In the Field Trial
release, the GPRS subscriber records are instead stored within an internal HLR of the
SGSN. This allows the GPRS service to be deployed without the need to update the
HLRs at the same time. As the HLR equipment is upgraded to support the GPRS
subscriber records, the Gr interface can be deployed on the SGSNs with a future
software release.
The internal HLR within the SGSN contains the IMSI of each GPRS subscriber along
with the GPRS specific subscription information, such as the subscriber IP address and
GGSN address.
2–18 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Standardized interfaces
Gs interface
Gs is the interface that enables the SGSN send local information to the MSC/VLR, and
enables SGSN receive paging requests from the MSC/VLR.
Over this interface, an association is created between the SGSN and MSC/VLR to
provide for interactions between the SGSN and the MSC/VLR. This association is
created when the VLR stores the SGSN number, and the SGSN stores the VLR number.
The association is used for coordinating class-A and class-B MSs in STANDBY and
READY states. A class-C MS can be attached only to either the GPRS or the circuit
switched service.
The association supports the following actions:
S IMSI attach and detach via SGSN. This makes combined GPRS/IMSI attach and
combined GPRS/IMSI detach possible, thus saving radio resources.
S Coordination of Local Area (LA) update and Routeing Area (RA) update, including
periodic updates, thus saving radio resources. A combined RA/LA update is sent
from the MS to the SGSN. The SGSN forwards the LA update to the VLR.
S Paging for a CS connection via the SGSN.
S Alert procedures for non-GPRS services.
S Suspend and resume.
S Identification procedure.
S Mobility Management (MM) information procedure.
When the Gs interface is present, all MSC-originated paging of GPRS-attached MSs
goes via the SGSN, thus allowing network coordination of paging. Paging coordination is
made by the SGSN based on the IMSI, and is provided independently of whether the MS
is in STANDBY or in READY state. When the SGSN receives a paging request over the
Gs interface for an IMSI unknown in the SGSN, the SGSN pages for the MS in the area
specified by the location information provided by the MSC/VLR. If no such location
information is provided, the SGSN pages for the MS in the routeing areas corresponding
to that MSC/VLR.
When the Gs interface is not present, all MSC-originated paging of GPRS-attached MSs
goes via the A interface, and coordination of paging cannot be performed.
The MM procedures use MAP interfaces between the SGSN and the MSC/VLR (Gs).

68P02903W01-O
FIELD TRIAL
Network protocols GPRS-300-101
Network protocols
GPRS application
protocols
There are many different protocols associated with GPRS networks. For convenience
they are presented in two groups:
S SGSN-BSS BSSGP protocol
S Other network protocols.
SGSN-BSS
BSSGP protocol
BSSGB protocol description
The primary function of BSSGP is to provide the radio-related, QoS, and routeing
information that is required to transmit user data between a BSS and an SGSN. In the
BSS, it acts as an interface between LLC frames and RLC/MAC blocks. In the SGSN, it
forms an interface between RLC/MAC-derived information and LLC frames. A secondary
function is to enable two physically distinct nodes, the SGSN and BSS, to operate node
management control functions.
There is a one-to-one relationship between the BSSGP protocol in the SGSN and in the
BSS. If one SGSN handles multiple BSSs, the SGSN has to have one BSSGP protocol
machine for each BSS. The main functions for the BSSGP protocol are to:
S Provide a connectionless link between the SGSN and the BSS.
S Transfer data unconfirmed between the SGSN and the BSS.
S Handle paging requests from SGSN to BSS.
S Give support for flushing of old messages in the BSS, such as when a MS
changes BSS.
S Support multiple layer 2 links between the SGSN and one BSS.
For packet transfer from SGSN to BSS the BSSGP is using a three-split address (cell
identity), QoS, and the MS identification, such as Temporary Logical Link Identity (TLLI),
IMSI. These three address parts are used to dynamically create queues and contexts in
both SGSN and BSS. The flow control mechanism is based on these queues and
contexts. For packet transfer from the BSS to the SGSN only the QoS and MS identity
are used for addressing of queues in the SGSN.
A cell context in the BSS consists of one queue for LLC packets per cell and per QoS
priority level. Signalling uses its own queue context and has the highest priority. The cell
context in BSS is allocated for each cell supporting GPRS. For each new GPRS cell
introduced in the BSS area, a new cell context will be allocated. The cell contexts may be
released either after a certain time, if the context has not been active, or if the cell
parameters are modified. This is an implementation issue. In the SGSN, the cell context
consists of the queue status for each QoS priority queue. QoS priority queues are
dynamically allocated and de-allocated (the procedures to accomplish this are
implementation dependent).
Flow control for up-link traffic from BSS to SGSN is managed by BSSGP for each link
and QoS priority level. When the queues in the SGSN reach their thresholds, the SGSN
uses the flow control messages to notify BSS that only BSSGP messages above a
certain QoS priority level can be accepted. If the highest QoS priority level is indicated in
the flow control message, all data traffic for that Gb link is interrupted. When SGSN
congestion recedes below the given threshold, the SGSN notifies the BSS about this
event. Signalling has its own queue with the highest-priority level.
2–20 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Network protocols
GPRS protocol stack

The Internet Protocol (IP) based backbone network is used to transfer both data and
signalling messages between support nodes. In addition, depending upon the reliability
required, either Transmission Control Protocol (TCP) or User Datagram Protocol (UDP)
is used in conjunction with IP. On top of the TCP/UDP layer spanning the Gn interface is
the GRPR Tunnelling Protocol (GTP). GTP is responsible for converting data flows from
the external networks such as X.25/Internet to the TCP/IP datagram format. Refer to
Figure 2-7 for a summary.
APPLIC-
ATION
IP/X.25 IP/X.25
SNDCP SNDCP GTP GTP
LLC LLC TCP/ TCP/

UDP UDP
RELAY
RLC RLC BSSGP BSSGP IP IP
FRAME FRAME
MAC MAC RELAY L2 L2
RELAY
GSM RF GSM L1 bis L1 bis L1 L1

RF
Um Gb Gn Gi
MS BSS SGSN GGSN
Figure 2-7 GPRS protocol stack

68P02903W01-O
FIELD TRIAL
BSS GPRS protocol

The protocol architecture that lies between the BSS and the SGSN is based on Frame
Relay (FR). FR uses virtual circuits allowing data to be multiplexed from several MSs. On
top of the FR protocols is another GPRS-specific protocol called Base Station System
GPRS Protocol (BSSGP).
The primary functions of BSSGP include the provision of radio-related information used
by the Radio Link Control (RLC) and Medium Access Control (MAC) functions. The
BSSGP must also provide functionality to enable two physically distinct nodes, an SGSN
and a BSS, to operate node management control functions.
Figure 2-8 illustrates the usage of BSSGP. Not only the Logical Link Control (LLC)
utilizes BSSGP, but also GPRS Mobility Management (GMM) and Network Management
(NM) at the SGSN. The functions of GMM deal with paging and radio status requests,
whereas the NM functions deal with such aspects as flow control and resets.
At the BSS, a ReLay (RL) provides the functions for controlling the transfer of LLC
frames between the RLC/MAC layer and the BSSGP layer.
SERVICE MODEL IN A BSS SERVICE MODEL IN A BSS
RELAY GMM NM LLC GMM NM
RL RL GMM NM BSSGP GMM NM
RLC/MAC BSSGP BSSGP
NETWORK SERVICE NETWORK SERVICE
Figure 2-8 BSSGP service model
2–22 15th Sep 99

68P02903W01-O
FIELD TRIAL
Other network
protocols
The following protocols are briefly outlined in the sections that follow this list:
S Border Gateway Protocol (BGP).
S Exterior Gateway Protocol (EGP).
S File Transfer Protocol (FTP).
S Frame Relay (FR).
S GPRS Tunnelling Protocol (GTP).
S Internet Protocol (IP).
S Lower Layer Compatibility (LLC).
S Network Services (NS).
S SubNetwork Dependent Convergence Protocol (SNDCP).
S SubNetwork Management Protocol (SNMP).
S Transmission Control Protocol/Internet Protocol (TCP/IP).
S User Datagram Protocol/Transmission Control Protocol (UDP/TCP).
Border gateway protocol

BGP is an inter-CommHub domain routeing protocol used in Internet core routers to
detect routeing loops. The BGP uses metrics to make intelligent routeing decisions.
Although designed as an inter-CommHub domain protocol, BGP can be used both within
and between domains. Two BGP neighbours communicating between domains must
reside on the same physical network. BGP routers within the same domain communicate
with one another for two reasons:
S To ensure that they have a consistent view of the domain.
S To determine which BGP router within that domain will serve as the connection
point to and from certain external domains.
Exterior gateway protocol

EGP is the primary inter-CommHub domain routeing protocol used in the Internet for
communication between the core Internet routers.
EGP is a dynamic routeing protocol that sends updates to neighbouring routers at regular
intervals, indicating the networks to which it is directly attached. This information is used
to construct and maintain routeing tables.
File Transfer Protocol

FTP is used by GPRS to transfer a file, or a portion of a file, from one system to another,
such as from the OMC-CommHub to the ISS.

68P02903W01-O
FIELD TRIAL
Frame relay protocol

FR protocols are used on the Gb interfaces of the SGSN. The frame relay access
environment includes all the hardware and software used to connect the SGSN sites.
internal computing environment to the frame relay service. The frame relay access
hardware consists of one or more E1/T1 interface boards.
A local loop connection is required to access a frame relay network. This involves a
connection from the SGSN premises to the nearest available Service Access Point
(SAP) for the frame relay carrier.
The following characteristics apply to the frame relay connection:
S The maximum frame relay information field size is 1,600 octets.
S The frame relay address length is 2 octets.
S The BSS and SGSN both use frame relay Data Terminal Equipment (DTE)
functionality; the SGSN can also use Data Communications Equipment (DCE)
functionality.
S Frame relay uses Permanent Virtual Circuits (PVCs).
S One or more frame relay PVCs are used between one SGSN and one BSS to
transport BSSGP Packet Data Units (PDU)s.
GTP
GTP tunnels user data and signalling between GSNs in the GPRS network. GTP uses
TCP/IP and UDP/IP protocols to communicate between the SGSN and GGSN, and
between two peer SGSNs during an inter-CommHub-SGSN-MS transfer. GTP
simultaneously supports two operation modes for information transfer between the
GGSN and SGSN: acknowledged and unacknowledged.
Internet protocol
IPv6 is a standard for the GPRS backbone network protocol that is used for routeing user
data and control signalling within the GSN, as well as to and from the Internet. IPv6
significantly increases the address space for IP devices (refer to GSM 03.60).
IPv6 supports more levels of addressing hierarchy and a greater number of addressable
nodes than IPv4 by increasing the IP address size from 32 bits to 128 bits. The
saleability of multicast routeing is improved by adding a scope field to multicast
addresses. A new type of address, called an anycast address, is defined which is used to
send a packet to any one of a group of nodes.
The IPv6 standards also define how to encapsulate IPv6 addresses within IPv4
addresses.
Besides expanded address, the IPv6 protocol also provides added security.
Lower layer compatibility protocol

LLC protocol is located below the SNDCP layer, and provides a reliable link between the
MS and its SGSN.
Network service protocol

The NS protocol transports BSSGP PDUs, and is based on the frame relay connection
between the BSS and the SGSN.
2–24 15th Sep 99

68P02903W01-O
FIELD TRIAL
Subnetwork dependent convergence protocol

SNDCP maps network-CommHub level characteristics onto the characteristics of the
underlying network.
SNDCP provides the following services to the network layer:
S Transmission and reception of Network-CommHub (N-CommHub) PDUs in
acknowledged and unacknowledged LLC mode.
S Transmission and reception between the MS and SGSN of variable-CommHub
length N-CommHub PDUs.
S Transmission and reception of N-CommHub PDUs between the SGSN and MS
according to the negotiated QoS profile.
S Transfer of the minimum amount of data possible between the SGSN and MS
using compression techniques.
Subnetwork management protocol

The OMC-CommHubG uses SNMP to gather information from devices in the network,
including the GSN CommHub, GGSN and SGSN boards, and the ISS.
Transmission control protocol/internet protocol

TCP/IP is used in the GPRS network to transport data for end-to-end user applications.
TCP/IP was selected because it allows public access to network protocols, and it allows
seamless integration between all computing environments that wish to operate in a
network environment. IP is defined in RFC 791.
Before a mobile can use the GPRS network, it must be assigned a static, a permanent
address assigned to the subscriber device by an operator, and an IP version 4 network
layer address. A mobile may have multiple addresses. IP addresses are mapped in the
HLR to the International Mobile Subscriber Identity (IMSI) of the subscriber.
The SGSN uses additional features of an IP network. For example, the SGSN uses IP
header and data compression to optimize the capacity of the radio path. The GSN
CommHub includes a network-controlled message screening function that filters out
unauthorized or unsolicited messages from entering the GPRS network. The filtering
function is typically performed by an IP firewall (refer to GSM 03.60).
User datagram protocol/transmission control protocol

UDP carries GTP PDUs for protocols that do not need a reliable data link. UDP also
provides protection against corrupted GTP PDUs.
TCP carries GTP PDUs for protocols requiring a reliable data link. TCP also provides
flow control and protection against lost and corrupted GTP PDUs.

68P02903W01-O
FIELD TRIAL
Logical link control

The LLC layer provides a highly reliable logical connection between the SGSN and the
MS, and as such spans both the Gb and Um interfaces. The LLC has been designed to
be independent of the underlying radio interface protocols in order to allow for the
introduction of alternative GPRS radio solutions at a later date. The LLC layer structure is
shown in Figure 2-9.
GPRS MOBILITY MANAGEMENT SNDCP SMS
LLGMM LLGMM LL3 LL5 LL9 LL11 LLSMS
LOGICAL
LINK
LOGICAL
ENTITY
LOGICAL LINK
LOGICAL SAPI=7
ENTITY
LINK LOGICAL LINK
MANAGE- SAPI=11
LOGICAL LINK ENTITY
MENT LINK ENTITY SAPI=9
ENTITY LOGICAL ENTITY SAPI=5
LINK SAPI=3
ENTITY
SAPI=1
MULTIPLEX PROCEDURE
GRR BSSGP
RLC/MAC LAYER MS SGSN BSSGP LAYER
RLC/MAC BSSGP
SIGNALLING
SIGNALLING AND DATA TRANSFER
Figure 2-9 LLC layer structure
2–26 15th Sep 99

68P02903W01-O
FIELD TRIAL
Chapter 3
PCU general description

68P02903W01-O
FIELD TRIAL
GPRS-300-101
ii 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101
Chapter 3
PCU general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Introduction to the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
PCU system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Overview of PCU in the GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
PCU summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
PCU environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
PCU description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
PCU purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
PCU hardware architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5
PCU configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
Data and signalling paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
PCU hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
PCU interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–15
GPRS BSS interface overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–15
PCU interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16
PCU system and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
System and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
PCU processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18

68P02903W01-O
FIELD TRIAL
GPRS-300-101
iv 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 Chapter overview
Chapter overview
Introduction to
the PCU
This chapter provides a general description of the Motorola Packet Control Unit (PCU),
which links between the GPRS Support Node (GSN) and the Motorola BSS.
The GSM recommendations define the functions of the GPRS, but allow flexibility in its
design. This chapter describes some of the unique features of the Motorola PCU.
Chapter overview
The chapter contains the following information about the PCU:
S PCU system.
S PCU description.
S PCU configuration.
S PCU interfaces.
S PCU system and control of functions.

68P02903W01-O
FIELD TRIAL
PCU system GPRS-300-101
PCU system
Overview of PCU
in the GPRS
GPRS is a packet radio system that allows mobile subscriber (MS) units to access data
services (such as World Wide Web (WWW) or email) using a modified GSM air interface
protocol. The modified air interface protocol allows multiple MS units to share a single
timeslot, and also allows different mobiles to utilize the uplink and downlink timeslots.
Two units form the basis of the Motorola GPRS hardware:
S The GSN complex module (SGSN, GGSN, GSN CommHub, and ISS).
S The Packet Control Unit (PCU).
The PCU is an adaptor/handler unit that permits the Motorola GSM facility access to the
internet facility. As such it needs interfaces with the BSC, on the GSM side, and the
SGSN, on the internet side.
Figure 3-1 shows a high-level view of how the PCU fits into the overall system
architecture.
BSC PCU SGSN
Figure 3-1 High-level view of the PCU environment
PCU summary
The PCU is a collection of high-performance processors that are responsible for:
S Packet scheduling on the air interface.
S Ensuring that efficient use is made of the air interface (which includes the notion
that a single MS unit can be utilizing up to eight radio timeslots for a single data
transfer.)
S Taking small uplink packets from the E1 links connected to the BSS that are
carrying user data from the MS units, and forming larger uplink packets to be sent
over the E1 links to the SGSN.
S Packet segmentation and packetization on the frame relay link to the SGSN
network entity.
S Taking downlink packets from the SGSN and segmenting these packets into small
packets to be sent to the MS units.
3–2 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 PCU system
PCU environment
Figure 3-2 shows the PCU is positioned within the GPRS network, where:
S BSC is Base Station Controller.
S BTS is Base Tranceiver Station.
S GGSN is Gateway GPRS Support Node.
S GR is Gb Router.
S HLR is Home Location Register.
S MS is Mobile Station.
S MSC is Mobile Switching Centre.
S PCU is Packet Control Unit.
S PDN is Public Data Network.
S PLMN is Public Land Mobile Network.
S SGSN is Service GPRS Support Node.
S TE is Terminal Equipment.
HLR GR
PDN TE
MAP-G Gr
Gs Gn Gi
MSC SGSN GGSN
Gb Gn
PCU
BSC GGSN
R/S Um
Abis OTHER
TE MS BTS PLMN
SIGNALLING
SIGNALLING AND DATA TRANSFER
Figure 3-2 Diagram showing PCU within the GPRS network

68P02903W01-O
FIELD TRIAL
PCU description GPRS-300-101
PCU description
PCU purpose
The new BSS functionality for GPRS mainly resides at the Packet Controller Unit (PCU).
The PCU includes the handling of frame relay, Network Services (NS) signalling, BSSGP
signalling, routeing of signalling messages, Radio Link Control (RLC), and Media Access
Control (MAC) preload and transferring of user data.
User data is routed to the PCU via the Channel Codec Unit (CCU) uplink from the BTS to
the BSC and then over E1 to the PCU. At the PCU the RLC blocks are reformulated in
Logical Link Control (LLC) frames and forwarded to the SGSN.
BSSGP signalling and NS signalling occur between the PCU and the SGSN using frame
relay protocol. There is also signalling between existing functional process at the BSC
such as the between the Base Station control Processor (BSP) at the BSC and the PCU
via the E1 interface, as well as between the PCU and channel coders.
The purpose of the PCU is to perform a variety of functions.
The PCU is responsible for the following GPRS MAC and RLC layer functions:
S LLC layer PDU segmentation into RLC blocks for downlink transmission.
S LLC layer PDU re-assembly from RLC blocks for uplink transmissions.
S PDCH scheduling functions for the uplink and downlink data transfers.
S PDCH uplink ARQ functions, including RLC block ack/nak.
S PDCH downlink ARQ function, including buffering and retransmission of RLC
blocks.
S Channel access control functions, such as access requests and grants.
S Radio channel management functions, such as power control, congestion control,
broadcast control information.
The functions inside the CCU are:
S The channel coding functions, including Forward Error Correction (FEC) and
interleaving.
S Radio channel measurement functions, including received quality level, received
signal level, and information related to timing advance measurements.
The BSS is responsible for allocation and de-allocation of radio resources. A PCU frame
can be transferred between the PCU and the CCU every 20 ms.
The remote PCU is considered a part of the BSC. The signalling between the BSC and
the PCU may be performed by using BSC internal signals. The inband signalling between
the CCU and the PCU functions, using PCU frames, is required when the Abis interface
is applied (options B and C in Figure 3-3 ).
3–4 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 PCU description
Um Gb
BTS BSC SITE GSN SITE

CCU
PCU A
CCU
Abis
CCU
PCU B
CCU

CCU
PCU C
CCU
Gb
KEY: CIRCUIT-SWITCHING FUNCTION (16 kbit/s OR 64 kbit/s)
PACKET-SWITCHING FUNCTION
Figure 3-3 Remote PCU positions
Remote PCU
When the PCU is remote to the BTS, the Channel Codec Unit (CCU) in the BTS may
control some of the functions in the remote PCU in the BSC.
The PCU may also control some of the functions of the CCU. This remote control is
performed by inband signalling carried by the control bits (C-bits) in each PCU frame.
PCU hardware
architecture
The PCU hardware is off-the-shelf equipment that is based upon the Compact PCI
(cPCI) standards. The cPCI is a set of standards that define a common chassis, power
supplies, and processor boards.
There are four cPCI board types:
S The Master Processor (MPROC).
S The BRIDGE (PPB).
S The Packet Interface Control Processor (PICP).
S The Packet Resource Processor (PRP).
The PICP and PRP boards may initially be the same hardware platform, the DPROC, but
in the long term they may be different hardware platforms. There is a single Plugin
Memory Card (PMC) module currently planned, the dual E1 PMC. These PMC modules
are installed on PICP boards.
MPROC
The MPROC is the system slot processor that is responsible for bus arbitration and CPCI
clock generation. It contains interface and BSSGP protocol functions, and is called the
PCU System Processor (PSP). Only one PSP may be equipped at a PCU.

68P02903W01-O
FIELD TRIAL
MPROC board (PSP)

The MPROC is the main control processor for the system, and works in conjunction with
the PPB. It acts as PCI system host, and in conjunction with the PPB supports hot
removal control for all board slots. It performs resource allocation, fault management,
and gateway management functions (such as control of allocation of cells to PRP
boards). These functions comprise the PSP.
The MPROC requires a high-performance processor system such as the 266 MHz
MPC750 with an 83 MHz bus for the memory subsystem. A minimum of 128 Mbytes of
DRAM is supported, upgradeable to 256 Mbytes. The MPROC has the ability to support
a single PMC module that is reserved for future use.
PCU system processor

The PSP resides on the MPROC. As well as control of bus arbitration, the PSP has the
following functional units:
GB manager
The Gb Manager (GBM) handles blocking/unblocking and reset.
Gateway manager
The GateWay Manager (GWM) handles the following function:
S Code loading of objects during initialization and reset.
S Board initialization and startup for software processes.
S Handling database information and changing affected functional units.
S Fault management functions (that is fault detection, fault recovery).
S Collection of statistics from functional units, and forwarding to the Central Statistics
Processor (CSP) on the GPROC.
S Collection of cell list for BSC-BTS dynamic allocation purposes.
S Audit procedures.
S Alarm collection and relaying.
S Cell resource sharing (that is balancing of cells) across equipped PRPs.
The PCU GWM acts as the interface to the BSC FM, SM, IP, CM, MMI, CP, Stats
process, CSP, as well as Radio SubSystem (RSS).
An I/O function is created on the PSP for communication with the PRP and PICP
functional units.
Bridge
The bridge, known as the PCI to PCI Bridge (PPB), allows an MPROC to be linked to a
separate bus. The PPB and MPROC are paired boards.
Bridge board
The PCU processor Bridge Board (PBB) board allows the redundant operation of the
system host PROC board, and gives the host PROC access to all boards in the system.
It supports control of hotswap for all boards, and a communication link between Bridge
boards to allow checkpointing and heartbeat messages between MPROC boards. This
allows migration to a fully hot swap, redundant, high-availability system, including hot
standby/load sharing between MPROC boards in the future, if required.
3–6 15th Sep 99

68P02903W01-O
FIELD TRIAL
DPROC
The DPROC boards are non-system slot boards that have two PMC sockets and can
host two different functions. The DPROC can be configured as either a PICP or a PRP.
If configured as the PICP, the DPROC contains up to two PMC modules to provide the
E1 interfaces. The E1 interface can support the Gb interface or the GPRS Data Stream
(GDS) interface, including the GPRS Signalling Link (GSL).
If configured as a PRP, the DPROC performs air interface scheduling, and neither of the
PMC sockets is used. A single processor can support a pool of 120 radio timeslots, of
which 30 radio timeslots can be active at any one time.
DPROC (PICP)
The DPROC (PICP) is used for all network interfacing functions to the outside world,
such as the SGSN and BSC. The PICP has up to two interface modules installed. Data
to/from these interfaces passes through the on-board processor. This processor has
different functions dependent on the interface type, but includes features such as packet
routeing on an incoming SGSN link, and packet scheduling to an outgoing SGSN link.
This board is a PCI slave board. The PICP routes data received from the SGSN or BSC
to the appropriate PRP board. The DPROC requires a high-performance processor
system such as a 266 MHz MPC750 with an 83 MHz bus for the memory subsystem. A
minimum of128 Mbytes of DRAM is supported, upgradeable to 256 Mbytes. The DPROC
(PICP) also supports two PMC modules that are used to house the E1 SGSN/BSC
interfaces.
Packet interface control processor

The PICP is a function residing on a DPROC. A PICP is made up of functional units (see
Figure 3-4).
PICP is a Gb functional unit to terminate the Gb links. Its function is to determine
whether an Logical Link Control (LLC) frame is user data, SGSN-MS signalling, or
BSSGP signalling. The LLC frame is then routed to the appropriate board based on LLC
frame type:
S Route signalling for paging messages to appropriate cell.
S Routeing of flushing of queued SDU at appropriate cell.
S Routeing flow control of downlink traffic.
S Queuing MS packets based on priority queues.
GSL LAPD functional unit for synchronisation of LAPD link over GSL between the PCU
and the BSC.
A Transcoder Rate Adaption Unit (TRAU) functional unit created for the synchronisation
and handling of PCU frames between the PCU and the BSC.
A PICP status functional unit for debugging mechanisms, statistics and alarms.
Finally an I/O functional unit is created for routeing messages between the functional
units on the PICP and the functional units on the PSP.

68P02903W01-O
FIELD TRIAL
TO PRP TO PSP
PICP
PMC 860 DUAL E1
TRAU TRAU
BSC COMM E1 FU GATEWAY
I/O MANAGER
(GWM)
GSL
BSC COMM E1 LAPD
MGR
TO
GWM FUs
PMC 860 DUAL E1
Gb LINK E1 TO
OTHER GB FUs
FRAME GB
RELAY FU
Gb LINK E1
PPC 860 DUAL E1 PP750
PICP
FRAME
GSL/TRAU
RELAY
PICP STATUS
(ALARMS,
STATS,
I/O DEBUGGING)
Figure 3-4 Packet interface control processor
DPROC (PRP)
The DPROC (PRP) is the processor where all of the radio related processing takes
place. Each of the GPRS channels is routed to a PRP, which performs all of the
RLC/MAC processing, air interface scheduling, and frame synchronization on BTS facing
channels.
The performance required from this board is such that it supports a minimum of 30 active
air interface timeslots, with the ability to monitor another 90 timeslots. A future doubling
of this capacity is envisaged (this will require 400 Mbytes/sec memory bandwidth). The
PRP maintains synchronization to the air interface by the exchange of the PCU-CCU
frames (which is transmitted even on inactive timeslots).
3–8 15th Sep 99

68P02903W01-O
FIELD TRIAL
Packet resource processor

The PRP is where all radio related processing takes place. The PRP performs all of
RLC/MAC processing, air interface scheduling and frame synchronisation on the BTS
facing channels. The following functional units provide this functionality (see Figure 3-5):
PICP
FRAME
GSL/TRAU RELAY
PICP STATUS
(ALARMS,
I/O STATS,
DEBUGGING)
PSP
(GATEWAY PSP STATUS
MANAGER) (ALARMS,
INTERFACE STATS,
TO: DEBUGGING)
CM I/O
FM
RSS
CP Gb MANAGER
CSP
PRP STATUS
PRP
(ALARMS, CELL 2
STATS,
DEBUGGING) I/O CELL N
CELL 1
PAGING, FCBM
SYS INFO,
PACKET ACCESS
PRP SCHEDULER GRANTS
status RLC SEGMENTING
(alarms,
stats,
debuggin POWER
CONTROL LLC CAT
g) TIMING
ADVANCE
UPLINK
DOWNLINK
Figure 3-5 PCU resource processor
Packet scheduler
Packet scheduler is created to handle all scheduling of Packet Data CHannels (PDCHs)
on a per-call per Quality of Service (QoS) level basis.
CCCH paging manager

The Common Control CHannel (CCCH) paging manager processes the paging
messages coming from the SGSN to the BSC/BTS.

68P02903W01-O
FIELD TRIAL
Downlink segmentor
Downlink segmentor segments Logical Link Control (LLC) frames into Radio Link Control
(RLC) data blocks to be transmitted over the air interface.
Uplink concentrator
Uplink concentrator concentrates all the RLC data blocks for a Temporary Block Flow
(TBF) into a LLC frame.
Timeslot resource shifter

The Timeslot Resource Shifter (TRS) determines which TS are active in the PRP board
to support GPRS traffic.
System information manager

The SYstem information Manager (SYM) builds and sends GPRS system information
over the BCCH.
I/O function
I/O function is used for routeing between the functional units on the PRP, PICP, and PSP.
Flow control buffer management

Flow control Buffer Management (FBM) is a functional unit residing on the PRP to handle
all packets received by the SGSN.
Chassis
The chassis into which the boards are installed is intended to be an OEM item. It houses
a maximum of 16 CPCI boards, with the ability to support redundant host processors.
The power supply system is part of this OEM solution. The host processor, redundant
host processor, and their associated bridge boards occupy four of the slots, leaving 12
generic slots for the remaining boards. Hot removal of all boards is supported.
The PCU is an additional chassis that is collocated with any BSC that supports GPRS
functionality. It interfaces to the BSC, utilizing E1 PMC modules on a DPROC (PICP)
board. This requires corresponding Multiple Serial Interface boards (MSIs) to be present
in the BSC.
The chassis is a19-inch rack-mounting module supporting sixteen 6U PCI slots. Four of
these slots are taken by the two MPROC/bridge pairs for redundant systems. This leaves
12 generic slots that can be populated by any combination of PICP, and PRP boards with
their associated PMC modules. It supports front access for all replaceable modules,
redundant/load sharing PSU system, and status LEDs. The interconnect cabling is
routeable from the rear, front, or bottom of the chassis.
E1 PMC module
The E1 PMC module performs all of the physical layer termination of the E1 link to the
SGSN. The module also supports the termination of the frame relay layer 2 protocol, and
passes received data packets to its host board processor.
The E1 interfaces to the BSC provide for physical connection of all GPRS data channels
into and out of the BSC, allowing the BSC to switch the channels to the appropriate BTS.
These links also carry the GPRS Signalling Link (GSL) between the PCU and BSC. The
GSL can be multiple 64 k timeslots. It is used to manage and control the PCU/BSC
system. The diagram below shows a system where E1 PMCs are used to connect the
TDM data to the BSC. The MSIs used for these links can be equipped in any chassis of a
multi-chassis BSC system.
3–10 15th Sep 99

68P02903W01-O
FIELD TRIAL
Fault tolerance
The PCU supports load sharing across the PRP, PICP, and E1 PMC. The hardware can
be N+M redundant (and would generally be equipped as N+1 when load sharing is
active), but software loads share across all installed boards, with any failures causing a
loss in total capacity capability. The operator determines whether the hardware is
provisioned for greater capacity than required, such that failures do not affect the system
capabilities.
The PCU supports 2N redundancy of MPROC, and PPB boards. An MPROC and PPB
board are linked in function that is they both have to be active for the system to be active.
Failure of either the MPROC, or its associated PPB, requires a switch to the other pair of
boards. Under these conditions, the other MPROC and PPB manages both sides of the
cPCI bus.

68P02903W01-O
FIELD TRIAL
PCU configuration GPRS-300-101
PCU configuration
Data and
signalling paths
There are three data and signalling paths between the PCU and the SGSN (see
Figure 3-6, Figure 3-7, and Figure 3-8):
S A direct Gb interface path (option A).
S An indirect path via the Gb interfaces through the BSC (option B).
S An indirect path via the Gb interfaces through the BSC and RXCDR (option C).
Gb
RXCDR SGSN
A Gb Gb
X.25
OMC-R BSC PCU
Abis
BSC: BASE STATION CONTROLLER
BTS: BASE TRANSCEIVER STATION
BTS MS: MOBILE STATION
OMC-R: OMC-RADIO
Um PCU: PACKET CONTROL UNIT
RXCDR: REMOTE TRANSCODER
SGSN: SERVING GPRS SUPPORT NODE
MS
Figure 3-6 BSS functional blocks
Depending upon the needs of the voice and data networks, the Gb traffic, user data, and
signalling can take different paths between the PCU and SGSN. In all cases, the Gb
traffic is always carried over 64 kbit/s E1 channels. Refer to Figure 3-6, Figure 3-7, and
Figure 3-8 for a summary of the three connection methods.
Option C, routeing a connection through the transcoder, is a convenient way to bring
GPRS traffic from multiple PCUs to a single SGSN.
3–12 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 PCU configuration
ALL INTERFACES ARE Gb nx64 kbit/s E1 CHANNELS LAPF
PCU PCU PCU
BSC BSC
RXCDR
SGSN SGSN SGSN
OPTION A: DIRECT OPTION B: BSC OPTION C: BSC AND

PASS-THROUGH RXCDR
PASS-THROUGH
Figure 3-7 Data and signalling paths between PCU and SGSN
MSC
A INTERFACE
Gb OPTION A
RXCDR
OMC-R Gb OPTION B
BSC
PCU Gb OPTION C
BTS1 BTSn
Figure 3-8 Gb interface alternatives

68P02903W01-O
FIELD TRIAL
PCU configuration GPRS-300-101
PCU hardware
The PCU hardware is illustrated in the Cabinet chapter as well as in Figure 3-9 below.
The PCU description earlier in this chapter describes the boards listed below and seen
in Figure 3-9.
The minimum configuration is:
S 1 MPROC, main system control processor.
S 1 PBB, bridge board.
S 1 DPROC (PICP), for network interfacing to BSC and SGSN.
S 1 DPROC (PRP), for radio-related processing.
These boards are housed in a 16-slot chassis.
A fully-populated chassis holds 4 times the minimum configuration.
The PCU cabinet can accommodate up to 3 PCU chassis.
Figure 3-9 shows a fully-populated PCU chassis.
T T T T T T B B T T T T T T
CARD SLOT 1 ALARM PANEL CARD SLOT 11

1 11
A A
U U
M M X X
P P
R R
D D D D D D O O D D D D D D
P P P P P P C C P P P P P P
R R R R R R R R R R R R
O O O O O O R O O O O O O
C C C C C C C C C C C C A A
U U
X X
PS/FAN PS/FAN PS/FAN
AN AIR FILTER IS ATTACHED TO THE FRONT OF EACH THE 3 FAN/POWER SUPPLY UNITS
B: BRIDGE CARD
T: E1 TRANSITION MODULE
Figure 3-9 PCU chassis front view
3–14 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 PCU interfaces
PCU interfaces
GPRS BSS
interface
overview
The Motorola GPRS BSS (see Figure 3-10) includes the:
S Base Station Controller (BSC).
S Base Transceiver Station (BTS).
S Operations and Management Centre-Radio (OMC-R).
S Packet Control Unit (PCU).
Gb
RXCDR SGSN
A Gb Gb
X.25
OMC-R BSC PCU
Abis
BSC: BASE STATION CONTROLLER
BTS: BASE TRANSCEIVER STATION
BTS MS: MOBILE STATION
OMC-R: OMC-RADIO
Um PCU: PACKET CONTROL UNIT
RXCDR: REMOTE TRANSCODER
SGSN: SERVING GPRS SUPPORT NODE
MS
Figure 3-10 BSS functional blocks
The BSC supports the following interfaces (see Figure 3-10):

S BSC-BTS (Abis).
S BSC-OMC-R (X.25).
S BSC-RXCDR (A).
S BSC-PCU.
S PCU-SGSN (Gb).
This section defines the interfaces the PCU has with other elements of the GPRS.

68P02903W01-O
FIELD TRIAL
PCU interfaces GPRS-300-101
PCU interfaces
PCU-BTS interface
The PCU-BTS interface carries user data and radio resource management information,
called Radio Link Control/Media Access Control (RLC/MAC) packets, between the PCU
and BTS. The GPRS Signalling Links (GSL) carry signalling information on 64 kbit/s E1
timeslots between the PCU and BSC.
A GDS carries the packet data on 16 kbit/s E1 timeslots between the PCU and BSC.
An RSL carries the signalling information on 16 kbit/s or 64 kbit/s E1 timeslots between
the BSC and BTS.
Another 16 kbit/s E1 TS or channel carries the TRAU-like framed data between the BSC
and BTS.
A BCCH or CCCH carries the signalling information between the BTS and MS.
Between the BTS and MS, the packet data is carried over CS1 or CS2 encoded PDCHs
(see Figure 3-11).
GSL RSL Um
64 kbit/s TS 16/64 kbit/s TS BCCH
LAPD LAPD CCCH
PCU BSC BTS MS
SIGNALLING SIGNALLING SIGNALLING SIGNALLING
DATA DATA DATA DATA
GDS 16 kbit/s Um
16 kbit/s TS TRAU PDCH
CS1 or CS2
Figure 3-11 Data and signalling paths between PCU and MS

Figure 3-12 provides more detail of the E1 physical links.
BSC
E1PMC
DPROC
DPROC
(PICP)
(PICP)
MSI
MSI
E1PMC
The number of MSI links

needed is dependent on the
PCU capacity. All MSIs can
reside in a single BSC PCU
chassis even in expanded
systems.
Figure 3-12 PCU to BSC connection utilizing E1 links (four shown)
3–16 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 PCU interfaces
Gb interface
The Gb traffic, user data and signalling, can take different paths between the PCU and
SGSN depending upon the needs of the voice and data networks. In all cases, the Gb
traffic is always carried over 64 kbit/s E1 channels. Refer to Figure 3-13 for a summary of
the three connection methods. Option C, routeing a connection through the transcoder, is
a convenient way to bring GPRS traffic from multiple PCUs to a single SGSN.
ALL INTERFACES ARE Gb nx64kbit/s E1 CHANNELS LAPF
PCU PCU PCU
BSC BSC
RXCDR
SGSN SGSN SGSN
OPTION A: DIRECT OPTION B: BSC OPTION C: BSC AND

PASS-THROUGH RXCDR
PASS-THROUGH
Figure 3-13 Data and signalling paths between PCU and SGSN
The PCU is managed, including software download and operations, by the OMC-R as an
extension to the BSS. The OMC information destined for the PCU is passed through the
BSC. The CMIP interface is modified on the BSC to include the management of the PCU
as a new device.
A summary of this processes is shown in Figure 3-14 below.
PCU TO BE MANAGED BY Mo-MIP
OML GSL
OMC-R BSC PCU
X.25 64 kbit/s
E1
OML: OPERATIONS AND MAINTENANCE LINK

GSL: GPRS SIGNALLING LINK
Mo-MIP: OBJECT ORIENTED MANAGEMENT PROTOCOL BASED ON CMIP
Figure 3-14 PCU is managed from the OMC-R

68P02903W01-O
FIELD TRIAL
PCU system and control functions GPRS-300-101
PCU system and control functions
System and
control functions
The Packet Control Unit (PCU) performs:
S Radio functions.
S GPRS network functions.
PCU has interfaces to:
S An OMC-R.
S BSC.
S SGSN.
Radio functions
The PCU is responsible for the following GPRS MAC and RLC layer functions as defined
in GSM 03.64:
S LLC layer PDU segmentation into RLC blocks for down-link transmission.
S LLC layer PDU re-assembly from RLC blocks for up-link transmissions.
S PDCH scheduling functions for the up-link and down-link data transfers.
S PDCH up-link ARQ functions, including RLC block ack/nak.
S PDCH down-link ARQ function, including buffering and retransmissions of RLC
blocks.
S Channel access control functions, such as access requests and grants.
S Radio channel management functions, such as power control, congestion control,
broadcast control information.
S Interacting with existing BSS software for allocation/de-allocation of radio
resources for GPRS.
S Multiplexes data and signalling onto BSC facing E1 links.
SGSN functions
The PCU and the SGSN use frame relay and the Base Station System GPRS Protocol
(BSSGP) protocols to exchange user data and signalling information. The frame relay
network can be point-to-point or an actual network. Signalling data, used for flow control
and congestion management, is exchanged between the PCU and SGSN. On the
down-link side, the PCU uses the QoS information that is contained within each LLC
frame to determine how to buffer and schedule the GPRS data.
PCU processes
There are three PCU processes:
S PRP processes.
S GB processes.
S GWM processes.
3–18 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 PCU system and control functions
PRP processes:
The PRP processes are listed below:
S The Packet Resource Manager (PRM):
– Performs all RLC/MAC functions.
– Realises UL/DL power control and timing advance.
S The DownLink Segmentator (DLS) segments LLC frames into RLC data blocks to
be transmitted over the air interface
S The UpLink Concatenator (ULC) concatenates RLC data blocks into LLC frames.
S The Timeslot Resource Shifter (TRS) determines which TSs are active in a PRP
board to perform a control of the GPRS traffic.
S The SYstem information Manager (SYM) builds and sends GPRS system
information messages over the BCCH.
S CCCH Paging Manager (CPGM) processes the paging messages coming from the
SGSN to the BSC/BTS.
GB processes
The GB processes are listed below:
S The Gb router (GR) routes incoming BSSGP PDUs from the SGSN to the relevant
SW process in the PCU.
S The Flow control Buffer Manager (FBM) controls buffer capacity for each cell and
each mobile so that the incoming data from the SGSN matches the air throughput.
S The Gb Manager (GBM) manages the state of all cell and signalling links between
the PCU and the SGSN.
S The Gb Transmit Manager GTM) collects all UL frames from various ULCs and
sends them on the appropriate NS-VC.
S The Network Service Tester (NST) periodically tests all alive Network
Service-Virtual Circuit (NS-VC) on a PICP board.
S The Frame Relay (FR) performs the frame relay protocol functions.
GWM processes
The GWM processes are listed below:
S The Pcu Fault Transaction Process (PFTP) is the central collection point for all
faults generated in the PCU.
S The Pcu Fault Transaction Process (PFCP) resides in every DPROC and collects
all faults for that DPROC.
S The Pcu Central Authority (PCA) initializes devices, brings them out/in of service,
tests the devices, and performs fault recovery of the PCU.
S The Pcu System Audit Process (PSAP) monitors periodically the soft devices to
maintain the reliability of the system.
S The Pcu Configuration Management (PCM) distributes all database changes
performed at the BSC to the PCU boards.
S The Cell Balancer (CB) handles the load balancing of cells across all PRPs.

68P02903W01-O
FIELD TRIAL
PCU system and control functions GPRS-300-101
3–20 15th Sep 99

68P02903W01-O
FIELD TRIAL
Chapter 4
GSN general description

68P02903W01-O
FIELD TRIAL
GPRS-300-101
ii 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101
Chapter 4
GSN general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
GSN chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
Chapter structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
GSN system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
GSN overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
GSN in GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3
GSN software architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
GGSN and SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
GSN peripheral devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7
GSN system functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
GSN management from the OMC-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
SGSN description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
SGSN description structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
SGSN functions overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
SGSN architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
GGSN description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
GGSN functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
GGSN architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
GSN CommHub description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
GSN CommHub description structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
GSN CommHub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
GSN CommHub hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
GSN CommHub modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19
ISS description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
ISS description structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
ISS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
ISS hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
ISS functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–23
Network topology structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–23
Speech transcoder functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–23
BSS serial data transmission links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26
Coded transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29
GSN standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–31
GSN standardized interfaces structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–31
Standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–31
SGSN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–32
GSN CommHub interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–36

68P02903W01-O
FIELD TRIAL
GPRS-300-101
iv 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN chapter overview
GSN chapter overview
Chapter structure
This chapter describes the outlines the operation of the GPRS Support Node (GSN) and
its components, and describes how the GSN fits into a GPRS system.
The sections in this chapter describe or provide:
S GSN system.
S SGSN description.
S GGSN description.
S GSN CommHub description.
S ISS description.
S Network topology.
S GSN standardized interfaces.

68P02903W01-O
FIELD TRIAL
GSN system GPRS-300-101
GSN system
GSN overview
The GPRS Support Node (GSN) can be equipped as a GSN complex or a GSN remote.
A GSN complex is a complete set of GPRS network functions that are located together.
A complex is expected to be deployed in the centre of the GPRS servicing area.
A GSN remote is a set of SGSNs that service a remote or detached GPRS area that is
too small to justify an entire complex. At the remote, a GSN CommHub ties the remote
SGSNs together and provides the network link back to the serving GSN complex. In
addition, the complex provides the remote with the functions of an O&M, GGSN, DNS
services, charging gateway, and external interfaces and services. See the Figure 4-1 and
Figure 4-2.
GSN functional blocks

Figure 4-1 shows the main GSN functional blocks.
PACKET DATA
NETWORK
SMS
HLR
Gi
Gr, Gd Gr, Gd
GSN Gn
GSN BILLING SYSTEM
REMOTE COMPLEX
Gb Gb
GPRS GPRS
BSS BSS
Um Um
MOBILE MOBILE
STATION STATION
Figure 4-1 Complex and remote GSN functional blocks
4–2 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN system
GSN network elements

A GSN complex has the following network elements (see Figure 4-2):
S Charging Gateway (CG).
S GSN Communications Hub (GSN CommHub).
S Gateway GPRS Support Node (GGSN).
S Internet Protocol Support Server (ISS).
S High Availability Disk Array (HADA).
S Home Location Register (HLR).
S Operations and Maintenance Centre-GPRS (OMC-G).
S Serving GPRS Support Node (SGSN).
S Short Messaging Service (SMS).
Figure 4-2 shows the elements of complex and remote GSN networks.
PACKET DATA GGSN

NETWORK
REMOTE SGSN
Gi OMC-G
GSN COMMHUB
GSN COMMHUB CHARGING

GATEWAY
SMS-C
SGSN
HLR SGSN IP SUPPORT
SERVER
Gr
TRANSCODER
Gb TRANSCODER Gb
BSC BSC
Figure 4-2 Complex and remote GSN network elements
GSN in GPRS
The GPRS Support Node (GSN) is the main element in the GPRS infrastructure. It is a
high performance, broadband packet-switching node that provides connection and
interworking with various data networks, mobility management with the GPRS registers,
and delivery of data packets to mobile stations.
The GSN can be physically integrated with the Mobile Switching Centre (MSC) or it can
be a separate network element based on the architecture of data network routers. The
user data flows directly between the GSN and the Base Station Subsystem (BSS).
Physically, the data can flow transparently through the MSC.
All GSNs must implement the Gn interface protocols in order to communicate with other
GSNs in the same Public Land Mobile Network (PLMN). A limited internal home location
register (HLR) function within the (Serving GPRS Support Node) SGSN is provided for
basic subscriber management purposes.

68P02903W01-O
FIELD TRIAL
GSN software
architecture
The GSN software architecture is designed on five functional planes (see Figure 4-3):
S Control function:
– Signalling information between different GPRS components, such as MS
attach and PDP activate.
– Macroscopic MS context information.
S Transmission function:
– Data traffic transmission between different GPRS components.
– Microscopic MS context information.
S OAMP function:
– Interface with OMC-G.
– Interface with control and transmission function for collection of OAMP data
(such as statistics)
– Interface for forwarding of alarms to the OMC-G from the control function
and transmission function.
– Configuration Management of Control and Transmission function.
S Accounting metering function:
– Interface with external billing system.
– Collection of billing information from control and transmission functions.
S Network support function:
– Domain name server.
– Time server.
BILLING/ NETWORK
ACCOUNTING SUPPORT OMC-G
SYSTEM SERVER
CONTROL FUNCTION
METERING FUNCTION
OAMP FUNCTION
ACCOUNTING
TRANSMISSION
FUNCTION
Figure 4-3 System framework
4–4 15th Sep 99

68P02903W01-O
FIELD TRIAL
GGSN and SGSN

The GGSN and SGSN are two separate products that can be combined in the same
physical node, or can reside in different physical nodes. Figure 4-4 shows the GGSN and
SGSN in a GSN system.
TF CF
IP/100BASET IP/100BASE
GSN COMMHUB
SGSN GGSN
IP/100BASET
E1
GSN ISS
BSS
Figure 4-4 GGSN and SGSN in a GSN system
GSN complex cabinets

Figure 4-5 shows the various GSN units within the GSN complex cabinets.
GGSN (REDUNDANT)
GGSN
ISS (STAND-BY)
ISS (ACTIVE)
GSN SHELF
HADA (ACTIVE)
Figure 4-5 GSN complex cabinets

68P02903W01-O
FIELD TRIAL
SGN shelf
The SGSN boards are housed in a SGN shelf unit.
The GSN shelf for this release is a 16-slot CPX8216 CompactPCI with a 400 W power
supply and a hot swap backplane that supports rear transition modules. The sixteen slots
are accessed through the front of the chassis, and four peripheral bays to the right of the
slots provide access to hard disk and CD-ROM drives (see Figure 4-6).
Figure 4-6 Front view of the SGSN shelf
GGSN
The GGSN is a Cisco 7206. Figure 4-7 provides an idealized front view.
PORT ADAPTER PORT ADAPTER
CISCO 7200
SERIES PC CARD SLOTS PORT PORT PORT
Figure 4-7 Front view of GGSN
4–6 15th Sep 99

68P02903W01-O
FIELD TRIAL
GGSN/SGSN hardware
Table 4-1 lists the hardware components for the SGSN and GGSN.
Table 4-1 SGSN/GGSN hardware

Component Hardware
SGSN One MCP750 transmission function
(SGSN-TF) board with a dual E1 PMC
module inserted in the PMC socket.
One MCP750 control function (SGSN-CF)
board with a transition module for
connecting to the hard disk.
GGSN Cisco 7206 (see
http://www.cisco.com/univercd/cc/td/produ
ct/access/acs_serv/as5800/7200dox/7206
gide/index.htm)
The MCP750 processor board supports control and maintenance functions, network
management, fault management, account information recording, system configuration,
and provides coordination between other modules in the GSN.
The MCP750 processor board has the following characteristics:
S 256 MB RAM.
S One 1-Mbyte 16 bit flash memory on board.
S Additional 64 bit 8 Mbyte flash memory.
S Compact Flash memory socket with 48 Mbyte Compact Flash. The Compact Flash
memory board is configured as an EIDE primary master drive.
S One 10/100 BASE-T Ethernet port.
S One asynchronous serial port (console).
S One transition module.
S One 66 MHz dual E1 PMC module (SGSN-TF board only).
GSN peripheral
devices
The GSN supports the following peripheral devices:
Power supply and fan unit

The Power Supply and Fan (PSF) unit is a set of two 450 watt power supplies and three
5.0 inch tube axial fans together in a sheetmetal housing.
Console terminal
The GSN processor boards support an RS-232 serial communication channel, which can
be connected to an console terminal that is used for system configuration, monitoring, or
debugging. The console terminal is located outside of the GSN cabinet.

68P02903W01-O
FIELD TRIAL
GSN system
functions
The GSN provides the following functions:
S Class C (data) MS functionality.
S GSN CommHub firewall screening.
S Domain Name Service (DNS).
S Internal Home Location Register Service (HLRS).
S Point-to-point Connectionless Network Service (CLNS).
S Point-to-point Connection Oriented Network Service (CONS).
S Quality of Service (QoS) management.
S Mobility Management (MM).
S SNMP interface to Operations and Maintenance (O&M) system.
S TCP/IP header compression.
S Time Service (TS).
S V.42 data compression.
An
The metering feature collects the following information at the GGSN for each packet data
protocol (PDP) context:
S Number of uplink Protocol Data Units (PDUs).
S Number of uplink bytes.
S Number of downlink PDUs.
S Number of downlink bytes.
This information describes the amount of traffic a PDP context has generated or
received.
The operator can view the metering data by telnetting to the GGSN, and accessing the
file through a UNIX editor.
Cy
The mode that an MS operates in depends on the services to which the MS is attached.
Class-C mode of operation means that the MS is exclusively attached to GPRS services.
Gg
Firewall screening by the GSN CommHub provides the ability to restrict or deny access
to the GSN components from external networks (for example, the Internet).
Domain name service

Domain Name Service (DNS) is an Internet-and system-wide database that translates
host names into Internet Protocol (IP) addresses, and IP addresses into host names.
DNS allows users to enter text-based addresses when sending messages. Text-based
addresses are easier to remember than number-based IP addresses required by a GSN.
The DNS server also responds to translation requests from servers in other systems.
The ISS is the DNS primary server, and the OMC-G is the DNS secondary server. All
GSN boards are clients of the DNS servers.
4–8 15th Sep 99

68P02903W01-O
FIELD TRIAL
Internal home location register service

The Internal Home Location Register (HLR) is a simple data store that resides in the
SGSN, and contains subscriber data required for GPRS operation.
When an MS attaches to the GPRS network, a Location Update (LU) message is
received from the SGSN, and the internal HLR provides the SGSN with subscriber
information. The internal HLR can hold data for up to 50,000 subscribers.
The operator can view, add, modify, and delete subscriber data by editing the ASCII HLR
data file.
Point-to-point connectionless network service

The Point-to-Point-Connectionless Network Service (PTP-CLNS) provides datagram-type
connectivity, and is intended to support bursty non-interactive applications. With
point-to-point CLNS, one or more single packets are sent from a subscriber to a
destination. Each transmitted packet is independent of all other transmitted packets.
Point-to-point connection oriented network service (CONS)

The Point-To-Point-Connection Oriented Network Service (PTP-CONS) provides a logical
relation between users, in which multiple packets are sent between a single subscriber
and a single destination. This connection may last anywhere from seconds to hours.
PTP-CONS supports interactive and transaction-based applications, and applications
based on Connection Oriented Network Protocol (CONP).
Quality of service management

Quality of Service (QoS) is the collective effect of service performance determining the
degree of user satisfaction. Performance is measured by three criteria: speed, accuracy,
and dependability.
This release of the GSN supports QoS level 4.
Mobility management
Mobility Management (MM) tracks the current location of an MS within a PLMN.
The mobility management functions supported by GPRS are GPRS-Attach and
GPRS-Detach.
GPRS-Attach occurs when an MS indicates to the PLMN that it wants to use the GPRS
PTP service. This can be immediately after the MS has been switched on, or later when
the user decides to use GPRS services. GPRS-Attach is successful only if the subscriber
has a valid GPRS subscription.
GPRS-Detach occurs when the MS indicates to the PLMN that the MS has finished using
the GPRS services.
SNMP interface to operations and maintenance system

The SGSN can be managed from the Operations & Maintenance (O&M) system using
Simple Network Management Protocol (SNMP) protocol, as defined by the Internet
Engineering Task Force (IETF).
TCP/IP header compression

The GSN supports standard (as defined by IETF) Transmission Control Protocol/Internet
Protocol (TCP/IP) header compression between the MS and the SGSN. This reduces
communication overhead on the TCP header by as much as 85%.

68P02903W01-O
FIELD TRIAL
Time service
The Time Service(TS) maintains the real-time clock for the system components in a
GSN.
The ISS is the TS primary server for the GSN. It takes its time from Universal Time
Coordinated (UTC), an ISO timekeeping standard from the station clock or through one
or more sources on the Internet. All other GSN boards synchronize time from this server.
The OMC-G is the TS secondary server. If the ISS is not operational, the OMC-G takes
over primary status, and provides time service for the GSN boards until the ISS service is
restored.
V.42 data compression

Data compression optimizes the use of radio path capacity by transmitting as little of the
Service Data Unit (SDU) as possible, while simultaneously preserving the information
contained within it.
GSN
management
from the OMC-G
The OMC-G enables operators to use an NT Graphical User Interface (GUI) when
managing the following GSN functions:
S Configuration management.
S Fault management.
S Load management.
S Performance management.
The OMC-G also provides security by requiring operators to use different levels of login
IDs and passwords when accessing the GSN. Because authorization for operator actions
occurs on the managing system, there is no requirement to carry access or authorization
information with each request going across the management interface.
4–10 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 SGSN description
SGSN description
SGSN
description
structure
The SGSN description structure is:
S SGSN functions overview.
S SGSN architecture.
S Functional entities and hardware mapping.
SGSN functions
overview
The SGSN provides Gb and Gn communication protocols for MS access to the GPRS
network through the BSS.
S The Gb interface provides mobile subscribers access to the GPRS network
through the Base Station Subsystem (BSS).
S The Gn interface provides access between GGSNs.
The SGSN also provides two E1 interfaces.
The SGSN detects and tracks MSs in its service area, providing a reliable, secure data
channel as the MS moves between cells. The SGSN also mediates access to the
network resources and implements packet scheduling.
Subscription information is stored in a GPRS register (internal HLR) where the mapping
between an identity (such as MS-ISDN or IMSI) of an MS and the PSPDN address is
located. The GPRS register acts as a database from which the SGSNs query whether a
new MS in its area is allowed to join the GPRS network.
Each SGSN interfaces with one or more Base Station Systems (BSS).
SGSN
architecture
Functional entities
The SGSN consists of the following software functional entities (see Figure 4-8):
SGSN-control
Part of the control plane, the SGSN-control, is responsible for handling SGSN signalling,
such as MS attach, and PDP activate.
It contains macroscopic information about the MS, that is VLR.

68P02903W01-O
FIELD TRIAL
SGSN description GPRS-300-101
Transmission function
The SGSN transmission function is made up of two functional entities, the
SGSN-GNPROC and the SGSN-GBPROC.
SGSN-GNPROCis part of the transmission plane and responsible for GTP, relay,
SNDCP, and LLC protocols. It serves as an anchor and point for an MS within an SGSN.
SGSN-GNPROC is responsible for paging of MSs and receiving/forwarding data to/from
the appropriate SGSN-GBPROC. The GNPROC contains microscopic MS context
information; MS MM state, PDP state and cell location.
SGSN-GBPROC is part of the transmission plane responsible for BSSGP protocol. Each
GBPROC is connected to one BSS via a number of E1 links. The GBPROC is
responsible for QoS scheduling and flow control. The functional entity contains cell and
frame relay PVC mapping.
CONTROL FUNCTION
SGSN-CONTROL
SGSN GNPROC GSN

COMMHUB
TRANSMISSION FUNCTION
SGSN GbPROC
FR E1 FR E1
ÇÇÇÇÇÇÇÇÇÇ
BSS
Figure 4-8 SGSN architecture
4–12 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 SGSN description
Functional
entities and
hardware
mapping
The functional entities for the SGSN and GGSN can be mapped to the same processor
board or distributed among processor boards. This allows the configuration of GSN to
adapt to the different needs of networks.
SGSN architecture
The SGSN functional entities are split into functions. The control function and the
transmission function.
Control function
The control function comprises an instance of SGSN-control and SGSN-OAMP. The
control function holds the OAMP function for the CF and the TF.
The SGSN-GBPROC and SGSN-GNPROC are combined together to form the
transmission function on a processor board. The board has two mezzanine interface
boards supporting up to four E1s to allow connection to the BSS (see Figure 4-9).
GGSN SGSN-CF SGSN-TF
OAMP OAMP tf
sgsn-gbproc
GG sgsn-gnproc
E1
I/F
BSC
Figure 4-9 Functional entities and hardware mapping

68P02903W01-O
FIELD TRIAL
GGSN description GPRS-300-101
GGSN description
GGSN functions
The GGSN provides Gi/Gc/Gn communication protocols for signalling and transmission
data.
S The Gi interface provides access between Public Land Mobile Network (PLMN)
subscribers and devices attached to one or more external packet data networks.
S The Gc interface provides communication between a GGSN and a Home Location
Register (HLR).
S The Gn interface uses GPRS Tunnel Protocol (GTP) to provide signalling and data
communication between the SGSN and the GGSN.
The main functions of the GGSN involve interaction with the external data network. The
GGSN directs mobile terminated packets to the SGSN serving the Mobile Station (MS),
allowing the mobile subscriber to move freely within the coverage area of the home
PLMN or a foreign PLMN.
The GGSN also decapsulates and forwards MS packets from mobile to external data
networks, and handles the billing of traffic data.
GGSN
architecture
The Gateway to GPRS Support Node (GGSN) consists of the following software
functional entities (see Figure 4-10):
S Control function.
S Transmission function.
GGSN–control
GGSN-control belongs to the control plane, and is responsible for handling the GGSN
signalling traffic such as create PDP request. GGSN-control contains macroscopic MS
context information, such as the PDP context information.
4–14 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GGSN description
GGSN-GiPROC is part of the transmission plane responsible for the Gi interface. It
forwards data from/to the GGSN-GNPROC.
GGSN-GNPROC is also part of the transmission plane, and is responsible for the GTP
protocol between the GGSN and the SGSN. GGSN-GNPROC is responsible for QoS,
and flow control between the SGSN and GGSN.
GGSN-OAMP belongs to the OAMP plane and is responsible for the GGSN OAMP
function. It interfaces between the OMC-G and the functional entities.
OAMP PLANE
GGSN-OAMP
CONTROL PLANE
GGSN-CONTROL
GGSN GGSN-GNPROC
GNPROC
TRANSMISSION
FUNCTION
GGSN-GIPROC
PDN
Figure 4-10 GGSN architecture

68P02903W01-O
FIELD TRIAL
GGSN description GPRS-300-101
Functional
entities and
hardware
mapping
The functional entities for the SGSN and GGSN can be mapped to the same processor
board or distributed among processor boards. This allows the configuration of GSN to
adapt to the different needs of networks.
SGSN architecture
The SGSN functional entities split into functions. The control function and the
transmission function.
Control function
The control function comprises an instance of SGSN-control and SGSN-OAMP. The
control function holds the OAMP function for the CF and the TF.
The SGSN-GBPROC and SGSN-GNPROC are combined together to form the
Transmission function on a processor board. The board has two mezzanine interface
boards supporting up to four E1s to allow connection to the BSS.
GGSN architecture
For the GGSN the functional entities are combined on to one processor board. So the
GGSN comprises the GGSN-OAMP and the GGSN-CONTROL, GGSN-GiPROC and
GGSN-GNPROC, forming a process called the gg (see Figure 4-11).
GGSN SGSN-CF SGSN TF
OAMP OAMP tf
sgsn-gbproc
GG sgsn-gnproc
E1
I/F
BSC
Figure 4-11 Functional entities and hardware mapping
4–16 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN CommHub description
GSN CommHub description
GSN CommHub
description
structure
The GSN CommHub description structure is:
S GSN CommHub.
S GSN CommHub hardware.
S GSN CommHub modules.
GSN CommHub
The GSN CommHub is the central connection point for the GPRS Service Node (GSN)
components in a General Packet Radio Service (GPRS) system. It is also the connection
point to other GPRS systems, or other networks such as the Internet.
The GSN CommHub uses standard Cisco Supervisor and Internetwork Operating
System (IOS) software which is pre-installed in the Cisco modules.
The GSN CommHub provides the functionality of the GPRS backbone IP router, gateway
IP router and IP firewall. The GSN CommHub is specific to the Motorola implementation
of the GSN, and though its functionality is specified in the ETSI recommendations, the
name is not. The GSN CommHub is an off-the-shelf router. It is the central connection
point for all communication within GSN elements, and between the GSN and outside
network elements.
The GSN CommHub provides the functions of the backbone IP router. This router
provides the indirect data paths, called the Gn interface, between the PLMN intranet
nodes such as the GGSN or SGSN.
The GSN CommHub reduces the number of direct physical channels needed by a GSN
to communicate with its peers, since the backbone IP router performs no GPRS specific
functions, and is used only to route IP datagrams between the SGSN and GGSNs. Each
GSN may have direct physical connections to two IP routers for reliability.
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 GSN CommHub
implements the inter-domain IP routeing protocols, and is used to provide increased
fanout capability between the GGSN and external network gateways. It acts only as an
IP network relay, and performs no GPRS specific functions (that is it is an off-the-shelf IP
router product, which can be supplied by a number of third-party vendors).
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 a 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.

68P02903W01-O
FIELD TRIAL
GSN CommHub description GPRS-300-101
GSN CommHub functions

The GSN CommHub provides:
S Local Area Network (LAN) connectivity between:
– A Serving GPRS Support Node (SGSN) and a Gateway GPRS Support
Node (GGSN).
– An SGSN or GGSN and the Internet Support Server (ISS).
– The Operations and Maintenance Centre-GPRS (OMC-G) and the SGSNs,
GGSNs, and ISS.
S Wide Area Network (WAN) connectivity between the GGSN and external data
networks.
GSN CommHub
hardware
The GSN CommHub hardware consists of a chassis and special purpose modules.
GSN CommHub chassis

The GSN CommHub chassis is a 13-slot Catalyst 5500 LAN switch manufactured by
Cisco Systems, Inc. (see Figure 4-12).
Catalyst 5500
Figure 4-12 Front view of the GSN CommHub chassis
4–18 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN CommHub description
GSN CommHub
modules
The GSN CommHub modules (boards) select the most suitable route between a source
and a destination, and 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 4-13 shows the GSN CommHub modules and how they connect to other system
components.
GSN COMMHUB
BACKPLANE SGSN-CF
SUPERVISOR ENGINE
SGSN-TF
10/100 BASE-T MODULE
GGSN
ROUTER
E1/T1 I/O
SWITCH
MODULE
MODULE OTHER PLMN
GATEWAY
Figure 4-13 GSN CommHub modules and connection

The modules in the GSN CommHub are:
S Router Switch Module (RSM).
S Supervisor Engine (SE) module.
S 10/100 BASE-T switch module.
S T1/E1 serial module (VIP2 module).
Router switch module

An RSM can be configured as either a bridge or a router for Local Area Networks (LANs)
or Wide Area Networks (WANs).
In a LAN, RSM modules connect to local systems, and perform routeing and bridging
between segments within the GSN CommHub chassis and local networks. In a WAN,
RSM modules with VIP2/serial modules connect to remote systems.
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.

68P02903W01-O
FIELD TRIAL
GSN CommHub description GPRS-300-101
Supervisor engine module

The supervisor engine module manages a Catalyst 5500. Both RSM and 10/100BASE-T
modules are controlled through the supervisor engine, which enables the GSN
CommHub to display alarms and statistics for the individual modules.
The supervisor engine and the 10/100 BASE-T fast Ethernet switching modules are used
in association with each other. The supervisor engine manages one or more 10/100
BASE-T switch modules. 10/100 BASE-T boards connect components to Ethernet.
10/100 BASE-T switch module

10/100 BASE-T switch modules connect GPRS components to Ethernet, and provide
intelligence for filtering out Ethernet violations.
4–20 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 ISS description
ISS description
ISS description
structure
The ISS description structure is:
S ISS overview.
S ISS hardware.
S ISS functions.
ISS overview
The ISS is a server that provides GPRS system components with Domain Name Service
(DNS), Network Time Protocol (NTP), and other IP-based support functions for the GSN.
In trial release, the ISS functions are provided on a Sun platform. In GA release, some of
the ISS functions (such as NTP) are to be migrated to a board within the SGSN or
GGSN chassis. There may be multiple ISSs per network, for example at multiple
geographical sites.
The GSNs require accurate time information for generating accounting records and logs.
The Network Time Protocol (NTP) is used to synchronize the time of a computer client or
server to another server or reference time source, such as a radio or satellite receiver or
modem. It provides client accuracies typically within a millisecond on LANs and up to a
few tens of milliseconds on WANs, relative to a primary server synchronized to
Co-ordinate Universal Time (UTC) via a Global Positioning Service (GPS) receiver, for
example. Typical NTP configurations utilize multiple redundant servers and diverse
network paths, in order to achieve high accuracy and reliability.
ISS hardware
The GSN ISScomprises a pair of Sun Netra t 1125 modules connected to a pair of Sun
Netra st D1000 storage modules, the High Availability Disk Array (HADA). The GSN ISS
communicates with the GGSN and SGSN through the GSN CommHub and is connected
to the GSN CommHub through a 10/100 BASE-T LAN (see Figure 4-14).
Hard disk
A Sun Netra st D1000 High Availability Disk Array (HADA) is collocated in the GSN
communications cabinet with the ISS; see Figure 4-5.
NETRA t
ÉÉ
1125
ÉÉ SUN
Figure 4-14 ISS hardware platform

68P02903W01-O
FIELD TRIAL
ISS description GPRS-300-101
ISS functions
The ISS provides the following functions:
Time service
The ISS maintains the real-time clock for the GSN.
The ISS is the Time Service (TS) primary server for the GSN. It takes its time from
Universal Time Coordinated (UTC), an ISO timekeeping standard from the station clock
or through one or more sources on the Internet. All other GSN boards synchronize time
from this server.
The OMC-G is the TS secondary server. If the ISS is down, the OMC-G takes over
primary status, and provides time service for the GSN boards until the ISS service is
restored.
Domain name service

The Domain Name Service (DNS) is an Internet, and system-wide, database that
translates host names into IP addresses, and IP addresses into host names.
DNS allows users to enter text-based addresses when sending messages. Text-based
addresses are easier to remember than number-based IP addresses required by a GSN.
The DNS server also responds to translation requests from servers in other systems.
The ISS is the DNS primary server, and the OMC-G is the DNS secondary server. All
GSN boards are clients of the DNS servers.
The ISS provides translation between Internet Protocol (IP) addresses and host names
of system components.
4–22 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Network topology
Network topology
Network
topology
structure
The network topology structure is:
S Speech transcoder functions.
S BSS serial data transmission links.
S Coded transmission.
Speech
transcoder
functions
The XCDR or RXCDR converts data between two different transmissions systems to
permit communication between the MS and the MSC.
Transmission and coding systems

Table 4-2 compares the two different coding and transmission systems.
Table 4-2 Comparison of coding and transmission systems

Land network Cellular system air interface
Uses 64 kbit/s PCM Uses 16 kbit/s GSM coded channels for routeing traffic
channels for routeing data between the BSS and MSs.
signalling and traffic data The 13 kbit/s de-interleaved vocoder traffic data from the
between the MSC and Air Interface is combined with 3 kbit/s of remote control
BSS. protocol to make one 16 kbit/s GSM coded channel
(timeslot).
TheRemote transCoDeR (RXCDR, where X is trans) converts between the 64 kbit/s

PCM data format and the 13 kbit/s RXCDR data format, allowing MSC to MS
communication. The following figures show how the XCDR function fits into the call
process.

68P02903W01-O
FIELD TRIAL
Network topology GPRS-300-101
Transcoding at the BSC

The BTS multiplexes four 16 kbit/s speech channels into a single 64 kbit/s channel
(timeslot) on the BTS-to-BSC interface.The 16 kbit/s rate is adapted from the 13 kbit/s
vocoder channel (actually 22.8 kbit/s after interleaving) used on the Air Interface.
In the uplink direction (from BSS-to-MS), the transcoder at the BSC:
S Demultiplexes each 64 kbit/s channel (timeslot) on the BTS-to-BSC interface into
four 16 kbit/s speech channels.
S Converts each of the four 16 kbit/s speech channels into a 64 kbit/s PCM channel
(timeslot) on the BSC-to-MSC interface.
In the downlink direction (from MS-to-BSS), the transcoder performs the above actions in
reverse order.
Figure 4-15 shows the BSS with transcoding at the BSC:
E1/T1 LINE:
ONE TRAFFIC CHANNEL
PER ONE 64 kbit/s UPLINK (Rx)
TIMESLOT FOR A TOTAL
OF 30/22PCM DOWNLINK (Tx)
TRAFFICCHANNELS
E1/T1 LINE:
BSC TRANSCODES EACH FOUR 16 kbit/s GSM
64 kbit/s PCM CHANNEL TRAFFIC/SIGNALLING CHANNEL PER
TO A 16 kbit/s GSM ONE 64 kbit/s TIMESLOT FOR A TOTAL
CODED OF 120 GSM CODED
TRAFFIC/SIGNALLING TRAFFIC/SIGNALLING CHANNELS
CHANNEL
AIR INTERFACE:
ONE OF EIGHT 22.8 kbit/s
CHANNELS ON AN RF
CHANNEL
BSC
MSC BTS
(STANDALONE)
(STANDALONE)
WITH XCDRs
MS
BSS (FUNCTION)
Figure 4-15 BSS with transcoding at the BSC
4–24 15th Sep 99

68P02903W01-O
FIELD TRIAL
Remote transcoding
The BTS multiplexes four 16 kbit/s speech channels into a single 64 kbit/s channel
(timeslot) on the BTS-to-BSC interface.The 16 kbit/s rate is adapted from the 13 kbit/s
vocoder channel used on the Air Interface.
The BSC routes each 16 kbit/s speech channel within the 64 kbit/s timeslot to the correct
64 kbit/s timeslot for transmission to the Remote transCoDeR (RXCDR, where X is
trans).
In the uplink direction (from BSS-to-MS), the transcoder at the MSC:
S Demultiplexes each 64 kbit/s channel (timeslot) on the BSC-to-RXCDR interface.
S Converts each of the four 16 kbit/s speech channels into a 64 kbit/s PCM channel
(timeslot) on the RXCDR-to-MSC interface.
In the downlink direction (from MS-to-BSS), the RXCDR performs the above actions in
reverse order.
Figure 4-16 shows the BSS with remote transcoding.The RXCDR site is normally located
close to, or at, the MSC.
E1/T1 LINE:
REMOTE TRANSCODER (RXCDR)
ONE TRAFFIC CHANNEL CABINET TRANSCODES EACH
PER ONE 64 kbit/s UPLINK (Rx)
64 kbit/s PCM CHANNEL TO A
TIMESLOT FOR A TOTAL 16 kbit/s GSM TRAFFIC/SIGNALLING DOWNLINK (Tx)
OF 30/22 PCM CHANNEL.
TRAFFICCHANNELS
E1/T1 LINE:
FOUR 16 kbit/s GSM
TRAFFIC/SIGNALLING CHANNEL PER
ONE 64 kbit/s TIMESLOT FOR A TOTAL
OF 120 GSM CODED AIRINTERFACE:
TRAFFIC/SIGNALLING CHANNELS ONE OF EIGHT 22.8 kbit/s
CHANNELS ON AN RF
CHANNEL
MSC RXCDR BSC BTS

(STANDALONE) (STANDALONE)
MS
BSS (FUNCTION)
OPTIONALLY PHYSICALLY COLLOCATED
Figure 4-16 BSS with remote transcoding

68P02903W01-O
FIELD TRIAL
CCDSP control information

The 3 kbit/s remote transcoder control protocol in the Air Interface contains information
that the RXCDR digital signal processors (DSPs) and Channel Code Digital Signal
Processors (CCDSPs) require.
The CCDSP is part of each Transceiver Control Unit (TCU) located in the BTS.The
CCDSP control information is sent directly between the CCDSPs and XCDR DSPs.
The 3 kbit/s contain different information on the uplink (Rx) and downlink (Tx) direction.
In the uplink, the 3 kbit/s of control contains the following information required by the
XCDR:
S Used/ordered frame type (speech or data).
S Used/ordered channel type (full or half-rate).
S Coded speech or user data.
S Discontinuous Transmission (DTx) information.
S Intermediate 8 kbit/s or 16 kbit/s rate adaption (half-rate).
S Transparent and non-transparent bearer service notification.
S Framing and ordered time alignment information to synchronize the transcoder
with the channel codec.
In the downlink, the 3 kbit/s of control data contains the following information generated
by the RXCDR:
S Used/ordered frame type (speech or data).
S Used/ordered channel type (full or half-rate).
S Coded speech or data.
S Discontinuous transmission (DTx) information.
S Intermediate 8 kbit/s or 16 kbit/s rate adaption (half-rate).
S Transparent and non-transparent bearer service notification.
S Framing information.
S Used time alignment.
BSS serial data

transmission
links
The BSS provides digital signal interfaces and transmission links to the land circuits
linking the BSS and the MSC.
E1/T1 links
The digital signal interface circuits that run between the BSS network components and
the MSC are E1/T1 links.
Each E1/T1 link is a four-wire circuit that provides two-way communications.
S One pair of wires for the uplink (Rx) direction.
S One pair of wires for the downlink (Tx) direction.
Each wire pair carries a time division multiplexed E1/T1 serial data stream.
The BSS multiplexes signalling or traffic data from the MS on the uplink data streams for
routeing to the MSC.The MSC multiplexes mobile-terminated subscriber signalling and
traffic data on the downlink data stream for routeing through the BSS to the MSs.
4–26 15th Sep 99

68P02903W01-O
FIELD TRIAL
Transmission systems
E1/T1 links use the following:
S ITU-TSS primary digital multiplex system with 64 kbit/s PCM channels up to the
transcoder.
S 16 kbit/s GSM coded channels from the transcoder.
Primarymultiplex system
This is used on the A Interface, which is the standardized interface between the BSS and
the MSC.
The control portion of the A interface is specified by the BSS Application Part (BSSAP) of
the ITU-TSS Signalling System 7 (C7) protocols.
C7 signalling
The C7 signalling information is sent at 64 kbit/s, and provides:
S Flow control.
S Error detection and correction.
S Ordered transmission.
S Link management.
S Link error monitoring.
Channels
The digital multiplexed signal carries 32 (E1) or 24 (T1) channels (timeslots):
S E1
– 30 voice frequency circuits of digitized PCM data.
– One channel for timing data (CH0).
– One channel for signalling data (normally CH16).
S T1
– 24 voice frequency circuits of digitized PCM data.
The 32/24 channels are time division multiplexed onto a single transmission line (wire
pair) with a data rate of E1/T1.
PCM channel format primary multiplex signal

PCM channel format for the E1/T1 primary multiplexed signal, where the 32/24 channels
equal one frame, is shown in Figure 4-17.
1 FRAME
32/24 CHANNELS
CH0 CH1 CH2 CH15 CH16 CH17 CH18 CH31/23

SYNC SIG
INFORMATION SIGNALLING
FOR FRAME TIMING INFORMATION
(E1 only) (E1 only)
Figure 4-17 PCM channel format for the E1/T1 primary multiplexed signal

68P02903W01-O
FIELD TRIAL
A interface frame channel structure

Table 4-3 provides the channel structure of the frame.
Table 4-3 Channel structure of A interface frame

Channel number(s) Channel function
Ch0 (E1 only) Synchronization information for frame timing
Ch1 - Ch15 Traffic channels
Ch16 (E1 only) Signalling channel, containing all signalling information for the
30/24 traffic channels
Ch17 - Ch31 (E1) Traffic channels
Ch17 - Ch23 (T1) Traffic channels
The 32/24 channel frames occur at the world wide standard of 8000 samples per second.
This sample rate is double the highest supported speech frequency of 4 kHz. Each
channel consists of an eight-bit word.
4–28 15th Sep 99

68P02903W01-O
FIELD TRIAL
Coded
transmission
In the coded transmission system, the transcoder:
S Compresses each 64 kbit/s PCM data channel.
S Encodes channel data into a GSM defined format.
S Subrate multiplexes the compressed channels.
64 kbit/s compression
The transcoder compresses each 64 kbit/s channel into a 16 kbit/s channel.
Coding
The scheme used is Linear Predictive Coding (LPC).
Subrate multiplexing
After the 64 kbit/s channels are compressed into 16 kbit/s channels, subrate multiplexing
enables a single E1/T1 link to carry four times the number of traffic channels provided by
the PCM.
After transcoding, each frame contains:
S E1
– One 64 kbit/s synchronization (timing) channel.
– One 64 kbit/s control (signalling) channel.
– 120 x 16 kbit/s traffic channels (that is, 4 x 30 x 16 kbit/s traffic channels).
S T1
– 96 x 16 kbit/s traffic channels (that is, 4 x 24 x 16 kbit/s traffic channels).
Subrate multiplexed links

Table 4-4 shows the BSS E1/T1 links that use subrate multiplexing.
Table 4-4 Subrate multiplexed links

If transcoding is performed at... Then subrate multiplexing is used on...79.7
The BSC The BSC to BTS E1/T1 link.
The RXCDR The RXCDR to BSC E1/T1 link.
The BSC to BTS E1/T1 link.

68P02903W01-O
FIELD TRIAL
Channel format subrate multiplexed signal

Figure 4-18 shows the channel format of the subrate multiplexed E1/T1 link.
1 FRAME
32/24 CHANNELS
CH0 CH1 CH2 CH15 CH16 CH17 CH18 CH31/23

PRIMARY
16 kbit/s
16 kbit/s
16 kbit/s
16 kbit/s
SUBCHANNELS
CH0 CH1 CH2 CH3

SUBRATE
Figure 4-18 Channel format of subrate multiplexed E1/T1 link
NOTE
The coded channels are not PCM. Also, there is no dedicated signalling
channel like timeslot 16 in the standard ITU-TSS system.
4–30 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN standardized interfaces
GSN standardized interfaces
GSN
standardized
interfaces
structure
The GSN standardized interfaces structure is:
S Standardized interfaces.
S SGSN interfaces.
S GSN CommHub interfaces.
Standardized
interfaces
This section describes interfaces from the following sources/destinations:
S SGSN.
S GSN CommHub.
Figure 4-19 and Figure 4-20 summarize what is described in the following sections.
PACKET DATA
NETWORK
SMS
HLR
Gi
Gr, Gd Gr, Gd
GSN Gn
GSN BILLING SYSTEM
REMOTE COMPLEX
Gb Gb
GPRS GPRS
BSS BSS
Um Um
MOBILE MOBILE
STATION STATION
Figure 4-19 Complex and remote GSN functional blocks

68P02903W01-O
FIELD TRIAL
GSN standardized interfaces GPRS-300-101
PACKET DATA GGSN

NETWORK
REMOTE SGSG
Gi OMC-G
GSN COMMHUB
GSN COMMHUB
CHARGING
GATEWAY
SMS-C
SGSN
HLR SGSN IP SUPPORT
SERVER
Gr
TRANSCODER
Gb TRANSCODER Gb
BSC BSC
Figure 4-20 Complex and remote GSN network elements
SGSN interface
The five SGSN interfaces are described in this section.
SGSN-BSS (Gb) interface

The Gb interface connects the BSS to the SGSN, allowing the exchange of signalling
information and user data. The Gb interface allows many users to be multiplexed over
the same physical resource. Resources are given to a user upon activity (when data is
sent or received) and are re-allocated immediately thereafter. This is in contrast to the A
interface, where a single user has the sole use of a dedicated physical resource
throughout the lifetime of a call, irrespective of activity.
GPRS signalling and user data are sent in the same transmission plane. No dedicated
physical resources are required to be allocated for signalling purposes. Access rates per
user may vary without restriction from zero data to the maximum possible line rate (such
as 2048 kbit/s for an E1 trunk). Note that the use of T1 trunks is not currently supported.
The Gb interface link layer is based on frame relay. Frame relay virtual circuits are
established between SGSN and BSS. LLC PDUs from many users are multiplexed on
these virtual circuits. The virtual circuits may be multi-hop, and traverse a network of
frame relay switching nodes. Frame relay is used for signalling and data transmission.
4–32 15th Sep 99

68P02903W01-O
FIELD TRIAL
Frame relay characteristics

The following characteristics apply for the frame relay connection:
The maximum frame relay information field size is 1600 octet.
The frame relay address length is 2 octets, providing up to 1024 Data Link Connection
Identifiers (DLCIs). However, only DLCIs in the range 1-318 are considered valid.
The BSS and the SGSN both implement frame relay DTE functionality. The SGSN may
optionally also implement DCE functionality. (This is required in order to support the BSS
and SGSN to be interconnected via a simple E1 trunk, in which case the BSS functions
as the DTE, and the SGSN as the DCE, or a frame relay network, in which case both the
BSS and the SGSN may function as DTEs.)
Frame relay PVCs must be used.
No encapsulation on top of frame relay must be used.
One or more frame relay PVCs are used between one SGSN and one BSS to transport
BSSGP packets.
A frame relay network interface is usually required on the SGSN to support the Gb
interface to the BSS. In some configurations, the PCU may be collocated with the SGSN,
or the SGSN and PCUs may be interconnected using nailed-up physical circuits. In these
configurations no Frame relay network is needed.
A frame relay SGSN-to-BSC connection is a Virtual Circuit (VC), which is termed a Data
Link Connection (DLC). In GPRS, all DLCs are currently Permanent Virtual Circuits
(PVCs); PVCs are pre-defined by both sides of the connection (SGSN and BSC).
Each DLC has an identifying number called a Data Link Connection Identifier (DLCI). A
DLCI has local significance only, that is the DLCI is different at the SGSN and BSC ends.
Therefore, the network administrator needs to know both the SGSN and BSC DLCIs for
each DLC being provisioned across a frame relay network. The routeing tables in each
intervening frame relay switch take care of routeing the frames to the proper destination,
alternately reading and assigning DLCI values in the control portion of the frames, as
appropriate.
BSSGP (Base Station Subsystem GPRS Protocol) is implemented in the SGSN as a
user-level application which uses the services of the frame relay protocol to communicate
with BSS.
SGSN-BSS BSS GPRS protocol

The primary function of BSS GPRS protocol (BSSGP) is to provide the radio-related,
QoS, and routing information that is required to transmit user data between a BSS and a
SGSN. In the BSS, it acts as an interface between LLC frames and RLC/MAC blocks. In
the SGSN, it forms an interface between RLC/MAC-derived information and LLC frames.
A secondary function is to enable two physically distinct nodes, the SGSN and BSS, to
operate node management control functions.
There is a one-to-one relationship between the BSSGP protocol in the SGSN and in the
BSS. If one SGSN handles multiple BSSs, the SGSN has to have one BSSGP protocol
machine for each BSS.

68P02903W01-O
FIELD TRIAL
BSSGP functions
The main functions for the BSSGP protocol are to:
Provide a connectionless link between the SGSN and the BSS.
Transfer data unconfirmed between the SGSN and the BSS.
Provide tools for bi-directional control of the flow of data between the SGSN and the
BSS.
Handle paging requests from SGSN to BSS.
Give support for flushing of old messages in the BSS, such as when a MS changes BSS.
Support multiple-layer 2 links between the SGSN and one BSS.
For packet transfer from SGSN to BSS, the BSSGP is using a three-split address-cell
identity, QoS, and the MS identification, such as TLLI, and IMSI. These three address
parts are used to dynamically create queues and contexts in both SGSN and BSS. The
flow control mechanism is based on these queues and contexts. For packet transfer from
the BSS to the SGSN only, the QoS and MS identity are used for addressing of queues
in the SGSN.
A cell context in the BSS consists of one queue for LLC packets per cell and per QoS
priority level. Signalling uses its own queue context and has the highest priority. The cell
context in BSS is allocated for each cell supporting GPRS. For each new GPRS cell
introduced in the BSS area, a new cell context is allocated. The cell contexts may then
be released either after a certain time: when the context has not been active, or when the
cell parameters are modified. This is an implementation issue. In the SGSN, the cell
context consists of the queue status for each QoS priority queue. QoS priority queues
are dynamically allocated and de-allocated (the procedures to accomplish this are
implementation dependent).
Flow control for uplink traffic from BSS to SGSN is managed by BSSGP for each link and
QoS priority level. When the queues in the SGSN reach their thresholds, the SGSN uses
the flow control messages to notify BSS that only BSSGP messages above a certain
QoS priority level can be accepted. When the highest QoS priority level is indicated in the
flow control message, all data traffic for that Gb link is interrupted. When SGSN
congestion recedes below the given threshold, the SGSN notifies the BSS about this.
Signalling has its own queue with the highest priority level.
4–34 15th Sep 99

68P02903W01-O
FIELD TRIAL
SGSN-HLR (Gr) interface

In the trial release of the SGSN, the Gr interface is replaced by an internal database
lookup. Information typically stored in an HLR will be instead stored locally within a
GPRS register in the SGSN. This is necessary, since it is unlikely that the necessary
HLR upgrades will be in place for initial GPRS trials.
The internal Home Location Register (HLR) within the SGSN contains the IMSI of each
GPRS subscriber along with the GPRS specific subscription information, such as the
subscriber IP address and GGSN address.
The Gr interface will be supported in the GA release of the SGSN product. In the trial
release, the GPRS subscriber records are instead stored within an internal HLR of the
SGSN. This allows the GPRS service to be deployed without the need to update the
HLRs at the same time. As the HLR equipment is upgraded to support the GPRS
subscriber records, the Gr interface can be deployed on the SGSNs with a future
software release.
The Gr and Gc interfaces use the common C7 physical links which terminate at a remote
Signaling Transfer Point (STP). This provides access to all nodes in the C7 network,
including the HLRs of both the local and foreign PLMNs.
In order to determine the C7 point code of the HLR, an Signalling Connection Control
Part (6-8) (SCCP) Global Title Translation (GTT) must be performed on the IMSI. This
function may be performed in either the SGSN, the STP, or both (in the case of partial
GTT). When performed within the SGSN, the GTT tables are configured via O&M
functions with the appropriate translations.
The MAP and C7 software is to be acquired from a third-party software vendor. Some
changes may be required to MAP message formats to accommodate GPRS functions.
MAP is specified in 09.02.
SGSN-SMS (Gd) interface

This interface is not supported in trial release of the SGSN, but will be provided in a
future release.
The Gd interface uses the common C7 physical links, which terminate at a remote
Signaling Transfer Point (STP). This provides access to all nodes in the C7 network,
including the SMS-Service Centres (SMS-SC) of both the local and foreign PLMNs.
The SMS-SC forwards short messages to the SGSN upon receiving an SGSN address
from the HLR. The actual ability of the GSN to deliver the messages is determined by the
number of 64 kbit/s links between the GSN and SMS-SC. The messages are carried as
normal packets though the SGSN, and are considered as part of the actual load on a the
network.
SGSN-OMC-G interface
This interface is by 100 BaseT Ethernet connection. The interface is used to support the
provision of load management, configuration management, fault management and
performance management of the SGSN.
Configuration management of the SGSN can be performed by SNMP protocol and MMI
commands at the SGSN.
For GA, all information at the SGSN can be configured by SNMP managed objects.

68P02903W01-O
FIELD TRIAL
GSN CommHub
interfaces
The five GSN CommHub interfaces are described in this section.
GSN CommHub-packet data network (Gi) interfaces

The software protocols and physical connection that are needed to connect the GSN
(GGSN) to an external packet data network are defined by the Gi interface standard. In
the implementation shown in Figure 4-21, the Gi interface is divided into two
components, the Gi-e, which lies on the external network side of the gateway IP router,
and the Gi-i, which is the internal Gi interface between the GGSN and the gateway.
IP
HOST IP
IP IP HOST
HOST HOST IP IP IP
HOST HOST
EXTERNAL IP HOST
NETWORK
EXTERNAL IP EXTERNAL IP
NETWORK NETWORK
EXTERNAL EXTERNAL
GATEWAY IP GATEWAY IP
ROUTER ROUTER
Gi-e Gi-e
GATEWAY IP GATEWAY IP
ROUTER ROUTER
Gi-i Gi-i
GATEWAY GATEWAY
GSN GSN
Gn-g Gn-g
BACKBONE
IP ROUTER
Figure 4-21 Architecture of a GPRS Network
GSN CommHub-packet data network (external) (Gi-e) interface

The external Gi interface (Gi-e) is provided by the gateway IP router, which is a
third-party IP router product. The number of physical communication ports required on
the IP router depends upon the number of different external network connections
required and the capacity requirements of each external interface connection. Standard
IP router products support all common interface protocols and media, including frame
relay over E1.
4–36 15th Sep 99

68P02903W01-O
FIELD TRIAL
GSN CommHub-packet data network (internal) (Gi-i) interface

One or more physical IP ports on the GGSN may be associated with the internal Gi
interface (Gi-i). The GPRS specifications define two interface protocols to external data
networks and users, IP, and X.25. In GA, only the IPv4 is supported on the Gi interface.
The GGSN is configured as multiple logical IP hosts, where it has multiple unique IP
addresses that each have the same <Network-number> part (and the same
<Sublet-number> part); these IP interfaces are known as logical hosts, and 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 following points outline the GGSN Gi-i addressing scheme:
S The Gi-i interface functions are implemented on one or more processor boards.
S Each Gi-i processor board is associated with a single, unique IP address.
S Each Gi-i processor board has a single 100BaseT physical interface configured as
an IP port. This IP port has a direct physical connection to the gateway IP router
(that is both are on the same LAN segment).
S Each Gi-i interface processor board acts as the primary IP route for a
preconfigured subset of the MS IP address population.
S Each Gi-i interface processor board may also be configured as a backup route
(higher cost) to a different subset of MS IP addresses, such that there is always a
primary and a backup Gi-i I/F for any individual MS IP address.
S For MS terminated packets, the gateway IP router selects the appropriate GGSN
IP port based upon the destination IP address of the packet (such as using the
least cost route).
S For MS originated packets, the gateway IP router is always used as the default
route to external network addresses by each Gi-i interface processor board.
S A standard IP routeing protocol, such as OSPF, is used between the IP ports on
the Gi-i interface processors and the gateway IP router. Alternatively, static IP
routeing tables may be configured in both the gateway IP router and the Gi-i
interface processor boards.

68P02903W01-O
FIELD TRIAL
SGSN-GSN CommHub-GGSN (Gn) interface

The software protocols and physical connection that are needed to connect the GGSN to
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 and TCP/IP stacks. GTP defines both signalling (control) and data
transfer functions between two GSNs. GTP is specified in GSM 09.60.
In this document, the Gn interface is divided into two parts, the Gi-g which represents the
GGSN side of the Gn interface, and the Gi-s which represents the SGSN side of the Gn
interface (see Figure 4-22).
GATEWAY GATEWAY
GSN GSN
Gn-g
BACKBONE
IP ROUTERS
Gn-s
SERVING SERVING
GSN GSN
Figure 4-22 Gn-s, Gn-g interfaces
GSN configuration options

The three GSN configuration options for the physical channels associated with the Gn
interface are as follows:
S The LAN option uses an Ethernet port connected to 100BaseT Ethernet. An IP
router is also connected to the same LAN, in order to allow the SGSN to
communicate with remote GSNs over a Wide Area Network (WAN). One or more
GGSNs or SGSNs may also be attached to the same LAN segment, allowing
direct communication between peer GSNs across the LAN.
S The FR point-to-point option uses an E1 physical port to establish a fixed link over
a PSTN leased E1 line. The frame relay protocol is used to transfer IP packets
across the E1 physical link to a remote IP router or a remote GSN.
S The FR network option uses an E1 physical port to access a frame relay network.
Permanent Virtual Circuits (PVC) are established across the frame relay network
to communicate with a remote IP router, or with one or more remote GSNs.
4–38 15th Sep 99

68P02903W01-O
FIELD TRIAL
Multiple logical IP hosts

The GSN Gn interface is configured as multiple logical IP hosts. A GSN may have
multiple unique IP addresses that each have the same <Network-number> part (and the
same <Subnet-number> part); these IP interfaces are known as logical hosts and 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.
A GGSN or SGSN is configured as multiple logical IP hosts. The GSN has multiple
unique IP addresses, which use separate Gn physical interfaces.
The GTP packets are addressed to the individual Gn I/F processor which handles them.
The following points outline the Gn addressing scheme:
S The Gn interface functions are implemented on one or more processor boards.
S Each Gn processor board is associated with a single, unique IP address.
S Each Gn processor board may be viewed as a separate logical GSN, from the
point of view of the peer GSNs.
S When an SGSN sends a GTP packet to the GGSN, it is routed to a specific IP
address and Gn processor board. This GGSN processor board is considered to be
the anchor for the tunnel to the SGSN. The SGSN IP address may change as the
MS moves within the PLMN, but the GGSN IP address is constant for the duration
of the tunnel.
SGSN-GSN CommHub-foreign GGSN (Gp) interface

The Gp interface is equivalent to the Gn interface, and is present on both the SGSN and
GGSN. The Gn GTP tunnels are associated with a local GSN, whereas the Gp GTP
tunnels are associated with a foreign GSN (the GSN IP address is in a different domain).
Since GTP packets travel outside of the PLMN intranet, the SGSNs and GGSNs must
have access to a gateway IP router. For security reasons, the gateway IP router should
have a dedicated path to each authorized foreign PLMN, such that GTP packets do not
travel over a public IP network (such as the internet). The gateway IP router may be
configured with a firewall function, to allow packets only from authorized IP domains
(foreign PLMNs) and to the GTP UDP/TCP port numbers.

68P02903W01-O
FIELD TRIAL
4–40 15th Sep 99

68P02903W01-O
FIELD TRIAL
Chapter 5
GPRS functional description

68P02903W01-O
FIELD TRIAL
GPRS-300-101
ii 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101
Chapter 5
GPRS functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
Overview of GPRS functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
Channel groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Radio channel groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
PCCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
PBCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
PTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
Multiframe structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Mapping packet data logical channels onto physical channels . . . . . . . . . . . . . . . 5–4
Allocation of resources to GRPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
Burst structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Burst overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Timing advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7
Medium access control and radio link control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9
Channel coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–11
Channel coding overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–11
Channel coding schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–11
Coding scheme 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
Coding scheme 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–13
Coding scheme 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Coding scheme 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15
Mobility management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Mobility management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Definition of mobility management states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
IDLE (GPRS) state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
STANDBY state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–17
READY state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–17
IDLE/STANDBY/ READY state functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–18
STANDBY timer function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
READY timer function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Periodic RA update timer function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–21
Mobile reachable timer function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–21
Session management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–22
Session management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–22
Definition of packet data protocol states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–22
PDP context activation, modification, and de-activation functions . . . . . . . . . . . . 5–24
PDP context activation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–25
Network-requested PDP context activation procedures . . . . . . . . . . . . . . . . . . . . . 5–27
Successful network-requested PDP context activation procedure . . . . . . . . . . . . 5–28
Unsuccessful network-requested PDP context activation procedure . . . . . . . . . . 5–29
Anonymous access PDP context activation procedure . . . . . . . . . . . . . . . . . . . . . 5–32
Modification procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–34
PDP context modification procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–34
PDP context de-activation initiated by MS procedure . . . . . . . . . . . . . . . . . . . . . . . 5–35
PDP context de-activation initiated by GGSN procedure . . . . . . . . . . . . . . . . . . . . 5–36
Anonymous access PDP context de-activation initiated by MS procedure . . . . . 5–37
Anonymous access PDP context de-activation initiated by GGSN procedure . . 5–38
Packet routeing and transfer function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–39
Relay function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–39
Packet terminal adaptation function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Encapsulation function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40

68P02903W01-O
FIELD TRIAL
GPRS-300-101
iv 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 Overview
Overview
Overview of
GPRS functions
This chapter provides an outline of the following GPRS functions:
S Channel groups.
S Multiframe structure.
S Burst structure.
S Channel coding.
S Mobility management.
S Session management.

68P02903W01-O
FIELD TRIAL
Channel groups GPRS-300-101
Channel groups
Radio channel
groups
There are three basic groups of radio channels for GPRS:
S Packet Common Control CHannel (PCCCH).
S Packet Broadcast Control CHannel (PBCCH).
S Packet Traffic CHannel (PTCH).
PCCCH
PCCCH is a set of logical channels used for common signalling. These channels are
described below.
Packet random access channel

The Packet Random Access CHannel (PRACH) is used by Mobile Stations (MSs) to
initiate uplink transfer, for example for sending data or as a response to a paging
message.
The access burst is used to obtain timing advance information.
The PRACH is found only on the uplink.
Packet paging channel

The Packet Paging CHannel (PPCH) is used to page an MS before downlink packet
transfer. PPCH uses paging groups in order to allow for discontinuous reception.
The PPCH can be used for paging mobiles in both circuit-switched and packet-switched
modes, but this is applicable only for class A and class B GPRS MSs.
An MS that is currently engaged in packet transfer can be paged for circuit-switched
services on a Packet Access Control CHannel (PACCH).
The PPCH is found only on the downlink.
Packet access grant channel

The Packet Access Grant CHannel (PAGCH) is used in the packet transfer
establishment phase to send resource assignment messages to an MS before packet
transfer.
Additional resource assignment messages can be sent on a PAGCH if the MS is
currently involved in packet transfer.
The PAGCH is found only on the downlink.
Packet notification channel

The Packet Notification CHannel (PNCH) is used to send a Point-To-Multipoint-Multicast
(PTM-M) notification to a group of MSs before PTM-M packet transfer.
The notification has the form of a resource assignment for packet transfer.
The PNCH is found only on the downlink.
5–2 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Channel groups
PBCCH
Packet Broadcast Control CHannel (PBCCH) is not allocated.
This system can be broadcast on the Broadcast Control CHannel (BCCH).
The PBCCH is found only on the downlink.
PTCH
Packet Traffic CHannel (PTCH) comprises the following channels:
S Packet Data Traffic CHannel (PDTCH).
S Packet Associated Control CHannel (PACCH).
Packet data traffic channel

The Packet Data Traffic CHannel (PDTCH) is allocated for data transfer.
PDTCH is temporarily dedicated to one MS or a group of MSs in the PTM-M case.
In multislot operation, one MS may use multiple PDTCHs in parallel for individual packet
transfer.
The PDTCH is found on both the uplink and downlink.
Packet associated control channel

The Packet Associated Control CHannel (PACCH) conveys signalling information related
to a given MS. Such information includes acknowledgments, power control information,
and resource assignments.
One PACCH is associated with one or several PDTCHs that are concurrently assigned to
one MS.
The PACCH is found on both the uplink and downlink.

68P02903W01-O
FIELD TRIAL
Multiframe structure GPRS-300-101
Multiframe structure
Mapping packet
data logical
channels onto
physical
channels
A Packet Data CHannel (PDCH) is a physical timeslot that has been allocated for use by
the GPRS. This allocation may be permanent or temporary in nature, such that dynamic
reconfiguration between GPRS and GSM can take place. The sharing of the physical
channel by different packet data logical channels is based upon blocks of four
consecutive bursts. The Packet Random Access CHannel (PRACH), however, uses
access bursts, and the Packet Associated Control CHannel (PACCH) is able to utilize
four consecutive bursts under some message conditions.
The Packet Common Control CHannel (PCCCH) does not have to be allocated
permanently in a cell. When the PCCCH is not allocated, the Common Control CHannel
(CCCH) is used to initiate a packet transfer. The mapping of the PCCCH, when it does
not exist, onto the physical channels must follow one of the following rules:
S PCCCH is mapped onto one or several physical channels according to the
51-multiframe. In this case, PCCCH occupies the whole of the physical channel
along with the Packet Broadcast Control CHannel (PBCCH).
S PCCCH is mapped on to one or several physical channels according to the
52-multiframe. In this case, the PCCCH, PBCCH, and Packet Data Traffic
CHannel (PDTCH) all share the same physical channel, PDCH.
PCCCH on the 51-multiframe

The existence and location of the PCCCH is broadcast on the cell. The mapping of the
PRACH, the Packet Paging Channel (PPCH), and the Packet Access Grant CHannel
(PAGCH) follow similar rules to those for the Random Access CHannel (RACH), the
Paging CHannel (PCH), and the Access Grant CHannel (AGCH) on each of the physical
channels on which the PCCCH is mapped.
PCCCH on the 52-multiframe

Figure 5-1 shows the structure of the 52-frame multiframe. In this case, control channels
and traffic channels may be combined onto a single physical channel in a variety of fixed
and dynamic allocation schemes.
IDLE FRAMES
0 1 2 3 4 5...... .........51
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
RADIO BLOCKS
Figure 5-1 GPRS 52-frame multiframe
5–4 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Multiframe structure
Allocation of
resources to
GRPS
A cell that is supporting the GPRS may allocate resources on one or more physical
channels. These physical channels (PDCHs) are taken from a common pool of channels
available within a cell, and as such reduce the number of circuit-switched channels
available. The actual allocation of physical channels to either circuit-switched or GPRS is
done dynamically according to the capacity-on-demand principle. Common channel
signalling required by GPRS in the initial phase of the packet transfer is conveyed on the
PCCCH when it has been allocated, or alternatively on the CCCH. Thus, the operator
can now allocate resources to GPRS within a cell only when a packet is to be
transferred.
The GPRS specifications do not require PDCHs to be permanently allocated. The
allocation of GPRS capacity, however, can be based on the needs for actual packet
transfer, or as ETSI describes it, on the capacity-on-demand principle. Under this
principle, the operator is free to decide whether to allocate permanently or temporarily
some physical resources to GPRS traffic. When the PDCHs are congested due to GPRS
traffic load, and more resources are available within the cell, the network is free to
allocate more resources as PDCHs. In such cases, note that this does not imply the
existence of a PCCCH. When no PCCCH is present, the GPRS MSs camp on the CCCH
as usual.
It is expected that the PCCH would be allocated either as a result of increased demand
for packet data transfer or whenever there are enough available physical channels in a
cell to be able to improve the quality of the service. It is also possible to allocate more
physical resources on one or more PDCHs if required. Conversely, the network is able to
release the PCCCH, forcing the MSs to return to the CCCH.
As the number of allocated PDCHs can be increased or decreased according to demand,
it is necessary for the networks to support the following principles:
S Load supervision ... carries out the monitoring of load conditions on the PDCHs,
and as a result, the number of PDCHs can be increased or decreased.
S Dynamic allocation ... unused channels can be allocated as PDCHs to increase the
overall quality of service offered by GPRS.
Release of PDCHs
The fast release of PDCHs is critical if dynamic sharing of resources is to take place
between circuit-switched and packet switch services. To achieve this end, GSM offers
three possible methodologies:
S Wait for all the assignments to terminate on the particular PDCH.
S Individually notify all users that have an assignment on that PDCH.
S Broadcast the notification about de-allocation.

68P02903W01-O
FIELD TRIAL
Burst structure GPRS-300-101
Burst structure
Burst overview
Burst is described in the following sections:
S Timing advance.
S Medium access control and radio link control.
5–6 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Burst structure
Timing advance
Initial Timing Advance (TA) is calculated on the access burst as in GSM. However, unlike
GSM, an MS using GPRS may not be continuously transmitting, and this, therefore,
introduces the need for a process known as TA continuous update (see Figure 5-2).
52-MULTIFRAME NUMBER n:
UPLINK TAI=0 TAI=1
B0 B1 B2 0 B3 B4 B5 1 B6 B7 B8 2 B9 B10 B11 3
DOWNLINK TA MESSAGE 1 TAI MESSAGE 1
52-MULTIFRAME NUMBER n+1:

UPLINK TAI=2 TAI=3
B0 B1 B2 4 B3 B4 B5 5 B6 B7 B8 6 B9 B10 B11 7
52-MULTIFRAME NUMBER n+2
UPLINK TAI=4 TAI=5
B0 B1 B2 8 B3 B4 B5 9 B6 B7 B8 10 B9 B10 B11 11
UPLINK TAI=6 TAI=7
B0 B1 B2 12 B3 B4 B5 13 B6 B7 B8 14 B9 B10 B11 15
UPLINK TAI=8 TAI=9
B0 B1 B2 16 B3 B4 B5 17 B6 B7 B8 18 B9 B10 B11 19
UPLINK TAI=10 TAI=11
B0 B1 B2 20 B3 B4 B5 21 B6 B7 B8 22 B9 B10 B11 23
B0 B1 B2 24 B3 B4 B5 25 B6 B7 B8 26 B9 B10 B11 27
52-MULTIFRAME NUMBER n+7

B0 B1 B2 28 B3 B4 B5 29 B6 B7 B8 30 B9 B10 B11 31
B0-B11 ARE RADIO BLOCKS IDLE BURSTS ARE NUMBERED FROM 0-31
Figure 5-2 Timing advance

68P02903W01-O
FIELD TRIAL
Timing advance continuous process

The TA continuous update process involves the MS sending access bursts on an
assigned Packet Access Control CHannel (PACCH) using an idle timeslot, and receiving
TA Instructions (TAI) on a subsequent TA message. In case this message is not correct,
the MS listens to the next three TA messages. Figure 5-2 shows the process. In this
example, the MS transmits an access burst in idle slot 1 of multiframe (n), and receives
the TA value in TA-messages in multiframes (n+2) and (n+3).
To illustrate this pair of events, Figure 5-2 shows an MS transmitting an access burst on
idle slots 0, 2, 4, or 6, and receives its updated advance value in subsequent TA
messages 3, 4, and 1, but it has only to read these if TA message 2 was not received
correctly.
5–8 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Burst structure
Medium access
control and radio
link control
The Medium Access Control (MAC) function defines the procedures that enable multiple
MSs to share a common transmission link. As such, the MAC function provides
arbitration between the many MSs attempting to transmit simultaneously, and provides
collision avoidance, detection, and recovery procedures.
The functions of MAC allow for a single MS to be allocated several physical channels.
The Radio Link Control (RLC) function defines the procedure for selective retransmission
of unsuccessfully delivered RLC data blocks. The RLC function is also responsible for the
segmentation and re-assembly of LLC-PDUs into RLC data blocks (see Figure 5-3).
LLC LLC
RLC
RLC RLC
MAC
MAC MAC
PHYSICAL PHYSICAL
LAYER LAYER
FH INFORMATION FIELD FCS LLC
BH INFO FIELD BCS BH INFO FIELD BCS BH INFO FIELD BCS RLC/MAC
NORMAL NORMAL NORMAL NORMAL PHYSICAL

BURST BURST BURST BURST LAYER
Figure 5-3 Mode of operation

68P02903W01-O
FIELD TRIAL
Mode of operation
Refer to Figure 5-3. The Network-Protocol Data Units (N-PDUs) are segmented into the
SubNetwork-Protocol Data Units (SN-PDUs) by the SNDCP. These SN-PDUs are
encapsulated into several LLC frames, which may vary in size.
The maximum size of an LLC frame is 1600 octets minus the BSSGP protocol control.
The LLC frames are segmented into RLC data blocks, the size of which depends upon
the channel coding scheme being used.
At the RLC/MAC layer, a selective Automatic ReQuest for retransmission (ARQ) protocol
that includes block numbering is used between the MS and the GPRS network. The
GPRS network provides for retransmission of erroneous RLC data blocks. When the
complete LLC frame is successfully transferred across the RLC layer, the frame is
forwarded to the LLC layer.
Uplink state flag

The Uplink State Flag (USF) is used on the PDCHs to allow multiplexing of radio blocks
from a number of different MSs. When the SDCCH coding scheme is used, the USF
comprises three bits at the start of each radio block sent on the downlink. The USF
enables the coding of eight different USF states. The USF states are used to multiplex
the uplink traffic.
On PCCCH, one USF value is used to denote the presence of a PRACH (USF = FREE).
The other uses USF values, USF = R1 ... USF = R7, to reserve the uplink for different
MSs. On PDCHs not carrying a PCCCH, all eight of the USF values are used to reserve
the uplink.
The MS sends the packet channel request in one of four bursts on the radio block used
for the PRACH (indicated by setting the USF = FREE). In the access, the burst is
selected randomly.
5–10 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Channel coding
Channel coding
Channel coding
overview
The Physical Link Layer (PLL) is responsible for Forward Error Correction (FEC) coding
that allows for the detection and correction of transmitted codewords and the indication of
uncorrectable codewords.
Channel coding
schemes
Four different coding schemes have been defined for GPRS:
S CS-1, mandatory for BSS and MS.
S CS-2, mandatory for MS.
All control channels except the Packet Random Access CHannel (PRACH) use CS-1. As
for GSM, a special request scheme is used for the access request. The standard 8-bit
access request uses the same coding scheme as GSM. A new extended access request
contains 11 bits, and uses a specially adapted scheme. Traffic channels may use
schemes CS-1, CS-2, CS-3, and CS-4. This arrangement allows the coding scheme to
be dynamically adapted to the channel conditions, and thereby maximizes throughput
and optimizes performance. Figure 5-4 shows the structure of the radio block. Refer also
to Table 5-1.
The Uplink Status Flag (USF) is transmitted on the downlink, and is an invitation to an
MS to transmit. The Block Check Sequence (BCS) used for the detection of errors and
subsequent Automatic Repeat Request (ARQ) uses a sending window of 64 blocks. T is
the block Type indicator, and PC is the Power Control.
RADIO BLOCK
USF RLC HDR RLC DATA BCS
MAC HDR RLC/MAC DATA BLOCK
BCS IS PART OF
PHYSICAL HEADER
MAC HDR RLC/MAC CONTROL BLOCK
USF RLC/MAC SIGNALLING INFORMATION BCS
RADIO BLOCK
Figure 5-4 Radio block structures

68P02903W01-O
FIELD TRIAL
Channel coding GPRS-300-101
Table 5-1 Coding parameters for coding schemes

Scheme Code USF Pre- Radio BCS Tail Coded Punc- Data
rate coded Block bits tured rate
USF - USF bits kb/s
&
BCS
CS-1 1/2 3 3 181 40 4 456 0 9.05
CS-2 =2/3 3 6 268 16 4 588 132 13.4
CS-3 =3/4 3 6 312 16 4 676 220 15.6
CS-4 1 3 12 428 16 – 456 – 21.4
Coding scheme 1
For Coding Scheme-1 (CS-1), 40 bits are used for the Block Check Sequence (BCS) to
increase protection. These and the USF (3 bits), header and data (181 bits). In addition
to 4 tail bits are passed through a 1/2 rate convolution encoder resulting in a protocol
456-bit payload. Refer to Figure 5-5 for detail.
In CS-1 the data rate is equal to 181 bits/20 ms or 9.05 kbit/s.
USF HEADER AND DATA + BCS 224 BITS
4 TAIL BITS
RATE 1/2 CONVOLUTIONAL CODING
3 181 40
456 BITS
Figure 5-5 CS-1
5–12 15th Sep 99

68P02903W01-O
FIELD TRIAL
Coding scheme 2
For Coding Scheme-2 (CS-2), only 16 bits are used for the BCS, but in this case a CRC
code is used. Other differences between CS-2 and CS-1 include the use of a six-bit USF
to increase robustness during transmission over the air interface. Four tail bits are added
to the sequence before passing through a 1/2 rate convoluted encoder. The result of this
is a bit stream of 588 bits/20ms, but this needs to be reduced to 456 bits to bring it into
line with GSM burst structures. 132 bits are, therefore, punctured. This sequence is seen
in Figure 5-6.
6 268 16
USF HEADER AND DATA BCS 294 BITS
4 TAIL BITS
12
588 BITS
PUNCTURING (132 BITS)
12
456 BITS
FIRST PUNCTURED BITS LAST
1 2 ... 15 16 17 18 19 20 21 22 23 ... 587 588
(EXCEPT 12 SPECIFIC BITS)
Figure 5-6 CS-2

68P02903W01-O
FIELD TRIAL
Channel coding GPRS-300-101
Coding scheme 3
For Coding Scheme-3 (CS-3), the process used is very similar to that of CS-2, other than
in the degree of puncturing.
In this case, the header and data is made up of 312 bits, and after encoding with USF,
BCS, and tail bits the result is 676 bits. This is punctured to the 456 bits required by the
GSM burst structure. The puncturing sequence is seen in Figure 5-7.
6 312 16
USF HEADER AND DATA BCS 338 BITS
4 TAIL BITS
12
676 BITS
PUNCTURING (220 BITS)
12
456 BITS
FIRST PUNCTURED BITS
1 2 ... 15 16 17 ... 21 22 23 ... 27 28 29 ...
... 669 670 671 672 673 674 675 676
LAST
Figure 5-7 CS-3
5–14 15th Sep 99

68P02903W01-O
FIELD TRIAL
Coding scheme 4
For Coding Scheme-4 (CS-4), there is no Forward Error Correction (FEC) applied to the
data, and as such there is more capacity for user information. The BCS comprises 16
bits, using a CRC code and the USF extended to 12 bits for robustness. Under this
scheme it is possible to carry 428 bits of header and data. See Figure 5-8 for detail.
In CS-4, the data rate is equal to 428 bits/20ms or 21.4kbit/s.
12 428 16
USF HEADER AND DATA + BCS 456 BITS
NO CODING
456 BITS
Figure 5-8 CS-4

68P02903W01-O
FIELD TRIAL
Mobility management GPRS-300-101
Mobility management
Mobility
management
overview
Mobility management comprises the following states and functions:
S Definition of mobility management states.
S IDLE (GPRS) state.
S STANDBY state.
S READY state.
S IDLE/STANDBY/READY state functionality.
S STANDBY timer function.
S READY timer function.
S Periodic RA update timer function.
S Mobile reachable timer function.
Definition of
mobility
management
states
The Mobility Management (MM) activities related to a GPRS subscriber are
characterized by one of three different MM states. Each state describes a certain level of
functionality and information allocated. The information sets held at Mobile Station (MS)
and Serving GPRS Support Node (SGSN) are denoted MM context.
In the non-anonymous access case, the MM state relates only to GPRS MM activities of
a subscriber. The MM state is independent of the number and state of Packet Data
Protocol (PDP) contexts for that subscriber.
In the anonymous access case, the MM state relates to GPRS MM activities of an MS
represented only by an auxiliary ??? (TTLI).
IDLE (GPRS)
state
In GPRS IDLE state, the subscriber is not attached to the GPRS mobility management.
The MS and SGSN context hold no valid location or routeing information for the
subscriber. The subscriber-related mobility management procedures are not performed.
Public Land Mobile Network (PLMN) selection and GPRS cell selection and reselection
processes are performed by the MS.
The MS may receive Point-To-Point-Multicast (PTM-M) transmissions. Point-To-Point
(PTP) and Point-To-Multipoint-GPRS (PTM-G) data transfers to and from the mobile
subscriber and the paging of the subscriber are not possible. The GPRS MS is seen as
unreachable in this case.
In order to establish MM contexts in the MS and the SGSN, the MS performs the
GPRS-Attach procedure.
5–16 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Mobility management
STANDBY state
In STANDBY state, the subscriber is attached to the GPRS mobility management. The
MS and SGSN have established MM contexts for the subscriber International Mobile
Subscriber Identity (IMSI).
The MS may receive PTM-M and PTM-G data. Pages for PTP or PTM-G data transfers
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 de-activation of PDP contexts while in STANDBY state.
A PDP context is activated before data is transmitted or received.
An MT PTP or PTM-G packet can be received by the SGSN in the MM STANDBY state
when a PDP context is activated. 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 cannot be 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 may initiate the GPRS-Detach procedure to move to the IDLE state. When the
STANDBY timer expires, the MM contexts in the SGSN and in the MS independently
return to the IDLE state, and may be deleted.
READY state
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
done via the SGSN. The SGSN transfers downlink data to the BSS responsible for the
actual GPRS cell of the subscriber.
The MS may receive PTM-M and PTM-G data in READY state.
The MS may activate or de-activate PDP contexts while in READY 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.

68P02903W01-O
FIELD TRIAL
IDLE/STANDBY/
READY state
functionality
State transitions and functions
Movement from one state to the next is dependent on the current state (IDLE,
STANDBY, or READY) and the event concerned (for example GPRS-Attach).
Figure 5-9 outlines the state transitions described below.
STANDBY
IDLE TIMER IDLE
EXPIRY
or
CANCEL GPRS DETACH
LOCATION or
GPRS DETACH
CANCEL LOCATION
GPRS ATTACH GPRS ATTACH
STANDBY READY READY

TIMER
EXPIRY
PDU TRANSMISSION READY TIMER EXPIRY
or
FORCE TO STANDBY
or
READY TIMER EXPIRY ABNORMAL RLC CONDITION
or
FORCE TO STANDBY
PDU RECEPTION
STANDBY STANDBY
MM STATE MODEL OF MS MM STATE MODEL OF SGSN
Figure 5-9 Functional mobility management state model
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

STANDBY timer expiry: The MM and PDP contexts in the MS and SGSN may be
deleted. The GGSN PDP contexts must be 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 LLC PDU to the SGSN, possibly in response to a
page.
PDU reception: The SGSN receives an LLC PDU from the MS.
5–18 15th Sep 99

68P02903W01-O
FIELD TRIAL
Moving from READY to STANDBY

READY timer expiry: The MS and the SGSN MM contexts return to STANDBY state.
Force to STANDBY: The MS or the SGSN indicates an immediate return to STANDBY
state. The MS or the SGSN may signal a return to STANDBY state before the READY
timer expires.
Abnormal 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 requests that the MM context in the SGSN return to IDLE state,
and that the PDP contexts in the SGSN 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.
For anonymous access, a reduced mobility management state model consisting of IDLE
and READY states is used. The Anonymous Access (AA) MM state machine is
independently handled by the MS and the network, and may coexist with an IMSI-based
MM state machine. Several AA MM state machines may coexist in the same MS and
SGSN simultaneously.
Figure 5-10 outlines the state transitions for anonymous access described below.
IDLE IDLE
READY TIMER
EXPIRY
READY TIMER AA PDP CONTEXT or
AA PDP CONTEXT EXPIRY ACTIVATION ABNORMAL RLC
ACTIVATION or CONDITION
AA PDP CONTEXT or
DE-ACTIVATION AA PDP CONTEXT
DE-ACTIVATION
READY READY
AA MM STATE MODEL OF MS AA MM STATE MODEL OF SGSN
Figure 5-10 Functional anonymous access mobility management state model
Moving from IDLE to READY

AA PDP context activation: The MS requests an anonymous access, and a logical link to
an SGSN is initiated. MM contexts are established at the MS and SGSN, and PDP
contexts are established at the MS, at the SGSN, and at the GGSN.

68P02903W01-O
FIELD TRIAL
Moving from READY to IDLE
READY timer expiry: The MM and PDP contexts in the MS, the SGSN, and the GGSN
are deleted.
Abnormal Radio Link Control (RLC) condition: The SGSN MM context must be deleted in
case of delivery problems on the radio interface or in case of irrecoverable disruption of a
radio transmission.
AA PDP context de-activation: The network (either the SGSN or GGSN) initiates the AA
PDP context de-activation procedure; for example, due to malicious usage of the
anonymous service. The MM and PDP contexts in the MS, the SGSN, and the GGSN
must be deleted.
STANDBY timer
function
The STANDBY timer function maintains the STANDBY timer in the MS and SGSN. The
STANDBY timer controls the time an MS remains in STANDBY state. When the
STANDBY timer expires, the MS and SGSN MM contexts must return to IDLE state, and
the PDP contexts must return to INACTIVE state. The MM and PDP contexts in the
SGSN may be deleted.
The length of the STANDBY timer must be the same in the MS and SGSN. The initial
length of the STANDBY timer is defined as a default value. The SGSN (and only the
SGSN) may change the length of the STANDBY timer by transmitting a new value in the
attach accept or routeing area update accept messages.
If the STANDBY timer length is set to zero, the MS must immediately be forced into IDLE
state. If the timer length is set to all ones (binary), the STANDBY timer function must be
de-activated, that is the timer no longer runs, and the MS remains in STANDBY state.
The STANDBY timer must be reset and begin running in the MS and SGSN every time
STANDBY state is entered.
READY timer
function
The READY timer function maintains the READY timer in the MS and SGSN. The
READY timer controls the time an MS remains in the READY state in the MS and the
SGSN. The READY timer must be reset and begin 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 must return to STANDBY state.
In case of anonymous access the MM context must be deleted.
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. The SGSN (and only the SGSN)
may change the length of the READY timer by transmitting a new value in the attach
accept, routeing area update accept, or AA PDP context accept messages.
If the READY timer length is set to zero, the MS must immediately be forced into
STANDBY state. If the timer length is set to all ones (binary), the READY timer function
must be de-activated, that is the timer no longer runs, and the MS remains in the READY
state.
5–20 15th Sep 99

68P02903W01-O
FIELD TRIAL
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 must start a periodic routeing area update
procedure.
If the MS is in coverage, but out of GPRS coverage when the periodic RA update
expires, and if the MS is IMSI-attached to a network in network operation mode I, the
periodic location update procedure (or other appropriate update procedure) must be
started immediately. Also irrespective of whether the MS was IMSI-attached, and
irrespective of the network operation mode, the periodic RA update procedure (or other
appropriate update procedure) must be started as soon as the MS returns to GPRS
coverage.
If the MS is out of coverage when the periodic RA update timer expires, either:
S If the mobile returns to coverage in a cell that supports GPRS, the periodic RA
update procedure (or other appropriate update procedure) must be started as soon
as the MS returns to coverage.
S If the mobile returns to coverage in a cell that does not support GPRS, and if the
MS is IMSI-attached, the periodic location update procedure (or other appropriate
update procedure) must be started as soon as the MS returns to coverage in that
cell. Also irrespective of whether the MS was IMSI-attached, the periodic RA
update procedure (or other appropriate update procedure) must be started as soon
as the MS returns to GPRS coverage.
If the MS lost GPRS coverage, but the periodic RA update timer did not expire while out
of GPRS coverage, the MS must not perform the periodic RA update procedure because
of the return of the MS to coverage.
If the MS lost coverage, but the periodic RA update timer did not expire while out of
coverage, the MS must not perform the periodic RA update procedure because of the
return of the MS to coverage.
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 periodic RA update timer must not be longer than the
STANDBY timer.
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 must clear Paging Proceed Flag
(PPF). Typically, this causes the SGSN to stop sending GPRS paging or CS paging
messages to the MS, but other features (for example Mobile Switching Centre/Visitor
Location Register (MSC/VLR) based call forwarding) may occur immediately. PPF is set
when the next activity from the MS is detected. The MM and PDP contexts must be kept
in the SGSN.
When an MS first registers in an SGSN, the PPF is set.

68P02903W01-O
FIELD TRIAL
Session management GPRS-300-101
Session management
Session
management
overview
Session management comprises the following states and functions:
S Definition of packet data protocol states.
S PDP context, activation, modification, and de-activation functions.
S Packet routeing and transfer function.
S Relay function.
S Packet terminal adaptation function.
S Encapsulation function.
Definition of
packet data
protocol states
A PTP 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. Activation
and de-activation are described under PDP context activation, modification, and
de-activation functions . All PDP contexts of a subscriber are associated with the same
MM context for the IMSI of that subscriber.
INACTIVE state
The INACTIVE state characterises the data service for a certain PDP address of the
subscriber as 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
changing location of a subscriber causes no update for the PDP context in INACTIVE
state even if the subscriber is attached to the GPRS MM.
Mobile-terminated PTP packets received in INACTIVE state by the GGSN may initiate
the network-requested PDP context activation procedure if the GGSN is allowed to
initiate the activation of the PDP context for that PDP address. 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 document.
The MS initiates the movement from INACTIVE to ACTIVE state by initiating the PDP
context activation procedure.
5–22 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Session management
ACTIVE state
In ACTIVE state, the PDP context for the PDP address in use is activated in MS, SGSN,
and GGSN. The PDP context contains mapping and routeing information for transferring
PDUs for that particular PDP address between MS and GGSN. The ACTIVE state PDP
context is updated according to changed subscriber location initiated by mobility
management procedures,such as SGSN address and Tunnel IDentifiers (TIDs). The
PDP state ACTIVE 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 INACTIVE state when the de-activation
procedure is initiated (see Figure 5-11).
All active PDP contexts for an MS are moved to INACTIVE state when the MM state
changes to IDLE.
INACTIVE
DE-ACTIVATE
ACTIVATE PDP PDP CONTEXT
CONTEXT or
MM STATE
CHANGE TO IDLE
ACTIVE
Figure 5-11 Functional PDP state model

68P02903W01-O
FIELD TRIAL
PDP context
activation,
modification, and
de-activation
functions
These functions are only meaningful at the GSN Network SubSystem (NSS) level and do
not directly involve the BSS. An MS in STANDBY or READY state can initiate these
functions at any time to activate or de-activate a PDP context in the MS, the SGSN, and
the GGSN. A GGSN may request the activation of a PDP context to a GPRS-attached
subscriber. A GGSN may initiate the de-activation of a PDP context.
Upon receiving an activate PDP context request message, the SGSN initiates
procedures to set up PDP contexts.
Upon receiving a de-activate PDP context request message, the SGSN initiates
procedures to de-activate PDP contexts. If a logical name is stored in the PDP context
GGSN Address field, and if the SGSN needs to use this field, the SGSN converts this
logical name to an IP address upon PDP context activation. The SGSN stores the
converted IP address in the GGSN Address in Use field. If an IP address is stored in
the GGSN Address field, the same IP address is stored in GGSN Address in Use.
An MS does not have to receive the (de)activate PDP context accept message before
issuing another (de)activate PDP context request. However, only one request can be
outstanding for every Network Service Access Point Identifier (NSAPI).
State and dynamic PDP addresses

PDP addresses can be allocated to an MS in three different ways:
S The Home Public Land Mobile Network (HPLMN) operator assigns a PDP address
permanently to the MS (static PDP address).
S the HPLMN operator assigns a PDP address to the MS when a PDP context is
activated (dynamic HPLMN PDP address).
S the Visited Public Land Mobile Network (VPLMN) operator assigns a PDP address
to the MS when a PDP context is activated (dynamic VPLMN PDP address).
It is the HPLMN operator that defines in the subscription whether a dynamic HPLMN or
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.
Only static PDP addressing is applicable in the network-requested PDP context
activation case.
5–24 15th Sep 99

68P02903W01-O
FIELD TRIAL
PDP context
activation
procedure
The PDP context activation procedure is shown in Figure 5-12.
MS SGSN GGSN
1. ACTIVATE PDP CONTEXT REQUEST
2. SECURITY FUNCTIONS
3. CREATE PDP CONTEXT REQUEST
3. CREATE PDP CONTEXT RESPONSE
4. ACTIVATE PDP CONTEXT ACCEPT
Figure 5-12 PDP context activation procedure
The procedure steps are detailed in the following step descriptions.
Step 1
The MS sends an activate PDP context request (NSAPI, PDP type, PDP address,
access point name, QoS requested, PDP configuration options) message to the
SGSN. The MS uses PDP address to indicate whether it requires the use of a
static PDP address, or whether it requires the use of a dynamic PDP address. The
MS leaves PDP address empty to request a dynamic PDP address. The MS may
use access point name to select a reference point to a certain external network.
Access point name is a logical name referring to the external packet data network
that the subscriber wishes to connect to. QoS requested indicates the desired QoS
profile. PDP configuration options may be used to request optional PDP
parameters from the GGSN (see GSM 09.60). PDP configuration options is sent
transparently through the SGSN.
Step 2
Security functions may be executed.

68P02903W01-O
FIELD TRIAL
Step 3
The SGSN validates the activate PDP context request using PDP type (optional),
PDP address (optional), and Access Point Name (APN) (optional) provided by the
MS and the PDP context subscription records. The validation criteria, the APN
selection criteria, and the mapping from APN to a GGSN are described in annex A.
If no GGSN address can be derived, or if the SGSN has determined that the activate
PDP context request is not valid according to the rules described in annex A, the SGSN
rejects the PDP context activation request.
If a GGSN address can be derived, the SGSN creates a TID for the requested
PDP context by combining the IMSI stored in the MM context with the NSAPI
received from the MS. If the MS requests a dynamic address, the SGSN lets a
GGSN allocate the dynamic address. The SGSN may restrict the requested QoS
attributes given its capabilities, the current load, and the subscribed QoS profile.
The SGSN sends a create PDP context request (PDP type, PDP address, Access
Point Name (APN), QoS negotiated, TID, selection mode, PDP configuration
options) message to the affected GGSN. The APN must be the APN network
identifier of the APN selected according to the procedure described in annex A.
PDP address is empty if a dynamic address is requested. The GGSN may use the
APN to find an external network. Selection mode indicates whether a subscribed
APN was selected, or whether a non-subscribed APN sent by MS or a
non-subscribed APN chosen by SGSN was selected. Selection mode is set
according to annex A. The GGSN may use selection mode when deciding whether
to accept or reject the PDP context activation. For example, if an APN requires
subscription, the GGSN is configured to accept only the PDP context activation
that requests a subscribed APN, as indicated by the SGSN with selection mode.
The GGSN creates a new entry in its PDP context table. The new entry allows the
GGSN to route PDP PDUs between the SGSN and the external PDP network. The
GGSN may further restrict QoS negotiated given its capabilities and the current
load. The GGSN returns a create PDP context response (TID, PDP address,
BackBone Protocol (BBP), reordering required, PDP configuration options, QoS
negotiated, cause) message to the SGSN. PDP address is included if the GGSN
has allocated a PDP address. BBP indicates whether TCP or UDP is used to
transport user data on the backbone network between the SGSN and GGSN.
Reordering required indicates whether the SGSN is to reorder N-PDUs before
delivering the N-PDUs to the MS. PDP configuration options contain optional PDP
parameters that the GGSN may transfer to the MS. These optional PDP
parameters may be requested by the MS in the activate PDP context request
message, or may be sent unsolicited by the GGSN. PDP configuration options is
sent transparently through the SGSN. The create PDP context messages are sent
over the GPRS backbone network.
If QoS negotiated received from the SGSN is incompatible with the PDP context
being activated (such as the reliability class is insufficient to support the PDP
type), the GGSN rejects the create PDP context request message. The compatible
QoS profiles are configured by the GGSN operator.
Step 4
The SGSN inserts the NSAPI along with the GGSN address in its PDP context. If
the MS has requested a dynamic address, the PDP address received from the
GGSN is inserted in the PDP context. The SGSN selects a radio priority level
based on QoS negotiated, and returns an activate PDP context accept (PDP type,
PDP address, NSAPI, QoS negotiated, radio priority level, PDP configuration
options) message to the MS. The SGSN is now able to route PDP PDUs between
the GGSN and the MS.
5–26 15th Sep 99

68P02903W01-O
FIELD TRIAL
Procedure comments
For each PDP address, a different quality of service (QoS) profile may be requested. For
example, some PDP addresses may be associated with email that can tolerate lengthy
response times. Other applications cannot tolerate delay, and demand a very high level
of throughput, interactive applications being one example. These different requirements
are reflected in the QoS profile. If a QoS requirement is beyond the capabilities of a
PLMN, the PLMN negotiates the QoS profile as close as possible to the requested QoS
profile. The MS either accepts the negotiated QoS profile, or de-activates the PDP
context.
After an SGSN has successfully updated the GGSN, the PDP contexts associated with
an MS is distributed.
If the PDP context activation procedure fails, or if the SGSN returns an activate PDP
context reject (cause) message, the MS may attempt another activation to the same
APN up to a maximum number of attempts.
Network-request
ed PDP context
activation
procedures
The network-requested PDP context activation procedure allows the GGSN to initiate the
activation of a PDP context. When receiving a PDP PDU, the GGSN checks whether a
PDP context is established for that PDP address. If no PDP context has been previously
established, the GGSN may try to deliver the PDP PDU by initiating the
network-requested PDP context activation procedure. The criteria used by the GGSN to
determine whether trying to deliver the PDP PDU to the MS may be based on
subscription information, and are outside the scope of GPRS standardisation.
To support network-requested PDP context activation the GGSN needs static PDP
information about the PDP address. To determine whether network-requested PDP
context activation is supported for a PDP address, the GGSN checks whether there is
static PDP information for that PDP address.
When these checks have been performed, the GGSN may initiate the network-requested
PDP context activation procedure.
The network operator may implement the following techniques to prevent unnecessary
enquiries to the HLR:
S Implementation of the Mobile station Not Reachable for GPRS flag (MNRG)
technique in GGSN, SGSN, and HLR (see Unsuccessful Network-Requested
PDP Context Activation Procedure ).
S The GGSN may reject or discard PDP PDUs after a previous unsuccessful
delivery attempt. This systematic rejection of PDP PDUs would be performed
during a certain time after the unsuccessful delivery.
S The GGSN may store the address of the SGSN with which the GGSN established
the last PDP context. This would prevent an enquiry to the HLR. This SGSN
address would be considered as valid during a certain time.

68P02903W01-O
FIELD TRIAL
Successful
network-requeste
d PDP context
activation
procedure
The successful network-requested PDP context activation procedure is shown in
Figure 5-13.
MS SGSN HLR GGSN
1. PDP PDU
2. SEND ROUTEING INFO FOR GPRS
2. SEND ROUTEING INFO FOR GPRS ACK
3. PDU NOTIFICATION REQUEST
3. PDU NOTIFICATION RESPONSE
4. REQUEST PDP CONTEXT ACTIVATION
5. PDP CONTEXT ACTIVATION PROCEDURE
Figure 5-13 Successful network-requested PDP context activation procedure

Step 1
When receiving a PDP PDU, the GGSN determines if the network-requested PDP
context activation procedure has to be initiated. The GGSN may store subsequent
PDUs received for the same PDP address.
Step 2
The GGSN may send a send routeing information for GPRS (IMSI) message to
the HLR. If the HLR determines that the request can be served, it returns a send
routeing information for GPRS-Ack (IMSI, SGSN address, mobile station not
reachable reason) message to the GGSN. The mobile station not reachable
reason parameter is included if the MNRG flag is set in the HLR. The Mobile
station Not Reachable Reason (MNRR) parameter indicates the reason for the
setting of the MNRG flag as stored in the MNRR record (see GSM 03.40). If the
MNRR record indicates a reason other than No Paging Response, the HLR
includes the GGSN number in the GGSN list of the subscriber.
If the HLR determines that the request cannot be served (such as IMSI unknown
in HLR), the HLR sends a send routeing information for GPRS-Ack (IMSI, MAP
error cause) message. Map error cause indicates the reason for the negative
response.
Step 3
If the SGSN address is present and either MNRR is not present or MNRR
indicates No Paging Response, the GGSN sends a PDU notification request
(IMSI, PDP type, PDP address) message to the SGSN indicated by the HLR.
Otherwise the GGSN sets the MNRG flag for that MS. The SGSN returns a PDU
notification response (cause) message to the GGSN in order to acknowledge that
it requests the MS to activate the PDP context indicated with PDP Address.
5–28 15th Sep 99

68P02903W01-O
FIELD TRIAL
Step 4
The SGSN sends a request PDP context activation (PDP type, PDP address)
message to request the MS to activate the indicated PDP context.
Step 5
The PDP context is activated with the PDP context activation procedure (see PDP
context activation procedure ).
Unsuccessful
network-requeste
d PDP context
activation
procedure
If the PDP context requested by the GGSN cannot be established, the SGSN sends a
PDU notification response (cause) or a PDU notification reject request (IMSI, PDP type,
PDP address, cause) message to the GGSN depending on whether the context
activation fails before or after the SGSN has sent a request PDP context activation
message to the MS. Cause indicates the reason why the PDP context could not be
established:
S IMSI Not Known: The SGSN has no MM context for that IMSI (cause in PDU
notification response).
S MS GPRS Detached: The MM state of the MS is IDLE (cause in PDU notification
response).
S MS Not GPRS Responding: The MS is GPRS-attached to the SGSN, but the MS
does not respond. This may be due to the lack of a response to a GPRS paging
request, due to an abnormal RLC condition, or due to no activate PDP context
request message received within a certain time after the request PDP context
activation message was delivered to the MS (cause in PDU notification reject
request).
S MS Refuses: The MS refuses explicitly the network-requested PDP context
(cause in PDU notification reject request).
When receiving the PDU notification response or the PDU notification reject request
message, the GGSN may reject or discard the PDP PDU depending on the PDP type.
After an unsuccessful network-requested PDP context activation procedure, the operator
may perform some actions to prevent unnecessary enquiries to the HLR. The actions
taken depend on the cause of the delivery failure:
S If the MS is not reachable or if the MS refuses the PDP PDU (cause value MS Not
GPRS Responding or MS Refuses), the SGSN must not change the setting of
MNRG for this MS. The GGSN may refuse any PDP PDU for that PDP address
during a certain period. The GGSN may store the SGSN address during a certain
period, and send subsequent PDU notification request messages to that SGSN.
S If the MS is GPRS-detached or if the IMSI is not known in the SGSN (cause value
MS GPRS Detached or IMSI Not Known), the SGSN, the GGSN, and the HLR
may perform the protection and mobile user activity procedures.

68P02903W01-O
FIELD TRIAL
Protection procedure
The protection procedure is shown in Figure 5-14.
SGSN HLR GGSN
1. PDU NOTIFICATION RESPONSE
2. PDU NOTIFICATION REJECT REQUEST
2. PDU NOTIFICATION REJECT RESPONSE
3. SEND ROUTEING INFO FOR GPRS
3. SEND ROUTEING INFO FOR GPRS ACK
4. FAILURE REPORT
4. FAILURE REPORT ACK
Figure 5-14 Protection procedure
Step 1
When the MM context of the mobile is IDLE or if the SGSN has no information
about that user, the SGSN returns a PDU notification response (cause) message
to the GGSN with cause equal to MS GPRS Detached or IMSI Not Known,
otherwise the cause is Activation Proceeds. If the cause is MS GPRS Detached
or IMSI Not Known and if the SGSN has an MM context for that user, the SGSN
sets MNRG to indicate the need to report to the HLR when the next contact with
that MS is performed.
Step 2
When the MS does not respond or refuses the activation request, the SGSN sends
a PDU notification reject request (IMSI, PDP type, PDP address, cause) message
to the GGSN with cause equal to MS Not GPRS Responding or MS Refuses.
The GGSN returns a PDU notification reject response message to the SGSN.
Step 3
When cause equals IMSI Not Known, the GGSN may send a send routeing
information for GPRS (IMSI) message to the HLR. The HLR returns a send
routeing information for GPRS-Ack (IMSI, SGSN address, cause) message to the
GGSN indicating the address of the SGSN that currently serves the MS. If SGSN
address is different from the one previously stored by the GGSN, steps 3, 4, and 5
in Figure 5-13 are followed.
5–30 15th Sep 99

68P02903W01-O
FIELD TRIAL
Step 4
When SGSN address is the same as the one previously stored in the GGSN, or
when the cause value returned in step 1 equals MS GPRS Detached, the GGSN
sets MNRG for that PDP address, and sends a failure report (IMSI, GGSN
number, GGSN address) message to the HLR to request MNRG to be set in the
HLR. The HLR sets (if not already set) MNRG for the subscriber that owns the
IMSI, and adds GGSN number and GGSN address to the list of GGSNs to report
to when activity from the owner of that IMSI is detected. The GGSN number is
either the number of the GGSN, or, if a protocol-converting GSN is used as an
intermediate node, the number of the protocol-converting GSN. GGSN address is
an optional parameter that is included if a protocol-converting GSN is used.
Mobile user activity procedure

The mobile user activity procedure is shown in Figure 5-15.
MS SGSN HLR GGSN

1. ATTACH REQUEST
2A. READY FOR SM
2B. UPDATE LOCATION

3. NOTE MS GPRS PRESENT
Figure 5-15 Mobile user activity procedure
Step 1
The SGSN receives an indication that an MS is reachable,such as an attach
request message from the MS.
Step 2A
When the SGSN contains an MM context of the MS and MNRG for that MS is set,
the SGSN sends a READY for SM (IMSI, MS reachable) message to the HLR,
and clears MNRG for that MS.
Step 2B
When the SGSN does not keep the MM context of the MS, the SGSN sends an
update location message to the HLR.
Step 3
When the HLR receives the READY for SM message or the update location
message for an MS that has MNRG set, it clears MNRG for that MS, and sends a
note MS GPRS present (IMSI, SGSN address) message to all the GGSNs in the
list of the subscriber. (The READY for SM message also triggers the SMS alert
procedure.) SGSN address contains the address of the SGSN that currently
serves the MS. Upon reception of note MS present, each GGSN clears MNRG.

68P02903W01-O
FIELD TRIAL
Anonymous
access PDP
context
activation
procedure
The MS can anonymously initiate PDP context activation in IDLE, STANDBY, and
READY states. An existing MM context in the SGSN is neither required nor used in this
case. Only dynamic PDP addressing is applicable.
The anonymous access PDP context activation procedure is shown in Figure 5-16.
MS SGSN GGSN
1. ACTIVATE AA PDP CONTEXT REQUEST
2. CREATE AA PDP CONTEXT REQUEST
2. CREATE AA PDP CONTEXT RESPONSE
3. ACTIVATE AA PDP CONTEXT ACCEPT
Figure 5-16 Anonymous access PDP context activation procedure
Step 1
The MS sends an activate AA PDP context request (NSAPI, PDP type, PDP
address, access point name, QoS requested, PDP configuration options) message
to the SGSN. The MS uses a random temporary Logical Link Identity (TLLI) at the
RLC/MAC layer for identification purposes. The MS uses PDP address to indicate
that it requires the use of a dynamic PDP address. The MS uses an APN to select
a reference point to a certain external network that provides anonymous services.
QoS requested indicates the desired QoS profile. PDP configuration options may
be used to request optional PDP parameters from the GGSN (see GSM 09.60).
PDP configuration options is sent transparently through the SGSN.
5–32 15th Sep 99

68P02903W01-O
FIELD TRIAL
Step 2
The SGSN may restrict the requested QoS value given its capabilities and the
current load. The SGSN assigns an auxiliary TLLI, and creates an AA-TID for the
PDP-context. The SGSN sends a create AA PDP context request (PDP type, PDP
address, access point name, QoS negotiated, AA-TID, selection mode, PDP
configuration options) message to the GGSN indicated by the APN in the activate
AA PDP context request message. Selection mode indicates how the APN was
selected. The GGSN creates a new entry in its PDP context table. The new entry
allows the GGSN to route PDP PDUs between the SGSN and the server(s) that
provide services for anonymous MSs. The GGSN may use the APN to find an
external network that provides anonymous services. The GGSN may further
restrict QoS negotiated given its capabilities and the current load. The GGSN
allocates a dynamic PDP address, and returns a create AA PDP context response
(AA-TID, PDP address, BB protocol, reordering required, PDP configuration
options, QoS negotiated, cause) message to the SGSN. The BBP indicates
whether TCP or UDP is to be used to transport user data on the backbone network
between the SGSN and GGSN. Reordering required indicates whether the SGSN
is to reorder N-PDUs before delivering the N-PDUs to the MS. PDP configuration
options contain optional PDP parameters that the GGSN may transfer to the MS.
These optional PDP parameters may be requested by the MS in the activate PDP
context request, or may be sent unsolicited by the GGSN. PDP configuration
options is sent transparently through the SGSN. The GGSN checks the source
and destination address in all subsequent anonymous MO PDP PDUs received
from the SGSN. When the GGSN detects an invalid address in an MO PDP PDU,
the PDP PDU is discarded, and the MM and PDP contexts are deleted in the
GGSN, SGSN, and MS, as defined in Anonymous access PDP context
de-activation initiated by GGSN procedure.
When QoS negotiated received from the SGSN is incompatible with the PDP
context being activated (such as the reliability class is insufficient to support the
PDP type), the GGSN rejects the create AA PDP context request message. The
compatible QoS profiles are configured by the GGSN operator.
Step 3
The SGSN inserts the NSAPI along with the PDP address received from the
GGSN in its PDP context. The SGSN selects a radio priority level based on QoS
negotiated, and returns an activate AA PDP context accept (A-TLLI, PDP type,
PDP address, NSAPI, QoS negotiated, radio priority level, PDP configuration
options) message to the MS. The SGSN is now able to route anonymous PDP
PDUs between the GGSN and the MS.
After an SGSN has successfully updated the GGSN, the MM and PDP contexts
associated with an MS are distributed.
If the AA PDP context activation procedure fails, or if the SGSN returns an activate AA
PDP context reject (cause) message, the MS may attempt another activation of the
same GGSN up to a maximum number of attempts.

68P02903W01-O
FIELD TRIAL
Modification
procedures
A SGSN can decide to modify parameters that were negotiated during an activation
procedure for one or several PDP contexts. The following parameters can be modified:
S QoS negotiated.
S Radio priority level.
The SGSN has several means of informing the MS of such a modification:
S Send a separate modify PDP context request message to the MS.
S Piggyback the modification information on a mobility management signalling
exchange, such as routeing area update.
PDP context
modification
procedure
The standalone PDP context modification procedure is shown in Figure 5-17.
MS SGSN GGSN
1. UPDATE PDP CONTEXT REQUEST
2. UPDATE PDP CONTEXT RESPONSE

3. MODIFY PDP CONTEXT REQUEST
4. MODIFY PDP CONTEXT RESPONSE
Figure 5-17 PDP context modification procedure

Step 1
The SGSN sends an update PDP context request (TID, QoS negotiated) message
to the GGSN. If QoS negotiated received from the SGSN is incompatible with the
PDP context being modified (such as the reliability class is insufficient to support
the PDP type), the GGSN rejects the update PDP context request. The compatible
QoS profiles are configured by the GGSN operator.
Step 2
The GGSN may restrict QoS negotiated given its capabilities and the current load.
The GGSN stores QoS negotiated, and returns an update PDP context response
(TID, QoS negotiated) message.
Step 3
The SGSN sends a modify PDP context (NSAPI, QoS negotiated, radio priority
level) message to the MS. There can be one or a list of NSAPI, QoS negotiated,
and radio priority level parameter triplets in the message.
Step 4
The MS acknowledges by returning a modify PDP context accept message. If the
MS does not accept the new QoS negotiated, it de-activates the corresponding
PDP context(s) with the PDP context de-activation initiated by MS procedure.
5–34 15th Sep 99

68P02903W01-O
FIELD TRIAL
PDP context
de-activation
initiated by MS
procedure
The PDP context de-activation initiated by MS procedure is shown in Figure 5-18.
MS SGSN GGSN
1. DE-ACTIVATE PDP CONTEXT REQUEST
2. SECURITY FUNCTIONS
3. DELETE PDP CONTEXT REQUEST
3. DELETE PDP CONTEXT RESPONSE
4. DE-ACTIVATE PDP CONTEXT ACCEPT
Figure 5-18 PDP context de-activation initiated by MS procedure
Step 1
The MS sends a de-activate PDP context request (NSAPI) message to the SGSN.
Step 2
Security functions may be executed (see GSM 03.60).
Step 3
The SGSN sends a delete PDP context request (TID) message. The GGSN
removes the PDP context, and returns a delete PDP context response (TID)
message to the SGSN. If the MS was using a dynamic PDP address, the GGSN
releases this PDP address, and makes it available for subsequent activation by
other MSs. The delete PDP context messages are sent over the GPRS backbone
network.
Step 4
The SGSN returns a de-activate PDP context accept (NSAPI) message to the MS.
At GPRS-Detach, all PDP contexts for the MS are implicitly de-activated.

68P02903W01-O
FIELD TRIAL
PDP context
de-activation
initiated by
GGSN procedure
The PDP context de-activation Initiated by GGSN procedure is shown in Figure 5-19.
MS SGSN GGSN
1. DELETE PDP CONTEXT REQUEST
2. DE-ACTIVATE PDP CONTEXT REQUEST
2. DE-ACTIVATE PDP CONTEXT ACCEPT

3. DELETE PDP CONTEXT RESPONSE
Figure 5-19 PDP context de-activation initiated by GGSN procedure
Step 1
The GGSN sends a delete PDP context request (TID) message to the SGSN.
Step 2
The SGSN sends a de-activate PDP context request (NSAPI) message to the MS.
The MS removes the PDP context, and returns a de-activate PDP Context accept
(NSAPI) message to the SGSN.
Step 3
The SGSN returns a delete PDP context response (TID) message to the GGSN. If
the MS was using a dynamic PDP address, the GGSN releases this PDP address,
and makes it available for subsequent activation by other MSs. The delete PDP
context messages are sent over the GPRS backbone network. The SGSN may not
wait for the response from the MS before sending the delete PDP context
response message.
5–36 15th Sep 99

68P02903W01-O
FIELD TRIAL
Anonymous
access PDP
context
de-activation
initiated by MS
procedure
The MS must not issue explicit de-activation request messages to delete anonymous
contexts in the network. Instead, the READY timer is used as an implicit de-activation
timer to save signalling traffic on the radio interface.
The anonymous access PDP context de-activation initiated by MS procedure is shown in
Figure 5-20.
MS SGSN GGSN
1. READY TIMER EXPIRY

2. DELETE AA PDP CONTEXT REQUEST
2. DELETE AA PDP CONTEXT RESPONSE
Figure 5-20 Anonymous access PDP context de-activation initiated by MS procedure
Step 1
The READY timer expires in the MS and SGSN.
Step 2
The SGSN sends a delete AA PDP context request (AA-TID) message. The
GGSN removes the PDP context, and returns a delete AA PDP context response
(AA-TID) message to the SGSN. The GGSN releases this PDP address, and
makes it available for subsequent anonymous activation by other MSs.

68P02903W01-O
FIELD TRIAL
Anonymous
access PDP
context
de-activation
initiated by
GGSN procedure
If the GGSN detects a misuse or fraud of the anonymous context as described in
Anonymous access PDP context activation procedure step 2, it initiates the
de-activation independently of the READY timer expiry.
If the anonymous server detects a misuse or fraud, it may request the GGSN to
de-activate the AA context. The method that the anonymous server uses to inform the
GGSN is outside the scope of the GSM specifications.
The anonymous access PDP context de-activation initiated by GGSN procedure is
shown in Figure 5-21.
MS SGSN GGSN
1. DELETE AA PDP CONTEXT REQUEST

2. IDENTITY REQUEST
2. IDENTITY RESPONSE
3. DE-ACTIVATE AA PDP CONTEXT REQUEST
3. DE-ACTIVATE AA PDP CONTEXT ACCEPT

4. DELETE AA PDP CONTEXT RESPONSE
Figure 5-21 Anonymous access PDP context de-activation Initiated by GGSN

procedure
Step 1
The GGSN sends a delete AA PDP context request (AA-TID) message to the
SGSN.
Step 2
The SGSN may send an identity request (identity type = IMSI or IMEI) message to
the MS. The MS responds with an identity response (IMSI or IMEI) message.
Step 3
The SGSN sends a de-activate AA PDP context request (NSAPI) message to the
MS. The MS removes the PDP context, and returns a de-activate AA PDP context
accept (NSAPI) message to the SGSN.
Step 4
The SGSN returns a delete AA PDP context response (AA-TID) message to the
GGSN. The GGSN releases this PDP address, and makes it available for
subsequent activation by other MSs. The delete AA PDP context messages are
sent over the GPRS backbone network. The SGSN may not wait for the accept
from the MS before sending the delete AA PDP context response message.
5–38 15th Sep 99

68P02903W01-O
FIELD TRIAL
Packet routeing
and transfer
function
The packet routeing and transfer function:
S Routes and transfers packets between a mobile TE and an external network, that
is between reference point R and reference point Gi.
S Routes and transfers packets between mobile TE and other GPRS PLMN, that is
between reference point R and reference point Gi via interface Gp.
S Routes and transfers packets between TEs, that is between the R reference point
in different MSs.
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 and the implementation. The packet data protocol
in the MS may limit the maximum size of the PDP PDUs that are routed and transferred,
such as due to MS memory limitations.
Between the SGSN and the MS, PDP PDUs are transferred with the SNDCP.
Between the SGSN and the GGSN, PDP PDUs are routed and transferred with either the
TCP/IP or the UDP/IP protocols. The GPRS Tunnelling Protocol (GTP) transfers data
through tunnels. A tunnel is identified by a tunnel identifier (TID) and a GSN address.
To support roaming GPRS subscribers, and for forward compatibility, the SGSN is not
required to know the tunnelled PDP. Every SGSN must have the capability of transferring
PDUs belonging to PDPs not supported in the PLMN of the SGSN.
Relay function
The relay function of a network node transfers the PDP PDUs received from the
incoming link to the appropriate outgoing link. At SGSN and GGSN, the relay function
stores all valid PDP PDUs until they are forwarded to the next network node, or until the
maximum holding time of the PDP PDUs is reached. The PDP PDUs are discarded when
buffering is longer than their maximum holding time. 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 too short a holding time 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.

68P02903W01-O
FIELD TRIAL
Packet terminal
adaptation
function
The packet terminal adaptation function adapts packets received from and transmitted to
the Terminal Equipment (TE) to a form suitable for transmission within GSM.
A range of MT versions providing different standard interfaces towards the TE can be
used, such as:
S MT with asynchronous serial interface and Packet Assembly/Disassembly (PAD)
support (such as AT command set PAD, X.28 [34] / X.29 [35] / X.3 [32] PAD). In
the case when the PAD function does not exist in the MT, it exists in the TE.
S integrated MT with industry standard application program interface.
S MT with synchronous serial interface.
Encapsulation
function
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, at the SGSN, and at the GGSN. Encapsulation 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 one for the GPRS connection between
SGSN and MS.
In the PTP case, encapsulation requires that the MS is attached to GPRS, and that the
PDP context activation procedure has been executed. If the GPRS-Attach or PDP
context activation procedures cannot be successfully executed, uplink-bound PDP PDUs
are discarded in the MS. If these procedures have not been executed when a
downlink-bound PDP PDU arrives in the GGSN, the downlink PDP PDU is discarded,
rejected, or the network-requested PDP context activation procedure is initiated.
Encapsulation between SGSN and GGSN

The GPRS backbone network encapsulates a PDP PDU with a GPRS Tunnelling
Protocol (GTP) header, and inserts this GTP PDU in a TCP PDU or UDP PDU that again
is inserted in an IP PDU. The IP and GTP PDU headers contain the GSN addresses and
tunnel endpoint identifier necessary to uniquely address a GSN PDP context.
Encapsulation between SGSN and MS

Between SGSN and MS, an SGSN or MS PDP context is uniquely addressed with a
temporary logical link identity and a network layer service access point identifier pair.
TLLI is derived from the P-TMSI. A NSAPI is assigned when the MS initiates the PDP
context activation function.
5–40 15th Sep 99

68P02903W01-O
FIELD TRIAL
Chapter 6
Cabinet overview

68P02903W01-O
FIELD TRIAL
GPRS-300-101
ii 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101
Chapter 6
Cabinet overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Overview of cabinets and enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1
Cabinets and enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1
PCU cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
PCU cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
PCU chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3
PCU chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3
GSN complex cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4
GSN complex cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4
GSN shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5
GSN shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5
GSN Commhub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
GSN Commhub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
GSN ISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7
GSN ISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7

68P02903W01-O
FIELD TRIAL
GPRS-300-101
iv 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 Overview of cabinets and enclosures
Overview of cabinets and enclosures
Cabinets and
enclosures
This chapter provides general views of the following cabinets and enclosures:
S PCU cabinet.
S PCU chassis.
S GSN complex cabinets.
S GSN shelf.
S GSN CommHub.
S GSN ISS.

68P02903W01-O
FIELD TRIAL
PCU cabinet GPRS-300-101
PCU cabinet
PCU cabinet
Figure 6-1 shows a simplified front view of a PCU cabinet.
CARD CAGE
PSU/FAN PSU/FAN PSU/FAN
Figure 6-1 Front view of a PCU cabinet
6–2 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 PCU chassis
PCU chassis
PCU chassis
Figure 6-2 shows a simplified front view of a PCU chassis.
PRP or PICP
PRP or PICP
PRP or PICP
PRP or PICP
PRP or PICP
PRP or PICP
PRP or PICP
PRP or PICP
PRP or PICP
PRP or PICP
PRP or PICP
PRP or PICP
PSP
PPB
PSP
PPB
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Figure 6-2 Front view of the PCU chassis
Figure 6-3 shows a simplified front view of a PCU chassis.
T T T T T T B B T T T T T T
BOARD SLOT 1 ALARM PANEL BOARD SLOT 11

1 11
A A
U U
M M X X
P P
R R
D D D D D D O O D D D D D D
P P P P P P C C P P P P P P
R R R R R R R R R R R R
O O O O O O R O O O O O O
C C C C C C C C C C C C A A
U U
X X
PS/FAN PS/FAN PS/FAN
AN AIR FILTER IS ATTACHED TO THE FRONT OF EACH THE 3 FAN/POWER SUPPLY UNITS
B: BRIDGE BOARD
T: E1 TRANSITION MODULE
Figure 6-3 PCU chassis front view

68P02903W01-O
FIELD TRIAL
GSN complex cabinets GPRS-300-101
GSN complex cabinets
GSN complex
cabinets
Figure 6-4 shows a simplified front view of a GSN complex cabinets.
GGSN (REDUNDANT)
GGSN
ISS (STAND-BY)
ISS (ACTIVE)
GSN SHELF
HADA (ACTIVE)
Figure 6-4 Front view of the GSN complex cabinets
6–4 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN shelf
GSN shelf
GSN shelf
Figure 6-5 shows a simplified front view of a GSN shelf, SGSN chassis.
Figure 6-5 Front view of the GSN cage

68P02903W01-O
FIELD TRIAL
GSN Commhub GPRS-300-101
GSN Commhub
GSN Commhub
Figure 6-6 shows a simplified view of a GSN CommHub.
Catalyst 5500
Figure 6-6 Front view of the GSN CommHub
6–6 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN ISS
GSN ISS
GSN ISS
Figure 6-7 shows a simplified front view of a GSN ISS.
NETRA t
ÉÉ
1125
ÉÉ SUN
Figure 6-7 Front view of the GSN ISS

68P02903W01-O
FIELD TRIAL
GSN ISS GPRS-300-101
6–8 15th Sep 99

68P02903W01-O
FIELD TRIAL
Chapter 7
GPRS specifications

68P02903W01-O
FIELD TRIAL
GPRS-300-101
ii 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101
Chapter 7
GPRS specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
GPRS specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1
Specifications overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1
OMC-G specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
GPRS OMC-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
GSN specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–10
GSN chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–10
PCU specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–11
PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–11
Motorola MCP750 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–11
General description of PCU functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–12
PCU board descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–13
PCU processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–15
GSN CommHub specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–17
GSN CommHub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–17
GSN ISS specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–20
GSN ISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–20
GSN HADA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–21

68P02903W01-O
FIELD TRIAL
GPRS-300-101
iv 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 GPRS specifications
GPRS specifications
Specifications
overview
S This chapter provides specifications for the following:
S OMC-G specifications.
S GSN specifications.
S PCU specifications.
S GSN CommHub specifications.
S GSN ISS specifications

68P02903W01-O
FIELD TRIAL
OMC-G specifications GPRS-300-101
OMC-G specifications
GPRS OMC-G
Summary
The OMC-G provides GSN management functionality in the following areas:
S Fault management.
S Load and database management.
S Security management.
S Online help.
Standards
ETSI technical report 10.18 covering O&M for GPRS. This standard is still being
formulated, and Motorola aims to achieve the maximum compliance.
Description: fault management

The OMC-G fault management application provides the following functionality:
S Alarm window.
S View of alarms/events from SGSN, GGSN, ISS, and GSN CommHub.
S Handling/unhandling of alarms.
S Clearing of alarms.
S Removal of cleared alarms.
S Subscription to specified alarms/events.
S Filtering (blacklisting) of specified alarms/events.
S Alarm/event history reporting.
S Map view.
S Tabular view.
S Support for regions.
The OMC administrator is able to subdivide the network into one or more regions, which
are defined in terms of one or more SGSNs, GGSNs, ISSs and GSN CommHubs.
7–2 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 OMC-G specifications
Alarm window
The alarm window is at the heart of the OMC-G fault management application (see
Figure 7-1).
Figure 7-1 Configuration management
This provides the OMC operator with an alarm list. These are acknowledged by the
operator, who takes corrective action based on the particular problem. With the alarm
selected, menu options and mouse options are context sensitive, providing the operator
with a direct route to addressing the problem.
Alarms are displayed based on the operator subscription criteria, and can be re-sorted
and reformatted to suit the operator preferences.
The tabular view provides a summary view of outstanding alarms, showing their source
along with a number of operator selectable fields such as alarm count and severity.
The navigator window can be configured to provide a further summarized view of the
system alarm status by displaying alarm-related icons within the navigation display.
The alarm window and tabular view can be accessed from menu options on the OMC
workspace, from the navigator, as well as from the geographic and topological maps.

68P02903W01-O
FIELD TRIAL
OMC-G navigator
The overall fault management functionality is captured on the following user view:
The OMC-G configuration management user interface consists primarily of the OMC
navigator (see Figure 7-2) and parameter views Figure 7-3, which are accessed through
the OMC workspace.
Figure 7-2 OMC-G navigator with SGSN hierarchy and expanded Gb interface
containment
The OMC-G configuration management provides GUI support for the creation of GSNs
with default parameters. GSNs can also be deleted through the GUI. GSN parameters
can be viewed and modified through the appropriate parameter view Figure 7-3.
Access from the OMC-G to the ISS and GSN CommHub is provided for configuration
management activities.
The OMC-G GUI provides support for Gb link (SGSN to PCU connection) configuration.
Facilities are provided to enable the export of Gb information from the PCU and the
application of Gb information to the GSN. Gb information can be extracted from both
SGSN and PCU for comparison.
The OMC-G supports the propagation of one or more SGSN parameter values to
one/multiple/all SGSNs. Likewise it is possible to propagate one or more GGSN
parameter values to one/multiple/all GGSNs.
7–4 15th Sep 99

68P02903W01-O
FIELD TRIAL
Parameter views
Figure 7-3 shows the parameter view.
Figure 7-3 SGSN - Gb interface – NS parameter view

68P02903W01-O
FIELD TRIAL
Load and database management

The OMC-G load management applications are available as options on the Load Mgt
menu on the navigator, map, and tabular view. The following functionality is provided:
S Installation of software load/database.
S Deletion of software load/database.
S Download of software load/database.
S Progress display of software load/database download.
S Activation (swap) of new software load/database.
S Upload of database.
S Progress display of database upload.
Figure 7-4 below shows the load management operations as displayed on the main
menu.
Figure 7-4 Performance Management
The OMC-G performance management application provides the user with the ability to
view GSN statistics in two ways:
S On-demand.
S Polled.
7–6 15th Sep 99

68P02903W01-O
FIELD TRIAL
On-demand statistics view

The GSN statistics attributes can be viewed on-demand through the SGSN performance
parameter view and the GGSN performance parameter view. These can be invoked from
the OMC-G navigator application (see Figure 7-5).
Figure 7-5 On-demand statistics

68P02903W01-O
FIELD TRIAL
Polled statistics view

The GSN statistics attributes can be viewed on a polled basis. This means that the user
can create a real-time display of a statistic for a specific GSN. The statistic is displayed in
a graphical form, and is updated periodically according to a polling interval. The polling
interval can be changed by the user.
The polled statistic graph can be launched from the display menu on any of the main
OMC-G applications, that is navigator, map, tabular view, alarm window, event window,
SGSN and GGSN parameter views (see Figure 7-6).
Figure 7-6 Polled statistics
Background statistics
Statistics values are also collected by the GSN in files, independent of on-demand and
polled viewing. These files are sent to the OMC-G at intervals of 15 minutes. They can
be displayed in graphical and tabular formats. Custom statistics can be derived from the
raw statistics. PM reports can be scheduled.
7–8 15th Sep 99

68P02903W01-O
FIELD TRIAL
Security management
Security management involves both user authentication and control of user access. User
authentication is achieved via a validity check of the username/password combination, as
entered by the user when he/she attempts to logon to the system.
Access control must be administerable by the security administrator.
Access control must be on a per-operation basis; for example the operator must not be
allowed to perform configuration operations.
Access control must also be on a per-region basis; for example the operator has either
have no access, read-only access, or read/write access to a region. If the operator has
read-only access to a region, the related user access privileges are redundant. If the
operator has read/write access to a region, the related write access privileges are those
defined by the related user access privileges.
On-line help
Context sensitive on-line help is available from the OMC-G GUI.
Benefits
S Task focused operability from day one.
S Fully functional GUI for all parameters setting.
S Background on-demand and polled statistics mean that operators can have
flexibility in their performance management.
Applications
This feature is used by any operator deploying the Motorola GSN network for its
configuration, monitoring, and management.
Compatibility/dependencies/network elements affected

This feature requires the implementation of the Motorola OMC-G, SGSN, GGSN, ISS,
GSN CommHub.
The OMC-G requires the implementation of a Windows NT server.

68P02903W01-O
FIELD TRIAL
GSN specifications GPRS-300-101
GSN specifications
GSN chassis
Table 7-1 lists the specifications for the GSN chassis.
Table 7-1 GSN chassis specifications

Category Specification
Dimensions H 533.4 mm x W 482.6 mm x D 435 mm
Weight 13.6 kg: without boards or peripherals installed
31.85 kg: with peripherals and CPU installed
Mounting Per EIA Standard RS-310-C in 19 inch rack with mounting
brackets
Slots Sixteen hot swap-capable 4HP CompactPCI slots, including
two CPU slots, two HSC bridge slots twelve 12 I/O slots
Power Supplies/Fans Three bays, front accessible
Backplane Two 8-slot, 64-bit CompactPCI domains
1 CPU slot, 1 HSC bridge slot, and 6 I/O slots per domain
Power Supply PS/2 style with MTBF > 90,000 hours
Output –400 W @ 50°C
+5 V – 30 A (range 24 to 30 A)
+3.3 V – 28 A (range 20 to 28 A)
+12 V – 14 A
–12 V – 1 A
Input Voltage 93 Vac–265 Vac auto-sensing, 47 Hz – 63 Hz (fuse protected)
Temperature 5°C to +40°C: operating -5°C to +55°C: short-term
Humidity 5% to 85% @ 40°C: operating 10% to 95% @ 40°C: storage
Altitude 1800 m: operating 9000 m: storage
Shock and Vibration Conforms to Bellcore document GR-63-CORE (US), 4.4 and
ETSI, ETS 300-019 (Europe)
Acoustic Noise >60 dB (peripherals idle, at 1 meter and 25°C)
EMC shielding Meets all EMC requirements without the benefit of an
EMC-shielding bezel
Regulatory Safety: UL1950, EN60950, CSA 22.2 std#950 Flammability:
Requirements Bellcore GR-63-CORE (Sec 4.2), IEC 950.
Emissions: FCC part 15 subpart B, EN55022 Class A,
ICES-003 Industry Canada, EN60555-2 Immunity:
EN55101-2 (ESD), EN55101-3 (EMI), EN55101-4 (EFT).
7–10 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 PCU specifications
PCU specifications
PCU
This section specifies the following PCU boards:
S Motorola MCP750 features.
S General description of PCU functions.
S PCU board descriptions.
S PCU processes.
Motorola MCP750
features
The list below provides the Motorola MCP750 features:
S PowerPC 750 32-bit microprocessor.
S 32 Kb/32 Kb L1 cache.
S 1 Mb of secondary backside cache.
S 16Mb to 256Mb of ECC DRAM, via memory mezzanine.
S Two 32-pin PLCC/CLCC sockets for FLASH memory, up to 1 Mb capacity for
on-board firmware or user specified requirements.
S 4 Mb or 8 Mb on-board FLASH memory for user specified requirements on
memory mezzanine.
S CompactFLASHTM memory board socket for optional CompactFLASH memory.
S On-board debug monitor with self-test diagnostics.
S Ethernet transceiver interface with 32-bit PCI local bus DMA, 10/100 Mb/s with
auto-negotiate speed select.
S Single size IEEE P1386.1 compliant 32/64-bit PMC expansion slot with front panel
or optional P2 I/O
Two USB ports
S 8 K x 8 NVRAM and time-of-day clock with replaceable battery backup.
S Two asynchronous serial ports.
S Two async/sync serial ports.
S Four 32-bit timers, one watchdog timer.
S IEEE 1284 8-bit bidirectional parallel port.
S Floppy disk controller.
S Mouse and keyboard interfaces.
S 64-bit CompactPCI interface.
S Optional secondary CompactPCI interface.
Single CompactPCI slot, even when fully configured

68P02903W01-O
FIELD TRIAL
PCU specifications GPRS-300-101
Motorola MCP750 specifications

Table 7-2 gives the specifications for MCP750.
Table 7-2 MCP750 specifications

Part Number Description
MCP750-1222 MPC 750, 16 Mb ECC DRAM, 5 Mb FLASH, 1 Mb L2 cache
Heurikon Corporation PM/T1 and PM/E1

CPU: MPC860MH 40 MHz Motorola PowerQUICC
Local PCI Bus Controller: PLX Technology PCI9060ES
Notes:
S Host PCI reset resets this device.
S PCI bus is little endian.
S Has command line interface for setup/debugging.
General
description of
PCU functions
The Packet Control Unit (PCU) within the Base Station Subsystem (BSS) is the
functional entity that terminates the Gb interface. The PCU is considered to be a
component of the BSC which interfaces to the SGSN via the Gb interface.
The PCU provides the GPRS radio channel control functions such as the RLC/MAC
protocols. The PCU may be implemented as a stand-alone equipment, or may be
incorporated within the BSC or BTS. In addition, the PCU may be collocated with the
SGSN in some network configurations. The Motorola system places the PCU with the
BSC.
Packetizer
UL: RLC data blocks concatenated into LLC frames.
DL: LLC frames segmented into RLC data blocks.
Timeslot allocation manager for GPRS (MAC)

Assignment of TSs to MSs that have requested a data channel.
Scheduling of RLC data blocks on air.
Error detector for the air interface (RLC ARQ)

Retransmissions of RLC data blocks occur when data blocks are corrupted over the air
interface.
The ARQ mechanism uses a window of 64 elements, each one of them indicating if the
RLC data block is un/acknowledge.
7–12 15th Sep 99

68P02903W01-O
FIELD TRIAL
Radio channel manager

Power control.
Timing Advance.
Sysinfo messages generation.
PCU board
descriptions
The PCU utilizes MCP750 processor boards within the compactPCI chassis. They are:
S PSP board: Packet System Processor.
S PRP board: Packet Resource Processor.
S PICP board: Packet Interface Control Processor.
S PPB board: PCI to PCI Board.
The RJ-45 sockets on the front of the boards connect to the GSN CommHub to allow
access to the network.
PSP board: Packet System Processor

System processor of the PCI bus:
S Provides bus arbitration.
S Provides high-availability SW.
S Performs PCI configuration and all centralised functions at the application level
(Gb Interface management and gateway management).
S Collects statistics, alarms and performs fault management.
The digital board has a 750 power pc processor.
PRP board: Packet Resource Processor

GPRS non-system processor, performs:
S Segmentation of LLC frame.
S Concatenation of RLC data blocks.
S RLC ARQ.
S Timeslot management.
S Downlink flow control of data buffers.
It has 20 ms to process ALL UL/DL data packets.
One PRP board can control up to 120 timeslots (maximum of 30 active).
The board uses a 750 power pc processor.
PICP board: Packet Interface Control Processor

The PICP board performs the following related functions:
S Communication between PCU and BSC/SGSN.
S Each board has two PMC sockets to allocate PMC modules.
S One PMC module interfaces PCU-BSC using the LAPD protocol, and the other
PMC module interfaces PCU-SGSN using the frame relay protocol.
S Each PMC module supports two E1 links.
S The PMC modules use an 860 power pc processor.

68P02903W01-O
FIELD TRIAL
PPB board: PCI to PCI Board

The PPB board performs the following functions:
S Connects two CPCI buses on the backplane of the PCU.
S Works closely to the MPROC to administrate the PCI bus.
S Contains memory of the active processor so that if it fails, the memory can be
copied to the standby board.
PRPCompactPCI
CompactPCI is a very high performance computer bus standard for industrial and
telecommunications applications. CompactPCI boards are inserted from the front of the
chassis, and I/O can break out either to the front or to the rear.
Compared to standard desktop PCI, CompactPCI supports twice as many PCI slots
(eight slots as opposed to four) and offers a packaging scheme that is much better suited
for use in industrial applications. For example, Compact PCI boards are designed for
front loading and removal from a chassis. The boards are firmly held in position by their
connectors, board guides on both sides, and a face plate that solidly screws into the
chassis.
Boards are mounted vertically allowing for natural or forced air convection for cooling.
Finally the pin-and-socket connector of the CompactPCI board is significantly more
reliable and has better shock and vibration characteristics than the board edge connector
of the standard PCI boards.
The power and signal pins on the CompactPCI connector are staged so as to allow the
specification to support hot swapping, a feature that is very important for fault tolerant
systems, and which is not possible on standard PCI.
More Information can be found on the MCG Compact CPI FAQ*.
Currently for the PCU the 16-slot Motorola CPX2116 CompactPCI enclosure is used; for
field trial and GA, a16-slot chassis will be utilized.
Processor boards are inserted into the chassis, and are loaded with the software for PCU
functionality. The boards are MCG MCP750 boards.
7–14 15th Sep 99

68P02903W01-O
FIELD TRIAL
MCP750
The MCP750 processor board has the following characteristics:
S 128 Mb RAM.
S One 1 Mbyte 16 bit flash memory on board.
S Additional 64 bit 8 Mbyte flash memory.
S Compact Flash memory socket with 48 Mbyte CompactFlash.
S One 10/100 BaseT Ethernet port.
S One asynchronous serial port.
S One transition module for connection to the hard drive (SGSN CF and GGSN
boards only).
S One dual E1 PMC module: (SGSN TF board only).
The MCP750 processor board supports control and maintenance functions, network
management, fault management, account information recording, system configuration,
and provides coordination between other modules in the PCU. The Compact Flash
memory board on each processor board is configured as an EIDE primary master drive.
The MCG overview of the board states:
The MCP750 Series is a family of CompactPCI processor modules based on the
Motorola PowerPlus architecture with PowerPC microprocessors that push performance
and functionality to unprecedented levels.
Utilizing Motorola low power, high-performance PowerPC 750 microprocessors, the
Peripheral Component Interconnect (PCI) bus for the on-board peripherals,
processor/memory bus to PCI bus bridge, and a 64-bit bridge to the CompactPCI
interface, the MCP750 packs optimum performance and functionality in a single
CompactPCI slot.
PCU processes
There are three PCU processes:
S PRP processes.
S GB processes.
S GWM processes.
PRP processes:
The PRP processes are listed below:
S The Packet Resource Manager (PRM):
– Performs all RLC/MAC functions.
– Realises UL/DL power control and timing advance.
S The DownLink Segmentator (DLS) segments LLC frames into RLC data blocks to
be transmitted over the air interface
S The UpLink Concatenator (ULC) concatenates RLC data blocks into LLC frames.
S The Timeslot Resource Shifter (TRS) determines which TSs are active in a PRP
board to perform a control of the GPRS traffic.
S The SYstem information Manager (SYM) builds and sends GPRS system
information messages over the BCCH.
S CCCH Paging Manager (CPGM) processes the paging messages coming from the
SGSN to the BSC/BTS.

68P02903W01-O
FIELD TRIAL
GB processes
The GB processes are listed below:
S The Gb router (GR) routes incoming BSSGP PDUs from the SGSN to the relevant
SW process in the PCU.
S The Flow control Buffer Manager (FBM) controls buffer capacity for each cell and
each mobile so that the incoming data from the SGSN matches the air throughput.
S The Gb Manager (GBM) manages the state of all cell and signalling links between
the PCU and the SGSN.
S The Gb Transmit Manager (GTM) collects all UL frames from various ULCs, and
sends them on the appropriate NS-VC.
S The Network Service Tester (NST) periodically tests all alive NS-VCs on a PICP
board.
S The Frame Relay (FR) performs the frame relay protocol functions.
GWM processes
The GWM processes are listed below:
S The Pcu Fault Transaction Process (PFTP) is the central collection point for all
faults generated in the PCU.
S The Pcu Fault Transaction Process (PFCP) resides in every DPROC, and collects
all faults for that DPROC.
S The Pcu Central Authority (PCA) initializes devices, brings them out/in of service,
tests the devices, and performs fault recovery of the PCU.
S The Pcu System Audit Process (PSAP) monitors periodically the soft devices to
maintain the reliability of the system.
S The Pcu Configuration Management (PCM) distributes all database changes
performed at the BSC to the PCU boards.
S The Cell Balancer (CB) handles the load balancing of cells across all PRPs.
7–16 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN CommHub specifications
GSN CommHub specifications
GSN CommHub
Table 7-3 lists the specifications for the GSN CommHub.
Table 7-3 GSN CommHub specifications

Category Item Specification
Dimensions—Cisco Catalyst Height 62.5 cm
5000 chassis
Width 43.1 cm
Depth 46.0 cm (55.0 cm
including cable guide)
Weight 22.75 kg (chassis only)
1.36 to 2.27 kg (each
module)
65.65 kg for fully
configured chassis with 13
switching modules and 2
power supplies
Slots 13 (including 2 for power
supplies)
Electrical Power supply output 1100 W maximum
System power dissipation 1100 W maximum
configuration
750W typical with
maximum configuration
System heat dissipation 1571 W
AC input voltage 100 to 240 Vac wide input
with power factor corrector
DC input voltage -40.5 to -72 Vdc
continuous
AC frequency 47 to 63 Hz
AC input current 16A maximum at 100 Vac
–127 Vac, 8A maximum at
200 Vac to 240 Vac with
full configuration (max of
1.8 kVA)
DC input current 53 A maximum at 48 V
(nominal)
27 A maximum at 60 V
(nominal)
Power supply output 200 A at +5.15V; 6 A at
+12V; 2 A at +24 V
DC power cable wire 8 AWG 90°C copper
gauge conductors

68P02903W01-O
FIELD TRIAL
GSN CommHub specifications GPRS-300-101

Airflow 285 cubic feet per minute
through system fan
assembly
Environmental Temperature 0 to +40°C (operating)
-20°C to +65°C
(non-operating and
storage)
Relative Humidity 10 to 90% non-condensing
(operating)
5 to 95% non-condensing
(non-operating and
storage)
Altitude Sea level to 3050 meters
Vibration, operating 5 to 200 Hz, 0.5 g (1
oct/min)
Vibration, non-operating 5 to 200 Hz, 1 g (1
oct/min)
200 TO 500 Hz, 2 g (1
oct/min
Switching components Backplane 3.6 Gbit/s
5-Gbit/s cell-based
switching fabric for ATM
Microprocessor 25-MHz 68EC040 for the
(Supervisor Engine II) Network Management
Processor
Memory (Supervisor Engine DRAM 16 Mb
II)
Flash (onboard) 16 Mb
NVRAM 256 Kb
Electrical – power supply Voltage Range 90 Vac–130 Vac or
modules 180Vac – 260 Vac,
auto-switched
Input Current 3 A (max)
8 A (max) input peak
AC Overload Protection 5.0 A, 250 V, slow-blow
fuse
Output per Power Supply 150 W, 512 BTU/hr
+ 5 V @ 20 A
+ 12 V @ 4 A
- 12 V @ 3 A
Minimum load is 15 W.
7–18 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN CommHub specifications

Safety and regulatory Safety UL-1950, CSA 22.2 No.
specifications 950, IEC 950, TS 001,
AS/NZS 3260 CE Marking
Electromagnetic FCC Class A (47 CFR,
interference Park 15), EN55022 Class
A and VCCI Class I,
AS/N23548, Class A with
UTP cables
EN55022 Class B and
VCCI Class 2,
AS/N23590, Class B with
shielded UTP cables

68P02903W01-O
FIELD TRIAL
GSN ISS specifications GPRS-300-101
GSN ISS specifications
GSN ISS
Table 7-4 below lists the specifications for the Sun Cluster and ISS.
Table 7-4 Sun Netra t 1125 specifications

Height (Netra t 1125) 431.8 mm
Width 431.8 mm
Depth 496.1 mm
AC input 110 Vac to 240 Vac nominal
90 Vac to 264 Vac, 47 Hz to 63 Hz,
DC output 325 W (maximum)
Operating temperature Operating: 5°C to 40°C
Non-operating: -5°C to 55°C
Relative Humidity Operating: 5% to 80% non-condensing at 35°C
(5% to 90% for a maximum of 96 hours)
Non-operating: 10% to 95% non-condensing at 40°C
Elevation Operating: –300 m to +3000 m
Non-operating: –300 m to +12,000m
Acoustic noise Less than 60 dBA at a distance of 600 mm and a height of
1500 m, measured at 25°C
7–20 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN ISS specifications
GSN HADA
Table 7-5 below lists the specifications for the Sun Netra st D1000 storage modules
(HADA) that are paired with the Sun Netra d 1125 GSN ISS modules.
Table 7-5 Sun Netra st D1000 specifications

Height (Netra t 1125) 175 mm
Width 449.4 mm
Depth 532.5 mm
Weight 23.4 kg without disk drives
32.3 kg fully loaded
AC power requirements Voltage: 100 Vac to 240 Vac nominal
Frequency: 47 Hz to 63 Hz
Maximum operating current: 5 amps
Maximum surge current: 22 amps peaks
DC power requirements Voltage: –38Vdc
Maximum operating current: 11 amps
Maximum input surge: 22 amps peak
Operating temperature Operating: 0°C to 40°C
Non-operating: -25°C to 65°C
Relative Humidity 5% to 85% non-condensing
5% to 95% non-condensing at 40°C
Altitude (based on Operating: 0 m to +3000 m
drives) Non-operating: 0 m to +12,000m
Heat dissipation 260 W, 1092 BTU per hour: operating
(maximum)
Sound power 6.6 B, in accordance with ISO 9296
Earthquake NEBS requirement for earthquake zone 4

68P02903W01-O
FIELD TRIAL
GSN ISS specifications GPRS-300-101
7–22 15th Sep 99

68P02903W01-O
FIELD TRIAL
Chapter 8
Software features

68P02903W01-O
FIELD TRIAL
GPRS-300-101
ii 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101
Chapter 8
Software features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Software features GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
Introduction to GPRS software features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
PCU features: GSR4 supplemental release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–3
Point-to-point GPRS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–3
GPRS radio channel allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–5
Medium access mode – fixed/dynamic allocation . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6
Support of MS classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–7
GPRS coding schemes CS-1 and CS-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8
Dynamic adaptation of coding schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–9
Two phase packet access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–10
Frequency hopping of PDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–11
Power, interface, balancing, and sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–12
Power control: uplink/downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–12
Gb interface (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–13
PCU load balancing and sharing (Gb and BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–14
OMC-G GSR4 supplemental release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–15
GPRS OMC-R (PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–15
DataGen support for GPRS (supplemental) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–20
Software features GSN: GRPS IP network backbone features . . . . . . . . . . . . . . . . . . . . 8–21
GSN features summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–21
GPRS IP network backbone features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–22
Time server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–23
GPRS backbone (Gn) (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–24
PDN interface (Gi) (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–26
GSN packet data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–29
TCP/IP header compression; V.42bis data compression . . . . . . . . . . . . . . . . . . . . 8–29
QoS profile classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–30
Ciphering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–31
Secure tunnelling (Gi) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–32
GSN mobility management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–33
Attach support: class A, B, C mobile stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–33
Inter-SGSN handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–35
HLR interface (Gr) (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–36
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–37
PTP-CLNS (static IPv4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–38
GPRS charging features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
Account metering and collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
Charging gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–41
GPRS network support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Lawful intercept – phase 1 (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
GSN OA&M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–44
SNMP management interface (TCP/IP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–44
GSN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–45
PCU interface (Gb) (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–45
Software features OMC-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–46
OMC-G features summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–46

68P02903W01-O
FIELD TRIAL
GPRS-300-101
OMC workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–47

Introduction to the OMC-G workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–47
Using the OMC-G workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–47
Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–48
Introduction to the OMC-G navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–48
Using the OMC-G navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–48
Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–49
Introduction to the OMC-G map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–49
Using the OMC-G map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–49
Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–50
Introduction to the OMC-G table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–50
Using the OMC-G table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–50
Parameter views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–52
Introduction to the OMC-G parameter view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–52
Using the OMC-G parameter view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–52
Alarm Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–53
Introduction to the OMC-G alarm display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–53
Using the OMC-G alarm display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–53
Audible indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–54
Introduction to the OMC-G audible indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–54
Using the OMC-G audible indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–54
Alarm printing service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–55
Introduction to the OMC-G alarm printing service . . . . . . . . . . . . . . . . . . . . . . . . . . 8–55
Using the OMC-G alarm printing service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–55
User profile editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–56
Introduction to the OMC-G user profile editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–56
Using the OMC-G user profile editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–56
Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–57
Introduction to OMC-G help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–57
Using the OMC-G help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–57
Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–58
Introduction to OMC-G configuration management . . . . . . . . . . . . . . . . . . . . . . . . . 8–58
View and modify SGSN/GGSN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–58
Sanity check an SGSN/GGSN database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–59
Compare PCU and SGSN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–60
Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–61
Introduction to OMC-G performance management . . . . . . . . . . . . . . . . . . . . . . . . . 8–61
Viewing SGSN/GGSN statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–61
iv 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101
Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–62

Introduction to OMC-G fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–62
Using OMC-G fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–62
Load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–63
Introduction to OMC-G load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–63
Using OMC-G load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–63
15th Sep 99 System Information: GPRS Overview v

68P02903W01-O
FIELD TRIAL
GPRS-300-101
vi 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 Software features GPRS
Software features GPRS
Introduction to
GPRS software
features
This chapter describes the GPRS features as follows:
S PCU features.
S Power, interface, balancing, and sharing.
S OMC-G GSR4 supplemental release.
S Software features GSN: GPRS IP network backbone features.
S GSN packet data transfer.
S GSN mobility management.
S GPRS charging features.
S GPRS network support.
S GSN OA&M.
S GSN configuration.
S Operations and maintenance centre-GPRS.
S Software features OMC-G.
S OMC workspace.
S Navigator.
S Map.
S Table.
S Parameter views.
S Alarm display.
S Audible indicator.
S Alarm printing service.
S User profile editor.
S Help.
S Fault management.
S Load management.

68P02903W01-O
FIELD TRIAL
Software features GPRS GPRS-300-101
System overview
GPRS is a new service which enables a subscriber to send and receive data in an
end-to-end packet transfer mode within a GSM Network. This enables a more
cost-effective use of network resources for data transfer.
GPRS introduces a new device, at the BSS, known as the PCU. The PCU manages the
packet radio interface and also enables the interface from the BSS to the SGSN. The
PCU itself is managed by the existing OMC-R.
GPRS introduces two new network nodes:
The SGSN keeps track of the individual MS locations and performs security functions
and access control. The SGSN is connected to the BSS via a frame relay network.
The GGSN provides interworking with external packet-switched networks, and is
connected with SGSNs via an IP-based GPRS backbone network. This backbone
network includes the GSN CommHub and IP Support Server (ISS) nodes.
O&M services (load management, configuration management, fault management,
performance management, and security management) are provided for the GPRS
network through an OMC-G.
8–2 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 PCU features: GSR4 supplemental release
PCU features: GSR4 supplemental release
Point-to-point
GPRS service
Summary
GPRS provides a new set of bearer services supporting packet mode transmission. This
supporting low-speed and high-speed signalling, a data transmission technique with
improved efficiency compared with circuit based techniques. In the GSR4 supplemental
release, point-to-point GPRS service is supported.
Standards
This feature complies with GSM standards.
Description
GPRS enables the subscriber to send and receive data in an end-to-end packet transfer
mode, without utilizing circuit switched network resources. General characteristics where
GPRS offers superior performance compared with circuit technology include applications
where:
S The transmission of small volumes of data is frequent.
S The transmission of large volumes of data is infrequent.
S The time between successive transmissions greatly exceeds the average transfer
delay.
In its initial release, the network supports implementation of one to eight timeslots on a
single carrier per cell for the transmission of GPRS traffic. This enables the network
operator to optimally size the network for efficient support of a mix of GPRS and voice
traffic. To support this mix, each timeslot on a GPRS carrier can be configured as
dedicated to circuit traffic, or GPRS traffic, or can be configured as switchable between
the two. In the case of switchable timeslots, GPRS traffic has precedence over circuit
switched traffic on the last remaining timeslot.
In the GSR4 supplemental release, the GPRS the network supports cell reselection
mode NC0, as defined by ETSI. In this mode, the network provides the Mobile Station
(MS) with information regarding the quality and signal strength of the link. The MS then
uses this information to determine whether to request a cell reselection based upon
signal strength of neighbour cells. GPRS carriers can also be configured to support the
GSM discontinuous transmission feature, defined for circuit switched traffic in an effort to
conserve MS battery life. Network operation mode II is also supported, in which the
network uses the CCCH paging channel for both CS and GPRS paging.
Benefits
GPRS provides a resource efficient method for delivery of data services, leading to direct
revenue-generating capabilities, as well as indirect benefits such as reduced churn.

68P02903W01-O
FIELD TRIAL
PCU features: GSR4 supplemental release GPRS-300-101
Applications
Applications, their ease of use, and value to the end user or operation, are the key to
success for GPRS. With the advent of GPRS, for the first time a reliable high bit rate
cellular medium is available for commercial exploitation. In addition, increased
competition for new customers and the commoditization of basic cellular services is
driving operators to look for means of increasing value to the consumer and return for the
operator.
The highest level of value-added can be found by deploying applications that enable
businesses to differentiate in their own markets. Some of the key applications that can be
delivered over point-to-point GPRS service in its initial release, and further into the future,
include email, corporate database access and file transfer, diary management, and
E-commerce.

Implementation of a GPRS network requires changes to several components of a GSM
network, including new mobile terminals capable of supporting GPRS, and modifications
of the MSC, HLR and billing systems. Serving and gateway GPRS support nodes are
required, along with an Operations and Maintenance Centre-GPRS (OMC-G) to manage
the network. Upgrades to the Motorola BSS include BSS software and incorporation of
packet control unit to provide packet connections between the BTS and the serving
GPRS support node. At the BTS, no retrofit is required for DRCU2 and later carriers.
8–4 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS radio
channel
allocation
Summary
Dynamic allocation of radio resources allows an operator to configure the radio resources
of a cell as dedicated circuit switched, dedicated GPRS, or switchable between circuit
switched and GPRS. This enables efficient use of air interface resources, and allows an
operator to tailor the cellular network to the packet data traffic requirements of the
operator.
Standards
Description
This feature provides the flexibility for a cell supporting GPRS to allocate a given radio
resource to handle circuit switched voice/data or packet data as required. A radio
resource can be configured as dedicated to circuit switched traffic, packet data traffic, or
switchable between the two. In the latter case, the traffic demands of the network
determine the type of traffic handled by the air interface timeslot. This provides the
operator with a degree of flexibility when configuring a GPRS capable network, and also
facilitates maximum utilization of resources. In a GPRS capable cell approaching
congestion, GPRS traffic is given preference over the last switchable radio resource.
Benefits
The ability to dynamically share radio resources between GPRS packet data traffic and
GSM circuit switched traffic allows the operator to maximize the traffic handling capability
of the available network resources.
Applications
This feature is essential where limited radio resources are available and efficient use of
those resources is desired.

This feature requires a GPRS capable GSM BSS.

68P02903W01-O
FIELD TRIAL
Medium access
mode –
fixed/dynamic
allocation
Summary
The medium access control procedures include the functions related to the management
of the common transmission resources. These include the packet data physical channels
and the radio link connections on packet data physical channels.
Standards
Description
The medium access control procedures support the assignment of radio resources to
mobile stations for transmission of GPRS protocol data units (PDUs). In all cases, the
network determines the assignment, and transmits this information for a given radio
resource to all mobile stations sharing that resource. Two methods of medium access
control are supported in the GSR4 supplemental release, dynamic and fixed.
In dynamic medium access allocation, three Uplink State Flag (USF) bits are transmitted
in every downlink block. Through these USF bits, the network instructs one of the MSs
sharing a timeslot to transmit data on the uplink. Mobiles monitor the channel for their
instruction to transmit. The advantage offered by dynamic allocation is flexibility in the
assignment of the air interface resource.
The fixed allocation uses bitmaps to convey to the MS when the MS is allowed to
transmit. The fixed allocation mechanism has several key advantages. These are:
S Enables use of half-duplex MSs.
S Improved downlink power control.
S Enables higher uplink throughput.
The Medium Access Control (MAC) procedures support the provision of Temporary Block
Flows (TBFs) allowing the point-to-point transfer of signalling and user data between the
network and a mobile station. A temporary block flow is a physical connection used by
the two entities to support the transfer of GPRS protocol data units (PDUs) on packet
data channels (PDCH). A TBF is temporary, and is maintained only for the duration of the
data transfer.

8–6 15th Sep 99

68P02903W01-O
FIELD TRIAL
Support of MS
classes
Summary
In the GSR4 supplemental release, the GPRS network supports multislot mobile classes
1-12 (semi-duplex), and 19-20 (half-duplex).
Standards
Description
In its initial release, the GPRS network supports multislot MS classes 1-12, 19 and 20.
This includes support of both semi-duplex (classes 1-12) and half-duplex (classes 19 and
20). Semi-duplex MSs can support up to 4 TimeSlot (TS) downlink and 1 TS uplink, or 2
TS downlink and 2 TS uplink. Half-duplex MSs, can support 6 TS downlink or 2 TS
uplink, or 1 TS downlink and 4 TS uplink (fixed allocation MAC mode).
GSM voice MSs are semi-duplex. The direction of speech information transfer alternates
rapidly, about 210 times per second, between the uplink and the downlink directions. This
rapid switching emulates a full duplex speech connection.
The basic GPRS MS are semi-duplex as well. These MSs spend a significant proportion
of time switching directions, which significantly limits their total throughput. For example,
the most capable semi-duplex MS can receive 4 timeslots while transmitting 1 timeslot,
or receive 3 timeslots while transmitting 2, etc.
The half-duplex MS is a semi-duplex MS with the added capability of also being able to
perform half-duplex GPRS procedures. The half-duplex MS takes advantage of the fact
that GPRS does not require the rapid switching of directions provided by the semi-duplex
MSs. In fact, switching directions 2 or 3 times per second is adequate. By switching
directions much less often, the half-duplex MSs can provide about 38% more total
throughput than semi-duplex MSs, and can provide nearly double the throughput in a
single direction.
The half-duplex MSs provide the following advantages:
S Nearly twice the useful throughput than the most capable semi-duplex MS.
S Twice the talk time of a full duplex MS with the same throughput.
S Small incremental complexity over the semi-duplex MSs.
Benefits
By supporting multiple classes of multislot MSs, GPRS throughput can be maximized
while preserving talk time. Also, through the support of multiple MS classes, the operator
is able to meet the data throughput requirements of a broad base of subscribers.


68P02903W01-O
FIELD TRIAL
GPRS coding
schemes CS-1
and CS-2
Summary
Coding schemes CS-1 and CS-2, providing 9.05 kbit/s and 13.4 kbit/s respectively, are
supported. Coding schemes CS-3 and CS-4 will be supported in a later release.
Standards
Description
Table 8-1 provides the throughput capability for each of the GPRS coding schemes.
Table 8-1 Throughput capability for GPRS coding schemes

Coding scheme User data rate Error correction
CS-1 9.05 kbit/s High
CS-2 13.4 kbit/s Medium
CS-3 15.6 kbit/s Low
CS-4 21.4 kbit/s None
Coding schemes 1 and 2 are supported in the GSR4 supplemental release. Both provide
a degree of forward error correction, depending upon the prevailing RF conditions.
Through support of these two coding schemes, a higher throughput is enabled for MSs
operating in those areas of the network with excellent RF coverage, based upon reduced
requirement for error correction. In those areas of the network where RF coverage
suffers, error correction can be boosted maintaining a quality transmission, at a slightly
reduced throughput.
Benefits
This feature facilitates maximum data throughput per channel.

8–8 15th Sep 99

68P02903W01-O
FIELD TRIAL
Dynamic
adaptation of
coding schemes
Summary
This feature enables the network to change the coding scheme between MS
transmissions based upon the radio characteristics of the link. Movement between CS-1
and CS-2 is supported in the initial GPRS release.
Standards
Description
During a GPRS transmission, the network monitors the characteristics of the radio link.
Based upon these measured characteristics, the network is able to change the coding
scheme in use in order to maximize throughput of the link. As an example, a MS with a
high-quality radio connection can maximize throughput with minimal error correction
using CS-2. If the quality of the link deteriorates, the number of retransmissions required
would begin to increase due to the inadequate level of forward error correction. In this
scenario, there would eventually be a point at which the throughput enabled by CS-1
would exceed that of CS-2, based upon the fact that the improved error correction would
reduce the number of retransmissions.
Benefits
This feature allows the network to maximize data throughput per channel under various
RF conditions.
Compatibility / Dependencies / Network elements affected


68P02903W01-O
FIELD TRIAL
Two phase
packet access
Summary
The GSR4 supplemental release of GPRS supports two phase packet access. This
allows an exchange of information to take place between the MS and the network prior to
assignment of resources.
Standards
Description
The purpose of the packet access procedure is to establish an uplink transmission to
support the transfer of packet data units from the MS to the network. The packet access
procedure can take place in either one or two phases. Motorola supports the two phase
packet access procedure in the GSR4 supplemental release. In this procedure, the MS
requests a packet resource on the random access burst. The network provides an
immediate assignment of a single block, to which the MS responds with its radio access
capability (classmark) and MS ID, and the number of octets of user data. Based upon
this information, the network assigns a resource for the uplink transmission.
Benefits
A two phase uplink access procedure minimizes the risk of assignment errors, and helps
to ensure efficient use of resources by providing the network with key data prior to
assignment of a channel.

8–10 15th Sep 99

68P02903W01-O
FIELD TRIAL
Frequency
hopping of PDCH
Summary
The GPRS network support frequency hopping of the packet data channel (PDCH).
Standards
Description
Frequency hopping is one of the Motorola key techniques to improve capacity and quality
in a highly loaded GSM network. These same benefits are realized when frequency
hopping is implemented on GPRS carriers. For GPRS, all packet data channels assigned
to a single MS are included in the same frequency hopping system, which specifies the
frequencies over which the timeslots hop and the hopping sequence.
The principle of frequency hopping is as simple as changing the frequency used in
transmission at regular intervals. It has been included in GSM specifications mainly in
order to deal with two specific problems which can affect transmission quality:
S Multipath fading.
S Interference.
Multipath fading immunity can be increased by exploiting its frequency selectivity. By
using different frequencies, the probability of being continuously affected by fading is
reduced, so the transmission link quality is improved. This improvement is much more
noticeable for slow moving MSs.
Interference coming from neighbour cells transmitting the same or adjacent frequencies
can be reduced by using frequency hopping. This is because calls are moving through
different frequencies that are not equally affected by interfering signals.
Benefits
The benefits of frequency hopping include improved quality and system performance.
Cost reductions are also possible. Fewer sites may be needed, and frequency planning
and optimization activities are simplified.


68P02903W01-O
FIELD TRIAL
Power, interface, balancing, and sharing GPRS-300-101
Power, interface, balancing, and sharing
Power control:
uplink/downlink
Summary
The power control feature enables power adjustment over the radio link based upon the
characteristics of the link.
Standards
Description
Power control is supported over the radio interface on both the uplink and downlink.
Power adjustments are directed by the network based upon the measured characteristics
of the radio link.
Benefits
This feature allows the network to maximize data throughput per channel, while
minimising interference levels.

8–12 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Power, interface, balancing, and sharing
Gb interface
(optional)
Summary
The PCU interface or Gb interface provides connection between the BSS and the SGSN.
Standards
Description
The Gb interface connects the BSS/PCU to the SGSN, allowing the exchange of
signalling information and user data. The Gb interface allows many users to share the
same physical resource. To facilitate cost-effective transmission, the Motorola GPRS
offering also supports infrastructure sharing, which allows the operator to carry A
interface (CS) and Gb interface (packet) traffic on a single E1 using the nailed
connections capability. These two features enable a cost-effective transmission solution
in a GPRS capable network. As GPRS traffic increases, it may become appropriate to
dedicate one or more span lines to GPRS traffic. To accommodate this scenario, the
network also supports a direct connection between the PCU and the SGSN.
established between the SGSN and BSS. PDUs from many users are multiplexed on
these virtual circuits. The virtual circuits may be multi-hop, and traverse a network of
frame relay switching nodes. Frame relay is used for both signalling and data
transmission.
Benefits
The Gb interface while providing connectivity between the BSS and SGSN, helps
improve the operability of the GPRS system through redundancy and load sharing.
Timeslots on a single E1 can be configured to support either Gb or A interface, providing
the operator with transmission line cost savings.
Applications
The Gb interface supports communications between the PCU and SGSN.


68P02903W01-O
FIELD TRIAL
Power, interface, balancing, and sharing GPRS-300-101
PCU load
balancing and
sharing (Gb and
BTS)
Summary
This feature provides high reliability through efficient resource management. It also
manages the movement of resources from one part of a BSS to another to meet varying
peak capacity requirements in a network designed primarily for coverage.
Standards
Description
The primary objective of this feature is to economically support the use of multiple
timeslots per cell, with no delay penalty, in a GPRS BSS configured for coverage rather
than capacity. A coverage based GPRS network provides coverage over a large number
of cells, and assumes a low average throughput per cell. This feature allows a network to
effectively move or enable resources as needed throughout a BSS to handle traffic
peaks.
Another objective of this feature is to provide high reliability. During periods when the
designated resource is not required due to a failure, the spare resource can be used to
manage peak loads. This is accomplished by means of load sharing of E1 link lines and
other key components within the BSS. A GPRS BSS/PCU can be configured to support a
maximum capacity of 270 active timeslots.
In the case of link line or equipment failures, the GPRS BSS provides load sharing of the
following resources:
S E1 link lines on the BTS-BSC link.
S E1 links on the BSS-PCU link.
S PRP (RLC/MAC) boards within the PCU.
S E1 link lines on the Gb (PCU-SGSN) interface.
Benefits
This feature provides savings through the efficient use and management of a limited set
of resources. Combined with the GPRS feature GPRS radio channel allocation, this
feature allows an operator to configure switchable circuit/packet timeslots across a
network to handle peak loads. It also provides a cost-effective approach to high reliability.
Applications
This feature is essential in networks where limited resources are required to support
varying throughput requirements cost effectively.

8–14 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 OMC-G GSR4 supplemental release
OMC-G GSR4 supplemental release
GPRS OMC-R
(PCU)
Summary
The OMC-R PCU support for GPRS is a fully integrated solution within the existing
OMC-R architecture. It consists of support for the PCU as part of the BSS in the
following key management areas:
S Fault management.
S Load management.
S Security management.
S On-line help.
Standards
ETSI technical report 10.18 covering O&M for GPRS. This standard is still being
formulated and Motorola aims to achieve the maximum compliance.

68P02903W01-O
FIELD TRIAL
OMC-G GSR4 supplemental release GPRS-300-101
Description: fault management

The existing OMC-R fault management application is updated to support new GPRS
BSS/PCU alarms and events.
The OMC-R map is extended to cover the PCU, facilitating both fault management and
configuration management. As can be seen in Figure 8-1, the PCU is represented as a
discrete entity on the map within the BSS structure. Both PCU and dummy GSN icons
are identifiable by new symbols together with 01 representing data.
Figure 8-1 OMC-R overview map showing PCU representation
OMC-R fault management

The OMC-R fault management application provides the following support for the PCU:
S Alarm window, to view alarms/events.
S Handling/unhandling of alarms.
S Clearing of alarms.
S Removal of cleared alarms.
S Alarm/event history reporting.
Alarms associated with the PCU are shown alongside the normal BSS alarms. Alarms
can be handled in the same way as the existing OMC-R, via a popup menu. There is also
some support for the consolidation of PCU alarms as shown by the subscriber impact
statement within the alarm message.
The OMC-R fault management application also provides support for the following:
S Subscription to specified alarms/events.
S Filtering (blacklisting) of specified alarms/events.
New device classes have been added for the PCU components, such as DPROC. Both
subscriptions and filtering can be enabled on this basis. Specific subscriptions could be
established for GPRS devices, or they can be handled as part of the overall GSM
network, depending on a particular network operators method of operation.
8–16 15th Sep 99

68P02903W01-O
FIELD TRIAL
Configuration management
The existing OMC-R configuration management application has been updated to support
GPRS BSS and PCU configuration. The various functions can be accessed from the
navigation tree.
OMC-R configuration management functionality is supported for the GPRS elements:
S OMC-R GUI support for creation (with default parameter values) of PCU.
S OMC-R GUI support for deletion of PCU.
S OMC-R GUI support for creation/deletion of devices under the PCU.
S OMC-R GUI support for view/modify of GPRS BSS and PCU parameters.
S Propagation of related cell parameter values within cells.
In order to provide effective configuration management of the GPRS parts of the network
within the existing structure of the GUI, several objects now have specific GPRS
parameters. These include BSS, site, cell, LCF, and RTF. In addition, Motorola has
provided a new class of GPRS objects for specific GPRS parameters. Figure 8-2 shows
the navigation tree with SGSN and BSS PCU indicated on it. The PCU is treated as
having an equivalent status to the site object within the hierarchy.
Figure 8-2 Navigation tree showing GPRS elements
Support is also provided for audits, and the PCU can be specifically audited.

68P02903W01-O
FIELD TRIAL
Cell parameter propagation

Another key aspect of configuration management for which there is support for GPRS
PCU is cell parameter propagation. This operates in much the same way as existing
functionality. Figure 8-3 shows some typical GPRS specific parameters selected.
Figure 8-3 GPRS cell parameter propagation setup screen
Performance management
The existing OMC-R performance management application has been
updated to support new GPRS BSS and PCU statistics. The OMC-R
performance management application provides the following
functionality:
S Background statistics sent to the OMC-R in intervals of 30 or 60 minutes.
S Background statistics can be displayed in graphical format.
S Background statistics can be displayed in tabular format.
S Key statistics can be derived from raw statistics.
S Custom statistics can be derived from raw & key statistics.
S PM reports can be scheduled.
8–18 15th Sep 99

68P02903W01-O
FIELD TRIAL
Load and database management

The PCU load/database is included as part of the standard BSC load/database download
from the OMC-R to the BSC. Thus the existing OMC-R load and database management
functionality applies to GPRS PCU. This consists of:
S Install of software load/database.
S Delete of software load/database.
S Download of software load/database.
S Activate (swap) of new software load/database.
S Upload of database.
Security management
The existing OMC-R access control applies to the GPRS PCU, giving the following:
S Access control must be administerable by the security administrator.
S Access control must be on a per-operation basis; for example operator1 must not
be allowed to perform configuration operations.
The security management appears exactly the same as the existing screens.
On-line help
Context sensitive on line help is available from OMC-R GUI, covering topics related to
the PCU in exactly the same way that existing OMC-R help is available.
Benefits
These are:
S Fully integrated PCU means that upgrading a network or portion of a network to be
GPRS capable requires minimum operator training.
S Use of familiar screens and menus.
S Functionally rich solution from the outset, with a full range of features.
S High level control of key GPRS timeslot usage, greatly easing overall management
of the data side of the network.
Applications
The OMC-R PCU functionality is required by any network operator upgrading all or
portions of a Motorola BSS subsystem to be GPRS capable.

These features require the implementation of Motorola GPRS BSS and PCU elements
and functionality, together with existing OMC-R. There may be a requirement to upgrade
existing OMC-R hardware, depending on the size of the data network to be implemented.
There is no dependency on having a Motorola GSN.

68P02903W01-O
FIELD TRIAL
DataGen support
for GPRS
(supplemental)
Summary
DataGen support of the BSS/PCU feature.
Description
DataGen supports all BSS MMIs required for BSS/PCU features, including:
S Revgen: revgen a BSS CM binary database object to populate the DataGen
database.
S GCMD (command generator): recreates the BSS MMI scripts supporting PCU
from the revgened binary object. All MMIs including PCU support is retained.
S Difference reporter: reports difference between two BSS CM databases that
contain PCU.
S Sysgen compiler: compiles MMI scripts with PCU support to produce a new CM
binary database.
Benefits
Simplifies large-scale changes of Motorola GPRS PCU networks.
Applications
This feature is applicable in all Motorola GSM networks with PCU functionality.

BSS, PCU.
8–20 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Software features GSN: GRPS IP network backbone features
Software features GSN: GRPS IP network backbone features
GSN features
summary
The following features are outlined under GSN features:
S Domain name server (DNS).
S Time server.
S GPRS backbone (Gn).
S PDN interface (Gi).
S TCP/IP header compression; V.42bis data compression.
S QoS profile classes.
S Ciphering.
S Secure tunnelling (Gi).
S Attach support: class A, B, C MSs.
S Inter-SGSN handover.
S HLR Interface (Gr).
S Authentication.
S PTP-CLNS (Static IPv4.
S Charging gateway.
S Lawful intercept – phase 1.
S SNMP management interface (TCP/IP).
S PCU interface (Gb).
S GPRS Operations and Maintenance Centre-GPRS.

68P02903W01-O
FIELD TRIAL
Software features GSN: GRPS IP network backbone features GPRS-300-101
GPRS IP network
backbone
features
Summary
A Domain Name Server (DNS) function maps logical names to network layer Internet
Protocol (IP) addresses.
Standards
This feature is a standard internet function and is compliant with prevailing GSM
standards.
Description
A DNS server is needed 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). To
prevent network thrashing, the GSN nodes temporarily store the mapping of logical
names and IP addresses in an address cache.
The DNS function resolves logical GSN names to GSN addresses. This allows the
resolution of any names for GSN and other GPRS nodes within the GPRS backbone of
the PLMN. DNS feature functionality applies to all the GPRS network elements and
nodes within the network.
Benefits
This feature allows the network administrator to assign logical equipment names to IP
interfaces, and to map these names to their IP addresses. This feature also provides
support for a distributed network, and helps to break out the domain name server
functionality so external DNS servers can be used to connect to the GPRS network.
Applications
This feature is provided as an integral part of the Motorola GPRS offering, and is
essential to convert logical names to internet addresses.

This feature has no external hardware or software dependencies.
8–22 15th Sep 99

68P02903W01-O
FIELD TRIAL
Time server
Summary
The time server synchronizes the time across all GSN components in the data network.
Standards
This feature is compliant with all GSM standards and IP protocol standards as defined in
IETF RFC-1305.
Description
The Time Server (TS) accurately maintains the time-of-day for the GSN. The TS
correlates management information across the GSN system so that all GPRS
components operate on a common time base. In addition, accurate timing is needed to
time stamp traffic statistics, fault logs, and charging records.
The TS maintains the system components within five seconds of actual Greenwich Mean
Time (GMT) and is based upon the Network Time Protocol (NTP). The time server
synchronizes the ISS, GGSN and SGSN components in the GSN network.
Benefits
Time server maintains network time synchronization across all elements connected to the
GSN for proper operations.
Applications
This feature is essential for all the GPRS GSN components to operate on a common
time base.

This feature has no Motorola hardware or software dependencies. However, it requires
an external NTP server on the internet that must be configured and synchronized.

68P02903W01-O
FIELD TRIAL
GPRS backbone
(Gn) (optional)
Summary
The GPRS backbone functionality serves as a backbone IP router, and is provided by the
GSN Communications Hub (GSN CommHub). This router provides the indirect data
paths, called the Gn interface, between the PLMN intranet nodes such as the GGSN or
SGSN. It also performs the tunnelling and routeing functions such as UDP tunnelling,
static routeing, and dynamic routeing, based on Open Shortest Path First (OSPF).
Standards
This feature is compliant with all current prevailing TCP/IP standards and GSM standards
as defined by ETSI.
Description
In the Motorola GPRS implementation, the GSN CommHub provides the functionality of
the GPRS backbone IP router, gateway IP router, and IP firewall. The GSN CommHub is
an off-the-shelf router, and is specific to the Motorola implementation of the GSN. It is the
central connection point for all communication within GSN elements and between the
GSN and outside network elements.
The GSN CommHub, which serves as a backbone IP router, provides the indirect data
paths, called the Gn interface, between the PLMN intranet nodes such as the GGSN or
SGSN. It reduces the number of direct physical channels needed by a GSN to
communicate with its peers. Since the backbone IP router performs no GPRS specific
functions, and is used only to route IP datagrams between the SGSN and GGSNs, each
GSN may have direct physical connections to two IP routers for reliability.
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 GSN CommHub
implements the inter-domain IP routeing 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 a 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.
The software protocols and physical connection that are needed to connect the GGSN to
the SGSN are also 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 and TCP/IP stacks. GTP defines both signalling (control)
and data transfer functions between two GSNs. GTP is specified in GSM 09.60.
In this document, the Gn interface is divided into two parts, the Gi-g, which represents
the GGSN side of the Gn interface, and the Gi-s, which represents the SGSN side of the
Gn interface. A standard routeing protocol OSPF is used between the IP ports on the
Gi-I interface processors and the gateway IP router. Alternatively, static IP routing tables
may be configured in both the gateway IP router and the Gi-i interface processor boards.
Benefits
GPRS backbone interface performs the tunnelling and routing functions such as UDP
tunnelling, static routeing, and dynamic routeing based on OSPF, thereby acting as a
central connection point for all communication within GSN elements and the outside
network.
8–24 15th Sep 99

68P02903W01-O
FIELD TRIAL
Applications
The GPRS backbone encompasses the functions of the GPRS backbone IP router,
gateway IP router, and IP firewall. This feature is essential for operation of GPRS
network.


68P02903W01-O
FIELD TRIAL
PDN interface
(Gi) (optional)
Summary
This feature is an integral part of the GPRS network and is essential for connecting the
GGSN to the Packet Data Network(PDN). Network interworking is required whenever a
PLMN supporting GPRS and any other network are involved in the execution of a GPRS
service request. PDN (Gi) interface supports both transparent and non-transparent
access.
Standards
This feature is compliant with all current prevailing GSM standards and internet
standards.
8–26 15th Sep 99

68P02903W01-O
FIELD TRIAL
Description
The software protocols and physical connection needed to connect the GSN (GGSN) to
an external packet data network are defined by the Gi interface standard. In the Motorola
implementation, the Gi interface is divided into two components, the Gi-e which lies on
the external network side of the gateway IP router, and the Gi-i which is the internal Gi
interface between the GGSN and the gateway.
Implementation of this feature helps support the following internet working functions on
the data network: border gateway, network-controlled screening, transport access, and
network address translation. Network controlled screening acts as a firewall preventing
unauthorized use. Network address translation converts one address to another address
of a different type. Address translation may be used to convert an external network
protocol address into an internal network address that can be used for routeing packets
within and between the PLMN(s). Address mapping is used to map a network address to
another network address of the same type for the routeing and relaying of messages
within and between the PLMN(s), for example to forward packets from one network node
to another.
Transparent access mode allows the GSN to connect to the internet, intranet, or ISP.
This service includes MS to external network encryption and dynamic addressing. This
service is transparent because the MS does not send any authentication request
information at PDP context activation, and the GGSN does not take any part in the user
authentication/authorization process.
Non-transparent access mode allows the GSN to connect the internet, intranet, or ISP.
This service includes user authentication, using a Dynamic Host Control Protocol
(DHCP), MS to external network encryption, and dynamic addressing. This service is
non-transparent because the MS sends authentication request information at PDP
context activation, and the GGSN forwards this information to a DHCP service during the
user authentication/authorization process.
The GPRS network GGSN requires four high-level functions in order to provide secure,
non-transparent access to a foreign IP network, such as an ISP or private corporate
intranet:
S Authentication, a means to authenticate the GPRS user to the foreign IP network.
S Addressing, a means to acquire an IP address from the foreign network IP address
domain.
S Routeing, a means to transfer IP packets between the GPRS network and the
foreign network.
S Confidentiality, a means to encrypt user data sent between the GPRS network and
the foreign network.
The authentication and addressing functions are provided by the radius protocol and
DHCP. Routeing and confidentiality functions are provided by means of the IPSec
Encapsulation Security Payload (ESP) tunnelling protocol. ESP provides data
confidentiality and integrity by encrypting IP packets between the GPRS network and the
peer data network (such as a private corporate intranet).
Benefits
PDN interface allows the connection of GSN to external packet networks. Transparent
access functionality allows subscribers to transparently connect to networks outside in
the data world. Using non-transparent access feature, operators can provide their
subscribers with more secure means of connecting to the external data networks.
Applications
This feature provides the interface that is needed to successfully connect a GGSN to
external public switched networks, and is provided as a standard offering.

68P02903W01-O
FIELD TRIAL

8–28 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN packet data transfer
GSN packet data transfer
TCP/IP header
compression;
V.42bis data
compression
Summary
This GPRS feature provides compression of the total TCP/IP header when an
IP-datagram is used within the context of a TCP connection. GPRS also provides V.42
bis data compression.
Standards
This feature is compliant with prevailing GSM standards and TCP/IP standards.
Description
The compression function optimizes use of radio path capacity by transmitting as little of
the Service Data Unit (SDU), that is the exterior PDP PDU, as possible, while at the
same time as preserving the information contained within it. Transfer of the minimum
amount of data is made possible between the SGSN and MS through compression
techniques.
Compression is a technique used to compress redundant protocol control information
and user data. This may include for example TCP/IP header compression and V.42 bis
data compression. Compression may be performed independently for each QoS delay
class and precedence class. When several network layers use the same QoS delay class
and precedence class, one common compressor is used for these network layers.
Compression parameters are negotiated between the MS and the SGSN. Compression
is an optional SNDC function.
Benefits
Compression techniques optimize the use of radio resources.
Applications
This feature is provided as a standard offering on Motorola GSN network equipment, and
compression techniques must be employed on all IP packets and datagrams.


68P02903W01-O
FIELD TRIAL
GSN packet data transfer GPRS-300-101
QoS profile
classes
Summary
This feature implements all of the Quality of Service (QoS) features and capabilities. This
functionality makes it possible to respond to local data traffic conditions adaptively. GPRS
must include the functionality to increase or decrease the amount of radio resources
allocated to GPRS on a dynamic basis, as specified by the operator.
Standards
This feature is compliant with prevailing GSM standards.
Description
A quality of service profile is associated with each Packet Data Protocol (PDP) context.
The QoS profile is considered to be a single parameter with multiple data transfer
attributes. These attributes include precedence class, delay class, reliability class, peak
throughput class, and mean throughput class. In GSN 1, the SGSN supports only delay
class 4, unspecified service. The SGSN supports all enhanced QoS classes in future
releases.
A quality of service profile, negotiated between the MS and the SGSN, is associated with
every PDP context. The QoS profile is considered to be a single parameter with multiple
data transfer attributes. It defines the quality of service expected in terms of the following
class attributes:
S Precedence, which indicates the relative importance of maintaining the service
commitments under abnormal network conditions.
S Delay, which indicates packet delays.
S Reliability, which specifies the residual error rates.
S Peak throughput, the maximum expected throughput measured at the Gi and R
interfaces.
S Mean throughput, the mean throughput measured at the Gi and R reference
points.
GPRS must satisfy, within the constraints introduced by the MS radio environment, the
QoS requirements of the interworked-with network.
Benefits
The feature provides a method to offer better quality services and varied services to the
users. Operators are able to define the quality of service offered to different classes of
subscribers based on a variety of parameters.
Applications
This feature allows operators to set the quality of service levels offered to different
groups of subscribers. It can be efficiently used to differentiate different kinds of service
offered.

8–30 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN packet data transfer
Ciphering
Summary
The ciphering feature provides an additional level of security to the GPRS data network.
The SGSN performs cipher setting procedures based on the same algorithms, keys, and
criteria as in existing GSM. GPRS uses a ciphering algorithm optimized for packet data
transmission.
Standards
This feature is compliant with all current prevailing GSM standards.
Description
Ciphering is a security feature that provides user identity confidentiality and user data
confidentiality on the network. In contrast to the scope of ciphering in existing GSM (a
single logical channel between BTS and MS), the scope of GPRS ciphering is from the
ciphering function at the SGSN to the ciphering function in the MS (see Figure 8-4).
MS BTS + BSC SGSN
SCOPE OF GPRS CIPHERING
SCOPE OF EXISTING GSM CIPHERING
Figure 8-4 Scope of GPRS ciphering
Ciphering is done in the LLC layer, and from the perspective of the existing GSM
MS-BTS radio path. An LLC PDU is transmitted as plain text.
The ciphering algorithm to be used for GPRS ciphering complies with the requirements
for the GPRS ciphering algorithm. The TDMA frame number is not known at the SGSN.
Therefore, a logical link control frame number may replace the TDMA frame number as
an input to the algorithm. The standard key management procedures for the Kc is used.
Benefits
Ciphering provides confidentiality for subscribers on the network. Because there is a
unique key involved to decode any user data, a higher level of data security exists for the
subscribers.
Applications
This feature is an integral part of the GPRS network, and the functionality is provided on
the GSN.


68P02903W01-O
FIELD TRIAL
GSN packet data transfer GPRS-300-101
Secure
tunnelling (Gi)
Summary
This feature enables the GSN to use a virtual private network (VPN) to connect the
GPRS network to an internet service provider (ISP).
Standards
This feature is compliant with the established GSM standards.
Description
A Virtual Private Network (VPN) is a network constructed using public transmission
facilities to interconnect nodes within a private network. For example, there are a number
of systems in which operators create networks using the internet as the medium for
transporting data. These systems use encryption and other security mechanisms to
ensure that only authorized users can access the network and that the data cannot be
intercepted. Secure tunnelling feature provides operators with the capability to connect to
these types of private networks.
Benefits
This feature allows operators to provide their users with the capability of connecting to
outside networks by deploying highly secure mechanisms and internet compatible
standards.
Applications
This feature can be used by subscribers to connect to other private networks, and is
available as a standard on Motorola GSN systems.

8–32 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN mobility management
GSN mobility management

Attach support:
class A, B, C
mobile stations
Summary
The GPRS-Attach support feature connects a Mobile Station (MS) to the PLMN for the
purpose of using the GPRS-Point-To-Point (GPRS-PTP) feature. This feature allows
three different classes of mobiles, classes A, B and C, to attach to the GPRS network,
depending on the MS capabilities and subscription levels.
Standards
This feature is compliant with the ETSI defined GSM standards as stated in GSM 07.60
and GSM 02.60 specifications.
Description
GPRS-Attach is performed when the MS indicates its presence to the PLMN for the
purpose of using the GPRS PTP service. This can be immediately after the MS has been
switched on, or later as the user decides to use the GPRS services. The MS identifies
itself with its GSM identity (IMSI, TLLI). A GPRS-Attach must be successfully performed
only if the subscriber has a valid GPRS subscription. It is assumed that the user does
not, under normal circumstances, initiate a GPRS-Attach without first ensuring that the
data handling capability necessary in the terminating equipment has been activated.
The GPRS standards have defined several new MS classes that specify distinct data
capabilities. In compliance with the defined standards, Motorola GPRS network allows
these new devices to simultaneously access circuit switched and packet data services.
This also permits access to multiple GPRS timeslots. The GPRS MS classes are class
A, class B, and class C.
Class A allows the simultaneous attachment, activation, monitoring, and invocation of
circuit switched and packet data services. A MS user can make and/or receive calls on
the two services simultaneously.
Class B supports the simultaneous attachment, activation, and monitoring of circuit
switched and packet data services. Simultaneous GPRS and circuit switched traffic is not
supported. The MS user can make and/or receive calls on either of the two services
sequentially, but not simultaneously. The selection of the appropriate service is
performed automatically.
Class C supports only non-simultaneous attachment of circuit switched and packet data.
When both services (GPRS and circuit switched) are supported, a class C MS can make
and/or receive calls only from the manually or default-selected service, that is either
GPRS or circuit switched service. The status of the service which has not been selected
is detached, that is not reachable. The capability for GPRS-attached class-C MSs to
receive and transmit SMS messages is optional. The network supports SMS message
reception and transmission for GPRS-Attached class-C MSs.
The SGSN manages the access and attachment of GPRS MSs to the GPRS network.
The SGSN treats all MSs as class C devices. The SGSN does not support the class A
and class B features that combine circuit switched and packet control messages. Also,
the SGSN does not support the class B features associated with circuit switched paging.
The BSS treats class A MSs like class B MSs.
Benefits
This feature allows different classes of MSs with distinct capabilities to connect to the
GPRS network.

68P02903W01-O
FIELD TRIAL
GSN mobility management GPRS-300-101
Applications
This feature can be used by operators to provide different levels of service and
subscriptions to their subscribers. It presents a unique revenue-generation opportunity for
operators.

This feature has no external hardware or software dependencies. However it is
dependent on the type of MSs used by the subscribers and their capabilities.
8–34 15th Sep 99

68P02903W01-O
FIELD TRIAL
Inter-SGSN
handover
Summary
This feature provides mobility management between two cells serviced by different BSCs
and SGSNs, thus providing more flexibility to the MSs.
Standards
This feature is compliant with GSM standards.
Description
Through this feature, the SGSN must support MS mobility management between two
cells serviced by separate BSCs and SGSNs. This requires communications functions
between the two SGSNs involved.
Benefits
This feature helps in providing an improved level of service to subscribers. It enhances
the quality of service offered by allowing the MSs to move over to another SGSN when a
handover becomes necessary.
Applications
This feature is provided as a standard offering on the Motorola GPRS GSN system.


68P02903W01-O
FIELD TRIAL
HLR interface
(Gr) (optional)
Summary
HLR interface is a feature that provides connectivity between the SGSN and the Home
Location Register (HLR). This interface is also referred to as the Gr interface.
Standards
Description
The Gr interface connects a GGSN to the HLR. The Gr interfaces use the 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 of both the
local and foreign PLMNs. In order to determine the SS7 point code of the HLR, an SCCP
Global Title Translation (GTT) is performed on the IMSI. This function may be performed
in either the SGSN, or the STP, or both in the case of partial GTT. When performed
within the SGSN, the GTT tables are configured via O&M functions with the appropriate
translations.
Benefits
This interface allows a GSN within the GPRS network to connect an HLR to external
third-party HLRs.
Applications
This feature is essential for connecting a SGSN to a HLR, and is provided as a standard.

8–36 15th Sep 99

68P02903W01-O
FIELD TRIAL
Authentication
Summary
Authentication is a security feature that guards against unauthorized GPRS usage.
Standards
Description
Authentication is a security-enhancing feature on the GSN. The SGSN manages the
MSs. It uses authentication and authorization to control access to the GPRS network. It
also uses IP header compression and data compression to make more efficient use of
the radio channels, and it encrypts packets before they are sent over the air.
The SGSN authenticates the MS to the GPRS network. This includes the identification
and authentication of the service requester, and the validation of the service request type
to ensure that the user is authorized to use a particular network service. The
authentication function is performed in association with the mobility management
functions. A subscription is checked during the GPRS-Attach procedure and also during
the PDP context activation procedure. The SGSN uses the subscriber information, which
is stored in the Home Location Register (HLR), to identify the subscriber device,
authenticate the user, and encrypt user data. The SGSN stores subscriber data retrieved
from the HLR and information about the users current session in a local database.
Benefits
It provides a secure network and prevents unauthorized and unlawful use of the network.
Only users with valid subscription privileges are able to access the network, and the
network provides authentication for the user when the user logs on.
Applications
This feature is essential to provide security and allow authorized access only to
subscribers on the GSN network.
Compatibility/dependencies /network elements affected


68P02903W01-O
FIELD TRIAL
PTP-CLNS (static
IPv4)
Summary
PTP-CLNS feature provides a point-to-point connectionless-mode transmission of a
single unit of data from a source service-access-point to one or more destination
service-access-point(s) without establishing a connection. A connectionless-mode
service allows an entity to initiate such a transmission by the performance of a single
service access.
Standards
GPRS provides data communications services consistent with the connectionless
network layer service definition ISO 8348. PTP-CLNS is based upon the Open Standard
Interface (OSI) standards and the widely used Internet Protocol (IP) standards. This
feature is compliant with all current prevailing GSM standards.
Description
Connectionless-mode transmission is the transmission of a single unit of data from a
source service-access-point to one or more destination service-access-point(s) without
establishing a connection. In contrast to a connection, an instance of the use of a
connectionless-mode service does not have a clearly distinguishable lifetime. The
PTP-CLNS service has the following fundamental characteristics:
S No dynamic peer-to-peer agreement is involved in an instance of the service.
S All of the information required to deliver a unit of data (destination address, quality
of service selection, options, etc.) is presented to the layer providing the
connectionless-mode service, together with the user data to be transmitted, in a
single service access. The layer providing the connectionless-mode service is not
required to relate this access to any other service access.
S Each unit of data transmitted is entirely self-contained and can be routed
independently.
S Copies of a unit of data can be transmitted to a number of destination addresses.
Connectionless-mode transfer normally implies that the service:
S Does not provide confirmed delivery of SDUs.
S Does not guarantee delivery of SDUs.
S Does not guarantee maintenance of SDU sequencing.
S Does not guarantee elimination of SDUs.
Benefits
The PTP-CLNS service allows the transfer of information, called data packets, among
service users without the need for end-to-end call establishment procedures. The
PTP-CLNS teleservice is very good for bursty applications that use small packets (less
than 500 octets). In these applications, the time between successive transmissions
greatly exceeds the average transfer delay.
Applications
This feature is ideal to be used for typical bursty packet-based applications such as:
S Accessing information stored in a remote data centre.
S Storing and forwarding messages.
S Handling transaction or telemetry messages.
8–38 15th Sep 99

68P02903W01-O
FIELD TRIAL


68P02903W01-O
FIELD TRIAL
GPRS charging features GPRS-300-101
GPRS charging features
Account
metering and
collection
Summary
Account metering and collection functionality enables operators to collect network usage
data, and provide billing records to subscribers based on their connection to internal and
external networks.
Standards
This feature is compliant with ETSI specified GSM standards as defined in GSM 03.60.
Description
The SGSN and GGSN collect network usage data, called billing calling records,
necessary to support subscription and traffic fee management. In addition, the SGSN
collects usage information for the radio network, while the GGSN collects usage
information for the external data networks.
Billing calling records are routed to a Charging Gateway (CG) where the individual
charging records are stored and processed. If the charging gateway is unavailable, the
GSNs are able to store a limited number of charging records. The billing system (BS) of
the network operator collects the records from the CG. The GGSN provides the SGSN a
unique charging ID to all records generated for one PDP context. This record is unique
over a billing recording interval, and is needed to relate charging records that are
collected by multiple SGSNs during and after an SGSN-SGSN handover.
Benefits
This feature enables operators to measure data usage of subscribers on the networks,
and bill them for the same.
Applications
This feature is essential in order to bill subscribers for their network usage.

8–40 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GPRS charging features
Charging
gateway
Summary
This Charging Gateway (CG) feature acts as a storage buffer for real-time collection of
Charging Data Records (CDR). The CG function is part of the GSN.
Standards
This feature is compliant with all prevailing GSM standards.
Description
The Charging Gateway (CG) is used to aggregate and reliably store subscriber
accounting data. The SGSN and GGSN create accounting information. This information
is cached locally, and then transferred to the CG, where it is collected by the operator
billing system. The charging gateway software can be configured from the OMC-G.
Benefits
This feature provides an interface into the billing system for efficiently completing the
billing function.
Applications
The charging gateway functionality helps operators in billing their customers.


68P02903W01-O
FIELD TRIAL
GPRS network support GPRS-300-101
GPRS network support

Lawful intercept
– phase 1
(optional)
Summary
Lawful intercept feature on the GSN system provides operators the functionality to allow
law enforcement agencies with the ability to monitor all data traffic and location
information of a particular MS by tracking its IMSI.
Standards
This feature is compliant with ETSI specified GSM standards.
Description
Lawful intercept function for GPRS includes an ADMinistration Function (ADMF)
implemented on an independent platform. The administration function provides the
following capabilities:
S Receive requests (for instance from legal enforcement agencies) to provide lawful
intercept on one or more MSs.
S Receive the reported lawful intercept related information or intercept product from
the SGSN/GGSN and forward it to the requesting authority after suitable
formatting and filtering.
Lawful intercept functionality satisfies the following key requirements:
S It is possible to provide GPRS lawful intercept of all MSs (roaming or otherwise) in
a PLMN.
S The Intercept Product (IP) and Intercept Related Information (IRI) is available
within a few seconds of the relevant events that gave rise to the legal intercept
feature being activated for any given MS.
S All GPRS specific ciphering is undone before providing the IP.
S It is possible to generate billing information related to lawful intercept on any given
MS.
S It is possible to request lawful intercept for a GPRS MS identified at least by its
MS-ISDN and/or IMSI.
S The intercept related information for GPRS contains information about GPRS
attach, detach, PDP context activation, de-activation, cell update, and RA update.
S For GPRS, the Intercept Product (IP) is captured at the LLC protocol layer that is
common to all user data protocols.
S The intercept product is provided to the requesting law enforcement agency using
a standard networking protocol (TCP/IP).
S Suitable security procedures are provided between the requesting function and the
ADMF, and between the ADMF and the SGSN/GGSN.
S The operator is provided with tools to configure and manage the ADMF and the
lawful intercept related functionality located in the SGSN/GGSN.
Benefits
Lawful intercept provides operators with the capability to track and monitor data traffic
and location information for a particular MS.
8–42 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GPRS network support
Applications
This feature is essential for law enforcement agencies and operators to monitor
subscriber devices.


68P02903W01-O
FIELD TRIAL
GSN OA&M GPRS-300-101
GSN OA&M
SNMP
management
interface (TCP/IP)
Summary
This enables the GSN to be managed using SNMP V1 protocols for fault, performance
and configuration management.
Standards
This feature is compliant with GSM and TCP/IP internet standards. SNMP V1 must be
defined in a series of internet Radio Frequency Channels (RFCs). These include SNMP
[RFC 1157], SMI [RFC 1155], MIB definition [RFC 1212], and Trap definition [RFC1215].
Description
SNMP management interface provides functionality to configure various parts of the GSN
data network based on the standard SNMP protocol. SNMP V1 protocols can be used to
manage the GSN for fault management, performance management, and configuration
management.
Benefits
This feature assists operators in performing various fault, performance, and configuration
management functions within the GSN network.
Applications
Operators find this feature extremely useful in order to configure their networks. It can
also be used to perform diagnostics and network optimization on user networks.

8–44 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 GSN configuration
GSN configuration
PCU interface
(Gb) (optional)
Summary
The PCU interface or Gb interface provides connection between the BSS and the SGSN.
This feature provides redundancy and load balancing across the frame relay link between
the BSS and the SGSN.
Standards
This feature is compliant with current prevailing GSM standards as defined by ETSI.
Description
The Gb interface connects the BSS to the SGSN, allowing the exchange of signalling
information and user data. The Gb interface allows many users to be multiplexed over
the same physical resource. Resources are given to a user upon activity (when data is
sent or received), and are re-allocated immediately thereafter. This is in contrast to the A
interface, where a single user has the sole use of a dedicated physical resource
throughout the lifetime of a call, irrespective of activity.
GPRS signalling and user data are sent in the same transmission plane. No dedicated
physical resources are required to be allocated for signalling purposes. Access rates per
user may vary without restriction from zero data to the maximum possible line rate (for
example 2048 kbit/s for an E1 link). Currently the use of T1 links is not supported.
established between SGSN and BSS. LLC PDUs from many users are multiplexed on
these virtual circuits. The virtual circuits may be multi-hop and traverse a network of
frame relay switching nodes. Frame relay must be used for signalling and data
transmission.
The load sharing function distributes the user packet data traffic across the frame relay
links that make up the BSS-SGSN interface. Load sharing provides a seamless physical
transport service for the upper protocol layers by re-organizing the packet data traffic
between unblocked, or in-service, E1 links. Load sharing is performed by the PCU and
SGSN, and it only applies to user data.
Gb traffic, user data and signalling, can take different paths between the PCU and SGSN
depending upon the needs of the voice and data networks. In all cases, the Gb traffic is
always carried over 64 kbit/s E1 channels.
Benefits
PCU or Gb interface, while providing connectivity between the BSS and SGSN, helps
improve the operability of the GPRS system through redundancy and load sharing.
Applications
This feature is essential, and is an integrated part of the GPRS SGSN offering.


68P02903W01-O
FIELD TRIAL
Software features OMC-G GPRS-300-101
Software features OMC-G
OMC-G features
summary
S OMC Workspace
S Navigator
S Map
S Parameter Views
S Alarm Display
S Audible Indicator
S Alarm Printing Service
S User Profile Editor
S Help
S Configuration Management
S Performance Management
S Fault Management
S Load Management
8–46 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 OMC workspace
OMC workspace
Introduction to
the OMC-G
workspace
The OMC-G workspace acts as a container within which the OMC-G applications run.
From the workspace the operator can open the navigator, table or map.
Using the OMC-G

workspace
The file, view, tools, windows, and help menus are managed by the workspace. The edit,
view, display, config mgt, load mgt, popup menus and toolbars are managed by the
individual applications running within the workspace.
It is possible to save the layout of the OMC-G workspace and the applications currently
running in it. To reopen the OMC-G workspace with the saved layout, double-click on the
file to which the layout was saved or use the open workspace menu option.
General and application specific user preferences are present in the options box. The
properties relevant to the workspace application are contained on the general tab.
User settings
These are particular to the user, and this box lists the current user.
Workspace
There are two tick (check) boxes, one that allows the selection of a specific workspace to
be loaded at start-up. The other allows any changes made to be saved upon exit.
Feature
traceability
This feature is identified as follows:
RDB number: 3538.
Feature title: OMC-G workspace application for Windows NT.

68P02903W01-O
FIELD TRIAL
Navigator GPRS-300-101
Navigator
Introduction to
the OMC-G
navigator
The navigator is used to view the network containment hierarchy for the portion of the
network that is under the control of the OMC-G.
Using the OMC-G

navigator
When opened, the navigator shows the regions in the network that the user has access
to. Below region level, the SGSN, GGSN, GSN CommHub, and ISS nodes associated
with that region are displayed.
Nodes on the navigator are sorted according to type and alphabetically. The navigator
allows the operator to view the hierarchy of each of these nodes. For the SGSN and
GGSN nodes, this means navigating down the containment hierarchy. A parameter view
can be invoked for each object found, in order to view its attributes.
For the GSN CommHub and ISS nodes, the navigator provides access to menu options
that allow the operator to start telnet sessions to the machines, and also to start any
appropriate third-party configuration management applications.
Configuration management activities, such as device creation and deletion, may be
invoked from the navigator.
Alarm information is propagated on the navigator. When alarm indications are enabled,
nodes on the navigator reflects the colour of the highest severity alarm associated with
that node, and any of its contained devices (when the node is not expanded). If the node
is not alarmed, then the severity icon is not displayed.
By default the navigator is configured not to show alarm information. Alarm information
can be turned on with the Tools→Options menu item.
The navigator shows all regions that are configured within the OMC-G database for that
user. Access to those regions is controlled via the user profile editor.
Other applications such as load management, and performance management can be
started from the navigator.
Feature
traceability
RDB number: 3541.
Feature title: Navigator window (Windows NT).
8–48 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Map
Map
Introduction to
the OMC-G map
The map view provides an overview of the status of network components in a region.
Using the OMC-G

map
A map consists of a background and a series of nodes. The background may be divided
into several layers, each of which may be turned on or off independently. The
background may be either geographic or topological.
Alarm information is propagated on the map. When alarm indications are enabled, nodes
on the map reflect the colour of the highest severity alarm associated with that node and
any of its contained devices.
A new/seen indicator is displayed on each node where a change has occurred and has
not been acknowledged by the operator.
The new/seen indicator consists of a flashing “*” on the node. A flashing node indicates
the presence of new alarms in the alarm window associated with that node. The flashing
stops when the operator has acknowledged each new alarm (and therefore changed the
alarm state from NEW to SEEN).
The “!” symbol on a node indicates the presence of unhandled alarms and is not removed
until the alarm(s) causing the change on the node has been handled.
The map is dynamically updated as new alarms occur. They are handled and cleared
when a node name is changed. It also recognises and updates when new nodes are
created or deleted.
Using the OMC-G map, it is possible to:
S Hide/show the level of detail shown on the map using the layers dialogue box.
S Print the displayed portion of the map.
S Perform case-sensitive textual searches (next and previous) in the map.
S Zoom and pan in the map.
Feature
traceability
RDB number: 3539.
Feature title: Map support for routine O&M (Windows NT).

68P02903W01-O
FIELD TRIAL
Table GPRS-300-101
Table
Introduction to
the OMC-G table
The OMC-G table provides an overview of the status of network components in any
given region. It allows the status and performance of network components to be
monitored simultaneously based on a number of user-defined criteria.
Menu options are provided that allow the operator to configure the data displayed on the
window. A combination of alarm information and attribute values can be seen on the
same display.
Using the OMC-G

table
The operator specifies a region or network component and a template when opening a
table.
The table consists of rows and columns. Each row in the view identifies the region,
network element, or device that is being monitored. Each column in the view determines
the information that is displayed to the user. The columns displayed in the view are those
associated with the template
Displaying alarms in the table

Currently, an alarm or attribute column can be created in a template. In the table, an
alarm-monitor column allows the user to monitor alarms for an SGSN or GGSN. The cell
(table-cell) reflects the colour of the highest severity alarm for the row and any of its
contained devices.
It is also possible to display one of the following values in the cell:
S The total number of alarms associated with the device and any of its contained
devices.
S The number of highest severity alarms and the total number of alarms associated
with the cell and any of its contained devices.
S The number of alarmed devices.
An attribute column allows an operator to monitor an attribute value. If the attribute is not
applicable to the row, then the cell is cross-hatched (///).
New/seen indicator
A new/seen indicator is displayed on each cell where a change has occurred and has not
been acknowledged.
The new/seen indicator, for an alarm, consists of the cell flashing and a “!” symbol
superimposed on the cell. A flashing cell indicates the presence of new alarms in the
alarm window associated with that cell. The flashing stops when each new alarm is
acknowledged (that is, the alarm state has been changed from NEW to SEEN).
The ”!” symbol on a cell indicates the presence of unhandled alarms and is not removed
until the alarm(s) causing the change on the cell has been handled.
Using the OMC-G table, it is possible to:
S Hide or show columns.
S Copy selected cells, rows, and columns to either an email, Excel, or Word.
S Print the complete table contents (print selected is not available).
S Perform textual searches (next and previous) in the table.
8–50 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Table
Feature
traceability
RDB number: 3540.
Feature title: Tabular view of network status for routine O&M (Windows NT).

68P02903W01-O
FIELD TRIAL
Parameter views GPRS-300-101
Parameter views
Introduction to
the OMC-G
parameter view
A parameter view is used to display a full set of attributes for an object to a user.
Using the OMC-G

parameter view
The parameter view supports three user modes:
S Read only attributes may be viewed but not edited.
S Read-write: a user may change parameter values and save them.
S Create: the initial parameter values for an object may be set when the object is
first created. Once an object has been created, the parameter view enters edit
mode.
Changes made to an the parameters of an object by the user are validated according to
the specified range rules for each parameter; for example, range of valid values for
integer parameters.
Each parameter has an OMC and NE name. The OMC name is generally more
user-friendly. A user may change from one labelling scheme to another via the options
dialogue on the tools menu. A radio button on the parameter tab toggles between the two
naming schemes.
A menu option is available in the parameter view window to search the view by
parameter label, using the current labelling scheme.
Feature
traceability
RDB number: 3738.
Feature title: GSM OMC Windows NT forms application.
8–52 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Alarm Display
Alarm Display
Introduction to
the OMC-G alarm
display
The alarm display is used to monitor or view alarms. An alarm report is displayed for
each alarm occurrence.
Menu options are available in this window to sort or search the contents, or modify the
window layout. Operators can choose to view the alarm reports in either single or
multi-line format.
Using the OMC-G

alarm display
The alarm window displays a list of alarms. By default the list is presented in reverse
chronological order; that is, the most recent events are shown at the bottom of the list.
An alarm display can be opened from a node on the navigator/map or a cell in the table.
Alarms that are reported from the device (and its contained devices) for which the alarm
display was opened are displayed.
Managing alarms
Alarms have a new and a handling status. Alarms can be cleared by the operator or
internally by the system. Alarms that are cleared can be removed from the alarm window
automatically or upon user request. It is possible to handle, unhandle, and clear alarms.
Alarms display an icon that indicates the alarm severity. The word New under the “!”
symbol is used in the alarm view to indicate that an alarm has not been acknowledged as
seen by a user. Click on the alarm to tag it as being seen by the user. The “!” icon is used
to indicate that the alarm has not been handled.
In the OMC-G alarm display the user can:
S Hide or show fields in alarms.
S Sort alarms.
S Perform textual searches (next and previous) on alarms in the window.
S Copy selected alarms to either an email, Excel, or Word.
S Print the complete content of the alarm display (print selected is not available).
S Handle, unhandle, clear, and remove single or multiple alarms.
S Obtain context-sensitive help on alarms.
Feature
traceability
RDB number: 3542.
Feature title: Alarm window (Windows NT).

68P02903W01-O
FIELD TRIAL
Audible indicator GPRS-300-101
Audible indicator
Introduction to
the OMC-G
audible indicator
The OMC-G provides visual and audio feedback to the user on the occurrence of new
alarms.
Using the OMC-G

audible indicator
On starting the OMC-G workspace the audible indicator is displayed (bottom right corner
of the workspace). By default the audible indicator does not give audio feedback.
Single-click on the audible indicator to acknowledge the alarm occurrence and stop the
audio and visual indicators. The visual indicator is displayed as a grey colour when
acknowledged.
Double-click on the indicator to launch the appropriate alarm view, currently this is an
alarm view for the network.
Clearing the alarms affecting the audible indicator results in the audio and visual
indicators being cleared.
The audible indicator may be configured via its property page, available from the
Tools→Options menu item.
In the OMC-G, the following may be configured:
S The alarms used to provide audio/visual feedback.
– All alarms since the audible indicator was last clicked.
– All unseen alarms since the audible indicator was last clicked.
– All unhandled alarms since the audible indicator was last clicked.
S Whether audio feedback is enabled.
S The sound file that is played for each alarm severity .
Feature
traceability
RDB number: 3727.
Feature title: Audible alarm indicator (Windows NT).
8–54 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Alarm printing service
Alarm printing service
Introduction to
the OMC-G alarm
printing service
The alarm printing service permits the continuous printing of new alarms. The service is
disabled by default.
Using the OMC-G

alarm printing
service
For the alarm printing service to be available, the registry on the NT server must be
modified prior to starting the OMC-G. The keys in the registry that need to be modified
are located under:
HKEY_LOCAL_MACHINE\SOFTWARE\Motorola\GSM_OMC\Networks\
<NetworkName> \Event\Services\AlarmPrinter
They are:
Load
This flag determines if this service should be enabled or not. The default value is 0, that
is, not enabled. In order to avail of the direct alarm printing service, the load value must
be set to 1. For this change to take effect the NT server processes must be stopped and
restarted.
Device
This is the device that you wish to print to, by default this is LPT1: but another device, for
example: c:\temp\alarmprint.txt, can be used.
UseSocket
This flag is used to determine whether the alarms are directed to a device, for example:
printer or file, or another machine and port. The default value is 0; that is, alarms are
directed to a device. In order to redirect the alarms to a different machine/port, the
UseSocket value must be set to 1.
To initiate the print process, use the client application MotAlarmPrinter that is located in
the bin directory where the OMC release has been installed.
Running the print service application creates an icon in the task tray, which has a context
menu with two items in it. The menus allow the alarm printing to be started and stopped.
Alarm printing needs to be restarted, using MotAlarmPrinter, following a stop/start of the
NT server processes.
Feature
traceability
None.

68P02903W01-O
FIELD TRIAL
User profile editor GPRS-300-101
User profile editor
Introduction to
the OMC-G user
profile editor
The user profile editor is used to create profiles for users within the OMC-G. NT user
accounts can also created using the editor if the operator has the appropriate
administrator permissions.
It also provides a list of the users currently configured to use the OMC-G.
The command partitioning feature of the user profile editor is an accessible feature, but is
unsupported, and thus untested, since it is not a committed feature for the field trial.
Also the region editor feature is accessible, but is not a committed feature for the field
trial. This feature is also unsupported and untested.
Using the OMC-G

user profile
editor
It is possible to view a user current configuration; for example, the command groups and
regions that the user has access to.
Command groups can be assigned to or removed from a user. A user should be
assigned access to all command groups.
Users may be assigned or denied access to regions.
The user profile editor may not, currently, be invoked directly from the OMC-G
workspace.
Feature
traceability
RDB number: 3732.
Feature title: User profile editor (Windows NT).
8–56 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Help
Help
Introduction to
OMC-G help
Help is available on each OMC-G application. Context-sensitive help is available on
alarms and parameter attributes.
Using the OMC-G

help
The help is displayed in a HTML help viewer.
On the left side of the window is the Navigation pane. It contains three navigational tabs:
the Contents tab, the Index tab, and the Search tab.
On the right side of the window is the Topic pane. It displays the selected help topic, or
the default help topic.
The third pane is the Toolbar, which is located below the help window title bar.
Feature
traceability
RDB number: 3596.
Feature title: Help system for routine O&M (Windows NT).

68P02903W01-O
FIELD TRIAL
Configuration management GPRS-300-101
Configuration management
Introduction to
OMC-G
configuration
management
Configuration management allows the operator to configure the GSN nodes. It allows the
operator perform the following tasks:
S View SGSN and GGSN configuration.
S Modify SGSN and GGSN configuration.
S Perform a sanity check of an SGSN or GGSN database.
S Change SGSN and GGSN configuration via updated database files.
S Compare SGSN data related to Gb link with the corresponding PCU data
(retrieved from OMC-R).
S Generate an updated SGSN database from PCU configuration.
S Provide telnet access to SGSN, GGSN, GSN CommHub, and ISS.
S Provide tftp access to SGSN, GGSN, GSN CommHub, and ISS.
View and modify

SGSN/GGSN
configuration
The main tools used to view and modify the SGSN/GGSN configuration are the navigator
and parameter view applications.
View configuration
Using the navigator, the operator can browse the complete SGSN or GGSN hierarchy.
Parameter views can be opened to view the attributes of the objects contained by the
SGSN or GGSN.
Modify configuration
Attribute values can be changed from within the parameter views. In some cases, where
part of the SGSN or GGSN configuration is stored in a table, a table view can be opened
to view the configuration.
From the navigator, menu options can be selected to create new objects or delete
existing ones.
8–58 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Configuration management
Sanity check an
SGSN/GGSN
database
The OMC-G operator can request an SGSN or GGSN to sanity check a database
configuration file. This sanity check is executed at the GSN itself. The GSN database can
then be merged with, or replace, the current GSN configuration. The merge and replace
options are available for GSN database update while the GSN is still running.
Merge database
In database merge, data which is present in the existing GSN configuration, but missing
from the downloaded configuration file, is retained in the updated GSN configuration.
Replace database
In replace database, that data present in the existing GSN configuration, but missing
from the downloaded configuration file, is removed from the updated GSN configuration.
In both the merge and replace cases, any new data present in the downloaded
configuration file is appended to the existing GSN configuration. Also, any changes to
configuration data which exists in the current GSN configuration is retained in the
updated GSN configuration.

68P02903W01-O
FIELD TRIAL
Configuration management GPRS-300-101
Compare PCU
and SGSN
configuration
Another important part of SGSN configuration management is to compare PCU and
SGSN configuration data; that is, common Gb link related configuration information. This
enables the network operator to ensure that the PCU and SGSN connections are
correctly configured. The Gb Link Data menu option produces a report on the PCU to
SGSN connectivity. It also allows the operator to generate an updated SGSN database
file. This generated database file can then be downloaded to the SGSN and merged with
or replace the current GSN configuration.
Feature
traceability
RDB number: 3572.
Feature title: GPRS-OMC-G management of SGSN, GGSN, IP Support Server (ISS),
and GSN CommHub via SNMP.
8–60 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Performance management
Performance management
Introduction to
OMC-G
performance
management
The performance management feature provides the operator with the capability to view
and compare statistics of GSN nodes. The operator can perform the following tasks:
S View SGSN and GGSN statistics attributes on a form.
S View SGSN and GGSN statistics on a periodically updating graph, polled statistics.
S Export SGSN and GGSN statistics periodically, and generate a report using ISM
utilities.
S Access the statistics options from all OMC-G applications, such as navigator, map,
alarm window, and table.
S Create new statistics that are mathematical expressions based on existing statistic
attributes, and view them in graphs.
Viewing
SGSN/GGSN
statistics
The tools to view the SGSN and GGSN attributes are the navigator and parameter view
applications.
To view polled statistics, any OMC-G application can be used; currently, these are
navigator, map, alarm window, and table.
Select a GSN node or classes under it; a polled statistics option is displayed on the
popup menu and display menu. Selecting either SGSN or GGSN statistic launches the
GPRS statistics application in the OMC workspace. This displays a periodically updating
graph of the selected statistic for the selected GSN node.
Multiple graphs can be run for multiple nodes.
It is possible to manipulate these graphs in various ways :
S View the graphs in three formats: plot, scatter plot, or bar (default is plot).
S Change the number of points displayed in each graph (default is 10).
S Change the size of each chart, in pixels (default is a 250 pixel square).
S Compare multiple statistics by viewing them on one graph.
S Enlarge, zoom, translation features.
S View the statistics data in a tabular format.
S Change the interval of polling the statistics.
Feature
traceability
RDB number: 3572.

68P02903W01-O
FIELD TRIAL
Fault management GPRS-300-101
Fault management
Introduction to
OMC-G fault
management
The fault management feature allows the operator to detect problems on the GPRS
network elements of the SGSN, GGSN, GSN CommHub, and ISS. Through its alarm
management and alarm logging applications the problem can be evaluated, and
appropriate operator action taken.
Using OMC-G
fault
management
When a GPRS Network Element (NE) discovers an alarm condition in the network it
sends an SNMP trap to the OMC-G. This trap is converted into an ISO alarm by the
OMC-G. All alarms are written to the OMC-G event log.
The OMC-G alarms are uniquely identified by source, event type and trap id. Some
alarms are cleared by the system when it recovers; these are called FMIC alarms. OIC
alarms have to be cleared by the operator. When the problem has been resolved, a
good news alarm is raised to clear its corresponding bad news alarm. In the GSN, trap
N+1 clears trap N. For GSN CommHub trap N–1 clears trap N.
Viewing and monitoring alarms
The operator can view and monitor the alarms as they arrive through the alarm display in
which details of each alarm are displayed in either multi-line or single-line format.
Multi-line format offers extra details on each alarm, for example, trap id, trap name and
enterprise. When an alarm is raised it is given a New status to convey to the operator
that it has not yet been dealt with.
Once an alarm is dealt with, its status is changed to Seen. When the alarm is handled it
is updated with the user name of the operator.
When the problem is cleared by the system or the operator, its status changes to
Cleared, and it may be removed from the alarm window. Context-sensitive help is also
available in each alarm.
The alarm display can be displayed from the navigator, map, table, and audible indicator.
Logging information
The OMC event logs can be launched from the GPRS applications icon on the OMC-G
desktop. New logs are created daily or when the alarm count reaches 5000. They display
a detailed history of all alarms raised. It is possible to filter certain alarms from the event
log. Viewing selected fields of the alarm is possible through the preferences menu. Event
logs can also be saved in ASCII or tab-delineated format. The event logs are maintained
on the system for seven days before being deleted.
All traps and logging information are written to the trace log on the GSN. With a GSN
device selected it is possible to tftp this log file to a specified location on the OMC-G.
Feature
traceability
RDB number: 3572.
8–62 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 Load management
Load management
Introduction to
OMC-G load
management
Load management allows the operator to store, load and swap GSN software loads. The
operator can perform the following tasks:
S Install a GSN software load or database onto the OMC-G.
S Delete a GSN software load or database from the OMC-G.
S Download a software load or database from the OMC-G to a GSN.
S Swap a software load and corresponding database at a GSN.
S Upload a database from a GSN.
S View current download/swap/upload status.
Using OMC-G
load
management
The load management menu options are available from the navigator, table, and map
applications.
During an installation, the operator may transfer a software load or database from a
UNIX mounted CD, DAT, or user directory for storage at the OMC-G.
Delete allows the operator to delete previously installed software loads and databases.
Uploaded databases may also be deleted.
The Download option enables the operator to download a software load or database
from the OMC-G to a specific GSN. The transferred load is stored at the GSN for later
swap. Download may occur while the GSN is active.
Using Swap, the operator can activate a previously downloaded software load version
and corresponding database at a specific GSN. The GSN then reboots with the specified
software load version.
The Upload database option enables the operator to upload a file containing the current
configuration settings at a specific GSN, for storage at the OMC-G. Database upload
may be performed while the GSN is running.
The load management status window allows the operator to view all download, swap,
and upload operations which are currently in progress. Information displayed for each
operation includes start time, network element name, and estimated completion time.
Feature
traceability
RDB number: 3572.

68P02903W01-O
FIELD TRIAL
Load management GPRS-300-101
8–64 15th Sep 99

68P02903W01-O
FIELD TRIAL
Chapter 9
Glossary of technical terms and
abbreviations

68P02903W01-O
FIELD TRIAL
GPRS-300-101
ii 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101
Chapter 9
Glossary of technical terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . i
Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
A ......................................................................... 9–2
B ......................................................................... 9–4
C ......................................................................... 9–6
D ......................................................................... 9–10
E ......................................................................... 9–12
F ......................................................................... 9–13
G ......................................................................... 9–14
H ......................................................................... 9–17
I .......................................................................... 9–18
K ......................................................................... 9–20
L ......................................................................... 9–21
M ......................................................................... 9–22
N ......................................................................... 9–24
O ......................................................................... 9–25
P ......................................................................... 9–26
Q ......................................................................... 9–28
R ......................................................................... 9–29
S ......................................................................... 9–30
T ......................................................................... 9–32
U ......................................................................... 9–34
V ......................................................................... 9–35
W ........................................................................ 9–36
X ......................................................................... 9–37
Z ......................................................................... 9–38

68P02903W01-O
FIELD TRIAL
GPRS-300-101
iv 15th Sep 99
68P02903W01-O
FIELD TRIAL
GPRS-300-101 Numbers
Numbers
# Number.
2 Mbit/s link 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.
4GL 4th Generation Language.

68P02903W01-O
FIELD TRIAL
A GPRS-300-101
A
A interface Interface between MSC and BSS.
AA Anonymous Access.
AB Access Burst.
Abis interface Interface between a remote BSC and BTS. Motorola offers a
GSM standard and a unique Motorola Abis interface. The
Motorola interface reduces the amount of message traffic and
thus the number of 2 Mbit/s lines required between BSC and
BTS.
ac Alternating Current.
AC Access Class (C0 to C15).
ACCH Associated Control CHannel.
ACK, Ack ACKnowledgement.
ACM Address Complete Message.
ACSE Associated Control Service Element.
ADCCP ADvanced Communications Control Protocol.
ADM ADMinistration processor.
ADMF ADMinistrative Function.
ADN Abbreviated Dialling Number.
ADPCM Adaptive Differential Pulse Code Modulation.
AEC Acoustic Echo Control.
AFC Automatic Frequency Control.
AFN Absolute Frame Number.
AGC Automatic Gain Control.
AGCH Access Grant CHannel. A GSM common control channel
used to assign MS to a SDCCH or a TCH.
Air interface The radio link between the BTS and the MS.
AMA Automatic Message Accounting (processor).
APN Access Point Name. The purpose of the APN information
element is to identify the packet data network to which the
GPRS user wishes to connect. The Access Point Name is a
label or a fully qualified domain name according to DNS
naming conventions as specified in GSM 03.03.
Applied Load This is the per-cell GPRS application data such as email that
is carried on GPRS carrier timeslots from all of the mobiles in
a cell.
ARFCN Absolute Radio Frequency Channel Number. An integer
which defines the absolute RF channel number.
ARQ Automatic ReQuest for retransmission.
ARP Address Resolution Protocol.
ASCE Association Control Service Element. An ASE which provides
an AP with the means to establish and control an association
with an AP in a remote NE. Maps directly onto the
Presentation layer (OMC).
ASCII American Standard Code for Information Interchange.
9–2 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 A
ASE Application Service Element (OMC)

ASE Application Specific Entity (TCAP).
ATM Asynchronous Transfer Mode.
ATT (flag) ATTach.
AU Access Unit.

68P02903W01-O
FIELD TRIAL
B GPRS-300-101
B
B Interface Interface between MSC and VLR.
BA BCCH Allocation. The radio frequency channels allocated in a
cell for BCCH transmission.
BBP BackBone Protocol.
Bc Committed Burst rate.
BCCH Broadcast Control CHannel. A GSM control channel used to
broadcast general information about a BTS site on a per cell
or sector basis.
BCS Block Check Sequence.
Be Burst excess rate.
BER Bit Error Rate. A measure of signal quality in the GSM
system.
BFI Bad Frame Indication.
BGP Border Gateway Protocol.
BH Busy Hour.
BL BootLoad. Also known as download. For example, databases
and software can be downloaded to the NEs from the BSS.
BLER BLock Error Rate.
bit/s Bits per second (bit/s).
Bm Full rate traffic channel.
BN Bit Number. Number which identifies the position of a
particular bit period within a timeslot.
BS Billing System.
BS 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.
BSC Base Station Controller. A network component in the GSM
PLMN which has the digital control function of controlling all
BTSs. The BSC can be located within a single BTS cabinet
(forming a BSS) but is more often located remotely and
controls several BTSs (see BCF, BCU, and BSU).
BSP Base Site control Processor (at BSC).
BSS Base Station System. BSS provides RF control and
transmission for GPRS mobile devices. The system of base
station equipment (Transceivers, controllers and so on) which
is viewed by the MSC through a single interface as defined by
the GSM 08 series of recommendations, as being the entity
responsible for communicating with MSs in a certain area.
The radio equipment of a BSS may cover one or more cells.
A BSS may consist of one or more base stations. If an
internal interface is implemented according to the GSM 08.5x
series of recommendations, then the BSS consists of one
BSC and several BTSs.
BSSAP BSS Application Part.
9–4 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 B
BSSGP BSS GPRS Protocol. The functions of the BSSGP are to

provide radio-related information, and to perform node
management functions between the SGSN and the BSS.
BSS GPS Base Station System Global Positioning System.
BSSI Base Station System Indentifier.
BSSMAP Base Station System Management Application Part (6-8).
BTS 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 (TRXs).
Burst A period of modulated carrier less than one timeslot. The
physical content of a timeslot.
BVC BSSGP Virtual Channel. The functions of the BSSGP are to
provide radio-related information and to perform node
management functions between the SGSN and the BSS.
BVC BSS Virtual Circuit.

68P02903W01-O
FIELD TRIAL
C GPRS-300-101
C
Card Also referred to as Board. A printed circuit assembly.
C Interface Interface between MSC and HLR/AUC.
C7 ITU-TSS Signalling System number 7 (sometimes referred to
as S7 or SS7); a card (or a module).
C7 module The C7 module provides the logical interface to the HLR,
MSC/VLR (future) and SMS-C (future). A C7 module has up
to four E1 interfaces, which typically connect to a C7
Signalling Transfer Point (STP) pair. The C7 Module has a
unique address within the GSN complex, and is directly
connected to the GSN CommHub via a 100BaseT port. In the
GSN Release 1, one C7 module is provided for every three
SGSN modules. The C7 module that serves a particular
SGSN module need not be located in the same shelf module
as the SGSN module.
CA Cell Allocation. The radio frequency channels allocated to a
particular cell.
CA Central Authority.
CADM Country ADMinistration. The Motorola procedure used within
DataGen to create new country and network files in the
DataGen database.
CAI Charge Advice Information.
CB Cell Balancer.
CBCH Cell Broadcast CHannel.
CBMI Cell Broadcast Message Identifier.
CBSMS Cell Broadcast Short Message Service.
CCCH Common Control CHannel(s). A class of GSM control
channels used to control paging and grant access. Includes
AGCH, PCH, and RACH.
CCD Common Channel Distributor.
CCDSP Channel Coding Digital Signal Processor.
CCH Control CHannel. Control channels are channels which carry
system management messages.
CCITT Comité Consultatif International Télégraphique et
Téléphonique. This term has been superseded by ITU-TSS
(International Telecommunications Union –
Telecommunications Sector).
CCPE Control Channel Protocol Entity.
CCU Channel Coder-decoder (Coding) Unit.
CDR Charging Data Records.
9–6 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 C
CD-ROM Compact Disk-Read-Only Memory.

Cell By GSM definition, a cell is 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 analogue
systems where cell is taken to mean the same thing as site.
(See below).
1 Cell =
1 Sector
Omni Site 6-Sector Site

1-Cell Site or
(1 BTS) 6-Cell Site
(6 BTSs)
CEPT Conférence des administrations Européennes des Postes et

Telecommunications.
CERM Circuit Error Rate Monitor.
CF Control Function module. CF performs the SGSN mobility
management functions and OA&M functions for the GSN
module. CF has a unique IP address within the GSN, and is
directly connected to the GSN Communications Hub by a
100Base T port.
CF The CF provides the SGSN mobility management functions
and OA&M functions. It has a unique IP address within the
GSN complex, and is directly connected to the GSN
CommHub via a 100BaseT port.
CG Charging Gateway.
CGF Charging Gateway Function.
Channel 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.
C/I Carrier-to-Interface ratio.
CIM Coaxial Interconnect Module.
Ciphertext Unintelligible data produced through the use of encipherment.
CIR Committed Information Rate.
CKSN Ciphering Key Sequence Number.
CLI Calling Line Identity.
CLIP Calling Line Identification Presentation supplementary
service.
CLIR Calling Line Identification Restriction supplementary service.
CLM Connectionless Manager.
CLNS ConnectionLess Network Service.
CM Configuration Management.
CM Connection Management.

68P02903W01-O
FIELD TRIAL
C GPRS-300-101
CMD CoMmanD.
CMM Channel Mode Modify.
CMIP Common Management Information Protocol.
CMISE Common Management Information Service Element. An ASE
which provides a means to transfer management information
via CMIP messages with another NE over an association
established by ASCE using ROSE (OMC).
Collocated Placed together; two or more items together in the same
place.
CODEC COder-DECoder.
COMM, Comms COMMunications.
CommHub GSN Communications Hub. The unit provides ethernet
switching and IP routeing for the GSN complex local
networking and GSN complex E1 interfaces to the public data
network.
CommsLink Communications Link. (2Mbit/s)
Communications The communications cabinet holds the GSN communications
cabinet equipment, including the GSN Communications Hub and the
Sun Cluster, required to support a GSN complex.
Communications This cabinet holds the GSN complex communications
cabinet equipment: the CommHub, Internet Support Services, and
High Availability Disk Arrays.
CNR Cisco Network Registrar. CNR is a Cisco product that
provides DNS server capabilities to the GSN.
CONP Connection-Oriented Network Protocol.
CONS Connection-Oriented Network Service.
CP Call Processing.
CPCI A set of standards that define a common card cage, power
supplies, and processor boards.
cPCI A set of standards that define a common card cage, power
supplies, and processor boards. Compact PCI.
CPGM CCCH Paging Manager.
CPU Central Processing Unit.
CR Connection Request (Part of SCCP network connectivity).
CRM Cell Resource Manager.
CS Coding Scheme.
CS-1 Coding Scheme-1 (9.05 kbit/s per TCH).
CSFP Code Storage Facility Processor (at BSC and BTS).
CSP Central Statistics Process. The statistics process in the BSC.
CSPDN Circuit Switched Public Data Network.
CT Channel Tester.
9–8 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 C
CT Channel Type.
CUG SS Closed User Group Supplementary Service.

68P02903W01-O
FIELD TRIAL
D GPRS-300-101
D
D Interface Interface between VLR and HLR.
DataGen Sysgen Builder System. A Motorola offline BSS binary object
configuration tool.
dB Decibel. A unit of power ratio measurement.
DB Dummy Burst (see Dummy burst).
DBA DataBase Administration/Database Administrator.
DBMS DataBase Management System.
dc Direct Current.
DCCH Dedicated Control CHannel. A class of GSM control channels
used to set up calls and report measurements. Includes
SDCCH, FACCH, and SACCH.
DCE Data Circuit terminating Equipment.
DCE Data Communication Equipment.
DCF Data Communications Function.
DCN Data Communications Network. A DCN connects Network
Elements with internal mediation functions or mediation
devices to the Operations Systems.
DDS DataGen Directory Structure.
DET DETach.
DFE Decision Feedback Equalizer.
DGT Data Gathering Tool.
DHCP Dynamic Host Control Protocol.
DHP Digital Host Processor.
DINO E1/HDSL Line termination module.
DINO T1 Line termination module.
DL Data Link (layer).
DL DownLink.
DLC Data Link Connection.
DLCI Data Link Connection Identifier.
DLD Data Link Discriminator.
DLS DownLink Segmentator.
DLSP Data Link Service Process.
DLSP Digital Link Signalling Processor.
Dm Control channel (ISDN terminology applied to mobile service).
DMR Digital Mobile Radio.
DN Directory Number.
DNS Domain Name Service (Server/System). The DNS is a
distributed Internet directory service. DNS is used primarily to
translate between logical domain or equipment names to IP
addresses. In GPRS, an Access Point Name (APN) is a form
of DNS name.
DNIC Data network identifier.
9–10 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 D
Downlink Physical link from the BTS towards the MS (BTS transmits,
MS receives).
DPROC Data PROCessor board (in PCU).
DPS Domain Name System. The DPS is a distributed Interned
directory service. DPS is used primarily to translate between
logical domain or equipment names to IP addresses. In
GHIS, an Access Point Name (AN) is a form of DPS name.
DRC Data Rate Converter board. Provides data and protocol
conversion between PLMN and destination network for 8
circuits (p/o IWF).
(D)RCU Generic term for radio channel unit. May be standard RCU or
diversity radio channel unit DRCU.
DRX Discontinuous Reception.
DSP Digital Signal Processor.
DTE Data Terminal Equipment.
DTx Discontinuous Transmission.
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.

68P02903W01-O
FIELD TRIAL
E GPRS-300-101
E
E Interface Interface between MSC and MSC.
ECID The Motorola European Cellular Infrastructure Division.
EDGE Enhanced Data rates for GSM Evolution.
Effective Load 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.
EGP Exterior Gateway Protocol.
EGPRS Enhanced GPRS.
EIDE Enhanced Integrated Design (Disk) Electronics.
EIR Equipment Identity Register.
EQB Equalizer Board. Control circuit for equalization for 8 time
slots each with equalizing circuitry and a DSP (p/o RCU).
EQCP Equalizer Control Processor.
EQ DSP Equalizer Digitizer Signal Processor.
Erlang 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).
ERR ERRor.
ESP Encapsulation Security Payload.
ESP Electro-static Point.
Ethernet Type of Local Area Network.
ETR ETSI Technical Report.
ETS European Telecommunication Standard.
ETSI European Telecommunications Standards Institute.
9–12 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 F
F
F Interface Interface between MSC and EIR.
FA Functional Area.
FACCH Fast Associated Control Channel. A GSM dedicated control
channel which is associated with a TCH and carries control
information after a call is set up (see SDCCH).
FACCH/F Fast Associated Control Channel/Full rate.
FACCH/H Fast Associated Control Channel/Half rate.
FB Frequency correction Burst (see Frequency correction burst).
FBM Flow control Buffer Management.
FCCH Frequency Correction CHannel. A GSM broadcast control
channel which carries information for frequency correction of
the mobile (MS).
FDMA Frequency Division Multiple Access.
FEC Forward Error Correction.
FH Frequency Hopping.
FM Frequency Modulation.
FR Frame Relay.
FPGA Field Programmable Gate Array.
FQDN Fully Qualified Domain Name.
Frequency correction Period of RF carrier less than one timeslot whose modulation
bit stream allows frequency correction to be performed easily
within an MS burst.
FRU Field Replaceable Unit.
FSN Forward Sequence Number.
FTD File Transit Delay.
FTP File Transfer Protocol.

68P02903W01-O
FIELD TRIAL
G GPRS-300-101
G
G Interface Interface between VLR and VLR.
GB, Gbyte Gigabyte.
Gb Interface between an SGSN (SGN) and a BSS (BSC)
(between PCU and GSN CommHub).
Gb card Gb card performs the SGSN Gb interface communication
protocol functions. It has a unique IP address within the GSN.
It is directly connected to the GSN Communications Hub by a
100Base T port. It supports four E1 ports to remotely located
BSS sites.
GBL Gb Link.
Gb link The Gb Link is used to carry both GPRS user data and
signalling information by using frame relay over E1 between
the PCU and SGSN. From one to four E1s may be
provisioned per SGSN.
GBM Gb Manager.
Gb module The Gb module provides the SGSN Gb interface
communication protocol functions. It has a unique IP address
within the GSN complex, and is directly connected to the
GSN CommHub via a 100BaseT port. It supports 4 E1 ports
to remotely located BSS, sites and these are referred to as
GBL links.
G-CDR GGSN-Call Detail Record.
GCLK Generic Clock board. System clock source, one per site (p/o
BSS, BTS, BSC, IWF, RXCDR).
GCMD Generator CoMmanD (CoMmanD Generator).
GCR Group Call Register.
GDL
GDS GPRS Data Stream.
GDS LAPD (GSL) The GSLs are is 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.
GDS TRAU 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.
gg GGSN-CONTROL, GGSN-GiPROC, GGSN-GNPROC
integrated functions
GGSN Gateway GPRS Support Node (shelf unit). GGSN provides
internetworking with external packet-switched networks, and
is connected with SGSNs through an IP-based GPRS
backbone network. The GGSN is a Cisco 7206 router.
GGSN-CONTROL GGSN-CONTROL function.
GGSN-GiPROC GGSN Gi Processor.
GGSN-GNPROC GGSN Gn Processor.
GHz Giga-Hertz (109).
9–14 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 G
Gi Interface between GGSN and PDN (reference point between

GPRS and an external PDN).
GMR GSM Manual Revision.
GMM GPRS Mobility Management.
GMSC Gateway Mobile-services Switching Centre (see Gateway
MSC).
GMT Greenwich Mean Time.
Gn An interface between the SGSN and GGSN ( between two
GSNs within the same PLMN).
Gn module Gn module performs the SGSN communication protocol
functions for a single Gn interface. It has a unique IP address
within the GSN complex, and is directly connected to the
GSN Communications Hub by a 100BaseT port.
GND GrouND.
GOS Grade Of Service.
GPA GSM PLMN Area.
GPC General Protocol Converter.
GPS Global Positioning Service/System.
GR Gb Router.
GPROC Generic Processor board. GSM generic processor board: a
68030 with 4 to 16 Mb RAM (p/o BSS, BTS, BSC, IWF,
RXCDR).
GPROC2 Generic Processor board. GSM generic processor board: a
68040 with 32 Mb RAM (p/o BSS, BTS, BSC, IWF, RXCDR).
GPRS General Packet Radio Service.
GPRS-Attach GPRS-Attach is performed when the MS indicates its
presence to the PLMN for the purpose of using the GPRS
PTP service. This can be immediately after the MS has been
switched on, or later as the user decides to use the GPRS
services. The MS identifies itself with its GSM identity (IMSI,
TLLI). A GPRS-Attach is successfully performed only if the
subscriber has a valid GPRS subscription. It is assumed that
the user does not, under normal circumstances, initiate a
GPRS-Attach without first ensuring that the data handling
capability necessary in the terminating equipment has been
activated, such as the laptop computer has been turned on.
GPRS-Detach GPRS-Detach is performed when the MS indicates to the
PLMN that the MS is no longer using the GPRS services. The
MS identifies itself with its GSM identity (IMSI, TLLI).
GPRS Network The GPRS Network Subsystem (NSS) is responsible for all
Subsystem network management and mobility related management. NSS
may contain the following components: SGSN, GGSN, ISS,
and CGF.
GSM Groupe Spécial Mobile (the committee).
GSM Global System for Mobile communications.
GSL GPRS Signalling Link(s).
GSM Global System for Mobile communications (the system).
GSM MS GSM Mobile Station.

68P02903W01-O
FIELD TRIAL
G GPRS-300-101
GSM PLMN GSM Public Land Mobile Network.

GSMRF GSM Radio Frequency.
GSN GPRS Support Node. GSN is a set of Motorola equipment
that is addressed by one SS7 point code, is switched through
the same GSN Communications Hub, and is located at one
site.
GSN cabinet The GSN cabinet holds a combination of GSN shelves and
GGSN modules, up to three GSN shelf units.
GSN CommHub GSN Communications Hub.
GSN complex GSN complex consists of multiple components connected to
a single LAN switch. Some of the components that may be
connected to the LAN switch include: SSGN, GGSN, CG, and
ISS. A GSN complex is defined by the physical connections
of components to the GSN Communication Hub. A GSN
complex performs the Gateway function (GGSN), or the
Serving Function (SGSN), or both functions.
GSN complex A GSN complex consists of multiple components connected
to a single GSN CommHub. Some of the components that
may be connected to a GSN complex are the SGSN, GGSN,
CGF, and ISS. A GSN complex is defined by the physical
connection of entities to the GSN Communications Hub.
GSN shelf The GSN shelf is the set of equipment contained within a
19 inch CompactPCI shelf that is interconnected by the same
cPCI bus. In the GSN Release 1, a GSN shelf contains one
C7 card, one to three SGSN modules (CF, Gn, and Gb
cards), and two shelf management modules.
GSN Sun Cluster See Sun Cluster.
GSR GSM System (Software) Release.
GTM Gb Transmit Manager.
GTP GPRS Tunnelling Protocol.
GTT Global Title Translation.
Guard period Period at the beginning and end of timeslot during which MS
transmission is attenuated.
GUI Graphical User Interface.
GWM GateWay Manager.
GWY GateWaY (MSC/LR) interface to PSTN.
9–16 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 H
H
HADA High Availability Disk Array.
HA NFS High Availability Network File Service.
H Interface Interface between HLR and AUC.
HDLC High level Data Link Control.
HDSL High bit-rate Digital Subscriber Line.
High Availability Disk The High Availability Disk System provides reliable long-term
System storage for network configuration, software loads, charging
data information, and network statistics.
High Availability Provides reliable long-term storage for network configuration,
Storage System software loads, charging data information, and network
statistics.
HLC High Layer Compatibility. The HLC can carry information
defining the higher layer characteristics of a teleservice active
on the terminal.
HLR Home Location Register. The LR where the current location
and all subscriber parameters of an MS are permanently
stored.
HLRS Home Location Register Service.
HPLMN Home PLMN.
HSM HLR Subscriber Management.
HSSI High-Speed Serial Interface.
HW Hardware.
Hyperframe 2048 superframes. The longest recurrent time period of the
frame structure.

68P02903W01-O
FIELD TRIAL
I GPRS-300-101
I
IA Incoming Access (closed user group (CUG) SS
(supplementary service)).
IAM Initial Address Message.
IANA Internet Address Name Authority.
ICMP Internet Control Message Protocol.
IDN Integrated Digital Network.
IE Information Element (signalling).
IEC International Electrotechnical Commission.
IEEE Institute of Electrical and Electronic Engineers.
IEI Information Element Identifier.
IETF Internet Engineering Task Force.
IMEI International Mobile station Equipment Identity. Electronic
serial number that uniquely identifies the MS as a piece or
assembly of equipment. The IMEI is sent by the MS along
with request for service.
IMSI International Mobile Subscriber Identity. Published mobile
number (prior to ISDN) (see also MSISDN) that uniquely
identifies the subscription. It can serve as a key to derive
subscriber information such as directory number(s) from the
HLR.
IMSI International Mobile Station Identity.
INS IN Service.
Interworking The general term used to describe the inter-operation of
networks, services, supplementary services and so on. See
also IWF.
Interval A recording period of time in which a statistic is pegged.
IOS Internet Operating System.
I/O Input/Output.
IP Intercept Product.
IP Internet Protocol.
IPC Inter-Process Communication.
IRI Intercept Related Information.
ISDN Integrated Services Digital Network. An integrated services
network that provides digital connections between
user-network interfaces.
ISG Motorola Information Systems group (formally CODEX).
ISO International Organisation for Standardization.
ISS Integrated Support Server. ISS performs the Charging
Gateway Function, Domain Name System, Network Time
Protocol, and other functions required by the GSN.
9–18 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 I
ISS Internet (IP) Support Services (Server). The ISS equipment

performs the Charging Gateway Function (CGF), Domain
Name System (DNS), Network Time Protocol (NTP) required
by a GSN complex. The ISS uses the Sun Netra hardware,
which is connected to the GSN CommHub using 100 BaseT.
The ISS hardware is located in the Communications Cabinet.
ISUP ISDN User Part (of signalling system No. 7).
ITC Information Transfer Capability.
ITU International Telecommunication Union.
IWF 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.
IWMSC InterWorking MSC.
IWU InterWorking Unit.

68P02903W01-O
FIELD TRIAL
K GPRS-300-101
K
k kilo (103).
kb, kbit kilo-bit.
kbit/s, kbps kilo-bits per second.
kbyte kilobyte.
Kc Ciphering key. A sequence of symbols that controls the
operation of encipherment and decipherment.
kHz kilo-Hertz (103).
kph Kilometres per hour.
KSW Kiloport SWitch.
kW kilo-Watt.
9–20 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 L
L
L1 Layer 1.
L2ML Layer 2 Management Link.
L2R Layer 2 Relay function. A function of an MS and IWF that
adapts a user’s known layer2 protocol LAPB onto RLP for
transmission between the MT and IWF.
L2R BOP L2R Bit Orientated Protocol.
L2R COP L2R Character Orientated Protocol.
L3 Layer 3.
LA Local Area.
LAC Location Area Code.
LAI Location Area Identity. The information indicating the location
area in which a cell is located.
LAN Local Area Network.
LANX LAN Extender half size board. Fibre optic distribution of LAN
to/from other cabinets (p/o BSS etc).
LAPB Link Access Protocol Balanced (of ITU-TSS Rec. x.25).
LAPD Link Access Protocol D-channel (Data).
LAP-G Link Access Protocol-GPRS.
LCF Link Control Function.
LCN Local Communications Network.
LCP Link Control Processor.
LED Light-Emitting Diode.
LLC Logical Link Control.
LLC Lower Layer Compatibility. The LLC can carry information
defining the lower layer characteristics of the terminal.
LLGMM Logical Link GPRS Mobility Management.
LLSMS Logical Link Short Message Service.
LPC Linear Predictive Coding.
LSSU Link Stations Signalling Unit (Part of MTP transport system).
LU Location Update.

68P02903W01-O
FIELD TRIAL
M GPRS-300-101
M
M Mega (106).
MAC Medium Access Control.
MACN Mobile Allocation Channel Number.
MAP Mobile Application Part (of signalling system No. 7). The
inter-networking signalling between MSCs and LRs and EIRs.
MAPP Mobile Application Part Processor.
MB, Mbyte Megabyte.
Mbit/s Megabits per second.
MCAP Motorola Cellular Advanced Processor.
MCDF Motorola Customer Data Format used by DataGen for simple
data entry and retrieval.
M-CDR Mobility management-Call Detail Record.
MCP570 Main Control Processor570.
MF MultiFrame.
MHz Mega-Hertz (106).
MIB Management Information Base. A Motorola OMC-R
database. There is a CM MIB and an EM MIB.
Microcell 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.
min minute(s).
ms micro-second (10–6).
MM Mobility Management.
MIB SNMP Information Base.
MME Mobile Management Entity.
MMI Man-Machine Interface.
MNRG Mobile station Not Reachable for GPRS (flag).
MNRR Mobile station Not Reachable Reason.
MO Mobile Originated.
Mobis Motorola Abis Interface.
Module A module is a self-contained, separable assembly of
electronic parts and/or software, such as the three-card set
that makes up the SGSN.
Mo-MIP
MoU Memorandum of Understanding.
MPROC MasterPROCessor board (in PCU).
MS Mobile Station. The GSM subscriber unit.
MSC Mobile-services Switching Centre, Mobile Switching Centre.
msec millisecond (.001 second).
MSI Multiple Serial Interface board. Intelligent interface to two
2 Mbit/s digital links (see 2 Mbit/s link and DS-2) (p/o BSS).
9–22 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 M
MSISDN Mobile Station International ISDN number.

MT Mobile Terminated. Describes a call or short message
destined for an MS.
MT Mobile Terminal.
MTL MTp Transport layer Link (A interface).
MTM Mobile-To-Mobile (call).
MTP Message Transfer Part.
MT/PP Mobile Terminated Point-to-Point messages.
Multiframe 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.

68P02903W01-O
FIELD TRIAL
N GPRS-300-101
N
N/W Network.
NAT Network Address Translation.
NB Normal Burst (see Normal burst).
N-CommHub Network_Communications Hub.
NC0 Network Cell reselection mode 0.
NCH Notification CHannel.
NE Network Element (Network Entity). NE is a GSN component
that is managed by the OMC-G GUI.
NET Norme Européennes de Telecommunications.
NF Network Function.
NFS Network File System.
NFS Server The NFS Server provides reliable long-term storage for
network configuration, software storage, charging data
information, and network statistics.
NIC Network Independent Clocking.
NIS Network Information Service. It allows centralised control of
network information for example hostnames, IP addresses
and passwords.
NM Network Management.
Nm Newton metres.
NMC ...
NMSI National Mobile Station Identification number.
Normal burst A period of modulated carrier less than a timeslot.
Nr/sub Number of requests/subscriber.
NS Network Service.
NS-VC Network Service-Virtual Circuit
NSAP Network Service Access Point.
NSAPI NSAP Identifier.
NSP Network Service Provider.
NSS GSN Network SubSystem.
NST Network Service Tester.
NTP Network Time Protocol. The NTP is used to synchronize the
time of GSN components. It provides accuracy within a
millisecond on LANs, and up to a few tens of milliseconds on
WANs relative to a primary server synchronized to
Coordinated Universal Time (UTC) via a Global Positioning
Service (GPS) receiver.
NVRAM Non-Volatile Random Access Memory.
nW Nano-Watt (10–9).
9–24 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 O
O
OA Outgoing Access (CUG SS).
OAMP Operation, Administration, Maintenance, and Provisioning.
O&M Operations and Maintenance.
OC3
OMAP Operations and Maintenance Application Part (of signalling
system No. 7) (was OAMP).
OMC Operations and Maintenance Centre. The OMC node of the
GSM TMN provides dynamic O&M monitoring and control of
the PLMN nodes operating in the geographical area
controlled by the specific OMC.
OMC-G Operations and Maintenance Centre — Gateway Part
(Iridium).
OMC-G Operations and Maintenance Centre — GPRS Part. OMC-G
is a GSN network management tool that provides a GUI for
configuration management, performance management, fault
management, and load management functions.
OMC-CommHubG OMC-Communications Hub for GPRS.
OMC-R Operations and Maintenance Centre — Radio Part.
OOS Out Of Service.
OSI Open Systems Interconnection.
OSI Open Systems Interface.
OSPF Open Shortest Path First.
Overlap Overlap sending means that digits are sent from one system
to another as soon as they are received by the sending
system. A system using ~ will not wait until it has received all
digits of a call before it starts to send the digits to the next
system. This is the opposite of en bloc sending where all
digits for a given call are sent at one time.

68P02903W01-O
FIELD TRIAL
P GPRS-300-101
P
PAD Packet Assembler/Disassembler facility.
PACCH Packet Associated Control CHannel.
PAGCH Packet Access Grant CHannel.
PAGCH Paging and Access Grant CHannel.
Paging 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.
PATH CEPT 2 Mbit/s route through the BSS network.
PBB PCU processor Bridge Board.
PBCCH Packet Broadcast Control CHannel.
PCA PCU Control Authority.
PCCCH Packet Common Control CHannel.
PCH Paging CHannel. A GSM common control channel used to
send paging messages to the MSs.
PCI Packet Control Interface.
PCI Compact Peripheral Component Interconnect.
PCHN Physical Channel.
PCM Pulse Code Modulation (see also 2 Mbit/s link which is the
physical bearer of PCM).
PCM PCU Configuration Management.
PCU Packet Control Unit (p/o GPRS).
PD Protocol Discriminator.
PDCH Packet Data Channel. PDCH carries a combination of
PBCCH and PDTCH logical channels.
PDN Public Data Network.
PDP Packet Data Protocol.
PDTCH Packet Data Traffic CHannel.
PDU Packet Data Unit.
PDU Protocol Data Unit.
Peg A single incremental action modifying the value of a statistic.
Pegging Modifying a statistical value.
PFCP PCU Fault Collection Process.
PFTP PCU Fault Transaction Process.
PH Packet Handler.
PHI Packet Handler Interface.
PICP Packet Interface Control Processor (a board).
PLL Phase Lock Loop (refers to phase locking the GCLK in the
BTS).
PLMN Public Land Mobile Network. The mobile communications
network.
PMC PCI Mezzanine Card.
9–26 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 P
PMC Plugin Memory Card.

PM/E1 Plugin Memory/E1.
PM/T1 Plugin Memory/T1.
PNCH Packet Notification CHannel.
POI Point of Interconnection (with PSTN).
POP3 Post Office Protocol 3.
POTS Plain Old Telephone Service (basic telephone services).
PPB Pci to Pci Bridge.
ppb Parts per billion.
PPCH Packet Paging CHannel.
PPF Paging Proceed Flag.
ppm Parts per million (x 10–6).
PRACH Packet Random Access CHannel.
Primary Cell 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.
PRM Packet Resource Manager.
PRP Packet Resource Process(or).
PSA Periodic Supervision of Accessibility.
PSAP PCU System Audit Process.
PSAP Presentation Services Access Point.
PSF Power Supply and Fan unit.
PSP Pcu System Processor.
PSG
PSPDN Packet Switched Public Data Network. Public data
communications network. x.25 links required for NE to OMC
communications will probably be carried by PSPDN.
PSTN Public Switched Telephone Network. The UK land line
telephone network.
PSU Power Supply Unit.
PTCH Packet Traffic CHannel.
PTM-G Point-To-Multipoint-GPRS.
PTM-M Point-To-Multipoint-Multicast.
P-TMSI Packet-TMSI.
PTP Point-To-Point (as in PTP-CLNS).
PTP-M Point-To-Point-Multicast.
PTP-CLNS PTP-ConnectionLess Network Service.
PVC Permanent Virtual Circuit.
PVC PSG Virtual Channel. A data and signalling communication
path across the Ghee-interface between remote PSG entities.

68P02903W01-O
FIELD TRIAL
Q GPRS-300-101
Q
QOS Quality Of Service.
QoS Quality of Service.
9–28 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 R
R
RA Routeing Area.
RAB Random Access Burst.
RACCH Random Access Control CHannel. A GSM common control
channel used to originate a call or respond to a page.
RACH Random Access CHannel.
RAI Routeing Area Identity.
RAID Redundant Array of Independent Disks.
RAM Random Access Memory.
RCB Radio Control Board (p/o DRCU).
RCI Radio Channel Identifier.
RCP Radio Control Processor.
RCU Radio Channel Unit. Contains transceiver, digital control
circuits, and power supply (p/o BSS) (see DRCU).
RDB Requirements DataBase.
Revgen A Motorola DataGen utility for producing an MMI script from a
binary object database.
RF Radio Frequency.
RFC, RFCH Radio Frequency Channel. A partition of the system RF
spectrum allocation with a defined bandwidth and centre
frequency.
RFI Radio Frequency Interference.
RFM Radio Frequency Module.
RJ45 Network cable/Connector type.
RL ReLay.
RLC Radio Link Control.
RLCI Radio Link Control Interface.
RLP Radio Link Protocol. An ARQ protocol used to transfer user
data between an MT and IWF. See GSM 04.22.
RS232 Standard serial interface.
RSM Router Switch Module.
RSLP Radio System Link Processor.
RSS Radio SubSystem (replaced by BSS).
RTD RLC-block-equivalent Transit Delay.
Rx Receive (uplink).
RXCDR Remote transcoder.

68P02903W01-O
FIELD TRIAL
S GPRS-300-101
S
S/W (or SW) SoftWare.
SACCH Slow Associated Control CHannel. A GSM control channel
used by the MS for reporting RSSI and signal quality
measurements.
SACCH/C4 Slow Associated Control CHannel/SDCCH/4.
SACCH/C8 Slow Associated Control CHannel/SDCCH/8.
SACCH/T Slow Associated Control CHannel/Traffic channel.
SACCH/TF Slow Associated Control CHannel/Traffic channel Full rate.
SAP 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.
SAPI Service Access Point Indicator (identifier).
SB Synchronization Burst (see Synchronization burst).
S-CDR SGSN-Call Detail Record.
SCH Synchronization CHannel. A GSM broadcast control channel
used to carry information for frame synchronization of MSs
and identification of base stations.
SCCP Signalling Connection Control Part (6-8).
SDCCH Stand-alone Dedicated Control CHannel(s). A GSM control
channel where the majority of call setup occurs. Used for MS
to BTS communications before MS assigned to TCH.
SDU Service Data Unit.
SE Supervisor Engine.
SFH Slow Frequency Hopping.
SGSN Serving GPRS Support Node. SGSN is a set of three cards
that includes the following: Control Function (CF) module, the
Gn module, and the Gb card.
SGSN-CF SGSN-Control Function (Card).
SGSN-CONTROL SGSN-CONTROL function.
SGSN-GBPROC SGSN-Gb Processor.
SGSN module This module is a 3-card set of equipment contained within a
19 inch CompactPCI shelf. The 3-card set includes Control
Function module, a Gn module, and a Gb module.
SGSN-OAMP SGSN-Operations And Maintenance Processor.
SGSN-TF SGSN-Transmission Function (card).
Shelf Management The Shelf Management module is a 2-card set that is located
Module in the GSN shelf. Each Shelf Management module contains a
system slot (SS) processor module (card) and a bus bridge
module (card). The Shelf Management module performs the
bus control functions, 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
shelf contains two Shelf Management Units (4 cards in total).
SM Short Message.
9–30 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 S
SME Short Message Entity.

SMI Short Message Identifier.....?
SMS Short Message Service.
SMS-C Short Message Service-Centre.
SMS-GMSC SMS-Gateway Mobile Switching Centre.
SMS-IWMSC SMS-InterWorking Mobile Switching Centre.
SMS-SC SMS-Service Centre.
SN-PDU SubNetwork-Protocol Data Unit.
SNDCP SubNet Dependent Control Protocol.
SNDCP SubNetwork Dependent Convergence Protocol.
SNMP Single Network Management Protocol (MIB).
SOA Suppress Outgoing Access (CUG SS).
Spare A module 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.
Spare B module 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.
SPC Signalling Point Code.
SPI Signalling Point Inaccessible.
SS System Slot.
SS7 Signalling System 7 (an ITU-TSS standard).
SS7 module The SS7 module provides the logical interface to the HLR,
MSC/VLR, and SM-SC. An SS7 module has up to four E1
interfaces that usually connect to an SS7 Signalling Transfer
Point (STP) pair. The SS7 module has a unique IP address
within the GSN complex. It is directly connected to the GSN
Communications Hub through a 100BaseT port. See also C7.
SCCP
SSP Service Switching Point (an intelligent network element).
STP Signalling Transfer Point.
Sun Cluster Sun Cluster is a redundant pair of Sun Netra t 1125s and Sun
Netra st D1000s. The ISS functionality is provided by the Sun
Netra t 1125s, and the pair of Sun Netra st D1000s provide
the high availability storage system.
Superframe 51 traffic/associated control multiframes or 26
broadcast/common control multiframes (period 6.12s).
Super user User account that can access all files, regardless of
protection settings, and control all user accounts.
SVC Switch Virtual Circuit.
SYM SYstem information Manager.
Synchronization burst Period of RF carrier less than one timeslot whose modulation
bit stream carries information for the MS to synchronize its
frame to that of the received signal.

68P02903W01-O
FIELD TRIAL
T GPRS-300-101
TA Timing Advance.
TACS Total Access Communications System (European analogue
cellular system).
TAF Terminal Adaptation Function.
TBF Temporary Block Flow.
TCAP Transaction Capabilities Application Part.
TCH Traffic CHannel. GSM logical channels which carry either
encoded speech or user data.
TCH/F A full rate TCH.
TCH/F2.4 A full rate TCH at 2.4 kbit/s.
TCH/FS A full rate Speech TCH.
TCH/H A half rate TCH.
TCH/H2.4 A half rate TCH at 2.4 kbit/s.
TCH/H4.8 A half rate TCH at 4.8 kbit/s.
TCH/HS A half rate Speech TCH).
TCP/IP Transmission Control Protocol/Internet Protocol.
TCU Transceiver Control Unit.
TDM Time Division Multiplexing.
TDMA Time Division Multiple Access.
TDMA Time Domain Multiple Access.
TE Terminal Equipment. Equipment that provides the functions
necessary for the operation of the access protocols by the
user.
Telnet
TFTP Trivial File Transfer Protocol.
TID Tunnel IDentifier.
Timeslot The multiplex subdivision in which voice and signalling bits
are sent over the air. Each RF carrier is divided into 8
timeslots.
Timing advance 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.
TLLI Temporary Logical Link Identity.
TLV Type, Length and Value.
TM Traffic Manager.
TMCP Transition Module Control Processor.
TMSI Temporary Mobile Subscriber Identity.
Traffic channels Channels which carry user’s speech or data (see also TCH).
TRAU Transcoder Rate Adaption Unit.
9–32 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 T
TRS Timeslot Resource Shifter.

TS Time Service (Server).
TS TimeSlot (see Timeslot).
TSA TimeSlot Acquisition.
TSS
TSW Timeslot SWitch.
TTL Time-To-Line.
TTLI
Tx Transmit (downlink).

68P02903W01-O
FIELD TRIAL
U GPRS-300-101
U
UDI Unrestricted Digital Information.
UDP User Datagram Protocol.
UDP/TCP User Datagram Protocol/Transmission Control Protocol.
UL UpLink.
ULC UpLink Concatenator.
Um Air interface. Interface between BTS and mobile.
UMTS Universal Mobile Telecommunications Systems
Uplink Physical link from the MS towards the BTS (MS transmits,
BTS receives).
Useful part of burst That part of the burst used by the demodulator; differs from
the full burst because of the bit shift of the I and Q parts of
the GMSK signal.
USF Uplink Status Flag.
USSD Unstructured Supplementary Service Data.
UTC Universal Time Coordinated.
UUS User-to-User Signalling supplementary service.
9–34 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 V
V
VC Virtual Circuit.
VIP2 T1/E1 serial module.
VLR Visitor Location Register. A GSM network element which
provides a temporary register for subscriber information for a
visiting subscriber. Often a part of the MSC.
VPLMN Visited PLMN.
VPN Virtual Private Network.

68P02903W01-O
FIELD TRIAL
W GPRS-300-101
W
WAN Wide Area Network.
WS Work Station. The remote device via which O&M personnel
execute input and output transactions for network
management purposes.
WSF Work Station Function block.
WWW World Wide Web.
9–36 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101 X
X
X.25 CCITT specification and protocols for public packet-switched
networks (see PSPDN).
X.25 link A communications link which conforms to X.25 specifications
and uses X.25 protocol (NE to OMC links).
XCDR TransCoDerR (where X is trans).

68P02903W01-O
FIELD TRIAL
Z GPRS-300-101
9–38 15th Sep 99

68P02903W01-O
FIELD TRIAL
Index
15th Sep 99 System Information: GPRS Overview I–1

68P02903W01-O
FIELD TRIAL
GPRS-300-101
I–2 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101
A architecture
GGSN, 4–14, 4–16
PCU, 3–5
A interface, 4–27
SGSN, 4–11, 4–13, 4–16
frame channel, 4–28
Attach support: Class A, B, C mobiles, software
PAA DP context, MS-initiated, deactivation procedure, features, 8–33
5–37
audible indicator, software features, 8–54
Abbreviations authentication, software features, 8–37
A, 9–2
B, 9–4
C, 9–6 B
D, 9–10
E, 9–12 background statistics, 7–8
F, 9–13
BASE-T switch module, functions, 4–20
G, 9–14
H, 9–17 between SGSN and GGSN, encapsulation, 5–40
I, 9–18 between SGSN and MS, encapsulation, 5–40
K, 9–20
BGP, protocol, 2–23
L, 9–21
M, 9–22 bridge
N, 9–24 board, 3–6
Numbers, 9–1 PCI to PCI, 3–6
O, 9–25 BSSGP
P, 9–26 functions, 4–34
Q, 9–28 protocol, 2–20, 2–22
R, 9–29 SGSN-BSS, 4–33
S, 9–30
burst structure
T, 9–32
mode of operation, 5–10
U, 9–34
timing advance, 5–7
V, 9–35
W, 9–36
X, 9–37
Z, 9–38
C
account metering and collection, software features, C7 signalling, 4–27
8–40 cabinet
commhub, 6–6
activation procedure GSN, 4–5, 6–4
PDP context, 5–25 ISS, 6–7
PDP context, anonymous access, 5–32 PCU, 6–2
PDP context, network-requested, 5–27
PDP context, successful network-requested, 5–28 cabinets, overview, 6–1
PDP context, unsuccessful network-requested, cage
5–29 GSN, 6–5
PCU, 6–3
ACTIVE state, session management, 5–22
CCCH paging manager, functions, 3–9
active state, session management, 5–23
CCDSP, control information, 4–26
air interface, error detector, 7–12 channel coding
alarm display, software features, 8–53 functions, 5–11
schemes for, 5–11
alarm printing service, software features, 8–55
channel format, multiplexed links, 4–30
An, 4–8 channels, 4–27
application protocols, GPRS, 2–20 channels and frames, 2–6

68P02903W01-O
FIELD TRIAL
GPRS-300-101
chapter 1, about, 1–1 deactivation procedure

AA PDP context, MS-initiated, 5–37
characteristics, frame relay, 4–33
PDP context, GGSN initiated, 5–36
charging gateway, software features, 8–41 definition
chassis mobility management, 5–16
GSN CommHub, 4–18 session management, 5–22
PCU, 3–10 definitions
ciphering, software features, 8–31 E1 link, 4–26
T1 link, 4–26
coding, transmissions, 4–29
description
commhub GGSN, 4–14
cabinet, 6–6 GSN, 4–2
functions, 4–18 ISS, 4–21
commhub modules, GSN, 4–19 PCU, 3–2
SGSN, 4–11
compare PCU and SGSN configuration, software
features, 8–60 descriptions
MCP750 board, 7–15
component overview, GPRS, 2–9 PCU board, 7–13
compression PCU functions, 7–12
64 kbit/s, 4–29 PICP board, 7–13
TCP/IP, 4–9 PPB board, 7–14
V.42 data, 4–10 PRP board, 7–13
PRPCompactPCI board, 7–14
concentrator I/O card, functions, 4–20 PSP board, 7–13
configuration, PCU, 3–12 DNS, functions, 4–22
configuration management, software features, 8–58 documentation coding, 1–3
configuration options, GSN, 4–38 Domain Name Service, (DNS), 4–8
connectivity, GSN CommHub, 2–15 Domain Name Service. See DNS, 4–8
continuous process, timing advance, 5–8 downlink segmentor, functions, 3–10
control DPROC, 3–7

function, 4–13, 4–16 (PICP), 3–7
functions, 3–18 (PRP), 3–8
dynamic adaptation of coding schemes, software
control information, CCDSP, 4–26
features, 8–9
CS-1, 5–12
CS-2, 5–13
E
CS-3, 5–14
E1, PMC, 3–10
CS-4, 5–15
E1 interface
Cy, 4–8 PCU to BSC, 2–15
physical links, 2–14
E1 link, definition, 4–26
D EGP, protocol, 2–23
databases, DNS, 4–8, 4–22 EIR, 2–12
DataGen support for GPRS, software features, 8–20 elements, GSN, 4–5
de-activation procedure encapsulation
PDP context, anonymous access, between SGSN and GGSN, 5–40
GGSN-initiated, 5–38 between SGSN and MS, 5–40
PDP context, MS-initiated, 5–35 functions, 5–40
I–4 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101
environment, PCU, 3–3 LAN bridge/router card, 4–19

MAC/RLC, 5–9
equipment identity register, 2–12
mobile reachable timer, 5–21
equipment, GPRS hardware, this manual applies to, moving from IDLE to READY, 5–18, 5–19
1–1 moving from READY to IDLE, 5–19, 5–20
error detector, air interface, 7–12 moving from READY to STANDBY, 5–19
moving from STANDBY to IDLE, 5–18
moving from STANDBY to READY, 5–18
PACCH, 5–3
F packet routeing and transfer, 5–39
fault management, software features, 8–62 packet scheduler, 3–9
packet terminal adaptation, 5–40
fault tolerance, PCU, 3–11 PAGCH, 5–2
FBM, functions, 3–10 PBCCH, 5–3
PCCCH, 5–2
features PCCCH on 51-multiframe, 5–4
Help, 8–57 PCCCH on 52-multiframe, 5–4
Motorola MCP750, 7–11 PCU system, 3–18
overview, 2–7 PDP address, 5–24
features summary PDP, context activation, modification, and
GSN, 8–21 de-activation, 5–24
PDTCH, 5–3
OMC-G, 8–46, 8–47
periodic RA update timer, 5–21
PCU, 8–3
PNCH, 5–2
FR, protocol, 2–24 PPCH, 5–2
frame relay PRACH, 5–2
characteristics, 4–33 PRP, 3–9
interface, 2–17 PSP, 3–6
PTCH, 5–3
frames and channels, 2–6 radio, 3–18
frequency hopping of PDCH, software features, 8–11 radio channel groups, 5–2
READY timer, 5–20
FTP, protocol, 2–23 relay, 5–39
function SGSN, 3–18
control, 4–13, 4–16 STANDBY timer, 5–20
transmission, 4–16 state transitions, 5–18
supervisor engine module, 4–20
functional entities and hardware mapping TRS, 3–10
GGSN, 4–16 uplink concentrator, 3–10
SGSN, 4–13 USF, 5–10
functions
BASE-T switch module, 4–20
BSSGP, 4–34
G
CCCH paging manager, 3–9 GB, processes, 3–19, 7–16
channel coding, 5–11 Gb, interface, 3–17
commhub, 4–18
concentrator I/O card, 4–20 Gb interface, software features, 8–13
control, 3–18 GBM, functions, 3–6
DNS, 4–22 Gd, interface, 2–17
downlink segmentor, 3–10
Gf, interface, 2–17
encapsulation, 5–40
FBM, 3–10 Gg, 4–8
GBM, 3–6 GGSN
GWM, 3–6 architecture, 4–14, 4–16
I/O, 3–10 description, 4–14
IDLE/STANDBY/READY state, 5–18 functional entities and hardware mapping, 4–16
ISS, 4–22 transmission function, 4–15

68P02903W01-O
FIELD TRIAL
GPRS-300-101
GGSN/SGSN GPRS
hardware, 4–7 application protocols, 2–20
shelf unit, 4–6 component overview, 2–9
introduction, 2–10
network elements, 2–9
GGSN-control, 4–14 network subsystem, 2–13
overview, 2–4
Gi phase 2, 2–7
interface, 2–16 protocol stack, 2–21
interfaces, 4–36 radio subsystem, 2–3
resources allocation, 5–5
software features, 8–1
Gi-e, interface, 4–36 time allocation manager, 7–12
GPRS architecture, overview, 2–3
Gi-i, interface, 4–37
GPRS backbone (Gn), software features, 8–24
General Packet Radio Service, 2–1 GPRS BSS, 2–11
GPRS coding schemes, software features, 8–8
Glossary of technical terms GPRS elements, GSN, 2–5
A, 9–2
GPRS infrastructure, GSN, 4–3
B, 9–4
C, 9–6 GPRS IP network backbone, software features, 8–22
D, 9–10 GPRS OMC-G, software features, 7–2
E, 9–12 GPRS OMC-R (PCU), software features, 8–15
F, 9–13 GPRS publications, 1–2, 1–8
G, 9–14
GPRS radio channel allocation, software features,
H, 9–17
8–5
I, 9–18
K, 9–20 GPRS service node, 2–11
L, 9–21 GPRS services, introduction, 2–2
M, 9–22 GPRS Support Node (GSN), 4–1
N, 9–24 Gr, interface, 2–18
Numbers, 9–1
Gs, interface, 2–19
O, 9–25
P, 9–26 GSM, system functions, 4–8
Q, 9–28 GSN, 2–11
R, 9–29 cabinet, 4–5, 6–4
S, 9–30 cage, 6–5
T, 9–32 commhub modules, 4–19
configuration options, 4–38
U, 9–34
description, 4–2
V, 9–35 elements, 4–5
W, 9–36 features summary, 8–21
X, 9–37 GPRS elements, 2–5
Z, 9–38 GPRS infrastructure, 4–3
interfaces, 2–16
Gn, interface, 2–16, 4–38 network elements, 4–3
OMC-G management, from, 4–10
peripheral devices, 4–7
Gp software architecture, 4–4
interface, 2–18 standardized interfaces, 4–31
interfaces, 4–39 system components, 2–11
I–6 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101
GSN CommHub, 4–17 interfaces

chassis, 4–18 A, 4–27
connectivity, 2–15 Gb, 3–17
hardware, 4–18 Gi, 4–36
interfaces, 4–36 Gi-e, 4–36
specifications, 7–17 Gi-i, 4–37
Gn, 4–38
GSN HADA, specifications, 7–21 Gp, 4–39
GTP, protocol, 2–24 GSN, 2–16
GSN CommHub, 4–36
GWM IP, 2–16
functions, 3–6 PCU, 3–16
processes, 3–19, 7–16 PCU-BTS, 3–16
SGSN, 4–32
SGSN–BSS, 4–32
SGSN-HLR, 4–35
H SGSN-OMC-G, 4–35
SGSN-SMS, 4–35
hardware standardized, 2–16, 4–31
GGSN/SGSN, 4–7 Internal HLRS, 4–9
ISS, 4–21
introduction
PCU, 3–14
GPRS, 2–10
hardware, GPRS equipment, this manual applies to, specifications, 7–1
1–1 IP
help, software features, 8–57 interfaces, 2–16
protocol, 2–24
Heurikon Corp PM/T1 & PM/E1, specifications, 7–12 IP hosts, multiple logical, 4–39
HLR, 2–12 ISS
cabinet, 6–7
HLR interface (Gr), software features, 8–36
description, 4–21
home location register, 2–12 functions, 4–22
hardware, 4–21
how to order manuals, 1–7 specifications, 7–20
I L
LAN bridge/router card, functions, 4–19
IDLE state, mobility management, 5–16 lawful intercept – phase 1, software features, 8–42
IDLE/STANDBY/READY state, functions, 5–18 Linear Predictive Coding, 4–29
inter-SGSN handover, software features, 8–35 LLC, 2–26
protocol, 2–24
interface
load & database management, load & database, 7–6
frame relay, 2–17
Gd, 2–17 load management, software features, 8–63
Gf, 2–17 logical link control, 2–26
Gi, 2–16
Gn, 2–16
Gp, 2–18 M
Gr, 2–18
Gs, 2–19 MAC/RLC, functions, 5–9
OMC-G, 2–15, 2–16 management
SNMP-O&M, 4–9 load & database, 7–6
Um, 2–16 security , 7–9

68P02903W01-O
FIELD TRIAL
GPRS-300-101
map, software features, 8–49 network subsystem, GPRS, 2–13

MCP750 board, descriptions, 7–15 new features, 2–8
medium access mode, software features, 8–6 NMC
DNS secondary server, 4–8, 4–22
mobile user activity procedure, session management,
5–31 time service, providing, 4–10
non–GSN, system components, 2–12
mobile reachable timer, functions, 5–21
NS, protocol, 2–24
mobile station, 2–11
mobility management, 4–9
definition, 5–16 O
IDLE state, 5–16
READY state, 5–17 OMC-G, 2–11, 2–12
STANDBY state, 5–17 features summary, 8–46, 8–47
mode of operation, burst structure, 5–10 interface, 2–15, 2–16
OMC-G management, of, GSN, 4–10
modes, dynamic and fixed allocation, 2–6
on-demand statistics, view, 7–7
modification procedure, PDP context, 5–34
overview
modification procedures, session management, 5–34
cabinets, 6–1
Motorola MCP750 features, 2–7
features, 7–11 GPRS, 2–4
specifications, 7–12 GPRS architecture, 2–3
moving from IDLE to READY, functions, 5–18, 5–19 PCU, 3–1
moving from READY to IDLE, functions, 5–19, 5–20

moving from READY to STANDBY, functions, 5–19 P
moving from STANDBY to IDLE, functions, 5–18 PACCH, functions, 5–3
moving from STANDBY to READY, functions, 5–18 packet data network, 2–12
MPROC, 3–5 packet routeing, transfer function, 5–39
(PSP), 3–6
packet routeing and transfer, functions, 5–39
MSC/VLR, 2–12
packet scheduler, functions, 3–9
multiframe, structure, 5–4
packet terminal adaptation, functions, 5–40
multiplexed links
packetiser, 7–12
channel format, 4–30
subrate, 4–29 PAGCH, functions, 5–2
multiplexing, subrate, 4–29 parameter views, software features, 8–52
PBB, 3–6
N PBCCH, functions, 5–3

PCCCH, functions, 5–2
navigator, software features, 8–48
PCCCH on 51-multiframe, functions, 5–4
network elements
GPRS, 2–9 PCCCH on 52-multiframe, functions, 5–4
GSN, 4–3 PCI to PCI, bridge, 3–6
network protocols, 2–20 PCM, channel format, 4–27
I–8 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101
PCU PDP, context activation, modification, and

architecture, 3–5 de-activation, functions, 5–24
cabinet, 6–2 PDTCH, functions, 5–3
cage, 6–3
chassis, 3–10 performance, 2–7
configuration, 3–12 performance management, software features, 8–61
description, 3–2
periodic RA update timer, functions, 5–21
environment, 3–3
fault tolerance, 3–11 peripheral devices, GSN, 4–7
features summary, 8–3 phase 2, GPRS, 2–7
hardware, 3–14
physical links, E1 interface, 2–14
interfaces, 3–15, 3–16
overview, 3–1 PICP, 3–7
processes, 3–18, 7–15 PICP board, descriptions, 7–13
purpose, 3–4
remote, 3–5 PMC, E1, 3–10
specifications, 7–11 PNCH, functions, 5–2
summary, 3–2
point-to-point GPRS service, software features, 8–3
system & control functions, 3–18
system functions, 3–18 polled statistics, view, 7–8
PCU board, descriptions, 7–13 power control: uplink/downlink, software features,
8–12
PCU functions, descriptions, 7–12
PPB board, descriptions, 7–14
PCU interface (Gb), software features, 8–45
PPCH, functions, 5–2
PCU load balancing & sharing, software features, PRACH, functions, 5–2
8–14
processes
PCU system, overview, 3–4 GB, 3–19, 7–16
PCU-BTS, interface, 3–16 GWM, 3–19, 7–16
PCU, 3–18, 7–15
PDCH, resource release, 5–5 PRP, 3–19, 7–15
PDN, 2–12 protection procedure, session management, 5–30
PDN interface (Gi), software features, 8–26 protocol stack, GPRS, 2–21
PDP address, functions, 5–24 protocols
PDP context BGP, 2–23
BSSGP, 2–20, 2–22
activation procedure, 5–25
EGP, 2–23
modification procedure, 5–34
FR, 2–24
PDP context, anonymous access, activation FTP, 2–23
procedure, 5–32 GTP, 2–24
PDP context, anonymous access, GGSN-initiated, IP, 2–24
de-activation procedure, 5–38 LLC, 2–24
NS, 2–24
PDP context, GGSN initiated, deactivation procedure, SNDCP, 2–25
5–36 SNMP, 2–25
PDP context, MS-initiated, de-activation procedure, TCP/IP, 2–25
5–35 UDP/TCP, 2–25
PDP context, network-requested, activation PRP

procedure, 5–27 functions, 3–9, 3–10
processes, 3–19, 7–15
PDP context, successful network-requested,
activation procedure, 5–28 PRP board, descriptions, 7–13
PRPCompactPCI board, descriptions, 7–14
PDP context, unsuccessful network-requested,
activation procedure, 5–29 PSP, functions, 3–6

68P02903W01-O
FIELD TRIAL
GPRS-300-101
PSP board, descriptions, 7–13 schemes for, channel coding, 5–11

PTCH, functions, 5–3 secure tunnelling (Gi), software features, 8–32
security, management, 7–9
PTP-CLNS, 4–9
session management
PTP-CLNS (static IPv4), software features, 8–38 ACTIVE state, 5–22
PTP-CONS, 4–9 active state, 5–23
definition, 5–22
mobile user activity procedure, 5–31
modification procedures, 5–34
Q protection procedure, 5–30
QoS, management, 4–9 SGSN
architecture, 4–11, 4–13, 4–16
QoS profile classes, software features, 8–30 description, 4–11
functional entities and hardware mapping, 4–13
functions, 3–18
R interfaces, 4–32
specifications, 7–10
radio, functions, 3–18 transmission function, 4–12, 4–13
radio channel groups, functions, 5–2 SGSN–BSS, interface, 4–32
SGSN-BSS, BSSGP, 4–33
READY state, mobility management, 5–17
SGSN-control, 4–11
READY timer, functions, 5–20 SGSN-HLR, interface, 4–35
real-time clock, time service, 4–22 SGSN-OMC-G, interface, 4–35
relay, functions, 5–39 SGSN-SMS, interface, 4–35
shelf unit, GGSN/SGSN, 4–6
remote transcoder, 2–13
short message system, 2–13
resource release, PDCH, 5–5 SMS, 2–13
resources allocation, GPRS, 5–5 SNDCP, protocol, 2–25
RSM, 4–19 SNMP, protocol, 2–25
SNMP management interface (TCP/IP), software
RXCDR, 2–13
features, 8–44
functions, 4–23
SNMP-O&M, interface, 4–9
software architecture, GSN, 4–4
S software features
account metering and collection, 8–40
sanity check an SGSN/GGSN database, software alarm display, 8–53
features, 8–59 alarm printing service, 8–55
Attach support: Class A, B, C mobiles, 8–33
audible indicator, 8–54
authentication, 8–37
charging gateway, 8–41
ciphering, 8–31
compare PCU and SGSN configuration, 8–60
configuration management, 8–58
DataGen support for GPRS, 8–20
dynamic adaptation of coding schemes, 8–9
fault management, 8–62
frequency hopping of PDCH, 8–11
I–10 15th Sep 99

68P02903W01-O
FIELD TRIAL
GPRS-300-101
Gb interface, 8–13 specifications

GPRS, 8–1 GSN CommHub, 7–17
GPRS backbone (Gn), 8–24 GSN HADA, 7–21
GPRS coding schemes, 8–8 Heurikon Corp PM/T1 & PM/E1, 7–12
introduction, 7–1
GPRS IP network backbone, 8–22
ISS, 7–20
GPRS OMC-G, 7–2 Motorola MCP750, 7–12
GPRS OMC-R (PCU), 8–15 PCU, 7–11
GPRS radio channel allocation, 8–5 SGSN, 7–10
help, 8–57 standardized interfaces, 2–16
HLR interface (Gr), 8–36 GSN, 4–31
inter-SGSN handover, 8–35
STANDBY state, mobility management, 5–17
lawful intercept – phase 1, 8–42
load management, 8–63 STANDBY timer, functions, 5–20
map, 8–49 state transitions, functions, 5–18
medium access mode, 8–6 statistics, background, 7–8
navigator, 8–48
structure, multiframe, 5–4
parameter views, 8–52
PCU interface (Gb), 8–45 subrate
PCU load balancing & sharing, 8–14 multiplexed links, 4–29
multiplexing, 4–29
PDN interface (Gi), 8–26
performance management, 8–61 supervisor engine module, functions, 4–20
point-to-point GPRS service, 8–3 support of mobile classes, software features, 8–7
power control: uplink/downlink, 8–12 SYM, functions, 3–10
PTP-CLNS (static IPv4), 8–38
system, overview, 8–2
QoS profile classes, 8–30
sanity check an SGSN/GGSN database, 8–59 system & control functions, PCU, 3–18
secure tunnelling (Gi), 8–32 system components
SNMP management interface (TCP/IP), 8–44 GSN, 2–11
support of mobile classes, 8–7 non–GSN, 2–12
table, 8–50 system functions, GSN, 4–8
TCP/IP header/V.42bis data compression, 8–29
time server, 8–23
two phase packet access, 8–10 T
user profile editor, 8–56
T1 link, definition, 4–26
using OMC-G alarm display, 8–53
using OMC-G alarm printing service, 8–55 table, software features, 8–50
using OMC-G audible indicator, 8–54 TCP/IP, protocol, 2–25
using OMC-G fault management, 8–62 TCP/IP header, compression, 4–9
using OMC-G help, 8–57
TCP/IP header/V.42bis data compression, software
using OMC-G load management, 8–63 features, 8–29
using OMC-G map, 8–49
TE, 2–13
using OMC-G navigator, 8–48
using OMC-G parameter view, 8–52 terminal equipment, 2–13
using OMC-G table, 8–50 time allocation manager, GPRS, 7–12
using OMC-G user profile editor, 8–56 time server, software features, 8–23
using OMC-G workspace, 8–47
Time Service, (TS), 4–10
view & modify SGSN/GGSN configuration, 8–58
viewing SGSN/GGSN statistics, 8–61 time service, real-time clock, 4–22
workspace, 8–47 Time Service (TS), 4–10

68P02903W01-O
FIELD TRIAL
GPRS-300-101
timing advance using OMC-G audible indicator, software features,

burst structure, 5–7 8–54
continuous process, 5–8 using OMC-G fault management, software features,
transcoding 8–62, 8–63
at BSC, 4–24
using OMC-G help, software features, 8–57
remote, 4–25
using OMC-G map, software features, 8–49
transfer function, packet routeing, 5–39
transmission using OMC-G navigator, software features, 8–48
coded, 4–29 using OMC-G parameter view, software features,
function, 4–16 8–52
systems, 4–27
using OMC-G table, software features, 8–50
transmission function
GGSN, 4–15 using OMC-G user profile editor, software features,
8–56
SGSN, 4–12, 4–13
TRS, functions, 3–10 using OMC-G workspace, software features, 8–47
two phase packet access, software features, 8–10

V
U V.42 data, compression, 4–10
UDP/TCP, protocol, 2–25 view
Um, interface, 2–16 on-demand statistics, 7–7
polled statistics, 7–8
Universal Time Coordinated (UTC), 4–10
view & modify SGSN/GGSN configuration, software
updates, to manuals, 1–7 features, 8–58
uplink concentrator, functions, 3–10 viewing SGSN/GGSN statistics, software features,
user profile editor, software features, 8–56 8–61
USF, functions, 5–10
using OMC-G alarm display, software features, 8–53
W
using OMC-G alarm printing service, software
features, 8–55 workspace, software features, 8–47
I–12 15th Sep 99

68P02903W01-O
FIELD TRIAL

GPRS Overview

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

GPRS Overview

Hochgeladen von

Copyright:

Verfügbare Formate

For:rrobot

Printed on:Tue, Mar 21, 2000 09:11:06

15th Sep 99 System Information: GPRS Overview i

Copyrights, notices and trademarks

, MOTOROLA and M-Cell are trademarks of Motorola Inc.

Issue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

15th Sep 99 System Information: GPRS Overview iii

Other documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12

PCU interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–15

15th Sep 99 System Information: GPRS Overview v

Channel groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2

PCU cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2

15th Sep 99 System Information: GPRS Overview vii

OMC-G GSR4 supplemental release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–15

viii 15th Sep 99

Alarm Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–53

15th Sep 99 System Information: GPRS Overview ix

Issue status of this manual

Manual Date of Remarks

Problem GMR Remarks

15th Sep 99 System Information: GPRS Overview 1

Special key sequences

CTRL–c Press the Control and c keys at the same time.

15th Sep 99 System Information: GPRS Overview 3

First aid in case of electric shock

Reporting safety issues

15th Sep 99 System Information: GPRS Overview 5

Warnings and cautions

Example and format

Example and format

15th Sep 99 System Information: GPRS Overview 7

Human exposure to radio frequency energy (PCS1900 only)

Power density (S)

15th Sep 99 System Information: GPRS Overview 9

Uncontrolled Environment Controlled Environment

r+ ǸGPin + Ǹ 43.65 5 + 1.16m

15th Sep 99 System Information: GPRS Overview 11

Beryllium health and safety precautions

Product life cycle

15th Sep 99 System Information: GPRS Overview 13

Devices sensitive to static

15th Sep 99 System Information: GPRS Overview 15

Motorola GSM manual set

15th Sep 99 System Information: GPRS Overview 17

GMR amendment record

GMR number Incorporated by (signature) Date

15th Sep 99 System Information: GPRS Overview 19

15th Sep 99 System Information: GPRS Overview i

15th Sep 99 System Information: GPRS Overview iii

Introduction to GPRS documentation

15th Sep 99 System Information: GPRS Overview 1–1

Motorola GPRS documentation

1–2 15th Sep 99

How does the

Order Number Date of issue Remarks

15th Sep 99 System Information: GPRS Overview 1–3

Figure 1-1 Example breakdown of GPRS publication number

1–4 15th Sep 99

Category 1: What it is.

Category 2: How to use it.

Category 3: How it works.

Category 4: How to prepare it for use.

Category 5: How to maintain it.

Category 6: What it consists of.