Installation and Configuration C-SGSN-1

Installation and Configuration: C-SGSN Data Configuration
31-Jan-2005 Motorola, Inc. All Rights Reserved
CONTROLLED INTRODUCTION
68P02904W52-B 31-Jan-2005
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 the Motorola logo are registered trademarks of Motorola Inc. Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc. All other brands and corporate names are trademarks of their respective owners.
31-Jan-2005
Table of Contents
Contents


Issue status of this manual . . . . . . Version information . . . . . . . Resolution of service requests . . Incorporation of CDCNs. . . . . General information . . . . . . . . . Purpose . . . . . . . . . . . . Feature references . . . . . . . . Cross references . . . . . . . . Data encryption . . . . . . . . . Text conventions . . . . . . . . Reporting safety issues . . . . . . . Procedure . . . . . . . . . . . Warnings and cautions . . . . . . . . Warnings . . . . . . . . . . . . Failure to comply with warnings . Cautions . . . . . . . . . . . . General warnings . . . . . . . . . . Warning labels . . . . . . . . . Specific warnings . . . . . . . . General cautions . . . . . . . . . . Caution labels. . . . . . . . . . Specific cautions . . . . . . . . Devices sensitive to static . . . . . . Special handling techniques . . . Motorola manual set . . . . . . . . . Ordering manuals and CD-ROMs Manual amendment . . . . . . . . . GMR availability . . . . . . . . CDCN availability . . . . . . . CDCN instructions . . . . . . . CDCN amendment record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 2 2 3 3 3 4 5 5 6 6 7 7 7 7 9 9 9 13 13 13 14 14 15 15 16 16 16 17 18
Chapter 1: Overview
Data to Be Configured and Data Configuration Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . Points for Attention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 2 1- 4 1- 5
68P02904W52-B 31-Jan-2005
Contents
Chapter 2: Hardware Configuration

Hardware Configuration Overview Configuring Rack . . . . . . . . Description . . . . . . . . . Procedure . . . . . . . . . Example . . . . . . . . . . Reference . . . . . . . . . Configuring Subrack . . . . . . Description . . . . . . . . . Procedure . . . . . . . . . Example . . . . . . . . . . Reference . . . . . . . . . Configuring Board . . . . . . . Description . . . . . . . . . Procedure . . . . . . . . . Example . . . . . . . . . . Reference . . . . . . . . . Configuring Port . . . . . . . . Description . . . . . . . . . Procedure . . . . . . . . . Example . . . . . . . . . . Reference . . . . . . . . . Configuring Clock. . . . . . . . Description . . . . . . . . . Procedure . . . . . . . . . Example . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 2 2- 3 2- 3 2- 3 2- 3 2- 4 2- 5 2- 5 2- 5 2- 5 2- 6 2- 7 2- 7 2- 8 2-10 2-14 2-18 2-18 2-18 2-19 2-19 2-21 2-21 2-21 2-21 2-22
Chapter 3: SS7 Configuration

SS7 Configuration Overview . . . . . . . . . Configuring Local Office . . . . . . . . . . Description . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Configuring MTP Data . . . . . . . . . . . Description . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . SCCP Configuration . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Configuring MAP (Gr/Gd/Ge/Gf/Lg interface) Description . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Configuring BSSAP+ (Gs interface) . . . . . Description . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 2 3- 3 3- 3 3- 3 3- 3 3- 4 3- 5 3- 5 3- 7 3- 7 3- 8 3-15 3-15 3-16 3-16 3-17 3-24 3-24 3-24 3-24 3-25 3-26 3-26 3-26
ii
68P02904W52-B 31-Jan-2005
Contents
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-26 3-27
Chapter 4: Iu interface Configuration (3G)

Iu interface Configuration Overview . . . Configuring User Plane of Iu Interface . . Description . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . Example . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . Configuring Control Plane of Iu Interface . Description . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . Example . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 2 4- 3 4- 3 4- 4 4- 4 4- 5 4- 9 4- 9 4-11 4-11 4-14
Chapter 5: Gn/Gp Interface Configuration

Gn/Gp Interface Configuration Overview Gn/Gp Interface Route Configuration . . Description . . . . . . . . . . . . Procedure . . . . . . . . . . . . Example . . . . . . . . . . . . . Reference . . . . . . . . . . . . Configure DNS/HOSTFILE . . . . . . Description . . . . . . . . . . . . Procedure . . . . . . . . . . . . Example . . . . . . . . . . . . . Reference . . . . . . . . . . . . Configuring GTP Protocol Parameters . Description . . . . . . . . . . . . Procedure . . . . . . . . . . . . Example . . . . . . . . . . . . . Reference . . . . . . . . . . . . Configuring QoS Parameters . . . . . . Description . . . . . . . . . . . . Procedure . . . . . . . . . . . . Example . . . . . . . . . . . . . Reference . . . . . . . . . . . . Configuring IPSec. . . . . . . . . . . Description . . . . . . . . . . . . Procedure . . . . . . . . . . . . Example . . . . . . . . . . . . . Reference . . . . . . . . . . . . Configuring OSPF. . . . . . . . . . . Description . . . . . . . . . . . . Procedure . . . . . . . . . . . . Example . . . . . . . . . . . . . Reference . . . . . . . . . . . . Configuring RIP. . . . . . . . . . . . Description . . . . . . . . . . . . Procedure . . . . . . . . . . . . Example . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 2 5- 3 5- 3 5- 3 5- 3 5- 4 5- 6 5- 6 5- 6 5- 6 5- 7 5- 8 5- 8 5- 9 5- 9 5- 9 5-10 5-10 5-10 5-10 5-11 5-16 5-16 5-17 5-18 5-19 5-24 5-24 5-24 5-24 5-25 5-28 5-28 5-28 5-28 5-29
68P02904W52-B 31-Jan-2005
iii
Contents
Chapter 6: Gb Interface Configuration (2.5G)

Gb Interface Configuration Overview . . . Configuring Link and Management Entity. Description . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . Example . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . Configuring Protocol Parameters . . . . . Description . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . Example . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . Configuring Cell Reference Parameters . . Description . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . Example . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 2 6- 3 6- 3 6- 4 6- 4 6- 6 6- 9 6- 9 6- 9 6- 9 6-10 6-14 6-14 6-14 6-14 6-15
Chapter 7: MM Configuration
MM Configuration Overview . . . . . . . . . . . . Configuring Authentication and Ciphering Parameters . Description . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . Configuring Timers . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . Configuring PLMN . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . Configuring Paging Parameters. . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 2 7- 3 7- 3 7- 3 7- 3 7- 4 7- 6 7- 6 7- 6 7- 6 7- 7 7- 8 7- 8 7- 8 7- 8 7- 8 7-10 7-10 7-10 7-11 7-11
Chapter 8: SM Configuration
SM Configuration Overview . . . . . . . . . . . . . Configuring SM Parameters . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . Configuring Mapping between PDP Type and APN NI . Description . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88888888882 3 3 3 3 3 6 6 6 6
iv
68P02904W52-B 31-Jan-2005
Contents
Reference . . . . . . . . . . . . . . . . . . . . . Configuring Shared PLMN OI . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . . Configuring IP Address of GGSN supporting MIP or DHCP Description . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
8- 6 8- 8 8- 8 8- 8 8- 8 8- 8 8- 9 8- 9 8- 9 8- 9 8-10
Chapter 9: Service Configuration

Configuring SMS . . . . . . Description . . . . . . . Procedure . . . . . . . Example . . . . . . . . Reference . . . . . . . Configuring CAMEL service. Description . . . . . . . Procedure . . . . . . . Example . . . . . . . . Reference . . . . . . . Configuring LCS . . . . . . Description . . . . . . . Procedure . . . . . . . Example . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9999999999999992 2 2 2 2 4 4 4 5 5 6 6 7 7 8
Chapter 10: Charging Configuration

Charging Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . Configuring Ga Interface Parameters . . . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring CG and Route between SGSN and CG . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Charging Characteristic Parameters and Default Charging Characteristics Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring CDR Optional Field . . . . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Charging Behavior . . . . . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 2 10- 3 10- 3 10- 3 10- 3 10- 3 10- 5 10- 5 10- 6 10- 6 10- 7 10- 9 10- 9 10- 9 10- 9 10-10 10-12 10-12 10-12 10-12 10-12 10-37 10-37
68P02904W52-B 31-Jan-2005
Contents
Procedure . . . . . . . . . . . . . Example . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . Configuring Special Charging Rate Period Description . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . Example . . . . . . . . . . . . . . Reference . . . . . . . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
10-37 10-37 10-37 10-39 10-39 10-39 10-39 10-40
Chapter 11: System Configuration

System Configuration Overview . . . . . . Configuring System Basic Information . . . Description . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Configuring Remote Maintenance Gateway . Description . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Configuring SNMP . . . . . . . . . . . . Description . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Configuring OMC-S/T 2.0 IP Address . . . Description . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Configuring System Time . . . . . . . . . Description . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 2 11- 3 11- 3 11- 3 11- 3 11- 3 11- 5 11- 5 11- 5 11- 5 11- 5 11- 6 11- 6 11- 6 11- 6 11- 7 11- 8 11- 8 11- 8 11- 8 11- 8 11- 9 11- 9 11- 9 11-10 11-10
Chapter 12: Feature Configuration

Feature Configuration Overview Roaming Barred by IMSI . . . Overview of the Function . Description . . . . . . . . Procedure . . . . . . . . Example . . . . . . . . . Reference . . . . . . . . Choosing GGSN by IMSI . . . Overview of the Function . Description . . . . . . . . Procedure . . . . . . . . Example . . . . . . . . . Reference . . . . . . . . RAI IE in Gn . . . . . . . . . Overview of the Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1212121212121212121212121212122 3 3 3 3 4 4 5 5 5 5 6 6 7 7
vi
68P02904W52-B 31-Jan-2005
Contents
Description . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . Detaching Inactive Subscribers . . . . . . . . . . . . Overview of the Function . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . Not detaching inactive subscribers of the specified APN Overview of the Function . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . GPRS Second Authentication in Attach . . . . . . . . Overview of the Function . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . GPRS Second Authentication in RAU . . . . . . . . Overview of the Function . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . Rejecting GPRS Subscribers Attach by APNNI . . . . Overview of the Function . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . . . . . Rejecting GPRS Subscribers Attach by IMSI . . . . . Overview of the Function . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . References . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12- 7 12- 7 12- 7 12- 8 12- 9 12- 9 12- 9 12- 9 12-10 12-10 12-11 12-11 12-11 12-11 12-12 12-12 12-13 12-13 12-13 12-13 12-14 12-14 12-15 12-15 12-15 12-15 12-16 12-16 12-17 12-17 12-17 12-18 12-18 12-18 12-19 12-19 12-19 12-20 12-20 12-20
68P02904W52-B 31-Jan-2005
vii
Contents
This page intentionally left blank.
viii
68P02904W52-B 31-Jan-2005
List of Figures
List of Figures

Figure 1-1: Data configuration flow. . . . . . . . . . . . . . . . . . . . Figure 2-1: The position information of a rack. . . . . . . . . . . . . . . Figure 2-2: Slots in a PSM subrack (3G). . . . . . . . . . . . . . . . . . Figure 2-3: Slots in a PSM subrack (2.5G). . . . . . . . . . . . . . . . . Figure 3-1: DSP configuration. . . . . . . . . . . . . . . . . . . . . . Figure 3-2: Load sharing of links in one link set. . . . . . . . . . . . . . Figure 3-3: Load sharing of links in different link sets. . . . . . . . . . . Figure 3-4: Example of signaling link set/signaling link algorithm selection.. Figure 3-5: SCCP DSP. . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-6: DPC+SSN addressing mode. . . . . . . . . . . . . . . . . . Figure 3-7: DPC+SSN addressing through the transfer of STP B. . . . . . Figure 3-8: DPC+GT addressing mode. . . . . . . . . . . . . . . . . . . Figure 3-9: IMSI-GT conversion.. . . . . . . . . . . . . . . . . . . . . Figure 4-1: IPOA PVC and RNCOA PVC. . . . . . . . . . . . . . . . . Figure 4-2: Networking example. . . . . . . . . . . . . . . . . . . . . Figure 4-3: Optical connection in the example. . . . . . . . . . . . . . . Figure 5-1: Gn/Gp interface networking diagram. . . . . . . . . . . . . . Figure 5-2: Schematic diagram of CBWFQ. . . . . . . . . . . . . . . . . Figure 5-3: Relationship between WRED and the queuing mechanism. . . . Figure 5-4: IPSec configuration networking. . . . . . . . . . . . . . . . Figure 5-5: Relation between IKE and IPSec. . . . . . . . . . . . . . . . Figure 6-1: Gb interface configuration networking. . . . . . . . . . . . . Figure 6-2: Numbering of the ports on UFEU. . . . . . . . . . . . . . . Figure 6-3: Gb protocol stack at the user plane. . . . . . . . . . . . . . . Figure 6-4: Gb protocol stack at the control plane. . . . . . . . . . . . . . Figure 7-1: Scope of ciphering.. . . . . . . . . . . . . . . . . . . . . . Figure 9-1: SMS network architecture. . . . . . . . . . . . . . . . . . . Figure 9-2: LCS network structure. . . . . . . . . . . . . . . . . . . . . Figure 10-1: Ga interface network example. . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1- 2 2- 4 2-10 2-12 3- 9 3-12 3-12 3-13 3-18 3-20 3-20 3-21 3-23 4- 6 4-11 4-12 5- 4 5-11 5-13 5-18 5-23 6- 4 6- 6 6-10 6-10 7- 4 9- 3 9- 8 10- 6
68P02904W52-B 31-Jan-2005
ix
List of Figures
68P02904W52-B 31-Jan-2005
List of Tables
List of Tables

Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2: Service requests resolved in this manual . . . . . . . . . . . . . . . . . . . . . . Table 3: CDCNs incorporated in this manual . . . . . . . . . . . . . . . . . . . . . . . . Table 3-1: Relations between link No, timeslot number and UEPI/UTPI port. . . . . . . . . . Table 3-2: Relationship between the number of link sets/links and the number of 1s in the mask. Table 3-3: SLS allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-4: Number of subsystems related to SGSN. . . . . . . . . . . . . . . . . . . . . . Table 4-1: ATM service characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4-2: Meanings of the parameters related to ATM traffic. . . . . . . . . . . . . . . . . Table 10-1: S-CDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 10-2: M-CDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 10-3: S-SMO-CDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 10-4: S-SMT-CDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 10-5: LCS-MT-CDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 10-6: LCS-MO-CDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 10-7: LCS-NI-CDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
2 2 2 3-11 3-14 3-14 3-19 4- 8 4- 8 10-13 10-20 10-24 10-27 10-31 10-32 10-34
68P02904W52-B 31-Jan-2005
xi
List of Tables
xii
68P02904W52-B 31-Jan-2005
About This Manual

68P02904W52-B 31-Jan-2005
Issue status of this manual
Issue status of this manual

The following shows the issue status of this manual since it was first released.
Version information
The following table lists the versions of this manual in order of issue: Table 1 Manual version history Date of issue 02 Jul 2004 31 Jan 2005 This is a new manual. CONTROLLED INTRODUCTION Remarks
Manual issue A B
Resolution of service requests

The following Service Requests are now resolved in this manual: Table 2 Service requests resolved in this manual GMR Number N/A Remarks Original issue - Controlled introduction
Service Request N/A
Incorporation of CDCNs
The following CDCNs are now incorporated in this manual: Table 3 CDCNs incorporated in this manual GMR Number N/A Remarks
CDCN N/A
68P02904W52-B 31-Jan-2005
General information
General information

Motorola disclaims all liability whatsoever, implied or express, for any risk of damage, loss or reduction in system performance arising directly or indirectly out of the failure of the customer, or anyone acting on the customers behalf, to abide by the instructions, system parameters or recommendations made in this manual If this manual was obtained when attending 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 cellular communications manuals are intended to instruct and assist personnel in the operation, installation and maintenance of the Motorola cellular infrastructure equipment and ancillary devices. It is recommended that all personnel engaged in such activities be properly trained by Motorola.
Failure to comply with Motorolas operation, installation and maintenance instructions may, in exceptional circumstances, lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by Motorola, although they can be used to supplement and enhance the knowledge gained through such training.
Feature references
Most of the manuals in the set, of which this manual is part, are revised to accommodate features released at Motorola General System Releases (GSRn) or GPRS Support Node (GSNn) releases. In these manuals, new and amended features are tagged to help users to assess the impact on installed networks. The tags are the appropriate Motorola Roadmap DataBase (RDB) numbers or Research and Development Prioritization (RDP) numbers. The tags include index references which are listed in the manual Index. The Index includes the entry feature which is followed by a list of the RDB or RDP numbers for the released features, with page references and hot links in electronic copy.
68P02904W52-B 31-Jan-2005
General information
The tags have the format: {nnnn} or {nnnnn} Heading1 Where: {nnnn} {nnnnn} The tags are positioned in text as follows: New and amended feature information New sentence/s or new or amended text. Complete new blocks of text as follows: Full sections under a main heading Full paragraphs under subheadings Tag position in text Immediately before the affected text. Immediately after the headings as follows: Main heading Subheading is: the RDB number the RDP number Heading2
New or amended complete Figures and Tables Warning, Caution and Note boxes. General command syntax, operator input or displays (in special fonts).
After the Figure or Table number and before the title text. Immediately before the affected text in the box. On a separate line immediately above the affected item.
For a list of Roadmap numbers and the RDB or RDP numbers of the features included in this software release, refer to the manual System Information: GSM Overview (68P02901W01), or to the manual System Information: GPRS Overview (68P02903W01), or to the manual System Information: UMTS Overview (68P02905W21).
Cross references
Throughout this manual, references are made to external publications, chapter numbers and section names. The references to external publications are shown in italics, chapter and section name cross references are emphasised blue 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.
68P02904W52-B 31-Jan-2005
General information
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the GSM and GPRS network is encrypted. In order to comply with the export and import requirements of particular countries, this encryption occurs at different levels as individually standardised, or may not be present at all in some parts of the network in which it is normally implemented. The manual set, of which this manual is a part, covers encryption as if fully implemented. Because the rules differ in individual countries, limitations on the encryption included in the particular software being delivered, are covered in the Release Notes that accompany the individual software release.
Text conventions
The following conventions are used in the Motorola cellular infrastructure 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: Heading1 CTRL-c ALT-f CR or RETURN Heading2 Press the Control and c keys at the same time. Press the Alt and f keys at the same time. Press the pipe symbol key. Press the Return key.
68P02904W52-B 31-Jan-2005
Reporting safety issues
Reporting safety issues

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: Procedure 1 Heading1 1 2 3 Safety issue reporting Heading2 Make the equipment concerned safe, for example by removing power. Make no further attempt to adjust or rectify the equipment. Report the problem directly to the Customer Network Resolution Centre, Swindon +44 (0)1793 565444 or China +86 10 88417733 (telephone) and follow up with a written report by fax, Swindon +44 (0)1793 430987 or China +86 10 68423633 (fax). Collect evidence from the equipment under the guidance of the Customer Network Resolution Centre.
68P02904W52-B 31-Jan-2005
Warnings and cautions

The following describes how warnings and cautions are used in this manual and in all manuals of this Motorola manual set.
Warnings
A definition and example follow below:
Definition of Warning
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
Do not look directly into fibre optic cables or 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.
Failure to comply with warnings

Observe all warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola manuals. Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals, or on the equipment itself, violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Cautions
A definition and example follow below:
68P02904W52-B 31-Jan-2005
Definition of Caution
A caution means that there is a possibility of damage to systems, software or individual items of equipment within a system. However, this presents no danger to personnel.
Example and format
Do not use test equipment that is beyond its due calibration date; arrange for calibration to be carried out.
68P02904W52-B 31-Jan-2005
General warnings
General warnings

Observe the following specific warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola manuals: Potentially hazardous voltage. Electric shock. RF radiation. Laser radiation. Heavy equipment. Parts substitution. Battery supplies. Lithium batteries,
Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals, violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Warning labels
Warnings particularly applicable to the equipment are positioned on the equipment. 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
Specific warnings used throughout the GSM manual set are shown below, and will be incorporated into procedures as applicable. These must be observed by all personnel at all times when working with the equipment, as must any other warnings given in text, in the illustrations and on the equipment.
68P02904W52-B 31-Jan-2005
General warnings
Potentially hazardous voltage
This equipment operates from a potentially hazardous voltage of 230 V a.c. single phase or 415 V a.c. three phase supply. To achieve isolation of the equipment from the a.c. supply, the a.c. input isolator must be set to off and locked. When working with electrical equipment, reference must be made to the Electricity at Work Regulations 1989 (UK), or to the relevant electricity at work legislation for the country in which the equipment is used.
Motorola GSM equipment does not utilise high voltages.
Electric shock
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. ALWAYS send for trained first aid or medical assistance IMMEDIATELY. In cases of low voltage electric shock (including public supply voltages), serious injuries and even death, may result. Direct electrical contact can stun a casualty causing breathing, and even the heart, to stop. It can also cause skin burns at the points of entry and exit of the current. In the event of an electric shock it may be necessary to carry out artificial respiration. ALWAYS send for trained first aid or medical assistance IMMEDIATELY. If the casualty is also suffering from burns, flood the affected area with cold water to cool, until trained first aid or medical assistance arrives.
10
68P02904W52-B 31-Jan-2005
General warnings
RF radiation
High RF potentials and electromagnetic fields are present in this 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. Relevant standards (USA and EC), to which regard should be paid when working with RF equipment are: ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10 kHz to 300 GHz).
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.
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, a competent responsible person must ensure that adequate lifting facilities are available. Where provided, lifting frames must be used for these operations. 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 equipment has 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.
68P02904W52-B 31-Jan-2005
11
General warnings
Parts substitution
Do not install substitute parts or perform any unauthorized modification of equipment, because of the danger of introducing additional hazards. Contact Motorola if in doubt to ensure that safety features are maintained.
Battery supplies
Do not wear earth straps when working with stand-by battery supplies. Use only insulated tools.
Lithium batteries
Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective lithium batteries must not be removed or replaced. Any boards containing defective lithium batteries must be returned to Motorola for repair. Contact your local Motorola office for how to return defective lithium batteries.
12
68P02904W52-B 31-Jan-2005
General cautions
General cautions

Observe the following cautions during operation, installation and maintenance of the equipment described in the Motorola manuals. Failure to comply with these cautions or with specific cautions elsewhere in the Motorola manuals may result in damage to the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other cautions given in text, on the illustrations and on the equipment.
Fibre optics
Fibre optic cables must not be bent in a radius of less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices. These metal oxide semiconductor (MOS) devices are susceptible to damage from electrostatic charge. See the section Devices sensitive to static in the preface of this manual for further information.
68P02904W52-B 31-Jan-2005
13
Devices sensitive to static
Devices sensitive to static

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 short circuited together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic foam. Provided the leads are short circuited 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: Always wear an earth strap which must be connected to the electrostatic point (ESP) on the equipment. Leave the short circuit on the leads until the last moment. It may be necessary to replace the conductive foam by a piece of wire to enable the device to be fitted. Do not wear outer clothing made of nylon or similar man made material. A cotton overall is preferable. If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic work surfaces with an anti-static cloth before starting the operation. All metal tools should be used and when not in use they should be placed on an earthed surface. Take care when removing components connected to electrostatic sensitive devices. These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to electrostatic damage. However PCBs should be handled with care, preferably by their edges and not by their tracks and pins, they should be transferred directly from their packing to the equipment (or the other way around) and never left exposed on the workbench.
14
68P02904W52-B 31-Jan-2005
Motorola manual set
Motorola manual set

