zxg10-bss-gprs operation and commissioning procedure

7/28/2019 ZXG10-BSS-GPRS Operation and Commissioning Procedure

1/40

After-Sales Technology Filefor Mobile Service

Technology File Name: ZXG10-BSS-GPRS

debugging

Document No.:

Version: A

Quality Grade:

Total 30 Pages

(Cover included)

Drafted by: Zhang Mingjing

Reviewed by: _____________

Counter-signed by: _________

Standardized by: ___________

Approved by: ______________

ZTE CORPORATION


2/40

Revision Record

File No. VersionPrepared/

Modified byDate

Change

Reason

Major

Revisions

(Gist Only)

A Zhang Mingjing 2005/7/8 None None

Note 1: Fill in this table each time modifying archive files (files archived to business department or

archive room of ZTE).

Note 2: For the first filing, the items of Change Reason and Major Changes shall be filled in with

None.


3/40

Chapter 1 Hardware Install............................................................................................................................5

1.1 The structure of the GPRS cabinet.........................................................................................................5

1.2 Shelf of the Packet Control Unit BPCU.................................................................................................6

1.2.1 Overview......................................................................................................................................6

1.2.2 Configuration of BPCU................................................................................................................6

1.2.3 Function and Principle..................................................................................................................6

1.2.4 Backplane and Interface...............................................................................................................7

1.2.5 Backplane DIP Switch and the Jumpers......................................................................................9

1.3 Shelf of the Gb Interface Unit BGIU...................................................................................................10

1.3.1 Overview....................................................................................................................................10

1.3.2 Configuration of BGIU..............................................................................................................10

1.3.3 Function and Principle................................................................................................................11

1.3.4 Backplane and Interface.............................................................................................................11

1.3.5 Backplane DIP Switch and the Jumpers....................................................................................13

1.4 Cable Connection ................................................................................................................................15

1.4.1 Cable From BNET to BPCU......................................................................................................15

1.4.2 Cable From BNET to BGIU.......................................................................................................15

1.4.3 HW Cable From BPCU to BGIU...............................................................................................16

1.4.4 Network Cable of the PCU ........................................................................................................16

1.4.5 Network Cable from MP to BGIU.............................................................................................16

1.4.6 RS485 Cable for Two Adjacent Layers of Power Supplies.......................................................17

1.4.7 RS485 Cable for the Same Layer of Power Supplies................................................................17

1.4.8 MON-DSNI/POWB Cable in the BCTL (SCU) Layer..............................................................18

Chapter 2 Data Preparation.........................................................................................................................19

2.1 DATA REQUIRED...............................................................................................................................19

2.2 Configuration data of the GPRS commissioned at Bijie as provided by Alcatel................................19

Chapter 3 Data Configuration......................................................................................................................20

3.1 Back Up the Foreground and Background Data .................................................................................20

3.1.1 Use the tools/dbbak/cmexp to export the DUMP data of the background ...............................20

3.1.2 Use the OMCFTP tool to retrieve the ZDB data of the modules at the foreground..................20

3.2 Modify the Configuration File of Server and Restart the OMCR ......................................................20


4/40

3.3 Perform Physical Configuration in the Integrated Configuration Environment .................................20

3.3.1 Add rack......................................................................................................................................20

3.3.2 Add board...................................................................................................................................21

3.3.3 For TIC, the BRCH should be configured ................................................................................22

3.3.4 Configure NSVC........................................................................................................................23

3.4 Perform Radio Configuration in the Integrated Configuration Environment .....................................26

3.4.1 Configure the GPRS cell to make it support GPRS or not........................................................26

3.4.2 Configure relevant data in GPRS cell options .......................................................................26

3.4.3 Configure static and dynamic channels.....................................................................................27

3.5 Modifying Relevant Timers in Radio Resource Management ............................................................29

3.5.1 Modifying the timers of BSC.....................................................................................................29

3.5.2 Modifying cell timer...................................................................................................................34

Chapter 4 Status Viewing and Routine Test................................................................................................35

4.1 Status Viewing......................................................................................................................................35

4.1.1 Status viewing in Dynamic data management...........................................................................35

4.1.2 Status viewing in Data probe..................................................................................................35

4.2 Routine Test of Commissioning...........................................................................................................37

4.2.1 Accessing WAP via mobile phone: ...........................................................................................37

4.2.2 Data service: ..............................................................................................................................37

4.2.3 Notes...........................................................................................................................................38


5/40

Chapter 1 Hardware Install1.1 The structure of the GPRS cabinet

The structure of the GPRS cabinet is as shown in Fig. 1.1-1

BGIU

BPCU 1

BPCU 2

Layer 1

Layer 2

Layer 6

Layer 3

Layer 4

Layer 5

BPCU 3

BPCU 4

Fig. 1.1-2 Composition of the GPRS Cabinet

With redundancy reserved and according to the actual measuring, the power

consumption of each fully-configured shelf is:

1. GIU shelf

Power consumption: 110W

2. BPCU shelf

Power consumption: 110W

The GPRS cabinet shown in Fig. 1.1 -2 consists of one BGIU shelf and 4 BPCU

shelves. Therefore, the maximum power consumption of the cabinet is:

110W+440W=550W.


6/40

1.2 Shelf of the Packet Control Unit BPCU

1.2.1 Overview

After GPRS is introduced, two kinds of shelves, namely BGIU and BPCU, are added to

the system. The BGIU shelf carries the Gb interface unit GIU, whereas the BPCU shelf

carries the packet control unit PCU.

1.2.2 Configuration ofBPCU

Configuration of the boards of BPCU is shown in Fig. 1.2 -3.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

POWB

FRP

PUC

PUC

PUC

PUC

FRP

FRP

BRP

BRP

BRP

BRP

POWB

BRP

BRP

BRP

BRP

FRP

BRP

BRP

FRP

BRP

FRP

BRP

BRP

BRP

Fig. 1.2-3 Full Configuration of the BPCU Shelf

The following boards can be configured in the BPCU shelf:

1. PUC

2. BRP

3. FRP

4. POWB

BPCU has two SPCUs. Each BPCU has two mandatory POWB boards. Each SPCU

has two PUC boards as the active and standby. BPCU may have up to 3 FRP boards in

the N + 1 mode and up to 7 BRP boards in the N + 1 mode.

1.2.3 Function andPrinciple

PCU consists of multiple SPCUs, but the quantity of SPCUs depends on the need of

the subscriber.

The structure of SPCU is shown in Fig. 1.2 -4.


7/40

FRP

BRP

AUC

FRP

BRP

.

.

.

.

.

.

PUC

18M

18M

18M

18M

18M

18M

Fig. 1.2-4 Structure of SPCU

SPCU consists of PUC and the protocol processing board FRP or BRP (both of which

adopt GDPP as the hardware).

PCU processes 3 kinds of protocols, namely: FR, BSSGP, and RLC/MAC protocols.

BSSGP and RLC/MAC protocols are processed by BRP, and the FR protocol is

processed by FRP.

PUC manages FRP and BRP, provides the communication channel for BRP and RMM,

completes the circuit switching between the service channel of the switching network

and BRP, and the circuit switching between the Gb channel of GIPP and FRP. PUC is

connected with FRP and BRP through one 8M HW single-polarity cable. It is

connected with the T-net and the GIPP of GIU through one 8M HW differential cable.

1.2.4 Backplane andInterface

The backplane of the BPCU shelf is the BPCU board, the rear view of which is

illustrated in Fig. 1.2 -5.


8/40

Fig. 1.2-5 Rear View of the BPCU Backplane


9/40

The external interfaces of the BPCU shelf are shown in Table 1.2 -1.

Table 1.2-1 External Interfaces of the BPCU Shelf

Interface ID Function Connection Relation

X1_485_INSocket of the bus 485, the power

monitoring busConnects the upper shelf

X1_485_OUTSocket of the bus 485, the power

monitoring busConnects the lower shelf

X52, X58 Power supply socket Connects the busbar

X53_TENT (V2.0) HW and the clock For the network switching unit

X53_GIPP (V2.0) HW and the clock Connects GIU

X51_485_INSocket of the bus 485, the power

monitoring busConnects the upper shelf

X51_485_OUTSocket of the bus 485, the power

monitoring busConnects the lower shelf

X24, 55 Ethernet interface Connects HMS

1.2.5 Backplane DIP Switchand the Jumpers

Layout of the backplane of the BPCU shelf is shown in Fig. 1.2 -6.

X57

X58

X60

X61

X56

X27

X59

X60

Fig. 1.2-6 Jumper Layout of the BPCU Shelf Backplane

Jumpers X56 and 59 on the BPCU backplane decide at which layer this shelf is placed

in the rack (numbered from the bottom to the top). Jumpers X27 and X60 decide if the

POWB board of this shelf is the last one monitored by the bus 485. Meanings of the

jumpers and the switch are shown in Table 1.2 -2.


10/40

Table 1.2-2 Meanings of BPCU Jumpers

Jumper Position

(from top to bottom)Status Meaning

X56, X57_1~6 OFF OFF OFF OFF OFF ON In the first shelf of the rack

X56, X57_1~6 OFF OFF OFF OFF ON OFF In the second shelf of the rack

X56, X57_1~6 OFF OFF OFF ON OFF OFF In the third shelf of the rack

X56, X57_1~6 OFF OFF ON OFF OFF OFF In the fourth shelf of the rack

X56, X57_1~6 OFF ON OFF OFF OFF OFF In the fifth shelf of the rack

X56, X57_1~6 ON OFF OFF OFF OFF ON In the sixth shelf of the rack

X27, 60 OFF

The POWB board closest to the

jumper is not the last one monitored

by the bus 485.

X27, 60 ON


jumper is the last one monitored by

the bus 485.

Note: OFF: The short-circuit cap is not plugged. ON: The short-circuit cap is plugged.

1.3 Shelf of the Gb Interface Unit BGIU

1.3.1 Overview

The BGIU shelf carries the Gb interface unit (GIU) and performs the Gb interface

function.

1.3.2 Configuration ofBGIU

Configuration of the boards of BGIU is shown in Fig. 1.3 -7.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

POWB

TIC

TIC

TIC

TIC

TIC

TIC

TIC

TIC

