01 Body

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration
Contents
Contents
1 Overview......................................................................................................................................1-1
1.1 Preconditions for Data Configuration ...........................................................................................................1-2 1.2 Concepts Related to Data Configuration.......................................................................................................1-2 1.3 Data Configuration Flow...............................................................................................................................1-7
2 System Network Data Configuration ....................................................................................2-1

2.1 General Configuration Sequence...................................................................................................................2-2 2.2 External Input Data .......................................................................................................................................2-2 2.3 System Network Data Configuration ............................................................................................................2-2 2.3.1 Configuring IP Address of PCU...........................................................................................................2-2 2.3.2 Configuring Routing Information ........................................................................................................2-3 2.3.3 Configuring SNMP information...........................................................................................................2-4 2.4 Example for System Network Data Configuration........................................................................................2-5
3 Hardware Data Configuration.................................................................................................3-1

3.1 General Configuration Sequence...................................................................................................................3-2 3.2 External Input Data .......................................................................................................................................3-2 3.3 System Hardware Data Configuration ..........................................................................................................3-2 3.4 Example for System Hardware Data Configuration......................................................................................3-4
4 Pb/G-Abis Interface Data Configuration ..............................................................................4-1

4.1 General Configuration Sequence and Optimization on the Pb/G-A-bis Interface.........................................4-2 4.2 External Input Data .......................................................................................................................................4-2 4.3 Pb Interface Data Configuration....................................................................................................................4-2 4.3.1 Configuring E1 Exchange Data ...........................................................................................................4-2 4.3.2 Configuring E1 Timeslot......................................................................................................................4-3 4.3.3 Configuring LAPD Link ......................................................................................................................4-6 4.3.4 Optimized Configuration of the Pb Interface.......................................................................................4-7 4.4 Example for Pb Interface Data Configuration...............................................................................................4-8 4.4.1 Example ...............................................................................................................................................4-8 4.4.2 Configuration .......................................................................................................................................4-9 4.4.3 Configuration Check..........................................................................................................................4-10
5 GPRS Cell Configuration .........................................................................................................5-1

5.1 General Configuration Sequence and Optimization in the GPRS Cell .........................................................5-2
Issue 03 (2007-11-05)
Huawei Technologies Proprietary
Contents
5.2 External Input Data .......................................................................................................................................5-3 5.3 GPRS Cell Data Configuration .....................................................................................................................5-3 5.3.1 Configuring ATTR Data.......................................................................................................................5-3 5.3.2 Configuring GPRS Data of the Cell.....................................................................................................5-5 5.3.3 Configuring Cell CS Dynamic Adjustment Parameter.......................................................................5-12 5.3.4 Configuring MS Power Control Parameter........................................................................................5-15 5.3.5 Configuring Cell Related Information ...............................................................................................5-17 5.3.6 Configuring Cell PDCH.....................................................................................................................5-19 5.3.7 Configuring Cell Supporting Transmission Through Satellite ...........................................................5-21 5.3.8 Configuring Cell EGPRS Parameter ..................................................................................................5-22 5.3.9 Configuring Cell STANDARDOPTPARA Data ................................................................................5-24 5.3.10 Configuring Cell PRIVATEOPTPARA Data....................................................................................5-26 5.3.11 Optimized Configuration Data of the GPRS Cell ............................................................................5-31 5.4 Example for GPRS Cell Data Configuration...............................................................................................5-33
6 Gb Interface Data Configuration ............................................................................................6-1

6.1 Connection Modes of the Gb Interface .........................................................................................................6-3 6.1.1 Gb Over FR..........................................................................................................................................6-3 6.1.2 Gb Over IP ...........................................................................................................................................6-3 6.2 General Configuration Sequence...................................................................................................................6-4 6.2.1 Configuring the Gb Interface in Gb Over FR ......................................................................................6-4 6.2.2 Configuring the Gb Interface in Gb Over IP........................................................................................6-4 6.3 External Input Data .......................................................................................................................................6-4 6.3.1 External Input Data in Gb Over FR .....................................................................................................6-4 6.3.2 External Input Data in Gb Over IP.......................................................................................................6-5 6.4 Gb Interface Data Configuration...................................................................................................................6-5 6.4.1 Configuring Gb Interface E1 Data .......................................................................................................6-5 6.4.2 Configuring BC Information................................................................................................................6-7 6.4.3 Modifying NS Information (Optional).................................................................................................6-9 6.4.4 Configuring NS-VC and PVC Information........................................................................................6-10 6.4.5 Configuring IP Address for RPPU at the Gb Interface....................................................................... 6-11 6.4.6 Configuring Route for RPPU at the Gb Interface ..............................................................................6-12 6.4.7 Configuring the NSVL Information ...................................................................................................6-13 6.4.8 Configuring the BindNSVL Information ...........................................................................................6-14 6.4.9 Configuring Location Information of NSE Signaling Entity .............................................................6-15 6.4.10 Configuring Gb Interface Cell Information .....................................................................................6-15 6.4.11 Configuring the BSSGP Data...........................................................................................................6-16 6.5 Example for Gb Interface Data Configuration ............................................................................................6-19 6.5.1 Example for Gb Interface Data Configuration in Gb Over FR ..........................................................6-19 6.5.2 Example for Gb Interface Data Configuration in Gb Over IP............................................................6-23
ii
Issue 03 (2007-11-05)
Figures
Figures
Figure 1-1 Mapping between internal ports and external ports of L2PU board 1 ..............................................1-6 Figure 2-1 PCU maintenance networking ..........................................................................................................2-6 Figure 3-1 Configuration of each slot in the PCU6000 ......................................................................................3-3 Figure 3-2 PCU hardware configuration ............................................................................................................3-4 Figure 4-1 Pb interface trunk connection ...........................................................................................................4-8 Figure 6-1 Structure of Gb protocol. ..................................................................................................................6-2 Figure 6-2 Gb interface E1 connection.............................................................................................................6-20 Figure 6-3 Gb interface IP connection..............................................................................................................6-23
Issue 03 (2007-11-05)
iii
Tables
Tables
Table 4-1 E1 sub-timeslot table ..........................................................................................................................4-4 Table 4-2 Functions of the related commands ....................................................................................................4-7 Table 5-1 Corresponding network operation mode.............................................................................................5-6 Table 5-2 Meanings of different values of the DRXTimerMax..........................................................................5-8 Table 5-3 Explanations of the value .................................................................................................................5-19 Table 5-4 Cell STANDARDOPTPARA data configuration..............................................................................5-24 Table 5-5 Cell PRIVATEOPTPARA data configuration ...................................................................................5-27 Table 5-6 Explanation of PSPrecedence values................................................................................................5-28 Table 5-7 Optimized configuration commands of the GPRS............................................................................5-31 Table 6-1 Commands for configuring IP address for RPPU at the Gb interface ..............................................6-12 Table 6-2 Commands for configuring route for RPPU at the Gb interface.......................................................6-12 Table 6-3 Commands for configuring NSVL ...................................................................................................6-13 Table 6-4 Commands for configuring the BindNSVL......................................................................................6-14 Table 6-5 Commands used to modify the BSSGP data.....................................................................................6-17
iv
Issue 03 (2007-11-05)
1 Overview
1
About This Chapter
The following table lists the contents of this chapter. Title 1.1 Preconditions for Data Configuration 1.2 Concepts Related to Data Configuration 1.3 Data Configuration Flow Description
Overview
This section describes the Preconditions for Data Configuration. This section describes the Concepts Related to Data Configuration. This section describes the Data Configuration Flow.
Issue 03 (2007-11-05)
1-1
1 Overview
1.1 Preconditions for Data Configuration

The data configuration of the PCU can be implemented offline. Upon completion of the data configuration, the data can be loaded into the PCU with relevant commands. The data can also be configured and modified online. Prior to the data configuration of the PCU, the following conditions should be confirmed: The configuration of the PCU hardware equipment is known. The networking deployment of the GPRS system is known. Parameters from the service providers or those to be negotiated with the BSC and SGSN should be ready.
1.2 Concepts Related to Data Configuration

IP Address of the PCU
It refers to the external IP address of the PCU. With this IP address, the OMC Server communicates with the PCU, and operator can directly log in the PCU for data configuration and maintenance operation by local maintenance terminal (LMT). For details, refer to section 2.3.1 "Configuring IP Address of PCU" for detailed configuration method.
E1 Timeslot
The transmission of data and signaling between PCU and BSC or between PCU and BTS is mainly by E1. One 2 Mbit/s E1 is divided into 32 timeslots with each timeslot at 64kbit/s. Furthermore, one timeslot can consist of four 16 kbit/s sub-timeslots. Therefore, one E1 line can be divided into one hundred and twenty-eight 16 kbit/s sub-timeslots. Each E1 needs to occupy one timeslot for transmitting the synchronous information. One or more timeslots are required for signaling transmission between each PCU and BSC. In addition, each one for CS-1 and CS-2 or two for CS-3 or CS-4 of the remaining sub-timeslots can be used as a packet channel. For details, refer to section 4.3.2 "Configuring E1 Timeslot."
BSSGP
The BSSGP performs functions such as signaling transmission and subscriber data transmission. BSSGP at PCU provides RLC/MAC layer with the MS related parameters such as radio access capability and QoS of the data packet. Based on these parameters, RLC/MAC allocates and dispatches the radio resources. Moreover, BSSGP can obtain the parameters needed in SGSN from RLC/MAC, including the cell identifier and subscriber ID of the data packet. BSSGP at SGSN controls the downlink data traffic based on the parameters transmitted from PCU. Thus, BSSGPs cooperate in the management of the SGSN and BSS node. For details, refer to section 6.4.10 "Configuring Gb Interface Cell Information."
1-2
Issue 03 (2007-11-05)
1 Overview
NS
Here NS refers to the network service control sub-layer as specified in ETSI GSM 08.16. It is irrelative to the transmission network at the Gb interface. NS can provide logic links for BSSGP and transparent data channels for the upper layer in the load-sharing mode. Moreover, NS can also be used to manage NS-VC. For details, refer to section 6.4.3 "Modifying NS Information (Optional)" and section 6.4.4 "Configuring NS-VC and PVC Information."
FR
The link layer data at the Gb interface is based on Frame Relay (FR). Frame Relay virtual circuits are established between SGSN and BSS. LLC PDUs from many subscribers are multiplexed on these virtual circuits. FR shall be used for signaling and data transmission. The Gb interface connected to the network through FR is called Gb Over FR. The following characteristics apply for the Frame Relay connection: The maximum Frame Relay information field size shall be 1600 octets. The Frame Relay address length shall be 2 octets. Frame Relay PVCs shall be used. One or more Frame Relay PVCs shall be used between SGSN and BSS to transport BSSGP PDUs. For details, refer to section 6.4.1 "Configuring Gb Interface E1 Data" and section 6.4.2 "Configuring BC Information."
Gb Over IP
The Gb interface connected to the network through IP network is called Gb Over IP. The subscriber data and signaling data are transmitted through UDP packet. The protocol stacks and functions of the NS layer and upper layers are the same as Gb Over FR. For details, refer to section 6.4.5 Configuring IP Address for RPPU at the Gb Interface, 6.4.6 Configuring Route for RPPU at the Gb Interface, 6.4.7 Configuring the NSVL Information and 6.4.8 Configuring the BindNSVL Information.
CGI
CGI is the abbreviation of cell global identity. CGI=MCC+MNC+LAC+CI. Here, MCC indicates the mobile country code. It is composed of 3 digits. MNC indicates the mobile network number. It is used to identify the mobile network subscribers subscriber to, and it is composed of 2 or 3 digits dependent on the country. LAC indicates the location area code. Generally, each BSC has one LAC. CI indicates the cell ID. CGI is allocated and specified by the service providers. However, if the BSC data configuration is prior to the PCU data configuration, the CGI configuration of the corresponding cell in BSC can be referred to. In section 5.3.1 "Configuring ATTR Data", the configuration of CGI is involved.
CellID
Cell ID: CellID = MCC + MNC + LAC + RAC + CI. Here, RAC indicates the routing area code. It is numbered sequentially in one location area. This value can be obtained via conversion from CGI and RAC.
Issue 03 (2007-11-05)
1-3
1 Overview
In section 6.4.10 "Configuring Gb Interface Cell Information", the configuration of CellID is involved.
Backup of Cells in the Same BSC

PCU provides the function of cell backup for cells in the same BSC. To use this function, the subscriber should configure the active/standby RPPU (Pb) boards. The active and standby RPPU (Pb) boards should be configured under the same BSC. Normally, the cell service runs on the active RPPU (Pb) board. In case the active RPPU (Pb) board of the cell fails, the cell can be transferred to the standby RPPU (Pb) board automatically and thus minimize the influence caused by the RPPU board failure. For details, refer to section 5.3.1 "Configuring ATTR Data."
Network Operation Mode

Network operation mode I: the network sends a CS paging message for a GPRS-attached MS, either on the same channel as the GPRS paging channel (for example, the packet paging channel or the CCCH paging channel), or on a GPRS traffic channel. This means that the MS needs only to monitor one paging channel, and that it receives CS paging messages on the packet data channel when it has been assigned a packet data channel. Network operation mode II: the network sends the CS paging message to a GPRS-attached MS on the CCCH paging channel that is also used for PS paging. The MS needs only to monitor the CCCH paging channel. It has been assigned a packet data channel. The PS paging is received on the CCCH paging channel. Network operation mode III: the network sends a CS paging message for a GPRS-attached MS on the CCCH paging channel, and sends a GPRS paging message on either the packet paging channel (if allocated in the cell) or on the CCCH paging channel. This means that an MS that wants to receive pages for both circuit-switched and packet-switched services shall monitor both paging channels if the packet paging channel is allocated in the cell. No paging co-ordination is performed by the network. If the system is equipped with the Gs interface, mode I is configured. When the system is not equipped with the Gs interface or the packet common control channel (PCCCH), mode II should be configured. When the system is not equipped with the Gs interface but with the PCCCH, mode III is required. Cells in the same routing area should be configured with the same network operation mode. In section 5.3.2 Configuring GPRS Data of the Cell, related configuration is involved.
Timer and Counter

In course of configuration, the following timers and counters are involved. T3168 The timer T3168 is used to set the duration of MS waiting for the packet uplink assignment message. After transmitting the packet resource request message, MS will enter the state of waiting for the packet uplink assignment message. It depends on T3168 to decide when to stop the waiting. T3192 This timer is used on the mobile station side when the mobile station has received all of the RLC data blocks. When timer T3192 expires the mobile station shall release the resources associated with the TBF (e.g. TFI) and begin to monitor its paging channel. N3102
1-4
Issue 03 (2007-11-05)
1 Overview
At each cell reselection the mobile station shall set the counter N3102 to the value defined by the optional broadcast parameter PAN_MAX. Whenever the mobile station receives a Packet Ack/Nack that allows the advancement of V(S), the mobile station shall increment N3102 by the broadcast value PAN_INC, however N3102 shall never exceed the value PAN_MAX. Each time T3182 expires the mobile station shall decrement N3102 by the broadcast value PAN_DEC. When N3102 0 is reached, the mobile station shall perform an abnormal release with cell re-selection. In section 5.3.2 Configuring GPRS Data of the Cell, the configuration of T3168, T3192 and N3102 is involved.
Network Control Mode

During the network controlled cell re-selection, the network may request measurement reports from the MS and control its cell re-selection. Hence, three types of mode is defined as follows: NC0: Normal MS controls. The MS shall perform autonomous cell re-selection. NC1: MS control with measurement reports. The MS shall send measurement reports to the network. The MS shall perform autonomous cell re-selection. NC2: Network control. The MS shall send measurement reports to the network. The MS shall not perform autonomous cell re-selection. In section 5.3.5 Configuring Cell Related Information, related configuration is involved.
BSIC
It refers to the base station identity code. BSIC is used by MS to distinguish the adjacent BTSs. It is a 6bit code. It includes NCC (3bit) + BCC (3bit). NCC is the network color code used for distinguishing different countries (or different provinces in the same country) and operators. Its format is XY1Y2, wherein X is used to identify the service providers; Y1Y2 is used to identify the province. BCC is the base station color code allocated by each service providers independently. Different NCC should be used for adjacent PLMN, while in adjacent area. The same BCCH carrier may be used. In section 5.3.4 Configuring MS Power Control Parameter, the configuration of BSIC is involved.
Internal Port and External Port

The subboard on the RPPU is the L2PU, and each L2PU has four external ports. The RPPU can only process 4 Mbit/s signaling and data from each subboard and only two ports of each subboard can work at the same time, for example, the subboard has only 2 actual ports. For the L2PU board, the physical ports map to the logical ports in a four-to-two manner, as shown in Figure 1-1.
Issue 03 (2007-11-05)
1-5
1 Overview
Figure 1-1 Mapping between internal ports and external ports of L2PU board 1
7 6 5 4 L2PU
3 2
3 2 1 0 L2PU physicall port RPPU
1 0 logical port
BC
BC refers to the bearer channel of frame relay. As the timeslot group of E1 line, BC is the physical channel to transmit data and signaling. Its bandwidth = the number of timeslots x 64kbits/s. For example, the whole E1 line can be either configured as one BC, or divided into multiple BCs. For easy local management, in the same E1, BCs are distinguished by numbers, which are called BCID (BC Identification). At both ends of an E1, the local BCID is irrelevant to that of the same physical BC at the opposite end. Timeslot allocation configured for BC at one side must be the same as for a specific BC at the peer end, so that a communicable BC can be formed to connect the two ends. In section 6.4.2 Configuring BC Information, the configuration of BC is involved.
PVC
PVC refers to the permanent virtual connection of the frame relay. In one BC, a PVC is differentiated from others by its number, which is called DLCI (Data Link Connection ID). In general, the configuration of BC in SGSN and PCU should be the same, for example, the set of DLCI configured in the PCU and SGSN should be the same, or only the intersection can take effect. In section 6.4.4 Configuring NS-VC and PVC Information, the configuration of DLCI is involved.
LQC Mode
EGPRS adopts one of the following two link quality control modes: LA The basic principle of link adaptation is as follows:
1-6
Issue 03 (2007-11-05)
1 Overview
Step 1 When the radio environment does not change, PCU retransmits data in the coding mode with the original rate. Step 2 When the radio environment becomes worse, PCU retransmits 1/2 of the original RLC data block in the coding mode with a lower rate. In this way, it can guarantee the transmission of data blocks when the radio environment deteriorates. Step 3 When the radio environment becomes better, PCU retransmits data in the coding mode with a higher rate. ----End IR Incremental redundancy, also known as Hybrid Type II/III ARQ, enables higher data rates through combining information from different transmissions of RLC data blocks when decoding. The basic principle of IR is as follows: PCU adopts a coding mode with a high rate and weak error correction capability when transmitting data for the first time, regardless of the radio transmission environment. If the data is received incorrectly, PCU retransmits the extra coding data. The receiver combines the extra data and the data received previously and then decodes them. The process is repeated until the receiver decodes received data successfully.
1.3 Data Configuration Flow

To perform the data configuration flow, do as follows: Step 1 Configure system network data; Step 2 Configure hardware data; Step 3 Configure Pb interface data; Step 4 Configure GPRS cell data; Step 5 Configure Gb interface data.
Upon completion of the data configuration, the configuration data should be loaded into the FLASH Memory with the command write. Otherwise, the configuration data will be lost when the system is restarted. If it is the first time to configure data, only when the system is restarted can the data take effect after the data are loaded into the FLASH Memory. ----End
Issue 03 (2007-11-05)
1-7
2 System Network Data Configuration
System Network Data Configuration
About This Chapter

The following table lists the contents of this chapter. Title 2.1 General Configuration Sequence 2.2 External Input Data 2.3 System Network Data Configuration 2.4 Example for System Network Data Configuration Description This section describes the General Configuration Sequence. This section describes the External Input Data for the System Network Data Configuration. This section describes the System Network Data Configuration. This section describes the Example for System Network Data Configuration.
Issue 03 (2007-11-05)
2-1
System network data configuration is the precondition for data loading and maintenance of the system. Only after the system network data have been configured, can other data be loaded into the PCU smoothly. The data of this part should be configured at the PCU command terminal directly. If the hardware installation of the PCU has not been completed, other data should be configured first. In this case, the data of this part should be configured before other data are loaded into the PCU. If the network data of the PCU have been configured, please skip over this chapter and start data configuration with Chapter 3.
2.1 General Configuration Sequence

General configuration sequence is to add active/standby IP addresses of the PCU firstly, and then add the routing information. Finally, you need to add the SNMP information.
2.2 External Input Data

The external input data consists of the following three types: The IP address (the number of which is 2 % the number of PCU processing frames) of the PCU together with the corresponding subnet mask and gateway IP address. This parameter is planned and assigned by the service providers. The IP address of the maintenance console together with the corresponding subnet mask and gateway IP address. The IP address of the SNMP network maintenance console to receive trap message, the information of the operator, the location of the SNMP equipment, the group with the read priority only and the group with the write priority.
2.3 System Network Data Configuration