The Motorola manual sets provide the information needed to operate, install and maintain the Motorola equipment. Manuals for the GSM, GPRS and UMTS products are available on the following media: Printed hard copy. Electronic, as fully navigable PDF files on: The Motorola customer support web site at: (https://mynetworksupport.motorola.com/index.asp). CD-ROM produced in support of a major system software release.
Each CD-ROM includes all manuals related to a specified main GSM, GPRS or UMTS software release, together with current versions of appropriate hardware manuals, and has additional navigation facilities. A snapshot copy of on-line documentation is also included, though it will not be updated in line with subsequent point releases. The CD-ROM does not include Release Notes or documentation supporting specialist products such as MARS or COP.
Ordering manuals and CD-ROMs

Use the Motorola 68Pxxxxxxxx order (catalogue) number to order hard copy manuals or CD-ROMs. All orders must be placed with your Motorola Local Office or Representative.
68P02904W52-B 31-Jan-2005
15
Manual amendment
Manual amendment

Changes to a manual that occur after the printing date are incorporated into the manual using either Customer Documentation Change Notices (CDCNs) or General Manual Revisions (GMRs). Small changes are published in CDCNs. These describe the changes rather than replacing large sections of the manual. They are sent directly to customers and Motorola Local Offices and are accessible on the Motorola Extranet. CDCNs are numbered in sequence using the format: Shortened manual order number Issue identifier CDCN number
For example: 01W23-M-CDCN01 would be the first CDCN produced for 68P2901W23M. Major changes are effected by publishing a GMR. GMRs are also produced in order to incorporate CDCNs when the numbers applying to a particular manual become significant. In this case, the CDCNs numbers are listed in the GMR amendment record. 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.
GMR availability
GMRs are published as follows: Printed hard copy - Complete replacement content or loose leaf pages with amendment list. Remove and replace pages in this manual, as detailed on the GMR instruction sheet.
Motorola service web - Updated at the same time as hard copies. CD-ROM - Updated periodically as required.
CDCN availability
CDCNs are published as follows: PDF distributed electronically - Description of changes, occasionally with replacement loose leaf pages. Motorola service web - Updated at the same time as hard copies.
16
68P02904W52-B 31-Jan-2005
Manual amendment
CDCN instructions
When a CDCN is incorporated in this manual, the record below is completed to record the amendment. Retain the instruction sheet that accompanies each CDCN and insert it in a suitable place in this manual for future reference.
68P02904W52-B 31-Jan-2005
17
Manual amendment
CDCN amendment record

Record the manual insertion of CDCNs in this manual in the following table: CDCN number Incorporated by (signature) Date
18
68P02904W52-B 31-Jan-2005
Chapter
Overview

Office data serves as the basis for normal operations of SGSN. This chapter introduces the office data to be configured and the data configuration flow. The readers of this manual should be acquainted with the basic knowledge of GPRS and WCDMA and the architecture and principle of Motorola C-SGSN.
68P02904W52-B 31-Jan-2005
1-1
Data to Be Configured and Data Configuration Flow
Chapter 1: Overview

Figure 1-1 shows the data to be configured and the data configuration flow. Figure 1-1 Data configuration flow.
Start
Hardware Configuration
SS7 Configuration
Iu Configuration (Skip this step for 2.5G)
Gn/Gp Interface Configuration
Gb Configuration (Skip this step for 3G)
MM Configuration
SM Configuration
Service Configuration
Charging Configuration
System Configuration
Feature Configuration
End
1-2
68P02904W52-B 31-Jan-2005
The term 'Iu interface' in this manual refers to the Iu-PS interface, '2.5G' to the General Packet Radio Service (GPRS) system, and '3G' to the Wideband Code Division Multiple Access (WCDMA) system. Description of this data configuration flow: 1. 2. Hardware configuration acts as the base of other configuration. Therefore, you should perform the hardware configuration first. Interface configuration includes configurations for the interfaces Gr/Gs/Gd/Ge/Gf/Lg, Iu, Gn/Gp/Ga and Gb. The configuration for certain interfaces depends on the actual networking mode of Motorola C-SGSN. You should perform the interface configuration starting from the lower layer to the upper layer of the protocol stack. Interface configuration, MM configuration, SM configuration, service configuration, charging configuration, system configuration and feature configuration are independent of one another. You may start from any configuration after the hardware configuration. Figure 1-1 shows the usual data configuration flow, that is, the sequence of the chapter arrangement in this manual.
3.
4.
68P02904W52-B 31-Jan-2005
1-3
Points for Attention
Chapter 1: Overview
Points for Attention

To ensure successful data configuration, note the following information: 1. 2. 3. Be familiar with the equipment hardware before the data configuration. Be familiar with the requirements raised at the engineering design stage before the data configuration. Collect the data to be negotiated with the peer office before the data configuration. Refer to the corresponding section in each chapter of this manual for data to be negotiated with the peer office.
1-4
68P02904W52-B 31-Jan-2005
Data Configuration Modes

To modify the configuration file, first modify the first line as ';FFFFFFFF FFFFFFFF 00000001', that is, the semicolon should be followed by 8 Fs, 1 space, 8 Fs, 1 space, 7 0s, 1 '1' and 'Enter' in sequence. Otherwise, the modification of the configuration file will not take effect. Before uploading the new MML.TXT, back up the old MML.TXT to the local computer for use upon upload failure.
MML.txt should not include non-ADD commands, such as MOD and RMV. You can only carry out the MOD and RMV commands through the LM.
After modifying the data configuration through the LM, use command SAVE CFG to save the modification. Otherwise, all the modifications will get lost when the system restarts. Some modified parameters do not take effect until you restart the corresponding board.
Perform data configuration in the following two modes: 1. Edit the MML.TXT file You may edit the MML.TXT file to perform system initial configuration or modify a mass of system data. After the edit, you need load the MML.TXT file using ADD CFG or upload it in binary from the FTP Server to \hda0\sgsn\config in the active and standby UOMUs. Then you may restart the UOMUs to make the commands in MML.TXT effective. 2. Carry out a single MML command or multiple MML commands at a time through the Local Manager (LM) of Motorola C-SGSN. You can use this mode to modify a little data. When entering a command through the 'Command Input' box of the LM, note that a parameter in red color is mandatory and the others optional. You may also double click a command in the MML Command Navigator to pop up the 'Command Input' box. At the same time, the online help about this command will display in the 'Help Information' tap page.
68P02904W52-B 31-Jan-2005
1-5
Chapter 1: Overview
1-6
68P02904W52-B 31-Jan-2005
Chapter
Hardware Configuration

68P02904W52-B 31-Jan-2005
2-1
Hardware Configuration Overview
Hardware Configuration Overview

Hardware configuration includes rack configuration, subrack configuration, board configuration, port configuration and clock configuration. After the hardware configuration, the system hardware can normally work. You shall perform hardware configuration in the following sequence: 1. 2. 3. 4. 5. Rack configuration. Subrack configuration. Board configuration. Port configuration. Clock configuration.
2-2
68P02904W52-B 31-Jan-2005
Configuring Rack
Configuring Rack

This section introduces rack configuration. After this configuration, you can configure subracks and boards in a rack.
Description
Preset conditions
None.
Data preparations
Item Basic information. Rack number. Place number. Row number. Data Column number.
Procedure
Step 1 Operation Add a rack. Command ADD RACK
Add racks by rack number in ascending order and delete them in descending order.
Example
;;Add a rack. ADD RACK: RN=0, PN=1, ROW=1, COL=1, PNM="UMTS-UTEST", SRNUM=4;
68P02904W52-B 31-Jan-2005
2-3
Configuring Rack
Reference
The position information of a rack is useful to locate a system alarm. That is, it can help locate the rack of the alarming module. An example of the position information of a rack is illustrated as Figure 2-1. Figure 2-1 The position information of a rack.
Place No.0
Row No.1
RACK NO.2
RACK NO.3
Row No.0
RACK NO.0
RACK NO.1
Column No.0
Column No.1
2-4
68P02904W52-B 31-Jan-2005
Configuring Subrack
Configuring Subrack

This section introduces subrack configuration. After this configuration, you can add boards to subracks.
Description
Preset conditions
A rack already exists before subrack configuration.
Data preparations
Item BNET subrack. PSM subrack. Rack number. Rack number. WDMB binding flag. Subrack number. Subrack number. URCU's ULPU slot number 1 URCU's ULPU port number 1 URCU's ULPU slot number 2 URCU's ULPU port number 2 data
Procedure
Step 1 2 Operation Add a BNET subrack. Add a PSM subrack. Command ADD SUBRACK ADD SUBRACK
Example
;;Add a BNET subrack. ADD SUBRACK: SRN=2, SRT=BNET; ;;Add a PSM subrack. ADD SUBRACK: SRN=0, SRT=PSM, SN1=2, PN1=1, SN2=3, PN2=1;
68P02904W52-B 31-Jan-2005
2-5
Configuring Subrack
Reference
The physical subracks can be divided into two types: PSM and BNET. Only one BNET subrack, but more than one PSM subrack can be configured in the system. Power distribution subracks are connected to PSM subracks through serial port. In this way, the URCUs in a PSM subrack can monitor the connected power distribution subracks. You can connect the power distribution subracks in one rack to only one PSM subrack.
2-6
68P02904W52-B 31-Jan-2005
Configuring Board
Configuring Board

This section introduces the configuration for board information. After this configuration, boards can normally work and you can perform operation and maintenance on boards.
Only boards in PSM subracks (except UPWR, UPMU, UALU and ULPU) and UHPUs in the BNET subrack need be configured. Other boards in the BNET subrack require no manual configuration and they can work properly once they are inserted and powered on.
Description
Preset conditions
The required rack and subrack already exist before board configuration.
Data preparations
Item Basic information. UOMU Subrack number. Relative ULPU slot number 1. Slot number. Relative ULPU port number 1. Board type. Relative ULPU slot number 2. Relative ULPU port number 2. Active/ standby status. IP address and mask of the upper network port. Data
IP address and mask of the upper network port. UCDR Relative ULPU slot number 1. IP address.
Board specs.
Relative ULPU port number 1. Board specs.
Relative ULPU slot number 2.
Relative ULPU port number 2.
Active/ standby status.
UCDR group number.
Cont.
68P02904W52-B 31-Jan-2005
2-7
Configuring Board
Item URCU Active/ standby status. Board specs.
Data IP address (of the URCU in the basic PSM subrack).
USPU
Active/ standby status. Active/ standby status. Active/ standby status. Active/ standby status. Active/ standby status. IP address. Active/ standby status.
Board specs.
UGBI
PMCDOWN type. PMCUP type. Board specs.
PMCUP type. IP address.
Board specs.
UGTP
Board specs.
UICP
UHPU
IP address and mask of FEA. H.110 clock level.
IP address and mask of FEB. Backup Type. Balance mode.
ULAN UEPI/UTPI
Procedure
1. Add UOMU/UCDR. Step 1 2 2. Add URCU. Step 1 Operation Add a URCU. ADD BRD Command Operation Add optical port information. Add UOMU/UCDR. ADD BRD Command ADD BRDCFG
2-8
68P02904W52-B 31-Jan-2005
Configuring Board
1. You need to configure the UOMU before adding URCUs. 2. You need not to configure the backup URCU and the system will configure it automatically. 3. Add UICP/USPU/UGTP/UGBI. Step 1 2 Operation Add active UICP/USPU/UGTP/UGBI. Add standby UICP/USPU/UGTP/UGBI. ADD BRD ADD BRD Command
You need to configure the URCU before adding UICP/USPU/UGTP/UGBIs. 4. Add UEPI/UTPI. Step 1 2 Operation Add UEPI/UTPI. Add UEPI/UTPI clock information. ADD BRD ADD UEPIUTPICFG Command
You need to configure the corresponding IO board before adding UEPI/UTPIs. 5. Add ULAN. Step 1 Operation Add a ULAN. ADD BRD Command
You need to configure the URCU board before adding ULANs. 6. Add UHPU.
68P02904W52-B 31-Jan-2005
2-9
Configuring Board
Add a UHPU by editing MML.txt: Step 1 Operation Add UHPU. ADD BRD Command
You need to configure the UOMU board before adding UHPUs. Dynamically add a UHPU through the LM after system operation: Step 1 2 Operation Activate slot Add a UHPU Command SET BNET_UHPU_LOAD_TYPE ADD BRD
Example
3G example
Figure 2-2
U E P I U S P U
2
Slots in a PSM subrack (3G).

U E P I U S P U
3
P W U SU
I C P
0
U E P I U S P U
4
U E P I U S P U
5
U B I U U R C U
6
U A C U
U B I U U R C U
U A C U
U B S U U C D R
U B S U U C D R
11
U L A N U G T P
12
U F S U U G T P
13
U F S U U O M U
15 16
U P W R U P W R
17
U P W R U P W R
18
I C P
1
U O M U
14
10
Take Figure 2-2 as an example. Suppose UHPUs are inserted in slots 9 and 10 of the BNET subrack (with subrack number of 2). You can add boards (for 3G) in these slots in the following sequence: ;;Add UOMU optical port information ADD BRDCFG: SRN=UOMU, SN1=2, PN1=1, SN2=3, PN2=1; ;;Add UOMU
2-10
68P02904W52-B 31-Jan-2005
Configuring Board
ADD BRD: SRN=0, SN=14, BP=IO, RS=ACTIVE, IP1="10.1.1.1", SNM1="255.255.0.0", IP2="20.1.1.1", SNM2="255.255.0.0", PSRN=0, PSN=15, SPEC=A, BT=UOMU; ADD BRD: SRN=0, SN=15, BP=IO, RS=STANDBY, PSRN=0, PSN=14, SPEC=A, BT=UOMU; ;;Add UCDR optical port information ADD BRDCFG: SRN=UCDR0, SN1=2, PN1=1, SN2=5, PN2=1; ;;Add UCDR ADD BRD: SRN=0, SN=10, BP=IO, RS=ACTIVE, IP1="10.2.1.2", SNM1="255.255.0.0", PSRN=0, PSN=11, UCDRGN=0, SPEC=A, BT=UCDR; ADD BRD: SRN=0, SN=11, BP=IO, RS= STANDBY, PSRN=0, PSN=10, UCDRGN=0, SPEC=A, BT=UCDR; ;;Add URCU ADD BRD: SRN=0, SN=6, BP=IO, RS=ACTIVE, IP1="20.1.1.2", SNM1="255.255.0.0", PSRN=0, PSN=8, SPEC=A, BT=URCU; ;;Add UICP ADD BRD: SRN=0, SN=0, BP=IO, RS=ACTIVE, PSRN=0, PSN=1, SPEC=A, BT=UICP; ADD BRD: SRN=0, SN=1, BP=IO, RS= STANDBY, PSRN=0, PSN=0, SPEC=A, BT=UICP; ;;Add USPU ADD BRD: SRN=0, SN=2, BP=IO, RS=ACTIVE, PSRN=0, PSN=3, PMCUT=USS7, PMCDT=USS7, SPEC=A, BT=USPU; ADD BRD: SRN=0, SN=3, BP=IO, RS= STANDBY, PSRN=0, PSN=2, PMCUT=USS7, PMCDT=USS7, SPEC=A, BT=USPU; ADD BRD: SRN=0, SN=4, BP=IO, RS=ACTIVE, PSRN=0, PSN=5, PMCUT=USS7, PMCDT=USS7, SPEC=A, BT=USPU; ADD BRD: SRN=0, SN=5, BP=IO, RS= STANDBY, PSRN=0, PSN=4, PMCUT=USS7, PMCDT=USS7, SPEC=A, BT=USPU; ;;Add UGTP ADD BRD: SRN=0, SN=12, BP=IO, RS=ACTIVE, IP1="10.2.1.1", SNM1="255.255.0.0", PSRN=0, PSN=13, PMCUT=USEC, SPEC=A, BT=UGTP; ADD BRD: SRN=0, SN=13, BP=IO, RS= STANDBY, PSRN=0, PSN=12, PMCUT=USEC, SPEC=A, BT=UGTP; ;;Add UEPI ADD BRD: SRN=0, SN=2, BP=BACK<ENV>, RS=ACTIVE, BT=UEPI; ADD BRD: SRN=0, SN=3, BP=BACK<ENV>, RS=STANDBY, BT=UEPI; ADD BRD: SRN=0, SN=4, BP=BACK<ENV>, RS=ACTIVE, BT=UEPI; ADD BRD: SRN=0, SN=5, BP=BACK<ENV>, RS=STANDBY, BT=UEPI;
68P02904W52-B 31-Jan-2005
2-11
Configuring Board
ADD UEPIUTPICFG: SRN=0, SN=2, CL=SL, BT=UFEU_PLUS; ADD UEPIUTPICFG: SRN=0, SN=3, CL=SL, BT=UFEU_PLUS; ADD UEPIUTPICFG: SRN=0, SN=4, CL=SL, BT=UFEU_PLUS; ADD UEPIUTPICFG: SRN=0, SN=5, CL=SL, BT=UFEU_PLUS; ;;Add ULAN ADD BRD: SRN=0, SN=12, BP=BACK<ENV>, IP1="20.1.1.3", SNM1="255.255.0.0", BT=ULAN; ;;Add UHPU ADD BRD: SRN=2, SN=9, BP=IO, RS=ACTIVE, IP1="10.2.1.3", SNM1="255.255.0.0", IP2="10.3.1.3", SNM2="255.255.0.0", PSRN=2, PSN=10, BT=UHPU; ADD BRD: SRN=2, SN=10, BP=IO, RS= STANDBY, PSRN=2, PSN=9, BT=UHPU;
2.5G example
Figure 2-3
U U E E P P P I I U E P I U G B I
2
Slots in a PSM subrack (2.5G).

U E P I U G B I
3
W U SU
G B I G B I
1
U E P I U S P U
4
U E P I U S P U
5
U B I U U R C U
6
U A C U
U B I U U R C U
U A C U
U B S U U C D R
U B S U U C D R
11
U L A N U G T P
12
U F S U U G T P
13
U F S U U O M U
15 16
U P W R U P W R
17
U P W R U P W R
18
U O M U
14
10
Take Figure 2-3 as an example. Suppose UHPUs are inserted in slots 9 and 10 in the BNET subrack (with subrack number of 2). You can add boards (2.5G) in these slots in the following sequence: ;;Add UOMU optical port information ADD BRDCFG: SRN=UOMU, SN1=2, PN1=1, SN2=3, PN2=1; ;;Add UOMU ADD BRD: SRN=0, SN=14, BP=IO, RS=ACTIVE, IP1="10.1.1.1", SNM1="255.255.0.0", IP2="20.1.1.1", SNM2="255.255.0.0", PSRN=0, PSN=15, SPEC=A, BT=UOMU; ADD BRD: SRN=0, SN=15, BP=IO, RS=STANDBY, PSRN=0, PSN=14, SPEC=A, BT=UOMU; ;;Configure UCDR optical port information ADD BRDCFG: SRN=UCDR0, SN1=2, PN1=1, SN2=53 PN2=1;
2-12
68P02904W52-B 31-Jan-2005
Configuring Board
;; Add UCDR ADD BRD: SRN=0, SN=10, BP=IO, RS=ACTIVE, IP1="10.2.1.2", SNM1="255.255.0.0", PSRN=0, PSN=11, UCDRGN=0, SPEC=A, BT=UCDR; ADD BRD: SRN=0, SN=11, BP=IO, RS= STANDBY, PSRN=0, PSN=10, UCDRGN=0, SPEC=A, BT=UCDR; ;; Add URCU ADD BRD: SRN=0, SN=6, BP=IO, RS=ACTIVE, IP1="20.1.1.2", SNM1="255.255.0.0", PSRN=0, PSN=8, SPEC=A, BT=URCU; ;; Add UGBI ADD BRD: SRN=0, SN=0, BP=IO, RS=ACTIVE, PSRN=0, PSN=3, PMCUT=UEPC, PMCDT=UFEU, SPEC=A, BT=UGBI; ADD BRD: SRN=0, SN=1, BP=IO, RS=ACTIVE, PSRN=0, PSN=3, PMCUT=UEPC, PMCDT=UFEU, SPEC=A, BT=UGBI; ADD BRD: SRN=0, SN=2, BP=IO, RS=ACTIVE, PSRN=0, PSN=3, PMCUT=UEPC, PMCDT=UFEU, SPEC=A, BT=UGBI; ADD BRD: SRN=0, SN=3, BP=IO, RS= STANDBY, PMCUT=UEPC, PMCDT=UFEU, SPEC=A, BT=UGBI; ;;Add USPU ADD BRD: SRN=0, SN=4, BP=IO, RS=ACTIVE, PSRN=0, PSN=5, PMCUT=USS7, PMCDT=USS7, SPEC=A, BT=USPU; ADD BRD: SRN=0, SN=5, BP=IO, RS= STANDBY, PSRN=0, PSN=4, PMCUT=USS7, PMCDT=USS7, SPEC=A, BT=USPU; ;;Add UGTP ADD BRD: SRN=0, SN=12, BP=IO, RS=ACTIVE, IP1="10.2.1.1", SNM1="255.255.0.0", PSRN=0, PSN=13, PMCUT=USEC, SPEC=A, BT=UGTP; ADD BRD: SRN=0, SN=13, BP=IO, RS= STANDBY, PSRN=0, PSN=12, PMCUT=USEC, SPEC=A, BT=UGTP; ;; Add UEPI ADD BRD: SRN=0, SN=0, BP=BACK<ENV>, RS=ACTIVE, BT=UEPI; ADD BRD: SRN=0, SN=1, BP=BACK<ENV>, RS=ACTIVE, BT=UEPI; ADD BRD: SRN=0, SN=2, BP=BACK<ENV>, RS=ACTIVE, BT=UEPI; ADD BRD: SRN=0, SN=3, BP=BACK<ENV>, RS=STANDBY, BT=UEPI; ADD BRD: SRN=0, SN=4, BP=BACK<ENV>, RS=ACTIVE, BT=UEPI; ADD BRD: SRN=0, SN=5, BP=BACK<ENV>, RS=STANDBY, BT=UEPI; ADD UEPIUTPICFG: SRN=0, SN=0, CL=SL, BT=UFEU_PLUS; ADD UEPIUTPICFG: SRN=0, SN=1, CL=SL, BT=UFEU_PLUS; ADD UEPIUTPICFG: SRN=0, SN=2, CL=SL, BT=UFEU_PLUS;
68P02904W52-B 31-Jan-2005
2-13
Configuring Board
ADD UEPIUTPICFG: SRN=0, SN=3, CL=SL, BT=UFEU_PLUS; ADD UEPIUTPICFG: SRN=0, SN=4, CL=SL, BT=UFEU_PLUS; ADD UEPIUTPICFG: SRN=0, SN=5, CL=SL, BT=UFEU_PLUS; ;;Add ULAN ADD BRD: SRN=0, SN=12, BP=BACK<ENV>, IP1="20.1.1.3", SNM1="255.255.0.0", BT=ULAN; ;; Add UHPU ADD BRD: SRN=2, SN=9, BP=IO, RS=ACTIVE, IP1="10.2.1.3", SNM1="255.255.0.0", IP2="10.3.1.3", SNM2="255.255.0.0", PSRN=2, PSN=10, BT=UHPU; ADD BRD: SRN=2, SN=10, BP=IO, RS= STANDBY, PSRN=2, PSN=9, BT=UHPU;
Reference
Virtual Subrack
Similar to a PSM subrack, the active and standby UOMUs occupy two optical ports of the BNET subrack. They only get power supply from the subrack where it is located. Therefore, the two UOMUs in Motorola C-SGSN are usually regarded as a virtual subrack, namely UOMU subrack, with subrack number 31. Similarly, the active and standby UCDRs in one group also occupy two ports of the BNET subrack. They are also regarded as a virtual subrack, namely UCDR subrack, with subrack number 32 plus UCDR group number.
UOMU
Board position: UOMUs are installed in slots 14 and 15 in the basic PSM subrack (generally the subrack number is 0). Backup information: The UOMU works in 1+1 backup mode. Back board: UFSU ,which requires no data configuration. PMC board: UFIU ,which requires no data configuration. IP address: A UOMU provides two network ports. The upper network port is connected to the LM or remote maintenance terminal. The lower network port is connected with the UMPU through the ULAN, supporting maintenance on the BNET subrack.
URCU
Board position: URCUs are installed in slots 6 and 8 of the PSM subrack. Backup information: The URCU works in 1+1 backup mode. The active URCU is in slot 6 and the standby in slot 8. Back board: UACU, which requires no data configuration. PMC board: UFIU, which requires no data configuration.
2-14
68P02904W52-B 31-Jan-2005
Configuring Board
IP address: You need to configure an IP address only for the active URCU in subrack 0. With this IP address you may configure an IPoA PVC between the active URCU and UMPU. Then the URCU can maintain the BNET subrack through this PVC.
UCDR
Board position: UCDRs are installed in slots 10 and 11 in the basic PSM subrack or in any two slots among slots 0 to 15 in an extended PSM subrack. Backup information: The UCDR works in 1+1 backup mode. The system is configured with four pairs of UCDRs. Each pair consists of one active and one standby UCDR. Each pair must contain one odd-numbered slot and one even-numbered slot for UCDRs. Back board: UBSU, which requires no data configuration. PMC board: UFIU, which requires no data configuration. IP address: The IP address of the active UCDR is mandatory. It is used for the SGSN to communicate with the CG as the external IP address of the Ga interface.
UHPU
Board position: UHPUs are installed in slot 9 through slot 14 in the BNET subrack. Backup information: The UHPU works in 1+1 backup mode. Every two neighboring UHPUs work in active/standby mode. That is, UHPUs in slots (9, 10), (11, 12) and (13, 14) form three pairs of active/standby boards. The UHPUs in slot 9, slot 11 and slot 13 are active and those in slot 10, slot 12 and slot 14 are standby. IP address: Each UHPU contains two forward engines, namely FEA and FEB. They can forward data packets at high speed. You may set an IP address for each engine as well as the IP address of the SGSN GTP-U. You may also set an IP address for only one engine. Because only the forward engine with IP address can forward data, make sure that at least one forward engine has been configured with IP address before PDP context activation. If you set an IP address for both of the engines, the IP addresses must be in different network segments.
USPU
Board position: USPUs are installed in slots 0 to 5 and 10 to 15 in the PSM subrack. Backup information: The USPU works in 1+1 backup mode. The active and standby USPUs must be neighbouring and generally the USPU on the left in each pair is active. Back board: The active/standby configuration of UEPI/UTPI boards is consistent with that of their IO boards USPU. PMC board: A USPU can be configured with two types of PMC boards, USS7 (providing 2 Mbit/s signaling link or 64 kbit/s link) or UMTP (providing 64 kbit/s link).
68P02904W52-B 31-Jan-2005
2-15
Configuring Board
1. When the USPU is to be configured with two PMC boards, their board types must be the same. 2. The PMC board types on the active and standby USPUs must be the same. 3. If you add only one PMC board, USS7 or UMTP, you shall mount it in the lower position (PMCDOWN) on its USPU.
UICP
Board position: UICPs are installed in slot 0 to 5 and 10 to 15 in the PSM subrack. Backup information: UICP works in 1+1 backup mode. The active and standby UICPs must be neighbouring and usually the left UICP in a pair of active/standby UICPs is active. Back board: none PMC board: none
UGTP
Board position: UGTPs are installed in slots 12 and 13 in the basic PSM subrack (the subrack number is 0). Backup information: The UGTP works in 1+1 backup mode, with the active UGTP in slot 12. Back board: none. PMC board: USEC, Only in the upper position. IP address: You shall configure an IP address for the active UGTP as the address of the GTP signaling plane in the SGSN.
UGBI
Board position: You may add UGBIs in slot 0 to 5 and 10 to 15 in a PSM subrack. Backup information: The UGBI works in N+1 (N11) backup mode. There is only one standby UGBI in one subrack. Back board: The UEPI also works in N+1 backup mode, which consistent with UGBI. No E1 cables are connected to the standby UEPI. PMC board: The UEPC provides LLC layer encryption and UFEU provides FR layer functions. Each UGBI is configured with one UFEU (mandatory and one UEPC (optional).
UEPI/UTPI
Board position: UEPI/UTPI is a back board and can be installed in slot 0 to 5 and 10 to 15 in the PSM subrack. Backup information: The backup relation of a UEPI/UTPI is the same as that of the corresponding IO board. If the IO board is a USPU, the UEPI/UTPI will work in 1+1 backup mode. If the IO board is a UGBI, the UEPI/UTPI will work in N+1 backup mode. Port backup information: The backup type of the UEPI/UTPI port includes load sharing mode, 1+1 backup mode and N+1 backup mode.
2-16
68P02904W52-B 31-Jan-2005
Configuring Board
Load sharing mode: used when the IO board is USPU. It indicates each of the UEPIs/UTPIs provides a group of E1/T1 ports (0 to 3 and 4 to 7). You should add two PMC boards to a USPU. The upper PMC board processes the services on the E1/T1 ports of the standby UEPI/UTPI and the lower processes that on the E1/T1 ports of the active UEPI/UTPI. 1+1 backup mode: used when the IO board is USPU. It indicates that only the active UEPI/UTPI provides two groups of E1/T1 ports. The USPU is configured with two PMC boards. The upper one processes the services on the first group of E1/T1 ports (4 to 7) and the lower processes those on the second group of E1/T1 ports (0 to 3). N+1 backup mode: used when the IO board is UGBI. It indicates that only the active UEPI/UTPI provides two groups of E1/T1 ports. The only UFEU on the UGBI processes the services on the two groups of ports. Clock stratum: The stratum of the H110 clock for UEPI/UTPI includes PM, SM and SL. The board whose clock stratum is PM extracts clock from the optical port of the URCU in slot 6. The board whose clock stratum is SM extracts clock from the optical port of the URCU in slot 8. The extracted clock serves as the signal source for the clock bus of the subrack. The board whose clock stratum is SL extracts clock only from the CT bus. Only one of the UEPIs/UTPIs in a subrack supports PM, another supports SM and the others support SL. The UEPI/UTPI configured with PM, SM or SL is not specified. However, you shall configure the three stratums in the sequence of PM, SM and SL. Balance mode: When the impedance of an UEPI transmission line is 75 ohm (coaxial cable), UEPI will work in unbalanced mode. When the impedance of an UEPI transmission line is 120 ohm (twisted pair), the UEPI will work in balanced mode. UTPI only works in balanced mode (100 ohm).
ULAN
Board position: ULAN is a back-plug board .You can add ULANs in slots 0 to 5 and 10 to 15. Backup information: none IP address: The IP address of the ULAN must be in the same network segment with that of the internal maintenance network port of the UOMU. UOMU uses this IP address to load software to the ULAN.
68P02904W52-B 31-Jan-2005
2-17
Configuring Port
Configuring Port

This section introduces the configuration for port properties. The ports that need configuration in the system include E1/T1, FE/GE, VA and ATM. A port can work normally only after proper configuration for its properties.
Description
Preset conditions
The board providing the port already exists.
Data preparations
Item E1/T1 Subrack number. Slot number. Data Port number. Frame Type. Support extraction of 2M clock from SS7. Port rate. Code Type.
FE/GE
Slot number. IP Address.
Subslot number. Working mode. First port number. Subslot number.
Port number.
Negotiation mode.
MTU
ATM VA
First slot number. Slot number.
Second slot number. Virtual port number.
Second port number. Interface IP address.
Backup type.
Procedure
1. Add E1/T1. Step 1 Operation Add E1/T1. Command ADD E1T1CFG
2-18
68P02904W52-B 31-Jan-2005
Configuring Port
2. Add FE/GE. Step 1 2 3. Add VA. Step 1 4. Add ATM. Step 1 Operation Add POS port property. Command ADD BNET_PORT_BACKUP Operation Add VA interface property. Command ADD BNET_UHPU_IF_IP Operation Add FE/GE interface property. Add FE/GE interface IP address. Command MOD BNET_IP_PROPERTY ADD BNET_GFI_IF_IP
Example
;;Add E1/T1 ADD E1T1CFG: SRN=0, SN=4, PORT=2, LKFRMT=DF, LKCT=HDB3; ADD E1T1CFG: SRN=0, SN=4, PORT=1, LKFRMT=DF, LKCT=HDB3; ADD E1T1CFG: SRN=0, SN=4, PORT=3, LKFRMT=DF, LKCT=HDB3; ADD E1T1CFG: SRN=0, SN=4, PORT=0, LKFRMT=DF, LKCT=HDB3; ;;Add FE/GE ADD BNET_GFI_IF_IP: SN=3, PN=0, IP="191.22.12.123", MSK="255.255.0.0"; ;;Add VA ADD BNET_UHPU_IF_IP: SN=10, SUBSN=0, VPN=12, IP="191.22.6.120", MSK="255.255.255.0";
Reference
1). The IP address for each virtual port cannot be in the same network segment. 2). The system automatically generates the IP address for virtual port 0 of either UHPU forward engine. Therefore, this IP address does not need manual setting. You may use SET BNET_INTERNAL_IP to modify the network segment of it if necessary. 68P02904W52-B 31-Jan-2005 2-19
Configuring Port
E1/T1
E1/T1 links in the SGSN serve as physical links for SS7 interfaces and Gb interface. E1 links support two frame formats (DF and CRC) and one code type (HDB3). T1 links support two frame formats (SF and ESF) and three code types (B8ZS, AMI and AMI_ZCS). Settings for the frame format and code type must be consistent with those at the peer, so that E1/T1 links can work normally. When an E1/T1 link serves as the physical link for SS7 interface, the system can extract 2 MHz clock the E1/T1 link as its own clock.
FE/GE
The FE/GE port serves as the physical port of the Gn/Gp and Ga interfaces. You need to configure only an IP address for it. For the other parameters of this port, you can adopt the default values. The IP address for the FE/GE port must be in the same network segment as that for the port of the connected external router.
VA
The Virtual ATM (VA) ports, virtual ports in SGSN, are provided by UHPU and UMPU. There are two forward engines (similar to routers functionally) in the UHPU. Each engine provides 32 VA ports (0 to 31). UMPU contains only one forward engine that provides 32 VA ports (0 to 31). You may set an IP address for each VA port to establish IPoA links between the UHPU or UMPU and the other boards.
ATM
ULPU and UFIU provide ATM ports. You need to configure only the backup property of the ULPU ATM port connected with the RNC. The system automatically sets the properties of the ULPU ATM port connected with the UFIU. The backup type of ATM ports include: Redundancy backup. In normal cases, the two ATM ports receive and transmit data. If one port is faulty, the other will process the data on both ports. 1+1 backup. In normal cases, the active ATM port receives and transmits data while the standby only transmits data. If the active port is faulty, the services on it will be shifted to the standby one. You can set the ATM port connected with the RNC to work only in 1+1 backup mode. In addition, the RNC must support port backup.
2-20
68P02904W52-B 31-Jan-2005
Configuring Clock
Configuring Clock

This section introduces the configuration for the Motorola C-SGSN system clock. The system can extract clock from the specified clock source after this configuration.
Description
Preset conditions
The board configuration has finished. The system works normally. The external clock source works properly and is well connected with the system. The E1/T1 configuration has finished if the system supports the extraction of 2 MHz clock from E1/T1.
Data preparations
Item Clock source. Clock source grade. Data Clock source type. ULPU Slot number (mandatory when the clock source is SDH). ULPU Port number (mandatory when the clock source is SDH).
Procedure
Step 1 2 Operation Add BNET clock reference source. Set the current clock source. Command ADD BNET_CLOCK_SOURCE SET BNET_CURRENT_CLOCK
Example
;;Add BNET clock reference source. ADD BNET_CLOCK_SOURCE: GD=3, TP=BITS1_2MBPS; ADD BNET_CLOCK_SOURCE: GD=4, TP=SDH, SN=2, PN=1; ;;Set the current clock source. SET BNET_CURRENT_CLOCK: MD=MANUL_MODE, GD=3;
68P02904W52-B 31-Jan-2005
2-21
Configuring Clock
Reference
The clock module in the UNET provides clock for the SGSN system. It extracts clock from the clock sources, processes and provides the ULPU with clock signals. The ULPU transfers the clock signals through its optical port to the URCU. The URCU forwards the clock signals to the UEPI/UTPI at last. The clock module has the following clock sources: SDH clock from ULPU. Building Integrated Timing System (BITS) clock, including BITS1 and BITS2. BITS1 is provided by BITS network and BITS2 is the standby clock source of BITS1. The BITS clock has two input sources: 2 MHz input source and 2 Mbit/s input source. 2M clock extracted from SS7. Clock generated from the local oscillator on the clock board. You may configure the clock sources existing in the system according to the actual situations. You may add up to four external clock sources. Then you need to specify a stratum for each source. The stratum depends on the clock stability and reliability. Stratum 4 stands for the highest stratum and stratum 0 for the lowest. Stratum 0 stands for the clock generated from the local oscillator on the clock board.
2-22
68P02904W52-B 31-Jan-2005
Chapter
SS7 Configuration

68P02904W52-B 31-Jan-2005
3-1
SS7 Configuration Overview
SS7 Configuration Overview

This chapter introduces the SS7 configuration, including the local office configuration, MTP layer configuration, SCCP layer configuration, MAP layer configuration (Gr/Gd/Ge/Gf/Lg interface) and BSSAP+ layer configuration (Gs interface). The SS7 configuration follows the sequence below: 1. 2. 3. 4. 5. Local office configuration. MTP layer configuration. SCCP layer configuration. MAP layer configuration (Gr/Gd/Ge/Gf/Lg interface). BSSAP+ layer configuration (Gs interface).
3-2
68P02904W52-B 31-Jan-2005
Configuring Local Office

This section introduces the local office configuration. Only after the local office configuration is implemented the other configurations of SS7 can be implemented.
Description
Preset conditions
None
Data preparations
Item Signaling Network Type. Country codes. Signaling point code. Support BSSAP+ flag. SGSN number. Subsystem Number of BSSAP+ Data STP flag. Mobile country code. Mobile network code.
Basic Information.
Procedure
Step 1 Operation Set the information of the signaling point whose index number is 0. Set the information of the signaling point whose index number is not 0. SET OFI Command
ADD OFI
Example
;; Set the information of the signaling point whose index number is 0. SET OFI: IF=INVALID, IRF=INVALID, NF=VALID, NRF=VALID, NOPC="111111", NROPC="1111", NSTRU=LABEL24, NRSTRU=LABEL14, STPF= DISABLE, RSTF=DISABLE, SGSNN="86139000101", MCC="460", MNC="00", CC="86", MAPNI=NAT, BSSAPPF=ENABLE, BSSAPPNI=NAT;
68P02904W52-B 31-Jan-2005
3-3
;;Set the information of the signaling point whose index number is not 0. ADD OFI: OPX=1, NOPC="12346", SGSNN="861390215555";
Reference
Motorola C-SGSN can provide multiple signaling points, that is, in the same signaling network, one Motorola C-SGSN can define 16 OPC instead of one and there are multiple OPCs corresponding to one DPC. Therefore, there can be more than 16 signaling links between two network nodes. The command SET OFI can be used to add and modify the information of OPC with index 0. The commands ADD OFI and RMV OFI are used to add and remove the information of the OPC with index other than 0.
3-4
68P02904W52-B 31-Jan-2005
Configuring MTP Data

The MTP layer data configuration includes the settings of MTP signaling link, route and signaling point. After the settings, the communication with each network node on the MTP layer can be implemented normally.
Description
Preset conditions
Before the configuration, the relevant hardware equipment should be working normally. The physical links with the destination signaling points should be normal. Make sure you have configured the local office information.
68P02904W52-B 31-Jan-2005
3-5
Data preparations
If there is a direct route between the DPC and the local office, then you should prepare the following data: Item DPC MTP DP MTP link. Subrack number. Signaling link type. MTP link set. MTP route. Signaling link selection mask. Priority. Cont. Network indicator. Slot number. Data Corresponding OPC. Link number. STP flag. Adjacent flag. SLC Link set selection mask. Priority.
Link rate type.
3-6
68P02904W52-B 31-Jan-2005
If the STP transfers the signals between the DPC and the local office, then you should prepare the following data: Item MTP DPC DPC Network indicator. Data Corresponding OPC. Link set selection mask.
MTP route.
Priority.
Procedure
If there is a direct path between the DPC and the local office: Step 1 2 3 4 Operation Add MTP destination signaling point. Add MTP signaling link set. Add MTP signaling route. Add MTP signaling link. Command ADD N7DPC ADD N7LKS ADD N7RT ADD N7LNK
If the STP transfers signals between the DPC and the local office: Step 1 3 Operation Add MTP destination signaling point. Add MTP signaling route. Command ADD N7DPC ADD N7RT
Example
If there is one direct route and two indirect routes to HLR, and there are four links in each link set, then the configuration is as follow: ;; Add MTP destination signaling point ADD N7DPC: DPX=0, OPC="1106a", NI=NAT, DPC="12345", DPN="HLR"; ADD N7DPC: DPX=1, OPC="1106a", NI=NAT, DPC="1106FF", STPF= TRUE, ADJF= TRUE,SLSSM=B0100, DPN="STP1"; ADD N7DPC: DPX=2, OPC="1106a", NI=NAT, DPC="1106EF", STPF= TRUE, ADJF= TRUE,SLSSM=B0100, DPN="STP2"; ;; Add MTP signaling link set ADD N7LKS: LSX=0, DPX=0, SLSM =B0011, LSN="hlr";
68P02904W52-B 31-Jan-2005
3-7
ADD N7LKS: LSX=1, DPX=1, SLSM= B0011, LSN="STP1"; ADD N7LKS: LSX=2, DPX=2, SLSM= B0011, LSN="STP2"; ;; Add MTP signaling route ADD N7RT: LSX=0, PRI=0, DPX=0, RTN="hlr"; ADD N7RT: LSX=1, PRI=1, DPX=0, RTN="STP1"; ADD N7RT: LSX=2, PRI=2, DPX=0, RTN="STP2"; ;; Add MTP signaling link ADD N7LNK: SRN=0, SN=2, LNK=0, TS=16, LSX=0, SLC=0, SLCS=0, LKN="HLR_LINK1"; ADD N7LNK: SRN=0, SN=2, LNK=1, TS=48, LSX=0, SLC=1, SLCS=1, LKN="HLR_LINK2"; ADD N7LNK: SRN=0, SN=2, LNK=2, TS=80, LSX=0, SLC=2, SLCS=2, LKN="HLR_LINK3"; ADD N7LNK: SRN=0, SN=2, LNK=3, TS=112, LSX=0, SLC=3, SLCS=3, LKN="HLR_LINK4"; ADD N7LNK: SRN=1, SN=2, LNK=0, TS=16, LSX=1, SLC=0, SLCS=0, LKN="STP1_LINK1"; ADD N7LNK: SRN=1, SN=2, LNK=1, TS=48, LSX=1, SLC=1, SLCS=1, LKN=" STP1_LINK2"; ADD N7LNK: SRN=1, SN=2, LNK=2, TS=80, LSX=1, SLC=2, SLCS=2, LKN=" STP1 _LINK3"; ADD N7LNK: SRN=1, SN=2, LNK=3, TS=112, LSX=1, SLC=3, SLCS=3, LKN=" STP1_LINK4"; ADD N7LNK: SRN=1, SN=2, LNK=0, TS=16, LSX=2, SLC=0, SLCS=0, LKN="STP2_LINK1"; ADD N7LNK: SRN=1, SN=2, LNK=1, TS=48, LSX=2, SLC=1, SLCS=1, LKN=" STP2_LINK2"; ADD N7LNK: SRN=1, SN=2, LNK=2, TS=80, LSX=2, SLC=2, SLCS=2, LKN=" STP2_LINK3"; ADD N7LNK: SRN=1, SN=2, LNK=3, TS=112, LSX=2, SLC=3, SLCS=3, LKN=" STP2_LINK4";
Reference
MTP Destination Signaling Point
From the view of the local office, you can divide the signaling points into original signaling points (the signaling points where the local office is) and the destination signaling points (the signaling points to which the local office signaling messages are transmitted). 3-8 68P02904W52-B 31-Jan-2005
For an OSP, you can categorize its Destination Signaling Point (DSP) into adjacent destination signaling points and non-adjacent destination signaling points. A destination signaling point with a direct signaling link to the OSP is an adjacent signaling point of the OSP; while the one without a direct signaling link to the OSP but with MTP signaling relationship is a non-adjacent signaling point of the OSP. The DSPs to be set at the OSP depend on the network architecture and the operator network planning. However, the DSP that has direct signaling link with the OSP is mandatory, such as the DPC1 and STP in Figure 3-1. DPC2 in Figure 3-1 does not have direct signaling link with the OSP; therefore, whether to configure DPC2 depends on the addressing mode specified by the operator. It should be configured if the DPC addressing has been adopted, but not if the GT addressing has been adopted. Figure 3-1 DSP configuration.
DPC2
STP
DPC1
Signaling link OPC No signaling link, but signaling relationship
MTP link set

The MTP link set is a group of parallel signaling links between two adjacent signaling points.
MTP signaling route

