05 GU - OC2024 - E01 - 0 ZXSDR BTS Data Configuration 98P

ZXSDR BTS Data Configuration
Contents
1 Overview........................................................................................................................................................1
1.1 SDR Base Station Commissioning Flow.............................................................................................1
2 Commissioning Preparation........................................................................................................................3
2.1 Preparation for Data Configuration.....................................................................................................3
2.1.1 Planning IP Address..................................................................................................................3
2.1.2 Planning Radio Data.................................................................................................................6
2.1.3 Planning Abis Interface Integration Data.................................................................................6
2.2 Other Preparations...............................................................................................................................7
3 Hardware Check...........................................................................................................................................9
3.1 Jumper Switch Check Inside SA Board............................................................................................10
3.2 BBU Power-up/Power-Down............................................................................................................11
4 OMCR Data Configuration.......................................................................................................................13
4.1 BSC Function Creation......................................................................................................................14
4.2 Board Configuration at BSC Side.....................................................................................................16
4.2.1 Creating Abis Interface Board................................................................................................17
4.2.2 Creating IPBB for OMCB Connection..................................................................................21
4.3 IP-Related Configuration...................................................................................................................21
4.3.1 Creating IP Abis Interface of BSC.........................................................................................22
4.3.2 Creating the Interface in BSC to Connect with OMCB.........................................................24
4.3.3 Creating the Interface in BSC to Connect with SDR.............................................................25
4.4 Configuration of BBU Logical Site...................................................................................................34
4.4.1 Creating Logical Site..............................................................................................................34
4.4.2 Creating Cell...........................................................................................................................36
i
4.4.3 Creating TRX..........................................................................................................................38

5 OMCB Data Configuration/Export/Modification...................................................................................41
5.1 Preparation for Data Configuration...................................................................................................41
5.1.1 Checking OMCB Server Configuration File..........................................................................41
5.1.2 Adding Route..........................................................................................................................43
5.2 Data Configuration Flow...................................................................................................................44
5.2.1 Filling Data.............................................................................................................................45
5.2.2 Converting Data......................................................................................................................49
5.2.3 Importing Data........................................................................................................................50
5.2.4 Synchronizing Data................................................................................................................57
5.3 Data Export Flow...............................................................................................................................61
5.4 Data Modification Flow.....................................................................................................................64
5.4.1 Modifying Data Online...........................................................................................................64
5.4.2 Modifying Data Offline..........................................................................................................68
6 Data Configuration in NEGOTIATION Template..................................................................................71
6.1 Configuration Instruction in Corresponding Sheets..........................................................................71
6.1.1 Basic Parameter......................................................................................................................71
6.1.2 Equipment Parameter.............................................................................................................72
6.1.3 Transmission Parameter..........................................................................................................83
6.1.4 Radio Parameter.....................................................................................................................89
ii
1 Overview
1.1 SDR Base Station Commissioning Flow
Figure 1-1 SDR Base Station Commissioning Flow
Figure 1-2 SDR Data Configuration Flow
Chapter 6 Data Configuration in NEGOTIATION Template
2 Commissioning Preparation
2.1 Preparation for Data Configuration
Note:
The configuration data used in this document is for reference only. The onsite planning
data should be used in the actual commissioning of SDR base station.
2.1.1 Planning IP Address

2.1.1.1 E1 Transmission
The IP planning in the example of this guide is shown as Figure 2 -3.
Figure 2-3 IP Planning in IPOE Mode
Refer to Table 2 -1 for the planning of IP addresses.

Table 2-1 IP Data Planning Table (IPOE)
Configuration Item
The
OMP
IP address
of
Physical Location
The OMC2 port on
OMP
3
Configuration
129.18.0.1/24
Remarks
The internal IP address
The
OMP
port
of OMCR Server
(eth6) on SBCX
The OMC2 port
of OMCR Server
(eth4) on SBCX
129.18.0.100/24
139.18.0.100/24
For the OMCB rectified

after
OMCR/OMCB
split, the eth4:1 port is

required
to
be
configured. For the new

office, it is not required.
The
external
address
of
IP
OMCR
The OMC1 port
10.0.18.10/24
(eth3) on SBCX
Server
The
external
address
of
IP
OMCB
The OMC1 port
10.0.18.1/24
(eth3:1) on SBCX
Server
The
interface
IP
address in BSC to
The interface IP on
139.18.0.254/24
IPBB
connect with OMCB

Server
The IP Abis address
The IP of the RPU
(virtual address) on
interface on OMP
118.18.0.1/32
BSC
The
IP address
of
OMCB channel
The
interface
The IP of the RPU
118.18.0.1/32
interface on OMP
IP
address in BSC to
The
IP
of
the
It must be the same as

the IP Abis address.
118.18.1.254/24
interface on EUIP
The Abis interface and

the OMCB interface can
connect with SDR
use either the same

IPBB
IPBBs.
The IP address of SDR
The
IP
of
the
interface on SDR
118.18.1.100/24
or
different
2.1.1.2 FE Transmission
Figure 2-4 IP Planning in IPOE Mode
Table 2-2 IP Data Planning Table (FE)

Configuration Item
Physical Location
The IP address of
The OMC2 port on
OMP
OMP
The OMP port (eth6)
of OMCR Server
on SBCX
The
of OMCR Server
(eth4) on SBCX
OMC2
port
Configuration
Remarks
129.18.0.3/24
129.18.0.1/24
139.18.0.100/24
For
the
OMCB
rectified
after
OMCR/OMCB
the
eth4:1
split,
port
is
required
to
be
configured.
For
the
new office, it is not

required.
The
address
external
of
IP
OMCR
The
OMC1
port
10.0.18.10/24
port
10.0.18.1/24
(eth3) on SBCX
Server
The
address
external
of
IP
OMCB
The
OMC1
(eth3:1) on SBCX
Server
Configuration Item
The
interface
IP
address in BSC to
Physical Location
The interface IP on
Configuration
Remarks
139.18.0.254/24
IPBB
connect with OMCB

Server
The IP Abis address
The
interface
(virtual address) on
address in OMP to
BSC
connect with RPU
The IP address of
he
OMCB channel
address in OMP to
OMCB channel can be
connect with RPU
the same as the IPAbis
interface
IP
IP
118.18.0.1/32
118.18.0.1/32
The IP address of
address, or a different
address.
The
IP
The IP address of the
address in BSC to
interface
IPBB on the Abis
118.18.2.4/30
The Abis interface and

the OMCB interface
connect with SDR
interface
can
same
use either the

IPBB
different IPBBs.
The IP address of SDR
The
IP
of
the
118.18.2.3/30
The gateway address
IPBB_SDR interface
118.18.2.1/30
of SDR
IP address
interface on SDR
2.1.2 Planning Radio Data

Refer to Table 2 -3 for the planning of radio data.
Table 2-3 Radio Data Planning
Parameter Name
Example
MCC
460
MNC
13
LAC
CI
91
NCC
BCC
2.1.3 Planning Abis Interface Integration Data

Refer to Table 2 -4 for the planning of the data for Abis interface integration.
or
Table 2-4 Planning of the Data for Abis Interface Integration

Parameter Description
Example
BSCID
10
GSM Site ID
SDR IP address (GSM)
118.18.1.100
The remote IP of SDR SCTP
118.18.0.1
The remote port No. of SDR SCTP
14595 (14592+Module No.)
OMM gateway address
118.18.0.1
2.2 Other Preparations
Network cable
Two test phones (supporting basic GSM CS & PS services) and the data wires,
SIM cards, and data cards
Personnel and vehicles
3 Hardware Check
Check the items in the following table before site commissioning.
Table 3-5 Hardware Check List
Check Item
Content and Standard
Board Check
The type, number, and location of boards
Check Result
Pass Fail
are consistent with those in the planning.

The internal jumper switches of SA board
Pass Fail
are correctly configured according to the

transmission type.
Input
Power
Supply
Check
The polarity of the input power cable of
Pass Fail
BBU and RU are correct.

The input voltage of BBU and RU is
Pass Fail
between -40VDC and -57VDC.

If BBU and RU use the single-phase 220V
Pass Fail
power supply, the variation range of the

single-phase voltage is between 200 V AC
and 240V AC, and the variation range of
frequency is between 47 Hz and 53 Hz.
Besides, the PSU should be connected to
convert AC to DC for BBU and RU.
Rack Cable Check
The cable from the FS board to RU is
Pass Fail
connected correctly.
There is no crossed or loose connection of
Pass Fail
the antenna jumpers that are connected to

RU.
Check of the Connection
If FE cable is used, the FE cable is
on the Abis Interface
connected to the CC board correctly.

If E1 cable is used, the E1 cable from DDF
Pass Fail
Pass Fail
to the SDR base station is connected

correctly.
Equipment
Check
Power-up
Check the status of boards after they are
Pass Fail
powered on.
The shelves are well grounded.
Pass Fail
3.1 Jumper Switch Check Inside SA Board
For the site that uses 75 transmission, the jumpers on SA should be set as:
X1-X4: short circuit, X5: open circuit, which is the default setting during
product delivery and needs no adjustments.
Figure 3-5 Jumper Setting in 75 Transmission Mode
ON: The jumper is set as short circuit, that is, the jumper is capped. OFF: The jumper is set as open circuit. That is, the
jumper is uncapped.
For the site that uses 120 transmission, the jumpers on SA should be set as:
X1-X4: open circuit, X51-X53: open circuit, X54: short circuit.
10
ON-The jumper is set short-circuited, i.e. the jumper cap is placed on the jumper; OFF-The jumper is set open-circuited,
i.e. the jumper cap is removed.
3.2 BBU Power-up/Power-Down

Purpose
Checking All the boards in BBU whether can be power-up or power-down normally
Procedure
1.
Pull out all the BBU boards, leaving only the PM and FA modules in the slots.
Before power-up, make sure the power switch on the PM panel is set as OFF.
2.
After power-on, set the power switch on the PM panel and ON, and check
whether the RUN indicator of the PM module is ON, and the ALM
indicator is OFF.
3.
Check whether the FAN module runs normally, and whether the PWR
indicator is ON, and the ALM indicator is OFF.
4.
After the fan is powered up and runs normally, insert CC, UBPG, FS, and SA
boards, and observe whether the boards work normally.
5.
Switch off the power system from the power distribution cabinet or PSU, and
observe the status of the boards after the equipment is powered off.
11
Note:
1. When the PM module and each board are powered up, the ALM indicator
flashes in the beginning. It means the boards have not been started yet. It can be
regarded as a normal situation. When the SA board is not inserted, the ALM
indicator on the FA panel remains ON. Connect the power cable of PM before
powering on the shelf. DO NOT insert or extract the power cable when the PM is
powered on.
2. The boards at Slots 1-12 all have two handles, of which the left one has three
gears and the right one is fixed. When extracting a board, first pull the left handle to
the outermost gear, and then pull out the board. To insert a board, first insert it
along the slot, and then push the left handle to the innermost gear and lock the
board.
12
4 OMCR Data Configuration

This chapter describes the data configuration of SDR in OMCR. The data configuration
depends on the planning in 2.1 Preparation for Data Configuration. This chapter
focuses on the following subjects:
BSC Function Creation
Board Configuration at BSC Side
IP-Related Configuration
Configuration of BBU Logical Site