POWB

GIPP

GIPP

HMS

HMS

Fig. 1.3-7 Full Configuration of the BGIU Shelf

The following boards can be configured in the BGIU shelf:

1. GIPP


11/40

2. TIC

3. HMS

4. POWB

One BGIU has 2 mandatory POWB boards, 2 GIPP boards as the active and standby,

up to 8 TIC boards, and 2 HMS boards as the active and standby.

1.3.3 Function andPrinciple

At the Gb interface, the E1 interface of frame relay is adopted. Accordingly, GIU

(GPRS Interface Unit) is designed to provide the physical interface for E1 frame relay.

GIU provides the physical layer functions of the Gb interface and the related loop test

functions.

Its structure is shown in Fig. 1.3 -8.

GIPP

TIC

TIC

.

.

.

GIPP

18M

28M

88M18M

42M

42M

Fig. 1.3-8 Schematic Diagram of the GIU Structure

1.3.4 Backplane andInterface

The backplane of the BGIU shelf is the BGIU board, the rear view of which is

illustrated in Fig. 1.3 -9.


12/40

Fig. 1.3-9 Rear View of the BGIU Backplane


13/40

The external interfaces of the BGIU shelf are shown in Table 1.3 -3.

Table 1.3-3 External Interfaces of the BGIU Shelf

Interface ID Function Connection Relation

X1_485_INSocket of the bus 485, the

power monitoring busConnects the upper shelf

X1_485_OUTSocket of the bus 485, the

power monitoring busConnects the lower shelf

X60, X62 Power supply socket Connects the busbar

X7_TENT-HW HW and the clock For the network switching unit

X8_SPCU (1-4) -HW HW and the clock Connects PCU

X27_485_INSocket of the bus 485, the

power monitoring busConnects the upper shelf

X27_485_OUTSocket of the bus 485, the

power monitoring busConnects the lower shelf

X130-152 Ethernet interface Connects MP and PUC

TIC (0-7) IN (0-3) 75 E1 input signals Connects SGSN

TIC (0-7) OUT (0-3) 75 E1 output signals Connects SGSN

1.3.5 Backplane DIPSwitchandtheJumpers

Layout of the backplane of the BGIU shelf is shown in Fig. 1.3 -10.

X57

X58

X60

X61

X29

X27

X61

X58

Fig. 1.3-10 Jumper Layout of the BGIU Shelf Backplane

Jumpers X61 and 29 on the BPCU backplane decide at which layer this shelf is placed

in the rack (numbered from the bottom to the top). Jumpers X27 and X58 decide if the

POWB board of this shelf is the last one monitored by the bus 485. Meanings of the

jumpers and the switch are shown in Table 1.3 -4.


14/40

Table 1.3-4 Meanings of BGIU Jumpers

Jumper Position

(from top to bottom)Status Meaning

X29, X61_1~6 OFF OFF OFF OFF OFF ON In the first shelf of the rack

X29, X61_1~6 OFF OFF OFF OFF ON OFF In the second shelf of the rack

X29, X61_1~6 OFF OFF OFF ON OFF OFF In the third shelf of the rack

X29, X61_1~6 OFF OFF ON OFF OFF OFF In the fourth shelf of the rack

X29, X61_1~6 OFF ON OFF OFF OFF OFF In the fifth shelf of the rack

X29, X61_1~6 ON OFF OFF OFF OFF ON In the sixth shelf of the rack

X27, 58 OFF


jumper is not the last one

monitored by the bus 485.

X27, 58 ON


jumper is the last one monitored by

the bus 485.

Note: OFF: The short-circuit cap is not plugged. ON: The short-circuit cap is plugged.


15/40

1.4 Cable ConnectionNote:

Locking plate should be installed at all the backplane sockets corresponding

to the 3*8-pin plugs.

Ensure that the power of the shelf is off during the cable connection. Connect

the cables properly, check the cabling, and then power on the equipment.

1.4.1 Cable From BNET to BPCU

D-type cable. Name: BNET-BPCU cable. Type: 3*8 cable

Pay attention to the correspondence relationship between the HW number and

the T-network connection cable.

As a rule, it is: SPC (HW1 number 5) (HW2 number 5)

SN Cable

Name

End A End B Remarks

DSNI_S/BNET~PUC/BPCU (GPRS rack)

1 BSC-BGDn 1#L3_DSNI2-S_SPC32~33

UP1~8

n# L2_BPCU-

96PIN_TNET(V2.0) UP1~8

GPRS rack


DN25~32

n# L3_BPCU-


GPRS rack


DN17~24

n# L4_BPCU-


GPRS rack

4 BSC-BGDn 1# L3_DSNI1-S_SPC26~27

DN9~16

n#

L5_BPCU_96PIN_TNET(V2.0)

UP1~8

GPRS rack

1.4.2 Cable From BNET to BGIU

D-type cable. Name: BNET-BGIU cable. Type: 3*8 cable

Pay attention to the correspondence relationship between the HW number and

the T-network connection cable

As a rule, it is: SPC (HW1 number 5) (HW2 number 5)

SN Cable

Name

End A End B Remarks

DSNI_S/BNET~GIPP/BGIU (GPRS rack)