The MTP route is the path for the transmission of signaling messages between two signaling points. Signaling route specifies the correspondence between destination signaling points and link sets. In other words, signaling routes determine which link sets are used to transmit the signaling to the DSP. One signaling route only corresponds to one link set; while one link set can correspond to multiple signaling routes. The signaling route to a destination signaling point can be categorized into two types: direct routes and the indirect routes. Direct route refers to the signaling route between the OSP and the destination signaling point without the signaling transfer point. While indirect route refers to the signaling route in which the signaling is transmitted to the destination signaling point using the signaling transfer point. The link set corresponding to the direct route is the link set between the originating signaling point and the destination signaling point. The link set corresponding to the indirect route is the link set between the originating signaling point and the signaling transfer point. If there is a direct route and an indirect route to a destination signaling point, specify the priorities of the signaling routes, then select the route with higher priority. Usually the direct routes are specified with higher priority. Up to 16 routes can have the same priority and they can share the load. When there are multiple routes, the signaling will prefer the route with higher priority.
68P02904W52-B 31-Jan-2005
3-9
MTP signaling link

The signaling link is a physical link that connects signaling points and transmits signaling messages. A signaling link is composed of signaling data link and signaling terminal. Signaling data link is a kind of physical medium for signaling transmission. Any timeslot in the PCM system can be specified as a signaling data link, except timeslot 0. In the PCM primary group, TS16 is generally specified as the signaling data link. Signaling terminal is responsible for the MTP layer 2 processing of the data in a specified signaling data link. Physically, in Motorola C-SGSN, one signaling link is one or more time slots in the E1/T1 link. A signaling data link is specified by a timeslot number while a signaling terminal is specified by a link number One USPU can be assembled with two UMTP or two USS7 boards. Each UMTP can process four 64 kbit/s signaling links. Each USS7 can process thirty two 64 kbit/s signaling links or one 2 Mbit/s signaling link.
You cannot configure the UMTP and the USS7 on the same USPU board. The 64 k link and the 2 Mbit/s link cannot be in the same link set. The 2 Mbit/s signaling link can corresponds to 1 to 31 continuous timeslots. However, all the timeslots should be within the same E1/T1 port. The number of timeslots seized by 64k link is fixedly 1. The number of timeslots for 2M link should be consistent with the corresponding setting on the peer end.
Table 3-1 lists the relations and value ranges of the link No, timeslot number and the UEPI/UTPI port when different subboards are configured on the USPU and UEPI/UTPI adopts different backup types.
3-10
68P02904W52-B 31-Jan-2005
Table 3-1
Relations between link No, timeslot number and UEPI/UTPI port. Subboard position Lower subboard. Link number Timeslot number 0 to 127 UEPI/UTPI backup type Load sharing. 1+1 4 to 7 128 to 255 Load sharing. 1+1 Lower Subboard 0 to 31 0 to 127 Load sharing. 1+1 32 to 63 128 to 255 Load sharing. 1+1 0 0 to 127 Load sharing. 1+1 32 128 to 255 Load sharing. 1+1 UEPI/UTPI port Active E1_0 or E1_1. Active E1_0. Standby E1_0 or E1_1. Active E1_1. ActiveE1_0 or E1_1. Active E1_0. Standby E1_0 or E1_1. Active E1_1. Active E1_0 or E1_1. Active E1_0. Standby E1_0 or E1_1. Active E1_1.
Subboard type
0 to 3
UMTP Upper subboard
USS7_64 Upper subboard. Lower subboard. USS7_2M Upper subboard.
The 'USS7_64' indicates that USS7 is used to process 64 kbit/s signaling link, and 'USS7_2M' indicates that the USS7 is used to process 2 Mbit/s signaling link. The active E1_0 indicates the 0 to 3 E1/T1 of the active UEPI/UTPI. The active E1_1 indicates the 4 to 7 E1/T1 of the active UEPI/UTPI. The standby E1_0 indicates the 0 to 3 E1/T1 of the standby UEPI/UTPI. The standby E1_1 indicates the 4 to 7 E1/T1 of the standby UEPI/UTPI. The link Numbers and E1/T1 port Numbers in the same UMTP/USS7 have no correspondence but range restriction. All the timeslots 0 of E1 ports are used for synchronization and cannot be used as the timeslots of the signaling links. In this case, the timeslot number should not be the multiplier of 32. There is no such restriction for T1 port. T1 port only provides 24 timeslots. The start timeslot number of each port is the multiplier of 32, for example, 0 to 23, 32 to 55.
Load sharing of SS7 signaling network

There are two types of load sharing.
68P02904W52-B 31-Jan-2005
3-11
1.
Load sharing of links in one link set. The former load sharing refers to load sharing among links in one link set based on the Signaling Link Selection (SLS) code, as illustrated in Figure 3-2. In the figure, there are two signaling links between signaling points A and B. The signaling messages are allocated to these two links according to the last bit of the SLS in the signaling message (0 or 1). Figure 3-2 Load sharing of links in one link set.
SLS=XXX0
SLS=XXX1
2.
Load sharing of links in different link sets. Figure 3-3 illustrates the signaling service sharing among links in different link sets. Figure 3-3 Load sharing of links in different link sets.
XXX0
A D E B
XXX1
F C
XXXX
Even when the signaling messages to different DSPs use the same signaling link set, they may not use the same load sharing type. Take Figure 3-3 for example, services to B are shared between link sets DE and DF based on SLS while services to C are only undertaken by the link set DF because of EC fault. To realize the above two signaling sharing modes, Motorola C-SGSN utilizes signaling link set selection mask and SLS mask to averagely distribute signaling messages according to SLS. There are two sources for the SLS code. In the TUP/ISUP message, it is the lower 4 bits of the CIC; while in the SCCP message, it is allocated by SCCP cyclically. As SLS changes in a cyclic manner, the load sharing based on SLS can ensure that the load among various links or link sets is well-proportioned.
3-12
68P02904W52-B 31-Jan-2005
Mask setting principles

The signaling link set masks and the signaling link masks determine the allocation of SLS in the link set and between the links. Figure 3-4 shows the algorithm used by SGSN to select a signaling link set or signaling link through the corresponding mask. Figure 3-4
SLS Mask 1 1 1 0
Example of signaling link set/signaling link algorithm selection.

1 1 1 0 0 is skipped This bit taken as the lowest bit (bit) This bit taken as the second lowest bit (bit)
1 Form 0011 = 0x3 Calculate the remainder Number of available signaling routes with the same priority Fourth signaling route
0011 % 4 3
Conclusion: The fourth signaling route is selected for the signalling service with SLS to be 1111.
The SLSs generated on the MTP upper layer are allocated cyclically. If you use the masks to control the allocation of SLSs in the MTP signaling link sets and between the MTP signaling links, then you can ensure that the load sharing between each link set/signaling link will be reasonable. The following are the principles for setting the mask: 1. Set the number of '1's in the mask according to number of signaling link sets or the number of signaling links. See Table 3-2.
68P02904W52-B 31-Jan-2005
3-13
Table 3-2 the mask.
Relationship between the number of link sets/links and the number of 1s in The number of link sets/links 2 3 to 4 5 to 8 9 to 16 The number of 1s in the mask 1 2 3 4
2.
The roles of SLS in the allocation of signaling links and signaling link sets are the same. Therefore, to ensure that all links in a signaling link set can be selected, the bit '1' in the signaling link mask and that in the signaling link set mask cannot be the same. For example, when the signaling link set mask is '0011' and the number of signaling links in it are 4, the signaling link mask should be '1100'. If the number of signaling links are 2, the signaling link mask should be '1000' or '0100'. Take an example to illustrate the setting of signaling link set mask and signaling link mask. Suppose that there are four signaling link sets (0, 1, 2 and 3) to a certain destination signaling point and that each link set contains two links. According to the above principles, the signaling link set mask can be set as '1010' and the signaling link mask can be set as '0100'. The signaling link set/SLS algorithm is shown in Table 3-3.
Table 3-3
SLS allocation. SLS 0, 1, 4, 5 2, 3, 6, 7 8, 9, 12, 13 10, 11, 14, 15 0 1 0 1 0 1 0 1 Link number 0, 1 4, 5 2, 3 6, 7 8, 9 12, 13 10, 11 14, 15 SLS
Link set number 0 1 2 3
The load sharing described above is realized among link sets with the same priority. Only when all the links with higher priorities are unavailable, the signaling service will be shared by the link sets with lower priorities.
3-14
68P02904W52-B 31-Jan-2005
SCCP Configuration
SCCP Configuration

The SCCP data configuration includes the SCCP destination signaling code configuration, SCCP subsystem configuration, new GT configuration and the GT translation. Usually the new GT configuration is not necessary. After the SCCP data configuration, SGSN can communicate with the signaling points with the SCCP function on the SCCP layer.
Description
Preset conditions
You should first implement the configuration of the MTP layer data. The local office provides the SCCP function.
Data preparations
If there is a direct route between the DPC and the local office, or the STP transfers signals between the DPC and the local office, and the addressing mode is DPC+SSN, then you should prepare the following data: Item DPC GT DPC Network indicator. Data Load sharing DPC. IMSI number segment (add HLR). New GT.
HLR/SMC/EIR/ IMSI-GT corresponding SCP/GMLC relation (add Number. HLR).
If the STP transfers signals between the DPC and the local office, and the addressing mode is DPC+GT/NGT, then you should prepare the following data: Item GT HLR/SMC/EIR/ IMSI number segment (add SCP/GMLC HLR). Number. Data IMSI-GT corresponding relation (add HLR). New GT.
68P02904W52-B 31-Jan-2005
3-15
SCCP Configuration
Procedure
If there is a direct route between the DPC and the local office, or the STP transfers signals between the DPC and the local office, and the addressing mode is DPC+SSN: Step 1 2 3 (optional). 4 (optional). 5 Operation Configure SCCP destination signaling point. Configure SCCP subsystem. Configure IMSI-GT translation table. Configure new GT table. Configure GT translation table. Command ADD SCCPDPC ADD SCCPSSN ADD IMSIGT ADD SCCPNGT ADD SCCPGT
When adding HLR, you need to execute Step 3. Usually, SGSN does not need the configuration of new GT table. Therefore, the above Step 4 can be omitted.
If the STP transfers signals between the DPC and the local office, and the addressing mode is DPC+GT/NGT: Step 1 (Optional). 2 (Optional). 3 Operation Configure IMSI-GT translation table. Configure new GT table. Configure GT translation table. Command ADD IMSIGT ADD SCCPNGT ADD SCCPGT
When adding HLR, you need to execute Step 1. Usually, SGSN does not need the configuration of new GT table. Therefore, the above Step 2 can be omitted.
Example
Configure the SCCP layer data of the HLR, among which the users with the IMSI number segments of 460001001, 460001002 and 460001003 belong to this HLR:
3-16
68P02904W52-B 31-Jan-2005
SCCP Configuration
;;Configure SCCP destination signaling points. ADD SCCPDPC: DPX=0, DPC="12345 ", OPC="1106a", NI=NAT; ;;Configure local office SCCP subsystem. ADD SCCPSSN: SSNX=0, SSN=SCMG, NI=NAT, DPC="1106a", OPC="1106a"; ADD SCCPSSN: SSNX=1, SSN=SGSN, NI=NAT, DPC="1106a",OPC="1106a"; ;;Configure HLR SCCP subsystem. ADD SCCPSSN: SSNX=2, SSN=SCMG, NI=NAT,DPC="12345", OPC="1106a"; ADD SCCPSSN: SSNX=3, SSN=HLR, NI=NAT, DPC="12345", OPC="1106a"; ;;Configure IMSI-GT translation relation. ADD IMSIGT: IMSI="46000", GT="86139"; ;;Configure GT ADD SCCPGT: GTX=0, NI=NAT, RT=DPCSSN, ADDR="861391001", DPC="12345", SSN=HLR; ADD SCCPGT: GTX=1, NI=NAT, RT=DPCSSN, ADDR="861391002", DPC="12345", SSN=HLR; ADD SCCPGT: GTX=2, NI=NAT, RT=DPCSSN, ADDR="861391003", DPC="12345", SSN=HLR;
Reference
SCCP DSP
The configuration of SCCP destination signaling point is to create a destination signaling point associated with the local office signaling point SSCP signaling on the SCCP layer.
All SCCP DSPs to be added to SCCP DSP Table must be described in MTP DSP Table, but not to be described in SCCP DSP Table. Generally, the following SCCP DSPs need to be defined:
68P02904W52-B 31-Jan-2005
3-17
SCCP Configuration
The SCCP DSPs that have direct signaling routes to the OSP, The SCCP STPs (the signaling points supports SCCP transfer function), The SCCP DSPs based on DPC+SSN addressing mode. SCCP DSP.
Figure 3-5
C A
B
In Figure 3-5, A is the OSP; B and D are signaling points having SCCP signaling relationship with the OSP; and C is the SCCP signaling transfer point. If the addressing mode from A to D is DPC+SSN, the SCCP destination signaling points to be configured for A are B and D. If the addressing mode from A to D is DPC+GT, the SCCP destination signaling points to be configured for A are B and C. In this case, C has to translate the GT in the message from A. Destination signaling point can work in three modes: independent, active/standby, and load sharing. Independent mode means that the DSP has no standby signaling point. Active/standby mode means that the DSP has a standby signaling point so that SCCP messages are sent to this DSP if it is available, otherwise, the messages are sent to the standby signaling point. Load-sharing mode means that the DSP has a standby signaling point so that SCCP messages are sent to these two signaling points by turn. If only one of them is available, the messages are sent to the available one. Usually, the two STPs are configured to work in load sharing mode. There can be multiple virtual originating signaling points at the OSP for one DSP. SCCP processes messages transmitted to the DSP in a cyclic mode. It selects one virtual signaling point at the OSP as the OPC in the MTP message for the corresponding DSP.
SCCP Subsystem
The SubSystem Number (SSN) is the local addressing information used by SCCP. It is used to identify multiple SCCP subscribers in a network node. If the network node functions more than an STP, a subsystem number has to be specified for each SCCP subsystem (SCCP subscriber). Each subsystem number is unique in the whole network.
3-18
68P02904W52-B 31-Jan-2005
SCCP Configuration
The number of subsystems related to SGSN is shown in Table 3-4. Table 3-4 Number of subsystems related to SGSN. Subsystem SCCP Management subsystem. HLR VLR MTS-U EIR INAP GMLC CAP SGSN GGSN BSSAP+ 0x01 0x06 0x07 0x08 0x09 0x0C 0x91 0x92 0x95 0x96 0xFC (configurable). Subsystem number
The SCCP management subsystems corresponding to SCCP remote signaling points defined at the OSP must be defined in the OSP data tables. Other subsystems to be defined depend on the network entity. For example, the HLR subsystem has to be defined for HLR and the MTS-U subsystem has to be defined for MTS-U. The subsystems to be defined at the OSP include SCMG, SGSN and BSSAP+.
GT Translation
In SS7 signaling system, all messages are transmitted through MTP. MTP address is composed of SPC and network identification. In PLMN, the destination address in mobile-concerned message is identified by other information (for example HLR number, MSISDN). SCCP needs to translate the GT information of the called subscriber into DPC or DPC+SSN for the MTP to transmit the message. The process of translation is called GT translation. The configuration content of GT translation includes translation result type, GT indicator, translation type, numbering plan and address information (for example, SGSN number, MTS-U/VLR number, HLR number, IMSI and SCP number). Before the configuration of GT translation, specify the type of translation according to the addressing mode. The addressing mode depends on the following situations: 1. There is a direct physical link between the two signaling points. Under this case, the GT is translated into DPC + SSN, and the addressing mode is illustrated in Figure 3-6.
68P02904W52-B 31-Jan-2005
3-19
SCCP Configuration
Figure 3-6
A Subsystem
DPC+SSN addressing mode.

B Subsystem
SCCP
SCCP
MTP DPC+SSN
M TP
2.
There is no direct physical link between the two signaling points (A and C). The MTP signaling message is transferred through an STP (B). In this case, the GT is translated into DPC+SSN. The signaling message from A uses DPC+SSN addressing mode. The DPC is the signaling point code of C. The SSN is the subsystem number of C. When the MTP of B receives the MTP message from A and finds out that the message is not transmitted for B, it will forward the message according to the DPC. The message sent to C also adopts the DPC+SSN mode. The DPC and SSN remain the same. This kind of networking requires that B should have the STP function. See Figure 3-7. Figure 3-7 DPC+SSN addressing through the transfer of STP B.
A Subsystem
B Subsystem
C Subsystem
SCCP
SCCP
SCCP
MTP DPC+SSN
3.
MTP DPC+SSN
MTP
There is no direct physical link between the two signaling points (A and C). The SCCP signaling message is transferred through an STP (B). Under this situation, the GT is translated into DPC+ GT. The signaling message from A uses DPC+GT addressing mode, where DPC is the signaling point code of B and GT is the GT code of C. The MTP of B receives the message from the MTP of A, and then sends the message to its SCCP. SCCP then performs GT translation and the translation result is DPC+SSN, where DPC is the signaling point code of C and SSN is the subsystem number of C. The translation result is then sent to MTP layer and MTP layer sends the result to C according to the DPC specified. The networking under this situation requires B to have STP function. Refer to Figure 3-8.
3-20
68P02904W52-B 31-Jan-2005
SCCP Configuration
Figure 3-8
DPC+GT addressing mode.
A Subsystem
B Subsystem
C Subsystem
SCCP
SCCP
SCCP
MTP DPC+GT
MTP DPC+SSN
MTP
To meet the requirements of different network, the SCCP layer can translate certain GT into new GT before forwarding it. In this case, you should configure a new GT table. The addressing mode is DPC+NGT.
68P02904W52-B 31-Jan-2005
3-21
SCCP Configuration
Common GTs for SGSN

In SGSN, you should configure the following GTs: GT IMSI number segments of all the local subscribers in HPLMN. IMSI number segments of all the foreign subscribers in the HPLMN. IMSI number segments of all subscribers in the PLMN that allows roaming. Number of the local SGSN. HLR number. Address mode DPC+SSN (in general). Description Addressing the local HLR. DPC is the DPC of the local HLR. SSN is the SSN of the HLR. Addressing the foreign HLR. DPC is the DPC of STP. Addressing the foreign network HLR. DPC is the DPC of STP. Addressing the local SSN. DPC is the DPC of the local SGSN. You shall configure HLR number only when the IMSI adopts the DPC + SSN addressing mode to address this HLR. DPC is the DPC of HLR. Addressing SMC. DPC is the DPC of STP. Addressing SCP. DPC is the DPC of STP. Addressing GMLC. DPC is the DPC of STP. Addressing EIR. DPC is the DPC of STP. Addressing MTS-U/VLR. DPC is the DPC of MTS-U/VLR.
DPC+GT (in general).
DPC+GT (in general).
Set as DPC. DPC+SSN (in general).
SMC number. SCP GMLC EIR MTS-U/VLR number.
DPC+GT (in general). DPC+GT (in general). DPC+GT (in general). DPC+GT (in general). DPC+SSN (in general).
When the SCP and GMLC are the same physical entity, The Ge and Lg interfaces simultaneously exist between the SGSN and the DPC. In this case, the GT translation mode of SCP should be set as DPC or DPC+GT/NGT mode, instead of DPC+SSN mode. When the SCP and GMLC are not the same physical entity, the GT translation mode of the SCP can be set as DPC+SSN mode.
3-22
68P02904W52-B 31-Jan-2005
SCCP Configuration
IMSI-GT conversion
When the mobile subscriber initiates location update to or obtains an authentication set from HLR, there is no HLR number or MSISDN of the subscriber in SGSN. The only HLR addressing information is the IMSI of the subscriber. IMSI will be first converted to GT code. Then the GT code will be used for HLR addressing. Figure 3-9 shows the conversion from IMSI to GT. Figure 3-9 IMSI-GT conversion.
IMSI
MCC Conversion
MNC Conversion NC
MSIN
GT
CC
MSIN
MCC: Mobile country code. MNC: Mobile network code MSIN: Mobile subscriber identification No. CC: Country code NC: Network code
The IMSI GT Conversion is to convert the MCC+MNC of IMSI to CC+NC of GT. MSIN can be obtained directly by mapping. CC+NC is used to identify the PLMN or an HLR in the PLMN of a country. NC can be either the National Destination Code (NDC) or NDC followed by several numbers. It is used to identify a PLMN or an HLR in the PLMN. Moreover, MSIN is used to identify a mobile subscriber in HLR.
68P02904W52-B 31-Jan-2005
3-23
Configuring MAP (Gr/Gd/Ge/Gf/Lg interface)

This section introduces the configuration of the MAP layer function of the Gr interface. After the configuration, SGSN can perform the MAP layer signaling exchange with the HLR.
Description
Preset Conditions
The configuration of local office information, MTP information and SCCP information have been completed.
Data Preparation
If SGSN provides the zone restriction function, then you should prepare the following data: Item Area code. ZC LAI RAI Data
Procedure
Step 1 2 (Optional). Description Configure the MAP function. Configure the zone code. Command SET MAPFUNC ADD MAPZC
Example
;;Configure the MAP function. SET MAPFUNC: ZC=YES; ;; Configure the zone code ADD MAPZC: ZC="1234", LAI="460001111", ZCN="test", RAC=1;
3-24
68P02904W52-B 31-Jan-2005
Reference
MAP
Mobile Application Part (MAP) protocol defines how the information is exchanged for MS roaming between the network entities in the mobile system. Functions of MAP interfaces in PS domain are described below. Signaling interworking between SGSN and HLR/SMS-MTS-U/GMLC is implemented through MAP protocols. Among these protocols, TCAP, SCCP and MTP protocols are the same as those bearing MAP signaling in CS network. The design of SGSN takes the compatibility between 2.5G GPRS MAP version and the UMTS MAP version into consideration to ensure that the SGSN can interwork with the MAP of lower version. MAP message processing modules strictly comply with 3GPP TS 29.002 and provide all basic functions specified in 3GPP TS 29.002, including: Version negotiation. Mobility management for both 2G and 3G MSs. Management of subscription data management, including GPRS subscription data, LCS subscription data and CAMEL subscription data. Security management, including authentication for both 2G and 3G MSs and authentication failure report function. Error recovery. The HLR notifies the SGSN for processing after resetting. Short message function, including Mobile Originated Short Message Service (MO-SMS), Mobile Terminated Short Message Service (MT-SMS) and short message alert. Gc interface message forwarding function, including routing information fetch and failure report, and MS presence notification. MS location function, including location report and provision of location information. Users can configure the above functions.
Configure MAP zone code table

The MAP zone code is one of the measures the operator uses to control the subscriber roaming. The operator divides the service coverage into multiple zones, with each being identified with a zone code. If the subscriber has subscribed to a specific or several service zones, the subscriber can roam within the subscribed zones. In SGSN, you should configure the corresponding zone code subscription that allows roaming. When there is an intersection between the zone code subscribed by the subscriber and the zone code configured in SGSN, it means that this subscriber can access this zone. Otherwise, this subscriber access will be rejected.
68P02904W52-B 31-Jan-2005
3-25
Configuring BSSAP+ (Gs interface)

This section introduces the configuration of BSSAP+ layer. After the configuration, SGSN can normally implement the function of the Gs interface.
Description
Preset conditions
The configuration of the local office information, MTP information and SCCP information has been completed.
Data preparations
Item Basic information. VLR LAI Data
Procedure
Step 1 2 3 Operation Configure BSSAP+ timer. Configure VLR table. Set RAI-VLR corresponding relation. ADD VLR ADD LAIVLR Command SET BSSAPPTMR
Example
;;Set the VLR table ADD VLR: VN="8613800220", VNM="vlr1"; ;;Add the RAI-VLR corresponding relation ADD VLR: LAI="460002701", RAC="0901",VN="8613800220", VNM="vlr1"; ADD VLR: LAI="460002701", RAC="0902",VN="8613800220", VNM="vlr1"; 3-26 68P02904W52-B 31-Jan-2005
Reference
Upon the initialization of the system, the default values of the length of each BSSAP+ timer are set. These default values are the recommended values of the protocol. Usually the users do not need to modify these values. For the definition of each timer, refer to 3GPP 29.018. SGSN might be connected to multiple VLRs. To locate the VLR, SGSN obtains the VLR number according to RAI, translates the GT and then obtains the destination signaling code of MTS-U/VLR.
68P02904W52-B 31-Jan-2005
3-27
3-28
68P02904W52-B 31-Jan-2005
Chapter
Iu interface Configuration (3G)

68P02904W52-B 31-Jan-2005
4-1
Iu interface Configuration Overview
Iu interface Configuration Overview

Iu interface configuration includes configuration for the user plane and control plane of the Iu interface. There is no restriction to the configuration sequence.
4-2
68P02904W52-B 31-Jan-2005
Configuring User Plane of Iu Interface

This section introduces the configuration for the IP route and GTP parameters of the user plane. After the configuration, the user plane of the Iu interface can normally process data.
Description
Preset conditions
The hardware configuration has finished.
Data preparations
Item VPI/VCI Basic information. Local IP address. Data Slot number and port number of optical port which is connected with RNC. Traffic parameter.
68P02904W52-B 31-Jan-2005
4-3
Procedure
If the IPOA PVC type is RNCOA, you may configure the user plane related data through the following steps. Step 1 2 3 (optional). 4 (optional). 5 6 Operation Add VRT template. Add local IP address to a VA port of the UHPU. Add a record to the PVC Traffic Table. Add the backup relation on the optical port connected to RNC. Add an IPOA PVC between an RNC and SGSN. Add GTP parameters. Command ADD BNET_VRT ADD BNET_LOCAL_IP ADD BNET_CONN_TRAFFIC ADD BNET_PORT_BACKUP ADD BNET_RNC_IPOA See Chapter 5, "Gn/Gp Interface Configuration,"
If the IPOA PVC type is normal IPOA, you may configure the user plane related data through the following steps. Step 1 2 (optional). 3 (optional). 4 5 Operation Add IP address to a VA port of the UHPU. Add a record to the PVC Traffic Table. Add the backup relation on the optical port connected to RNC. Add an IPOA PVC between an RNC and SGSN. Add GTP parameters. Command ADD BNET_UHPU_IF_IP ADD BNET_CONN_TRAFFIC ADD BNET_PORT_BACKUP ADD BNET_RNC_IPOA See Chapter 5, "Gn/Gp Interface Configuration,"
Example
Add an normal IPOA PVC between the SGSN and an RNC
;;Add an IP address to the VA port of the UHPU. ADD BNET_UHPU_IF_IP: SN=9, SUBSN=1, VPN=1, IP="20.20.41.100", MSK="255.255.255.0"; ;;Add an IPOA PVC between an RNC and SGSN. ADD BNET_RNC_IPOA: SN=3, PN=7, VPI=5, VCI=200, HSN=9, HSSN=1, VPN=1, IP="20.20.41.12"; 4-4 68P02904W52-B 31-Jan-2005
Add two RNCOA IPOA PVCs between the SGSN and an RNC
ADD BNET_VRT: VRTNO=1, IP="191.22.6.98", MASK="255.255.255.0"; ADD BNET_LOCAL_IP: SN=9, SSN=0, VPN=1, VRTNO=1, LIP="191.22.6.76"; ADD BNET_LOCAL_IP: SN=9, SSN=1, VPN=1, VRTNO=1, LIP="191.22.6.77"; ADD BNET_RNC_IPOA: SN=2, PN=0, VPI=5, VCI=200, HSN=9, HSSN=0, VPN=1, IP="191.22.6.55", IPOATY=RNCOA; ADD BNET_RNC_IPOA: SN=2, PN=0, VPI=5, VCI=201, HSN=9, HSSN=1, VPN=1, IP="191.22.6.55", IPOATY=RNCOA;
Reference
IPOA PVC
The IPOA PVCs between SGSN and RNC are divided into two types: Normal IPOA PVC. There is only one normal IPOA PVC between an RNC and an SGSN. That is, the RNC can communicate with only one FE of the SGSN. Data packets from the RNC to the other FEs are forwarded through that FE.To add an IPOA PVC, you shall specify the IP address of the VA port. RNCOA PVC. There is an RNCOA PVC between an RNC and each FE of an SGSN. That is, the RNC can communicate with each FE and transmit data packets to a specified FE of the SGSN. This increases system efficiency. To add an RNCOA PVC, you shall specify the local IP address of the VA port. Figure 4-1 shows the differences between an RNCOA PVC and normal IPOA PVC. There is only one IPOA PVC between RNC1 and the SGSN. Therefore, the data from RNC1 to FEB in the UHPU or to the other boards shall be forwarded by FEA. Because there are four RNCOA PVCs between RNC2 and the SGSN, RNC2 can directly transmit data to the target FE.
68P02904W52-B 31-Jan-2005
4-5
Figure 4-1
IPOA PVC and RNCOA PVC.
UHPU
RNC1
IPoA PVC
VA port
FEA
RNCOA PVC
RNC2
RNCOA PVC VA port RNCOA PVC FEB
RNCOA PVC
UHPU
VA port
FEA
VA port
FEB
Modify the configurations at RNC according to different IPOA PVC types.
IP address for VA port and forward engine and local IP address for VA port
UHPUs provide data forward function in the SGSN. Each UHPU contains two forward engines, FEA and FEB. Each engine has an IP address, that is, the IP address for the GTP user plane of SGSN. This IP address is also for the GTP user plane of the Gn/Gp interface. Each forward engine provides 32 VA ports. Each port has an IP address. With this IP address, the SGSN can set up PVCs to an RNC, UGTP and UCDR. From the point of an RNC, the IP address of the VA port is that of the SGSN gateway. That is, the UHPUs forward the IP packets from an RNC to the GTP user plane of SGSN.
4-6
68P02904W52-B 31-Jan-2005
The IP addresses for different VA ports should be in different network segments. Each VA port also has a local IP address. To add an RNCOA PVC between SGSN and an RNC, you shall specify the local IP address of the VA port. Note that you can set the local IP addresses for different VA ports in one network segment. In addition, the network segment of a local IP address must exist in the VRT Table. Therefore, you should add the VRT Table before adding a local IP address. The local IP address and IP address of a VA port are independent from each other.
PVC Traffic parameters

The ATM services used for configuring the ATM layer include CBR, RTVBR, NRTVBR and UBR, as shown below: Constant Bit Rate (CBR), service that does not support error check, flow control or other processing. It realizes a smooth transition between the current telephony system and B-ISDN system. Variable Bit Rate (VBR), service classified into realtime transmission (RT-VBR) and non-realtime transmission (NRT-VBR). RT-VBR is used to describe the service featuring variable data streams and strict realtime requirement, for example interactive compressed video such as videoconference. NRT-VBR is used on the communication occasions requiring timing transmission. In such case, some delays and variations, for example, those in E-mail transmission can be accepted by the application. Unspecified Bit Rate (UBR), service that does not make any commitment or feedback to congestion. It is suitable for transmitting IP packets. In case of congestion, UBR cells will be discarded. However, neither relevant feedback nor the request for slowing down the transmission speed will be returned to the sender. Table 4-1 shows the descriptions of these ATM service characteristics.
68P02904W52-B 31-Jan-2005
4-7
Table 4-1
ATM service characteristics. CBR Y Y Y Y RT-VBR N N NRT-VBR N N UBR
Service characteristic Guaranteed bandwidth. Applicable to realtime communication. Applicable to burst communication. Feedback on congestion.
Table 4-2 shows the ATM traffic related parameters. In the Motorola C-SGSN system, the parameters in this table are configured in combination. For example, NOCLPNOSCR indicates 'no CLP, no SCR'. NOCLPNOSCRCDVT indicates 'no CLP, no SCP, with CDVT'; CLPNOTAGGINGSCR indicates 'no CLP, no TAGGING, with SCR'. Table 4-2 Meanings of the parameters related to ATM traffic. Parameter Peak cell rate. Sustainable cell rate. Cell delay variation tolerance. Cell loss priority. PCR SCR CDVT CLP Abbreviation Meaning Maximum cell transmission rate (cell/s). Long-term average cell transmission rate (cell/s). Maximum tolerable cell jitter (0.1s). Indicating which cells can be discarded (CLP=1), and which cells shall not be discarded (CLP=0) upon network congestion. Tagging the cells with CLP=0.
Tag.
TAGGING
There are some default traffic parameters in the system. You may directly use them according to the corresponding parameter ID.
4-8
68P02904W52-B 31-Jan-2005
Configuring Control Plane of Iu Interface

