owb091001(slide)sgsn9810 v900r010c01 system principle-20100505-b-v1.1

HUAWEI TECHNOLOGIES CO., LTD.

www.huawei.com

HUAWEI Confidential

Security Level: INTERNAL

SGSN9810 V900R010 System Principle

ISSUE1.1

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential

This slide describes the system overview, system

structure, service processing, operation and

maintenance, and new features of the SGSN9810

V900R010 ATCA platform.


References

SGSN9810 V900R010C01 System Principle


Upon completion of this course, you will be able to:

Learn about the main performance specifications of SGSN9810 V900R010.

Learn about the hardware and software structures of SGSN9810 V900R010.

Learn about the maintenance and alarm implementation of SGSN9810 V900R010.

Learn about the new features of SGSN9810 V900R010.


Chapter 1 SGSN9810 V900R010 System OverviewChapter 1 SGSN9810 V900R010 System Overview

Chapter 2 SGSN9810 V900R010 System StructureChapter 2 SGSN9810 V900R010 System Structure

Chapter 3 SGSN9810 V900R010 Software InstallationChapter 3 SGSN9810 V900R010 Software Installation

Chapter 4 SGSN9810 V900R010 Service ProcessingChapter 4 SGSN9810 V900R010 Service Processing

Chapter 5 SGSN9810 V900R010 Operation and Chapter 5 SGSN9810 V900R010 Operation and MaintenanceMaintenance

Chapter 6 SGSN9810 V900R010 Environment MonitoringChapter 6 SGSN9810 V900R010 Environment Monitoring

Chapter 7 SGSN9810 V900R010 Time SynchronizationChapter 7 SGSN9810 V900R010 Time Synchronization

Chapter 8 SGSN9810 V900R010 Clock ManagementChapter 8 SGSN9810 V900R010 Clock Management

Chapter 9 SGSN9810 V900R010 Charging ManagementChapter 9 SGSN9810 V900R010 Charging Management


Chapter 1 SGSN9810 V900R010 System

Overview

1.1 Network Position of SGSN9810 V900R010

1.2 Specifications of SGSN9810 V900R010


Upon completion of this chapter, you will be able to:

Learn about the external interfaces and network

position of SGSN9810 V900R010.

Learn about the typical configuration and major

specifications of SGSN9810 V900R010.


Network Position of SGSN9810 V900R010

The GPRS network is a 2.5G network developed based on the GSM network to support the packet

service. The UMTS network is a 3G network supporting CS and PS services. The structure of the UMTS

PS domain is the same as that of the GPRS network.

The preceding figure shows the structure of the GPRS/UMTS network.


Specifications of SGSN9810 V900R010

Item Value (2.5G) Value (3G)

Maximum number of attached users 12 million 12 million

Maximum number of PDP contexts that can be activated simultaneously

22 million 22 million

Maximum packet data forwarding capability (pps)

1.5 million 8 million

Maximum packet data forwarding traffic (bit/s) 3 G 20 G


Hardware Platform of SGSN9810 V900R010

SGSN9810 V900R010 adopts hardware platform open standards telecom

architecture (OSTA) 2.0 of Huawei. Based on the ATCA technology, OSTA 2.0

features high rate, high availability, good expansibility, and good manageability.

High rate

OSTA 2.0 adopts high-speed serial data links and a switching structure to implement a

maximum bandwidth of 2.5 Tbit/s for data switching within a subrack.

High availability

OSTA 2.0 supports hot swap of all boards and subboards, and supports redundancy backup

of key components such as the power supply, fan, management module, and various

boards, to implement system reliability of 99.999%.

Good expansibility

OSTA 2.0 supports using interface boards to expand the interfaces of ATCA boards in a

subrack and supports inter-subrack cascading.

Good manageability

OSTA 2.0 adopts the standard management bus to manage the components in the system.


Software Platform of SGSN9810 V900R010

SGSN9810 V900R010 adopts the embedded software platform, carrier grade platform (CGP), which can be universally used by the CN products of Huawei. The CGP software platform can be used on different hardware platforms and operation systems, and is easy to operate and maintain.

Inter-hardware platformThe CGP software platform provides versatile hardware platform interfaces so that the application software at the upper layer can be run on different platforms. It also implements hardware device management irrelevant with the hardware platform.

Inter-operating systemThe CGP software platform shields different operating system interfaces at the lower layer by providing versatile virtual operating system application programming interfaces (VOSAPIs) for upper-layer applications.

Easy operation and maintenanceThe CGP software platform provides implementation mechanisms of functions such as operation and maintenance, alarm management, performance measurement, call/signaling trace, data backup, board switchover, and online loading for upper-layer applications.


Typical Configuration of SGSN9810 V900R010 （ 3G）

In the ATCA standard, the active and standby slots are paired as follows: slot 0 and slot 2, slot 1 and 3, slot 4 and slot 8, slot 5 and slot 9, slot 10 and 12, and slot 11 and slot 13. The EPUs must comply with this restriction because the EPUs use the update bus that requires the preceding pairing method according to the ATCA standard. The ECUs and OMUs do not use the update bus, and therefore, they do not need to comply with this restriction. To ensure that the EPUs comply with the restriction, the preceding paring method is recommended for the ECUs and OMUs.

Typical specifications: maximum SAU number: 2 million; maximum PDP context number: 2 million; maximum UMTS throughput: 2 Gbit/s; maximum GPRS throughput: 0.8 Gbit/s


Typical specifications: maximum SAU number: 2 million; maximum PDP context number: 2 million; maximum UMTS throughput: 2 Gbit/s; maximum GPRS throughput: 0.8 Gbit/s

0 1 2 3 4 5 6 7 8 9 10 11 12 13

USI

ETI

USI

ETI

PFI

PFI

TMI

TMI

PFI

PFI

PFI

PFI

PFI

PFI

OMU

ECU

OMU

ECU

EPU

EPU

SWU

SWU

EPU

EPU

EPU

EPU

EPU

EPU

SMU SMU

14 15


Typical Configuration of SGSN9810 V900R010 （ 2G）


Typical specifications: maximum SAU number: 2 million; maximum PDP context number: 2 million; maximum UMTS throughput: 2 Gbit/s/maximum GPRS throughput: 0.4 Gbit/s


Typical specifications: maximum SAU number: 2 million; maximum PDP context number: 2 million; maximum UMTS throughput: 2 Gbit/s/maximum GPRS throughput: 0.4 Gbit/s

0 1 2 3 4 5 6 7 8 9 10 11 12 13

USI

ETI

USI

ETI

ETI

ETI

TMI

TMI

ETI

ETI

ETI

PFI

ETI

PFI

OMU

ECU

OMU

ECU

ECU

ECU

SWU

SWU

ECU

ECU

ECU

EPU

ECU

EPU

SMU SMU

14 15


Question

What are the major specifications of the SGSN9810 V900R010 ATCA platform?


Chapter 2 SGSN9810 V900R010 System Chapter 2 SGSN9810 V900R010 System

StructureStructure

2.1 SGSN9810 V900R010 Hardware

Components

2.2 SGSN9810 V900R010 Logical Structure

2.3 SGSN9810 V900R010 System Bus Structure

2.4 SGSN9810 V900R010 Software Structure

2.5 SGSN9810 V900R010 Process Deployment



Learn about the overall structure of the SGSN9810


Learn about the process deployment on the SGSN9810



System Structure of the ATCA Subrack

Front view of the subrack1. Slot for a board2. Fan box (with an air intake vent)3. Slot for the SMM

Rear view of the subrack1. Air exhaust vent2. Slot for an interface board3. Cable trough4. PDB5. Slot for the SDM


Basic Dimensions Rack: 2200 mm (H) x 600 mm (W) x 800 mm (D)

A rack can be configured with three ATCA subracks.

Subrack:

14 U (H) x 19 inch (W)

Door thickness: 25 mm

Distance between the front cable rack and the

air intake vent: 100 mm

Distance between the back cable rack and the

air intake vent: 60 mm

Subrack depth: 390 mm

Boards:

Front board: 8 U (H) x 280 mm (D) x 30.48 mm

(W)

Back board: 8 U (H) x 70 mm (D) x 30.48 mm

(W)

Cabinet depth: 600 mm25 mm

100 mm Subrack depth: 390 mm

60 mm

85 mm 55 mm

Front door

Back door

Front cable rack

Back cable rack

Front board

Back board

Connector

Backplane


Basic Service Boards

Hardware Type

CPU Type Memory Storage Maximum Power Consumption

Board Name

UPBA2 Two Intel Xeon quad-core processors with low power consumption. Each quad-core processor supports a 12 MB level-2 cache and a 1333 MHz front side bus (FSB).

Six VLP DDR2 RDIMM memories with a total capacity of 24 GB, that is, 4 GB each

Two hot swappable 2.5-inch SAS hard disks, each with a capacity of 73 GB or 146 GB; configuration completed before delivery