16/40

1 BSC-BGDn 1# L3_DSNI1-S_SPC24~25

DN1~8

n# L1_BGIU_GIPP_TNET

UP25-32

GPRS rack

1.4.3 HW Cable From BPCU to BGIU

D-type cable. Name: BNET-BGIU cable. Type: 3*8 cable

SN Cable Name End A End B Remarks

PUC/BPCU ~ GIPP/ BGIU (GPRS rack)

1 BSC-BGD01 n#L5_BPCU_96PIN_GIPP(V2.0)

UP25~32

n#

L6_BGIU_GIPP_SPCU1

DN1~8

GPRS rack; where

end A of the cable

between PUC and

GIPP is connected

with the PUC, and

end B is connected

with the GIPP.


UP25~32

n#

L6_BGIU_GIPP_SPCU1

DN9~16


UP25~32

n#L6_BGIU_GIPP_SPCU1

DN17~24


UP25~32

n#L6_BGIU_GIPP_SPCU1

DN25~32

1.4.4 Network Cable of the PCUThis cable is laid to the J45 ports (totally 23 pieces) of the HMS board (which

can be replaced with HUB) of the GIU shelf. The SPCU shelf contains two

RJ45 ports. The upper RJ45 port corresponds to the left PUC board, and the

lower RJ45 port corresponds to the right PUC board.

Network Cable of the PCU

BPCU~HUB (or HMS)

1 Network cable of the

PCU

BPCU _

X54

HUB (any one in L6_BGIU_RJ45-

1~21)

GPRS rack

2 Network cable of the

PCU

BPCU _

X55

HUB (any one in L6_BGIU_RJ45-

1~21)

GPRS rack

1.4.5 Network Cable from MP to BGIU

All the network cables from MP (the other end of the O+ cable) to GIU shelf

are laid to the RJ45 port of the HMS board (which can be replaced with HUB)

of the GIU shelf. O cable (cable from MP to HUB)

SN Cable Name


17/40

1 B01 1 cable is configured for each MP, and the

cable length depends on the site survey

result

1.4.6 RS485 Cable for Two Adjacent Layers of Power Supplies

B-type cable (485). Name: cable from the upper-layer power supply to the

lower-layer power supply. Type: 3*8 cable.

The connection relationship from the upper-layer RS485 end to the lower-

layer RS485 end is shown in the following table.

The upper-layer RS485 end Position of the 485-OUT socket of the

POWB board at the Ln+1 (n means the number of layers, n=1~6 from bottom

upward) layer.

The lower-layer RS485 end Position of the 485-IN socket of the POWB

board at the Ln (n means the number of layers, n=1~6 from bottom upward)

layer.

Upper-layer RS485 End Lower-layer RS485 End

Ln+1_POWB_L(R)_485-OUT UP9~16 Ln_POWB_L(R)_485-IN UP1~8

To add a layer of BATC shelf, it is necessary to add two B-byte cables for

connecting this layer of BATC shelf with the upper-layer shelf.

1.4.7 RS485 Cable for the Same Layer of Power Supplies

C-type cable (485). Name: common-layer power cable. Type: 3*8 cable.

The connection relationship from the left RS485 end to the right RS485 end is

shown below. The connection relationship is fully bilateral-symmetrical. The

left RS485 end Position of the 485-OUT socket of the left POWB board

of the lower-layer shelf.

Right RS485 end Position of the 485-OUT socket of the right POWB

board of the lower-layer shelf.

Table Connection Relationship From the Left RS485 End to the Right RS485 End

RS485OUT RS485OUT

N# POWB_L_485-OUT UP9~16 N# POWB_L_485-OUT UP9~16


18/40

1.4.8 MON-DSNI/POWB Cable in the BCTL (SCU) Layer

A-type cable (485). Name: MON-DSNI/POWB cable

The connection relationship from the MON end to the POWBn end is shown

in the following table.

MON end Position of the MOND2 socket of the MON board of the

BCTL (SCU) shelf

FBI end Position of the RS485 socket in the FBI1 slot of the BNET shelf.

POWB end 485-IN socket of the right POWB board at the 6th layer of

the number n rack (n means the rack number, n=1~5. If n>5, the A+ cable is

required).

Table Connection Relationship From the MON End to the POWB End

MON POWB DSNI

1# L4_MON_MOND2

DN25~32

n# L6_POWB_R_485-IN

UP1~8

1# L3_FBI2'__RS485-IN

UP1~8

Note: A-type cable is the one pulls N 38 cable. In the above table, n=1-5.

It means the number n cable connector at the multi-connector cable end.

The POWB end of the A-type cable is connected only with the right POWB

on the top layer of shelf (L6) of each rack.

In case of expanding the GPRS rack, it is necessary to determine the BGA

type according to the number of racks. If the central rack is configured, it is

not necessary to configure the GPRS rack.

Use BGA01 if the number of racks is 1; use BGA02 if the number of racks is

2; use BGA03 if the number of racks is 3; use BGA04 if the number of racks

is 4; and use BGA05 if the number of racks is 5. As for the cables mentioned

above, only 1 cable is required if there is only 1 BSC.