This section introduces the configuration for the control plane of the Iu interface. After the configuration, an RNC can normally interact with the SGSN for signaling.
Description
Preset conditions
Hardware configuration (for example, board configuration) related to the Iu interface has finished.
68P02904W52-B 31-Jan-2005
4-9
Data preparations
Item Basic information. RNC information. SAAL link information. MTP3B OPC RNC SPC Optical Slot to RNC. SLC Cont. NI MCC Optical Port to RNC. MNC VPI/VCI at CN side, VPI/VCI at RNC side. RNC ID Traffic parameters. Link number. Data
4-10
68P02904W52-B 31-Jan-2005
Procedure
Step 1 2 3 4 5 6 7 8 9 10 11 Operation Add a signaling point on the Iu interface. Add an originating signaling point on the Iu interface. Add an SAAL link. Add an MTP3B destination signaling point. Add an MTP3B signaling link set. Add an MTP3B signaling route. Add an MTP3B signaling link. Add an SCCP destination signaling point. Add an SCCP subsystem. Add RNC information. Add the mapping relation between UICP and RNC. Command ADD IUSP ADD IUOPC ADD SAALLNK ADD MTP3BDPC ADD MTP3BLKS ADD MTP3BRT ADD MTP3BLNK ADD IUSCCPDPC ADD IUSCCPSSN ADD RNC ADD UICPRNC
Example
Figure 4-2 shows a networking example of the control plane of the Iu interface. There are two RNCs, the SPCs of which are 0x100 and 0x101. Both NIs are national standby network. The SGSN SPC is 0x200 and its NI is national standby network. The two UICPs in the SGSN are configured in slots 1 and 2 of subrack 2. Figure 4-2 Networking example.
NI=NATIONALRES SPC=0X0100
RNC1
RNC2
BNET
SGSN
U I C P
U I C P
68P02904W52-B 31-Jan-2005
4-11
In this example, each RNC is connected with two UICPs. Therefore, if only one link is required between each RNC and UICP, you shall add altogether four SAAL links between RNC and SGSN. Take the optical connection in Figure 4-3 as an example. RNC1 is connected with optical port 3 on the board in slot 5 through a fiber. RNC2 is connected with optical port 2 on the board in slot 4 through a fiber. There are altogether two SAAL links between the SGSN and RNC1. The VPI/VCI of the first link is 1/100 (at RNC side) and 0/100 (at SGSN side). The VPI/VCI of the second link is 1/101 (at RNC side) and 0/101 (at SGSN side). There are altogether two SAAL links between the SGSN and RNC2. The VPI/VCI of the first link is 1/102 (at RNC side) and 0/102 (at SGSN side). The VPI/VCI of the second link is 1/103 (at RNC side) and 0/103 (at SGSN side). The UICP in slot 1 of subrack 2 processes the services on the first SAAL link between RNC1 and RNC2. The UICP in slot 2 of subrack 2 processes the services on the second SAAL link between RNC1 and RNC2. Figure 4-3 Optical connection in the example.
RNC1
VPI/VCI=1/100
RNC2
VPI/VCI=1/102
VPI/VCI=1/101
SLOT/PORT=5/3
VPI/VCI=1/103
SLOT/PORT=4/2
BNET
VPI/VCI=0/100 VPI/VCI=0/101
VPI/VCI=0/102
VPI/VCI=0/103
SGSN
U I C P
U I C P
SUBRACK/SLOT=2/2
SUBRACK/SLOT=2/1
According to the preceding configuration data and networking mode, you may configure the Iu interface related data as follows: ;;Add s signaling point. ADD IUSP: SPX=0, NI=NATB, SPC="200", CDT=LABEL14, STPF=DISABLE; ADD IUSP: SPX=1, NI=NATB, SPC="100", CDT=LABEL14, STPF=DISABLE; ADD IUSP: SPX=2, NI=NATB, SPC="101", CDT=LABEL14, STPF=DISABLE;
4-12
68P02904W52-B 31-Jan-2005
;;Add an originating signaling point. ADD IUOPC: OPX=0, NI=NATB, SPC="200", RSTF=ENABLE; ;;Add an SAAL link. ADD SAALLNK: LNK=0, RSN=5, RPN=3, RVPI=1, RVCI=100, CVPI=0, CVCI=100, SRN=2, SN=1, RTRAFI=10, STRAFI=10; ADD SAALLNK: LNK=1, RSN=5, RPN=3, RVPI=1, RVCI=101, CVPI=0, CVCI=101, SRN=2, SN=2, RTRAFI=10, STRAFI=10; ADD SAALLNK: LNK=2, RSN=4, RPN=2, RVPI=1, RVCI=102, CVPI=0, CVCI=102, SRN=2, SN=1, RTRAFI=10, STRAFI=10; ADD SAALLNK: LNK=3, RSN=4, RPN=2, RVPI=1, RVCI=103, CVPI=0, CVCI=103, SRN=2, SN=2, RTRAFI=10, STRAFI=10; ;;Add an MTP3B destination signaling point. ADD MTP3BDPC:DPX=0,DPN = "RNC1",NI=NATB, DPC="100", SLSSM=1, ADJF=TRUE; ADD MTP3BDPC: DPX=1, DPN="RNC2",NI=NATB, DPC="101", SLSSM=1,ADJF=TRUE; ;;Add an MTP3B link set. ADD MTP3BLKS: LSX=0, LSN="toRNC1", NI=NATB, DPC="100", SLSM=14, EMGF= DISABLE; ADD MTP3BLKS: LSX=1, LSN="toRNC2",NI=NATB, DPC="101", SLSM=14, EMGF=DISABLE; ;;Add an MTP3B route. ADD MTP3BRT: RTX=0, RTN="to RNC1", NI=NATB, DPC="100", PRI=0, LSX=0; ADD MTP3BRT: RTX=1, RTN="to RNC2", NI=NATB, DPC="101", PRI=0, LSX=1; ;;Add an MTP3B link ADD MTP3BLNK: LNK=0, LKN="LINK0", LSX=0, SLC=0, PRI=0, SATF=DISABLE, INHF=DISABLE, CONSTHD=0, CONETHD=0; ADD MTP3BLNK: LNK=1, LKN="LINK1", LSX=0, SLC=1, PRI=0, SATF=DISABLE, INHF=DISABLE, CONSTHD=0, CONETHD=0; ADD MTP3BLNK: LNK=2, LKN="LINK2", LSX=1, SLC=0, PRI=0, SATF=DISABLE, INHF=DISABLE, CONSTHD=0, CONETHD=0; ADD MTP3BLNK: LNK=3, LKN="LINK3", LSX=1, SLC=1, PRI=0, SATF=DISABLE, INHF=DISABLE, CONSTHD=0, CONETHD=0; ;;Add SCCP DPC ADD IUSCCPDPC: DPX=0, NI=NATB, DPC="100"; ADD IUSCCPDPC: DPX=1, NI=NATB, DPC="101"; ;;Add an SCCP subsystem. ADD IUSCCPSSN: SSNX=0, NI=NATB, SPC="100", SSN=RANAP, BSSN=NODEFINE;
68P02904W52-B 31-Jan-2005
4-13
ADD IUSCCPSSN: SSNX=1, NI=NATB, SPC="100", SSN= SCMG, BSSN=NODEFINE; ADD IUSCCPSSN: SSNX=2, NI=NATB, SPC="101", SSN=RANAP, BSSN=NODEFINE; ADD IUSCCPSSN: SSNX=3, NI=NATB, SPC="101", SSN= SCMG, BSSN=NODEFINE; ADD IUSCCPSSN: SSNX=4, NI=NATB, SPC="200", SSN=RANAP, BSSN=NODEFINE; ADD IUSCCPSSN: SSNX=5, NI=NATB, SPC="200", SSN= SCMG, BSSN=NODEFINE; ;;Add RNC information. ADD RNC: RNCX=0, RNCN="RNC01", MNC="00",MCC="460", RNCID=0, NI= NATB, SPC="100"; ADD RNC: RNCX=1, RNCN="RNC02", MNC="00",MCC="460", RNCID=1, NI= NATB, SPC="101"; ;;Add mapping relations between RNC and UICP. ADD UICPRNC: SRN=2, SN=1,RNCX=0; ADD UICPRNC: SRN=2, SN=1,RNCX=1; ADD UICPRNC: SRN=2, SN=2,RNCX=0; ADD UICPRNC: SRN=2, SN=2,RNCX=1;
Reference
Each UICP can correspond to up to 64 RNCs.
Broadband SS7
The signaling plane of the Iu interface adopts broadband SS7. Compared with the narrowband SS1, the broadband SS7 has the following two features: It requires SAAL link configuration. Each SAAL link serves as a Permanent Virtual Channel (PVC) in ATM switching. It provides a signaling transmission channel for the MTP3B. Each signaling point (including the originating signaling point) on the Iu interface shall be configured with two subsystems. One is the SCCP Management Subsystem (SCMG) with subsystem number of 1 and the other is network entity related subsystem (RANAP) with subsystem number of 142.
4-14
68P02904W52-B 31-Jan-2005
Configure RNC
The RNC Description Table describes the basic information of RNC such as the SPC and the network indicator and the control parameters of the signaling process (for example, the duration of various timers). The SGSN shall query the RNC Description Table to check whether the target RNC exists during relocation.
Configure mapping relation between UICP and RNC

The mapping relation between RNC and UICP is a many-to-many relation. Take following factors into consideration during the configuration: Load-sharing factor. There may be many UICPs configured in the system. The load on each UICP shall be shared evenly during the configuration. Security factors. For the sake of security, configure two or more UICPs for an RNC so that the RNC services can remain normal when one UICP is faulty.
68P02904W52-B 31-Jan-2005
4-15
4-16
68P02904W52-B 31-Jan-2005
Chapter
Gn/Gp Interface Configuration

68P02904W52-B 31-Jan-2005
5-1
Gn/Gp Interface Configuration Overview
Gn/Gp Interface Configuration Overview

This part presents instructions to configure data for Gn/Gp interface, including Gn/Gp interface route configuration, GTP protocol parameter configuration, DNS configuration , IPSEC configuration , OSPF configuration and RIP configuration.
5-2
68P02904W52-B 31-Jan-2005
Gn/Gp Interface Route Configuration

The Route configuration of Gn/Gp Interface is as follows:
Description
Preset conditions
Hardware configuration for the UGTP/UHPU has been completed.
Data preparation
Item UGTP subrack number and slot number. UHPU subrack number, slot number and forward engine number. Data ULPI/ULPC interface IP address. Gn/Gp route planning.
Basic information.
Procedure
Step 1 2 (optional). 3 4 Operation Configure IPoA PVC between the UGTP and the UHPU. Configure ULPI/ULPC interface backup. Configure ULPI/ULPC interface IP. Configure IP route to target node. Command ADD SGSN_IP_IPOA_PVC ADD BNET_NETWORK_BACKUP ADD BNET_GFI_IF_IP ADD BNET_IP_ROUTE
Example
Figure 5-1 shows Gn/Gp interface networking. The UGTP is in Slot 12 of the PSM Subrack 0; The UHPU is in Slot 9 of the BNET Subrack 2;
68P02904W52-B 31-Jan-2005
5-3
The ULPI is in Slot 5 of the BNET Subrack 2. SGSN provides the Gn/Gp interface through the ULPI, and then connects to GGSN with a router. Figure 5-1 Gn/Gp interface networking diagram.
IPOA FEA: 10.21.40.37 FEB: 10.21.41.37 PSM U R C U U G T P U G T P BNET
U L P U
U L P I
U N E T
U H P U
10.22.40.13
192.25.5.1 192.25.5.5 ROUTER 192.22.66.253 LAN Switch GGSN GTP-C: GGSN GTP-U: 192.22.66.6 192.22.66.1
;;Configure IPoA PVC between the UGTP and the UHPU. ADD SGSN_IP_IPOA_PVC: SRN=0, SN=12, HSN=9, HSSN=0; ;;Configure ULPI interface ADD BNET_GFI_IF_IP: SN=5, SSN=0,PN=0, IP="192.25.5.1", MSK="255.255.255.0"; ;;Configure IP route to GSN ADD BNET_IP_ROUTE: IP="192.22.66.6", MSK="255.255.255.255", GATE="192.25.5.5", PRE=0;
Reference
In SGSN, the Gn/Gp interface function is realized mainly by the UGTP, the UHPU and the ULPI/ULPC. The UGTP is responsible for functions of the GTP-C signaling plane, IPSec processing and NTP client. The UHPU is responsible for functions of GTP-U, routing and forwarding of GTP-C messages. The ULPI/ULPC provides external FE/GE Ethernet interface. The UGTP provides an IP address for the external SGSN GTP signaling plane. The UHPU provides two IP addresses (each IP address corresponds to a forwarding engine) for the external SGSN GTP user plane. Each port of the ULPI/ULPC provides an IP address for SGSN to connect an external router.
5-4
68P02904W52-B 31-Jan-2005
Configure IPOA PVC

To forward GTP-C messages, it is necessary to establish an IPOA PVC between the UGTP and the UHPU. The IPOA PVC can be on any engine of the UHPU.
The configuration of this IPOA PVC is different from that at the Iu interface, for it is only necessary to specify the location of the UGTP and the UHPU and forward engine instead of the IP address of the port.
Configure IP route
Since the destination IP addresses of IP messages sent by the UGTP and the UHPU may not be in the same network segment with the IP address of the ULPI/ULPC, it is necessary to configure IP route to specify the ULPI/ULPC interface to the destination IP address.
68P02904W52-B 31-Jan-2005
5-5
Configure DNS/HOSTFILE

Only after completion of configuration for DNS/HOSTFILE, can SGSN perform APN and SGSN number resolution correctly.
Description
Preset conditions
None.
Data preparation
Item DNS SERVER HOSTFILE IP address. APN or SGSN number. DNS priority. IP list. Data
Procedure
Step 1 2 Operation Configure DNS Server. Configure HOSTFILE. Command ADD DNSS ADD DNSH
Example
;;Add DNS Server ADD DNSS: IP="172.25.5.97", PRI=PRI1; ;;Add DNS host information ADD DNSH: NM="ggsn62.com.mnc000.mcc460.gprs", ADDRT=AF_INET, ADDR1="172.25.6.53";
5-6
68P02904W52-B 31-Jan-2005
Reference
During inter-SGSN Routing Area Updating (RAU), Relocation or PDP CONTEXT activation, domain name is usually used to specify the old SGSN or APN. Under this scenario, domain name resolution is used to obtain the IP address corresponding to the domain name. Two measures can be taken for domain name resolution: using the DNS server, using HOSTFILE. The DNS server provides the service of domain name resolution. HOSTFILE is saved in the local SGSN and contains only a few records. Follow the procedures below for domain name resolution. First, SGSN searches for the HOSTFILE records on the UGTP. If it cannot find records in the HOSTFILE, it searches for records in the DNS Cache in the UGTP. If it still cannot get records, it uses the DNS server for domain name resolution. The DNS Cache in the UGTP is a buffer that saves the domain name and IP address obtained using the DNS server. It is used to speed up the domain name resolution, and thus to cut down the number of accesses to the DNS server. The record in the DNS Cache has a certain life cycle. When its life cycle expires, the record will become invalid. Generally, DNS server is required to be configured for domain name resolution. And HOSTFILE is usually used for the resolution of those frequently used domain names, because resolution by HOSTFILE is more efficient than the resolution by DNS server.
68P02904W52-B 31-Jan-2005
5-7
Configuring GTP Protocol Parameters

The setting of protocol parameters may have serious impact upon the system. It is recommended to adopted system default values. You should kwow the case without a doubt before making a modification to the parameter configuration.
GTP protocol parameters are used to control functions of the GTP control plane (Gn/Gp interface) and the GTP user plane (including Iu interface and Gn/Gb interface).
Description
Preset conditions
None.
Data preparation
None.
5-8
68P02904W52-B 31-Jan-2005
Procedure
Operation Configure GTP message. Parameter type Whether to send optional fields. Equipment associated information. Path maintenance mode. Overload/congestion threshold. Number of GPT-U paths supported, number of signaling messages waiting for responses. Configure UHPU running parameter. Overload/congestion threshold. Whether to check sequence number of packets forwarded. Bandwidth. Bandwidths of various services. Command SET GTPPUB SET GTPPUB SET GTPPUB SET UGTP SET GTPPUB SET UHPUPATH SET UHPUUSRCTRL SET SEQCHK SET UHPUBW SET BWRATIO
Configure GTP path parameter.
Example
;; Set GTP-C/GPT-U path maintenance mode. SET GTPPUB: PMNTM=ECHO, ECHOSIG=ON;
Reference
Refer to 3GPP29.060 for details about the GTP protocol.
68P02904W52-B 31-Jan-2005
5-9
Configuring QoS Parameters

Quality of Service (QoS) is an evaluation of performance of user data flow passing by network. The presentation of QoS aims to provide 3G/2.5G users with reliable point-to-point services. The QoS evaluation is based on multiple specifications including service availability, delay, delay jitter, throughput and packet loss ratio. SGSN configuration associated with QoS includes CBWFQ parameter, WRED parameter, DSCP remark and mapping between QoS and DSCP.
Description
Preset conditions
None.
Data preparation
None.
Procedure
Step * * * * * Operation Configure CBWFQ parameter. Configure WRED parameter. Configure remarking correspondence. Configure mapping relationship from QoS to DSCP. Configure mapping relationship from DSCP to QoS. Command SET QOSPRI SET WRED SET DSCPRMK SET QOSDSCP SET DSCPQOS
Example
;;Modify DSCP of corresponding to the Steaming service as EF SET QOSDSCP: SCDSCP=EF;
5-10
68P02904W52-B 31-Jan-2005
Reference
CBWFQ
Figure 5-2 Schematic diagram of CBWFQ.
queue queue 0 queue 1 queue 2 Priority queue
queue N1
Classification Data packets to be sent via this interface
Default queues queue 1 queue 2
queue N2
As shown in Figure 5-2, CBWFQ (Class Based Weighted Fair Queuing) first classifies packets according to the interfaces using which they have entered the network equipment, and the protocols adopted for the packets, and also as per whether the packets match ACL. Then it let the packets of different classes enter different queues. The packets that do not match any class are sent into the default queues, and are processed as per WFQ, that is they are processed in stream mode. During dequeue scheduling, each queue is allocated with a bandwidth. The scheduler sends the dequeuing packets out as per the bandwidth allocated to each queue. Queue 0 is the priority queue. The packets of one or multiple classes can be set to enter the priority queue, and the corresponding occupied bandwidth can also be set. When there are packets in the priority queue, the scheduler always send these packets first. Only when there is no packet left in this queue shall the scheduler start to schedule the packets in other queues.
... ...
Data packets off the interface
Dequeue scheduling
68P02904W52-B 31-Jan-2005
5-11
When there is no congestion on the interface that is when there is no packet in other queues), all the packets in the priority queue can be sent. When congestion occurs to the interface (that is when there are packets in other queues), the transmission speed of the packets in the priority queue shall be restricted, and the packets beyond the specified traffic limit shall be discarded. In this way, the packets that belong to the priority queue can get free bandwidth when no congestion occurs to the interface, whereas, in the case of interface congestion, the occupied bandwidth shall not exceed the specified bandwidth, to ensure the specified bandwidth for other packets. In addition, if any, the scheduler shall send the packets in the priority queue. Therefore, for the packets in the priority queue, the transmission delay is maximally the time taken by the interface to send a packet with the largest size. Whether delay or delay jitter takes place, the impact can be minimized in the priority queue, which provides reliable QoS guarantee for delay-sensitive applications such as VoIP services. Queues 1 to N1 in Figure 5-2 are the queues of the packets of each class. The packets of each class occupy a queue. When the scheduler schedules to dequeue packets, the dequeuing packets are sent out as per the bandwidth specified by the user for each class. The packets that belong to queue 1 to queue N1 are ensured the specified bandwidth. When there is no packet of certain classes on the interface, the packets that belong to queue 1 to queue N1 can fairly get free bandwidth. When congestion takes place on the interface, it can still be ensured that the packets of each class can occupy the minimum bandwidth specified by the user. Compared with the time division multiplexing system, the line utilization ratio is greatly enhanced. The packets that do not match any class specified by the user are sent to the default queues. The default queues can be logically considered as one queue, but actually, it is a WFQ queue. The packets that have entered the default queues are then classified in stream mode. Packets can be classified into maximum 64 classes (including the default class). So the maximum value of N1 is 63. N2 (the number of default queues) can be set by the user. For the default queues and queue 1 to queue N1, the user can set the maximum queue length. When the queue length reaches the maximum length, the policy of discarding tails shall be adopted by default. But the user can also select the discarding policy of WRED (Weighted Random Early Detection). Refer to II. WRED for further description. However, for the priority queue, when congestion occurs to the interface, flow control shall be started. Therefore, the user need not set the queue length (The policy of discarding tails is not required). In addition, because the packets in the priority queue are generally VoIP (Voice over IP) packets which adopt UDP, the discarding policy of WRED is also not required.
WRED
Due to the limitation of memory resources, the traditional processing method is that all the incoming packets are discarded when the queue length reaches the specified maximum length. For TCP packets, discarding of numerous packets will lead to TCP timeout, thus triggering the slow startup and congestion avoiding mechanism of TCP to slow down the transmission of TCP packets. When the packets of multiple TCP connections are discarded from a queue at the same time, the slow startup and congestion avoiding mechanism will be triggered for these TCP connections at the same time, which is called 'TCP global synchronization'. In this way, the packets sent from these TCP connections to the queue will be reduced simultaneously, so that the speed of incoming packets of the queue is below the line transmission speed, thus reducing the utilization ratio of line bandwidth. Moreover, the traffic volume of the packets sent to the queue always changes abruptly, so the traffic volume on the line always fluctuates between minimum quantity and saturation.
5-12
68P02904W52-B 31-Jan-2005
To avoid such kind of problem from occurrence, the discarding policy of WRED (Weighted Random Early Detection) can be adopted for the queues. The difference between WRED and RED is that IP priority is adopted and discarding policies are differentiated. The user can set the low threshold and high threshold for the queue length. When the queue length is below the low threshold, no packet shall be discarded from the queue. When the queue length is between the low and high thresholds, WRED starts to randomly discard packets. Moreover, the discarding probability is high for long queues. When the queue length is higher than the high threshold, all the packets shall be discarded from the queue. Because WRED randomly discards packets, the transmission speed of multiple TCP connections will not be reduced simultaneously, thus avoiding TCH global synchronization from occurrence. When the packets of one TCP connection are discarded, the other TCP connections still maintain high transmission speed. In this way, there are always packets sent at a high speed from one or multiple TCP connections at any time, thus enhancing the utilization ratio of line bandwidth. If queue length, low threshold and high threshold are directly adopted for discarding packets as well as for comparison, burst data streams shall be treated unfairly, which is unfavorable for the transmission of data streams. Therefore, during the comparison of queue length, low threshold and high threshold, and discarding of packets, the average length of queues (relative value based on the comparison of the specified thresholds and average length) is adopted. The average length of queues is the result of low-pass filtration. It reflects the changing trend of the queues, and is non-sensitive to the burst changing of queue length. So the unfair treatment of burst data streams can be avoided. When the queuing mechanism adopts WFQ, for the packets with different precedence levels, the user can set different queue length filtration coefficients, low thresholds, high thresholds and discarding probabilities. In this way, different discarding characteristics can be provided to the packets with different precedence levels. See Figure 5-3 for the relationship between WRED and the queuing mechanism. Figure 5-3 Relationship between WRED and the queuing mechanism.
RED discarding queue 1 queue 2 Classification Dequeue scheduling Data packets to be sent via this interface queue N1 Data packets off the interface
When WRED is adopted together and WFQ, stream-based WRED can be realized. When packet classification is performed, different streams have their own queues. For a small stream, because the queue length is always comparatively small, the discarding probability will also be comparatively small, whereas, the large stream will have comparatively large queue length, and hence more packets will be discarded, thus protecting the benefits of small streams. Even if WRED is adopted together with other queuing mechanisms, for a small stream, because the number of packets is small, the discarding probability shall also be comparatively small. The benefits of small streams can also be protected.
68P02904W52-B 31-Jan-2005
5-13
Mapping relation between QoS and DSCP

Diff-Serv is an IP QoS model that is applicable to the backbone network and can satisfy multiple service requirements. This model defines standard forwarding services such as Expedited Forwarding (EF), Assured Forwarding (AF), and so on. In the Diff-Serv system, users can apply for services at different levels using the DS field of packet marking which is redefined from ToS field in the IP packet. The first 6 bits of DS field are DSCP (DS CodePoint) and the group of the packets with the same DSCP value is called Behavior Aggregate (BA). A router reserves the mapping of DSCP to Per-Hop Behaviors (PHB, the behaviors satisfying a forwarding requirement, such as traffic policing, traffic shaping, queue management and other QoS behaviors). When a packet enters a router, it will be classified into a BA according to its DSCP and forwarded by a specific PHB. Currently, IETF has defined three standard PHBs: Expedited Forwarding (EF), Assured Forwarding (AF) and Best-Effort (BE - the default PHB).
5-14
68P02904W52-B 31-Jan-2005
EF PHB. EF is defined as the forwarding process like this: The information flow rate sent from any Diff-Serv node must in any case be equal to or higher than the set rate. EF PHB cannot be remarked in the DS field. Remarking is only allowed at the edge node and a new DSCP (different mappings of DSCP to PHB can be selected for different DS domains) is required to adapt to the features of EF PHB. When the 'tunneling' technology is adopted, an external packet needs to be marked as EF. EF PHB aims to simulate the forwarding effect of Virtual Leased Line in the DS domain and provides the forwarding service with low packet discarding rate, low delay and high bandwidth.
AF PHB. AF is designed to satisfy the following requirements: when users subscribe bandwidth services with ISP, traffic is allowed to exceed the specifications of the subscription. For the traffic that does not exceed the subscription specifications, the forwarding quality should be ensured. For the traffic that exceeds the specifications, it is hoped that they should be forwarded at a lower QoS levels instead of being discarded simply. Currently, four categories of AF have been defined, namely, AF1, AF2, AF3 and AF4. Each category of AF service packet can be further divided into 3 drop precedence. AF code point AFij means that AF category is i (1<= i <= 4) and drop precedence is j (1<= j <= 3). When providing AF services, operators allocate different bandwidth resources to each category of AF. There is one special requirement for AF PHB: traffic control is not allowed to change the order of the packets in the same information flow. For example, different packets in a service flow belong to the same AF level, but marked with different drop precedence during traffic policing. In this case, though there are different discarding probabilities for different packets, the order between them cannot be changed. This mechanism is especially applicable to multimedia service transmission.
BE PHB This is the traditional IP packet delivery service, which only focuses on the reachability and requires nothing else. All the routers must support BE PHB. The mapping from QoS to DSCP is mainly based on Traffic Class and Traffic Handling priority. QoS includes four classes based on Traffic Class:
conversational class (CONV for short). streaming class (STREAM for short). interactive class (INTACT for short). background class (BG for short). Traffic Handling priority is valid only when Traffic Class is interactive class. The mapping from DSCP to QoS is irrelative to Traffic Handling priority.
DSCP Remarking
In the course of flow control, SGSN may discard messages exceeding the specified threshold, or degrade DSCP class to lessen the impact upon the system.
68P02904W52-B 31-Jan-2005
5-15
Configuring IPSec
Configuring IPSec

IPSec configuration includes creation of manual security policy, isakmp security policy and IPSec Dynamic security Policy.
Description
Preset conditions
None.
Data preparation
Item IP protocol. Data flow parameter. Destination port operator. IPSEC Protocol. Security policy number. IPSEC manual security policy. Output ESP key string. Source port operator. Destination port 1. AH Auth Algorithm. Peer IP address. Input ESP hexadecimal encryption key. Output ESP key string. Source port 1. Destination port 2. ESP encryption algorithm. Input AH SPI. Input ESP hexadecimal verification key. Output ESP hexadecimal encryption key. Data Source port 2. Precedence. Destination IP. Type of service. Encapsulation mode. Input AH hexadecimal key. Input AH key string. Compress Algorithm. Input ESP SPI. Output AH hexadecimal key. Destination mask.
IPSEC Transform.
ESP Auth Algorithm. Input AH key string. Output AH SPI.
Output ESP SPI.
Output ESP hexadecimal verification key.
5-16
68P02904W52-B 31-Jan-2005
Configuring IPSec
Procedure
Create manual security policy:
Step 1 2 3 Operation Configure Access control list. Configure IPSEC Transform. Configure manual security policy. ADD ACL ADD IPSECTRANS ADD IPSECMANUALCM Command
Create isakmp security policy:

Step 1 2 3 4 (optional). 5 (optional). 6 (optional). 7 Operation Configure Access control list. Configure IPSEC Transform. Configure IKE security policy. Configure IKE pre-shared key. Configure peer RSA public key. Configure local RSA public and private keys. Configure IPSEC ISAKMP security policy. ADD ACL ADD IPSECTRANS ADD IKEPLC ADD IKEKEY ADD RSAPEER ADD RSALOC ADD IPSECISAKMPCM Command
Create IPSec Dynamic security Policy:

Step 1 (optional). 3 3 4 (optional). 5 (optional). 6 (optional). 7 Operation Configure Access control list. Configure IPSEC Transform. Configure IKE security policy. Configure IKE pre-shared key. Configure peer RSA public key. Configure local RSA public and private keys. Configure IPSEC dynamic security policy. ADD ACL ADD IPSECTRANS ADD IKEPLC ADD IKEKEY ADD RSAPEER ADD RSALOC ADD IPSECDYNCM Command
Step 4, 5 and 6 are optional. Whether step 4, 5 and 6 are necessary depends on IKE security policy.
68P02904W52-B 31-Jan-2005
5-17
Configuring IPSec
Example
Create a security tunnel between SGSN and GGSN to protect data flow between them. Here, the router instead of GGSN provides IPSec function. Figure 5-4 shows the IPSec configuration networking. The security protocol is ESP, the encryption algorithm is DES, and the verification algorithm is SHA1-HMAC-96. Figure 5-4
SGSN Serial2/0/1 202.38.163.1 Internet Serial4/1/2 202.38.162.1 10.1.2.1
IPSec configuration networking.

Router
GGSN 10.1.2..2
To create manual security policy

;;Add an ACL ADD ACL: ACLN=1, DIP="10.1.2.2", DM="0.0.0.0"; ;;Configure an transform mode, with AH protocol, HMAC-MD5 verification algorithm and tunnel mode. ADD IPSECTRANS: CTNM="TunAHMD5", PRO=AH, AHAUTH=HMAC_MD5; ;;Add an IKE manual IKE security policy: ADD IPSECMANUALCM:CMSN =1, ACLN=180, PIP="202.38.162.1", CTNM ="TUNAHMD5", IAHSPI =256, IAHKEYS="This%Isa$EX4AMPLE@", OAHSPI = 256,OAHKEYS= "i55ReALLYl@veGarfi*ld! ";
To create isakmp security policy:

;;Add an ACL ADD ACL: ACLN=1, DIP="10.1.2.2", DM="0.0.0.0"; ;; Configure an transform mode, with AH protocol, HMAC-MD5 verification algorithm and tunnel mode. ADD IPSECTRANS: CTNM="TunAHMD5", PRO=AH, AHAUTH=HMAC_MD5S; ;;Configure IKE security policy ADD IKEPLC: PRI=1; ;;Configure IKE pre-shared key ADD IKEKEY: KI=1, PIP1="202.38.162.1", KEY="a1b2c*3d4e5"; ;;Configure IPSEC ISAKMP security policy
5-18
68P02904W52-B 31-Jan-2005
Configuring IPSec
ADD IPSECISAKMPCM: CMSN=101, ACLN=1, PIP1="202.38.162.1", CTNM1=" TunAHMD5";
To create IPSec Dynamic security Policy

;; Configure an transform mode, with AH protocol, HMAC-MD5 verification algorithm and tunnel mode. ADD IPSECTRANS: CTNM="TunAHMD5", PRO=AH, AHAUTH=HMAC_MD5; ;;Configure IKE security policy ADD IKEPLC: PRI=1; ;; Configure IKE pre-shared key ADD IKEKEY: KI=1, PIP1="202.38.162.1", KEY="a1b2c*3d4e5"; ;; Configure IPSEC ISAKMP security policy ADD IPSECDYNCM: DCN=201, PIP1="202.38.162.1", CTNM1=" TunAHMD5";
Reference
None
IPSec
IPSec (IP Security) is a serial protocols established by IETF to ensure data security transmission on Internet. The communication devices ensure the confidential, integrated and authentic data packet transmission on the Internet through encryption and data origin authentication provided at the IP layer. IPSec implements the protection for IP datagram and the upper layer protocols through the Authentication Header (AH) and the Encapsulating Security Payload (ESP). Additionally, these mechanisms are correctly implemented and deployed, so that they ought not to adversely affect users, hosts, and other Internet components. AH (Authentication Header) is a packet header authentication protocol, mainly to provide functions such as data origin authentication, data integrity check and protection against replays. ESP (Encapsulating Security Payload) provides encrypting function for IP packets in addition to implementing all AH protocol functions. You can use AH protocol or ESP protocol or even both of them together. Security service provided by IPSec requires shared key. Internet Key Exchange, IKE, provides IPSec with automatic negotiation key exchange, establishment and maintenance of Security Association. It can simplify IPSec application and management.
Some Concepts Related to IPSec Implementation

The following concepts are related to IPSec Implementation.
68P02904W52-B 31-Jan-2005
5-19
Configuring IPSec
Data Flow. Data flow is a set of packets flow with the same data characteristics. Data flow can be recognized by the source IP address or destination IP address. Also you can recognize them by protocol type or port number. IPSec can enable different security protections for different data flow. For example, different security protocols, algorithms and shared keys will be used for different data flows.
IPSec policy. IPSec policy will be configured manually by user. It will specify security measures to be used for different data flows. For data flow definition will be implemented by configuring many rules in access control list, quote this access control list in IPSec policy to specify the protected data flow. An IPSec policy will be identified uniquely by 'name' and 'sequence number'. IPSec policies are divided into manual ones and IKE negotiated ones. The former needs users to configure the parameters such as key and spi and the latter automatically generates these parameters through IKE negotiation.
IPSec policy Sets. IPSec policy sets are collection for all IPSec policies having the same name and different sequence numbers. On an interface, an IPSec policy set can be used or removed. In IPSec policy sets many IPSec policies can be used on this interface at the same time, so for implement different security protections for different data flows. In one IPSec policy set, the smaller the sequence number is, the higher the priority will be.
Security Association. Security Association (SA) includes protocol, algorithm, shared key and other contents, prescribing how to process IP packets. Security association works in one direction. Between two security gateways, it is a two-way communication, so two security associations are required to provide separate security protection for inbound and outbound data flows. Security Association is identified uniquely by a triplet including Security Parameter Index (SPI), destination IP address, security protocol number (AH or ESP). The user can configure and maintain security association manually, but he needs to configure more parameters. Security Association can also be established and maintained by IKE. IKE can automatically configure and maintain the Security Association according to IPSec policy without user intervention.
Duration. There are two types of SA duration: time-based (in seconds) and traffic-based (in kilobytes). The traffic-based SA duration, that is, the valid time of the SA is accounted according to the traffic transmitted in the protection of IPSec, and the SA is invalid when the set value is exceeded. No matter which one of the two types expires first, the SA will get invalid. Before the SA is about to get invalid, IKE will set up a new SA for IPSec negotiation. So, a new SA is ready before the existing one obtains invalid.
5-20
68P02904W52-B 31-Jan-2005
Configuring IPSec
Security Parameter Index. Security Parameter Index (SPI) is a 32-bit value. Each IPSec packet will carry this value. Security Parameter Index (SPI), destinations IP address and security protocol numbers together form a triplet, to identify a specified Security Association uniquely. In manual configuration for Security Association, manually assigning Security Parameter Index (SPI) is required. To ensure Security Association exclusiveness, different security parameter indexes must be used to configure Security Association. When IKE negotiation creates Security Association, random number will be used to generate Security Parameter Index (SPI).
IPSec proposal. IPSec proposal content includes security protocol, algorithm used by security protocol and packet encapsulation format of security protocol. It specifies the mode to transform ordinary IP packet into IPSec packet. In IPSec policy, quote an IPSec proposal so for specify the protocol and algorithm used by IPSec policy and so on.
Preparation for IPSec Configuration Specify data flow and security gateways to be configured
Security tunnel is the end-to-end tunnel between two security gateways. A local end and a peer must be specified for a security tunnel. A security tunnel corresponds to a protected data flow. Many security tunnels can be configured between two security gateways. Security tunnel will be configured on the interfaces between two security gateways, such as Ethernet interface, synchronous/asynchronous serial interface. The local and peer address of a security tunnel indicate the IP address of the interfaces. Related IKE peer need to be configured in IPSec policy (ipsec policy) according to the requirements. Access control list (acl) needs to be configured, and data flow specified for protection. In addition, access control list (security acl) should be quoted in IPSec policy.
Specify negotiation mode for Security Association establishment