170 W Operation and Maintenance Unit (OMU)

UPBA3 Two Intel Xeon quad-core processors with low power consumption. Each quad-core processor supports a 4 MB level-2 cache and a 1333 MHz FSB.

Six FBDIMM DDR2 memories with a total capacity of 24 GB, that is, 4 GB each

Two hot-swappable 2.5-inch SAS hard disks

One 64 GB flash hard disk

170 W Enhanced Control-Plane Unit (ECU)

(combining the functions of processes such as USPP, UICP, USGP, UGBP, UFEU, USS7, and UCDR on the CPCI platform)

MSPB One RMI XLR732 eight-core processor with 32 VCPUs, a dominant frequency of 950 MHz, and a 2 MB level-2 cache.

8 GB One 1 GB CF card

Four cores for running Liunx

Four cores for running VXWorks

125 W Enhanced Packet forward Unit (EPU) (combining the functions of the GTP, UGFU, and ULIP on the CPCI platform)


Basic Auxiliary BoardsBoard Type Description Board Name

Switching network board

It provides basic Layer 2 switching functions for GE interfaces on the base plane and fabric plane inside a subrack and between subracks. The basic features include:

Supporting interface binding

Supporting IEEE 802.3x auto-sensing and traffic control on all Ethernet interfaces

Supporting automatic learning of up to 16384 MAC addresses

Supporting 4096 802.1Q VLANs

Supporting 802.1D STP, MSTP, and RSTP

Supporting HGMP

Supporting device stacking/cascading

Supporting priority (8COS) queues on outbound interfaces

Supporting 9 KB jumbo frames (B02)

Switch Unit (SWU)

Board in the back slot of the SWU

It connects cables between subracks. It can be installed with a clock subboard to provide a Stratum-2 clock.

Switch Interface (SWI)

Subrack management unit

It manages and maintains the components in the subrack. The basic functions include:

Subrack configuration, SWU configuration, status information collection and fault detection of the SWU, power-on and power-off control and power supply monitoring, slot verification, heat dissipation monitoring, fan monitoring and control, and power supply monitoring and control.

Subrack Manage & Maintenance Unit (SMM)

Subrack data unit It stores device files and is located in the back slot of the SMM. Subrack Data Manage (SDM)

Board in the back slot of the OMU

It can be installed with various types of subboard. On the SGSN9810, only the GE subboard or precise time subboard is used, and the subboard is installed in the back slot of the OMU. The GE subboard provides maintenance interfaces and the precise time subboard provides precise time for the SGSN9810 connected to no NTP server.

Universal Service Interface (USI)


Basic Auxiliary BoardsBoard Type Description Board Name

Board in the back slot of the narrowband interface processing board

It is installed with the E1 interface subboard and the channelized STM-1 subboard to provide E1 interfaces for the Gb interface, SS7 interface, and later IP-over-E1 interface. It is installed in the back slot of the ECU.

E1/TI Interface (ETI)

Board in the back slot of the broadband interface processing board

It, together with the broadband interface processing board, implements the access to broadband interfaces such as ATM, POS, and GE interfaces. It can be installed with two interface processing subboards that can be ATM/POS interface processing subboards, FE/GE electrical interface processing subboards, or GE optical interface processing subboards. The hardware of this board is the same as that of the ETI, whereas the logical functions provided by the two boards are different. This board is installed in the back slot of the EPU.

Packet Forward Interface (PFI)

GE interface subboard in the back slot of the OMU

It is installed on the OMB to provide GE interfaces. Operation Interface PMCCard (OIC)

Precise time subboard It is installed on the OMB to provide precise time for the system. Timer PMCCard (TMC)

Clock subboard It is installed on the SWB to provide a Stratum-2 clock for the system. Clock PMCCard (CLC)

E1 interface subboard It is installed on the EPB to provide E1 interfaces. E1/T1 PMCCard (ETC)

Channelized STM subboard

It is installed on the EPB to provide channelized STM-1 interfaces (and channelized STM-4 interfaces later)

Channel STM PMCCard (CSC)

ATM interface subboard

It is installed on the PIB to provide ATM interfaces. (One ATM interface subboard can provide four 155 Mbit/s ATM interfaces, or two 622 Mbit/s ATM interfaces and two 155 Mbit/s ATM interfaces.)

ATM Interface PMCCard (AIC)

Ethernet electrical interface subboard

It is installed on the PIB to provide 10M/100M/1000M auto-sensing Ethernet electrical interfaces.

Ethernet Electric Interface PMCCard (EEC)

Ethernet optical interface subboard

It is installed on the PIB to provide 1000M auto-sensing Ethernet optical interfaces.

Ethernet Fiber Interface PMCCard (EFC)


Typical Configuration of SGSN9810 V900R010 ATCA Boards

In each subrack, there are 14 vertical slots numbered 0 to 13 and two horizontal slots.

Two SMMs, two SDMs, two SWUs, and two SWIs must be configured in each subrack to

implement active/standby switchovers.

The two SMMs and the two SDMs are fixedly installed at the bottom of each subrack. The SMMs

and SDMs are inserted respectively in front and back slots in pairs. The SWUs and SWIs are

fixedly configured in front slots 6 and 7 and back slots 6 and 7 of each subrack.

Basic subrackBasic subrack Service subrackService subrack


SGSN9810 V900R010 Logical Structure

According to logical functions, the SGSN9810 can be divided into six subsystems: the switching subsystem, packet data transfer subsystem, service processing subsystem, charging subsystem, OM subsystem, and clock subsystem.


SGSN9810 V900R010 Subsystems

Name Function Hardware

Switching subsystem It provides communications between boards and connects subracks.

SWU/TMI/TSI

Packet data transfer

subsystem

It provides Gn/Gp and Iu-PS interfaces and supports routing and forwarding of interface data.

EPU

Service processing subsystem

It implements link layer management of narrowband signaling (MTP2 and FR), SS7 protocol processing, and other upper-layer protocols and functions such as MAP, MM, SM, CAMEL, LCS, and lawful interception.

ECU

Charging subsystem It collects, stores, encodes, and sends CDRs. ECU

OM subsystem It provides external OM interfaces and

implements functions such as system

maintenance, configuration, performance

measurement, and alarm and log generation.

OMU

Clock subsystem It provides Stratum-2 and Stratum-3 clocks. TMI in the back slot of the SWU


SGSN9810 V900R010 System Bus Structure

The system bus organically connects the components of the entire system to implement information exchange and communications between subsystems.As shown in the following figure, SGSN9810 V900R010 has three types of system buses.IPMB bus in redBase bus in blackFabric bus in blue

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SWU

SWI

SWU

SWI

FAN FAN

SMM

SDM

SMM

SDM

PDBSerial

Fabric

BASE

IPMB


IPMB BusThe IPMB bus is the system management bus in an OSTA 2.0 subrack. It connects all modules and boards in the subrack. Through the IPMB bus, the subrack management module SSM uniformly manages hardware in the subrack. The connection of the IPMB bus is as follows.

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SWU

SWI

SWU

SWI

FAN FAN

SMM

SDM

SMM

SDM

PDBSerialIPMB

The IPMB bus is the management bus of the entire system and connects all modules and boards. The SMM is the core of the entire management system. It communicates with the IPMCs of the board, fan box, and PDB to deliver monitoring commands and report messages through the IPMB bus.

The system monitors and manages each Field Replaceable Unit (FRU) through the connection between the SMM and the IPMB bus. For example, the system detects the board temperature/voltage/reset, fan status/speed, and voltage/current of the PDB. If any abnormality is detected, the internal IPMC of the FRU reports alarms to the SMM.


Base BusThe base bus is mainly used as the channel for information about software installation, alarm management, and maintenance on the control plane.The SWU is the switching core of the entire base plane. It implements information exchange on the system control plane and provides cascading interfaces on the base plane. All boards are connected to the SWU through the base plane. Through the SWU, control plane information is exchanged between boards. The following figure shows the connection of the base bus.Connection of the base bus.

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SWU

SWI

SWU

SWI

SMM

SDM

SMM

SDM

BASE


Fabric Bus

The fabric bus provides the data channel for the service plane and carries information about services. The SWU is the switching core of the fabric bus. It exchanges service plane information exchange and provides cascading interfaces. All processor boards are connected to the SWU through the fabric bus and exchange service information through the SWU. The following figure shows the connection of the fabric bus.Connection of the fabric bus

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SPM

UPB

USI

SWU

SWI

SWU

SWI

Fabric


SGSN9810 V900R010 Software Structure

The SGSN9810 software adopts the distributed architecture. Functional modules are distributed on different boards and can be configured flexibly according to the network topology.

According to positions, the SGSN9810 software can be divided into host software and daemon software.

Overall software structure of SGSN9810 V900R010

Operating system

Middleware

Communications management

