SGSN Principles How Does It Works PDF

HUAWEI SGSN9810 Serving GPRS Support Node
V800R009
System Principle
Issue 03
Date 2009-05-27
Part Number 00413586
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Proprietary and Confidential

System Principle Contents
Contents
About This Document.....................................................................................................................1

1 System Structure of SGSN9810...............................................................................................1-1
1.1 Overview of SGSN9810..................................................................................................................................1-2
1.2 Hardware Structure.........................................................................................................................................1-3
1.2.1 SGSN subracks.......................................................................................................................................1-3
1.2.2 PSM Subrack..........................................................................................................................................1-5
1.2.3 SGSN Board...........................................................................................................................................1-6
1.3 Software Structure...........................................................................................................................................1-8
1.3.1 Platform System..................................................................................................................................1-10
1.3.2 Service System.....................................................................................................................................1-10
1.3.3 Charging System..................................................................................................................................1-11
1.3.4 O&M System........................................................................................................................................1-11
2 Principle of the Hardware........................................................................................................2-1

2.1 Interconnection Between PSM Subracks.......................................................................................................2-2
2.2 Buses in PSM Subracks...................................................................................................................................2-3
2.2.1 Shared Resource Bus..............................................................................................................................2-3
2.2.2 H.110 Bus...............................................................................................................................................2-4
2.2.3 Serial Port Bus........................................................................................................................................2-6
2.3 Power Supply SubSystem...............................................................................................................................2-7
2.3.1 Structure.................................................................................................................................................2-7
2.3.2 Power Supply Monitoring...................................................................................................................2-10
2.4 Clock Synchronization Subsystem................................................................................................................2-12
2.4.1 Technical Specifications......................................................................................................................2-12
2.4.2 Structure...............................................................................................................................................2-14
2.4.3 Clock Interface Part..............................................................................................................................2-15
2.4.4 Clock Distribution Part.........................................................................................................................2-16
2.4.5 Clock Control Part................................................................................................................................2-18
2.5 Equipment Monitoring Subsystem................................................................................................................2-18
2.5.1 Fan Monitoring.....................................................................................................................................2-18
2.5.2 Equipment Room Environment Monitoring........................................................................................2-19
3 Principle of the Platform System............................................................................................3-1

3.1 The location of the platform system................................................................................................................3-2
Issue 03 (2009-05-27) Huawei Proprietary and Confidential i

Contents System Principle
3.2 Platform Management Subsystem...................................................................................................................3-3

3.2.1 The Structure of Platform Management Subsystem..............................................................................3-3
3.2.2 Load Management..................................................................................................................................3-4
3.2.3 Startup Management..............................................................................................................................3-6
3.2.4 Switchover Management........................................................................................................................3-7
3.2.5 Patch Processing.....................................................................................................................................3-9
3.3 Internal Communication Subsystem.............................................................................................................3-11
3.3.1 Structure...............................................................................................................................................3-11
3.3.2 The procedure for exchanging data between the subracks...................................................................3-12
4 Principle of the Service System...............................................................................................4-1

4.1 The structure of the service processing system...............................................................................................4-2
4.2 IP Routing Subsystem.....................................................................................................................................4-3
4.2.1 The structure of IP Routing Subsystem..................................................................................................4-3
4.2.2 Principle of IP routing subsystem..........................................................................................................4-5
4.3 Gb Interface Subsystem..................................................................................................................................4-7
4.3.1 The structure of Gb Interface Subsystem...............................................................................................4-7
4.3.2 The procedure for processing Gb packets in the Gb interface subsystem..............................................4-9
4.4 Iu Interface Control Plane Subsystem...........................................................................................................4-11
4.4.1 The structure of Iu Interface Control Plane Subsystem.......................................................................4-11
4.4.2 The procedure for signaling processing in the Iu interface signaling subsystem................................4-14
4.5 Gn/Gp Interface Subsystem .........................................................................................................................4-16
4.5.1 The structure of Gn/Gp Interface Subsystem ......................................................................................4-16
4.5.2 The procedure for User Data forwarding.............................................................................................4-18
4.5.3 Procedure for Processing Gn/Gp Signaling Data.................................................................................4-20
4.5.4 Procedure for DNS Resolution.............................................................................................................4-21
4.5.5 Procedure for NTP Synchronization....................................................................................................4-22
4.6 Signaling Subsystem.....................................................................................................................................4-23
4.6.1 The structure of Signaling Subsystem..................................................................................................4-23
4.6.2 Procedure for L3 Signaling .................................................................................................................4-26
4.7 Typical Data Processing Procedure...............................................................................................................4-28
4.7.1 2.5G signaling data flow......................................................................................................................4-28
4.7.2 3G signaling data flow.........................................................................................................................4-30
4.7.3 2.5G service data flow..........................................................................................................................4-31
4.7.4 3G service data flow.............................................................................................................................4-32
5 Principle of the Charging System...........................................................................................5-1

5.1 The location of the charging system in the SGSN..........................................................................................5-2
5.2 The structure of the modules in the charging system......................................................................................5-3
5.3 The procedure for generating a CDR..............................................................................................................5-4
5.4 Processing and Sending a CDR.......................................................................................................................5-6
6 Principle of the O&M System..................................................................................................6-1

6.1 The location of the O&M system in the SGSN...............................................................................................6-3
ii Huawei Proprietary and Confidential Issue 03 (2009-05-27)

System Principle Contents
6.2 The structure of the modules in the O&M system..........................................................................................6-4

6.3 Configuration Management.............................................................................................................................6-5
6.4 Performance Measurement..............................................................................................................................6-7
6.4.1 The basic concepts of performance measurement..................................................................................6-7
6.4.2 Procedure for performance measurement...............................................................................................6-8
6.5 Alarm Management.......................................................................................................................................6-10
6.6 Query and Control.........................................................................................................................................6-13
6.7 Security Management....................................................................................................................................6-14
6.7.1 Domain Management...........................................................................................................................6-14
6.7.2 User Authorities...................................................................................................................................6-15
6.7.3 User Name and Password.....................................................................................................................6-15
6.7.4 Command Groups................................................................................................................................6-16
6.8 User or Interface Tracing..............................................................................................................................6-17
6.9 Log Management...........................................................................................................................................6-18
6.10 External Maintenance Interface...................................................................................................................6-19
6.10.1 Command Input and Output Interface................................................................................................6-20
6.10.2 SNMP Interface..................................................................................................................................6-21
6.10.3 SSH.....................................................................................................................................................6-21
Index.................................................................................................................................................i-1
Issue 03 (2009-05-27) Huawei Proprietary and Confidential iii

System Principle Figures
Figures
Figure 1-1 Location of the SGSN9810 in a GPRS/UMTS network....................................................................1-2

Figure 1-2 Hardware configuration of the SGSN9810.........................................................................................1-4
Figure 1-3 Boards in the switching subrack.........................................................................................................1-5
Figure 1-4 Boards in the basic subrack................................................................................................................1-6
Figure 1-5 Boards in the extended subrack for both 2.5G and 3G services ........................................................1-6
Figure 1-6 Structure of the SGSN9810 software.................................................................................................1-9
Figure 2-1 Interconnection between the PSM subracks.......................................................................................2-2
Figure 2-2 Buses in the PSM subrack..................................................................................................................2-3
Figure 2-3 Shared resource bus............................................................................................................................2-4
Figure 2-4 H.110 bus............................................................................................................................................2-5
Figure 2-5 Principle of the USPU switchover......................................................................................................2-6
Figure 2-6 Serial port bus.....................................................................................................................................2-7
Figure 2-7 Power input part..................................................................................................................................2-8
Figure 2-8 Power distribution part.......................................................................................................................2-9
Figure 2-9 Principles of monitoring the PDB....................................................................................................2-10
Figure 2-10 Principles of monitoring the UPWR...............................................................................................2-11
Figure 2-11 Maximum allowed input jitter and lower limit of wander..............................................................2-14
Figure 2-12 Architecture of the clock synchronization system..........................................................................2-15
Figure 2-13 Procedure for clock distribution inside the PSM subrack..............................................................2-17
Figure 2-14 Fan monitoring...............................................................................................................................2-18
Figure 2-15 Equipment room environment monitoring.....................................................................................2-19
Figure 3-1 Location of the platform system in the SGSN....................................................................................3-2
Figure 3-2 Modules inside the platform management subsystem........................................................................3-3
Figure 3-3 Loading channels for each board........................................................................................................3-5
Figure 3-4 Sequence of board startup...................................................................................................................3-7
Figure 3-5 Switchover procedure.........................................................................................................................3-8
Figure 3-6 Working principle of the software patch..........................................................................................3-10
Figure 3-7 Transfer of patch states.....................................................................................................................3-11
Figure 3-8 Logical structure of the internal communication subsystem............................................................3-12
Figure 3-9 Procedure for exchanging data between the subracks......................................................................3-13
Figure 4-1 Structure of the service system...........................................................................................................4-2
Figure 4-2 Modules inside the IP routing subsystem ..........................................................................................4-4
Figure 4-3 Procedure for processing IP packets in the IP routing subsystem......................................................4-6
Issue 03 (2009-05-27) Huawei Proprietary and Confidential v

Figures System Principle
Figure 4-4 Modules inside the Gb interface subsystem ......................................................................................4-8

Figure 4-5 Procedure for processing Gb packets in the Gb interface subsystem...............................................4-10
Figure 4-6 Modules inside the Iu interface control plane interface subsystem..................................................4-12
Figure 4-7 Procedure for signaling processing in the Iu interface signaling subsystem....................................4-15
Figure 4-8 Modules inside the Gn/Gp interface subsystem...............................................................................4-17
Figure 4-9 Procedure for forwarding user data..................................................................................................4-19
Figure 4-10 Procedure for processing the Gn/Gp signaling data.......................................................................4-20
Figure 4-11 Procedure for DNS resolution .......................................................................................................4-21
Figure 4-12 Procedure for NTP synchronization ..............................................................................................4-22
Figure 4-13 Modules inside the signaling subsystem........................................................................................4-24
Figure 4-14 Procedure for signaling processing ................................................................................................4-27
Figure 4-15 Processing procedure for 2.5G uplink signaling data flow ............................................................4-29
Figure 4-16 Processing procedure for 3G uplink signaling data flow ...............................................................4-30
Figure 4-17 Processing procedure for 2.5G uplink service data flow ...............................................................4-31
Figure 4-18 Processing procedure for 3G uplink service data flow...................................................................4-32
Figure 5-1 Location of the charging system in the SGSN................................................................................... 5-2
Figure 5-2 Structure of the charging subsystems ................................................................................................5-3
Figure 5-3 Charging flow points for the mobility management service.............................................................. 5-5
Figure 5-4 Procedure for sending a CDR.............................................................................................................5-7
Figure 6-1 Location of the O&M system in the SGSN........................................................................................6-3
Figure 6-2 Hierarchy of the O&M system........................................................................................................... 6-4
Figure 6-3 Composition of the O&M system.......................................................................................................6-5
Figure 6-4 Configuration management flow........................................................................................................6-6
Figure 6-5 Procedure for performance measurement...........................................................................................6-8
Figure 6-6 Alarm management flow..................................................................................................................6-11
Figure 6-7 Query and control flow.....................................................................................................................6-13
Figure 6-8 Procedure for user authentication.....................................................................................................6-15
Figure 6-9 Procedure for user tracing or interface tracing ................................................................................6-18
Figure 6-10 External O&M interfaces of the SGSN .........................................................................................6-20
Figure 6-11 Structure and flow of SNMP..........................................................................................................6-21
Figure 6-12 Establishing an SSH channel between the SGSN and LMT..........................................................6-22
vi Huawei Proprietary and Confidential Issue 03 (2009-05-27)

System Principle Tables
Tables
Table 1-1 Boards in the SGSN ............................................................................................................................1-7

Table 2-1 Connection description in the PSM subrack......................................................................................2-10
Table 2-2 Technical specifications of the clock synchronization system...........................................................2-13
Table 5-1 MS status in the M-CDR generation procedure...................................................................................5-5
Table 5-2 Description of the charging flow points...............................................................................................5-6
Table 6-1 User groups and authorities................................................................................................................6-15
Table 6-2 Command group description..............................................................................................................6-16
Issue 03 (2009-05-27) Huawei Proprietary and Confidential vii

System Principle About This Document
About This Document
Purpose
This manual describes the following content:
l Position, functions, hardware structure, and software structure of the SGSN
l Implementation principles of the hardware, platform system, service system, charging
system, and O&M system
Related Versions
The following table lists the product versions related to this document.
Product Name Version
SGSN9810 V800R009
Intended Audience
The intended audiences of this document are:
l Marketing staff
l Installation engineers & technicians
l Operation & maintenance personnel
Organization
1 System Structure of SGSN9810
The syetem structure of SGSN consists of hardware structure and software structure
2 Principle of the Hardware
The principle of the hardware system involves principles of the interconnection between
subracks, internal cables, power supply, clocks, and monitoring system.
3 Principle of the Platform System
The platform system consists of the platform management subsystem and internal
communication subsystem. The system realizes board drive, communications, and data
management.
4 Principle of the Service System
Issue 03 (2009-05-27) Huawei Proprietary and Confidential 1

About This Document System Principle
The service system consists of the IP routing subsystem, Gb interface subsystem, Iu interface
control plane subsystem, Gn/Gp interface subsystem, and signaling subsystem. The service
system processes the external interface protocol and high-level signaling for the SGSN and
forwards user data.
5 Principle of the Charging System
The charging system operates in the USPU, UGTP, and UCDR boards. The charging system
collects, codes, buffers, and sends CDRs as well as provides charging information for the billing
center.
6 Principle of the O&M System
The O&M system is a management center of the SGSN. The O&M system provides interactive
interfaces between an operator and the SGSN.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

avoided,will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not

avoided,could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save

time.
Provides additional information to emphasize or supplement

important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.
2 Huawei Proprietary and Confidential Issue 03 (2009-05-27)

System Principle About This Document
Courier New Examples of information displayed on the screen are in
Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder .
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Issue 03 (2009-05-27) Huawei Proprietary and Confidential 3

About This Document System Principle
Format Description
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 03 (2009-05-27)
Remove SGSN N+1 function.
Bug revision.
Initial field trial release.
4 Huawei Proprietary and Confidential Issue 03 (2009-05-27)

System Principle 1 System Structure of SGSN9810
1 System Structure of SGSN9810
About This Chapter
The syetem structure of SGSN consists of hardware structure and software structure
1.1 Overview of SGSN9810
The SGSN9810 is a device in a core networkpacket switched (CNPS) domain of the general
packet radio system (GPRS) or universal mobile telecommunications system(UMTS).
1.2 Hardware Structure
The SGSN9810 consists of cabinets,Subrack,Board.
1.3 Software Structure
Each board in the SGSN9810 has its own software. Based on the functions of the software, the
SGSN9810 software is divided into various software systems.
Issue 03 (2009-05-27) Huawei Proprietary and Confidential 1-1

1 System Structure of SGSN9810 System Principle
1.1 Overview of SGSN9810

The SGSN9810 is a device in a core networkpacket switched (CNPS) domain of the general
packet radio system (GPRS) or universal mobile telecommunications system(UMTS).
Figure 1-1 shows the location of the SGSN9810 in a GPRS/UMTS network.
Figure 1-1 Location of the SGSN9810 in a GPRS/UMTS network
RAN CN-CS
GSM/GPRS BSS HLR
MSC/VLR SMS-GMSC
BSC SMS-IWMSC
PSTN,
GMSC ISDN
BTS
MS
UMTS UTRAN SS7
Billing
RNC EIR Center
CG
NodeB
DNS
Firewall SGSN Firewall Server
WAP
Core Gateway
Other PLMN Network
BG
GGSN HA
Internet,
DNS /FA
Intranet, AAA
Server
etc. Server
CN-PS
MS: mobile station RAN: radio access network
CN-CS: core network circuit switched CN-PS: core network packet switched domain
domain
BSS: base station subsystem UTRAN: UMTS terrestrial radio access network
BTS: base transceiver station BSC: base station controller
RNC: radio network controller BG: border gateway
SGSN: serving GPRS Support Node HA: home agent
1-2 Huawei Proprietary and Confidential Issue 03 (2009-05-27)

CG: charging gateway DNS: domain name service
GGSN/FA: gateway GPRS support node/ AAA: authentication, authorization, and

foreign agent accounting
MSC/VLR: mobile service switching center/ HLR: home location register

visitor location register
WAP: wireless access protocol EIR: equipment identification register
SMS-GMSC: short message service SMS-IWMSC: short message service

gateway MSC interworking MSC
GMSC: gateway MSC PSTN: public switched telephone network
ISDN: integrated services digital network SS7: CCITT signaling system No.7
The serving GPRS support node (SGSN) provides the following functions:
l Routing and forwarding of data packets

l Encryption and authentication
l Session management
l Mobility management
l Logical link management
l Generation and output of charging data records (CDRs)
1.2 Hardware Structure

The SGSN9810 consists of cabinets,Subrack,Board.
1.2.1 SGSN subracks
The SGSN9810 consists of one or more cabinets. Each cabinet houses four subracks that are
called packet service module (PSM) subracks.
1.2.2 PSM Subrack
Each PSM subrack has 21 slots. Boards can be inserted from both the front side and the rear side
of the subrack.PSM subracks are classified into the switching subrack, basic subrack, and
extended subrack.
1.2.3 SGSN Board
The boards in the SGSN process services for the SGSN.
1.2.1 SGSN subracks

The SGSN9810 consists of one or more cabinets. Each cabinet houses four subracks that are
called packet service module (PSM) subracks.

of the subrack.
Figure 1-2 shows the SGSN9810 hardware in full configuration.
Figure 1-2 Hardware configuration of the SGSN9810
Power Distribution Box
U U U U U U U U U U U U U U U U U
C C G G F F R R F F F F G G A P P
D D F F C C C C C C C C F F L W W
R R U U U U U U U U U U U U U R R
PSM Subrack
Air Deflector
I I S S S S R R S S G G G G A P P
C C P P P P C C P P B B B B L W W
P P U U U U U U U U I I I I U R R
PSM Subrack
Air Deflector
G G G G S S R R S S G G G G A P P
B B B B P P C C P P B B B B L W W
I I I I U U U U U U I I I I U R R
PSM Subrack
Air Deflector
U U U U U U U U U U U U U U U
G G G G G G R R O O G G A P P
T T B B F F C C M M T T L W W
P P I I U U U U U U P P U R R
PSM Subrack
Dummy Pannel