There are 2 modes to configure Security Association. One is manual mode (manual), the other is IKE automatic negotiation (isakmp). The configuration of the former is a bit complicated, in which IPSec policy information and all information required by Security Association establishment must be manually entered, and some advanced IPSec features (for example timing update for shared key) will not be supported. However, its advantage is that it can independently implement IPSec function without IKE. However the configuration of the latter is comparatively simple, in which only IPSec policy information needs to be configured. IKE automatic negotiation will be used to establish and maintain Security Association. Using IKE negotiation to configure Security Association is herewith recommended. While creating an IPSec policy, negotiation mode must be specified. Negotiation mode cannot be changed if IPSec policy is established. To change negotiation mode, you can only delete the old IPSec policy and then establish a new one. When IKE negotiation is specified, related IKE configuration needs to be done. For detailed operation, refer to IKE configuration.
68P02904W52-B 31-Jan-2005
5-21
Configuring IPSec
Specify security protocol, algorithm and encapsulation format

AH and ESP protocols are two kinds of security protocols. AH protocol can support MD5 and SHA-1 authentication algorithm. ESP protocol can support MD5 and SHA-1 authentication algorithm, DES and 3DES encryption algorithm. On the both ends of security tunnel, IPSec policy must be configured with the same protocol and algorithm. There are 2 kinds of IPSec encapsulation for IP packets: transport mode and tunnel mode. In transport mode, IPSec protects upper layer protocols, but does not protect IP packet header. In tunnel mode, IPSec will put entire IP packet into protection, and add a new IP header in front of the original IP packet. The source and destination addresses of this new IP header are IP addresses of the ends of security tunnel According to the requirements configure a security IPSec proposal (ipsec proposal), then, in IPSec policy (ipsec policy), quote this IPSec proposal (proposal).
Specify key and security parameter index (SPI)

If Security Association is established through IKE negotiation, the above information will be generated by IKE negotiation and no manual entering is required. If Security Association is configured manually, the above information must be specified in advance. On both ends of security tunnel, SPI and shared key of inbound Security Association on local end must be the same as that of the peer outbound Security Association. The SPI and shared key of outbound Security Association on local end must be the same with the peer inbound Security Association. IKE Overview
IPSec and IKE

Internet Key Exchange (IKE) protocol is configured in a framework specified by Internet Security Association and Key Management Protocol (ISAKMP). IKE will provide automatic negotiation and exchange of shared key for IPSec and configure Security Association, thus to simplify IPSec application and management. Network security has 2 meanings: one is internal LAN security, the other is external data exchange security. The former is implemented by means of Firewall, Network Address Translation (NAT) and so on. Emerging IPSec (IP Security) implements the latter. The IPSec association can be manually configured by the user, but when nodes increase in the network, manual configuration will be very difficult, and hard to ensure security. In this case, the IKE automatic negotiation can be used to establish Security Association and exchange shared key.
IKE Security Mechanism

IKE has a series of self-protection mechanisms to safely distribute shared key, authenticate identity, and establish IPSec Security Association and so on in unsecured network. IKE security mechanism includes:
5-22
68P02904W52-B 31-Jan-2005
Configuring IPSec
Diffie-Hellman (DH) exchange and shared key distribution. Diffie-Hellman algorithm is a shared key algorithm. The both parties in communication can exchange some data without transmitting shared key and find the shared key by calculation. The pre-condition for encryption is that the both parties must have shared key. The merit of IKE is that it never transmits shared key directly in the unsecured network, but calculates the shared key by exchanging a series data. Even if the third party (for example Hackers) captured all exchange data used to calculate shared key for both parties, he cannot figure out the real shared key.
Perfect Forward Secrecy (PFS). PFS feature is a security feature. When a shared key is decrypted, there will be no impact on the security of other shared keys, because these secrets have no derivative relations among them. PFS feature is ensured by DH algorithm.
Identity authentication. Identity authentication will authenticate identity for both parties in communication. Authentication key can be entered to generate shared key. It is impossible for different authentication keys to generate the same shared key between the two parties. Authentication key is the key in identity authentication for both parties.
Identity protection. After shared key is generated, identity data will be sent in encrypted mode, thus implementing identity data protection. IKE using 2 stages to implement IPSec shared key negotiation and Security Association creation. In the first stage, parties involved in the communication will establish a channel for identity authentication and security protection. An ISAKMP Security Association (ISAKMP SA) is established by the exchange in this stage. In the second stage, security channel established in phase 1 will be used to negotiate specific Security Association for IPSec and establish IPSec SA. IPSec SA will be used for final IP data security transmission. The relation between IKE and IPSec is shown in Figure 5-5. Figure 5-5 Relation between IKE and IPSec.
SA negotiation
IKE IKE
Router A
Router B
TCP/UDP
SA
SA
TCP/UDP
IPSec
IPSec
IP
Encrypted IP packet
68P02904W52-B 31-Jan-2005
5-23
Configuring OSPF
Configuring OSPF

Open Shortest Path First (OSPF) is an internal network gateway protocol developed by IETF based on link state. It is necessary to make some associated configuration before OSPF is enabled for the Gn/Gp interface.
Description
Preset conditions
None.
Data preparation
Item Basic information. Interface IP. Slot number. Data Port number. Virtual port number. Interface priority. Interface network type.
IP of neighboring node.
Procedure
Step 1 2 3 4 Operation Start OSPF protocol. Add interface running OSPF protocol. Set property for OSPF interface. Add neighboring node of OSPF protocol. Command STR BNET_OSPF_RIP ADD BNET_OSPF_NETWORK SET BNET_OSPF_PRO ADD BNET_OSPF_NEIGHBOR
Example
;; Start OSPF protocol STR BNET_OSPF_RIP: TYPE=OSPF; ;; Add an interface running OSPF protocol
5-24
68P02904W52-B 31-Jan-2005
Configuring OSPF
ADD BNET_OSPF_NETWORK: IP="192.100.0.0", MASK="0.0.255.255", AID=1; ;; Set property for OSPF protocol interface SET BNET_OSPF_PRO: SN=5, PN=0, VPN=0, TYPE=PRIORITY, VALUE=1; ;;Add OSPF neighboring node ADD BNET_OSPF_NEIGHBOR: IP="10.100.1.1";
Reference
Open Shortest Path First (OSPF) is an Interior Gateway Protocol based on the link state developed by IETF.
Process of OSPF Route Calculation

The routing calculation process of the OSPF protocol is as follows: Each OSPF-capable router maintains a Link State Database (LSDB), which describes the topology of the whole AS. According to the network topology around itself, each router generates a Link State Advertisement (LSA). The routers on the network transmit the LSAs among them by transmitting the protocol packets to each other. Thus, each router receives the LSAs of other routers and all these LSAs compose its LSDB. LSA describes the network topology around a router, so the LSDB describes the network topology of the whole network. Routers can easily transform the LSDB to a weighted directed map, which actually reflects the topology architecture of the whole network. Obviously, all the routers get a graph exactly the same. A router uses the SPF algorithm to calculate the shortest path tree with itself as the root, the tree shows the routes to the nodes in the autonomous system. The external routing information is leaf node. A router, which advertises the routes, also tags them and records the additional information of the autonomous system. Obviously, the Routing tables obtained by different routers are different. Furthermore, suppose that the routers are directly connected without other in-between routing devices in a broadcast network. To enable the individual routers to broadcast the information of their local statuses to the whole AS, any two routers in the environment should establish adjacency between them. In this case, however, the changes that any router takes will result in multiple transmissions, which is not only unnecessary but also wastes the precious bandwidth resources. To solve this problem, 'Designated Router' (DR) is defined in the OSPF. Thus, all the routers only send information to the DR for broadcasting the network link states in the network. Thereby, the number of router adjacent relations on the multi-access network is reduced. OSPF supports interface-based packet authentication to guarantee the security of route calculation. Also, it transmits and receives packets by IP multicast.
OSPF Packets
OSPF uses five types of packets:
68P02904W52-B 31-Jan-2005
5-25
Configuring OSPF
Hello Packet: It is the common packet which is periodically sent by a router to its peer. It contains the values of some timers, DR, BDR and the known peer.
Database Description (DD) Packet: When two routers synchronize their databases, they use the DD packets to describe their own LSDBs, including the digest of each LSA. The digest refers to the HEAD of an LSA, which can be used to uniquely identify the LSA. Such reduces the traffic size transmitted between the routers, since the HEAD of a LSA only occupies a small portion of the overall LSA traffic. With the HEAD, the peer router can judge whether it already has had the LSA.
Link State Request (LSR) Packet: After exchanging the DD packets, the two routers know which LSAs of the peer routers are lacked in the local LSDBs. In this case, they will send LSR packets requesting for the needed LSAs to the peers. The packets contain the digests of the needed LSAs.
Link State Update (LSU) Packet: The packet is used to transmit the needed LSAs to the peer router. It contains a collection of multiple LSAs (complete contents).
Link State Acknowledgment (LSAck) Packet. The packet is used for acknowledging the received LSU packets. It contains the HEAD(s) of LSA(s) requiring acknowledgement.
Related Concepts
Router ID. To run OSPF, a router must have a router ID. If no ID is configured, the system will automatically select an IP address from the IP addresses of the current interface as the Router ID. DR (Designated Router). Suppose there is a broadcast network environment, in which, the routers are directly connected without other in-between routing devices. To enable the individual routers to broadcast the information of their local statuses to the whole AS, all routers in the environment should establish adjacency. In this case, however, the changes that any router takes will result in multiple transmissions, which are not only unnecessary but also waste the precious bandwidth resources. To solve the problem, OSPF defines the 'Designated Router' (DR). All the routers only need to transmit information to the DR for broadcasting the network link states. Which router can be the DR in its segment is not specified manually. Instead, DR is elected by all the routers in the segment.
5-26
68P02904W52-B 31-Jan-2005
Configuring OSPF
BDR (Backup Designated Router). If the DR fails for some faults, a new DR must be elected and synchronized with the other routers on the segment. This process will take a relatively long time, during which, the route calculation is incorrect. To shorten the process, BDR is brought forth in OSPF. In fact, BDR is a backup for DR. DR and BDR are elected in the meantime. The adjacencies are also established between the BDR and all the routers on the segment, and routing information is also exchanged between them. After the existing DR fails, the BDR will become a DR immediately.
Area. The network size grows increasingly larger. If all the routers on a huge network are running OSPF, the large number of routers will result in an enormous LSDB, which will consume an enormous storage space, complicate the SPF algorithm, and add the CPU load as well. Furthermore, as a network grows larger, the topology becomes more likely to take changes. Hence, the network will always be in 'turbulence', and a great deal of OSFP packets will be generated and transmitted in the network. This will lower the network bandwidth utility. In addition, each change will cause all the routes on the network to compute the route again. OSPF solves the above problem by partitioning an AS into different areas. Areas logically group the routers. The borders of areas are formed by routers. Thus, some routers may belong to different areas. A router connects the backbone area and a non-backbone area is called Area Border Router (ABR). An ABR can connect to the backbone area physically or logically.
Backbone Area. After the area division of OSPF, not all the areas are equal. In which, an area is different from all the other areas. Its area-id is 0 and it is usually called the backbone area.
Virtual link. Since all the areas should be connected logically, virtual link is adopted so that the physically separated areas can still maintain the logic connectivity.
Route Summary. AS is divided into different areas which are interconnected using OSPF ABRs. The routing information between areas can be reduced through route summary. Thus, the size of routing table can be reduced and the calculation speed of the router can be improved. After finding an intra-area route of an area, the ABR will look up the routing table and encapsulate each OSPF route into an LSA and send it outside the area.
68P02904W52-B 31-Jan-2005
5-27
Configuring RIP
Configuring RIP

Routing Information Protocol (RIP) is a simple dynamic routing protocol. It is necessary to perform RIP associated configuration when RIP is required at the Gn/Gp interface.
Description
Preset conditions
None.
Data preparation
Item Basic information. Interface IP. adjacent node IP. Data
Procedure
Step 1 2 3 Operation Start RIP protocol. Add an interface running RIP protocol. Add an adjacent node of RIP protocol. Operation STR BNET_OSPF_RIP ADD BNET_RIP_NETWORK ADD BNET_RIP_NEIGHBOR
Example
;; Start RIP protocol STR BNET_OSPF_RIP: TYPE=RIP; ;; Add an interface running RIP protocol ADD BNET_RIP_NETWORK: IP="20.20.20.0"; ;; Add an adjacent node of RIP protocol ADD BNET_RIP_NEIGHBOR: IP="20.20.20.20";
5-28
68P02904W52-B 31-Jan-2005
Configuring RIP
Reference
Routing Information Protocol (RIP) is a relatively simple dynamic routing protocol, but it has a wide application. RIP is a kind of Distance-Vector (D-V) algorithm-based protocol and exchanges routing information using UDP packets. It employs Hop Count to measure the distance to the destination host, which is called Routing Cost. In RIP, the hop count from a router to its directly connected network is 0, and that to a network which can be reached through another router is 1, and so on. To restrict the time to converge, RIP prescribes that the cost is an integer ranging between 0 and 15. The hop count equal to or exceeding 16 is defined as infinite, that is to say, the destination network or the host is unreachable. RIP sends routing refreshing message every 30 seconds. If no routing refreshing message is received from one neighboring network in 180 seconds, RIP will tag all routes of the neighboring network to be unreachable. If no routing refreshing message is received from one neighboring network in 300 seconds, RIP will finally remove the routes of the neighboring network from the routing table. To improve the performances and avoid route loop, RIP supports Split Horizon, Poison Reverse and allows importing the routes discovered by other routing protocols. Each router running RIP manages a route database, which contains routing entries to all the reachable destinations in the network. These routing entries contain the following information:
68P02904W52-B 31-Jan-2005
5-29
Configuring RIP
Destination address: IP address of a host or network. Next hop address: The address of the next router that an IP packet will pass through for reaching the destination. Output interface: The interface through which the IP packet should be forwarded. Cost: The cost for the router to reach the destination, which should be an integer in the range of 0 to 16. Timer: Duration from the last time that the routing entry is modified now. The timer is reset to 0 whenever a routing entry is modified. Route tag: Discriminate whether the route is generated by an interior routing protocol or by an exterior routing protocol. The whole process of RIP startup and running can be described as follows:
If RIP is enabled on a router for the first time, the router will broadcast the request packet to the adjacent routers. Upon receiving the request packet, the adjacent routers (on which, RIP should have been enabled) respond to the request by returning the response packets containing information of their local routing tables. After receiving the response packets, the router, which has sent the request, will modify its own routing table. At the same time, RIP broadcasts its routing table to the adjacent routers every 30 seconds. The adjacent routers will maintain their own routing table after receiving the packets and will select an optimal route, and then advertise the modification information to their respective adjacent network so for make the updated route globally known. Furthermore, RIP uses the timeout mechanism to handle the out-timed routes so for ensure the real-timeliness and validity of the routes. With these mechanisms, RIP, an interior routing protocol, enables the router to learn the routing information of the whole network. RIP has become one of the actual standards of transmitting router and host routes by far. It can be used in most of the campus networks and the regional networks that are simple yet extensive. For larger and more complicated networks, RIP is not recommended.
5-30
68P02904W52-B 31-Jan-2005
Chapter
Gb Interface Configuration (2.5G)

68P02904W52-B 31-Jan-2005
6-1
Gb Interface Configuration Overview
Gb Interface Configuration Overview

Gb interface configuration includes link configuration, management entity configuration, protocol parameter configuration and cell reference parameter configuration. They should be done in sequence.
6-2
68P02904W52-B 31-Jan-2005
Configuring Link and Management Entity

This part presents instructions to configure Gb interface physical and logic links and management entities. Upon the completion of the configuration, SGSN can communicate with BSS normally.
Description
Preset conditions
You have completed board configuration.
68P02904W52-B 31-Jan-2005
6-3
Data preparation
Item BC parameter. NS-VC parameter. NSE parameter. E1/T1 parameter. BC timeslot distribution. NS-VCI BSSID Check mode. Link frame format. BC mode. NSEI Data FR protocol mode. DLCI
Procedure
Step 1 2 3 4 Operation Configure E1/T1. Configure BC. Configure NSVC. Configure NSE. ADD BC ADD NSVC ADD NSE Command ADD E1T1CFG
Example
Figure 6-1
Gb interface configuration networking.
460010001010001 SGSN BSS0

0 UGBI UEPI 1 UGBI UEPI 2 UGBI UEPI
460010001010002 460010001010003 460010001010004 460010002010001 460010002010002 BSS1 460010002010003 460010002010004
6-4
68P02904W52-B 31-Jan-2005
Figure 6-1 shows Gb interface networking. The configuration description is given below. ;; Configure E1/T1. ADD E1T1CFG: FN=0, SN=0, PORT=0, LKFRMT=DF, LKCT=HDB3; ADD E1T1CFG: FN=0, SN=0, PORT=1, LKFRMT=DF, LKCT=HDB3; ADD E1T1CFG: FN=0, SN=1, PORT=0, LKFRMT=DF, LKCT=HDB3; ADD E1T1CFG: FN=0, SN=1, PORT=1, LKFRMT=DF, LKCT=HDB3; ADD E1T1CFG: FN=0, SN=2, PORT=0, LKFRMT=DF, LKCT=HDB3; ADD E1T1CFG: FN=0, SN=2, PORT=1, LKFRMT=DF, LKCT=HDB3; ;;Configure BC. ADD BC: FN=0, SN=0, PN=0, BCID=0, TS="00001000", DLCIT=1, MODE=DCE, PROTOCOL=Q933, BWCNTL=NO; ADD BC: FN=0, SN=0, PN=1, BCID=1, TS="00001000", DLCIT=1, MODE=DCE, PROTOCOL=Q933, BWCNTL=NO; ADD BC: FN=0, SN=1, PN=0, BCID=0, TS="00001000", DLCIT=1, MODE=DCE, PROTOCOL=Q933, BWCNTL=NO; ADD BC: FN=0, SN=1, PN=1, BCID=1, TS="00001000", DLCIT=1, MODE=DCE, PROTOCOL=Q933, BWCNTL=NO; ADD BC: FN=0, SN=2, PN=0, BCID=0, TS="00001000", DLCIT=1, MODE=DCE, PROTOCOL=Q933, BWCNTL=NO; ADD BC: FN=0, SN=2, PN=1, BCID=1, TS="00001000", DLCIT=1, MODE=DCE, PROTOCOL=Q933, BWCNTL=NO; ;;Add NSVCs between SGSN and BSS0,BSS1. ADD NSVC: OTHERNODE="BSS0", NSVCI=0, NSEI=0, FN=0, SN=0, PN=0, BCID=0, DLCI=16; ADD NSVC: OTHERNODE="BSS1", NSVCI=1, NSEI=1, FN=0, SN=0, PN=1, BCID=1, DLCI=16; ADD NSVC: OTHERNODE="BSS0", NSVCI=2, NSEI=0, FN=0, SN=1, PN=0, BCID=0, DLCI=16; ADD NSVC: OTHERNODE="BSS1", NSVCI=3, NSEI=1, FN=0, SN=1, PN=1, BCID=1, DLCI=16; ADD NSVC: OTHERNODE="BSS0", NSVCI=4, NSEI=0, FN=0, SN=2, PN=0, BCID=0, DLCI=16; ADD NSVC: OTHERNODE="BSS1", NSVCI=5, NSEI=1, FN=0, SN=2, PN=1, BCID=1, DLCI=16; ;;Configure NSE of SGSN: ADD NSE: OTHERNODE="TO BSS0", NSEI=0, FN=0, SN=0, BSSID=0; ADD NSE: OTHERNODE="TO BSS1", NSEI=1, FN=0, SN=1, BSSID=1;
68P02904W52-B 31-Jan-2005
6-5
Reference
Configure E1/T1
Only after the E1/T1 ports of UEPI/UTPI are configured by using the command ADD E1T1CFG, the FR layer link can be connected. If there are more than one E1/T1s connected to a BSS, and the number of the UGBI boards configured for SGSN is greater than 1, the E1/T1s must be connected to the UGBI boards uniformly.
E1 is the physical cable connecting BSS and SGSN. BSS can be connected with SGSN either directly or through the intermediate FR network. In SGSN, the UEPI/UTPI provides E1/T1 physical interface, and the UFEU implements FR protocol processing. UFEU has 8 E1 ports, numbered 0 to 7 respectively. E1/T1 cables can be led out of the 8 E1/T1 ports on UEPI/UTPI, as shown in Figure 6-2. Figure 6-2 Numbering of the ports on UFEU.
L O C A L P C I U E P C U F E U U E P I / U T P I 7 6 5 4 3 2 1 0 E1/T1
U G B I
7 6 5 4 3 2 1 0
E1/T1
Configure BC
BC refers to the bearer channel of frame relay, corresponding to the timeslot group of E1/T1 cables. A BC can be allocated with all available timeslots of an E1/T1, or only several of them. Its bandwidth equals to the number of timeslots multiplies 64 kbit/s. BCs of the same E1/T1 cable are distinguished by BCID (BC Identification). The basic principles for BC allocation are as follows:
6-6
68P02904W52-B 31-Jan-2005
The time slots occupied by the BC corresponding to SGSN and PCU should be the same. If BSS is connected with SGSN directly in the point-to-point manner, the BC corresponding to SGSN and that to PCU should be transmitted through the same pair of E1 cables. Configure as many time slots of E1 as possible to one BC. For example, configure the 31 time slots to one BC. The BC mode at SGSN should correspond to the data configuration at PCU. The PCU end is generally configured as DTE while the SGSN end as DCE. For example, if PCU is configured as DCE, SGSN has to be configured as DTE. If BSS and SGSN are connected through an intermediate FR network, both BSS and SGSN should act as DTE. The two ends of the cable should negotiate about the distribution of the time slots in BC.
PVC
Permanent Virtual Connection (PVC) refers to the permanent virtual connection of the frame relay. In one BC, a PVC is differentiated from others by its Data Link Connection ID (DLCI). DLCI at SGSN side should be the same with that at the BSS side. PVC is created together with NS-VC in the configuration for NSVC.
NS-VC
The configuration of NSVCI should be consistent with the data configuration at the PCU side. If BSS is connected with SGSN directly in the point-to-point manner, the PVCs corresponding to NSVCs at the two ends should be the same, that is the parameters BCI and DLCI at the two ends shall be configured the same.
NS-VC is the virtual link provided by NS layer for BSSGP layer, through which NS transmits the data of BSSGP layer. One NS-VC on the NS layer corresponds to one PVC on FR. That means, if one NS-VC has been configured in NS layer, it also acts as one PVC in FR layer. An NS-VC is uniquely identified by its NS-VCI. Each NS-VCI is unique in SGSN, and it is the same with that in BSS. NS divides NS-VCs into different groups by their NSEIs. NS-VCs in the same group work in load sharing mode. All NS-VCs in the same group (with the same NSEI) in SGSN are connected to only one BSS. One group of NS-VCs corresponds to one group of cells. For a BSS can contain multiple BSCs, all the cells corresponding to the BSC can be taken as one group. Allocate NS-VCs to each cell group (the number of NS-VCs depends on the traffic volume of the cell group). All the NS-VCs of one cell form one group too. The NS-VCs of one group should be evenly distributed at the UGBI board, UFEU board, E1/T1 and BC in the system. If a UGBI board has been configured with cells or SIG, it shall also be configured with the NS-VCs of the same NSEI. The number of NS-VCs allocated in this case depends on the total traffic volume of the cells configured on the board.
68P02904W52-B 31-Jan-2005
6-7
The number of NS-VCs configured on one BC depends on the time slots occupied by the BC and shall satisfy the following condition: 10 kbit/s (the number of time slots occupied by the BC % 64 kbit/s) + the number of NS-VCs to be configured on the BC 100 kbit/s.
NSE
Each group of NS-VCs requires an NSE to manage the group. Likewise, each group of cells requires an SIG on the UGBI to manage the group. NSE and SIG are in one-to-one correspondence. SIG is created automatically accompanying the creation of NSE.
The configuration of NSEI should be consistent with the data configuration at the PCU side.
6-8
68P02904W52-B 31-Jan-2005
Configuring Protocol Parameters

The setting of protocol parameters may have serious impact upon the system. It is recommended to adopt system default values. You should kwow the case without a doubt before making a modification to the parameter configuration.
It includes configuration of parameters of various protocol layers (NS, BSSGP and SNDCP) and Gb general information.
Description
Preset conditions
None.
Data preparation
None.
Procedure
Step * * * * * Operation Configure NS. Configure BSSGP. Configure flow control switch. Configure SNDCP. Configure GB. SET NS SET BSSGP SET FLOWCTRL SET SNDCP SET GB Command
Example
Set NS parameters, so that the number of NSVCs per board can be 250. SET NS:NSVCNUM=250;
68P02904W52-B 31-Jan-2005
6-9
Reference
The protocol stack of the Gb interface is composed of SNDCP, LLC, BSSGP, NS and FR. The location of the protocol stack of the Gb interface at the GPRS user plane is shown in Figure 6-3. Figure 6-3
Application IP Relay SNDCP SNDCP LLC Relay RLC RLC MAC GSM RF Um BSSGP Network Service L1bis Gb BSSGP IP Network Service L1bis L2 L1 Gn IP L2 L1 Gi LLC UDP UDP GTP-U GTP-U IP
Gb protocol stack at the user plane.
MAC GSM RF
MS
BSS
SGSN
GGSN
At the user plane, SNDCP, LLC, BSSGP and NS cooperate in transmitting N-PDU from GTP-U to BSS/MS or transmitting data from BSS/MS to GTP-U. The Gb protocol stack at the control plane is shown in Figure 6-4. LLC, BSSGP and NS provide transparent and unacknowledged signaling transmission channel for GMM/SM. Figure 6-4
GMM/SM LLC
Relay
Gb protocol stack at the control plane.

GMM/SM LLC RLC MAC BSSGP BSSGP Network Service L1bis Gb
RLC MAC GSM RF
Network Service GSM RF L1bis Um
MS
BSS
2G-SGSN
SNDCP
SubNetwork Dependent Convergence Protocol (SNDCP) controls the creation and release of the link under the instruction of SM. It provides a uniform interface for various PDPs at the upper layer and permits PDPs of different types to be introduced to the upper layer. It also provides the upper layer with acknowledged and unacknowledged data transmission services. Major functions of the SNDCP protocol layer include:
6-10
68P02904W52-B 31-Jan-2005
Multiplexing of multiple PDP activations; Mapping multiple network layer entities to the appropriate LLC connections through the N-PDU multiplexing; Providing the transmission of user data in the acknowledged and unacknowledged mode; Providing caching for N-PDUs in acknowledged mode until the acknowledgement from the opposite side is received; Managing the transmission sequence of each NSAPI independently; Providing compression and decompression functions for the user data; Providing compression and decompression functions for the subscriber protocol control information; Segmenting N-PDU to several LL-PDUs and re-assembling multiple LL-PDUs belonging to the same packet to N-PDU; Providing the XID parameter negotiation between peer SNDCP entities at the network side and the mobile subscriber side; Performing inter-SGSN routing updating in cooperation with GMM, GTP-U and SM; Accomplishing handover from 2.5G to 3G in cooperation with GMM, GTP-U and SM; Creating, re-creating and releasing the acknowledged LLC operation.
The above segmentation and reassembly function is independent of the network layer protocol used.
LLC
Logical Link Control (LLC) provides logical links between SGSN and MS. It encapsulates the data or signaling messages of GMM/SMS/SNDCP to LL-PDU and transmit it to LLC at the subscriber side. The logical link of LLC does not correspond to any direct physical connection. Instead, it transmits LL-PDU to BSS through the Gb interface (BSSGP, NS, FR). Then, BSS transmits LL-PDU to MS or in the opposite direction the MS transmits it to SGSN. LLC shields the transmission details of the bottom layer from the upper layer. The LLC protocol layer provides the following major functions:
68P02904W52-B 31-Jan-2005
6-11
Point-to-point data transmission link in acknowledged mode between MS and SGSN; Point-to-point data transmission link in unacknowledged mode between MS and SGSN; LLC PDU framing, de-framing and CRC check function; XID parameter negotiation function; Private transmission of user data by means of encryption; Logical link control functions; Error recovery and report.
BSSGP
At SGSN, the Base Station Subsystem GPRS Protocol (BSSGP) layer is located between LLC and the Network System (NS) of the Gb protocol stack. It provides channels for the data and signaling transmission between BSS and SGSN. Major functions of the BSSGP protocol layer include: In the downlink direction, the BSSGP at the SGSN side provides BSS with relevant radio information needed by RLC/MAC; In the uplink direction, the BSSGP at the BSS side transmits relevant radio information provided by RLC/MAC to the network; It provides node management between SGSN and BSS; It provides transmission for uplink/downlink data; It provides transmission for signaling messages; It provides the upper layer data with the flow control function in the downlink direction; It provides BVC status management; It provides MS status management.
NS
The Network System (NS) protocol layer provides the upper layer with the PVC data link and transparent data transmission in the load-sharing mode. The NS layer includes the NS control sublayer and the FR sublayer. NS control sublayer is located between BSSGP and FR in the Gb protocol stack. It provides unacknowledged data transmission for the upper layer. Major functions of the NS control sublayer include:
6-12
68P02904W52-B 31-Jan-2005
Providing unacknowledged data transmission between BSS and SGSN for the upper layer through the PVC provided by FR; Providing link congestion indication for the upper layer through congestion report mechanism of FR; Providing the upper layer with status indication such as the change of link transmission capability; Providing load sharing on valid PVCs. Compared with common frame relays, the FR sublayer has simpler functions, including:
LMI function; Transmission and reception of the FR frame; Congestion statistics report.
68P02904W52-B 31-Jan-2005
6-13
Configuring Cell Reference Parameters

This part presents instructions to configure cell reference parameters. Upon the completion of the configuration, SGSN can establish cells on the UGBI boards recommended.
Description
Preset conditions
None.
Data preparation
Item Basic information. UGBI subrack number, slot number. Cell ID. Data
Procedure
Step 1 Operation Add cell reference parameter. Command ADD CELLREF
Example
;; Add cell reference parameter ADD CELLREF: CELLID="460008613900002", CELLFN=0, CELLSN=5;
6-14
68P02904W52-B 31-Jan-2005
Reference
The cell configuration is made at the BSS side and no special cell configuration is needed at the SGSN side. After a cell has been configured at the BSS side, the cell information synchronization will be completed at the SGSN side automatically. Cells at the SGSN side will be evenly distributed on as many UGBI boards as possible to meet the requirement for load sharing. The cells at the SGSN side can be distributed as recommended through the data configuration. Moreover, the existing cells can be deleted and the configuration of the UGBI board accommodating the cell can also be modified accordingly. The cell configuration parameter reveals the advice on the cell distribution of the user. The system will determine whether to use the cell distribution advised by the user based on the actual running situation.
68P02904W52-B 31-Jan-2005
6-15
6-16
68P02904W52-B 31-Jan-2005
Chapter
MM Configuration

68P02904W52-B 31-Jan-2005
7-1
MM Configuration Overview
MM Configuration Overview

Mobility Management (MM) configuration in Motorola C-SGSN refers to the configurations for the following procedures and timers: Attach. Detach. RAU. Relocation. Inter-system Change. Security Management. Motorola C-SGSN supports both GMM (2.5G) and PMM (3G). GMM stands for the GPRS mobility management in the GSM and PMM for the packet mobility management in the UMTS system. This section introduces configuration for GMM and PMM parameters. There is no restriction to the configuration sequence.
7-2
68P02904W52-B 31-Jan-2005
Configuring Authentication and Ciphering Parameters

This section introduces the configuration for authentication and ciphering parameters. The authentication and ciphering procedures will function based on the preset parameters after this configuration.
Description
Preset conditions
None.
Data preparations
None.
Procedure
Step 1 2 3 Operation Modify authentication and ciphering parameters (2G). Modify authentication and ciphering parameters (3G). Mod Authentication Failure Table. SET GMM SET PMM SET AUTHFAIL Command
Example
;;Modify the GMM parameter PTMSIREALLOC to NO. SET GMM: PTMSIREALLOC=NO;
68P02904W52-B 31-Jan-2005
7-3
Reference
Authentication
The SGSN initiates the 'GSM authentication'. It implies authentication of the MS by the network and establishment of a new GSM ciphering key (Kc) agreement between the SGSN and an MS. The SGSN initiates the 'UMTS authentication'. It implies mutual authentication, that is, the authentication of an MS by the network and the authentication of the network by the MS. It also implies establishment of a new UMTS ciphering key (CK) and integrity key (IK) agreement between the SGSN and the MS. Different service and network providers have different requirements for network security. Therefore, SGSN can specify whether to enable authentication or ciphering during a procedure based on user configurations. For example, you can enable authentication during INTRA RAU procedure. SGSN provides an authentication and ciphering controlled global switch. The authentication and ciphering parameters configured are available only when this switch is set to on. If the switch is set to off, no authentication or ciphering procedure will start.
Ciphering
Figure 7-1 shows the scope of ciphering. Figure 7-1 Scope of ciphering.
MS
BSS/UTRAN
SGSN Scope of GPRS ciphering Scope of UMTS ciphering
As shown in Figure 7-1, the scope of UMTS ciphering is narrower than that of GPRS ciphering. It is only from the ciphering function in the UTRAN to the ciphering function in the MS. If you enable the ciphering function, you need configure the SGSN-supported ciphering algorithms. The algorithms include GEA_1(2.5G),GEA_2 (2.5G), NO_ENCRYPTION (3G) and UEA1 (3G).
IMEI check
If an EIR exists in the network, SGSN can perform IMEI check and decide whether the involved MS can be accessed to the system based on the check result.
P-TMSI
Usually the network does not directly use an IMSI but uses a P-TMSI allocated by the SGSN as a temporary MS identity between the MS and the SGSN. The reallocation procedure guarantees the randomness of the temporary identity. This avoids the leakage of the user identity. You may specify whether to start P-TMSI reallocation.
7-4
68P02904W52-B 31-Jan-2005
Authentication failure configuration