Protocol processing

Service processing

Operating system

Database software

Performance managementmanagement

Configuration management managementAlarm management management

Maintenance management

Performance management

Configuration management

Alarm magement

Maintenance management WebUI

LMTDatabase

Device management

Device management

Host software Daemon software

Signaling interface and bearer


SGSN9810 V900R010 Processes

Name Function Board Remarks

Operation and Maintenance Process (OMP)

It implements product adaptation and proxy of the CGP OM part.

OMU Only one pair of active and standby OMPs can be configured for the entire system.

User information Index Process (UIP)

It mainly processes the functions of the SIPU.

ECU Only one pair of active and standby UIPs can be configured for the entire system.

Charging Data Process (CDP)

It stores CDRs and provides the Ga interface.

ECU -

License Center Process (LCP)

It functions as the system control center by implementing license control and heartbeat handshakes through the Gb interface.

ECU Only one pair of active and standby LCPs can be configured for the entire system.

Signaling Processing Process (SPP)

It processes signaling. ECU -

GB interface Process (GBP)

It processes signaling and data of the Gb interface, manages resources and alarms, and supports Gb over IP.

ECU -


SGSN9810 V900R010 Processes

Name Function Board Remarks

SiGtran Process (SGP) It processes the control plane signaling and SIGTRAN protocol stack of the Iu interface.

ECU -

Logical Link handle Process (LLP)

It mainly handles the MTP link and the FR link.

ECU -

Packet Forward Process (PFP)

It forwards packets. EPU -

GPRS Tunnel Protocol (GTP) It processes the GTP protocol. EPU -

User plane Management Process (UMP)

It mainly manages the user plane platform and the device.

EPU -

Lawful Interception Process (LIP)

It controls lawful interception. EPU Only one pair of active and standby LIPs can be configured for the entire system.

Monitor (MON) It monitors processes. OMU, ECU, and EPU

It is a CGP process and is invisible on the LMT.

IO Management Unit (IMU) It provides functions such as device resource management of the board, communications proxy of the OMU, and service process loading.

OMU, ECU, and EPU

It is a CGP process.

Rack Management Unit (RMU)

It manages active and standby service process arbitration.

OMU, ECU, and EPU

It is a CGP process.


Process Deployment

Process groupA process group binds multiple processes of several types according to a ratio, for example, 8 SPPs + 8 GBPs + 8 SGPs + 8 LLPs + CDP.

SGSN9810 process groups:ECUGP, EPUGP, LIPGP, LCPGP, UIPGP, and OMPGP

Processes in each process group:ECUGP: SPP/GBP/SGP/LLP/CDP (8 SPPs + 8 GBPs + 8 SGPs + 8 LLPs + CDP)EPUGP: GTP/PCP/UMP (8 GTPs + PCP + UMP)LIPGP: LIP LCPGP: LCP UIPGP: UIP OMPGP: OMP


Question

Which types of board does SGSN9810 V900R010 provide and what are the functions of

the boards?

What are the buses on the ATCA platform and what are the functions of each bus?

Which types of process group does SGSN9810 V900R010 provide?


Chapter 3 SGSN9810 V900R010 Software Chapter 3 SGSN9810 V900R010 Software

InstallationInstallation

3.1 Installation Method

3.2 Installation Principle

3.3 Basic Installation Procedure



Learn about the software installation procedure of SGSN9810 V900R010.


Installation Method

According to the positions where the source files are stored, software installation methods can be divided into two types.

Installing software and data from the local storage media of the OMU, such as the hard disk of the OMU, to the memory of the board. In this case, all source files to be installed are stored in the local storage media of the OMU.

Installing software and data from the local storage media of each board to the memory of the board. In this case, the source files to be installed are stored in the local storage media of each board.

According to the types of file to be installed, installation methods can be divided into operating system file installation and host program file installation.

Operating system file installation refers to installing files related to the operating system from the local storage media of each board or network to the memory of the board.

Host program file installation refers to installing the service programs of the SGSN9810 from the local storage media of each board to the memory of the board or from the OMU to the local storage media and then to the local memory

According to the positions where the source files are stored, software installation methods can be divided into two types.

Installing software and data from the local storage media of the OMU, such as the hard disk of the OMU, to the memory of the board. In this case, all source files to be installed are stored in the local storage media of the OMU.

Installing software and data from the local storage media of each board to the memory of the board. In this case, the source files to be installed are stored in the local storage media of each board.

According to the types of file to be installed, installation methods can be divided into operating system file installation and host program file installation.

Operating system file installation refers to installing files related to the operating system from the local storage media of each board or network to the memory of the board.

Host program file installation refers to installing the service programs of the SGSN9810 from the local storage media of each board to the memory of the board or from the OMU to the local storage media and then to the local memory

OMU

Memory

Local storage media

load

Base bus

Write

Read

Board

Intra-board data bus


Installation Principle

By using the base bus, the board communicates with the OMU through the SWU, requesting for system software installation. Two planes are used during this course, that is, base plane 1 and base plane 2. Base plane 2 is used only after the communications on base plane 1 fail.

By using the base bus, the board communicates with the OMU through the SWU, requesting for system software installation. Two planes are used during this course, that is, base plane 1 and base plane 2. Base plane 2 is used only after the communications on base plane 1 fail.

OMU/INU

Base bus

swu

swu

board

Base plane 2

Base plane 1

Base bus Base bus

Base bus


Basic Installation Procedure

After the subrack is powered on or reset, each board in the subrack automatically starts the local BIOS program. The BIOS program determines whether to start the operating system locally or from the network according to the start mode.

If the BIOS program determines to start the operating system locally, the BIOS program checks whether the operating system has failed to be started locally for over three consecutive times. If yes, the BIOS program starts the operating system from the network to automatically repair the operating system. Otherwise, the BIOS program installs and starts the operating system from the local storage media.

If the BIOS program determines to start the operating system from the network, the BIOS program installs a network bootstrap program (NBP) for instructing the operating system and runs the NBP. The NBP reads the subrack number, slot number, and hardware version of the local board, and sends an installation request to the OMU. The OMU reads configuration data according to the reported subrack number, slot number, and hardware version, and sends the related operating system files through TFTP to the NBP. After receiving the operating system files, the NBP starts the operating system.

After being started, the operating system automatically runs a platform management program. This program interacts with the OMU to report the CRCs of the program files and data files in the local storage media. (If the local storage media does not exist or contains no file, the reported CRC is null.) The OMU compares the reported CRCs with the CRCs of the corresponding files on the local storage media. If the CRCs are different, the OMU instructs the board to install the corresponding files. Then, the board installs the files to the local storage media. (If the local storage media does not exist, the files are installed in the local memory.) After the installation is complete, related programs are run.

After the subrack is powered on or reset, each board in the subrack automatically starts the local BIOS program. The BIOS program determines whether to start the operating system locally or from the network according to the start mode.

If the BIOS program determines to start the operating system locally, the BIOS program checks whether the operating system has failed to be started locally for over three consecutive times. If yes, the BIOS program starts the operating system from the network to automatically repair the operating system. Otherwise, the BIOS program installs and starts the operating system from the local storage media.

If the BIOS program determines to start the operating system from the network, the BIOS program installs a network bootstrap program (NBP) for instructing the operating system and runs the NBP. The NBP reads the subrack number, slot number, and hardware version of the local board, and sends an installation request to the OMU. The OMU reads configuration data according to the reported subrack number, slot number, and hardware version, and sends the related operating system files through TFTP to the NBP. After receiving the operating system files, the NBP starts the operating system.

After being started, the operating system automatically runs a platform management program. This program interacts with the OMU to report the CRCs of the program files and data files in the local storage media. (If the local storage media does not exist or contains no file, the reported CRC is null.) The OMU compares the reported CRCs with the CRCs of the corresponding files on the local storage media. If the CRCs are different, the OMU instructs the board to install the corresponding files. Then, the board installs the files to the local storage media. (If the local storage media does not exist, the files are installed in the local memory.) After the installation is complete, related programs are run.

Program and data files


Chapter 4 SGSN9810 V900R010 Service Chapter 4 SGSN9810 V900R010 Service

ProcessingProcessing

4.1 2G Attach

4.2 2G Activation

4.3 2G Data Transmission

4.4 3G Attach

4.5 3G Activation

4.6 3G Data Transmission



Learn about the signaling processing procedures of

SGSN9810 V900R010.


Procedure Introduction

This chapter takes the most simple attach, activation, and data transmission procedures as examples to describe the interaction between the internal processes of the SGSN9810 in each procedure. The processing of the messages in other procedures is similar to the processing of the messages in the basic procedures except one more interaction process.

MS SGSN HLR GGSN

Attach RequestAttach RequestUpdate LocationUpdate Location

Update Location AckUpdate Location Ack

Attach AcceptAttach Accept

