installation and configuration c-sgsn-1

Installation and Configuration: C-SGSNData Configuration

© 31-Jan-2005 Motorola, Inc. 68P02904W52-BAll Rights Reserved CONTROLLED INTRODUCTION 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 tocopy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola productsdescribed in this document may not be copied or reproduced in any manner without the express written permission of Motorola. Furthermore, the purchaseof Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the copyrights, patents or patentapplications 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 inaccordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized copies is prohibited by law. No part ofthe 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 omissionsin this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to any products described herein to improvereliability, 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 tonotify 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.

CONTROLLED INTRODUCTION 31-Jan-2005

Tableof

Contents

Contents■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

Installation and Configuration: C-SGSN Data ConfigurationIssue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Version information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Resolution of service requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Incorporation of CDCNs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Feature references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Data encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Failure to comply with warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Warning labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Specific warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Caution labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Specific cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Special handling techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Motorola manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Ordering manuals and CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Manual amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16GMR availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16CDCN availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16CDCN instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17CDCN amendment record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 1: OverviewData to Be Configured and Data Configuration Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 2Points for Attention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 4Data Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 5

68P02904W52-B i31-Jan-2005 CONTROLLED INTRODUCTION

Contents

Chapter 2: Hardware ConfigurationHardware Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 2Configuring Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 3

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 3Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 3Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 3Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 4

Configuring Subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 5Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 5Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 5Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 5Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 6

Configuring Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 7Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 7Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 8Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Configuring Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Configuring Clock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Chapter 3: SS7 ConfigurationSS7 Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 2Configuring Local Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 3


Configuring MTP Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 5Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 5Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 7Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 7Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 8

SCCP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