Authentication failure configuration includes the configuration of two parameters, CAFTIMES and PURPERIOD (UserPurgePeriod). If the number of subscriber authentication failures exceeds the value of CAFTIMES during a user purge period, the system will generate an alarm. If the number of subscriber authentication failures donot exceed the value of CAFTIMES during a user purge period, the subscriber authentication failure records will be purged when the next user purge period starts.
68P02904W52-B 31-Jan-2005
7-5
Configuring Timers
Configuring Timers

Timer settings might severely effect system functions. Therefore, modify the timer configurations with care. Normally you may adopt the default timer settings of the system.
This section introduces the configuration for MM dependent timers. The preset timers will affect MM procedures.
Description
Preset Conditions
None.
Data preparations
None.
Procedure
Step 1 2 3 Operation Modify the subscriber database timer. Modify the GMM timer (2.5G). Modify the PMM timer (3G). Command SET SDBTMR SET GMMTMR SET PMMTMR
Example
;;Modify the PMM timer length to 40. SET PMMTMR: PRDTMR=40;
7-6
68P02904W52-B 31-Jan-2005
Configuring Timers
Reference
Functionally, MM timers can be divided into two types. The first type of MM timers can be called message timers. They define the time for the SGSN to wait for a signaling response message. The SGSN will resend the request or terminate the ongoing procedure if it has not received the response message from the peer end within the defined time. These timers include: Detach Req Retrans Timer (T3322). Message Retrans Timer (T3350). Auth-req Retrans Timer (T3360). Identity Req Retrans Timer (T3370). Paging Response Timer (T3313). Reloc Res alloc timer. Old SGSN RelocCmpTimer. New SGSN RelocCmpTimer. The second type of MM timers can be called behavior timers. If such a timer expires, SGSN or the MS must start the corresponding procedure. These timers include Period-RAU Timer, MS reachable Timer and PTMSI Realloc Timer. These timers are usually dependent on the service and network providers and their values might be adjusted according to the actual situations. For the details about the preceding timers see 3GPP 24.008. Subscriber Databases (SDBs) of Motorola C-SGSN are used to store MS's subscription data and dynamic data. The Subscriber Index Processing Unit (SIPU) on URCU0 is used to record on which USPU the subscription data is stored. To reduce signaling exchanges with HLR, the MS subscription data will not be deleted from SDB immediately after an MS has been detached. Instead, the data will be kept for a period of time. If a super-charger is supported by the system, and is also supported in MS's subscription data, its subscription data will be sustained after MS detachment so long as the SDB Table is not full. SDB timer configuration refers to the configuration parameters such as 'Purge Ms Timer Length', 'Check Time On SIPU' and 'Check Time On USPU'. The initial values for these parameters have been set during system initialization. Generally, they do not need modification.
68P02904W52-B 31-Jan-2005
7-7
Configuring PLMN
Configuring PLMN

This section introduces the configurations for HPLMN, peer PLMN and connected PLMN. The subscribers in the HPLMN or the connected PLMN can be attached to this SGSN or the peer PLMN after the configurations.
Description
Preset Conditions
None.
Data preparations
Item Basic information. MCC and MNC of HPLMN. Data MCC and MNC of peer PLMN. MCC and MNC of connected PLMN.
Procedure
Step 1 2 3 Operation Add a HPLMN. Add a connected PLMN. Add a peer PLMN. Command ADD HPLMN ADD CONNECTPLMN ADD PEERPLMN
Example
;;Add a connected PLMN. ADD CONNECTPLMN: MCC="460", MNC="00", CC="86";
Reference
Motorola C-SGSN can support multiple HPLMNs. That is, multiple PLMNs share a SGSN. You may use MOD SYS or SET OFI to configure the HPLMN supported by the system by default and use ADD HPLMN to configure other HPLMN.
7-8
68P02904W52-B 31-Jan-2005
Configuring PLMN
A connected PLMN refers to the PLMN that has subscribed roaming protocols with the HPLMN of the SGSN. When an MS belonging to the connected PLMN roams to local SGSN, SGSN can define whether to allow the MS access so that the MS can share the corresponding services. The peer PLMN refers to a PLMN it provides the same function as that of HPLMN when an MS selects a network. Generally, the serving areas of the peer PLMN and those of the HPLMN are the same or overlap. When an MS is attached to the HPLMN, SGSN will send the peer PLMN to the MS. In the next selection of PLMN, the MS can detect the peer HPLMN and select it or the HPLMN.
68P02904W52-B 31-Jan-2005
7-9
Configuring Paging Parameters

You shall also configure the mapping relation between an NRA and RNC.
This section introduces the configuration for 2.5 G and 3G paging parameters. SGSN can start PS paging or CS paging after this configuration.
Description
Preset Conditions
The Iu interface configuration has finished.
Data preparations
Item Basic information. LAI of the null routing area. RAC of the null routing area. Data RAI-RNC mapping relation.
Procedure
Step 1 2 Operation Add null routing area. Add 3G Paging Table. ADD NRA ADD 3GPAGING Command
Step 2 is mandatory in 3G network only.
7-10
68P02904W52-B 31-Jan-2005
Example
;;Add a null routing area. ADD NRA: LAI="460002233", RAC="01"; ;;Add 3G Paging Table. ADD 3GPAGING:LAI="460000001",RAC="01",RNCINDEX=0;
Reference
The Null RA Table is mainly used in the Circuit-Switched (CS) paging procedures of 2.5G/3G MS. A Null routing Area (NA) in SGSN is a group of cells in a location area that does not support GPRS service. The coding scheme of a null RA is the same as that of a common RA. Under the same LAI, there should be only one null RA. In the 2.5G network, when an MS is both IMSI and GPRS-attached in a network that operates in mode I, then the MTS-U/VLR executes paging for circuit-switched services using the SGSN. If the MS is in STANDBY state, then it is paged in the routing area and in the null routing area. In the 3G network, the SGSN need to send paging to the RNC where the routing area is located. Therefore, you need to configure the mapping relation between the RAI and RNC.
68P02904W52-B 31-Jan-2005
7-11
7-12
68P02904W52-B 31-Jan-2005
Chapter
SM Configuration

68P02904W52-B 31-Jan-2005
8-1
SM Configuration Overview
SM Configuration Overview

Session Management (SM) configuration includes the configuration for SM parameters, mapping relations between PDP type and Access Point Name Network Identifier (APN NI) and Shared Public Land Mobile Network Operator Identifier (PLMN OI) list. There is no sequence restriction to the configurations.
8-2
68P02904W52-B 31-Jan-2005
Configuring SM Parameters

This section introduces the configuration for SM parameters, including optional functions, timers and QoS. The system can normally perform session management according to the configuration.
Description
Preset conditions
The MM configuration has finished.
Data preparations
None.
Procedure
Step 1 2 Operation Modify 2G SM protocol parameter. Modify 3G SM protocol parameter. Command SET 2GSM SET 3GSM
Example
;;Modify the preservation procedure enable indicator to YES. SET 2GSM: PPU=YES;
Reference
To specify 'Security in SM enable', you shall set 'Enable all auth and ciph' to on when configuring MM parameters.
68P02904W52-B 31-Jan-2005
8-3
Session Management (SM) performs tunnel creation, modification and release between SGSN and GGSN. The session management of 3G SGSN also controls the creation, modification and release of the Radio Access Bearer (RAB) between SGSN and RNC/MS.
Optional functions in SM
You may specify whether to enable some functions in the SM procedures by configuring the corresponding parameters. These parameters include 'Security in SM enable', 'PFT enable' and 'Preservation procedure enable'.
SM timers
Functionally, the SM timers can be divided into two types. The first type of SM timers can be called message timers. They define the time for the SGSN to wait for a signaling response message. The SGSN will resend the request or terminate the ongoing procedure if it has not received the response message from the peer end within the timer-defined time. These timers include: Network-initiated activation timer (T3385). Network-initiated modification timer (T3386 ). Network-initiated deactivation timer (T3395). Timer defining the time limit for SM to query DNS. Timer defining the time limit for SM to wait for GTP-C version detection. Timer defining the time limit of RAB assignment procedure. The second type of SM timers can be called behavior timers, for example, the timer defining the time limit for BSS to store BSS packet context. If such a timer expires, the network node must start the corresponding procedure. These timers are dependent on the service and network providers and their values might be adjusted according to the actual situations. For the details about the preceding timers see the online help of MOD SM command.
QoS
While creating the packet transmission route, the session management procedure should also specify the QoS for this route. A QoS negotiation will be performed among MS, RNC, SGSN and GGSN during the session management process so that the QoS provided by various nodes can be consistent with each other. You may either define the maximum QoS that can be provided by SGSN or use its default value.
8-4
68P02904W52-B 31-Jan-2005
RAB QoS negotiation

When establishing an RAB through negotiations with an RNC, the SGSN supports two QoS negotiation modes. In mode 1, the SGSN specifies a percentage between an available bit rate and the first bit rate for an RAB. If it cannot provide the first bit rate, the RNC will attempt to use the available bit rate (the percentage x the first bit rate) to create an RAB. If the attempt fails, the RNC will return a failure message. Note that both the SGSN and RNC shall support protocol R4 in this mode. In mode 2, the SGSN negotiates the QoS with the RNC in descending order of bit rate. The possible bit rates are in a negotiated bit rate list. If the RNC does not support the MS requested bit rate, the SGSN will select the bit rate of lower based on the settings in the negotiated bit rate list to re-negotiate with the RNC until an RAB is successfully set up or the RNC fails to support the rate of the lowest priority.
APN resolution
Access Point Name (APN) is a logical name referring to the external packet data network and/or to a service that the subscriber is to access. It consists two parts: APN Network Identifier (NI) and APN Operator Identifier (OI). APN resolution is the procedure of translating the APN into the IP address of the GGSN. An MS can use multiple PDP addresses and APNs. To activate a session, the PDP address and APN required by the MS should meet the requirements of the subscription data. You may use MOD SM to set the HPLMN OI of the SGSN. When an MS initiates a PDP context activation request, the SGSN can adopt the preset OI to resolute the GGSN if necessary.
68P02904W52-B 31-Jan-2005
8-5
Configuring Mapping between PDP Type and APN NI

This section introduces the configuration for the mapping relations between PDP types and APN NI. After the configuration, the SGSN can retrieve the corresponding APN NI based on the PDP type.
Description
Preset conditions
None.
Data preparations
Item Basic information. PDP type. APNNI Data
Procedure
Step 1 Operation Add the mapping relation between a PDP TYPE and an APN NI. Command ADD PDPAPN
Example
Add an APN "169.net" that supports IPV4. ADD PDPAPN: PDPT=PT_IPV4, APNNI="169.net";
Reference
Mapping relation between PDP TYPE and APN NI Table shows the APN NI supported by the PDP TYPE. The possible PDP types are IPv4, IPv6 and PPP. Each PDP type corresponds to only one APN NI. When the subscriber initiates the following two kinds of PDP context activation requests, the Mapping relationship between PDP TYPE and APN NI Table will be used to find the corresponding APN:
8-6
68P02904W52-B 31-Jan-2005
1. 2.
The activation request carries no PDP address or APN and there is only one set of subscribed data with APN '*'; The activation request carries the PDP type and there is only one set of subscribed data matching with this PDP type. Moreover, the subscribed APN is '*'.
68P02904W52-B 31-Jan-2005
8-7
Configuring Shared PLMN OI
Configuring Shared PLMN OI

This section introduces the configuration for a shared PLMN OI. After the configuration, the SGSN can query the GGSN based on the shared PLMN OI during MS's PDP context activation.
Description
Preset conditions
The configuration for the shared PLMN has finished.
Data preparations
Item Basic information. GGSN IP Data
Procedure
Step 1 Operation Add a shared PLMN OI. Command ADD SHAREPLMNOI
Example
;;Add a shared PLMN OI "MNC007.MCC460.gprs". ADD SHAREPLMNOI: SPO=" MNC007.MCC460.gprs ";
Reference
The shared PLMN OI is used only in the PDP context activation of a roaming MS. 1. If the activation request from the roaming MS does not carry APN OI and the VPLMN OI is allowed in the subscription data, the SGSN will initiate DNS resolution using the APN based on the VPLMN OI, shared PLMN OI or HPLMN OI in order of precedence (it tries the APN based on the VPLMN OI first) If the activation request from the roaming MS carries an APN OI and the VPLMN OI is allowed in the subscription data, the carried APN OI might be the VPLMNM OI or shared PLMN OI. 68P02904W52-B 31-Jan-2005
2.
8-8
Configuring IP Address of GGSN supporting MIP or DHCP

This section introduces the configuration for IP Address of GGSN supporting MIP or DHCP, the SGSN can query the GGSN supporting MIP or DHCP while the APN name is 'MIPv4FA' or 'dhcp'.
Description
Preset conditions
None.
Data preparations
None.
Procedure
Step 1 2 Operation Add IP address of GGSN that supports MIPv4 service. Add IP address of GGSN that supports DHCP service. Command ADD MIPGIP ADD DHCPGIP
Example
;;Add IP address of GGSN that supports MIPv4 service. ADD MIPGIP: IP="191.22.33.171"; ;;Add IP address of GGSN that supports DHCP service. ADD DHCPGIP: IP="191.22.33.172";
68P02904W52-B 31-Jan-2005
8-9
Reference
When External PDN Address Allocation is used, it is the responsibility of the MS and the PDN to allocate and release the dynamic PDP address by means of protocols such as DHCP or MIP. In case of DHCP, the GGSN provides the function of a DHCP Relay Agent as defined in RFC 2131 '47' and RFC 1542 '45'. In case of MIP, the GGSN provides the function of a Foreign Agent as defined in RFC 2002 '46'. If the APN carried in the PDP context activation request from an MS is 'MIPv4FA' or 'DHCP', the SGSN need not initiate DNS parse on the APN. Instead, it shall query the configuration information to obtain the IP address of the GGSN that supports MIPv4 or DHCP service.
8-10
68P02904W52-B 31-Jan-2005
Chapter
Service Configuration

68P02904W52-B 31-Jan-2005
9-1
Configuring SMS
Configuring SMS

This section describes the Short Message Service (SMS) protocol parameters configuration for the SGSN to process short message services. Generally, you need not perform the configuration.
Description
Preset conditions
None
Data preparations
None
Procedure
Step 1 Operation Modify the SMS protocol configuration list. SET SMS Command
Example
None
Reference
If SM-MT or SM-MO setting requires authentication, it is necessary to turn on the Encryption and Authentication switch when configuring mobile management parameters.
9-2
68P02904W52-B 31-Jan-2005
Configuring SMS
SMS is a basic telecommunication service. It provides short message receiving/transmitting services for subscribers. These services include Short Message Mobile Originated (SMMO), Short Message Mobile Terminated (SMMT), and Short Message Alert (SM Alert). The SMS function requires the coorperation of multiple entities, as shown in Figure 9-1. Figure 9-1
MS
SMS network architecture.

Um Gb Gd
BSS
Iu Uu
SGSN
Gr
SMS-GMSC SMS-IWMSC
SM-SC
UE
UTRAN
HLR
In Figure 9-1, the Gb interface or Iu interface and the Gd interface are responsible for forwarding short messages. The C interface provides routing function for the MS to receive short messages. The Gr interface performs SM alert and SM authentication functions. There are four types of SMS parameters: QoS index, maximum number of repeated transmission times, flow switch and timer length.
68P02904W52-B 31-Jan-2005
9-3
Configuring CAMEL service

This section describes the CAMEL Service configuration for SGSN to process intelligent network services.
Description
Preset conditions
During the MAP configuration (by carrying out SET MAPFUNC), the CAMEL versions supported by the SGSN have been set correctly.
Data preparations
None
Procedure
Step 1 2 Operation Modify the CAMEL-supporting mode. Add the IMSI/MSISDN number segment used to trigger CAMEL GPRS services. Add the IMSI/SMS MSISDN number segment used to trigger CAMEL SMS services. Modify the CAMEL timer. Command SET CAMELSPT ADD IMSILIST/ADD MSISDNLIST ADD IMSILIST/ADD MSISDNLIST SET CAMELTMR
You may skip Steps 1-3 if you do not use number segment to trigger CAMEL services. Step 2 is for the number segment to trigger CAMEL GPRS services. Step 3 is for the number segment to trigger CAMEL SMS services.
9-4
68P02904W52-B 31-Jan-2005
Example
;; Modify the CAMEL-supporting mode. SET CAMELSPT: SUPGPRS=SUPPORT, SUPMODGPRS=IMSI, SUPSMS=SUPPORT, SUPMODSMS=IMSI; ;; Add an IMSI number segment. ADD IMSILIST: BEGIMSI="460001021432170", ENDIMSI="460001021432179", TDP1=ATTACH, SRVKEY1=1, SCPADD1="861390218888", DFTHDL1=CONTINUE; ;; Add a SMS IMSI number segment. ADD SMSIMSILIST: BEGIMSI="460001021432170", ENDIMSI="460001021432179", TDP=SMTS-UOLLECTEDINFO, SRVKEY=1, SCPADD="861390218888", DFTHDL=CONTINUE;
Reference
The SGSN supports the CAMEL 3 characteristic.
CAMEL Services
SGSN supports CAMEL GPRS services and CAMEL SMS services. CAMEL GPRS services: gsMTS-UF in SGSN controls CAMEL subscribers access and CAMEL PDP conversations. SGSN supports access of 2.5G CAMEL subscribers and 3G CAMEL subscribers. CAMEL SMS services: gsMTS-UF controls short message transmission of SGSN.
CAMEL trigger mode

There are two trigger modes of CAMEL services: CSI trigger mode and number segment trigger mode. In the former mode, the subscription information of the CAMEL subscriber contains CAMEL-related information. The SGSN processes the CAMEL subscriber according to the subscription information provided by HLR. In the latter mode, the subscription information of the CAMEL subscriber does not contain CAMEL-related information. The SGSN checks whether the subscriber is a CAMEL subscriber based on the MSISDN or IMSI number segment and processes it correspondingly according to the data configuration of the local office. In the latter mode, you need configure the information including the CAMEL trigger point, service key, default processing and SCP.
Camel timer
The SGSN has set initial values to each CAMEL timer during initialization. Generally, you can skip the modification. Otherwise, you may carry out SET INSMTMR to modify the timer.
68P02904W52-B 31-Jan-2005
9-5
Configuring LCS
Configuring LCS

If LCS setting requires authentication, it is necessary to turn on the Encryption and Authentication switch when configuring mobile management parameters.
This section describes the LoCation Service (LCS) configuration for SGSN to process location services.
Description
Preset conditions
None
Data preparations
None
9-6
68P02904W52-B 31-Jan-2005
Configuring LCS
Procedure
Step 1 2 3 4 5 6 Operation Configure the LCS parameter list. Configure the mapping relations between SAI and the geographic coordinate. Configure the mapping relations between CELLID and the geographic coordinate. Configure the mapping relations between addresses of the SGSN control plane and SGSN numbers. Configure the mapping relations between LCS Client and its home GMLC number. Configure a GMLC in HPLMN. Command SET LCSPARA ADD SAIGEO ADD CELLGEO ADD SGSNIPNUM ADD GMLCCLIENT ADD GMLCINHPLMN
Example
;; Modify the LCS Privacy Verify Timer to 30,000 ms, the LCS Location Report Timer to 25,000 ms, the GMLC Response Timer to 25,000 ms and the MOLR Continue Timer to 15,000 ms. LCS does not require verification. GMLC is not specified belonging to HPLMN. SET LCSPARA: TR1=30000, TR2=25000, TR3=25000, TR4=15000, AUTH=NO_AUTH, GLHP=NO_LIM; ;; The position of Service Area 4600907551234 is latitude 515'25" north and longitude 3545'55" west, radius of service area is 35000 m. ADD SAIGEO: SAI="4600907551234", LAT=NORTH_LATITUDE, LAD=5, LAM=15, LAS=25, LOT=WEST_LONGITUDE, LOD=35, LOM=45, LOS=55,RAD=35000; ;; Add a GMLC in HPLMN with the ID to be 861390123456789 to this SGSN. ADD GMLCINHPLMN: GMLCNUM="861390123456789"; ;; The position of Cell 460008613900001 is latitude 515'25" north and longitude 3545'55" west,radius of cell is 5500 m. ADD CELLGEO: CELLID="460008613900001", LAT=NORTH_LATITUDE, LAD=5, LAM=15, LAS=25, LOT=WEST_LONGITUDE, LOD=35, LOM=45, LOS=55, RAD=5500; ;; The LCS Client number is 861391234567890 and its home GMLC number is 861390123456789. ADD GMLCCLIENT: CLIENTNUM="861391234567890", GMLCNUM="861390123456789"; ;;Add the mapping relation between IP address of SGSN control plane and SGSN number, with IP address of SGSN control plane of 191.22.37.101, and SGSN number of 861390123456789: ADD SGSNIPNUM: SGSNIP="191.22.37.101", SGSNNUM="861390123456789";
68P02904W52-B 31-Jan-2005
9-7
Configuring LCS
Reference
LCS refers to the procedures related to UE location request, location measurement and calculation, and location result transmission performed by the mobile telecommunications system. The procedures include the PS_MO_LR procedure, PS_MT_LR procedure, and PS_NI_LR procedure. After obtaining the location information of UE, the system can provide various services based on the information. These services include on-demand services, information customization and service customization. LCS is applicable to many services such as the commercial location service (value-added service), internal location service, emergency location service and lawful interception service. In the network structure of 3GPP releases, LCS is a relatively independent system affiliated to the core network, as shown in Figure 9-2. Figure 9-2 LCS network structure.
Gb
HLR 2G-SGSN
Lg Lh
GERAN UE
Um
GMLC
Lg Uu
Le
External LCS Client
UTRAN
Iu
3G-SGSN
External LCS Client is the application server for the location-based services. It has a connection with GMLC through the Le interface. External LCS Client initiates location requests, and utilizes the location results to implement location-based services. Gateway Mobile Location Center (GMLC) is the gateway equipment connected to the external LCS Client. After obtaining a location request message through Le interface, GMLC performs addressing to HLR through Lh interface. After that, it initiates a location request to VMTS or SGSN through Lg interface. Finally, it returns the location result to the External LCS Client through Le interface. LCS Server consists of CN equipment, access network and GMLC. It can respond to location requests. CN equipment includes SGSN, HLR and MTS-U/VLR. They implement UE addressing, location message transmitting, and management of subscriber information storage. RNC performs the location measurement and calculation function of the LCS system.
LCS parameters
The LCS parameter list defines the lengths of various LCS timers. It also defines whether to authenticate the LCS procedure and whether to limit GLMC in HPLMN. The SGSN has set initial values to each LCS timer during initialization. Generally, you may skip the modification.
Location calculation
In 2.5G, the SGSN locates a subscriber in the geographic coordinate according to the cell ID. In 3G, the SGSN locates a subscriber in the geographic coordinate according to SAI.
9-8
68P02904W52-B 31-Jan-2005
Configuring LCS
Because of inaccuracy in locating, there is difference between the actual position of a subscriber and the obtained position in the geographic coordinate. The difference depends on the radius of the cell or the service area.
Mapping relations between GMLC and LCS CLIENT

In the MO location service, the SGSN queries the mapping relation table of GMLC and LCS CLIENT according to the LCS CLIENT information in the information sent by a MS to obtain the corresponding GMLC. If it is set in the LCS software parameter configuration that the GMLC belongs to HPLMN, the SGSN will judge whether the GMLC number involved with the procedure is the GMLC number configured in HPLMN. If not, the SGSN will refuse to perform LCS.
Delayed location
There are two types of LCS: instant location services and delayed location services. The instant location service means that subscribers can obtain their location information instantly if they attach the SGSN. The delayed location service means that if subscribers do not attach the SGSN, the SGSN will report their location information when they attach the SGSN. In the course of delayed location, when a subscriber attaches another SGSN, it is necessary to get the SGSN number as per the corresponding IP address, and forwards the SGSN number to GMLC by the message from SGSM to GMLC. Upon receipt of the SGSN number, the GMLC originates a location procedure to the SGSN to which the subscriber attaches. If there is no configuration for mapping relation between IP address of SGSN control plane and SGSN number, the message reported by SGSN to GMLC will not contain SGSN number. Therefore, GMLC must request HLR for the corresponding SGSN number before originating a location procedure to the SGSN to which the subscriber attaches.
68P02904W52-B 31-Jan-2005
9-9
Configuring LCS
9-10
68P02904W52-B 31-Jan-2005
10
Charging Configuration

Chapter
68P02904W52-B 31-Jan-2005
10-1
Charging Configuration Overview
Charging Configuration Overview

The charging configuration includes the Ga interface software parameter configuration, CG and route configuration, charging characteristic configuration, CDR format configuration, charging behavior configuration and special charging rate period. You should follow the above sequence to implement the configuration.
10-2
68P02904W52-B 31-Jan-2005
Configuring Ga Interface Parameters

This section introduces the configuration of the Ga interface parameters. SGSN will work according to the configured parameters.
Description
Preset Conditions
None
Data Preparations
None
Procedure
Step 1 Operation Configure the Ga interface parameters. Command SET CHGGA
Example
;;Modify the Ga interface parameters SET CHGGA: GCR=R99, UCR=R4, CHGVER99=GPP32015V3A0;
Reference
CDR protocol version
SGSN currently supports the following CDR versions: 2G supports R98, R99, R4. 3G supports R99, R4. R98 supports GSM 12.15 V7.6.0 and China Mobile CG specification V1.3.0. R99 supports 3GPP 32.015 V3.6.0 and 3GPP 32.015 V3.a.0. R4 supports 3GPP 32.215 V4.4.0.
68P02904W52-B 31-Jan-2005
10-3
CDR resending parameters

If there is no response from the CG after the CDR is sent, SGSN can resend the CDR. The operator can set the number of resending times and the time to wait for the response. Usually it is not necessary to modify the initial settings provided by the system.
Hard disk alarm parameters

When the communication between CG and SGSN is interrupted, SGSN will temporarily save the CDR to the UBSU hard disk. When the communication is resumed, SGSN will resend the CDR. To manage the hard disk, the operator can set the hard disk alarm parameters, including the read/write error alarm threshold and the hard disk space-lack alarm threshold.
10-4
68P02904W52-B 31-Jan-2005
Configuring CG and Route between SGSN and CG

This section introduces the configuration of CG as well as the route between SGSN and CG. After the configuration, SGSN can communicate with the CG normally.
Description
Preset conditions
None
Data preparations
Item Basic information of CG. Route information. IP address. Priority. Data UDP receiving port number. ULPI interface IP address UDP sending port number. Ga port route planning TCP listen port number. Protocol release supported
UCDR subrack number, slot number.
UHPU subrack number slot number, forwarding engine number
68P02904W52-B 31-Jan-2005
10-5
Procedure
Step 1 2 3 (Optional). 4 5 Operation Configure CG information. Configure the IPoA PVC between UCDR and UHPU. Configure the ULPI port backup relation. Configure the IP of ULPI port. Add the SGSN-to-CG IP route. Command ADD CHGCG ADD SGSN_IP_IPOA_PVC ADD BNET_NETWORK_BACKUP ADD BNET_GFI_IF_IP ADD BNET_IP_ROUTE
Example
Figure 10-1
Ga interface network example.

IPOA PSM U R C U U C D R U C D R
BNET FEA:10.21.40.37 FEB:10.21.41.37
U L P U
U L P I
U N E T
U H P U
10.88.40.13
192.5.5.1 192.5.5.5 ROUTER 192.22.88.253 CG:192.22.88.15
LAN Switch
Figure 10-1 shows the system network. The UCDR is located in Subrack 0, Slot 10. The UHPU is located in Subrack 2, Slot 9 and uses forwarding engine 0.The ULPI is located in Subrack 2, Slot 5 and uses Port 0. ;;Configure CG ADD CHGCG: IP="192.22.88.15", GRD=0, PRO=UDP, SPN=3386, RPN=3386, CGR=R98; ;;Configure the IPoA PVC between UCDR and UHPU
10-6
68P02904W52-B 31-Jan-2005
ADD SGSN_IP_IPOA_PVC: FN=0, SN=10, HSN=9, HSSN=0; ;;Configure the port IP of ULPI ADD BNET_GFI_IF_IP: SN=5, SSN=0 ,PN=0, IP="192.5.5.1", MSK="255.255.255.0"; ;;Configure the SGSN-to-CG IP route ADD BNET_IP_ROUTE: IP="192.22.88.0", MSK="255.255.255.0", GATE="192.5.5.5", PRE=0;
Reference
CG
The CG information includes the IP address, priority, GTP' bearing protocol and CG protocol version. For CG with GTP' bearing protocol as UDP, the configuration information includes the sending port number and the receiving port number For CG with GTP' bearing protocol as TCP, the configuration information includes the TCP listen port number You can connect one SGSN to maximum 10 CGs. The records of CG Information Table should comply with the configuration regulations as follows: 1. 2. 3. For CG with GTP' bearing protocol as UDP, the IP address (IP), Sending Port Number (SPN) and Receiving Port Number (RPN) of a CG identify a unique record. For CG with GTP' bearing protocol as TCP, the IP address and TCP listen port of a CG identify a unique record. The CGs with the same IP address cannot share the same SPN, RPN and TCPPORT. If the 2.5G CDRs and 3G CDRs are sent to the same CG, it is necessary to configure two CG records with the same IP but different ports. If the setting of the protocol release of the CG is incorrect, the CG cannot browse and combine the bills sent from the GSN although the communication between them is normal.
4.
When one SGSN is connected with multiple CGs, the CDR sending is based on the following principles in sequence: 1. 2. 3. 4. 5. Send CDRs to the CG addresses specified by the charging behavior (See the charging behavior configuration). Send CDRs to the CG addresses specified by the charging characteristics (See the charging characteristics configuration). Send CDRs to the CG addresses as recommended in GGSN. Send CDRs to the CG addresses according to the priority of CGs. 0 is for the highest priority while 5 the lowest. Lastly, for the CGs with the same priority and of the same type, send CDRs according to CG load size. CDRs will be sent to the CG with lower load prior to the CG with higher load.
68P02904W52-B 31-Jan-2005
10-7
SGSN-to-CG Route
In SGSN, the UCDR, UHPU and ULPI/ULPC implement the functions of the Ga interface. The UCDR implements the CDR coding, sending and GTP' protocol processing. The UHPU implements the routing and forwarding of GTP' packets. The ULPI/ULPC provides an external FE/GE Ethernet interface. The UCDR provides an IP address as the external SGSN Ga interface address. Each of the ULPI/ULPC port provides an IP address for SGSN to connect external routers. To forward GTP' messages, it is required to build an IPOA PVC between UCDR and UHPU. You can build this IPOA PVC on any engine of the UHPU.
Different from the IPOA PVC of the Iu interface, this IPOA PVC does not need the subscriber to specify the IP address bound to the port. The subscriber only has to specify the UCDR position, the UHPU position and the forwarding engine. The destination IP address of the IP packet from the UCDR might be in different network segment with that of the ULPI/ULPC interface. Therefore, you should configure an IP route indicating the ULPI/ULPC interface to the destination IP address.
10-8
68P02904W52-B 31-Jan-2005
Configuring Charging Characteristic Parameters and Default Charging Characteristics

This section introduces the configuration of charging characteristic parameters. After the configuration, SGSN will charge the subscriber of a certain type of charging characteristic according to the configuration.
Description
Preset conditions
None.
Data preparations
Item Basic information. The MNC and MCC of the subscriber. Data
Procedure
Step 1 2 Operation Configure the charging characteristic parameters. Configure the subscriber's default charging characteristics. Command SET CHGCHAR ADD CHGDCHAR
Example
;;Modify the charging characteristic parameters SET CHGCHAR: CC=HOTBILLING, MPL=120, SMOP=NO; ;; Configure the subscriber's default charging characteristics ADD CHGDCHAR: ST=ROAMING, MCC="460", MNC="00", DCC=PREPAID;
68P02904W52-B 31-Jan-2005
10-9
Reference
Charging characteristics
There are four types of charging characteristics: NORMAL (normal charging characteristic): The subscriber pays the charges on a periodic basis, for example, on a monthly basis. HOTBILLING (hotbilling charging characteristic): The subscriber pays the charges right after the conversation. FLATRATE (flatrate charging characteristic): The subscriber pays the charges on a periodic basis, for example, on a monthly basis. However, the charges of every period (for example, every month) are fixed. PREPAID (prepaid charging characteristic): The subscriber needs to prepay a certain amount of charges before obtaining certain services. If the prepaid charge is not enough to cover the expenses of the service, this service will be forcedly interrupted. The parameters for each type of charging characteristics include: CDR types and conditions for generating CDRs: SGSN can generate many types of CDR, including S-CDR, M-CDR, S-SMO-CDR, S-SMT-CDR, LCS-MO-CDR, LCS-MT-CDR and LCS-NI-CDR. It is not necessary to provide all types of CDRs. Therefore, you can decide through the configuration whether to generate the CDR. When you specify to generate M-CDR and S-CDR, you also need to specify the generation conditions, for example, the period for periodically generating M-CDR. Service restriction flag This flag indicating whether SGSN will restrict the subscriber service of this charging characteristic when the buffer is full. IP address of CG The CDR for the subscriber of this charging characteristic is preferentially sent to the IP address of CG. The priority of this CG is higher than that of the CG recommended by GGSN or other CGs or the CG configured by using ADD CHGCG but lower than the CG specified in the charging behavior.
10-10
68P02904W52-B 31-Jan-2005
Default charging characteristics

Usually the HLR provides SGSN with the charging characteristic as the subscription data. If the subscription data does not specify the charging characteristic, SGSN can use the preset default charging characteristics. SGSN supports three types of default charging characteristics: Default configuration of the subscriber who belongs to the PLMN where the SGSN is Default configuration of the visiting subscriber who uses the GGSN in the PLMN where the SGSN is Default configuration of the roaming subscriber who uses the GGSN in the subscriber HPLMN You can use the ADD CHGDCHAR command to configure the default charging characteristics for the visiting and roaming subscribers of the specified PLMN. For the visiting or roaming subscribers whose default charging characteristics are not configured by using the ADD CHGDCHAR command, the default charging characteristics configured in the MOD CHGCDR command will be used.
68P02904W52-B 31-Jan-2005
10-11
Configuring CDR Optional Field