2.3.1 Configuring IP Address of PCU
If only the IP address of the POMU board is known when the IP address of the PCU is to be added, use the command ''telnet <active POMU board IP address>'' in the Run dialogue box under Windows before adding the IP address. If the IP address of the PCU is already known when the IP address is to be added, deleted, modified or queried, use the command ''telnet <PCU IP address>'' in the Run dialogue box under Windows directly to log in the PCU for operation. Each PCU can be configured with two IP addresses: the active/standby IP addresses. When the active IP address is unreachable, the standby IP address can be invoked automatically for maintenance.
Related Command
Command ipaddress add ipaddress del Function Adding the IP address of the PCU Deleting the IP address of the PCU
2-2
Issue 03 (2007-11-05)
Command ipaddress set ipaddress show
Function Modifying the IP address of the PCU Querying the IP address of the PCU
Major Parameter Description

IpAddress It refers to the active IP address of the PCU. It is defined and allocated by the service providers. This IP address can be configured as any IP address except for the active one. IpMask It refers to the subnet mask. Slave The identifier of standby IP address of the PCU, and It is optional parameter. If this parameter is involved, it suggests the IP address configured is standby IP address.
The standby IP address is optional with the PCU, while the active is compulsory. To ensure the reliability of system maintenance, it is recommended that both the active IP address and standby IP address should be configured.
2.3.2 Configuring Routing Information

During remote maintenance of PCU, the IP address of PCU, OMC Server and the maintenance console may belong to the different sub-network. If the PCU and the maintenance console are in different sub-network, the routing information configuration is required. The routing information should be configured at PCU, OMC Server and SNMP maintenance console at the same time.
Related Command
Command route add route del route set route show Function Adding routing information of the PCU. Deleting routing information of the PCU. Modifying routing information of the PCU. Querying routing information of the PCU.
Issue 03 (2007-11-05)
2-3
At PCU, the routing information can be configured via the command terminal. Generally, the maintenance console and the OMC Server are located in the same network segment. Therefore, the routing information configuration is required only at the OMC Server. The routing information at the OMC Server should be configured at the Unix command line interface. As far as the SNMP console is concerned, if the SNMP Server and the OMC Server are at the same network segment, no further configuration is need, or else the configuration of router information to the SNMP maintenance console is compulsory.

Destination It indicates the destination address, that is, the IP address of the peer end equipment. For the PCU, it indicates the IP address of the OMC Server and SNMP maintenance console; while for the OMC Server and SNMP maintenance console, it indicates the IP address of the PCU. Mask It refers to the subnet mask of the peer end equipment. Gateway It refers to the IP address of the local gateway router.
2.3.3 Configuring SNMP information

SNMP is the standard protocol widely used in TCP/IP network. It aims at transmitting the maintenance information between any nodes, with which the query of the information, modification of the configuration, troubleshooting, layout and report of the capacity at any nodes of the network can be realized.
Related Command
Command snmp add traphost snmp del traphost snmp set contact snmp set location snmp set rocommunity snmp set rwocommunity snmp set trap snmp show all Function Adding the IP address of the SNMP console to receive trap message Deleting the IP address of the SNMP console to receive trap message Modifying the information of the operator of the SNMP equipment Modifying the location information of the SNMP equipment Modifying the name of the group with the read only priority Modifying the name group with the write priority Modifying the trap flag to send Trap message Querying all the configuration of SNMP
2-4
Issue 03 (2007-11-05)

TrapHost It refers to the IP address of SNMP maintenance console to receive Trap message. Up to five IP address can be configured. Contact Contact information of SNMP network management personnel, this parameter should be configured as a string less than 64 characters. The configuration of this parameter will not affect the provision of the SNMP function. Location Location information of SNMP equipment, this parameter should be configured as a string less than 64 characters. The configuration of this parameter will not affect the provision of the SNMP function. RoCommunity The name of read-only community, this parameter should be configured as a string less than 32 characters. RwCommunity The name of read-write community, this parameter should be configured as a string less than 32 characters. Flag Trap flag, value range: Enable, Disable
2.4 Example for System Network Data Configuration

Example
Configure the IP address of the PCU as such: the active IP address is 136.17.24.5, the standby IP address is 136. 17.24.7 and the subnet mask is 255.255.0.0. Make maintenance for the PCU at the maintenance console and maintenance terminal which are located in the network segment different from that accommodating the PCU, as shown in Figure 2-1. As is known, the IP address of Router1 is 136.17.24.108 and the IP address of Router2 is 129.18.10.106. Maintenance for the PCU is made via the OMC Server, which is located in the same network segment as that accommodating the maintenance console and maintenance terminal. The IP address of the OMC Server is 129.18.10.12. The IP address of Router3 is 192.168.0.1, and the IP address of the SNMP server is 192.168.0.10. The SNMP maintenance console is suggested be located in Shanghai, and the maintenance staff is Leon, basic subscriber has the authority to read the trap and advanced subscriber have the authority to write the trap.
Issue 03 (2007-11-05)
2-5
Figure 2-1 PCU maintenance networking
WAN/LAN Router 3
Router 1
Router 2
SNMP Server
PCU
M2000 Server
LMT
LMT
Configuration
ipaddress add <IpAddress> <IpMask>[Slave]
ipaddress add 136.17.24.5 255.255.0.0 ipaddress add 136.17.24.7 255.255.0.0 slave
route add
<Destination> <Mask> <Gateway>
route add 129.18.10.0 255.255.255.0 136.17.24.108 (from PCU to OMC Server) route add 192.168.0.1 255.255.255.0 136.17.24.108(from PCU to SNMP Server)
The two commands above configured the routing information from PCU to OMC Server and SNMP Server. And the related routing information from OMC Server and SNMP Server to PCU should also be configured in OMC Server and SNMP Server separately
snmp add traphost snmp set contact

snmp set contact Leon
<TrapHost> <Contact> <Location> <RoCommunity> <RwCommunity>
snmp add traphost 192.168.0.10
snmp set location snmp set rocommunity
snmp set location shanghai
snmp set rocommunity basicsubscriber
snmp set rwocommunity
snmp set rwcommunity advancedsubscriber
Configuration Check
Upon completion of the configuration, use a PC in the same sub-network as that of OMC Server and input telnet <PCU IP address> (telnet 136.17.24.5 in this example) in the dialogue box under Windows Start\Run. If the login is successful, the network parameter configuration is considered to be successful.
2-6
Issue 03 (2007-11-05)
3 Hardware Data Configuration
3
About This Chapter
Title
Hardware Data Configuration
The following table lists the contents of this chapter. Description This section describes the General Configuration Sequence for adding new boards into the system. This section describes the External Input Data for the hardware configuration information. This section describes the System Hardware Data Configuration. This section describes the Example for System Hardware Data Configuration.
3.1 General Configuration Sequence 3.2 External Input Data 3.3 System Hardware Data Configuration 3.4 Example for System Hardware Data Configuration
Issue 03 (2007-11-05)
3-1

The general configuration sequence for adding new boards into the system is as follows: Step 1 Add slot information of the POMU board; Step 2 Add slot information of the RPPU board. ----End

The hardware configuration information of the PCU equipment includes: The number of the RPPU (Pb) board (a maximum of nine) The number of the RPPU (Gb) board (a maximum of three) The number and position of the L2PU in each RPPU.
3.3 System Hardware Data Configuration

The PCU has the following boards: POMU BSU (back board of the POMU) HSC RPPU (Pb) RPPU (Gb) E1TM (back board of the RPPU) L2PU (subboard of the RPPU) The information about the slots on the POMU, the RPPU, and the L2PU is required to be configured. The number of RPPU boards on the Pb interface must not exceed nine while that on the Gb interface must not exceed three.
Related Command
Command slot add slot del slot show Function Adding the slot information of a board Deleting the slot information of a board Querying the slot information of a board
3-2
Issue 03 (2007-11-05)
When modifying the board configuration (for example, adding an L2PU board to or deleting an L2PU board from the RPPU board), please delete the slot configuration information of the previous RPPU board first before adding the new configuration information.

SlotNo It refers to the slot number. The slots in a PCU6000 processing frame are numbered 020 from the left to the right, as is shown in Figure 3-1. During the configuration, you can refer to the silkscreen that is corresponding to each slot and attached to the PCU6000 processing frame. Excluding slots 7, 9, 1620, all slots must be configured. Figure 3-1 Configuration of each slot in the PCU6000
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 U P W R b 19 U P W R b 20
R P P U
R P P U
R P P U
R P P U
R P P U
R P P U
P O M U
P O M U
R P P U
R P P U
R P P U
R P P U
R P P U
R P P U
BoardClass The board type, that is, the type of the board inserted in the slot. In the PCU, the POMU board can only be inserted in slot 6 and slot 8. The parameter for these slots is configured as pomu. It is recommended that the RPPU (Gb) board should be inserted in slot 13~15 while other slots (0~5, 10~12) are only for the RPPU (Pb) board. The parameter of these slots is configured as "rppu", no matter the slot is of the RPPU (Pb) board or of the RPPU (Gb) board. PMC0 It is the type of subboard 0 in the RPPU. In each RPPU board, two subboards of the same type can be inserted and the subboard at the bottom is numbered 0. The type of the subboard inserted into the RPPU (Pb) should be the L2PU and be configured as lapd. The type of the subboard inserted into the RPPU (Gb) is the L2PU and is configured as "12pufr". If no L2PU is inserted into the RPPU, the subboard is configured as "none". PMC1 It is the type of subboard 1 in the RPPU. The configuration method of this parameter is the same as that of PMC0.
Issue 03 (2007-11-05)
3-3
Each RPPU board can be configured with one or two subboards. The type of the two subboards must be the same.
3.4 Example for System Hardware Data Configuration

Example
Figure 3-2 shows the hardware configuration of this PCU. Slots 02 are configured with the RPPU (Pb) board. The RPPU board in slot 2 is configured with two L2PU boards and the RPPU board in slot 0 and slot 1 is configured with an L2PU board at its bottom. Slot 15 is configured with the RPPU (Gb) board and the board is configured with one L2PU boards. Figure 3-2 PCU hardware configuration
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 U P W R b 19 U P W R b 20
R P P U
R P P U
R P P U
P O M U
P O M U
R P P U
Configuration
To configure the system hardware data, do as follows: Step 1 Configure slot information of the POMU board: slot add <SlotNo ><BoardClass ><PMC0><PMC1>
slot add 6 POMU none none slot add 8 POMU none none
Step 2 Configure slot information of the RPPU board:

slot add 0 RPPU lapd none slot add 1 RPPU lapd none slot add 2 RPPU lapd lapd slot add 15 RPPU l2pufr none
The former three commands in the above are used to configure the slot information of the RPPU (Pb) board while the last command is used to configure the slot information of the RPPU (Gb) board. In the Gb Over IP mode, the L2PU0 and L2PU1 need not to be configured.
----End
3-4
Issue 03 (2007-11-05)
Configuration Check
The data configuration information of the Pb interface takes effect only after the system is reset. Therefore, please use the write command to load the information into the FLASH Memory first and use the reboot command to reset the PCU before checking the hardware data configuration information. Input the command slot show all at the command terminal. If the configuration is normal, the system will display "normal" in the column Status (which indicates the status information of each slot), as shown in the following. SlotNo BoardClass PMC0 PMC1 Status 0 1 2 6 8 15 RPPU RPPU RPPU POMU1 POMU2 RPPU lapd lapd lapd none none l2pufr none none lapd none none none normal normal normal normal normal normal
The POMU board is backed up in the 1+1 mode. During running, the system will automatically select a POMU board as the active board (displayed as POMU1 during query) and the other board as the standby board (displayed as POMU2 during query). If the status of all boards configured is normal, the configuration is considered to be successful.
Issue 03 (2007-11-05)
3-5
4 Pb/G-Abis Interface Data Configuration
Pb/G-Abis Interface Data Configuration
About This Chapter

The following table lists the contents of this chapter. Title 4.1 General Configuration Sequence 4.2 External Input Data 4.3 Pb Interface Data Configuration 4.4 Example for Pb Interface Data Configuration Description This section describes the General Configuration Sequence for the Pb/G-Abis Interface Data Configuration. This section describes the External Input Data for the Pb/G-Abis Interface Data Configuration. This section describes the Pb Interface Data Configuration. This section describes the Example for Pb Interface Data Configuration.
Issue 03 (2007-11-05)
4-1
PCU is connected with BSC through the E1 and the Pb interface between them is a type of private interface. PCU is not directly connected with BTS through the trunk. The signaling and data between them are transmitted transparently via BSC. And the G-Abis interface between PCU and BTS is also a private interface. The E1 trunk connecting PCU with BSC can bear the LAPD link (link between PCU and BSC) as well as the packet service link (link between PCU and BTS). The purpose of the Pb/G-Abis interface configuration is just to define the application of each timeslot or sub-timeslot in the E1 line. One PCU can be connected with multiple BSCs. The BSCs are identified using the uniform BSC No. Moreover, one BSC can have several E1 trunk cables connected with PCU. The RPPU boards connected with the same BSC can be configured as the backup of each other. In PCU, each RPPU board can communicate with only one BSC.
4.1 General Configuration Sequence and Optimization on the Pb/G-A-bis Interface

The general configuration sequence is to configure the E1 exchange data first, and then configure the E1 timeslot. Finally, you are required to configure the LAPD link. After optimization, you can add all the configuration information of an E1 port on the Pb interface by running a command. The configuration includes: E1 exchange data E1 timeslot LAPD link Other parameters of an E1 port are configured with the default value. If there are any special requirements, run the corresponding configuration command.

The external input data consists of the following two types: The number of E1s connected with each RPPU (Pb) board, E1 port number and the application of each sub-timeslot in E1; Configuration of PCIC at BSC that is correspondent to E1 slot at RPPU (Pb).
4.3 Pb Interface Data Configuration

4.3.1 Configuring E1 Exchange Data
No matter whether E1 of the PCU transmits the data and signaling transparently through the Ater interface or not, the E1 connected with the RPPU (Pb) board should be configured using these commands.
4-2
Issue 03 (2007-11-05)
Related Command
Command pcu add e1exchange pcu del e1exchange pcu set e1exchange pcu show e1exchange Function Adding E1 exchange configuration information Deleting E1 exchange configuration information Modifying E1 exchange configuration information Querying E1 exchange configuration information

RPPUNo It refers to the slot number of the RPPU board. Generally, it is recommended that the RPPU (Pb) should be inserted in slots 05 and 1012. E1No It refers to the E1 number. Each RPPU (Pb) board provides 8 E1 ports at 2Mbit/s altogether through two L2PU subboards. Logically, the 8 E1 ports are numbered 07 from the bottom up successively. E1s 03 are from L2PU0 while 47 E1s are from L2PU1. Physically, these 8 E1 ports share one DB50 connector physically. Since each RPPU can process only 120 packet channels at a time, only one L2PU board is needed generally. At most 2 E1 ports are required. ConnnectType It refers to the equipment connected with PCU through this E1. It should be configured as BSC. RelatedE1No It refers to the peer entity E1 number. It should be configured as null. SynchroInfo It indicates whether this E1 is used for clock synchronization. Among the four E1s connecting the L2PU with a BSC, only one of them can be set to Yes. The other three should be set to No.
Each RPPU board can communicate with only one BSC. And it can process only 120 packet channels at a time. Therefore, generally, the RPPU board holds only one L2PU board and provides 12 E1 trunk cables. Generally, that one L2PU board gives four E1s applies only when the RPPUs are in the N+1 backup mode.
4.3.2 Configuring E1 Timeslot

Physically, the E1 sub-timeslot acts as the role of bearing the data & signaling transmission. A specific E1 sub-timeslot is determined by means of three parameters, such as RPPU board number, E1 number and E1 sub-timeslot number.
Issue 03 (2007-11-05)
4-3
Related Command
Command pcu add e1slot pcu del e1slot pcu set e1slot pcu show e1slot Function Adding E1 timeslot configuration information Deleting E1 timeslot configuration information Modifying E1 timeslot configuration information Querying E1 timeslot configuration information

E1TimeSlot It refers to the E1 sub-timeslot number. Table 4-1 shows the allocation of the E1 trunk timeslot and sub-timeslot in the Abis interface. The first column is used to indicate the timeslot number of a certain 64kbit/s timeslot in E1. Tsi (i ranges from 0 to 127) in the table is used to identify a certain 16kbit/s sub-timeslot in E1. In PCU, Tsi is numbered from left to right and from the top down. Table 4-1 E1 sub-timeslot table Timeslot 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 1 Ts0 Ts4 Ts8 Ts12 Ts16 Ts20 Ts24 Ts28 Ts32 Ts36 Ts40 Ts44 Ts48 Ts52 Ts56 Ts60 2 Ts1 Ts5 Ts9 Ts3 Ts17 Ts21 Ts25 Ts29 Ts33 Ts37 Ts41 Ts45 Ts49 Ts53 Ts57 Ts61 3 Ts2 Ts6 Ts10 Ts14 Ts18 Ts22 Ts26 Ts30 Ts34 Ts38 Ts42 Ts46 Ts50 Ts54 Ts58 Ts62 4 Ts3 Ts7 Ts11 Ts15 Ts19 Ts23 Ts27 Ts31 Ts35 Ts39 Ts43 Ts47 Ts51 Ts55 Ts59 Ts63
4-4
Issue 03 (2007-11-05)
Timeslot 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
1 Ts64 Ts68 Ts72 Ts76 Ts80 Ts84 Ts88 Ts92 Ts96 Ts100 Ts104 Ts108 Ts112 Ts116 Ts120 Ts124
BSCNo It refers to the BSC number of the logical cell. Uniformly numbered in PCU, it has nothing to do with the BSC equipment. And its only purpose is to identify the different BSCs at PCU. PCIC It refers to the PCIC number. It is corresponding to the E1 sub-timeslot (determined by means of RPPUNo, E1No and E1TimeSlot) of PCU in the one-to-one manner. The difference between PCIC and E1TimeSlot is that PCIC is numbered in the top-down and left-to-right manner. Please note the correspondence between these two parameters. For example, if both the E1 sub-timeslot number at PCU and the PCIC initial number at BSC are 0, the PCIC number corresponding to E1 sub-timeslot 1 is 32, to E1 sub-timeslot 2 is 64, to E1 sub-timeslot 3 is 96 and to E1 sub-timeslot 4 is 1. Usage It refers to the application of the E1 sub-timeslot. Generally, it is as follows: Step 1 Synchronization (configured as nouse). In PCU, the sub-timeslots 03 in each E1 are fixedly configured for synchronization.
Issue 03 (2007-11-05)
4-5
Step 2 LAPD link (configured as lapdlink). At least one LAPD link should be configured for the E1s connecting the PCU with a BSC. This LAPD link should be configured in the No. 16 timeslot, for example, the sub-timeslot from No.64 to No.67. Step 3 Packet service (configured as packetservice). Except for those used for synchronization and LAPD link, all the timeslots in E1 can be used for the packet service. Each sub-timeslot for CS-1 and CS-2 or every two sub-timeslot for CS-3 and CS-4 acts as a packet channel and each RPPU board can support a maximum of 120 packet channels. ----End
4.3.3 Configuring LAPD Link

The LAPD link is used to bear the signaling interacted with BSC.
Related Command
Command pcu add lapd pcu del lapd pcu set lapd pcu show lapd Function Adding LAPD link configuration information Deleting LAPD link configuration information Modifying LAPD link configuration information Querying LAPD link configuration information

LapdLinkNo It refers to the LAPD link number. It is obtained by uniformly numbering the LAPD links in the same PCU. The value range is 0254. RPPUNo It refers to the RPPU (Pb) board number. Value range: 05, 1012. E1No It refers to the E1 number of the E1 from the RPPU (Pb). These E1s are numbered 07 from the bottom to the top. StartTS It refers to the sub-timeslot number of the first sub-timeslot in the E1 timeslot configured as the LAPD link. Its range is 0127. BSCNo It refers to the BSC number of the logic cell, uniformly numbered in the PCU. It is unrelated to the BSC equipment. It is used to identify different BSCs connected with the PCU. Its range is 0254. LapdName
4-6
Issue 03 (2007-11-05)
It refers to the name of the LAPD link, a string of up to 31 characters and number, starting with a letter.
4.3.4 Optimized Configuration of the Pb Interface

Function
Complete all the configurations of an E1 port by running one command. The configurations include: E1exchange E1slot LAPD
Related Command
Table 4-2 Functions of the related commands Command pcu add pbe1 pcu del pbe1 Function Adding configuration information of the E1 port, including e1exchange, e1slot, and lapd. Deleting configuration information of the E1 port, including e1exchange, e1slot, and lapd

RPPUNo It refers to the RPPU board number Value range: 05, 1015 E1No It refers to the E1 number Value range: 07 BSCNo It refers to the BSC number of the peer end Value range: 0254 StartPCIC It refers to the start PCIC number Value range: 065534 EndPCIC It refers to the end PCIC number
Issue 03 (2007-11-05)
4-7
Value range: 065534 It refers to the difference between the EndPCIC and the StartPCIC is between 67 and 127. LapdNo LAPD link number Value range: 0254 LapdName It refers to the LAPD link name String length: a maximum of 31 The character string consists of letters, numerals, undline, hyphen, and colon. It is case insensitive and starts with a letter. SynchroInfo It refers to whether the E1 cable is used in clock synchronization. Yes or no
4.4 Example for Pb Interface Data Configuration