Note:
1. In iOMCRV6.20.711d and later versions, the configuration flow of SDR

transmission parameters in IPOE mode has been greatly improved compared with the
previous versions.
2. If the onsite version is earlier than iOMCRV6.20.711d, configure the SDR data
in OMCR according to Sections 4.1 to 4.4.
3. If the onsite version is iOMCRV6.20.711d or a later version, the transmission
parameters related IPOE in the SDR data configuration can be configured
automatically when the logical base station is created in OMCR. For the other
configuration items, refer to the procedure in Sections 4.1 to 4.4. The detailed method
is shown as follows:
i.
It is not necessary to configure HDLC information when creating the EUIP board.
ii. It is not necessary to create IP Over E1 Configuration, PPP Configuration,

IPAbis Bandwidth Resource Pool, and PPP Bandwidth Pool in IP Related Config.
The above contents in i. and ii. can be created automatically when the logical base
station is created. The method is as follows: Choose IPOE Support in the Basic
Property tab. In the pop-up Transfer Property tab, associate the IP, PCM, and IP Abis
pool ID of the base station, and then click OK. The parameters related to IPOE are
created automatically. Confirm the configuration in the corresponding tab.
13
4.1 BSC Function Creation

Purpose
Configure the BSC Function related to SDR commissioning at BSC side, including
OMCB IP, IPABIS, and OMCB Channel IP, etc.
Procedure
1.
Right-click BSC Managed Element to choose Apply Mutex Right from the
drop-down list as shown in Figure 4 -6.
Figure 4-6 Applying Mutex Right
2.
Double-click BSC Function node as shown in Figure 4 -7.
14
Figure 4-7 Configuration and Management Node of BSC Function
3.
In the window of BSC Function, configure the corresponding parameters as

shown in Figure 4 -8 and Figure 4 -9.
Figure 4-8 BSC Function - Basic Property Tab
15
Figure 4-9 BSC Function - IP Property Tab
Refer to the following table for the description of the parameters:

Parameter Name
OMCB IP
Configuration Tab
Basic property
Content
139.18.0.100
Description
Internal IP of OMCB server.
Configured as eth4:1 IP.
SCTP IP1 of IP
IP Property
118.18.0.1
ABIS
The IP used to communicate

with
site
control
plane.
Configured as the virtual

RPU IP for the Abis interface.
OMCB channel IP
IP Property
118.18.0.1
The IP used to communicate

with
site
operation
and
maintenance plane. For IPOE

site, it must be consistent with
SCTP IP1 of IP ABIS. For
FE
site,
unless
specially
required, it is suggested to be
consistent with SCTP IP1 of
IP ABIS.
4.2 Board Configuration at BSC Side

The section focuses on the configuration of the boards related to SDR in BSC,
including IPBB, DTB, EUIP, etc., which are the interface boards connected with SDR
or OMCB.
16
4.2.1 Creating Abis Interface Board

4.2.1.1 Configuring Board in E1/T1 Transmission Mode on the Abis interface
Purpose
Configure the boards on the Abis interface, including DTB (or SDTB/SDTB2) and
EUIP (the physical board is EIPI).
Procedure
1.
Double-click BSC Rack in Figure 4 -10.
Figure 4-10 BSC Rack Node
2.
Create a DTB for the Abis interface. Add a PCM interface supporting SDR sites.
In the tab of PCM Information, configure the following items as shown in
Figure 4 -11.
17
Figure 4-11 Configuring DTB in PCM Information Tab

Parameter Name
Configuration Tab
Content
Board function type
Basic Information
DTB
PCM type
PCM Information
Type of EUIP
Description
Select Type of EUIP as
PCM type.
Frame mode
PCM Information
Multi frame
Select Multi frame as

Frame mode.
PCM No.
PCM Information
Add
according
this
to
item
onsite
situation.
3.
Create the EUIP board, configure the connection from PCM port to EUIP. In the
tab of HDLC Information, configure the following items as shown in Figure 4
-12.
18
Figure 4-12 Configuring EUIP in HDLD Information Tab

Parameter Name
Configuration Tab
Content
Board function type
Basic Information
EUIP
HDLC No.
HDLC Information
Configure this item according
Description
to the actual situation.

EUIP 2MHW No.
DT Unit No.
DT PCM No.
HDLC Information
HDLC Information
HDLC Information
The 2MHW No. in
EUIP
The Unit No. of
DTB
The E1 No. of DTB

TS Config Informat
HDLC Information
ion
Add the onsite TS resources to
Configure
the
the list on the right list. Unless
connection between
specified, select 1-31 TSs.
EUIP 2MHW TS
and DT PCM TS.
Note:
19
EUIP and the corresponding DTB or SDTB/SDTB2 should be in the same shelf.
4.2.1.2 Configuring Board in FE Transmission Mode on the Abis Interface
Purpose
Configure the IPBB on the Abis interface (the physical board is BIPI or GIPI).
Procedure
Create an IPBB board to provide the Ethernet port (FE or GE) for SDR access. In the
tab of Basic Information, configure the following items as shown in Figure 4 -13.
Figure 4-13 Creating IPBB in Basic Information Tab

Parameter Name
Content
Board function type
IPBB
Backup mode
1+1 backup mode
Channel mode
Channel mode 2
Description
The channel mode depends on the exchange type

connected with IPBB. Select Channel mode 2 if a
100 M switch is used. Select Channel mode 3 if a
20
Parameter Name
Content
Description
1000 M switch is used. In Channel mode 2, the rear
board is RMINC. In Channel mode 3, the rear board
is RGER.
Local port Number
Use all the four internal ports.
Outer Ports in use
Yes
Whether the external ports should be used (If

RMINC is used, Port1 to Port4 is corresponding to
FE1 to FE4. If REGR is used, only Port1 is
corresponding to the GE interface on the rear board.)
Port work mode
Self adaptive
Speed
100M
4.2.2 Creating IPBB for OMCB Connection

The Abis interface and the OMCB interface can use either the same IPBB or different
IPBBs. The configuration method is the same as mentioned previously.
Tip:
In the 1000 M platform, the IPBB on the Abis interface is corresponding to RGER
(1000 M rear board) by default, and the IPBB to connected with OMCB is
corresponding to RMNIC (100 M rear board) by default.
In the configuration of the RGER board, pay attention to the interface rate of the switch
connected to the RGER. If a 100 M switch is used, set the rate as 100 M instead of
1000 M or self-adaptive.
The network ports of the IPBBs connected with OMCB and SDR should be in different
sub-networks.
4.3 IP-Related Configuration

This section focuses on the IP-related configuration, including RPU virtual IP Address,
IPBB_OMCB, IPBB_SDR, or EUIP, IPOE, PPP, and the bandwidth resource pool on
the Abis interface, etc. These parameters are the basic elements for the link
establishment between SDR base station and OMCB.
4.3.1 Creating IP Abis Interface of BSC

Purpose
Create the IP Abis interface for BSC in RPU. The configuration is the same in the E1
and FE transmission modes.
21
Procedure
1.
Double-click IP Related Config in Figure 4 -14.
Figure 4-14 The Node for IP Related Config
2.
Click
to add an Interface as shown in Figure 4 -15.
Figure 4-15 Interface Configuration Tab
3.
Configure the parameters related to IP Abis Interface as shown in Figure 4

-16.
22
Figure 4-16 Creating IP Abis Interface in Create Interface Tab

Parameter Name
Content
Board function type
RPU
IP address
118.18.0.1
Description
Multiple virtual IP addresses can be configured
in RPU, which are used for IPAbis (two IP
addresses can be configured for SCTP and
OMCB Channel), IPA, and IPGb, etc.
Subnet mask
255.255.255.255
The mask should be 255.255.255.255.
Port No.
Default value: 1
If RPU is configured with multiple virtual IP

addresses, the Port Nos. of each IP address
should not be the same.
4.3.2 Creating the Interface in BSC to Connect with OMCB

Purpose
Create the interface in the IPBB of BSC to connect with SDR. This interface applies to
both E1 and FE transmission modes.
23
Procedure
Refer to the procedure to configure the IP Abis interface. Configure the IPBB OMCB
parameters as shown in Figure 4 -17.
Figure 4-17 Creating the IPBB Interface to Connect With OMCB

Parameter Name
Content
Board function type
IPBB
IP address
139.18.0.254
Description
The IP of the IPBB port connected with
OMCB server, and the gateway IP from
OMCB server to SDR.
Subnet mask
255.255.255.0
Port No.
When RGER is used, there is only one

external GE interface in IPBB, the Port
No. is 1. When RMNIC is used, there are
four external FE interfaces in IPBB, the
Port Nos. are 1, 2, 3, and 4.
24
Parameter Name
MAC address
Content
Description
Any value within [00-D0-
Make sure this MAC address is not the
D0-A0-00-00,00-D0-D0-
same as that in the other ports.
A0-9F-FF] or [00-19-C63E-30-10,00-19-C6-4E-300F].
4.3.3 Creating the Interface in BSC to Connect with SDR

4.3.3.1 Configuring Abis Interface in the E1 Transmission Mode
When the E1 transmission mode is used on the Abis interface of SDR base station, two
configuration methods can be used:
1.
Configure the port with serial No.
2.
Configure the port without serial No. The configuration of the port without serial
No. applies to the BSC with more than 200 or 400 sites for the configuration
method. This chapter focuses on the configuration for the port with serial No.
Purpose
When the port is configured with a serial No., create the interface in BSC to connect
with SDR, IPOE, PPP, IPAbis bandwidth resource pool, PPP bandwidth resource pool
(optional).
Knowledge:
When Invalid is selected for MP Flag (hereinafter refers to PPP), the purpose to
configure IPOE is to designate a physical location for the EUIP interface configured in
the last step, that is, to map the EUIP IP address to a PCM port in a certain DTB, as
shown in Figure 4 -18.
25
Figure 4-18 Setting IPOE in PPP Mode
When Valid is selected for MP Flag (hereinafter refers to ML-PPP), even if IPOE is
configured, the physical interface corresponding to the EUIP IP is not designated, until
their connection is configured in PPP Configuration, as shown in Figure 4 -19.
Figure 4-19 Setting IPOE in ML-PPP Mode
Procedure
1.
Configure the EUIP interface.
Configure the interface IP address in BSC to connect with SDR. Refer to RUIP
interface configuration procedure to configure the parameters related to E1 interface, as
26
Figure 4-20 Configuring E1 Interface in Create Interface Window

Parameter Name
Content
Board function type
EUIP
IP address
118.18.1.254
Description
BTS gateway IP, and the actual
IP address in BSC to connect
with base station.
Subnet mask
255.255.255.0
Port No.
191
In the PPP protocol, the valid

Port Nos. are 1-190. In the MLPPP protocol, the valid Port
Nos. are 191-254.
Refer to the following table for the description of the associated parameters:
27
Parameter Name
Port No.
Associated Parameter
Configuration Tab for
Name
Port No.
IP
Over
E1
Description
In the PPP
configuration,
Configuration tab,
PPP configuration
when Invalid is selected

