PCU

HUAWEI PCU6000 Packet Control Unit Technical Manual
Contents
Contents
1 General Introduction.................................................................................................................1-1
1.1 Overview of Functions ..................................................................................................................................1-2 1.2 Topology .......................................................................................................................................................1-3 1.3 Features .........................................................................................................................................................1-4 1.4 Technical Specifications................................................................................................................................1-5
2 Functional Description..............................................................................................................2-1
2.1 Overview.......................................................................................................................................................2-2 2.2 Service Processing Function .........................................................................................................................2-2 2.2.1 Packet Channel Configuration .............................................................................................................2-3 2.2.2 Packet Access Support .........................................................................................................................2-6 2.2.3 Paging Processing ................................................................................................................................2-7 2.2.4 DRX Support .......................................................................................................................................2-8 2.2.5 Radio Resources Allocation .................................................................................................................2-8 2.2.6 System Information Broadcasting........................................................................................................2-8 2.2.7 Radio Link Control ..............................................................................................................................2-9 2.2.8 Channel Coding Schemes and CS Change Control..............................................................................2-9 2.2.9 Modulation and Coding Schemes and MCS Change Control ............................................................2-10 2.2.10 G-TRAU Frame Transmission ......................................................................................................... 2-11 2.2.11 Radio Link Monitoring .................................................................................................................... 2-11 2.2.12 Radio Frequency Power Control......................................................................................................2-12 2.2.13 Cell Reselection Control ..................................................................................................................2-12 2.2.14 Supporting the PFM/PFC.................................................................................................................2-13 2.2.15 Flow Control and QoS Guarantee ....................................................................................................2-13 2.2.16 Mobility Management and Communication Management...............................................................2-14 2.2.17 Gb Over IP .......................................................................................................................................2-15 2.2.18 PFC High-Priority Preemption.........................................................................................................2-15 2.3 Signaling Function ......................................................................................................................................2-16 2.3.1 Gb Interface Signaling .......................................................................................................................2-16 2.3.2 In-Band Signaling Between PCU and BTS........................................................................................2-19 2.3.3 Pb Interface Signaling........................................................................................................................2-19 2.4 Operation and Maintenance Function .........................................................................................................2-19 2.4.1 Network Maintenance ........................................................................................................................2-19
Issue 05 (2008-05-30)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
Contents
HUAWEI PCU6000 Packet Control Unit Technical Manual 2.4.2 Operation and Maintenance Management..........................................................................................2-20 2.4.3 Configuration Management ...............................................................................................................2-21 2.4.4 Alarm Management............................................................................................................................2-21 2.4.5 Performance Measurement ................................................................................................................2-21 2.4.6 Interface Tracing ................................................................................................................................2-21 2.4.7 Security Management ........................................................................................................................2-22
3 System Structure ........................................................................................................................3-1

3.1 Overview.......................................................................................................................................................3-2 3.2 Hardware Structure .......................................................................................................................................3-2 3.3 Software Structure.........................................................................................................................................3-5 3.3.1 HUAWEI PCU6000 Operating System ...............................................................................................3-6 3.3.2 POMU Software...................................................................................................................................3-7 3.3.3 RPPU Software ....................................................................................................................................3-8 3.3.4 L2PU/HLPU Software .......................................................................................................................3-10 3.4 Equipment Features..................................................................................................................................... 3-11 3.4.1 Gb Interface ....................................................................................................................................... 3-11 3.4.2 G-Abis Interface................................................................................................................................. 3-11 3.4.3 Pb Interface ........................................................................................................................................ 3-11 3.4.4 Operation and Maintenance ............................................................................................................... 3-11 3.4.5 Clock Synchronization.......................................................................................................................3-12 3.4.6 Overload Processing ..........................................................................................................................3-12 3.4.7 POMU Simple Hot Backup................................................................................................................3-13 3.4.8 Dynamic Data Configuration .............................................................................................................3-14 3.4.9 Backup of the Cells of the Same BSC ...............................................................................................3-14 3.4.10 Software Loading.............................................................................................................................3-15 3.4.11 Satellite Transmission Function .......................................................................................................3-18 3.4.12 On Line Patches ...............................................................................................................................3-18 3.4.13 License .............................................................................................................................................3-18
4 Interface Functions ....................................................................................................................4-1

4.1 Gb interface...................................................................................................................................................4-2 4.1.1 Overview..............................................................................................................................................4-2 4.1.2 Signaling at Different Layers of the Gb Interface................................................................................4-3 4.1.3 Characteristics of the Gb Interface.......................................................................................................4-5 4.2 G-Abis Interface............................................................................................................................................4-5 4.2.1 Overview..............................................................................................................................................4-5 4.2.2 Characteristics of the G-Abis Interface................................................................................................4-6 4.2.3 Physical Layer/Transmission Media ....................................................................................................4-7 4.2.4 A Brief Introduction to G-TRAU Frame Structure ..............................................................................4-9 4.2.5 Characteristics of the G-Abis Interface................................................................................................4-9 4.3 Pb Interface ................................................................................................................................................. 4-11 4.3.1 Overview............................................................................................................................................ 4-11
ii
Issue 05 (2008-05-30)
Contents
4.3.2 Internal Structure of the Pb Interface ................................................................................................. 4-11 4.3.3 Characteristics of Pb Interface ...........................................................................................................4-12 4.4 O Interface...................................................................................................................................................4-13 4.4.1 Overview............................................................................................................................................4-13 4.4.2 Software Structure..............................................................................................................................4-14
5 Operation & Maintenance........................................................................................................5-1

5.1 Overview.......................................................................................................................................................5-2 5.2 Characteristics ...............................................................................................................................................5-4 5.3 Implementation of PCU O&M Function.......................................................................................................5-4 5.3.1 Configuration Management .................................................................................................................5-4 5.3.2 Alarm Management..............................................................................................................................5-6 5.3.3 Performance Measurement ..................................................................................................................5-7 5.3.4 Interface Information Tracing ............................................................................................................5-13
6 Technical Indices........................................................................................................................6-1
6.1 Product Safety ...............................................................................................................................................6-2 6.1.1 Safety Standard ....................................................................................................................................6-2 6.1.2 Physical Protection Characteristics ......................................................................................................6-2 6.1.3 Data Backup and Security Characteristics ...........................................................................................6-2 6.2 Environmental Conditions.............................................................................................................................6-3 6.2.1 Environmental Conditions Required by the Equipment.......................................................................6-3 6.2.2 EMC.....................................................................................................................................................6-3 6.2.3 Noise ....................................................................................................................................................6-3 6.2.4 Storage Condition ................................................................................................................................6-4 6.2.5 Transportation Condition .....................................................................................................................6-4 6.3 Power Supply and Power Consumption ........................................................................................................6-4 6.4 Capacity ........................................................................................................................................................6-4 6.4.1 Maximum Capacity..............................................................................................................................6-4 6.4.2 Minimum Capacity ..............................................................................................................................6-5
7 Configuration and Examples ...................................................................................................7-1

7.1 GPRS Configuration and Examples ..............................................................................................................7-2 7.2 EGPRS Configuration and Examples............................................................................................................7-4
Issue 05 (2008-05-30)
iii
Figures
Figures
Figure 1-1 Position of the PCU in the GPRS/GSM network..............................................................................1-2 Figure 1-2 Location of the PCU .........................................................................................................................1-3 Figure 1-3 Typical topology of the PCU ............................................................................................................1-3 Figure 2-1 Signaling plane of the GPRS BSS ....................................................................................................2-2 Figure 2-2 Radio channel structure ....................................................................................................................2-5 Figure 2-3 Gb interface point-to-point frame relay connection........................................................................2-16 Figure 2-4 Gb interface intermediate frame relay network connection ............................................................2-16 Figure 2-5 Direct connection mode in the Gb Over IP network.......................................................................2-17 Figure 2-6 Router connection mode in the Gb Over IP network ......................................................................2-17 Figure 3-1 PCU logic structure...........................................................................................................................3-2 Figure 3-2 Configuration of the HUAWEI PCU6000 cabinet............................................................................3-3 Figure 3-3 HUAWEI PCU6000 processing frame configuration .......................................................................3-4 Figure 3-4 HUAWEI PCU6000 hardware structure ...........................................................................................3-4 Figure 3-5 HUAWEI PCU6000 software logic structure ...................................................................................3-5 Figure 3-6 POMU software loading flow 1......................................................................................................3-15 Figure 3-7 RPPU software loading flow ..........................................................................................................3-16 Figure 3-8 L2PU/HLPU software loading flow ...............................................................................................3-17 Figure 4-1 Gb protocol stack..............................................................................................................................4-2 Figure 4-2 BSSGP service models .....................................................................................................................4-4 Figure 4-3 The O interface of GPRS/GSM ......................................................................................................4-13 Figure 4-4 Software structure of the O interface ..............................................................................................4-14 Figure 5-1 GSM/GPRS O&M system ................................................................................................................5-2 Figure 5-2 PCU O&M system............................................................................................................................5-3 Figure 5-3 The connection between PCU and OMC..........................................................................................5-3 Figure 5-4 Structure of the HUAWEI PCU6000 traffic measurement system ...................................................5-7
iv
Issue 05 (2008-05-30)
Tables
Tables
Table 2-1 Description of priority ........................................................................................................................2-4 Table 2-2 Channel coding schemes ....................................................................................................................2-9 Table 2-3 Channel coding schemes ..................................................................................................................2-10 Table 3-1 Measures for PCU faults...................................................................................................................3-13 Table 4-1 Transmission parameters relating to coding schemes .........................................................................4-6 Table 4-2 Transmission parameters relating to modulation and coding schemes ...............................................4-6 Table 4-3 Example of the timeslot configuration for the G-Abis interface (PCU-BSC) ....................................4-7 Table 4-4 Example of the timeslot configuration for the G-Abis interface (BSC-BTS).....................................4-8 Table 4-5 Structure of the G-TRAU frame .........................................................................................................4-9 Table 5-1 PCU performance measurement types................................................................................................5-9 Table 6-1 Environmental storage condition required by the HUAWEI PCU6000 equipment............................6-3 Table 6-2 EMC specifications ............................................................................................................................6-3 Table 6-3 Specifications of noise and security ...................................................................................................6-3 Table 6-4 Power supply and power consumption of the PCU ............................................................................6-4 Table 6-5 The processing capability of PCU with the maximum configuration.................................................6-4 Table 6-6 The processing capability of PCU with the minimum configuration..................................................6-5 Table 7-1 PCU GPRS configuration example 1 .................................................................................................7-2 Table 7-2 The PCU GPRS configuration example 2 ..........................................................................................7-3 Table 7-3 The PCU EGPRS configuration example ...........................................................................................7-4
Issue 05 (2008-05-30)
1 General Introduction
1
About This Chapter
Section 1.1 Overview of Functions 1.2 Topology 1.3 Features 1.4 Technical Specifications
General Introduction
The following table lists the contents of this chapter. Describes This section describes the functions. This section describes the Topology. This section describes the features of PCU. This section describes the technical specifications of PCU.
Issue 05 (2008-05-30)
1-1
Figure 1-1 shows the position of the PCU in the GSM/GPRS network. The GPRS BSS (Base Station Subsystem) connects to the MS (Mobile Station) through the Um interface. It is responsible for packet radio transmitting/receiving, and packet radio resources management. The BSS also connects to the SGSN (Serving GPRS Support Node) of the NSS (Network Subsystem), realizing the connection between MSs or between the MS and fixed network subscribers, to transmit system signaling and user information. To realize the O&M of the BSS, the connection between the BSS and the Operation and Maintenance Subsystem (OMS) is needed. With the newly added hardware PCU, the BSS supports GPRS based on existing GSM BSS, and the software upgrade of the BSC and BTS of the original GSM network. Figure 1-1 Position of the PCU in the GPRS/GSM network
GSM NSS
GPRS NSS
Ab i
BSC LMT
Gb
Pb
WAN/LAN
GSM/GPRS BSS
PCU LMT
R R R
M2000 Telnet M2000 M2000 Client Terminal Server Client GSM/GPRS O&M subsystem
(1) PCU: Packet Control Unit (3) LMT: Local Maintenance Terminal (2) BSC: Base Station Controller
...
The HUAWEI PCU6000 is developed in accordance with the GSM and GPRS specifications issued by the ETSI.
1.1 Overview of Functions

The HUAWEI PCU6000 performs the following functions: Managing most PS resources Controlling PS calls Transmitting PS data Supporting the Gb, the G-Abis, and Pb interfaces Gb interface supporting IP-based network
1-2
Issue 05 (2008-05-30)
1.2 Topology
The PCU of the M900/M1800 BSS is a piece of semi-independent equipment. Functionally, it is part of the BSC. In terms of location, it is relatively independent. It can be located on the BSC site, SGSN site, or MSC site. The HUAWEI PCU6000 location is a combination of schemes A, B, and C as shown in Figure 1-2. Figure 1-2 Location of the PCU
Um BTS PCU Abis CCU CCU BTS BSC site PCU GSN site BSC site Gb GSN site
CCU CCU
CCU CCU
BTS
BSC site PCU
GSN site
Packet switching PCU: Packet Control Unit
Circuit switching (16kbit/s or 64kbit/s) BTS: Base Transceiver Station
Gb
CCU: Channel Code Unit
Figure 1-3 shows the typical topology of the PCU. Figure 1-3 Typical topology of the PCU
BSS
A BSC BTS BSS PCU MSC/VLR Gb SGSN HLR Gs Gr SS7
BSC BTS
Issue 05 (2008-05-30)
1-3
The PCU is connected to the BSC through the standard E1 cable and to the SGSN through the standard E1 cable or network cable. The connection between the PCU and the SGSN is based on PTP frame relay or frame relay network, and the IP-based network.. The PCU can be located at the BSC site or the SGSN site. The PCU is located at the BSC site. This topology is applicable when the PCU and the BSC are located at the same site or the BSC equipment is distributed closely in the local network construction. (Initially local GPRS user traffic is low. Therefore, the data from several BSCs is converged by the PCU and in turn, the transmission cost is reduced.) The PCU is located at the SGSN site. This topology is applicable when newly added equipment of GPRS is distributed closely in the local network. When BSC sites are scattered, close distribution of GPRS equipment facilitates the management.
1.3 Features
The HUAWEI PCU6000 has the following features: Modular structure, supporting smooth expansion of the network.. Large capacity and high processing capability. The GPRS/EDGE activates a maximum of 1080/900 PDCHs at the same time. The maximum throughput on the Gb interface is 24 Mbit/s. Measurement report preprocessing. Uplink open-loop power control. Optimal G-Abis interface solutions. Supporting CS-1, CS-2, CS-3 and CS-4. CS dynamic adjustment algorithms. Supporting MCS-1, MCS-2, MCS-3, MCS-4, MCS-5, MCS-6, MCS-7, MCS-8, and the MCS-9. Dynamic MCS adjustment algorithm. Supporting incremental redundancy (IR) and link adaptation (LA) for link quality control. Multiplexing of GPRS and EGPRS MSs. PDCH dynamic conversion. Flexible topologies. Gb interface downlink flow control. POMU simple hot backup. Cell backup in the same office direction. Gb interface supporting IP-based network.
1-4
Issue 05 (2008-05-30)
1.4 Technical Specifications

The HUAWEI PCU6000 follows the relevant GSM/GPRS technical specifications stipulated by the ETSI and relevant IETF standards. The relevant ETSI GSM/GPRS technical specifications include: EN 301 344, GSM 03.60 V7.4.0, ETSI EN 300 940, GSM 04.08 V7.5.1, ETSI 3GPP TS 04.18 V8.15.0, 3GPP 3GPP TS 04.60 V8.15.0, 3GPP 3GPP TS 48.016 V4.3.0, 3GPP TS 101 351, GSM 04.64 V7.3.0, ETSI TS 101 297, GSM 04.65 V7.3.0, ETSI EN 300 908, GSM 05.02 V7.4.0, ETSI EN 300 911, GSM 05.08 V7.3.1, ETSI TS 101 299, GSM 08.16 V7.1.0, ETSI TS 101 343, GSM 08.18 V7.3.0, ETSI The relevant IETF standards include: RFC854, Telnet Protocol specification RFC 768, User Datagram Protocol specification RFC 791, Internet Protocol specification
Issue 05 (2008-05-30)
1-5
2 Functional Description
2
About This Chapter
Section
Functional Description
The following table lists the contents of this chapter.

Describes
2.1 Overview 2.2 Service Processing Function 2.3 Signaling Function 2.4 Operation and Maintenance Function
This section describes the overview of the functional description. This section describes the service processing function. This section describes the signaling function. This section describes the operation and maintenance function.
Issue 05 (2008-05-30)
2-1
2.1 Overview
Figure 2-1 shows the signaling plane of GPRS BSS. It mainly achieves the functions at the RLC/MAC, BSSGP, NS protocol layers, and fulfills the related functions of the air interface RF.
Figure 2-1 Signaling plane of the GPRS BSS
GMM/SM LLC Relay RLC MAC GSM RF MS Um RLC MAC GSM RF BSS BSSGP Network Service L1bis Gb SGSN BSSGP Network Service L1bis GMM/SM LLC
(1) GMM: GPRS Mobility Management (3) RLC: Radio Link Control (5) BSSGP: Base Station System GPRS Protocol
(2) LLC: Logical Link Control (4) MAC: Medium Access Control (6) SM: Session Management
The PCU is semi-independent equipment that processes the main service flows of GPRS BSS, including the implementation of functions at the RLC/MAC, BSSGP, NS protocol layers. BTS mainly implements the RF-related functions at the air interface, while the BSC establishes the link between the PCU and the BTS to transmit packet data transparently.
2.2 Service Processing Function

The HUAWEI PCU6000 performs the following service functions: Packet Channel Configuration Packet Access Support Paging Processing DRX Support Radio Resources Allocation System Information Broadcasting Radio Link Control Channel Coding Schemes and CS Change Control Modulation and Coding Schemes and MCS Change Control G-TRAU Frame Transmission Radio Link Monitoring Radio Frequency Power Control Supporting the PFM/PFC
2-2
Issue 05 (2008-05-30)
Flow Control and QoS Guarantee Mobility Management and Communication Management Gb Over IP PFC High-Priority Preemption
2.2.1 Packet Channel Configuration

Types of Packet Data Logical Channels
PDCH (Packet Data CHannel) is of the following four types: PDTCH (Packet Data Traffic CHannel) PDTCH transmits the user data in the mode of packet switching at a transmission rate of 0 kbit/s 59.2 kbit/s. All packet data traffic channels are un-directional, either uplink (PDTCH/U), for a mobile originated packet transfer, or downlink (PDTCH/D), for a mobile terminated packet transfer. The PDTCH on the TRX supporting the EDGE can be configured to the following four channel types:

EGPRS dedicated channel: Used by the EGPRS MS only. EGPRS preferred channel: Preferred to be used by the EGPRS MS. When this channel is idle, it can be used by the GPRS MS. EGPRS common channel: Used by the GPRS MS and EGPRS MS. GPRS channel: Used by the GPRS MS. The EGPRS MS does not use this channel. ( If there is no E channel in the cell, the EGPRS MS uses the G channel. )
The PDTCH on the TRX not supporting the EDGE can only be configured to GPRS channel PBCCH (Packet Broadcast Control CHannel) The PBCCH broadcasts the parameters used by the MS to access the network for packet transmission operation. The PBCCH also reproduces the information transmitted onto the BCCH to allow circuit-switching operation. The existence of the PBCCH in the cell is indicated on the BCCH. The MS in the GPRS attached mode monitors the PBCCH, only if it exists. In the absence of PBCCH, the BCCH can be used to broadcast information for packet operation. PCCCH (Packet Common Control CHannel) PCCCH includes the following:

PPCH (Packet Paging CHannel): Downlink only, used to page the MS. PRACH (Packet Random Access CHannel): Uplink only, used to request allocation of one or several PDTCHs (for uplink or downlink direction). PAGCH (Packet Access Grant CHannel): Downlink only, used to allocate one or several PDTCHs. PNCH (Packet Notification CHannel): Downlink only, used to notify the MS of PTM-M call.
If no PCCCH is allocated, the information for packet switching operation is transmitted onto the CCCH. If a PCCCH is allocated, it may transmit the information for packet switching operation.
Issue 05 (2008-05-30)
2-3
Packet dedicated control channels The packet dedicated control channels are:

PACCH (Packet Associated Control CHannel): Bi-directional, used to transmit the packet signaling in data transmission. PTCCH/U (Packet Timing advance Control CHannel Uplink): Used to transmit random access bursts to estimate the timing advance for one MS in packet transfer mode. PTCCH/D (Packet Timing Advance Control CHannel Downlink): Used to transmit timing advance updates to several MSs. One PTCCH/D is paired with several PTCCH/Us.
The HUAWEI PCU6000 supports all the functions of packet channels.
Combination of Packet Data Logical Channels

The types of combinations are: PBCCH + PCCCH + PDTCH + PACCH + PTCCH PCCCH + PDTCH + PACCH + PTCCH PDTCH + PACCH + PTCCH Among which, PCCCH = PPCH + PRACH + PAGCH + PNCH. When you configure the PBCCH in a cell, the first combination is used. The cell can have only one such channel combination. When there are many MSs in a cell and the PCCCH is busy, one or more second channel combinations can be configured. Unless the first type is used, the second channel combination cannot be configured in a cell. The channel combination of the third type is used for the uplink and downlink packet data transmission. A cell can be configured with one or more channels of such combinations. The HUAWEI PCU6000 system supports all types of channel combinations. Among them, the channels of the third type are divided into the fixed PDCHs and the dynamic PDCHs. The fixed PDCHs transmit GPRS packet data. They cannot be seized by circuit services. The dynamic PDCHs are converted to TCH or PDTCH according to the need of services. That is, when the system is initialized, it serves as the TCH. When there is a demand for packet services, the dynamic PDCHs are converted into PDCH, and when there is a demand for circuit services, it is converted from PDCH to TCH. An MS can define the following priorities: The PCU applies for the PDCH from the BSC The BSC reclaims the PDCH from the PCU For details, refer to Table 2-1.
Table 2-1 Description of priority Priority PCU Applies for the PDCH From the BSC BSC Reclaims the PDCH From the PCU
The circuit service uses the dynamic PDCH privilegedly.
The PCU unconditionally releases the PDCH
2-4
Issue 05 (2008-05-30)
Priority
PCU Applies for the PDCH From the BSC
BSC Reclaims the PDCH From the PCU
If all the PDCHs reach the upper limit of multiplexing or no available channel exists, the PS service is privilegedly used. If all the PDCHs reach the upper limit of multiplexing or no available channel exists, the PS service is privilegedly used. The BSC rejects to release the occupied PDCHs.
The PCU refuses to release the occupied control PDCHs. The PCU refuses to release the occupied PDCH The PCU rejects to release the occupied PDCHs.
Mapping of Logical Channels onto Physical Channels

The GPRS packet channel has the 52-multiframe structure. Each channel has 52 multi-frames, and every four frames constitute a radio block. Therefore, a radio channel has 12 radio blocks, 2 PTCCHs, and 2 idle frames. Figure 2-2 shows the structure of the radio channel.
Figure 2-2 Radio channel structure
B0
B1
B2
B3
B4
B5
B6
B7
B8
B9
B10
B11
B0~B11: 12 Radio Blocks
T: PTCCH Frame
X: Idle Frame
Among which, PBCCH: It can be mapped in the sequence given above to radio blocks of B0, B3, B6, and B9, along with the number of blocks, depending on how busy the broadcast channel is. PCCCH: PAGCH and PPCH can be mapped to any radio block of the downlink channels (except the radio block seized by the PBCCH). The PRACH is the corresponding uplink frame when PBCCH, PAGCH, PPCH occupy the radio blocks. PDTCH: It can be mapped to any radio block for the transmission of packet data. PACCH: It can be mapped to any radio block for the transmission of air interface radio signaling. PTCCH: The 12th and 38th uplink frames of every 52 multi-frames are PTCCH/U, and the 12th and 38th downlink frames of two adjacent 52 multi-frames form a PTCCH/D.
Issue 05 (2008-05-30)
2-5
2.2.2 Packet Access Support

When the upper layer of the MS has data to send, the RLC/MAC of the MS initiates the packet access process. The MS packet access is performed using either of the following methods: Short access One phase access Two phase access Single block without TBF establishment access Paging response Cell update Mobility management procedure When the data for transmission are fewer than eight RLC blocks, the channel request type of the MS will be the short access, and the number of data blocks can be calculated assuming channel coding scheme CS-1. When the data for transmission are more than eight RLC blocks, and the required RLC mode is the acknowledged mode, the channel request type of the MS will be either one phase access or two-phase access. When the data for transmission is the MS measurement report, the channel request type is the single block without TBF establishment access. There are other channel request types, such as the paging response, cell update, mobility management procedure. However, these channel request types are generally treated as the one phase access or two-phase access. In the case of short access and one phase access, the radio resources are assigned to the MS permanently (such as the TFI, dynamic allocation USF or the fixed allocation radio block bitmap, etc.). Then the MS starts to transmit data. For the two-phase access channel request, a radio block is first assigned to the MS to transmit the packet resource request. The MS starts to transmit data over the assigned resources only after the resources (including the TFI, USF, or the fixed allocation radio block bitmap) are assigned to the MS for the second time. Since the PACKET CHANNEL REQUEST is the only 8-bit or 11-bit access burst, it carries comparatively less information. The PACKET RESOURCE REQUEST is a RLC/MAC signaling packet with CS-1 codes, carrying comparatively more information (including TLLI of MS, multi-slot capabilities of MS, wireless priority.). Therefore, it facilitates the assignment of appropriate resources to the MS. The HUAWEI PCU6000 supports all access methods, among which the paging response, cell update, mobility management procedure are generally treated as the two-phase access method.
2-6
Issue 05 (2008-05-30)
2.2.3 Paging Processing

In the GPRS/GSM system, the paging includes packet paging and paging co-ordination, which are described below:
Packet Paging
When transmitting downlink data to the MS, the SGSN initiates packet paging to locate the MS. The paging request message generated by the SGSN is transmitted through the Gb interface to the PCU, which in turn translates it into the PACKET PAGING REQUEST of the Um interface. If the BSS is configured with the PCCCH, the message is transmitted over the PPCH. If the BSS is not configured with the PCCCH, the PCU forwards the message through the Pb interface to the BSC, which then sends it over the PCH. When the MS receives the packet-paging message, it initiates the uplink TBF (Temporary Block Flow) establishment procedure. The MS will then send the paging response packet in the form of data to the PCU through the Um interface, and the PCU will forward it to the SGSN. After receiving the paging response, the SGSN processes it and is ready to transmit the downlink data.
Paging Co-ordination
In the GSM network, when a circuit paging reaches an MSC, the MSC locates the registered location area of the MS, and sends the circuit-paging message to all the BSCs, within the location area. If there is a Gs interface between the SGSN and MSC, the GPRS/GSM system runs in the network operation mode I. The circuit paging messages of GSM service can be sent through the GPRS packet channel. (That is, if a MS is attached to the GPRS, then the circuit paging is sent through the Gs interface, Gb interface, the MSC and SGSN to the PCU.) The PCU decides the channel to send the message. In the network operation mode I, if the MS is assigned the PDCH, the message is sent over the PACCH. If it is not assigned the PDCH, but the system is configured with the PCCCH, the message is sent over the PPCH. If it does not assign the PDCH, and the system is not configured with the PCCCH, then the PCU will forward the message through the Pb interface to the BSC, and the BSC will send it over the PCH. If there is no Gs interface between the SGSN and the MSC, the GPRS/GSM system can work only in operation mode II or III. In this case, the system sends the circuit-paging message over the CCCH. When the MS receives the circuit-paging message, it accesses the RACH, and initiates the circuit link establishment process. If the MS is handling the GPRS service, it will start the GPRS SUSPEND process to suspend the GPRS service. The MS cannot recover the GPRS service until the circuit link is released. The HUAWEI PCU6000 supports the packet paging and circuit paging functions that are previously mentioned.
Issue 05 (2008-05-30)
2-7
2.2.4 DRX Support

The HUAWEI PCU6000 supports DRX, and the MS concerned should support DRX too. The MS that supports DRX receives only the paging message (packet or circuit paging) of the corresponding paging group in the paging channel, whereas the MS that does not support DRX translates all the paging messages in the paging channel. It is obvious that the MS that supports DRX significantly reduces its power consumption.
2.2.5 Radio Resources Allocation

Medium Access Modes
HUAWEI PCU6000 supports the dynamic allocated and extended dynamic allocated medium access control modes. The radio blocks used by the MS are allocated by the PCU temporarily. While allocating radio resource to the MS, the PCU allocates several radio channels, and their corresponding USF (Uplink State Flag) value. When the MS receives the assignment message, it monitors the USF value of the downlink radio block in the assigned channel. If the value is the same as the assigned USF, the MS will transmit the data in the corresponding uplink radio block. The USF value that HUAWEI PCU6000 realizes is granularity 1 and 4.
Multi-slot Capability of the MS

The HUAWEI PCU6000 supports the MS of 145 classes. It can make optimal resources allocation according to the MS multi-slot capability and the radio resources. The MS is divided into 45 classes according to the multi-slot capability. For further details, see ETSI GSM 05.02 Protocol. The number of packet channels used varies with the MS class. When allocating radio resources to the MS, the PCU takes into consideration the factors from multiple perspectives, such as the data transmission volume of the MS, the required QoS grade, available radio channels.
Allocating Uplink and Downlink Resources Based on Service Priorities

There are three service priorities: downlink priority (for example the downloading), uplink priority (for example the uploading), and neutral priority (for example the ping). When the capacity of multi-timeslots can be satisfied, allocate downlink channels and uplink channels as many as possible to the downlink priority and uplink priority respectively. Allocate two uplink timeslots to the neutral priority if there are two uplink timeslots left.
2.2.6 System Information Broadcasting

The system information is mainly used to broadcast the parameters necessary for the MS, to access the network required by the service. When the cell supports the GPRS service, the SI13 message is added to the BCCH. If not, the SI13 is not broadcast. The cell may or may not be configured with PBCCH. The existence of PBCCH is notified to the MS through the SI13 message. The PBCCH broadcasts the packet system information dedicated to the GPRS. The packet system information is of the following types: PSI1, PSI2, PSI3, PSI3bis, PSI4, PSI5, and PSI13. PSI1 includes information such as cell selection, PRACH control, control channel description, and power control parameters ,etc.
2-8
Issue 05 (2008-05-30)
PSI2 includes information such as the reference frequency lists, cell allocation lists, GPRS mobile allocation lists, and PCCCH description, etc. PSI3 includes information such as the BCCH allocation list of the neighboring cell, serving cell /non-serving cell selection parameters, etc. PSI3 includes information such as the BCCH allocation list of the neighboring cell, non-serving cell selection parameters, etc. PSI4 includes the PDCH list for the MS measurement in the serving cell. PSI5 includes information such as measurement reports, network controlled cell reselection, etc. Similar to the SI13 broadcast over the BCCH, PSI13 includes the access-related information specific to the GPRS cells. PSI1PSI4 can be broadcast over PBCCH or can be sent over PACCH. PSI5 can be broadcast only over PBCCH, and PSI13 can be sent only over PACCH. When a cell has PBCCH, it does not send PSI13 message over PACCH. Instead, it broadcasts PSI1 periodically. When a cell has no PBCCH, it only broadcasts PSI13 over PACCH periodically. The BSS has the capability to send all GPRS-related system information, control high-speed and low-speed retransmission of system information, and control the transmission of system information over PACCH according to the configuration of cell PBCCH/PCCCH.
2.2.7 Radio Link Control

RLC (Radio Link Control) layer is responsible for the segmentation and re-assembly of LLC-PDUs. It uses a slide window protocol, using the acknowledged and unacknowledged modes. The same is to ensure the transmission of data between the peer layers. The size of RLC window of GPRS is 64, and that of EGPRS ranges from 64 to 1024. In the acknowledged mode, each data block sent by TBF (Temporary Block Flow) requires the acknowledgement from the receiving side. Otherwise, it has to be retransmitted. The acknowledged mode does not release TBF until all the data is sent and it receives the acknowledgement from the receiving side. In the unacknowledged mode, the data block sent by TBF does not require the acknowledgement from the receiving side. Filling bit replaces the data block that is missing or replaces the data block that has errors in transmission. When all the data is transmitted, TBF is ready for the release. The HUAWEI PCU6000 system supports both the acknowledged and unacknowledged modes, specifies the RLC mode for sending uplink data according to the request message of the MS, and determines the RLC mode for sending downlink data according to the type of downlink LLC-PDUs.
2.2.8 Channel Coding Schemes and CS Change Control

The GPRS has four channel coding schemes. Table 2-2 shows the allowable transmission rates and sizes of the RLC/MAC packet.
Table 2-2 Channel coding schemes Channel Coding Scheme Size of RLC/MAC Data Blocks (octets) Rate (kbit/s)
CS-1 CS-2
23 33
9.05 13.4
Issue 05 (2008-05-30)
2-9
Channel Coding Scheme
Size of RLC/MAC Data Blocks (octets)
Rate (kbit/s)
CS-3 CS-4
39 53
15.6 21.4
Different channel coding schemes have different transmission rates and different radio transmission quality requirements. The higher the transmission rate, the higher is the quality requirements for air radio transmission. In data transmission, the BSS can dynamically adjust the channel coding schemes, according to the change of radio quality. This is to make full use of radio resources, and to increase the transmission rate to ensure the transmission quality. The HUAWEI PCU6000 supports the four coding schemes from CS-1 to CS-4. The PCU is also capable to change dynamically into the four coding schemes according to the radio transmission quality.
2.2.9 Modulation and Coding Schemes and MCS Change Control

The EGPRS has nine modulation and coding schemes. Table 2-3 shows the allowable transmission rates and sizes of the RLC/MAC packet.
Table 2-3 Channel coding schemes Channel Coding Scheme Size of RLC/MAC Data Blocks (octets) Rate (kbit/s)
MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9
22 28 37 44 56 74 2x56 2x68 2x74
8.8 11.2 14.8 17.6 22.4 29.6 44.8 54.4 59.2.
Different modulation and coding schemes have different transmission rates and different radio transmission quality requirements. The higher the transmission rate, the stricter is the quality requirements for radio transmission. . In data transmission, the BSS dynamically adjusts channel-coding schemes, according to the change of radio quality to use radio resources completely, and to increase the transmission rate without affecting the transmission quality. The HUAWEI PCU6000 supports the nine modulation and coding schemes from MCS-1 to MCS-9 and is capable to change dynamically into the nine modulation and coding schemes, according to the radio transmission quality.
2-10
Issue 05 (2008-05-30)
2.2.10 G-TRAU Frame Transmission

The communication between the HUAWEI PCU6000 and the BTS uses the self-designed G-TRAU frame structure. RLC/MAC blocks are encapsulated in the G-TRAU frame. In downlink transmission, the PCU processes the data and control messages, forms a RLC/MAC block, and transmits it through the G-TRAU frame to the BTS. While in uplink transmission, the BTS decodes and transmits the whole RLC/MAC block through the G-TRAU frame to the PCU, which in turn processes the RLC/MAC block. Besides the RLC/MAC block, both the uplink and downlink G-TRAU frames carry in band signaling, which includes synchronization information, measurement information, control information, and check information. For different G-TRAU frame formats, there is different in band signaling. Through the in band signaling, the PCU and the BTS jointly achieve the GPRS BSS functions with minimum changes to the BSC module of the original circuit switching.
2.2.11 Radio Link Monitoring

To improve the transmission reliability in the GPRS system, several link-monitoring methods are used. The HUAWEI PCU6000 achieves the following link- monitoring functions specified in the protocol.
The Link Monitoring in the Mode of Uplink Dynamic Allocation

When the MAC is in dynamic allocation mode, the PCU allocates resources to each TBF through USF. The MS determines its authority in using the uplink channels by measuring its own USF in the allocated channels. Once the MS detects its own USF, it sends the data block onto the corresponding uplink channel. If the MS cannot correctly receive the USF due to poor radio link quality, it does not send data blocks to the network on the corresponding uplink channel. (As required by the protocol, the PCU judges the validity of the link on the monitored size of counter N3101.) N3101 is initially set to zero at the time of TBF establishment. One is added to the value of the counter N3101 for each radio block allocated to that mobile station, if no data is received. Once it receives the data block of the MS, N3101 is re-set to zero. When N3101 exceeds its maximum value N3101_max, the PCU starts the timer T3169. When T3169 expires, TBF is released and the corresponding resources are reused.
Downlink Monitoring
For the downlink TBF, the PCU sets RBBP in the downlink data block. In this manner, it allocates an uplink-signaling channel to the MS. The PCU monitors the signaling channel through the counter N3105 and thus checks the validity of TBF. N3105 is initially set to zero at the time of TBF establishment. The network should increment counter N3105 for each radio block allocated to that mobile station with the RRBP field, if no RLC/MAC control message is received. Once it receives the message correctly, N3105 is reset. When N3105 exceeds its maximum value N3105_max, the PCU starts start the timer T3195. When T3195 expires, TBF is released and the corresponding resource is reused.
Issue 05 (2008-05-30)
2-11
Uplink Release Monitoring