Use A+ cable if the number of racks is higher than 5. Use BGA+01 if thenumber of racks is 6; and use BGA+02 if the number of racks is 7.

SN (Latest) Code Name Model

1 P0626401AA02 BSC-BGA01 ZX062.G.3521

2 P0627410AA03C2025 BSC-BGA02 ZX062B-02-10-02

3 P0627409AA03C0000 BSC-BGA03 ZX062B-02-10-03

4 P0627408AA03C0000 BSC-BGA04 ZX062B-02-10-04

5 P0627414AA03C0000 BSC-BGA05 ZX062B-02-10-05

6 P0627415AA03C0000 BSC-BGA+01 ZX062B-02-10-06

7 P0627416AA03C0000 BSC-BGA+02 ZX062B-02-10-07


19/40

Chapter 2 Data Preparation

2.1 DATA REQUIRED

For SGSN, the five items of data should be provided: NSEI, NSVCI, DLCI

(Data Link Carrier Identity), BRCH and RAC.

NSEI: Network Service Entity Identifier

NSVCI: Network Service Virtual Connection Identifier, which identifies the

network service virtual connection from BSS to SGSN

BRCH: Bear Channel, timeslot number for use of trunk circuit

DLCI: Data Link Connect Identity, which is a concept related to frame relayRAC: Routing Area Code Like the GSM which uses location area to manage a

group of cells, the GPRS further itemizes the management, and divides one

location area into several routing areas, identified with RAI

(MCC+MNC+LAC+RAC).

2.2 Configuration data of the GPRS commissioned at Bijie asprovided by Alcatel

Syste

m No.

Location BSC

Name

FR-

BC

BSC

ID

Gb TS NSEI DLCI NSVC CIR/

EIR/

NIR

PRIO

RITY

vender

4-11

BiJie1

BiJie

1

71

1

1 to

8

13

115 1101

1

0 ZTE

116 1101

2

1

4-12

Bijie2

Bijie2

72

2

1 to

8

14

117 1101

3

0 ZTE

118 1101

4

1


20/40

Chapter 3 Data Configuration

3.1 Back Up the Foreground and Background Data

3.1.1 Use the tools/dbbak/cmexp to export the DUMP data of the

background

3.1.2 Use the OMCFTP tool to retrieve the ZDB data of the modules at the

foreground

3.2 Modify the Configuration File of Server and Restart theOMCR

Make sure that Environment = GSM in $OMCHOME/conf/syscfg.ini is

changed to Environment = GPRS, so as to give rise to the GPRS

configuration options.

Restart the OMCR server.

3.3 Perform Physical Configuration in the IntegratedConfiguration Environment

3.3.1 Add rack

Perform the operation of adding rack through Physical view in the

integrated configuration environment. Add a new rack in Physical view (or

configure it in the vacant shelf of the original rack), and then add the two

layers of shelves: ZXG10_GIU and ZXG10_SPCU.


21/40

3.3.2 Add board

When adding the three types of boards: GIPP, PUC and TIC, pay attention to

the following aspects:

Note down the allocated HW number of the GIPP and PUC boards for ease of

physical connection


22/40

3.3.3 For TIC, the BRCH should be configured

Add TS according to the BRCH data provided by SGSN. For example, in the

following illustration, SGSN allocates the TS1-8, and uses default values for

other items.

Note: The FRPNO connected with the BRCH of the same PUC may vary.

Therefore, when configuring the second PCM, it is necessary to select 2 for

FRPNO.


23/40

3.3.4 Configure NSVC

In Physical view, right click on BSC. In the menus that appear, select

Configure NSVC and start the configuration.

NSEI, NSVCI and DLCI are provided by SGSN.

Burst package size can be set as 640KB*number of timeslots. Here the BRCH has 8

timeslots, so it can be set as 640*8=5120KB.

For other parameters, the default values apply.


24/40


25/40


26/40

3.4 Perform Radio Configuration in the IntegratedConfiguration Environment

3.4.1 Configure the GPRS cell to make it support GPRS or not

In the Edit radio information of cell window, select Support GPRS, and

the GPRS cell options window will appear.

3.4.2 Configure relevant data in GPRS cell options

In the GPRS cell options window, input the following data:

NSE ID:

Select the service entity of the network

BVC ID:

ID of the BSSGP Virtual Connection (BVC). Under the same Network Service

Entity (NSE), each GPRS cell can be identified uniquely by a BVCI.

Generally, a BVCI = SITEID + CELLID. (For example, set 11 as the BVCI for the

first cell 1 of site 1)

Routing area code:

Provided by SGSN

Routing color code:

Set according to the network planning


27/40

BRP group:

Select the corresponding BRP group, whose value range is 1~6.

The correspondence relationship between the BRP group and the BRP

board is:

The BRP board is designed as N+M backup. If seven BRP boards are

configured as a full capacity, it is 6+1 backup. Therefore, the BRP groups are

in a one-to-one relationship with the BRP boards.

However, the BRP board decides the logical serial number according to the

sequence of startup. The first started BRP board is the first BRP group.

Therefore, no necessary relationship exists between the BRP group and the

actual slot.

You can use the dynamic data management to search the BRP board

corresponding to the current BRP group, or use the data probe to search the