for MP Flag, the Port
No. configured in IPOE
should be consistent
with that in this tab.
In the PPP
Configuration tab,
when Valid is selected
for MP Flag, the Port
No. configured in PPP
should be consistent
with that in this tab.
Configure the IPOverE1 parameters.

Refer to Figure 4 -21 for the IPOE configuration mode.
28
Figure 4-21 Creating IP over E1 Configuration

Parameter Name
Port No.
Content
Description
In PPP protocol, Port No. is an

associated
parameter,
which
is
corresponding to PortNo configured for

EUIP in the Interface tab. In the same
EUIP board, PortNo should be unique.
In ML-PPP protocol, Port No. is an
associated parameter, which is quoted
by Subsystem:module:unit:sunit:port
in the PPP Configuration tab. In the
same EUIP board, PortNo should be
unique. Generally the Port No. starts
from 1.
HDLC No.
Associated parameter
Start TS
The TS resource used in E1 link, which
End TS
31
should be automatically consistent with

the HDLC TS created in EUIP.
Refer to the following table for the description of the associated parameters:
Parameter Name
Port No.
Configuration Tab for
Name
Port No.
IP
Over
configuration
E1
Description
The configuration in
both tabs should be
consistent.
HDLC No.
HDLC No.
Create EUIP board
The configuration in
both tabs should be
consistent.
2.
Configure the PPP parameters.
When Valid is selected for MP Flag, the PPP parameter configuration has two
functions: 1. Associate the multiple PortNo parameters configured in IPOE
Configuration with the EUIP Port No. parameters configured in Interface. 2.
Designate the corresponding SDR for the EUIP port, that is, set the Peer IP of the port.
When Invalid is selected for MP Flag, the PPP parameter configuration has one
function: Designate the corresponding SDR for the EUIP Port, that is, set the Peer IP
29
of the port.
Refer to Figure 4 -22 for the configuration mode when Invalid is selected for MP
Flag.
Figure 4-22 Creating PPP Configuration

Parameter Name
Content
Description
Peer IP
118.18.0.100
BTS IP address
MP No. sign
Valid
In PPP protocol, this parameter

is set as Invalid. In ML-PPP
protocol
(when
configured
with
site
is
multiple
transmission links), Mpno is set

as Valid. The value should be
configured as the corresponding
EUIP Port No.
IP header compression sign
Whether IP header compression

is
30
enabled.
IP
header
Parameter Name
Content
Description
compression can save some
Abis bandwidth. When the IP
header compression sign is
enabled at both BSC and SDR
sides, the function can be valid.
Keep time
If Keep time is 25 s, and Keep

granularity is 5 s, it indicates
the inspection frame is sent in
every 5 s. The message is sent
for 5 times within the Keep
Keep granularity
time, if no ACK message is

received for five successive
times, it indicates the PPP link
is broken.
Create IP Abis bandwidth resource pool as shown in Figure 4 -23.
Figure 4-23 Creating IP ABIS Bandwidth Resource Pool

Parameter Name
IP ABIS Pool ID
Content
1
Description
It should be consistent with Site
31
Parameter Name
Content
Description
ID.
Module No
The resource pool for Module N

can only be used by the site of
Module N.
Attribute
IP over E1
Working mode
Mixed
Uplink config bandwidth
17,200
It should be configured 1-1.5

times of the actual bandwidth.
Downlink config bandwidth
17,200
It should be configured 1-1.5

times of the actual bandwidth.
3.
Create PPP bandwidth resource pool as shown in Figure 4 -24.
Figure 4-24 Creating PPP Bandwidth Resource Pool
Parameter Name
Content
Description
Subsystem:module:unit:sunit:port:MP
Quote
No
Configuration corresponding to the
the
MP
No.
in
PPP
site.
IP Abis bandwidth resource poolID
Quote the IPAbis bandwidth resource

port IP corresponding to the site.
Note:
The purpose to configure PPP bandwidth resource pool is to associate MP No. of the
site with the IPAbis bandwidth resource pool, because the IPAbis bandwidth resource
32
pool ID is required when the SDR site is created in OMCR. After the creation of PPP
bandwidth resource pool, the SDR site in OMCR is mapped to the corresponding
information such as PPP, IPOE, and E1, etc. For the SDR site, in the Configuration
Management window of DTB or SDTB, the SDR site name connected with a certain
E1 cable can be viewed. Or in E1 Trunk Alarm in Alarm Management, the SDR site
corresponding to the E1 can be viewed.
4.3.3.2 Configuring Abis Interface in the FE Transmission Mode
The creation of the FE interface in BSC to connect with SDR is the same as the
creation of the interface in BSC to connect with OMCB. refer to 4.3.2 Creating the
Interface in BSC to Connect with OMCB for details.
4.4 Configuration of BBU Logical Site

SDR data can be divided in two categories:
Physical data: Configured in NEGONIATION or MO table, and imported to OMCB or
LMT through CMX.
Radio data: configured in OMCR or batch_create_sdr.xls.
This section introduces the SDR radio data configuration. It focuses on the
configuration of the basic property and radio information of the SDR site. The basic
property parameters include Site ID, Module No., and Quoted Resource Pool No., etc.
And the radio parameters include cell, TRX, channel, and neighbor cell, etc.
4.4.1 Creating Logical Site

Purpose
Configure the basic property and radio information of the SDR site. The basic property
parameters include Site ID, Module No., and quoted resource pool No., etc.
Procedure
1.
In the OMCR topology tree, create the SDR logical site as shown in Figure 4
-25.
33
Figure 4-25 Creating SDR Site
2.
Configure the parameters related to the site as shown in Figure 4 -26.
Figure 4-26 Creating SDR Site
34

Parameter Name
Site ID
Content
1
Description
This value should be consistent
with
the
GSM
Site
ID
configured in SDR.
Site type
SDR
Module No
The CMP Module No.
IPOE Support
Choose the option according to

onsite
situation.
If
Yes
is
selected, the Transfer Property

window pops up automatically.
The PCM port of the site
connected with BSC can be
configured in this window.
Abis resource dynamic manage
Used when the site is shared by

multiple operators.
CS bandwidth pool
PS bandwidth pool
Abis satellite access type
Select
Non-satellite
ABIS
access, Satellite ABIS access, or

Super site.
Site IP address
SDR IP address
4.4.2 Creating Cell

Purpose
Configure the cell parameters, including the identification codes and frequency band,
etc.
Procedure
1.
In the OMCR topology tree, create the cell as shown in Figure 4 -27.
35
Figure 4-27 Creating Cell
2.
Configure the cell parameters, as shown in Figure 4 -28.
Figure 4-28 Configuring Cell Parameters
36

Parameter Name
Configuration Tab
Content
Cell type
Basic Params1
Macro cell
MCC
Basic Params1
460
Description
Configure this item according to
the actual situation.
MNC
Basic Params1

LAC
Basic Params1
58201

CI
Basic Params1
44440

NCC
Basic Params1
BCC
Basic Params1

Frequency band
Basic Params1
GSM900

4.4.3 Creating TRX

Purpose
Configure the carrier, frequency, channel type, etc.
Procedure
1.
In the OMCR topology tree, create the TRX as shown in Figure 4 -29.
37
Figure 4-29 Creating TRX
2.
Configure the TRX parameters, as shown in Figure 4 -30.
Figure 4-30 Configuring the TRX Parameters

Parameter Name
Configuration Tab
Cell type
Content
Description
Common
TRX
BCCH Mark
Frequency
No
TRX Info
23
38
Configure this item according to the
actual situation.
Port No.
IP Parameters
The value should be unique in the

same BSC.
TRX group No.
IP Parameters
In 1000 M platform environment,

one TRX group supports 35 TRXs
(in
iBSCV6.20.615
versions),
or
iBSCV6.20.614
28
and
and
TRXs
later
(in
previous
versions). In 100 M environment,

one TRX group supports 16 TRXs.
One TRX group can only be
allocated to one DSP.
Local switch port
IP Parameters
39
Required in the local switch.
5 OMCB Data
Configuration/Export/Modification
OMCBV4.11 supports both SDRV4.11 and SDRV4.09 sites. When OMCBV4.11 is
used to support SDRV4.09, the configuration is the same as that in OMCBV4.09. This
guide only focuses on the configuration of SDRV4.11 in OMCBV4.11.
5.1 Preparation for Data Configuration

5.1.1 Checking OMCB Server Configuration File
5.1.1.1 Checking OMCR/OMCB Split Configuration File
Purpose
Make sure the parameters of RB split are configured with correct values.
Procedure
Log in to the OMCB server as the gomcb user, and open the home/gomcb/umssvr/deploy directory.
[gomcb]vi deploy/deploy-010muep.properties
muep-install-issplit=1
1 means OMCR/OMCB split
[gomcb]vi deploy/deploy-030guomcb.properties
muep-common-sbcx-type=1
It refers to OMCB in OMCR/OMCB split
version.
5.1.1.2 Checking the deploy-020sdrmap.properties File
Purpose
Make sure the parameter of omcb-ftpserver-ip is configured with correct address.
Procedure
1.
Log in to the OMCB server as the gomcb user, and open the
home\gomcb\ums-svr\deploy directory.
41
2.
Check the contents of the deploy-020sdrmap.properties file, and set

the IP address of OMCB. Modify relevant contents according to the type of the
SDR managed by the OMCB and the connection between SDR and BSC.
$vi deploy-020sdrmap.properties
Refer to the followings for modifications:

Parameter Name
userdefined-zxwomc-common-
Content
Description
139.18.0.100
It is the internal IP of OMCB,
nodeb-api.omcb-ftpserver-ip
and
should
according
be
to
configured
the
actual
planning.
3.
Save the configuration and exit.
5.1.1.3 Checking deploy-999split.properties File

Purpose
Make sure the external and internal IP of OMCB address are configured rightly in the
deploy-999split.properties file,.
Procedure
1.
Log in to the OMCB server as the gomcb user, and open the
home\gomcb\ums-svr\deploy directory.
2.
Check the contents of the deploy-999split.properties file, and set the

IP address of OMCB. Modify relevant contents according to the type of the SDR
managed by the OMCB and the connection between SDR and BSC.
$vi deploy-999split.properties
3.
See the followings for modifications:

Parameter Name
ums.systemproperty.com.zte.u
Content
10.0.18.1
ms.uep.localaddress
Description
It is the external IP of OMCB, and should
be configured according to the actual
planning.
ums.systemproperty.com.zte.u
139.18.0.100
ms.bind.socket.client.ip
It is the internal IP of OMCB, and should

be configured according to the actual
planning.
ums.services.bind.multi.local.a
139.18.0.100,*.*.*
ddresses
The first one is the internal IP of OMCB,

and should be configured according to the
actual planning.
42
4.
Save the configuration and exit.
5.1.1.4 Checking deploy-default.properties File

Purpose
Check the setting of the FTP port.
Procedure
1.
Log in to the server as the gomcb user.
$cd ums-svr\deploy
2.
Open the deploy-default.properties file.
$vi deploy-default.properties
3.
Search the userdefined-uep-psl-ftpserver.port field in the file.

Make sure the value of the field is the same as that set for the ftpserver port
enabled for OMCB service. Keep the default value 20021.
userdefined-uep-psl-ftpserver.port=20021
5.1.2 Adding Route