Configuring MAP (Gr/Gd/Ge/Gf/Lg interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

Configuring BSSAP+ (Gs interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

ii 68P02904W52-BCONTROLLED INTRODUCTION 31-Jan-2005

Installation and Configuration: C-SGSN Data Configuration Contents

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

Chapter 4: Iu interface Configuration (3G)Iu interface Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 2Configuring User Plane of Iu Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 3


Configuring Control Plane of Iu Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 9Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 9Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Chapter 5: Gn/Gp Interface ConfigurationGn/Gp Interface Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 2Gn/Gp Interface Route Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 3


Configure DNS/HOSTFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 6Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 6Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 6Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 6Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 7

Configuring GTP Protocol Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 8Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 8Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 9Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 9Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 9

Configuring QoS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Configuring IPSec. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19

Configuring OSPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25

Configuring RIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29

68P02904W52-B iii31-Jan-2005 CONTROLLED INTRODUCTION

Contents

Chapter 6: Gb Interface Configuration (2.5G)Gb Interface Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 2Configuring Link and Management Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 3


Configuring Protocol Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 9Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 9Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 9Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 9Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Configuring Cell Reference Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15

Chapter 7: MM ConfigurationMM Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 2Configuring Authentication and Ciphering Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 3


Configuring Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 6Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 6Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 6Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 6Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 7

Configuring PLMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 8Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 8Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 8Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 8Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 8

Configuring Paging Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11

Chapter 8: SM ConfigurationSM Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 2Configuring SM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 3


Configuring Mapping between PDP Type and APN NI. . . . . . . . . . . . . . . . . . . . . . . . . . 8- 6Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 6Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 6Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 6

iv 68P02904W52-BCONTROLLED INTRODUCTION 31-Jan-2005

Installation and Configuration: C-SGSN Data Configuration Contents

Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 6Configuring Shared PLMN OI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 8


Configuring IP Address of GGSN supporting MIP or DHCP . . . . . . . . . . . . . . . . . . . . . . . 8- 9Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 9Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 9Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 9Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10

Chapter 9: Service ConfigurationConfiguring SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 2


Configuring CAMEL service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 4Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 4Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 4Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 5Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 5

Configuring LCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 6Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 6Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 7Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 7Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 8

Chapter 10: Charging ConfigurationCharging Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 2Configuring Ga Interface Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 3


Configuring CG and Route between SGSN and CG . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 5Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 5Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 6Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 6Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 7

Configuring Charging Characteristic Parameters and Default Charging Characteristics . . . . . . . . . . . 10- 9Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 9Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 9Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 9Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10

Configuring CDR Optional Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12

Configuring Charging Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37

68P02904W52-B v31-Jan-2005 CONTROLLED INTRODUCTION

Contents

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37

Configuring Special Charging Rate Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-40

Chapter 11: System ConfigurationSystem Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 2Configuring System Basic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 3


Configuring Remote Maintenance Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 5Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 5Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 5Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 5Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 5

Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 6Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 6Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 6Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 6Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 7

Configuring OMC-S/T 2.0 IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 8Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 8Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 8Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 8Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 8

Configuring System Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 9Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 9Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 9Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10

Chapter 12: Feature ConfigurationFeature Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 2Roaming Barred by IMSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 3

Overview of the Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 3Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 3Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 3Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 4Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 4

Choosing GGSN by IMSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 5Overview of the Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 5Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 5Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 5Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 6Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 6

RAI IE in Gn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 7Overview of the Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 7

vi 68P02904W52-BCONTROLLED INTRODUCTION 31-Jan-2005

Contents


Detaching Inactive Subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 9Overview of the Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 9Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 9Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 9Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

Not detaching inactive subscribers of the specified APN . . . . . . . . . . . . . . . . . . . . . . . . . 12-11Overview of the Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12

GPRS Second Authentication in Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13Overview of the Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14

GPRS Second Authentication in RAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15Overview of the Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16

Rejecting GPRS Subscribers Attach by APNNI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17Overview of the Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18

Rejecting GPRS Subscribers Attach by IMSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19Overview of the Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20

68P02904W52-B vii31-Jan-2005 CONTROLLED INTRODUCTION

Contents

This page intentionally left blank.

viii 68P02904W52-BCONTROLLED INTRODUCTION 31-Jan-2005

Listof

Figures

List of Figures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

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

68P02904W52-B ix31-Jan-2005 CONTROLLED INTRODUCTION

List of Figures


x 68P02904W52-BCONTROLLED INTRODUCTION 31-Jan-2005

Listof

Tables

List of Tables■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

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

68P02904W52-B xi31-Jan-2005 CONTROLLED INTRODUCTION

List of Tables


xii 68P02904W52-BCONTROLLED INTRODUCTION 31-Jan-2005

AboutThisManual

Installation and Configuration: C-SGSNData Configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02904W52-B 131-Jan-2005 CONTROLLED INTRODUCTION

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

Manualissue Date of issue Remarks

A 02 Jul 2004 This is a new manual.

B 31 Jan 2005 CONTROLLED INTRODUCTION

Resolution of service requests

The following Service Requests are now resolved in this manual:

Table 2 Service requests resolved in this manual

ServiceRequest

GMRNumber Remarks

N/A N/A Original issue - Controlled introduction

Incorporation of CDCNs

The following CDCNs are now incorporated in this manual:

Table 3 CDCNs incorporated in this manual

CDCN GMRNumber Remarks

N/A N/A

2 68P02904W52-BCONTROLLED INTRODUCTION 31-Jan-2005

General information

General information■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

• Motorola disclaims all liability whatsoever, implied or express, for any risk of damage, lossor reduction in system performance arising directly or indirectly out of the failure of thecustomer, or anyone acting on the customers behalf, to abide by the instructions, systemparameters or recommendations made in this manual

• If this manual was obtained when attending a Motorola training course, it will not be updatedor amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was suppliedunder normal operational circumstances, to support a major software release, then correctionswill 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 isrecommended that all personnel engaged in such activities be properly trained by Motorola.

Failure to comply with Motorola’s operation, installation and maintenanceinstructions 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, althoughthey 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 releasedat 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 arethe 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 includesthe entry feature which is followed by a list of the RDB or RDP numbers for the released features, withpage references and hot links in electronic copy.


General information

The tags have the format: {nnnn} or {nnnnn}

Heading1 Heading2Where: is:

{nnnn} the RDB number

{nnnnn} the RDP number

The tags are positioned in text as follows:

New and amended feature information Tag position in textNew sentence/s or new or amended text. Immediately before the affected text.

Complete new blocks of text as follows:

• Full sections under a main heading

• Full paragraphs under subheadings

Immediately after the headings as follows:

• Main heading

• Subheading

New or amended complete Figures and Tables After the Figure or Table number and beforethe title text.

Warning, Caution and Note boxes. Immediately before the affected text in the box.

General command syntax, operator input ordisplays (in special fonts).

On a separate line immediately above theaffected item.

For a list of Roadmap numbers and the RDB or RDP numbers of the features included in this softwarerelease, refer to the manual System Information: GSM Overview (68P02901W01), or to the manual SystemInformation: 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 referencesare emphasised blue in text.

This manual is divided into uniquely identified and numbered chapters that, in turn, are divided intosections. Sections are not numbered, but are individually named at the top of each page, and are listed inthe table of contents.


General information

Data encryption

In order to avoid electronic eavesdropping, data passing between certain elements in the GSM and GPRSnetwork 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 someparts 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, limitationson the encryption included in the particular software being delivered, are covered in the Release Notesthat accompany the individual software release.

Text conventions

The following conventions are used in the Motorola cellular infrastructure manuals to represent keyboardinput text, screen output text and special key sequences.

InputCharacters typed in at the keyboard are shown like this.

OutputMessages, prompts, file listings, directories, utilities, and environmentalvariables that appear on the screen are shown like this.

Special key sequencesSpecial key sequences are represented as follows:

Heading1 Heading2CTRL-c Press the Control and c keys at the same time.

ALT-f Press the Alt and f keys at the same time.

¦ Press the pipe symbol key.

CR or RETURN Press the Return key.


Reporting safety issues

Reporting safety issues■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Whenever a safety issue arises, carry out the following procedure in all instances. Ensure that all sitepersonnel are familiar with this procedure.

Procedure

Whenever a safety issue arises:

Procedure 1 Safety issue reporting

Heading1 Heading21 Make the equipment concerned safe, for example by removing power.

2 Make no further attempt to adjust or rectify the equipment.

3 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 writtenreport by fax, Swindon +44 (0)1793 430987 or China +86 10 68423633 (fax).

4 Collect evidence from the equipment under the guidance of the Customer NetworkResolution Centre.


Warnings and cautions

Warnings and cautions■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following describes how warnings and cautions are used in this manual and in all manuals of thisMotorola manual set.

Warnings

A definition and example follow below:

Definition of WarningA warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, or illhealth. 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. Laserradiation can come from either the data in/out connectors or unterminated fibreoptic 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 describedin the Motorola manuals. Failure to comply with these warnings, or with specific warnings elsewhere inthe Motorola manuals, or on the equipment itself, violates safety standards of design, manufacture andintended use of the equipment. Motorola assumes no liability for the customer’s failure to comply withthese requirements.

Cautions

A definition and example follow below:


Warnings and cautions

Definition of CautionA caution means that there is a possibility of damage to systems, software or individual items of equipmentwithin 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 forcalibration to be carried out.


General warnings

General warnings■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Observe the following specific warnings during all phases of operation, installation and maintenance ofthe 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, violatessafety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability forthe customer’s failure to comply with these requirements.

Warning labels

Warnings particularly applicable to the equipment are positioned on the equipment. Personnel working withor operating Motorola equipment must comply with any warning labels fitted to the equipment. Warninglabels 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 intoprocedures as applicable.

These must be observed by all personnel at all times when working with the equipment, as must any otherwarnings given in text, in the illustrations and on the equipment.


General warnings

Potentially hazardous voltage

This equipment operates from a potentially hazardous voltage of 230 V a.c. singlephase or 415 V a.c. three phase supply. To achieve isolation of the equipment fromthe 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 andpull 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. Itcan 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 fortrained first aid or medical assistance IMMEDIATELY.

If the casualty is also suffering from burns, flood the affected area with cold water to cool, until trainedfirst aid or medical assistance arrives.


General warnings

RF radiation

High RF potentials and electromagnetic fields are present in this equipmentwhen in operation. Ensure that all transmitters are switched off when anyantenna connections have to be changed. Do not key transmitters connectedto 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 toRadio Frequency Electromagnetic Fields, 3 kHz to 300 GHz

• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10kHz to 300 GHz).

Laser radiation

Do not look directly into fibre optic cables or optical data in/out connectors. Laserradiation can come from either the data in/out connectors or unterminated fibreoptic cables connected to data in/out connectors.

Lifting equipment

When dismantling heavy assemblies, or removing or replacing equipment, acompetent responsible person must ensure that adequate lifting facilities areavailable. Where provided, lifting frames must be used for these operations.

When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible personmust ensure that adequate lifting facilities are available. Where provided, lifting frames must be used forthese operations. When equipment has to be manhandled, reference must be made to the Manual Handlingof Loads Regulations 1992 (UK) or to the relevant manual handling of loads legislation for the country inwhich the equipment is used.


General warnings

Parts substitution

Do not install substitute parts or perform any unauthorized modification ofequipment, because of the danger of introducing additional hazards. ContactMotorola if in doubt to ensure that safety features are maintained.

Battery supplies

Do not wear earth straps when working with stand-by battery supplies. Useonly insulated tools.

Lithium batteries

Lithium batteries, if subjected to mistreatment, may burst and ignite. Defectivelithium batteries must not be removed or replaced. Any boards containingdefective lithium batteries must be returned to Motorola for repair.

Contact your local Motorola office for how to return defective lithium batteries.


General cautions

General cautions■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Observe the following cautions during operation, installation and maintenance of the equipment describedin the Motorola manuals. Failure to comply with these cautions or with specific cautions elsewhere in theMotorola manuals may result in damage to the equipment. Motorola assumes no liability for the customer’sfailure to comply with these requirements.

Caution labels

Personnel working with or operating Motorola equipment must comply with any caution labels fitted to theequipment. 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 beobserved by all personnel at all times when working with the equipment, as must any other cautions givenin 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 thesection Devices sensitive to static in the preface of this manual for furtherinformation.


Devices sensitive to static

Devices sensitive to static■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of insulation that issusceptible to damage from electrostatic charge. Such a charge applied to the leads of the device couldcause irreparable damage.

These charges can be built up on nylon overalls, by friction, by pushing the hands into high insulation packingmaterial or by use of unearthed soldering irons.

MOS devices are normally despatched from the manufacturers with the leads short circuited together, forexample, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic foam. Providedthe 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 handlingthe replacement:

• Always wear an earth strap which must be connected to the electrostatic point (ESP) on theequipment.

• Leave the short circuit on the leads until the last moment. It may be necessary to replace theconductive 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 overallis preferable.

• If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic worksurfaces 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. Thesecomponents may be providing protection to the device.

When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to electrostaticdamage. However PCBs should be handled with care, preferably by their edges and not by their tracks andpins, they should be transferred directly from their packing to the equipment (or the other way around) andnever left exposed on the workbench.


Motorola manual set

Motorola manual set■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Motorola manual sets provide the information needed to operate, install and maintain the Motorolaequipment. 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. Asnapshot copy of on-line documentation is also included, though it will not be updated in line with subsequentpoint releases.

The CD-ROM does not include Release Notes or documentation supporting specialist products such asMARS 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.


Manual amendment

Manual amendment■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Changes to a manual that occur after the printing date are incorporated into the manual using either CustomerDocumentation Change Notices (CDCNs) or General Manual Revisions (GMRs).

• Small changes are published in CDCNs. These describe the changes rather than replacing largesections of the manual. They are sent directly to customers and Motorola Local Offices andare 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 68P2901W23–M.

• Major changes are effected by publishing a GMR. GMRs are also produced in order toincorporate CDCNs when the numbers applying to a particular manual become significant. Inthis 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 sameidentity as the target manual. Each GMR is identified by a number in a sequence that starts at01 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 replacementloose leaf pages.

• Motorola service web - Updated at the same time as hard copies.


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 forfuture reference.


Manual amendment

CDCN amendment record

Record the manual insertion of CDCNs in this manual in the following table:

CDCN number Incorporated by (signature) Date


Chapter

1Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

Office data serves as the basis for normal operations of SGSN. This chapter introduces the office datato be configured and the data configuration flow.

The readers of this manual should be acquainted with the basic knowledge of GPRS and WCDMA and thearchitecture and principle of Motorola C-SGSN.

68P02904W52-B 1-131-Jan-2005 CONTROLLED INTRODUCTION

Data to Be Configured and Data Configuration Flow Chapter 1: Overview

Data to Be Configured and Data Configuration Flow■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

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-BCONTROLLED INTRODUCTION 31-Jan-2005

Installation and Configuration: C-SGSN Data Configuration Data to Be Configured and Data Configuration Flow

The term 'Iu interface' in this manual refers to the Iu-PS interface, '2.5G' to the General PacketRadio Service (GPRS) system, and '3G' to the Wideband Code Division Multiple Access(WCDMA) system.

Description of this data configuration flow:

1. Hardware configuration acts as the base of other configuration. Therefore, you should performthe hardware configuration first.

2. 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 networkingmode of Motorola C-SGSN. You should perform the interface configuration starting from thelower layer to the upper layer of the protocol stack.

3. Interface configuration, MM configuration, SM configuration, service configuration, chargingconfiguration, system configuration and feature configuration are independent of one another.You may start from any configuration after the hardware configuration.

4. Figure 1-1 shows the usual data configuration flow, that is, the sequence of the chapterarrangement in this manual.


Points for Attention Chapter 1: Overview

Points for Attention■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

To ensure successful data configuration, note the following information:

1. Be familiar with the equipment hardware before the data configuration.

2. Be familiar with the requirements raised at the engineering design stage before the dataconfiguration.

3. Collect the data to be negotiated with the peer office before the data configuration. Refer tothe corresponding section in each chapter of this manual for data to be negotiated with thepeer office.


Installation and Configuration: C-SGSN Data Configuration Data Configuration Modes

Data Configuration Modes■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

• To modify the configuration file, first modify the first line as ';FFFFFFFFFFFFFFFF 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, themodification of the configuration file will not take effect.

• Before uploading the new MML.TXT, back up the old MML.TXT to the localcomputer for use upon upload failure.

• MML.txt should not include non-ADD commands, such as MOD and RMV. Youcan only carry out the MOD and RMV commands through the LM.

• After modifying the data configuration through the LM, use command SAVECFG to save the modification. Otherwise, all the modifications will get lostwhen the system restarts.

• Some modified parameters do not take effect until you restart thecorresponding 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 ofsystem data. After the edit, you need load the MML.TXT file using ADD CFG or upload it inbinary from the FTP Server to \hda0\sgsn\config in the active and standby UOMUs. Thenyou 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 LocalManager (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 othersoptional. You may also double click a command in the MML Command Navigator to popup the 'Command Input' box. At the same time, the online help about this command willdisplay in the 'Help Information' tap page.


Data Configuration Modes Chapter 1: Overview



Chapter

2Hardware Configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■


Hardware Configuration Overview Chapter 2: Hardware Configuration

Hardware Configuration Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Hardware configuration includes rack configuration, subrack configuration, board configuration, portconfiguration and clock configuration. After the hardware configuration, the system hardware can normallywork.

You shall perform hardware configuration in the following sequence:

1. Rack configuration.

2. Subrack configuration.

3. Board configuration.

4. Port configuration.

5. Clock configuration.


Installation and Configuration: C-SGSN Data Configuration Configuring Rack

Configuring Rack■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces rack configuration. After this configuration, you can configure subracks and boardsin a rack.

Description

Preset conditionsNone.

Data preparationsItem Data

Basicinformation.

Racknumber.

Placenumber.

Rownumber.

Columnnumber.

Procedure

Step Operation Command1 Add a rack. 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;


Configuring Rack Chapter 2: Hardware Configuration

Reference

The position information of a rack is useful to locate a system alarm. That is, it can help locate the rack of thealarming 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.

Row No.1

Row No.0

Column No.0 Column No.1

Place No.0

RACK NO.0 RACK NO.1

RACK NO.2 RACK NO.3


Installation and Configuration: C-SGSN Data Configuration Configuring Subrack

Configuring Subrack■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces subrack configuration. After this configuration, you can add boards to subracks.

Description

Preset conditionsA rack already exists before subrack configuration.

Data preparationsItem data

BNETsubrack.

Racknumber.

Subracknumber.

Racknumber.

Subracknumber.

URCU'sULPU slotnumber 1

URCU'sULPU portnumber 1

URCU'sULPU slotnumber 2

URCU'sULPU portnumber 2

PSMsubrack.

WDMBbinding flag.

Procedure

Step Operation Command1 Add a BNET subrack. ADD SUBRACK

2 Add a PSM 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;


Configuring Subrack Chapter 2: Hardware Configuration

Reference

The physical subracks can be divided into two types: PSM and BNET. Only one BNET subrack, but morethan 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 aPSM subrack can monitor the connected power distribution subracks. You can connect the power distributionsubracks in one rack to only one PSM subrack.


Installation and Configuration: C-SGSN Data Configuration Configuring Board

Configuring Board■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration for board information. After this configuration, boards can normallywork and you can perform operation and maintenance on boards.

Only boards in PSM subracks (except UPWR, UPMU, UALU and ULPU) and UHPUs in theBNET subrack need be configured. Other boards in the BNET subrack require no manualconfiguration and they can work properly once they are inserted and powered on.

Description

Preset conditionsThe required rack and subrack already exist before board configuration.


Basicinformation.

Subracknumber.

Slot number. Board type.

RelativeULPU slotnumber 1.

RelativeULPU portnumber 1.



Active/standbystatus.

IP addressand mask ofthe uppernetworkport.

UOMU

IP addressand mask ofthe uppernetworkport.

Board specs.





Active/standbystatus.

UCDR groupnumber.

UCDR

IP address. Board specs.

Cont.


Configuring Board Chapter 2: Hardware Configuration

Item DataURCU Active/

standbystatus.

Board specs. IP address(of theURCU in thebasic PSMsubrack).

USPU Active/standbystatus.

Board specs.

UGBI Active/standbystatus.

PMCDOWNtype.

PMCUPtype.

Board specs.

UGTP Active/standbystatus.

PMCUPtype.

IP address. Board specs.

UICP Active/standbystatus.

Board specs.

UHPU Active/standbystatus.

IP addressand mask ofFEA.

IP addressand mask ofFEB.

ULAN IP address.

UEPI/UTPI Active/standbystatus.

H.110 clocklevel.

BackupType.

Balancemode.

Procedure

1. Add UOMU/UCDR.

Step Operation Command1 Add optical port information. ADD BRDCFG

2 Add UOMU/UCDR. ADD BRD

2. Add URCU.

Step Operation Command1 Add a URCU. ADD BRD



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 Operation Command1 Add active

UICP/USPU/UGTP/UGBI.ADD BRD

2 Add standbyUICP/USPU/UGTP/UGBI.

ADD BRD

You need to configure the URCU before adding UICP/USPU/UGTP/UGBIs.

4. Add UEPI/UTPI.

Step Operation Command1 Add UEPI/UTPI. ADD BRD

2 Add UEPI/UTPI clockinformation.

ADD UEPIUTPICFG

You need to configure the corresponding IO board before adding UEPI/UTPIs.

5. Add ULAN.

Step Operation Command1 Add a ULAN. ADD BRD

You need to configure the URCU board before adding ULANs.

6. Add UHPU.



Add a UHPU by editing MML.txt:

Step Operation Command1 Add UHPU. ADD BRD

You need to configure the UOMU board before adding UHPUs.

Dynamically add a UHPU through the LM after system operation:

Step Operation Command1 Activate slot SET

BNET_UHPU_LOAD_TYPE

2 Add a UHPU ADD BRD

Example

3G example

Figure 2-2 Slots in a PSM subrack (3G).

PWS

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

UEPI

UEPI

UEPI

UPWR

UACU

UBIU

UACU

UBIU

UICP

UICP

USPU

USPU

URCU

URCU

UCDR

UGTP

UGTP

UOMU

UOMU

UCDR

UPWR

UFSU

UFSU

UPWR

UPWR

UBSU

UBSU

UEPI

UEPI

USPU

USPU

UEPI

UEPI

ULAN

Take Figure 2-2 as an example. Suppose UHPUs are inserted in slots 9 and 10 of the BNET subrack (withsubrack 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



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 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 UEPIUTPICFG: SRN=0, SN=2, 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 Slots in a PSM subrack (2.5G).

PWS

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

UEPI

UEPI

UEPI

UPWR

UACU

UBIU

UACU

UBIU

UGBI

UGBI

URCU

URCU

UCDR

UGTP

UGTP

UOMU

UOMU

UCDR

UPWR

UFSU

UFSU

UPWR

UPWR

UBSU

UBSU

UEPI

UEPI

USPU

USPU

UEPI

UEPI

UEPI

UEPI

UGBI

UGBI

ULAN

Take Figure 2-3 as an example. Suppose UHPUs are inserted in slots 9 and 10 in the BNET subrack (withsubrack 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;



;; 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=3, BP=IO, RS= STANDBY, PMCUT=UEPC, PMCDT=UFEU, SPEC=A,BT=UGBI;

;;Add 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 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 SubrackSimilar 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 MotorolaC-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 arealso regarded as a virtual subrack, namely UCDR subrack, with subrack number 32 plus UCDR group number.

UOMUBoard position: UOMUs are installed in slots 14 and 15 in the basic PSM subrack (generally the subracknumber 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 orremote maintenance terminal. The lower network port is connected with the UMPU through the ULAN,supporting maintenance on the BNET subrack.

URCUBoard 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 thestandby in slot 8.

Back board: UACU, which requires no data configuration.

PMC board: UFIU, which requires no data configuration.



IP address: You need to configure an IP address only for the active URCU in subrack 0. With this IP addressyou may configure an IPoA PVC between the active URCU and UMPU. Then the URCU can maintainthe BNET subrack through this PVC.

UCDRBoard position: UCDRs are installed in slots 10 and 11 in the basic PSM subrack or in any two slotsamong 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 withthe CG as the external IP address of the Ga interface.

UHPUBoard 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 inactive/standby mode. That is, UHPUs in slots (9, 10), (11, 12) and (13, 14) form three pairs of active/standbyboards. 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 datapackets at high speed. You may set an IP address for each engine as well as the IP address of the SGSNGTP-U. You may also set an IP address for only one engine. Because only the forward engine with IPaddress can forward data, make sure that at least one forward engine has been configured with IP addressbefore PDP context activation. If you set an IP address for both of the engines, the IP addresses must be indifferent network segments.

USPUBoard 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 beneighbouring 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 theirIO boards USPU.

PMC board: A USPU can be configured with two types of PMC boards, USS7 (providing 2 Mbit/s signalinglink or 64 kbit/s link) or UMTP (providing 64 kbit/s link).



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.

UICPBoard 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 neighbouringand usually the left UICP in a pair of active/standby UICPs is active.

Back board: none

PMC board: none

UGTPBoard 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 signalingplane in the SGSN.

UGBIBoard 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 (N≤11) backup mode. There is only one standby UGBIin one subrack.

Back board: The UEPI also works in N+1 backup mode, which consistent with UGBI. No E1 cables areconnected to the standby UEPI.

PMC board: The UEPC provides LLC layer encryption and UFEU provides FR layer functions. Each UGBIis configured with one UFEU (mandatory and one UEPC (optional).

UEPI/UTPIBoard 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+1backup mode and N+1 backup mode.



• Load sharing mode: used when the IO board is USPU. It indicates each of the UEPIs/UTPIsprovides a group of E1/T1 ports (0 to 3 and 4 to 7). You should add two PMC boards to aUSPU. The upper PMC board processes the services on the E1/T1 ports of the standbyUEPI/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 activeUEPI/UTPI provides two groups of E1/T1 ports. The USPU is configured with two PMCboards. The upper one processes the services on the first group of E1/T1 ports (4 to 7) and thelower 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 activeUEPI/UTPI provides two groups of E1/T1 ports. The only UFEU on the UGBI processes theservices on the two groups of ports.

Clock stratum: The stratum of the H110 clock for UEPI/UTPI includes PM, SM and SL. Theboard 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 slot8. The extracted clock serves as the signal source for the clock bus of the subrack. The boardwhose 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 otherssupport SL. The UEPI/UTPI configured with PM, SM or SL is not specified. However, youshall 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 120ohm (twisted pair), the UEPI will work in balanced mode.

UTPI only works in balanced mode (100 ohm).

ULANBoard 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 internalmaintenance network port of the UOMU. UOMU uses this IP address to load software to the ULAN.


Configuring Port Chapter 2: Hardware Configuration

Configuring Port■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration for port properties. The ports that need configuration in the systeminclude E1/T1, FE/GE, VA and ATM. A port can work normally only after proper configuration for itsproperties.

Description

Preset conditionsThe board providing the port already exists.


E1/T1 Subracknumber.

Slot number. Port number. Frame Type. Supportextractionof 2M clockfrom SS7.

Code Type.

FE/GE Slot number. Subslotnumber.

Port number. Negotiationmode.

Port rate. MTU

IP Address. Workingmode.

ATM First slotnumber.

First portnumber.

Second slotnumber.

Second portnumber.

Backup type.

VA Slot number. Subslotnumber.

Virtual portnumber.

Interface IPaddress.

Procedure

1. Add E1/T1.

Step Operation Command1 Add E1/T1. ADD E1T1CFG


Installation and Configuration: C-SGSN Data Configuration Configuring Port

2. Add FE/GE.

Step Operation Command1 Add FE/GE interface property. MOD BNET_IP_PROPERTY

2 Add FE/GE interface IP address. ADD BNET_GFI_IF_IP

3. Add VA.

Step Operation Command1 Add VA interface property. ADD BNET_UHPU_IF_IP

4. Add ATM.

Step Operation Command1 Add POS port property. ADD BNET_PORT_BACKUP

Example

;;Add E1/T1

ADD E1T1CFG: SRN=0, SN=4, PORT=2, 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 eitherUHPU 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 ifnecessary.


Configuring Port Chapter 2: Hardware Configuration

E1/T1E1/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 frameformats (SF and ESF) and three code types (B8ZS, AMI and AMI_ZCS). Settings for the frame format andcode 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 theE1/T1 link as its own clock.

FE/GEThe FE/GE port serves as the physical port of the Gn/Gp and Ga interfaces. You need to configure only an IPaddress 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 connectedexternal router.

VAThe 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 VAports (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 andthe other boards.

ATMULPU and UFIU provide ATM ports. You need to configure only the backup property of the ULPU ATM portconnected with the RNC. The system automatically sets the properties of the ULPU ATM port connectedwith the UFIU.

The backup type of ATM ports include:

• Redundancy backup. In normal cases, the two ATM ports receive and transmit data. If oneport 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 thestandby only transmits data. If the active port is faulty, the services on it will be shifted tothe standby one.

You can set the ATM port connected with the RNC to work only in 1+1 backup mode. Inaddition, the RNC must support port backup.


Installation and Configuration: C-SGSN Data Configuration Configuring Clock

Configuring Clock■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration for the Motorola C-SGSN system clock. The system can extractclock from the specified clock source after this configuration.

Description

Preset conditionsThe board configuration has finished. The system works normally. The external clock source works properlyand is well connected with the system. The E1/T1 configuration has finished if the system supports theextraction of 2 MHz clock from E1/T1.


Clock source. Clock source grade. Clock source type. ULPU Slot number(mandatory whenthe clock source isSDH).

ULPU Port number(mandatory whenthe clock source isSDH).

Procedure

Step Operation Command1 Add BNET clock reference

source.ADD BNET_CLOCK_SOURCE

2 Set the current 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;


Configuring Clock Chapter 2: Hardware Configuration

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 opticalport 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 isprovided by BITS network and BITS2 is the standby clock source of BITS1. The BITS clockhas 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 eachsource. The stratum depends on the clock stability and reliability. Stratum 4 stands forthe highest stratum and stratum 0 for the lowest. Stratum 0 stands for the clock generatedfrom the local oscillator on the clock board.


Chapter

3SS7 Configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■


SS7 Configuration Overview Chapter 3: SS7 Configuration

SS7 Configuration Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This chapter introduces the SS7 configuration, including the local office configuration, MTP layerconfiguration, 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. Local office configuration.

2. MTP layer configuration.

3. SCCP layer configuration.

4. MAP layer configuration (Gr/Gd/Ge/Gf/Lg interface).

5. BSSAP+ layer configuration (Gs interface).


Installation and Configuration: C-SGSN Data Configuration Configuring Local Office

Configuring Local Office■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the local office configuration. Only after the local office configuration is implementedthe other configurations of SS7 can be implemented.

Description

Preset conditionsNone


SignalingNetworkType.

Signalingpoint code.

SGSNnumber.

STP flag. Mobilecountrycode.

Mobilenetworkcode.Basic

Information. Countrycodes.

SupportBSSAP+flag.

SubsystemNumber ofBSSAP+

Procedure

Step Operation Command1 Set the information of the

signaling point whose indexnumber is 0.

SET OFI

2 Set the information of thesignaling point whose indexnumber is not 0.

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;


Configuring Local Office Chapter 3: SS7 Configuration

;;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 MotorolaC-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 commandsADD OFI and RMV OFI are used to add and remove the information of the OPC with index other than 0.


Installation and Configuration: C-SGSN Data Configuration Configuring MTP Data

Configuring MTP Data■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The MTP layer data configuration includes the settings of MTP signaling link, route and signaling point. Afterthe settings, the communication with each network node on the MTP layer can be implemented normally.

Description

Preset conditionsBefore the configuration, the relevant hardware equipment should be working normally. The physicallinks with the destination signaling points should be normal. Make sure you have configured the localoffice information.


Configuring MTP Data Chapter 3: SS7 Configuration

Data preparationsIf there is a direct route between the DPC and the local office, then you should prepare the following data:

Item Data

MTP DPDPC Network

indicator.Correspond-ing OPC.

STP flag. Adjacentflag.

Link setselectionmask.

MTP link. Subracknumber.

Slot number. Linknumber.

Link ratetype.

SLC Priority.

Signalinglink type.

MTP linkset.

Signalinglink selectionmask.

MTP route. Priority.

Cont.



If the STP transfers the signals between the DPC and the local office, then you should prepare the followingdata:

Item DataMTP DPC DPC Network

indicator.Correspond-ing OPC.

Link setselectionmask.

MTP route. Priority.

Procedure

If there is a direct path between the DPC and the local office:

Step Operation Command1 Add MTP destination signaling

point.ADD N7DPC

2 Add MTP signaling link set. ADD N7LKS

3 Add MTP signaling route. ADD N7RT

4 Add MTP signaling link. ADD N7LNK

If the STP transfers signals between the DPC and the local office:

Step Operation Command1 Add MTP destination signaling

point.ADD N7DPC

3 Add MTP signaling route. ADD N7RT

Example

If there is one direct route and two indirect routes to HLR, and there are four links in each link set, thenthe 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";



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=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=0, TS=16, LSX=2, SLC=0, SLCS=0,LKN="STP2_LINK1";




Reference

MTP Destination Signaling PointFrom the view of the local office, you can divide the signaling points into original signaling points (thesignaling points where the local office is) and the destination signaling points (the signaling points to whichthe local office signaling messages are transmitted).



For an OSP, you can categorize its Destination Signaling Point (DSP) into adjacent destination signalingpoints and non-adjacent destination signaling points. A destination signaling point with a direct signaling linkto the OSP is an adjacent signaling point of the OSP; while the one without a direct signaling link to the OSPbut 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 inFigure 3-1. DPC2 in Figure 3-1 does not have direct signaling link with the OSP; therefore, whether toconfigure DPC2 depends on the addressing mode specified by the operator. It should be configured if the DPCaddressing has been adopted, but not if the GT addressing has been adopted.

Figure 3-1 DSP configuration.

DPC1

Signaling link

No signaling link,

but signaling relationship

DPC2

OPC

STP

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

MTP signaling routeThe MTP route is the path for the transmission of signaling messages between two signaling points. Signalingroute 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 signalingroutes.

The signaling route to a destination signaling point can be categorized into two types: direct routes and theindirect routes. Direct route refers to the signaling route between the OSP and the destination signaling pointwithout the signaling transfer point. While indirect route refers to the signaling route in which the signaling istransmitted 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 thedestination signaling point. The link set corresponding to the indirect route is the link set between theoriginating 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 thesignaling routes, then select the route with higher priority. Usually the direct routes are specified with higherpriority. Up to 16 routes can have the same priority and they can share the load. When there are multipleroutes, the signaling will prefer the route with higher priority.



MTP signaling linkThe 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 systemcan be specified as a signaling data link, except timeslot 0. In the PCM primary group, TS16 is generallyspecified 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 signalingdata 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/ssignaling 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 whendifferent subboards are configured on the USPU and UEPI/UTPI adopts different backup types.



Table 3-1 Relations between link No, timeslot number and UEPI/UTPI port.

Subboardtype

Subboardposition

Link number Timeslotnumber

UEPI/UTPIbackup type

UEPI/UTPIport

Load sharing. Active E1_0 orE1_1.Lower

subboard. 0 to 3 0 to 1271+1 Active E1_0.

Load sharing. Standby E1_0or E1_1.

UMTP

Upper subboard 4 to 7 128 to 2551+1 Active E1_1.

Load sharing. ActiveE1_0 orE1_1.Lower

Subboard 0 to 31 0 to 1271+1 Active E1_0.


USS7_64

Uppersubboard. 32 to 63 128 to 255

1+1 Active E1_1.

Load sharing. Active E1_0 orE1_1.Lower

subboard. 0 0 to 1271+1 Active E1_0.


USS7_2M

Uppersubboard. 32 128 to 255

1+1 Active E1_1.

• 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_1indicates the 4 to 7 E1/T1 of the active UEPI/UTPI. The standby E1_0 indicates the 0 to3 E1/T1 of the standby UEPI/UTPI. The standby E1_1 indicates the 4 to 7 E1/T1 of thestandby UEPI/UTPI.

• The link Numbers and E1/T1 port Numbers in the same UMTP/USS7 have no correspondencebut range restriction.

• All the timeslots 0 of E1 ports are used for synchronization and cannot be used as thetimeslots of the signaling links. In this case, the timeslot number should not be the multiplierof 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 of32, for example, 0 to 23, 32 to 55.

Load sharing of SS7 signaling networkThere are two types of load sharing.



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 theSignaling Link Selection (SLS) code, as illustrated in Figure 3-2. In the figure, there are twosignaling links between signaling points A and B. The signaling messages are allocated tothese 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.

A B

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.

A D E

F

B

C

XXX0

XXX1

XXXX

Even when the signaling messages to different DSPs use the same signaling link set, they maynot use the same load sharing type. Take Figure 3-3 for example, services to B are sharedbetween link sets DE and DF based on SLS while services to C are only undertaken by thelink set DF because of EC fault.

To realize the above two signaling sharing modes, Motorola C-SGSN utilizes signaling link setselection 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 theCIC; while in the SCCP message, it is allocated by SCCP cyclically. As SLS changes in acyclic manner, the load sharing based on SLS can ensure that the load among various linksor link sets is well-proportioned.



Mask setting principlesThe signaling link set masks and the signaling link masks determine the allocation of SLS in the link setand between the links. Figure 3-4 shows the algorithm used by SGSN to select a signaling link set orsignaling link through the corresponding mask.

Figure 3-4 Example of signaling link set/signaling link algorithm selection.

SLS 1

Mask 10 0

0 is skippedThis bit taken as the lowest bit (bit)This bit taken as the second lowest bit (bit)

1 1

Form =0011% Calculate the remainder4 Number of available signaling routes

with the same priority

3 Fourth signaling routeConclusion: The fourth signaling route is selected for the signalling

service with SLS to be 1111.

1 1 1

1

0011 0x3

The SLSs generated on the MTP upper layer are allocated cyclically. If you use the masks to control theallocation of SLSs in the MTP signaling link sets and between the MTP signaling links, then you canensure that the load sharing between each link set/signaling link will be reasonable. The following are theprinciples for setting the mask:

1. Set the number of '1's in the mask according to number of signaling link sets or the number ofsignaling links. See Table 3-2.



Table 3-2 Relationship between the number of link sets/links and the number of 1s inthe mask.

The number of link sets/links The number of 1s in the mask2 1

3 to 4 2

5 to 8 3

9 to 16 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 thesignaling 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, thesignaling link mask should be '1100'. If the number of signaling links are 2, the signaling linkmask 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 signalingpoint and that each link set contains two links. According to the above principles, the signalinglink set mask can be set as '1010' and the signaling link mask can be set as '0100'. The signalinglink set/SLS algorithm is shown in Table 3-3.

Table 3-3 SLS allocation.

Link set number SLS Link number SLS0 0, 1, 4, 5 0 0, 1

1 4, 5

1 2, 3, 6, 7 0 2, 3

1 6, 7

2 8, 9, 12, 13 0 8, 9

1 12, 13

3 10, 11, 14, 15 0 10, 11

1 14, 15

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 servicewill be shared by the link sets with lower priorities.


Installation and Configuration: C-SGSN Data Configuration SCCP Configuration

SCCP Configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The SCCP data configuration includes the SCCP destination signaling code configuration, SCCP subsystemconfiguration, new GT configuration and the GT translation. Usually the new GT configuration is notnecessary. After the SCCP data configuration, SGSN can communicate with the signaling points withthe SCCP function on the SCCP layer.

Description

Preset conditionsYou should first implement the configuration of the MTP layer data. The local office provides the SCCPfunction.

Data preparationsIf there is a direct route between the DPC and the local office, or the STP transfers signals between the DPCand the local office, and the addressing mode is DPC+SSN, then you should prepare the following data:

Item DataDPC DPC Network

indicator.Load sharingDPC.

GT HLR/SMC/EIR/SCP/GMLCNumber.

IMSI-GTcorrespondingrelation (addHLR).

IMSI numbersegment (addHLR).

New GT.

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 DataGT HLR/SMC/EIR/

SCP/GMLCNumber.

IMSI numbersegment (addHLR).

IMSI-GTcorrespondingrelation (addHLR).

New GT.


SCCP Configuration Chapter 3: SS7 Configuration

Procedure

If there is a direct route between the DPC and the local office, or the STP transfers signals between the DPCand the local office, and the addressing mode is DPC+SSN:

Step Operation Command1 Configure SCCP destination

signaling point.ADD SCCPDPC

2 Configure SCCP subsystem. ADD SCCPSSN

3 (optional). Configure IMSI-GT translationtable.

ADD IMSIGT

4 (optional). Configure new GT table. ADD SCCPNGT

5 Configure GT translation table. 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 Operation Command1 (Optional). Configure IMSI-GT translation

table.ADD IMSIGT

2 (Optional). Configure new GT table. ADD SCCPNGT

3 Configure GT translation table. 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 of460001001, 460001002 and 460001003 belong to this HLR:



;;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;



Reference

SCCP DSPThe configuration of SCCP destination signaling point is to create a destination signaling point associatedwith 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 tobe described in SCCP DSP Table.

Generally, the following SCCP DSPs need to be defined:



• 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.

Figure 3-5 SCCP DSP.

A

C

B

D

In Figure 3-5, A is the OSP; B and D are signaling points having SCCP signaling relationshipwith the OSP; and C is the SCCP signaling transfer point. If the addressing mode from A to Dis DPC+SSN, the SCCP destination signaling points to be configured for A are B and D. Ifthe addressing mode from A to D is DPC+GT, the SCCP destination signaling points to beconfigured 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 loadsharing.

• 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 messagesare sent to this DSP if it is available, otherwise, the messages are sent to the standby signalingpoint.

• Load-sharing mode means that the DSP has a standby signaling point so that SCCP messagesare sent to these two signaling points by turn. If only one of them is available, the messages aresent 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. SCCPprocesses messages transmitted to the DSP in a cyclic mode. It selects one virtual signalingpoint at the OSP as the OPC in the MTP message for the corresponding DSP.

SCCP SubsystemThe SubSystem Number (SSN) is the local addressing information used by SCCP. It is used to identifymultiple SCCP subscribers in a network node. If the network node functions more than an STP, a subsystemnumber has to be specified for each SCCP subsystem (SCCP subscriber). Each subsystem number is uniquein the whole network.



The number of subsystems related to SGSN is shown in Table 3-4.

Table 3-4 Number of subsystems related to SGSN.

Subsystem Subsystem numberSCCP Management subsystem. 0x01

HLR 0x06

VLR 0x07

MTS-U 0x08

EIR 0x09

INAP 0x0C

GMLC 0x91

CAP 0x92

SGSN 0x95

GGSN 0x96

BSSAP+ 0xFC (configurable).

The SCCP management subsystems corresponding to SCCP remote signaling points defined at the OSP mustbe 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 TranslationIn SS7 signaling system, all messages are transmitted through MTP. MTP address is composed of SPC andnetwork identification. In PLMN, the destination address in mobile-concerned message is identified by otherinformation (for example HLR number, MSISDN). SCCP needs to translate the GT information of the calledsubscriber into DPC or DPC+SSN for the MTP to transmit the message. The process of translation iscalled 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 inFigure 3-6.



Figure 3-6 DPC+SSN addressing mode.

SCCP

MTP

Subsystem

SCCP

Subsystem

DPC+SSN

A B

MTP

2. There is no direct physical link between the two signaling points (A and C). The MTP signalingmessage is transferred through an STP (B).

In this case, the GT is translated into DPC+SSN. The signaling message from A usesDPC+SSN addressing mode. The DPC is the signaling point code of C. The SSN is thesubsystem number of C. When the MTP of B receives the MTP message from A and finds outthat 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.

SCCP

MTP

Subsystem

SCCP

Subsystem

DPC+SSN

A B

MTP

SCCP

Subsystem

C

MTP

DPC+SSN

3. There is no direct physical link between the two signaling points (A and C). The SCCPsignaling message is transferred through an STP (B).

Under this situation, the GT is translated into DPC+ GT. The signaling message from A usesDPC+GT addressing mode, where DPC is the signaling point code of B and GT is the GT codeof C. The MTP of B receives the message from the MTP of A, and then sends the message to itsSCCP. SCCP then performs GT translation and the translation result is DPC+SSN, where DPCis the signaling point code of C and SSN is the subsystem number of C. The translation result isthen 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.



Figure 3-8 DPC+GT addressing mode.

SCCP

MTP

Subsystem

SCCP

Subsystem

DPC+GT

A B

MTP

SCCP

Subsystem

C

MTP

DPC+SSN

To meet the requirements of different network, the SCCP layer can translate certainGT into new GT before forwarding it. In this case, you should configure a new GTtable. The addressing mode is DPC+NGT.



Common GTs for SGSNIn SGSN, you should configure the following GTs:

GT Address mode DescriptionIMSI number segments of all thelocal subscribers in HPLMN.

DPC+SSN (in general). Addressing the local HLR. DPCis the DPC of the local HLR. SSNis the SSN of the HLR.

IMSI number segments of allthe foreign subscribers in theHPLMN.

DPC+GT (in general). Addressing the foreign HLR. DPCis the DPC of STP.

IMSI number segments of allsubscribers in the PLMN thatallows roaming.

DPC+GT (in general). Addressing the foreign networkHLR. DPC is the DPC of STP.

Number of the local SGSN. Set as DPC. Addressing the local SSN. DPC isthe DPC of the local SGSN.

HLR number. DPC+SSN (in general). You shall configure HLR numberonly when the IMSI adopts theDPC + SSN addressing mode toaddress this HLR. DPC is theDPC of HLR.

SMC number. DPC+GT (in general). Addressing SMC. DPC is theDPC of STP.

SCP DPC+GT (in general). Addressing SCP. DPC is the DPCof STP.

GMLC DPC+GT (in general). Addressing GMLC. DPC is theDPC of STP.

EIR DPC+GT (in general). Addressing EIR. DPC is the DPCof STP.

MTS-U/VLR number. DPC+SSN (in general). Addressing MTS-U/VLR. DPC isthe DPC of MTS-U/VLR.

When the SCP and GMLC are the same physical entity, The Ge and Lg interfaces simultaneouslyexist between the SGSN and the DPC. In this case, the GT translation mode of SCP should be setas DPC or DPC+GT/NGT mode, instead of DPC+SSN mode. When the SCP and GMLC are notthe same physical entity, the GT translation mode of the SCP can be set as DPC+SSN mode.



IMSI-GT conversionWhen the mobile subscriber initiates location update to or obtains an authentication set from HLR, there is noHLR number or MSISDN of the subscriber in SGSN. The only HLR addressing information is the IMSI of thesubscriber. 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.

CC: Country code NC: Network codeMSIN: Mobile subscriber identification No.

CC NC MSIN

MSIN

MCC: Mobile country code. MNC: Mobile network code

MCC MNCIMSI

GT

Conversion Conversion

The IMSI GT Conversion is to convert the MCC+MNC of IMSI to CC+NC of GT. MSIN can be obtaineddirectly by mapping.

CC+NC is used to identify the PLMN or an HLR in the PLMN of a country. NC can be either the NationalDestination Code (NDC) or NDC followed by several numbers. It is used to identify a PLMN or an HLR inthe PLMN. Moreover, MSIN is used to identify a mobile subscriber in HLR.


Configuring MAP (Gr/Gd/Ge/Gf/Lg interface) Chapter 3: SS7 Configuration

Configuring MAP (Gr/Gd/Ge/Gf/Lg interface)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration of the MAP layer function of the Gr interface. After theconfiguration, SGSN can perform the MAP layer signaling exchange with the HLR.

Description

Preset ConditionsThe configuration of local office information, MTP information and SCCP information have been completed.

Data PreparationIf SGSN provides the zone restriction function, then you should prepare the following data:

Item DataArea code. ZC LAI RAI

Procedure

Step Description Command1 Configure the MAP function. SET MAPFUNC

2 (Optional). Configure the zone code. 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;


Installation and Configuration: C-SGSN Data Configuration Configuring MAP (Gr/Gd/Ge/Gf/Lg interface)

Reference

MAPMobile Application Part (MAP) protocol defines how the information is exchanged for MS roaming betweenthe 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 throughMAP protocols. Among these protocols, TCAP, SCCP and MTP protocols are the same asthose bearing MAP signaling in CS network. The design of SGSN takes the compatibilitybetween 2.5G GPRS MAP version and the UMTS MAP version into consideration to ensurethat the SGSN can interwork with the MAP of lower version.

• MAP message processing modules strictly comply with 3GPP TS 29.002 and provide all basicfunctions 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, LCSsubscription data and CAMEL subscription data.

• Security management, including authentication for both 2G and 3G MSs and authenticationfailure 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 failurereport, 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 tableThe MAP zone code is one of the measures the operator uses to control the subscriber roaming. The operatordivides the service coverage into multiple zones, with each being identified with a zone code. If the subscriberhas subscribed to a specific or several service zones, the subscriber can roam within the subscribed zones. InSGSN, you should configure the corresponding zone code subscription that allows roaming. When there is anintersection between the zone code subscribed by the subscriber and the zone code configured in SGSN, itmeans that this subscriber can access this zone. Otherwise, this subscriber access will be rejected.


Configuring BSSAP+ (Gs interface) Chapter 3: SS7 Configuration

Configuring BSSAP+ (Gs interface)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration of BSSAP+ layer. After the configuration, SGSN can normallyimplement the function of the Gs interface.

Description

Preset conditionsThe configuration of the local office information, MTP information and SCCP information has beencompleted.


Basic in-formation.

VLR LAI

Procedure

Step Operation Command1 Configure BSSAP+ timer. SET BSSAPPTMR

2 Configure VLR table. ADD VLR

3 Set RAI-VLR correspondingrelation.

ADD LAIVLR

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";


Installation and Configuration: C-SGSN Data Configuration Configuring BSSAP+ (Gs interface)

Reference

Upon the initialization of the system, the default values of the length of each BSSAP+ timer are set. Thesedefault values are the recommended values of the protocol. Usually the users do not need to modify thesevalues. 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 accordingto RAI, translates the GT and then obtains the destination signaling code of MTS-U/VLR.


Configuring BSSAP+ (Gs interface) Chapter 3: SS7 Configuration



Chapter

4Iu interface Configuration (3G)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■


Iu interface Configuration Overview Chapter 4: Iu interface Configuration (3G)

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.


Installation and Configuration: C-SGSN Data Configuration Configuring User Plane of Iu Interface

Configuring User Plane of Iu Interface■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration for the IP route and GTP parameters of the user plane. After theconfiguration, the user plane of the Iu interface can normally process data.

Description

Preset conditionsThe hardware configuration has finished.


Basic information.

VPI/VCI Local IP address. Slot number andport number ofoptical port whichis connected withRNC.

Traffic parameter.


Configuring User Plane of Iu Interface Chapter 4: Iu interface Configuration (3G)

Procedure

If the IPOA PVC type is RNCOA, you may configure the user plane related data through the following steps.

Step Operation Command1 Add VRT template. ADD BNET_VRT

2 Add local IP address to a VA portof the UHPU.

ADD BNET_LOCAL_IP

3 (optional). Add a record to the PVC TrafficTable.

ADD BNET_CONN_TRAFFIC

4 (optional). Add the backup relation on theoptical port connected to RNC.

ADD BNET_PORT_BACKUP

5 Add an IPOA PVC between anRNC and SGSN.

ADD BNET_RNC_IPOA

6 Add GTP parameters. See Chapter 5, "Gn/Gp InterfaceConfiguration,"

If the IPOA PVC type is normal IPOA, you may configure the user plane related data through the followingsteps.

Step Operation Command1 Add IP address to a VA port of the

UHPU.ADD BNET_UHPU_IF_IP

2 (optional). Add a record to the PVC TrafficTable.

ADD BNET_CONN_TRAFFIC

3 (optional). Add the backup relation on theoptical port connected to RNC.

ADD BNET_PORT_BACKUP

4 Add an IPOA PVC between anRNC and SGSN.

ADD BNET_RNC_IPOA

5 Add GTP parameters. See Chapter 5, "Gn/Gp InterfaceConfiguration,"

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";



Add two RNCOA IPOA PVCs between the SGSN and an RNCADD 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 PVCThe 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. Thatis, the RNC can communicate with only one FE of the SGSN. Data packets from the RNC tothe other FEs are forwarded through that FE.To add an IPOA PVC, you shall specify the IPaddress of the VA port.

• RNCOA PVC. There is an RNCOA PVC between an RNC and each FE of an SGSN. Thatis, the RNC can communicate with each FE and transmit data packets to a specified FE ofthe SGSN. This increases system efficiency. To add an RNCOA PVC, you shall specify thelocal IP address of the VA port.

Figure 4-1 shows the differences between an RNCOA PVC and normal IPOA PVC. There isonly one IPOA PVC between RNC1 and the SGSN. Therefore, the data from RNC1 to FEB inthe UHPU or to the other boards shall be forwarded by FEA. Because there are four RNCOAPVCs between RNC2 and the SGSN, RNC2 can directly transmit data to the target FE.



Figure 4-1 IPOA PVC and RNCOA PVC.

RNC1

RNC2

UHPU

UHPU

FEA

FEA

FEB

FEB

VA port

VA port

VA port

VA port

RNCOA PVC

RNCOA PVC

RNCOA PVC

RNCOA PVC

IPoA PVC

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 portUHPUs provide data forward function in the SGSN. Each UHPU contains two forward engines, FEA andFEB. Each engine has an IP address, that is, the IP address for the GTP user plane of SGSN. This IP address isalso 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 canset up PVCs to an RNC, UGTP and UCDR. From the point of an RNC, the IP address of the VA port is that ofthe SGSN gateway. That is, the UHPUs forward the IP packets from an RNC to the GTP user plane of SGSN.



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 shallspecify the local IP address of the VA port. Note that you can set the local IP addresses for different VA portsin 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 parametersThe ATM services used for configuring the ATM layer include CBR, RTVBR, NRTVBR and UBR, asshown below:

• Constant Bit Rate (CBR), service that does not support error check, flow control or otherprocessing. It realizes a smooth transition between the current telephony system and B-ISDNsystem.

• Variable Bit Rate (VBR), service classified into realtime transmission (RT-VBR) andnon-realtime transmission (NRT-VBR). RT-VBR is used to describe the service featuringvariable data streams and strict realtime requirement, for example interactive compressedvideo such as videoconference. NRT-VBR is used on the communication occasions requiringtiming transmission. In such case, some delays and variations, for example, those in E-mailtransmission can be accepted by the application.

• Unspecified Bit Rate (UBR), service that does not make any commitment or feedback tocongestion. It is suitable for transmitting IP packets. In case of congestion, UBR cells willbe discarded. However, neither relevant feedback nor the request for slowing down thetransmission speed will be returned to the sender.

Table 4-1 shows the descriptions of these ATM service characteristics.



Table 4-1 ATM service characteristics.

Servicecharacteristic

CBR RT-VBR NRT-VBR UBR

Guaranteedbandwidth.

Y Y N N

Applicableto realtimecommunication.

Y Y N N

Applicableto burstcommunication.

N N Y Y

Feedback oncongestion.

N N N N

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, NOCLPNOSCRindicates '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 Abbreviation MeaningPeak cell rate. PCR Maximum cell transmission

rate (cell/s).

Sustainable cell rate. SCR Long-term average celltransmission rate (cell/s).

Cell delay variationtolerance.

CDVT Maximum tolerable cell jitter(0.1µs).

Cell loss priority. CLP Indicating which cells canbe discarded (CLP=1), andwhich cells shall not bediscarded (CLP=0) uponnetwork congestion.

Tag. TAGGING Tagging the cells withCLP=0.

There are some default traffic parameters in the system. You may directly use them accordingto the corresponding parameter ID.


Installation and Configuration: C-SGSN Data Configuration Configuring Control Plane of Iu Interface

Configuring Control Plane of Iu Interface■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration for the control plane of the Iu interface. After the configuration, anRNC can normally interact with the SGSN for signaling.

Description

Preset conditionsHardware configuration (for example, board configuration) related to the Iu interface has finished.


Configuring Control Plane of Iu Interface Chapter 4: Iu interface Configuration (3G)


Basicinformation.

OPC NI

RNCinformation.

RNC SPC MCC MNC RNC ID

SAAL linkinformation.

Optical Slot toRNC.

Optical Port toRNC.

VPI/VCI at CNside, VPI/VCIat RNC side.

Trafficparameters.

Link number.

MTP3B SLC

Cont.



Procedure

Step Operation Command

1 Add a signaling point on the Iuinterface. ADD IUSP

2 Add an originating signaling pointon the Iu interface. ADD IUOPC

3 Add an SAAL link. ADD SAALLNK

4 Add an MTP3B destinationsignaling point. ADD MTP3BDPC

5 Add an MTP3B signaling link set. ADD MTP3BLKS

6 Add an MTP3B signaling route. ADD MTP3BRT

7 Add an MTP3B signaling link. ADD MTP3BLNK

8 Add an SCCP destinationsignaling point. ADD IUSCCPDPC

9 Add an SCCP subsystem. ADD IUSCCPSSN

10 Add RNC information. ADD RNC

11 Add the mapping relation betweenUICP and RNC. ADD UICPRNC

Example

Figure 4-2 shows a networking example of the control plane of the Iu interface. There are two RNCs, theSPCs of which are 0x100 and 0x101. Both NIs are national standby network. The SGSN SPC is 0x200 and itsNI 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.

BNET

RNC1

U

I

C

P

RNC2

SGSN

SPC=0X0100 SPC=0X0101

SPC=0X0200

U

I

C

P

NI=NATIONALRES NI=NATIONALRES

NI=NATIONALRES



In this example, each RNC is connected with two UICPs. Therefore, if only one link is required between eachRNC 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 withoptical 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) and0/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) and0/103 (at SGSN side).

The UICP in slot 1 of subrack 2 processes the services on the first SAAL link between RNC1 and RNC2. TheUICP 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

BNET

VPI/VCI=1/102

VPI/VCI=1/103VPI/VCI=1/101

VPI/VCI=1/100

SLOT/PORT=5/3

SGSN

RNC2

U

I

C

P

U

I

C

P

SLOT/PORT=4/2

VPI/VCI=0/100

VPI/VCI=0/102

VPI/VCI=0/101

VPI/VCI=0/103

SUBRACK/SLOT=2/1 SUBRACK/SLOT=2/2

According to the preceding configuration data and networking mode, you may configure the Iu interfacerelated data as follows:

;;Add s signaling point.

ADD IUSP: SPX=0, NI=NATB, SPC="200", CDT=LABEL14, STPF=DISABLE;





;;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 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 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;



ADD IUSCCPSSN: SSNX=1, NI=NATB, SPC="100", 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;




Reference

Each UICP can correspond to up to 64 RNCs.

Broadband SS7The signaling plane of the Iu interface adopts broadband SS7. Compared with the narrowband SS1, thebroadband 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 beconfigured with two subsystems. One is the SCCP Management Subsystem (SCMG) withsubsystem number of 1 and the other is network entity related subsystem (RANAP) withsubsystem number of 142.



Configure RNCThe RNC Description Table describes the basic information of RNC such as the SPC and the networkindicator 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 RNCThe mapping relation between RNC and UICP is a many-to-many relation. Take following factors intoconsideration during the configuration:

• Load-sharing factor. There may be many UICPs configured in the system. The load on eachUICP shall be shared evenly during the configuration.

• Security factors. For the sake of security, configure two or more UICPs for an RNC so that theRNC services can remain normal when one UICP is faulty.


Chapter

5Gn/Gp Interface Configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■


Gn/Gp Interface Configuration Overview Chapter 5: Gn/Gp Interface Configuration

Gn/Gp Interface Configuration Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This part presents instructions to configure data for Gn/Gp interface, including Gn/Gp interface routeconfiguration, GTP protocol parameter configuration, DNS configuration , IPSEC configuration , OSPFconfiguration and RIP configuration.


Installation and Configuration: C-SGSN Data Configuration Gn/Gp Interface Route Configuration

Gn/Gp Interface Route Configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Route configuration of Gn/Gp Interface is as follows:

Description

Preset conditionsHardware configuration for the UGTP/UHPU has been completed.

Data preparationItem Data

Basicinformation.

UGTPsubracknumber andslot number.

UHPUsubracknumber,slot numberand forwardenginenumber.

ULPI/ULPCinterface IPaddress.

Gn/Gp routeplanning.

Procedure

Step Operation Command1 Configure IPoA PVC between the

UGTP and the UHPU.ADD SGSN_IP_IPOA_PVC

2 (optional). Configure ULPI/ULPC interfacebackup.

ADD BNET_NET-WORK_BACKUP

3 Configure ULPI/ULPC interfaceIP.

ADD BNET_GFI_IF_IP

4 Configure IP route to target node. 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;


Gn/Gp Interface Route Configuration Chapter 5: Gn/Gp Interface Configuration

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

PSM

U

R

C

U

U

G

T

P

U

G

T

P U

L

P

U

U

L

P

I

U

N

E

T

U

H

P

U

BNET

FEA: 10.21.40.37

FEB: 10.21.41.37

GGSN GTP-U:

192.22.66.1

192.25.5.1

GGSN GTP-C:

192.22.66.6

192.25.5.5

192.22.66.253

ROUTER

LAN Switch

10.22.40.13

;;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. TheUHPU is responsible for functions of GTP-U, routing and forwarding of GTP-C messages. The ULPI/ULPCprovides external FE/GE Ethernet interface.

The UGTP provides an IP address for the external SGSN GTP signaling plane. The UHPU provides two IPaddresses (each IP address corresponds to a forwarding engine) for the external SGSN GTP user plane. Eachport of the ULPI/ULPC provides an IP address for SGSN to connect an external router.


Installation and Configuration: C-SGSN Data Configuration Gn/Gp Interface Route Configuration

Configure IPOA PVCTo 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 onlynecessary to specify the location of the UGTP and the UHPU and forward engine instead ofthe IP address of the port.

Configure IP routeSince the destination IP addresses of IP messages sent by the UGTP and the UHPU may not be in the samenetwork segment with the IP address of the ULPI/ULPC, it is necessary to configure IP route to specify theULPI/ULPC interface to the destination IP address.


Configure DNS/HOSTFILE Chapter 5: Gn/Gp Interface Configuration

Configure DNS/HOSTFILE■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Only after completion of configuration for DNS/HOSTFILE, can SGSN perform APN and SGSN numberresolution correctly.

Description



DNSSERVER

IP address. DNSpriority.

HOSTFILE APN orSGSNnumber.

IP list.

Procedure

Step Operation Command1 Configure DNS Server. ADD DNSS

2 Configure HOSTFILE. 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";


Installation and Configuration: C-SGSN Data Configuration Configure DNS/HOSTFILE

Reference

During inter-SGSN Routing Area Updating (RAU), Relocation or PDP CONTEXT activation, domain nameis usually used to specify the old SGSN or APN. Under this scenario, domain name resolution is used to obtainthe 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 thelocal SGSN and contains only a few records.

Follow the procedures below for domain name resolution. First, SGSN searches for theHOSTFILE records on the UGTP. If it cannot find records in the HOSTFILE, it searches forrecords in the DNS Cache in the UGTP. If it still cannot get records, it uses the DNS serverfor domain name resolution. The DNS Cache in the UGTP is a buffer that saves the domainname and IP address obtained using the DNS server. It is used to speed up the domain nameresolution, and thus to cut down the number of accesses to the DNS server. The record in theDNS 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. AndHOSTFILE is usually used for the resolution of those frequently used domain names, becauseresolution by HOSTFILE is more efficient than the resolution by DNS server.


Configuring GTP Protocol Parameters Chapter 5: Gn/Gp Interface Configuration

Configuring GTP Protocol Parameters■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The setting of protocol parameters may have serious impact upon the system. Itis recommended to adopted system default values. You should kwow the casewithout 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 theGTP user plane (including Iu interface and Gn/Gb interface).

Description


Data preparationNone.


Installation and Configuration: C-SGSN Data Configuration Configuring GTP Protocol Parameters

Procedure

Operation Parameter type CommandWhether to send optional fields. SET GTPPUB

Configure GTP message. Equipment associatedinformation. SET GTPPUB

Path maintenance mode. SET GTPPUBSET UGTPConfigure GTP path parameter.

Overload/congestion threshold. SET GTPPUB

Number of GPT-U pathssupported, number of signalingmessages waiting for responses.

SET UHPUPATH

Overload/congestion threshold. SET UHPUUSRCTRL

Whether to check sequencenumber of packets forwarded. SET SEQCHK

Bandwidth. SET UHPUBW

Configure UHPU runningparameter.

Bandwidths of various services. SET BWRATIO

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.


Configuring QoS Parameters Chapter 5: Gn/Gp Interface Configuration

Configuring QoS Parameters■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Quality of Service (QoS) is an evaluation of performance of user data flow passing by network. Thepresentation of QoS aims to provide 3G/2.5G users with reliable point-to-point services. The QoS evaluationis based on multiple specifications including service availability, delay, delay jitter, throughput and packetloss ratio.

SGSN configuration associated with QoS includes CBWFQ parameter, WRED parameter, DSCP remarkand mapping between QoS and DSCP.

Description



Procedure

Step Operation Command* Configure CBWFQ parameter. SET QOSPRI

* Configure WRED parameter. SET WRED

* Configure remarkingcorrespondence.

SET DSCPRMK

* Configure mapping relationshipfrom QoS to DSCP.

SET QOSDSCP

* Configure mapping relationshipfrom DSCP to QoS.

SET DSCPQOS

Example

;;Modify DSCP of corresponding to the Steaming service as EF

SET QOSDSCP: SCDSCP=EF;


Installation and Configuration: C-SGSN Data Configuration Configuring QoS Parameters

Reference

CBWFQ

Figure 5-2 Schematic diagram of CBWFQ.

......

Data packets to be

sent via this interface

Classification

queue

queue 0

queue 1

queue 2

queue N1

Default queues

queue 1

queue 2

queue N2

Priority queue

Data packets off the

interface

Dequeue

scheduling

As shown in Figure 5-2, CBWFQ (Class Based Weighted Fair Queuing) first classifies packets accordingto the interfaces using which they have entered the network equipment, and the protocols adopted for thepackets, and also as per whether the packets match ACL. Then it let the packets of different classes enterdifferent queues. The packets that do not match any class are sent into the default queues, and are processed asper WFQ, that is they are processed in stream mode.

During dequeue scheduling, each queue is allocated with a bandwidth. The scheduler sends the dequeuingpackets 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 thescheduler start to schedule the packets in other queues.



When there is no congestion on the interface that is when there is no packet in other queues), all the packets inthe priority queue can be sent. When congestion occurs to the interface (that is when there are packets in otherqueues), the transmission speed of the packets in the priority queue shall be restricted, and the packets beyondthe specified traffic limit shall be discarded. In this way, the packets that belong to the priority queue can getfree bandwidth when no congestion occurs to the interface, whereas, in the case of interface congestion, theoccupied bandwidth shall not exceed the specified bandwidth, to ensure the specified bandwidth for otherpackets. In addition, if any, the scheduler shall send the packets in the priority queue. Therefore, for thepackets in the priority queue, the transmission delay is maximally the time taken by the interface to send apacket with the largest size. Whether delay or delay jitter takes place, the impact can be minimized in thepriority 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 occupya queue. When the scheduler schedules to dequeue packets, the dequeuing packets are sent out as per thebandwidth specified by the user for each class. The packets that belong to queue 1 to queue N1 are ensuredthe specified bandwidth. When there is no packet of certain classes on the interface, the packets that belong toqueue 1 to queue N1 can fairly get free bandwidth. When congestion takes place on the interface, it can stillbe ensured that the packets of each class can occupy the minimum bandwidth specified by the user. Comparedwith 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 defaultqueues can be logically considered as one queue, but actually, it is a WFQ queue. The packets that haveentered 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 ofN1 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 thequeue length reaches the maximum length, the policy of discarding tails shall be adopted by default. Butthe 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, thediscarding policy of WRED is also not required.

WREDDue to the limitation of memory resources, the traditional processing method is that all the incoming packetsare discarded when the queue length reaches the specified maximum length. For TCP packets, discardingof numerous packets will lead to TCP timeout, thus triggering the slow startup and congestion avoidingmechanism of TCP to slow down the transmission of TCP packets. When the packets of multiple TCPconnections are discarded from a queue at the same time, the slow startup and congestion avoiding mechanismwill be triggered for these TCP connections at the same time, which is called 'TCP global synchronization'. Inthis way, the packets sent from these TCP connections to the queue will be reduced simultaneously, so that thespeed of incoming packets of the queue is below the line transmission speed, thus reducing the utilization ratioof line bandwidth. Moreover, the traffic volume of the packets sent to the queue always changes abruptly, sothe traffic volume on the line always fluctuates between minimum quantity and saturation.



To avoid such kind of problem from occurrence, the discarding policy of WRED (Weighted Random EarlyDetection) can be adopted for the queues. The difference between WRED and RED is that IP priority isadopted and discarding policies are differentiated. The user can set the low threshold and high threshold forthe queue length. When the queue length is below the low threshold, no packet shall be discarded from thequeue. When the queue length is between the low and high thresholds, WRED starts to randomly discardpackets. Moreover, the discarding probability is high for long queues. When the queue length is higher thanthe 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 bereduced simultaneously, thus avoiding TCH global synchronization from occurrence. When the packets ofone TCP connection are discarded, the other TCP connections still maintain high transmission speed. In thisway, there are always packets sent at a high speed from one or multiple TCP connections at any time, thusenhancing the utilization ratio of line bandwidth.

If queue length, low threshold and high threshold are directly adopted for discarding packets as well as forcomparison, burst data streams shall be treated unfairly, which is unfavorable for the transmission of datastreams. Therefore, during the comparison of queue length, low threshold and high threshold, and discardingof packets, the average length of queues (relative value based on the comparison of the specified thresholdsand average length) is adopted. The average length of queues is the result of low-pass filtration. It reflectsthe changing trend of the queues, and is non-sensitive to the burst changing of queue length. So the unfairtreatment of burst data streams can be avoided.

When the queuing mechanism adopts WFQ, for the packets with different precedence levels, the user can setdifferent queue length filtration coefficients, low thresholds, high thresholds and discarding probabilities. Inthis 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.

Classification

Data packets to be

sent via this interface

queue 1

queue 2

queue N1

RED

discarding

Dequeue

scheduling

Data packets off

the interface

When WRED is adopted together and WFQ, stream-based WRED can be realized. When packet classificationis performed, different streams have their own queues. For a small stream, because the queue length isalways comparatively small, the discarding probability will also be comparatively small, whereas, thelarge stream will have comparatively large queue length, and hence more packets will be discarded, thusprotecting the benefits of small streams.

Even if WRED is adopted together with other queuing mechanisms, for a small stream, because the numberof packets is small, the discarding probability shall also be comparatively small. The benefits of smallstreams can also be protected.



Mapping relation between QoS and DSCPDiff-Serv is an IP QoS model that is applicable to the backbone network and can satisfy multiple servicerequirements. This model defines standard forwarding services such as Expedited Forwarding (EF), AssuredForwarding (AF), and so on.

In the Diff-Serv system, users can apply for services at different levels using the DS field of packet markingwhich is redefined from ToS field in the IP packet. The first 6 bits of DS field are DSCP (DS CodePoint) andthe group of the packets with the same DSCP value is called Behavior Aggregate (BA). A router reserves themapping of DSCP to Per-Hop Behaviors (PHB, the behaviors satisfying a forwarding requirement, such astraffic 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).



• EF PHB.

EF is defined as the forwarding process like this: The information flow rate sent from anyDiff-Serv node must in any case be equal to or higher than the set rate. EF PHB cannot beremarked 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 requiredto adapt to the features of EF PHB. When the 'tunneling' technology is adopted, an externalpacket needs to be marked as EF.

EF PHB aims to simulate the forwarding effect of Virtual Leased Line in the DS domain andprovides 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 serviceswith ISP, traffic is allowed to exceed the specifications of the subscription. For the traffic thatdoes not exceed the subscription specifications, the forwarding quality should be ensured. Forthe traffic that exceeds the specifications, it is hoped that they should be forwarded at a lowerQoS levels instead of being discarded simply.

Currently, four categories of AF have been defined, namely, AF1, AF2, AF3 and AF4. Eachcategory of AF service packet can be further divided into 3 drop precedence. AF code pointAFij means that AF category is i (1<= i <= 4) and drop precedence is j (1<= j <= 3). Whenproviding 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 theorder of the packets in the same information flow. For example, different packets in a serviceflow belong to the same AF level, but marked with different drop precedence during trafficpolicing. In this case, though there are different discarding probabilities for different packets,the order between them cannot be changed. This mechanism is especially applicable tomultimedia service transmission.

• BE PHB

This is the traditional IP packet delivery service, which only focuses on the reachability andrequires 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 RemarkingIn the course of flow control, SGSN may discard messages exceeding the specified threshold, or degradeDSCP class to lessen the impact upon the system.


Configuring IPSec Chapter 5: Gn/Gp Interface Configuration

Configuring IPSec■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

IPSec configuration includes creation of manual security policy, isakmp security policy and IPSec Dynamicsecurity Policy.

Description



IP protocol. Source portoperator.

Source port1.

Source port2.

DestinationIP.

Destinationmask.

Data flowparameter. Destination

portoperator.

Destinationport 1.

Destinationport 2.

Precedence. Type ofservice.

IPSECTransform.

IPSECProtocol.

AH AuthAlgorithm.

ESPencryptionalgorithm.

ESP AuthAlgorithm.

Encapsula-tion mode.

CompressAlgorithm.

Securitypolicynumber.

Peer IPaddress.

Input AHSPI.

Input AHkey string.

Input AHhexadecimalkey.

Input ESPSPI.

Output ESPkey string.

Input ESPhexadecimalencryptionkey.

Input ESPhexadecimalverificationkey.

Output AHSPI.

Input AHkey string.

Output AHhexadecimalkey.

IPSECmanualsecuritypolicy.

Output ESPSPI.

Output ESPkey string.

Output ESPhexadecimalencryptionkey.

Output ESPhexadecimalverificationkey.


Installation and Configuration: C-SGSN Data Configuration Configuring IPSec

Procedure

Create manual security policy:Step Operation Command

1 Configure Access control list. ADD ACL

2 Configure IPSEC Transform. ADD IPSECTRANS

3 Configure manual security policy. ADD IPSECMANUALCM

Create isakmp security policy:Step Operation Command

1 Configure Access control list. ADD ACL


3 Configure IKE security policy. ADD IKEPLC

4 (optional). Configure IKE pre-shared key. ADD IKEKEY

5 (optional). Configure peer RSA public key. ADD RSAPEER

6 (optional). Configure local RSA public andprivate keys.

ADD RSALOC

7 Configure IPSEC ISAKMPsecurity policy.

ADD IPSECISAKMPCM

Create IPSec Dynamic security Policy:Step Operation Command

1 (optional). Configure Access control list. ADD ACL


3 Configure IKE security policy. ADD IKEPLC

4 (optional). Configure IKE pre-shared key. ADD IKEKEY

5 (optional). Configure peer RSA public key. ADD RSAPEER

6 (optional). Configure local RSA public andprivate keys.

ADD RSALOC

7 Configure IPSEC dynamicsecurity policy.

ADD IPSECDYNCM

Step 4, 5 and 6 are optional. Whether step 4, 5 and 6 are necessary depends on IKE security policy.



Example

Create a security tunnel between SGSN and GGSN to protect data flow between them. Here, the router insteadof GGSN provides IPSec function. Figure 5-4 shows the IPSec configuration networking. The securityprotocol is ESP, the encryption algorithm is DES, and the verification algorithm is SHA1-HMAC-96.

Figure 5-4 IPSec configuration networking.

GGSN10.1.2..2

SGSN

Internet Serial4/1/2202.38.162.1

Serial2/0/1202.38.163.1

Router

10.1.2.1

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



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

IPSecIPSec (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 theInternet 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 AuthenticationHeader (AH) and the Encapsulating Security Payload (ESP). Additionally, these mechanisms are correctlyimplemented and deployed, so that they ought not to adversely affect users, hosts, and other Internetcomponents.

AH (Authentication Header) is a packet header authentication protocol, mainly to provide functions such asdata origin authentication, data integrity check and protection against replays. ESP (Encapsulating SecurityPayload) 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 IPSecwith automatic negotiation key exchange, establishment and maintenance of Security Association. It cansimplify IPSec application and management.

Some Concepts Related to IPSec ImplementationThe following concepts are related to IPSec Implementation.



• Data Flow.

Data flow is a set of packets flow with the same data characteristics. Data flow can berecognized by the source IP address or destination IP address. Also you can recognize them byprotocol type or port number. IPSec can enable different security protections for differentdata flow. For example, different security protocols, algorithms and shared keys will be usedfor different data flows.

• IPSec policy.

IPSec policy will be configured manually by user. It will specify security measures to be usedfor different data flows. For data flow definition will be implemented by configuring manyrules in access control list, quote this access control list in IPSec policy to specify the protecteddata 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 needsusers to configure the parameters such as key and spi and the latter automatically generatesthese parameters through IKE negotiation.

• IPSec policy Sets.

IPSec policy sets are collection for all IPSec policies having the same name and differentsequence numbers. On an interface, an IPSec policy set can be used or removed. In IPSecpolicy sets many IPSec policies can be used on this interface at the same time, so for implementdifferent security protections for different data flows. In one IPSec policy set, the smaller thesequence 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. Betweentwo security gateways, it is a two-way communication, so two security associations arerequired to provide separate security protection for inbound and outbound data flows. SecurityAssociation is identified uniquely by a triplet including Security Parameter Index (SPI),destination IP address, security protocol number (AH or ESP). The user can configure andmaintain security association manually, but he needs to configure more parameters. SecurityAssociation can also be established and maintained by IKE. IKE can automatically configureand 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 tothe traffic transmitted in the protection of IPSec, and the SA is invalid when the set valueis exceeded.

No matter which one of the two types expires first, the SA will get invalid. Before the SAis about to get invalid, IKE will set up a new SA for IPSec negotiation. So, a new SA isready before the existing one obtains invalid.



• 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 togetherform a triplet, to identify a specified Security Association uniquely. In manual configurationfor Security Association, manually assigning Security Parameter Index (SPI) is required. Toensure Security Association exclusiveness, different security parameter indexes must be usedto configure Security Association. When IKE negotiation creates Security Association, randomnumber will be used to generate Security Parameter Index (SPI).

• IPSec proposal.

IPSec proposal content includes security protocol, algorithm used by security protocol andpacket encapsulation format of security protocol. It specifies the mode to transform ordinary IPpacket into IPSec packet. In IPSec policy, quote an IPSec proposal so for specify the protocoland 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 bespecified for a security tunnel. A security tunnel corresponds to a protected data flow. Many security tunnelscan be configured between two security gateways. Security tunnel will be configured on the interfacesbetween two security gateways, such as Ethernet interface, synchronous/asynchronous serial interface. Thelocal 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. Accesscontrol 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 IKEautomatic negotiation (isakmp). The configuration of the former is a bit complicated, in which IPSec policyinformation and all information required by Security Association establishment must be manually entered, andsome advanced IPSec features (for example timing update for shared key) will not be supported. However, itsadvantage is that it can independently implement IPSec function without IKE. However the configurationof the latter is comparatively simple, in which only IPSec policy information needs to be configured. IKEautomatic negotiation will be used to establish and maintain Security Association. Using IKE negotiation toconfigure Security Association is herewith recommended.

While creating an IPSec policy, negotiation mode must be specified. Negotiation mode cannot be changed ifIPSec policy is established. To change negotiation mode, you can only delete the old IPSec policy and thenestablish a new one.

When IKE negotiation is specified, related IKE configuration needs to be done. For detailed operation, referto IKE configuration.



Specify security protocol, algorithm and encapsulation format

AH and ESP protocols are two kinds of security protocols. AH protocol can support MD5 and SHA-1authentication algorithm. ESP protocol can support MD5 and SHA-1 authentication algorithm, DES and3DES encryption algorithm. On the both ends of security tunnel, IPSec policy must be configured with thesame 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 putentire IP packet into protection, and add a new IP header in front of the original IP packet. The source anddestination 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 byIKE negotiation and no manual entering is required. If Security Association is configured manually, theabove information must be specified in advance.

On both ends of security tunnel, SPI and shared key of inbound Security Association on local end must bethe same as that of the peer outbound Security Association. The SPI and shared key of outbound SecurityAssociation 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 Associationand Key Management Protocol (ISAKMP). IKE will provide automatic negotiation and exchange of sharedkey 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. EmergingIPSec (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 ensuresecurity. In this case, the IKE automatic negotiation can be used to establish Security Association andexchange shared key.

IKE Security Mechanism

IKE has a series of self-protection mechanisms to safely distribute shared key, authenticate identity, andestablish IPSec Security Association and so on in unsecured network.

IKE security mechanism includes:



• Diffie-Hellman (DH) exchange and shared key distribution.

Diffie-Hellman algorithm is a shared key algorithm. The both parties in communication canexchange 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 ofIKE is that it never transmits shared key directly in the unsecured network, but calculatesthe 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 figureout 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 onthe security of other shared keys, because these secrets have no derivative relations amongthem. 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 differentauthentication keys to generate the same shared key between the two parties. Authenticationkey 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 implementingidentity data protection.

IKE using 2 stages to implement IPSec shared key negotiation and Security Associationcreation. In the first stage, parties involved in the communication will establish a channel foridentity authentication and security protection. An ISAKMP Security Association (ISAKMPSA) is established by the exchange in this stage. In the second stage, security channelestablished in phase 1 will be used to negotiate specific Security Association for IPSec andestablish 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.

Encrypted IP packet

TCP/UDP

IPSec

TCP/UDP

IPSecIP

IKE IKE

SA SA

SA negotiation

Router A Router B


Configuring OSPF Chapter 5: Gn/Gp Interface Configuration

Configuring OSPF■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Open Shortest Path First (OSPF) is an internal network gateway protocol developed by IETF based on linkstate. It is necessary to make some associated configuration before OSPF is enabled for the Gn/Gp interface.

Description



Basicinformation.

Interface IP. Slot number. Port number. Virtual portnumber.

Interfacepriority.

Interfacenetworktype.

IP ofneighboringnode.

Procedure

Step Operation Command1 Start OSPF protocol. STR BNET_OSPF_RIP

2 Add interface running OSPFprotocol.

ADD BNET_OSPF_NETWORK

3 Set property for OSPF interface. SET BNET_OSPF_PRO

4 Add neighboring node of OSPFprotocol.

ADD BNET_OSPF_NEIGHBOR

Example

;; Start OSPF protocol

STR BNET_OSPF_RIP: TYPE=OSPF;

;; Add an interface running OSPF protocol


Installation and Configuration: C-SGSN Data Configuration 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 CalculationThe routing calculation process of the OSPF protocol is as follows:

• Each OSPF-capable router maintains a Link State Database (LSDB), which describes thetopology of the whole AS. According to the network topology around itself, each routergenerates a Link State Advertisement (LSA). The routers on the network transmit the LSAsamong them by transmitting the protocol packets to each other. Thus, each router receives theLSAs of other routers and all these LSAs compose its LSDB.

• LSA describes the network topology around a router, so the LSDB describes the networktopology of the whole network. Routers can easily transform the LSDB to a weighted directedmap, which actually reflects the topology architecture of the whole network. Obviously, allthe routers get a graph exactly the same.

• A router uses the SPF algorithm to calculate the shortest path tree with itself as the root, thetree shows the routes to the nodes in the autonomous system. The external routing informationis leaf node. A router, which advertises the routes, also tags them and records the additionalinformation of the autonomous system. Obviously, the Routing tables obtained by differentrouters are different.

Furthermore, suppose that the routers are directly connected without other in-between routingdevices in a broadcast network. To enable the individual routers to broadcast the informationof their local statuses to the whole AS, any two routers in the environment should establishadjacency between them. In this case, however, the changes that any router takes will result inmultiple transmissions, which is not only unnecessary but also wastes the precious bandwidthresources. To solve this problem, 'Designated Router' (DR) is defined in the OSPF. Thus, all therouters 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 routecalculation. Also, it transmits and receives packets by IP multicast.

OSPF PacketsOSPF uses five types of packets:


Configuring OSPF Chapter 5: Gn/Gp Interface Configuration

• Hello Packet:

It is the common packet which is periodically sent by a router to its peer. It contains the valuesof 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 ownLSDBs, including the digest of each LSA. The digest refers to the HEAD of an LSA, whichcan be used to uniquely identify the LSA. Such reduces the traffic size transmitted between therouters, 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 arelacked in the local LSDBs. In this case, they will send LSR packets requesting for the neededLSAs 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 ofmultiple LSAs (complete contents).

• Link State Acknowledgment (LSAck) Packet.

The packet is used for acknowledging the received LSU packets. It contains the HEAD(s) ofLSA(s) requiring acknowledgement.

Related Concepts

• Router ID.

To run OSPF, a router must have a router ID. If no ID is configured, the system willautomatically select an IP address from the IP addresses of the current interface as the RouterID.

• DR (Designated Router).

Suppose there is a broadcast network environment, in which, the routers are directly connectedwithout other in-between routing devices. To enable the individual routers to broadcast theinformation of their local statuses to the whole AS, all routers in the environment shouldestablish adjacency. In this case, however, the changes that any router takes will result inmultiple transmissions, which are not only unnecessary but also waste the precious bandwidthresources. To solve the problem, OSPF defines the 'Designated Router' (DR). All the routersonly 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 electedby all the routers in the segment.


Installation and Configuration: C-SGSN Data Configuration Configuring OSPF

• BDR (Backup Designated Router).

If the DR fails for some faults, a new DR must be elected and synchronized with the otherrouters on the segment. This process will take a relatively long time, during which, the routecalculation is incorrect. To shorten the process, BDR is brought forth in OSPF. In fact, BDRis a backup for DR. DR and BDR are elected in the meantime. The adjacencies are alsoestablished between the BDR and all the routers on the segment, and routing information is alsoexchanged 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 runningOSPF, the large number of routers will result in an enormous LSDB, which will consumean 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 begenerated and transmitted in the network. This will lower the network bandwidth utility. Inaddition, 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 logicallygroup the routers. The borders of areas are formed by routers. Thus, some routers may belongto different areas. A router connects the backbone area and a non-backbone area is called AreaBorder 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 fromall 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 physicallyseparated areas can still maintain the logic connectivity.

• Route Summary.

AS is divided into different areas which are interconnected using OSPF ABRs. The routinginformation between areas can be reduced through route summary. Thus, the size of routingtable can be reduced and the calculation speed of the router can be improved. After finding anintra-area route of an area, the ABR will look up the routing table and encapsulate each OSPFroute into an LSA and send it outside the area.


Configuring RIP Chapter 5: Gn/Gp Interface Configuration

Configuring RIP■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Routing Information Protocol (RIP) is a simple dynamic routing protocol. It is necessary to perform RIPassociated configuration when RIP is required at the Gn/Gp interface.

Description



Basicinformation.

Interface IP. adjacentnode IP.

Procedure

Step Operation Operation1 Start RIP protocol. STR BNET_OSPF_RIP

2 Add an interface running RIPprotocol.

ADD BNET_RIP_NETWORK

3 Add an adjacent node of RIPprotocol.

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";


Installation and Configuration: C-SGSN Data Configuration Configuring RIP

Reference

Routing Information Protocol (RIP) is a relatively simple dynamic routing protocol, but it has a wideapplication. RIP is a kind of Distance-Vector (D-V) algorithm-based protocol and exchanges routinginformation using UDP packets. It employs Hop Count to measure the distance to the destination host, whichis called Routing Cost. In RIP, the hop count from a router to its directly connected network is 0, and that to anetwork which can be reached through another router is 1, and so on. To restrict the time to converge, RIPprescribes that the cost is an integer ranging between 0 and 15. The hop count equal to or exceeding 16 isdefined 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 oneneighboring network in 180 seconds, RIP will tag all routes of the neighboring network to be unreachable. Ifno routing refreshing message is received from one neighboring network in 300 seconds, RIP will finallyremove 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 allowsimporting the routes discovered by other routing protocols.

Each router running RIP manages a route database, which contains routing entries to all the reachabledestinations in the network. These routing entries contain the following information:


Configuring RIP Chapter 5: Gn/Gp Interface Configuration

• 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 forreaching 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 therange of 0 to 16.

• Timer: Duration from the last time that the routing entry is modified now. The timer is resetto 0 whenever a routing entry is modified.

• Route tag: Discriminate whether the route is generated by an interior routing protocol orby 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 tothe adjacent routers. Upon receiving the request packet, the adjacent routers (on which, RIPshould have been enabled) respond to the request by returning the response packets containinginformation of their local routing tables.

• After receiving the response packets, the router, which has sent the request, will modify itsown routing table.

• At the same time, RIP broadcasts its routing table to the adjacent routers every 30 seconds. Theadjacent routers will maintain their own routing table after receiving the packets and will selectan optimal route, and then advertise the modification information to their respective adjacentnetwork so for make the updated route globally known. Furthermore, RIP uses the timeoutmechanism to handle the out-timed routes so for ensure the real-timeliness and validity of theroutes. With these mechanisms, RIP, an interior routing protocol, enables the router to learn therouting information of the whole network.

RIP has become one of the actual standards of transmitting router and host routes by far. Itcan be used in most of the campus networks and the regional networks that are simple yetextensive. For larger and more complicated networks, RIP is not recommended.


Chapter

6Gb Interface Configuration (2.5G)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■


Gb Interface Configuration Overview Chapter 6: Gb Interface Configuration (2.5G)

Gb Interface Configuration Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Gb interface configuration includes link configuration, management entity configuration, protocol parameterconfiguration and cell reference parameter configuration. They should be done in sequence.


Installation and Configuration: C-SGSN Data Configuration Configuring Link and Management Entity

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 conditionsYou have completed board configuration.


Configuring Link and Management Entity Chapter 6: Gb Interface Configuration (2.5G)


BCparameter.

BC timeslotdistribution.

BC mode. FR protocolmode.

NS-VCparameter.

NS-VCI NSEI DLCI

NSEparameter.

BSSID

E1/T1parameter.

Check mode. Link frameformat.

Procedure

Step Operation Command1 Configure E1/T1. ADD E1T1CFG

2 Configure BC. ADD BC

3 Configure NSVC. ADD NSVC

4 Configure NSE. ADD NSE

Example

Figure 6-1 Gb interface configuration networking.

UGBI UEPI

UGBI UEPI

UGBI UEPI

SGSNBSS0

BSS1

460010001010001

460010001010002

460010001010003

460010001010004

460010002010001

460010002010002

460010002010003

460010002010004

0

1

2



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;






;;Configure BC.

ADD BC: FN=0, SN=0, PN=0, BCID=0, 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;






;;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;



Reference

Configure E1/T1

• Only after the E1/T1 ports of UEPI/UTPI are configured by using the commandADD E1T1CFG, the FR layer link can be connected.

• If there are more than one E1/T1s connected to a BSS, and the number of theUGBI boards configured for SGSN is greater than 1, the E1/T1s must beconnected to the UGBI boards uniformly.

E1 is the physical cable connecting BSS and SGSN. BSS can be connected with SGSN either directly orthrough the intermediate FR network.

In SGSN, the UEPI/UTPI provides E1/T1 physical interface, and the UFEU implements FR protocolprocessing.

UFEU has 8 E1 ports, numbered 0 to 7 respectively. E1/T1 cables can be led out of the 8 E1/T1 ports onUEPI/UTPI, as shown in Figure 6-2.

Figure 6-2 Numbering of the ports on UFEU.

UGBI

L O C A L

P C I

U E P I

001123U

FEU

23

UEPC 4

567

E1/T1

E1/T1

7

7654 U

T P I

/

Configure BCBC refers to the bearer channel of frame relay, corresponding to the timeslot group of E1/T1 cables. A BCcan be allocated with all available timeslots of an E1/T1, or only several of them. Its bandwidth equals tothe number of timeslots multiplies 64 kbit/s. BCs of the same E1/T1 cable are distinguished by BCID (BCIdentification).

The basic principles for BC allocation are as follows:



• 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 toSGSN and that to PCU should be transmitted through the same pair of E1 cables. Configureas many time slots of E1 as possible to one BC. For example, configure the 31 time slots toone BC. The BC mode at SGSN should correspond to the data configuration at PCU. ThePCU end is generally configured as DTE while the SGSN end as DCE. For example, if PCUis configured as DCE, SGSN has to be configured as DTE.

• If BSS and SGSN are connected through an intermediate FR network, both BSS and SGSNshould act as DTE. The two ends of the cable should negotiate about the distribution of thetime slots in BC.

PVCPermanent 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 shouldbe 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 atthe PCU side.

• If BSS is connected with SGSN directly in the point-to-point manner, the PVCscorresponding to NSVCs at the two ends should be the same, that is theparameters 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 ofBSSGP layer. One NS-VC on the NS layer corresponds to one PVC on FR. That means, if one NS-VC hasbeen 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 samewith that in BSS.

NS divides NS-VCs into different groups by their NSEIs. NS-VCs in the same group work in load sharingmode.

All NS-VCs in the same group (with the same NSEI) in SGSN are connected to only one BSS. One group ofNS-VCs corresponds to one group of cells. For a BSS can contain multiple BSCs, all the cells correspondingto the BSC can be taken as one group. Allocate NS-VCs to each cell group (the number of NS-VCs dependson 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 BCin the system. If a UGBI board has been configured with cells or SIG, it shall also be configured with theNS-VCs of the same NSEI. The number of NS-VCs allocated in this case depends on the total traffic volumeof the cells configured on the board.



The number of NS-VCs configured on one BC depends on the time slots occupied by the BC and shall satisfythe following condition: 10 kbit/s ≤ (the number of time slots occupied by the BC % 64 kbit/s) + the numberof NS-VCs to be configured on the BC ≤100 kbit/s.

NSEEach group of NS-VCs requires an NSE to manage the group. Likewise, each group of cells requires anSIG on the UGBI to manage the group. NSE and SIG are in one-to-one correspondence. SIG is createdautomatically accompanying the creation of NSE.

The configuration of NSEI should be consistent with the data configuration at thePCU side.


Installation and Configuration: C-SGSN Data Configuration Configuring Protocol Parameters

Configuring Protocol Parameters■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The setting of protocol parameters may have serious impact upon the system. It isrecommended to adopt system default values. You should kwow the case withouta doubt before making a modification to the parameter configuration.

It includes configuration of parameters of various protocol layers (NS, BSSGP and SNDCP) and Gbgeneral information.

Description



Procedure

Step Operation Command* Configure NS. SET NS

* Configure BSSGP. SET BSSGP

* Configure flow control switch. SET FLOWCTRL

* Configure SNDCP. SET SNDCP

* Configure GB. SET GB

Example

Set NS parameters, so that the number of NSVCs per board can be 250.

SET NS:NSVCNUM=250;


Configuring Protocol Parameters Chapter 6: Gb Interface Configuration (2.5G)

Reference

The protocol stack of the Gb interface is composed of SNDCP, LLC, BSSGP, NS and FR. The location of theprotocol stack of the Gb interface at the GPRS user plane is shown in Figure 6-3.

Figure 6-3 Gb protocol stack at the user plane.

Application

IP

SNDCP

LLC

GSM RF

RLC

MAC

MS

GSM RF L1bis

Relay

NetworkService

BSSGPRLC

MAC

BSS

Relay

L1bis L1

NetworkService

L2

IP

GTP-USNDCP

UDPLLC

BSSGP

SGSN

IP

L1

L2

IP

UDP

GTP-U

GGSNUm Gb Gn Gi

At the user plane, SNDCP, LLC, BSSGP and NS cooperate in transmitting N-PDU from GTP-U to BSS/MSor 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 transparentand unacknowledged signaling transmission channel for GMM/SM.

Figure 6-4 Gb protocol stack at the control plane.

BSSGPRelay

GMM/SM

LLC

RLC

MAC

GSM RF

GMM/SM

LLC

BSSGP

L1bis

Um GbMS BSS 2G-SGSN

NetworkService

RLC

MAC

GSM RF L1bis

NetworkService

SNDCPSubNetwork Dependent Convergence Protocol (SNDCP) controls the creation and release of the link underthe instruction of SM. It provides a uniform interface for various PDPs at the upper layer and permits PDPsof different types to be introduced to the upper layer. It also provides the upper layer with acknowledgedand unacknowledged data transmission services.

Major functions of the SNDCP protocol layer include:



• Multiplexing of multiple PDP activations;

• Mapping multiple network layer entities to the appropriate LLC connections through theN-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 theopposite 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 controlinformation;

• Segmenting N-PDU to several LL-PDUs and re-assembling multiple LL-PDUs belongingto the same packet to N-PDU;

• Providing the XID parameter negotiation between peer SNDCP entities at the network sideand 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 networklayer protocol used.

LLCLogical Link Control (LLC) provides logical links between SGSN and MS. It encapsulates the data orsignaling 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-PDUto BSS through the Gb interface (BSSGP, NS, FR). Then, BSS transmits LL-PDU to MS or in the oppositedirection the MS transmits it to SGSN. LLC shields the transmission details of the bottom layer from theupper layer.

The LLC protocol layer provides the following major functions:


Configuring Protocol Parameters Chapter 6: Gb Interface Configuration (2.5G)

• 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.

BSSGPAt SGSN, the Base Station Subsystem GPRS Protocol (BSSGP) layer is located between LLC and theNetwork System (NS) of the Gb protocol stack. It provides channels for the data and signaling transmissionbetween 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 radioinformation needed by RLC/MAC;

• In the uplink direction, the BSSGP at the BSS side transmits relevant radio informationprovided 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.

NSThe Network System (NS) protocol layer provides the upper layer with the PVC data link and transparent datatransmission 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 unacknowledgeddata transmission for the upper layer.

Major functions of the NS control sublayer include:



• Providing unacknowledged data transmission between BSS and SGSN for the upper layerthrough the PVC provided by FR;

• Providing link congestion indication for the upper layer through congestion report mechanismof FR;

• Providing the upper layer with status indication such as the change of link transmissioncapability;

• 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.


Configuring Cell Reference Parameters Chapter 6: Gb Interface Configuration (2.5G)

Configuring Cell Reference Parameters■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This part presents instructions to configure cell reference parameters. Upon the completion of theconfiguration, SGSN can establish cells on the UGBI boards recommended.

Description



Basicinformation.

UGBIsubracknumber, slotnumber.

Cell ID.

Procedure

Step Operation Command1 Add cell reference parameter. ADD CELLREF

Example

;; Add cell reference parameter

ADD CELLREF: CELLID="460008613900002", CELLFN=0, CELLSN=5;


Installation and Configuration: C-SGSN Data Configuration Configuring Cell Reference Parameters

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 completedat the SGSN side automatically. Cells at the SGSN side will be evenly distributed on as many UGBIboards as possible to meet the requirement for load sharing. The cells at the SGSN side can be distributedas recommended through the data configuration. Moreover, the existing cells can be deleted and theconfiguration 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 willdetermine whether to use the cell distribution advised by the user based on the actual running situation.


Configuring Cell Reference Parameters Chapter 6: Gb Interface Configuration (2.5G)



Chapter

7MM Configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■


MM Configuration Overview Chapter 7: MM Configuration

MM Configuration Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Mobility Management (MM) configuration in Motorola C-SGSN refers to the configurations for the followingprocedures 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 GPRSmobility management in the GSM and PMM for the packet mobility management in theUMTS system.

This section introduces configuration for GMM and PMM parameters. There is no restrictionto the configuration sequence.


Installation and Configuration: C-SGSN Data Configuration Configuring Authentication and Ciphering Parameters

Configuring Authentication and CipheringParameters■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration for authentication and ciphering parameters. The authentication andciphering procedures will function based on the preset parameters after this configuration.

Description


Data preparationsNone.

Procedure

Step Operation Command1 Modify authentication and

ciphering parameters (2G).SET GMM

2 Modify authentication andciphering parameters (3G).

SET PMM

3 Mod Authentication FailureTable.

SET AUTHFAIL

Example

;;Modify the GMM parameter PTMSIREALLOC to NO.

SET GMM: PTMSIREALLOC=NO;


Configuring Authentication and Ciphering Parameters Chapter 7: MM Configuration

Reference

AuthenticationThe SGSN initiates the 'GSM authentication'. It implies authentication of the MS by the network andestablishment 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 ofan MS by the network and the authentication of the network by the MS. It also implies establishment of a newUMTS 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, SGSNcan 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 authenticationand ciphering controlled global switch. The authentication and ciphering parameters configured are availableonly when this switch is set to on. If the switch is set to off, no authentication or ciphering procedure will start.

CipheringFigure 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 onlyfrom 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. Thealgorithms include GEA_1(2.5G),GEA_2 (2.5G), NO_ENCRYPTION (3G) and UEA1 (3G).

IMEI checkIf an EIR exists in the network, SGSN can perform IMEI check and decide whether the involved MS can beaccessed to the system based on the check result.

P-TMSIUsually the network does not directly use an IMSI but uses a P-TMSI allocated by the SGSN as a temporaryMS identity between the MS and the SGSN.

The reallocation procedure guarantees the randomness of the temporary identity. This avoids the leakage ofthe user identity.

You may specify whether to start P-TMSI reallocation.


Installation and Configuration: C-SGSN Data Configuration Configuring Authentication and Ciphering Parameters

Authentication failure configurationAuthentication failure configuration includes the configuration of two parameters, CAFTIMES andPURPERIOD (UserPurgePeriod). If the number of subscriber authentication failures exceeds the value ofCAFTIMES during a user purge period, the system will generate an alarm. If the number of subscriberauthentication failures donot exceed the value of CAFTIMES during a user purge period, the subscriberauthentication failure records will be purged when the next user purge period starts.


Configuring Timers Chapter 7: MM Configuration

Configuring Timers■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Timer settings might severely effect system functions. Therefore, modify the timerconfigurations with care. Normally you may adopt the default timer settingsof the system.

This section introduces the configuration for MM dependent timers. The preset timers will affect MMprocedures.

Description

Preset ConditionsNone.


Procedure

Step Operation Command1 Modify the subscriber database

timer.SET SDBTMR

2 Modify the GMM timer (2.5G). SET GMMTMR

3 Modify the PMM timer (3G). SET PMMTMR

Example

;;Modify the PMM timer length to 40.

SET PMMTMR: PRDTMR=40;


Installation and Configuration: C-SGSN Data Configuration 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 asignaling response message. The SGSN will resend the request or terminate the ongoing procedure if it hasnot 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 orthe MS must start the corresponding procedure. These timers include Period-RAU Timer, MSreachable Timer and PTMSI Realloc Timer. These timers are usually dependent on the serviceand 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 dataand dynamic data. The Subscriber Index Processing Unit (SIPU) on URCU0 is used to recordon which USPU the subscription data is stored.

To reduce signaling exchanges with HLR, the MS subscription data will not be deletedfrom SDB immediately after an MS has been detached. Instead, the data will be kept for aperiod of time. If a super-charger is supported by the system, and is also supported in MS'ssubscription data, its subscription data will be sustained after MS detachment so long as theSDB Table is not full.

SDB timer configuration refers to the configuration parameters such as 'Purge Ms TimerLength', 'Check Time On SIPU' and 'Check Time On USPU'. The initial values for theseparameters have been set during system initialization. Generally, they do not need modification.


Configuring PLMN Chapter 7: MM Configuration

Configuring PLMN■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configurations for HPLMN, peer PLMN and connected PLMN. The subscribers inthe HPLMN or the connected PLMN can be attached to this SGSN or the peer PLMN after the configurations.

Description

Preset ConditionsNone.


Basic information. MCC and MNC ofHPLMN.

MCC and MNC of peerPLMN.

MCC and MNC ofconnected PLMN.

Procedure

Step Operation Command1 Add a HPLMN. ADD HPLMN

2 Add a connected PLMN. ADD CONNECTPLMN

3 Add a peer PLMN. 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 useMOD SYS or SET OFI to configure the HPLMN supported by the system by default and use ADD HPLMNto configure other HPLMN.


Installation and Configuration: C-SGSN Data Configuration 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 allowthe 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 anetwork. 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 ofPLMN, the MS can detect the peer HPLMN and select it or the HPLMN.


Configuring Paging Parameters Chapter 7: MM Configuration

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 pagingor CS paging after this configuration.

Description

Preset ConditionsThe Iu interface configuration has finished.


Basic information. LAI of the nullrouting area.

RAC of the nullrouting area.

RAI-RNC mappingrelation.

Procedure

Step Operation Command1 Add null routing area. ADD NRA

2 Add 3G Paging Table. ADD 3GPAGING

Step 2 is mandatory in 3G network only.


Installation and Configuration: C-SGSN Data Configuration Configuring Paging Parameters

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 Nullrouting 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 shouldbe 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, thenthe MTS-U/VLR executes paging for circuit-switched services using the SGSN. If the MS is in STANDBYstate, 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.


Configuring Paging Parameters Chapter 7: MM Configuration



Chapter

8SM Configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■


SM Configuration Overview Chapter 8: SM Configuration

SM Configuration Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Session Management (SM) configuration includes the configuration for SM parameters, mapping relationsbetween PDP type and Access Point Name Network Identifier (APN NI) and Shared Public Land MobileNetwork Operator Identifier (PLMN OI) list. There is no sequence restriction to the configurations.


Installation and Configuration: C-SGSN Data Configuration Configuring SM Parameters

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 conditionsThe MM configuration has finished.


Procedure

Step Operation Command1 Modify 2G SM protocol

parameter.SET 2GSM

2 Modify 3G SM protocolparameter.

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' toon when configuring MM parameters.


Configuring SM Parameters Chapter 8: SM Configuration

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 RadioAccess Bearer (RAB) between SGSN and RNC/MS.

Optional functions in SMYou may specify whether to enable some functions in the SM procedures by configuring the correspondingparameters. These parameters include 'Security in SM enable', 'PFT enable' and 'Preservation procedureenable'.

SM timersFunctionally, 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 asignaling response message. The SGSN will resend the request or terminate the ongoing procedure if it hasnot 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 definingthe time limit for BSS to store BSS packet context. If such a timer expires, the network nodemust start the corresponding procedure. These timers are dependent on the service and networkproviders 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.

QoSWhile creating the packet transmission route, the session management procedure should also specify the QoSfor this route. A QoS negotiation will be performed among MS, RNC, SGSN and GGSN during the sessionmanagement 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.


Installation and Configuration: C-SGSN Data Configuration Configuring SM Parameters

RAB QoS negotiationWhen establishing an RAB through negotiations with an RNC, the SGSN supports two QoS negotiationmodes. In mode 1, the SGSN specifies a percentage between an available bit rate and the first bit rate for anRAB. If it cannot provide the first bit rate, the RNC will attempt to use the available bit rate (the percentagex the first bit rate) to create an RAB. If the attempt fails, the RNC will return a failure message. Note thatboth the SGSN and RNC shall support protocol R4 in this mode. In mode 2, the SGSN negotiates the QoSwith the RNC in descending order of bit rate. The possible bit rates are in a negotiated bit rate list. If theRNC does not support the MS requested bit rate, the SGSN will select the bit rate of lower based on thesettings in the negotiated bit rate list to re-negotiate with the RNC until an RAB is successfully set up or theRNC fails to support the rate of the lowest priority.

APN resolutionAccess Point Name (APN) is a logical name referring to the external packet data network and/or to a servicethat the subscriber is to access. It consists two parts: APN Network Identifier (NI) and APN OperatorIdentifier (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 requiredby 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 activationrequest, the SGSN can adopt the preset OI to resolute the GGSN if necessary.


Configuring Mapping between PDP Type and APN NI Chapter 8: SM Configuration

Configuring Mapping between PDP Type and APN NI■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration for the mapping relations between PDP types and APN NI. After theconfiguration, the SGSN can retrieve the corresponding APN NI based on the PDP type.

Description



Basic information. PDP type. APNNI

Procedure

Step Operation Command1 Add the mapping relation between

a PDP TYPE and an APN NI.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 Mappingrelationship between PDP TYPE and APN NI Table will be used to find the corresponding APN:


Installation and Configuration: C-SGSN Data Configuration Configuring Mapping between PDP Type and APN NI

1. The activation request carries no PDP address or APN and there is only one set of subscribeddata with APN '*';

2. The activation request carries the PDP type and there is only one set of subscribed datamatching with this PDP type. Moreover, the subscribed APN is '*'.


Configuring Shared PLMN OI Chapter 8: SM Configuration

Configuring Shared PLMN OI■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration for a shared PLMN OI. After the configuration, the SGSN can querythe GGSN based on the shared PLMN OI during MS's PDP context activation.

Description

Preset conditionsThe configuration for the shared PLMN has finished.


Basic information. GGSN IP

Procedure

Step Operation Command1 Add a shared PLMN OI. 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 OIis allowed in the subscription data, the SGSN will initiate DNS resolution using the APNbased on the VPLMN OI, shared PLMN OI or HPLMN OI in order of precedence (it triesthe APN based on the VPLMN OI first)

2. If the activation request from the roaming MS carries an APN OI and the VPLMN OI is allowedin the subscription data, the carried APN OI might be the VPLMNM OI or shared PLMN OI.


Installation and Configuration: C-SGSN Data Configuration Configuring IP Address of GGSN supporting MIP or DHCP

Configuring IP Address of GGSN supporting MIPor DHCP■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration for IP Address of GGSN supporting MIP or DHCP, the SGSN canquery the GGSN supporting MIP or DHCP while the APN name is 'MIPv4FA' or 'dhcp'.

Description



Procedure

Step Operation Command1 Add IP address of GGSN that

supports MIPv4 service.ADD MIPGIP

2 Add IP address of GGSN thatsupports DHCP service.

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";


Configuring IP Address of GGSN supporting MIP or DHCP Chapter 8: SM Configuration

Reference

When External PDN Address Allocation is used, it is the responsibility of the MS and the PDN to allocate andrelease the dynamic PDP address by means of protocols such as DHCP or MIP. In case of DHCP, the GGSNprovides 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 SGSNneed not initiate DNS parse on the APN. Instead, it shall query the configuration information to obtain the IPaddress of the GGSN that supports MIPv4 or DHCP service.


Chapter

9Service Configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■


Configuring SMS Chapter 9: Service Configuration

Configuring SMS■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section describes the Short Message Service (SMS) protocol parameters configuration for the SGSN toprocess short message services. Generally, you need not perform the configuration.

Description


Data preparationsNone

Procedure

Step Operation Command1 Modify the SMS protocol

configuration list.SET SMS

Example

None

Reference

If SM-MT or SM-MO setting requires authentication, it is necessary to turn on theEncryption and Authentication switch when configuring mobile managementparameters.


Installation and Configuration: C-SGSN Data Configuration Configuring SMS

SMS is a basic telecommunication service. It provides short message receiving/transmitting services forsubscribers. These services include Short Message Mobile Originated (SMMO), Short Message MobileTerminated (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 SMS network architecture.

MS

UE

BSS

UTRAN

SGSNSMS-GMSC

SMS-IWMSC

HLR

SM-SCUm Gb Gd

Uu

IuGr

C

In Figure 9-1, the Gb interface or Iu interface and the Gd interface are responsible for forwarding shortmessages. The C interface provides routing function for the MS to receive short messages. The Gr interfaceperforms 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.


Configuring CAMEL service Chapter 9: Service Configuration

Configuring CAMEL service■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section describes the CAMEL Service configuration for SGSN to process intelligent network services.

Description

Preset conditionsDuring the MAP configuration (by carrying out SET MAPFUNC), the CAMEL versions supported by theSGSN have been set correctly.


Procedure

Step Operation Command1 Modify the CAMEL-supporting

mode.SET CAMELSPT

2 Add the IMSI/MSISDN numbersegment used to trigger CAMELGPRS services.

ADD IMSILIST/ADDMSISDNLIST

3 Add the IMSI/SMS MSISDNnumber segment used to triggerCAMEL SMS services.

ADD IMSILIST/ADDMSISDNLIST

4 Modify the CAMEL timer. 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.


Installation and Configuration: C-SGSN Data Configuration Configuring CAMEL service

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 ServicesSGSN supports CAMEL GPRS services and CAMEL SMS services.

CAMEL GPRS services: gsMTS-UF in SGSN controls CAMEL subscribers access and CAMEL PDPconversations. 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 modeThere 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-relatedinformation. The SGSN processes the CAMEL subscriber according to the subscription information providedby HLR.

In the latter mode, the subscription information of the CAMEL subscriber does not contain CAMEL-relatedinformation. The SGSN checks whether the subscriber is a CAMEL subscriber based on the MSISDN orIMSI 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 timerThe SGSN has set initial values to each CAMEL timer during initialization. Generally, you can skip themodification. Otherwise, you may carry out SET INSMTMR to modify the timer.


Configuring LCS Chapter 9: Service Configuration

Configuring LCS■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

If LCS setting requires authentication, it is necessary to turn on the Encryptionand Authentication switch when configuring mobile management parameters.

This section describes the LoCation Service (LCS) configuration for SGSN to process location services.

Description




Installation and Configuration: C-SGSN Data Configuration Configuring LCS

Procedure

Step Operation Command1 Configure the LCS parameter list. SET LCSPARA

2 Configure the mapping relations between SAI and the geographiccoordinate.

ADD SAIGEO

3 Configure the mapping relations between CELLID and thegeographic coordinate.

ADD CELLGEO

4 Configure the mapping relations between addresses of the SGSNcontrol plane and SGSN numbers.

ADD SGSNIPNUM

5 Configure the mapping relations between LCS Client and its homeGMLC number.

ADD GMLCCLIENT

6 Configure a GMLC in HPLMN. ADD GMLCINHPLMN

Example

;; Modify the LCS Privacy Verify Timer to 30,000 ms, the LCS Location Report Timer to 25,000 ms, theGMLC Response Timer to 25,000 ms and the MOLR Continue Timer to 15,000 ms. LCS does not requireverification. 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 5°15'25" north and longitude 35°45'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 5°15'25" north and longitude 35°45'55" west,radius ofcell 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 ofSGSN control plane of 191.22.37.101, and SGSN number of 861390123456789:

ADD SGSNIPNUM: SGSNIP="191.22.37.101", SGSNNUM="861390123456789";



Reference

LCS refers to the procedures related to UE location request, location measurement and calculation, andlocation result transmission performed by the mobile telecommunications system. The procedures include thePS_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 onthe information. These services include on-demand services, information customization and servicecustomization.

LCS is applicable to many services such as the commercial location service (value-added service), internallocation service, emergency location service and lawful interception service.

In the network structure of 3GPP releases, LCS is a relatively independent system affiliated to the corenetwork, as shown in Figure 9-2.

Figure 9-2 LCS network structure.

GMLC

3G-SGSN

GERAN

UTRAN

UE

Lg

Le

IuLg

Um

Uu

External LCSClient

2G-SGSNGb HLR

Lh

External LCS Client is the application server for the location-based services. It has a connection with GMLCthrough the Le interface. External LCS Client initiates location requests, and utilizes the location resultsto 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 throughLh interface. After that, it initiates a location request to VMTS or SGSN through Lg interface. Finally, itreturns 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 messagetransmitting, and management of subscriber information storage.

RNC performs the location measurement and calculation function of the LCS system.

LCS parametersThe LCS parameter list defines the lengths of various LCS timers. It also defines whether to authenticatethe LCS procedure and whether to limit GLMC in HPLMN. The SGSN has set initial values to each LCStimer during initialization. Generally, you may skip the modification.

Location calculationIn 2.5G, the SGSN locates a subscriber in the geographic coordinate according to the cell ID. In 3G, theSGSN locates a subscriber in the geographic coordinate according to SAI.


Installation and Configuration: C-SGSN Data Configuration Configuring LCS

Because of inaccuracy in locating, there is difference between the actual position of a subscriber and theobtained position in the geographic coordinate. The difference depends on the radius of the cell or theservice area.

Mapping relations between GMLC and LCS CLIENTIn the MO location service, the SGSN queries the mapping relation table of GMLC and LCS CLIENTaccording to the LCS CLIENT information in the information sent by a MS to obtain the correspondingGMLC.

If it is set in the LCS software parameter configuration that the GMLC belongs to HPLMN, the SGSN willjudge 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 locationThere are two types of LCS: instant location services and delayed location services. The instant locationservice means that subscribers can obtain their location information instantly if they attach the SGSN. Thedelayed location service means that if subscribers do not attach the SGSN, the SGSN will report theirlocation information when they attach the SGSN.

In the course of delayed location, when a subscriber attaches another SGSN, it is necessary to get the SGSNnumber as per the corresponding IP address, and forwards the SGSN number to GMLC by the message fromSGSM to GMLC. Upon receipt of the SGSN number, the GMLC originates a location procedure to the SGSNto which the subscriber attaches. If there is no configuration for mapping relation between IP address ofSGSN control plane and SGSN number, the message reported by SGSN to GMLC will not contain SGSNnumber. Therefore, GMLC must request HLR for the corresponding SGSN number before originating alocation procedure to the SGSN to which the subscriber attaches.


Chapter

10Charging Configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■


Charging Configuration Overview Chapter 10: Charging Configuration

Charging Configuration Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The charging configuration includes the Ga interface software parameter configuration, CG and routeconfiguration, charging characteristic configuration, CDR format configuration, charging behaviorconfiguration and special charging rate period. You should follow the above sequence to implementthe configuration.


Installation and Configuration: C-SGSN Data Configuration Configuring Ga Interface Parameters

Configuring Ga Interface Parameters■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration of the Ga interface parameters. SGSN will work according to theconfigured parameters.

Description

Preset ConditionsNone

Data PreparationsNone

Procedure

Step Operation Command1 Configure the Ga interface

parameters.SET CHGGA

Example

;;Modify the Ga interface parameters

SET CHGGA: GCR=R99, UCR=R4, CHGVER99=GPP32015V3A0;

Reference

CDR protocol versionSGSN 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.015V3.6.0 and 3GPP 32.015 V3.a.0. R4 supports 3GPP 32.215 V4.4.0.


Configuring Ga Interface Parameters Chapter 10: Charging Configuration

CDR resending parametersIf there is no response from the CG after the CDR is sent, SGSN can resend the CDR. The operator can set thenumber of resending times and the time to wait for the response. Usually it is not necessary to modify theinitial settings provided by the system.

Hard disk alarm parametersWhen the communication between CG and SGSN is interrupted, SGSN will temporarily save the CDR to theUBSU 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 thehard disk space-lack alarm threshold.


Installation and Configuration: C-SGSN Data Configuration Configuring CG and Route between SGSN and CG

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 theconfiguration, SGSN can communicate with the CG normally.

Description



Basicinformationof CG.

IP address. Priority. UDPreceivingport number.

UDP sendingport number.

TCP listenport number.

Protocolreleasesupported

Routeinformation.

UCDRsubracknumber, slotnumber.

UHPUsubracknumber slotnumber,forwardingenginenumber

ULPIinterface IPaddress

Ga port routeplanning


Configuring CG and Route between SGSN and CG Chapter 10: Charging Configuration

Procedure

Step Operation Command1 Configure CG information. ADD CHGCG

2 Configure the IPoA PVC betweenUCDR and UHPU.

ADD SGSN_IP_IPOA_PVC

3 (Optional). Configure the ULPI port backuprelation.

ADD BNET_NET-WORK_BACKUP

4 Configure the IP of ULPI port. ADD BNET_GFI_IF_IP

5 Add the SGSN-to-CG IP route. ADD BNET_IP_ROUTE

Example

Figure 10-1 Ga interface network example.

BNET

LAN Switch

192.22.88.253

192.5.5.5

FEA:10.21.40.37

FEB:10.21.41.37

10.88.40.13

ROUTER

192.5.5.1

CG:192.22.88.15

IPOA

U

R

C

U

PSM

U

C

D

R

U

C

D

R U

L

P

U

U

N

E

T

U

H

P

U

U

L

P

I

Figure 10-1 shows the system network. The UCDR is located in Subrack 0, Slot 10. The UHPU is located inSubrack 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


Installation and Configuration: C-SGSN Data Configuration Configuring CG and Route between SGSN and CG

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

CGThe CG information includes the IP address, priority, GTP' bearing protocol and CG protocol version. ForCG with GTP' bearing protocol as UDP, the configuration information includes the sending port numberand the receiving port number For CG with GTP' bearing protocol as TCP, the configuration informationincludes the TCP listen port number

You can connect one SGSN to maximum 10 CGs. The records of CG Information Table should comply withthe configuration regulations as follows:

1. 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.

2. For CG with GTP' bearing protocol as TCP, the IP address and TCP listen port of a CGidentify a unique record.

3. The CGs with the same IP address cannot share the same SPN, RPN and TCPPORT. If the2.5G CDRs and 3G CDRs are sent to the same CG, it is necessary to configure two CGrecords with the same IP but different ports.

4. If the setting of the protocol release of the CG is incorrect, the CG cannot browse and combinethe bills sent from the GSN although the communication between them is normal.

When one SGSN is connected with multiple CGs, the CDR sending is based on the following principles insequence:

1. Send CDRs to the CG addresses specified by the charging behavior (See the chargingbehavior configuration).

2. Send CDRs to the CG addresses specified by the charging characteristics (See the chargingcharacteristics configuration).

3. Send CDRs to the CG addresses as recommended in GGSN.

4. Send CDRs to the CG addresses according to the priority of CGs. 0 is for the highest prioritywhile 5 the lowest.

5. Lastly, for the CGs with the same priority and of the same type, send CDRs according to CGload size. CDRs will be sent to the CG with lower load prior to the CG with higher load.


Configuring CG and Route between SGSN and CG Chapter 10: Charging Configuration

SGSN-to-CG RouteIn 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 therouting 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 portprovides 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 canbuild 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 subscriberto specify theIP address bound to the port. The subscriber only has to specify the UCDR position, the UHPUposition and the forwarding engine.The destination IP address of the IP packet from the UCDR might be in different network segmentwith that of the ULPI/ULPC interface. Therefore, you should configure an IP route indicating theULPI/ULPC interface to the destination IP address.


Installation and Configuration: C-SGSN Data Configuration Configuring Charging Characteristic Parameters and Default Charging Characteristics

Configuring Charging Characteristic Parametersand Default Charging Characteristics■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration of charging characteristic parameters. After the configuration, SGSNwill charge the subscriber of a certain type of charging characteristic according to the configuration.

Description



Basicinformation.

The MNCand MCCof thesubscriber.

Procedure

Step Operation Command1 Configure the charging

characteristic parameters.SET CHGCHAR

2 Configure the subscriber's defaultcharging characteristics.

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;


Configuring Charging Characteristic Parameters and Default Charging Characteristics Chapter 10: Charging Configuration

Reference

Charging characteristicsThere are four types of charging characteristics:

• NORMAL (normal charging characteristic): The subscriber pays the charges on a periodicbasis, for example, on a monthly basis.

• HOTBILLING (hotbilling charging characteristic): The subscriber pays the charges rightafter the conversation.

• FLATRATE (flatrate charging characteristic): The subscriber pays the charges on a periodicbasis, 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 amountof charges before obtaining certain services. If the prepaid charge is not enough to cover theexpenses 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 toprovide all types of CDRs. Therefore, you can decide through the configuration whether togenerate the CDR.

When you specify to generate M-CDR and S-CDR, you also need to specify the generationconditions, for example, the period for periodically generating M-CDR.

• Service restriction flag

This flag indicating whether SGSN will restrict the subscriber service of this chargingcharacteristic when the buffer is full.

• IP address of CG

The CDR for the subscriber of this charging characteristic is preferentially sent to the IPaddress of CG. The priority of this CG is higher than that of the CG recommended by GGSN orother CGs or the CG configured by using ADD CHGCG but lower than the CG specified inthe charging behavior.


Installation and Configuration: C-SGSN Data Configuration Configuring Charging Characteristic Parameters and Default Charging Characteristics

Default charging characteristicsUsually the HLR provides SGSN with the charging characteristic as the subscription data. If the subscriptiondata 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 wherethe 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 characteristicsfor the visiting and roaming subscribers of the specified PLMN. For the visiting or roamingsubscribers whose default charging characteristics are not configured by using the ADDCHGDCHAR command, the default charging characteristics configured in the MOD CHGCDRcommand will be used.


Configuring CDR Optional Field Chapter 10: Charging Configuration

Configuring CDR Optional Field■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the CDR as well as its configuration. After the configuration, the CDR that isgenerated by SGSN will only contain the fields specified by the operator.

Description



Procedure

Step Operation Command1 Configuring CDR parameters. 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.


Installation and Configuration: C-SGSN Data Configuration Configuring CDR Optional Field

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 Conditionsare specified as part of the field definition.O:This field is optional and configurable either using additional TMN management functionsor by using manufacturer specific means.OM:This is a field that, if provisioned by the operator to be present, shall always be included in theCDRs. 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 CDRswhen the required conditions are met. In other words, an OC parameter that is configured to bepresent is a conditional parameter.

Table 10-1 S-CDR.

Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0Record Type. SGSN PDP

contextrecord.

M M M M M

NetworkInitiatedPDPContext.

A flag that ispresent if thisis a networkinitiated PDPcontext.

C C C C OC

ServedMSISDN.

The primaryMSISDNof thesubscriber.

M O O OM

Cont.



Table 10-1 S-CDR. (Continued)

Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0SystemType.

Indicatesthe type ofair interfaceused, forexampleUTRAN.This fieldis presentwhen eitherthe UTRANor GERANair-interfaceis used. Itis omittedwhen theservice isprovided bya GSM airinterface.

C C OC

ServedIMSI.

IMSI of theserved party.

M M M M M

ServedIMEI.

The IMEI ofthe ME, ifavailable.

C C C C OC

SGSNAddress.

The IPaddress ofthe currentSGSN.

M M M M OM

MS NetworkCapability.

The mobilestationNetworkCapability.

O O O O OM

RoutingArea code.

RAC atthe timeof 'RecordOpeningTime'.

O O O O OM

Local AreaCode.

LAC atthe timeof 'RecordOpeningTime'.

O O O O OM

Cont.




Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0Cell Identity. Cell identity

for GSM orService AreaCode (SAC)for UMTSat the timeof 'RecordOpeningTime'.

O O O O OM

Charging ID. PDP contextidentifierused toidentify thisPDP contextin differentrecordscreated byGSNs

M M M M M

GGSNAddressUsed.

The controlplane IPaddress ofthe GGSNcurrentlyused. TheGGSNaddress isalways thesame foran activatedPDP context.

M M M M M

AccessPoint NameNetworkIdentifier.

The logicalname of theconnectedaccesspoint tothe externalpacket datanetwork(networkidentifierpart ofAPN).

M M M M OM

Cont.




Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0APNSelectionMode.

An indexindicatinghow the APNwas selected.

O O O O OM

AccessPoint NameOperatorIdentifier.

The OperatorIdentifierpart of theAPN.

M M M M OM

PDP Type. PDP type,that isIP, PPP,IHOSS:OSP.

M M M M OM

Served PDPAddress.

PDP addressof the servedIMSI, thatis IPv4 orIPv6. Thisparametershall bepresentexcept whenboth the PDPtype is PPPand dynamicPDP addressassignmentis used.

M M C C OC

Cont.




Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0List ofTraffic DataVolumes.

A list ofchangesin charg-ing condi-tions for thisPDP context,each changeis timestamped.Chargingconditionsare usedto catego-rize trafficvolumes,such as perQoS/tariffperiod. Ini-tial and sub-sequentlychanged QoSand corre-spondingdata volumesare listed.

M M M M OM

RecordOpeningTime.

Time stampwhen PDPcontext isactivated inthis SGSNor recordopeningtime onsubsequentpartialrecords.

M M M M M

Duration. Duration ofthis record inthe SGSN.

M M M M M

SGSNChange.

Presentif this isfirst recordafter SGSNchange.

C C C C C

Cont.




Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0Cause forRecordClosing.

The reasonfor closureof the recordfrom thisSGSN.

M M M M M

Diagnostics. A moredetailedreason forthe releaseof theconnection.

O O O O OM

RecordSequenceNumber.

Partialrecordsequencenumber inthis SGSN.Only presentin caseof partialrecords.

C C C C C

Node ID. Name of therecordingentity.

O O O O OM

RecordExtensions.

A set of net-work opera-tor/manufac-turer specificextensions tothe record.Conditionedupon the ex-istence of anextension.

O O O O OC

LocalRecordSequenceNumber.

Consecutiverecordnumbercreated bythis node.The numberis allocatedsequentiallyincluding allCDR types.

O O O O OM

Cont.




Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0RNC UnsentDownlinkVolume.

Thedownlinkdata volumewhich theRNC has notsent to MS.This field ispresent whenthe RNChas providedunsentdownlinkvolumecount atRAB release.

C C OC

CAMELInformation.

Set ofCAMELinformationrelated toPDP context.For moreinformationseeDescriptionof RecordFields. Thisfield ispresent ifCAMELservice isactivated.

C C OC

ChargingCharacter-istics.

The Charg-ing Charac-teristics ap-plied to thePDP context.

C C M

ChargingCharacteris-tics SelectionMode.

Holds infor-mation abouthow Charg-ing Charac-teristics wereselected.

OM



Table 10-2 M-CDR.

Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0Record Type. SGSN

mobilitymanagementrecord.

M M M M M

ServedIMSI.

IMSI of theMS.

M M M M M

ServedIMEI.


C C C C OC

ServedMSISDN.


O O OM

SGSNAddress.

The IPaddress ofthe currentSGSN.

M M M M OM


The mobilestationnetworkcapability.

O O O O OM

RoutingArea code.

RoutingArea atthe time ofthe RecordOpeningTime.

O O O O OM

Local AreaCode.

LocationArea Codeat the timeof RecordOpeningTime.

O O O O OM

Cell Identity. The CellIdentity forGSM orService AreaCode (SAC)for UMTS atthe time ofthe RecordOpeningTime.

O O O O OM

Cont.



Table 10-2 M-CDR. (Continued)

Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0Change ofLocation.

A list ofchangesin RoutingArea Code,each with atime stamp.This field isnot requiredif partialrecords aregeneratedwhen thelocationchanges.

O O O O OC

RecordOpeningTime.

Timestampwhen MS isattached tothis SGSNor recordopening timeon followingpartialrecord.

M M M M M

Duration. Duration ofthis record.

O O O O OM

SGSNChange.

Presentif this isfirst recordafter SGSNchange.

C C C C C

Cause forRecordClosing.

The reasonfor theclosure ofthe record inthis SGSN.

M M M M M

Diagnostics. A moredetailedreason forthe releaseof theconnection.

O O O O OM

Cont.




Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0RecordSequenceNumber.

Partialrecordsequencenumber inthis SGSN;only presentin caseof partialrecords.

C C C C C


O O O O OM

RecordExtensions.


O O O O OC



O O O O OM


The Charg-ing Char-acteristicsused by theSGSN.

C C M

Cont.




Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0SystemType.


C C OC

CAMELInformation.

Set ofCAMEL in-formation re-lated to At-tach/Detachsession. Formore infor-mation, seeDescriptionof RecordFields. Thisfield ispresent ifCAMEL ser-vice is acti-vated.

C C OC



OM



Table 10-3 S-SMO-CDR.

Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4


MobileOriginatedSMS.

M M M M M

ServedIMSI.

The IMSIof thesubscriber.

M M M M M

ServedIMEI.


O O O O OC

ServedMSISDN.


O O O O OM


The mobilestationnetworkcapability.

M M M M OM

ServiceCenter.

The address(E.164)of theSMS-servicecenter.

M M M M OM

RecordingEntity.

The E.164number ofthe SGSN.

M M M M OM

LocationArea Code.

The LocationArea Codefrom whichthe messageoriginated.

O O O O OM

RoutingArea Code.

The RoutingArea Codefrom whichthe messageoriginated.

O O O O OM

Cont.



Table 10-3 S-SMO-CDR. (Continued)

Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0Cell Identity. The Cell

Identity forGSM orService AreaCode (SAC)for UMTSfrom whichthe messageoriginated.

O O O O OM

Event TimeStamp.

The time atwhich themessage wasreceived bythe SGSNfrom thesubscriber.

M M M M M

MessageReference.

A referenceprovidedby the MSuniquelyidentifyingthis message.

M M M M M

SMS Result. The resultof the at-tempted de-livery if un-successful.

C C C C C

RecordExtensions.

A set of net-work oper-ator/ man-ufacturerspecific ex-tensions tothe record.Conditionedupon the ex-istence of anextension.

O O O O OC


O O O O OM

Cont.




Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0LocalRecordSequenceNumber.


O O O O OM


The Charg-ing Charac-teristics flagset used bythe SGSN.

C C M

SystemType.


C C OC

Cont.




Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0DestinationNumber.

Thedestinationshortmessagesubscribernumber.

O O OM

CAMELInformation.

Set ofCAMELinformationrelatedto SMSsession.For moreinformationseeDescriptionof RecordFields. Thisfield ispresent ifCAMELservice isactivated.

C C OC



OM

Table 10-4 S-SMT-CDR.

Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4


MobileTerminatedSMS.

M M M M M

ServedIMSI.

The IMSIof thesubscriber.

M M M M M

Cont.



Table 10-4 S-SMT-CDR. (Continued)

Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0ServedIMEI.


O O O O OC

ServedMSISDN.


O O O O OM


The mobilestationnetworkcapability

M M M M OM

ServiceCenter.

The address(E.164)of theSMS-servicecenter.

M M M M OM

RecordingEntity.

The E.164number ofthe SGSN.

M M M M OM

LocationArea Code.

The LocationArea Code towhich themessage wasdelivered.

O O O O OM

RoutingArea Code.

The RoutingArea Codeto which themessage wasdelivered.

O O O O OM

Cell Identity. The CellIdentity forGSM orService AreaCode (SAC)for UMTSto which themessage wasdelivered.

O O O O OM

Cont.




Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0Event TimeStamp.

Deliverytime stamp,time at whichmessage wassent to theMS by theSGSN.

M M M M M

SMS Result. The resultof the at-tempted de-livery if un-successful.

C C C C C

RecordExtensions.


O O O O OC


O O O O OM



O O O O OM


The Charg-ing Charac-teristics flagset used bythe SGSN.

C C M

Cont.




Field Descrip-tion

CMCCR98V1.3.0

ETSIR98V7.6.0

ETSIR99V3.6.0

ETSIR99V3.A.0

ETSIR4

V4.4.0SystemType.


C C OC



OM

CAMELInformation.

Set ofCAMELinformationrelatedto SMSsession.For moreinformationseeDescriptionof RecordFields. Thisfield ispresent ifCAMELservice isactivated.

OC



Table 10-5 LCS-MT-CDR.

Field DescriptionETSIR4

V4.4.0Record Type. SGSN Mobile Terminated LCS. M

Recording Entity. The E.164 number of the SGSN. M

LCS Client Type. The type of LCS client thatinvokes the LR.

M

LCS Client Identity. Further identification of the LCSclient.

M

Served IMSI. The IMSI of the subscriber. M

Served MSISDN. The primary MSISDN of thesubscriber.

OM

SGSN Address. The IP address of the currentSGSN.

OM

Location Type. The type of estimated location. M

LCS QoS. QoS of the LR, if available. C

LCS Priority. Priority of the LR, if available. C

MLC Number. The E.164 address of therequesting GMLC.

M

Event Time stamp. The time at which thePerform_Location_Requestis sent by the SGSN.

M

Measurement Duration. The duration of proceeding thelocation request.

OM

Notification To MS User. The privacy notification to MSuser that was applicable when theLR was invoked, if available.

C

Privacy Override. This parameter indicates theoverride MS privacy by the LCSclient, if available.

C

Location. The LAC and CI when the LR isreceived.

OM

Routing Area Code. The Routing Area Code to whichthe LCS terminated.

OM

Location Estimate. The location estimate for thesubscriber if contained ingeographic position and the LRwas successful.

OC

Positioning Data. The positioning method used orattempted, if available.

C

Cont.



Table 10-5 LCS-MT-CDR. (Continued)


V4.4.0LCS Cause. The result of the LR if any failure

or partial success happened asknown at radio interface.

OC

Cause for Record Closing. The reason for closure of therecord from this SGSN.

M

Diagnostics. More detailed information aboutthe Cause for Record Closingif any failure or partial successhappened.

C

Node ID. Name of the recording entity. OM

Local Record Sequence Number. Consecutive record numbercreated by this node. The numberis allocated sequentially includingall CDR types.

OM

Charging Characteristics. The Charging Characteristics usedby the SGSN. (always use thesubscribed CC).

M

Charging CharacteristicsSelection Mode.

Holding the information abouthow Charging Characteristicswere selected (onlysubscribed/home default/visiteddefault).

OM

System Type. Indicates the type of air interfaceused, for example UTRAN. Thisfield is present when either theUTRAN or GERAN air-interfaceis used. It is omitted when theservice is provided by a GSM airinterface.

OC

Record Extensions. A set of networkoperator/manufacturer specificextensions to the record.Conditioned upon the existence ofan extension.

OC

Table 10-6 LCS-MO-CDR.


V4.4.0Record Type. SGSN Mobile Originated LCS. M

Recording Entity. E.164 number of the SGSN. M

Cont.



Table 10-6 LCS-MO-CDR. (Continued)


V4.4.0LCS Client Type. The type of the LCS client that

invoked the LR, if available.C

LCS Client Identity. Further identification of the LCSclient, if available.

C

Served IMSI. The IMSI of the subscriber. M

Served MSISDN. The primary MSISDN of thesubscriber.

OM


OM

Location Method. The type of the location request. M

LCS QoS. QoS of the LR, if available. C

LCS Priority. Priority of the LR, if available. Oc

MLC Number. The E.164 address of the involvedGMLC, if applicable.

C


M


OM


OM

Routing Area Code. The Routing Area Code fromwhich the LCS originated.

OM


OC


C

LCS Cause. The result of the LR if any failureor partial success happened asknown at radio interface.

C


M


C


Cont.



Table 10-6 LCS-MO-CDR. (Continued)


V4.4.0Local Record Sequence Number. Consecutive record number

created by this node. The numberis allocated sequentially includingall CDR types.

OM

Charging Characteristics. The Charging Characteristics flagset used by the SGSN.

M

Charging CharacteristicsSelection Mode.

Holding information about howCharging Characteristics wereselected

OM


OC


OC

Table 10-7 LCS-NI-CDR.


V4.4.0Record Type. SGSN Network Induced LCS. M

Recording Entity. The E.164 number of the SGSN. M

LCS Client Type. The type of the LCS client thatinvoked the LR, if available.

C

LCS Client Identity. Further identification of the LCSclient, if available.

C

Served IMSI. The IMSI of the subscriber ifsupplied.

C

Served MSISDN. The primary MSISDN of thesubscriber if supplied.

C


OM

Served IMEI. The IMEI of the ME, if available. OC

Cont.



Table 10-7 LCS-NI-CDR. (Continued)


V4.4.0LCS QoS. QoS of the LR, if available. C

LCS Priority. Priority of the LR, if available. C

MLC Number. The E.164 address of the involvedGMLC, if applicable.

C


M


OM


OM

Routing Area Code. The Routing Area Code fromwhich the LCS originated.

OM


OC


C

LCS Cause. The result of the LR if any failureor partial success happened asknown at radio interface.

C


M


C


Local Record Sequence Number. Consecutive record numbercreated by this node. The numberis allocated sequentially includingall CDR types.

OM

Charging Characteristics. The Charging Characteristics flagset used by the SGSN.

M

Cont.



Table 10-7 LCS-NI-CDR. (Continued)


V4.4.0Charging CharacteristicsSelection Mode.

Holding information about howCharging Characteristics wereselected.

OM


OC


OC


Installation and Configuration: C-SGSN Data Configuration Configuring Charging Behavior

Configuring Charging Behavior■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration of charging behavior. After the configuration, SGSN can adoptdifferent charging methods for the subscribers.

Description



Procedure

Step Operation Command1 Configure charging behavior

parameters.ADD CHGBEHA

Example

;; Configure charging behavior parameters

ADD CHGBEHA: CB=B1, BA=PLT, PURGELEN=60, ACC=HOTBILLING-1&FLATRATE-1&PREPAID-1&NORMAL-1;

Reference

The charging behavior refers to the charging methods for implementing charges on the subscribers. Eachtype of charging behavior corresponds to one type of charging characteristic. SGSN supports the followingcharging behavior:


Configuring Charging Behavior Chapter 10: Charging Configuration

1. 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.

2. 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.

3. The SMTS-U address that does not generate S-SMO-CDRs (SMTS-U). If the local subscriberwith this charging behavior sends a short message to this SMTS-U address, the S-SMO-CDRwill not be generated.

4. The roaming subscriber is prohibited from using the local GGSN (NOROAMING). Theroaming subscriber with this charging behavior cannot use the local GGSN.

5. 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.

6. The IP address of the CG (CGIP). The CDRs of the subscriber with this charging behaviorwill be preferentially sent to this CG. The priority of this CG is higher than that of the CGspecified by the charging characteristic, that of the CG recommended by GGSN or other CGs,and that of the CGs configured by operators.

• 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.


Installation and Configuration: C-SGSN Data Configuration Configuring Special Charging Rate Period

Configuring Special Charging Rate Period■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section introduces the configuration of special charging rate periods. After the configuration, SGSN canrecord the subscriber traffic flow of different tariff periods.

Description



Procedure

Step Operation Command1 Configure the charging holiday. ADD CHGHOLI

2 Configure the charging days in aweek.

SET CHGWKDY

3 Configure the tariff period in aday.

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 ofthe tariff period is 00:00. The end time is 10:00.

ADD CHGTARI: TT=WORK, ST=00&00, ET=10&00, CC=NORMAL;


Configuring Special Charging Rate Period Chapter 10: Charging Configuration

Reference

Charging holidayCharging holiday is to configure the holiday property of a day and the corresponding charging characteristics.

Charging days in a weekCharging days in a week is to set the tariff properties (weekday or weekend) of the seven days in a week andthe corresponding charging characteristics.

Tariff periodThe tariff period is used together with charging holiday and charging days in a week. It is used to set thespecial tariff periods for the holidays and weekends. You can set multiple periods, but the periods with thesame charging characteristics should not overlap.

The duration of any tariff period cannot be less than ten minutes.


Chapter

11System Configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■


System Configuration Overview Chapter 11: System Configuration

System Configuration Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The system configuration consists of the system basic information configuration, remote maintenance gatewayconfiguration, SNMP parameter configuration, OMC-S/T 2.0 IP configuration and system time configuration.

You may perform all configurations in any sequence.


Installation and Configuration: C-SGSN Data Configuration Configuring System Basic Information

Configuring System Basic Information■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section describes the system basic information configuration.

Description



Basicinformation.

IP address. FTP username.

FTPpassword.

IP addressof thedefault FTPgateway.

Procedure

Step Operation Command1 Configure the basic information

of the system.SET SYS

Example

;;Configure the FTP server:

SET SYS: SWSIP="175.22.44.100", SWSUSRNAME="loader", SWSPWD="loader";

Reference

The system basic information includes:


Configuring System Basic Information Chapter 11: System Configuration

• System description information including the ID, name, location, time zone, provided servicesand 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 ofthe HPLMN where the SGSN is located.

• FTP server information.

The FTP server stores the information including board software and configuration files of thesystem. You need to obtain the corresponding files from the FTP server in case of systemloading 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 thegateway. If the system has not loaded the UOMU software, the UOMU will use the defaultFTP gateway set in SET SYS command. Otherwise, it will use the default FTP gateway setin ADD GATEWAY command.


Installation and Configuration: C-SGSN Data Configuration Configuring Remote Maintenance Gateway

Configuring Remote Maintenance Gateway■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section describes the remote maintenance gateway configuration. After the configuration, the systemcan perform maintenance on the SGSN through an LM in a network segment different from the UOMUnetwork segment.

Description

Preset conditionsThe configuration of the UOMU has finished.


Basicinformation.

IP address ofthe gateway.

IP addressand the maskcode of thedestination.

Procedure

Step Operation Command1 Configure the remote maintenance

gateway.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


Configuring SNMP Chapter 11: System Configuration

Configuring SNMP■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section describes the SNMP configuration. After the configuration, the SGSN can exchange informationwith the SNMP network management center.

Description



Basicinformation.

Readcommunityname.

Writecommunityname.

TRAP IPaddress.

Procedure

Step Operation Command1 Configure the community name. SET SCOMM

2 Add a TRAP IP address. 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";


Installation and Configuration: C-SGSN Data Configuration Configuring SNMP

Reference

Motorola C-SGSN can access the Network Management Center (NMC) through Simple NetworkManagement Protocol (SNMP). Motorola C-SGSN supports SNMP V1. The SNMP subsystem in MotorolaC-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 andwrite some of them. The critical configuration data include system information, Gb interface configurationinformation 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 MotorolaC-SGSN system.

SNMP configuration includes the SNMP community name configuration and destination TRAP addressconfiguration.

• 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 readsdata from or writes data to the Motorola C-SGSN. The NMC shall be configured with both, acommunity name (used for accessing the Motorola C-SGSN) and the IP address of theMotorola C-SGSN. In addition, the community name configured in the NMC shall be the sameas 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 IPaddresses 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 NMCsaccess the Motorola C-SGSN with the same community name.


Configuring OMC-S/T 2.0 IP Address Chapter 11: System Configuration

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 SGSNonly after the configuration.

Description



Basicinformation.

OMC-S/T2.0 IP.

Procedure

Step Operation Command1 Set the OMC-S/T 2.0 IP address. SET EMS

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 theOMC-S/T 2.0 IP address in the SGSN before OMC-S/T 2.0 logon.


Installation and Configuration: C-SGSN Data Configuration Configuring System Time

Configuring System Time■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section describes the system time configuration. After the configuration, the SGSN can obtain the timeinformation from a specified NTP server.

Description

Preset conditionsThe configuration of the UGTP has finished. To use NTP as the system time reference, you need configure theIP route between the SGSN and the NTP server. For details, see Chapter 5, "Gn/Gp Interface Configuration,"in this manual.


Procedure

To use the NTP timing:

Step Operation Command1 Set the NTP client. SET NTP

2 Set the NTP server. ADD NTPS

3 Set the daylight saving time. SET DST

Otherwise:

Step Operation Command1 Set the system time. SET SYSTIME

2 Set the daylight saving time. SET DST


Configuring System Time Chapter 11: System Configuration

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 fromthe NTP server through the Network Timing Protocol (NTP). Because the time obtained from the NTPserver is synchronous with the entire network, we recommend that you should obtain the time informationfrom the NTP server.

To obtain the system time information from the NTP server, you need start an NTP client (located at UGTP) inthe SGSN. The client will sample the time information from the NTP server at a specified frequency (pollingfrequency). The difference between the system time and the NTP server reference time may be greater thanor equal to a specified threshold (time adjustment threshold). In that case, the SGSN will synchronize itstime to the NTP server time.

There may be multiple NTP servers in a network. You may set these servers to different priority levels. Toensure 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 orbehind the standard time during a specified period.


Chapter

12Feature Configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■


Feature Configuration Overview Chapter 12: Feature Configuration

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


Installation and Configuration: C-SGSN Data Configuration Roaming Barred by IMSI

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 updaterequest will be rejected if the IMSI of the subscriber is within a roaming-barred IMSI range and the subscriberis in a roaming-barred location (routing) area.

Description



Basic information. The mapping relation between an IMSI range and aroaming-barred location (routing) area.

Procedure

Step Operation Command1 Enable the function of roaming

barred by IMSI range.SET SERVICE_PARA

2 Add the mapping relationbetween an IMSI range and aroaming-barred location (routing)area.

ADD RESTRICTAREA


Roaming Barred by IMSI Chapter 12: Feature Configuration

Example

SET SERVICE_PARA: ROAM=YES;

ADD RESTRICTAREA: BEGIMSI="460017551111111", ENDIMSI="460017552222222",LAI="460007123", RAC="5";

Reference

None.


Installation and Configuration: C-SGSN Data Configuration Choosing GGSN by IMSI

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 MappingRelation 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 obtainthe corresponding GGSN IP address. Otherwise, it will select an APN OI based on the APN OI selectionalgorithm defined in protocol 23.060. Then it will initiate a DNS parse procedure to obtain the correspondingGGSN IP address.

Description



Basic information. The mapping relation between an IMSI range andan APN OI.

Procedure

Step Operation Command1 Enable the function of choosing

GGSN by IMSI range.SET SERVICE_PARA

2 Add the mapping relation betweenan IMSI range and an APN OI.

ADD IMSIAPNOI


Choosing GGSN by IMSI Chapter 12: Feature Configuration

Example

MOD SERVICE_PARA: GGSN=YES;

ADD IMSIAPNOI:BEGIMSI = 460007551111111, ENDIMSI = 460007552222222,APNOI="MNC007.MCC460.GPRS";

Reference

None.


Installation and Configuration: C-SGSN Data Configuration 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 PDPContext Request carrying an extra routing area identifier information element (RAI IE) to a user-definedGGSN. This IE contains MNC and MCC.

Description



Basic information. IP Address of the GGSN control plane.

Procedure

Step Operation Command1 Enable the function 'RAI IE in

Gn'.SET SERVICE_PARA

2 Add an GGSN that requires themessages received through the Gninterface to carry RAI IE.

ADD GGSNCHARACT

Example

SET SERVICE_PARA: GNMSG=YES;

ADD GGSNCHARACT: IP="168.22.168.12",ISRAIRQD = YES;


RAI IE in Gn Chapter 12: Feature Configuration

Reference

None.


Installation and Configuration: C-SGSN Data Configuration Detaching Inactive Subscribers

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 notinitiated PDP context activation request within a specified time after the routing area update.

This function is valid only for 2.5G subscribers.

Description



Procedure

Step Operation Command1 Enable the function of detaching

inactive subscribers.SET SERVICE_PARA

2 Modify the Inactive-subscriberDetach Timer.

SET GMMTMR


Detaching Inactive Subscribers Chapter 12: Feature Configuration

Example

SET SERVICE_PARA: DETACH =YES;

SET GMMTMR: NACTTMR=400;

Reference

None.


Installation and Configuration: C-SGSN Data Configuration Not detaching inactive subscribers of the specified APN

Not detaching inactive subscribers of the specifiedAPN■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

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 specifiedAPN. After the configuration takes effect, with the function "Detaching Inactive Subscribers" enabled, theinactive subscriber who has subscribed the specified APN will not be detached forcibly.


Description

Preset conditionsThe function 'Detaching Inactive Subscribers' is enabled,


Procedure

Step Operation Command1 Add an APN NI that cannot be

detached forcedly.ADD APNNICHARACT


Not detaching inactive subscribers of the specified APN Chapter 12: Feature Configuration

Example

;; Add an APN NI that cannot be detached forcedly.

ADD APNNICHARACT : APNNI="motorola1.com",RSVIDLEUSER = YES;

Reference

None.


Installation and Configuration: C-SGSN Data Configuration GPRS Second Authentication in Attach

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 secondauthentication request if the first authentication fails during an attach procedure. For example, theauthentication 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 thesecond 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 uponthe failure in the first authentication.


Description



Procedure

Step Operation Command1 Enable the function 'GPRS

Second Authentication In Attach'.SET SERVICE_PARA


GPRS Second Authentication in Attach Chapter 12: Feature Configuration

Example

SET SERVICE_PARA: ATTSAUTH=YES;

Reference

None.


Installation and Configuration: C-SGSN Data Configuration GPRS Second Authentication in RAU

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 secondauthentication request if the first authentication fails during a routing area update (RAU) procedure. Forexample, the authentication can be considered failed when the SRES returned by the MS is different fromthat 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_REJECTmessage to the MS.

If the function is disabled, the network will send the AUTHENTICATION_REJECT message to the MS uponthe failure in the first authentication.


Description



Procedure

Step Operation Command1 Enable the function 'GPRS

Second Authentication in RAU'.SET SERVICE_PARA


GPRS Second Authentication in RAU Chapter 12: Feature Configuration

Example

SET SERVICE_PARA: RAUSAUTH=YES;

Reference

None.


Installation and Configuration: C-SGSN Data Configuration Rejecting GPRS Subscribers Attach by APNNI

Rejecting GPRS Subscribers Attach by APNNI■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■


When providing both 2G GPRS services and 3G services, the network operator can specify different APNNIsfor 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 subscribedto 2G GPRS APNNI.

This function is valid only for 3G networks.

Description



Basicinformation

ANP NI


Rejecting GPRS Subscribers Attach by APNNI Chapter 12: Feature Configuration

Procedure

Step Operation Command1 Enable the function of rejecting

GPRS subscribers’ attach byAPNNI.

SET SERVICE_PARA:APNREJGPRS=YES;

2 Add the APNNI of GRPSsubscribers to APNNI list.

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


Installation and Configuration: C-SGSN Data Configuration Rejecting GPRS Subscribers Attach by IMSI

Rejecting GPRS Subscribers Attach by IMSI■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■


When providing both 2G GPRS services and 3G services, the network operator can specify different IMSInumber segments for 2G GPRS subscribers and 3G subscribers to prevent 2G GPRS subscribers fromattaching to 3G networks.

If this function is enabled, the SGSN will reject the attach to 3G networks of the users whose IMSI is in theIMSI number segment of 2G GPRS.

This function is valid only for 3G networks.

Description



Basicinformation

IMSInumbersegment


Rejecting GPRS Subscribers Attach by IMSI Chapter 12: Feature Configuration

Procedure

Step Operation Command1 Enable the function of rejecting

GPRS subscriber’ attach by IMSI.SET SERVICE_PARA:IMSIREJGPRS=YES;

2 Add the IMSI number segment ofGRPS subscribers.

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


Index

Index■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

C■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Charging Configuration Overview . . . . . . . 10- 2Choosing GGSN by IMSI . . . . . . . . . . . 12- 5

Description . . . . . . . . . . . . . . . . 12- 5Data preparations . . . . . . . . . . . . 12- 5Preset conditions . . . . . . . . . . . . 12- 5

Example. . . . . . . . . . . . . . . . . . 12- 6Overview of the Function . . . . . . . . . . 12- 5Procedure . . . . . . . . . . . . . . . . . 12- 5Reference . . . . . . . . . . . . . . . . . 12- 6

Configure DNS/HOSTFILE. . . . . . . . . . . 5- 6Description . . . . . . . . . . . . . . . . . 5- 6

Data preparation . . . . . . . . . . . . . . 5- 6Preset conditions . . . . . . . . . . . . . 5- 6

Example. . . . . . . . . . . . . . . . . . . 5- 6Procedure . . . . . . . . . . . . . . . . . . 5- 6Reference . . . . . . . . . . . . . . . . . . 5- 7

Configuring Authentication and CipheringParameters . . . . . . . . . . . . . . . . . . . 7- 3

Description . . . . . . . . . . . . . . . . . 7- 3Data preparations . . . . . . . . . . . . . 7- 3Preset conditions . . . . . . . . . . . . . 7- 3


Authentication. . . . . . . . . . . . . . . 7- 4Authentication failure configuration. . . . . 7- 5Ciphering . . . . . . . . . . . . . . . . . 7- 4IMEI check . . . . . . . . . . . . . . . . 7- 4P-TMSI . . . . . . . . . . . . . . . . . . 7- 4

Configuring Board . . . . . . . . . . . . . . . 2- 7Description . . . . . . . . . . . . . . . . . 2- 7

Data preparations . . . . . . . . . . . . . 2- 7Preset conditions . . . . . . . . . . . . . 2- 7

Example. . . . . . . . . . . . . . . . . . . 2-102.5G example . . . . . . . . . . . . . . . 2-123G example . . . . . . . . . . . . . . . . 2-10

Procedure . . . . . . . . . . . . . . . . . . 2- 8Reference . . . . . . . . . . . . . . . . . . 2-14

UCDR . . . . . . . . . . . . . . . . . . 2-15UEPI/UTPI . . . . . . . . . . . . . . . . 2-16UGBI . . . . . . . . . . . . . . . . . . . 2-16UGTP . . . . . . . . . . . . . . . . . . 2-16UHPU . . . . . . . . . . . . . . . . . . 2-15UICP . . . . . . . . . . . . . . . . . . . 2-16ULAN . . . . . . . . . . . . . . . . . . 2-17

Configuring Board (contd.)Reference (contd.)

UOMU . . . . . . . . . . . . . . . . . . 2-14URCU . . . . . . . . . . . . . . . . . . 2-14USPU. . . . . . . . . . . . . . . . . . . 2-15Virtual Subrack . . . . . . . . . . . . . . 2-14

Configuring BSSAP+ (Gs interface) . . . . . . . 3-26Description . . . . . . . . . . . . . . . . . 3-26

Data preparations . . . . . . . . . . . . . 3-26Preset conditions . . . . . . . . . . . . . 3-26

Example. . . . . . . . . . . . . . . . . . . 3-26Procedure . . . . . . . . . . . . . . . . . . 3-26Reference . . . . . . . . . . . . . . . . . . 3-27

Configuring CAMEL service . . . . . . . . . . 9- 4Description . . . . . . . . . . . . . . . . . 9- 4



CAMEL Services . . . . . . . . . . . . . 9- 5Camel timer . . . . . . . . . . . . . . . . 9- 5CAMEL trigger mode . . . . . . . . . . . 9- 5

Configuring CDR Optional Field . . . . . . . 10-12Description . . . . . . . . . . . . . . . . 10-12

Data preparations . . . . . . . . . . . . 10-12Preset conditions . . . . . . . . . . . . 10-12

Example. . . . . . . . . . . . . . . . . . 10-12Procedure . . . . . . . . . . . . . . . . . 10-12Reference . . . . . . . . . . . . . . . . . 10-12

Configuring Cell Reference Parameters . . . . . 6-14Description . . . . . . . . . . . . . . . . . 6-14

Data preparation . . . . . . . . . . . . . . 6-14Preset conditions . . . . . . . . . . . . . 6-14


Configuring CG and Route between SGSN andCG . . . . . . . . . . . . . . . . . . . . . 10- 5


Example. . . . . . . . . . . . . . . . . . 10- 6Procedure . . . . . . . . . . . . . . . . . 10- 6

68P02904W52-B IX-131-Jan-2005 CONTROLLED INTRODUCTION

Index

Configuring CG and Route between SGSN and CG(contd.)

Reference . . . . . . . . . . . . . . . . . 10- 7CG . . . . . . . . . . . . . . . . . . . 10- 7SGSN-to-CG Route . . . . . . . . . . . 10- 8

Configuring Charging Behavior . . . . . . . . 10-37Description . . . . . . . . . . . . . . . . 10-37



Configuring Charging Characteristic Parameters andDefault Charging Characteristics . . . . . . . 10- 9


Example. . . . . . . . . . . . . . . . . . 10- 9Procedure . . . . . . . . . . . . . . . . . 10- 9Reference . . . . . . . . . . . . . . . . . 10-10

Charging characteristics . . . . . . . . . 10-10Default charging characteristics . . . . . . 10-11

Configuring Clock . . . . . . . . . . . . . . . 2-21Description . . . . . . . . . . . . . . . . . 2-21



Configuring Control Plane of Iu Interface . . . . 4- 9Description . . . . . . . . . . . . . . . . . 4- 9

Data preparations . . . . . . . . . . . . . 4-10Preset conditions . . . . . . . . . . . . . 4- 9


Broadband SS7 . . . . . . . . . . . . . . 4-14Configure mapping relation between UICP andRNC . . . . . . . . . . . . . . . . . . . 4-15Configure RNC . . . . . . . . . . . . . . 4-15

Configuring Ga Interface Parameters . . . . . 10- 3Description . . . . . . . . . . . . . . . . 10- 3

Data Preparations . . . . . . . . . . . . 10- 3Preset Conditions . . . . . . . . . . . . 10- 3

Example. . . . . . . . . . . . . . . . . . 10- 3Procedure . . . . . . . . . . . . . . . . . 10- 3Reference . . . . . . . . . . . . . . . . . 10- 3

CDR protocol version . . . . . . . . . . 10- 3CDR resending parameters . . . . . . . . 10- 4Hard disk alarm parameters. . . . . . . . 10- 4

Configuring GTP Protocol Parameters . . . . . . 5- 8Description . . . . . . . . . . . . . . . . . 5- 8


Configuring GTP Protocol Parameters (contd.)Example. . . . . . . . . . . . . . . . . . . 5- 9Procedure . . . . . . . . . . . . . . . . . . 5- 9Reference . . . . . . . . . . . . . . . . . . 5- 9

Configuring IP Address of GGSN supporting MIP orDHCP . . . . . . . . . . . . . . . . . . . . . 8- 9


Example. . . . . . . . . . . . . . . . . . . 8- 9Procedure . . . . . . . . . . . . . . . . . . 8- 9Reference . . . . . . . . . . . . . . . . . . 8-10

Configuring IPSec . . . . . . . . . . . . . . . 5-16Description . . . . . . . . . . . . . . . . . 5-16


Example. . . . . . . . . . . . . . . . . . . 5-18To create IPSec Dynamic security Policy . . 5-19To create isakmp security policy: . . . . . . 5-18To create manual security policy . . . . . . 5-18

Procedure . . . . . . . . . . . . . . . . . . 5-17Create IPSec Dynamic security Policy: . . . 5-17Create isakmp security policy: . . . . . . . 5-17Create manual security policy: . . . . . . . 5-17

Reference . . . . . . . . . . . . . . . . . . 5-19IPSec . . . . . . . . . . . . . . . . . . . 5-19Preparation for IPSec Configuration. . . . . 5-21Preparation for IPSec Configuration - IKE SecurityMechanism . . . . . . . . . . . . . . . . 5-22Preparation for IPSec Configuration - IPSec andIKE. . . . . . . . . . . . . . . . . . . . 5-22Preparation for IPSec Configuration - Specifydata flow and security gateways to beconfigured . . . . . . . . . . . . . . . . 5-21Preparation for IPSec Configuration - Specify keyand security parameter index (SPI) . . . . . 5-22Preparation for IPSec Configuration - Specifynegotiation mode for Security Associationestablishment . . . . . . . . . . . . . . . 5-21Preparation for IPSec Configuration - Specifysecurity protocol, algorithm and encapsulationformat . . . . . . . . . . . . . . . . . . 5-22Some Concepts Related to IPSecImplementation . . . . . . . . . . . . . . 5-19

Configuring LCS . . . . . . . . . . . . . . . . 9- 6Description . . . . . . . . . . . . . . . . . 9- 6



Delayed location. . . . . . . . . . . . . . 9- 9

IX-2 68P02904W52-BCONTROLLED INTRODUCTION 31-Jan-2005

Index

Configuring LCS (contd.)Reference (contd.)

LCS parameters . . . . . . . . . . . . . . 9- 8Location calculation . . . . . . . . . . . . 9- 8Mapping relations between GMLC and LCSCLIENT . . . . . . . . . . . . . . . . . 9- 9

Configuring Link and Management Entity . . . . 6- 3Description . . . . . . . . . . . . . . . . . 6- 3



Configure BC . . . . . . . . . . . . . . . 6- 6Configure E1/T1. . . . . . . . . . . . . . 6- 6NS-VC . . . . . . . . . . . . . . . . . . 6- 7NSE . . . . . . . . . . . . . . . . . . . 6- 8PVC . . . . . . . . . . . . . . . . . . . 6- 7

Configuring Local Office . . . . . . . . . . . . 3- 3Description . . . . . . . . . . . . . . . . . 3- 3



Configuring MAP (Gr/Gd/Ge/Gf/Lg inter-face). . . . . . . . . . . . . . . . . . . . . . 3-24

Description . . . . . . . . . . . . . . . . . 3-24Data Preparation . . . . . . . . . . . . . . 3-24Preset Conditions . . . . . . . . . . . . . 3-24


Configure MAP zone code table . . . . . . 3-25MAP . . . . . . . . . . . . . . . . . . . 3-25

Configuring Mapping between PDP Type and APNNI . . . . . . . . . . . . . . . . . . . . . . . 8- 6



Configuring MTP Data . . . . . . . . . . . . . 3- 5Description . . . . . . . . . . . . . . . . . 3- 5



Load sharing of SS7 signaling network . . . 3-11Mask setting principles. . . . . . . . . . . 3-13MTP Destination Signaling Point . . . . . . 3- 8MTP link set . . . . . . . . . . . . . . . 3- 9MTP signaling link . . . . . . . . . . . . 3-10

Configuring MTP Data (contd.)Reference (contd.)

MTP signaling route . . . . . . . . . . . . 3- 9Configuring OMC-S/T 2.0 IP Address . . . . . 11- 8



Configuring OSPF . . . . . . . . . . . . . . . 5-24Description . . . . . . . . . . . . . . . . . 5-24



OSPF Packets . . . . . . . . . . . . . . . 5-25Process of OSPF Route Calculation . . . . . 5-25Related Concepts . . . . . . . . . . . . . 5-26

Configuring Paging Parameters . . . . . . . . . 7-10Description . . . . . . . . . . . . . . . . . 7-10

Data preparations . . . . . . . . . . . . . 7-10Preset Conditions . . . . . . . . . . . . . 7-10


Configuring PLMN. . . . . . . . . . . . . . . 7- 8Description . . . . . . . . . . . . . . . . . 7- 8

Data preparations . . . . . . . . . . . . . 7- 8Preset Conditions . . . . . . . . . . . . . 7- 8


Configuring Port . . . . . . . . . . . . . . . . 2-18Description . . . . . . . . . . . . . . . . . 2-18



ATM . . . . . . . . . . . . . . . . . . . 2-20E1/T1. . . . . . . . . . . . . . . . . . . 2-20FE/GE . . . . . . . . . . . . . . . . . . 2-20VA . . . . . . . . . . . . . . . . . . . . 2-20

Configuring Protocol Parameters . . . . . . . . 6- 9Description . . . . . . . . . . . . . . . . . 6- 9


Example. . . . . . . . . . . . . . . . . . . 6- 9Procedure . . . . . . . . . . . . . . . . . . 6- 9Reference . . . . . . . . . . . . . . . . . . 6-10

BSSGP . . . . . . . . . . . . . . . . . . 6-12LLC . . . . . . . . . . . . . . . . . . . 6-11


Index

Configuring Protocol Parameters (contd.)Reference (contd.)

NS . . . . . . . . . . . . . . . . . . . . 6-12SNDCP . . . . . . . . . . . . . . . . . . 6-10

Configuring QoS Parameters . . . . . . . . . . 5-10Description . . . . . . . . . . . . . . . . . 5-10



CBWFQ . . . . . . . . . . . . . . . . . 5-11DSCP Remarking . . . . . . . . . . . . . 5-15Mapping relation between QoS andDSCP. . . . . . . . . . . . . . . . . . . 5-14WRED . . . . . . . . . . . . . . . . . . 5-12

Configuring Rack . . . . . . . . . . . . . . . 2- 3Description . . . . . . . . . . . . . . . . . 2- 3



Configuring Remote Maintenance Gateway . . 11- 5Description . . . . . . . . . . . . . . . . 11- 5

Data preparations . . . . . . . . . . . . 11- 5Preset conditions . . . . . . . . . . . . 11- 5


Configuring RIP . . . . . . . . . . . . . . . . 5-28Description . . . . . . . . . . . . . . . . . 5-28



Configuring Shared PLMN OI. . . . . . . . . . 8- 8Description . . . . . . . . . . . . . . . . . 8- 8



Configuring SM Parameters . . . . . . . . . . . 8- 3Description . . . . . . . . . . . . . . . . . 8- 3



APN resolution . . . . . . . . . . . . . . 8- 5Optional functions in SM. . . . . . . . . . 8- 4QoS . . . . . . . . . . . . . . . . . . . 8- 4

Configuring SM Parameters (contd.)Reference (contd.)

RAB QoS negotiation . . . . . . . . . . . 8- 5SM timers . . . . . . . . . . . . . . . . . 8- 4

Configuring SMS. . . . . . . . . . . . . . . . 9- 2Description . . . . . . . . . . . . . . . . . 9- 2



Configuring SNMP . . . . . . . . . . . . . . 11- 6Description . . . . . . . . . . . . . . . . 11- 6



Configuring Special Charging Rate Period . . . 10-39Description . . . . . . . . . . . . . . . . 10-39



Charging days in a week . . . . . . . . . 10-40Charging holiday . . . . . . . . . . . . 10-40Tariff period. . . . . . . . . . . . . . . 10-40

Configuring Subrack . . . . . . . . . . . . . . 2- 5Description . . . . . . . . . . . . . . . . . 2- 5



Configuring System Basic Information. . . . . 11- 3Description . . . . . . . . . . . . . . . . 11- 3



Configuring System Time . . . . . . . . . . . 11- 9Description . . . . . . . . . . . . . . . . 11- 9


Example. . . . . . . . . . . . . . . . . . 11-10Procedure . . . . . . . . . . . . . . . . . 11- 9Reference . . . . . . . . . . . . . . . . . 11-10

Configuring Timers. . . . . . . . . . . . . . . 7- 6Description . . . . . . . . . . . . . . . . . 7- 6

Data preparations . . . . . . . . . . . . . 7- 6Preset Conditions . . . . . . . . . . . . . 7- 6

Example. . . . . . . . . . . . . . . . . . . 7- 6


Index

Configuring Timers (contd.)Procedure . . . . . . . . . . . . . . . . . . 7- 6Reference . . . . . . . . . . . . . . . . . . 7- 7

Configuring User Plane of Iu Interface . . . . . . 4- 3Description . . . . . . . . . . . . . . . . . 4- 3


Example. . . . . . . . . . . . . . . . . . . 4- 4Add an normal IPOA PVC between the SGSN andan RNC . . . . . . . . . . . . . . . . . . 4- 4

Configuring User Plane of Iu Interface (contd.)Example (contd.)

Add two RNCOA IPOA PVCs between the SGSNand an RNC . . . . . . . . . . . . . . . . 4- 5

Procedure . . . . . . . . . . . . . . . . . . 4- 4Reference . . . . . . . . . . . . . . . . . . 4- 5

IP address for VA port and forward engine and localIP address for VA port . . . . . . . . . . . 4- 6IPOA PVC . . . . . . . . . . . . . . . . 4- 5PVC Traffic parameters . . . . . . . . . . 4- 7

D■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Data Configuration Modes . . . . . . . . . . . 1- 5Data to Be Configured and Data ConfigurationFlow . . . . . . . . . . . . . . . . . . . . . 1- 2Detaching Inactive Subscribers . . . . . . . . 12- 9


Detaching Inactive Subscribers (contd.)Example. . . . . . . . . . . . . . . . . . 12-10Overview of the Function . . . . . . . . . . 12- 9Procedure . . . . . . . . . . . . . . . . . 12- 9Reference . . . . . . . . . . . . . . . . . 12-10

Devices sensitive to static . . . . . . . . . . . . . 14Special handling techniques. . . . . . . . . . . 14

F■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Feature Configuration Overview. . . . . . . . 12- 2

G■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Gb Interface Configuration Overview . . . . . . 6- 2General cautions . . . . . . . . . . . . . . . . . 13

Caution labels . . . . . . . . . . . . . . . . . 13Specific cautions . . . . . . . . . . . . . . . . 13

Fibre optics . . . . . . . . . . . . . . . . . 13Static discharge . . . . . . . . . . . . . . . 13

General information . . . . . . . . . . . . . . . 3Cross references . . . . . . . . . . . . . . . . 4Data encryption . . . . . . . . . . . . . . . . 5Feature references . . . . . . . . . . . . . . . 3Purpose . . . . . . . . . . . . . . . . . . . . 3Text conventions . . . . . . . . . . . . . . . . 5

Input . . . . . . . . . . . . . . . . . . . . 5Output . . . . . . . . . . . . . . . . . . . 5Special key sequences . . . . . . . . . . . . 5

General warnings. . . . . . . . . . . . . . . . . 9Specific warnings . . . . . . . . . . . . . . . 9

Battery supplies . . . . . . . . . . . . . . . 12Electric shock . . . . . . . . . . . . . . . . 10Laser radiation . . . . . . . . . . . . . . . 11Lifting equipment . . . . . . . . . . . . . . 11Lithium batteries . . . . . . . . . . . . . . 12Parts substitution . . . . . . . . . . . . . . 12

General warnings (contd.)Specific warnings (contd.)

Potentially hazardous voltage . . . . . . . . . 10RF radiation . . . . . . . . . . . . . . . . . 11

Warning labels . . . . . . . . . . . . . . . . . 9Gn/Gp Interface Configuration Overview . . . . 5- 2Gn/Gp Interface Route Configuration . . . . . . 5- 3

Description . . . . . . . . . . . . . . . . . 5- 3Data preparation . . . . . . . . . . . . . . 5- 3Preset conditions . . . . . . . . . . . . . 5- 3


Configure IP route . . . . . . . . . . . . . 5- 5Configure IPOA PVC . . . . . . . . . . . 5- 5

GPRS Second Authentication in Attach . . . . 12-13Description . . . . . . . . . . . . . . . . 12-13


Example. . . . . . . . . . . . . . . . . . 12-14Overview of the Function . . . . . . . . . . 12-13Procedure . . . . . . . . . . . . . . . . . 12-13


Index

GPRS Second Authentication in RAU (contd.)Reference . . . . . . . . . . . . . . . . . 12-14

GPRS Second Authentication in RAU . . . . . 12-15Description . . . . . . . . . . . . . . . . 12-15


GPRS Second Authentication in RAU (contd.)Example. . . . . . . . . . . . . . . . . . 12-16Overview of the Function. . . . . . . . . . 12-15Procedure . . . . . . . . . . . . . . . . . 12-15Reference . . . . . . . . . . . . . . . . . 12-16

H■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Hardware Configuration Overview . . . . . . . 2- 2

I■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Issue status of this manual (contd.)Issue status of this manual . . . . . . . . . . . . 2

Incorporation of CDCNs . . . . . . . . . . . . 2Resolution of service requests. . . . . . . . . . 2

Issue status of this manual (contd.)Version information . . . . . . . . . . . . . . 2

Iu interface Configuration Overview . . . . . . . 4- 2

M■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Manual amendment. . . . . . . . . . . . . . . . 16CDCN amendment record . . . . . . . . . . . 18CDCN availability . . . . . . . . . . . . . . . 16CDCN instructions . . . . . . . . . . . . . . . 17GMR availability . . . . . . . . . . . . . . . 16

MM Configuration Overview . . . . . . . . . . 7- 2Motorola manual set . . . . . . . . . . . . . . . 15

Ordering manuals and CD-ROMs . . . . . . . . 15

N■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Not detaching inactive subscribers of the specified APN(contd.)

Not detaching inactive subscribers of the specifiedAPN. . . . . . . . . . . . . . . . . . . . . 12-11

Description . . . . . . . . . . . . . . . . 12-11Data preparations . . . . . . . . . . . . 12-11Preset conditions . . . . . . . . . . . . 12-11

Example. . . . . . . . . . . . . . . . . . 12-12

Not detaching inactive subscribers of the specified APN(contd.)

Overview of the Function. . . . . . . . . . 12-11Procedure . . . . . . . . . . . . . . . . . 12-11Reference . . . . . . . . . . . . . . . . . 12-12

P■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Points for Attention. . . . . . . . . . . . . . . 1- 4

R■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

RAI IE in Gn (contd.)RAI IE in Gn. . . . . . . . . . . . . . . . . 12- 7


Index

RAI IE in Gn (contd.)Description . . . . . . . . . . . . . . . . 12- 7



Rejecting GPRS Subscribers Attach byAPNNI . . . . . . . . . . . . . . . . . . . 12-17

Description . . . . . . . . . . . . . . . . 12-17Data preparations . . . . . . . . . . . . 12-17Preset conditions . . . . . . . . . . . . 12-17

Example. . . . . . . . . . . . . . . . . . 12-18Overview of the Function . . . . . . . . . . 12-17Procedure . . . . . . . . . . . . . . . . . 12-18Reference . . . . . . . . . . . . . . . . . 12-18

Rejecting GPRS Subscribers Attach by IMSI . . 12-19

Rejecting GPRS Subscribers Attach by IMSI (contd.)Description . . . . . . . . . . . . . . . . 12-19


Example. . . . . . . . . . . . . . . . . . 12-20Overview of the Function . . . . . . . . . . 12-19Procedure . . . . . . . . . . . . . . . . . 12-20References. . . . . . . . . . . . . . . . . 12-20

Reporting safety issues . . . . . . . . . . . . . . 6Procedure . . . . . . . . . . . . . . . . . . . 6

Roaming Barred by IMSI . . . . . . . . . . . 12- 3Description . . . . . . . . . . . . . . . . 12- 3



S■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

SCCP Configuration . . . . . . . . . . . . . . 3-15Description . . . . . . . . . . . . . . . . . 3-15



Common GTs for SGSN . . . . . . . . . . 3-22GT Translation . . . . . . . . . . . . . . 3-19

SCCP Configuration (contd.)Reference (contd.)

IMSI-GT conversion . . . . . . . . . . . . 3-23SCCP DSP . . . . . . . . . . . . . . . . 3-17SCCP Subsystem . . . . . . . . . . . . . 3-18

SM Configuration Overview . . . . . . . . . . 8- 2SS7 Configuration Overview . . . . . . . . . . 3- 2System Configuration Overview. . . . . . . . 11- 2

W■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Warnings and cautions . . . . . . . . . . . . . . 7Cautions. . . . . . . . . . . . . . . . . . . . 7

Definition of Caution . . . . . . . . . . . . 8Example and format . . . . . . . . . . . . . 8

Failure to comply with warnings . . . . . . . . 7

Warnings and cautions (contd.)Warnings . . . . . . . . . . . . . . . . . . . 7

Definition of Warning . . . . . . . . . . . . 7Example and format . . . . . . . . . . . . . 7


installation and configuration c-sgsn-1

Documents

potentially hazardous voltage

reporting safety issues

dismantling heavy assemblies

pdp context activation

fibre optic cables

metal oxide semiconductor

violates safety standards

adequate lifting facilities