1.2.2 PSM Subrack

of the subrack.PSM subracks are classified into the switching subrack, basic subrack, and
extended subrack.
The following slots are fixedly configured:
l Slot 6 and Slot 8: configured with the URCU (front board) and the UBIU (back board)
l Slot 7 and Slot 9: configured with the UACU (back board)
l Slot 17 and Slot 19: configured with the UPWR, which occupies two slots and is inserted
from both the front side and the rear side of the slot
l Slot 16: configured with the UALU (front board)
Other slots are common slots, which can be configured with any types of boards. Based on the
configurations for different boards, PSM subracks are classified into the switching subrack, basic
subrack, and extended subrack.
Switching Subrack
The PSM subrack configured with the frame connect unit (UFCU) is called the switching
subrack. The SGSN can be and must be configured with only one switching subrack.
Figure 1-3 shows the switching subrack in full configuration.
Figure 1-3 Boards in the switching subrack
U U U U U U U U U U U U U U U U U U
B B P P P P B A B A P P P P P P P P
S S I I I I I C I C I I I I I I W W
U U U U U U U U U U U U U U U U R R
C C G G F F R R F F F F G G A P P
D D F F C C C C C C C C F F L W W
R R U U U U U U U U U U U U U R R
NOTE
In Figure 1-3, the boards in the upper part of the subrack are inserted from the rear, and the boards in the
lower part are inserted from the front.
Basic Subrack
The PSM subrack configured with the packet service O&M unit (UOMU) is called the basic
subrack. The SGSN can be and must be configured with only one basic subrack.
Figure 1-4 respectively show the boards in the basic subrack.

Figure 1-4 Boards in the basic subrack
U U U U U U U U U U U
B A B A F F L C C P P
I C I C S S A K K W W
U U U U U U N I I R R
U U U U U U U U U U U
R R O O G G S S A P P
C C M M T T P P L W W
U U U U P P U U U R R
NOTE
In the above three figure, the boards in the upper part of the subrack are inserted from the rear, and the
boards in the lower part are inserted from the front.
Extended Subrack
Other PSM subracks except the switching subrack and basic subrack are called the extended
subracks. The SGSN can be configured with no extended subrack or with multiple extended
subracks.
An extended subrack can be configured to process 2.5G services, 3G services, or both of them.
Figure 1-5 shows the boards in the extended subrack for both 2.5G and 3G services.
Figure 1-5 Boards in the extended subrack for both 2.5G and 3G services
U U U U U U U U U U U U U U U U
E E E E E E B A B A E E E E P P
P P P P P P I C I C P P P P W W
I I I I I I U U U U I I I I R R
G G G G S S R R S S S S I I A P P
B B B B P P C C P P P P C C L W W
I I I I U U U U U U U U P P U R R
NOTE
In Figure 1-5, the boards in the upper part of the subrack are inserted from the rear, and the boards in the
lower part are inserted from the front.
1.2.3 SGSN Board

The boards in the SGSN process services for the SGSN.
Table 1-1 lists all the boards in the SGSN.

Table 1-1 Boards in the SGSN

Name Description
UACU Auxiliary control unit
UAIC Asynchronous transfer mode (ATM)

interface card
UALU Alarm unit
UBIU Back interface unit
UBSU Back storage unit
UCDR Charging detail record unit
UCKI Clock unit
UEEC Ethernet electric interface card
UEFC Ethernet fiber interface card
UEPC Encryption processing card
UEPI E1 processing interface unit
UTPI T1 processing interface unit
UFCU Frame connect unit
UFEU Frame relay enhance unit
UFIU Fiber interface unit
UFSU PSM flash disk storage unit
UGBI Gb interface unit
UGFU GPRS tunneling protocol (GTP) forwarding

unit
UGTP GTP processing unit
UICP Iu_PS control processing unit
ULAN LAN-switch card
UOMU Packet service O&M unit
UPIU Packet interface unit
URCU Sub-rack control unit
USIG SIGTRAN process unit
USPU Packet service signal processing unit
USS7 CCITT signaling system No.7 (SS7)

signaling link processing unit

Name Description
UPWR PSM power module
1.3 Software Structure

Each board in the SGSN9810 has its own software. Based on the functions of the software, the
SGSN9810 software is divided into various software systems.
As shown in Figure 1-6.

Figure 1-6 Structure of the SGSN9810 software

No.7
signalling
BSS
node, such
as HLR
E1 E1
UICP UGTP UGBI USPU
Iu interface
Gn/Gp Gb
control O Charging O O Signaling Charging O
interface interface
plane M system M M subsystem system M
subsystem subsystem
subsystem BSS
Platform Platform
Platform management Platform management
management management
BUS
UOMU URCU USIG
Internal
O Signaling O
OM communication
M subsystem M
subsystem
Platform Platform
Platform management
Service subrack
Network cable Fiber cable Fiber cable

LMT
Fiber cable
UCDR UFCU UGFU

Gn/Gp
Internal interface
Charging O O subsystem O
communication
system M M M
subsystem
IP routing
subsystem
Platform Platform Platform

management management management
Switching subrack BUS
Fiber cable or
network cable
IP node,
RNC such as
GGSN
NOTE
When Gb over IP and SS7 over IP functions are used, the UGFU provides the interfaces to connect the
SGSN with the HLR and BSS.
The SGSN9810 software consists of the following four systems:
l Platform system
l Service system

l Charging system
l O&M system
The following sections describe the functions of each system.

1.3.1 Platform System
communication subsystem. The platform system realizes board drive, communications between
boards, and data management.
1.3.2 Service System
The service system consists of the internet protocol (IP) routing subsystem, Gb interface
subsystem, Iu interface control plane subsystem, Gn/Gp interface subsystem, and signaling
subsystem. The service system processes the external interface protocols and high-level
signaling for the SGSN and transfers user data.
1.3.3 Charging System
The charging system collects, codes, buffers, and sends CDRs and provides charging information
for the billing center.
1.3.4 O&M System
The O&M system provides the O&M interfaces for the SGSN. The O&M system realizes alarm
management, performance statistics, signaling tracing, in addition to command resolution and
processing.
1.3.1 Platform System

communication subsystem. The platform system realizes board drive, communications between
boards, and data management.
The subsystems of the platform system has the following functions:
l Platform management subsystem
It realizes operation system, hardware drive, communications between boards,
configuration data, and user data management. It is the foundation on which other software
modules operate.
It works in all the boards.
l Internal communication subsystem
It realizes routing and forwarding of data or signaling between subracks.
It works in the UFCU of the switching subrack, in addition to the URCU, UCDR, and
UOMU of the service subrack. The main functions are realized in the UFCU.
NOTE
Unless specially mentioned, the boards involved in this manual include subboards and back boards. For
example, the UOMU mentioned above includes the UOMU and UFSU.
1.3.2 Service System

The service system consists of the internet protocol (IP) routing subsystem, Gb interface
subsystem, Iu interface control plane subsystem, Gn/Gp interface subsystem, and signaling
subsystem. The service system processes the external interface protocols and high-level
signaling for the SGSN and transfers user data.
The subsystems of the service system has the following functions:

l IP routing subsystem
It provides the interfaces to connect the SGSN with the external IP networks and carries
out IP routing and security check.
The IP routing subsystem works in the UGFU board.
l Gb interface subsystem
It realizes the functions of the physical layer, frame relay (FR), network service (NS), base
station subsystem GPRS protocol (BSSGP), subnetwork dependent convergence protocol
(SNDCP), and logical link control (LLC) layers for the Gb interface.
The Gb interface subsystem works in the UGBI board.
l Iu interface control plane subsystem
It realizes the functions of the signaling ATM adaptation layer (SAAL), message transfer
part broadband (MTP3B), signaling connection and control part (SCCP), and radio access
network application part (RANAP) layers for the Iu interface control plane.
The Iu interface subsystem works in the UICP board.
l Gn/Gp interface subsystem
It realizes GTP-C signaling forwarding, network time protocol (NTP) client, domain name
service (DNS) client, and GPRS tunnel protocol (GTP) data packets forwarding between
the Gn/Gp interface and Iu interface or between the Gn/Gp interface and Gb interface
The Gn/Gp interface subsystem works in the UGTP and UGFU boards.
l Signaling subsystem
It realizes the functions of message transfer part (MTP) L1/L2/L3, or simple control
transmission protocol (SCTP) and SS7 MTP3-user adaptation (M3UA) layers of
SIGTRAN for SS7 in addition to the functions of SCCP, transaction capability application
part (TCAP), mobile application part (MAP), CAMEL application part (CAP), mobility
management (MM), session management (SM), short message service (SMS), customized
applications for mobile network enhanced logic (CAMEL), and base station subsystem
application part (BSSAP+) protocol layers.
The signaling subsystem works in the USPU and USIG boards. The USIG board realizes
the functions of SCTP and M3UA layers, while other functions are realized by the USPU
board.
1.3.3 Charging System

The charging system collects, codes, buffers, and sends CDRs and provides charging information
for the billing center.
The charging system operates in the USPU, UGTP, and UCDR boards.
1.3.4 O&M System

The O&M system provides the O&M interfaces for the SGSN. The O&M system realizes alarm
management, performance statistics, signaling tracing, in addition to command resolution and
processing.
The O&M system consists of the host software and terminal software.
l The host software works in all the boards. Its main functions are realized in the UOMU.
l The terminal software works in the PC and provides the man machine interface.

System Principle 2 Principle of the Hardware
2 Principle of the Hardware
About This Chapter
The principle of the hardware system involves principles of the interconnection between
subracks, internal cables, power supply, clocks, and monitoring system.
2.1 Interconnection Between PSM Subracks
The SGSN consists of multiple subracks. The subracks communicate with each other through
the switching subrack.
2.2 Buses in PSM Subracks
The buses in the PSM subrack transfer the data, clocks, and control signals between the boards
in the subrack.
2.3 Power Supply SubSystem
The power supply subsystem powers the entire SGSN9810. It requires high reliability. The
SGSN9810 adopts a dual-circuit backup and point-to-point monitoring method in the design.
2.4 Clock Synchronization Subsystem
When the SGSN9810 provides narrowband signaling to connect with other devices or frame
relay (FR) to connect with the base station subsystem (BSS), the clock synchronization
subsystem is required to be configured to carry out clock synchronization.
2.5 Equipment Monitoring Subsystem
The equipment monitoring subsystem consists of fan monitoring and equipment room
environment monitoring to ensure that the SGSN can work in a normal environment.

2 Principle of the Hardware System Principle
2.1 Interconnection Between PSM Subracks

The SGSN consists of multiple subracks. The subracks communicate with each other through
the switching subrack.
Figure 2-1 Interconnection between the PSM subracks
U U U U U U U U
R R O O C C R R
C C M M D D C C
U U U U R R U U
U U U U U U U U
B B F F B B B B
I I S S S S I I
U U U U U U U U
U
L
A
N
U U U U U U U U
P P P P P P B B
I I I I I I I I
U U U U U U U U
U U U U U U U U
F F F F F F R R
C C C C C C C C
U U U U U U U U
Switching subrack
The UBIUs, back boards of the URCUs in each PSM subrack, connect to the UPIUs, back boards
of the UFCUs in the switching subrack through SDH transport module-1 (STM-1) fibers.
Through information exchange and routing of the UFCU, the boards in different PSM subracks
can communicate with each other.
Though the UOMUs and UCDRs are inserted in the PSM subrack, they cannot directly
communicate with the URCUs in the same subrack. The back boards of the UOMUs and UCDRs
connect with the UPIUs, back boards of the UFCUs. Through information exchange and routing
of the UFCU, the UOMUs and UCDRs can communicate with all other boards.
The UFSUs, back boards of the UOMUs, connect with the ULANs and UBIUs, back boards of
the URCUs in the switching subrack through network cables to form an initial loading channel
for the active URCU when the system is power-on.

2.2 Buses in PSM Subracks

The buses in the PSM subrack transfer the data, clocks, and control signals between the boards
in the subrack.
The PSM subrack contains the following three types of buses, as shown in Figure 2-2.
l Shared resource bus

l H.110 bus
l Serial port bus
Figure 2-2 Buses in the PSM subrack
U U U U
BB: back board B B B B B B B A B A B B B B B B
B B B B B B I C I C B B B B B B
U U U U
Serial port bus

H.110 bus
Shared resoure Shared resoure
bus A bus B
U U U
F F F F F F R R F F F F F F A
FB: front board
B B B B B B C C B B B B B B L
U U U
2.2.1 Shared Resource Bus

The shared resource bus is also called OSTA bus.
2.2.2 H.110 Bus
The H.110 bus provides the following functions: Carrying out service switchover between the
active and standby USPUs or UGBIs. Providing a transmission channel for reference clock in
the subrack
2.2.3 Serial Port Bus
The serial port bus carries out control, load, and state query for the boards that are controlled by
the center processing unit (CPU) in the subrack but not connected to the shared resource bus.
These boards include the UCKI, UEPI, and UALU.
2.2.1 Shared Resource Bus

The shared resource bus is also called OSTA bus.
Functions
Through the shared resource bus, the URCU carries out loading, managing, and maintaining the
USPU, UICP, UGBI, UGTP and USIG boards in the subrack.

NOTE
Though the UOMUs and UCDRs are inserted in the PSM subrack, they communicate with the URCUs in
the switching subrack through fibers instead of the shared resource bus.
The backplane (motherboard) in the PSM subrack provides pins for the shared resource bus to
connect the bus with the boards.
Realization
As shown in Figure 2-3, each subrack has two shared resource buses, namely A and B. The
bandwidth of each shared resource bus is 2 Gbit/s.
Figure 2-3 Shared resource bus
U U U U
FB: front board B A B A
I C I C
U U U U
Shared resource bus A Shared resource bus B
U U
F F F F F F R R F F F F F F
B B B B B B C C B B B B B B
U U
Slot 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
The URCU at slot 6 manages the front boards configured in the left half of the subrack through
shared resource bus A. The URCU at slot 8 manages the front boards (except the UALU and
UPWR) configured in the right half of the subrack through shared resource bus B.
The UACUs at slots 7 and 9 are respectively connected to the two shared resource buses to bridge
the two buses. In this case, the URCU at slot 6 can manage the front boards (except the UALU
and UPWR) configured in the right half of the subrack through shared resource bus B, and the
URCU at slot 8 can manage the front boards configured in the left half of the subrack through
shared resource bus A.
The URCUs adopt the active and standby working mode. The active URCU manages the front
boards (except the UALU and UPWR) in the whole subrack through shared resource bus A and
shared resource bus B.
2.2.2 H.110 Bus

The H.110 bus provides the following functions: Carrying out service switchover between the
active and standby USPUs or UGBIs. Providing a transmission channel for reference clock in
the subrack

Functions
As shown in Figure 2-4, each subrack has one H.110 bus, which provides a switching capacity
of 4,096 timeslots and bandwidth of 256 Mbit/s. The H.110 bus provides the following functions:
l Carrying out service switchover between the active and standby USPUs or UGBIs.
l Providing a transmission channel for reference clock in the subrack.
Figure 2-4 H.110 bus
BB: back U U U U
board B B B B B B B A B A B B B B B B
U U U U
H.110 bus
FB: front
board U U
F F F F F F R R F F F F F F
B B B B B B C C B B B B B B
U U
Service Backup for Front Board Switchover

NOTE
This section takes the USPU switchover as an example. The switchover procedure for the UGBI is similar
to that for the USPU.
As shown in Figure 2-5, the communication path for narrowband SS7 is from E1, UEPI 0,
internal highway bus, and to USPU0.
When the USPU is switched over, the communication path is from E1, UEPI 0, H.110 bus, UEPI
1, internal highway bus, and to USPU0.
NOTE
The highway bus is used to transfer data between the front board and its back board. The transfer rate is 8
Mbit/s. Two channels of highway buses correspond to eight channels of E1 in the back board.

Figure 2-5 Principle of the USPU switchover

Data Data
UEPI0 UEPI1 UEPI0 UEPI1
H.110 bus H.110 bus
HW HW HW HW
USPU0 USPU1 USPU0 USPU1
Before After
switchover switchover
CAUTION
Only in the case of front board switchover, H.110 bus can carry out service backup. Because E1
is fixedly configured in the UEPI, the signaling link may be interrupted if the back board is
switched over.
2.2.3 Serial Port Bus

The serial port bus carries out control, load, and state query for the boards that are controlled by
the center processing unit (CPU) in the subrack but not connected to the shared resource bus.
These boards include the UCKI, UEPI, and UALU.
As shown in Figure 2-6, the rate of the serial port bus is 9,600 bit/s. The URCU is an active
node. The UCKI, UEPI, and UALU are standby nodes.

Figure 2-6 Serial port bus
U U U U
B B B B B B B A B A B B B B B B
U U U U
Serial port bus
BB: back board U U U

R R A
C C L
U U U
NOTE
The standby node of the serial ports also includes the power distribution box. It communicates with the
active node at the rate of 9,600 bit/s.
2.3 Power Supply SubSystem

The power supply subsystem powers the entire SGSN9810. It requires high reliability. The
SGSN9810 adopts a dual-circuit backup and point-to-point monitoring method in the design.
2.3.1 Structure
The power supply system consists of two parts:Power input part and Power distribution part
2.3.2 Power Supply Monitoring
The power supply monitoring module monitors the power supply system in real time, reports
power running status, and generates alarms when detecting faults.
2.3.1 Structure
The power supply system consists of two parts:Power input part and Power distribution part
Power Input Part

The power input part refers to the power distribution frame (PDF) from the direct current (DC)
distributor to the SGSN9810 cabinet.

Figure 2-7 Power input part
(2)
-48V1
PGND
BGND
-48V1
-48V1
-48V2
PGND
BGND
-48V2
-48V2
-48V1
PGND
BGND
-48V2
(1) GND
GND
PGND
(3) (3) (3)
(4)
(1) DC distributor (2) Power distribution frame
(3) SGSN9810 cabinet (4) Protection grounding bus
The power input part contains the DC distributor, the PDF, and the connection cables.
The DC distributor and the power distribution cabinet are not parts of the SGSN9810. The power
distribution cabinet is required to provide two independent and stable channels of input power
supply. The DC distributor provides two independent channels of 48 V power supply and one
channel of protection ground (PGND) for each SGSN9810 cabinet.
Normally, two channels of 48 V power supply work at the same time. When one is faulty, the
other independently supplies power.
Power Distribution Part