In accordance with the protocol, the PCU guarantees the normal release of uplink TBF through the counter N3103. N3103 is initially set to zero at the time of TBF establishment. When the PCU correctly receives all the data of uplink TBF, it sends the Packet Uplink ACK/NACK (FAI=1) message to the MS, and set RRBP for the MS to acknowledge the message. If the PCU does not receive the correct Packet Control ACK message, N3103 will increment by one. If N3103 exceeds its maximum value, the PCU will start the timer T3169. When T3169 expires, TBF is released and the corresponding resource is reused.
2.2.12 Radio Frequency Power Control

The HUAWEI PCU6000 provides the uplink open-loop power control algorithm. For the details, see ETSI GSM 05.08 Protocol. The open-loop power control presumes that the uplink and downlink have the same path fading, so that the MS can adjust the output power based on the received signal level.
2.2.13 Cell Reselection Control

Network Control Modes of Cell Reselection
The GPRS network control modes are of the following three types: NC0, NC1, and NC2: NC0: The MS should perform autonomous cell re-selection and should not send the measurement report. NC1: The MS should perform autonomous cell re-selection and send the measurement report. NC2: It is controlled by the network. The MS should send the measurement report and accept the cell re-selection controlled by the network. The HUAWEI PCU6000 determines the network control modes, according to the data configuration of the user. At present, it supports the NC0, NC1, and NC2 mode.
Autonomous Cell Reselection

The MS monitors the PBCCH/BCCH carriers of the neighboring cell, at any time, determines the optimal cell according to carrier signal intensity and base station color codes in the carriers, and starts the cell update process to notify the network of the cell where it is located.
Network Assisted Cell Change

The function of the network assisted cell change (NACC) realizes the Cell Change Notification (CCN) procedure. The system message of the adjacent cell required by an MS is sent to the MS before the cell reselection. The function requires the support of the MS and the BSC. The cell configuration supports the NACC. The NACC can accelerate the cell reselection and can shorten the time of the service interruption caused by the cell reselection.
Cell Change Control

According to the parameters of cell system information broadcast, the MS periodically submits the measurement report to the BSS. The BSS in turn sends the packet change cell message to the MS. It also orders the MS to select new cell according to the MS measurement reports, the loads of each neighboring cell.
2-12
Issue 05 (2008-05-30)
2.2.14 Supporting the PFM/PFC

The Packet Flow Context Management (PFM) is used to satisfy the QoS demand that is in higher priority. The PFM is a new feature introduced for the guaranteed bit rate (GBR). The PFM supplies the setup, delete, and modification of the Packet Flow Context (PFC).
2.2.15 Flow Control and QoS Guarantee

Flow Control
As the Gb interface and the Um interface have different physical media and transfer protocols, they have different transmission rates. The transmission rate of the Gb interface is higher than that of the Um interface. In the downlink data transmission, the data transmission at the Um interface is influenced by the MS multi-slot capability, radio quality, and available radio channels in the cell. The data transmission rate is not constant, which makes the flow control of the downlink data necessary.
The cell bucket is the maximum packet data volume that can be stored in the cell, which varies with the number of packet channels in the cell. The MS bucket is the maximum packet data volume that can be stored for the MS, which varies with the number of packet channels allocated to the MS.
When the cell works normally, the PCU starts the flow control process, and periodically reports the bucket size and bucket leak rate, according to the condition of the packet channels in the cell. The PCU also periodically submits the reports of the bucket size and the bucket leak rate of the MS depending on the radio resources used by the MS. The SGSN adjusts the downlink data flow speed of the cell and each MS according to the parameters reported, so that it can control the downlink data flow.
The bucket leak rate is the rate of data transmission. The PCU system controls the downlink data flow, periodically the bucket size and bucket leak rate of the current cell and the current MS to the SGSN. The PCU also adjusts the parameters reported according to the change of cell packet resources and the resources occupied by the MS.
Quality of Service Guarantee