Purpose
According to the IP planned in Section 2.1.1 Planning IP Address, the IP of the
OMCB server is not in the same subnetwork as the SDR IP. Therefore, it is necessary
to add the route from the OMCB gateway to the subnetwork of the SDR.
Procedure
1.
Adding Routes
The OMCB server IP is 139.18.0.100. The gateway address (the IPBB_OMCB

address) is 139.18.0.254. The IP address of the SDR is in the subnetwork
118.18.0.0. Add a route from OMCB (that is, SBCX) to connect with the SDR IP
subnet with the following command:
#route add net 118.18.0.0 gw 139.18.0.254 netmask 255.255.0.0 eth4
2.
Check the route status.
After the route is added, check the route status with the netstat nr command.
3.
Set a permanent route.
43
After adding the route with the route add command, edit the /etc/rc.d
/rc.local file as the root user and add the following line into the file, so as
to avoid the route loss due to SBCX reboot.
#route add net 118.18.0.0 gw 139.18.0.254 netmask 255.255.0.0 eth4
In this way, the route will be added automatically whenever SBCX is booted.
4.
Verify the route after adding it.
Exit from all processes, and reboot SBCX. Then, check again whether the route
works normally with the netstat nr command.
Make sure the SDR IP can be connected successfully with the ping command
from SBCX.
5.2 Data Configuration Flow

This section introduces the data configuration flow for the new site in OMCBV4.11.
This flow also applies to the all table modification for the site.
There are two methods to configure the site data in SDRV4.09 and earlier versions:
1.
Configure the data in the GUI of LMT or OMCB.
2.
Configure the data in the Negotiation template in Excel format, convert the
Excel to xml format with SDRConfTool, and then import the data in xml format
to LMT or OMCB.
In SDRV4.11, the configuration in the GUI of LMT and OMCB is cancelled.

Therefore, the data can only be configured in EXCEL format. The data configuration
flow in the SDRV4.11 series versions is also different from that in the previous
versions. Refer to Figure 5 -31 for the detailed configuration flow.
44
Figure 5-31 Data Configuration Flow in OMCBV4.11
As shown in the above figure, the data configuration flow of OMCBV4.11 mainly
includes four phases: filling data, converting data, importing data, and synchronizing
data. The detailed procedure of each phase is shown as follows:
5.2.1 Filling Data

LMT and OMCB in V4.11 does not support GUI configuration. The data can only be
configured in the EXCEL template and then imported to LMT or OMCB.
5.2.1.1 Selecting Template
For SDRV4.11, there are two types of EXCEL template for data configuration,
45
including MO Template and NEGOTIATION Template.

MO Template
The MO Template contains all MO data for site configuration. It consists of many
sheets and is very complicated in configuration. In actual application, the data is not
configured in MO Template directly. It serves as the supplementary table of the
NEGOTIATION Template. The parameters that cannot be configured in the
NEGOTIATION Template will be filled in the MO Template.
NEGOTIATION Template (or PLAN Template)
The NEGOTIATION Template is similar to the templates in the previous versions.
Many default parameters are omitted, and many parameters are automatically
associated. Therefore, only some necessary data needs to be filled on site, and it is
applicable to most sites.
In OMCBV4.11.10.08P05 and the previous OMCBV4.11 series versions,

NEGONIATION Template and MO Template are released in OMCB and LMT
packages, and both templates can be imported to OMCB or LMT through CMX.
If the NEGOTIATION Template is required to be imported, it will be converted
to MO Template by CMX automatically.
1.
In OMCB version package, the directory of MO Template and NEGOTIATION

\ums-clnt\deploy\template\CMX
2.
In LMT version package, the directories of MO Template and NEGOTIATION

i.
MO Template is in the copy_version\config\ directory. The file name is

as follows:
ii.
NEGOTIATION Template is in the copy_version\config\conf\r08

46
directory. The file name is as follows:
Tip:
1. The above templates in different versions may not be in the same directories as
mentioned above. Search NEGONIATION*.xls or MO*.xls in the ums-clnt directory
of OMCB client or the copy_version directory of LMT to confirm the location of the
template.
2.
Both MO Template and NEGOTIATION Template have the Chinese and
English
versions.
For
example,
SDR(GU)_4.11_CM_NEGONIATION_TEMPLATE_V4.11.10.14.xls
is
if
the
English
version,
SDR(GU)_4.11_CM_NEGONIATION_TEMPLATE_V4.11.10.14_CN.xls is the
Chinese version.
iii. In the copy_version\Template and

copy_version\Negotiation_template\ directories of LMT, there are
many NEGOTIATION Templates applicable to different scenarios. The sample
data of the each scenario is filled in the corresponding template, which serves as
the reference for onsite data configuration. Refer to Figure 5 -32 for details.
Figure 5-32 Data Configuration Templates in Different Scenarios
For
OMCBV4.11.10.08P06
and
later
versions
(such
as
OMCBV4.11.10.14 and OMCBV4.11.10.15, etc.), the conversion from

47
NEGOTIATION Template to MO Template is completed in the SDRConfTool

independently. Only the MO Template can be imported to OMCB or LMT
through CMX.
NEGOTIATION
Template
in
directory
\template\v4.11.10.14
(NEGOTIATION
Template
OMCBV4.11.10.14
in
of
the
OMCBV4.11.10.08
is
released
SDRConfTool
is
released
in
the
package.
in
the
\template\v4.11.10.08 directory of the SDRConfTool package.)
5.2.1.2 Filling in Template

Fill SDR configuration data in NEGOTIATION Template or MO Template.
It is not suggested to configure data in MO Template directly, because there are lots of
parameters to be filled in, and the constraint relation between sheets is very
complicated. Refer to MOM User Guide in the \umsclnt\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-cmwsf.par\res\info directory for detailed filling instruction of MO Template.
5.2.2 Converting Data

The NEGOTIATION Template with all the configuration data cannot be imported to
OMCB directly. Use SDRConfTool to convert NEGOTIATION Template to MO
Template, and then import the data to OMCB.
ZXSDRConfTool_v4.1.0 can be used to convert NEGOTIATION Template to MO
Template, or MO Template to NEGOTIATION Template. The directories of
SDRConfTool are shown in the following figure. NEGOTIATION Templates for
different versions supported by the SDRConfTool is saved in the template directory.
The run.bat file is the program to run the tool.
48
Purpose
Convert the local NEGOTIATION Template completed to MO Template.
Procedure
1.
Double-click run.bat, and the following window pops up.
2.
Click the button of Import Negotiation File to choose the NEGOTIATION

Template with the configuration data. Click the button of Export SDR MO File
to set the name and path of the exported MO Template. (for the data
modification in existing network, click the button of Synchronized SDR MO
File to choose the original MO Template exported from the existing network.)
Choose en_US for English MO Template to be exported or zh_CN for the
Chinese one in the Language column. )
3.
Click Execute to start data conversion.
5.2.3 Importing Data

Data import is performed in CMX. CMX is short for Configuration Management
49
expert. It is integrated in LMT and OMCB, providing data import and export interface
and perform validity check of the configuration data.
In OMCBV4.11.10.08P05 and earlier versions, NEGOTIATION Template can be
imported to OMCB through CMX. During the operation, the NEGOTIATION
Template is converted MO Template automatically.
In OMCBV4.11.10.08P06 and later versions, such as MCBV4.11.10.14 and
OMCBV4.11.10.15, only MO Template can be imported to OMCB, but not
NEGOTIATION Template.
Purpose
Import the local MO Template to CMX and generate xml file.
Procedure
1.
In Configuration Management > SDR Configuration Management, choose

CMX-OMCB to start CMX.
Figure 5-33 Starting CMX
2.
In the window of CMX-Wizard, choose Import Data File, and then click Next.
50
Figure 5-34 Importing Data
3.
Click
to choose the file to be imported. In the drop-down list of
Matched base station, choose Modify main configset or Create new

configset.
Figure 5-35 Choosing File and Matched Base Station
51
4.
If Modify main configset is chosen, click Next to start data verification. If the
verification fails, the Exception Detail button will be shown in the red box as
shown in Figure 5 -36. Click this button to view the detailed error information.
If the verification is passed, the window of Figure 5 -37 will be opened.
Figure 5-36 Verifying Data (Modifying Main Configset)
5.
In the window of successful verification, double-click the NE (as marked in red

box in Figure 5 -37), to query the modified parameters (as shown in Figure 5
-38).
52
Figure 5-37 Verifying Data Successfully (Modifying Main Configset)
Figure 5-38 Querying Modified Data (Modifying Main Configset)
In Figure 5 -37, click Next. (If the mutex right has not been applied, the window of
Apply mutex right will pop up. Select the corresponding NE to apply mutex right.)
Data import progress bar will be shown. After the data is imported successfully, the
Next button will be changed to Finish as shown in Figure 5 -39. Click Finish to
complete the data conversion.
53
Figure 5-39 Importing Data Successfully (Modifying Main Configset)
6.
If Create new configset is chosen, click Next to start data verification. If the
verification fails, the Exception Detail button will be shown in the red box as
shown in Figure 5 -40. Click this button to view the detailed error information.
If the verification is passed, the window of Figure 5 -41 (the NE exists in
OMCB) or Figure 5 -42 (the NE does not exist in OMCB) will be opened.
Figure 5-40 Verifying Data (Creating New Configset)
54
Figure 5-41 Verifying Data Successfully 1 (Creating New Configset)
Figure 5-42 Verifying Data Successfully 2 (Creating New Configset)
In Figure 5 -41 or Figure 5 -42, click Next and the following dialog box pops up. It
prompts the Batch Offline Reverse will be started, and CMX will be closed
automatically.
55
Figure 5-43 Prompt for Closing CMX
5.2.4 Synchronizing Data

5.2.4.1 Batch Offline Reverse
Purpose
Import the xml file generated by CMX into the database of OMCB, belonging to the
target SDR .
Procedure
1.
In Figure 5 -43, click Yes, and dialogue box of Batch Offline Reverse of OMCB
will pop up.
Figure 5-44 Batch Offline Reverse
2.
Set the ConfigSet Label to be imported and the corresponding Subnetwork.

Click OK and the following dialogue box pops up.
56
Figure 5-45 Successful Batch Offline Reverse
3.
Click OK, a box pops up indicating whether to switch the successful configset
from slave to master state. Click Cancel to complete Batch Offline Reverse, or
click OK to continue with the following procedure.
Figure 5-46 Whether to switch Successful Configset to Master State
4.
If OK is selected in the last step, the following dialogue box pops up. Select the
configsets of the NEs to be switched to the master state.
57
Figure 5-47 Selecting the Site for ConfigSet Switchover
5.
Select the NE to be switched, click OK, and the following dialogue box pops up
indicating the configset switchover is successful. Click OK and Batch Offline
Reverse is successful.
Figure 5-48 Completing ConfigSet Switchover
58
5.2.4.2 Synchronizing Data

Purpose
Synchronize the data in the OMCB database to the actual equipment (SDR) to valid it
in the network.
Procedure
1.
After the successful Batch Offline Reverse, right-click the managed element to
choose Synchronize All Tables or Synchronize Modified Tables.
Note:
In OMCBV4.11, after switching the configset, choose Synchronize Modified Tables