Activate PDP Context RequestActivate PDP Context RequestCreate PDP Context RequestCreate PDP Context Request

Create PDP Context ResponseCreate PDP Context ResponseActivate PDP Context AcceptActivate PDP Context Accept

Uplink MessageUplink MessageUplink MessageUplink Message

Downlink MessageDownlink MessageDownlink MessageDownlink Message


Signaling Flow in the Attach Procedure Initiated by the GPRS Access User Using the E1 Bearer

ECU

SPP

GBPLLP

Gb

4 3

5.Update Location

1.AttachRequest

Gr

7 8

2

9

10.AttachAccept

6.Update Location Ack

1. After receiving an Attach Request message from the interface board, the LLP processes the FR protocol stack of the Gb interface, strips the FR protocol header, and sends the message to the GBP. (The LLP functions as the UFEU of the CPCI platform.)

2. After receiving the Attach Request message, the GBP processes the NS, BSSGP, and LLC protocol stacks of the Gb interface, and assigns a PDP context to the user. The GBP strips the NS, BSSGP, and LLC protocol headers layer by layer to obtain the Layer 3 information in the Attach Request message, and then sends the message to the SPP. (The GBP functions as the UGBI of the CPCI platform.)

3. After receiving the Attach Request message, the SPP implements the MM procedure. The SPP assigns a PDP context to the user and initiates the location update procedure to the HLR. The SPP constructs an Update Location message, encapsulates the message with the MAP, TCAP, and SCCP protocols, and sends the message to the LLP. (The SPP functions as the USPU of the CPCI platform.)

4. After receiving the Update Location message, the LLP encapsulates the message with the MTP3 protocol, selects a link, and sends the message to the HLR. (The LLP functions as the USS7 of the CPCI platform.)

5. The Update Location message is sent to the HLR.6. After receiving an Update Location Ack message from the HLR, the LLP strips the MTP3

protocol header and sends the message to the SPP. (The LLP functions as the USS7 of the CPCI platform.)

7. After receiving the Update Location Ack message, the SPP strips the MAP, TCAP, and SCCP protocol headers, constructs an Attach Accept message, and sends the message to the GBP. (The SPP functions as the USPU of the CPCI platform.)

8. After receiving the Attach Accept message, the GBP encapsulates the LLC, BSSGP, and NS protocol headers, selects a link, and sends the message to the LLP. (The GBP functions as the UGBI of the CPCI platform.)

9. After receiving the Attach Accept message, the LLP encapsulates the FR protocol header and sends the message to the interface board. (The LLP functions as the UFEU of the CPCI platform.)

10. The Attach Accept message is sent to the user.


Signaling Flow in the Attach Procedure Initiated by the GPRS Access User Using the IP Bearer

EPU

PFP

ECU

SGP

SPP

GBP

Gb

9 3

1.AttachRequest

Gr

4 10

12.AttachAccept

21158

6.UpdateLocation

7.UpdateLocation Ack

1. After receiving an Attach Request message, the PFP searches the forwarding table, strips the UDP, IP, and MAC protocol headers, and sends the message to the GBP. (The PFP functions as the UGFU of the CPCI platform.)

2. After receiving the Attach Request message, the GBP processes the NS, BSSGP, and LLC protocol stacks of the Gb interface, and assigns a PDP context to the user. The GBP strips the NS, BSSGP, and LLC protocol headers layer by layer to obtain the Layer 3 information in the Attach Request message, and then sends the message to the SPP. (The GBP functions as the UGBI of the CPCI platform.)

3. After receiving the Attach Request message, the SPP implements the MM procedure. The SPP assigns a PDP context to the user and initiates the location update procedure to the HLR. The SPP constructs an Update Location message, encapsulates the message with the MAP, TCAP, and SCCP protocols, and sends the message to the SGP. (The SPP functions as the USPU of the CPCI platform.)

4. After receiving the Update Location message, the SGP encapsulates the message with the M3UA and SCTP protocols, selects a link, and sends the message to the PFP. (The SGP functions as the USIG of the CPCI platform.)

5. After receiving the Update Location message, the PFP encapsulates the IP and MAC protocol headers, and sends the message to the HLR.

6. The Update Location message is sent to the HLR.7. After receiving an Update Location Ack message from the HLR, the PFP strips the IP and MAC

protocol headers, and sends the message to the SGP. (The PFP functions as the UGFU of the CPCI platform.)

8. After receiving the Update Location Ack message, the SGP strips the M3UA and SCTP protocol headers, and sends the message to the SPP. (The SGP functions as the USIG of the CPCI platform.)

9. After receiving the Update Location Ack message, the SPP strips the MAP, TCAP, and SCCP protocol headers, constructs an Attach Accept message, and sends the message to the GBP. (The SPP functions as the USPU of the CPCI platform.)

10. After receiving the Attach Accept message, the GBP encapsulates the LLC, BSSGP, and NS protocol headers, selects a link, and sends the message to the PFP. (The GBP functions as the UGBI of the CPCI platform.)

11. After receiving the Attach Accept message, the PFP encapsulates the UDP, IP, and MAC protocol headers, and sends the message to the user. (The PFP functions as the UGFU of the CPCI platform.)



Signaling Flow in the PDP Context Activation Procedure Initiated by the GPRS Access User Using the E1 Bearer

EPU ECU

Gb

10 3

Gn

11

2

GTP SPP

GBPLLPPFP

1.Activate PDPContext Request

12.Activate PDPContext Accept

4

9

5 8

6.Create PDPContextRequest

7.CreatePDP Context

Response

1. After receiving an Activate PDP Context Request message from the interface board, the LLP processes the FR protocol stack of the Gb interface, strips the FR protocol header, and sends the message to the GBP. (The LLP functions as the UFEU of the CPCI platform.)

2. After receiving the Activate PDP Context Request message, the GBP processes the NS, BSSGP, and LLC protocol stacks of the Gb interface. The GBP strips the NS, BSSGP, and LLC protocol headers layer by layer to obtain the Layer 3 information in the Activate PDP Context Request message, and then sends the message to the SPP. (The GBP functions as the UGBI of the CPCI platform.)

3. After receiving the Activate PDP Context Request message, the SPP implements the SM procedure. The SPP assigns a PDP context to the user and initiates the PDP context creation procedure to the GGSN. The SPP constructs a Create PDP Context Request message and sends the message to the GTP. (The SPP functions as the USPU of the CPCI platform.)

4. After receiving the Create PDP Context Request message, the GTP assigns a PDP context to the user, encapsulates the GTP-C and UDP protocol headers, and sends the message to the PFP. (The GTP functions as the UGTP of the CPCI platform.)

5. After receiving the Create PDP Context Request message, the PFP encapsulates the IP and MAC protocol headers, and sends the message to the GGSN. (The PFP functions as the UGFU of the CPCI platform.)

6. The Create PDP Context Request message is sent to the GGSN.7. After receiving a Create PDP Context Response message, the PFP searches the forwarding table, strips the IP and MAC protocol headers, and sends the message

to the GTP. (The PFP functions as the UGFU of the CPCI platform.)8. After receiving the Create PDP Context Response message, the GTP strips the GTP-C and UDP protocol headers, and sends the message to the SPP. (The GTP

functions as the UGTP of the CPCI platform.)9. After receiving the Create PDP Context Response message, the SPP constructs an Activate PDP Context Accept message and sends the message to the GBP.

(The SPP functions as the USPU of the CPCI platform.)10. After receiving the Activate PDP Context Accept message, the GBP encapsulates the LLC, BSSGP, and NS protocol headers, selects a link, and sends the

message to the LLP. (The GBP functions as the UGBI of the CPCI platform.)11. After receiving the Activate PDP Context Accept message, the LLP encapsulates the FR protocol header and sends the message to the interface board. (The LLP

functions as the UFEU of the CPCI platform.)12. The Activate PDP Context Accept message is sent to the user.


Signaling Flow in the PDP Context Activation Procedure Initiated by the GPRS Access User Using the IP Bearer

EPU

PFP

ECU

GTP

SPP

GBP

Gb

9

3

Gn

4

10

211

58




7.CreatePDP Context

Response

1. After receiving an Activate PDP Context Request message, the PFP searches the forwarding table, strips the IP and UDP protocol headers, and sends the message to the GBP. (The PFP functions as the UGFU of the CPCI platform.)

2. After receiving the Activate PDP Context Request message, the GBP processes the NS, BSSGP, and LLC protocol stacks of the Gb interface. The GBP strips the NS, BSSGP, and LLC protocol headers layer by layer to obtain the Layer 3 information in the Activate PDP Context Request message, and then sends the message to the SPP. (The GBP functions as the UGBI of the CPCI platform.)

3. After receiving the Activate PDP Context Request message, the SPP implements the SM procedure. The SPP assigns a PDP context to the user and initiates the PDP context creation procedure to the GGSN. The SPP constructs a Create PDP Context Request message and sends the message to the GTP. (The SPP functions as the USPU of the CPCI platform.)