The power distribution part refers to power distribution from the power distribution box (PDB)
to each component of the cabinet.

Figure 2-8 Power distribution part
-48V1 RTN1 -48V2 RTN2 -48V3 RTN3 -48V4 RTN4 -48V5 RTN5 -48V6 RTN6
1.1 1.2 2.1 2.2 5.1 5.2 6.1 6.2 7.1 7.2 8.1 8.2
QW11WSTB
9
COM1
COM2
10
QW11WSTB
11
3.1 3.2 4.1 4.2

W1
PSM3
5.1 5.2 8.1 8.2

W3 W2
PSM2
3.13.2 4.1 4.2

W5 W4
12
PSM1
2.1 2.2 7.1 7.2

W7 W6
UBIU UBIU
PSM0
ATM155M
8K_IN
8K_OUT
COM1
COM2
COM2 + 9 10
10/100 BT
13
11 12 6.1 6.2
W9 W8
Table 2-1 lists the cable numbers and cable names in Figure 2-8.

Table 2-1 Connection description in the PSM subrack

Cable Name Cable Number
PSM0 subrack power cable 1 and 6
PDB monitor cable 9 and 10
Subrack PGND cable From W2 to W9
Inter-cabinet PGND cable From 11 to 13
Two channels of 48 V power supply are input into a power distribution box (PDB) after
lightning protection and overcurrent protection. Then eight channels of 48 V power supply in
two groups (four channels in each group) are distributed to the subracks in the cabinet. The two
groups work as hot backup for each other.
The UPWR in each subrack obtains 48 V power from the backplane. The power is then provided
for other boards after converted to the working power.
Meanwhile, the PDB checks the input power voltage and output power state. It generates an
audio alarm when a fault occurs.
2.3.2 Power Supply Monitoring

The power supply monitoring module monitors the power supply system in real time, reports
power running status, and generates alarms when detecting faults.
Monitoring the PDB

Each cabinet of the SGSN9810 is configured with a PDB, which is monitored by the service
processing subrack.
Figure 2-9 shows the principles of monitoring the PDB.
Figure 2-9 Principles of monitoring the PDB
PDB
Monitor board
RS485 RS485
UBIU UBIU
URCU URCU

The principles of monitoring the PDB are illustrated as follows:
l The PDB is equipped with a monitor board, which is used to collect the running status of
the PDB.
l The monitor board provides two RS485 serial ports, one active and the other standby.
Through the RS485 serial port cables, the active port connects with the COM2+ interface
on the UBIU, back board of the active URCU and the standby port connects with the COM2
+ interface on the UBIU, back board of the standby URCU.
l The URCU processes the information collected from the PDB and reports the results to the
UOMU. When a fault occurs, the URCU generates an alarm and sends it to the alarm
subsystem and alarm box.
NOTE
When a cabinet is configured with multiple service processing subracks, the lowest subrack installed in
the cabinet monitors the PDB of the cabinet.
Monitoring Power Supply of Service Processing Subracks

The UPWR is the power supply module in the service processing subrack. It monitors the UPWR
through the UALU of the subrack.
Figure 2-10 shows the principles of monitoring the UPWR.
Figure 2-10 Principles of monitoring the UPWR
U U
P P
W W
W U Power R R
U
S A state signal
R
M L
C
U U U U
U
P P
W W
R R
Each service processing subrack is configured with four UPWRs, two at the front and two at the
rear. The principles of monitoring the UPWR are illustrated as follows:
l The UPWR reports the power supply status to the UALU through the dedicated signal
cables in the backplane.
l The UALU monitors the power supply status in real time. It reports the status data to the
URCU. The UALU also displays the status of the back UPWRs through the indicators.
l The URCU processes the data reported by the UALU, and sends the results to the UOMU.
If the power supply system is faulty, the URCU sends an alarm to the alarm box and alarm
subsystem through the UOMU.
l The UALU has a temperature sensor to monitor the temperature of the subrack.

2.4 Clock Synchronization Subsystem

When the SGSN9810 provides narrowband signaling to connect with other devices or frame
relay (FR) to connect with the base station subsystem (BSS), the clock synchronization
subsystem is required to be configured to carry out clock synchronization.
The clock synchronization subsystem of the SGSN9810 adopts advanced digital phase-lock loop
and reliable software phase-lock technologies. It has the following features:
l The subsystem enables stratum-2 clock (including category A and category B), stratum-3
clock, and enhanced stratum-3 clock for choice.
l The structure can be flexibly customized. The stratum-2 and stratum-3 clocks can be
selected through terminals.
l The input reference source is diversified, such as 2.048 MHz and 2.048 Mbit/s.
l The software has powerful functions, such as display, alarm, and O&M functions. You can
use the maintenance terminal to control the reference clock and phase-lock mode.
l The subsystem has powerful phase-lock capability, and is applicable to different clock
transmission conditions. When the clock reference subsystem is abnormal, the clock
synchronization subsystem can work in free-run mode to maintain synchronization for a
period of time.
2.4.1 Technical Specifications
Technical specifications consists of Network access parameter, Long-term phase change, Clock
working mode, Input jitter tolerance.
2.4.2 Structure
The UCKI is the core of the whole clock synchronization system. It is fixedly configured in the
basic subrack. The active and standby UCKIs work in the hot backup mode.
2.4.3 Clock Interface Part
The clock interface part includes the UCKI, UEPI/UTPI, and UPIU boards in addition to
connected cables. It accesses and locks the clock source to provide the stable clock for the
SGSN9810.
2.4.4 Clock Distribution Part
The clock distribution part includes the UCKI, UBIU, UPIU, dedicated clock cables, and H.110
bus. The clock distribution part distributes the clock signals provided by the UCKI to the UEPIs
or UPIUs in all the subracks.
2.4.5 Clock Control Part
The clock control part includes the URCU, UOMU, local maintenance terminal (LMT), and
serial port bus.
2.4.1 Technical Specifications

Technical specifications consists of Network access parameter, Long-term phase change, Clock
working mode, Input jitter tolerance.
Table 2-2 shows the technical specifications of the clock synchronization system.

Table 2-2 Technical specifications of the clock synchronization system

Item Specification
Network access Lowest accuracy Stratum-2 clock: 410-7

parameter
Stratum-3 clock: 4.6 10-6
Pull-in range Stratum-2 clock: able to

synchronize with the accuracy of
410-7
Stratum-3 clock: able to
synchronize with the accuracy of
4.610-6
Maximum frequency offset Stratum-2 clock: 510-10/day

Stratum-3 clock: 210-4/day
Initial maximum frequency offset Stratum-2 clock: < 5 10-10/day

Stratum-3 clock: < 1 10-8/day
Long-term phase Ideal working status Maximum relative time interval

change error (MRTIE)1ms
Hold working status MRTIE (ns)as +(1/2)bs+c

The letter s indicates time with
the unit as second. The unit of
MRTIE is nanosecond (ns).
Stratum-2 clock:
a = 0.5 b = 1.1610-5 c = 1000
Stratum-3 clock:
a = 10 b = 2.310-4 c = 1000
Clock working Fast pull-in, locked, holdover, and free-run

mode
Input jitter tolerance Refer to Figure 2-11 for details.
NOTE
l Lowest accuracy is the maximum value of the offset to the nominal frequency in a long term (20 years)
in the case of no external reference frequency (free-run mode).
l Maximum frequency offset is the maximum value of the relative frequency offset in a unit period during
the consecutive running of the clock.
l Pull-in range is the maximum frequency bandwidth of the input clock signals that the clock can lock.
l MRTIE refers to the maximum peak-peak delay change of the tested clock to an actual reference clock
during the test.

Figure 2-11 Maximum allowed input jitter and lower limit of wander
Y (UI)
Peak-to-peak jitter and wander amplitude (logarithm)
2
10
A 0 =36.9
10 1
Slope: 20dB / 10 times of frequency interval
A1=1.5
1
A2=0.2
10 -1
X
1.2 10- 5 10 20 2.4 k 18 k 100 k f (Hz)
For example, if the jitter frequency of an input signal is 1 kHz, the amplitude is greater than 1.5
UI, and the system can still work normally, it indicates that the signal meets the requirements.
NOTE
UI is the unit interval. The reciprocal of the digital signal frequency is one UI. For example, the UI of 2.048
Mbit/s signal is 488 ns.
2.4.2 Structure
Figure 2-12 shows the architecture of the clock synchronization system.

Figure 2-12 Architecture of the clock synchronization system

E1 STM-1/
STM-4
U U U U
STM-1/ B E E P
E1 I P P I
STM-4 BITS
U I I U
2 MHz internal STM-1 H.110 bus
clock cable
U U U U
R G S G
C B P F
U I U U
U U U 8 kHz internal U U
P E B clock cable B P
I P I I I
U I U U U
U E1 STM-1/
C STM-4
H.110 bus K STM-1
I
U U U U U
G S R R F
F P C C C
U U U U U U U U U
B E E P
I P P I
Switching
U I I U
subrack
H.110 bus
U U U U
R G S G
C B P F
U I U U
The clock synchronization system of the SGSN9810 consists of three parts:

l Clock interface part
l Clock signaling distribution part
l Clock control part
2.4.3 Clock Interface Part

The clock interface part includes the UCKI, UEPI/UTPI, and UPIU boards in addition to
connected cables. It accesses and locks the clock source to provide the stable clock for the
SGSN9810.
The SGSN9810 supports two types of clock sources, cable clock source and building integrated
timing supply (BITS) clock source. If the clock source is stratum 2, the local clock can be set to
stratum 2 or stratum 3. If the clock source is stratum 3, the local clock can be set to only stratum
3.
l Cable clock source
If the clock stratum of the peer device (HLR) is lower than stratum 3, the local end can
extract the clock source from the E1 or SDH that is connected with the peer end.

The UEPI provides the E1 interface to extract the E1 cable clock from the peer end and
generate a 2 MHz clock source.
The UPIU provides the SDH interface for ATM-1 or ATM-4 to extract the SDH cable
clock and generate a 2 MHz clock source. The extracted 2 MHz clock is sent to the
UBIU through the local bus. Then the UBIU provides the clock interface for the clock
to access the UCKI.
The UCKI obtains the cable clock from the UEPI or UBIU through the 2 MHz internal
clock cable.
The UCKI traces, locks, and generates the cable clock and then generates stable clock
signals.
l BITS clock source
The interfaces provided by the UCKI can directly connect with the external clock source,
such as BITS. Thus, the UCKI can obtain the 2 MHz or 2 Mbit/s clock source.
2.4.4 Clock Distribution Part

The clock distribution part includes the UCKI, UBIU, UPIU, dedicated clock cables, and H.110
bus. The clock distribution part distributes the clock signals provided by the UCKI to the UEPIs
or UPIUs in all the subracks.
The clock distribution part includes clock distribution from the UCKI to all the PSM subracks
and clock distribution inside the PSM subrack.
Clock Distribution from the UCKI to all the PSM Subracks

The steps for distributing signals from the UCKI to all the PSM subracks are as follows:
1. The UCKI sends the clock signals to the UBIU through the 8 kHz internal clock cable.
2. The UBIU sends the clock signals to the UPIU, back board of the UFCU through the H.
110 clock bus.
3. The UPIU, back board of the UFCU sends the clock signals to the UBIUs in all the subracks.
Clock Distribution Inside the PSM Subrack

Figure 2-13 shows the procedure for clock distribution inside the PSM subrack.

Figure 2-13 Procedure for clock distribution inside the PSM subrack
U U
R R
C C
U U
8 kHz clock ref. cable
8 kHz clock ref. cable
H.110 clock bus A
H.110 clock bus B
U U U U U U
B B E E E P
I I P P P I
U U I I I U
U U
P P
I I
U U
The steps for distributing clock signals inside the PSM subrack are as follows:
1. The UBIU sends the STM-1 signals to the URCU.
2. The UPIU, subboard of the URCU processes the STM-1 signals and extracts the clock
signals that are then sent to the UBIU.
NOTE
The UBIU in the switching subrack directly obtains the clock signals from the UCKI through the 8
kHz internal clock cable. Therefore, the UBIU does not need to obtain the clock signals from the
URCU.
3. After receiving the clock signals, the UBIU carries out either the following settings based
on data configuration and the DIP switches:
l Directly driving the H.110 bus in the PSM subrack
l Sending the clock signals to the UEPI through the 8 kHz internal clock cable. The H.
110 bus is driven by the UEPI.
4. The UPIU, subboard of the UEPI and UGFU, extracts the clock signals from the H.110
bus.
The H.110 bus consists of the following two groups:
l CLK_A: driven by the UBIU in slot 6 or the UEPI configured for the primary master (PM).

l CLK_B: driven by the UBIU in slot 8 or the UEPI configured for the secondary master
(SM).
For normal operation, CLK_A provides the clock. For abnormal operation, CLK_B provides
the clock.
2.4.5 Clock Control Part

The clock control part includes the URCU, UOMU, local maintenance terminal (LMT), and
serial port bus.
Through the clock control module, you can carry out data configuration, data maintenance, and
status query for the SGSN9810 clock system.
2.5 Equipment Monitoring Subsystem

The equipment monitoring subsystem consists of fan monitoring and equipment room
environment monitoring to ensure that the SGSN can work in a normal environment.
2.5.1 Fan Monitoring
Each PSM subrack is equipped with a fan box. The fan box contains six fans and a fan monitoring
module. Based on the temperature of the subrack, the fan monitoring module monitors the
running status of the fan and adjusts the rotation speed.
2.5.2 Equipment Room Environment Monitoring
The PDB monitors the environment of the equipment room. Equipment room environment
monitoring is an optional function.
2.5.1 Fan Monitoring

Each PSM subrack is equipped with a fan box. The fan box contains six fans and a fan monitoring
module. Based on the temperature of the subrack, the fan monitoring module monitors the
running status of the fan and adjusts the rotation speed.
Figure 2-14 shows the architecture of the fan monitoring module.
Figure 2-14 Fan monitoring
Fan box
W Fan Fan Fan
U
S Monitor
R
M board
C
U
U Fan Fan Fan
PSM subrack
The principles of fan monitoring are illustrated as follows:

l The fan box is equipped with a monitor board, which is used to collect the running status
of the fan box.
l The monitor board provides an RS485 serial port to connect to the UBIU, backboard of the
URCU in the service processing subrack through a RS485 serial port cable on the backplane
of the subrack.
l The URCU analyzes the information collected from the fan box and reports the results to
the UOMU. For the detected faults, the URCU sends alarms to the alarm subsystem and
alarm box through the UOMU.
l You can configure the fan box through the maintenance system.
2.5.2 Equipment Room Environment Monitoring

The PDB monitors the environment of the equipment room. Equipment room environment
monitoring is an optional function.
Figure 2-15 shows the principle of the equipment room environment monitoring.
Figure 2-15 Equipment room environment monitoring
PDB Detection Connected

interfaces to sensors
Monitor board
RS485 RS485
UBIU UBIU
URCU URCU
PSM subrack
The PDB has five Boolean value detection interfaces which are connected to the temperature
sensor, the humidity sensor, and the smoke sensor.
The reporting path of the equipment room is the same as that of the PDB power status.

System Principle 3 Principle of the Platform System
3 Principle of the Platform System
About This Chapter
management.
3.1 The location of the platform system
All the software of the SGSN boards contains the platform system.
3.2 Platform Management Subsystem
The platform management subsystem realizes operation system, hardware drive, and
communications between boards. It is the foundation on which other software modules operate.
The platform management subsystem works in all the boards.
3.3 Internal Communication Subsystem
The hardware of the SGSN consists of multiple subracks. Different subracks need exchange
information, such as signaling and data, with each other. The internal communication subsystem
realizes information exchange between the different subracks.

3 Principle of the Platform System System Principle
3.1 The location of the platform system

All the software of the SGSN boards contains the platform system.
management.
Figure 3-1 shows the location of the platform system in the SGSN.
Figure 3-1 Location of the platform system in the SGSN

No.7
signalling
BSS
node, such
as HLR
E1 E1
UICP UGTP UGBI USPU
Iu interface
Gn/Gp Gb
interface interface
subsystem subsystem
subsystem BSS
Platform Platform
BUS
UOMU URCU USIG
Internal
O Signaling O
OM communication
M subsystem M
subsystem
Platform Platform
Platform management
Service subrack

LMT
Fiber cable
UCDR UFCU UGFU

Gn/Gp
Internal interface
communication
system M M M
subsystem
IP routing
subsystem

Fiber cable or
network cable
IP node,
RNC such as
GGSN

3.2 Platform Management Subsystem

The platform management subsystem realizes operation system, hardware drive, and
communications between boards. It is the foundation on which other software modules operate.
The platform management subsystem works in all the boards.
3.2.1 The Structure of Platform Management Subsystem
The platform management subsystem consists of the following modules: Operation system
module, Data management module, Load management module, Switchover and backup
management module.
3.2.2 Load Management
Load means a process of loading software to the Flash memory of a board. The boards in the
PSM subrack can work only after the software is loaded.
3.2.3 Startup Management
Board startup means a process from board power-on till the board is in normal operation. During
this process, the board completes:
3.2.4 Switchover Management
The purpose of switchover is to enhance stability for system operation. Once a board runs
abnormally, the system can activate the backup board to replace the work done by the faulty
board in case of service interruption.
3.2.5 Patch Processing
Sometimes adaptive and corrective modifications to the host software are required during the
running of a system. For example, you need to eliminate some found defects from the system,
and add some new features. Traditionally, you halt the running of the host software to upgrade.
It affects services, however, and is not beneficial to enhance communication quality. By patching
the host software, the software can be upgraded in the in-service state, which ensures the quality
of the provided communication services.
3.2.1 The Structure of Platform Management Subsystem

The platform management subsystem consists of the following modules: Operation system
module, Data management module, Load management module, Switchover and backup
management module.
Figure 3-2 shows the modules inside the platform management subsystem.
Figure 3-2 Modules inside the platform management subsystem
Switchover and
Data Load
backup
management
Operation system