to avoid base station reset due to all table synchronization. However, some parameters
can only be modified in the modified table synchronization mode. The corresponding
prompts will be shown during the modified table synchronization.
Figure 5-49 Synchronizing Data
59
5.3 Data Export Flow

Purpose
Export the data of one SDR from OMCB database to local client, the export file is MO
Template.
Procedure
1.
In Configuration Management, open the SDR Configuration Management

menu, and click CMX-OMCB, as shown in Figure 5 -33.
2.
In the window of CMX-Wizard, choose Export Data File, and then click Next,
as shown in Figure 5 -50.
Figure 5-50 Clicking Export Data File
3.
Click the site to be exported, set the name and path of the file to be exported. In
order to export the slave configset, choose the check box of Export slave
Configsets. In order to export the master configset, clear this check box. Click
Next.
60
Figure 5-51 Setting Export Properties
4.
If the check box of Export slave configsets is not chosen, the export result will
prompt in the pop-up window as shown in Figure 5 -52 and Figure 5 -53.
Figure 5-52 Failure to Export Master Configset
61
Figure 5-53 Exporting Data Successfully
5.
If the check box of Export slave configsets is chosen, click the item in the
configset column of any line as shown in Figure 5 -54, and choose one of the
configset of the site from the drop-down list. Type Configset userlabel to locate
a certain configset.
Figure 5-54 Choosing Slave Configset
6.
If an error occurs during data export, the Exception Detail button will be shown
in the CMX window as shown in Figure
5 -55. Click the button to view the
cause of the error. If no error occurs, the successful export prompt will pop up as
62
Figure 5-55 Failure to Export Slave Configset
5.4 Data Modification Flow

5.4.1 Modifying Data Online
Purpose
Modify data of one SDR in OMCB database, such as adding records, deleting records
or modification some value in existing records.
Procedure
1.
In Configuration Management, open the SDR Configuration Management

menu, and click CMX-OMCB as shown in Figure 5 -33.
2.
In the window of CMX-Wizard, choose Modify Data File, and then click
Next.
63
Figure 5-56 Choosing Modifying Data File
3.
Choose the site to be modified, and click Next.
Figure 5-57 Choosing the Site to Be Modified
4.
Click Edit, the 411_ALLDATA.xls template (the MO Template for the

64
chosen site) will pop up. Modify the template, and then save and close the
template. Click Next.
Figure 5-58 Editing MO Template
5.
Two progress bars for data conversion, verification and comparison will be
shown in the window. If the data is not correct, the Exception Detail button will
be shown in the red box of the following figure. Click the button to view the
detailed error information.
65
Figure 5-59 Converting, Verifying, and Comparing Data
6.
If the data is correct, the following window will be open. In this window,
double-click the NE to view the specified parameters modified in the above
steps.
Figure 5-60 Viewing Modified Parameters
7.
In the above figure, click Next, and the data import progress bar will be shown.
66
After the data is successfully modified, the Next button will be changed to
Finish button. Click Finish to complete data modification.
Figure 5-61 Completing Data Modification
5.4.2 Modifying Data Offline

In the scenario where lots of data needs to be modified, it is suggested to modify data
offline, that is, to export data to local environment, and modify it.
Purpose
Modify data in local NEGOTIATION Template or MO Template.
Procedure
1.
Export the MO Template with the configuration data to the client in the PC
according to 5.3 Data Export Flow.
2.
If the data to be modified is not included in the NEGOTIATION Template,

modify the data in the MO Template.
3.
If the data to be modified is included in the NEGOTIATION Template, use

SDRConfTool to convert MO Template to NEGOTIATION Template, and then
convert NEGOTIATION Template to MO Template.
i.
Open SDRConfTool, click the Export tab.

67
ii.
Click the button of Import SDR MO File to choose the MO Template to be

converted. Click the button of Export Negotiation File to set the name and path
of NEGOTIATION Template to be generated. Choose en_US (English) or
zh_CN (Chinese) for Language.
iii. Click Execute to start converting MO Template to NEGOTIATION Template.

iv. Modify the NEGOTIATION Template, and save it. Convert the NEGOTIATION
Template to MO Template.
v.
Click the Import tab of SDRConfTool.
68
vi. Click the button of Synchronized SDR MO File to choose the original MO
Template exported from the existing network. Click the button of Import
Negotiation File to choose the modified MEGOTIATION Template. Click the
button of Export SDR MO File to set the name and path of the MO Template to
be generated. Choose en_US (English) or zh_CN (Chinese) for Language of
the template.
vii. Click Execute to start converting NEGOTIATION Template to MO Template.
4.
Import the modified MO Template to OMCB or LMT.
69
6 Data Configuration in NEGOTIATION

Template
6.1 Configuration Instruction in Corresponding Sheets
The same as SDRV4.09, the configuration data in SDRV4.11 can also be separated
into four categories, including basic parameter, equipment parameter, transmission
parameter, and radio parameter.
6.1.1 Basic Parameter

6.1.1.1 SubNetwork
Fill in SUBNETWORK_ID and SDR_VERSION in the SubNetwork sheet.
Refer to Table 6 -6 for filling instructions.
Table 6-6 Filling Instruction of SubNetwork Sheet
Parameter Name
Content
SUBNETWORK_ID
Description
The ID when Subnetwork is
created in OMCB
TEMPLATE_VERSION
4.1.0
Not required to be modified
SDR_VERSION
4.11.10.14P04
Not required to be modified
6.1.1.2 Base Station

Fill in the information related to the base station in the Base Station sheet, including
BTS_NAME, NE_ID, NE_IP, SDR_TYPE, and BSC_ID.
Refer to Table 6 -7 for filling instructions.
Table 6-7 Filling Instruction of Base Station Sheet
Parameter Name
Content
Description
BTS_NAME
Site Name
NE_ID
NE ID, corresponding to ManagedElement ID

in OMCB.
NE_IP
Base station IP, not required for IPOE site.
SDR_TYPE
Base station type, make the choice according

71
Parameter Name
Content
Description
to onsite situation (such as BS8900A, BS8800

GU360, etc.), for the CRAN site, choose
BS8700.
BSC ID where the base station is connected
to.
BSC_ID
6.1.2 Equipment Parameter

6.1.2.1 Clock
Fill
in
the
general
properties
of
site
clock
synchronization,
including
CLOCK_SYNC_MODE, and parameters related to GPS clock synchronization.

Table 6-8 Filling Instruction of Clock Sheet
Item
NE_ID
Parameter Name
Network Element ID
Value Range
Corresponding to the NE_ID in Base
Station sheet.
CLOCK_PRIORITY
Clock Source Priority
Value range: 1 to 8.
The priority of clock reference resource. 1
refers to the top priority.
CLOCK_TYPE
Clock Source Type
Refer to Table 6 -9 for the description of

clock resource values.
If GNSS reference source is configured,
and CLOCK_SYNC_MODE is not 0:
GSM/UMTS Frequency Sync, only GNSS
reference
source
is
allowed
to
be
configured.
Generally, LINE is used in IPOE mode,
and 1588 is used in FE mode.
CLOCK_SYNC_M
Clock Synchronization Mode
ODE
0: GSM/UMTS Frequency Sync

1: GSM FrameNumber Sync. UMTS
Frequency Sync
2:
GSM
Frequency
Sync.
UMTS
FrameNumber Sync
3: GSM/UMTS FrameNumber Sync
GPS_CABLE_TYP
GPS Cable Type
E
GPS_RECEIVER_T
0: Multiplexing input
1: Distribution input
GPS Receiver Type
YPE
1: GPS
2: GLONASS
3: GPS+GLONASS
72
Item
Parameter Name
Value Range
GPS_CABLE_DEL
Length of Cascade cable(m)
Integer: 0 to 15.
Enable SSM
Y: Yes
AY
CLOCK_SSM
N: No
Must be configured if CLOCK_TYPE is
SyncE
Table 6-9 Value Description of Clock Reference Source

Value
Description
Internal GNSS
Internal GNSS
External GNSS
External GNSS
Cascade GNSS
Cascade GNSS
1PPS+TOD
1PPS+TOD
BITS-2MHz
BITS-2MHz clock
BITS-2Mbps
BITS-2Mbps clock
Line
Line clock: CC board of BBU
1588
IP clock reference source. The IP for 1588 clock

synchronization
with
the server must be
configured.
SyncE
SyncE clock.
6.1.2.2 IpClock
Table 6-10 Configuration Instruction for Parameters Related to IEEE1588 Clock
Item
NE_ID
Parameter Name
Network Element ID
Value Range
Station sheet.
LINK_PRIORITY
Link Priority

Link priority of IP clock
TRANS_TYPE
IP Clock Transmission Mode
Transmission mode of 1588 clock

message
0: Multicast
1: Unicast
IPCLK_SYNC_SERV
IP Address of 1588 Clock
Must be configured for IP 1588 clock
ER_IP
Sync Server
reference source. Valid only when it is IP

over Ethernet transmission type.
IPCLK_IP_NO
IP Link No. of 1588 Clock

73
INTEGER: 0 to 19. Existed in IP sheet.
Item
Parameter Name
Value Range
Sync Channel
6.1.2.3 Time
Table 6-11 Filling Instruction of Time Sheet
Item
Parameter Name
NE_ID
Value Range
Network Element ID
Corresponding to the NE_ID in

Base Station sheet.
NTP_SERVER_IP
NTP Server IP Address
This item must be filled in.
TIME_ZONE
Time Zone
This item must be filled in.
SUMMER_TIME_START
Summer Time Start
Pattern: MM-DD HH:mm. Fill

in '0' if it is not used.
SUMMER_TIME_END
Summer Time End
Pattern: MM-DD HH:mm. Fill

in '0' if it is not used.
6.1.2.4 Equipment
Fill in base station hardware information in the Equipment sheet, including
RADIO_MODE, board information in each slot, RACK_TOPOLOGY, and clock
resource information.
Refer to Table 6 -12 for the parameter description. SHELF2_BBU is configured for
stacked BBUs. Currently all the V4.11 series versions support B8200 stack, but the
current versions do not support B8300 stack.
Table 6-12 Filling Instruction of Equipment Sheet
Item
Parameter Name
Value Range
NE_ID
Network Element ID
Network Element ID
TELECOM_OPERATOR
Telecom Operator
127 bytes at most, without & ' " < > #

%
OPERATOR_PLANNED_ID
Network
Element
planned by operator
ID

%
Operator plans the unique network
element ID for base station. Do not
set the parameter if it is not planed.
This parameter can be configured in
V4.11.10.14 and later versions.
74
Item
VENDOR_PLANNED_ID
Parameter Name
Network
Element
planned by vendor
Value Range
ID

%
Vendor plans the unique network
element ID for base station. Do not
set the parameter if it is not planed.
RADIO_MODE
Radio Mode
UMTS, GSM, GSM+UMTS
BBU_TYPE
BBU Type
BBU Type (BBU-2U refers to B8200,

BBU-3U refers to B8300, DIET can
only be configured for BS8908.)
BBU_SLOT_1
BBU Slot 1
If the physical board is CC0 or CC2,

select CC. If the physical board is
CC16, select CCC. TRB related
options can only be configured for
BS8908.
BBU_SLOT_2
BBU Slot 2
BBU_SLOT_3
BBU Slot 3
BBU_SLOT_4
BBU Slot 4
BBU_SLOT_5
BBU Slot 5
BBU_SLOT_6
BBU Slot 6
BBU_SLOT_7
BBU Slot 7
BBU_SLOT_8
BBU Slot 8
BBU_SLOT_9
BBU Slot 9
Configure UBPG in this slot only

when BBU Type is BBU-3U.
Configure this slot only when the

BBU Type is BBU-3U.
BBU_SLOT_10
BBU Slot 10

BBU Type is BBU-3U.
BBU_SLOT_11
BBU Slot 11

BBU Type is BBU-3U.
BBU_SLOT_12
BBU Slot 12

BBU Type is BBU-3U.
BBU_SLOT_14
BBU Slot 14
Configure SE in this slot only when

the BBU Type is BBU-3U.
BBU_SLOT_15
BBU Slot 15
BBU_SLOT_16
BBU Slot 16

BBU Type is 3U.
BBU_SLOT_17
BBU Slot 17

BBU Type is 3U.
SHELF2_BBU_SLOT_1
Shelf 2's BBU Slot 1

75
Configure the boards for the second
Item
Parameter Name
SHELF2_BBU_SLOT_2
SHELF2_BBU_SLOT_3
SHELF2_BBU_SLOT_4
SHELF2_BBU_SLOT_5
SHELF2_BBU_SLOT_6
SHELF2_BBU_SLOT_7
SHELF2_BBU_SLOT_8
SHELF2_BBU_SLOT_14
SHELF2_BBU_SLOT_15
RACK_TOPOLOGY
Rack Topology
Value Range
stacked BBU.
Example: 1-2-3, 1-4, 1-51-52, it

means RSU 2 and RSU 4 are
connected to the main rack, RSU3 is
cascaded with RSU2, RRU51 is
connected to the FS optical port, and
RRU52 is cascaded with RRU 51.
In the ring network, the rack topology
can be shown as 1-51-52-1.
RU02 and R8890 series boards do
not
support
cascade
connection.
R8882-S9000C and R8882-S1800C

can be configured in 18 cascade
levels, while the other RF boards can
be configured in four cascade levels
at most. Do not fill in this item if the
cascade is not used.
GSM single-mode sites can also use
the UBPG2 at Slots 3, 4, and 8 as the
upper-level optical port, provided that
the FS board is not configured and
UBPG/UBPG2 is not configured at
the other slots except Slots 3, 4, and
8.
FS3_OPTICAL_MODULE_T
Optical Module Type of
1.25G, 2.5G, 3G, 6G. Default value:
YPE
FS in Slot 3
1.25G. If the rates of the first three

optical ports are different from the
rates of the last three ones, separate
the values with comma, for example:
6G, 1.25G.
FS4_OPTICAL_MODULE_T
Optical Module Type of
1.25G, 2.5G, 3G, 6G. Default value:
YPE
FS in Slot 4
1.25G. If the rates of the first three

optical ports are different from the
76
Item
Parameter Name
Value Range
rates of the last three ones, separate
the values with comma, for example:
6G, 1.25G.
Note:
In both B8200 and B8300, Slot 13 is configured with SA board fixedly. This board
must be configured, although it is not configured in the NEGOTIATION Template, it is
configured automatically when the NEGOTIATION Template is imported to OMCB
through CMX.
6.1.2.5 RU
Fill in the basic RU properties in the RU sheet, including radio mode, BOARD_TYPE,
FS_PORT, OPTICAL_MODULE_TYPE, and ANTENNA_TYPE.
Refer to Table 6 -13 for the parameter description in this sheet.
Table 6-13 Filling Instruction of RU Sheet
Parameter Name
Content
Description
NE_ID
Network Element ID
RRU_NAME
RRU Name
RU_NO
RU No.
BOARD_TYPE
Board Type
FS_PORT
The optical port No. of FS/UBPG2. For the FS at

Slot 3, FS_PORT is 0 to 5. For the FS at Slot 4,
FS_PORT is 20 to 25. Refer to the detailed
description in the NEGOTIATION Template.
(CRAN site does not support UBPG2 board.)
OPTICAL_MODULE_TYPE
Optical Module Type

R8860, R8860E, RSU60, RSU60E, RU02 use
1.25G optical ports. R8882 (except R8882C) uses
2.5G optical port. R8882C uses 6G optical port.
The FS optical type should be consistent with that
of RRU.
ANTENNA_TYPE
Antenna Type. ANT:Normal Antenna, RET:Aisg
VSWR_LOWER
VSWR Lower Limit
VSWR_UPPER
VSWR Upper Limit

77
Parameter Name
Content
Description
LOWER_RESUME_LIMIT
Alarm Recovery Lower Limit of VSWR
UPPER_RESUME_LIMIT
Alarm Recovery Upper Limit of VSWR
DIVERSITY_MODE
0: Normal diversity reception

1: Cross diversity reception
Default: 0
This
parameter
can
be
configured
in
6.1.2.6 PaDevice
Configure the power amplifier device of each RU in the PaDevice sheet. Each power
amplifier device occupies one line.
Table 6-14 Filling Instruction of PaDevice Sheet
Item
Parameter Name
NE_ID
Network Element ID
RU_NO
RU No.
Value Range
RSU value range: 2 to 50.
RRU value range: 51 to 201.
Must be configured in the RU
sheet.
PADEV_NO
PA Device No.
Integer: 1 to 3.
The second PA is 2, and the
third PA is 3.
RADIO_MODE
Radio Mode
UMTS, GSM, GSM+UMTS
TRANSMIT_FREQ
Central Downlink Frequency(MHz)
Multiple of 0.2MHz. 0 or
blank represents automatic
calculation by Node B.
6.1.2.7 RxDevice
Configure the receiving devices for each RU in the RxDevice sheet. Each receiving
device occupies one line. The RF receiving extension association or tower amplifier
parameters can also be set in this sheet.
Table 6-15 Filling Instruction of RxDevice Sheet
Item
Parameter Name
NE_ID
Network Element ID
RU_ NO
RU No.
78
Value Range
RRU value range: 51 to 201. RSU value
range: 2 to 50.
RX_PORT_NO
Rx Port ID
RECEIVE_FREQ
Central
Integer: 1 to 6.
Uplink
Frequency(MHz)
Multiple
of
0.2MHz.
or
blank
represents automatic calculation by Node

B. When downlink frequency is not 0,
uplink frequency should not be 0. When
uplink frequency is 0, all the downlink
frequency must be set as 0.
RX_EXTENSION_RU
Rx RF Extension RU
The frequency band of associated RU
No.
should be identical. Each RU can only be

associated once.
The boards of R8882 do not support
extension connection.
RX_EXTENSION_PORT
Rx RF Extension Port
Integer: 1 to 6.
ID
TMA_NO
TMA No.
Value range: 1 to 96. The value should be

unique.
TM_TYPE
Tower Top Amplifier
TMA,A-TMA,A-COM,ETMA,A-ETMA
type
RX_POWER_GAIN
Tower Top Amplifier
TMA: 70 to 150
Uplink Power Gain
A-TMA: 44 to 100
A-COM: 0 to 14
ETMA: 200 to 320
A-ETMA: 92 to 100
Invalid: 65535
TX_POWER_GAIN
Tower Top Amplifier
Downlink
Invalid : 255
Power
Gain(0.1db)
TMA_NOISE
Tower Top Amplifier
Noise
Invalid: 255
Coefficient(0.1dB)
ANT_NO
RET_NO
Connected Mechanical
This field cannot be configured. Do not
Antenna RDN
modify it.
Connected
Antenna RDN
RET

modify it.
6.1.2.8 EPm
Configure the embedded power device in the EPm sheet to analyze and report alarms to
BBU.
79
Table 6-16 Filling Instruction of EPm Sheet

Item
Parameter Name
NE_ID
Network Element ID
EPM_BOARD
Connected Board
Value Range
It indicates the BBU board connected with the
embedded power device (SA or SE).
SA,
SE-SlotNo,
2-SA: SA in shelf 2,
2-SE-SlotNo: SE in shelf 2
EPM_PWR_TYPE
Epm Power Type
Select the product type according to the actual

physical equipment:
ZXDU58 B900
ZXDU58 B121
ZXDU68 B201
ZXDU150
ZXDU45
ZXDU75
ZXDU58 B121(V4.5)
ZXDU68 B201(V5.0) (It can only be configured
in V4.11.10.14 and later versions)
ZXDU68 W301
ZXDU68 S301
ZXDU58 B121(V2.2) (It can only be configured
in V4.11.10.14P02 and later versions)
EPM_DEAL_MO
EPm Data Processing
0: Transparent transmission
DE
Mode
1: Parse
6.1.2.9 Dry Contact

Table 6-17 Filling Instruction of Dry Contact Sheet
Item
NE_ID
Parameter Name
Network Element ID
Value Range
Station sheet.
DRY_CONTACT_POSITI
Dry Contact Position
ON
SA/SE-SlotNo
FCE (1-1-18)
FCE-RackNo: the FCE set in the FCE
sheet
RU-No.: the RU set in the RU sheet
DRY_CONTACT_NO
Dry Contact No.
Dry Contact No. The boards that support

dry contact alarms are SA, FCE boards,
and radio frequency boards.
80
Item
Parameter Name
DRY_CONTACT_USERL
User Label
Value Range
128 bytes at most. Default: null. Without &
ABEL
'"<>#%/\?@:,
DRY_CONTACT_TYPE
Dry Contact Type
Input: Input dry contact. Output: Output

dry contact.
Output dry contact should be linked to Dry
Contact No.6 or 7 of SA/SE.
DRY_CONTACT_CONTE
Dry
Contact
NT
Code
Alarm
Valid to input dry contact. For the userdefined
dry
contact,
NETOGIATION
refer
Template
to
in
the
the
corresponding version.
For user-defined dry contact, the value
range is 198092550 to 198092599.
(In V4.11.10.14, the range of the new userdefined dry contact code is 198096424 to
198096473.)
Note: It is necessary to set user-defined
alarm code in OMCB. The method is
shown as follows:
In Alarm Management, click Alarm
Setting > User-defined Alarm Code
Description Setting, and modify the
description of the code to be used, then this
alarm code can be used in Configuration
Management.
ALARM_STATUS
Dry
Contact
Alarm
Status
Valid only if type is input.

OPEN: Alarm appears if contact is open
CLOSE:Alarm appears if contact is closed
OUT_CONTACT_TYPE
Output Dry Contact
Valid only if type is output.
Status
0: Output low level

1: Output high level
6.1.2.10 PowerOutlet
PowerOutlet refers to the power output port. After the TAM board is configured, the
data in this sheet can be configured.
Table 6-18 Filling Instruction of PowerOutlet Sheet
Item
Parameter Name
Value Range
NE_ID
Network Element ID
TAM_SHELF
TAM Board Shelf No.
TAM_SLOT
TAM Board Slot No.
81
TAM_PORT
TAM Board Port No.
TAM_WORKING_CURRENT
Work Current Value (mA)
Configure the maximum current