R_BRP table of the central module and then obtain the BRP board from the

BRPgroup field.

Each BRP group supports a maximum of 40 GPRS cells or 40 PS

channels (sum of dynamic channels and static channels). Generally, 40 PS

channels are preferable. Therefore, before configuring the data, it is necessary

to allocate the BRP groups as required in advance to avoid too many channels

configured on a BRP group.

LSA ID: Remains unchanged

3.4.3 Configure static and dynamic channels

1. During the radio resources configuration, adjust configurations of the


28/40

PDTCH channel in each cell to ensure the numbers of both the dynamic

and static PDTCH channels configured on each BRP board are not more

than 40.

2. For the offices with large GPRS flow (esp. overseas offices), the

numbers of both the dynamic and static PDTCH channels configured on

each BRP board should not be more than 30.

3. Packet channels are configured in the BCCH carrier frequency.

4. Do not configure dynamic channels for sites in a city zone.

5. A dynamic channel should be configured behind a static channel, that is,

the time slot of a dynamic channel should be larger than that of a static

channel.

6. TSC of the PDTCH channels on the same TRX should be identical.

7. When the frequency hopping is used, the packet time slots on the same

TRX should have the same frequency parameters (MA, MAIO and HSN)

and the same training sequence codes (TSC).

8. If you choose to configure a cell to support PS, you must configure at

least one PS channel.

9. Configure one dynamic channel for a cell with one carrier frequency.

10. Configure one static channel for a cell with two carrier frequencies.

11. Configure two static channels for a cell with three carrier frequencies.

12. Configure three static channels for a site with more than three carrier

frequencies.

13. Configure four or more static channels for key sites.


29/40

3.5 Modifying Relevant Timers in Radio ResourceManagement

3.5.1 Modifying the timers of BSC


30/40

T3193: The default value of this parameter is 51. The value of this parameter should be

greater than that of the timer T3192.


31/40

CellFcThs: The threshold of BVC flow control.

It is the threshold of triggering the BVC flow control process. The BVC flow control

is performed between the SGSN and the BSS, namely, on the Gb interface, and is

performed only on the downlink. Specifically, the BSS provides the flow control

parameters and the SGSN implements them. The BVC flow control aims to prevent

discarding some LLC data due to timeout caused by too busy packet channels (too many

buffered LLC frames) in a BVC on the BSS, or discarding the new downlink LLC datadue to limited memory resources (overflow of LLC frame buffer). The BSS GP process

at the BSS side makes statistics of the current overflow ratio of the BVC periodically

(including short statistics and long statistics). In case of overflow of long statistic timer,

the BVC flow control process will be originated unconditionally. When the difference

between two overflow ratios is greater than CellFcThs, the triggering of the process is

subject to confirmation of the SGSN. In case of overflow of short statistic timer, and the

difference between two overflow ratios is greater than CellFcThs, the BVC flow

control process will be originated. In this case, the triggering of the process is also

subject to confirmation of the SGSN. The default value of this parameter is 80.

CellFcPer: Flow control period of BVC:

It is the BVC overflow ratio statistic period, namely, BVC long statistic period in the

BVC flow control process. In order to provide reference for the BVC flow control at

the SGSN side, the BSSGP process at the BSS side makes statistics of the current

overflow ratio of the BVC periodically. In case of overflow of long statistic timer, the

BVC flow control process will be originated unconditionally. When the difference

between two overflow ratios is greater than CellFcThs, the triggering of the process is


difference between two overflow ratios is greater than CellFcThs, the BVC flow

control process will be originated. In this case, the triggering of the process is also


32/40

subject to confirmation of the SGSN. In our system, BVC short statistic period = BVC

long statistic period / 3. The default value of this parameter is 3000. At Bijie, this

parameter is set to 30000.

MsFcThs: MS flow control threshold.

It is the threshold of triggering the MS flow control process. The MS flow control is

performed between the SGSN and the BSS, namely, on the Gb interface, and is

performed only on the downlink. Specifically, the BSS provides the flow control

parameters and the SGSN implements them. The MS flow control aims to prevent

discarding some LLC data due to timeout caused by too busy packet channels (too many

buffered LLC frames) in an MS in the BSS, or discarding the new downlink LLC data

due to limited memory resources (overflow of LLC frame buffer). The BSS GP process

at the BSS side makes statistics of the current overflow ratio of the MS periodically

(including short statistics and long statistics). In case of overflow of long statistic timer,

the MS flow control process will be originated unconditionally. When the difference

between two overflow ratios is greater than MsFcThs, the triggering of the process is


difference between two overflow ratios is greater than MsFcThs, the MS flow control

process will be originated. In this case, the triggering of the process is also subject to

confirmation of the SGSN. The default value of this parameter is 80.

MsFcPer: Flow control period of MS.

It is the MS overflow ratio statistic period, namely, MS long statistic period in the

MS flow control process. In order to provide reference for the flow control at the

SGSN side, the BSSGP process at the BSS side makes statistics of the current overflow

ratio of each MS periodically. In case of overflow of long statistic timer, the MS flow

control process will be originated unconditionally. When the difference between two

overflow ratios is greater than MsFcThs, the triggering of the process is subject to

confirmation of the SGSN. In case of overflow of short statistic timer, and the difference

between two overflow ratios is greater than MsFcThs, the MS flow control process

will be originated. In this case, the triggering of the process is also subject to

confirmation of the SGSN. In our system, MS short statistic period = MS long statistic

period / 3. The default value of this parameter is 3000. At Bijie, this parameter is set to

30000.

MS encoding mode:

The GPRS data block can adopt different encoding modes in CS-1 ~ CS-4. The

corresponding data rates are 9.05kb/s, 13.4kb/s, 15.6kb/s and 21.4kb/s respectively. The

encoding mode at a lower level has a higher error correction capability and a lower data

throughput. When the radio transmission quality of the network is good, it means a low

probability of retransmitting error radio blocks. In this case, the encoding mode with a

larger data amount (namely, channel encoding mode at a higher level) can be used. The

default mode is CS-1. At Bijie, the encoding mode is CS-2.

N3101 (maximum permitted number of consecutive lost uplink data blocks):


33/40

The parameter for use at the RLC/MAC layer on the BRP. During the packet uplink

transmission process, the BSS will specify a USF (corresponding to an uplink TBF) for

each uplink block. For a USF, if the network receives data correctly on the specified

uplink data, it will clear the counter N3101 for this NBF. If the count of consecutive

losses on the specified uplink block is more than N3101 (N3101max), the timer T3169will be started. Upon expiry of the timer T3169, the network can reuse the TFI and USF

resources. The default value of this parameter is 10. At Bijie, this parameter is set to 9.

N3101 (count of packet uplink acknowledged / unacknowledged

reattempts):

The parameter for use at the RLC/MAC layer on the BRP. During the packet uplink

transmission process, if the network detects that the uplink TBF is completed (CV=0,

and V(Q)=V(R)), and all RLC data blocks have been received, the network will send a

packet uplink acknowledged / unacknowledged message to set the last

acknowledgement identity to 1. The identity header of the RLC/MAC control block

includes a legal RRBP domain. Then, the network will clear the counter N3103. If the

MS receives the packet uplink acknowledged / unacknowledged message whose FAI

is 1 as sent from the network side, the MS should send the packet control

acknowledgement message on the corresponding block specified by the RRBP, and

release the TBF. If the network has not received the packet control acknowledgement

message in the radio block specified by the RRBP field, the network should increase the

value of the counter N3103, and retransmit the packet uplink acknowledged /

unacknowledged message. If the counter N3103 goes beyond the N3103 (N3103max),

the network should start the timer T3169. Upon expiry of the timer T3169, the networkcan reuse the TFI and USF resources. The default value of this parameter is 10. At Bijie,

this parameter is set to 8.

N3105 (maximum permitted number of consecutive lost uplink RLC/MAC

control messages):

The parameter for use at the RLC/MAC layer on the BRP. During the packet downlink

transmission process, the BSS will set the RRBP field on the downlink RLC data block

periodically, so as to notify the MS to send the RLC/MAC control message (e.g.,

packet downlink acknowledgement message) on the corresponding uplink block. For

a TBF, if the count of consecutive lost RLC/MAC control messages on the specifieduplink block is more than N3105 (N3105max), the timer T3195 will be started. Upon

expiry of the timer T3195, the network can reuse the TFI resources. The default value of

this parameter is 10. At Bijie, this parameter is set to 7.


34/40

3.5.2 Modifying cell timer

T3168:set to 4.0s.

T3192: The default value of this parameter is 0.5s.

Network operation mode: Mode 2 should be selected for this parameter.

Like the cell under RAC, the network operation mode must be consistent.


35/40

Chapter 4 Status Viewing and RoutineTest

4.1 Status Viewing

From Alarm management we can find if there has problem of GPRS.

You can view the status in Data probe, Dynamic data management

4.1.1 Status viewing in Dynamic data management

Select the [ZTE CorporationDomainBSS FunctionLogic Site] node onthe navigation tree on the left in the main interface.

Select the cell to be operated in the upper right list, right-click and the

relevant operations of the BVC in the menu can be seen. Select the [BVC

Block], [BVC Unblock], [BVC Reset], [BVC Signaling Reset] or [BVC State

Query] menu to query or modify the relevant dynamic properties of the BVC,

as shown in Fig. 4.1 -11.

Fig. 4.1-11 Relevant Operations of the BVC

4.1.2 Status viewing in Data probe.

Gb interface state viewing: If the status field in the central module


36/40

R_NSVC is 0, the status is normal.

It can be deemed a symbol of successful interconnection. Other statuses are

described as follows (hexadecimal):

0x0001 Congested0x0002 Seriously congested

0x0004 Peer end blocked (SGSNBLOCK)

0x0008 Local manual blocking

0x0010 Local service blocking (NSTESTBLOCK)

0x0020 Fault blocking (FAULTBLOCK)

0x0040 Manual blocking of the corresponding GIPP subunit

0x0080 Manual blocking of the corresponding TIC subunit

0x0100 Manual blocking of the corresponding AUC subunit

BTS status viewing: There are two tables: R_PSBTS and R_PSCHAN, in

which the status fields are described as follows

(hexadecimal):