4.4.1 Example
The following example is based on Section 3.4 Example for System Hardware Data Configuration. Among the three RPPU boards, RPPU2 serves as the backup of RPPU0 and RPPU1. RPPU0 is connected with BSC0 and RPPU1 is connected with BSC1. L2PU0 in RPPU0 is connected with BSC0 and L2PU1 is connected with BSC1. For details, refer to Figure 4-1: Figure 4-1 Pb interface trunk connection
L2PU1
BSC0
L2PU0 L2PU0 L2PU0
BSC1
RPPU0
RPPU1
RPPU2
4-8
Issue 03 (2007-11-05)
Configure 120 packet channels in RPPU0 and RPPU1. RPPU2 is used as the backup board for RPPU0 and RPPU1.
4.4.2 Configuration
General Configuration Sequence of Pb Interface
Step 1 Configuring E1 exchange information: pcu add e1exchange <RPPUNo> <E1No> <ConnnectType> <RelatedE1No> <SynchroInfo>
pcu add e1exchange 0 0 bsc null yes pcu add e1exchange 1 0 bsc null yes pcu add e1exchange 2 0 bsc null yes pcu add e1exchange 2 4 bsc null yes
Step 2 Configuring E1 sub-timeslot information: pcu add e1slot <RPPUNo> <E1No> <E1TimeSlot> <BSCNo> <PCIC> <Usage>
pcu add e1slot 0 0 0 0 0 nouse pcu add e1slot 0 0 1 0 32 nouse pcu add e1slot 0 0 2 0 64 nouse pcu add e1slot 0 0 3 0 96 nouse pcu add e1slot 0 0 4 0 1 packetservice pcu add e1slot 0 0 5 0 33 packetservice pcu add e1slot 0 0 6 0 65 packetservice pcu add e1slot 0 0 7 0 97 packetservice pcu add e1slot 0 0 8 0 2 packetservice ... pcu add e1slot 0 0 63 0 111 packetservice pcu add e1slot 0 0 64 0 16 lapdlink pcu add e1slot 0 0 65 0 48 lapdlink pcu add e1slot 0 0 66 0 80 lapdlink pcu add e1slot 0 0 67 0 112 lapdlink pcu add e1slot 0 0 68 0 17 packetservice ... pcu add e1slot 0 0 127 0 127 packetservice ...
With the above 128 commands, the E1 sub-timeslot in RPPU0 is configured. The sub-timeslots 0~3 in E1 No.0 are applied for synchronization. The sub-timeslots 64~67 serve as LAPD links for signaling transmission. While the other 120 sub-timeslots are used for 120 packet services. And the timeslot of E1 in RPPU1 and RPPU2 should be configured accordingly. At the primary stage of the GPRS service, the traffic is rather low and the number of packet channels activated simultaneously is rather small. Therefore, only one LAPD link is required. Thus, the investment in the trunk can be reduced.
Step 3 Configuring LAPD link: pcu add lapd <LapdLinkNo> <RPPUNo> <E1No> <StartTS> <BSCNo> <LapdName>
pcu add lapd 0 0 0 64 0 bsc0 pcu add lapd 1 1 0 64 1 bsc1 pcu add lapd 2 2 0 64 0 bsc0back pcu add lapd 3 2 4 64 1 bsc1back
----End
Issue 03 (2007-11-05)
4-9
Optimized Configuration of the Pb Interface

PCU add pbe1 <RPPUNo> <E1No> <BSCNo> <StartPCIC> <EndPCIC> <LapdNo> <LapdName> <SynchroInfo>
PCU add pbe1 0 0 0 0 127 0 bsc0 yes PCU add pbe1 1 0 1 0 127 1 bsc1 yes PCU add pbe1 2 0 0 0 127 2 bsc0back yes PCU add pbe1 2 4 1 0 127 3 bsc1back yes
4.4.3 Configuration Check
The Pb interface data configuration information can take effect only after the relevant RPPU board is reset. Therefore, please use the write command to load the information to the FLASH Memory first and use the io reset command to reset the relevant RPPU board before checking the Pb interface data configuration information. Upon completion of the Pb interface data configuration, check the following items to ensure the Pb interface configuration is successful. The procedure is as follows: Step 1 Check the E1 configuration: Use the command pcu check e1config to check the completeness of the E1 configuration. If the E1 configuration is right, the following results will be output: pcu (supervisor)#pcu check e1config All E1 configuration data are right (including the Table E1exchange, LAPD and E1Slot). Step 2 Check the PCIC status: Use the command "mt pcic show available {<BSCNo> all } | {<BSCName> all } | <BoardNo> | <BoardNo> <E1No> | all to check the PCIC status. In this example, check the E1 sub-timeslots (PCIC) configuration in the RPPU boards which are plugged in slot 02. In the following, only the PCIC status of the RPPU board in slot 0 is listed: pcu (supervisor)#mt pcic show available all The operation is successful. 480 PCIC(s) available RPPU: 0 E1: 0 E1Slot: 4 BSC: 0 PCIC: 1 ...
4-10
Issue 03 (2007-11-05)
The E1slot configuration is considered to be successful as long as the number of PCICs available shown in the result is consistent with that of the E1slots configured.
Step 3 Checking the LAPD link status: Use the command "mt lapd show state {<BoardNo> all} | <LapdNo> |<LapdName>" to check the LAPD link status. In this example, check the status of the LAPD links configuration in the RPPU boards which are plugged in slot 02. In the following, only the LAPD link status of RPPU board in slot 0 is listed: pcu (supervisor)#mt lapd show state 0 all The operation is successful. Altogether 1 LAPD processed RPPU: 0 LAPD: 0 Management status: Unblock Operation status: Available
The LAPD link is considered to be in the normal status as long as the management status is displayed as Unblock and the operation status as Available.
----End
Issue 03 (2007-11-05)
4-11
5 GPRS Cell Configuration
5
About This Chapter
Title 5.1 General Configuration Sequence 5.2 External Input Data 5.3 GPRS Cell Data Configuration 5.4 Example for GPRS Cell Data Configuration
GPRS Cell Configuration
The following table lists the contents of this chapter. Description This section describes the General Configuration Sequence for the GPRS Cell Configuration. This section describes the External Input Data for the GPRS Cell Configuration. This section describes the GPRS Cell Data Configuration. This section describes the Example for GPRS Cell Data Configuration.
Issue 03 (2007-11-05)
5-1
The GPRS cell configuration mainly includes the GPRS cell ID configuration and the GPRS cell data configuration. The GPRS cell ID indicates the cell supporting the GPRS service. The objective of the GPRS cell data configuration is actually to confirm the various parameters required for defining a GPRS cell. Only when these parameters are all ready, can the GPRS cell be considered to be well defined. PCU and BSC cooperate in providing the relevant cell with packet and circuit switched services at the same time. For the cell supporting the GPRS service, the data should be configured in the PCU. In addition, relevant data configuration should also be made in the BSC. PCU is responsible for broadcasting the packet system information of the GPRS cell. If the cell supports the GPRS, it should broadcast the system information related to the service. The packet system information indicates the characteristics of the GPRS supported by the cell. It can be considered as the MS approach to the common information such as the frequency resource information, cell selection information, cell ID information and common channel configuration. PCU and BSC cooperate in providing the packet and circuit switched services. BSC should be configured with the common information and resources of the packet and circuit services of a cell. The common information includes the cell frequency resource and the radio channel attribute, etc. And the attributes related to the GPRS provided by the cell should be configured at PCU. In the GPRS system, the channel coding can be divided into 4 schemes: CS-1, CS-2, CS-3 and CS-4. When EGPRS function is enabled, additional 9 coding schemes for channels can be adopted: MCS-1, MCS-2, MCS-3, MCS-4, MCS-5, MCS-6, MCS-7, MCS-8 and MCS-9. The higher level the CS is at, the faster the transmission rate is. And the requirement for the channel quality in Um interface will be more stringent accordingly. The PCU can modify the coding scheme dynamically based on the factors such as the channel quality so as to achieve the optimum performance.
5.1 General Configuration Sequence and Optimization in the GPRS Cell

To configure the sequence and optimization in the GPRS cell, do as follows: Step 1 Configure the ATTR data of the cell. Step 2 Configure the GPRS data of the cell. Step 3 Configure the CSPARA data of the cell. Step 4 Configure the PWPAR data of the cell. Step 5 Configure the RELATEINFO data of the cell. Step 6 Configure the PDCH parameter of the cell. Step 7 Configure the SATTRANS data of the cell. Step 8 Configure the EGPRS data of the cell.
5-2
Issue 03 (2007-11-05)
If the cell is configured with PBCCH physically, it should also be configured with the PCCCH parameter, PRACH parameter and the PSI1 parameter. In addition, the parameters such as adjacent cell parameter, system information extension measurement parameter and system information network control measurement parameter are also optional for configuration. PBCCH is the optional configuration of Huawei PCU equipment. To configure it, relevant License is required. This manual only provides data configuration methods in regard to general functions.
----End Optimized configuration of the GPRS cell information is as follows: You can run a command to configure a cell. The configuration contains in the following tables: attr table cell table gprs table cspara table pwpar table pdchpara table egprspara table privateopt table Other parameters of the call are configured with default values. If there are any special requirements, run the corresponding configuration command.
The command can be used to add cell functions. It is used to configure more about the GPRS cell information.
Run the cell optimization configuration command to configure the GPRS cell information. To modify the configuration of a cell table, run the pcu set command. The configuration sequence is the general configuration sequence for configuring the GPRS cell information.

The external input data consists of the following two types: CGI, provided by the service providers; Network operation mode, defined based on the SGSN
5.3 GPRS Cell Data Configuration

5.3.1 Configuring ATTR Data
ATTR is used to indicate the attributes of the cell. It defines the CGI, RA and other such information of some cells.
Issue 03 (2007-11-05)
5-3
Related Command
Command pcu add attr pcu del attr pcu set attr pcu show attr Function Adding the ATTR configuration information of the cell Deleting the ATTR configuration information of the cell Modifying the ATTR configuration information of the cell Querying the ATTR configuration information of the cell

LCNo It refers to logic cell number It is uniformly numbered in the PCU. Value range: 065534 CGI It refers to the sole cell global identification. This parameter is provided by the service providers. It should be not only consistent with the CGI configuration in BSC but also corresponding to the CellID parameter configured on the Gb interface. BSC It refers to the BSC number of the logic cell Value range: 0254 It is uniformly numbered in the PCU and has nothing to do with the BSC equipment. It is used only to identify the different BSCs at the PCU. SiteNo It refers to the site number, which indicates BTS under a BSC. Value range: 065534 RA It refers to routing area (RA) number, which is a hexadecimal number. Value range: 00ff The RA is smaller than the LA (location area); for example, the RA here refers to the RA under the same BSC. At present, one PCU can be connected with multiple BSCs. The RAs will be numbered in each BSC sequentially. SGPRS It indicates whether to support the GPRS service. This parameter should be configured as Yes. PrimRPPU It refers to the slot number of the slot where the active RPPU (Pb) board used for processing the service of the cell is located. Configure it based on the actual situation. For easily locating
5-4
Issue 03 (2007-11-05)
the board, it is recommended that the RPPU (Pb) board should be configured in slots 05 and 1012 of the PCU processing frame. SecRPPU It refers to the number of the slot where the standby RPPU (Pb) board used for processing the service of the cell is located, and it should not be the same as the PrimRPPU. This parameter determines whether to apply backup at the same office direction for the cell. If it is required to apply this function, the standby RPPU (Pb) board used for processing services of the cell should be configured by means of this parameter. Note that this RPPU board should be connected with the relevant BSC. If it is not required to apply backup at the same office direction for the cell, this parameter should be configured as 255.
The parameters of PrimRPPU and SecRPPU are used to configure the backup function of the cell. Two modes of backup of the GPRS cell are offered: N+1 backup mode. In this mode, one specified board will be configured for backup, and this board may be connected with 4 BSC at the most, but only cells belong to the same BSC can be activated at a time. Mutual backup mode. In this mode, the mutual backuped RPPU boards should connect to the same BSC.
ActiveState It refers to the target activation status of the cell. This parameter is used to increase the reusability of the configuration. During data configuration, no matter whether active or deactive is configured to be for this parameter, the PCU initially configures it as Deactive. Upon completion of the cell data configuration, the command mt gcell active can be used to activate the cell. InUse It determines whether the cell configuration takes effect. It has two options, such as True or False. This parameter is for testing the configuration data after a new deployment or after the system software upgrade. The subscriber can set the parameter of one cell as True to locate the possible problems. If the cell proves to be able to provide services normally, then the parameter of all cells can be set as True. LCName It refers to the name of the logic cell. A maximum of 31 letters, numbers or symbols can be inputted for this parameter with the first digit being a letter.
5.3.2 Configuring GPRS Data of the Cell

Related Command
Command pcu add gprs pcu del gprs pcu set gprs pcu show gprs Function Adding the GPRS configuration information of the cell Deleting the GPRS configuration information of the cell Modifying the GPRS configuration information of the cell Querying the GPRS configuration information of the cell
Issue 03 (2007-11-05)
5-5