value of the specified port.
Value Range
TAM0: 75 to 300
TAM1: 75 to 400
TAM2: 75 to 400
TAM_ALM_MODE
Alarm Detect Mode
0: currentDetect
1: pulsewidthDetect
6.1.2.11 AISG
Table 6-19 Filling Instruction of AISG Sheet
Item
Parameter Name
NE_ID
Network Element ID
AISG_RU_NO
CCU Rack No.
Value Range
RSU value range: 2 to 50. RRU value range:
51 to 201. Must be configured in the RU
sheet.
UNIQUE_ID
Device Serial Number
The
sum
of
UNIQUE_ID
MULTI_ANT_NO should be unique.

DEV_TYPE
Device Type
RETC
MULTI_RET
ATMA
MULTI_TMA
ACOM
AETMA
NSNRET
LGPTMA
VENDOR_CODE
Vendor Code
127 bytes at most.
AISG_VERSION
AISG Version
1.1
2.0
RET_RU_NO
Connected RET Device
Connected RET Device No., the associated
RU No
ANTENNA_TYPE must be RET. Mutually

exclusive to AISG_TMA_NO.
RET_PORT_NO
Connected RET Device
Connected RET Device Port No, configured
Port No
in a pair with RET_RU_NO. Mutually

exclusive to AISG_TMA_NO.
AISG_TMA_NO
Connected TMA Device
Integer: 1 to 96. TMA_NO in the RxDevice
No.
sheet must be configured in advance.

TM_TYPE must be A-TMA, A-COM or A82
Item
Parameter Name
Value Range
ETMA.
Mutually exclusive to RET_RU_NO and
RET_PORT_NO.
MULTI_ANT_NO
Subunits No.
AISG_USERLABEL
Description
FATHER_PORT
Value range: 1 to 4. 255: Invalid.

of
Self-
128 bytes at most, can be blank.
defined Field
Without & ' " < > # % / \ ? @ : ,
Superior Channel
Integer: 0 to 12.
Used for SDTMA device of NSN private
protocol. The value for other devices is 0.
SELF_PORT
Local Channel
Integer: 0 to 12.
Used for SDTMA device of NSN private
protocol. The value for other devices is 0.
6.1.3 Transmission Parameter

6.1.3.1 Transmission
Fill in the transmission information in the Transmission sheet, including
TRANSMISSION_TYPE,
TRANSMISSION_MEDIUM,
ETHERNET_WORK_MODE, and FE_BANDWIDTH, etc.

Table 6-20 Filling Instruction of Transmission Sheet
Item
Parameter Name
NE_ID
Network Element ID
TRANSMISSION_TYPE
Transmission Type
Value Range
Only IP can be chosen for GSM
radio mode.
TRANSMISSION_MEDIUM
Transmission Medium
FE+E1 and FE+T1 are applicable

to GSM/UMTS dual-mode base
stations where the GSM network
and UMTS network use different
transmission routes.
ETHERNET_WORK_MODE
Ethernet Mode
Options: Auto, 1000M, 100M,

10M, 100M-Fiber. Auto means
self-adaptation.
FE_BANDWIDTH
FE_PHYLAYERPORTNO
FE/GE
If the UES board is configured, the
BandWidth(kbps)
maximum bandwidth is 250Mbps.
FE/GE Physical Layer
The
Port No.
corresponding
physical
Different
83
layer
to
port
No.
Ethernet.
from
E1T1_PHYLAYERPORT_NO.
6.1.3.2 ATM
Fill in this ATM sheet if TRANSMISSION_TYPE is ATM or ATM+IP.
Table 6-21 Filling Instruction of ATM Sheet
Item
Parameter Name
NE_ID
Network Element ID
ATM_E1T1_PHYLAYERPORT_NO
ATM
E1/T1
Physical
Layer Port No.
Value Range
Pattern:
portNo,portNo,..
portNo:0 to 17. Must be

configured in E1T1 sheet. 8
ports at most.
ATM_ADDRESS
ATM address
Just fill in the valid length.

Do not fill in this item if the
parameter is not used.
Pattern: digits + ., for
example, 1.1.1.2
6.1.3.3 E1T1
Configure E1T1 physical layer port in the E1T1 sheet. If HDLC or ATM is configured,
this sheet must be filled in.
Table 6-22 Filling Instruction of E1T1 Sheet
Item
Parameter Name
NE_ID
Network Element ID
E1T1_PHYLAYERPORT_NO
E1/T1 Physical Layer Port No.
Value Range
Integer: 0 to 17. Should be
unique
in
the
whole
subnetwork, and different from

FE_PHYLAYERPORTNO.
E1T1_SHELF
E1T1 Board Shelf No.
Integer: 1 to 2.
E1T1_BOARD
E1T1 Board Type
SA
SE-5
SE-14
TRB
Series
(applicable
to
BS8908)
E1T1_PORT
E1/T1 Port No.
Integer: 0 to 7, should be
unique in the whole network.
84
6.1.3.4 HDLC
Fill in HDLC related information in the HDLC sheet, including HDLC_NO,
HDLC_E1T1_PHYLAYERPORT_NO, HDLC_TIMESLOT_MAP, etc. Each NE can occupy
eight lines at most, with one line for each HDLC link. There are four TSI records at
most.
Table 6-23 Filling Instruction of HDLC Sheet
Item
Parameter Name
NE_ID
Network Element ID
HDLC_NO
HDLC Link No.
Value Range
Integer: 0 to 15. Unique within
the same site.
HDLC_E1T1_PHYLAYERPO
E1/T1 Physical Layer Port No.
RT_NO
Integer: 0 to 17.
Must be configured in the
E1T1 sheet.
HDLC_TIMESLOT_MAP
HDLC Timeslot
Except Timeslot 0, Timeslots 131 are available.Pattern: start of

time slot-end of time slot,... For
non-consecutive
timeslots,
separate
segments
different
with comma, for example, 15,10-20.

TSI_IN_TIMESLOT_MAP
TSI In Timeslot
The filling pattern is the same

as that of the HDLC timeslot. It
should not be the same as the
HDLC timeslot.
TSI_OUT_PHYLAYERPORT
TSI Out Physical Layer Port
Value range: 0 to 17. It should
_NO
No.
not
be
the
same
as
the
E1T1_PHYLAYERPORT_NO
(in). Must be configured in the
E1T1 sheet.
TSI_OUT_TIMESLOT_MAP
TSI Out Timeslot
The filling pattern is the same

as that of the HDLC timeslot.
The number of the in-timeslots
must be the same as the number
of the out-timeslots.
TSI_OUT_NO
TSI Out No.
This
field
cannot
configured. Do not modify it.
85
be
6.1.3.5 IP
Fill in the IP related information in the IP sheet, including IP_NO, VLAN and PPP
related information. Fill in this IP sheet if TRANSMISSION_TYPE is ATM or
ATM+IP.
Table 6-24 Filling Instruction of IP Sheet
Item
Parameter Name
NE_ID
Network
Value Range
Element
ID
IP_NO
IP No.
Integer: 0 to 19.
IP_VLAN_ID
IP Vlan ID
Configure this item when FE

transmission
and
VLAN
are
configured. Use the same value as

VLANID of the connected switch
port.
IP_VLAN_IP_ADDR
IP Address
Configure it as the site IP address

in FE transmission mode.
IP_VLAN_MASK
IP Subnet Mask
Configure it as the site IP mask in

FE transmission mode.
IP_VLAN_GATEWAY
IP Gateway Address
Configure it as the site IP

gateway
in
FE
transmission
mode. Generally, it is the port IP

connected with the site.
STATICROUTE_IPADDRESS
Static
Route
Destination
IP
Address
IPV4, or left blank if static route

is not configured.
In PPP mode, static route is not
configured.
STATICROUTE_NETWORKMASK
Static
STATICROUTE_NEXTHOP_IPADDR
PATH_DOMAIN
Route
Network Mask
is not configured.
Static Route Next
Hop IP Address
is not configured.
Path Domain
Integer:
to
invalidUMTS
parameter.
3.
255:
multi-path
The
integration
parameter at OMCR site is:

OMCB module in the OMCB
PATH sheet.
PPP_NO
PPP No.
Integer: 0 to 7. ML-PPP: 0 to 2.
Fill in this item when PPP
transmission is used.
86
Item
Parameter Name
PPP_HDLC_NO
PPP
HDLC
Link
No.
Value Range
Value range: 0 to 15. Separate the
values with comma if there are
two or more Nos, for example
0,1,2.Fill in this item when PPP
transmission is used. Eight links
can be filled in at most.
The
HDLC
link
should
be
configured in the HDLC sheet in

advance. The HDLC used should
contain at least one main link.
PPP_IP_ADDRESS
Base
Station
IP
PPPoE IP address, that is, base
Address
station IP address.
PPP_PROTOCOL
PPP Encapsulation
Select ML-PPP.
PPP_COMPRESSION
Support IP compress
Whether PPP supports IP header
or not
compression or not. Refer to

4.3.3.1
Configuring
Abis
Interface in the E1 Transmission

Mode-
Configure
the
PPP
parameters for details.

MP_HEAD
MP Head
Long: long sequence, Short: short

sequence. Valid in the ML-PPP
mode.
MP_PRIORITY
MP Priority
It is valid when the encapsulation

type is ML-PPP.
6.1.3.6 SCTP
Fill HDLC related information in the SCTP sheet, including SCTP_NO,
SCTP_RADIO_MODE, SCTP_LOCAL_PORT, SCTP_REMOTE_PORT,
SCTP_REMOTE_IP, and SCTP_IP_NO. For GSM or UMTS single mode, each NE
occupies one line. For GSM+UMTS dual-mode, each NE occupies two lines, one for
GSM in the SCTP_RADIO_MODE, the other for UMTS in the
SCTP_RADIO_MODE.
Table 6-25 Filling Instruction of SCTP Sheet
Parameter Name
Content
Description
NE_ID
Network Element ID
SCTP_NO
SCTP No.
87
SCTP_RADIO_MODE
SCTP Radio Mode
SCTP_LOCAL_PORT
SCTP Local Port, that is, GSM site ID
SCTP_REMOTE_PORT
SCTP Remote Port, that is, CMP Module

No. + 14592
SCTP_REMOTE_IP
SCTP Remote IP Address, that is, SCTP

IP1 of IP ABIS configured in OMCR
BSC Function.
SCTP_IP_NO
IP No. of SCTP Channel, must be

defined in the IP sheet. The IP link is
assigned to GSM.
SCTP_INOUT_STREAM
SCTP_QOS
6.1.3.7 OMC Channel

Fill in the OMCB channel related information in the OMC Channel sheet, including
OMC_CHANNEL_NO, OMCB_GATEWAY_IP, OMCB_IP_NO, OMC_SERVER_IP,
and INNER_IP.
Table 6-26 Filling Instruction of OMC Channel Sheet
Parameter Name
Content
Description
NE_ID
Network Element ID
OMC_CHANNEL_NO
OMC Channel Link No.
OMCB_GATEWAY_IP
OMC Used IP No. In GSM networking, it