The platform management subsystem consists of the following modules:

l Operation system module: it realizes hardware drive, communications management, and
memory management
l Data management module: it realizes configuration data and user data management
l Load management module: it realizes software and patch load management
l Switchover and backup management module: it realizes board switchover and backup
control
3.2.2 Load Management

PSM subrack can work only after the software is loaded.
Overview of Load Management

Load can apply to the whole system, whole subrack, all versions, whole board, a file, or a patch.
PSM subrack can work only after the software is loaded. Load can apply to the whole system,
whole subrack, all versions, whole board, a file, or a patch.
The loaded data includes load module, product basic input output system (BIOS), host software,
and patch.
The SGSN9810 has the following two board software versions:
l Active version
It is saved in directory \hda0\sgsn\software in the hard disk of the UOMU.
l Backup version
It is saved in directory \hda0\sgsn\softback in the hard disk of the UOMU.
Principle of Load Management

Different boards have different loading channels.
Figure 3-3 shows the loading channels for each board.

Figure 3-3 Loading channels for each board
(4)
Active UOMU ULAN
(1) Switching subrack

Active URCU
Standby URCU
(2) (3) (2)
UFCU UPIU UGFU/UGPU
UCDR/
(5) Servicing subrack (8) Standby
UOMU
Active URCU
Standby URCU
(6) (7)
UGFU/UGPU UEPI/UPIU
NOTE
In Figure 3-3, the UGPU represents the UGBI, USPU, UICP, UGTP, and USIG.
The steps for loading the software for each board are as follows:
l Path 1:
For the URCU in the switching subrack: the active packet UOMU the URCU in the
switching subrack
The active URCU in the switching subrack loads the host software from the active
UOMU through an Ethernet cable.
The standby URCU in the switching subrack loads the host software from the active
UOMU through an optical fiber. If the load fails, the standby URCU in the switching
subrack loads the host software from the active UOMU through an Ethernet cable.
l Path 2:
The UGPU/UFCU/UGFU in the switching subrack: the active UOMU the URCU in the
switching subrack the UGPU/UFCU/UGFU in the switching subrack
The UGPU/UFCU/UGFU in the switching subrack loads the host software from the active
URCU through the resource Bus.
l Path 3:
The UPIU in the switching subrack: the active UOMU the URCU in the switching
subrack the UPIU in the switching subrack

The UPIU in the switching subrack loads the host software from the active URCU through
the port Bus.
l Path 4:
The ULAN: the active UOMU the ULAN
The ULAN loads the host software from the active UOMU through an Ethernet cable.
l Path 5:
The URCU in the service subrack: the active UOMU the UFCU the URCU in the
service subrack
l Path 6:
The UGPU/UGFU in the service subrack except the UOMU and UCDR: the active UOMU
the UFCU the URCU in the service subrack the UGPU/UGFU in the service
subrack
l Path 7:
The UEPI/UPIU in the service subrack : the active UOMU the UFCU the URCU in
the service subrack the UEPI/UPIU in the service subrack
The UEPI/UPIU in the service subrack loads the host software from the active URCU
through the port Bus.
l Path 8:
UCDR/standby UOMU: the active UOMU the UFCU the UCDR/standby UOMU
NOTE
l The active and standby UOMUs connect to different UFCUs.

l The back boards except the ULAN load the host software through their front boards.
l The subboard loads the host software through its front board and back board.
3.2.3 Startup Management

Board startup means a process from board power-on till the board is in normal operation. During
this process, the board completes:
l Initializing the software and hardware
l Obtaining and processing the configuration data for the board
Figure 3-4 shows the sequence of SGSN9810 board startup.

Figure 3-4 Sequence of board startup
Start sequence 1
Active UOMU
STM-1 Ethernet channel

Active URCU in the Active and standby
Start sequence 2 switching subrack Backplane bus UFCU/UGFU/UGPU in the
switching subrack
STM-1 STM-1
STM-1
Start sequence 3
Active and standby
URCU in the service Standby URCU in
Standby UOMU the switching
subrack subrack
Start sequence 4 Backplane bus

Active and standby
UGFU/UGPU in the service subrack
The steps for the board startup are as follows:
1. The active UOMU starts.

2. The active URCU in the switching subrack requests startup to the active UOMU.
3. The active and standby UFCUs/UGFUs/UGPUs in the switching subrack request startup
to the active URCU in the switching subrack.
4. The active/standby URCUs and UCDRs in the service subrack, the standby URCU in the
switching subrack, and the standby UOMU request startup to the active URCU in the
switching subrack through STM-1 multimode optical fibers.
5. The UGFU/UGPU in the service subrack requests startup to the URCU in the service
subrack through the backplane bus.
NOTE
l Hereinbefore descriptions refer to UOMU offline startup and boards startup. The other one mode is
UOMU online startup, here URCU is normal working, when the maim UOMU be reset and restarts, it
should send request to main URCU and then be restarted.
l If an error occurs during the UOMU startup caused by the configuration data in mml.txt, the UOMU
sends the error of the wrong data configuration to the FTP server. Therefore, the FTP server must be
ensured for normal operation and correct configuration during the process of startup.
l The standby UOMU, standby UCDR, URCU in the switching subrack, and the URCU in the non-
switching subrack cannot start working until the UFCU/ UPIU works normally.
3.2.4 Switchover Management


Overview of Switchover Management

Board switchover is triggered by various factors under a specified prerequisite.
The prerequisite for switchover is that a backup board exists. The boards in the SGSN have the
following two backup types:
l 1+1 backup: suitable for a majority of the boards
l N+1 backup: suitable for the UGBI board
Switchover consists of the following three types:

l Fault switchover
Triggered by faulty reset of a board
l Manual switchover
Triggered by a manual command
l Automatic manual switchover
Triggered by a hot board swap, a back board fault, and the UGBI switchover
Principle of Switchover Management

The switchover procedure contains the following four steps: switchover judgment beforehand,
earlier stage of upper-layer switchover, lower-layer switchover, and later stage of upper-layer
switchover.
Figure 3-5 shows the switchover procedure.
Figure 3-5 Switchover procedure
Switchover judgment Switchover judgment

Step 1 beforehand beforehand Step 1
Earlier stage of upper- Later stage of upper-

Step 2 layer switchover layer switchover Step 4
Step 3 Low-layer switchover Low-layer switchover Step 3
Old active board New active board
The switchover procedure contains the following four steps:

1. Switchover judgment beforehand
This step is to judge whether the switchover conditions are met and whether the switchover
can be carried out. The upper-layer modules can add the restrictions on manual switchover
in this step, such as restricting manual switchover when the data for the active and standby
boards is inconsistent.

NOTE
Only manual switchover has this step

2. Earlier stage of upper-layer switchover
This step is the earlier stage of the switchover. The upper-layer modules in the original
active board make preparations for the switchover, such as backing up the data that has not
been backed up to the standby board. After the switchover, the original active board is
resetted.
NOTE
Only manual switchover has this step.

3. Low-layer switchover
This step is to finish switchover of the operational system (OS) in the lower-layer modules,
synchronization of internal communication links, and central database (CDB) data switch.
4. Later stage of upper-layer switchover
This step is the later stage of the switchover. The upper-layer modules in the new active
board carry out some smooth work to ensure normal services, such as data consistency
check. After the switchover, the new active board can perform the services.
If the manual switchover fails in the earlier stage of upper-layer switchover, switchover recovery
is needed. If it fails in the late stage of upper-layer switchover, however, switchover recovery
is not needed.
When the earlier stage of upper-layer switchover fails, the original active board still runs
normally but the standby board is resetted. The upper-layer modules in the original active board
roll back the work carried out in this stage.
3.2.5 Patch Processing

Concept of Patch
The fundamental concepts of the software paten are described as follows: Patch, Patch area,
Patch file, Patch unit, Patch ID.
Before the patch is activated, the function call statements of the main program calls the faulty
function. After the patch is activated, however, the function call statements of the main program
are modified to the correct function in the patch area, and thus the function problem is solved.

Principle of Patch management

Software patch management includes load, activation, deactivation, confirmation, and removal
to realize state transfer for a patch.
Figure 3-6 shows the working principle of the software patch.
Figure 3-6 Working principle of the software patch
Program area Main program
Before After
activation Call function1 activation Patch area
Function1 (faulty) Function1 (correct)
Patch unit 1
Function2 (faulty) Call function2 Function2 (correct)
Function3 (faulty)
Call function3 Function3 (correct) Patch unit 2
NOTE
The function call statements of the main program are modified in the system memory after the patch
activation command is executed. For the confirmed patch, the function call statements are automatically
modified after the board resets. For the unconfirmed patch, however, the original function call statements
are used.
The fundamental concepts of the software patch are described as follows:
l Patch
A patch is a segment of executable program codes, used to replace the codes to be corrected
or updated in the host software.
l Patch area
The patch area is a dedicated area in the memory of the SGSN used to store patches.
l Patch file
A patch file is a dedicated file that contains patch information. A patch file may contain
multiple patch units. The UOMU can save multiple patch files, but only one activated patch
file can be loaded to the patch area of a board.
l Patch unit
A patch unit is added to the patch file by every time patching the host software. The new
patch file differs from the old one in an additional patch unit. A patch unit may contain
modification to multiple functions. The patch discussed in this document specially means
the patch unit. Patch management is actually management on patch units.
l Patch ID
The patch ID an identifier used to mark the patch unit in the form of character string, such
as "CUOMU001." This character string contains three parts: C/T, board type, and patch
unit ID. Letter C indicates that the patch is commercial and letter D indicates that the patch
is temporary. The patch unit ID is a digit.

A patch has four states in the host software:

l Idle state: The initial state which indicates that the memory does not contain the software
patch.
l Deactivated state: The patch is in the patch area but is not activated. The patch codes cannot
be executed.
l Activated state: The patch is activated. The patch codes can be executed. This is a pilot
state.
l Operating state: The patch is in the normal working state. It cannot be deactivated, but only
removed.
Software patch management includes load, activation, deactivation, confirmation, and removal
to realize state transfer for a patch, as shown in Figure 3-7.
Figure 3-7 Transfer of patch states

Load
Idle state Deactivated state
Remove
Remove Remove Activate Deactivate
Operating state Activated state

Confirm
3.3 Internal Communication Subsystem

The hardware of the SGSN consists of multiple subracks. Different subracks need exchange
information, such as signaling and data, with each other. The internal communication subsystem
realizes information exchange between the different subracks.
3.3.1 Structure
The internal communication subsystem consists of the exchange processing module and the
exchange controlling module.
3.3.2 The procedure for exchanging data between the subracks
The UFCU need cooperate with the URCU to exchange data between the subracks.
3.3.1 Structure
The internal communication subsystem consists of the exchange processing module and the
exchange controlling module.
Figure 3-8 shows the logical structure of the internal communication subsystem.

Figure 3-8 Logical structure of the internal communication subsystem
UPIU
Exchange
processing
Exchange
controlling
UFCU
The internal communication subsystem works in the UFCU. The subsystem consists of the
following modules:
l Exchange processing module: encapsulating and forwarding data between the subracks
l Exchange controlling module: managing and maintaining routing data between the
subracks
3.3.2 The procedure for exchanging data between the subracks

The UFCU need cooperate with the URCU to exchange data between the subracks.
Figure 3-9 shows the procedure for exchanging data between the subracks.

Figure 3-9 Procedure for exchanging data between the subracks
Data
Data Destination subrack

No./slot No.
Destination subrack
VPI/VCI
No./slot No. U U
Service R F
board C C
Bus U ATM STM-1 U
Bus
U U
Bus ATM STM-1
Service R F
board C C
Data U U
Data
Destination subrack No./
Destination subrack
slot No.
No./slot No.
VPI/VCI
The steps for exchanging data between the subracks are as follows:
1. The service board adds the destination subrack number and slot number in the message that
is then sent to the URCU through the local bus.
2. The URCU adds the VPI and VCI in the message, and disassembles the message to ATM
cells. Then the ATM cells are sent to the switching subrack through the fibers connecting
the subracks.
3. The source UFCU combines the data from the ATM cells into the destination data. Based
on the destination subrack number, the source UFCU determines the UFCU connected with
the destination subrack. Then the data is forwarded to the destination UFCU through the
local bus.
4. The destination UFCU encapsulates the message to the ATM cells and adds the VPI and
VCI for addressing. Then the UFCU sends the message to the destination URCU.
5. The destination URCU obtains the destination slot number from the payload in the ATM
cells and then sends the message containing the slot number to the destination service board
through the local bus.

System Principle 4 Principle of the Service System
4 Principle of the Service System
About This Chapter
forwards user data.
4.1 The structure of the service processing system
The UICP, UGTP, USIG, UGBI, USPU, and UGFU boards have the service system.
4.2 IP Routing Subsystem
The IP routing subsystem provides the interfaces to connect the SGSN with the external IP
networks and realizes communication with the GSN, CG, DNS server, NTP server, RNC, SS7
node supporting SS7 over IP, and PCU supporting Gb over IP.
4.3 Gb Interface Subsystem
The Gb interface subsystem realizes the functions of the FR layer, NS layer, BSSGP layer, LLC
layer, and SNDCP for the Gb interface.
4.4 Iu Interface Control Plane Subsystem
The Iu interface control plane subsystem realizes the functions of the SAAL, MTP3B, SCCP,
and RANAP layers for the Iu interface control plane.
4.5 Gn/Gp Interface Subsystem
The Gn/Gp interface subsystem realizes the following functions:GTP-C signaling
forwarding,NTP client,DNS client,GTP data packets forwarding between the Gn/Gp interface
and Iu interface or between the Gn/Gp interface and Gb interface
4.6 Signaling Subsystem
The signaling subsystem realizes the functions of MTP L1/L2/L3, or SCTP and M3UA of
SIGTRAN for SS7 in addition to SCCP, MAP, TCAP, CAP, MM, SM, SMS, CAMEL, and
BSSAP+ protocol layers.
4.7 Typical Data Processing Procedure
The procedure for handling the typical data contains signaling and data handling.

4 Principle of the Service System System Principle
4.1 The structure of the service processing system

The UICP, UGTP, USIG, UGBI, USPU, and UGFU boards have the service system.
Figure 4-1 shows the structure of the service processing system.
Figure 4-1 Structure of the service system

No.7
signalling
BSS
node, such
as HLR
E1 E1
UICP UGTP UGBI USPU
Iu interface
Gn/Gp Gb
interface interface
subsystem subsystem
subsystem BSS
Platform Platform
BUS
UOMU URCU USIG
Internal
O Signaling O
OM communication
M subsystem M
subsystem
Platform Platform
Platform management
Service subrack

LMT
Fiber cable
UCDR UFCU UGFU

Gn/Gp
Internal interface
communication
system M M M
subsystem
IP routing
subsystem

Fiber cable or
network cable
IP node,
RNC such as
GGSN

forwards user data.
The functions of the five subsystems are described as follows:
l IP routing subsystem
It provides the interface to connect the SGSN with the external IP network and realizes
communication with the GSN, CG, DNS server, NTP server, RNC, SS7 node supporting
SS7 over IP, and PCU supporting Gb over IP.
The IP routing subsystem works in the UGFU board.
l Gb interface subsystem
It realizes the functions of the physical, FR, NS, BSSGP, and LLC layers for the Gb
interface.
The Gb interface subsystem works in the UGBI board.
l Iu interface control plane subsystem
It realizes the functions of the SAAL, MTP3B, SCCP, and RANAP layers for the Iu
interface control plane.
The Iu interface control plane subsystem works in the UICP board.
l Gn/Gp interface subsystem
It processes the Gn/Gp interface protocol and forwards user data between the Gn/Gp
interface and Iu interface or between the Gn/Gp interface and Gb interface.
l Signaling subsystem
It realizes the functions of MTP L1/L2/L3, or SCTP and M3UA layers for SS7 in addition
to SCCP, MAP, TCAP, CAP, MM, SM, SMS, CAMEL, and BSSAP+ protocol layers.
The signaling subsystem works in the USPU and USIG boards. The USIG board realizes
the functions of SCTP, and M3UA layers, and other functions are realized by the USPU
board.
4.2 IP Routing Subsystem

The IP routing subsystem provides the interfaces to connect the SGSN with the external IP
networks and realizes communication with the GSN, CG, DNS server, NTP server, RNC, SS7
node supporting SS7 over IP, and PCU supporting Gb over IP.
4.2.1 The structure of IP Routing Subsystem
The IP routing subsystem consists of the IPv4/IPv6, ACL, TCP, UDP, OSPF, RIP, and routing
modules.
4.2.2 Principle of IP routing subsystem.
Routing IP packets is a process in which the SGSN receives the IP packets and then distributes
them to different modules for processing.
4.2.1 The structure of IP Routing Subsystem

The IP routing subsystem consists of the IPv4/IPv6, ACL, TCP, UDP, OSPF, RIP, and routing
modules.

Figure 4-2 shows the modules inside the IP routing subsystem.
Figure 4-2 Modules inside the IP routing subsystem
Gn/Gp interface subsystem
Routing module
RIP
UDP TCP OSPF

A
C
L
IPv4 IPv6
IP routing subsystem
OM system
Platform system
UGFU
The modules inside the IP routing subsystem are described as follows:
l IPv4/IPv6
The IPv4 module realizes the functions of the Ipv4 protocol.
The IPv6 module realizes the functions of the Ipv6 protocol that is supported by the Gn/
Gp interface, Iu interface, Gb interface, and SS7 interface.
The physical interfaces of the IP network are realized by the UPIU, back board of the
UGFU. The types of the physical interfaces are the GE (fiber interface or network interface),
FE, STM-1 ATM, and STM-4 ATM interfaces.
l ACL
The access control list (ACL) module filters the IP packets based on the ACL defined by
a user to ensure that only the legal data packets can access the SGSN, and therefore prevents
the SGSN from illegal attacks.
l TCP
The TCP module realizes the functions of the TCP protocol that provides reliable data
communication for the application layer. The TCP module partitions the data received from
the application into suitable blocks and sends these blocks to the network layer. It also
confirms the received packets and sets the time-out clock for the last confirmed packets.