This section introduces the CDR as well as its configuration. After the configuration, the CDR that is generated by SGSN will only contain the fields specified by the operator.
Description
Preset conditions
None.
Data preparations
None.
Procedure
Step 1 Operation Configuring CDR parameters. Command SET CHGCDR
Example
;; Configure CDR parameters SET CHGCDR: ML=CC_SELECT_MODE-0;
Reference
You can decide through configuration whether to generate the optional fields in the CDR. Table 10-1 shows the S-CDR structure of five protocol types. Table 10-2 shows the M-CDR structure of five protocol types. Table 10-3 shows the S-SMO-CDR structure of five protocol types. Table 10-4 shows the S-SMT-CDR structure of five protocol types. Table 10-5 shows the LCS-MT-CDR structure of one protocol types.
10-12
68P02904W52-B 31-Jan-2005
Table 10-6 shows the LCS-MO-CDR structure of one protocol types. Table 10-7 shows the LCS-NI-CDR structure of one protocol types.
The meaning of the symbols in the table is as follows: M:This field is Mandatory and shall always be present in the CDR. C:This field shall be present in the CDR only when certain Conditions are met. These Conditions are specified as part of the field definition. O:This field is optional and configurable either using additional TMN management functions or by using manufacturer specific means. OM:This is a field that, if provisioned by the operator to be present, shall always be included in the CDRs. In other words, an OM parameter that is provisioned to be present is a mandatory parameter. OC:This is a field that, if provisioned by the operator to be present, shall be included in the CDRs when the required conditions are met. In other words, an OC parameter that is configured to be present is a conditional parameter. Table 10-1 Field Record Type. S-CDR. Description SGSN PDP context record. A flag that is present if this is a network initiated PDP context. The primary MSISDN of the subscriber. M CMCC R98 V1.3.0 M ETSI R98 V7.6.0 M ETSI R99 V3.6.0 M ETSI R99 V3.A.0 M ETSI R4 V4.4.0
Network Initiated PDP Context. Served MSISDN.
OC
OM
Cont.
68P02904W52-B 31-Jan-2005
10-13
Table 10-1 Field System Type.
S-CDR. (Continued) Description Indicates the type of air interface used, for example UTRAN. This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface. IMSI of the served party. The IMEI of the ME, if available. The IP address of the current SGSN. The mobile station Network Capability. RAC at the time of 'Record Opening Time'. LAC at the time of 'Record Opening Time'. M C M C CMCC R98 V1.3.0 ETSI R98 V7.6.0 C ETSI R99 V3.6.0 C ETSI R99 V3.A.0 OC ETSI R4 V4.4.0
Served IMSI. Served IMEI. SGSN Address.
M C
M C
M OC
OM
MS Network Capability.
OM
Routing Area code.
OM
Local Area Code.
OM
Cont.
10-14
68P02904W52-B 31-Jan-2005
Table 10-1 Field Cell Identity.
S-CDR. (Continued) Description Cell identity for GSM or Service Area Code (SAC) for UMTS at the time of 'Record Opening Time'. PDP context identifier used to identify this PDP context in different records created by GSNs The control plane IP address of the GGSN currently used. The GGSN address is always the same for an activated PDP context. The logical name of the connected access point to the external packet data network (network identifier part of APN). O CMCC R98 V1.3.0 O ETSI R98 V7.6.0 O ETSI R99 V3.6.0 O ETSI R99 V3.A.0 ETSI R4 V4.4.0 OM
Charging ID.
GGSN Address Used.
Access Point Name Network Identifier.
OM
Cont.
68P02904W52-B 31-Jan-2005
10-15
Table 10-1 Field APN Selection Mode. Access Point Name Operator Identifier. PDP Type.
S-CDR. (Continued) Description An index indicating how the APN was selected. The Operator Identifier part of the APN. PDP type, that is IP, PPP, IHOSS:OSP. PDP address of the served IMSI, that is IPv4 or IPv6. This parameter shall be present except when both the PDP type is PPP and dynamic PDP address assignment is used. O CMCC R98 V1.3.0 O ETSI R98 V7.6.0 O ETSI R99 V3.6.0 O ETSI R99 V3.A.0 ETSI R4 V4.4.0 OM
OM
OM
Served PDP Address.
OC
Cont.
10-16
68P02904W52-B 31-Jan-2005
Table 10-1 Field List of Traffic Data Volumes.
S-CDR. (Continued) Description A list of changes in charging conditions for this PDP context, each change is time stamped. Charging conditions are used to categorize traffic volumes, such as per QoS/tariff period. Initial and subsequently changed QoS and corresponding data volumes are listed. Time stamp when PDP context is activated in this SGSN or record opening time on subsequent partial records. Duration of this record in the SGSN. Present if this is first record after SGSN change. M CMCC R98 V1.3.0 M ETSI R98 V7.6.0 M ETSI R99 V3.6.0 M ETSI R99 V3.A.0 ETSI R4 V4.4.0 OM
Record Opening Time.
Duration.
SGSN Change.
Cont.
68P02904W52-B 31-Jan-2005
10-17
Table 10-1 Field Cause for Record Closing.
S-CDR. (Continued) Description The reason for closure of the record from this SGSN. A more detailed reason for the release of the connection. Partial record sequence number in this SGSN. Only present in case of partial records. Name of the recording entity. A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. Consecutive record number created by this node. The number is allocated sequentially including all CDR types. M CMCC R98 V1.3.0 M ETSI R98 V7.6.0 M ETSI R99 V3.6.0 M ETSI R99 V3.A.0 M ETSI R4 V4.4.0
Diagnostics.
OM
Record Sequence Number.
Node ID.
OM
Record Extensions.
OC
Local Record Sequence Number.
OM
Cont.
10-18
68P02904W52-B 31-Jan-2005
Table 10-1 Field RNC Unsent Downlink Volume.
S-CDR. (Continued) Description The downlink data volume which the RNC has not sent to MS. This field is present when the RNC has provided unsent downlink volume count at RAB release. Set of CAMEL information related to PDP context. For more information see Description of Record Fields. This field is present if CAMEL service is activated. The Charging Characteristics applied to the PDP context. Holds information about how Charging Characteristics were selected. CMCC R98 V1.3.0 ETSI R98 V7.6.0 C ETSI R99 V3.6.0 C ETSI R99 V3.A.0 OC ETSI R4 V4.4.0
CAMEL Information.
OC
Charging Characteristics.
Charging Characteristics Selection Mode.
OM
68P02904W52-B 31-Jan-2005
10-19
Table 10-2 Field Record Type.
M-CDR. Description SGSN mobility management record. IMSI of the MS. The IMEI of the ME, if available. The primary MSISDN of the subscriber. The IP address of the current SGSN. The mobile station network capability. Routing Area at the time of the Record Opening Time. Location Area Code at the time of Record Opening Time. The Cell Identity for GSM or Service Area Code (SAC) for UMTS at the time of the Record Opening Time. M M M CMCC R98 V1.3.0 M ETSI R98 V7.6.0 M ETSI R99 V3.6.0 M ETSI R99 V3.A.0 M ETSI R4 V4.4.0
Served IMSI. Served IMEI. Served MSISDN.
M C
M C
M C
M C
M OC
OM
SGSN Address.
OM
OM
Routing Area code.
OM
Local Area Code.
OM
Cell Identity.
OM
Cont.
10-20
68P02904W52-B 31-Jan-2005
Table 10-2 Field Change of Location.
M-CDR. (Continued) Description A list of changes in Routing Area Code, each with a time stamp. This field is not required if partial records are generated when the location changes. Timestamp when MS is attached to this SGSN or record opening time on following partial record. Duration of this record. Present if this is first record after SGSN change. The reason for the closure of the record in this SGSN. A more detailed reason for the release of the connection. O CMCC R98 V1.3.0 O ETSI R98 V7.6.0 O ETSI R99 V3.6.0 O ETSI R99 V3.A.0 OC ETSI R4 V4.4.0
Record Opening Time.
Duration. SGSN Change.
O C
O C
O C
O C
OM C
Cause for Record Closing.
Diagnostics.
OM
Cont.
68P02904W52-B 31-Jan-2005
10-21
Table 10-2 Field Record Sequence Number.
M-CDR. (Continued) Description Partial record sequence number in this SGSN; only present in case of partial records. Name of the recording entity. A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. Consecutive record number created by this node. The number is allocated sequentially including all CDR types. The Charging Characteristics used by the SGSN. C CMCC R98 V1.3.0 C ETSI R98 V7.6.0 C ETSI R99 V3.6.0 C ETSI R99 V3.A.0 C ETSI R4 V4.4.0
Node ID.
OM
Record Extensions.
OC
OM
Cont.
10-22
68P02904W52-B 31-Jan-2005
M-CDR. (Continued) Description Indicates the type of air interface used, for example UTRAN. This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface. Set of CAMEL information related to Attach/Detach session. For more information, see Description of Record Fields. This field is present if CAMEL service is activated. Holds information about how Charging Characteristics were selected. CMCC R98 V1.3.0 ETSI R98 V7.6.0 C ETSI R99 V3.6.0 C ETSI R99 V3.A.0 OC ETSI R4 V4.4.0
CAMEL Information.
OC
OM
68P02904W52-B 31-Jan-2005
10-23
S-SMO-CDR. Description SGSN Mobile Originated SMS. The IMSI of the subscriber. The IMEI of the ME, if available. The primary MSISDN of the subscriber. The mobile station network capability. The address (E.164) of the SMS-service center. The E.164 number of the SGSN. The Location Area Code from which the message originated. The Routing Area Code from which the message originated. M CMCC R98 V1.3.0 M ETSI R98 V7.6.0 M ETSI R99 V3.6.0 M ETSI R99 V3.A.0 M ETSI R4 V4.4.0
Served IMSI. Served IMEI. Served MSISDN.
OC
OM
OM
Service Center.
OM
Recording Entity. Location Area Code.
OM
OM
Routing Area Code.
OM
Cont.
10-24
68P02904W52-B 31-Jan-2005
Table 10-3 Field Cell Identity.
S-SMO-CDR. (Continued) Description The Cell Identity for GSM or Service Area Code (SAC) for UMTS from which the message originated. The time at which the message was received by the SGSN from the subscriber. A reference provided by the MS uniquely identifying this message. The result of the attempted delivery if unsuccessful. A set of network operator/ manufacturer specific extensions to the record. Conditioned upon the existence of an extension. Name of the recording entity. O CMCC R98 V1.3.0 O ETSI R98 V7.6.0 O ETSI R99 V3.6.0 O ETSI R99 V3.A.0 ETSI R4 V4.4.0 OM
Event Time Stamp.
Message Reference.
SMS Result.
Record Extensions.
OC
Node ID.
OM
Cont.
68P02904W52-B 31-Jan-2005
10-25
Table 10-3 Field Local Record Sequence Number.
S-SMO-CDR. (Continued) Description Consecutive record number created by this node. The number is allocated sequentially including all CDR types. The Charging Characteristics flag set used by the SGSN. Indicates the type of air interface used, for example UTRAN. This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface. O CMCC R98 V1.3.0 O ETSI R98 V7.6.0 O ETSI R99 V3.6.0 O ETSI R99 V3.A.0 ETSI R4 V4.4.0 OM
System Type.
OC
Cont.
10-26
68P02904W52-B 31-Jan-2005
Table 10-3 Field Destination Number.
S-SMO-CDR. (Continued) Description The destination short message subscriber number. Set of CAMEL information related to SMS session. For more information see Description of Record Fields. This field is present if CAMEL service is activated. Holds information about how Charging Characteristics were selected. S-SMT-CDR. Description SGSN Mobile Terminated SMS. The IMSI of the subscriber. M CMCC R98 V1.3.0 M ETSI R98 V7.6.0 M ETSI R99 V3.6.0 M ETSI R99 V3.A.0 M ETSI R4 V4.4.0 CMCC R98 V1.3.0 ETSI R98 V7.6.0 O ETSI R99 V3.6.0 O ETSI R99 V3.A.0 ETSI R4 V4.4.0 OM
CAMEL Information.
OC
OM
Served IMSI.
Cont.
68P02904W52-B 31-Jan-2005
10-27
Table 10-4 Field Served IMEI. Served MSISDN.
S-SMT-CDR. (Continued) Description The IMEI of the ME, if available. The primary MSISDN of the subscriber. The mobile station network capability The address (E.164) of the SMS-service center. The E.164 number of the SGSN. The Location Area Code to which the message was delivered. The Routing Area Code to which the message was delivered. The Cell Identity for GSM or Service Area Code (SAC) for UMTS to which the message was delivered. O CMCC R98 V1.3.0 O ETSI R98 V7.6.0 O ETSI R99 V3.6.0 O ETSI R99 V3.A.0 OC ETSI R4 V4.4.0
OM
OM
Service Center.
OM
Recording Entity. Location Area Code.
OM
OM
Routing Area Code.
OM
Cell Identity.
OM
Cont.
10-28
68P02904W52-B 31-Jan-2005
Table 10-4 Field Event Time Stamp.
S-SMT-CDR. (Continued) Description Delivery time stamp, time at which message was sent to the MS by the SGSN. The result of the attempted delivery if unsuccessful. A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. Name of the recording entity. Consecutive record number created by this node. The number is allocated sequentially including all CDR types. The Charging Characteristics flag set used by the SGSN. M CMCC R98 V1.3.0 M ETSI R98 V7.6.0 M ETSI R99 V3.6.0 M ETSI R99 V3.A.0 M ETSI R4 V4.4.0
SMS Result.
Record Extensions.
OC
Node ID.
OM
OM
Cont.
68P02904W52-B 31-Jan-2005
10-29
S-SMT-CDR. (Continued) Description Indicates the type of air interface used, for example UTRAN. This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface. Holds information about how Charging Characteristics were selected. Set of CAMEL information related to SMS session. For more information see Description of Record Fields. This field is present if CAMEL service is activated. CMCC R98 V1.3.0 ETSI R98 V7.6.0 C ETSI R99 V3.6.0 C ETSI R99 V3.A.0 OC ETSI R4 V4.4.0
OM
CAMEL Information.
OC
10-30
68P02904W52-B 31-Jan-2005
Table 10-5
LCS-MT-CDR. Field Description SGSN Mobile Terminated LCS. The E.164 number of the SGSN. The type of LCS client that invokes the LR. Further identification of the LCS client. The IMSI of the subscriber. The primary MSISDN of the subscriber. The IP address of the current SGSN. The type of estimated location. QoS of the LR, if available. Priority of the LR, if available. The E.164 address of the requesting GMLC. The time at which the Perform_Location_Request is sent by the SGSN. The duration of proceeding the location request. The privacy notification to MS user that was applicable when the LR was invoked, if available. This parameter indicates the override MS privacy by the LCS client, if available. The LAC and CI when the LR is received. The Routing Area Code to which the LCS terminated. The location estimate for the subscriber if contained in geographic position and the LR was successful. The positioning method used or attempted, if available. M M M M M OM OM M C C M M ETSI R4 V4.4.0
Record Type. Recording Entity. LCS Client Type. LCS Client Identity. Served IMSI. Served MSISDN. SGSN Address. Location Type. LCS QoS. LCS Priority. MLC Number. Event Time stamp.
Measurement Duration. Notification To MS User.
OM C
Privacy Override.
Location. Routing Area Code. Location Estimate.
OM OM OC
Positioning Data.
C Cont.
68P02904W52-B 31-Jan-2005
10-31
Table 10-5
LCS-MT-CDR. (Continued) Field Description The result of the LR if any failure or partial success happened as known at radio interface. The reason for closure of the record from this SGSN. More detailed information about the Cause for Record Closing if any failure or partial success happened. Name of the recording entity. Consecutive record number created by this node. The number is allocated sequentially including all CDR types. The Charging Characteristics used by the SGSN. (always use the subscribed CC). Holding the information about how Charging Characteristics were selected (only subscribed/home default/visited default). Indicates the type of air interface used, for example UTRAN. This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface. A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. OC ETSI R4 V4.4.0
LCS Cause.
Cause for Record Closing. Diagnostics.
M C
Node ID. Local Record Sequence Number.
OM OM
OM
System Type.
OC
Record Extensions.
OC
Table 10-6
LCS-MO-CDR. Field Description SGSN Mobile Originated LCS. E.164 number of the SGSN. M M Cont. ETSI R4 V4.4.0
Record Type. Recording Entity.
10-32
68P02904W52-B 31-Jan-2005
Table 10-6
LCS-MO-CDR. (Continued) Field Description The type of the LCS client that invoked the LR, if available. Further identification of the LCS client, if available. The IMSI of the subscriber. The primary MSISDN of the subscriber. The IP address of the current SGSN. The type of the location request. QoS of the LR, if available. Priority of the LR, if available. The E.164 address of the involved GMLC, if applicable. The time at which the Perform_Location_Request is sent by the SGSN. The duration of proceeding the location request. The LAC and CI when the LR is received. The Routing Area Code from which the LCS originated. The location estimate for the subscriber if contained in geographic position and the LR was successful. The positioning method used or attempted, if available. The result of the LR if any failure or partial success happened as known at radio interface. The reason for closure of the record from this SGSN. More detailed information about the Cause for Record Closing if any failure or partial success happened. Name of the recording entity. C C M OM OM M C Oc C M ETSI R4 V4.4.0
LCS Client Type. LCS Client Identity. Served IMSI. Served MSISDN. SGSN Address. Location Method. LCS QoS. LCS Priority. MLC Number. Event Time stamp.
Measurement Duration. Location. Routing Area Code. Location Estimate.
OM OM OM OC
Positioning Data. LCS Cause.
C C
M C
Node ID.
OM Cont.
68P02904W52-B 31-Jan-2005
10-33
Table 10-6
LCS-MO-CDR. (Continued) Field Description Consecutive record number created by this node. The number is allocated sequentially including all CDR types. The Charging Characteristics flag set used by the SGSN. Holding information about how Charging Characteristics were selected Indicates the type of air interface used, for example UTRAN. This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface. A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. OM ETSI R4 V4.4.0
Charging Characteristics. Charging Characteristics Selection Mode. System Type.
M OM
OC
Record Extensions.
OC
Table 10-7
LCS-NI-CDR. Field Description SGSN Network Induced LCS. The E.164 number of the SGSN. The type of the LCS client that invoked the LR, if available. Further identification of the LCS client, if available. The IMSI of the subscriber if supplied. The primary MSISDN of the subscriber if supplied. The IP address of the current SGSN. The IMEI of the ME, if available. M M C C C C OM OC Cont. ETSI R4 V4.4.0
Record Type. Recording Entity. LCS Client Type. LCS Client Identity. Served IMSI. Served MSISDN. SGSN Address. Served IMEI.
10-34
68P02904W52-B 31-Jan-2005
Table 10-7
LCS-NI-CDR. (Continued) Field Description QoS of the LR, if available. Priority of the LR, if available. The E.164 address of the involved GMLC, if applicable. The time at which the Perform_Location_Request is sent by the SGSN. The duration of proceeding the location request. The LAC and CI when the LR is received. The Routing Area Code from which the LCS originated. The location estimate for the subscriber if contained in geographic position and the LR was successful. The positioning method used or attempted, if available. The result of the LR if any failure or partial success happened as known at radio interface. The reason for closure of the record from this SGSN. More detailed information about the Cause for Record Closing if any failure or partial success happened. Name of the recording entity. Consecutive record number created by this node. The number is allocated sequentially including all CDR types. The Charging Characteristics flag set used by the SGSN. C C C M ETSI R4 V4.4.0
LCS QoS. LCS Priority. MLC Number. Event Time stamp.
Measurement Duration. Location. Routing Area Code. Location Estimate.
OM OM OM OC
Positioning Data. LCS Cause.
C C
M C
Node ID. Local Record Sequence Number.
OM OM
M Cont.
68P02904W52-B 31-Jan-2005
10-35
Table 10-7
LCS-NI-CDR. (Continued) Field Description Holding information about how Charging Characteristics were selected. Indicates the type of air interface used, for example UTRAN. This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface. A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. OM ETSI R4 V4.4.0
Charging Characteristics Selection Mode. System Type.
OC
Record Extensions.
OC
10-36
68P02904W52-B 31-Jan-2005
Configuring Charging Behavior

This section introduces the configuration of charging behavior. After the configuration, SGSN can adopt different charging methods for the subscribers.
Description
Preset conditions
None.
Data preparations
None.
Procedure
Step 1 Operation Configure charging behavior parameters. Command ADD CHGBEHA
Example
;; Configure charging behavior parameters ADD CHGBEHA: CB=B1, BA=PLT, PURGELEN=60, ACC=HOTBILLING-1&FLATRATE1&PREPAID-1&NORMAL-1;
Reference
The charging behavior refers to the charging methods for implementing charges on the subscribers. Each type of charging behavior corresponds to one type of charging characteristic. SGSN supports the following charging behavior:
68P02904W52-B 31-Jan-2005
10-37
1. 2. 3.
Long timer of closing the idle PDP (PLT). If there is no data transfer within this time segment, the subscriber with this charging behavior will be forcedly deactivated. Short timer of closing the idle PDP (PST). If there is no data transfer within this time segment, the subscriber with this charging behavior will be forcedly deactivated. The SMTS-U address that does not generate S-SMO-CDRs (SMTS-U). If the local subscriber with this charging behavior sends a short message to this SMTS-U address, the S-SMO-CDR will not be generated. The roaming subscriber is prohibited from using the local GGSN (NOROAMING). The roaming subscriber with this charging behavior cannot use the local GGSN. The subscriber is prohibited from initiating the QoS change from the network side (NOQOS). A subscriber with this charging behavior cannot initiate the QoS change from the network side. The IP address of the CG (CGIP). The CDRs of the subscriber with this charging behavior will be preferentially sent to this CG. The priority of this CG is higher than that of the CG specified by the charging characteristic, that of the CG recommended by GGSN or other CGs, and that of the CGs configured by operators.
4. 5. 6.
You can configure PLT, PST, NOROAMING and NOQOS only once. The same type of charging characteristic cannot simultaneously support both PLT and PST. You can configure charging behaviors of only one CG IP address for each charging characteristic, but you can configure charging behaviors of multiple SMTS-U addresses.
10-38
68P02904W52-B 31-Jan-2005
Configuring Special Charging Rate Period

This section introduces the configuration of special charging rate periods. After the configuration, SGSN can record the subscriber traffic flow of different tariff periods.
Description
Preset conditions
None
Data preparations
None
Procedure
Step 1 2 3 Operation Configure the charging holiday. Configure the charging days in a week. Configure the tariff period in a day. Command ADD CHGHOLI SET CHGWKDY ADD CHGTARI
Example
;;Add a holiday configuration of normal charging characteristic: 01-05-2001. ADD CHGHOLI: DAY=1, MONTH=5, YEAR=2001, CC= NORMAL; ;;Add a weekday configuration of normal charging characteristic: Monday is a normal week day. SET CHGWKDY: WKDAY= MON, CC=NORMAL, TT=WORK; ;;Add a tariff period record of normal charging characteristic. The tariff type is workday. The start time of the tariff period is 00:00. The end time is 10:00. ADD CHGTARI: TT=WORK, ST=00&00, ET=10&00, CC=NORMAL;
68P02904W52-B 31-Jan-2005
10-39
Reference
Charging holiday
Charging holiday is to configure the holiday property of a day and the corresponding charging characteristics.
Charging days in a week

Charging days in a week is to set the tariff properties (weekday or weekend) of the seven days in a week and the corresponding charging characteristics.
Tariff period
The tariff period is used together with charging holiday and charging days in a week. It is used to set the special tariff periods for the holidays and weekends. You can set multiple periods, but the periods with the same charging characteristics should not overlap.
The duration of any tariff period cannot be less than ten minutes.
10-40
68P02904W52-B 31-Jan-2005
11
System Configuration

Chapter
68P02904W52-B 31-Jan-2005
11-1
System Configuration Overview
System Configuration Overview

The system configuration consists of the system basic information configuration, remote maintenance gateway configuration, SNMP parameter configuration, OMC-S/T 2.0 IP configuration and system time configuration. You may perform all configurations in any sequence.
11-2
68P02904W52-B 31-Jan-2005
Configuring System Basic Information

This section describes the system basic information configuration.
Description
Preset conditions
None
Data preparations
Item Basic information. IP address. FTP user name. FTP password. Data IP address of the default FTP gateway.
Procedure
Step 1 Operation Configure the basic information of the system. SET SYS Command
Example
;;Configure the FTP server: SET SYS: SWSIP="175.22.44.100", SWSUSRNAME="loader", SWSPWD="loader";
Reference
The system basic information includes:
68P02904W52-B 31-Jan-2005
11-3
System description information including the ID, name, location, time zone, provided services and exchange capacity of the system. Protocol version supported by the system such as R4 or R99. HPLMN information including the mobile network number and mobile country number of the HPLMN where the SGSN is located. FTP server information. The FTP server stores the information including board software and configuration files of the system. You need to obtain the corresponding files from the FTP server in case of system loading and board software upgrade. You may also back up various files such as alarm files, performance files and log files generated by the system during operation to the FTP server. If the FTP server and the UOMU are in different network segment, you need configure the gateway. If the system has not loaded the UOMU software, the UOMU will use the default FTP gateway set in SET SYS command. Otherwise, it will use the default FTP gateway set in ADD GATEWAY command.
11-4
68P02904W52-B 31-Jan-2005
Configuring Remote Maintenance Gateway
Configuring Remote Maintenance Gateway

This section describes the remote maintenance gateway configuration. After the configuration, the system can perform maintenance on the SGSN through an LM in a network segment different from the UOMU network segment.
Description
Preset conditions
The configuration of the UOMU has finished.
Data preparations
Item Basic information. IP address of the gateway. IP address and the mask code of the destination. Data
Procedure
Step 1 Operation Configure the remote maintenance gateway. Command ADD GATEWAY
Example
;; Configure the remote maintenance gateway: ADD GATEWAY: GATEWAY="127.11.0.1", DSTIP="127.55.0.0",DSTMSK="255.255.240.0" ;;
Reference
None
68P02904W52-B 31-Jan-2005
11-5
Configuring SNMP
Configuring SNMP

This section describes the SNMP configuration. After the configuration, the SGSN can exchange information with the SNMP network management center.
Description
Preset conditions
None.
Data preparations
Item Basic information. Read community name. Write community name. TRAP IP address. Data
Procedure
Step 1 2 Operation Configure the community name. Add a TRAP IP address. Command SET SCOMM ADD TRAPIP
Example
;;Configure the community name: MOD SCOMM: RCN="SNMP1", WCN="SNMP2"; ;;Add a TRAP IP address: ADD TRAPIP: IP="191.22.5.11";
11-6
68P02904W52-B 31-Jan-2005
Configuring SNMP
Reference
Motorola C-SGSN can access the Network Management Center (NMC) through Simple Network Management Protocol (SNMP). Motorola C-SGSN supports SNMP V1. The SNMP subsystem in Motorola C-SGSN can help to fulfill the following functions: Using the SNMP interface, the NMC can read critical configuration data in the Motorola C-SGSN system and write some of them. The critical configuration data include system information, Gb interface configuration information and SS7 link information. Through the SNMP interface, TRAP can report alarms to NMC. Through the SNMP interface, NMC can retrieve the performance measurement data in the Motorola C-SGSN system. SNMP configuration includes the SNMP community name configuration and destination TRAP address configuration. There are two kinds of community names, read community name and write community name, used for Motorola C-SGSN to authenticate the authority of the NMC when the NMC reads data from or writes data to the Motorola C-SGSN. The NMC shall be configured with both, a community name (used for accessing the Motorola C-SGSN) and the IP address of the Motorola C-SGSN. In addition, the community name configured in the NMC shall be the same as that configured in the Motorola C-SGSN. Destination TRAP address refers to the IP address of the NMC. Based on this IP address, alarms can be reported to the corresponding NMC through TRAP operations. Motorola C-SGSN may have access to multiple NMCs. Correspondingly, users shall add the IP addresses of multiple NMCs. Thus, there can be multiple destination TRAP address records. However, there shall be only one community name record. In other words, the multiple NMCs access the Motorola C-SGSN with the same community name.
68P02904W52-B 31-Jan-2005
11-7
Configuring OMC-S/T 2.0 IP Address
Configuring OMC-S/T 2.0 IP Address

This section describes the OMC-S/T 2.0 IP address configuration. The OMC-S/T 2.0 can access the SGSN only after the configuration.
Description
Preset conditions
None
Data preparations
Item Basic information. OMC-S/T 2.0 IP. Data
Procedure
Step 1 Operation Set the OMC-S/T 2.0 IP address. SET EMS Command
Example
;;Set the OMC-S/T 2.0 IP address: SET EMS: IP="10.163.15.227";
Reference
Only the OMC-S/T 2.0 with a specified IP address can log on to the SGSN. Therefore, you need set the OMC-S/T 2.0 IP address in the SGSN before OMC-S/T 2.0 logon.
11-8
68P02904W52-B 31-Jan-2005
Configuring System Time

This section describes the system time configuration. After the configuration, the SGSN can obtain the time information from a specified NTP server.
Description
Preset conditions
The configuration of the UGTP has finished. To use NTP as the system time reference, you need configure the IP route between the SGSN and the NTP server. For details, see Chapter 5, "Gn/Gp Interface Configuration," in this manual.
Data preparations
None
Procedure
To use the NTP timing: Step 1 2 3 Otherwise: Step 1 2 Operation Set the system time. Set the daylight saving time. SET DST Command SET SYSTIME Operation Set the NTP client. Set the NTP server. Set the daylight saving time. SET NTP ADD NTPS SET DST Command
68P02904W52-B 31-Jan-2005
11-9
Example
;; Set the NTP client SET NTP: SRN=8, SN=14, RI=2, FTHD=15 , TMST=80; ;; Set the NTP server ADD NTPS: IP="10.11.132.11", VER=V3, PR=YES, AUTH=YES, KI=1, KEY="AAA"; ;; Set the daylight saving time SET DST: SD=07&01, ST=17&19&02, ED=10&1, ET=17&19&02, DD=1;
Reference
The system time information is applicable to all time-related information such as performance measurement, Motorola C-SGSN Alarm Management System, and charging. The SGSN can obtain the reference time from the internal timer. It can also obtain the reference time from the NTP server through the Network Timing Protocol (NTP). Because the time obtained from the NTP server is synchronous with the entire network, we recommend that you should obtain the time information from the NTP server. To obtain the system time information from the NTP server, you need start an NTP client (located at UGTP) in the SGSN. The client will sample the time information from the NTP server at a specified frequency (polling frequency). The difference between the system time and the NTP server reference time may be greater than or equal to a specified threshold (time adjustment threshold). In that case, the SGSN will synchronize its time to the NTP server time. There may be multiple NTP servers in a network. You may set these servers to different priority levels. To ensure the security of the servers, you may specify an encryption key to check the validity of the client. The SGSN time system supports the DST function. You may set the system time a specified time ahead of or behind the standard time during a specified period.
11-10
68P02904W52-B 31-Jan-2005
12
Feature Configuration

Chapter
68P02904W52-B 31-Jan-2005
12-1
Feature Configuration Overview
Feature Configuration Overview

Features refer to nonstandard functions provided to satisfy special demands, for example, from operators. Presently, an SGSN supports the following functions: Roaming Barred by IMSI. Choosing GGSN by IMSI. RAI IE in Gn. Detaching Inactive Subscriber. GPRS Second Authentication In Attach. GPRS Second Authentication In RAU. Rejecting GPRS subscribers attach by APNNI Rejecting GPRS subscribers attach by IMSI
12-2
68P02904W52-B 31-Jan-2005
Roaming Barred by IMSI

Roaming Barred by IMSI is explained below:
Overview of the Function

With the function 'Roaming Barred by IMSI' enabled, a subscriber's attach request or routing area update request will be rejected if the IMSI of the subscriber is within a roaming-barred IMSI range and the subscriber is in a roaming-barred location (routing) area.
Description
Preset conditions
None
Data preparations
Item Basic information. Data The mapping relation between an IMSI range and a roaming-barred location (routing) area.
Procedure
Step 1 2 Operation Enable the function of roaming barred by IMSI range. Add the mapping relation between an IMSI range and a roaming-barred location (routing) area. Command SET SERVICE_PARA ADD RESTRICTAREA
68P02904W52-B 31-Jan-2005
12-3
Example
SET SERVICE_PARA: ROAM=YES; ADD RESTRICTAREA: BEGIMSI="460017551111111", ENDIMSI="460017552222222", LAI="460007123", RAC="5";
Reference
None.
12-4
68P02904W52-B 31-Jan-2005
Choosing GGSN by IMSI

Choosing GGSN by IMSI is explained below:

With the function 'Choosing GGSN by IMSI' enabled, an SGSN will query the IMSI-APNOI Mapping Relation Table by the IMSI of a subscriber during a PDP context activation procedure. If the query succeeds, the SGSN will initiate a DNS parse procedure based on the queried APN Operator ID (APN OI) to obtain the corresponding GGSN IP address. Otherwise, it will select an APN OI based on the APN OI selection algorithm defined in protocol 23.060. Then it will initiate a DNS parse procedure to obtain the corresponding GGSN IP address.
Description
Preset conditions
None
Data preparations
Item Basic information. Data The mapping relation between an IMSI range and an APN OI.
Procedure
Step 1 2 Operation Enable the function of choosing GGSN by IMSI range. Add the mapping relation between an IMSI range and an APN OI. Command SET SERVICE_PARA ADD IMSIAPNOI
68P02904W52-B 31-Jan-2005
12-5
Example
MOD SERVICE_PARA: GGSN=YES; ADD IMSIAPNOI:BEGIMSI = 460007551111111, ENDIMSI = 460007552222222, APNOI="MNC007.MCC460.GPRS";
Reference
None.
12-6
68P02904W52-B 31-Jan-2005
RAI IE in Gn
RAI IE in Gn

RAI IE in Gn is as follows:

With the function 'RAI IE in Gn' enabled, an SGSN will send Create PDP Context Request and Update PDP Context Request carrying an extra routing area identifier information element (RAI IE) to a user-defined GGSN. This IE contains MNC and MCC.
Description
Preset conditions
None
Data preparations
Item Basic information. Data IP Address of the GGSN control plane.
Procedure
Step 1 2 Operation Enable the function 'RAI IE in Gn'. Add an GGSN that requires the messages received through the Gn interface to carry RAI IE. Command SET SERVICE_PARA ADD GGSNCHARACT
Example
SET SERVICE_PARA: GNMSG=YES; ADD GGSNCHARACT: IP="168.22.168.12",ISRAIRQD = YES;
68P02904W52-B 31-Jan-2005
12-7
RAI IE in Gn
Reference
None.
12-8
68P02904W52-B 31-Jan-2005
Detaching Inactive Subscribers