6. The Create PDP Context Request message is sent to the GGSN.7. After receiving a Create PDP Context Response message, the PFP searches the forwarding table,

strips the IP and MAC protocol headers, and sends the message to the GTP. (The PFP functions as the UGFU of the CPCI platform.)

8. After receiving the Create PDP Context Response message, the GTP strips the GTP-C and UDP protocol headers, and sends the message to the SPP. (The GTP functions as the UGTP of the CPCI platform.)

9. After receiving the Create PDP Context Response message, the SPP constructs an Activate PDP Context Accept message and sends the message to the GBP. (The SPP functions as the USPU of the CPCI platform.)

10. After receiving the Activate PDP Context Accept message, the GBP encapsulates the LLC, BSSGP, and NS protocol headers, selects a link, and sends the message to the PFP. (The GBP functions as the UGBI of the CPCI platform.)

11. After receiving the Activate PDP Context Accept message, the PFP encapsulates the UDP, IP, and MAC protocol headers, and sends the message to the user. (The PFP functions as the UGFU of the CPCI platform.)

12. The Activate PDP Context Accept message is sent to the user.


Data Transmission Flow for the GPRS Access User Using the E1 Bearer

EPU ECU

GbGn

GBP LLPPFP

1.UplinkMessage

5.DownlinkMessage

4.UplinkMessage

23

6 7

8.DownlinkMessage

1. After receiving an uplink message from the interface board, the LLP processes the FR protocol stack of the Gb interface, strips the FR protocol header, and sends the message to the GBP. (The LLP functions as the UFEU of the CPCI platform.)

2. After receiving the uplink message, the GBP processes the NS, BSSGP, LLC, and SNDCP protocol stacks of the Gb interface. The GBP strips the NS, BSSGP, LLC, and SNDCP protocol headers layer by layer, and sends the message to the PFP. (The GBP functions as the UGBI of the CPCI platform.)

2. After receiving the uplink message, the PFP encapsulates the GTP-U, UDP, IP, and MAC protocol headers, and sends the message to the GGSN. (The PFP functions as the UGFU of the CPCI platform.)

4. The uplink message is sent to the GGSN.5. After receiving a downlink message from the GGSN, the PFP searches the forwarding table, strips the GTP-U, UDP, IP, and

MAC protocol headers, and sends the message to the GBP. (The PFP functions as the UGFU of the CPCI platform.)6. After receiving the downlink message, the GBP encapsulates the SNDCP, LLC, BSSGP, and NS protocol headers, selects a

link, and sends the message to the LLP. (The GBP functions as the UGBI of the CPCI platform.)7. After receiving the downlink message, the LLP encapsulates the FR protocol header and sends the message to the interface

board. (The LLP functions as the UFEU of the CPCI platform.)8. The downlink message is sent to the user.


Data Transmission Flow for the GPRS Access User Using the IP Bearer

EPU

PFP

ECU

GBP

GbGn

2736

1.UplinkMessage5.Downlink

Message 4.UplinkMessage

8.DownlinkMessage

1. After receiving an uplink message from the interface board, the PFP searches the forwarding table, strips the UDP, IP, and MAC protocol headers, and sends the message to the GBP. (The PFP functions as the UGFU of the CPCI platform.)

2. After receiving the uplink message, the GBP processes the NS, BSSGP, LLC, and SNDCP protocol stacks of the Gb interface. The GBP strips the NS, BSSGP, LLC, and SNDCP protocol headers layer by layer, and sends the message to the PFP. (The GBP functions as the UGBI of the CPCI platform.)

2. After receiving the uplink message, the PFP encapsulates the GTP-U, UDP, IP, and MAC protocol headers, and sends the message to the GGSN. (The PFP functions as the UGFU of the CPCI platform.)

4. The uplink message is sent to the GGSN.5. After receiving a downlink message from the GGSN, the PFP

searches the forwarding table, strips the GTP-U, UDP, IP, and MAC protocol headers, and sends the message to the GBP. (The PFP functions as the UGFU of the CPCI platform.)

6. After receiving the downlink message, the GBP encapsulates the SNDCP, LLC, BSSGP, and NS protocol headers, selects a link, and sends the message to the PFP. (The GBP functions as the UGBI of the CPCI platform.)

7. After receiving the downlink message, the PFP encapsulates the UDP, IP, and MAC protocol headers, and sends the message to the user. (The PFP functions as the UGFU of the CPCI platform.)

8. The downlink message is sent to the user.


Signaling Flow in the Attach Procedure Initiated by the UMTS Access User Using the ATM Bearer

EPU

PFP

ECU

SGP

SPP

Iu

9 3

1.AttachRequest

Gr

4 10

12.AttachAccept

21158

6.UpdateLocation


1. After receiving an Attach Request message, the PFP searches the forwarding table, strips the ATM protocol header, and sends the message to the SGP. (The PFP functions as the UGFU of the CPCI platform.)

2. After receiving the Attach Request message, the SGP processes the SAAL and MTP3B protocol stacks of the Iu interface, strips the SAAL and MTP3B protocol headers, and sends the message to the SPP. (The SGP functions as the USIG of the CPCI platform.)

3. After receiving the Attach Request message, the SPP processes the SCCP and RANAP protocol stacks and implements the MM procedure. The SPP assigns a PDP context to the user and initiates the location update procedure to the HLR. The SPP constructs an Update Location message, encapsulates the message with the MAP, TCAP, and SCCP protocols, and sends the message to the SGP. (The SPP functions as the USPU of the CPCI platform.)


5. After receiving the Update Location message, the PFP encapsulates the IP and MAC protocol headers, and sends the message to the HLR.)6. The Update Location message is sent to the HLR.

7. After receiving an Update Location Ack message from the HLR, the PFP searches the forwarding table, strips the IP and MAC protocol headers, and sends the message to the SGP. (The PFP functions as the UGFU of the CPCI platform.)


7. After receiving the Update Location Ack message, the SPP strips the MAP, TCAP, and SCCP protocol headers, constructs an Attach Accept message, and sends the message to the SGP. (The SPP functions as the USPU of the CPCI platform.)

10. After receiving the Attach Accept message, the SGP encapsulates the MTP3B and SAAL protocol headers, selects a link, and sends the message to the PFP. (The SGP functions as the USIG of the CPCI platform.)

11. After receiving the Attach Accept message, the PFP encapsulates the ATM protocol header and sends the message to the user. (The PFP functions as the UGFU of the CPCI platform.)


For the Gr interface, only the signaling flow in the case of the IP bearer is described. The signaling flow in the case of the E1 bearer is the same as the signaling flow in the 2G system.

For the Gr interface, only the signaling flow in the case of the IP bearer is described. The signaling flow in the case of the E1 bearer is the same as the signaling flow in the 2G system.


Signaling Flow in the Attach Procedure Initiated by the UMTS Access User Using the IP Bearer

EPU

PFP

ECU

SGP

SPP

Iu

9 3

1.AttachRequest

Gr

4 10

12.AttachAccept

21158

6.UpdateLocation


1. After receiving an Attach Request message, the PFP searches the forwarding table, strips the IP and MAC protocol headers, and sends the message to the SGP. (The PFP functions as the UGFU of the CPCI platform.)

2. After receiving the Attach Request message, the SGP processes the M3UA and SCTP protocol stacks of the Iu interface, strips the M3UA and SCTP protocol headers, and sends the message to the SPP. (The SGP functions as the USIG of the CPCI platform.)

3. After receiving the Attach Request message, the SPP processes the SCCP and RANAP protocol stacks and implements the MM procedure. The SPP assigns a PDP context to the user and initiates the location update procedure to the HLR. The SPP constructs an Update Location message, encapsulates the message with the MAP, TCAP, and SCCP protocols, and sends the message to the SGP. (The SPP functions as the USPU of the CPCI platform.)


5. After receiving the Update Location message, the PFP encapsulates the IP and MAC protocol headers, and sends the message to the HLR.6. The Update Location message is sent to the HLR.

7. After receiving an Update Location Ack message from the HLR, the PFP searches the forwarding table, strips the IP and MAC protocol headers, and sends the message to the SGP. (The PFP functions as the UGFU of the CPCI platform.)


9. After receiving the Update Location Ack message, the SPP strips the MAP, TCAP, and SCCP protocol headers, constructs an Attach Accept message, encapsulates the RANAP, SCCP, and L3IF protocol headers, and sends the message to the SGP. (The SPP functions as the USPU of the CPCI platform.)

10. After receiving the Attach Accept message, the SGP encapsulates the M3UA and SCTP protocol headers, selects a link, and sends the message to the PFP. (The SGP functions as the USIG of the CPCI platform.)

11. After receiving the Attach Accept message, the PFP encapsulates the IP and MAC protocol headers, and sends the message to the user. (The PFP functions as the UGFU of the CPCI platform.)