NOTE
The SGSN does not use the TCP protocol of the UGFU.
l UDP
The UDP module realizes the functions of the UDP protocol that provides simple services
for the application layer. The UDP module sends only the packets called datagram from
one host to another, but it does not ensure that the datagram can reach the other end. The
application layer guarantees reliability.
l OSPF
The OSPF module realizes the functions of the Open Shortest Path First (OSPF) protocol.
The OSPF protocol is a widely-used Interior Gateway Protocol (IGP) based on link status
developed by the IETF organization.
l RIP
The RIP module realizes the functions of the Routing Information Protocol (RIP). The RIP
is a simple IGP mainly used in small-scale networks.
NOTE
The SGSN9810 supports only the RIP and OSPF based on the IPv4 protocol.
l Routing module
The routing module maintains the routing table and routes IP packets.
All the routing information of the SGSN is saved in the UGFU routing table. Each UGFU
maintains its own routing table. The routing table contains the following information:
Routes to the internal board, such as the UGTP
Routes between the UGFUs
Routes to the external devices
Routes to the destination IP nodes
4.2.2 Principle of IP routing subsystem.

Routing IP packets is a process in which the SGSN receives the IP packets and then distributes
them to different modules for processing.
Figure 4-3 shows the procedure for processing IP packets in the IP routing subsystem.

Figure 4-3 Procedure for processing IP packets in the IP routing subsystem
UGBI
Gb interface
data packets
Gn/Gp interface
subsystem
RIP
User plane
data RIP routing User plane U
information IP packets G
F
U
OSPF UDP TCP
OSPF routing TCP M3UA U

UDP
information packets signaling S
packets
I
G
ACL Routing
Ga interface U
IP packets not
IPv4 signaling C
processed by the
packets UGFU D
R
IPv4/IPv6
Gn/Gp interface U
UGFU Data frame signaling G
T
P
UPIU
IP packets
Router
The steps for processing IP packets in the IP routing subsystem are as follows:

NOTE
The above figure describes only the processing procedure when the SGSN receives IP packets. The
processing procedure when the SGSN sends IP packets is opposite to the procedure when the SGSN receives
IP packets.
1. After receiving the IP packets from the external router, the UPIU board processes the physical layer
and link layer and sends the data frames to the UGFU, front board of the UPIU through internal data
cables.
2. After the data frames enter the UGFU, they first enter the IPv4/IPv6 module. Then the IPv4/IPv6
module carries out the following processing:
l If the ACL function is configured, the ACL module filters the IPv4 packets and then discards the
illegal packets.
l If the destination address of the IP packets is not to the UGFU, the IP packets are sent to the routing
module for forwarding to the specified UGTP, USIG, another UGFU, or UCDR.
l The UGFU decapsulates the IP packets after processing. Based on the protocol types of the packets,
the UGFU distributes the packets to the upper-layer modules, such as the OSPF, TCP, or UDP.
3. The IP upper-layer module processes the data packets in the following ways:
l Processed by the UDP module
After receiving the UDP data packets, the UDP module decapsulates the packets and sends the data
packets to the upper layers based on the port numbers. For the GTP packets, the UDP module sends
them to the Gn/Gp interface subsystem for processing. For the Gb interface data, the UDP module
sends them to the UGBI board for processing. For the RIP data, the UDP module sends them to
the RIP module for processing.
l Processed by the OSPF module
After receiving the routing information, the OSPF module updates the routing table.
4.3 Gb Interface Subsystem

The Gb interface subsystem realizes the functions of the FR layer, NS layer, BSSGP layer, LLC
layer, and SNDCP for the Gb interface.
4.3.1 The structure of Gb Interface Subsystem
The Gb interface subsystem works in the UGBI board. When the Gb interface uses IP bearer,
the UGFU realizes the IP protocol.
4.3.2 The procedure for processing Gb packets in the Gb interface subsystem
Handling Gb-interface messages is a process in which the SGSN receives Gb-interface messages
and then distributes them to the related modules for processing.
4.3.1 The structure of Gb Interface Subsystem

The Gb interface subsystem works in the UGBI board. When the Gb interface uses IP bearer,
the UGFU realizes the IP protocol.
Figure 4-4 shows the modules inside the Gb interface subsystem.

Figure 4-4 Modules inside the Gb interface subsystem
SNDCP
LLC Encryption/
Decryption
UEPC
BSSGP
UDP NS FR
UEPI
IPv4 IPv6
UGBI UFEU
IP FR
The modules inside the Gb interface subsystem work in the UGBI and its suboards, UEPC and
UFEU. The Gb interface subsystem has the following modules:
l SNDCP
The SNDCP module realizes the following functions of the SNDCP protocol:
Providing the upper-layer protocols, IP or PPP with multiple routes to transmit data for
PDP contexts identified by NSAPI
Realizing protocol compression and data compression
Realizing fragmentation and reorganization for data packets
l LLC
The LLC module realizes the following functions of the LLC protocol:
Providing the upper-layer protocols, SMS, SNDCP, and GMM with logical link
connection in acknowledged and unacknowledged modes
Transmitting signaling and data between the SGSN and MS
Encrypting with the UEPC
l BSSGP
The BSSGP module realizes the functions of the BSSGP protocol. The BSSGP module
consists of the PTP module and the SIG module. The PTP module has the following
functions:
Transmitting cell data, providing the upper-layer protocols with the data transmission
channel in the acknowledged mode, and controlling downlink traffic

Reporting the GMM the MS radio status message received from the BSS. The GMM
informs the PTP module if the radio access capability changes
The SIG module performs BVC management and paging function.
l NS
The NS module realizes the functions of the NS control sublayers including NSVC
management and transmission of uplink and downlink data.
l Encryption/Decryption
The encryption/decryption module is in the UEPC, subboard of the UGBI. The module
encrypts and decrypts the data in the LLC layer.
NOTE
The UEPC is an optional board.

l FR
The FR module processes the FR protocol. It is in the UFEU, subboard of the UGBI.
The UFEU processes the FR data frames and transmits the data to the PCU through the
PVC.
4.3.2 The procedure for processing Gb packets in the Gb interface

subsystem
Handling Gb-interface messages is a process in which the SGSN receives Gb-interface messages
and then distributes them to the related modules for processing.
Figure 4-5 shows the procedure for processing Gb packets in the Gb interface subsystem.

Figure 4-5 Procedure for processing Gb packets in the Gb interface subsystem.
UGFU USPU
User plane L3
data packets signaling
UGBI
SNDCP
SNDCP data
packets
LLC
LLC data
LLC data packets Encryption/
packets Decryption
BSSGP UEPC
BSSGP data
packets
NS
NS data
packets
UDP
FR
IP
UGFU UFEU
IP packets FR frame
UPIU UEPI
IP packets FR frame
BSS
The steps for processing Gb packets in the Gb interface subsystem are as follows:
NOTE
The above figure describes only the processing procedure when the SGSN receives Gb packets. The
processing procedure when the SGSN sends Gb packets is opposite to the procedure when the SGSN
receives Gb packets.

1. The data from the BSS to the SGSN can enter the UGBI board in the following two ways:
l Gb interface carried by FR
After the data enters the UFEU through the UEPI, the FR module encapsulates the data
frame and forwards it to the NS module in the UGBI.
l Gb interface carried by IP
After the data enters the UGFU through the UPIU, the UGFU processes the IP layer
and UDP layer for the IP packets. Based on the destination port number and destination
IP address, the UGFU forwards the data to the NS module in the UGBI through the
internal communication system.
2. The NS module decapsulates the received data packets and processes the signaling pertinent
to the module, such as NSVC link management signaling. For the upper-layer data, the NS
module sends it to the BSSGP module for processing.
3. The BSSGP module decapsulates the received data packets and processes the signaling
pertinent to the module, such as cell management signaling. For the upper-layer data, the
BSSGP module sends it to the LLC module for processing.
4. The LLC module decapsulates the received data packets and processes them based on their
data types:
l The LLC module processes its relevant signaling, such as LLC link management
signaling.
l For the data to be sent to the SNDCP module, the UFEC board decapsulates the data
before the LLC module sends it to the SNDCP module.
l For L3 signaling, the LLC module directly sends it to the USPU board for processing.
5. The SNDCP module decapsulates the received data packets. If the TCP/IP header is
compressed, the module decompresses the header. If the user data is compressed, the data
is sent to the UEPC for decompression before it is forwarded to the UGFU for processing.
4.4 Iu Interface Control Plane Subsystem

The Iu interface control plane subsystem realizes the functions of the SAAL, MTP3B, SCCP,
and RANAP layers for the Iu interface control plane.
The Iu interface control plane subsystem works in the UICP board. When the Iu interface uses
IP bearer, the functions of the SCCP layer below are realized in the USIG and UGFU.
NOTE
The Iu interface user plane transfers data according to the GTP protocol. The Gn/Gp interface subsystem
realizes the basic functions for the Iu interface user plane.
4.4.1 The structure of Iu Interface Control Plane Subsystem

4.4.2 The procedure for signaling processing in the Iu interface signaling subsystem
Handling Iu-interface signaling is a process in which the SGSN receives and sends the Iu-
interface signaling packets.
4.4.1 The structure of Iu Interface Control Plane Subsystem


Figure 4-6 shows the modules inside the Iu interface control plane subsystem.
Figure 4-6 Modules inside the Iu interface control plane interface subsystem
USPU
RANAP
SCCP
M3UA MTP3B
SCTP SSCF
IPv4 IPv6 SSCOP
USIG UICP
UGFU UGFU
IP ATM
The Iu interface control plane subsystem consists of the following modules:
l RANAP
The RANAP establishes, releases, and modifies the radio access bearer. The RANAP
module realizes the following functions of RANAP:
Transferring the serving RNC and changing the SRNC function and relevant resources
RAB management, including the establishment, modification, and release of RAB
Releasing Iu resources
Transferring SRNS contexts
Iu interface overload control
Iu interface reset
Sending the UE Common ID message to the RNC
Paging users
Transferring NAS information
Controlling the UTRAN security mode

Controlling the report on location information

Reporting common faults
l SCCP
Through the SS7 network, the SCCP module establishes the connectionless and connection-
oriented network services between the signaling points and transmits the circuit-based and
noncircuit-based signaling in addition to information of other types. The SCCP module can
establish logical connection in the SS7 network, and thus provide end-to-end signaling
transfer between the signaling points.
The SCCP module realizes the following functions of SCCP:
Establishing temporary and permanent logical connection, including routing and IP
address switch.
Providing four-class services: class 0connectionless, class 1connectionless with order
guaranteed, class 2connection-oriented, and class 3connection-oriented based on
traffic control. The RANAP supports only class2 and class 0 services.
Segmentation and reassembly functions.
Connection release.
SCCP management, such as managing the SCCP module state, informing other nodes
of the module state change, and modifying the changed data.
l MTP3B
The MTP3B module enhances B-ISDN support function based on MTP-3 of the SS7
network.
The MTP3B module realizes the following functions of MTP3B:
Processing signaling messages, which contains message identification, allocation, and
routing.
A message is reported to the MTP3B from the SSCF layer through the primitive
interface. Message identification function judges whether the destination point code
(DPC) of the message is consistent with the signaling point code of the SGSN. If the
two are same, the SGSN carries out allocation function to send the message to the user
by judging the service indicator (SI) in the service information octet (SIO). If the two
are not same, the SGSN carries out signaling routing function.
If the signaling message is sent from the SCCP layer to the MTP-3B, the signaling
routing function is directly carried out.
Signaling network management function is used to control the constitution of the
signaling network, reassemble the network when it is faulty, and thus ensuring that
signaling messages can be correctly sent.
Signaling network management consists of signaling service management, signaling
link management, and signaling route management.
The signaling service management is used to transfer the signaling service from one
signaling link or route to another signaling link(s) or route(s) or reduce the signaling
service in the case of the signaling network congested.
The signaling route management is used to transmit the information about the signaling
network state to block and unblock the signaling routes.
The signaling link management is used to control the locally connected signaling links,
recover the faulty signaling links, idle connection, and links that are not located, as well
as disconnect the located links.
l SSCF

The SSCF (Q.2140) is used to switch the primitive, namely mapping between the signaling
entities, MTP-3B of the SS7 and SSCOP at the network node interface (NNI). This ensures
that the SSCOP of SAAL-UNI is the same as that of SAAL-NNI. The interface for the
MTP-3B is mapped into the SSCOP primitive interface through the SSCF.
The SSCF (Q.2140) realizes the following functions:
Mapping of the primitive. The SSCF maps the SAAL user primitive into the SSCOP
primitive.
Retrieving local data, which supports switch of MTP-3B links.
Traffic control. When the low-level links are congested, the SSCF informs the
information to the high-level links.
Changing the link states and reporting the information to the upper-layer management
entities.
l SSCOP
The SSCOP (Q.2110), main protocol of the SAAL, carries out adaptation to the ATM
signaling protocol. It provides the upper layers with reliable and orderly data transfer and
traffic control by establishing and maintaining the ATM signaling channel.
The SSCOP module realizes the following functions of SSCOP:
Guaranteeing continuity of the order when transferring SSCOP-SDUs.
Rectifying retransmission.
Controlling traffic through the sliding window mechanism. The receiving station can
control the data transfer rate of the sending station.
Reporting the errors to the upper-layer management entities.
Keeping the links.
Retrieving local data. The local SSCOP users can retrieve the SDUs that are not released
by the SSCOP entities in order.
Connection control. Establishing, releasing, and re-synchronizing the SSCOP
connection.
Transmitting acknowledged and unacknowledged user data.
Rectifying and recovering the protocol errors.
Allowing the peer entities to change state information.
4.4.2 The procedure for signaling processing in the Iu interface

signaling subsystem
Handling Iu-interface signaling is a process in which the SGSN receives and sends the Iu-
interface signaling packets.
Figure 4-7 shows the procedure for signaling processing in the Iu interface signaling subsystem.

Figure 4-7 Procedure for signaling processing in the Iu interface signaling subsystem
USPU
L3 signaling
RANAP
RANAP
signaling SCCP
signaling
SCCP
SCCP
signaling
MTP3B M3UA
MTP3B M3UA
signaling signaling
SCTP
SSCF
SSCOP SCTP
packets
UICP
IP
SAAL data
packets USIG
IP packets
ATM switch Routing

UGFU UGFU
ATM cells
IP packets
UPIU UPIU
ATM cells IP packets
RNC RNC
The steps for processing signaling in the Iu interface subsystem are as follows:
NOTE
The above figure describes only the processing procedure when the SGSN receives Iu packets. The
processing procedure when the SGSN sends Iu packets is opposite to the procedure when the SGSN receives
Iu packets.
1. Step 1 The signaling from the RNC to the SGSN can enter the UICP board in the following
two ways:
l Iu interface carried by ATM

The signaling enters the UICP board after it is forwarded by the UGFU board through
the ATM.
l Iu interface carried by IP
The signaling enters the USIG board after it is forwarded by the UGFU board through
the IP. The USIG board sends the SCCP message to the SCCP layer of the UICP board
for processing after handling the IP, SCTP, and M3UA layers.
2. After receiving the Iu interface signaling message from the UGFU, the UICP send it to the
SSCOP and SSCF for combination and adaptation, and then to the MTP3B module.
3. After receiving the signaling message, the MTP3B module processes the message based
on the message type. For the message pertinent to the module, such as the MTP3B link
management message, the MTP3B module processes the message itself. For the SCCP
message, the MTP3B module sends it to the SCCP module for processing.
4. After receiving the signaling message from the USIG or MTP3B module, the SCCP module
processes the message based on the SSN. For the message pertinent to the module, such as
the SCCP state management message, the SCCP module processes the message itself. For
the RANAP message, the SCCP module sends it to the RANAP module for processing.
5. After processing the RANAP signaling, the RANAP module processes the message based
on the message type. For the message pertinent to the module, such as the RAB assignment
message, the RANAP module processes the message itself. For the SM, MM, and SMS
messages, the RANAP module sends them to the USPU board for processing.
4.5 Gn/Gp Interface Subsystem

The Gn/Gp interface subsystem realizes the following functions:GTP-C signaling
forwarding,NTP client,DNS client,GTP data packets forwarding between the Gn/Gp interface
and Iu interface or between the Gn/Gp interface and Gb interface
4.5.1 The structure of Gn/Gp Interface Subsystem
4.5.2 The procedure for User Data forwarding
Forwarding user data is a process in which the SGSN receives the user-plane data and then
forwards the data to the related interfaces.
4.5.3 Procedure for Processing Gn/Gp Signaling Data
Handling Gn/Gp signaling is a process in which the SGSN receives the Gn/Gp signaling and
then distributes the signaling to the related modules for processing.
4.5.4 Procedure for DNS Resolution
DNS resolution refers to the processing procedure performed in the internal modules after the
SGSN initiates the domain name resolution.
4.5.5 Procedure for NTP Synchronization
NTP synchronization refers to the processing procedure performed in the internal modules after
the SGSN initiates the NTP synchronization.
4.5.1 The structure of Gn/Gp Interface Subsystem

Figure 4-8 shows the modules inside the Gn/Gp interface subsystem.

Figure 4-8 Modules inside the Gn/Gp interface subsystem

USPU
G
D N GTPU
T
N T contexts Data forwarding
P
S P management
C
UDP
IPv4 IPv6 ATM
IP routing
forwarding
UGTP UGFU
IP ATM
NOTE
The UGTP board can realize the functions of three types, namely GTP-C, GTP-U, and both of them. The
configuration data for the UGTP board determines which type of function can be realized.
The Gn/Gp interface subsystem consists of the following modules:

l GTP-C
When the UGTP receives the GTP-C messages, the GTP-C module distributes the GTP-C
messages according to the following rules:
If the flow identity for the GTP header in the GTP-C V0 version or TEID in the GTP-
C V1 version is invalid, the UGTP directly sends the message to the USPU assigned by
the SGSN.
If the flow identity or TEID is valid, the UGTP sends the message to the USPU that
corresponding to the flow identity or TEID.
l DNS
The DNS module realizes the DNS agent function.
The UGTP receives the domain name resolution request from the USPU, and interworks
with the DNS server to return the resolution result to the USPU.
Domain name resolution is used to resolve the GGSN IP address based on the APN when
the PDP context is activated, resolve the peer SGSN IP address based on the RAI during
inter-RAU, and resolve the peer SGSN IP address based on the RNC ID during relocation.
Domain name resolution can appeal to the following three means:
Using the DNS server
Using the DNS cache
Using the hostfile
The DNS is a server specially used for domain name resolution in the network. Saved in
the local SGSN, the hostfile contains fewer records than the DNS. The DNS cache, located

in the UGTP, is the cache for the domain names and IP addresses resolved by the DNS.
The cache is used to quickly resolve the domain names, and thus reducing the time for
visiting the DNS. The records saved in the cache has a lifecycle, so when the lifecycle
expires, the records become invalid.
The SGSN carries out domain name resolution in the following steps:
1. Look up the host information in the hostfile of the UGTP
2. Look up the host information in the DNS cache of the UGTP if no record is found in
step 1
3. Send the domain name resolution requirement to the DNS server if no record is found
in step 1 and step 2
l NTP
The NTP module realizes the NTP client function.
The UGTP has the NTP client function and it can interwork with the NTP server to
synchronize the local time for the SGSN. The SGSN9810 supports the third version of the
NTP protocol.
The SGSN can connect with the NTP server in the following two ways:
Through the service network, namely the port on the UGFU.
Through the maintenance network, namely the port on the UOMU.
l GTPU context management
The GTPU context management module realizes the GTPU context management function.
Every time an MS activates the PDP contexts, the GTPU contexts are generated. These
contexts contain the information about data transfer and forwarding, which are used by the
UGTP for processing the data.
l Data transfer
The data transfer module realizes forwarding data packets between the Gn/Gp interface
and Iu interface or between the Gn/Gp interface and Gb interface. This function is the most
important in the Gn/Gp subsystem.
4.5.2 The procedure for User Data forwarding

Forwarding user data is a process in which the SGSN receives the user-plane data and then
forwards the data to the related interfaces.
Figure 4-9 shows the procedure for forwarding user data.

Figure 4-9 Procedure for forwarding user data

UGBI
2.5G data
Data forwarding
ATM
IP routing
forwarding
UGFU
SAR
MAC ATM
UPIU UPIU
IP ATM
3G
data
GGSN RNC
The steps for forwarding user data are as follows:
NOTE
The above figure describes only the processing procedure when the SGSN receives GGSN packets. The
processing procedure when the SGSN sends RNC or BSS packets is opposite to the procedure when the
SGSN receives GGSN packets.
1. After receiving the data packets from the GGSN, the SGSN sends them to the IP routing
module in the UGFU board to process the IP layer and UDP layer of the packets
2. The IP routing module sends the processed GTP packets to the data transfer module.
For the 2.5G data packets, the data transfer module re-encapsulates them into the internal
packets before sending the packets to the UGBI for processing.
For the 3G data packets, the data transfer module re-encapsulates the payload in the GTP
packets and then sends the new GTP packets to the RNC through the ATM forwarding
module or IP routing module.

4.5.3 Procedure for Processing Gn/Gp Signaling Data

Handling Gn/Gp signaling is a process in which the SGSN receives the Gn/Gp signaling and
then distributes the signaling to the related modules for processing.
Figure 4-10 shows the procedure for processing the Gn/Gp signaling data.
Figure 4-10 Procedure for processing the Gn/Gp signaling data
USPU
GTPC
signaling
GTPC
UGTP
IP packets
IP route
UGFU
IP packets
MAC
UPIU
IP packets
IP
GGSN
The steps for processing the Gn/Gp signaling data are as follows:
NOTE
The above figure describes only the processing procedure when the SGSN receives GGSN packets. The
processing procedure when the SGSN sends GGSN packets is opposite to the procedure when the SGSN
receives GGSN packets.
1. After receiving the signaling data from the GGSN, the SGSN sends it to the IP routing
module in the UGFU board. Based on the destination IP address, namely the IP address of
the UGTP, the IP routing module forwards the data to the UGTP.
2. After processing the IP layer and UDP layer of the signaling, the UGTP sends the GTPC
message to the GTPC module.

3. The GTPC module decapsulates the GTPC message and sends it to the USPU in the internal
message form.
4.5.4 Procedure for DNS Resolution

DNS resolution refers to the processing procedure performed in the internal modules after the
SGSN initiates the domain name resolution.
Figure 4-11 shows the procedure for DNS resolution.
Figure 4-11 Procedure for DNS resolution
USPU
DNS DNS
request response
DNS
UGTP
IP packets
IP routing
UGFU
IP packets
MAC
UPIU
IP packets
IP
DNS Server
The steps for DNS resolution are as follows:
1. After receiving the DNS resolution request from the USPU, the DNS module in the UGTP
looks up the resolution record in the local hostfile and DNS cache in the UGTP. If the record
is found, the DNS module returns the resolution result to the USPU. If the record is not
found, the DNS module sends the DNS resolution request to the DNS server.
2. The IP routing module in the UGFU sends the DNS resolution request to the DNS server
through a proper port on the UPIU.

3. The DNS server sends the resolution result to the SGSN. After the UPIU and UGFU boards
process the resolution result, it is sent to the UGTP that initiates the resolution request, and
then to the USPU board.
4.5.5 Procedure for NTP Synchronization

NTP synchronization refers to the processing procedure performed in the internal modules after
the SGSN initiates the NTP synchronization.
Figure 4-12 shows the procedure for NTP synchronization.
Figure 4-12 Procedure for NTP synchronization
Other Other
boards Internal time boards
synchronization
message
Active URCU in the switching

subrack
Internal time
synchronization message
NTP
UGTP
IP packets IP packets
IP routing IP routing
UGFU UOMU
MAC MAC
UPIU UFSU
IP IP
NTP Server NTP Server
The steps for NTP synchronization are as follows:
1. The NTP module in the UGTP board sends the synchronization request to the NTP server.

2. The synchronization request can be sent to the NTP server through the UGFU and its back
board, the UPIU, or the UOMU and its back board, the UFSU.
3. The NTP server returns the synchronization result to the NTP module through the UPIU
and its front board, the UGFU, or the UFSU and its front board, the UOMU.
4. The NTP module processes the synchronization result and then sends the result to the active
URCU in the switching subrack through the internal message. The active URCU completes
time synchronization for the whole SGSN system.
NOTE
The NTP module regularly sends the synchronization request to the NTP server.
4.6 Signaling Subsystem

The signaling subsystem realizes the functions of MTP L1/L2/L3, or SCTP and M3UA of
SIGTRAN for SS7 in addition to SCCP, MAP, TCAP, CAP, MM, SM, SMS, CAMEL, and
BSSAP+ protocol layers.
4.6.1 The structure of Signaling Subsystem
The signaling subsystem works in the USPU and USIG boards. The USIG board realizes the
functions of SCTP and M3UA layers, while other functions are realized by the USPU board.
4.6.2 Procedure for L3 Signaling
Handling L3 signaling is a process in which the internal modules handle the L3 signaling after
the SGSN receives the signaling from an MS.
4.6.1 The structure of Signaling Subsystem

The signaling subsystem works in the USPU and USIG boards. The USIG board realizes the
functions of SCTP and M3UA layers, while other functions are realized by the USPU board.
Figure 4-13 shows the modules inside the signaling subsystem.

Figure 4-13 Modules inside the signaling subsystem
UGBI/UGTP/UICP
MM/SM/SMS/LCS
MAP
CAP TCAP BSSAP+
SCCP M3UA
MTP3 SCTP
USPU
IP
MTP2
USIG
USS7
Routing
UGFU
UEPI UPIU
No.7 signalling
point, such as
HLR
The signaling subsystem consists of the following modules:
l MM
The MM module realizes 2.5G and 3G mobility management, establishes contexts for
subscribers, and carries out attach, detach, location update, and intersystem change.
l SM

The SM module carries out session management for subscribers by establishing, releasing,
and modifying PDP contexts. During this process, the module establishes and releases
connection between the MS and SGSN.
l SMS
The SMS module realizes short message mobile originated (SM-MO), short message
mobile terminated (SM-MT), and short message alert (SMAlert) functions. It generates a
fault report in the case of abnormity in short messages.
l LCS
Location services (LCS) provide user location information in a standard format for
operators, common service suppliers, and value added service suppliers. The SGSN carries
out user authentication and location request management.
l MAP
The SGSN communicates with the entities in the GSM network through the MAP signaling
protocol.
Gr interface
The Gr interface is an interface used to exchange information about MS location and
user management between the SGSN and HLR.
The SGSN provides the HLR with MS location. The HLR sends the mobile subscribers'
information required for services to the SGSN.
Gd interface
The Gd interface is an interface used to exchange SM information between the SGSN
and SMS-GMSC or between the SGSN and SMS-IWMSC.
Gf interface
The Gf interface is an interface used to check international mobile station equipment
identity (IMEI) for subscribers between the SGSN and EIR.
Lg interface
The Lg interface is an interface between the SGSN and GMLC. The GMLC sends the
UE location query request and receives the UE location response through this interface.
Through cooperation with GTP, the SGSN also supports GTP-MAP. The GTP-MAP is
used in the case when the GGSN need originating PDP contexts but the GGSN itself
does not has the No.7 MAP interface. In such a case, the GGSN sends a request to the
SGSN that can support GTP-MAP switch. The SGSN then sends the information from
the HLR to the GGSN through the GTP message.
l TCAP
Transaction capabilities refer to a series of communication capabilities that provide an
interface between applications and a network layer service.
The TCAP defines a public function and is independent of specific applications.
l BSSAP+ signaling
The BSSAP+ signaling cooperates with the GMM/PMM to exchange the Gs interface
information between the SGSN and MSC/VLR.
l CAP
The CAP signaling realizes interworking between the SGSN and CAMEL gsmSCF through
the Ge interface. The SGSN informs the gprsSSF of the monitored user events, such as
attach, PDP context activation, and SMS so that the gprsSSF can control the user's actions.
l MTP3 and MTP2

The MTP3 and MTP2 realize functions of the MTP layer for SS7. The USS7, subboard of
the USPU realizes the MTP2. The USPU board realizes the MTP3.
l M3UA and SCTP
The M3UA and SCTP realize the IP bearer for SS7 on the USIG board.
4.6.2 Procedure for L3 Signaling

Handling L3 signaling is a process in which the internal modules handle the L3 signaling after
the SGSN receives the signaling from an MS.
Figure 4-14 shows the procedure for signaling processing.

Figure 4-14 Procedure for signaling processing

UGBI UGTP UICP
Gb interface Gn/Gp interface Iu interface
signaling signaling signaling
MM/SM/SMS/LCS
L3 signaling
MAP
Map signalling
CAP TCAP BSSAP+
TCAP
CAP signalling BSSAP+
signaling signaling
SCCP
SCCP
signaling
MTP3 M3UA
M3UA
USPU signaling
MTP3 signaling
SCTP
SCTP
MTP2
signaling
USS7
IP
No.7 signaling
USIG
IP packets
Routing
UGFU
IP packets
UEPI UPIU
No.7 signaling IP packets
HLR and other

devices
The steps for processing signaling are as follows:
NOTE
The above figure shows the Gb or Iu interface signaling exchanged with the HLR.

1. The signaling from the Gb or Iu interface is sent to the SM, MM, LCS, or SMS module in
the USPU for processing.
2. Through the internal message, the SM, MM, LCS, or SMS module informs the MAP
module of encapsulating the signaling or sending the signaling to the Gn/Gp interface
subsystem in the UGTP for processing.
3. After encapsulating the upper-layer signaling, the MAP module sends it to the TCAP layer.
4. After encapsulating the MAP signaling, the TCAP module sends it to the SCCP layer.
5. After encapsulating the TCAP message to the SCCP message, the SCCP layer sends the
SCCP message to the MTP or M3UA module for processing.
6. The MTP module adds the MTP header for the SCCP message and chooses a proper link
to send the message to the HLR or other SS7 nodes. The M3UA module adds the M3UA
header for the SCCP message and chooses a proper SCTP link. After encapsulating the
signaling to the IP packets, the M3UA module sends them to the SS7 nodes supporting the
IP through the UGFU.
4.7 Typical Data Processing Procedure

The procedure for handling the typical data contains signaling and data handling.
4.7.1 2.5G signaling data flow
Handling 2.5G signaling data flows is a process in which the internal modules handle the 2.5G
signaling data after the SGSN receives the data from the Gb interface.
4.7.2 3G signaling data flow
Handling 3G signaling data flows is a process in which the internal modules handle the 3G
signaling data after the SGSN receives the data from the Iu interface.
4.7.3 2.5G service data flow
Handling 2.5G service data flows is a process in which the internal modules handle the 2.5G
service data after the SGSN receives the data from the Gb interface.
4.7.4 3G service data flow
Handling 3G service data flows is a process in which the internal modules handle the 3G service
data after the SGSN receives the data from the Iu interface.
4.7.1 2.5G signaling data flow

Handling 2.5G signaling data flows is a process in which the internal modules handle the 2.5G
signaling data after the SGSN receives the data from the Gb interface.
The 2.5G uplink signaling data flow enters the SGSN from the BSS. The SGSN processes the
signaling and exchanges it with the HLR or GGSN upon requirement.
The 2.5G downlink signaling data flow enters the SGSN from the HLR or GGSN. The SGSN
processes the signaling and exchanges it with the BSS upon requirement.
The following illustrates the processing procedure for 2.5G uplink signaling data flow, as shown
in Figure 4-15.

Figure 4-15 Processing procedure for 2.5G uplink signaling data flow
U
U U U U U U U
G
P G F P B R E
BSS B BSS
I F C I I C P
I
U U U U U U I
U U U HLR
S S E and
I P P other
G U I devices
U U U U U U
P G F P B R
GGSNSG
I F C I I C
U U U U U U U
G
T
P
The steps for processing the 2.5G uplink signaling data flow are as follows:
1. The signaling from the BSS to the SGSN can enter the UGBI board in the following two
ways:
The signaling directly enters the UGBI through the UEPI.
The signaling enters the UGFU through the UPIU. Then the UGFU forwards the
signaling to the UGBI through the internal communication system.
2. After receiving the signaling from the BSS, the UGBI sends it to the protocol layers for
processing. For the signaling between the MS and SGSN, the UGBI forwards it to the USPU
for processing.
3. The USPU processes the signaling based on their types:
l Signaling related to the MM or SMS modules
This type of signaling should be exchanged with the SS7 nodes, such as the HLR or
SMC. In this case, the USPU processes the signaling based on the bearer types of SS7.
TDM bearer
The USPU exchanges the signaling with the SS7 nodes through the UEPI.
IP bearer
The USPU exchanges the signaling with the SS7 nodes through the USIG and
UGFU.
l Signaling related to the PDP contexts
This type of signaling should be exchanged with the GGSN. In this case, the USPU first
sends the signaling to the UGTP, and then the UGTP exchanges the signaling with the
GGSN through the IP interface provided by the UGFU.

4.7.2 3G signaling data flow

Handling 3G signaling data flows is a process in which the internal modules handle the 3G
signaling data after the SGSN receives the data from the Iu interface.
The 3G uplink signaling data flow enters the SGSN from the RNC. The SGSN processes the
signaling and exchanges it with the HLR or GGSN upon requirement.
The 3G downlink signaling data flow enters the SGSN from the HLR or GGSN. The SGSN
processes the signaling and exchanges it with the RNC upon requirement.
The following illustrates the processing procedure for 3G uplink signaling data flow, as shown
in Figure 4-16.
Figure 4-16 Processing procedure for 3G uplink signaling data flow
U
S U
I I
G C
U U U U U U P
P G F P B R
RNC I F C I I C
U U U U U U
U U U HLR
S S E and
I P P other
G U I devices
U U U U U U
GGSN,SG,
P G F P B R
and other
I F C I I C
devices U
U U U U U U
G
T
P
The steps for processing the 3G uplink signaling data flow are as follows:
1. The signaling from the RNC to the SGSN can enter the UICP board in the following two
ways:
l Iu interface carried by ATM
The signaling directly enters the UICP after it is forwarded by the ATM module in the
UGFU.
l Iu interface carried by IP
The signaling enters the USIG after it is forwarded by the IP module in the UGFU.
Then the USIG sends the SCCP message to the UICP for processing.
2. After receiving the signaling from the RNC, the UICP sends it to the protocol layers for
processing. For the signaling between the MS and SGSN, the UICP forwards it to the USPU
for processing.
3. The USPU processes the signaling based on their types:
l Signaling related to the MM or SMS modules

This type of signaling should be exchanged with the SS7 nodes, such as the HLR or
SMC. In this case, the USPU processes the signaling based on the bearer types of SS7.
TDM bearer
The USPU exchanges the signaling with the SS7 nodes through the UEPI.
IP bearer
The USPU exchanges the signaling with the SS7 nodes through the USIG and
UGFU.
l Signaling related to the PDP contexts
This type of signaling should be exchanged with the GGSN. In this case, the USPU first
sends the signaling to the UGTP, and then the UGTP exchanges the signaling with the
GGSN through the IP interface provided by the UGFU.
4.7.3 2.5G service data flow

Handling 2.5G service data flows is a process in which the internal modules handle the 2.5G
service data after the SGSN receives the data from the Gb interface.
The 2.5G uplink service data flow enters the SGSN from the Gb interface. After processed by
the SGSN, the data flow is forwarded from the Gn/Gp interface.
The 2.5G downlink service data flow enters the SGSN from the Gn/Gp interface. After processed
by the SGSN, the data flow is forwarded from the Gb interface.
The following illustrates the processing procedure for 2.5G uplink service data flow, as shown
in Figure 4-17.
Figure 4-17 Processing procedure for 2.5G uplink service data flow
BSS U
U U U U U U U
G
P G F P B R E
B BSS
I F C I I C P
I
GGSN U U U U U U I
The steps for processing the 2.5G uplink signaling data flow are as follows:
1. The signaling from the BSS to the SGSN can enter the UGBI board in the following two
ways:
The signaling directly enters the UGBI through the UEPI.
The signaling enters the UGFU through the UPIU. Then the UGFU forwards the
signaling to the UGBI through the internal communication system.
2. After receiving the signaling from the BSS, the UGBI sends it to the protocol layers for
processing. Then the processed data is forwarded to the UGFU.

3. Based on the destination IP address of the service data, the UGFU chooses a proper port
for the data that is then sent to the GGSN.
4.7.4 3G service data flow