The GPRS QoS (Quality of Service) includes the following indexes: precedence class, delay class, reliability class, peak throughput class, and mean throughput class. These can be further divided into many sub-classes. (Since all these indexes are applied to the end-to-end packet data transmission, they must meet the QoS according to the "best effort" class. That is, the principle of optimal utilization of resources to transmit data as quickly and correctly as possible. The end-to-end packet transmission involves air interface radio resource, Gb interface frame relay link resource, GPRS backbone network transmission bandwidth, and processing capability of all kinds of GPRS equipment. The services of different QoS classes occupy different system resources. The QoS of the users are also different. Therefore, the telecom operator chooses a flexible charging strategy, according to different QoS classes and different user classes, which will be conducive to the promotion of the GPRS service.
Issue 05 (2008-05-30)
2-13
HUAWEI PCU6000 supports bandwidth guarantee, ARP, and THP. According to the bandwidth guarantee, ARP, and THP functions, the MS can be categorized into: Supporting the GBR The assigned bandwidths satisfy the service requirements. They are stable and have high priority. However, the bandwidth resources of other MSs are not occupied. When the bandwidths cannot satisfy the service requirements, the SGSN must be informed. Not supporting the GBR The remaining bandwidths (the bandwidths remained after the MSs that supporting the GBR are assigned) are assigned in Best Effort mode. They have low priority and have the minimum bandwidth. No mutual exclusion happens. MS not supporting the GBR can be categorized into:
Supporting ARP and THP The higher the ARP and THP is, the more bandwidth the MS has. The lower the ARP and THP is, the less bandwidth the MS has.
Not supporting ARP and THP MS not supporting ARP and THP has smaller bandwidth than MS supporting ARP and THP. Different types of MSs not supporting ARP and THP have the same bandwidth.
The PFM/PFC procedure is the prerequisite of realizing the bandwidth guarantees. The PFM/PFC controls and manages the PFC. Related functions include the setup, modification, and deletion of the PFC.
2.2.16 Mobility Management and Communication Management

Mobility Management
The mobility management function is applied to PLMN (Public Land Mobile Network) to keep track of the current location of the MS. The mobility management function of the GPRS network is similar to that of the current GSM. One or more cells constitute a routing area (it is a subset of a location area), and one SGSN provides service to one or more routing areas. The tracking of the MS depends on the MS mobility management state. The GPRS mobility management includes the GPRS Attach/Detach, cell/RA (Routing Area) update, combined routing area/location area update, and paging. When an MS finishes the GPRS Attach, the SGSN creates a MM context for the MS, to store the information of the user current location and state. When the MS roams between different cells and routing areas, it starts the cell/routing area update procedure, and the SGSN stores the latest information of the MS. (In this way, the MS location is tracked.) When the MS starts the combined GPRS Attach/IMSI Attach, combined location area/routing area update or other procedures, the SGSN communicates the MS location information to the MSC through the Gs interface. In this way, one mobility management process alone can track the MS in the packet switching service and circuit switching service. For the specific process, please refer to the ETSI GSM 03.60 Protocol. Due to the layer-by-layer encapsulation of packet data, rest of the signaling in the mobility management procedures, except the paging procedure is transmitted as data in the BSS. That is, the BSS involves only the paging function in the mobility management. When the BSS receives the paging packet sent by the SGSN, it picks out the required information and sends the paging message through the air interface.
2-14
Issue 05 (2008-05-30)
Communication Management
The GPRS communication management includes the session management, charging management. As all of the upper layer signaling is transmitted as encapsulated data units, the BSS transmits the signaling data without participating in the session management process. In addition, the charging information is collected at the SGSN and the GGSN. The BSS does not participate in the charging management.
2.2.17 Gb Over IP
At the Gb interface, the NS (Network Service) layer realizes the functions such transmitting NS SDU data between the BSS and SGSN, indicating network congestion, and indicating status for the upper layer. The 3GPP protocols regulate that the sub-NS layer is carried over the frame relay network or IP-based network. The frame relay network carrying the Gb interface is realized in earlier PCU versions. The PCU V300R008 adds the feature of Gb over IP link, that is, sub-NS over IP. The remote point-to-point communications on the Gb interface is carried between the local NS-VL and peer NS-VL. The two points form an IP NS-VC. Each IP NS-VC is a virtual communications path between peer entities. In the Gb over IP network, each NS-VC is constructed of four elements (local IP address, local UDP port, peer IP address, and peer UDP port) for the PCU equipment. The PCU communicates with the SGSN according to the UDP protocols.
2.2.18 PFC High-Priority Preemption

High-priority preemption enables a high-priority MS to be allocated block resources first than a low-priority MS. That is, the GBR MS with a high priority can preempt the resources of the GBR MS with a low priority. The reasonable resource allocation enables the GBR requirements be fulfilled through negotiation and preemption. The introduction of the priority-based preemption strategy helps increase the access success rate and guarantee the QoS of high-priority subscribers when the resources are insufficient.
On receiving the access request from an MS, the system checks whether there are available resources. If there are no available resources but preemption is allowed for the service that the MS requests, then the system allocates the resources of the low-priority MS to the high-priority MS. This scheme enables the successful access of new service request.
Issue 05 (2008-05-30)
2-15
2.3 Signaling Function

2.3.1 Gb Interface Signaling
Figure 2-1 shows the Gb interface signalling plane. The protocols of all layers at the Gb interface are described below.
FR
The frame relay sub-layer FR of the Gb interface is a part of the NS layer sub-network service protocol. The frame relay module interworks between sub-networks, and helps to establish the connection (point-to-point) between the PCU and the SGSN through the direct dedicated leased line or through the frame relay network. The point-to-point connection refers to the direct connection between the PCU and the SGSN. In general, the PCU is DTE and the SGSN is DCE. (The intermediate network connection), as shown in Figure 2-3.
Figure 2-3 Gb interface point-to-point frame relay connection
Gb PCU
SGSN
Figure 2-4 shows the connection between the HUAWEI PCU6000 and the SGSN based on frame relay net.
Figure 2-4 Gb interface intermediate frame relay network connection
Frame Relay Network PCU Gb Gb SGSN
HUAWEI PCU6000 supports the above two ways of connections. The Local Management Interface (LMI) of the HUAWEI PCU6000 frame relay sub-layer of Huawei supports the management and maintenance of the PVC (Permanent Virtual Circuit). In supporting the PVC, the frame relay layer provides flexible bandwidth choices for the NS layer. Users can configure the NS-VC bandwidth in the range of 1kB1984kB. For the physical layer of the frame relay, the HUAWEI PCU6000 currently supports the E1 access mode. In case of network congestion, the frame relay layer submits the congestion indication, and the layer above the NS layer controls the congestion.
2-16
Issue 05 (2008-05-30)
IP
The Gb interface in the Gb Over IP network uses the IP protocols to transmit data. The IP transmission module interconnects sub-networks, so that the direct connection or IP-based connection (router connection mode) between PCU and SGSN can be realized. The direct connection in the Gb Over IP network refers to that the PCU and SGSN are connected directly without any other intermediate IP network. In this connection mode the switcher provides layer 2 switching for the PCU and SGSN.
Figure 2-5 Direct connection mode in the Gb Over IP network
The router connection mode in the Gb Over IP network refers to that the PCU and SGSN are connected through other intermediate IP network. In this connection mode the router provides layer 3 routing for the PCU and SGSN.
Figure 2-6 Router connection mode in the Gb Over IP network
HUAWEI PCU6000 supports the above two ways of connections. The LMI of the HUAWEI PCU6000 IP layer supports the management and maintenance of the Network Service Virtual Link (NSVL). Each RPPU for the Gb interface can provide up to 8 Mbit/s bandwidth for users. Therefore, the bandwidth cost is reduced. The Gb interface in the IP network provides 8 Mbit/s bandwidth for users, so that the bandwidth cost is reduced. In case of network congestion, the HUAWEI PCU6000 submits the congestion indication, and the layer above the NS layer controls the congestion.
NS
NS here refers to the network service control part of the NS protocol. The NS protocol layer is distributed on both sides of the Gb interface and its functions are symmetric on both sides. The NS layer protocol transmits the NS SDUs (Service Data Unit) through the Gb interface, configuring the NS-VC and managing its state, providing the network congestion state and network state reports to the upper layer service module, and sharing the load of the user data. All the messages transmitted through the Gb interface are transmitted in the form of NS SDU at the NS layer. The normal running of the NS layer provides a reliable path and guarantee for the normal running of the upper layer protocol. Normally, when the NS SDUs are transmitted at the NS layer, the NS layer guarantees its sequence, which is realized through LSP (Link Selection Parameters). However, in abnormal conditions (say, the load sharing), the sequence is not well guaranteed.
Issue 05 (2008-05-30)
2-17
The NS-VC state management function includes the reset, block, unblock, and test operations on the NS-VC. To stop using a certain NS-VC, the BSS or the SGSN sends the BLOCK message to the peer entity and block the NS-VC. At the same time, it changes the NS layer load sharing and share the traffic on the NS-VC with other NS-VCs. To use the blocked NS-VC, the BSS or the SGSN sends the UNBLOCK message to the peer entity to unblock the NS-VC. The BSS or the SGSN will also re-share the load at the NS layer, and inform the NS user (such as the BSSGP layer) of the new NS layer transmission capability. After a new NS-VC between the peer NS entities is established or the system is recovered from fault, the BSS or the SGSN resets the NS-VC. After the reset, the NS-VCs on both sides of the Gb interface are blocked and activated. To check whether the end-to-end communication exists in a certain NS-VC, the BSS or SGSN sends the test message to the peer entity for the testing operation. The testing operation is conducted after the successful reset, and it will periodically repeat the transmission of test messages. When detecting whether the bottom layer link is faulty or in congestion, the NS notifies the NS layer users through the congestion indication and state message. The NS also sends the transmission capability to the NS layer users to act accordingly. The most important function of the NS layer is the load sharing of user data. When the users above the NS layer send data to the NS layer, the NS layer allocates a LSP value to every user, which is transmitted with the data packet to the NS layer. The NS layer guarantees the sequence of user data transmission according to the LSP value. The NS layer chooses one or more NS-VCs to transmit the user data packet according to the LSP and the BVCI values. This is to ensure that the NS layer load is evenly distributed to all the unblocked NS-VCs of the same NSE. The HUAWEI PCU6000 supports all the NS layer functions of data transmission, NS-VC link management, user data load sharing.
BSSGP
The BSSGP protocol layer is distributed at both sides of the standard Gb interface, but the functions are asymmetric. The BSSGP protocol implements the transmission of signaling message and user data, downlink data flow control, BVC blocking and unblocking, BVC dynamic configuration and management, interface message error detection. The BSSGP protocol includes the following the basic procedures: Uplink and downlink data transmission procedure Paging procedure Notification procedure of radio access capability Radio access capability update procedure Radio state procedure Suspend and resume procedure FLUSH_LL (Logic Link) procedure Flow control procedure PTP BVC blocking and unblocking procedure BVC reset procedure Trace procedure PFM/PFC procedure
2-18
Issue 05 (2008-05-30)
The HUAWEI PCU6000 reports to the SGSN the default bucket size and bucket leak rate of the MS and the cell, depending on the data configuration. According to the change of the MS and cell radio resources in the process of transmission, and in cooperation with the SGSN, the PCU reports in time to SGSN the actual bucket size and bucket leak rate of the MS and cell. This is to control the downlink data flow. On request, the HUAWEI PCU6000 starts the MS radio access capability update and other procedures, gets the MS radio access capability from SGSN to optimize the resource allocation for the MS. The HUAWEI PCU6000 has the capability to start the GPRS service, suspend and resume procedures in case of the MS service change. This is to ensure the correctness of data transmission and avoid unnecessary data retransmission. The PCU also has the capability to start the radio state procedure with regard to the radio link quality of data transmission and the availability of current MS. It reports on time to the SGSN the radio state of the MS, cooperates with the SGSN to complete the FLUSH_LL procedure, and transfers or deletes the data temporarily stored for the MS. The HUAWEI PCU6000 has the capability to start PTP BVC blocking, unblocking and resetting procedures according to the cell state and NS-VC state. HUAWEI PCU6000 realizes the PFM/PFC procedure. The PFC is controlled and managed. Related functions include the support for the PFM/PFC procedure by the network and also the setup, modification, and deletion of the PFC.
2.3.2 In-Band Signaling Between PCU and BTS

The signaling between the PCU and the BTS is transmitted through the G-TRAU frame, including the synchronization information, measurement information, control information, and check information.
2.3.3 Pb Interface Signaling

The HUAWEI PCU6000 is a type of semi-independent equipment. The PCU and the BSC are connected through the Pb interface. The Pb interface is a nonstandard interface that mainly realizes the MS-originated packet data transmission procedure in CCCH, and the resource coordination between the PCU and the BSC.
2.4 Operation and Maintenance Function

2.4.1 Network Maintenance
The HUAWEI PCU6000 communicates with Network Maintenance Center through SNMP interface. The SNMP subsystem of the HUAWEI PCU6000 offers the following function: Network Maintenance Center gets the configuration data of the PCU by the SNMP interface. The configuration data include system information and Gb interface configuration information. PCU reports the alarm information to Network Maintenance Center by the TRAP in SNMP interface. Network Maintenance Center inquiries the result of performance measurement by SNMP interface
Issue 05 (2008-05-30)
2-19
The HUAWEI PCU6000 supports SNMP sampling based on the granularity of cell, the PCU frame, or the BSC.
2.4.2 Operation and Maintenance Management

The main functions are as follows:
Service Related
Inquire/block/unblock/reset cell Inquire/block/unblock LAPD link Inquire/block/unblock PCIC Inquire/block/unblock PDCH Inquire/block/unblock/reset PTP Inquire/reset SIG BVC Inquire/block/unblock/reset NSVC Inquire/activate/deactivate/clear PVC Trace interface information
Hardware Related
View hardware version Power on/off POMU board and RPPU board Reset board Switch over active and standby POMUs Format or partition hard disk and query the status of hard disk
Software Version Related

View software version Load software Software patch
Software Status Related

Configuring network parameters Configuring OMC parameters
Operation Related
Configuring the language of Man-machine interface (Chinese/English) User priority management Querying log of operation
2-20
Issue 05 (2008-05-30)
2.4.3 Configuration Management

The HUAWEI PCU6000 configuration management is achieved mainly through PCU-DB. The PCU-DB provides the following functions: Checking PCU configuration data validity Configuring PCU data Inquiring PCU data Adding, deleting and modifying PCU data Reverse compilation of PCU configuration data
2.4.4 Alarm Management

The HUAWEI PCU6000 alarm management system collects and processes the alarm messages of the PCU system. The alarm messages are stored in the hard disk of the POMU board, and sent to the OMC server for centralized storage when the system is connected to the OMC server. When the HUAWEI PCU6000 host is abnormal, the system sends the message as an alarm to the visible user interface. It notifies the maintenance personnel of the current state of the system, and the recommended solutions.
2.4.5 Performance Measurement

The HUAWEI PCU6000 traffic measurement management includes: Register the performance measurement task Collect and process the performance measurement result Inquire task state Inquire task measurement results Delete performance measurement task Backup the results of measurement between active POMU and standby POMU.
2.4.6 Interface Tracing

The interface tracing function intercepts the messages of Um, Pb, Gb, and Huawei-developed interfaces. It also interprets the bytes in the message and provides a means for the maintenance personnel to locate the problems. For different interfaces, it provides the means to set the filtering conditions to facilitate the user in viewing different types of messages at the interface. The filtering conditions at the Um interface: Cell number, TRX number, dummy message, null paging message, and system information message. The filtering conditions at the Pb interface: Cell number, paging message and maintenance message. The message tracing function at the Gb interface includes the BSSGP PTP BVC message tracing and BSSGP SIG BVC message tracing.

The filtering conditions for the tracking of BSSGP PTP BVC messages are 15-Byte or 16-Byte cell ID. The filtering conditions for the tracking of BSSGP SIG BVC messages are Nsei.
Issue 05 (2008-05-30)
2-21
2.4.7 Security Management

The HUAWEI PCU6000 takes steps to improve the stability and security in software and hardware aspects. The PCU software provides the backup mechanism for the boards and supporting functions. If during the running of the system, the board is detected to be faulty (hardware or software fault), the system acts accordingly to handle it automatically or to provide the alarm message to the maintenance personnel to handle it manually.
Board Backup Mechanism

The system sends the fault message to the alarm console or maintenance console to notify the maintenance personnel to provide timely maintenance. The system provides the abnormality processing for the software fault, keeps the on-site fault information, so that the maintenance engineer can locate the system fault with the help of the message. In case there is a standby board, the active board creates a backup of data on time, thus maintaining the consistency of running data in the active and standby boards. Once the active board is faulty, the standby board is started. For the faulty board, the board is automatically reset at the end of the software abnormality handling procedure. This reduces the recovery time.
Supporting Function
Inter-board communication between the active and standby POMU boards (IPC_SYS). Handshaking between the active and standby POMU boards. Board running state check by CPCI communication layer. Abnormality protection. Data backup between active and standby board. Manual switchover. Fetch on-site abnormal message. View board task state. View board state.
2-22
Issue 05 (2008-05-30)
3 System Structure
3
About This Chapter
Section Describes
System Structure
3.1 Overview 3.2 Hardware Structure 3.3 Software Structure 3.4 Equipment Features
This section describes the overview of the system structure. This section describes the hardware architecture of PCU. This section describes the software architecture of PCU. This section describes the equipment features of PCU.
Issue 05 (2008-05-30)
3-1
3 System Structure
3.1 Overview
The HUAWEI PCU6000 uses modular structure formed by placing several PCU frames together. The PCU frame comprises three modules, that is, POMU, RPPU, and HSC. Figure 3-1 shows the PCU logic structure.
Figure 3-1 PCU logic structure
LAN Switch M2000 Server E1

RPPU
SGSN E1 BSC BTS
POMU
E1 1+1
High-speed data bus PCU frame 1 PCU frame 2
3.2 Hardware Structure

The basic unit of the PCU6000 is the PCU processing frame (referred to as PCU frame). The configuration of a PCU cabinet is the same as that of the HUAWEI PCU6000. That is, a 19-inch standard N68E-22 cabinet. The dimensions of the PCU6000 cabinet are 2200 mm (height) x 600 mm (width) x 800 mm (depth). The height of the available space in the cabinet is 46 U (1 U = 44.45 mm). The weight of an empty cabinet is 100 kg.
3-2
Issue 05 (2008-05-30)
3 System Structure
The basic unit of the PCU6000 is the PCU6000 processing frame (referred to as PCU frame). Figure 3-2 shows the configuration of a PCU cabinet. Each PCU cabinet holds up to three PCU processing frames connected with the OMC through the LAN switch for centralized monitoring.
Figure 3-2 Configuration of the HUAWEI PCU6000 cabinet
2U Power distribution box 1U LAN switch 1U LAN switch cabling trough 3U Dummy panel
3U Dummy panel
3U Dummy panel
2U Air deflector
9U
PCU6000 processing frame
2U Air deflector
9U
PCU6000 processing frame
2U Air deflector
Issue 05 (2008-05-30)
3-3
3 System Structure
Figure 3-3 shows the HUAWEI PCU6000 frame configuration. The PCU frame contains 2 POMUs (Packet Operation & Maintenance Unit), 2 HSCs (Hot Swap Controller), 12 RPPUs (Radio Packet Processing Unit), 12 E1TMbs (E1 Terminal Multiplexes), 2 BSUs (Back Storage Unit), and 4 UPWRbs (power supply unit). Huawei recommends that the No.0No.5 and No.10No.12 RPPU boards be used for the Pb interface, and No.13No.15 RPPU boards for the Gb interface. The POMU software operates in the POMU board, the RPPU software operates in the RPPU board, and the HSC is used for the hot swap control.
Figure 3-3 HUAWEI PCU6000 processing frame configuration
The hardware structure of a HUAWEI PCU6000 processing frame is shown in Figure 3-4.
Figure 3-4 HUAWEI PCU6000 hardware structure
BSC
RPPU
RPPU
L2PU/ HLPU L2PU/ HLPU
BSC
P O M U
N+1
L2PU/ HLPU L2PU/ HLPU

1+1
SGSN
SGSN
PCU6000 processing frame LAN Switch
In the HUAWEI PCU6000 processing frame, the POMU board is in 1+1 POMU simple hot backup mode. One BSC can be connected to several RPPU boards. One RPPU can be connected with maximal four BSCs, but it can only handle the data from one BSC at a time.
3-4
Issue 05 (2008-05-30)
3 System Structure
3.3 Software Structure

Figure 3-5 shows the HUAWEI PCU6000 software structure. The PCU software can be divided into the following parts: PCU Operating system POMU software RPPU software L2PU/HLPU software
Figure 3-5 HUAWEI PCU6000 software logic structure
PCU software
POMU software
RPPU software
L2PU/HLPU software
State monitoring & management Fault management Software management Database management Performance measurement PCU operating system OS core module I/O processing System initialization
State monitoring & management Fault management Software management Database management Performance measurement RLC/MAC protocol processing Gb interface processing Pb interface processing G-Abis interface processing Link layer protocol processing
Issue 05 (2008-05-30)
3-5
3 System Structure
3.3.1 HUAWEI PCU6000 Operating System

The HUAWEI PCU6000 operating system consists of the OS core module, input/output processing module, and system initialization module. Please note that the operating system of HUAWEI PCU6000 is the same as that of M900/M1800 GSN.
OS Core Module
The PCU OS core module supports the following functions: OS initialization Real-time allocation of CPU time (task scheduling) Dynamic management of the system memory Communication and synchronization of tasks System timing System date and time management Measurement of the CPU occupancy
Input/Output Processing Module

The input/output processing module has the following functions: Inter-processor communication (IPC) Message reception and distribution Message transmitting and routing TCP/IP Socket communication Serial port communication IPC communicates between boards and between frames. TCP/IP Socket is for remote operation and maintenance as well as for the communication between frames, and the serial port communication is for local operation and maintenance.
System Initialization Module

The system initialization module provides the following functions: Software loading and self-checking Initialization of the applied modules and the synchronization of the initialization processes Active/standby switchover initialization The HUAWEI PCU6000 operating system is based on Huawei mature operating system VOS (Virtual Operation System). It is a virtual interface layer between the operating system and application programs, which is based on a certain multi-task operating system. VOS can be applied to various commercial operating systems including VxWorks, pSOS, Unix, and Windows 9x/NT. VOS shields the differences in the basic operating systems, enabling the convenient transplantation of the software of the whole system.
3-6
Issue 05 (2008-05-30)
3 System Structure
VOS builds up a transaction and message driving mechanism. As a task has more than one message queue, and the transaction for each message queue has different priorities. Therefore, the mechanism enjoys better real-time feature than the pure message driving mechanism. Besides, the OS uses a unified format in the distribution of transaction and message and a unified format in transaction processing functions. However, the upper layer applied modules need only the message processing functions to build the whole software system; thus greatly improving the reliability of the whole product. VOS participates in the management of memory, task, transaction, message, semaphore and time, provides plenty of debugging means and real- time monitoring functions. For the abnormal errors, the OS has perfect recovery measures such as the preservation of abnormal site, the restarting of abnormal tasks, the active and standby switchover, which increase the stability and the robustness of the system. VOS unifies the formats and processing methods of the PCU internal message, and it employs the same interface in receiving and sending module messages within a board and among boards. This facilitates not only the distributed processing of the whole system that improves the overall performance, but also the tracing of messages and the debugging of programs.
3.3.2 POMU Software

POMU software is divided into the following 5 modules:
State Management and Monitoring Module

The state management and monitoring module supports the following functions: Monitoring the running status of all the hardware equipment within a PCU6000 processing frame. Process the state change requests (originated internally or in operation and maintenance activities) from the hardware equipment. Control the running status of all the hardware units within a PCU6000 processing frame.
Fault Management Module

The fault management module achieves the alarm detection and hardware fault management functions, including the alarm detection, fault detection, fault diagnosis, fault isolation, and service recovery.
Software Management Module

The software management module supports the software upgrade by local or remote loading. Through the software loading, the module upgrades the software in the POMU board and the RPPU board. The local loading is based on the serial port communication, whereas the remote loading is based on the TCP/IP communication.
Database Management Module

The database management module provides the data and parameters necessary for the running of the system, which include the following: Configuration of the equipment physical and logic parameters Gb interface configuration data G-Abis interface configuration data
Issue 05 (2008-05-30)
3-7
3 System Structure
Pb interface configuration data Cell system information parameters Cell measurement preprocessing algorithm parameters Cell power control algorithm parameters Cell CS change algorithm parameters Cell flow control algorithm parameters Cell EGPRS parameters The data and parameters necessary for the running of the system of the PCU are stored in the PCU configuration database, which is a relational database with each relational table mutually independent. The PCU configuration database also describes a group of data that are related to each other. The database provides multilevel indexing mechanism and a dichotomy algorithm. The PCU configuration database is also a distributed database consisting of the main database in the POMU board and the local databases in the individual processing unit (RPPU boards). The local databases in the processing units are the subsets of the main database. They store the configuration parameters necessary for the normal running of the local processing units. When the data in the main database are modified, the database processing module uses the commands of insert, modify, and delete. This is to notify the processing interface to update the main database. The mechanism of principal and subordinate databases working together improves the efficiency in processing the local transactions and guarantees the consistency and reliability of the databases. The database management module is divided into the relational database management system (RDBMS) and the data interface module. The RDBMS is a highly efficient and reliable distributed database. It uses the transaction mechanism in which the transaction submission and scroll mechanism guarantees the consistency and completeness of the database is used. The data interface module provides a unified interface for the other applied modules of the system to query and modify the database. The applied modules access the unified operation on the configuration database through the database interface module.
Performance Measurement Module

The performance measurement module provides the measurement reports related to the system performance. The statistical data and reports are of considerable significance to the establishment and perfection of the GPRS traffic model. It is also important for the optimization of GPRS network planning.
3.3.3 RPPU Software

Each module in the POMU software has a corresponding module in the RPPU software that serves as its subordinate module. For example, the database management module of the POMU software drives the update process of a database. If the update process affects the database view resident in the RPPU, it can be fulfilled by activating a subordinate process of a certain database management module in the RPPU software. The RPPU software also contains the software management module, state monitoring and management module, fault management module, database management module and performance measurement module. Besides, the RPPU contains the following processing modules.
3-8
Issue 05 (2008-05-30)
3 System Structure
RLC/MAC Protocol Processing Module

The RLC/MAC protocol processing module accomplishes the radio interface RLC/MAC layer functions stipulated in the ETSI GPRS Specifications. The RLC/MAC protocol processing module is the most essential and complicated service functional module of the RPPU. It completes the following functions: Packet radio channel mapping, including the mapping of PBCCH, PCCCH, PDTCH and PACCH. Packet system information broadcasting Paging scheduling Access grant scheduling The channel class and block class allocation of the radio resources PDCH/TCH dynamic switch TBF establishment and release The RLC data packet transmission of TBF The assembly of uplink LLC PDUs and the segmentation of downlink LLC PDUs The measurement report preprocessing Power control decision CS/MCS dynamic change decision Downlink flow control decision
Gb Interface Processing Module

The Gb interface links the PCU and the SGSN and provides a reliable channel for the exchange of the signaling information and the user data. The Gb interface also allows multiple users to use the same physical resource thus tremendously increasing the utilization ratio of the physical resource. The Gb interface accomplishes the functions of load sharing, user data flow control, data compression, and sliding window management. The main function of the Gb interface processing module is to process the protocols of the three layers, that is, L1 layer, NS layer and BSSGP layer. The NS layer is further divided into sub-network service part and network service control part. The sub-network service layer uses the FR protocol. The Gb interface processing module is composed of the FR processing sub-module, NS protocol processing sub-module and BSSGP processing sub-module. FR (Frame Relay) protocol is realized in the L2PU/HLPU board. For details, refer to section 3.3.4 "L2PU/HLPU Software." . The functions of the NS protocol processing sub-module are symmetrical along the Gb interface. The NS protocol processing sub-module performs the following functions: Transmission of NS SDUs through the Gb interface Configuration and state management of NS-VC Provision of network congestion signal and network state report to BSSGP module Load sharing between NS-VCs within the same NSE The BSSGP layer processing sub-module completes the following functions: Transmission of signaling data and user data Downlink data flow control Acquisition of MS radio access capability
Issue 05 (2008-05-30)
3-9
3 System Structure
Blocking and unblocking of BVC Dynamic configuration and management of BVC Suspend and resume GPRS operation Radio status report of the MS
G-Abis Interface Processing Module

The G-Abis interface processing module has the following functions: E1 physical interface function Processing of G-TRAU frame (including the in-band signal processing between BTS and PCU) TDMA frame synchronization between the PCU and the BTS CCU
Pb Interface Processing Module

The Pb interface processing module has the following functions: E1 physical interface function LAPD processing Reception and distribution of Layer 3 messages at the Pb interface Routing and transmission of Layer 3 messages at the Pb interface
3.3.4 L2PU/HLPU Software

The L2PU/HLPU is a card inserted in the RPPU board. It mainly fulfills the link protocol processing functions as follows:
LAPD Protocol Processing Module

LAPD protocol processing module fulfils the link maintenance of LAPD. It has the following functions: LAPD link connection and disconnection Link monitoring Transmission and reception of Layer 3 messages at the Pb interface
Frame Relay Protocol Processing Module

The frame relay protocol processing module provides the communication between sub-networks. It also realizes the point-to-point connection or indirect connection between the PCU and the SGSN through intermediate frame relay network. The FR layer processing sub-module has the following functions: Support the standard ITU-T E1 interface and the ANSI T1 interface Apart from the ITU-T Q933 Appendix A regulated in GSM protocol, the Local Management Interface (LMI) supports ANSI T1-617 Appendix D Support the management and maintenance of Permanent Virtual Circuits (PVCs)
3-10
Issue 05 (2008-05-30)
3 System Structure
TRAU Protocol Processing

The TRAU protocol processing supports the following functions: The multiplexing and de-multiplexing of G-TRAU frame E1 exchange and transparent transmission, and Pb interface multiplexing Multiplexing on the A interface and Gb interface
3.4 Equipment Features

3.4.1 Gb Interface
For the features of Gb interface, refer to section 4.1.3 "Characteristics of the Gb Interface."
3.4.2 G-Abis Interface

For the features of the G-Abis interface, refer to the 4.2.5 "Characteristics of the G-Abis Interface."
3.4.3 Pb Interface
The HUAWEI PCU6000 supports the topology in flexible ways. One PCU can be connected with multiple BSCs. The PCU connected with multiple BSCs converge the packet services at the base station side. This tremendously cuts down customers investment in the equipment in the area with a comparatively small GPRS volume, especially in the initial stage of the GPRS operation. For the topologies of Pb interface and Gb interface, refer to section 1.2 "Topology." For other features of Pb interface, refer to section 4.3.3 "Characteristics of Pb Interface."
3.4.4 Operation and Maintenance

Integrated OMC System
The operation and maintenance of the HUAWEI PCU6000 realizes the flawless integration with that of the M900/M1800 BSS. The integrated and unified operation and maintenance interface enables the user to conduct integrated operation and maintenance of the GSM circuit-switched network and packet-switched network.
Convenient Remote Login Maintenance

The HUAWEI PCU6000 supports the operation and maintenance of the system through the LAN or by remote login through WAN. Through the remote login operation and maintenance, the user achieves the remote management and maintenance of the GSM/GPRS network. The remote management and maintenance of the GSM/GPRS network through the Internet greatly brings down the user's investment in the operation and maintenance equipment.
Issue 05 (2008-05-30)
3-11
3 System Structure
Local Maintenance with Complete Functionality

In the local maintenance mode, through the standard Windows hyper terminal the user completes most of the functions normally achieved through the remote login maintenance.
3.4.5 Clock Synchronization

The HUAWEI PCU6000 uses different clock resources at the Pb interface side and the Gb interface side. At the Pb interface side, the PCU achieves synchronization with the BSC that connects to the PCU through the E1 link, and meets the transmission requirements of the clock synchronization of the whole circuit-switched GSM network. There are two cases on the Gb interface side. If the PCU directly connects with the SGSN, the clock of the PCU synchronizes with that of the SGSN. If the PCU is to synchronize the SGSN through the frame relay network, it synchronizes the frame relay network directly connected with it (the SGSN also synchronizes the frame relay network directly connected with it). In either case, the PCU has an end-to-end clock synchronization with the frame relay network connected directly to it, thus meeting the requirements of the frame relay transmission.
3.4.6 Overload Processing

The HUAWEI PCU6000 provides flexible and efficient overload processing mechanism. When detecting any overload, the HUAWEI PCU6000 automatically activates the overload processing procedure to bring down the load of the system, and guarantees the system reliability in case of heavy traffic. The HUAWEI PCU6000 overload is roughly divided into the following cases: Processor overload Radio resource overload I/O equipment overload Message queue overload The HUAWEI PCU6000 overload processing is achieved through the system traffic reduction by controlling the uplink flow and the downlink flow. In either case, the control is done at the flow source. The uplink flow control is achieved by controlling the access requests originating from the MS (including the paging response) or by delaying the answer to the MS access requests. The control of the uplink access requests is achieved by controlling the random access of the PRACH/RACH. Delaying the answer to the MS access requests is achieved by the packet access queuing indication procedure. Bringing down the random access of the PRACH/RACH is achieved by extending the interval for the random access retransmission or forbidding certain classes of MS accesses. Although the former may bring down the answering speed of the system to some degree and affect the system service quality, it is useful in expanding the system capacity, and therefore can be used in a reasonable way. The latter may severely harm the system service quality. Normally it is not used. The downlink flow control is mainly achieved through controlling the transmission of LLC PDUs of the SGSN through Gb interface. When necessary, the transmitted LLC PDUs or paging requests is discarded to bring down the downlink flow of the system. For different classes of overloads, the HUAWEI PCU6000 has different strategies.
3-12
Issue 05 (2008-05-30)
3 System Structure
Take the radio resource overload as an example. The system generally takes the following measures according to the precedence class to bring down the load to the normal level:
Step 1 Delay the answer to the access request with low QoS or reject the access request with low QoS Step 2 Control the downlink flow of the MS with low QoS (that is, reduce the number of LLC PDUs sent to the MS by the SGSN through the downlink flow control) Step 3 Release the TBF of the MS with low QoS Step 4 Discard some paging requests Step 5 Block alternately the access of some MSs according to the access classes
There are 16 MS access classes in a PLMN among which, classes 09 are randomly assigned to subscribers, classes 1115 are assigned to subscribers with special priority level, and class 10 is assigned for emergency calls. If the system is congested and certain MS accesses have to be prohibited to bring down the system load, generally the MSs of classes 09 should be prohibited and to guarantee fairness, the access should be prohibited alternatively between the MSs of classes 09.
----End
3.4.7 POMU Simple Hot Backup

To improve the error correction capability of the equipment, HUAWEI PCU6000 provides the POMU simple hot backup functionality. The main difference between warm backup and hot backup is as follows: when the POMU simple hot backup happens, the reset of the POMU due to switchover between the active/standby POMUs does not lead to the reset of the RPPU. Thus, the duration of service interruption can be reduced to 10 seconds, which improves system reliability. The functions of POMU simple hot backup are as follows: Data backup When the system operates normally, the active POMU saves its configuration data, performance measurement data, and alarm data to the standby POMU in real time. Once the switchover between the active POMU and standby POMU takes place, you can still view the performance measurement results and alarm information that are generated before the switchover. Though the alarm information produced during switchover is not reported to the M2000, OMC, and SNMP, the alarm information can be reported after the system restores to normal operation. Fault detection of the system The success rate of active/standby switchover is 99%. If the switchover fails, the services are interrupted and the active POMU does not function properly. The system resets the entire subrack to restores to normal operation. When a fault occurs, the system takes relevant measures as shown in Table 3-1.
Issue 05 (2008-05-30)
3-13
3 System Structure
Table 3-1 Measures for PCU faults Faults Corresponding Measures Taken by the System
Software and hardware faults, system breakdown Fault recovery
The system generates alarm for RPPU board faults, migrates the cells of the board to the designated board, resets the RPPU board (the board reset may fail in case of a hardware fault) The system generates alarm for the recovery of the RPPU board faults, migrates the cell back, that is, moves the cells back to the original place The system generates alarm and resets the RPPU board
RPPU board cannot reach the normal operation status RPPU board reset
The system generates reset alarm
System Clock Synchronization

The active POMU board, the standby POMU board and all the RPPU boards regularly synchronize the system time to ensure the time consistency for all the boards of the system.
3.4.8 Dynamic Data Configuration

The HUAWEI PCU6000 provides the function of dynamic data configuration, which minimizes the influence of configuration on the service. The HUAWEI PCU6000 uses the dynamic data configuration method when the related attribute data of the cell is configured. When the configuration is complete, the PCU only needs to restart the related cell to make the configuration effective without restarting the board, which may affect the normal service of other cells. However, in the process of configuring the data of physical link attributes, it is necessary to restart the board concerned after the change of configuration, because it involves the bottom-layer physical transmission paths. The change of data in the dynamic data configuration follows the given procedure: For the cells that are not started, the configuration data can be changed freely. For the cells that are started, first de-activate the cells with the maintenance commands, and then activate the newly configured data to make them effective. For convenience, a command is provided to update and make effective all the configuration data in a cell. The user only needs to change the data. The de-activation and activation of the cell is done by the command automatically.
When a cell is in active state, the record of the cell is saved in an RPPU board. The cell is initialized. When the state of the O&M is normal, this cell can provide packet service. When a cell is in inactive state, the record of the cell is not saved in any of the RPPU board and this cell cannot provide packet service.
3.4.9 Backup of the Cells of the Same BSC

To further improve the fault-tolerance of the system, reduce the negative effect brought by the RPPU board faults and minimize the possibility of the service interruption The PCU system provides the backup of the cells in the same BSC.
3-14
Issue 05 (2008-05-30)
3 System Structure
When configuring the data of the cell, the subscriber needs to configure the active and the standby RPPU boards that are connected to the same BSC. Normally, the cell runs the active RPPU board. However, in case of a fault on the active RPPU board, the cell can be run on the standby RPPU board through cell migration, and then the cell can continue to work on the standby board. The system monitors the status change of the RPPU board. It also monitors and records the operation status of all the cells of the system. When the system detects that the status of RPPU changes are from normal to faulty, it checks the cells configured on the board and their operation status. Migrate the cells using the RPPU board to the standby board, and activate the cell to continue the service. To reduce the standby RPPU board load and improve efficiency, the PCU migrates the cell back when the RPPU fault is cleared. When the system detects that RPPU changes are from faulty to normal, it checks the cells configured on the board and their operation state. It first deactivates the cells using the standby RPPU board, then activates the cells on the recovered RPPU board, migrate the cells from the standby RPPU board to the active RPPU board.
3.4.10 Software Loading

The HUAWEI PCU6000 provides a perfect software upgrade scheme by employing the popular Client/Server structure.
The Process Flow of PCU Software Loading

POMU board software loading flow
Figure 3-6 POMU software loading flow 1
Maintenance terminal Serial port terminal
TCP/IP FTP Server
POMU board
TCP/IP
Serial port FTP Client processing program
As shown in Figure 3-6, the PCU board software loading is performed through the serial port terminal or network port terminal with the FTP fetching the target file. When all the data are transmitted, the FTP client writes them into the Flash memory. To remotely load the software of the POMU board, you can load the software from the serial port. You can also load the software of the RPPU board described in the following part.
Issue 05 (2008-05-30)
3-15
3 System Structure
RPPU board software loading flow

Figure 3-7 RPPU software loading flow
Maintenance terminal
Telnet terminal LOAD Server
TCP/IP
TCP/IP
POMU board
Telnet Server SYS LOADER Data bus
Data bus RPPU board RPPU's FLASH Memory
Figure 3-7 shows the RPPU board loading flow. The LOAD Server is similar to the FTP Server. It is specially used for PCU software loading. SYS LOADER is one of the operating tasks on the POMU board.
3-16
Issue 05 (2008-05-30)
3 System Structure
L2PU/HLPU software loading flow

Figure 3-8 L2PU/HLPU software loading flow
Maintenance terminal Telnet terminal LOAD Server
TCP/IP
TCP/IP POMU board Telnet Server SYS LOADER Data bus
Data bus RPPU board IO LOADER Data bus
L2PU/HLPU board
Data bus L2PU/HLPU's FLASH Memory
Figure 3-8 shows the L2PU/HLPU software loading flow. In it, IO LOADER is one of the tasks running in the RPPU board that receives data from the data bus between the POMU and the RPPU. The IO LOADER then writes them into the Flash memory of the L2PU/HLPU through the data bus between RPPU and L2PU/HLPU.
Features of the PCU Software Loading

Simple user interface with high operability. All the software loading of the board is performed through the POMU board. The software loading of POMU, RPPU and L2PU/HLPU is done using simple loading command through the Telnet terminal. The software loading of the POMU, RPPU, and HLPU is performed through the serial port terminal. All the software loading through the Telnet terminal support remote link. PC (run with LOAD Server or Telnet terminal) loads software to the PCU based on dialing network. The POMU board supports 1+1 backup mode and the operation is not interrupted by software upgrading. Powerful fault tolerance measures. Apart from the application programs, the Flash memory of every board has a BIOS program, which is chosen to run for reloading when the board does not start in case of software upgrade failure.(It is not applied to Standby POMU board software loading through Telnet terminal.)
Issue 05 (2008-05-30)
3-17
3 System Structure
3.4.11 Satellite Transmission Function

In some areas, with regard to topography, the general E1 cannot be used as the trunk between the BSC and the BTS or between the PCU and the SGSN. The HUAWEI PCU6000 can use satellite to transmit signaling and data.
3.4.12 On Line Patches

The HUAWEI PCU6000 supports online patching by patching. The function of the software can be enhanced without interruption of the service. This operation can be performed in remote areas. It is conveniently undone, thus reducing the cost and probability of failure for updating. The management of patches is the core of this function, which comprises the following four aspects: Loading the patches, activating the patches, deactivating the patches, removing the patches, and confirming the patches based on MML Reporting the information of patches to the operator with MML output and alarm Query the information of patches by MML. Auto-recovery of the patching after restart of the system
3.4.13 License
To protect the equipment investment of the GPRS operators, HUAWEI PCU6000 provides the license feature and enables online expansion through license configuration. That is, the network operators can purchase licenses to expand service ranges or service features without interrupting the ongoing services.
3-18
Issue 05 (2008-05-30)
4 Interface Functions
4
About This Chapter
Section Describes
Interface Functions
4.1 Gb interface 4.2 G-Abis Interface 4.3 Pb Interface 4.4 O Interface
This section describes the Gb interface. This section describes the G-Abis Interface. This section describes the Pb Interface. This section describes the O Interface.
Issue 05 (2008-05-30)
4-1
4.1 Gb interface
4.1.1 Overview
The Gb interface is an interface between the SGSN and the GPRS BSS. Through this interface, the SGSN communicates with the BSS to fulfill packet data transmission, flow control and mobility management. This interface is mandatory for the GPRS topology. The location of the Gb interface in the GPRS system is somewhat similar to the A interface in the GSM network. The A interface is located between the BSS and the MSC network subsystem, while the Gb interface is located between the BSS and the GSN core network. The difference is that the Gb interface provides functions and characteristics that are more suitable for packet services.
The Layered Protocol Structure on the Gb Interface

Figure 4-1 shows the location of the Gb interface and the structure of its protocol stack.
Figure 4-1 Gb protocol stack
LLC BSSGP NS L1 SGSN
RELAY RLC MAC BSSGP NS L1 BSS
Gb
Layer 1 is the physical layer of the Gb interface using the FR (Frame Relay) protocol. In the actual implementation, it is connected either through the point-to-point frame relay connection or through the frame relay network (multipoint-to-multipoint). The physical layer (layer 1) on the Gb interface can also use the Internet Protocol. In actual implementation, two modes can be used: direct connection and routing. The NS (Network Service) Layer 2 protocol of the Gb interface completes the transmission function of NS SDUs at the Gb interface and the function of NS-VC configuration and state management. The BSSGP Layer 3 protocol of the Gb interface implements uplink/downlink transmission of signaling and data of the upper layer (LLC layer), flow control of downlink data, operation and maintenance functions such as block, unblock and reset of BVC (BSSGP Virtual Connection).
4-2
Issue 05 (2008-05-30)
Gb-Related Protocols
Similar to A interface, the Gb interface also involves the interconnections between products of different manufacturers. Therefore, its definition is strictly stipulated in the GSM specifications to ensure excellent interworking between the GPRS BSSs of different manufacturers and the GPRS core network subsystem. Relevant protocols of the Gb interface are introduced as follows: GSM03.60 defines the location of the Gb interface and its protocol stack structure. GSM08.14 stipulates the FR protocol used by the physical layer of the Gb interface between the BSS and the SGSN. The 3GPP48.016 defines that the physical layer of the Gb interface between the BSS and the SGSN can use the IP protocol. GSM08.16 stipulates details of the Layer 2 protocol NS of the Gb interface between the BSS and the SGSN. GSM08.18 stipulates details of the Layer 3 protocol BSSGP of the Gb interface between the BSS and the SGSN.
4.1.2 Signaling at Different Layers of the Gb Interface

FR
Logically, the physical layer on the Gb interface uses the frame relay (FR) protocol. Physically, the physical layer on the Gb interface uses E1 or T1 tranmssion. The frame relay module supports the interconnection of subnetworks. Therefore, the PCU and the SGSN can be connected through private lines (point-to-point mode) or through the frame relay network (intermediate network mode).
IP
The physical layer of the Gb interface uses the FR (Frame Relay) protocol, while the physical media can be E1 or T1. The Frame Relay provides interworking between subnetworks, allows direction connection of the PCU to the SGSN through the dedicated line connection (point-to-point mode) or through the frame relay network (intermediate network mode). Frame Relay is a mature and general physical layer protocol, and its use is not limited to the GPRS Gb interface.
NS
NS protocol layers are distributed on both sides of the standard Gb interface. Its functions on both sides are symmetrical to each other. However, the interface services it provides to the upper layer BSSGP are relatively simple and clear-cut. It provides the following three service functions: Completion of the transmission of upper layer data units All the messages transmitted at the BSSGP layer are transmitted in the form of NS SDUs (Service Data Units) at the NS layer. The normal operation of the NS layer provides reliable path and guarantees the normal operation of the upper layer protocols.
Issue 05 (2008-05-30)
4-3
Network congestion detection When the NS layer detects a link congestion or congestion cleared at the bottom layer, the NS layer informs the upper layer through the congestion indicator, so that the latter perform necessary processing. Network status detection When the NS layer detects that no transmission can be done because of link fault at the bottom layer or faults have been eliminated at the bottom layer, it informs the upper layer that performs necessary processing.
BSSGP Layer 3 Protocol

BSSGP protocol layers are distributed on both sides of the standard Gb interface, but the functions on both sides are not entirely the same. Figure 4-2 depicts the service models realized by the BSSGP protocol on the BSS and the SGSN sides.
Figure 4-2 BSSGP service models
Service model in a BSS GMM NM PFM PFM Service model in a SGSN LLC GMM NM
RELAY
GSM 03.64
RL
GMM
NM
PFM
PFM BSSGP
GMM
NM
RLC/MAC
BSSGP
BSSGP
GSM 08.16
GSM 08.16
Network Service
Network Service
In terms of service models, the functions provided by BSSGP for the upper layer include three parts:
Between NM and BSSGP: This part mainly provides the network management function on the Gb interface, including downlink data flow control, block, unblock and reset of BVC (BSSGP Virtual Connection), and mobile station tracing. Between GMM and BSSGP: This part implements GPRS mobility management on the Gb interface, including GPRS services such as calling the MS on the network side, MS radio access capability synchronization and service suspend/resume. Uplink/downlink data transmission: Although the data transmission services provided by the Gb interface on the BSS and the SGSN bear different names (called service between RL and BSSGP at the BSS side and between LLC and BSSGP at the SGSN side), the function it realizes is completely the same. That is, it provides the function of transparent transmission of uplink/downlink upper layer data.
4-4
Issue 05 (2008-05-30)
Between PFM and BSSGP: This part realizes the control and management of the PFC, including the support for the PFM/PFC by the PCU and the core network and also the setup, modification, and deletion of the PFC.
4.1.3 Characteristics of the Gb Interface

Flexible Physical Interface and LMI Support
HUAWEI PCU6000 supports the E1 interface that complies with the ITU-T specifications. The local management interface (LMI) complies with the ITU-T Q933 Appendix A. This enables the interoperation between the HUAWEI PCU6000 and the equipment from other vendors.
Flexible FR BC Bandwidth and NS-VC Bandwidth Allocation Strategy

While, the bandwidths of the FR layer bearer channels of HUAWEI PCU6000 is flexibly allocated within 164 kbit/s and 3164 kbit/s, the rate of NS layer's NS-VCs is flexibly configured within 1 kbit/s1984 kbit/s.
Load Sharing Function at the NS Layer

HUAWEI PCU6000 supports the complete load sharing between NS-VCs under one NSE. NS-VCs can be located in different boards. This is important to enhance the transmission reliability and utilization ratio of the Gb interface.
Entity Backup Function at the BSSGP Layer

HUAWEI PCU6000 supports the backup of BSSGP PTP and BSSGP SIG entities. When a certain PTP/SIG entity is unavailable due to board fault, the services on the entity is switched over to the standby board. Therefore, this backup function greatly enhances the reliability of the BSSGP layer.
4.2 G-Abis Interface

4.2.1 Overview
The G-Abis interface is an internal interface between the PCU and the BTS of Huawei BSS. The PCU communicates with the BTS through this interface to implement packet signaling/data transmission, in-band signaling transmission and block synchronization. It is similar to the Abis interface between the BSC and the BTS, but the difference is that the G-Abis interface provides functions and characteristics suiting packet-switched services.
Issue 05 (2008-05-30)
4-5
4.2.2 Characteristics of the G-Abis Interface

For the position of the PCU, the GSM/GPRS specifications only describe three feasible schemes, without any substantial stipulation for the interface between the BTS and the PCU. Therefore, the implementation of the G-Abis interface by different manufacturers varies. Huawei GPRS G-Abis interface utilizes the transmission bandwidth fully, and effectively supports the processing of packet service data and signaling. The characteristics of Huawei G-Abis interface are listed below: Transmit packet-switched service data and signaling through the G-TRAU frame Transmit packet data of coding schemes CS-1/CS-2/CS-3/CS-4 by providing 16 kbit/s and 32 kbit/s bandwidths (refer to Table 4-1) Transmit packet data of MCS-1/MCS-2/MCS-3/MCS-4/MCS-5/MCS-6/MCS-7/MCS-8/MCS-9 by providing 16 kbit/s, 32 kbit/s, 48 kbit/s and 64 kbit/s bandwidths (refer to Table 4-2) Use G-TRAU frame transmission with abundant in-band signaling contents, including a series of mechanisms such as BTS measurement, BTS power control, RLC/MAC block coding scheme indication, and air interface block synchronization
Table 4-1 Transmission parameters relating to coding schemes Scheme Code Rate Coded Bits Data Rate (kbit/s)
CS-1 CS-2 CS-3 CS-4
1/2 2/3 3/4 1
456 588 676 456
9.05 13.4 15.6 21.4
In the case of supporting coding schemes CS-1/2, the G-Abis interface bandwidth can be less than 16 kbit/s, but when supporting coding schemes CS-3/4, the G-Abis interface must provide a bandwidth of 32 kbit/s.
Table 4-2 Transmission parameters relating to modulation and coding schemes Scheme Code Rate Raw Data Within One Radio Block Data Rate (kbit/s)
MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8
0.53 0.66 0.85 1.0 0.37 0.49 0.76 0.92
176 224 296 352 448 592 2x448 2x544
8.8 11.2 14.8 17.6 22.4 29.6 44.8 54.4
4-6
Issue 05 (2008-05-30)
Scheme
Code Rate
Raw Data Within One Radio Block
Data Rate (kbit/s)
MCS-9
1.0
2x592
59.2
If MCS-1/2 is supported, the G-Abis interface bandwidth can be less than 16 kbit/s. If the coding scheme MCS-3/4/5/6 is supported, the G-Abis interface must provide a bandwidth of 32 kbit/s. If the coding scheme MCS-7 is supported, the G-Abis interface must provide a bandwidth of 48 kbit/s. If MCS-8/9 is supported, the G-Abis interface must provide a bandwidth of 64 kbit/s. The coding scheme of RLC/MAC block is sent to the BTS by the PCU through the G-Abis interface. For downlink data, the BTS encodes radio blocks based on this coding scheme. For uplink radio blocks, the BTS also decodes radio blocks based on this coding scheme. The Packet Data Channel (PDCH) used by the GPRS uses 52-multiframe structure for its air interface, of which the RLC/MAC block keeps a strict mapping relation with the G-TRAU frame of the G-Abis interface. Synchronization information is exchanged between the PCU and the BTS through in-band signaling. After the synchronization process, the RLC/MAC block transmitted by the PCU to the BTS immediately establishes an accurate time sequence relation with the TDMA frame number of BTS. This minimizes the time delay in processing uplink/downlink RLC/MAC blocks at the BTS.
4.2.3 Physical Layer/Transmission Media

Like the Abis interface, the G-Abis interface physically uses 2 Mbit/s E1. The E1 is transmitted to the BTS through the BSC trunk. For the data at the G-Abis interface, the BSC only functions as a physical trunk. The sub-timeslots of the E1 between the PCU and the BSC bear the packet traffic channels of the G-Abis interface and LAPD channels of the Pb interface, as shown in Table 4-3. On the E1 from the BSC to the BTS, there are packet traffic channels of the G-Abis interface, circuit traffic channels of the Abis interface, RSL (Radio Signaling Link for circuit switching), and OML (Operation and Maintenance Link for circuit switching). Depending on the availability of signaling channel resources, the G-Abis interface and the Abis interface share the same E1, and both occupy the sub-timeslots on the E1, as shown in Table 4-4.
Table 4-3 Example of the timeslot configuration for the G-Abis interface (PCU-BSC) Timeslot Sub-Timeslot 0 Sub Timeslot 1 Sub-Timeslot 2 Sub-Timeslot 3 Usage
E1 synchronization timeslot Packet traffic channel Packet traffic channel
1 N
4 4n
5 4n+1
6 4n+2
7 4n+3
Issue 05 (2008-05-30)
4-7
Timeslot
Sub-Timeslot 0
Sub Timeslot 1
Sub-Timeslot 2
Sub-Timeslot 3
Usage
4m
4m+1
4m+2
4m+3
Slave timeslot, additional packet traffic channel supporting CS-3/CS-4/MCS -3/MCS-4/MCS5/MCS-6/MCS-7 /MCS-8/MCS-9 LAPD channel
31
124
125
126
127
Table 4-4 Example of the timeslot configuration for the G-Abis interface (BSC-BTS) Timeslot Sub-Timeslot 0 Sub-Timeslot 1 Sub-Timeslot 2 Sub-Timeslot 3 Usage
E1 synchronization timeslot Circuit traffic channel or packet traffic channel Slave timeslot, additional packet traffic channel supporting CS-3/CS-4/MCS3/MCS-4/MCS-5/ MCS-6/MCS-7/M CS-8/MCS-9 RSL OML
1 n
4 4n
5 4n+1
6 4n+2
7 4n+3
m ... 31
4m ... 124
4m+1 ... 125
4m+2 ... 126
4m+3 ... 127
The radio channels of the air interface can be dynamically switched into the TCH supporting voice service and the PDCH supporting GPRS. The sub-timeslots on the E1 can be dynamically allocated to the Abis interface or G-Abis interfaces. The sub-timeslots used for the Abis interface transmit voice data through the E-TRAU frame (GSM08.60 V600), whereas the sub-timeslots used for the G-Abis interface transmit packet data through the G-TRAU frame.
4-8
Issue 05 (2008-05-30)
4.2.4 A Brief Introduction to G-TRAU Frame Structure

A G-TRAU frame is bi-directional, transferred every 20ms between the BTS and the PCU over each PDCH. Table 4-5 shows the structure of G-TRAU frame.
Table 4-5 Structure of the G-TRAU frame G-TRAU frame domain Description
Frame header Data field In-band signaling contents
Used for G-TRAU frame synchronization between the BTS and the PCU. It is a special bit sequence for defining the G-TRAU frame RLC/MAC data block produced from the BTS decoding or coded RLC/MAC data block transmitted by the PCU to the BTS Complete signaling interaction between the PCU and the BTS
The signaling between the PCU and the BTS is in-band signaling, and it is a part of the G-TRAU frame. The in-band signaling contents of the G-TRAU frame are abundant, including a series of complicated mechanisms, such as BTS measurement, BTS power control, RLC/MAC block coding scheme indication, and block synchronization of the air interface between the BTS and the PCU.
4.2.5 Characteristics of the G-Abis Interface

Semi-Independent PCU Equipment and Flexible Physical Location
As mentioned before, no substantial stipulation of the G-Abis interface between the PCU and the BTS is given in the GSM/GPRS Specifications. Logically, the PCU is a part of the GPRS BSC, but physically, it can be either built-in equipment, or semi-independent equipment. In terms of physical location, the PCU is positioned in BTS, BSC or SGSN. The HUAWEI PCU6000 is semi-independent equipment, and is physically positioned in either the BSC or the SGSN (also in MSC in some special topology). In the network, the semi-independent PCU has the minimum impact on the existing circuit-switched GSM network. The existing BTS and BSC support GPRS without hardware upgrade. The semi-independent PCU meets the requirement of processing capability because of the introduction of packet-switched services. Therefore, it minimizes the impact on the processing capability of the already planned BSS. The semi-independent PCU also allows maximum flexibility in selecting the site for topology. In terms of its physical location, the PCU is either in the BSC site, or in the SGSN site, or even in the MSC site in a special topology. For description of M900/M1800 BSS topologies, refer to Section 3.2 in chapter System Feature - General Introduction.
Issue 05 (2008-05-30)
4-9
Dynamic Additional
Sub-Timeslot Technology
The advanced GSM BSS generally uses 16 kbit/s links (also called 16 kbit sub-timeslot) for its Abis interface. Under CS-1/CS-2 and MCS-1/MCS-2, the BSS also uses 16 kbit/s links for its G-Abis interface. Under coding schemes CS-3, CS-4, MCS-3, MCS-4, MCS-5 and MCS-6, the rate of one PDCH is 15.6 kbit/s, 21.4 kbit/s, 14.8 kbit/s, 17.6 kbit/s, 22.4 kbit/s, and 29.6 kbit/s respectively. Therefore, one PDCH can be mapped onto two 16 kbit/s links. Under MCS-7, the rate of one PDCH is 44.8 kbit/s, so one PDCH can be mapped onto three 16 kbit/s links. The rate of one PDCH is 54.4 kbit/s under MCS-8 and 59.2 kbit/s under MCS-9, so one PDCH can be mapped on to four 16 kbit/s links. The coding scheme, which the PDCH uses, will be rectified in a dynamic way, depending on the change of radio transmission environment for the MS occupying this PDCH. If the fixed mode is used to map one PDCH onto four 16 kbit/s links, the multiplex ratio of the G-Abis interface and the availability of G-Abis interface transmission equipment are greatly reduced. The use of dynamic additional sub-timeslot technology by the HUAWEI GPRS BSS solves the problem of transmission at the G-Abis interface under the coding schemes CS-3/4 or MCS-39. With the dynamic additional sub-timeslot technology, the HUAWEI GPRS BSS allocates in a static way a master 16 kbit/s sub-timeslot for the G-Abis interface of each PDCH using CS-3/4 or MCS-39. It also dynamically allocates one to three additional 16 kbit/s sub-timeslots. By using the dynamic additional sub-timeslot technology, the GPRS BSS support coding schemes CS-3 and CS-4, without the hardware grading of BTS, BSC and PCU. The GPRS BSS supports MCS-19, with hardware upgrading of the BTS, and only software upgrading of the BSC and the PCU. The dynamic additional sub-timeslot technology the HUAWEI GPRS BSS uses has the following characteristics: Any idle 16 kbit/s sub-timeslot at the G-Abis interface is an additional 16 kbit/s sub-timeslot, thus making full use of every idle sub-timeslot. Within the same site, an additional sub-timeslot is dynamically attached to different master timeslots, so the availability of additional sub-timeslots increases based on the statistical multiplex rules. The location of additional 16 kbit/s sub-timeslot is relatively flexible and need not be adjacent to the 16 kbit/s master timeslot. Data packets are assembled and disassembled through the software means, thus sparing the hardware upgrade due to the alteration of product specifications.
Quick and Smooth Time Synchronization Mechanism for Data Blocks Over the Air Interface
Because of the advanced synchronization mechanism and synchronization algorithm, after the completion of the system initialization, the HUAWEI PCU6000 realizes a smooth synchronization of the air interface frame number with the CCU (Channel Codec Unit) within 1 TDMA multi-frame period (240ms), taking a channel as a unit. The smooth air interface block synchronization between the HUAWEI PCU6000 and the CCU is essential to ensure a normal GPRS cell packet system information broadcast and high radio transmission efficiency for the GPRS cells.
4-10
Issue 05 (2008-05-30)
Good and Expandable G-TRAU Frame

Forward compatibility and backward compatibility have been fully considered in the structure definition of the G-TRAU frame, so it has good expandability. The 3-bit version number is defined in the frame header of the G-TRAU frame, and is capable of supporting G-TRAU of different versions. By means of the G-TRAU version mechanism, the HUAWEI BSS has good forward and backward compatibility at the G-Abis interface.
4.3 Pb Interface
4.3.1 Overview
The Pb interface is the interface between the HUAWEI PCU6000 and the HUAWEI BSC. Since the PCU is functionally semi-independent equipment and a part of the BSS, the interface between the PCU and the BSC is a non-standard interface, and the technical realization varies with manufacturers. GSM Specification puts forward three feasible schemes for the positioning of the PCU (please refer to Figure 1-2). It does not give any substantial stipulation relating to the interface between the PCU and the BSC. In the design of the GPRS system, the PCU is functionally a part of the BSS. However, as a piece of independent physical equipment, it is put together either with the BSC, or with the SGSN. One PCU frame (12 RPPU boards at the most) is connected to multiple BSCs through E1s.
One BSC can be supported connecting with multiple PCU processing frames in version GBSC32V300R002C12 and later versions.
The Pb interface function is an essential factor to realize flexible design of system topology. Huawei Pb interface realizes management of shared resources between the PCU and the BSC, including cells, packet channels and E1 trunks, system information. It also supports dynamic channel conversion and an access of MS on CCCH.
4.3.2 Internal Structure of the Pb Interface

As non-standard interface, the Pb interface has the following hierarchical structure: Layer 1 -- physical layer is realized by using the sub-timeslot of E1 line. The Pb interface and the G-Abis interface multiplex the same physical link by dividing sub-timeslots. E1 is divided into 128 sub-timeslots of 16 kbit/s, of which four sub-timeslots are used for synchronization. Some are used as physical links of the G-Abis interface some as physical links of the Pb interface, and the rest as idle sub-timeslots, or multiplexed as a part of the A interface. Layer 2 -- link layer uses the LAPD protocol, which is a general data link layer protocol. It receives data transmission service from the physical layer, and provides connection or connectionless service to Layer 3. In short, the aim of LAPD is to realize reliable end-to-end information transmission among the entities of Layer 3 by means of the interfaces on the physical layer.
Issue 05 (2008-05-30)
4-11
Layer 3 protocol is a set of self-defined signaling messages and is the core part of the Pb interface. It mainly realizes the information management of resources related to the GPRS between the PCU and the BSC, supports the switchover of dynamic channels between packet service and voice service, and also supports the access of MS on CCCH and voice paging message transmission. Since the standard LAPD protocol is used for the lower layer, the Pb interface protocol often refers to the Layer 3 signaling procedures.
4.3.3 Characteristics of Pb Interface

Support dynamic channel conversion between packet services and voice services During actual realization, channels are divided into the following categories: fixed packet channels, voice channels and dynamic channels. The fixed packet channels, like PBCCH, PCCCH and PDCH, are exclusively used for packet services. The voice channels, like TCH, BCCH and SDCCH, are exclusively used for voice services. Dynamic channels serve as speech TCHs during initialization, but they can be dynamically converted to PDCHs. When the packet service is heavy and voice service is relatively light, the PCU applies to the BSC for conversion from dynamic channel to dynamic packet channel. If the BSC finds that the voice service is heavy, it takes back from the PCU the converted channels. During this process, the priority levels of voice services and data services can be set based on the configuration of the PCU. Support of the MS request for access on CCCH The BTS is unable to identify the access request message sent by the MS on CCCH. Therefore, only after analyzing by the BSC can the request be determined as a packet access request. If the request is a packet access request, it is transferred to the PCU. Accordingly, the immediate assignment message by the PCU must be processed by the BSC before it is transferred to the BTS. Therefore, the access of the MS on CCCH and PCCCH are processed by the BSS in different modes. The technique of the MS that supports the access on CCCH is relatively simple. This access mode is common during the initial stage of GPRS service. The Pb interface makes it possible for the PCU to support two different MS access modes simultaneously, thus greatly improving the adaptability of the system to various kinds of MSs. Transmission of circuit paging messages When the network operates in network operation mode I, and no PCCCH is existing, the circuit paging messages sent by the MSC is transferred through the Gs interface (MSC-SGSN interface), Gb interface (SGSN-PCU interface). Then the circuit paging messages are forwarded by the PCU to the BSC through the Pb interface. Finally, the messages are transmitted by the BSC on the CCCH (For details of network operation modes, refer to the Appendix). Support of Suspend/Resume message sent by MSs in class B mode MSs in class B mode cannot to operate circuit service and packet service simultaneously. Therefore, after conversion from packet transmission to voice service, the MS sends the GPRS Suspend request to the BSC, and the BSC transfers the message to the PCU through Pb interface for processing. In addition, when the circuit service of the MS is completed, the BSC sends to the PCU a GPRS Resume request. The processing of messages of this kind improves the system capability to support MSs in class B mode.
4-12
Issue 05 (2008-05-30)
4.4 O Interface
4.4.1 Overview
The O interface refers to the interface between the PCU and the OMC (Operation and Maintenance Center). The GPRS system is an expansion and upgrade of the GSM, and its OMC uses the original GSM-OMC software. Therefore, they are the same in terms of software structure, software application and hardware topology. As shown in Figure 4-3 the PCU is only a newly added network element like MSC, BSC, HLR and GSN, to the OMC subsystem.
Figure 4-3 The O interface of GPRS/GSM
There is an exclusive BAM computer in the MSC, BSC, HLR of GSM, serving as a bridge between the boards and the OMC subsystem. It is responsible for collecting information of the equipment and for the communication with the OMC subsystem, realizing functions of the O interface. In the GPRS equipment like PCU, SGSN, there is no BAM. The OMA module (OMC Agent Module) on each operation and maintenance board (for instance, POMU board for PCU) realizes the bridging function between the system equipment and the OMC subsystem. In the case of different equipment, although the maintenance and management module of their OMC consoles are similar in the user interface, their interior functional realizations such as message analysis are different. After the GSM system is upgraded to GPRS, corresponding changes take place to the network entities on both ends of the O network. However, as a non-standard interface, the O interface itself will not change. Even if new equipment is added to the GSM system later, the same interface is used between the equipment and the OMC subsystem. This is to keep uniformity among the entire OMC subsystem and enhance the operability for users.
Issue 05 (2008-05-30)
4-13
4.4.2 Software Structure

Different from the network bottom layer interfaces like Gb and Pb, the O interface is an interface of the application layer, relatively simple in message structure and protocol hierarchy. The bottom layer of the O interface is based on the TCP/IP. Therefore, the OMC system is capable in remote topology. In terms of system composition, the software of the O interface mainly includes four parts as shown in Figure 4-4: OAM/BAM program, OMC Server/DB, OMC Shell and OMC console program. Its functions and characteristics are as follows:
Figure 4-4 Software structure of the O interface
OAM
BAM
......
PCU TCP/IP BSC LAN/WAN
OMC Shell Comm. Server

Traffic measurement Message tracing
Alarm
Database Server
Work Station
OMC Server/DB
OAM and BAM are different in terms of hardware and software realization, and in terms of messages and information administered by different equipment, but they have the same basic software functions. The OAM has the following two functions:
It serves as a communication bridge between the OMC system and the network equipment, transfer the operation/maintenance commands from the OMC to the PCU boards and direct the PCU response to the corresponding terminal equipment of the OMC. It serves as a server in the Client/Server network model.
In addition to the management of database and management of test and traffic measurement tasks.The OAM also implements storage and transfer of charging information, alarm information and traffic statistics data. It stores various important data into hard disks, and delivers the data to compact discs or the OMC server. Various service processes are operated on the OMC server, including communication server and database server.
4-14
Issue 05 (2008-05-30)
The communication server is the core part of the whole system, while the other parts are connected to it through application agents. The communication server provides an identifier to each application part connected to it. During message transfer, the communication server receives messages from different parts, and then determines the destinations for those messages before transferring those messages or getting them properly processed. In response to the request from the OAM/BAM or application consoles, various database servers manage various data through interaction with the database management system (DBMS). Besides, there are some other application servers and management modules on the OMC server. The OMC Shell is a user interface that implements management, operation and maintenance over GSM objects, and is also a communication interface that communicates with various console programs. With the OMC Shell, the visual management through a client on any equipment of the entire GSM system can be performed. This is done using the centralized operation and maintenance management functions. The OMC Shell program is composed of two parts: user interface module and communication module. The user interface module provides a visual operation interface, including the tree list and map window. (You can view the status and perform operation, maintenance and management of GSM objects through the interface.) The communication module is mainly responsible for communication management. The OMC WorkStation (WS) is a set of application functions. In case of different equipment, the functions of the WSs are different. The OMC WS of the PCU includes traffic measurement console, alarm console and message tracing console. Since the design of the whole system is to divide the modules according to the functions, the functions of the OMC WS can be easily rectified in accordance with the user requirements, thus substantially meeting the specific requirements of end users.
Issue 05 (2008-05-30)
4-15
5 Operation & Maintenance
5
About This Chapter
Section
Operation & Maintenance

Describes
5.1 Overview 5.2 Characteristics 5.3 Implementation of PCU O&M Function
This section describes the overview of the operation & maintenance. This section describes the characteristics of the operation & maintenance. This section describes the implementation of PCU O&M function.
Issue 05 (2008-05-30)
5-1
5.1 Overview
The operation and maintenance module of the HUAWEI PCU6000 provides the functions of operation and maintenance management, data configuration management, fault management, performance measurement management, security management. It also provides the means for users to remotely monitor the operation state of the PCU, maintain the PCU equipment, locate faults, and evaluate network performance. The O&M of the HUAWEI PCU6000 uses the Client/Server structure to support both remote login to and maintenance of Telnet, and the maintenance on OMC GUI (Graphical User Interface). The system supports five Telnet clients simultaneously. The number of GUI clients supported depends on the model and amount of the OMC servers. The OMC server using one Ultra60 supports 10 GUI clients simultaneously. The OMC server using one Sun E3500 supports 30 OMC terminals simultaneously. The number of Telnet clients does not affect the number of GUI clients. The positioning of the O&M of HUAWEI PCU6000 in the whole GSM/GPRS network is shown in Figure 5-1. It is integrated into the maintenance system of the GSM/GPRS OMC and is managed as a whole.
Figure 5-1 GSM/GPRS O&M system
A GSM NSS
BSC LMT
bi
Gb PCU
GPRS NSS
GSM/GPRS BSS
LMT
WAN/LAN
... NM Server NM Client NM Client M2000 Server M2000 Client
... M2000 Client Telnet Terminal
SNMP Network Management system O&M system
GSM/GPRS O&M system
5-2
Issue 05 (2008-05-30)
The O&M software of the HUAWEI PCU6000 resides in the POMU board and the RPPU board. Its position in the PCU software and its relationship with the application modules are shown in Figure 5-2 and Figure 5-3.
Figure 5-2 PCU O&M system
POMU board
Alarm & traffic measurement O&M commands Alarm report Measurement data O&M result Inter - board communication (IPC)
RPPU board
Send command POMU
Receive data O&M
RPPU O&M
Command interpretation
RLC/MAC
OAM
telnet server
TCP/IP
OMC
Telnet client
Figure 5-3 The connection between PCU and OMC

TCP/IP OAM OMC Server OMC System OMC Shell GUI Client
POMU
Local WS
GUI Client
Issue 05 (2008-05-30)
5-3
5.2 Characteristics
The characteristics of the PCU O&M are: Easy to operate The PCU O&M is designed in the Client/Server structure with the computer network, multiwindow visualization and other advanced technologies. It provides the multiwindow operation interface for easy operation. Remote/centralized maintenance function The PCU O&M achieves the remote/centralized maintenance functions through the computer network, Telnet and the OMC Server. Client/Server structure All the operation and maintenance tasks are done in the Client/Server mode, which supports the multi-point local/remote data configuration, maintenance and operation simultaneously. Strong message tracing and monitoring functions The PCU O&M trace, interpret and display the messages of the PCU nonstandard and standard interfaces (such as Um, Pb and Gb interfaces).
5.3 Implementation of PCU O&M Function

5.3.1 Configuration Management
Modules of PCU-DB
The PCU-DB is functionally divided into five modules: CDB (Configuration DB) The CDB is a data management system in the distributed environment. The essential CDB interface is the interface connecting the application part and the CDB kernel, which is used by all the application parts of CDB by invoking the functions. Command line interface module The command line interface module is connected with the Telnet module to provide command line, command line help information and configuration functions. Validity check module The validity check module checks the validity of the data entering the system from the command line, rejects invalid data, and invokes relevant functions to operate the valid data, such as Add, Delete and Modify operations. Upper layer API module The upper layer API module provides the data manipulation functions including data inquiry and modification for the protocol modules Data compilation module The data compilation module provides the function of decompiling the data in the memory into the text command lines.
5-4
Issue 05 (2008-05-30)
Database Loading
The configuration data is stored in the Flash memory of the POMU board. When the POMU board starts to work, the Telnet task is created, and the task interprets the data stored in the Flash memory of the POMU board into command lines for execution. As a result, the data for RAM (Random Access Memory) is generated.
Data Configuration Processing Procedure

The data configuration function of PCU-DB writes the valid data into CDB after the successful validity check of the data. To insert, modify and delete data in the table, it only needs to invoke the API function provided by CDB.
System Expansion Process

The data configuration in the case of system expansion is rather complicated. It has to configure plenty of tables. In this section, only two of the most basic configurations are cited as examples: Physical configuration (add boards) and logic configuration (add cells). In the case of adding boards, it is mandatory to configure the information of slot position, including the slot sequence number, board type. In the case of logic configuration such as adding cells, it is mandatory to add the configuration information of the logic cells.
Data Storage and Recovery

Data storage In the mode of advanced maintenance or supervisor configuration, commands are used to store the data of RAM into the Flash memory of the POMU board. To store the data of RAM of the equipment into the hard disk of the PC, the LOG function of the Telnet client is used. Data Recovery In the mode of supervisor configuration, commands are used to delete the data in the FLASH memory that cannot be automatically recovered by the system. However, by restarting the system, changing the command line of the configuration data into a text file, and utilizing the function of sending a script file through the hyper terminal, configuration data is quickly recovered.
System Data Management

After the system is started, the configuration management part reads the configuration file from the Flash memory, and the command line interpreter interprets and modifies the contents of the database. In the course of operation, the database provides the function interface for the application layer to invoke, inputs or modifies data through the command line interpreter and the function interface for the application layer, decompiles the contents in the database to command lines, and stores them in the Flash memory.
Issue 05 (2008-05-30)
5-5
5.3.2 Alarm Management

Characteristics of Alarm Management
The HUAWEI PCU6000 alarm system has the following characteristics: Real-time When the Host gives out an alarm, the alarm management system processes the alarm immediately and sends it to the user interface, and reports the information to the maintenance personnel immediately. This is very helpful for timely troubleshooting. Multilevel control In HUAWEI PCU6000, all possible alarms are classified into four levels with different priorities (critical, major, minor and warning). Serious alarms with a higher priority are handled in the first place. Convenient and flexible display The alarm message is queried through the OMC alarm console. The detailed message is also inquired through the Telnet terminal connected to the POMU board through LAN switch. (For example, when the system generates a software fault alarm, the alarm terminal gives you the information about the frame No., board No. and software module as to where the alarm occurred.) The alarm terminal also provides suggestions on handling the alarm. Besides, the alarm file stored in the PCU POMU board hard disk can be fetched through FTP.
Alarm Processing Modes

After the HUAWEI PCU6000 alarm management system receives the alarm, it first processes the alarm information, and then sends the alarm information to the user interface. The alarm processing modes is as follows: After the alarm information is generated, the system first stores the alarm information in the hard disk for later inquiry. If the Telnet real-time alarm terminal is set, the alarm is displayed at the Telnet terminal. If the OMC maintenance console and SNMP maintenance are set, the alarm information is sent to them too. Among the alarm information, irrespective of whether they are stored in the hard disk or sent to the background, those with a higher priority are processed first. The acknowledgement and retransmission mechanism is used for the alarm information sent to the OMC. This ensures the safe and complete transmission of the alarm information.
5-6
Issue 05 (2008-05-30)
5.3.3 Performance Measurement

Overview
The HUAWEI PCU6000 traffic measurement (statistics) module completes the traffic measurement function. It is composed of the traffic measurement module in the active POMU board, the traffic measurement module in the RPPU board and the traffic measurement codes added into all of the service modules. The counters for the traffic analysis are distributed among all the service modules of the RPPU board. The traffic measurement module of RPPU takes charge of the maintenance of all the counters used for measurement, and sends the original data collected to the POMU board. The counter is composed of the built-in global counter (the main part) and the dynamic counter (as a supplement that collects the original data necessary for the traffic measurement). The traffic measurement module of the POMU board serves as the connection with the Telnet terminal or the OMC, collects and stores the data measured. Figure 5-4 shows the system structure.
Figure 5-4 Structure of the HUAWEI PCU6000 traffic measurement system
Term 1 Term 2 ...... Term n OMC Server
Measurement interface (external)

POMU
TCP/IP Traffic measurement module Save DATA Result FTP inter-board Comm Layer Offline Analysis
Measurement interface (internal)
Traffic measurement module RPPU
......
......
Performance Measurement Management

The performance management function of the HUAWEI PCU6000 traffic statistics system includes the following aspects:
Step 1 Measurement task
Measurement task here refers to the measuring process of a group of measured objects and items as a set within certain time and measurement characteristics. For example, in registering the task of "Paging request measurement," The title of the task is "Paging request measurement," but the paging request performances of cell 1, cell 2... cell n is measured at the same time according to the selection of parameters by the user.
Issue 05 (2008-05-30)
5-7
For the input of the task parameters, the system provides three choices: SELECT SINGLE, SELECT MULTIPLE and SELECT ALL. The SELECT ALL is directed at the full configuration, and SELECT SINGLE or SELECT MULTIPLE requires specific parameters. SELECT MULTIPLE is restricted to 40 as the maximum by the system. For instance, in the full configuration of 128 cells, if the user selects SELECT ALL, the task measures the paging request performances of the 128 cells. Alternatively, the user can choose at random to measure one or several of the cells. If the user wants to create a task of "NS transmission performance measurement" and chooses SELECT ALL, then the task will count to NS transmission of 1024 NSVCIs. The system allows the registration of up to 80 measurement tasks.
Step 2 Register performance measurement task
The traffic measurement module in the POMU board receives the operation of registering the performance measurement task sent from the OMC traffic statistics console. It then checks the parameter validity, and decides whether it is successful in registering the task according to the resource state of the measurement task. If it is successful, the system assigns it a task sequence number and creates a unique corresponding file in the hard disk of the POMU board to store the measurement result.
Step 3 Collect and process performance measurement results
The performance measurement task has absolute life cycle and measurement period attributes. For instance, if there is a task named "Paging request measurement ," the measurement will be performed once in every 30 minutes from 9:00 to 21:00 every day, and the measurement task will last for a period of 60 days beginning from June 6, 2000. In this case, the system decides whether to fetch the measurement result according to the absolute timer of the system. It is specified that the minimum measurement period for a performance measurement task is five minutes. The traffic measurement module in the POMU board judges whether any task can be activated every one minute. A task is activated depending on whether it has met the following conditions. The current date of the task is within "the start date of the measurement" and "the end date of the measurement"; The current time of the task is within "the start time of the measurement" and "the end time of the measurement"; The difference between the current time and "the start time of the measurement" is the integer multiple of the measurement period. Those whose time type is Statistic by week or month are only activated at the configured days.
----End
The POMU board sends the information of the activated task to the RPPU board at a fixed time interval When the RPPU board receives the message. It fetches the related measurement result data from the board for the task, and sends them back to the POMU board. The POMU board receives the measurement result data from the RPPU board before the end of the measurement period. The measurement result data is the state value. Though the result of a measurement period is the difference between the "measured value at the end of the measurement period" and the "measured value at the start of the measurement period," it is necessary to calculate the difference, put them together for analysis and classification, and store them in the task result file.
5-8
Issue 05 (2008-05-30)
Step 1 Inquire task state
The information of the current task that is successfully registered tasks is inquired through the OMC traffic statistics console.
Step 2 Inquire task result
The measurement result of a measured task for a certain time segment is inquired through the OMC traffic statistics console. The traffic measurement file in the POMU board is also fetched through the FTP.
Step 3 Delete traffic measurement task
The traffic measurement module in the POMU board receives the traffic measurement task Delete operation sent from the OMC, checks the parameters, clears the task resource if the parameters are accepted, and deletes the corresponding traffic measurement file from the POMU board hard disk.
Step 4 Traffic statistics data synchronization in the active and standby POMU boards
When the active and standby POMU boards work normally, they achieve the data synchronization in the Timed writ-in mode. That is, when the original traffic statistics data of the active POMU board is written into the hard disk and then sent to the standby POMU board, the standby POMU board receives and then stores them. If the communication between the active and the standby POMU is abnormal, the active POMU log the periods of task result (maximum number is 100), which are not confirmed by the standby POMU and resend them when the communication recovers.
----End
Performance Measurement Types Supported

The performance measurement type is the essential element in performance measurement. Many performance measurement types constitute the measurement set of the performance measurement system. As one practical measurement set of the performance measurement system has many elements, to facilitate the use and inquiry, the PCU traffic measurement system divides the performance measurement types into many measurement subsets, according to a certain rule. Table 5-1 shows the logic relationship between the measurement subsets and performance measurement types.
Table 5-1 PCU performance measurement types Measurement Function Traffic Measurement Task
CPU performance measurement PCU overall performance measurement BSC overall performance measurement NS performance measurement BSSGP performance measurement
CPU performance measurement PCU overall performance measurement BSC overall performance measurement NS transmission performance measurement BSSGP performance measurement
Issue 05 (2008-05-30)
5-9
Measurement Function
Traffic Measurement Task
G-Abis interface performance measurement Pb interface performance measurement Cell performance measurement
TRAU link measurement LAPD link measurement Packet access performance measurement on CCCH Packet access performance measurement on PCCCH Packet access performance measurement on PACCH Rate of successful packet assignment Paging request measurement Uplink TBF establishment/release measure Downlink TBF establishment/release measurement Uplink LLC data transmission measurement Downlink LLC data transmission measurement Uplink RLC data transmission measurement Downlink RLC data transmission measurement Cell radio channel performance measurement Resource maintenance performance measurement PDCH resource performance measurement PDCH extremum value measurement Uplink EGPRS TBF establishment/release measurement Downlink EGPRS TBF establishment/release measurement Uplink EGPRS RLC data transmission measurement Downlink EGPRS RLC data transmission measurement GMSK_MEAN_BEP different value measurement 8PSK_MEAN_BEP different value measurement Uplink GMSK EGPRS RLC data retransmission rate measurement Uplink 8PSK EGPRS RLC data retransmission rate measurement
5-10
Issue 05 (2008-05-30)
Measurement Function
Traffic Measurement Task
Downlink GMSK EGPRS RLC data retransmission rate measurement Downlink 8PSK EGPRS RLC data retransmission rate measurement EGPRS PDCH resource performance measurement Performance measurement on the loads of channel resources
Performance Measurement Data Record

The performance measurement data are recorded and stored in the form of a file in the hard disk of the POMU board. Each task has only one file folder with the name "/hda1/ms/PcuMsXXX" (XXX is the task number in the form of three-digital integer.), which is stored as a binary file. The task number resources are limited (079 numbers). Once distributed, the resources cannot be redistributed before the release. If new performance measurement tasks are to be registered when all of the task number resources is distributed, the system suggests to the user to "delete the traffic measurement task" that is already registered, and then releases the resources. Otherwise, new performance measurement tasks cannot be registered.
Performance Measurement Data Transmission

Data transmission is necessary in the following three stages:
Step 1 When the POMU board fetches the measurement data of the performance measurement task from the RPPU board, the RPPU board sends the snapshots of performance measurement data to the POMU board. The data transmission is based on the inter-board communication, that is, through the socket of Voxworks. Step 2 When inquiring the performance measurement data through the OMC traffic statistics console, the POMU board sends the answer frames to the OMC. The data transmission is mainly based on TCP/IP. Step 3 In the case of remote control, the FTP is used to fetch measurement data. ----End
Performance Measurement Log

The performance measurement log is kept in the following cases: After receiving the command frames from the host or the client terminal, it checks the validity of the frame structure, length and contents (such as the validity of task type), and write into the log if it is invalid. In executing the memory operation, opening, reading and writing the files, the system is necessary to check whether the operation is unsuccessful. If it fails, it is written into the log.
Issue 05 (2008-05-30)
5-11
The performance measurement log file has the following structure: File name: PcuMs.log Key information: date, time, abnormality description information, and faulty source code file name, and fault source code line number.
Performance Measurement Data Processing

Step 1 Difference value processing
The value stored by the counter in the RPPU traffic measurement module is the measured state value at a certain time, whereas the traffic measurement task needs the D-value between two measurement periods. The calculation of the D-value is done in the POMU board, for example as follows. Now perform the "Uplink LLC data transmission measurement" for cell 5. Suppose the measurement types of "Uplink LLC data transmission measurement" have the following three items: Value (5, 211) = status (5, 211, k) - status (5, 211, k -1) Value (5, 212) = status (5, 212, k) - status (5, 212, k -1) Value (5, 213) = status (5, 213, k) - status (5, 213, k -1) Among which, status here is the measured state value of a certain item of a cell during the k period, and value here is the final value of a certain item of a cell. Status (i, j, k): i is the cell number, j is the measurement item number and k is the period number. Value (i, j): i is the cell number, j is the measurement item number.
Step 2 Ratio processing
In general, the measurement index is the "quantity" or "times" of a certain measurement item. Some indices are the ratio of two measuring counters, such as the Cell radio channel performance measurement, Uplink PDTCH/PACCH utilization rate, Downlink PDTCH/PACCH utilization rate. In this case, it is mandatory to specially process such indices based on previous data structure. The counters and buffer counters of the POMU board and the RPPU board, for each index with the "ratio" characteristic, is provided with two counters, one as the numerator and the other as the denominator, which provide the internal interfaces respectively for cumulative operation. When the POMU board sends the message of fetching data to the RPPU board, the RPPU board returns the values of the two counters at the same time. When processing the data from the OMC traffic statistics console, it processes the data specially by calculating the ratio, for example as follows. Now perform the "Cell radio channel performance measurement" measurement for cell 5. The value of measurement indexes "Uplink PDTCH/PACCH utilization rate" is value (5, 335) = [status (5, 332, k) - status (5, 332, k - 1) ] / [status (5, 335, k) - status (5, 335, k - 1) ] Among which, status here is the measured state value of a certain index of a cell during the k period, and value here is the result value of a certain index of a cell. Status (i, j, k): i is the cell number, j is the measurement item number and k is the period number. Value (i, j): i is the cell number, j is the measurement item number.
5-12
Issue 05 (2008-05-30)
Step 3 Error control
Due to the influence of the system operation environment, the communication between the RPPU board and the POMU board may become abnormal in practice; or due to the abnormal operation of RPPU board, the POMU board may not be able to process the returned data within a certain period. In addition, the neighboring periods of the measurement results are closely related. Thus, the data of the next period is unavailable. In this case, it is mandatory to have error control over the data returned by the RPPU board, for example as follows. Now conduct the "Paging request measurement" measurement for cell 5. The measurement is done once in every 60 minutes from 9:00 to 24:00 every day, and lasts from August 1, 2000 to August 10, 2000. Suppose from 9:00 to 11:00 of August 7, 2000, the RPPU board in cell 5 is faulty, and then the result of the following period should be set as invalid: Period 1: 9:00--10:00 Period 2: 10:00--11:00 Period 3: 11:00--12:00 The system processes as follows: Period i of cell 5 of task 3 returns the measurement data, sets the period number of cell 5 of task 3 to i. When the next period comes, the system checks whether the period number of the same cell has one period different from the current period. If not, perform the error processing. The current period: i 1, i, i + 1, i + 2 Period judgment: (i-1) - (i-2) = 1 --->(not updated) --->i+1- (i-1)>1 --->(i+2) - (i+1) =1 Store result: Result valid, Result invalid, Result invalid, Result valid Store the period number: i - 1--->(not updated) ---> i +1 --->i +2
----End
5.3.4 Interface Information Tracing

The interface tracing intercepts the messages between interfaces as demanded by the user and sends them to the OMC maintenance console, so as to provide the user a means to view the system operation state, detect and locate the problem in time and efficiently.
Characteristics of Interface Tracing

Real time When there are messages sent among the interfaces monitored by the tracing system, the tracing system processes the messages in time, judges if they satisfy the trace filter conditions, and then sends the messages that meet the user's demand to the OMC maintenance console. Pertinence The interface tracing function makes possible the tracing of multiple interfaces and setting different tracing filtering conditions for each interface. It supports the user to dynamically input the tracing filtering conditions through the OMC maintenance console and dynamically establish the tracing. The tracing filtering conditions thus serve the interface tracing function better.
Issue 05 (2008-05-30)
5-13
Data completeness and visualization The tracing system copies the intercepted messages completely to the OMC maintenance console, where the user can view every byte of the message. The interface tracing also provides the function of message interpretation, which, with the use of message interpreting template, interprets every byte of a message, thus making the data more visualized and convenient to use. Data reviewability The interface tracing function achieves the message saving and reviewing. The user can save the traced messages for later review. It provides a means to review the system operation status and problems.
Realization of Interface Tracing Function

The PCU O&M module realizes the interface tracing function. The whole interface tracing system is divided into two parts that run in the active POMU board and the RPPU boards respectively. The interface tracing systems of the active POMU board and the RPPU boards maintain their specific interface tracing description tables, and record the messages of each tracing. The user sends the tracing command and views the traced results through the OMC maintenance console. The interface tracing system run in the active POMU board, receives the tracing request from the OMC, and forwards it to the interface tracing systems of corresponding RPPU boards. When the user establishes the tracing through the OMC, the OMC sends the interface chosen by the user and the appointed interface tracing conditions to the interface tracing system in the active POMU board. When the active POMU board receives the request to establish tracing from the OMC, it checks the validity of the request. For invalid requests, it rejects them and sends to the OMC the reason of rejection. For valid requests, it records the tracing in the interface tracing description tables and establishes the information of the tracing at the maintenance console. It also forwards the request to the corresponding RPPU boards in line with the filtering conditions. The interface tracing system of the RPPU records the tracing in its interface tracing description table, and sends the acknowledgement to the active POMU board to confirm the establishment of the tracing. When the active POMU board receives the affirmation, it affirms the established acknowledgement in the local interface tracing descriptive table, and sends the response of successful establishment of tracing to the OMC. Otherwise, the active POMU board deletes the corresponding record from the local tracing descriptive table, and feeds back the failure of establishment of tracing to the OMC. The interface tracing system in the RPPU board monitors and intercepts the message transmissions between interfaces. According to the tracing recorded in the local interface tracing descriptive table, the interface tracing system decides whether the message meets the interface tracing filtering conditions, and accomplishes the filtering of messages in this board. The RPPU board sends the messages that meet the filtering conditions to the active POMU board, which in turn establishes the information of tracing in the OMC maintenance console according to the local tracing descriptive table. The POMU board then sends the intercepted interface messages to the OMC maintenance console that has established the tracing.
5-14
Issue 05 (2008-05-30)
When the user closes the interface tracing window or the OMC maintenance console, the OMC sends the request of stopping tracing to the interface tracing system of the active POMU board. Upon receiving such request, the active POMU board checks the validity of the request, reject the invalid request if any, and feedback the reason of rejection to the OMC. For the valid request, it forwards the request of stopping tracing to the corresponding RPPU board in line with the filtering conditions of the request. When the RPPU board receives the request, it deletes the corresponding tracing record from the local interface tracing descriptive table, sends the answer to the active POMU board, and affirms the deletion of the tracing. When the active POMU board receives the answer to stopping tracing from the RPPU board, it deletes the corresponding tracing record from the local interface tracing descriptive table, and feeds back the success of stopping tracing to the OMC. By now, an interface tracing is successfully stopped.
Types of Interface Tracing Supported

It now supports the tracing of Um interface, Pb interfaces, BSSGP cell message, and BSSGP signaling message. The filtering conditions supported by the Um interface tracing are cell number, TRX number, filtering dummy messages, filtering null paging messages, filtering system information and filtering data blocks. The filtering conditions for the Pb interface tracing are cell number, tracing calling messages, tracing maintenance messages. The filtering condition for BSSGP cell messages tracing is the cell ID. The filtering condition for BSSGP signaling messages tracing is NSEI number.
Issue 05 (2008-05-30)
5-15
6 Technical Indices
6
About This Chapter
Section Describes
Technical Indices
6.1 Product Safety 6.2 Environmental Conditions 6.3 Power Supply and Power Consumption 6.4 Capacity
This section describes the product safety indices. This section describes the environmental conditions indices. This section describes the power supply indices. This section describes the capacity indices.
Issue 05 (2008-05-30)
6-1
6 Technical Indices
6.1 Product Safety

6.1.1 Safety Standard
The equipment should be grounded and have lightning protection measures. This shall be done in line with the Grounding Specifications. All the contacts, nodes and similar devices with the voltage of 24V~500V (valid value or DC voltage) should have protective measures (such as shields) against direct connection with charged bodies, and have corresponding alarm symbols. Obvious labels, alarm measures, protective measures and other measures should be provided in parts where hazards may occur. Any vulnerable part should have automatic protection measures. Any testing point with a voltage of more than 30V should have measures against direct contact. During installation and maintenance, safety measures should be taken for the personnel. Key parts should have signs, notes or measures against incorrect operation. The noise limit on the overall system should be not more than 65 dB ~75dB. Electrical (bare conductor) clearance: 48V (over 1.5mm), 220V (over 2.5mm).
6.1.2 Physical Protection Characteristics

The protection features of the HUAWEI PCU6000 equipment should conform to the GR-63-CORE standard. The outside packing is waterproof and damp-proof. The vent and ventilation have dustproof nets. The vent of product should be rat-proof. For the parts that are frequently opened and closed, the devices against bumping and shaking should be provided.
6.1.3 Data Backup and Security Characteristics

The POMU board of the PCU supports 1+1 backup on real-time basis. The RPPU board supports N+1 (N4) backup in the same BSC, which allows other RPPU boards connected to the same BSC to take over the operation, in case a fault occurs to a certain RPPU board. Set passwords for the network management and equipment management, and set levels for OMC operation and command line operation. Different levels have different operation authorities. The anti-virus measures should be prepared by the user.
6-2
Issue 05 (2008-05-30)
6 Technical Indices
6.2 Environmental Conditions

6.2.1 Environmental Conditions Required by the Equipment
Table 6-1 describes the environmental condition required by the HUAWEI PCU6000 equipment.
Table 6-1 Environmental storage condition required by the HUAWEI PCU6000 equipment Specification Explanation
Temperature Humidity Air Pressure Wind Speed Sun Radiation Heat Radiation
0C 45C 10% 90% 70 kPa 106 kPa <5.0 m/s <700 W/m2 <600 W/m2
6.2.2 EMC
Table 6-2 EMC specifications Specification Explanation
EMC
Complies with the requirement of the ETSI V1.2.1(2000-03)
EN300 386
6.2.3 Noise
Table 6-3 describes the specifications of noise and security.
Table 6-3 Specifications of noise and security Specification Explanation
Noise Security
<72dB, and complies with the requirement of the EUROPEAN ETS 300 753 Complies with the requirements of the UL 60950, the EN60950, the IEC60825, and the B4943-2000.
Issue 05 (2008-05-30)
6-3
6 Technical Indices
6.2.4 Storage Condition

Complies with the EUROPEAN ETS 300 019-1-1 "not temperature-controlled storage." Temperature: 40 +70 Relative humidity: 10%100%
6.2.5 Transportation Condition

Complies with the EUROPEAN ETS 300 019-1-2 "Class 2.3 PUBLIC transportation." Temperature: 40+70 Relative humidity: 5%100%
6.3 Power Supply and Power Consumption

Table 6-4 Power supply and power consumption of the PCU Specification Explanation Value 400 W 20 W 19 W 1240 W
Power consumption
Processing frame of the PCU ( a single frame in full configuration) Power distribution box LAN Switch Maximum power consumption of the cabinet
Power supply
48 V DC
input voltage: 57 V 40 V
6.4 Capacity
6.4.1 Maximum Capacity
The number of activated PDCHs of the Um interface and the throughput of the Gb interface are the measurement for the capability of a PCU. The processing capability of a fully configured single-frame PCU is shown in Table 6-5. Up to six frames are configured.
Table 6-5 The processing capability of PCU with the maximum configuration The Number of Activated PDCHs The Number of E1s of Pb Interface Gb Interface Throughput The Number of E1s of Gb Interface
1080(GPRS) or 900(EGPRS)
36
24Mbit/s
12
6-4
Issue 05 (2008-05-30)
6 Technical Indices
6.4.2 Minimum Capacity

In the case of the minimum configuration of the PCU, only one single frame is needed to accommodate two RPPU boards. In this case, Table 6-6 shows its processing capacity.
Table 6-6 The processing capability of PCU with the minimum configuration The Number of Activated PDCHs The Number of E1s of Pb Interface Gb Interface Throughput The Number of E1s of Gb Interface
120(GPRS) or 100(EGPRS)
16Mbit/s
After the RPPU capacity is expanded using the HLPU, one RPPU has the following capabilities: Processing of 8 Mbit/s data stream on the Pb interface Processing of 16 Mbit/s data stream on the Gb interface Processing of 16 LAPD links on the Pb interface Processing of 400 PCICs on the Pb interface Processing of 4 E1s on the Pb interface Processing of 8 E1s on the Gb interface Processing of 7200 uplink/downlink protocol packets on the Gb interface
Issue 05 (2008-05-30)
6-5
7 Configuration and Examples
7
About This Chapter
Section
Configuration and Examples

Describes
7.1 GPRS Configuration and Examples 7.2 EGPRS Configuration and Examples
This section describes the GPRS configuration and examples. This section describes the EGPRS configuration and examples.
Issue 05 (2008-05-30)
7-1
The number of packet channels simultaneously activated measures the processing capability of the HUAWEI PCU6000 equipment. At present, the minimum PCU configuration supports 120 GPRS packet channels or 100 EGPRS packet channels, while its maximum single frame configuration supports 1080 GPRS packet channels or 900 EGPRS packet channels. The HUAWEI PCU6000 has two main processing elements: the RPPU and the POMU. The RPPU implements service functions on various protocol layers, while the POMU fulfills the operation and maintenance functions. When the RPPU board provides only the Pb interface, each RPPU can support 120 GPRS packet channels or 100 EGPRS packet channels, and is configured in N+1 backup mode. When the RPPU provides only the Gb interface, each RPPU can support about 7,200 packets of data flow. Each RPPU is configured in load-sharing mode. The POMUs are configured in 1+1 backup mode.
7.1 GPRS Configuration and Examples

Taking the 1024 carrier frequencies that the large-capacity BSC can support as an example, the PCU configuration is considered as follows: Suppose if GPRS packet channels are 10% of all the channels, then the number of packet channels is about 820. Minimum number of RPPU boards used for the Pb interface = 820/120 =6.83 7 pcs. Number of RPPU boards actually configured for the Pb interface = 7+2 (used for N+1 backup)=9 pcs. Number of Pb interface E1s = 72+22 =18 pcs. Minimum number of RPPUs required for the Gb interface = 820 x 18.45 kbit/s/64/248 0.95 1 pcs. Number of RPPUs actually configured for the Gb interface = 1 + 1 (used for backup) = 2 pcs. Number of E1s required for the Gb interface = 8 + 8 = 16 pcs. For example, if the coding scheme CS-4 is used, the data transmission rate of the Gb interface corresponding to each radio packet channel is 18.45 kbit/s. Table 7-1 shows the PCU configuration list of the above example.
Table 7-1 PCU GPRS configuration example 1 Item for PCU Configuration Quantity (pcs)
PCU cabinet RPPU board for Pb interface RPPU board for Gb interface POMU board Pb interface E1 Gb interface E1
1 9 3 2 18 16
7-2
Issue 05 (2008-05-30)
When one PCU is connected to several BSCs, since each RPPU board can be connected to only one BSC (except for the RPPU boards used for backup), the RPPU boards needed for the Pb interface processing should be calculated individually by the number of BSCs, while the number of Gb interfaces can be calculated together. Under this circumstance, the PCU plays a big role in converging service volume. An example is given below: Suppose one PCU is needed to connect two BSCs, with each BSC supporting 1024 carrier frequencies, and GPRS packet channels share 5% of all the channels, then the number of packet channels for each BSC is 410. Minimum number of RPPU boards used for the Pb interface connected with BSC1 = 410/120 = 3.41 4 pcs. Minimum number of RPPU boards used for the Pb interface connected with BSC2 = 410/120 = 3.41 4 pcs. Number of RPPU boards used for backup on the Pb interface = 1 pcs. Number of Pb interface E1s required for BSC1 = 4 x 2 + 2 (used for backup) = 10 pcs. Number of Pb interface E1s required for BSC2 = 4 x 2 + 2 (used for backup) = 10 pcs. Minimum number of RPPUs required for the Gb interface = 820 x 18.45 kbit/s/64/248 0.95 1 pcs. Number of RPPUs for actually required for the Gb interface = 1 + 1 (used for backup) = 2 pcs. Number of E1s required for the Gb interface = 8 + 8 = 16 pcs. Table 7-2 shows the PCU configuration of the above example.
Table 7-2 The PCU GPRS configuration example 2 Item for PCU Configuration Quantity (pcs)
PCU cabinet Pb interface RPPU board Gb interface RPPU board POMU board Pb interface E1 Gb interface E1
1 9 3 2 20 16
The HUAWEI PCU6000 allows flexible Pb/Ater interfaces des. Under this circumstance, the semi-permanent connection function provided by the RPPU board that processes the Pb interface is used, and extra E1 ports could possibly be occupied. However, it will not limit the processing capability of RPPU boards, as each RPPU board provides 4 E1 ports, which under most cases are sufficient.
Issue 05 (2008-05-30)
7-3
7.2 EGPRS Configuration and Examples

Suppose one PCU is required to connect one BSC. The BSC supports 900 carrier frequencies, and EGPRS packet channels share 10% of all the channels. The number of EGPRS packet channels for the BSC is about 720. Minimum number of RPPU boards used for the Pb interface = 720/100 =7.2 8 pcs. Number of RPPU boards actually configured for the Pb interface = 8+1 (used in N+1 backup)=9 pcs Number of Pb interface E1s = 8 4 + 1 4 =36 pcs. Minimum number of RPPUs required for the Gb interface = 720 x 52.01 kbit/s/64/248 2.35 3 pcs. Number of RPPUs actually required for the Gb interface = 3 pcs. Number of E1s required for the Gb interface = 24 pcs. For example, if the coding scheme MCS9 is used, the data transmission rate of the Gb interface corresponding to each radio packet channel is 52.01 kbit/s. Table 7-3 shows the PCU configuration list of the above example.
Table 7-3 The PCU EGPRS configuration example Item for PCU Configuration Quantity (pcs)
PCU cabinet RPPU board for Pb interface RPPU board for Gb interface POMU board Pb interface E1 Gb interface E1
1 9 3 2 36 24
7-4
Issue 05 (2008-05-30)

PCU

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PCU

Încărcat de

Drepturi de autor:

Formate disponibile

HUAWEI PCU6000 Packet Control Unit Technical Manual

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

3 System Structure ........................................................................................................................3-1

4 Interface Functions ....................................................................................................................4-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

5 Operation & Maintenance........................................................................................................5-1

7 Configuration and Examples ...................................................................................................7-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

1.1 Overview of Functions

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

BSC site PCU

Packet switching PCU: Packet Control Unit

Circuit switching (16kbit/s or 64kbit/s) BTS: Base Transceiver Station

CCU: Channel Code Unit

A BSC BTS BSS PCU MSC/VLR Gb SGSN HLR Gs Gr SS7

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

1.4 Technical Specifications

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

The following table lists the contents of this chapter.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

2.2 Service Processing Function

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

2.2.1 Packet Channel Configuration

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

The HUAWEI PCU6000 supports all the functions of packet channels.

Combination of Packet Data Logical Channels

The circuit service uses the dynamic PDCH privilegedly.

The PCU unconditionally releases the PDCH

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

PCU Applies for the PDCH From the BSC

BSC Reclaims the PDCH From the PCU

Mapping of Logical Channels onto Physical Channels

B0~B11: 12 Radio Blocks

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

2.2.2 Packet Access Support

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

2.2.3 Paging Processing

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI PCU6000 Packet Control Unit Technical Manual

2.2.4 DRX Support

2.2.5 Radio Resources Allocation

Multi-slot Capability of the MS

Allocating Uplink and Downlink Resources Based on Service Priorities

2.2.6 System Information Broadcasting

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd