ZXG10-BSC (V2)

Base Station Controller

Engineering Data Setting

Specifications
(V2005-01)

ZTE CORPORATION
ZXG10-BSC (V2) Base Station Controller
Engineering Data Setting Specifications (V2005-01)

* * * *

ZTE CORPORATION

ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P.R. China

Website: http://www.zte.com.cn

Postcode: 518057

Customer Support Center: (+86755) 26771900 800-9830-9830

Fax: (+86755) 26770801

Email: support@zte.com.cn

* * * *
 Statement

All rights reserved. No part of this documentation may be excerpted, reproduced,

translated, annotated or duplicated, in any form or by any means without the prior written
permission of ZTE Corporation.

and are the registered trade marks of ZTE Corporation. The names and
logos of ZTE products are proprietary logos or registered trade marks. The names of other
products and companies mentioned in this manual may be proprietary to their owners
respectively. Without the prior written permission of ZTE or the owners of third-party trade
marks or trade names, this manual does not grant the reader any permission or right to
use any marker appeared in the manual.

The product described herein conforms to the design requirements of environment

protection and human security. The storage, usage, and discard of the product shall
comply with the manual, related contract, or laws and regulations of related countries.

The actual product may differ from what is described in this standard due to frequent
update of ZTE products and fast development of technologies. Please contact the local
ZTE office for the latest updating information of the product.

For the latest document information, please visit http://support.zte.com.cn

Preface

This ZXG10-BSC (V2) Base Station Controller Engineering Data Setting

Specifications specifies data setting for the ZXG10-BSC (V2) engineering to set
software data more normalized and reasonable so that commissioning tests can be
successfully performed, system can run normally, and system failures by these causes
can be reduced. Hence, maintenance can be easier.
Contents

1 System Hardware Configuration.............................................................................................................1-1

1.1 Server Hardware Configuration.......................................................................................................1-1

1.2 Client Hardware Configuration........................................................................................................1-2

2 MP Software Installation..........................................................................................................................2-1

2.1 Setting Variables in Configuration File Tcpip.cfg...........................................................................2-1

3 Installation of Operating System.............................................................................................................3-1

3.1 Planning Disk Partitions...................................................................................................................3-1

4 Database Installation.................................................................................................................................4-1

4.1 Oracle 8.1.7 Enterprise Edition Installation.....................................................................................4-1

4.2 DB2 Universal Database V8.1 Installation......................................................................................4-1

5 OMCR (V2) Server Program Installation..............................................................................................5-1

5.1 Setting Server Domain, Number, and IP Address............................................................................5-1

5.2 Settings FTP.....................................................................................................................................5-1

5.3 Setting Configuration File Syscfg.ini...............................................................................................5-1

5.4 Setting Configuration File Dbcfg.ini...............................................................................................5-2

5.5 Setting Configuration File Bsccfg.ini..............................................................................................5-3

5.6 Setting Configuration File lmfcfg.ini...............................................................................................5-4

5.7 Setting Configuration File Pmcfg.ini...............................................................................................5-5

5.8 Setting Configuration File Ampcfg.ini.............................................................................................5-5

5.9 Setting Configuration File Define.ini...............................................................................................5-6

6 Configuration Management.....................................................................................................................6-1

6.1 Functions on Configuration Interface..............................................................................................6-1

6.2 Data Configuration Flow..................................................................................................................6-1

6.3 Physical Resource Configuration.....................................................................................................6-1

6.3.1 Configuring MSC Data.........................................................................................................6-1

-i-
 6.3.2 Configuring BSC Data..........................................................................................................6-2

6.3.3 Configuring Abis Interface TIC (BSC).................................................................................6-2

6.3.4 Configuring A-interface TIC.................................................................................................6-2

6.3.5 Allocating HW.......................................................................................................................6-3

6.3.6 Configuring MTP..................................................................................................................6-3

6.3.7 Configuring Physical Site.....................................................................................................6-3

6.3.8 Configuring Radio BSC........................................................................................................6-3

6.3.9 Configuring a Remote Sub-Multiplexing Rack....................................................................6-3

6.4 Radio Resource Configuration.........................................................................................................6-3

6.4.1 Creating Cell Radio Information...........................................................................................6-3

6.4.2 Creating TRX Radio Information.........................................................................................6-4

7 GPRS Data Configuration........................................................................................................................7-1

7.1 Physical Configuration.....................................................................................................................7-1

7.1.1 Setting GPRS Function Switch.............................................................................................7-1

7.1.2 Allocating HW.......................................................................................................................7-1

7.1.3 Configuring BRCH...............................................................................................................7-1

7.1.4 Configuring NSVC................................................................................................................7-1

7.2 Radio Configuration.........................................................................................................................7-2

7.2.1 Selecting Configuration Environment..................................................................................7-2

7.2.2 Configuring GPRS Cell.........................................................................................................7-2

7.2.3 Configuring Channels...........................................................................................................7-3

Appendix A Abbreviations............................................................................................................................A-1

-ii-
1 System Hardware Configuration

1.1 Server Hardware Configuration

To configure server hardware, you need to take database, CPU process capability,
number of managed objects, and response time of system to user order into
consideration so that the system can perform in optimal configuration.

Table System Hardware Configuration-1 shows the typical server hardware

configuration. When designing actual deployment project, you can change the
parameters according to system-related factors and system performance so that the
system can work in different environments. For example, when the number of managed
TRXs is increased, you can increase the CPU frequency, add CPUs and enlarge
memory.

Table System Hardware Configuration-1 Typical System Hardware Configuration (Main Parts)

System Configuration capacity

configure Small Moderate Large Larger

Number of
1 set 2 sets 2 or 3 sets ≥ 3 sets
servers

400 MHz*4
400 MHz*4
CPU 400 MHz*2 400 MHz*8 ≥ 400 MHz*8
400 MHz*4
400 MHz*8
1 GB
1 GB
Memory 512 MB 2 GB ≥ 2 GB
1 GB
2 GB

Disk 40 GB 80 GB 120 GB ≥ 120 GB

Number of In the range of

Smaller than In the range of 20,000
managed 150,000 and Greater than 400,000
20,000 and 150,000
MOs 400,000
Based on large capacity
The configuration is configuration, this configuration is
The configuration is
for dual-server system. for three-server system.
for dual- or three-
The It is recommended to 1) Extend each part (vertically
server system. It is
configuration is use Redundant Arrays extension)
Remarks recommended to use
for single-server of Inexpensive Disks 2) Add more severs (horizontal
RAID to enable
system. (RAID) to ensure high extension)
high speed and high
speed and high reliable 3) RAID is required to enable
reliable data access.
data access. high speed and high reliable
data access

Note: 1) The moderate-, large-, and larger-capacity servers in the table must Sun or Fujitsu servers. The small-capacity servers can be Sun servers,

Fujitsu servers or PCs.

1
 2) In actual design, the disk capacity must be increased for the RAID. The disk capacity is related to the disk type.

1.2 Client Hardware Configuration

PCs are used as clients. The hardware of the client must contain a CPU running at 800
MHz or faster, a hard disk of 10 GB or larger, and a memory of 128 MB or larger.

2
2 MP Software Installation

2.1 Setting Variables in Configuration File Tcpip.cfg

Table MP Software Installation-2 Setting Variables in Configuration File Tcpip.cfg

Variable Sub-item Meaning and description

BSC ID, a non-0 value of BYTE type. This value is not
BscID [MAIN] sensitive to the foreground. OMCR manages multiple
BSCs according to the value.
This variable indicates whether the module works
IsRemote [MAIN] remotely. Value 0 indicates a local module and value 1
a remote module.
This variable specifies the port that the local MP
TcpPort [MAIN] accepts a TCP link creation request. It is 5000 by
default.
This variable specifies the port that the local MP
UdpPort [MAIN]
accepts a UDP request. It is 5001 by default.
This variable specifies the Ethernet card No. that the
TcpCard [MAIN]
local MP finishes a UDP request. It is 1 by default.
This variable specifies the Ethernet card No. that the
UdpCard [MAIN]
local MP finishes a UDP request. It is 0 by default.
UDP SubNet [MAIN] BRP address. It is 14 by default.
Server number. One or more servers can be configured
to a system. A maximum of two servers can be
Server Mno [SERVER]
configured at present. The configuration number is
defined in syscfg.ini.
Server IP [SERVER] Server IP address.
Test server IP address. This IP address cannot be the
Test IP [SERVER] same as those of the server and Local Maintenance
Terminals (LMTs).
LMT Mno [LMT] LMT number.
LMT IP [LMT] IP address of the LMT.
MP module number. If the local MP is the same as this
module number, the system reads its IP address.
Module [MODULE]
Module 1 is the central module and modules 2–9 are
peripheral modules.
Left IP [MODULE] The IP address of the MP in the left slot.
Right IP [MODULE] The IP address of the MP in the right slot.

Note: Use a space instead of a dot (.) between numbers of an IP address.

1
3 Installation of Operating System

3.1 Planning Disk Partitions

Disk partition is based on the number and capacity of hard disks, so the partition
planning varies with disk size.

The following disk partition examples are for systems with two 18 GB hard disks, 1 36
GB hard disk, and two 36 GB hard disks.

Table Installation of Operating System-3 Oracle Database Disk Partitions

Hard disk Disk File system Size

2 18GB hard disks
0 / 1536 MB
2 times of the memory size. It is 1024 MB by
1 Swap
default.
3 /var 512 MB
The first 18GB hard disk
4 /usr 3072 MB
5 /opt 3072 MB
6 /oracleapp 2048 MB
7 /export/home Remaining size of the disk
The second 18GB hard disk 0 /oracleapp/u02 17578 MB
2 36GB hard disks
0 / 1536 MB
2 times of the memory size. It is 1024 MB by
1 Swap
default.
3 /var 1024 MB
The first 36GB hard disk
4 /usr 3072 MB
5 /opt 3072 MB
6 /oracleapp 2048 MB
7 /export/home Remaining size of the disk
The second 36GB hard disk 0 /oracleapp/u02 35156 MB
1 36GB hard disk
0 / 1536 MB
2 times of the memory size. It is 1024 MB by
1 Swap
default.
36GB hard disk 3 /var 512 MB
4 /usr 3072 MB
5 /opt 3072 MB
6 /oracleapp Remaining size of the disk

Note: Partition 2, which is not listed in the table, is the overlap partition. It is the total capacity of the hard disk instead of a partition.

1
 Table Installation of Operating System-4 DB2 Disk Partitions

Hard disk Disk File system Size

2 18GB hard disks
0 / 1536 MB
2 times of the memory size. It is 1024 MB by
1 Swap
default.
The first 18GB hard disk 3 /var 512 MB
4 /usr 3072 MB
5 /opt 5120 MB
7 /export/home Remaining size of the disk
0 /db2/u01 2048 MB (for system tables)
5120 MB (for tables except performance
1 /db2/u02
tables)
The second 18GB hard disk
Remaining size of the disk (for performance
3 /db2/u03
tables)
2 36GB hard disks
0 / 1536 MB
2 times of the memory size. It is 1024 MB by
1 Swap
default.
The first 36GB hard disk 3 /var 1024 MB
4 /usr 3072 MB
5 /opt 5120 MB
7 /export/home Remaining size of the disk
0 /db2/u01 2048 MB
1 /db2/u02 5120 MB
The second 36GB hard disk
3 /db2/u03 Remaining size of the disk
1 36GB hard disk
0 / 1536 MB
2 times of the memory size. It is 1024 MB by
1 Swap
default.
3 /var 512 MB
36GB hard disk
4 /usr 3072 MB
5 /opt 5120 MB
6 /db2 16384 MB
7 /export/home Remaining size of the disk

2
4 Database Installation

4.1 Oracle 8.1.7 Enterprise Edition Installation

Required disk space: 500 MB for system partition, 3 GB for Oracle main directory, and
8 GB for database table space files.

4.2 DB2 Universal Database V8.1 Installation

Required disk space: 270–700 MB for DB2 main directory, and 8 GB for database
table space files.

1
5 OMCR (V2) Server Program Installation

5.1 Setting Server Domain, Number, and IP Address

1. Network Management (NM) domain number: an integer in the range of 1–254.

2. Server number: an integer in the range of 128–139.

3. IP address: the IP address of the server. It can be detected automatically.

The server IP address configured at the client must be the same as this IP
address.

5.2 Settings FTP

FTP user name and password must be identical with the settings of the FTP server.

5.3 Setting Configuration File Syscfg.ini

As the server critical configuration file, syscfg.ini sets such parameters as server
number, NM domain number, IP address and start processes.

Server number, NM domain number, and IP address must be configured according to

network planning requirements.

For a multi-server system, the NMDomain must be the same value on all servers while
the MNo must be different values.

For example:

[LOCAL]

Server = 1

MNo = 131

NMDomain = 198

NMDomainAlias = Domain198

IP = 10.61.113.80

Where,

MNo: OMCR server number.

NMDomain: OMCR server NM domain number.

1
 ZXG10-BSC (V2) Base Station Controller Engineering Data Setting Specifications

NMDomainAlias: OMCR server NM domain alias.

IP: OMCR server IP address.

According to the user needs, the log parameters are configured as follows:

[SYSCFG]

Trace =1

TracePrint = 0

TraceMode = 2

TracePath =/export/home/omc/tmp/log

TraceLev =1

Environment = GPRS

Trace: To enable process log recording, set it to 1; to disable process log recording, set
it to 0.

TracePrint: To enable process log display on the server, set it to 1; to disable process
log display on the server, set it to 0.

TraceMode: Accept the default setting.

TracePath: Set the full path for saving logs.

TraceLev: Set the level for recording logs. Only one level is supported at present. It is 1
by default.

Environment: If the server does not support GPRS configuration, set it to GSM; if the
server does not support GPRS configuration, set it to GPRS.

5.4 Setting Configuration File Dbcfg.ini

As the file for configuring link between server and database, dbcfg.ini sets database
version, user name and password.

For a multi-server system, all dbcfg.ini are identical.

The parameters that require modification are DBVERSION, USERNAME and

PASSWORD.

[DATABASE]

DBMSTYPE: Database type. If the database is Oracle, set it to ORACLE; if the

connected database is DB2, set it to DB2.

DBINSTANCE = OMC

2
 ZXG10-BSC (V2) Base Station Controller Engineering Data Setting Specifications

DIFVERSION = V1.0

DBVERSION = 2.51.01a-756

USERNAME = omc@omc

PASSWORD = omc

DBVERSION: Database version.

USERNAME: Database user name and connection string. Use a symbol (@) to
separate the user name and the connection string.

PASSWORD: Database password.

5.5 Setting Configuration File Bsccfg.ini

Bsccfg.ini configures the link between the server and foreground. This file is
configured on Application Server (AS) only.

Parameters need to be configured include BSCNum, BSCID, ModuleNum,

LocalModuleNum, and IP address and ModuleID.

[GENERAL]

BSCNum = 1

# Number of BSCs in each MP supporting split

MComBsc = 1

# BSC1: Local BSC. All are local modules.

[BSC1]

# BSC ID, that is the Network Element ID.

BSCID = 130

IsRemote = 0

# Number of modules in the BSC.

ModuleNum = 2

# Number of local modules in the BSC.

LocalModuleNum = 2

# IP addresses of the module: the first one is the IP address of the left MP and the
second one is that of the right MP.

IP1 = 192.169.132.1 192.169.132.33

IP2 = 192.169.132.2 192.169.132.34

3
 ZXG10-BSC (V2) Base Station Controller Engineering Data Setting Specifications

IP3 = 192.169.132.3 192.169.132.35

IP4 = 234.234.43.3 234.34.34.34

# Foreground received and sent process IDs.

BmfRecePno = 90

BmfSendPno = 91

# Information of each module. The first module must be the central module, that is
module 1.

ModuleID1 = 1

ModuleID2 = 2

ModuleID3 =9

ModuleID4 = 5

BSCNum: Number of foreground BSCs.

BSCID: Foreground BSC ID.

ModuleNum: Number of foreground modules.

LocalModuleNum: Number of foreground local modules.

IP address: IP address of the foreground.

ModuleID: Foreground module ID.

5.6 Setting Configuration File lmfcfg.ini

Lmfcfg.ini configures FTP user name and password on server.

For a multi-server system, the value of FtpUserName must be identical on all the
servers, so must that of FtpPassword.

Parameters need to be configured include:

[FTPINFO]

FtpUserName = ftpuser

FtpPassword = ftp123

FtpUserName: FTP user name.

FtpPassword: FTP password.

4
 ZXG10-BSC (V2) Base Station Controller Engineering Data Setting Specifications

5.7 Setting Configuration File Pmcfg.ini

Pmcfg.ini configures files relative to performance management parameters.

Parameters need to be configured include LocalMeasFilePath, HistoryDataFilePath and

ImpDataFilePath.

[BAFINFO]

LocalMeasFilePath = /export/home/omc/tmp/pmmeas

[DATABAKUPINFO]

HistoryDataFilePath = /export/home/omc/tmp/pmhist

ImpDataFilePath = /export/home/omc/tmp/pmhist

LocalMeasFilePath: Full path for performance test data files.

HistoryDataFilePath: Full path for history data files.

ImpDataFilePath: Full path for imported files.

5.8 Setting Configuration File Ampcfg.ini

Ampcfg.ini configures files relative to process management parameters.

The [LOAD] section in ampcfg.ini on the database server is as follows:

[LOAD]

MaxLoad = 1

Load1 = DB

[DB]

MaxTakeover=2

Takeover1 = COM

Takeover2 = AP

The [LOAD] section in ampcfg.ini on the application server is as follows:

[LOAD]

MaxLoad = 2 Load1 = COM

Load2 = AP

Apd:

MaxTakeover = 1

Takeover1 = DB

5
 ZXG10-BSC (V2) Base Station Controller Engineering Data Setting Specifications

MaxTakeover: sets the migration function. The value range is 0–2. To disable the
migration function, set it to 0; to enable the migration function with the module that
Takeover1 specified started, set it to 1; to enable the migration function with the
modules that Takeover1 and Takeover2 specified started, set it to 2.

The migration function is available in dual-server system. If the server breaks down or
the network is disconnected when the server is running, the other server automatically
starts the module that should have been running on the peer server to ensure the normal
running of the OMCR (V2) server. For example, if the DB server fails, the AP server
starts the processes in the DB module automatically to ensure the normal running of
the OMCR (V2) server. Other items in ampcfg.ini can be kept unchanged.

5.9 Setting Configuration File Define.ini

If the user need to customize the DB2 installation, you can modify define.ini in the
$OMCHOME/db2sql directory. The parameters that can be modified include:

1. HOSTIP: DB2 server IP address.

2. NODENAME: Node name when the CATALOG space is created. It is OMC by

default.

3. DATABASE: Name of the database to be created.

4. CATALOGPATH: Path of the CATALOG space of the database created.

5. BUFFSIZE: Size of the buffer of the database to be created. It is 60% of the

memory size by default.

6. TEMPDIR: Path of the TEMP space of the database created.

7. TABLESPACEPATH: Path of the OMCR table space to be created. If the path is

null, the table space will be created in different directories. Parameters
MSPACEDIR, FMSPACEDIR, P MSPACEDIR, MISCSPACEDIR, and
TESTSPACEDIR must be set as follows:

CMSPACEDIR=/export/home/omc/db2data/cm

FMSPACEDIR=/export/home/omc/db2data/fm

PMSPACEDIR=/export/home/omc/db2data/pm

MISCSPACEDIR=/export/home/omc/db2data/misc

TESTSPACEDIR=/export/home/omc/db2data/test

8. SCHEMA: Database installation mode. To use small mode, set it to 0; to use

moderate mode, set it to 1; to use large mode, set it to 2. It is 0 by default.

6
 ZXG10-BSC (V2) Base Station Controller Engineering Data Setting Specifications

9. To change the size of a specific table space, you can change the remarked
parameters in define.ini.

7
6 Configuration Management

6.1 Functions on Configuration Interface

Use the integrated configuration management function to configure physical and
elemental radio parameters.

Use the radio resource management function to modify detailed radio parameters.

Use the software loading function to configure the foreground software version.

Use the dynamic data management function to block/unblock timeslots in network test.

6.2 Data Configuration Flow

Fig. Configuration Management-1 illustrates the data configuration flow.

Fig. Configuration Management-1 Data Configuration Flow

The configuration flow is: MSC, BSC → BSC RACK → BSC SHELF → BSC
BOARD, SITE → SITE RACK → SITE SHELF → SITE PANEL, transparent
channel, RADIO BSC → RADIO SITE → CELL → TRX, FHS, RELATIVE CELLS,
and EXTERNAL CELLS.

6.3 Physical Resource Configuration

6.3.1 Configuring MSC Data

1. MSCID: must be identical in configuration.

2. MSC signaling point code: is obtained through specific algorithm at the MSC-
side Originating signaling Point Code (OPC). Suppose the 14-digit OPC is X, Y
and Z. Convert X, Y, and Z to 3-digit (X13X12X11), 8-digit (X10X9X8X7X6X5X4X3)

1
 and 3-digit (X2X1X0) binary values. Add “0” to the beginning of values less than
3 or 8 digits. The three groups of binary values form a 14-digit binary value
X13X12X11 X10X9X8X7X6X5X4X3 X2X1X0. Convert this value to a decimal value F,
which is the value of MSC signaling point code.

6.3.2 Configuring BSC Data

1. MSCID: must be identical in configuration.

2. BSC signaling point code: The BSC signaling point code is obtained through the
algorithm, through which the MSC signaling point code is obtained, at the
Destination signaling Point Code (DPC) of the BSC office direction
corresponding to the MSC. You can set the “Hex test code” to any value. The
“Initialize radio information” option must be selected. The link error correction
parameter must be changed to 1. For other parameters, you can accept the
default settings.

3. Link error correction method: must be set to 1.

6.3.3 Configuring Abis Interface TIC (BSC)

The configuration of the Abis interface TIC must be consistent with the actual physical
connection line.

6.3.4 Configuring A-interface TIC

The configuration of A-interface trunk must meet the engineering design requirements.
According to the load sharing principle, you need to configure No. 7 signaling to the
trunk board uniformly. Where,

1. The BSC N7PCM number must be identical with that of the MSC-side office
direction, or calls cannot get through.

2. If signaling connection exists between the TIC and MSC, you must specify the
corresponding PCM as the signaling link (N7LINK).

3. The BSC Signaling Link Code (SLC) must be identical with that of the MSC-
side office direction, or calls cannot get through.

4. The TCPP communication capacity is limited, so the last PCM interface on the
last TIC on the right cannot be configured when the TIC is in full configuration
state. Otherwise, loading data will fail.

2
 ZXG10-BSC (V2) Base Station Controller Engineering Data Setting Specifications

6.3.5 Allocating HW

HW allocation to such PP boards as TCPP, BIPP, FSPP and NSPP must be consistent
with the actual physical connection line.

6.3.6 Configuring MTP

For 2 MB signaling No. 7 at A-interface, you must set the “Communication board
type" of the MTP parameter to [CMT_ZXG10_2MMTP]. If there are two MTPs, you
must set a same value to the “Communication board type" of the two boards.

6.3.7 Configuring Physical Site

The configuration of the site PCM must be consistent with the actual physical
connection line.

6.3.8 Configuring Radio BSC

The country code and network code must be correct during initial configuration
because no modification command is provided to change a command sent.

6.3.9 Configuring a Remote Sub-Multiplexing Rack

1. To enable a remote sub-multiplexing rack to work normally, you must configure

TICs to slots 12 and 13 on the FM frame.

2. For a rack consisting remote FM, the rack number range is 1–16. The rack
number range is 1–6 for other racks.

3. The TIC on the FM frame must be correspondent to the TIC on the NM frame.

4. Check whether the HW allocated to the NSPP matches the number of PCMs.

5. When only one FM frame is configured to the remote rack and no BATC is
connected, the TICs on the FM frame and NM frame are connected. Once the
command to connect the TICs is executed successfully, the reversed construction
script does not involve connection because no BATC is configured. This is
normal and you can continue the configuration.

6. It is recommended that an NM frame corresponds to a FM frame.

6.4 Radio Resource Configuration

6.4.1 Creating Cell Radio Information

1) The location area code must be identical with the location area code allocated by
the MSC.

3
 ZXG10-BSC (V2) Base Station Controller Engineering Data Setting Specifications

2) MCC, MNC, LAC and CI are unique.

3) Settings of cell type, GSM type and frequency hopping must be consistent with
the information configured.

6.4.2 Creating TRX Radio Information

One and only one BCCH must be configured to a cell.

4
7 GPRS Data Configuration

7.1 Physical Configuration

7.1.1 Setting GPRS Function Switch

To enable the GPRS function, you must change “Environment = GSM” in

$OMCHOME/conf/syscfg.ini to “Environment = GPRS” so that you can configure the
GPRS options.

7.1.2 Allocating HW

The HW allocated to the GIPP and PUC must be consistent with the actual physical
connection line.

7.1.3 Configuring BRCH

1. Add TS according to the BRCH data provided by the SGSN.

BRCH: Frame relay bearer channel, that is the used timeslot number of the
junction circuit.

2. The FRPNOs of the BRCHs connected to the same PUC.

7.1.4 Configuring NSVC

1. To configure the NSVC, you must get the three data, NSEI, NSVCI and DLCI,
from the SGSN.

NSEI: Network service entity identifier, usually corresponding to the BSCID.

NSVCI: Network service virtual connection identifier, indicating the network

service virtual connection between the BSS and SGSN. It usually corresponds to
the NSEI.

DLCI: Data link connection identifier, a concept related to frame relay. It usually
corresponds to the NSVCI.

2. It is recommended to set the “Packet burst size” to 640 KB x Number of

timeslots. If the BRCH has 8 timeslots, set the “Packet burst size” to 640 x 8 =
5120 KB.

1
7.2 Radio Configuration

7.2.1 Selecting Configuration Environment

You can complete a radio configuration either on “radio view” in the integrated
configuration environment or in the radio resource management environment. Both
environments have their advantages and disadvantages.

In the integrated configuration environment, you can complete the configuration

quickly. However, the system will roll back all your settings if a channel you wish to
modify is occupied. Channels are usually occupied and cannot be modified. In this
environment, you cannot modify the timer parameters and dynamic channels.

In the radio resource management environment, you can modify all settings and the
system will never roll back them automatically. In this environment, you need more
time to complete the configuration.

It is recommended that you configure a GPRS cell in the integrated configuration

environment, and then modify channels and timer parameters in the radio resource
management environment. For a new office without existing BTSs, you can complete
the configuration in the integrated configuration environment and never need to worry
about rollback.

It is recommended that you configure a GPRS cell in the integrated configuration

environment, and then modify channels and timer parameters in the radio resource
management environment.

7.2.2 Configuring GPRS Cell

1. NSEI: selects a network service entity.

2. BVCI: BSSGP virtual connection identifier. In an NSE, each GPRS cell is

identified by a unique BVCI. You can set it to SITEID + CELLID. (For
example, you can set the first cell on BSC1 to 11.)

3. Routing Area Identifier (RAI): The routing area is a management unit between
the location area and cell. An RAI range is 0–225. This value is configured at the
BSC, not relative to the SGSN.

4. BRP group:

1) Select the corresponding BRP group. The BRP group number range is 1–6.

2
 ZXG10-BSC (V2) Base Station Controller Engineering Data Setting Specifications

2) Relationship between BRP groups and BRP boards:

BRP boards work N+M backup mode. If the full configuration is 7 BRP boards,
they work in 6+1 backup mode. There is a correspondence relationship between
BRP groups and BRP boards.

The logical number of a BRP board is decided by its start order. The first started
BRP board corresponds to the first BRP group, so there is no fixed relationship
between BRP groups and slot positions.

You can use a data probe to check the R_BRP table of the central module. The
value in the “BRPgroup” field shows the BRP board corresponding to the
current BRP group.

3) Before configuration, you must analyze how many GPRS cells or PS channels a
BRP group can support to the maximum and allocate BRP groups to avoid
unbalanced configuration.

7.2.3 Configuring Channels

1. When the channel and BRP group resources are sufficient, you can configure

1) “1 dynamic channel + 1 static channel” to a 1-carrier frequency cell.

2) “1 dynamic channel + 2 static channels” to a 2-carrier frequency cell.

3) “1 dynamic channel + 3 static channels” to a cell with 3 or more carrier

frequencies.

2. When the channel and BRP group resources are insufficient, you can configure