The signaling flow in the case of the IP bearer and the signaling flow in the case of the ATM bearer are the same except that the encapsulated protocol headers are different.



Signaling Flow in the PDP Context Activation Procedure Initiated by the UMTS Access User Using the ATM Bearer

1. After receiving an Activate PDP Context Request message, the PFP searches the forwarding table, strips the ATM protocol header, and sends the message to the SGP. (The PFP functions as the UGFU of the CPCI platform.)

2. After receiving the Activate PDP Context Request message, the SGP processes the SAAL and MTP3B protocol stacks of the Iu interface. The SGP strips the SAAL and MTP3B protocol headers, and sends the message to the SPP. (The SGP functions as the USIG of the CPCI platform.)

3. After receiving the Activate PDP Context Request message, the SPP processes the RANAP and SCCP protocol stacks, and implements the SM procedure. The SPP assigns a PDP context to the user and initiates the PDP context creation procedure to the GGSN. The SPP constructs a Create PDP Context Request message and sends the message to the GTP. (The SPP functions as the USPU of the CPCI platform.)



6. The Create PDP Context Request message is sent to the GGSN.7. After receiving a Create PDP Context Response message from the GGSN, the PFP searches the

forwarding table, strips the IP and MAC protocol headers, and sends the message to the GTP. (The PFP functions as the UGFU of the CPCI platform.)


9. After receiving the Create PDP Context Response message, the SPP constructs an Activate PDP Context Accept message, encapsulates the RANAP and SCCP protocol headers, and sends the message to the SGP. (The GTP functions as the USPU of the CPCI platform.)

10. After receiving the Activate PDP Context Accept message, the SGP encapsulates the MTP3B and SAAL protocol headers, selects a link, and sends the message to the PFP. (The SGP functions as the USIG of the CPCI platform.)

11. After receiving the Activate PDP Context Accept message, the PFP encapsulates the ATM protocol header and sends the message to the user. (The PFP functions as the UGFU of the CPCI platform.)


EPU

PFP

ECU

GTP

SPP

SGP

Gb

9

3

Gn

4

10

211

58




7.CreatePDP Context

Response


Signaling Flow in the PDP Context Activation Procedure Initiated by the UMTS Access User Using the IP Bearer

1. After receiving an Activate PDP Context Request message, the PFP searches the forwarding table, strips the IP and MAC protocol headers, and sends the message to the SGP. (The PFP functions as the UGFU of the CPCI platform.)

2. After receiving the Activate PDP Context Request message, the SGP processes the M3UA and SCTP protocol stacks of the Iu interface. The SGP strips the M3UA and SCTP protocol headers, and sends the message to the SPP. (The SGP functions as the USIG of the CPCI platform.)

3. After receiving the Activate PDP Context Request message, the SPP processes the RANAP and SCCP protocol stacks, and implements the SM procedure. The SPP assigns a PDP context to the user and initiates the PDP context creation procedure to the GGSN. The SPP constructs a Create PDP Context Request message and sends the message to the GTP. (The SPP functions as the USPU of the CPCI platform.)



6. The Create PDP Context Request message is sent to the GGSN.7. After receiving a Create PDP Context Response message from the GGSN, the PFP searches the

forwarding table, strips the IP and MAC protocol headers, and sends the message to the GTP. (The PFP functions as the UGFU of the CPCI platform.)


9. After receiving the Create PDP Context Response message, the SPP constructs an Activate PDP Context Accept message, encapsulates the RANAP and SCCP protocol headers, and sends the message to the SGP. (The GTP functions as the USPU of the CPCI platform.)

10. After receiving the Activate PDP Context Accept message, the SGP encapsulates the M3UA and SCTP protocol headers, selects a link, and sends the message to the PFP. (The SGP functions as the UGBI of the CPCI platform.)

11. After receiving the Activate PDP Context Accept message, the PFP encapsulates the IP and MAC protocol headers, and sends the message to the user. (The PFP functions as the UGFU of the CPCI platform.)


EPU

PFP

ECU

GTP

SPP

SGP

Gb

9

3

Gn

4

10

211

58




7.CreatePDP Context

Response




Data Transmission Flow for the UMTS Access User

EPU

PFP

IuGn

1.UplinkMessage3.Downlink

Message 2.UplinkMessage

4.DownlinkMessage

1. After receiving an uplink message from the interface board, the PFP strips the ATM, IP, UDP, and GTP-U protocol headers, encapsulates the GTP-U, UDP, IP, and MAC protocol headers according to the PDP context, and sends the message to the GGSN. (The PFP functions as the UGFU of the CPCI platform.)

2. The uplink message is sent to the GGSN.3. After receiving a downlink message from the GGSN, the PFP strips the GTP-U,

UDP, IP, and MAC protocol headers, encapsulates the GTP-U, UDP, IP, and ATM protocol headers according to the PDP context, and sends the message to the RNC. (The PFP functions as the UGFU of the CPCI platform.)


Using the ATM bearerUsing the ATM bearer

1. After receiving an uplink message from the interface board, the PFP strips the IP, UDP, and GTP-U protocol headers, encapsulates the GTP-U, UDP, IP, and MAC protocol headers according to the PDP context, and sends the message to the GGSN. (The PFP functions as the UGFU of the CPCI platform.)

2. The uplink message is sent to the GGSN.3. After receiving a downlink message from the GGSN, the PFP strips the GTP-U,

UDP, IP, and MAC protocol headers, encapsulates the GTP-U, UDP, and IP protocol headers according to the PDP context, and sends the message to the RNC. (The PFP functions as the UGFU of the CPCI platform.)


Using the IP bearerUsing the IP bearer


Question

What is the signaling flow in the 2G attach procedure on the SGSN9810 V900R010 ATCA

platform?


Chapter 5 SGSN9810 V900R010 Operation Chapter 5 SGSN9810 V900R010 Operation

and Maintenanceand Maintenance

5.1 Hardware Structure of the OM Subsystem

5.2 Software Structure of the OM Subsystem

5.3 System Software Installation

5.4 Alarm Management



Learn about the OM subsystem on the SGSN9810 V900R010 ATCA

platform.

Learn about system software installation and patch installation on the

SGSN9810 V900R010 ATCA platform.


Hardware Structure of the OM Subsystem

The OM subsystem of the SGSN9810 consists of the LMT and OMU, and provides interfaces to the M2000.

The SGSN9810 provides three operation and maintenance modes:

Local maintenance through the LMT for initial installation and on-site fault location

Centralized maintenance through iManager M2000 for routine maintenance

Performance management through the WebUI


System Software Installation

The system software of SGSN9810 V900R010 can be installed through the OMU or the local

storage media of each board. Here, only the principle of the system software installation through

the OMU is described.

By using the base bus, the board communicates with the OMU through the SWU, requesting

for system software installation. Two planes are used during this course, that is, base plane 1

and base plane 2. Base plane 2 is used only after the communications on base plane 1 fail.

OMU

/INU

Host board

SWU

SWU

Base bus Base bus

Base bus Base bus


Alarm Management

All boards of SGSN9810 V900R010 are intelligent. They can monitor the status, running conditions, and external interfaces of

themselves, test and specify the running status, and report abnormalities to a higher-level device. A higher-level device can

automatically monitor the running status of a lower-level device, report abnormalities to a much-higher-level device, and perform

the active/standby switchover. Alarms can be divided into hardware alarms and software alarms.

Hardware alarms include:

Alarms about hardware (including the SMM, server board, and switching board) and the environment are reported by the SMM.

When hardware events, such as the board status change (for example, installed, removed, or powered off), abnormal fan speed,

abnormal temperature, abnormal voltage, and abnormal current, are detected, the SMM reports the events to the OMU through

the maintenance plane.

Alarms about the hard disk status, RAID status, and network interface status of the server board are reported by the IMU to the

OMU through the maintenance plane.

Software alarms include alarms about process faults, service process overload, and CPU overload.

Both host software and OMU software can generate software alarms. Alarms generated by each software module of the host are

sent to the alarm module, and then are transferred by the alarm module to the alarm service module on the OMU. Alarms

generated by the OMU are directly processed by the alarm service module of the OMU.

IMU

(SBU)

OMU

SMU

Alarm box

Alarm console

SWU

Report alarm

Display alarm

Base

bus

Base

bus

Basebus

Basebus

Report alarm

Report alarm

Report alarm

Display alarm


Question

How to install the system software of SGSN9810 V900R010?


Chapter 6 SGSN9810 V900R010 Chapter 6 SGSN9810 V900R010 Environment MonitoringEnvironment Monitoring

6.1 Power Supply Monitoring

6.2 Fan Monitoring

6.3 Equipment Room Environment Monitoring



Learn about the environment monitoring subsystem on the

SGSN9810 V900R010 ATCA platform.


Power Supply Monitoring