is configured as the OMCB channel IP
in BSC Function.
OMCB_IP_NO
OMC Server IP Address
OMC_SERVER_IP
OMC Server IP Address. Generally not

required in GSM networking.
INNER_IP
SDR inner ip address. Generally not

required in GSM networking.
OMCB_QOS
6.1.4 Radio Parameter

6.1.4.1 GSM Cell
Table 6-27 Filling Instruction of GSM Carrier Sheet
88
Item
Parameter Name
NE_ID
Network Element ID
CELL_ID
Cell No.
GPS_OFFSET
GPS
Value Range
Synchronous
Frame
Header Offset
POINT1_RU_NO
High speed railway cell entry
POINT1 RU NO and POINT2 RU NO
point 1 RU No.
should be configured in a pair.

The format is the same as the GSM
RU No. in the RU (GSM) sheet. It is
not required for the cell other than
high-speed railway cell.
POINT2_RU_NO
High speed railway cell entry
The format is the same as the GSM
point 2 RU No.
RU No. in the RU (GSM) sheet. It is

not required for the cell other than
high-speed railway cell.
BCCH_RU_NO
BCCH preferential RU No.
The format of the second PA of R8882

and RSU82 is RU No. #2.Do not fill
in this item if it is not required.
BCCH_TRU_NO
BCCH preferential Carrier No.
Do not fill in this item if it is not

required.
6.1.4.2 RU(GSM)
Fill in RU properties in GSM network in the RU(GSM) sheet, including
CARRIER_NUMBER, CARRIER_POWER_PARA, TRX_NUMBER for each cell, and the TX and
RX mode of antenna, etc. The PA of each RU occupies one line. For the RUs with two PA
units (RSU82 and R8882), fill in two line at most.

Table 6-28 Filling Instruction of RU(GSM) Sheet
Item
NE_ID
Parameter Name
Network Element ID
Value Range
Station sheet.
GRU_NO
GSM RU No.
The RU No. of PA unit 1 is the same as

RU_NO in the RU sheet. The pattern of
the RU No. of the PA unit 2 is RU
No.#2.
89
Item
CHANNEL_GROUP_NO
Parameter Name
GSM
Cell
Channel
Group No.
Value Range
If
CHANNEL_GROUP_NO
indicates
no
is
0,
it
grouping.
When
is
0,
CARRIER_GROUP
CHANNEL_GROUP_NO must be 0.
GU_CONFIG_MODE
GU
Carrier
Config
Mode
4G+1U, 2G+2U, INVALID.

In the single mode, the value is INVALID.
In the dual-mode, the value cannot be
INVALID.
All the DTR and RSU60 series do not
support 2G+2U.
CARRIER_GROUP
Carrier Group
Value range: 0 to 32. 0: Do not group.
CARRIER_NUMBER
Total Carrier Number
DTR series: 1 to 6, TTR series: 1 or 2,

RSU82 series: 1 to 6, R8882, 1 to 6. For
RSU82, when one channel (hereinafter
refers to A) is in GSM single mode, while
that
of
the
other
channel
is
in
GSM+UMTS dual-mode, the number of

carriers for Channel A should not be more
than four. For R8882, both of the two
channels must be in GSM single mode,
CARRIER_NUMBER for both channels
are four at most.
CARRIER_POWER_PARA
Carrier Power(W)

If RSU82 is configured with more than
four carriers, the product of Carrier
Power * Total Carrier Number should not
exceed 60 W. If it is configured with four
or fewer carriers, the product should not
exceed 80 W.
For the 20 W model of TTR and RSU02,
configure 20. For the 40 W model,
configure 40.
90
Item
Parameter Name
Value Range
STATIC_POWER_LEVEL
Static Power Level(db)
0db, 2db, 4db, 6db, 8db, 10db, 12db, 14db,

16db, 18db, 20db, -0.2db, -0.4db, -0.6db,
-0.8db, -1.0db, -1.2db
For the RF board other than RU02 series,
the value cannot be negative.
For the RF board in DIET site and R8882
series,
STATIC_POWER_LEVEL
can
only be 0 db to 12 db at most.
CELL_ID_1
First GSM Cell No.
Must be configured in the GSM Cell. 255:

Invalid.
TRX_NUMBER_1
Carrier
dedicated
Number
to
first
Value range: 0 to 6. The sum of all sector's

carrier number is not greater than the Total
sector
Carrier Number.
CELL_ID_2
Second GSM Cell No.
The same as above.
TRX_NUMBER_2
Carrier
The same as above.
Number
dedicated to second
sector
CELL_ID_3
Third GSM Cell No.
The same as above.
TRX_NUMBER_3
Carrier
The same as above.
dedicated
Number
to
third
sector
CELL_ID_4
Fourth GSM Cell No.
The same as above.
TRX_NUMBER_4
Carrier
The same as above.
dedicated
Number
to
fourth
sector
CELL_ID_5
Fifth GSM Cell No.
The same as above.
TRX_NUMBER_5
Carrier
The same as above.
dedicated
Number
to
fifth
sector
CELL_ID_6
Sixth GSM Cell No.
The same as above.
TRX_NUMBER_6
Carrier
The same as above.
dedicated
Number
to
sixth
sector
SUB_FREQ_BAND
Branch
Band
Frequence
Value range: 0 to 3. 0 or 255: Disable subfrequency band.
91
Item
TX_MODE
Parameter Name
Tx Mode
Value Range
0: Normal mode. 1: DPCT. 2: DDT. 3:
Antenna jumping.
RU02 series: 0 to 3. RSU82/R8882:
{0,2,3}.
Leave it blank for the other types of RUs.
Default: 0.
If the value is configured as 3, RU radio
mode should be GSM. FREQ_BAND,
SUB_FREQ_BAND,
STATIC_POWER_LEVEL of the two RU
channels
must
be
the
same.
CARRIER_NUMBER in R8882 series is

four at most.
If CARRIER_GROUP is not 0, or is
corresponding to two or more sectors, it
cannot be configured as 3.
RX_MODE
Rx Mode
0:2-antenna diversity reception

1:4-antenna diversity reception
2:Cross diversity reception (available in
V4.11.10.08)
RU02: 0 or 1. RSU82/R8882: 0 to 2. Not
required for the other RU types. Default:
0.
DDT_OFFSET
DDT delay
Integer: 0 to 8. This parameter can be

configured only when TX_MODE is DDT.
Default: 0.
GSM_RX_CONFIG
GSM
secondary
primary-
0:Primary
antenna
receiving
receiving setting
and
secondary
antenna
1:Primary antenna receiving. secondary

antenna not receiving
2:Secondary antenna receiving. primary
antenna not receiving
GSM_NO
GSM
Cell
Channel
Resource No.

modify it.
6.1.4.3 GSM Carrier

Fill in carrier related information in the GSM Carrier sheet, including TRX_NO,
CHANNEL_MODE, and FREQ_BAND, etc.
In order to configure an M-RRU cell, set CARRIER_NUMBER to 2 or a larger value,
92
and CHANNEL_MODE to 2:Multi carrier. If CHANNEL_MODE is set as 0:Single

carrier, CARRIER_GROUP of the corresponding RRU should be 0 (that is, nongroup), CARRIER_NUMBER is 1. If it is set as 1:Dual carrier, CARRIER_NUMBER is
2. If 1:Dual carrier or 2:Multi carrier is configured, CARRIER_GROUP must be
configured, and grouping must be performed.

If the RRUs associated with the base station are in the same CARRIER_GROUP
(greater than 0), their FREQ_BAND should be the same, and the number of RRUs
in the same group should be the same as CARRIER_NUMBER.
The total number of TRXs in the same FREQ_BAND of the same cell cannot be
greater than the total number of carriers, which are provided by the channel used by the
cell.
Refer to Table 6 -29 for detailed description of parameters.
Table 6-29 Filling Instruction of GSM Carrier Sheet
Parameter Name
Content
Description
NE_ID
Network Element ID
CELL_ID
Cell No.
TRX_NO
Logic Carrier Frequency No.
CHANNEL_MODE
Channel Mode. Generally, select 0:Single

carrier. Select 2:Multi carrier for multi
carrier group.
CARRIER_GROUP
Carrier Group
FREQ_BAND
Frequency Band
SUB_FREQ_BAND
Branch
Frequence
SUB_FREQ_BAND
in
Band.
RU(GSM)
If
is
configured, this item must be configured. If

SUB_FREQ_BAND in RU(GSM) is not
configured, this item can be omitted. The
Carrier configured with SUB_FREQ_BAND
can only be allocated to the RU in the same
SUB_FREQ_BAND
(this
configuration
process is completed automatically).

USE_IRC
Use IRC or Not

IRC can be used to improve receiving
performance, thus it is suggested to be
enabled.
STIRC is enhanced IRC, with which the
performance can be further enhanced.
93
Parameter Name
Content
EXTENSION_CARRIER
Description
Extend Carrier Frequency or Not
It is used in the ultra-wide coverage
scenario. Two TRX TSs are combined as one
to increase the TA applicable value.
MCUM_RX_SEL_MODE
MCUM_TX_SEL_MODE
94

05 GU - OC2024 - E01 - 0 ZXSDR BTS Data Configuration 98P

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

05 GU - OC2024 - E01 - 0 ZXSDR BTS Data Configuration 98P

Încărcat de

Drepturi de autor:

Formate disponibile

ZXSDR BTS Data Configuration

4.4.3 Creating TRX..........................................................................................................................38

Figure 1-1 SDR Base Station Commissioning Flow

Figure 1-2 SDR Data Configuration Flow

Chapter 6 Data Configuration in NEGOTIATION Template

2.1.1 Planning IP Address

Figure 2-3 IP Planning in IPOE Mode

Refer to Table 2 -1 for the planning of IP addresses.

The internal IP address

The internal IP address

The OMC2 port

For the OMCB rectified

split, the eth4:1 port is

configured. For the new

The OMC1 port

The OMC1 port

connect with OMCB

The IP of the RPU

The IP of the RPU

It must be the same as

The Abis interface and

connect with SDR

use either the same

The IP address of SDR

Chapter 6 Data Configuration in NEGOTIATION Template

Figure 2-4 IP Planning in IPOE Mode

Table 2-2 IP Data Planning Table (FE)

The OMC2 port on

The internal IP address

The OMP port (eth6)

The internal IP address

new office, it is not

Chapter 6 Data Configuration in NEGOTIATION Template

connect with OMCB

connect with RPU

OMCB channel can be

connect with RPU

the same as the IPAbis

The IP address of the

IPBB on the Abis

The Abis interface and

connect with SDR

use either the

The gateway address

2.1.2 Planning Radio Data

2.1.3 Planning Abis Interface Integration Data

Chapter 6 Data Configuration in NEGOTIATION Template

Table 2-4 Planning of the Data for Abis Interface Integration

SDR IP address (GSM)

The remote IP of SDR SCTP

The remote port No. of SDR SCTP

14595 (14592+Module No.)

OMM gateway address

2.2 Other Preparations

Personnel and vehicles

Chapter 6 Data Configuration in NEGOTIATION Template

Content and Standard

The type, number, and location of boards

are consistent with those in the planning.

are correctly configured according to the

The polarity of the input power cable of

BBU and RU are correct.

between -40VDC and -57VDC.