1) “1 dynamic channel” to a 1-carrier frequency cell.

2) “1 dynamic channel + 1 static channel” to a 2-carrier frequency cell.

3) “1 dynamic channel + 1 static channel” or “2 static channels” to a cell with 3

carrier frequencies.

4) “1 dynamic channel + 2 static channels” to a cell with 4 or more carrier

frequencies.

“1 dynamic channel + 3 static channels”, if available, to improve the network

access speed.

3
Appendix A Abbreviations

Abbreviation Full Name

Abis A-bis Interface
AIPP A Interface Peripheral Processor
AIU A Interface Unit
AUC Access Unit Controller
BAF BSS Adapter Function
BCCH Broadcast Channel
BIE Base station Interface Equipment
BIPP aBis Interface Peripheral Processor
BIU aBis Interface Unit
BOSN Bit Oriented Switching Network
BRP BSSGP RLC/MAC Protocol
BSIA Base Station Interface Adapter
BSC Base Station Controller
BSS Base station Sub System
BSSAP Base station Sub System Application Part
BSSGP Base station Sub System GPRS Protocol
BTS Base Transceiver Station
BVC BSSGP Virtual Connect
CBCH Cell Broadcast Channel
CCCH Common Control Channel
CDF Commands Dispatching Function
CLF Commands Logging Function
CMIP Common Management Information Protocol
CMIS Common Management Information Service
CRF Commands Resolution Function
CS Circuit Switched
DRT Dual-Rate Transcoder
DSP Digital Signal Processor
EDRT Enhanced DRT
EFD Event Forwarding Discriminator
EGSM Extend GSM
ESU Executable Software Unit
FN Frame Number
FR Frame Relay

1
 Abbreviation Full Name
FRP FR Protocol
FTAM File Transfer Access Maintenance
FU Frame Unit
FUC Frame Unit Controller
GGSN Gateway GPRS Support Node
GIPP Gb Interface Peripheral Processor
GIU GPRS Interface Unit
GPRS General Packet Radio Service
GSM Globe System for Mobile communication
GSN GPRS Support Node
HMS ZXIP10-AS HMS
HSN Hopping Sequence Number
LAF Local Access Function
LAPD Link Access Protocol of D-Channel
LMF Local Management Function
LMT Local Management Terminal
MAC Medium Access Control
MAF Management Application Functions
MAIO Mobile Allocation Index Offset
MIB Management Information Base
MIT MO Instance Tree
MF Mediation Function
MKF MMI Kernel Function
MMI Man Machine Interface
MML Man Machine Language
MO Managed Object
MOC Managed Object Class
MOF MO administration Function
MP Main Processor
MS Mobile Station
MSC Mobile Switch Center
MSF Management Support Function
MTP Message Transfer Part
NAF NMC Access Function
NC Network Control
NEF Network Element Function
NMC Network Management Center
NS Network Service
NSVC NS Virtual Circuit
OMC Operation Maintenance Center

2
 ZXG10-BSC (V2) Base Station Controller Engineering Data Setting Specifications

Abbreviation Full Name

OMCR Operation Maintenance Center Radio
OOF Operation Outputting Function
OSF Operations Systems Function
PACCH Packet Associated Control Channel
PAGCH Paging & Access Granted Channel
PCU Packet Control Unit
PDCH Packet Data Channel
PDTCH Packet Data Traffic Channel
PDU Protocol Data Unit
PP Peripheral Processor
PS Packet Switched
PTM Point To Multipoint
PTP Point To Point
PUC Packet Unit Control
PVC Permanent Virtual Circuit
RACH Random Access Channel
RMM Radio Management Module
RLC Radio Link Control
SDCCH Specified Control Channel
SGSN Serving GPRS Support Node
SMB Short Message Broadcast
SMM Service Management Module
SMS Short Message Service
SSF Session Services Function
TC TransCoder
TCH Traffic Channel
TCPP TransCoder unit Peripheral Processor
TIC Trunk Interface Circuit
TMM Transport Management Module
TMN Telecommunication Management Network
TRAU Transcoder and Rate Adaptor Unit
TRX Transceiver
UISF User Interface Support Function
WAF Windows Administration Function
WSF WorkStation Function