Handling 3G service data flows is a process in which the internal modules handle the 3G service
data after the SGSN receives the data from the Iu interface.
The 3G uplink service data flow enters the SGSN from the Iu interface. After processed by the
SGSN, the data flow is forwarded from the Gn/Gp interface.
The 3G downlink service data flow enters the SGSN from the Gn/Gp interface. After processed
by the SGSN, the data flow is forwarded from the Iu interface.
The following illustrates the processing procedure for 3G uplink service data flow, as shown in
Figure 4-18.
Figure 4-18 Processing procedure for 3G uplink service data flow
RNC U U
P G
I F
GGSN U U
The steps for processing the 3G uplink signaling data flow are as follows:
1. The data packets from the RNC are sent to the UGFU after processed by the ATM layer
and SAR of the UPIU.
2. The UGFU extracts the IP packets from the ATM cells and determines the destination
UGFU for the data based on the destination IP address.
3. The UGFU replaces the GTP header and modifies the tunnel identifier.
4. The UGFU finds the route for the data packets based on the destination IP address. Then
the UGFU sends the encapsulated data packets to the GGSN through the UPIU.

System Principle 5 Principle of the Charging System
5 Principle of the Charging System
About This Chapter
The charging system operates in the USPU, UGTP, and UCDR boards. The charging system
collects, codes, buffers, and sends CDRs as well as provides charging information for the billing
center.
5.1 The location of the charging system in the SGSN
5.2 The structure of the modules in the charging system
The charging system contains of charging information collection subsystem, CDR coding
module, Hard disk module
5.3 The procedure for generating a CDR
The procedure for generating a CDR contains the following three steps: Creating a CDR;
Generating a partial CDR; Closing a final CDR.
5.4 Processing and Sending a CDR
CDRs generated by the USPU and UGTP are sent to the UCDR. The enarging subsystem in the
UCDR encodes the CDRs with abstract syntax notation one (ASN.1), encapsulates the CDRs to
a GTP' packet and then sent the packet to the CG through the UGFU.

5 Principle of the Charging System System Principle
5.1 The location of the charging system in the SGSN

The charging system collects, codes, buffers, and sends CDRs as well as provides charging
information for the billing center.
Figure 5-1 shows where the charging system is located in the SGSN.
Figure 5-1 Location of the charging system in the SGSN

No.7
signalling
BSS
node, such
as HLR
E1 E1
UICP UGTP UGBI USPU
Iu interface
Gn/Gp Gb
interface interface
subsystem subsystem
subsystem BSS
Platform Platform
BUS
UOMU URCU USIG
Internal
O Signaling O
OM communication
M subsystem M
subsystem
Platform Platform
Platform management
Service subrack

LMT
Fiber cable
UCDR UFCU UGFU

Gn/Gp
Internal interface
communication
system M M M
subsystem
IP routing
subsystem

Fiber cable or
network cable
IP node,
RNC such as
GGSN

5.2 The structure of the modules in the charging system

The charging system contains of charging information collection subsystem, CDR coding
module, Hard disk module
Figure 5-2 shows the structure of the charging subsystems.
Figure 5-2 Structure of the charging subsystems
Charging S-CDR
information CDR coding
collection
UGTP
CDR sending
UCDR
Charging
information
collection M-CDR
Hard
USPU disk
UBSU
UGFU
UPIU
IP
CG
The charging system contains the following subsystems:
l Charging information collection subsystem

The charging information collection subsystem in the USPU collects M-CDR, S-SMO-
CDR, S-SMT-CDR, LCS-MT-CDR, LCS-MO-CDR, and LCS-NI-CDR. Then the
subsystem generates a half-finished CDR and sends the CDR to the UCDR board.
The charging information collection subsystem in the UGTP receives traffic information
from the UGFU and collects S-CDR. Then the subsystem generates a half-finished CDR
and sends the CDR to the UCDR board.

l CDR coding module

The CDR coding module carries out ASN.1 coding for the half-finished CDR and processes
it to a finished CDR that is suitable for transmission and complies with the protocol.
l CDR sending module
The CDR sending module encapsulates CDRs according to certain protocols, chooses the
suitable CG for the CDRs, and then transfers them through the UGFU.
l Hard disk module
When the SGSN and CG cannot communicate normally, the hard disk module buffers
CDRs.
5.3 The procedure for generating a CDR

The procedure for generating a CDR contains the following three steps: Creating a CDR;
Generating a partial CDR; Closing a final CDR.
Generating a CDR
A CDR contains many domains, such as user identity, service time, and service duration. The
billing center charges the users based on the CDR information.
The charging subsystem in the USPU and UGTP collects original charging information. Some
of the charging information is obtained from the user database or the configuration database,
but some dynamic information, such as the service duration is obtained from the specified
counter or timer.
The procedure for generating a CDR contains the following three steps:
l Creating a CDR
When a subscriber uses the service, the system is triggered to create a CDR at a certain
charging point and then records the subsequent charges in the CDR. For example, after
sending an ATTACH ACCEPT message to a user, the SGSN creates a mobility
management generated-charging data record (M-CDR) for the user.
l Generating a partial CDR
When a subscriber uses the service, the SGSN generates a partial CDR for the user if time,
traffic, tariff, or QoS change time reach the set threshold.
l Closing a final CDR
When the service terminates, the SGSN closes the CDR and generates a final CDR
One or more CDRs may be generated when a subscriber uses a certain service. These CDRs are
combined in the billing center for final charging on the user.
The following takes M-CDR as an example to explain how a CDR is generated.
Creation of M-CDR
The mobility management service starts when an MS attaches to the SGSN, and terminates when
the MS detaches from the SGSN. Since the service occurs in a series of processes, the creation
of an M-CDR is closely related to the connection status between the MS and the SGSN. To be
specific, the creation of an M-CDR contains three steps, creation, generation, and closure.
Table 5-1 lists the MS status in the M-CDR generation procedure.

Table 5-1 MS status in the M-CDR generation procedure
M-CDR Generation Procedure MS Status
Creation of a M-CDR Attached to the SGSN
Generation of a partial M-CDR From attached to the SGSN till detached from
the SGSN and conditions for generating a
partial M-CDR are met
Closure of a M-CDR Detached from the SGSN
Figure 5-3 shows the charging flow points for the mobility management service.
Figure 5-3 Charging flow points for the mobility management service
MS BSS/UTRAN Old SGSN New SGSN HLR
Attach Request
Insert Subscriber Data
Attach Accept
P1
Attach Complete
Routing Area Update

Request
Routing Area Update
Accept
P2 Routing Area Update

Request
RAU Update Request

RAU Update Response
RAU Update ACK
Routing Area Update P3

Accept
P4
Detach Request
Detach Accept
P5
Table 5-2 describes the charging flow points in Figure 5-3.

Table 5-2 Description of the charging flow points

Sequence Number Event Network Element
P1 The SGSN creates an M- Old SGSN

CDR for the MS.
P2 The SGSN generates a partial Old SGSN

M-CDR after the number of
location update for the MS
reaches the present threshold.
P3 Inter-SGSN switch occurs to Old SGSN

the MS. The old SGSN closes
the M-CDR.
P4 Inter-SGSN switch occurs to New SGSN

the MS. The new SGSN
creates an M-CDR.
P5 The MS detaches from the New SGSN

SGSN. The SGSN closes the
final M-CDR.
5.4 Processing and Sending a CDR

CDRs generated by the USPU and UGTP are sent to the UCDR. The enarging subsystem in the
UCDR encodes the CDRs with abstract syntax notation one (ASN.1), encapsulates the CDRs to
a GTP' packet and then sent the packet to the CG through the UGFU.
ASN.1 Coding
ASN.1 is a universal language used worldwide to describe data structure in the
telecommunication field. According to the 3rd generation partnership project (3GPP) protocol,
all CDR structures must adopt ASN.1 for description. ASN.1 has the following features:
l Unfixed-length data structure
The description fields of ASN.1 have two types, optional and mandatory. Each filed
contains a triplet of Tag, Length, and Value.
l Cross-platform
Data structures described by ASN.1 adopt the uniform network byte sequence for
transmission over networks.
Sending a CDR
Figure 5-4 shows the procedure for sending a CDR.

Figure 5-4 Procedure for sending a CDR
ASN.1 CDR
GTP' header ASN.1 CDR

Internal
CDR
UDP header
GTP' header
IP header
UDP header
Subrack Subrack
No:Slot No No:Slot No IP header
CG
U U U
S U C G
P G D F
U T R U
P
The steps for sending a CDR are as follows:

1. The USPU or UGTP generates a CDR and sends the CDR to the UCDR.
2. The UCDR encapsulates the ASN.1-encoded CDR using GTP, TCP/UDP, and IP in turn
and then sends the encapsulated CDR packet to the UGFU.
3. The UGFU queries the internal routing table and sends the CDR to the CG.

System Principle 6 Principle of the O&M System
6 Principle of the O&M System
About This Chapter
6.1 The location of the O&M system in the SGSN
The functions of the O&M system are mainly implemented on the UOMU board.
6.2 The structure of the modules in the O&M system
Based on its location, the O&M system can be categorized into two modules, back administration
module (BAM) and front administration module (FAM).
6.3 Configuration Management
Data configuration includes operations such as addition, deletion, modification, and query of
system data. Actually, data configuration is to manage the configuration database.
6.4 Performance Measurement
Performance measurement means measuring the SGSN and its surrounding network to obtain
data about network operation.
6.5 Alarm Management
The alarm system monitors the systemic operation and informs the maintenance personnel of
the detected faults or disturbance.
6.6 Query and Control
The query and control function indicates monitoring, controlling, and testing the hardware and
links in the system.
6.7 Security Management
Security management means controlling on users and user authorities to ensure that the
authorized users can operate the SGSN within the authorization range.
6.8 User or Interface Tracing
Tracing function is used in the routine maintenance for the SGSN. By tracing the information,
you can locate where the fault occurs in the service procedure. After the data is configured for
the SGSN, you can establish tracing to verify if the signaling links are normal, and thus judge
where the fault occurs.
6.9 Log Management

6 Principle of the O&M System System Principle
The log management subsystem records the generated messages when the system runs and saves
the messages to the UOMU hard disk, and thus facilitates problem location and system
maintenance.
6.10 External Maintenance Interface
The O&M subsystem acts as a bridge to connect the SGSN with users, so the subsystem must
provide various network management systems with the interconnected interfaces. Currently, the
SGSN can provide the command input and output interface and SNMP interface.

6.1 The location of the O&M system in the SGSN

The functions of the O&M system are mainly implemented on the UOMU board.
Figure 6-1 shows the location of the O&M system in the SGSN.
Figure 6-1 Location of the O&M system in the SGSN

No.7
signalling
BSS
node, such
as HLR
E1 E1
UICP UGTP UGBI USPU
Iu interface
Gn/Gp Gb
interface interface
subsystem subsystem
subsystem BSS
Platform Platform
BUS
UOMU URCU USIG
Internal
O Signaling O
OM communication
M subsystem M
subsystem
Platform Platform
Platform management
Service subrack

LMT
Fiber cable
UCDR UFCU UGFU

Gn/Gp
Internal interface
communication
system M M M
subsystem
IP routing
subsystem

Fiber cable or
network cable
IP node,
RNC such as
GGSN

Externally, the O&M system provides the network management systems with the uniform
human-machine language (MML) interfaces that realize the network management systems to
access the SGSN.
Internally, the O&M system cooperates with the other subsystems to maintain and monitor the
SGSN system.
6.2 The structure of the modules in the O&M system

Based on its location, the O&M system can be categorized into two modules, back administration
module (BAM) and front administration module (FAM).
l The BAM manages the interactive input and output management between the O&M system
and users. The BAM breaks down and delivers O&M tasks, collects and reports the SGSN
monitoring data. The BAM is in the UOMU.
l The FAM directly interacts with other subsystems. The FAM is located in all the IO boards
in the SGSN.
The BAM and the FAM perform operation and maintenance for the whole SGSN system, as
shown in Figure 6-2.
Figure 6-2 Hierarchy of the O&M system
FAM
UICP
IP BAM FAM
UOMU
LMT
FAM
USPU
SGSN
The BAM and the FAM modules consist of the configuration, query and control, performance,
alarm, security, tracing, and log management submodules, as shown in Figure 6-3.

Figure 6-3 Composition of the O&M system
LMT
IP
BAM
Command
processing
Security
management
Query and
Log Tracing Alarm Performance
Configuration control
management management management management
management
FAM
UOMU
FAM
Service board
6.3 Configuration Management

Data configuration includes operations such as addition, deletion, modification, and query of
system data. Actually, data configuration is to manage the configuration database.
Figure 6-4 shows the configuration management flow.

Figure 6-4 Configuration management flow
MML
command
Configuration
management
ADD/RMV/MOD/
LST/SET
Initialization
MML.TXT
CDB SAVE CFG
Service module
Dynamic Data Configuration

You can dynamically configure the data when the SGSN works normally.
To configure dynamic data, perform the following steps:
1. You send an MML configuration command through the LMT.

2. After you send the command, the configuration management module resolves the command
and checks the validity for the command.
3. If the command is illegal, the module conducts addition, modification, or deletion of data
in the database as directed by the command.
4. The CDB then validates the data that is updated dynamically.
NOTE
For some modification that may affect the normal running of the system, a configuration command only
changes the information in the database. The modified data takes effect only after the system restarts.
Static Data Configuration

MML.TXT can be manually modified off-line. The modified MML.TXT file is loaded to the
UOMU. When the system initializes, the UOMU reads the data from the MML.TXT to update
the data that is configured statically.

Saving and Recovering Configuration

When the system loads or updates the configuration, you must save the updated configuration
data to make them effective all the time.
To save the configuration, perform the following steps:
1. You send the configuration saving command SAVE CFG through the LMT.
2. After you send the command, the configuration management module browses through all
the tables in the CDB and converts each record to a certain MML command.
3. The converted MML commands are saved in sequence to a new file. Then the new initiation
MML.TXT file forms in the configuration database.
When the system restarts and initializes the CDB, it reads the commands from the initiation
MML.TXT file and executes the commands in the file one by one. Then the system writes the
configured data in the CDB, and thus completes recovering the data before the system starts.
6.4 Performance Measurement

6.4.1 The basic concepts of performance measurement
Performance measurement consists of the following basic elements: measurement index,
measurement unit, measurement set, measurement object, configurable object, non-configurable
object, and performance task.
6.4.2 Procedure for performance measurement
The procedure for performance measurement includes information collecting, reporting, and
processing.
6.4.1 The basic concepts of performance measurement

Performance measurement consists of the following basic elements: measurement index,
measurement unit, measurement set, measurement object, configurable object, non-configurable
object, and performance task.
The basic concepts of performance measurement are described as follows:
l Measurement item
It is also called measurement entity, which is a specific attribute item for statistics.
l Measurement unit
It is a set of measurement items that bear the same attribute.
l Measurement set
It is a set of measurement units that bear the same attribute.
l Measurement object
It is an entity object that is pointed at by the measurement item.
l Configurable object

It is an object to be configured by a user. Configurable objects may be in large quantity,

such as IMSI. The object may also be unpredictable in the system, such as an access point
name (APN). Therefore, the system cannot measure all the configurable objects.
l Unconfigurable object
It is an object automatically created by the system, such as a board.
l Performance task
It consists of measurement unit, measurement cycle, and other attributes. This task collects
all the performance data for all the measured objects on a time basis.
6.4.2 Procedure for performance measurement

The procedure for performance measurement includes information collecting, reporting, and
processing.
Figure 6-5 shows the procedure for performance measurement.
Figure 6-5 Procedure for performance measurement
M2000
database
server
M2000 client
MML Result data
command
LMT
Result data BAM performance Result data Performance

management data file
module
Result Performance
Initialization
buffer area task file
FAM performance
management
Result data module
UOMU
Service
board
Result
report area
FAM performance Result data
Object
management
area
module
Initial data
Counter
Service module
area
The steps for performance measurement are as follows:
1. System measurement initialization

After the system is first started, the BAM performance management module generates the
initial performance task file.
The performance task file records information such as measurement object, measurement
period, measurement set, measurement unit, and measurement index.
The measurement object is generated by the BAM performance management module after
the module obtains the measurement data from the system configuration file. The
measurement period has two types, five minutes and thirty minutes. Measurement set,
measurement unit, and measurement index are determined by the system configuration file.
2. Measurement information synchronization
The BAM performance management module synchronizes the measurement task
information to all the service boards. The FAM performance management module creates
the object area, counter area, and result reporting area.
3. Data collection
(1) The service modules in the service board collect all types of measurement data and
save it in the counter area. The measurement data is accumulated in the counter.
(2) The FAM performance management module in the service board collects data every
five minutes and calculates the increment of the data, and saves the data in the result
reporting area.
(3) The FAM performance management module in the service board reports the data in
the result reporting area to the FAM performance management module in the UOMU.
(4) The FAM performance management module in the UOMU gathers the measurement
data reported from all the service boards and then sends the data to the BAM
performance management module.
(5) The BAM performance management module formats the performance measurement
results and then saves the results in the result data file.
NOTE
Performance result data has three types, short-period result file (data measured every 5 minutes),
medium-period result file (data measured every 30 minute), and SNMP measurement result file.
The following shows how long these files can be stored in the SGSN:
l The short-period result file can be saved for one day.
l The medium-period result file can be saved for three and a half days.
l The SNMP measurement result file can be saved for seven days.
4. Data reporting
The BAM performance management module regularly sends the measurement result
information to the M2000 database server. The M2000 database server obtains the data
from the UOMU performance data file through the file transfer protocol (FTP) and saves
the data in the database.
The LMT can also automatically obtain the measurement result file from the UOMU hard
disk.
For the data of the simple network management protocol (SNMP), the network management
system actively obtains and queries the data.
5. Data processing
Through the M2000 client, you can query, analyze, and collect the measurement data saved
in the M2000 database server.

Through the LMT, you can browse through the performance measurement data saved
locally.
6.5 Alarm Management

The alarm system monitors the systemic operation and informs the maintenance personnel of
the detected faults or disturbance.
Based on the alarm type, alarms can be divided into two types:
l Fault alarm
l Event alarm
Based on the alarm severity level, alarms can be divided into four types:
l Critical alarm
l Major alarm
l Minor alarm
l Warning
Figure 6-6 shows the alarm management flow.