Detaching Inactive Subscribers is explained below:

With the function 'Detaching Inactive Subscribers' enabled, an SGSN will detach a subscriber if it has not initiated PDP context activation request within a specified time after the routing area update.
This function is valid only for 2.5G subscribers.
Description
Preset conditions
None
Data preparations
None.
Procedure
Step 1 2 Operation Enable the function of detaching inactive subscribers. Modify the Inactive-subscriber Detach Timer. Command SET SERVICE_PARA SET GMMTMR
68P02904W52-B 31-Jan-2005
12-9
Example
SET SERVICE_PARA: DETACH =YES; SET GMMTMR: NACTTMR=400;
Reference
None.
12-10
68P02904W52-B 31-Jan-2005
Not detaching inactive subscribers of the specified APN

The procedure of Not detaching inactive subscribers of the specified APN is explained below:

This section introduces how to configure the function of not detaching inactive subscribers of the specified APN. After the configuration takes effect, with the function "Detaching Inactive Subscribers" enabled, the inactive subscriber who has subscribed the specified APN will not be detached forcibly.
Description
Preset conditions
The function 'Detaching Inactive Subscribers' is enabled,
Data preparations
None.
Procedure
Step 1 Operation Add an APN NI that cannot be detached forcedly. Command ADD APNNICHARACT
68P02904W52-B 31-Jan-2005
12-11
Example
;; Add an APN NI that cannot be detached forcedly. ADD APNNICHARACT : APNNI="motorola1.com",RSVIDLEUSER = YES;
Reference
None.
12-12
68P02904W52-B 31-Jan-2005
GPRS Second Authentication in Attach

GPRS Second Authentication in Attach is explained below:

With the function 'GPRS Second Authentication in Attach' enabled, the network will initiate a second authentication request if the first authentication fails during an attach procedure. For example, the authentication can be considered failed when the SRES returned by the MS is different from that in the SGSN. The second request will use a new RAND (RAND2) different from the previous RAND (RAND1). When the second authentication fails, the network will send the AUTHENTICATION_REJECT message to the MS. If the function is disabled, the network will send the AUTHENTICATION_REJECT message to the MS upon the failure in the first authentication.
Description
Preset conditions
None
Data preparations
None.
Procedure
Step 1 Operation Enable the function 'GPRS Second Authentication In Attach'. Command SET SERVICE_PARA
68P02904W52-B 31-Jan-2005
12-13
Example
SET SERVICE_PARA: ATTSAUTH=YES;
Reference
None.
12-14
68P02904W52-B 31-Jan-2005
GPRS Second Authentication in RAU

GPRS Second Authentication in RAU is explained below:

With the function 'GPRS Second Authentication in RAU' enabled, the network will initiate a second authentication request if the first authentication fails during a routing area update (RAU) procedure. For example, the authentication can be considered failed when the SRES returned by the MS is different from that in the SGSN. The second request will use a new RAND (RAND2) different from the previous RAND (RAND1). When the second authentication fails, the network will send the AUTHENTICATION_REJECT message to the MS. If the function is disabled, the network will send the AUTHENTICATION_REJECT message to the MS upon the failure in the first authentication.
Description
Preset conditions
None
Data preparations
None.
Procedure
Step 1 Operation Enable the function 'GPRS Second Authentication in RAU'. Command SET SERVICE_PARA
68P02904W52-B 31-Jan-2005
12-15
Example
SET SERVICE_PARA: RAUSAUTH=YES;
Reference
None.
12-16
68P02904W52-B 31-Jan-2005
Rejecting GPRS Subscribers Attach by APNNI


When providing both 2G GPRS services and 3G services, the network operator can specify different APNNIs for 2G GPRS subscribers and 3G subscribers to prevent 2G GPRS subscribers from attaching to 3G networks. If this function is enabled, the SGSN will reject the attach to 3G networks of the users who have subscribed to 2G GPRS APNNI.
This function is valid only for 3G networks.
Description
Preset conditions
None.
Data preparations
Item Basic information ANP NI Data
68P02904W52-B 31-Jan-2005
12-17
Procedure
Step 1 Operation Enable the function of rejecting GPRS subscribers attach by APNNI. Add the APNNI of GRPS subscribers to APNNI list. Command SET SERVICE_PARA: APNREJGPRS=YES; ADD APNNILST
Example
To prevent 2G subscribers whose APNNI is GPRS from accessing 3G networks: SET SERVICE_PARA: APNREJGPRS=YES; ADD APNNILST: MCC="460", MNC="00", APNNI="GPRS";
Reference
None
12-18
68P02904W52-B 31-Jan-2005
Rejecting GPRS Subscribers Attach by IMSI


When providing both 2G GPRS services and 3G services, the network operator can specify different IMSI number segments for 2G GPRS subscribers and 3G subscribers to prevent 2G GPRS subscribers from attaching to 3G networks. If this function is enabled, the SGSN will reject the attach to 3G networks of the users whose IMSI is in the IMSI number segment of 2G GPRS.
This function is valid only for 3G networks.
Description
Preset conditions
None
Data preparations
Item Basic information IMSI number segment Data
68P02904W52-B 31-Jan-2005
12-19
Procedure
Step 1 2 Operation Enable the function of rejecting GPRS subscriber attach by IMSI. Add the IMSI number segment of GRPS subscribers. Command SET SERVICE_PARA: IMSIREJGPRS=YES; ADD USRATTIMSI
Example
To prevent 2G subscribers whose IMSI is in the range of 460001021432170 to 460001021432179 from accessing 3G networks: SET SERVICE_PARA: IMSIREJGPRS=YES; ADD IMSILIST: BEGINIMSI="460001021432170", ENDIMSI="460001021432179", USRATT=GPRS;
References
None
12-20
68P02904W52-B 31-Jan-2005
Index
Index

Charging Configuration Overview . . . . . Choosing GGSN by IMSI . . . . . . . . . Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Overview of the Function . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Configure DNS/HOSTFILE . . . . . . . . Description . . . . . . . . . . . . . . Data preparation . . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Configuring Authentication and Ciphering Parameters . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Authentication. . . . . . . . . . . . Authentication failure configuration. . Ciphering . . . . . . . . . . . . . . IMEI check . . . . . . . . . . . . . P-TMSI . . . . . . . . . . . . . . . Configuring Board . . . . . . . . . . . . Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . 2.5G example . . . . . . . . . . . . 3G example . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . UCDR . . . . . . . . . . . . . . . UEPI/UTPI . . . . . . . . . . . . . UGBI . . . . . . . . . . . . . . . . UGTP . . . . . . . . . . . . . . . UHPU . . . . . . . . . . . . . . . UICP . . . . . . . . . . . . . . . . ULAN . . . . . . . . . . . . . . . 68P02904W52-B 31-Jan-2005
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
101212121212121212. 5. 5. 5. 5. 5. 5. 5. . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 5 5 5 5 6 5 5 6 6 6 6 6 6 6 7
7- 3 7- 3 7- 3 7- 3 7- 3 7- 3 7- 4 7- 4 7- 5 7- 4 7- 4 7- 4 2- 7 2- 7 2- 7 2- 7 2-10 2-12 2-10 2- 8 2-14 2-15 2-16 2-16 2-16 2-15 2-16 2-17
Configuring Board (contd.) Reference (contd.) UOMU . . . . . . . . . . . . . . . URCU . . . . . . . . . . . . . . . USPU. . . . . . . . . . . . . . . . Virtual Subrack . . . . . . . . . . . Configuring BSSAP+ (Gs interface) . . . . Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Configuring CAMEL service . . . . . . . Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . CAMEL Services . . . . . . . . . . Camel timer . . . . . . . . . . . . . CAMEL trigger mode . . . . . . . . Configuring CDR Optional Field . . . . . Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Configuring Cell Reference Parameters . . Description . . . . . . . . . . . . . . Data preparation . . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Configuring CG and Route between SGSN CG . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
2-14 2-14 2-15 2-14 3-26 3-26 3-26 3-26 3-26 3-26 3-27 9- 4 9- 4 9- 4 9- 4 9- 5 9- 4 9- 5 9- 5 9- 5 9- 5 10-12 10-12 10-12 10-12 10-12 10-12 10-12 . 6-14 . 6-14 . 6-14 . 6-14 . 6-14 . 6-14 . 6-15 1010101010105 5 5 5 6 6
IX-1
Index
Configuring CG and Route between SGSN and CG (contd.) Reference . . . . . . . . . . . . . . . . . 10- 7 CG . . . . . . . . . . . . . . . . . . . 10- 7 SGSN-to-CG Route . . . . . . . . . . . 10- 8 Configuring Charging Behavior . . . . . . . . 10-37 Description . . . . . . . . . . . . . . . . 10-37 Data preparations . . . . . . . . . . . . 10-37 Preset conditions . . . . . . . . . . . . 10-37 Example. . . . . . . . . . . . . . . . . . 10-37 Procedure . . . . . . . . . . . . . . . . . 10-37 Reference . . . . . . . . . . . . . . . . . 10-37 Configuring Charging Characteristic Parameters and Default Charging Characteristics . . . . . . . 10- 9 Description . . . . . . . . . . . . . . . . 10- 9 Data preparations . . . . . . . . . . . . 10- 9 Preset conditions . . . . . . . . . . . . 10- 9 Example. . . . . . . . . . . . . . . . . . 10- 9 Procedure . . . . . . . . . . . . . . . . . 10- 9 Reference . . . . . . . . . . . . . . . . . 10-10 Charging characteristics . . . . . . . . . 10-10 Default charging characteristics . . . . . . 10-11 Configuring Clock . . . . . . . . . . . . . . . 2-21 Description . . . . . . . . . . . . . . . . . 2-21 Data preparations . . . . . . . . . . . . . 2-21 Preset conditions . . . . . . . . . . . . . 2-21 Example. . . . . . . . . . . . . . . . . . . 2-21 Procedure . . . . . . . . . . . . . . . . . . 2-21 Reference . . . . . . . . . . . . . . . . . . 2-22 Configuring Control Plane of Iu Interface . . . . 4- 9 Description . . . . . . . . . . . . . . . . . 4- 9 Data preparations . . . . . . . . . . . . . 4-10 Preset conditions . . . . . . . . . . . . . 4- 9 Example. . . . . . . . . . . . . . . . . . . 4-11 Procedure . . . . . . . . . . . . . . . . . . 4-11 Reference . . . . . . . . . . . . . . . . . . 4-14 Broadband SS7 . . . . . . . . . . . . . . 4-14 Configure mapping relation between UICP and RNC . . . . . . . . . . . . . . . . . . . 4-15 Configure RNC . . . . . . . . . . . . . . 4-15 Configuring Ga Interface Parameters . . . . . 10- 3 Description . . . . . . . . . . . . . . . . 10- 3 Data Preparations . . . . . . . . . . . . 10- 3 Preset Conditions . . . . . . . . . . . . 10- 3 Example. . . . . . . . . . . . . . . . . . 10- 3 Procedure . . . . . . . . . . . . . . . . . 10- 3 Reference . . . . . . . . . . . . . . . . . 10- 3 CDR protocol version . . . . . . . . . . 10- 3 CDR resending parameters . . . . . . . . 10- 4 Hard disk alarm parameters. . . . . . . . 10- 4 Configuring GTP Protocol Parameters . . . . . . 5- 8 Description . . . . . . . . . . . . . . . . . 5- 8 Data preparation . . . . . . . . . . . . . . 5- 8 Preset conditions . . . . . . . . . . . . . 5- 8
Configuring GTP Protocol Parameters (contd.) Example. . . . . . . . . . . . . . . . . . . 5- 9 Procedure . . . . . . . . . . . . . . . . . . 5- 9 Reference . . . . . . . . . . . . . . . . . . 5- 9 Configuring IP Address of GGSN supporting MIP or DHCP . . . . . . . . . . . . . . . . . . . . . 8- 9 Description . . . . . . . . . . . . . . . . . 8- 9 Data preparations . . . . . . . . . . . . . 8- 9 Preset conditions . . . . . . . . . . . . . 8- 9 Example. . . . . . . . . . . . . . . . . . . 8- 9 Procedure . . . . . . . . . . . . . . . . . . 8- 9 Reference . . . . . . . . . . . . . . . . . . 8-10 Configuring IPSec . . . . . . . . . . . . . . . 5-16 Description . . . . . . . . . . . . . . . . . 5-16 Data preparation . . . . . . . . . . . . . . 5-16 Preset conditions . . . . . . . . . . . . . 5-16 Example. . . . . . . . . . . . . . . . . . . 5-18 To create IPSec Dynamic security Policy . . 5-19 To create isakmp security policy: . . . . . . 5-18 To create manual security policy . . . . . . 5-18 Procedure . . . . . . . . . . . . . . . . . . 5-17 Create IPSec Dynamic security Policy: . . . 5-17 Create isakmp security policy: . . . . . . . 5-17 Create manual security policy: . . . . . . . 5-17 Reference . . . . . . . . . . . . . . . . . . 5-19 IPSec . . . . . . . . . . . . . . . . . . . 5-19 Preparation for IPSec Configuration. . . . . 5-21 Preparation for IPSec Configuration - IKE Security Mechanism . . . . . . . . . . . . . . . . 5-22 Preparation for IPSec Configuration - IPSec and IKE. . . . . . . . . . . . . . . . . . . . 5-22 Preparation for IPSec Configuration - Specify data flow and security gateways to be configured . . . . . . . . . . . . . . . . 5-21 Preparation for IPSec Configuration - Specify key and security parameter index (SPI) . . . . . 5-22 Preparation for IPSec Configuration - Specify negotiation mode for Security Association establishment . . . . . . . . . . . . . . . 5-21 Preparation for IPSec Configuration - Specify security protocol, algorithm and encapsulation format . . . . . . . . . . . . . . . . . . 5-22 Some Concepts Related to IPSec Implementation . . . . . . . . . . . . . . 5-19 Configuring LCS . . . . . . . . . . . . . . . . 9- 6 Description . . . . . . . . . . . . . . . . . 9- 6 Data preparations . . . . . . . . . . . . . 9- 6 Preset conditions . . . . . . . . . . . . . 9- 6 Example. . . . . . . . . . . . . . . . . . . 9- 7 Procedure . . . . . . . . . . . . . . . . . . 9- 7 Reference . . . . . . . . . . . . . . . . . . 9- 8 Delayed location. . . . . . . . . . . . . . 9- 9
IX-2
68P02904W52-B 31-Jan-2005
Index
Configuring LCS (contd.) Reference (contd.) LCS parameters . . . . . . . . . . . . . . 9- 8 Location calculation . . . . . . . . . . . . 9- 8 Mapping relations between GMLC and LCS CLIENT . . . . . . . . . . . . . . . . . 9- 9 Configuring Link and Management Entity . . . . 6- 3 Description . . . . . . . . . . . . . . . . . 6- 3 Data preparation . . . . . . . . . . . . . . 6- 4 Preset conditions . . . . . . . . . . . . . 6- 3 Example. . . . . . . . . . . . . . . . . . . 6- 4 Procedure . . . . . . . . . . . . . . . . . . 6- 4 Reference . . . . . . . . . . . . . . . . . . 6- 6 Configure BC . . . . . . . . . . . . . . . 6- 6 Configure E1/T1. . . . . . . . . . . . . . 6- 6 NS-VC . . . . . . . . . . . . . . . . . . 6- 7 NSE . . . . . . . . . . . . . . . . . . . 6- 8 PVC . . . . . . . . . . . . . . . . . . . 6- 7 Configuring Local Office . . . . . . . . . . . . 3- 3 Description . . . . . . . . . . . . . . . . . 3- 3 Data preparations . . . . . . . . . . . . . 3- 3 Preset conditions . . . . . . . . . . . . . 3- 3 Example. . . . . . . . . . . . . . . . . . . 3- 3 Procedure . . . . . . . . . . . . . . . . . . 3- 3 Reference . . . . . . . . . . . . . . . . . . 3- 4 Configuring MAP (Gr/Gd/Ge/Gf/Lg interface). . . . . . . . . . . . . . . . . . . . . . 3-24 Description . . . . . . . . . . . . . . . . . 3-24 Data Preparation . . . . . . . . . . . . . . 3-24 Preset Conditions . . . . . . . . . . . . . 3-24 Example. . . . . . . . . . . . . . . . . . . 3-24 Procedure . . . . . . . . . . . . . . . . . . 3-24 Reference . . . . . . . . . . . . . . . . . . 3-25 Configure MAP zone code table . . . . . . 3-25 MAP . . . . . . . . . . . . . . . . . . . 3-25 Configuring Mapping between PDP Type and APN NI . . . . . . . . . . . . . . . . . . . . . . . 8- 6 Description . . . . . . . . . . . . . . . . . 8- 6 Data preparations . . . . . . . . . . . . . 8- 6 Preset conditions . . . . . . . . . . . . . 8- 6 Example. . . . . . . . . . . . . . . . . . . 8- 6 Procedure . . . . . . . . . . . . . . . . . . 8- 6 Reference . . . . . . . . . . . . . . . . . . 8- 6 Configuring MTP Data . . . . . . . . . . . . . 3- 5 Description . . . . . . . . . . . . . . . . . 3- 5 Data preparations . . . . . . . . . . . . . 3- 6 Preset conditions . . . . . . . . . . . . . 3- 5 Example. . . . . . . . . . . . . . . . . . . 3- 7 Procedure . . . . . . . . . . . . . . . . . . 3- 7 Reference . . . . . . . . . . . . . . . . . . 3- 8 Load sharing of SS7 signaling network . . . 3-11 Mask setting principles. . . . . . . . . . . 3-13 MTP Destination Signaling Point . . . . . . 3- 8 MTP link set . . . . . . . . . . . . . . . 3- 9 MTP signaling link . . . . . . . . . . . . 3-10 68P02904W52-B 31-Jan-2005
Configuring MTP Data (contd.) Reference (contd.) MTP signaling route . . . . . . . . Configuring OMC-S/T 2.0 IP Address . . Description . . . . . . . . . . . . . Data preparations . . . . . . . . . Preset conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Configuring OSPF . . . . . . . . . . . Description . . . . . . . . . . . . . Data preparation . . . . . . . . . . Preset conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . OSPF Packets . . . . . . . . . . . Process of OSPF Route Calculation . Related Concepts . . . . . . . . . Configuring Paging Parameters . . . . . Description . . . . . . . . . . . . . Data preparations . . . . . . . . . Preset Conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Configuring PLMN. . . . . . . . . . . Description . . . . . . . . . . . . . Data preparations . . . . . . . . . Preset Conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Configuring Port . . . . . . . . . . . . Description . . . . . . . . . . . . . Data preparations . . . . . . . . . Preset conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . ATM . . . . . . . . . . . . . . . E1/T1 . . . . . . . . . . . . . . . FE/GE . . . . . . . . . . . . . . VA . . . . . . . . . . . . . . . . Configuring Protocol Parameters . . . . Description . . . . . . . . . . . . . Data preparation . . . . . . . . . . Preset conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . BSSGP . . . . . . . . . . . . . . LLC . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. 3- 9 11- 8 11- 8 11- 8 11- 8 11- 8 11- 8 11- 8 . 5-24 . 5-24 . 5-24 . 5-24 . 5-24 . 5-24 . 5-25 . 5-25 . 5-25 . 5-26 . 7-10 . 7-10 . 7-10 . 7-10 . 7-11 . 7-10 . 7-11 . 7- 8 . 7- 8 . 7- 8 . 7- 8 . 7- 8 . 7- 8 . 7- 8 . 2-18 . 2-18 . 2-18 . 2-18 . 2-19 . 2-18 . 2-19 . 2-20 . 2-20 . 2-20 . 2-20 . 6- 9 . 6- 9 . 6- 9 . 6- 9 . 6- 9 . 6- 9 . 6-10 . 6-12 . 6-11
IX-3
Index
Configuring Protocol Parameters (contd.) Reference (contd.) NS . . . . . . . . . . . . . . . . . SNDCP . . . . . . . . . . . . . . . Configuring QoS Parameters . . . . . . . Description . . . . . . . . . . . . . . Data preparation . . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . CBWFQ . . . . . . . . . . . . . . DSCP Remarking . . . . . . . . . . Mapping relation between QoS and DSCP . . . . . . . . . . . . . . . . WRED . . . . . . . . . . . . . . . Configuring Rack . . . . . . . . . . . . Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Configuring Remote Maintenance Gateway Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Configuring RIP . . . . . . . . . . . . . Description . . . . . . . . . . . . . . Data preparation . . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Configuring Shared PLMN OI. . . . . . . Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Configuring SM Parameters . . . . . . . . Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . APN resolution . . . . . . . . . . . Optional functions in SM. . . . . . . QoS . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
6-12 6-10 5-10 5-10 5-10 5-10 5-10 5-10 5-11 5-11 5-15 5-14 5-12 2- 3 2- 3 2- 3 2- 3 2- 3 2- 3 2- 4 11- 5 11- 5 11- 5 11- 5 11- 5 11- 5 11- 5 5-28 5-28 5-28 5-28 5-28 5-28 5-29 8- 8 8- 8 8- 8 8- 8 8- 8 8- 8 8- 8 8- 3 8- 3 8- 3 8- 3 8- 3 8- 3 8- 3 8- 5 8- 4 8- 4
. . . . . . . . . . . . . . . . . . . . . . . .
Configuring SM Parameters (contd.) Reference (contd.) RAB QoS negotiation . . . . . . . SM timers . . . . . . . . . . . . . Configuring SMS. . . . . . . . . . . . Description . . . . . . . . . . . . . Data preparations . . . . . . . . . Preset conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Configuring SNMP . . . . . . . . . . . Description . . . . . . . . . . . . . Data preparations . . . . . . . . . Preset conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Configuring Special Charging Rate Period Description . . . . . . . . . . . . . Data preparations . . . . . . . . . Preset conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Charging days in a week . . . . . . Charging holiday . . . . . . . . . Tariff period . . . . . . . . . . . . Configuring Subrack . . . . . . . . . . Description . . . . . . . . . . . . . Data preparations . . . . . . . . . Preset conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Configuring System Basic Information. . Description . . . . . . . . . . . . . Data preparations . . . . . . . . . Preset conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Configuring System Time . . . . . . . . Description . . . . . . . . . . . . . Data preparations . . . . . . . . . Preset conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Configuring Timers. . . . . . . . . . . Description . . . . . . . . . . . . . Data preparations . . . . . . . . . Preset Conditions . . . . . . . . . Example. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . .
8- 5 8- 4 9- 2 9- 2 9- 2 9- 2 9- 2 9- 2 9- 2 11- 6 11- 6 11- 6 11- 6 11- 6 11- 6 11- 7 10-39 10-39 10-39 10-39 10-39 10-39 10-40 10-40 10-40 10-40 . 2- 5 . 2- 5 . 2- 5 . 2- 5 . 2- 5 . 2- 5 . 2- 6 11- 3 11- 3 11- 3 11- 3 11- 3 11- 3 11- 3 11- 9 11- 9 11- 9 11- 9 11-10 11- 9 11-10 . 7- 6 . 7- 6 . 7- 6 . 7- 6 . 7- 6
IX-4
68P02904W52-B 31-Jan-2005
Index
Configuring Timers (contd.) Procedure . . . . . . . . . . . . . . . . . . 7- 6 Reference . . . . . . . . . . . . . . . . . . 7- 7 Configuring User Plane of Iu Interface . . . . . . 4- 3 Description . . . . . . . . . . . . . . . . . 4- 3 Data preparations . . . . . . . . . . . . . 4- 3 Preset conditions . . . . . . . . . . . . . 4- 3 Example. . . . . . . . . . . . . . . . . . . 4- 4 Add an normal IPOA PVC between the SGSN and an RNC . . . . . . . . . . . . . . . . . . 4- 4
Configuring User Plane of Iu Interface (contd.) Example (contd.) Add two RNCOA IPOA PVCs between the SGSN and an RNC . . . . . . . . . . . . . . . . 4- 5 Procedure . . . . . . . . . . . . . . . . . . 4- 4 Reference . . . . . . . . . . . . . . . . . . 4- 5 IP address for VA port and forward engine and local IP address for VA port . . . . . . . . . . . 4- 6 IPOA PVC . . . . . . . . . . . . . . . . 4- 5 PVC Traffic parameters . . . . . . . . . . 4- 7
Data Configuration Modes . . . . . . . . . . . 1- 5 Data to Be Configured and Data Configuration Flow . . . . . . . . . . . . . . . . . . . . . 1- 2 Detaching Inactive Subscribers . . . . . . . . 12- 9 Description . . . . . . . . . . . . . . . . 12- 9 Data preparations . . . . . . . . . . . . 12- 9 Preset conditions . . . . . . . . . . . . 12- 9
Detaching Inactive Subscribers (contd.) Example. . . . . . . . . . . . . . Overview of the Function . . . . . . Procedure . . . . . . . . . . . . . Reference . . . . . . . . . . . . . Devices sensitive to static . . . . . . . Special handling techniques. . . . .
. . . . . .
. . . . . .
. . . . . .
. 12-10 . 12- 9 . 12- 9 . 12-10 . . . 14 . . . 14
Feature Configuration Overview. . . . . . . .
12- 2
Gb Interface Configuration Overview General cautions . . . . . . . . . . Caution labels . . . . . . . . . . Specific cautions . . . . . . . . . Fibre optics . . . . . . . . . . Static discharge . . . . . . . . General information . . . . . . . . Cross references . . . . . . . . . Data encryption . . . . . . . . . Feature references . . . . . . . . Purpose . . . . . . . . . . . . . Text conventions . . . . . . . . . Input . . . . . . . . . . . . . Output . . . . . . . . . . . . Special key sequences . . . . . General warnings. . . . . . . . . . Specific warnings . . . . . . . . Battery supplies . . . . . . . . Electric shock . . . . . . . . . Laser radiation . . . . . . . . Lifting equipment . . . . . . . Lithium batteries . . . . . . . Parts substitution . . . . . . . 68P02904W52-B 31-Jan-2005
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
6- 2 . 13 . 13 . 13 . 13 . 13 . 3 . 4 . 5 . 3 . 3 . 5 . 5 . 5 . 5 . 9 . 9 . 12 . 10 . 11 . 11 . 12 . 12
General warnings (contd.) Specific warnings (contd.) Potentially hazardous voltage . . . . RF radiation . . . . . . . . . . . . Warning labels . . . . . . . . . . . . Gn/Gp Interface Configuration Overview Gn/Gp Interface Route Configuration . . Description . . . . . . . . . . . . . Data preparation . . . . . . . . . . Preset conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . Configure IP route . . . . . . . . . Configure IPOA PVC . . . . . . . GPRS Second Authentication in Attach . Description . . . . . . . . . . . . . Data preparations . . . . . . . . . Preset conditions . . . . . . . . . Example. . . . . . . . . . . . . . . Overview of the Function . . . . . . . Procedure . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . .
. 10 . 11 . 9 5- 2 5- 3 5- 3 5- 3 5- 3 5- 3 5- 3 5- 4 5- 5 5- 5 12-13 12-13 12-13 12-13 12-14 12-13 12-13
IX-5
Index
GPRS Second Authentication in RAU (contd.) Reference . . . . . . . . . . . . . . . GPRS Second Authentication in RAU . . . Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . .
. . . . .
. . . . .
12-14 12-15 12-15 12-15 12-15
GPRS Second Authentication in RAU (contd.) Example. . . . . . . . . . . . . . . . Overview of the Function . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . .
. . . .
. . . .
12-16 12-15 12-15 12-16
Hardware Configuration Overview . . . . . . . 2- 2
Issue status of this manual (contd.) Issue status of this manual . . . . . . . . . . . . Incorporation of CDCNs . . . . . . . . . . . . Resolution of service requests. . . . . . . . . .
2 2 2
Issue status of this manual (contd.) Version information . . . . . . . . . . . . . . 2 Iu interface Configuration Overview . . . . . . . 4- 2
Manual amendment. . . . . CDCN amendment record CDCN availability . . . . CDCN instructions . . . . GMR availability . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
16 18 16 17 16
MM Configuration Overview . . . . . . . . . . 7- 2 Motorola manual set . . . . . . . . . . . . . . . 15 Ordering manuals and CD-ROMs . . . . . . . . 15
Not detaching inactive subscribers of the specified APN (contd.) Not detaching inactive subscribers of the specified APN. . . . . . . . . . . . . . . . . . . . . 12-11 Description . . . . . . . . . . . . . . . . 12-11 Data preparations . . . . . . . . . . . . 12-11 Preset conditions . . . . . . . . . . . . 12-11 Example. . . . . . . . . . . . . . . . . . 12-12
Not detaching inactive subscribers of the specified APN (contd.) Overview of the Function . . . . . . . . . . 12-11 Procedure . . . . . . . . . . . . . . . . . 12-11 Reference . . . . . . . . . . . . . . . . . 12-12
Points for Attention. . . . . . . . . . . . . . . 1- 4
RAI IE in Gn (contd.) RAI IE in Gn. . . . . . . . . . . . . . . . . IX-6
12- 7 68P02904W52-B 31-Jan-2005
Index
RAI IE in Gn (contd.) Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Overview of the Function . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Rejecting GPRS Subscribers Attach by APNNI . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . Data preparations . . . . . . . . . . Preset conditions . . . . . . . . . . Example. . . . . . . . . . . . . . . . Overview of the Function . . . . . . . . Procedure . . . . . . . . . . . . . . . Reference . . . . . . . . . . . . . . . Rejecting GPRS Subscribers Attach by IMSI
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
12121212121212-
7 7 7 7 7 7 8
12-17 12-17 12-17 12-17 12-18 12-17 12-18 12-18 12-19
Rejecting GPRS Subscribers Attach by IMSI (contd.) Description . . . . . . . . . . . . . . . . 12-19 Data preparations . . . . . . . . . . . . 12-19 Preset conditions . . . . . . . . . . . . 12-19 Example. . . . . . . . . . . . . . . . . . 12-20 Overview of the Function . . . . . . . . . . 12-19 Procedure . . . . . . . . . . . . . . . . . 12-20 References. . . . . . . . . . . . . . . . . 12-20 Reporting safety issues . . . . . . . . . . . . . . 6 Procedure . . . . . . . . . . . . . . . . . . . 6 Roaming Barred by IMSI . . . . . . . . . . . 12- 3 Description . . . . . . . . . . . . . . . . 12- 3 Data preparations . . . . . . . . . . . . 12- 3 Preset conditions . . . . . . . . . . . . 12- 3 Example. . . . . . . . . . . . . . . . . . 12- 4 Overview of the Function . . . . . . . . . . 12- 3 Procedure . . . . . . . . . . . . . . . . . 12- 3 Reference . . . . . . . . . . . . . . . . . 12- 4
SCCP Configuration . . . . Description . . . . . . . Data preparations . . . Preset conditions . . . Example. . . . . . . . . Procedure . . . . . . . . Reference . . . . . . . . Common GTs for SGSN GT Translation . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
3-15 3-15 3-15 3-15 3-16 3-16 3-17 3-22 3-19
SCCP Configuration (contd.) Reference (contd.) IMSI-GT conversion . . . . SCCP DSP . . . . . . . . SCCP Subsystem . . . . . SM Configuration Overview . . SS7 Configuration Overview . . System Configuration Overview .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . .
3-23 3-17 3-18 8- 2 3- 2 11- 2
Warnings and cautions . . . . . . Cautions. . . . . . . . . . . . Definition of Caution . . . . Example and format . . . . . Failure to comply with warnings
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
7 7 8 8 7
Warnings and cautions (contd.) Warnings . . . . . . . . . . . . . . . . . . . Definition of Warning . . . . . . . . . . . . Example and format . . . . . . . . . . . . .
7 7 7
68P02904W52-B 31-Jan-2005
IX-7

Installation and Configuration C-SGSN-1

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Installation and Configuration C-SGSN-1

Încărcat de

Drepturi de autor:

Formate disponibile

Installation and Configuration: C-SGSN Data Configuration

31-Jan-2005 Motorola, Inc. All Rights Reserved

Installation and Configuration: C-SGSN Data Configuration

Chapter 2: Hardware Configuration

Chapter 3: SS7 Configuration

Installation and Configuration: C-SGSN Data Configuration

Chapter 4: Iu interface Configuration (3G)

Chapter 5: Gn/Gp Interface Configuration

Chapter 6: Gb Interface Configuration (2.5G)

Installation and Configuration: C-SGSN Data Configuration

Chapter 9: Service Configuration

Chapter 10: Charging Configuration

10-37 10-37 10-37 10-39 10-39 10-39 10-39 10-40

Chapter 11: System Configuration

Chapter 12: Feature Configuration

This page intentionally left blank.

This page intentionally left blank.

This page intentionally left blank.

About This Manual

Installation and Configuration: C-SGSN Data Configuration

Issue status of this manual

Issue status of this manual

Resolution of service requests

Service Request N/A

Special key sequences

Reporting safety issues

Reporting safety issues

Warnings and cautions

Warnings and cautions

Example and format

Failure to comply with warnings

Warnings and cautions

Example and format

Potentially hazardous voltage

Motorola GSM equipment does not utilise high voltages.

Devices sensitive to static

Devices sensitive to static

Special handling techniques

Motorola manual set

Motorola manual set

Ordering manuals and CD-ROMs

CDCN amendment record

Data to Be Configured and Data Configuration Flow

Data to Be Configured and Data Configuration Flow

Iu Configuration (Skip this step for 2.5G)

Gn/Gp Interface Configuration

Gb Configuration (Skip this step for 3G)

Installation and Configuration: C-SGSN Data Configuration

Data to Be Configured and Data Configuration Flow

Points for Attention

Points for Attention

Installation and Configuration: C-SGSN Data Configuration

Data Configuration Modes

Data Configuration Modes

Data Configuration Modes

This page intentionally left blank.

Hardware Configuration Overview

Chapter 2: Hardware Configuration

Hardware Configuration Overview

Installation and Configuration: C-SGSN Data Configuration

Chapter 2: Hardware Configuration

Installation and Configuration: C-SGSN Data Configuration

Chapter 2: Hardware Configuration