LCNo Logic cell number Value range: 0 65534 NMO Network operation mode The network operation mode is related to the paging channel used by the system. Three types of network operation modes are as follows: Mode I Mode II Mode III If the Gs interface is available, the system must be configured in mode I. If the Gs interface is unavailable, the system must be configured in mode II. If the Gs interface is unavailable, but the PCCCH is available, the system must be configured in mode III. Value range: 03 Table 5-1 Corresponding network operation mode NMO 0 1 2 3 Corresponding Network Operation Mode Network operation mode I Network operation mode II Network operation mode III Reserved
The current GPRS network is not configured with the Gs interface or the PCCCH. Thus, the NMO is set to 1, which indicates that mode II is used.
The network operation mode of a cell in the same routing area must be the same
T3168 Definition and format It refers to the timeout value of the T3168. The timer is used to set the maximum duration of the Packet Uplink Assignment message. The MS initiates a setup request for the uplink TBF by sending the Packet Resource Request message or by acknowledging the Channel Request Description message carried by the Packet Downlink Ack/Nack message. Then, the timer T3168 is started to wait for the Packet Uplink Assignment message on the network side.
5-6
Issue 03 (2007-11-05)
If the MS receives the Packet Uplink Assignment message before the timer T3168 expires, the T3168 is reset. If the MS does not receive the Packet Uplink Assignment message before the timer T3168 expires, it retriggers the packet access process. After retriggering the packet access process for four times, the MS considers that the setup of the uplink TBF fails. Value range: 5004000 ms (configured every 500 ms) It is recommended that 1000 ms is configured. Setting and impact If the parameter value decreases, the period for the MS determining the failure of the TBF setup gets shorter and the success rate of the TBF set up decreases in bad wireless condition. When the TBF fails to be set up, the average delay of the packet access gets shorter. In addition, the small value of the parameter increases the probability of resending the packet access request. As a result, the probability of the PCU reassignment increases and the system resource is wasted. If the parameter value increases, the period for the MS determining the failure of the TBF set up gets longer and the success rate of the TBF set up increases in bad wireless condition. When the TBF fails to be set up, the average delay of the packet access gets longer. Consider the following two points when configuring the parameter: Wireless condition is as follows: If the wireless condition is excellent, that is, BLER < 2%, Timer T3168 can be set to 500 ms. If the wireless condition is good, that is, 2% < BLER < 5%, Timer T3168 can be set to 1000 ms. If the wireless condition is bad, that is, 5% < BLER < 10%, Timer T3168 can be set to 2000 ms. Traffic measurement metrics: The T3168 is a timer that is used by the MS to initiate a request in the PACCH and wait for the Packet Uplink Assignment message. The value of the T3168 can be adjusted according to the uplink assignment success rate in the PACCH. The uplink assignment success rate = Uplink Assignment Successes in the PACCH/Uplink Assignments in the PACCH x 100%. If the success rate is low, you can increase the T3168 value to increase the uplink TBF assignment success rate when the link quality is good and no wireless resource congestion exists. For example, in a satellite cell, because the long and unstable transmit delay of the G-Abis interface is hard to improve, you can increase the T3168 value to improve the network quality. It is recommended that the T3168 value is set to 2000 ms. T3192 Definition and format The timeout value of the T3192 The timer is used to set the time for waiting for the TBF to be released after the MS receives the last data block. When the MS receives the RLC data block that contains FBI=1 and confirms that all the RLC data blocks in the TBF are received, the MS sends the Packet Downlink Ack/Nack message, carries FAI=1, and enables the T3192. If the T3192 expires, the MS releases relative resources of the TBF and monitors the paging channel. In the process for releasing the TBF, if the MS is in half-duplex state and receives the Packet Uplink Assignment message, the MS immediately responses to the Packet Uplink Assignment message. If no Packet Uplink Assignment message is
Issue 03 (2007-11-05)
5-7
received in the process of releasing the TBF, the MS enters the packet idle mode. In dual transfer mode, the MS enters the special mode. Value range: 0 ms, 80 ms, 120 ms, 160 ms, 200 ms, 500 ms, 1000 ms, and 1500 ms (500 ms is recommended). Setting and impact If the parameter value decreases, the MS releases the TBF faster. If there are new downlink data packets to send on the network side, the network must initiate the paging or immediate assignment process when the MS is ready. Thus, the setup time of the downlink TBF is long. If the parameter value increases, the related TBF resources, including TF1 and timeslot, are maintained long. If there is no downlink data transmission, the resource is occupied uselessly for a long time. If the T3192 is not overtime when the downlink data from the network side arrives, the network directly sends the Packet Downlink Assignment message to set up a downlink TBF and shorten the TBF setup time. When you configure the parameter: Choose the proper T3192 value by estimating the average interval of two continuous downlink data transmission. Analyze the cell service model and consider the cell service load. If the network resource is sufficient, that is, the GPRS service congestion rate is low, configure a large T3192 value to decrease the TBF setup time and improve the data transmission performance. For example, in a satellite cell, because the long and unstable transmit delay of the G-Abis interface is hard to improve, you can increase the T3192 value to improve the network quality. It is recommended that the T3192 value is set to 1500 ms. DRXTimerMax Definition and format The maximum time length of the non-DRX duration, that is, the Discontinuous Reception (DRX)_Timer_Max parameter in the call broadcast message. When the MS turns into the packet idle mode from the packet transmit mode, the non-DRX mode must be reserved for sometime. When the TBF is released, in non-DRX mode, the MS monitors all CCCH blocks (assuming that the cell is not configured with the PCCCH). At the same time, the PCU reserves the context related to the MS, and the reservation time is determined by the minimum values of the DRX_Timer_Max and the NON_DRX_TIMER. The value of the NON_DRX_TIMER is set according to the MS negotiating with the SGSN when the MS is attached with the GPRS. Normally, the value is large. Thus, the DRX_TIMER_MAX functions. Value range: 2 ( k - 1) between 0 s and 64 s. When k=0, the value is 0. It is recommended that the value is set to 4 s. That is, the MS turns into the DRX mode after 4 s. Table 5-2 shows meanings of different values of the DRXTimerMax. Table 5-2 Meanings of different values of the DRXTimerMax DRXTimerMax no 1s Meaning Immediately turn into the DRX mode Turn into the DRX mode after 1s
5-8
Issue 03 (2007-11-05)
DRXTimerMax 2s 64s
Meaning Turn into the DRX mode after 2s .. Turn into the DRX mode after 64s
Setting and impact When the network is not configured with the PCCCH, in non-DRX mode, the MS can monitor the immediate assignment message in all PCHs and AGCHs. The process lasts about 40 ms. In DRX mode, the MS can monitor the paging message only in the home paging group. Then, the MS receives the immediate assignment message in all paging blocks and reserved blocks in the AGCH. The process of receiving the paging message is long. The average duration is about the half of the paging multiframe period. When the BS_PA_MFRMS is 2, the duration is 235 ms. As a result, in non-DRX mode, the TBF setup time is short, but the MS power consumption increases. If the parameter value decreases, the TBF setup time increases. The MS power consumption, however, decreases. If the parameter value increases, the TBF setup time decreases. The MS power consumption, however, increases. To reduce the power consumption of a MS, it is recommended the value is set to 4 s. In addition, in DRX mode, the downlink data transmission has an impact on the TBF setup. The DRX period defined by the BS_PA_MFRMS also has an impact on the downlink TBF setup. According to a research, for the GPRS network, if the BTS3X series is used, it is recommended that the value of the BS_PA_MFRMS is set to 2. If the BTS2X series is used, it is recommended that the value of the BS_PA_MFRMS is set to 7. AccBurst It sets the type of the access burst used by MS in the PRACH, PTCCH/U and packet control acknowledgement message. It has two options, such as 8 bit and 11 bit. Some mobile phones do not support the 11 bit access burst type. Therefore, the recommended configuration of this parameter is 8 bit. CtrlAckType The control acknowledgement message type The parameter is used to set the type that the MS uses in the control acknowledge message. Value range: 0: Indicates that four access pulses are used and no polling message is required to be sent to obtain the time lead. 1: Indicates that the RLC/MAC control block is used and the polling message is required to be sent to obtain the time lead. It is recommended that the value is set to 0. BsCvMax Definition and format
Issue 03 (2007-11-05)
5-9
The maximum value of the MS countdown The parameter is used to set the BS_CV_MAX of the MS. The parameter is used by the MS to count the countdown value (CV) and determines the length of time of the T3198 (The T3198 value equals the time of BS_CV_MAX blocks. After the MS sends an uplink RLC data block, it sets the receive state of the data block to Pending and starts the T3198. If the MS receives the Packet Uplink Ack/Nack message before the T3198 expires, it updates the receive state of each uplink RLC data block based on the confirmation bitmap that contains in the message. If the T3198 corresponding to the RLC data block in Pending state expires, the MS sets the receive state of the data block to Nack and resends the uplink RLC data block. Value range: 015 (10 is recommended) In a satellite cell, it is recommended that the value is set to 15. Setting and impact If the parameter value decreases, the MS may resend the RLC data block whose waiting time expires before the PCU returns the Packet Uplink Ack/Nack message. As a result, more resources are occupied uselessly. If the parameter value increases, the move efficiency of sliding window decreases. The probability of the uplink TBF enters the countdown increases. As a result, the uplink transmit efficiency is reduced. To make the value precise, predict the transmit delay between the MS and the PCU. The transmit delay between the MS and the PCU in the current network is 200 ms. Thus, the value of the BS_CV_MAX cannot be less than 10. In a satellite cell, the transmit delay between the MS and the PCU is longer than 600 ms. Thus, the value of the BS_CV_MAX is set to 15. PanDec Definition and format The parameter is used to set the PAN_DEC that is used by the N3102 of the MS. When the T3182 expires, the N3102 decreases the value of the PAN_DEC. Value range: 07 and nouse (2 is recommended) Setting and impact Refer to "PAN " PanInc Definition and format The parameter is used to set the PAN_INC that is used by the N3102 of the MS. When the MS receives the Packet Uplink Ack/Nack message from the network that permitting the V (S) or the V (A) increases, the MS increases the PAN_INC to the N3102. The value of the PAN_INC must be greater than that of the PAN_DEC. Normally, PAN_INC = 2 x PAN_DEC. The N3102 value, however, cannot exceed the value defined by the PAN_MAX. Value range: 07 and nouse. (4 is recommended) Setting and impact Refer to "PAN ."
5-10
Issue 03 (2007-11-05)
The meanings of the two parameters are as follows: V(S): send state variable V(A): acknowledge state variablt
PanMax Definition and format The value of the PAN_MAX It is the maximum value of the N3102. Value range: 4, 8, , 32, and nouse (12 is recommended) Setting and impact Refer to "PAN ." EGPRSSupport The parameter is used to set whether the GPRS cell supports the EGPRS service. Value range: yes and no The PCU33 version does not support the EGPRS and the configuration is fixedly set to no. The PCU35 and its later versions support the EGRPS and whether the cell supports the EGPRS is determined by the attribute of the cell carrier frequency and the BSC configuration.
PAN Parameters Explanation

The PAN parameters are used to avoid the unpredictable link failures. In wireless link failure control, the PAN parameters are used with the N3102 at the MS side. When the MS detects that the sending window stops running, it starts the T3182. When the T3182 expires, the MS subtracts the PAN_DEC from the N3102 and run abnormal release and random access of the TBF. When the MS receives the Packet Uplink Ack/Nack message from the network to increase the V (S) or the V (A), it adds the PAN_INC to the N3102. The N3102 value, however, does not exceed the value defined by the PAN_MAX. When the N3102 value is no more than 0, the MS runs the TBF abnormal release and retriggers the cell reselection. When the cell reselects, the MS sets the N3102 value based on the PAN_MAX. The PAN_MAX is an optional broadcast parameter. Increasing the PAN_MAX and PAN_INC and decreasing the PAN_DEC can reduce the probabilities of the TBF abnormal release and cell reselection when the MS cannot receive the Packet Uplink Ack/Nack message. The MS, however, stops in the sending window. As a result, when the MS cannot send data, it occupies the wireless resources for a long time, and the resource usage rate is low. Decreasing the PAN_MAX and the PAN_INC and increasing the PAN_DEC facilitate the TBF abnormal release and cell reselection of an MS. As a result, the TBF normal release rate is reduced and the data transmission rate is affected. If the main GPRS services used by part of the cells in the network locate in the overlap area of two cells, you can: Adjust the CRH or the antenna angle to prevent the MS from reselecting a cell. Increase the PAN_MAX and the PAN_INC and decrease the PAN_DEC of a cell to reduce the sensibility of the MS to the TBF link abnormality.
Issue 03 (2007-11-05)
5-11
As a result, the MS does not frequently reselect the cell when the signal is weak or the link quality is poor. In a satellite cell, because the long and unstable transmit delay of the G-Abis interface is hard to improve and the MS may frequently reselect the cell if the MS is too sensible to the TBF link abnormality. To increase the sensibility of the MS in the satellite cell to the TBF link abnormality, it is recommended that: PAN_MAX = 32, PAN_INC = 2, PAN_DEC = 1
5.3.3 Configuring Cell CS Dynamic Adjustment Parameter

This configuration is to set the dynamic adjustment algorithm parameter of the cell channel-coding scheme (CS). The cell CS can be set to be a fixed value, for example, the CS can be fixed. It can also be set dynamically; for example, the network can dynamically adjust the CS based on the information such as the radio quality of the cell and the packet retransmission. Huawei PCU provides CS-3 and CS-4. When the channel quality is satisfactory, Huawei PCU can provide higher transmission rate and raise the utilization ratio of the radio frequency spectrum resources. To accomplish this function, the relevant License is required. Even the license is authorized, and the CS-3 or CS-4 is configured, if the free trunk at Abis is not enough to provide PDCH with more than one PCIC for CS-3 or CS-4, the system will adopt CS-2.
Related Command
Command pcu add cspara pcu del cspara pcu set cspara pcu show cspara Function Adding information of cell CS dynamic adjustment parameter Deleting information of cell CS dynamic adjustment parameter Modifying information of cell CS dynamic adjustment parameter Querying information of cell CS dynamic adjustment parameter

LCNo Logic cell number Value range: 065534 SupportCS34 Whether support CS-3 or CS-4 Value range: yes and no If the license from Huawei is authorized, please configure this parameter as yes, or else, configure it as no. UpFixCs The uplink fixed CS type
5-12
Issue 03 (2007-11-05)
Value range: cs1, cs2, cs3, cs4, and unfixed To use the fixed CS type in the uplink, set this parameter as cs1/cs2/cs3/cs4, which represent CS-1/CS-2/CS-3/CS-4 respectively. To adjust the CS type dynamically in the uplink, configure this parameter as Unfixed. UpDefaultCs The uplink default CS type Value range: cs1, cs2, cs3, and cs4 (The recommended configuration of the parameter is cs2.) If the uplink links dynamically adjust the CS type, the parameter sets the CS type that the first TBF uses in transmission. The CS types of other TBFs are dynamically adjusted based on the signal transmission quality. UpThdCs1Cs2 It refers to the retransmission rate threshold of the uplink TBF that determines the CS-1-to-CS-2 conversion of it. That is, when the retransmission rate of the uplink TBF is less than or equal to this value, the CS of the uplink TBF is converted from CS-1 to CS-2. Value range: 0100 (The recommended configuration of this parameter is 5.) UpThdCs2Cs1 It refers to the retransmission rate threshold of the uplink TBF that determines the CS-2-to-CS-1 conversion of it. That is to say, when the retransmission rate of the uplink TBF is more than or equal to this value, the CS of the uplink TBF is converted from CS-2 to CS-1. Value range: 0100 (The recommended configuration of this parameter is 10.) UpThdCs2Cs3 It refers to the retransmission rate threshold of the uplink TBF that determines the CS-2-to-CS-3 conversion of it. That is, when the retransmission rate of the uplink TBF is less than or equal to this value, the CS of the uplink TBF is converted from CS-2 to CS-3. Value range: 0100 (The recommended configuration of this parameter is 10.) UpThdCs3Cs2 It refers to the retransmission rate threshold of the uplink TBF that determines the CS-3-to-CS-2 conversion of it. That is, when the retransmission rate of the uplink TBF is more than or equal to this value, the CS of the uplink TBF is converted from CS-3 to CS-2. Value range: 0100. (The recommended configuration of this parameter is 20.) UpThdCs3Cs4 It refers to the retransmission rate threshold of the uplink TBF that determines the CS-3-to-CS-4 conversion of it. That is, when the retransmission rate of the uplink TBF is less than or equal to this value, the CS of the uplink TBF is converted from CS-3 to CS-4. Value range: 0100 (The recommended configuration of this parameter is 10.) UpThdCs4Cs3 It refers to the retransmission rate threshold of the uplink TBF that determines the CS-4-to-CS-3 conversion of it. That is, when the retransmission rate of the uplink TBF is more than or equal to this value, the CS of the uplink TBF is converted from CS-4 to CS-3. Value range: 0100 (The recommended configuration of this parameter is 20.)
Issue 03 (2007-11-05)
5-13
DnFixCs The downlink fixed CS type. Value range: cs1, cs2, cs3, cs4, and unfixed To use the fixed CS type in the downlink, set this parameter as cs1/cs2/cs3/cs4, which represent CS-1/CS-2/CS-3/CS-4 respectively. To adjust the CS type dynamically in the downlink, configure this parameter as Unfixed. DnDefaultCs It refers to the downlink default coding scheme. Value range: cs1, cs2, cs3, cs4 (The recommended configuration of this parameter is cs2.) If the coding scheme can be dynamically adjusted in the downlink, the coding scheme used for transmitting the first TBF can be set by this parameter. And the coding scheme of other TBFs can be dynamically adjusted based on the signal transmission quality. The recommended configuration of this parameter is cs2. DnThdCs1Cs2 It refers to the retransmission rate threshold of the downlink TBF that determines the CS-1-to-CS-2 conversion of it. That is, when the retransmission rate of the downlink TBF is less than or equal to this value, the CS of the downlink TBF is converted from CS-1 to CS-2. Value range: 0100 (The recommended configuration of this parameter is 5.) DnThdCs2Cs1 It refers to the retransmission rate threshold of the downlink TBF that determines the CS-2-to-CS-1 conversion of it. That is, when the retransmission rate of the downlink TBF is more than or equal to this value, the CS of the downlink TBF is converted from CS-2 to CS-1. Value range: 0100 (The recommended configuration of this parameter is 10.) DnThdCs2Cs3 It refers to the retransmission rate threshold of the downlink TBF that determines the CS-2-to-CS-3 conversion of it. That is, when the retransmission rate of the downlink TBF is less than or equal to this value, the CS of the downlink TBF is converted from CS-2 to CS-3. Value range: 0100 (The recommended configuration of this parameter is 10.) DnThdCs3Cs2 It refers to the retransmission rate threshold of the downlink TBF that determines the CS-3-to-CS-2 conversion of it. That is, when the retransmission rate of the downlink TBF is more than or equal to this value, the CS of the downlink TBF is converted from CS-3 to CS-2. Value range: 0100 (The recommended configuration of this parameter is 20.) DnThdCs3Cs4 It refers to the retransmission rate threshold of the downlink TBF that determines the CS-3-to-CS-4 conversion of it. That is, when the retransmission rate of the downlink TBF is less than or equal to this value, the CS of the downlink TBF is converted from CS-3 to CS-4. Value range: 0100 (The recommended configuration of this parameter is 10.) DnThdCs4Cs3
5-14
Issue 03 (2007-11-05)
It refers to the retransmission rate threshold of the downlink TBF that determines the CS-4-to-CS-3 conversion of it. That is, when the retransmission rate of the downlink TBF is more than or equal to this value, the CS of the downlink TBF is converted from CS-4 to CS-3. Value range: 0100 (The recommended configuration of this parameter is 20.) ResAssStrType It refers to the flag to determine the resource allocation strategy. Value range: MaxBandWidth and SaveRadioRes If it is configured as MaxBandWidth, it means that the strategy for maximum bandwidth will be adopted, and if it is configured as SaveRadioRes, it means that the strategy for optimization utilization of the radio resource will be adopted. And if the system does not support CS-3 or CS-4, this parameter should be configured as MaxBandWidth.
Configuration Recommendation
The uplink application in the current network is few, so the performance requirement of the upload speed is not as high as that of the downlink application. The recommended coding scheme configurations are as follows: For the network that does not support the CS3/4, set to "pcu add cspara (LCNo) no unfixed cs1 5 10 10 20 10 20 unfixed cs2 5 10 10 20 10 20 maxbandwidth" is recommended. For the network that support the CS3/4, set to "pcu add cspara (LCNo) yes unfixed cs2 5 10 10 20 10 20 unfixed cs4 5 10 10 20 10 20 maxbandwidth" is recommended. For the cell where the air interface quality is poor (receive level is greater than -90 dB or the average C/I is smaller than 15) and the requirement for the GPRS speed is low, set to "pcu add cspara (LCNo) no cs2 cs2 5 10 10 20 10 20 cs2 cs2 5 10 10 20 10 20 maxbandwidth" is recommended.
5.3.4 Configuring MS Power Control Parameter

This configuration is to set the power parameters used by the mobile station in the GPRS. With these parameters, the mobile phone can execute power measurement or implement the related functions.
Related Command
Command pcu add pwpar pcu del pwpar pcu set pwpar pcu show pwpar Function Adding information of cell power control parameter configuration Deleting information of cell power control parameter configuration Modifying information of cell power control parameter configuration Querying information of cell power control parameter configuration

LCNo
Issue 03 (2007-11-05)
5-15
Logic cell number Value range: 065534 ALPHA It refers to the Alpha parameter that is used for open loop power control. The ALPHA is used by the MS to count the output power PCH in the uplink PDCH of the MS. The parameter sets the decreased level of mobile transmit power and open loop power control that are corresponding to the path loss when the GPRS dynamic power control is used. The recommended configuration of this parameter is 1.0. GAMMA The initial power level Value range: 031 (The recommended configuration of this parameter is 14.) When the GPRS dynamic power control is used, the parameter sets the expected receive signal strength at the BTS end, that is, the MS initial power level. In the formula of the MS output power, PCH = min (0 GAMMA - ALPHA x (C + 48), PMAX), The parameter has an impact on the output power of the MS. The MS output power increases with the decrease of the parameter value. TAVGW Signal strength filter period for power control in packet idle mode, which is used to set the signal strength filter period of MS for power control in the packet idle mode. Value range: 025 (The recommended configuration of this parameter is 10.) The parameter is the period signal level filter parameter. It is used in idle mode for signal strength filter for the power control. The MS measures the downlink signal strength in packet idle mode. Use the parameter to count the Cn (Cn is the MS received signal level counted by the MS) in the MS output power formula PCH = min (0 GAMMA - ALPHA x (C + 48), PMAX). The parameter indicates the relation between Cn and Cn-1. The impact of Cn-1 to Cn has a positive relation with the parameter. TAVGT Signal strength filter period for power control in packet transfer mode, which is used to set the signal strength filter period of MS for power control in packet transfer mode. Value range: integer between 025. The recommended configuration of this parameter is 10. The parameter is the period signal level filter parameter. It is used in packet transmit mode for signal strength filter for the power control. The MS measures the downlink signal strength in packet transmit mode. The Cn (Cn is the MS received signal level counted by the MS) in MS output power formula PCH = min (0 GAMMA ALPHA x (C + 48), PMAX). The parameter indicates the relation between Cn and Cn-1. The impact of Cn-1 to Cn has a positive relation with the parameter. PB Power reduction value used by the BTS on PBCCH blocks, which is relative to the output power used on BCCH. Value range: 0, 2 dB, 4 dB, , 30 dB (The recommended configuration of this parameter is 2 dB.)
5-16
Issue 03 (2007-11-05)
The parameter indicates the decreased value of the BTS output power of the measuring channel. If the cell is not configured with PBCCH, this parameter does not work. PCMeasChan The channel that is used when the MS measures the receive power. The parameter is used to set a channel where the MS measures the receive power level and performs the uplink power control. Value range: bcch and pdch MeasChAvail This parameter indicates if the optional PSI4 message is broadcast. At present, Value range: yes and no (This parameter should be configured as No.) NAVGI This parameter is an interfering signal strength filter constant for power control. Value range: 015 (The recommended configuration of this parameter is 2.)
Power Control Parameters Explanation

The output power of a mobile: PCH = min (0 CH x (C + 48), PMAX) =1, so the formula is simplified to: PCH = min (0 CH C 48, PMAX) In the GSM900, 0 = 39 dBm, the value of CH is that of the GAMMA, C is a value obtained from the level of the downlink channel. If the measurement is performed at a fixed point, the value of C is equal to the received level. If the power control is to be started, that is to use the power less than PMAX to transmit: 0 CH C 48 < PMAX When C > 0 CH 48 PMAX, the power control starts, and the default value is 66 dB. The test finds out that the best received level of Huawei cell is around 60 dBm. Therefore, it is reasonable to configure the power control parameters as the previous recommendation.
5.3.5 Configuring Cell Related Information

Functions
This command is used to configure related information of a cell. According to the command, the network control mode that the cell uses, the BTS identity code, the packet access priority, and the route area color code can be chosen.
Related Command
Command pcu add relatedinfo Function Adding cell related configuration information.
Issue 03 (2007-11-05)
5-17
Command pcu del relatedinfo pcu set relatedinfo pcu show relatedinfo
Function Deleting cell related configuration information. Modifying cell related configuration information. Querying cell related configuration information.

LCNo Logic cell number The value range: 065534 NCO Network control mode Value range: NC0, NC1, and NC2 For details, refer to section 1.2 "Concepts Related to Data Configuration." At present, it is fixedly configured as nc0, which indicates the MS controlled cell re-selection, no measurement reporting. BSIC Definition and format Base station Identity code Value range: 063 For details, refer to section 1.2 "Concepts Related to Data Configuration." This parameter is allocated and specified by the service providers. If the BSC data are configured prior to PCU, please refer this parameter configuration to the BSIC configuration information of BSC and make this parameter in consistency with that configuration. Setting and impact When the PBCCH is not configured, the BSIC is not used in the packet service. The BSIC in the PCU can be inconsistent with the BSIC in the BSC. When the PBCCH is configured, the mobile is required to obtain the BSIC code for cell reselection in the PHCCH. The BSIC in the PCU must be consistent with the BSIC in the BSC. SpgcCCCHSup It indicates whether a cell supports the parameter SPLIT_PG_CYCLE on CCCH from the network side. SPLIT_PG_CYCLE is used to define the period of DRX, and it is optional for BTS and MS to support paging group based on CCCH. Value range: yes and no (The recommended configuration of this parameter is no.) PriAccThr Packet access priority level, which is used to set the priority of MS allowed to access the cell. Value range: 0 and 36 (The recommended configuration of this parameter is 6.)
5-18
Issue 03 (2007-11-05)
Table 5-3 shows the explanations of the value. Table 5-3 Explanations of the value Value 0 3 4 5 6 Meaning Prohibit the Packet access. Allows the packet access whose priority level is one. Allows the packet access whose priority level is one and two. Allows the packet access whose priority level is from one to three. Allows the packet access whose priority level is from one to four.
RAColor It refers to the routing area color code that is used to set the routing area color code of the GPRS cell. Value range: 07 You must configure this parameter based on the corresponding stipulations of the service providers. If no stipulation, take any value within the range as you like.
5.3.6 Configuring Cell PDCH

Function
This command is used to configure related attributes of the PDCH in a cell. According to the command, the number of uplink and downlink TBFs that each PDCH supports can be confirmed.
Related Command
Command pcu add pdchpara pcu del pdchpara pcu set pdchpara pcu show pdchpara Function Adding PDCH parameter configuration information of the cell Deleting PDCH parameter configuration information of the cell Modifying PDCH parameter configuration information of the cell Querying PDCH parameter configuration information of the cell

LCNo Logic cell number The value range: 065534 MaxUlHighLd
Issue 03 (2007-11-05)
5-19
Definition and format The maximum number of uplink TBFs can be supported by a PDCH in the cell. Value range: 17. (The recommended configuration of this parameter is 7.) . MaxUlHighLd must be greater than or equal to MaxUlLowLd. Setting and impact If the parameter value decreases, the number of multiplexing TBFs in the uplink channels decreases. If the GPRS traffic is large and the number of the GPRS subscribers is large, the uplink channel resource is easy to be used out. Therefore, other GPRS subscribers cannot access the network due to insufficient uplink channel resource. If the GPRS traffic is not heavy, especially the data transmission service is not busy, few data channels are configured in the cell, and the TBF setup failure rate is high (No channel is available in the uplink TBF setup and the release performance measurement, so the TBF setup failure rate is high.). It is recommended that the number of the data service channel is increased. Otherwise, set MaxUlHighLd to 7. If the parameter value increases, the number of multiplexing TBFs in the uplink channels increases and the congestion rate of the uplink data transmission increases. In addition, because the uplink channel is the control channel of the TBF, the congestion rate of the control signaling transmission increases. Therefore, the scheduling of uplink transmit block of some subscribers is delayed and the transmit performance is affected. Therefore, if the GPRS traffic is heavy, the cell is configured with many data channels and the subscriber requires high speed of the GPRS. It is recommended that the MaxUlHighLd is set to 4 to reduce the upper limit of uplink TBF multiplexing. MaxDlHighLd Definition and format The maximum downlink TBFs can be supported by a PDCH in the cell. Value range: 18 (The recommended configuration of this parameter is 8.) The MaxDlHighLd must be greater than or equal to the MaxDlLowLd. Setting and impact If the parameter value decreases, the number of multiplexing TBFs in the downlink channels decreases. Because the number of the MS supported downlink timeslots is greater than the number of the uplink timeslots, subscribers are not allowed to access the network if the upper limit of the downlink multiplexing TBF decreases. It is recommended that the MaxDlHighLd is set to 8. In some test cells, however, if they require high GPRS speed, it is recommended that more on-site data channels are configured. The upper limit of the downlink multiplexing TBF is decreased to ensure the bandwidth of the test subscriber. It is recommended that the MaxDlHighLd is set to 4. If the parameter value increases, the number of multiplexing TBFs in the downlink channels increases and the congestion rate of downlink data transmission increases. The limited bandwidth of the channel is shared by multiple subscribers. Therefore, the throughput of a subscriber is limited. MaxUlLowLd Definition and format If the number of uplink TBFs on the PDCH in the cell exceeds the value of the parameter and there is few circuit service, the PCU applies the dynamic PDCH to the BSC. Value range: 17 (The recommended configuration of the parameter is 4.) The MaxUlLowLd must be smaller than or equal to the MaxUlHighLd.
5-20
Issue 03 (2007-11-05)
Because the MaxUlLowLd must be smaller than or equal to the MaxUlHighLd, it is recommended that the value of the MaxUlLowLd is set to 3 if the value of the MaxUlHighLd is set to 4. Setting and impact The parameter defines the threshold for determining whether the GPRS service is busy or not. It triggers whether the network side applies the dynamic PDCH to the BSC. The usable PDCH in the board is limited (If only the GPRS service is supported, one RPPU supports 120 channels. If the EDGE service is supported, one RPPU supports 100 channels.) To ensure that the dynamic PDCH of key cell in the PS domain has the priority in application, it is recommended that the uplink MaxUlLowLd is set to 2. MaxDlLowLd Definition and format If the number of downlink TBFs of the PDCH in the cell exceeds the value of this parameter and the circuit service is idle, the PCU applies the dynamic PDCH to the BSC, Value range: 18 (The recommended configuration of this parameter is 4.) The MaxDlLowLd must be smaller than or equal to the MaxDlHighLd. Because the MaxDlLowLd must be smaller than or equal to the MaxDlHighLd, it is recommended that the value of the MaxDlLowL is set to 3 if the MaxDlHighLd is set to 4. Setting and impact The parameter defines the threshold for determining whether the GPRS service is busy or not. It triggers whether the network side applies the dynamic PDCH to the BSC. The usable PDCH in the board is limited (If only the GPRS service is supported, one RPPU supports 120 channels. If the EDGE service is supported, one RPPU supports 100 channels.) To ensure the dynamic PDCH of key cell in the PS domain has the priority in application. It is recommended that the downlink MaxUlLowLd is set to 4.
5.3.7 Configuring Cell Supporting Transmission Through Satellite

Function
This command targets at the Abis interface. The command can decide whether a satellite transmission cell supports the satellite transmission mode.
Related Command
Command pcu add sattrans pcu del sattrans pcu set sattrans Function Adding satellite transmission parameter configuration information of the cell Deleting satellite transmission parameter configuration information of the cell Modifying satellite transmission parameter configuration information of the cell
Issue 03 (2007-11-05)
5-21
Command pcu show sattrans
Function Querying satellite transmission parameter configuration information of the cell

LCNo Logic cell number Value range: 065534 SuprtSatTrans Whether the cell supports satellite based trunk between BSC and BTS. If this parameter is configured as yes, it means the cell support satellite based trunk, or else, it means the cell does not support the satellite based trunk.
5.3.8 Configuring Cell EGPRS Parameter

Function
This command is used to set the channel coding scheme (MCS) of a cell to dynamically adjust the algorithm parameters. The MCS of the cell can be set to a fixed value. That is, you can use a fixed coding scheme. The MCS of the cell also can be dynamically set. That is, according to the radio quality of a cell and the retransmission of the packet, the network can dynamically adjust the MCS.
Related Commands
Command pcu add egprspara pcu del egprspara pcu set egprspara pcu show egprspara Function Adding information of cell EGPRS parameter Deleting information of cell EGPRS parameter Modifying information of cell EGPRS parameter Querying information of cell EGPRS parameter

LCNo Logic cell number Value range: 065534 LQCMode Definition and format
5-22
Issue 03 (2007-11-05)
Link quality control (LQC) mode. It is a mode to dynamically adapt to the wireless transmit environment to improve the link quality through changing modulation mode and coding scheme during the data transmission. Value range: IR and LA Setting and impact The Link adaptation (LA) dynamically adjust the coding scheme of the channel by the network side based on the channel link transmit quality. The link quality is measured by the 8PSK MEAN BEP and the 8PSK CV BEP of the Packet EGPRS Downlink Ack/Nack message by the MS. According to the wireless measurement reported by the MS, the network side determines the coding scheme to transmit. The cell where the air interface quality is good is normally configured to LA. The Increment redundancy (IR) requires the network to retransmit only the data block with different punched codes and requires the MS to cache the history error information. Together with the data block whose error is rectified, the IR mode can achieve good transmit effect in the cell where the air interface quality is poor. However, The IR mode needs the support of the MS terminal. The cell where the air interface quality is poor is normally configured to IR. For details, refer to section 1.2 "Concepts Related to Data Configuration." BepPeriod This field contains the bit error probability (BEP) filter averaging period. Value range: 010 (The recommended configuration of this parameter is 10.) Egprs11BitChanReq It indicates whether to support 11-bit EGPRS channel request. Value range: Yes and No The G3PCUV300R006C01 and its later versions support the access of the EGPRS 11BIT. For details, refer to the Version Configuration Information of each version. UpFixMcs Uplink fixed MCS type, It can be valued as MCS1-MCS9 or UNFIXED. Value range: MCS1MCS9, and UNFIXED The uplink fixed MCS type. To use the fixed MCS type in the uplink, set this parameter as MCS1 - MCS9. To adjust the MCS type dynamically in the uplink, set this parameter as Unfixed. UpDefaultMcs It refers to the uplink default MCS type. Value range: MCS1MCS9 If the MCS type can be dynamically adjusted in the uplink, this parameter can determine the MCS type used for transmitting the first TBF. And the MCS types of other TBFs can be dynamically adjusted based on the signal transmission quality. The recommended value of this parameter is MCS2. DnFixMcs
Issue 03 (2007-11-05)
5-23
It refers to the downlink fixed MCS type. Value range: MCS1MCS9, and UNFIXED To use the fixed MCS type in the downlink, set this parameter as MCS1-MCS9 that represents MCS-1 - MCS-9 respectively. To adjust the MCS type dynamically in the downlink, set this parameter as Unfixed. DnDefaultMcs It refers to the downlink default MCS type. Value range: MCS1MCS9 If the downlink dynamically adjusts the MCS type, the parameter sets the MCS type of the first TBF in the transmission of the TBF. The MCS type of other TBFs is dynamically adjusted based on the signal transmission quality. For the cell where the air interface quality is good, it is recommended that the value is set to MCS6. For the cell where the air interface quality is poor, it is recommended that the value is set to MCS4.
5.3.9 Configuring Cell STANDARDOPTPARA Data

Function
This command is used to set the maximum value of the N3101, N3103, and N3105. The G3PCUV300R005C05 opens some network optimization parameters to subscribers and refines the functions of these parameters to the cell lever. Then subscribers can adjust the configuration based on the actual cell situation, such as service type, air interface coverage, and service requirements. The N3101, N3103, and N3105 are standard parameters defined in the protocol. Thus, they are arranged in the standard optimized parameters table.
Related Command
Table 5-4 lists the cell STANDARDOPTPARA data configuration. Table 5-4 Cell STANDARDOPTPARA data configuration Command pcu add standardoptpara pcu del standardoptpara pcu set standardoptpara pcu show standardoptpara Function Adding the configuration information of standard network parameters in a cell Deleting the configuration information of standard network parameters in a cell Modifying the configuration information of standard network parameters in a cell Querying the configuration information of standard network parameters in a cell
5-24
Issue 03 (2007-11-05)

LCNo It refers to logic cell number Value range: 065534 N3101 Definition and format The parameter is used to set the maximum value of the N3101. In uplink dynamic assignment mode, the network side achieves that multiple MSs share one uplink channel through carrying the USF in the downlink blocks. When the network side assigns the USF to the uplink TBF, that is, after the uplink TBF is set up, start the N3101. The network side waits for the MS to send the uplink data in the RLC uplink block that is reserved by the USF. If the MS sends valid uplink RLC block, reset the N3101. Otherwise, the N3101 is increased. When the N3101 overflows, the current uplink TBF is released abnormally. Value range: 830 (The default value is 20.) Setting and impact If the parameter value decreases, the tolerance of the network side to the uplink link abnormality decreases. Therefore, the ratio of the TBF abnormal release increases. If the parameter value increases, the network side still assigns the uplink resource to the MS when the network side cannot receive the corresponding MS data blocks due to the MS fault. The system resource is wasted. In key types of the GPRS traffic measurement, the number of the uplink TBF abnormal release caused by the N3101 overflow in the uplink TBF setup and release performance measurement records some of the reasons of the uplink TBF abnormal release. Normally, the reasons are poor quality of G-Abis interface transmit link, poor quality of air interface, bad network design, and mobile fault. When all the problems are solved, you can reduce the number of uplink TBF abnormal releases due to the N3101 overflow by increase the threshold of the N3101. The network quality is improved. In a satellite cell, because the long and unstable transmit delay of the G-Abis interface is hard to improve, you can improve the network quality by increasing the threshold of the N3101. It is recommended that the threshold of the N3101 in the satellite cell is set to 30. N3103 Definition and format The parameter is used to set the maximum value of the N3103. After the uplink transmit ends, the network side sends a Packet Uplink Ack/Nack message whose FAI=1 to the MS if it receives the last RLC data block. At the same time, the N3103 is started. If the network does not receive the Packet Control Ack/Nack message in a certain time, the N3103 is increased at the network side and the Packet Uplink Ack/Nack message is resent. When the N3103 overflows, the T3169 is started. When the T3169 expires, the current TBF is released abnormally. Value range: 25 (The default value is 3.) Setting and impact If the parameter value decreases, the tolerance of the network side to the uplink link abnormality decreases. As a result, the ratio of uplink TBF abnormal release increases.
Issue 03 (2007-11-05)
5-25
If the parameter value increases, the network side still assigns wireless resource to the MS when the network side cannot receive the correct Packet Control Ack/Nack message due to the MS fault. The system resource is wasted. In key types of the GPRS traffic measurement, the number of uplink TBF abnormal release caused by N3103 overflow in the uplink TBF setup and release performance measurement records some of the reasons of the uplink TBF abnormal release. Normally, the reasons are poor quality of G-Abis interface transmit link, poor quality of air interface, bad network design, and mobile fault. When all the problems are solved, you can reduce the number of uplink TBF abnormal releases due to the N3103 overflow by increase the threshold of the N3103. The network quality is improved. In a satellite cell, because the long and unstable transmit delay of the G-Abis interface is hard to improve, you can improve the network quality by increasing the threshold of the N3103. It is recommended that the threshold of the N3103 in the satellite cell is set to 5. N3105 Definition and format The parameter is used to set the maximum value of the N3105. When the downlink TBF is set up, the N3105 is started at the network side. When the network side sets the RRBP domain in the downlink RLC data block, it resets the N3105 if the network side receives the valid Packet Ack/Nack message from the MS in the RRBP domain corresponding uplink RLC wireless block. Otherwise, the N3105 is increased and the downlink data block to set the RRBP is resent. When the N3105 overflows, the T3195 is started. When the T3195 expires, the current TBF is released abnormally. Value range: 310 (The default value is 10.) Setting and impact If the parameter value decreases, the tolerance of the network side to the downlink link abnormality decreases. The ratio of downlink TBF abnormal release increases. If the parameter value increases, the network side still assigns wireless resource to the MS when the network side cannot receive the correct Packet Control Ack/Nack message due to the MS fault. The system resource is wasted. In key types of the GPRS traffic measurement, the number of the downlink TBF abnormal release caused by the N3105 overflow in the downlink TBF setup and release performance measurement records some reasons of the downlink TBF abnormal release. Normally, the reasons are poor quality of G-Abis interface transmit link, poor quality of air interface, bad network design, and mobile fault. When all the problems are solved, you can reduce the number of downlink TBF abnormal releases due to the N3105 overflow by increase the threshold of the N3105. The network quality is improved. The current default value of the N3105 is set to the maximum value. Do not change the value.
5.3.10 Configuring Cell PRIVATEOPTPARA Data

Function
This command is used to set the following parameters: Priority of the packet domain
5-26
Issue 03 (2007-11-05)
Delayed release time of the uplink nonextended TBF Inactive continuous time of the uplink extended TBF Delayed release time of the downlink TBF The G3PCUV300R005C05 opens some network optimization parameters to subscribers and refines the function of these parameters to the cell lever. Then subscribers can adjust the configuration based on the actual cell situation such as service type, air interface coverage, and service requirements. The PSPrecedence, UpTbfRelDelay, UpExtTbfInActDelay, and DnTbfRelDelay are parameters used in the optimization strategy of Huawei PCU. They differ from that of the competitors in name and realization method. Thus, they are arranged in the private optimized parameters table.
Related Commands
Table 5-5 lists the cell PRIVATEOPTPARA data configuration. Table 5-5 Cell PRIVATEOPTPARA data configuration Command pcu add privateoptpara pcu del privateoptpara pcu set privateoptpara pcu show privateoptpara Function Adding the configuration information of the cell non-standard network parameter Deleting the configuration information of the cell non-standard network parameter Modifying the configuration information of the cell non-standard network parameter Querying the configuration information of the cell non-standard network parameter

LCNo Logic cell number Value range: 065534 PSPrecedence Definition and format The parameter is used to set the channel priority of the packet domain. Value range: 02 (The default value is 0.) Table 5-6 lists the explanation of the value.
Issue 03 (2007-11-05)
5-27
Table 5-6 Explanation of PSPrecedence values PS Precedence 0 Meaning Indicates that the voice service has the priority. The parameter is equal to the dynamic channel property in versions earlier than G3PCUV300R005C05. When the PCU applies the dynamic channel to the BSC due to busy GPRS service, the BSC rejects the PCU request if the dynamic channel is used by the voice service. When the BSC applies the dynamic channel to the PCU due to busy voice service, the PCU accepts the BSC request and transfers the occupied dynamic channel to the TCH. When the PCU applies the dynamic channel to the BSC due to busy GPRS service, the BSC accepts the PCU request if the dynamic channel is used by the voice service. The dynamic channel is released and transferred to the data service channel. When the BSC applies the dynamic channel to the PCU due to busy voice service, the PCU accepts the BSC request and transfers the occupied dynamic non-control channel to the TCH. Indicates that the data service has the priority. When the PCU applies the dynamic channel to the BSC due to busy GPRS service, the BSC accepts the PCU request if the dynamic channel is used by the voice service. The dynamic channel is released and transferred to the data service channel. When the BSC applies the dynamic channel to the PCU due to busy voice service, the PCU rejects the BSC request if the dynamic channel is used by the GPRS service.
Setting and impact Keep the default value in the normal cell is recommended. Do not change the value. According to the description of parameter meaning, the set of the data service priority (1 or 2) may preempt the dynamic channel used by the voice service so that the call is dropped. In addition, in the half speed cell, the BSC determines whether to apply for the half speed voice channel by comparing the used TCHs proportion and threshold. As a result, the data service channel is used for a long time if the data service has the priority, and the half-speed channel usage is high. For offices that require few for the data service, do not change the default value of the parameter. Use the dynamic channel as the TCH by default, and it does not preempt by the data service. For offices that require many for the data service such as high speed and low call drup rate, increase the number of fixed PDCHs by comparing the traffic measurement results and cell special requirement. Only when the channel resource is limited, cautiously set the cell data service priority. Based on the times of the BSC reclaiming dynamic PDCH of the PDCH resource performance measurement, determine whether the resource configurations of the cell GPRS and voice services are reasonable. If the BSC reclaims dynamic PDCH many times and reclaims loaded PDCHs few times, it is an indication that the cell has heavy voice service, but the GPRS service is not affected. Thus, set the priority of the cell dynamic channel to 1 or do not change the priority. If the BSC reclaims dynamic PDCH and loaded PDCHs many times, it is an indication that the cell has heavy voice service, and the GPRS service is affected. If the cell is a key
5-28
Issue 03 (2007-11-05)
cell, it is recommended that the priority of the cell dynamic channel is set to 2 and the voice channel to expand the cell capacity is increased. UpTbfRelDelay Definition and format The parameter is used to set the delayed release time of the uplink nonextended TBF. When the network sidereceives the last RLC data block (CountValue = 0), it sends a Packet Uplink Ack/Nack message whose FAI = 1 to the MS to inform the MS to release the uplink TBF. To delay the uplink TBF release and faciliate the downlink TBF set up in the unreleased uplink TBF, the network side delays the uplink TBF release, that is, delay the time to send the Packet Uplink Ack/Nack message whose FAI = 1. The uplink TBF, however, is released automatically after the downlink TBF is set up or when the delay exceeds the value set by the UpTbfRelDelay. Value range: 0300 ms (The default value is 120 ms.) When the parameter is set to 0, it is an indication that the function is disabled. Definition and format The default value is recommended. Do not change the value. If the parameter value increases, the network side forcibly requires the MS to maintain the uplink TBF when the MS countdown ends. If there is downlink data to be sent at the network side, the downlink TBF can directly send the Pactket Downlink Assignment message in the PACCH. The downlink TBF set up time decreases. If there is uplink data to be sent at the MS, however, because the PCU does not support the uplink TBF setup in the uplink TBF, in the TBF that does not support the uplink extension, the data is transmitted by setting up the TBF when the uplink TBF is released. The overall transmit performance is affected. If the parameter value decreases, the influence of the function decreases, and the possibility to set up the downlink TBF in the uplink TBF decreases. Because the network adopts the optimization function of advanced downlink setup, the probability of the downlink TBF setup in the release delayed uplink TBF decreases. The optimization effect of the parameter to the network performance decreases. UpExtTbfInActDelay Definition and format The parameter is used to set the inactive continuous time of the uplink extended TBF. The G3PCUV300R005C05 supports the uplink extended TBF, which also needs the support of the MS. When the network side receives the last uplink RLC data block of the MS that supports the uplink extended TBF (CountValue = 0), it does not release the uplink TBF. Instead, the network side sets the TBF to inactive period. In inactive period, if the MS has the uplink RLC data block to be sent, it can directly use the uplink TBF whose state changed to inactive, and the inactive TBF becomes an active TBF. When the inactive continuous time ends, the network side sends a Packet Uplink Ack/Nack message whose FAI = 1 to the MS if the MS does not have uplink RLC data block to be sent. The message is to inform the MS to release the uplink TBF. In addition, when the uplink TBF is in inactive state, the downlink TBF can still be set up through the uplink TBF. Value range: 05000 ms (The default value is 2000 ms.)
Issue 03 (2007-11-05)
5-29
When the parameter is set to 0, it is an indication that the function is disabled. The function can also be disabled by inactivate the function at the BSC side. Setting and impact If the parameter value increases, the inactive time of the uplink TBF increases. As a result, the limited TBF resource cannot be released, and the network resource is wasted. If the parameter value decreases, the data transmit requirement at the MS or network side may be missed. The optimization function fails. The uplink extended TBF can greatly improve the network KPI performance, especially for the persistent discontinuous-uplink transmit service, such as interactive transmit and Ping. The optimum value is slightly greater than the break time of two discontinuous uplinks transmit. The function, however, needs the support of the MS. Thus, the use of this function has limitations. If the network requires high performance test of the interactive service, such as Ping, use the MS that supports the uplink extended TBF to meet the requirement that is recommended. DnTbfRelDelay Definition and format The parameter is used to set the delayed release time of the downlink TBF. After the network side sends the last downlink RLC data block and confirms that all downlink data blocks are received, it does not inform the MS to terminate the downlink TBF, that is to set FBI = 1. Instead, the network side forcibly sets the last data block as unreceived and resends the last data block which is marked by the RRBP to prevent the downlink TBF from release. During the downlink delayed release, the downlink RLC data block which is unpacked can directly be sent in the delayed release downlink TBF if the network side upper layer requires the sending of the downlink data. At the same time, the downlink TBF turns to transmit state from the delayed release state. In addition, when maintaining the downlink TBF to be unreleased, the MS must interact with the network side through responding to the Packet Downlink Ack/Nack message in the data block that corresponding to the RRBP. When the MS is required to send the uplink data, it immediately sends the uplink request to the network side by attaching the Channel Request Description in the Packet Downlink Ack/Nack message. Value range: 05000ms (The default value is 2400 ms.) When the parameter is set to 0, it is an indication that the function is disabled. Setting and impact If the parameter value increases, the wireless resource is wasted, the access performance of other MSs is affected, and the useless signaling occupation of the channel bandwidth increases. If the parameter value decreases, the original downlink TBF is released quickly. The following downlink data transmit cannot use the original downlink TBF, but it must be transmitted through new TBF. When the following MS is required to send the uplink data, it cannot transmit the data in the original downlink TBF. As a result, the TBF setup time and setup success rate are greatly affected. In addition, in the cell where the transmit delay is long, such as a satellite cell, because the delay of the G-Abis interface increases and the transmission is unstable, the downlink delayed release time must be increased to maintain the downlink TBF to be unreleased. Normally, it is recommended that the parameter in the satellite cell is set to 4000 ms.
5-30
Issue 03 (2007-11-05)
5.3.11 Optimized Configuration Data of the GPRS Cell

Function
This command is used to add all the configurations in a cell, including the data configurations in attr table, cell table, gprs table, cspara table, pwpar table, relatedinfo table, pdchpara table, egprspara table, standardopt table, and privateopt table. Other parameters in the cell are configured with default values. If there is any special requirement, the subscriber needs to configure by running configuration commands corresponded to each table.
Related Command
Table 5-7 lists the commands for optimized configuration of the GPRS cell. Table 5-7 Optimized configuration commands of the GPRS Command pcu add allofonecell pcu copy allofonecell pcu del allofonecell Function Adding all the data configuration of the GPRS cell Copying all the data configuration of the GPRS cell Deleting all the data configuration of the GPRS cell

LCNo Logical cell number Value range: 065534 CGI Cell global unique identification Length: 13 or 14 BSC The BSC number in a PCU Value range: 0254 SiteNo Site number Value range: 065534 RA Route area number (hexadecimal system) Value range: 00FF NMO
Issue 03 (2007-11-05)
5-31
Network operation mode 0: mode I 1: mode II 2: mode III SupportCS34 Whether the CS34 code mode is supported or not "yes"or"no" NCO Network control mode Types: "nc0", "nc1", "nc2" PrimPbRPPU Handle with the RPPU board number on active Pb interface of the cell Value range: 05, 1015 SecPbRPPU Handle with the RPPU board number on standby Pb interface of the cell (must not overlap with PrimPbRPPU) Value range: 05, 1015, 255 PrimGbRPPU Handle with the RPPU board number on active Gb interface of the cell Value range: 05, 1015 SecGbRPPU Handle with the RPPU board number on standby Gb interface of the cell Value range: 05, 1015 NSEI Identification of the NSE Value range: 065534 BVCI Identification of the BVC Value range: 265534 BSSID Identification of the BSS Value range: 0254 LCName Logical cell name, a string of up to 31 characters, case insensitive
5-32
Issue 03 (2007-11-05)
5.4 Example for GPRS Cell Data Configuration

Example
The following example is based on Section 3.4 Example for System Hardware Data Configuration and 4.4 Example for Pb Interface Data Configuration. This is an example for GPRS cell data configuration. It is successive to the content in the previous chapters; for example, this configuration is based on the configured data described in those chapters. Each BSC in the GPRS cell has 9 BTSs, and the BTS00~BTS08 belong to BSC0 while the BTS10~BTS18 belong to BSC1. Each BTS configured with 3 cells. The satellite transmission is adopted as the trunk between the BSC1 and BTS10~BTS18. The cell of BTS00 is named as HW000, HW001 and HW002, and the other cells are named with the same method. The CGI for the cells in BSC0 is from 4600081879c20 to 4600081879c3c, and the CGI for the cells in BSC1 is from 4600081889c40 to 4600081889c5c. The CGI and the cell are of one to one correspondences according to the order of CGI and cell names. Apply the network operation mode I. Uniformly configure the timeout value of the T3168 timer as 1000ms and that of the T3192 timer as 500ms. Make such configuration that MS is converted to the DRX mode 4s after it enters the packet idle mode from the packet transfer mode. Set the access burst type used by MS in the PRACH, PTCCH/U and packet control acknowledgement message as 8bit. Set the control acknowledgement message type as such: MS uses the RLC/MAC control block in the control acknowledgement message. Configure the maximum value of the MS countdown as 4. The configuration should also meet this requirement: N3102 will decrease by 3 when the time length of the MS T3192 timer expires and increase by 3 when the packet uplink message is received. Set the maximum value of N3102 as 12. And the enhanced GPRS service is not supported. Configure the CS of all the cells as follows. The CS should be dynamically adjusted based on the channel transmission quality. Both the uplink and the downlink use CS-2 by default. When the TBF is in CS-1, if the TBF retransmission rate is less than 5, the TBF will be converted from CS-1 to CS-2. When the TBF is in CS-2, if the TBF retransmission rate is more than 10, the TBF will be converted from CS-2 to CS-1. Under other situations, if the TBF retransmission rate is less than 7, the TBF will be converted from the CS at a lower transmission rate to CS at a higher transmission rate. If the TBF retransmission rate is more than 20, the TBF will be converted from the CS at a higher transmission rate to CS at a lower transmission rate. All the cells distribute the radio resource based on optimization utilization of radio resource. Configure the measurement report interpolation as follows. The minimum number of measurement reports that should be received by PCU before PCU allows interpolation of the measurement report is 3. And only when the number gap is less than or equal to 5, can the measurement report be interpolated. If the time interval between the previous report and this report exceeds 80, the measurement report received previously will be discarded. Set the number of measurement reports used for power control as 5. Set the upper limit of the difference between the valid value and average value of the BTS RX signal power as 6 and the lower limit of it as 6. Set the upper limit of the difference between the valid value and average value used in the bit error ratio filter as 5. Set the lower tolerance of the Ber filter as 5. Set the Alpha parameter of all cells as 1.0. Set the GAMMA parameter as 2. Set signal strength filter period for power control in packet idle mode as 2 and that in the packet transfer mode as 2. Set power reduction value used by the BTS on PBCCH blocks as -2dB. The mobile station shall measure the received power level on the BCCH for the purpose of the
Issue 03 (2007-11-05)
5-33
uplink power control, and the entire cell does not broadcast PSI4. Set the interfering signal strength filter constant for power control as 2. For all cells, network control mode 1 is applied; for example, MS should send measurement reports to the network and perform automatic cell reselection. The CCCH in the cell does not support the parameter SPLIT_PG_CYCLE. And the packet access of priority 1-4 is allowed. When the circuit switched service is busy, each uplink PDCH in the cell supports a maximum of 7 TBFs and each downlink PDCH supports a maximum of 8 TBFs. When the circuit is idle, each uplink PDCH in the cell supports a maximum of 4 TBFs and each downlink PDCH supports a maximum of 4 TBFs. Configure the EGPRS parameter of all the cells as follows. Set the LQC mode as LA. Set the BepPeriod as 10. All the cells do not support 11 bit EGPRS channel request. The MCS type should be dynamically adjusted based on the channel transmission quality. The uplink uses MCS-2 and the downlink uses MCS-6 by default.
Configuration
To configure the GPRS cell data, do as follows: Step 1 Configure the ATTR attribute of the cell. pcu add attr <LCNo> <CGI> <BSC> <SiteNo> <RA> <SGPRS> <PrimRPPU> <SecRPPU> <ActiveState> <InUse> <LCName>
pcu add attr 1 4600081879c4b 0 0 0 yes 0 2 deactive true HW000 pcu add attr 2 4600081879c4c 0 0 0 yes 0 2 deactive true HW001 pcu add attr 3 4600081879c4d 0 0 0 yes 0 2 deactive true HW002 pcu add attr 4 4600081879c4e 0 1 0 yes 0 2 deactive true HW010 ... pcu add attr 28 4600081879d00 1 0 0 yes 1 2 deactive true HW100 pcu add attr 29 4600081879d01 1 0 0 yes 1 2 deactive true HW101 ... pcu add attr 53 4600081889cbb 1 8 0 yes 1 2 deactive true HW181 pcu add attr 54 4600081889cc3 1 8 0 yes 1 2 deactive true HW182
If the ActiveState parameter is configured as Active, the PCU will give prompt on that configuration during data loading. However, the relevant data can still be loaded into the system smoothly. No matter whether this parameter is configured as Active or Deactive, the command mt gcell active should be used to activate cells configured in each RPPU board upon completion of the system configuration file loading.
Step 2 Configure the GPRS attribute of the cell. pcu add gprs <LCNo> <NMO> <T3168> <T3192> <DRXTimerMax> <AccBurst> <CtrlAckType> <BsCvMax> <PanDec> <PanInc> <PanMax> <EGPRSSupport>
pcu add gprs 1 1 1000ms 500ms 4s 8bit 0 10 2 4 12 no pcu add gprs 2 1 1000ms 500ms 4s 8bit 0 10 2 4 12 no ... pcu add gprs 53 1 1000ms 500ms 4s 8bit 0 10 2 4 12 no pcu add gprs 54 1 1000ms 500ms 4s 8bit 0 10 2 4 12 no
Step 3 Configure the CSPARA attribute of the cell.
5-34
Issue 03 (2007-11-05)
pcu add cspara
<LCNo> <SupportCS34> [<UpFixCs> <UpDefaultCs> <UpThdCs1Cs2> <UpThdCs2Cs1> <UpThdCs2Cs3> <UpThdCs3Cs2> <UpThdCs3Cs4> <UpThdCs4Cs3> <DnFixCs> <DnDefaultCs> <DnThdCs1Cs2> <DnThdCs2Cs1> <DnThdCs2Cs3> <DnThdCs3Cs2> <DnThdCs3Cs4> <DnThdCs4Cs3> <ResAssStrType>]
pcu add cspara 1 yes unfixed cs2 5 10 10 20 10 20 unfixed cs2 5 10 10 20 10 20 MaxBandWidth pcu add cspara 2 yes unfixed cs2 5 10 10 20 10 20 unfixed cs2 5 10 10 20 10 20 MaxBandWidth ... pcu add cspara 26 yes unfixed cs2 5 10 10 20 10 20 unfixed cs2 5 10 10 20 10 20 MaxBandWidth pcu add cspara 27 yes unfixed cs2 5 10 10 20 10 20 unfixed cs2 5 10 10 20 10 20 MaxBandWidth pcu add cspara 28 yes unfixed cs2 5 10 10 20 10 20 unfixed cs2 5 10 10 20 10 20 MaxBandWidth pcu add cspara 29 yes unfixed cs2 5 10 10 20 10 20 unfixed cs2 5 10 10 20 10 20 MaxBandWidth ... pcu add cspara 53 yes unfixed cs2 5 10 10 20 10 20 unfixed cs2 5 10 10 20 10 20 MaxBandWidth pcu add cspara 54 yes unfixed cs2 5 10 10 20 10 20 unfixed cs2 5 10 10 20 10 20 MaxBandWidth
Only with the relevant License, can the subscriber have the authority for using CS-3 and CS-4.
Step 4 Configure the power processing parameter. pcu add pwpar <LCNo> <ALPHA> <GAMMA> <TAVGW> <TAVGT> <PB> <PCMeasChan> <MeasChAvail> <NAVGI>
pcu add pwpar 1 1.0 14 10 10 -2db bcch no 2 pcu add pwpar 2 1.0 14 10 10 -2db bcch no 2 ... pcu add pwpar 26 1.0 14 10 10 -2db bcch no 2 pcu add pwpar 27 1.0 14 10 10 -2db bcch no 2 pcu add pwpar 28 1.0 14 10 10 -2db bcch no 2 pcu add pwpar 29 1.0 14 10 10 -2db bcch no 2 ... pcu add pwpar 53 1.0 14 10 10 2db bcch no 2 pcu add pwpar 54 1.0 14 10 10 2db bcch no 2
Step 5 Configuring parameter information related to the system information of the cell. pcu add relatedinfo <LCNo> <NCO> <BSIC> <SpgcCCCHSup> <PriAccThrr> <RAColor>
pcu add relatedinfo 1 nc0 0 no 6 0 pcu add relatedinfo 2 nc0 0 no 6 0 ... pcu add relatedinfo 26 nc0 0 no 6 0 pcu add relatedinfo 27 nc0 0 no 6 0 pcu add relatedinfo 28 nc0 0 no 6 1 pcu add relatedinfo 29 nc0 0 no 6 1 ... pcu add relatedinfo 53 nc0 0 no 6 1 pcu add relatedinfo 54 nc0 0 no 6 1
Step 6 Configure the dynamic PDCH information.
Issue 03 (2007-11-05)
5-35
pcu add pdchpara
<LCNo> <MaxUlHighLd> <MaxDlHighLd> <MaxUlLowLd> <MaxDlLowLd>
pcu add pdchpara 1 7 8 4 4 pcu add pdchpara 2 7 8 4 4 ... pcu add pdchpara 26 7 8 4 4 pcu add pdchpara 27 7 8 4 4 pcu add pdchpara 28 7 8 4 4 pcu add pdchpara 29 7 8 4 4 ... pcu add pdchpara 53 7 8 4 4 pcu add pdchpara 54 7 8 4 4
Step 7 Configure the SATTRANS data of the cell pcu add sattrans
pcu add sattrans 1 no pcu add sattrans 2 no ... pcu add sattrans 26 no pcu add sattrans 27 no pcu add sattrans 28 yes pcu add sattrans 29 yes ... pcu add sattrans 53 yes pcu add sattrans 54 yes
<LCNo> <SuprtSatTrans>
Step 8 Configure the EGPRS data of the cell pcu add egprs <LCNo> <LQCMode> <BepPeriod> <Egprs11BitChanReq> <UpFixMcs> <UpDefaultMcs> <DnFixMcs> <DnDefaultMcs>
pcu add egprspara 1 la 10 no unfixed mcs2 unfixed mcs6 pcu add egprspara 2 la 10 no unfixed mcs2 unfixed mcs6 ... pcu add egprspara 26 la 10 no unfixed mcs2 unfixed mcs6 pcu add egprspara 27 la 10 no unfixed mcs2 unfixed mcs6 pcu add egprspara 28 la 10 no unfixed mcs2 unfixed mcs6 pcu add egprspara 29 la 10 no unfixed mcs2 unfixed mcs6 ... pcu add egprspara 53 la 10 no unfixed mcs2 unfixed mcs6 pcu add egprspara 54 la 10 no unfixed mcs2 unfixed mcs6
Step 9 Configure the STANDARDOPTPARA data of the cell pcu add standardoptpara <LCNo> <N3101> <N3103> <N3105>
pcu add standardoptpara 1 20 3 10 pcu add standardoptpara 2 20 3 10 ... pcu add standardoptpara 26 20 3 10 pcu add standardoptpara 27 20 3 10 pcu add standardoptpara 28 20 3 10 pcu add standardoptpara 29 20 3 10 ... pcu add standardoptpara 53 20 3 10 pcu add standardoptpara 54 20 3 10
5-36
Issue 03 (2007-11-05)
Step 10 Configure the PRIVATEOPTPARA data of the cell pcu add privateoptpara <LCNo> <PSPrecedence> <UpTbfRelDelay> <UpExtTbfInActDelay> <DnTbfRelDelay>
pcu add privateoptpara 1 0 120 2000 5000 pcu add privateoptpara 2 0 120 2000 5000 ... pcu add privateoptpara 26 0 120 2000 5000 pcu add privateoptpara 27 0 120 2000 5000 pcu add privateoptpara 28 0 120 2000 5000 pcu add privateoptpara 29 0 120 2000 5000 ... pcu add privateoptpara 53 0 120 2000 5000 pcu add privateoptpara 54 0 120 2000 5000
----End Optimized configuration of the data of the GPRS cell is as follows: pcu add allofonecell <LCNo> <CGI> <BSC> <SiteNo> <RA> <NMO> <SupportCS34> <NCO> <PrimPbRPPU><SecPbRPPU><PrimGbRPPU><SecGbRPPU ><NSEI> <BVCI> <BSSID> <LCName>
pcu add allofonecell 1 4600081879c20 0 0 0 1 yes nc0 0 2 15 15 100 10 0 HW000 pcu add allofonecell 2 4600081879c21 0 0 0 1 yes nc0 0 2 15 15 100 11 0 HW001 pcu add allofonecell 3 4600081879c22 0 0 0 1 yes nc0 0 2 15 15 100 11 0 HW002 pcu add allofonecell 4 4600081879c23 0 0 0 1 yes nc0 0 2 15 15 100 11 0 HW003 ... pcu add allofonecell 53 4600081889c5b 0 0 0 1 yes nc0 0 2 15 15 100 100 0 HW181 pcu add allofonecell 54 4600081889c5c 0 0 0 1 yes nc0 0 2 15 15 100 101 0 HW182
Configuration Check
Please use the command mt gcell active to activate all the cells prior to checking the GPRS cell data configuration.
Upon completion the GPRS cell data configuration, please check the cell configuration status to ensure that no parameter is missed. The GPRS cell status and the PDCH status should also be checked. If the configuration is complete and the status of GPRS cell and PDCH is normal, the GPRS cell configuration can be considered to be successful. To check the configuration of the cell that is finished by using the optimized configuration commands, do as follows: Step 1 Check the completeness of the configured information. Use the command pcu check cellconfig all to check the completeness of the configured information of all cells. pcu (supervisor)#pcu check cell all
Issue 03 (2007-11-05)
5-37
Checking the list of the logic cell number: 1 ... 45 46 47 48 49 50 51 52 53 54 2 3 4 5 6 7 8 9 10
The following lists names of Tables not configured. (If PBCCH is configured for the cell, please refer to the left data list. Otherwise, please refer to the right.) The check result related to logic cell 1 is as follows: PBCCH configured Configuration incomplete (the following Tables are lacking) *Neighbour (Optional) *ExtMsrPar (Optional) *NwCtrlMsrPar (Optional) ... ... PBCCH not configured Configuration complete
In this example, PBCCH is not configured. Therefore, if "Configuration complete" is displayed for the data list "PBCCH not configured" in the check result of all configured cells, it can be considered that all cells are completely configured. The pcu check cellconfig command can check the cell table in PCU6000 35C05 version. If you run the command when the Gb interface is not configured, a prompt about there is a lack of the cell table can display.
Step 2 Check the GPRS cell status.

Ensure that the data at the Pb interface and the Gb interface should be normally configured and both BSC and SGSN should run normally before checking the GPRS cell status.
Use the command mt gcell show state {<BoardNo> all} | <LCNo> | <LCName> to check the completeness of the configured information in all cells. In this example, please check the status of all the cells configured in RPPU board 0~2. The following description is based on the configuration of cells in RPPU 0. pcu(supervisor)#mt gcell show state 0 all The operation is successful. Altogether 27 cells are processed. RPPU: 0 Cell: 1 Operation state: enabled Availability state: no exception BSC management state: unblocked Cause of BSC being blocked: unknown
5-38
Issue 03 (2007-11-05)
Management state of maintenance: unblocked Management state of Gb: unblocked ...
In this example, you need to check the status of all the cells configured on RPPU 0 to RPPU 2. The previous example describes only the cells configured on RPPU 0. If the number of processed cells is equal to that of the configured cells and if all parameters of each cell are the same as the above description, the cell status can be considered as normal.
Step 3 Checking the PDCH status. Use the command mt pdch show state {<LCNo>|<LCName>} {<PdchNo>|all} to check the completeness of the configured information of all PDCHs. In this example, please check the status of PDCHs in all the 54 cells. The following description is based on the status check of PDCHs in cell 1. pcu(supervisor)#mt pdch show state 1 all The operation is successful. 3 PDCH(s) processed Cell: 1004 PDCHNo: 0 Operation state: disabled Availability state: no exception BSC management state: unblocked Cause of BSC being blocked: unknown Management state of maintenance: unblocked The number of PCICs connected: 1 The number of available PCICs: 1 The state of PCICs connected: Is not used in channels. Cell: 1004 PDCHNo: 1 Operation state: disabled Availability state: not initialized BSC management state: blocked Cause of BSC being blocked: unknown Management state of maintenance: unblocked The number of PCICs connected: 0
Issue 03 (2007-11-05)
5-39
In this example, you need to check the status of the PDCHs on all the 54 cells. The previous example describes only the status of the PDCH in cell 1004. The PDCH of the cell is considered to be normal when it is in either status above mentioned. For the PDCH fixedly configured, the status is like that of PDCH0. For the PDCH dynamically configured, the status is like that of PDCH 1. The fixed or dynamic PDCH configuration is completed by BSC. The quantity of PDCH each cell configured depends on the actual condition of the cell, and it is configured in BSC.
5-40
Issue 03 (2007-11-05)
6 Gb Interface Data Configuration
6
Title
Gb Interface Data Configuration
About This Chapter

The following table lists the contents of this chapter. Description This section describes the connection modes of the Gb interface This section describes the general configuration sequence for the Gb interface data configuration. This section describes the external input data for the Gb interface data configuration. This section describes the Gb interface data configuration. This section describes the example for Gb interface data configuration.
6.1 Connection Modes of the Gb Interface 6.2 General Configuration Sequence 6.3 External Input Data 6.4 Gb Interface Data Configuration 6.5 Example for Gb Interface Data Configuration
Issue 03 (2007-11-05)
6-1
Gb is the standard interface between a PCU and an SGSN. Its protocol stack is responsible for providing the upper layer subscriber with data path and signaling path. Figure 6-1 shows the structure of the Gb interface protocol. Figure 6-1 Structure of Gb protocol.
At the PCU, the Gb interface related functions at the FR, NS and BSSGP layer are processed. The physical link at the Gb interface can be of E1, V.35 or high-speed serial port, IP-based network, etc. At present, what Huawei provides is E1 link and IP-based network link. To fully utilize the load sharing and backup functions provided by the software and to make good use of the link,, choose different configuration modes by considering the real physical link (E1 link or IP-based network link) that the Gb interface uses when configuring data for the Gb interface.
6-2
Issue 03 (2007-11-05)
6.1 Connection Modes of the Gb Interface

6.1.1 Gb Over FR
If the number of E1s connecting PCU with a specific SGSN is more than 1 and if the number of RPPU boards configured for Gb interface at PCU is more than 1 too, the E1 trunk cables should be evenly distributed to the RPPU boards. If the number of E1s connecting an RPPU board configured for Gb interface at PCU with an SGSN is more than 1 and if the number of L2PU boards inserted into the RPPU board at this Gb interface is more than 1 too, the E1 trunk cables should be evenly distributed to the L2PU boards. If the PCU and SGSN are directly connected in the point-to-point manner, please bind as many timeslots as possible at E1 together to form one bearer channel (BC). If PCU and SGSN were connected via the switching equipment, it would be better to configure each timeslot as one BC. (If the switching equipment can ensure that no slide happens during switching between timeslots, you may bind as many timeslots as possible together to form one BC). The NS-VCs configured at one BC should be few. The number of them should be based on the number of timeslots occupied by the BC. The following inequality is recommended: 10 kbit/s (the number of timeslots occupied by the BC 64 kbit/s) / the number of NS-VCs configured at the BC 100 kbit/s. One NS-VC group is corresponding to one cell group and they are identified by the NSEI. One PCU can be connected with multiple BSCs. The cells corresponding to one BSC can be form one cell group. The NS-VC can be allocated to each cell group based on the traffic of the cell group. And the NS-VCs to each cell groups form one NS-VC group. The cell group and the corresponding NS-VC group are identified by the same NSEI. Furthermore, Huawei sets up one SIG BVC (signaling BVC) for each cell group to manage the group of cells. The NS-VCs of one group should be evenly distributed to the RPPU board, L2PU board, E1 and BC at the Gb interface in the system.
6.1.2 Gb Over IP
In the Gb Over IP connection mode, the communication at the Gb interface does not use L2PU. Therefore, the L2PU needs not to be configured when the load sharing and backup are taken into consideration. If the number of RPPU boards at the Gb interface connecting the PCU6000 to the SGSN is more than 1, equally distribute the NS-VCs of the Gb Over IP to different RPPU boards. One NS-VC group is corresponding to one cell group and they are identified by the NSEI. One PCU can be connected with multiple BSCs. The cells corresponding to one BSC can form one cell group. The NS-VC can be allocated to each cell group based on the traffic of the cell group. And the NS-VCs to each cell groups form one NS-VC group. The cell group and the corresponding NS-VC group are identified by the same NSEI. Furthermore, Huawei sets up one SIG BVC (signaling BVC) for each cell group to manage the group of cells. The NS-VCs of one group should be evenly distributed to the RPPU board at the Gb interface in the system.
Issue 03 (2007-11-05)
6-3

6.2.1 Configuring the Gb Interface in Gb Over FR
The basic configuration sequence of the Gb interface is a kind of configuration from the bottom layer to the upper layer. Step 1 Configure the Gb interface E1 data. Step 2 Configure the BC data. Step 3 Configure the public parameter at the NS layer. Step 4 Configure the NS-VC and PVC data. Step 5 Configure the position of the NSE signaling entity. Step 6 Configure the Gb interface cell. Step 7 Configure the BSSGP data ----End
6.2.2 Configuring the Gb Interface in Gb Over IP

The basic configuration sequence of the Gb interface is a kind of configuration from the bottom layer to the upper layer. Step 1 Configure the IP address for the RPPU at the Gb interface. Step 2 Configure the route for the RPPU at the Gb interface. Step 3 Configure the NSVL data. Step 4 Configure the BindNSVL data. Step 5 Configure the position of the NSE signaling entity. Step 6 Configure the Gb interface cell. Step 7 Configure the BSSGP data ----End

6.3.1 External Input Data in Gb Over FR
The external input data are as follows: The number of RPPU boards configured for the Gb interface at PCU. The number of RPPU boards and L2PU boards in PCU that are connected with a specific SGSN. PCU is connected with SGSN directly in the point-to-point manner or via an intermediate network.
6-4
Issue 03 (2007-11-05)
The frame relay (FR) format of the Gb interface is time-slot-31-available or time-slot-30-available. FR code type and frame type of the Gb interface. The number of cells supported by PCU. The number of E1 links between PCU and SGSN. The number of BCs, the number of timeslots configured in the BCs and the number of subscribers planned by the service providers. The Cell ID (or CGI and RAC) of all the cells. NSEI. Tc, time interval of the MS flow control timer C. Th, least time interval between Bmax and R, which are triggered by the SGSN when the flow control message is received on the SGSN side.
6.3.2 External Input Data in Gb Over IP

The external input data are as follows: The number of RPPU boards configured for the Gb interface at PCU. The number of RPPU boards connecting PCU to SGSN. The PCU is connected to the SGSN through IP network or not. The number of cells supported by PCU. The IP address and UDP port that connect PCU and SGSN. The Cell ID (or CGI and RAC) of all the cells. NSEI. Tc, time interval of the MS flow control timer C. Th, least time interval between Bmax and R, which are triggered by the SGSN when the flow control message is received on the SGSN side.
6.4 Gb Interface Data Configuration

In Gb Over FR, refer to 6.2.1 "Configuring the Gb Interface in Gb Over FR" to configure the Gb interface. In Gb Over IP, refer to 6.2.2 "Configuring the Gb Interface in Gb Over IP " to configure the Gb interface.
6.4.1 Configuring Gb Interface E1 Data

This command is used to configure the E1 data on the Gb interface. In the data configuration, all the E1 port numbers, connection modes of the Gb interface, frame formats, frame types, and coding schemes are chosen
Related Command
Command e1t1 add Function Adding a piece of Gb interface E1 configuration information.
Issue 03 (2007-11-05)
6-5
Command e1t1 del e1t1 set e1t1 show
Function Deleting a piece of Gb interface E1 configuration information. Modifying a piece of Gb interface E1 configuration information. Querying a piece of Gb interface E1 configuration information.

BoardNo Slot number of the RPPU (Gb) board. Please configure this parameter based on the actual situation. For easily locating the board, it is recommended that the RPPU (Gb) board should be configured in slots 13~15 of the PCU processing frame and the configuration should be started from slot 15. PortNo It refers to the external physical port number. The L2PU is used. It ranges between 03. GbLinkMode The mode of links at Gb interface. At present, PCU only supports E1 link. FrFormat Frame format of FR. It has two options, such as PCM_30 and PCM_31. The option PCM_30 indicates that among the 32 timeslots of E1, timeslots 0 and 16 are unavailable for data transmission. The option PCM_31 indicates that among the 32 timeslots in E1, only timeslot 0 is unavailable for data transmission. The configuration of this parameter should be the same as that of SGSN. CodeClass Code type adopted at the Gb interface. It has two options, such as HDB3 and AMI. The configuration of this parameter should be the same as that of SGSN. FrameType Gb interface frame type. Please configure it as pcm_df or crc4_mf depending on the actual situation. The configuration of this parameter should be the same as that of SGSN. ClockMode It refers to the clock mode. It should be configured as Master or Slave based on the SGSN configuration. Generally, it is recommended that this parameter is configured as Master in SGSN and as Slave in PCU. SlaveClkSel Slave clock source. It is valid when the ClockMode is configured as Slave. It indicates the port number of the E1 port acting as the slave clock source at the plug-in board. The small pinch plate is the L2PU board. It ranges between 03.
6-6
Issue 03 (2007-11-05)
6.4.2 Configuring BC Information

The BC is the physical layer link on the Gb interface. This command is used to select the internal ports, the timeslots occupied by the BC, the identification types of the data link connection, and the frame relay protocols in frame relay mode.
Related Command
Command bc add bc del bc set bc show Function Adding a piece of BC configuration information. Deleting a piece of BC configuration information. Modifying a piece of BC configuration information. Querying a piece of BC configuration information.

BoardNo Slot number of the slot accommodating the RPPU (Gb) board. Please configure this parameter based on the actual situation. For easily locating the board, it is recommended that the RPPU (Gb) board should be configured in slots 13~15 of the PCU processing frame, and the configuration should be started from slot 15. LocalNo It refers to the internal logic port number. It ranges between 0~3. BCID It refers to the ID of BC. It ranges between 0~30. This parameter is unique for each E1. It is configured based on the actual mode of connection between PCU and SGSN. If PCU is directly connected with SGSN, for example, there is no intermediate network or other intermediate equipment between them. It is recommended that all available timeslots in one E1 should form one BC. If there is intermediate equipment between PCU and SGSN, it is recommended that each timeslot should be configured as one BC. TimeSlot Timeslots occupied by BC. This parameter should be configured based on the BC data configuration at SGSN. When configuring this parameter, please refer to the FrFormat parameter detailed in 6.4.1 Configuring Gb Interface E1 Data. If the FrFormat parameter is configured as PCM_30, timeslots 0 and 16 should not be configured. If the FrFormat parameter is configured as PCM_31, only timeslot 0 should not be configured. This parameter is a hexadecimal number of 4 bytes. If all timeslots except timeslot 0 are form one BC, the BC will be 11111111111111111111111111111110, for example, the parameter is configured as fffffffe. To cut the cost of the service providers, the Gb interface related charge is based on the number of subscribers (from which the Gb interface transmission rate can be obtained). If the current transmission rate is not satisfactory, please purchase License from Huawei in order to support the higher transmission rate.
Issue 03 (2007-11-05)
6-7
PortNo It refers to external physical port number. Use the L2PU board, the ports in the RPPU board are numbered 0~7 in the bottom-up manner. Port numbers 0~3 are corresponding to 0~1 of the LocalNo while port numbers 4~7 to 2~3 of the LocalNo. PortTS It refers to external port timeslot, which is a hexadecimal number of 4 bytes. Use the L2PU board, the number of internal port timeslots should be equal to the number of external port timeslots. Moreover, different BCs should not share the same timeslot of the same external port. DLCIType It refers to data Link Connection Identifier type. It ranges between 1~5. The configuration of this parameter at PCU should be identical with that at SGSN. It is recommended to configure this parameter as 1, which indicates that the FR address is of a binary group, in which 10 Mbit/s are valid. Mode It refers to the FR mode. This parameter should be configured based on SGSN. Generally, this parameter is configured as DTE at PCU. protocol It refers to the FR protocol. The configuration of this parameter should be identical with that of SGSN. The recommended configuration of it is q933. SubscriberN391 It refers to the DTE parameter. It ranges between 1~255. The recommended configuration of it is 6. SubscriberN392 It refers to the DTE parameter. It ranges between 1~10. The recommended configuration of it is 3. SubscriberN393 It refers to the DTE parameter. It ranges between 1~10. The recommended configuration of it is 4. SubscriberT391 It refers to the DTE parameter. It ranges between 5~30. The recommended configuration is 10. NetN392 It refers to the DCE parameter. If the parameter mode is configured as DTE, this parameter needs not to be configured. NetN393 It refers to the DCE parameter. If the parameter mode is configured as DTE, this parameter needs not to be configured. NetT392
6-8
Issue 03 (2007-11-05)
It refers to the DCE parameter. If the parameter mode is configured as DTE, this parameter needs not to be configured.
6.4.3 Modifying NS Information (Optional)

The parameters in this part are optional. The subscriber can skip over this part during Gb interface data configuration. And the system will automatically configure these parameters as their default values.
Related Command
Command ns set aliveretry ns set alivetimer ns set blockretry ns set blocktimer ns set nsenum ns set nsvcnum ns set resetretry ns set resettimer ns set testtimer ns set unblockretry ns show aliveretry ns show alivetimer ns show all ns show blockretry ns show blocktimer ns show nsenum ns show nsvcnum ns show resetretry ns show resettimer ns show testtimer ns show unblockretry Function Modifying the alive retry times. Modifying the duration of the alive timer. Modifying the block retry times. Modifying the duration of the block timer. Modifying the number of NSEIs of each board. Modifying the number of NSVCIs of each board. Modifying the reset retry times. Modifying the duration of the reset timer. Modifying the duration of the test timer. Modifying the unblock retry times. Querying the alive retry times. Querying the duration of the alive timer. Querying all NS data. Querying the block retry times. Querying the duration of the block timer. Querying the number of NSEIs of each board. Querying the number of NSVCIs of each board. Querying the reset retry times. Querying the duration of the reset timer. Querying the duration of the test timer. Querying the unblock retry times.

AliveRetry Value
Issue 03 (2007-11-05)
6-9
Alive retry times. It ranges between 5~15. Its default configuration is 10. AliveTimer Value It refers to the duration of the alive timer. It is fixedly configures as 3. BlockRetry Value Block retry times. It ranges between 1~6. Its default configuration is 3. BlockTimer Value It refers to the duration of the block timer. It ranges between 1~120. Its default configuration is 10. nsenum Value The number of NSEIs configured at each board. It ranges between 0~50. Its default configuration is 50. nsvcnum Value The number of NSVCIs configured at each board. It ranges between 0~1024. Its default configuration is 1024. ResetRetry Value It refers to the reset retry times. It is fixedly configures as 3. ResetTimer Value It refers to the duration of the reset timer. It ranges between 1~120. Its default configuration is 10. TestTimer Value It refers to the duration of the test timer. It ranges between 1~255. Its default configuration is 30. UnBlockRetry Value Unblock retry times. It ranges between 1~6. Its default configuration is 3.
6.4.4 Configuring NS-VC and PVC Information

NS-VC is the virtual link provided by NS layer for BSSGP layer, via which NS transmits the data of BSSGP layer. One NS-VC on the NS layer corresponds to one PVC on FR. Therefore in data configuration, the configuration of either NS-VC or PVC will do, for the data of the other will be automatically configured. NS-VC is solely identified by NS-VCI, which is unique in SGSN, so is PVC.NS-VC in SGSN corresponds to NS-VC in PCU one by one, and their IDs are the same. NS divides NS-VCs into different groups by their NSEIs. NS-VCs in the same group are in load sharing mode. Therefore, if when one NS-VC is invalid, NS can transmit data from the NS-VC via other NS-VCs in the same group. The office directions of NS-VCs in the same group are the same, for example, all NS-VCs in the same group of NS-VC (with the same NSEI) in SGSN are connected to (and only to) one certain BSS.
6-10
Issue 03 (2007-11-05)
Related Command
Command nsvc add nsvc del nsvc set nsvc show Function Adding a piece of NSVC configuration information. Deleting a piece of NSVC configuration information. Modifying a piece of NSVC configuration information. Querying a piece of NSVC configuration information.

NSVCI NSVC ID, which is obtained by numbering NSVCs under the same NSE. It ranges between 0~65534. The NS-VCs configured at one BC should be based on the number of timeslots occupied by the BC. The following inequality is recommended: 10 kbit/s (the number of timeslots occupied by the BC 64 kbit/s) / the number of NS-VCs configured at the BC 100 kbit/s. NSEI It refers to the NSE ID. NSEs are uniformly numbered under the same SGSN. Generally, one NSE is configured for each BSC and the connected PCU. The configuration of this parameter should be the same as that of SGSN. BoardNo It refers to the slot number of the slot accommodating the RPPU (Gb) board. Please configure this parameter based on the actual situation. For easily locating the board, it is recommended that the RPPU (Gb) board should be configured in slots 13~15 of the PCU processing frame. LocalNo It refers to the E1 port number. Each RPPU (Gb) provides four external E1/T1 ports through the E1TM inserted in its back, which are numbered 0~3 in the bottom-up manner. BCI It refers to the ID of BC. This parameter should be configured using the command bc add. DLCI It refers to the DLCI value. It is corresponding to the DLCIType configured using the command bc add. If the DLCIType is configured as 1, DLCI ranges between 16~1007.
6.4.5 Configuring IP Address for RPPU at the Gb Interface

Function
This topic describers configuring the IP address for RPPU at the Gb interface. This IP address is also the one when the SGSN set the peer NSVL, which is used to receive and transceiver following data.
Issue 03 (2007-11-05)
6-11
Related Command
Table 6-1 shows commands for configuring IP address for RPPU at the Gb interface. Table 6-1 Commands for configuring IP address for RPPU at the Gb interface Command gbip add ipaddress gbip del ipaddress gbip set ipaddress gbip show ipaddress Function Add a piece of RPPU IP address information Delete a piece of RPPU IP address information Modify a piece of RPPU IP address information Display a piece of RPPU IP address information

BoardNo It refers to the board number of RPPU at the Gb interface. Each RPPU board can only be configured with an IP address. IpAddress It refers to the IP address of RPPU. This character string must be decimal numerals. The IP address of RPPU and that of SGSN must keep the same to communicate the two parties.. IpMask It refers to the subnet mask, which is configured according to actual networking mode.
6.4.6 Configuring Route for RPPU at the Gb Interface

Function
This topic describers configuring route for RPPU at the Gb interface. The route directly influences the connection between RPPU and SGSN.
Related Command
Table 6-2 shows commands for configuring route for RPPU at the Gb interface. Table 6-2 Commands for configuring route for RPPU at the Gb interface Command gbip add route gbip del route gbip set route gbip show route Function Add a piece of RPPU route information Delete a piece of RPPU route information Modify a piece of RPPU route information Display a piece of RPPU route information
6-12
Issue 03 (2007-11-05)

BoardNo It refers to the board number of RPPU at the Gb interface. Each RPPU board can only be configured with ten pieces of route information. Destination It refers to the destination IP address. It can be the host IP address or the network IP address. Mask It refers to the subnet mask, which is configured according to actual networking mode. Gateway It refers to the Gateway IP address, which is configured according to actual networking mode.
6.4.7 Configuring the NSVL Information

Function
This topic describers configuring the NSVL. When configuring the local NSVL, you should specify the board number and port number of the NSVL. When configuring the peer NSVL, you should specify the IP address and port number of the NSVL on the SGSN side. When configuring the NSVL in Gb Over IP, you should configure NSVLs at the local end and peer end.
Related Command
Table 6-3 shows commands for configuring the NSVL. Table 6-3 Commands for configuring NSVL Command gbip add nsvl gbip del nsvl gbip set nsvl gbip show nsvl Function Add a piece of NSVL information Delete a piece of NSVL information Modify a piece of NSVL information Display a piece of NSVL information

NSVLI It refers to the NSVL identifier. One NSVLI only identifies one piece of NSVL information. The configured NSVLIs cannot be repeated. You can query all the configured NSVLIs by running the command gbip show nsvl all. And you can query all the configured NSVCIs by running the command nsvc show all. BoardNo It refers to the board number of RPPU at the Gb interface. Only when configuring the local NSVL should you specify the board number of RPPU. The IP address of the local
Issue 03 (2007-11-05)
6-13
NSVL is the same as that of the RPPU board that carries the NSVL. Each RPPU can be configured with a maximum of five local NSVLs. IP It refers to the IP address of the peer NSVL. Only when configuring the peer NSVL should you specify the peer IP address. Each PCU6000 processing frame can be configured with a maximum of ten pieces of peer NSVLs. This parameter must keep consistent with that on the SGSN side. UDPPort It refers to the port number of the UDP. Both the local and peer NSVLs need a port number. This parameter must keep consistent with that on the SGSN side.
6.4.8 Configuring the BindNSVL Information

Function
This topic describers configuring the BindNSVL information. Team NSVL to an NSEI through BindNSVL, and set the data weight and signaling weight for each NSVL. The binary NSVLs group (the local NSVL and peer NSVL) corresponding to one NSEI forms an NSVC in the Gb Over IP network. For example, if the number of local NSVLs under an NSEI is L and the number of peer NSVLs under an NSEI is R, the number of NSVCs under an NSEI should be L x R.
Related Command
Table 6-4 shows the commands for configuring the BindNSVL. Table 6-4 Commands for configuring the BindNSVL Command gbip add bindnsvl gbip del bindnsvl gbip set bindnsvl gbip show bindnsvl Function Add a piece of BindNSVL information Delete a piece of BindNSVL information Modify a piece of BindNSVL information Display a piece of BindNSVL information

NSEI It refers to the NSE signaling entity identity. NSEs are numbered under one SGSN. Generally one NSE is configured between the PCU and each BSC connecting to the PCU. This parameter must keep consistent with that on the SGSN side. NSVLI It refers to the NSVL identity. The NSVL must have been configured. DataWeight It refers to the data weight SigWeight It refers to the signaling weight.
6-14
Issue 03 (2007-11-05)
6.4.9 Configuring Location Information of NSE Signaling Entity

The NSE signaling entity manages a group of NS-VC. This command decides the active and standby board numbers of the NSE.
Related Command
Command nse add nse del nse set nse show Function Adding a piece of NSE signaling entity location information. Deleting a piece of NSE signaling entity location information. Modifying a piece of NSE signaling entity location information. Querying a piece of NSE signaling entity location information.

NSEI It refers to the NSE identification number. The NSEs share one number under one SGSN. Generally, one NSE is configured for each BSC that the PCU connects. This must be consistent with the configuration of the SGSN. At the same time, the routing area cannot cross NSEs, that is, one routing area cannot have more than one NSE. PrimeBoardNo Number of the active RPPU (Gb) board where NSE is located. SlaveBoardNo Number of the standby RPPU (Gb) board where NSE is located.
The board numbers of the active/standby RPPU (Gb) boards that accommodating NSE can be the same. If the two numbers are the same, NSE requires no backup.
6.4.10 Configuring Gb Interface Cell Information

Function
The cell information on the Gb interface can be finished by using the optimized configuration of the GPRS cell. If only one piece of cell information is required to be modified or added, you can perform this command to realize it. The operation is used to configure the cell information on the Gb interface. The operation chooses the NSE, and then the NSE chooses the NS-VC to make a communication.
Related Command
Command cell add Function Adding a piece of BSSGP layer signaling entity location information.
Issue 03 (2007-11-05)
6-15
Command cell del cell set cell show
Function Deleting a piece of BSSGP layer signaling entity location information. Modifying a piece of BSSGP layer signaling entity location information. Querying a piece of BSSGP layer signaling entity location information.

CellID It refers to the Cell ID, whose length is 15 or 16 bytes. The first 5 bytes (when CellID is composed of 15 bytes) or 6 bytes (when CellID is composed of 16 bytes) should be binary-coded decimal (BCD) and the following 10 bytes should be hexadecimal. The configuration of this parameter should be in consistency with that of CGI as well as that of the CellID at SGSN. NSEI NSE ID. This NSE parameter should have been configured using the commands nsvc add and nse add.
All the cells in one routing area must be configured with the same NSEI.
PrimaryBoardNo The board number of the original active RPPU (Gb) board in the cell. SlaveBoardNo The board number of the original standby RPPU (Gb) board in the cell. BVCI BVC ID, which is obtained by uniformly numbering BVCs under the same NSE. It ranges between 2~65534. BSSID BSS ID. This parameter is used to distinguish different BSSs. It should be in consistency with that of SGSN.
The NSEI maps the BSSID.
6.4.11 Configuring the BSSGP Data

Function
This operation is used to configure the parameters in the BSSGP layer.
Related Command
Table 6-5 shows the commands used to modify the BSSGP Data.
6-16
Issue 03 (2007-11-05)
Table 6-5 Commands used to modify the BSSGP data Command bssgp set BVCTf bssgp set MSTf bssgp set T1 bssgp set T2 bssgp set T3 bssgp set T4 bssgp set T5 bssgp set Tc bssgp set Th Function Change the duration of the BVC flow control timer (Timer F). Change the duration of the MS flow control timer (Timer F). Change the duration of the timer used to monitor the block (unblock) procedure. Change the duration of the timer used to monitor the reset procedure. Change the duration of the timer used to monitor the suspend procedure. Change the duration of the timer used to monitor the recovery procedure. Change the duration of the timer used to monitor the radio access capability update procedure. Change the duration of the flow control timer (Timer C). Change the minimum time intervals of the Bmax and R values generated and used by the SGSN after the MS flow control information is received. Query the duration of the BVC flow control timer (Timer F) Query the duration of the MS flow control timer (Timer F) Query the duration of the timer used to monitor the block (unblock) procedure. Query the duration of the timer used to monitor the reset procedure. Query the duration of the timer used to monitor the suspend procedure. Query the duration of the timer used to monitor the recovery procedure. Query the duration of the timer used to monitor the radio access capability update procedure. Query the duration of the flow control timer (Timer C). Query the minimum interval of the Bmax and R value that generated by the SGSN after the MS flow control information is received.
bssgp show BVCTf bssgp show MSTf bssgp show T1 bssgp show T2 bssgp show T3 bssgp show T4 bssgp show T5 bssgp show Tc bssgp show Th

Major parameters are as follows: BVCTf
Issue 03 (2007-11-05)
6-17
The duration of the BVC flow control timer, that is, the cell sends a flow control information every interval of duration of the timer. Value range: 10003000 Unit: ms Default: 1000. MSTf The duration of the MS flow control timer, that is, the MS sends a flow control information every interval of duration of the timer. Value range: 10003000 Unit: ms Default: 1000. T1 The duration of the timer used to monitor the block (unblock) procedure. Value range: 100030000 Unit: ms Default: 10000 T2 The duration of the timer used to monitor the reset procedure. Value range: 1000120000 Unit: ms Default: 10000 T3 The duration of the timer used to monitor the suspend procedure. Value range: 10010000 Unit: ms Default: 3000 T4 The duration of the timer used to monitor the recovery procedure. Value range: 10010000 Unit: ms Default: 3000 T5 The duration of the timer used to monitor the radio access capability update procedure. Value range: 100030000 Unit: ms Default: 10000 Tc The duration of the Timer C, that is, the MS in the BVC cell sends a flow control information every interval of duration of the timer.
6-18
Issue 03 (2007-11-05)
Value range: 100010000 Unit: ms Default: 5000 (It is recommended that "2000" is configured.) The smaller the parameter value, the higher the frequency of the flow control information sent by the MS in the BVC. Therefore, the SGSN can use the latest flow control parameter in real time and the transmission performance is improved. But if duration is too short, to send the flow control information, the MS in the BVC cell occupies a large number of bandwidths. The transmission performance worsens. If the value of the parameter is too great, the flow control mechanism on the Gb interface cannot adapt to the current situation in real time and the transmission performance falls. Some bandwidths can be saved. Th It refers to the minimum time intervals of the Bmax and R values generated and used by the SGSN after the MS flow control information is received. Value range: 5000600000 Unit: ms Default: 100000 (It is recommended that "5000" is configured.) The smaller the parameter value, the faster the SGSN can choose flow control parameters received in the flow control information and transmit according to the most suitable flow control parameters. The transmission performance is improved. If the value of this parameter is great, the lag phase is long. That is, after an MS sends the latest flow control parameters, the SGSN can use these new flow control parameters only after a long time. At this time, if the flow control parameters sent from the MS change, the SGSN controls the flow according to original flow control parameters. This is an apparent transmission bottleneck.
6.5 Example for Gb Interface Data Configuration

6.5.1 Example for Gb Interface Data Configuration in Gb Over FR
Example
For the Gb interface hardware configuration, please refer to section 3.4 "Example for System Hardware Data Configuration." Figure 6-2 shows the E1 connection. PCU is directly connected with SGSN through an E1 trunk. The frame format of the FR at the Gb interface is configured as PCM_31 and HDB3 code. The frame type is configured as PCM_DF. And the clock mode is configured as such: SGSN is master while PCU is slave.
The quantity of E1 configured in Gb depends on the quantity of PDCH configured in G-Abis. According to the 240 PDCH configured in the former examples, and suggest the data transmission rate in Um is about 11kbit/s and the transmission efficiency in Gb is 70%, so the E1 needs to be configured in Gb=240 x 11 kbit/s/(8 Mbit/s x 80%) 2.
Issue 03 (2007-11-05)
6-19
Figure 6-2 Gb interface E1 connection
L2PU
SGSN
RPPU15
The FR address of the Gb interface is of a binary group, in which 10 Mbit/s are valid. The mode of SGSN is set as DCE and that of PCU as DTE. For the protocol, Q933 is applied. Timeslots 1 and 2 are used for BSC0 while timeslots 3 and 4 for BSC1. The RAC of all the cells is 00. For other parameters, the default values are applied.
Configuration
To configure the data on the Gb interface, do as follows:
Step 1 Configure the Gb interface E1 information. e1t1 add <BoardNo> <PorNo> <GbLinkMode> <FrFormat> <CodeClass> <FrameType> <ClockMode> <SlaveClkSel>
e1t1 add 15 0 e1 pcm_31 hdb3 pcm_df slave 0 e1t1 add 15 1 e1 pcm_31 hdb3 pcm_df slave 0
As shown in Figure 6-2, these E1s lie in the L2PU board 0 at the RPPU board in slot 15. Other configurations are as described in the example.
Step 2 Configure BC information. bc add <BoardNo> <LocalNo> <BCID> <TimeSlot> <PortNo> <PortTS> <DLCIType> <Mode> <Protocol> [dte <SubscriberN391> <SubscriberN392> <SubscriberN393> <SubscriberT391>]
bc add 15 0 0 fffffffe 0 fffffffe 1 dte q933 dte 6 3 4 10 bc add 15 1 1 fffffffe 1 fffffffe 1 dte q933 dte 6 3 4 10
It is known that PCU is directly connected with SGSN. Therefore, all available timeslots in one E1 form one BC. The timeslot occupation depends on the License purchased by the service providers based on the number of subscribers. Here in this example, timeslots 1 to 31 in E1 0 are configured for transmission of data from BSC0 while timeslots 1 to 31 in E1 1 are configured for transmission of data from BSC1 (timeslot 0 is used for synchronization). Other parameters should be configured as described in the example.
Step 3 Configure NS-VC information.
6-20
Issue 03 (2007-11-05)
nsvc add
<NSVCI> <NSEI> <BoardNo> <LocalNo> <BCI> <DLCI>
nsvc add 0 0 15 0 0 137 nsvc add 1 0 15 0 0 138 nsvc add 18 0 15 0 0 155 nsvc add 19 0 15 0 0 156 nsvc add 20 1 15 1 1 157 nsvc add 39 1 15 1 1 176
According to the inequality 10 kbit/s (the number of timeslots occupied by BC 64 kbit/s)/the number of NS-VCs configured at BC 100 kbit/s. Both No.0 and No. 1 E1 occupy 31 timeslot to transmit data, so only one NSVC should be configured. Since PCU is connected with two BSCs, two NSEs should be configured.
Step 4 Configure the NSE information. nse add <NSEI> <PrimeBoardNo> <SlaveBoardNo>
nse add 0 15 15 nse add 1 15 15
Step 5 Configure the Gb interface cell information. cell add <CellID> <NSEI> <PrimaryBoardNo><SlaveBoardNo> <BVCI> <BSSID>
cell add 460008187009C20 0 15 15 20 0 cell add 460008187009C21 0 15 15 21 0 ... cell add 460008187009C3B 0 15 15 59 0 cell add 460008187009C3C 0 15 15 60 0 cell add 460008188019C40 1 15 15 61 1 ... cell add 460008188019C5C 1 15 15 62 1
CellID can be derived from CGI, since in 5.4 Example for GPRS Cell Data Configuration the CGIs have been configured from 4600081879c20 ~ 4600081879c3c and from 4600081889c40 ~ 4600081889c5c,the cellID for BSC0 should be configured from 460008187009c20 ~ 460008187009c3c and the ones for BSC1 should be configured from 460008188019c40-460008188019c5c. All the cells in the same RA must be configured with the same NSEI. 3NSEI must map the BSSID. The value range of the BVCI is 2-65534.
Configuration Check
Upon completion of the Gb interface data configuration, please check the status of BC and BVC. If the status of them is normal, the Gb interface configuration can be considered to be successful. To check configuration, do as follows:
Step 1 Check the BC status
Issue 03 (2007-11-05)
6-21
Use the command mt fr bc show statinfo <BoardNo> <LocalNo> <BCID> | all to check BC status. In this example, please check the status of BC at RPPU board 15. The following description is based on the status of BC set up for BSC0. pcu(supervisor)#mt fr bc show statinfo all The operation is successful. BC status: Link consistency check available; subscriber unblocked. The number of active PVCs: 2 ...
If BC is in the status "Link consistency check available; subscriber unblocked", the status is considered to be normal.
Step 2 Query the status of NS-VC.
Use the command mt nsvc show <NSEI><NSVCI> to query the status of NSVC. In this example, please query the status of all the NSVCs configured with the command nsvc add. The following description is based on the status query of NSVC 0. pcu (supervisor)#mt nsvc showstate 0 0 The operation is successful. NSVC status: Unblocked status.
If NSVC is in the Unblocked status, the status is considered to be normal.
Step 3 Query the Signal BVC status.
Use the command mt bvc signal showstate <NSEI> to check the status of the signaling BVC. In this example, please query the status of the NSEI signaling BVC configured using the command nsvc add. The following description is based on the signaling status query of BVC at NSEI 0. pcu(supervisor)#mt bvc signal show 0 The operation is successful. NSEI: 0 SIG BVC status: Normal.
Step 4 Query the PTP BVC status.
For this operation, correct information can be displayed only after the PCU data configuration is completed and the data are taken into internetworking with the successfully configured SGSN.
Use the command mt bvc ptp showstate <NSEI> {<BVCI>|all} to check the status of PTP BVC. In this example, please query the status of PTP BVC configured using the command cell add. The following description is based on the status query of BVCI 0 at NSEI 0. pcu (supervisor)#mt bvc ptp show 0 0 The operation is successful.
6-22
Issue 03 (2007-11-05)
NSEI: 0 BVCI: 0 PTP BVC status: Normal
6.5.2 Example for Gb Interface Data Configuration in Gb Over IP

Example
For the Gb interface hardware configuration, please refer to section3.4 "Example for System Hardware Data Configuration". Figure 6-3 shows the IP connection.
Figure 6-3 Gb interface IP connection
10/100BT
IP network
RPPU15
SGSN
The PCU (packet control unit) is connected to the SGSN through the IP-based network. All data frames at the Gb interface are transmitted through the UDP protocols. The IP address of NSVL on the SGSN side (the peer NSVL of the PCU) is 10.161.71.228, and the port number is 8666. The NSVL on the PCU side (the local NSVL of the PCU) is configured on the RPPU15. The IP address of RPPU15 is 129.12.220.100 and the port number is 8111. Other parameters use the defaulted value.
Configuration
Step 1 Configure the IP address for RPPU at the Gb interface gbip add ipaddress <BoardNo> <IpAddress> <IpMask>
gbip add ipaddress 15 129.12.220.100 255.255.0.0
Step 2 Configure route for RPPU at the Gb interface gbip add route <BoardNo> <Destination> <Mask> <Gateway>
gbip add route 15 10.161.71.228 255.255.255.255 129.12.1.188 gbip add route 15 10.161.71.0 255.255.255.0 10.161.71.1
Issue 03 (2007-11-05)
6-23
You can set the route between the PCU6000 and the SGSN, because they are directly connected to each other. That is, you can set the IP address of the SGSN as the destination IP address of the PCU6000, and the IP address of the PUC6000 the destination IP address of the SGSN.
Step 3 Configure the NSVL data gbip add nsvl <NSVLI> {local <BoardNo>}|{remote <IP>} <UDPPort>
gbip add nsvl 1501 local 15 8111 gbip add nsvl 1502 local 15 8222 gbip add nsvl 901 remote 10.161.71.228 8666 gbip add nsvl 902 remote 10.161.71.228 8777
In this step, the data 1501 and 1502 belongs to the local NSVL and is configured on the RPPU15 board. The data 901 and 902 belongs to the peer NSVL.
Step 4 Configure the BindNSVLdata gbip add bindnsvl <NSEI> <NSVLI> [<DataWeight> <SigWeight>]
gbip add bindnsvl 800 1501 255 255 gbip add bindnsvl 800 1502 255 255 gbip add bindnsvl 800 901 255 255 gbip add bindnsvl 800 902 255 255
Step 5 Configure the position data for NSE signaling entity nse add <NSEI> <PrimeBoardNo> <SlaveBoardNo>
nse add 800 15 15
Step 6 Configure Cell ID at the Gb interface cell add <CellID> <NSEI> <PrimaryBoardNo><SlaveBoardNo> <BVCI> <BSSID>
cell add 460008187009C20 800 15 15 20 0 cell add 460008187009C21 800 15 15 21 0 cell add 460008187009C3B 800 15 15 59 0 cell add 460008187009C3C 800 15 15 60 0
Cell ID can be obtained by calculating the CGI. The CGI is set to be from 4600081879c20 to 4600081879c3c, and from 4600081889c40 and 4600081889c5c,in 5.4 "Example for GPRS Cell Data Configuration", so the Cell ID of BSC0 is from 460008187009c20 to 460008187009c3c, and the Cell ID of BSC1 is from 460008188019c40 to 460008188019c5c. All cells in one RA should be configured with the same NSEI The NSEI and BSSID can match each other. The value range of BVCI is from 2 to 65534.
----END
6-24
Issue 03 (2007-11-05)
Configuration Check
After the data is configured at the Gb interface, check the connection status from local NSVL to peer NSVL and the status of BVC. If the two statues are normal, the data configuration at the Gb interface is successful.
Step 1 Use the command ping to check whether the communication between the PCU and the SGSN is normal. gbip ping <BoardNo> <Destination> [<Size> <Count> <Timeout>]
PCU_220(advanced)#gbip ping 15 10.161.71.228 32 4 1 Pinging 10.161.71.228 with 32 bytes of data: Reply from 10.161.71.228: bytes = 32 time<1ms Reply from 10.161.71.228: bytes = 32 time<1ms Reply from 10.161.71.228: bytes = 32 time = 10ms Reply from 10.161.71.228: bytes = 32 time = 10ms Ping statistics for 10.161.71.228: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) PCU_220(advanced)#
Step 2 Query the connection status between the local NSVL and the peer NSVL. mt nsvc show state
NSEI 800 800 800 800 LocalNSVLI 1501 1501 1502 1502
<NSEI> {<LocalNSVLI> [<remoteNSVLI>]} | all

LinkState available available available available
PCU_220(advanced)#gbip link 800 all RemoteNSVLI 901 902 901 902
PCU_220(advanced)#
Step 3 Query the status of Signal BVC mt bvc signal show state
PCU(super)#mt bvc signal show 800 This pperation is successful NSEI: SIG BVC status : 800 : normal
<NSEI>
In this step you should query the BVC signaling status of the NSEI that is configure by the command nsvc add. Here only shows an example: query the BVC signaling status of the NSEI 800. The correct data is displayed only when the PCU data configuration is completed and the PCU is connected to the configured SGSN.
Step 4 Query the status of PTP BVC mt bvc ptp show state <NSEI> <BVCI>| all
PCU (super)#mt bvc ptp show 800 0 This pperation is successful
Issue 03 (2007-11-05)
6-25

NSEI: BVCI: PTP BVCstatus :800 :0 :normal
In this step you should query the PTP BVC status configure by the command cell add. Here only shows an example: query the BVCI 0 status of the NSEI 800.
----END
6-26
Issue 03 (2007-11-05)

01 Body

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

01 Body

Enviado por

Direitos autorais:

Formatos disponíveis

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

2 System Network Data Configuration ....................................................................................2-1

3 Hardware Data Configuration.................................................................................................3-1

4 Pb/G-Abis Interface Data Configuration ..............................................................................4-1

5 GPRS Cell Configuration .........................................................................................................5-1

Huawei Technologies Proprietary

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

6 Gb Interface Data Configuration ............................................................................................6-1

Huawei Technologies Proprietary

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

Huawei Technologies Proprietary

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

Huawei Technologies Proprietary

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

Huawei Technologies Proprietary

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

1.1 Preconditions for Data Configuration

1.2 Concepts Related to Data Configuration

Huawei Technologies Proprietary

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

Huawei Technologies Proprietary

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

Backup of Cells in the Same BSC

Network Operation Mode

Timer and Counter

Huawei Technologies Proprietary

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

Network Control Mode

Internal Port and External Port

Huawei Technologies Proprietary

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

3 2 1 0 L2PU physicall port RPPU

Huawei Technologies Proprietary

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

1.3 Data Configuration Flow

Huawei Technologies Proprietary

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

2 System Network Data Configuration

System Network Data Configuration

About This Chapter

Huawei Technologies Proprietary

2 System Network Data Configuration

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

2.1 General Configuration Sequence

2.2 External Input Data

2.3 System Network Data Configuration

Huawei Technologies Proprietary

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

2 System Network Data Configuration

Command ipaddress set ipaddress show

Major Parameter Description

2.3.2 Configuring Routing Information

Huawei Technologies Proprietary

2 System Network Data Configuration

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

Major Parameter Description

2.3.3 Configuring SNMP information

Huawei Technologies Proprietary

HUAWEI PCU6000 Packet Control Unit Operation Manual - Data Configuration

2 System Network Data Configuration

Major Parameter Description

2.4 Example for System Network Data Configuration

Huawei Technologies Proprietary