Figure 6-6 Alarm management flow
Alarm box M2000 client
LAN
M2000
LMT database
MML Result
command data
Alarm
Alarm buffer Alarm log file
management
area
module
FAM
UOMU
Initial alarm
FAM FAM
Service module Service module
Service board Service board
Alarm Generation
If a service board detects abnormity when it runs, an alarm is generated. The generation of the
alarm is actually a process of cooperation between the FAM and BAM.
The steps for generating an alarm are as follows:
1. The service module generates an alarm.

2. The FAM alarm processing module sends the alarm to the BAM alarm processing module
in the UOMU board.
3. The BAM alarm processing module explains the alarm. If the alarm satisfies the shielding
condition, it is directly discarded. If the alarm does not satisfy the shielding condition, it is
reported to the LMT, alarm box, or M2000 database.
4. The maintenance console of the LMT and the M2000 display the alarms in a list and inform
the alarm list to the alarm box.
NOTE
l The alarms in the alarm box are from the UOMU, LMT, or M2000 maintenance console. The
source of an alarm depends on where the alarm box is installed.
l The alarms in the M2000 maintenance console are forwarded by the M2000 database.
Alarm Clearing
Only a fault alarm can be cleared. Alarm clearing has the following situations:
l When the fault is cleared, the service module generates a recovery alarm. The BAM then
clears the saved alarm.
l If the BAM receives the first alarm when a board resets, all the alarms about the board are
cleared.
l Expired clearing. If the alarm is not cleared for a period of more than 15 days, the system
automatically clears the alarm.
l When the LMT receives the alarm clearing, it displays the alarm in grey.
Alarming Saving
After an alarm is generated, it is saved as the active alarm in the memory or the history alarm
in the hard disk.
The active alarm indicates that the alarm is not cleared. When a fault alarm is generated, it is
directly saved to the active alarm buffer area. The recovery alarm then clears the alarm in the
buffer area. When the system initializes, the alarm processing module retrieves the alarm that
is not cleared in the history alarm log file and generates the active alarm list.
When the alarm saving timer expires, the alarms in the active alarm buffer area are saved to the
history alarm file. The file can save up to 25,000 alarm records, including fault alarms and event
alarms. If the file reaches the maximum capacity, it cyclically covers the alarms.
Alarm Box Operation

When the system generates an alarm, the system informs a user through the audible and visual
prompt that is performed by the alarm box.
The alarm box has three connection modes:
l Connecting to the serial port on the UOMU
l Connecting to the serial port on the LMT
l Connecting to the serial port on the M2000
Event alarms are not reported to the alarm box. Fault alarms can be reported to the alarm box if
they are set to report. By judging the setting, the BAM alarm processing module determines
whether to simultaneously report the alarm to the alarm box when the alarm is generated.

Through the UOMU board, you can reset the alarm box, reset the alarm indicator, and stop the
alarm sound.
6.6 Query and Control

The query and control function indicates monitoring, controlling, and testing the hardware and
links in the system.
Figure 6-7 shows the query and control flow.
Figure 6-7 Query and control flow
LAN
LMT
MML Board status

command report
Query and control

module
FAM
UOMU
Board status
FAM FAM
Equipment Maintenance and Status Query

To perform query and control on the SGSN, perform the following steps:
1. You send a query and control command through the maintenance console.
2. After you send the command, the query and control module resolves the command and
sends the query and control message to the board.

3. The board executes the command or obtains the board status. Then the board sends the
board status to the BAM in the UOMU board through a message.
In the procedure for common query control, the BAM or the FAM only acts as a bridge to transmit
messages. The specific operation should be performed by the service module.
Status Report
Through the LMT panel, you can view the hardware structure and status messages of the SGSN.
When the board status changes, the status is updated in real-time on the panel, which is realized
by the automatic report of board status.
The steps for reporting the board status are as follows:
1. When the board status changes, the message of the board status is generated. When the
BAM on the UOMU receives the message of board status change, the status report is
generated and then is reported to the LMT.
2. The LMT updates the panel in real-time based on the report.
The procedure for reporting CPU occupation rate is similar to that for reporting board status.
6.7 Security Management

Security management means controlling on users and user authorities to ensure that the
authorized users can operate the SGSN within the authorization range.
6.7.1 Domain Management
The SGSN classifies users into two domains: the local domain and M2000 domain. The
administrator independently manages the user in any one of the domain, but the administrator
in one domain cannot manage the users in the other domain.
6.7.2 User Authorities
The authority of an operator is classified to five levels.
6.7.3 User Name and Password
A user name is composed of up to 32 characters containing only alphabets and digits. It is case
insensitive and must start with an alphabet.
6.7.4 Command Groups
A command group is a set of commands. Commands form some command groups, and then the
command groups are assigned to users with different authorities for administration management.
A command can be in multiple command groups.
6.7.1 Domain Management

The SGSN classifies users into two domains: the local domain and M2000 domain. The
administrator independently manages the user in any one of the domain, but the administrator
in one domain cannot manage the users in the other domain.
The users in the two domains adopt different authentication methods, as shown in Figure 6-8.

Figure 6-8 Procedure for user authentication

Domain user
Authentication authentication
request Security request
management
Authentication module Domain user
LMT response authentication
M2000
response
Authentication Authentication
request response
Local user
information
UOMU
For the users that log in to the local domain, the SGSN authenticates them based on the user
information file saved locally.
For the users that log in to the M2000 domain, the SGSN sends the user authentication
information to the M2000, and then the M2000 authenticates the users.
6.7.2 User Authorities

The authority of an operator is classified to five levels.
The user authorities are classified into five groups as shown in Table 6-1.
Table 6-1 User groups and authorities

Authority Data Query System Data Administratio
Maintenance Configuration n
Guest - - -
User - -
Operator -
Administrator
Custom When adding a user, you can assign every privilege to this user.
NOTE
"" in Table 6-1 indicates the authority for the corresponding user group.
The command groups for the Guest, User, Operator, and Administrator are predefined in the LMT system.
6.7.3 User Name and Password

A user name is composed of up to 32 characters containing only alphabets and digits. It is case
insensitive and must start with an alphabet.
A user account consists of a user name and a password.

The length and character combination of a password are set by a user.
The LMT has two users:
l admin: The initial password is sgsnadmin. The admin has the highest authority and can
execute all the commands. Initially, the admin adds the other users and cannot be deleted.
The password of admin can only be modified by the admin.
l guest: The initial password is guestguest. The guest only has the log in, log out, and query
authorities.
NOTE
A user can change only his password.
6.7.4 Command Groups

A command group is a set of commands. Commands form some command groups, and then the
command groups are assigned to users with different authorities for administration management.
A command can be in multiple command groups.
The system defines 32 command groups as follows:
l G_0 to G_14, and G_31: default command group

l G_15 to G_30: custom command group
Table 6-2 describes these command groups.
Table 6-2 Command group description
Command Group Function Remarks
G_0 Guest group Predefined MML command

groups. The commands in
G_1 Alarm query these groups can be queried
G_2 Alarm modification but cannot be modified.
G_3 Performance query
G_4 Performance creation
G_5 Performance modification
G_6 Equipment query
G_7 Equipment modification
G_8 Configuration query
G_9 Configuration modification
G_10 Trace query
G_11 Trace creation
G_12 BNET query
G_13 BNET modification

Command Group Function Remarks
G_14 SGSN information

management
G_15 to G_30 Custom group The commands in these

groups can be queried and
modified.
G_31 System group Predefined MML command

groups. The commands in
these groups can be queried
but cannot be modified.
6.8 User or Interface Tracing

Tracing function is used in the routine maintenance for the SGSN. By tracing the information,
you can locate where the fault occurs in the service procedure. After the data is configured for
the SGSN, you can establish tracing to verify if the signaling links are normal, and thus judge
where the fault occurs.
Tracing consists of two types: user tracing and interface tracing.
Figure 6-9 shows the procedure for user tracing or interface tracing.

Figure 6-9 Procedure for user tracing or interface tracing
LAN
LMT
Tracing Tracing
creation report
Tracing module
FAM
UOMU
Tracing report
FAM FAM
To carry out user tracing or interface tracing, perform the following steps:
1. The operator sends the MML command to create the task through the maintenance console.
2. The tracing task resolves the command and sends the tracing message to the service module
in the board.
3. After processing the message, the service module sends it to the tracing module.
4. After processing the message, the tracing module sends it to the maintenance console.
6.9 Log Management

The log management subsystem records the generated messages when the system runs and saves
the messages to the UOMU hard disk, and thus facilitates problem location and system
maintenance.
The SGSN9810 saves the following logs:
l Operation log

The operation log contains the records of all LMT operations and other related information,
including: user name, user ID, IP address of the LMT, command, command execution data
or time, execution result.
NOTE
You can execute LST LOG to query the user operation log.
l System log
When the system runs, the system log records important events, such as startup, reset, and
load to facilitate the maintenance personnel to locate the problems.
l Fault log
When serious abnormity occurs in the system, the fault log records the on-site information
captured by the monitoring module. The information includes abnormal task information,
time when abnormity occurs, and call stack for function.
l FTP log
The FTP log records the user's operation on the files in the UOMU hard disk through the
FTP. The recorded information includes login time, login IP address, user name, and
operation files.
NOTE
You can execute LST LOG to query the user operation log.
All the logs discussed above can be obtained from UOMU hard disk through the FTP.
6.10 External Maintenance Interface

The O&M subsystem acts as a bridge to connect the SGSN with users, so the subsystem must
provide various network management systems with the interconnected interfaces. Currently, the
SGSN can provide the command input and output interface and SNMP interface.
The network management devices that directly connected with the SGSN include the LMT,
M2000, and network management system providing the SNMP interface. The SGSN connects
with the LMT and M2000 through the uniform input and output interfaces for MML commands.
Figure 6-10 shows the external O&M interfaces of the SGSN.

Figure 6-10 External O&M interfaces of the SGSN

M2000
MML command/
report interface
SNMP
interface
MML command/ LAN
report interface SNMP
Manager
LMT
SGSN
6.10.1 Command Input and Output Interface

All the O&M management on the SGSN is realized through MML commands with a uniform
format.
6.10.2 SNMP Interface
The SGSN adopts the SNMP interface to realize alarm and performance statistics functions.
6.10.3 SSH
The SGSN supports SSH 2.0 applied to the LMT and UOMU to guarantee security of network
access.
6.10.1 Command Input and Output Interface

All the O&M management on the SGSN is realized through MML commands with a uniform
format.
Command name: parameter name 1 = parameter value 1, parameter name 2 = parameter value
2, , parameter name N = parameter value N
The command delivered by the network management system is sent to the BAM on the UOMU
through the character strings. The BAM resolves the character strings and extract the specific
command and parameter values.
Likewise, command output adopts a uniform format for output reports. After encapsulating the
command execution result to a report with a uniform format, the BAM sends the report to the
network management system. Then the network management system resolves the text report to
obtain the execution result and query result.

6.10.2 SNMP Interface

The SGSN adopts the SNMP interface to realize alarm and performance statistics functions.
Figure 6-11 shows the structure and flow of SNMP.
Figure 6-11 Structure and flow of SNMP
Request/Response
Trap
SGSN (SNMP Agent) SNMP Manager
The network management system (NMS) and agent transfer management information by
sending messages to each other. The messages have the following types:
l Get Request message: to obtain the value of the specified management variable
l GetNext Request message: to continuously obtain a batch of values of the management
variable
l Get Response message: to meet the requirement and return the required value or the error
type
l Set Request message: to set the specified management variable
l Trap message: to actively send information from the managed equipment to the NMS in
emergency
The SGSN adopts the SNMP interface to realize alarm and performance statistics functions. The
alarm management function is realized through the Trap message and the performance
management function through the Get Request, GetNext Request, and Get Response messages.
6.10.3 SSH
The SGSN supports SSH 2.0 applied to the LMT and UOMU to guarantee security of network
access.
When a user on an insecure network telnets the SGSN, the secure shell (SSH) feature offers
security guarantee and powerful authentication to protect the SGSN from attacks, such as IP
address fraud and the interception of the plain text password.
The SGSN supports the SSH applied between the LMT and UOMU to ensure securely visiting
the network The SGSN can connect with multiple SSH clients.
The SSH client function allows users to establish SSH connections with the SGSN that supports
the SSH server, as shown in Figure 6-12.

Figure 6-12 Establishing an SSH channel between the SGSN and LMT
The communication between the server and the client follows six phases to accomplish the
authentication security connection of SSH:
l Negotiation for version
l Negotiation for algorithm
l Key exchange
l Identity Authentication
l Session request
l Interactive session
SSH can implement secure remote access on insecure networks. It has the following advantages:
l SSH supports RSA authentication mode. In RSA authentication, SSH implements secure
key exchange by generating public and private keys, and thus realizes the whole secure
process of sessions.
l SSH supports three data encryption standard: advanced encryption standard (AES), data
encryption standard (DES) and 3DES.
l SSH provides encryption to the transmitted data to guarantee data security and reliability.

System Principle Index
Index
A structure, 4-7
Gn/Gp interface subsystem
alarm management, 6-10 DNS resolution, 4-21
Gn/Gp signaling process, 4-20
B NTP synchronization, 4-22
structure, 4-16
board list, 1-6 user data forwarding, 4-18
bus
H.110 Bus, 2-4
serial port bus, 2-6
H
shared resource bus, 2-3 hardware
subracks, 2-3 board, 1-6
clock synchronization subsystem, 2-12
C equipment monitoring subsystem, 2-18
power supply subSystem, 2-7
charging system structure, 1-3
generating a CDR, 5-4 subrack, 1-5
location, 5-2
processing and sending a CDR, 5-6
clock synchronization subsystem
I
clock control Ppart, 2-18 internal communication subsystem
distribution part, 2-16 procedure , 3-12
interface part, 2-15 structure, 3-11
overview, 2-12 IP routing subsystem
structure, 2-14 principle, 4-5
configuration management, 6-5 structure, 4-3
Iu interface control plane subsystem
E structure, 4-11
Iu interface signaling subsystem
equipment monitoring subsystem procedure, 4-14
equipment room environment monitoring, 2-19
fan , 2-18
external maintenance interface
O
command input and output interface, 6-20 O&M system
SNMP interface, 6-21 alarm management, 6-10
SSH, 6-21 configuration management, 6-5
external maintenance interface, 6-19
F log management, 6-18
performance measurement, 6-7
fan monitoring, 2-18 query and control, 6-13
security management, 6-14
G
Gb interface subsystem
procedure, 4-9
Issue 03 (2009-05-27) Huawei Proprietary and Confidential i-1

Index System Principle
P
platform management subsystem
startup management, 3-6
switchover management, 3-7
platform system
internal communication subsystem, 3-11
location, 3-2
platform management subsystem, 3-3
power supply subsystem
monitoring, 2-10
structure, 2-7
S
security management
command groups, 6-16
domain management, 6-14
user authorities, 6-15
user name and password, 6-15
service system
Gb iInterface subsystem, 4-7
Gn/Gp interface subsystem, 4-16
IP routing subsystem, 4-3
Iu interface control plane subsystem, 4-11
signaling subsystem, 4-23
typical data processing procedure, 4-28
signaling subsystem
procedure, 4-26
structure, 4-23
software
charging system, 1-11
O&M system, 1-11
platform system, 1-10
service system, 1-10
structure, 1-8
startup management, 3-6
structure
hardware, 1-3
software , 1-8
subrack
bus, 2-3
structure, 1-5
switchover management, 3-7
i-2 Huawei Proprietary and Confidential Issue 03 (2009-05-27)


SGSN Principles How Does It Works PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SGSN Principles How Does It Works PDF

Uploaded by

Copyright:

Available Formats

HUAWEI SGSN9810 Serving GPRS Support Node

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

About This Document.....................................................................................................................1

2 Principle of the Hardware........................................................................................................2-1

3 Principle of the Platform System............................................................................................3-1

Issue 03 (2009-05-27) Huawei Proprietary and Confidential i

3.2 Platform Management Subsystem...................................................................................................................3-3

4 Principle of the Service System...............................................................................................4-1

5 Principle of the Charging System...........................................................................................5-1

6 Principle of the O&M System..................................................................................................6-1

ii Huawei Proprietary and Confidential Issue 03 (2009-05-27)

6.2 The structure of the modules in the O&M system..........................................................................................6-4

Issue 03 (2009-05-27) Huawei Proprietary and Confidential iii

Figure 1-1 Location of the SGSN9810 in a GPRS/UMTS network....................................................................1-2

Issue 03 (2009-05-27) Huawei Proprietary and Confidential v

Figure 4-4 Modules inside the Gb interface subsystem ......................................................................................4-8

vi Huawei Proprietary and Confidential Issue 03 (2009-05-27)

Table 1-1 Boards in the SGSN ............................................................................................................................1-7

Issue 03 (2009-05-27) Huawei Proprietary and Confidential vii

About This Document

Product Name Version

Issue 03 (2009-05-27) Huawei Proprietary and Confidential 1

5 Principle of the Charging System

6 Principle of the O&M System

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

Indicates a tip that may help you solve a problem or save

Provides additional information to emphasize or supplement

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

2 Huawei Proprietary and Confidential Issue 03 (2009-05-27)

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Issue 03 (2009-05-27) Huawei Proprietary and Confidential 3

Double-click Press the primary mouse button twice continuously and

4 Huawei Proprietary and Confidential Issue 03 (2009-05-27)

1 System Structure of SGSN9810

About This Chapter

Issue 03 (2009-05-27) Huawei Proprietary and Confidential 1-1

1.1 Overview of SGSN9810

Figure 1-1 shows the location of the SGSN9810 in a GPRS/UMTS network.

Figure 1-1 Location of the SGSN9810 in a GPRS/UMTS network

MS: mobile station RAN: radio access network

BTS: base transceiver station BSC: base station controller

RNC: radio network controller BG: border gateway

SGSN: serving GPRS Support Node HA: home agent

1-2 Huawei Proprietary and Confidential Issue 03 (2009-05-27)

CG: charging gateway DNS: domain name service

GGSN/FA: gateway GPRS support node/ AAA: authentication, authorization, and

MSC/VLR: mobile service switching center/ HLR: home location register