The power supply monitoring module monitors the power supply system in real time, reports power supply status, and generates alarms when abnormalities occur. The power supply monitoring module of the SGSN9810 is located in the PDB. That is, the PDB monitors power supply.

Each SGSN9810 cabinet is configured with a PDB. The PDB is monitored by subrack 0 in the same cabinet.

The SGSN9810 PDB is monitored as follows:

The PDB is equipped with an internal monitoring board for collecting information about the running status of the PDB.

The monitoring board provides an active RS485 serial interface and a standby RS485 serial interface. Through the external RS485 serial cables, the two interfaces are connected to the COM2 interfaces on the SDMs in the back slots of the active and standby SMMs in the service processing subrack respectively.

The SMM can process the information collected by the monitoring board of the PDB and report the information to the OMU through the internal base bus. Then, the OMU transfers the information to the OMC. If any fault occurs, the OMC generates an alarm and sends it to the alarm console or alarm box.

An SGSN9810 cabinet is usually configured with multiple service processing subracks. Generally, the subrack installed at the bottom of a cabinet is used to monitor the PDB of the cabinet.

OMU

Monitoring board

SDM SDM

SMM SMM

RS485 RS485

OSTA2.0 subrack

Base bus

PDB


Fan Monitoring

The service processing subrack of the SGSN9810 is an integrated subrack embedded with the fan box. The fan monitoring module monitors the running status of the fan and adjusts the fan speed based on the subrack temperature.

In the cabinet, the SMM manages and monitors the fan box through the IPMB bus.

The fan box communicates with the SMM through the internal BMC. The fan box reports alarms through the BMC. The SMM delivers commands to the BMC to intelligently adjust the fan speed.

SMM SMM

FAN

IPMB


Equipment Room Environment MonitoringThe equipment room environment monitoring is implemented by the PDB and the MRMU.

The PDB is configured with four external Boolean monitoring interfaces. The interfaces are connected to sensors such as the door status sensor, water sensor, and smoke sensor to collect information about the equipment room environment. The report path of the equipment room environment monitoring information is the same as that of the PDB monitoring information.

If necessary, you can configure more external Boolean monitoring interfaces or analog monitoring interfaces (for the temperature sensor and humidity sensor, for example) on the MRMU.

By default, the function of Environment Monitoring is disabled on the SGSN9810.

OMU

Monitoring board

SDM SDM

SMM SMM

RS485 RS485

OSTA2.0 subrack

Base bus

PDBBoolean sensor


Question

Which components are required to implement environment monitoring on the SGSN9810

V900R010 ATCA platform?


Chapter 7 SGSN9810 V900R010 Time Chapter 7 SGSN9810 V900R010 Time

SynchronizationSynchronization

7.1 Time Synchronization Principle

7.2 Time Synchronization Procedure



Learn about time synchronization on the SGSN9810



Time Synchronization Principle

Time synchronization of the SGSN9810 is centered on the OMU, and involves NTP servers, the OMU subsystem, the host subsystem, and the real-time clock (RTC) subboard. The RTC subboard has a crystal oscillator that provides time with high precision. When the NTP servers are unavailable, the RTC becomes the time source. During time synchronization, the OMU can function as a client to access the NTP servers and a server to provide the time synchronization service for the host. An NTP server can be an NMS or a dedicated time server.

When the synchronization period expires, the OMU sends NTP request messages to the NTP servers every second till all the NTP servers are traversed twice. That is, the OMU requests two time samples from each NTP server. For example, if there are three NTP servers, the time for the OMU to send NTP request messages to all NTP servers is six seconds. At the seventh second, the OMU performs calculation (by using the NTP algorithm) according to the messages returned by the NTP servers, arranges the order of the NTP servers according to the quality, and selects the best NTP server as the time source. Then, the OMU adjusts the local time according to the time provided by the time source.

NTP Server NTP Server NTP Server……

UPB

SMM

UPB

UPB

Master OMURTC Slave OMU RTC

NTP

NTP

……


Time Synchronization Procedure

The time synchronization procedure in the SGSN9810 is as follows:

The active OMU periodically synchronizes time from the NTP servers to the local operating system and the RTC on the back board. The OMU can communicate with the NTP servers through only the maintenance network interface, that is, the network interface of the OMU rather than the service network interface. If all NTP servers are unavailable, the OMU synchronizes time from the RTC to the local operating system. Time synchronization between the OMU and the NTP servers is based on the NTP protocol. Drive interfaces are adopted between the OMU and the RTC.

The standby OMU synchronizes time from the active OMU to the local operating system and the RTC on the back board. When the standby OMU synchronizes time from the active OMU, the active OMU needs to prevent network delays. The standby OMU runs the logic for processing NTP synchronization only after becoming the active OMU.

When the active OMU synchronizes time to the standby OMU and the host, the active OMU first reads time from the RTC. If the reading fails, the active OMU reads time from the local operating system.

Each board synchronizes time from the OMU periodically. The time synchronization is also based on the NTP protocol. If the communications between the OMU and a board are interrupted, the board runs independently.


Question

How does the SGSN9810 obtain precise time when the communications with the NTP server are interrupted?


Chapter 8 SGSN9810 V900R010 Clock Chapter 8 SGSN9810 V900R010 Clock

ManagementManagement

8.1 Structure of the Clock Subsystem

8.2 Cabling of the Clock Cable

8.3 Clock Source

8.4 Line Clock

8.5 Clock Working Mode


Structure of the Clock SubsystemStructure of the Clock Subsystem

The clock subsystem has an active clock module and a standby clock module. The standby clock module can trace and lock the clock frequencies and phases of the active clock module or directly lock external clocks. If the active clock module is faulty, the standby clock module can still output clock frequencies and phases.

The basic working flow of the clock subsystem is as follows: External clock sources are imported to extract clock signals from the BITS clock, E1, T1, STM-1, or STM-4 line. The clock modules process the clock signals. The clock signals output by the clock modules are transmitted to the switching network boards in each service subrack through inter-

subrack cables. These clock signals are provided for synchronization interfaces, such as the E1/T1, or STM-1/STM-4 synchronization interface, and synchronization circuits on the ETI or PFI in the back slot.

The active and standby clock modules simultaneously output clock signals to each board in each subrack. Then, each board selects the internal clock according to the configuration.

The clock subsystem has an active clock module and a standby clock module. The standby clock module can trace and lock the clock frequencies and phases of the active clock module or directly lock external clocks. If the active clock module is faulty, the standby clock module can still output clock frequencies and phases.

The basic working flow of the clock subsystem is as follows: External clock sources are imported to extract clock signals from the BITS clock, E1, T1, STM-1, or STM-4 line. The clock modules process the clock signals. The clock signals output by the clock modules are transmitted to the switching network boards in each service subrack through inter-

subrack cables. These clock signals are provided for synchronization interfaces, such as the E1/T1, or STM-1/STM-4 synchronization interface, and synchronization circuits on the ETI or PFI in the back slot.

The active and standby clock modules simultaneously output clock signals to each board in each subrack. Then, each board selects the internal clock according to the configuration.

The line extracets lock signals

Subrack configured with the Stratum-2 clock

board

Inter-subrack

cable

Inter-subrack

cable

Subrack N

Clock signal input

Clock distribution

Clock signal output

Clock distribution

Active

Standby


The figure shows the cabling of the 8 kHz clock cable. When the internal 8 kHz clock cable needs to be connected

to the ETI in the same subrack through the TMI, lead the cable out of the TMI and bypass the cable trough. Then, connect the cable to the ETI.

When the internal 8 kHz clock cable needs to be connected to the ETI in a different subrack through the TMI, lead the cable out of the TMI and then lead the cable rightwards along the cabling trough. Then, lead the cable upwards to the cable trough of the destination subrack and leftwards through the cable trough to the ETI of the destination subrack.

The figure shows the cabling of the 8 kHz clock cable. When the internal 8 kHz clock cable needs to be connected

to the ETI in the same subrack through the TMI, lead the cable out of the TMI and bypass the cable trough. Then, connect the cable to the ETI.

When the internal 8 kHz clock cable needs to be connected to the ETI in a different subrack through the TMI, lead the cable out of the TMI and then lead the cable rightwards along the cabling trough. Then, lead the cable upwards to the cable trough of the destination subrack and leftwards through the cable trough to the ETI of the destination subrack.

Cabling of the Clock CableCabling of the Clock Cable


Clock Source The clock source refers to the source of clock synchronization signals. The SGSN9810 supports the following types of clock source: BITS clock Line clock extracted by the ETI or PFI interface Internal crystal oscillator

Clock Source The clock source refers to the source of clock synchronization signals. The SGSN9810 supports the following types of clock source: BITS clock Line clock extracted by the ETI or PFI interface Internal crystal oscillator

Line Clock The line clock signals are extracted and output by the ETI or PFI.