R_PSBTS

0x00 Normal

0x01 Manual blocking of cell

0x02 Cell synchronization BRP

blocking (UNSYNCBRP)

0x04 Cell reset blocking

0x08 BTS blocking

0x10 P0-Pn communication fault

(MPCOMM_BLOCK)

0x20 BRP-Pn communication fault

(BRPPNCOMM)

R_PSCHAN

0x00000 Normal

0x10000 Manual blocking of BVC


37/40

0x20000 Whether the cell is

synchronized with the BRP

blocking

0x40000 BVC reset blocking

0x80000 BTS blocking

0x100000 BRP-Pn communication fault

blocking

0x200000 TFI resources congestion

0x400000 Channel service load

congestion

0x800000 No frame number for channel

4.2 Routine Test of Commissioning

After commissioning, it is necessary to perform a GPRS function test, including these items:

WAP, PING, WWW and FTP.

4.2.1 Accessing WAP via mobile phone:

Cell Mobile Phone Accessibility to WAP

4.2.2 Data service:

4.2.2.1 Ping IP1 (e.g., 202.112.20.132), and perform 4 different tests:

ping IP1 -w 3000 n 50; ping IP1 l 100 w 3000 n 50;

ping IP1 l 500 w 5000 n 50; ping IP1 l 1000 w 8000 n 50;

Cell Mobile

Phone

1st Test 2nd Test 3rd Test 4th Test

Send packet

Receive packet


38/40

Cell Mobile

Phone

1st Test 2nd Test 3rd Test 4th Test

Max. time

Min. time

Mean time

Send packet

Receive packet

Max. time

Min. time

Mean time

Send packet

Receive packet

Max. time

Min. time

Mean time

4.2.2.2 Downloading file from Internet

Log in to a website, and use Netants or Flashget to download the files.

Cell Mobile Phone 1st Test (file size: M} 2nd Test (file size: M)

4.2.2.3 FTP operation

Use CuteFTP to log in to the FTP site and download the files.

Cell Mobile Phone 1st Test (file size: M) 2nd Test (file size: M)

4.2.3 Notes

4.2.3.1 download

1. After the file is downloaded via Flashget or Netants, the Download information

box will contain an Average speed entry. Its value is about 3Kbps normally.

2. It is preferable to select a file with a size of about 1M for downloading, so that the


39/40

download duration is short, and the download speed rises to the peak.

3. Among the FTP download software, the cuteftp pro3.1 Build2.18.1 is

recommendable. Here are some Chinese FTP websites (anonymous login):

ftp.whnet.edu.cn

ftp.ia.hust.edu.cn

ftp.lib.pku.edu.cn

4.2.3.2 About configuration for accessing Internet via SAGEM OT96

1) Accessing internet via WAP

Press the @ key on the mobile phone Select 4 (advanced) to enter Select 1

(connection settings) to enter Select a provider (or create a provider), then press

modify Select preferred connection to enter Select GPRS for Preferred

connection, then select details, Select WAP gateway to enter Input the

IP address: 10.0.0.172, and select no secure for secure, and select validate to

go back to the previous directory Select APN to enter Select options

Select directory to enter Select add, input CMWAP (you can input

different letters on the same key if you hold down the key for a while, select

validate to go back to the previous level of directory Select CMWAP, and

then select activate to complete the configuration.

Before accessing the network via WAP, check that a GPRS symbol exists on the

mobile phone, and then press the @ key on the mobile phone Select 3 (go to

URL) to enter Input the URL, e.g., wap.sina.com. However, the GAGEM does

not support Chinese format, so the texts are illegible. To resolve the problem

thoroughly, you can input the URL in the bookmarks.

2) Dialup access

Taking the configuration under WIN2000 as an example:

a) Connect the USB-serial port. This serial port should be COM1 (otherwise,

change it to COM1).

b) Add a standard 28800bps modem at COM1.

c) Add a new dialup connection. Select the new COM1 as the modem, and input

*99*1# as the dialup number. The highest rate is up to 57600bps.

d) In Network, deselect all the three options in PPP setting.

e) These steps are essential: In Attribute -> Advanced -> Extra initialization

command of the standard 28800bps modem, input cmnet (in the win2000

environment, it is not possible to input all the parameters, and they need to be

modified in the registry, where no length restriction is imposed; in the WINNT
ftp://ftp.whnet.edu.cn/ftp://ftp.ia.hust.edu.cn/ftp://ftp.lib.pku.edu.cn/ftp://ftp.whnet.edu.cn/ftp://ftp.ia.hust.edu.cn/ftp://ftp.lib.pku.edu.cn/


40/40

environment, all the data can be input directly, and not necessarily modified in

the registry).

Run the regedit to open the registry, search cmnet and substitute

&K3;+CGDCONT=1,"IP","cmnet",0,0,0;+CGQREQ=1,0,0,3,0,0

for cmnet. (Note: CMNET is an APN, and is not case-sensitive. It is

set uniformly at the GGSN side. The APN of China Mobile of the

public network is CMNET.

f) Connect the SAGEM suite, and begin the dialup access (without having to

input the username or password).

zxg10-bss-gprs operation and commissioning procedure

Documents