The ETI or PFI provides two RJ-45 clock interfaces. The board extracts 8 kHz clock signals from the E1 line, and then outputs the signals to the active and standby TMIs through the two RJ-45 clock interfaces. The two interfaces are marked as 8K_OUT0 and 8K_OUT1 from top to bottom.

Each ETI or PFI panel has two output interfaces, which output the same clock signals. The signals are the line clock signals extracted from the same interface.

Line Clock The line clock signals are extracted and output by the ETI or PFI.

The ETI or PFI provides two RJ-45 clock interfaces. The board extracts 8 kHz clock signals from the E1 line, and then outputs the signals to the active and standby TMIs through the two RJ-45 clock interfaces. The two interfaces are marked as 8K_OUT0 and 8K_OUT1 from top to bottom.

Each ETI or PFI panel has two output interfaces, which output the same clock signals. The signals are the line clock signals extracted from the same interface.

Clock Working Mode The clock working mode defines the method of selecting the current clock source from clock sources of different

priorities. Each clock source is assigned with a priority according to the precision. Generally, the priorities of the BITS clock,

line clock, and internal crystal oscillator are in a descending order. If the system has multiple clock sources with different priorities, the clock working mode can be any of the following: AUTO: The clock board selects the current clock source according to the priority. When the current clock source

becomes invalid, the clock source with the lower priority automatically becomes the new current clock source. When the clock source of the higher priority recovers, it automatically becomes the current clock source.

MANUAL: The clock board does not automatically switch between clock sources but traces the specified clock source only. When the current clock source becomes invalid, the clock board enters the holdover mode.

FREE: The internal crystal oscillator automatically becomes the current clock source.

Clock Working Mode The clock working mode defines the method of selecting the current clock source from clock sources of different

priorities. Each clock source is assigned with a priority according to the precision. Generally, the priorities of the BITS clock,

line clock, and internal crystal oscillator are in a descending order. If the system has multiple clock sources with different priorities, the clock working mode can be any of the following: AUTO: The clock board selects the current clock source according to the priority. When the current clock source

becomes invalid, the clock source with the lower priority automatically becomes the new current clock source. When the clock source of the higher priority recovers, it automatically becomes the current clock source.

MANUAL: The clock board does not automatically switch between clock sources but traces the specified clock source only. When the current clock source becomes invalid, the clock board enters the holdover mode.

FREE: The internal crystal oscillator automatically becomes the current clock source.


Chapter 9 SGSN9810 V900R010 Charging Chapter 9 SGSN9810 V900R010 Charging

ManagementManagement

9.1 Implementation of the Charging Function

9.2 Structure of the Charging Function

9.3 CG Selection

9.4 CDP Selection

9.5 Caching CDRs to the Hard Disk

9.6 Principle of Charging Data Collection

9.7 Reliable CDR Transmission


Implementation of the Charging Function

SPP

GTP ASN.1 encoding

CDR caching

CDR sending CG

ECU HD

CDP

M-CDR

S-SMO-CDR

S-SMT-CDR

LCS-MO-CDR

LCS-MT-CDR

LCS-NI-CDR

S-CDRCDRs

CDRs CDRs

CDR files

CDR files


Structure of the Charging Function

Generate half-finished CDRs.

M-CDRS-SMT-CDRS-SMO-CDRLCS-MO-CDRLCS-MT-CDRLCS-NI-CDR

Forward RNC

traffic.

Forward half-finished CDRs.

SPP

Encode CDRs.

Send CDRs.

CDP

Receive and process half-finished CDRs.

RNC

Ga

SGP

Collect and forward RNC traffic.

Generate ahalf-finished CDRs.SCDR

Forward GB traffic.

Forward half-finished CDRs.

GTP

Encode CDRs.

Send CDRs.

CDP

Receive and process half-finished CDRs.

Cach CDRs.

Hard disk of the ECU

Ga

GBP

Collect and forward GB traffic.

Obtain SDB information.

Cach CDRs.

Hard disk of the ECU


CG Selection

The CDP can be configured to communicate with multiple CGs. The CGs can be

configured with different priorities. In such a case, CDRs are sent to the CG with

the highest priority.

If the CG with the highest priority or the link to the CG with the highest priority fails,

CDRs are sent to the CG with a lower priority.

CG1(priority 0)

CDPCG2

(priority 1)

CG3(priority 2)

CDRsCG1

(priority 0)

CDPCG2

(priority1)

CG3(priority 2)

CDRs

CG1(priority 0)

CDPCG2

(priority 1)

CG3(priority 2)

CDRs


CG Selection The CDP can be configured to communicate with multiple CGs. If the priorities of the CGs are

the same, the CGs work in load-sharing mode.

If the communications between the CDP and a CG fails, CDRs are sent to other CGs.

CG1(priority 0)

CDPCG2

(priority 0)

CG3(priority 0)

CDRs

CDRs

CDRs CG1(priority 0)

CDPCG2

(priority 0)

CG3(priority 0)

CDRs

CDRs


CDP Selection

If there are multiple CDPs in the system, the CDPs work in load-sharing mode.

If a CDP is abnormal, the SPP and the GTP send the half-finished CDRs to other

normal CDPs.

GTP1

S-CDRs

S-CDRs

GTP2

Both the active and standby CDP1 processes are normal.

UCDR1CDP1

UCDR1CDP2

GTP1

S-CDRs

S-CDRs

GTP2

Both the active and standby CDP1 processes are abnormal.

UCDR1CDP1

UCDR1CDP2


Caching CDRs to the Hard Disk When the communications between the CDP and the CG fail, CDRs are written

into the hard disk of the ECU where the CDP is located.

When the space of the hard disk of the ECU where the active CDP is located is

insufficient, CDRs are written into the hard disk of the ECU where the standby

CDP is located. Each ECU hard disk can store up to about 50 GB CDRs.

ASN.1 encoding

CDRsending unitr

CDRcaching unit

Hard disk

Active CDP

ECU

CDRcaching unit

Hard disk

Standby CDP

CDRs

CDRs

CDRs

CDRs

CDRs

The Ga interface fails.CDRs

ECU


Caching CDRs to the Hard Disk

After the Ga interface recovers, the CDR caching unit of the active CDP reads CDRs from the

hard disk of the ECU where the active CDP is located, and then sending unit sends the CDRs to

the CG.

If CDRs exist in the hard disk of the ECU where the standby CDP is located, the CDR caching unit

of the standby CDP reads the CDRs from the hard disk and sends the CDRs to the active CDP.

Then, the CDR caching unit of the active CDP sends the CDRs to the CG.

ASN.1 encoding

CDRsending unit

CDRcaching unit

Hard disk

Active CDP

ECU

CDRcaching unit

Hard disk

Standby CDP

ECU

CDRs

CDRs

CDRs

CDRs

CDRs

The Ga interface is normal.CDRs CDRs


CDR Storage Directories on the Hard Disk A directory named after a CDR type is a level-1 directory. For example, the directory R98 stores

R98 CDR files. The directory Errorcode stores the CDR files that are decoded incorrectly.

The directories CDR0 to CDR999 are level-2 directories that store normal CDR files. Each

directory can store up to 100 CDR files. The directory err stores the CDR files that are read or

written incorrectly.

The extension names of a normal CDR file, an abnormal CDR file, and a compressed CDR file

are *.CDR, *.ERR, and *.tar respectively. The value of * ranges from 0 to 99.

R98

Level-1 directory

R99

R4

R5

CDR0

CDR1

CDR999

Err

.

.

.

Level-2 directory

0.CDR

1.CDR

99.CDR

.

.

.

CDR file

R6

R7

errcode


Principle of Charging Data Collection

1. Each PDP context must trigger the generation of an S-CDR and a G-CDR.

2. The M-CDR is optional.

3. The SGSN9810 provides two types of short message CDR, that is, S-SMO-CDR and S-SMT-

CDR.

4. CDRs related to a PDP context provide the location information of the MS.

5. CDRs contain only the charging information defined in the related protocol.

6. Tariff change does not result in the generation of a large number of CDRs.

7. The charging IDs and other common charging information of the S-CDR and the G-CDR

generated for the same PDP context are the same.

8. The RNC collects information about the downlink data traffic that is not sent successfully.


Reliable CDR Transmission

The CDR sending unit of the CDP encapsulates a CDR into a frame and sends the frame to

the CG through the Data Record Transfer Request message.

If the CDR sending unit does not receive the response message from the CG within a

specified period, the CDR sending unit resends the Data Record Transfer Response

message till the response message from the CG is received or the specified maximum

transmission number is reached.

If the CDR sending unit does not receive the response message from the CG when the

specified maximum transmission number is reached, the CDR sending unit considers that

the CG is abnormal, and performs the CG redirection procedure.

Thank youwww.huawei.com

owb091001(slide)sgsn9810 v900r010c01 system principle-20100505-b-v1.1

Documents