ZXSDR (V4.11.10.14P04) Engineering Commissioning Guide

ZXSDR
Engineering
Guide
(V4.11.10.14P04)
Commissioning
ZXSDR (V4.11.10.14P04) Engineering Commissioning Guide
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following
terms. If you do not agree to the following terms, please notice that you are not allowed
to use this document.
Copyright 2015 ZTE CORPORATION. Any rights not expressly granted herein are
reserved. This document contains proprietary information of ZTE CORPORATION. Any
reproduction, transfer, distribution, use or disclosure of this document or any portion of
this document, in any form by any means, without the prior written consent of ZTE
CORPORATION is prohibited.
and
are registered trademarks of ZTE CORPORATION. ZTEs company
name, logo and product names referenced herein are either trademarks or registered
trademarks of ZTE CORPORATION. Other product and company names mentioned
herein may be trademarks or trade names of their respective owners. Without the prior
written consent of ZTE CORPORATION or the third party owner thereof, anyones access
to this document should not be construed as granting, by implication, estopped or
otherwise, any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and
personal security. This product shall be stored, used or discarded in accordance with
product manual, relevant contract or laws and regulations in relevant country
(countries).
This document is provided as is and as available. Information contained in this
document is subject to continuous update without further notice due to improvement
and update of ZTE CORPORATIONs products and technologies.
ZTE CORPORATION
Addres
s:
Websit
e:
Email:
Address: NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
http://dms.zte.com.cn
TSM.Aftersales@zte.com.cn
ZTE Confidential Proprietary
2015 ZTE CORPORATION. All rights reserved.
Revision History
Product Version
Document Version
Serial Number
Reason for Revision
V4.11
R1.0
First published
V4.11.10.08P05
R1.1
Modified for
V4.11.10.08P05
V4.11.10.08P05
R1.2
Revised
V4.11.10.14P02
R1.3
Modified for
V4.11.10.14P02
V4.11.10.14P04
R1.4
Modified for
V4.11.10.14P04
Author
Date
Document Version
Prepared
by
Reviewed by
Approved by
2011-8-15
R1.0
Zheng
Junhua
Zhao Yanghao
Chen Qi
2012-5-11
R1.1
Zhao
Yanghao
Chen Qi
Chen Qi
R1.2
Sun
Jingjing,
Zhao
Yanghao
Zhao Yanghao,
Chen Qi
Chen Qi
R1.3
Sun
Jingjing,
Zhao
Yanghao
Zhao Yanghao,
Chen Qi
Chen Qi
R1.4
Ma
Debao,
Zhao
Yanghao
Zhao Yanghao,
Chen Qi
Chen Qi
2012-5-25
2012-5-31
2012-8-1
II
2015ZTE CORPORATION. All rights reserved.
Intended audience: BSS Commissioning Engineer
Proposal: Before reading this document, you had better have the following knowledge and
skills.
SEQ
Knowledge and skills
Reference material
1
2
3
Follow-up document: After reading this document, you may need the following
information.
SEQ
Reference material
Information
1
2
3
III
About This Document

Summary
Chapter
Description
1 Overview
Introduces the general information of this guide
2 Commissioning Preparation
Introduces the preparation items before the commissioning
3 Hardware Check
Introduces the hardware check items
4 OMCR Data Configuration
Describes the data configuration procedure in OMCR
5 OMCB Data Configuration
Describes the data configuration procedure in OMCB
6 Data Configuration in
NEGOTIATION Template
Describes the parameters to be configured in NEGOTIATION

Template
7 SDR Version Management
Introduces the operations related to SDR version

management
8 SDR BTS Commissioning Test
Introduces the reference of commissioning test
AppA Quick Query of General

Information
Introduces the operations and commands related to the

commissioning
IV
TABLE OF CONTENTS
1
1.1
1.2
1.3
Overview...........................................................................................................1
Instruction of the Guide......................................................................................1
Version Information............................................................................................1
SDR Base Station Commissioning Flow............................................................2
2
2.1
2.2
2.3
2.3.1
2.3.2
2.3.3
2.4
Commissioning Preparation...........................................................................4
Preparation for the Version to Be Commissioned...............................................4
Preparation for Commissioning Material............................................................4
Preparation for Data Configuration.....................................................................4
Planning IP Address...........................................................................................
Planning Radio Data..........................................................................................
Planning Abis Interface Integration Data............................................................
Other Preparations.............................................................................................9
3
3.1
3.2
Hardware Check.............................................................................................10
Jumper Switch Check Inside SA Board............................................................10
BBU Power-up/Power-Down............................................................................12
4
4.1
4.2
4.2.1
4.2.2
4.3
4.3.1
4.3.2
4.3.3
4.4
4.4.1
4.4.2
4.4.3
OMCR Data Configuration.............................................................................13

BSC Function Creation....................................................................................14
Board Configuration at BSC Side.....................................................................16
Creating Abis Interface Board..........................................................................
Creating IPBB for OMCB Connection..............................................................
IP-Related Configuration..................................................................................21
Creating IP Abis Interface of BSC....................................................................
Creating the Interface in BSC to Connect with OMCB.....................................
Creating the Interface in BSC to Connect with SDR.........................................
Configuration of BBU Logical Site....................................................................33
Creating Logical Site........................................................................................
Creating Cell....................................................................................................
Creating TRX...................................................................................................
5
5.1
5.1.1
5.1.2
5.2
5.2.1
5.2.2
5.2.3
5.3
5.4
5.4.1
5.4.2
OMCB Data Configuration.............................................................................39

Preparation for Data Configuration...................................................................39
Checking OMCB Server Configuration File......................................................
Adding Route...................................................................................................
Data Configuration Flow...................................................................................41
Data Configuration...........................................................................................
Importing Data.................................................................................................
Synchronizing Data..........................................................................................
Data Export Flow.............................................................................................56
Data Modification Flow.....................................................................................60
Modifying Data Online......................................................................................
Modifying Data Offline......................................................................................
6
6.1
6.2
6.2.1
6.2.2
6.2.3
6.2.4
Data Configuration in NEGOTIATION Template...........................................66

Configuration Preparation................................................................................66
Configuration Instruction in Corresponding Sheets..........................................66
Basic Parameter..............................................................................................
Equipment Parameter......................................................................................
Transmission Parameter..................................................................................
Radio Parameter..............................................................................................
7
7.1
7.1.1
7.1.2
7.1.3
7.1.4
7.1.5
SDR Version Management.............................................................................89

Introduction of Version Management................................................................89
Introduction of Version Management in OMCBV4.11.......................................
Creating Version..............................................................................................
Downloading Version.......................................................................................
Activating Version............................................................................................
Managing Version............................................................................................
SDR BTS Commissioning Test.....................................................................97
AppA
A.1
A.2
A.3
A.3.1
A.3.2
A.3.3
A.3.4
A.3.5
Quick Query of General Information............................................................98

Conversion Between Absolute Frequency Point and Frequency......................98
IP Address of Each SDR Board........................................................................98
General SDR Commissioning Commands.......................................................99
SDR Commands in SDRV4.11.........................................................................
Checking SDR Running Version....................................................................101
Checking Link Status of the Board.................................................................103
Checking Relation of Physical TRX and Logical TRX.....................................104
Checking RU Running Information.................................................................104
VI
FIGURES
Figure 1-1 SDR Base Station Commissioning Flow................................................................2
Figure 1-2 SDR Data Configuration Flow................................................................................3
Figure 2-1 IP Planning in IPOE Mode.....................................................................................5
Figure 2-2 IP Planning in IPOE Mode.....................................................................................7
Figure 3-1 Jumper Setting in 75 Transmission Mode.........................................................11
Figure 4-1 Applying Mutex Right...........................................................................................14
Figure 4-2 Configuration and Management Node of BSC Function......................................15
Figure 4-3 BSC Function - Basic Property Tab.....................................................................15
Figure 4-4 BSC Function - IP Property Tab...........................................................................15
Figure 4-5 BSC Rack Node..................................................................................................17
Figure 4-6 Configuring DTB in PCM Information Tab............................................................17
Figure 4-7 Configuring EUIP in HDLD Information Tab.........................................................18
Figure 4-8 Creating IPBB in Basic Information Tab...............................................................19
Figure 4-9 The Node for IP Related Config...........................................................................21
Figure 4-10 Interface Configuration Tab................................................................................22
Figure 4-11 Creating IP Abis Interface in Create Interface Tab.............................................22
Figure 4-12 Creating the IPBB Interface to Connect With OMCB.........................................24
Figure 4-13 Setting IPOE in PPP Mode................................................................................25
Figure 4-14 Setting IPOE in ML-PPP Mode..........................................................................26
Figure 4-15 Configuring E1 Interface in Create Interface Window........................................27
Figure 4-16 Creating IP over E1 Configuration.....................................................................28
Figure 4-17 Creating PPP Configuration...............................................................................30
Figure 4-18 Creating IP ABIS Bandwidth Resource Pool......................................................31
Figure 4-19 Creating PPP Bandwidth Resource Pool...........................................................32
Figure 4-20 Creating SDR Site.............................................................................................33
Figure 4-21 Creating SDR Site.............................................................................................34
Figure 4-22 Creating Cell......................................................................................................35
Figure 4-23 Configuring Cell Parameters..............................................................................36
Figure 4-24 Creating TRX.....................................................................................................37
Figure 4-25 Configuring the TRX Parameters.......................................................................37
VII
Figure 5-1 Data Configuration Flow in OMCBV4.11..............................................................42

Figure 5-2 Data Configuration Templates in Different Scenarios...........................................44
Figure 5-3 Starting CMX.......................................................................................................48
Figure 5-4 Importing Data.....................................................................................................48
Figure 5-5 Choosing File and Matched Base Station............................................................49
Figure 5-6 Verifying Data (Modifying Main Configset)...........................................................49
Figure 5-7 Verifying Data Successfully (Modifying Main Configset)......................................50
Figure 5-8 Querying Modified Data (Modifying Main Configset)............................................50
Figure 5-9 Importing Data Successfully (Modifying Main Configset).....................................51
Figure 5-10 Verifying Data (Creating New Configset)...........................................................51
Figure 5-11 Verifying Data Successfully 1 (Creating New Configset)....................................52
Figure 5-12 Verifying Data Successfully 2 (Creating New Configset)....................................52
Figure 5-13 Prompt for Closing CMX....................................................................................53
Figure 5-14 Batch Offline Reverse........................................................................................53
Figure 5-15 Successful Batch Offline Reverse......................................................................54
Figure 5-16 Whether to switch Successful Configset to Master State...................................54
Figure 5-17 Selecting the Site for ConfigSet Switchover.......................................................55
Figure 5-18 Completing ConfigSet Switchover.....................................................................55
Figure 5-19 Synchronizing Data...........................................................................................56
Figure 5-20 Clicking Export Data File...................................................................................57
Figure 5-21 Setting Export Properties...................................................................................57
Figure 5-22 Failure to Export Master Configset....................................................................58
Figure 5-23 Exporting Data Successfully..............................................................................58
Figure 5-24 Choosing Slave Configset.................................................................................59
Figure 5-25 Failure to Export Slave Configset......................................................................59
Figure 5-26 Choosing Modifying Data File............................................................................60
Figure 5-27 Choosing the Site to Be Modified......................................................................61
Figure 5-28 Editing MO Template.........................................................................................61
Figure 5-29 Converting, Verifying, and Comparing Data.......................................................62
Figure 5-30 Viewing Modified Parameters............................................................................62
Figure 5-31 Completing Data Modification............................................................................63
Figure 7-1 Interface of Multiple Mode Station Software Management...................................89
Figure 7-2 SDRV4.11 Software Version Packages...............................................................90
Figure 7-3 Multiple Mode Station Software Management.....................................................91
Figure 7-4 Clicking Create Version Package........................................................................91
VIII
Figure 7-5 Choosing Version Packages to Be Created.........................................................92

Figure 7-6 Newly-Created Version Package.........................................................................93
Figure 7-7 Clicking Download...............................................................................................93
Figure 7-8 Choosing Package and Managed Element..........................................................94
Figure 7-9 Clicking Active.....................................................................................................94
Figure 7-10 Choosing Package and Managed Element........................................................95
Figure 7-11 Double-Clicking Station Software Management.................................................95
Figure 7-12 Function Tabs in Station Version Management..................................................96
TABLES
Table 1-1 Version Information.................................................................................................1
Table 2-1 IP Data Planning Table (IPOE)................................................................................5
Table 2-2 IP Data Planning Table (FE)....................................................................................7
Table 2-3 Radio Data Planning...............................................................................................8
Table 2-4 Planning of the Data for Abis Interface Integration..................................................8
Table 3-1 Hardware Check List.............................................................................................10
Table 6-1 Filling Instruction of SubNetwork Sheet.................................................................66
Table 6-2 Filling Instruction of Base Station Sheet................................................................67
Table 6-3 Filling Instruction of Clock Sheet...........................................................................67
Table 6-4 Value Description of Clock Reference Source.......................................................68
Table 6-5 Configuration Instruction for Parameters Related to IEEE1588 Clock...................69
Table 6-6 Filling Instruction of Time Sheet............................................................................69
Table 6-7 Filling Instruction of Equipment Sheet...................................................................70
Table 6-8 Filling Instruction of RU Sheet...............................................................................72
Table 6-9 Filling Instruction of PaDevice Sheet.....................................................................73
Table 6-10 Filling Instruction of RxDevice Sheet...................................................................74
Table 6-11 Filling Instruction of EPm Sheet..........................................................................75
Table 6-12 Filling Instruction of Dry Contact Sheet...............................................................75
Table 6-13 Filling Instruction of PowerOutlet Sheet..............................................................76
Table 6-14 Filling Instruction of AISG Sheet..........................................................................77
Table 6-15 Filling Instruction of Transmission Sheet.............................................................78
Table 6-16 Filling Instruction of ATM Sheet...........................................................................79
Table 6-17 Filling Instruction of E1T1 Sheet.........................................................................79
IX
Table 6-18 Filling Instruction of HDLC Sheet........................................................................80

Table 6-19 Filling Instruction of IP Sheet...............................................................................80
Table 6-20 Filling Instruction of SCTP Sheet.........................................................................82
Table 6-21 Filling Instruction of OMC Channel Sheet...........................................................83
Table 6-22 Filling Instruction of GSM Carrier Sheet..............................................................83
Table 6-23 Filling Instruction of RU(GSM) Sheet..................................................................84
Table 6-24 Filling Instruction of GSM Carrier Sheet..............................................................87
Overview
This chapter focuses on the following subjects:
1.1
Instruction of the GuideOverview
SDR Base Station Commissioning FlowInstructi

on of the Guide
This guide is the SDR commissioning guide prepared for BSS commissioning engineers.
This guide only applies to iBSCV6.20.61 and iBSCV6.20.71 series versions,
OMCBV4.11.10.14,
OMCBV4.11.10.08P06
and
later
series,
and
SDRV4.11.10.14, SDRV4.11.10.08P06 and later series.
1.2
Version Information
Table 1-1 Version Information
NE
Example Version
Applicable Version
IBSC
iBSCV6.20.710b
iBSCV6.20.61 series
iBSCV6.20.71 series
SDR
SDRV4.11.10.14P04
SDRV4.11.10.14 series,
SDRV4.11.10.08P06 and
later series
OMCR
iOMCRV6.20.710b-OMCB4.00.200m
iOMCRV6.20.61 series
iOMCRV6.20.71 series
OMCB
ZXOMCBV4.11.10.14P04
OMCBV4.11.10.14 series,
OMCBV4.11.10.08P06
and later series
EMS
EMSV12.11.40pxx
1.3
SDR Base Station Commissioning Flow

Figure 1-1 SDR Base Station Commissioning Flow
Figure 1-2 SDR Data Configuration Flow
Commissioning Preparation
Tip:
This chapter introduces the preparations to be completed before the commissioning of
SDR base station. The engineers who prepare for SDR base station commissioning are
required to read this chapter thoroughly.
This chapter focuses on the following subjects:
2.1
Preparation for the Version to Be CommissionedPreparation for Commissioning

Material
Preparation for Data ConfigurationOther

PreparationsPreparation for the Version to Be
Commissioned
The version to be commissioned should contain:
1.
The version files of SDR Base station
2.
The LMT software package matched with the SDR base station version
The above files and software package must be applied for and obtained from
http://support.zte.com.cn by the representative office.
2.2
Preparation for Commissioning Material

The documents related to SDR BTS commissioning include:
2.3
ZXG10
ISMG
Server
Guide(Professional)_R3.4
(SBCX)
Installation
and
Commissioning
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.3.1
Planning IP Address
The IP addresses in the special subnet such as 192 are not allowed to be used by the
NEs such as SDR and OMCB. Refer to G_20110824_030(Notice of Prohibition of
Internal IP Used as NE IPs in SDR Networking) for details.
2.3.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 -2 for the planning of IP addresses.
Table 2-2 IP Data Planning Table (IPOE)

Configuration Item
Physical
Location
Configuration
The IP address of OMP
The OMC2 port

on OMP
129.18.0.1/24
The internal IP address

of OMCR Server
The OMP port

(eth6) on SBCX
129.18.0.100/24
Remarks
Configuration Item
Configuration
Remarks
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. For details,
refer to ZXG10
ISMG Server
(SBCX) Installation
and Commissioning
Guide(Professional).
The internal IP address

of OMCR Server
The OMC2 port

(eth4) on SBCX
139.18.0.100/24
The external IP address

of OMCR Server
The OMC1 port

(eth3) on SBCX
10.0.18.10/24
The external IP address

of OMCB Server
The OMC1 port

(eth3:1) on
SBCX
10.0.18.1/24
The interface IP address

in BSC to connect with
OMCB Server
The interface IP
on IPBB
139.18.0.254/24
The IP Abis address

(virtual address) on BSC
The IP of the
RPU interface
on OMP
118.18.0.1/32
The IP address of OMCB

channel
The IP of the
RPU interface
on OMP
118.18.0.1/32
It must be the same

as the IP Abis
address.
118.18.1.254/24
The Abis interface

and the OMCB
interface can use
either the same
IPBB or different
IPBBs.
The interface IP address

in BSC to connect with
SDR
The IP address of SDR
Physical
Location
The IP of the
interface on
EUIP
The IP of the
interface on
SDR
118.18.1.100/24
2.3.1.2
FE Transmission
Figure 2-4 IP Planning in IPOE Mode
Table 2-3 IP Data Planning Table (FE)

Configuration
Item
Physical
Location
The IP address of
OMP
The OMC2 port

on OMP
The internal IP
address of OMCR
Server
The OMP port

(eth6) on SBCX
Configuration
129.18.0.3/24
129.18.0.1/24
The OMC2 port

(eth4) on SBCX
The internal IP
address of OMCR
Server
139.18.0.100/24
The external IP
address of OMCR
Server
The OMC1 port

(eth3) on SBCX
The external IP
address of OMCB
Server
The OMC1 port

(eth3:1) on
SBCX
The interface IP
address in BSC to
connect with
OMCB Server
The interface IP
on IPBB
Remarks
10.0.18.10/24
10.0.18.1/24
139.18.0.254/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. For details, refer
to ZXG10 ISMG Server
(SBCX) Installation and
Commissioning
Guide(Professional).
2.3.2
Configuration
Item
Physical
Location
The IP Abis
address (virtual
address) on BSC
The interface IP
address in OMP
to connect with
RPU
The IP address of
OMCB channel
he interface IP
address in OMP
to connect with
RPU
The interface IP
address in BSC to
connect with SDR
Configuration
Remarks
118.18.0.1/32
118.18.0.1/32
The IP address of OMCB

channel can be the same
as the IPAbis address, or a
different address.
The IP address
of the IPBB on
the Abis
interface
118.18.2.4/30
The Abis interface and the

OMCB interface can use
either the same IPBB or
different IPBBs.
The IP address of
SDR
The IP of the
interface on
SDR
118.18.2.3/30
The gateway
address of SDR
IPBB_SDR
interface IP
address
118.18.2.1/30
Planning Radio Data

Refer to Table 2 -4 for the planning of radio data.
Table 2-4 Radio Data Planning

Parameter Name
2.3.3
Example
MCC
460
MNC
13
LAC
CI
91
NCC
BCC
Planning Abis Interface Integration Data

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

Parameter Description
BSCID
Example
10
Parameter Description
2.4
Example
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
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
Hardware Check
Check the items in the following table before site commissioning.
Table 3-6 Hardware Check List

Check Item
Pass Fail
The internal jumper switches of SA board are

correctly configured according to the
transmission type.
Pass Fail
The polarity of the input power cable of BBU

and RU are correct.
Pass Fail
The input voltage of BBU and RU is between

-40VDC and -57VDC.
Pass Fail
If BBU and RU use the single-phase 220V

power supply, the variation range of the singlephase 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.
Pass Fail
The cable from the FS board to RU is

connected correctly.
Pass Fail
There is no crossed or loose connection of the

antenna jumpers that are connected to RU.
Pass Fail
Check of the
Connection
on the Abis
Interface
If FE cable is used, the FE cable is connected

to the CC board correctly.
Pass Fail
If E1 cable is used, the E1 cable from DDF to

the SDR base station is connected correctly.
Pass Fail
Equipment
Power-up
Check
Check the status of boards after they are

powered on.
Pass Fail
The shelves are well grounded.
Pass Fail
Input Power
Supply Check
Rack Cable
Check
Jumper Switch Check Inside SA Board
10
Check Result
The type, number, and location of boards are

consistent with those in the planning.
Board Check
3.1
Content and Standard
For the site that uses 75 transmission, the jumpers on SA should be set as: X1X4: 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: X1X4: open circuit, X51-X53: open circuit, X54: short circuit.
ON-The jumper is set short-circuited, i.e. the jumper cap is placed on the jumper; OFF-The jumper is set opencircuited, i.e. the jumper cap is removed.
3.2
BBU Power-up/Power-Down
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.
Note:
12
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.
OMCR Data Configuration

This chapter describes the data configuration of SDR in OMCR. The data configuration
depends on the planning in 2.3 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.
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 dropdown list as shown in Figure 4 -6.
Figure 4-6 Applying Mutex Right
2.
14
Double-click BSC Function node as shown in Figure 4 -7.
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
Figure 4-9 BSC Function - IP Property Tab
Refer to the following table for the description of the parameters:

Parameter Name
OMCB IP
SCTP IP1 of IP
ABIS
OMCB channel IP
4.2
Configuration
Tab
Basic property
IP Property
IP Property
Content
Description
139.18.0.100
Internal IP of OMCB
server. Configured as
eth4:1 IP.
118.18.0.1
The IP used to
communicate with site
control plane.
Configured as the
virtual RPU IP for the
Abis interface.
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.
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.
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.
16
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.
Figure 4-11 Configuring DTB in PCM Information Tab

Parameter Name
Configuration Tab
Content
Description
Board function type
Basic Information
DTB
PCM type
PCM Information
Type of EUIP
Select Type of EUIP

as PCM type.
Frame mode
PCM Information
Multi frame
Select Multi frame as

Frame mode.
Parameter Name
PCM No.
3.
Configuration Tab
Content
Description
Add this item
according to onsite
situation.
PCM Information
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.
Figure 4-12 Configuring EUIP in HDLD Information Tab
18
Parameter Name
Configuration
Tab
Board function typ

e
Basic Information
EUIP
HDLC No.
HDLC Information
Configure this item

according to the
actual situation.
EUIP 2MHW No.
HDLC Information
Configure this item

according to the
actual situation.
DT Unit No.
HDLC Information
Configure this item

according to the
actual situation.
The Unit No. of DTB
DT PCM No.
HDLC Information
Configure this item

according to the
actual situation.
The E1 No. of DTB
TS Config Informa
tion
HDLC Information
Add the onsite TS

resources to the list
Configure the
connection between
Content
Description
The 2MHW No. in

EUIP
Parameter Name
Configuration
Tab
Content
on the right list.
Unless specified,
select 1-31 TSs.
Description
EUIP 2MHW TS and
DT PCM TS.
Note:
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
4.2.2
Content
Board function type
IPBB
Backup mode
1+1 backup mode
Description
Channel mode
Channel mode 2
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
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
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.
20
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.
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.
Figure 4-16 Creating IP Abis Interface in Create Interface Tab

Parameter
Name
Board funct
ion type
IP address
22
Content
Description
RPU
118.18.0.1
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.
Parameter
Name
4.3.2
Content
Description
Subnet
mask
255.255.255.2
55
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.
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.
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
24
Content
Board functio
n type
IPBB
IP address
139.18.0.254
Subnet mask
255.255.255.0
Description
The IP of the IPBB port connected with

OMCB server, and the gateway IP from
OMCB server to SDR.
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.
MAC
address
Any value within [00-D0D0-A0-00-00,00-D0-D0-A09F-FF] or [00-19-C6-3E-3010,00-19-C6-4E-30-0F].
Make sure this MAC address is not the

same as that in the other ports.
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 (depending on the BSC
version). Refer to GT-20100827-026(Notice of Evasion of IPOE Site Access
Number) 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.
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 shown in Figure 4 -20.
26
Figure 4-20 Configuring E1 Interface in Create Interface Window

Parameter Name
Board function type
Content
EUIP
IP address
118.18.1.254
Subnet mask
255.255.255.0
BTS gateway IP, and the

actual IP address in BSC
to connect with base
station.
In the PPP protocol, the
valid Port Nos. are 1-190.
In the ML-PPP protocol,
the valid Port Nos. are
191-254.
191
Port No.
Description
Refer to the following table for the description of the associated parameters:
Parameter
Name
Associated
Parameter
Name
Port No.
Port No.
Configuration Tab
for Associated
Parameter
IP Over E1
configuration,
PPP configuration
Description
In the PPP Configuration tab,
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
Parameter
Name
Associated
Parameter
Name
Configuration Tab
for Associated
Parameter
Description
PPP should be consistent with
that in this tab.
Configure the IPOverE1 parameters.

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

Parameter
Name
Port No.
28
Content
1
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
Parameter
Name
Content
Description
from 1.
HDLC No.
Associated parameter
Start TS
End TS
31
The TS resource used in E1 link, which 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
Associated
Parameter
Name
Configuration Tab for

Associated Parameter
Description
Port No.
Port No.
IP Over E1 configuration
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 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
Peer IP
MP No. sign
Content
118.18.0.100
BTS IP address
Valid
In PPP protocol, this parameter is set

as Invalid. In ML-PPP protocol
(when a site is configured with
multiple transmission links), Mpno is
set as Valid. The value should be
configured as the corresponding
EUIP Port No.
IP header compression
sign
Keep time
Keep granularity
.
30
Description
Whether IP header compression is

enabled. IP header 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.
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 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
Content
Description
IP ABIS Pool ID
It should be consistent with Site 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
No
Quote the MP No. in PPP

Configuration corresponding to
the 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
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.
Knowledge:
Refer to G_ST_Explanation of Differences in iBSCV6.20.614 Configuration_R1.0 for the
knowledge for the above Steps 4 and 5.Step 4 is compulsory, while Step 5 is optional.
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.
32
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.
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

Parameter Name
Content
Site ID
Site type
SDR
Module No
Description
This value should be
consistent with the GSM
Site ID configured in
SDR.
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
34
Parameter Name
Content
Select Non-satellite ABIS

access, Satellite ABIS
access, or Super site.
Abis satellite access

type
Site IP address
4.4.2
Description
SDR IP address
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.
Figure 4-27 Creating Cell
2.
Configure the cell parameters, as shown in Figure 4 -28.
Figure 4-28 Configuring Cell Parameters

Parameter
Name
36
Configuration
Tab
Content
Description
Cell type
Basic Params1
Macro cell
MCC
Basic Params1
460
Configure this item

according to the actual
situation.
MNC
Basic Params1
Configure this item

situation.
LAC
Basic Params1
58201
Configure this item

situation.
CI
Basic Params1
44440
Configure this item

situation.
NCC
Basic Params1
Configure this item

situation.
BCC
Basic Params1
Configure this item

situation.
Frequency band
Basic Params1
GSM900
Configure this item

situation.
4.4.3
Creating TRX
Procedure
1.
In the OMCR topology tree, create the TRX as shown in Figure 4 -29.
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
38
Configuration
Tab
Content
Cell type
Common TRX
BCCH Mark
No
Description
Frequency
TRX Info
23
Configure this item

situation.
Port No.
IP Parameters
The value should be unique

in the same BSC.
In 1000 M platform
environment, one TRX
group supports 35 TRXs (in
iBSCV6.20.615 and later
versions), or 28 TRXs (in
iBSCV6.20.614 and
previous versions). In 100
M environment, one TRX
group supports 16 TRXs.
One TRX group can only be
allocated to one DSP.
TRX group No.
IP Parameters
Local switch
port
IP Parameters
Required in the local switch.
OMCB Data Configuration

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.10.14P04.
5.1
Preparation for Data Configuration
5.1.1
Checking OMCB Server Configuration File
5.1.1.1
Checking OMCR/OMCB Split Configuration File

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
5.1.1.2
It refers to OMCB in OMCR/OMCB split version.
Checking the deploy-020sdrmap.properties File

1.
Log in to the OMCB server as the gomcb user, and open the home\gomcb\umssvr\deploy directory.
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-commonnodeb-api.omcb-ftpserver-ip
3.
Save the configuration and exit.
Content
Description
139.18.0.10
0
It is the internal IP of OMCB, and

should be configured according
to the actual planning.
5.1.1.3
Checking deploy-999split.properties File

1.
Log in to the OMCB server as the gomcb user, and open the home\gomcb\umssvr\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
Description
10.0.18.1
It is the external IP of OMCB,

and should be configured
planning.
ums.systemproperty.com.zte.um
s.bind.socket.client.ip
139.18.0.100
It is the internal IP of OMCB,

and should be configured
planning.
ums.services.bind.multi.local.ad
dresses
139.18.0.100
,*.*.*
The first one is the internal IP

of OMCB, and should be
configured according to the
actual planning.
ums.systemproperty.com.zte.um
s.uep.localaddress
4.
5.1.1.4
Content
Save the configuration and exit.
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
40
5.1.2
Adding Route
Purpose
According to the IP planned in Section 2.3.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.

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.
5.2
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.
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.
Figure 5-31 Data Configuration Flow in OMCBV4.11
As shown in the above figure, the data configuration flow of OMCBV4.11 mainly includes
three phases: data configuration, data import, and data synchronization. The detailed
procedure of each phase is shown as follows:
42
5.2.1
Data Configuration
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, 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 is

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

shown as follows:
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

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,
if
SDR(GU)_4.11_CM_NEGONIATION_TEMPLATE_V4.11.10.14.xls
is
the
English
version,
SDR(GU)_4.11_CM_NEGONIATION_TEMPLATE_V4.11.10.14_CN.xls is the
Chinese version.
iii.
44
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 NEGOTIATION Template to MO
Template is completed in the SDRConfTool independently. Only the MO Template
can be imported to OMCB or LMT through CMX.
However, the SDRConfTool is not updated simultaneously with OMCB. Therefore,
SDRConfTool is not released in the OMCB version package, but in the ECC
website. The representative office can apply for and download SDRConfTool from
ECC (currently, the latest version is ZXSDRConfTool_v4.1.0).
NEGOTIATION Template in OMCBV4.11.10.14 is released in the
\template\v4.11.10.14
directory
of
the
SDRConfTool
package.
(NEGOTIATION Template in OMCBV4.11.10.08 is released 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.
The filling instruction of NEGOTIATION Template is the similar to that of

SdrConfTool3.4.x in SDRV4.09. Refer to 6 for details.
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-cm-wsf.par\res\info
directory for detailed filling instruction of MO Template.
5.2.1.3
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.
1.
46
Double-click run.bat, and the following window pops up.
5.2.2
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.
Importing Data
Data import is performed in CMX. CMX is short for Configuration Management 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.
This guide only focuses on the configuration flow of OMCBV4.11.10.14.
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.
Figure 5-34 Importing Data
3.
48
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
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).
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.
50
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)
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.
52
Figure 5-43 Prompt for Closing CMX
5.2.3
Synchronizing Data
5.2.3.1
Batch Offline Reverse

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.
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.
54
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.
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
5.2.3.2
Synchronizing Data
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
5.3
56
Data Export Flow

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.
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
Figure 5-53 Exporting Data Successfully
5.
58
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 shown in
Figure 5 -53.
Figure 5-55 Failure to Export Slave Configset
5.4
Data Modification Flow
5.4.1
Modifying Data Online

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.
Figure 5-56 Choosing Modifying Data File
3.
60
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 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.
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.
62
In the above figure, click Next, and the data import progress bar will be shown.
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. The general procedure
is as follows:
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.
64
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.
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.
4.
Click Execute to start converting NEGOTIATION Template to MO Template.
Import the modified MO Template to OMCB or LMT. (Refer to 5.2.2 Importing Data.)
Data Configuration in NEGOTIATION

Template
6.1
Configuration Preparation
NEGOTIATION
Template
in
SDRV4.11.10.14
is
template\v4.11.10.14 directory of SDRConfTool package.
released
in
the
Although
NEGONIATION
Template
is
also
saved
in
the
\umsclnt\deploy\template\CMX directory of OMCB client, due to the frequent update of
SDRConfTool, it is suggested to use the NEGOTIATION Template in the latest
SDRConfTool.
6.2
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.
The
parameter
filling
instruction
in
this
guide
is
based
on
SDR(GU)_4.11_CM_NEGOTIATION_TEMPLATE_V4.11.10.14P04. The SHEETs in
NEGOTIATION Templates of different versions may be different, but all the necessary
parameters can be found in the template.
6.2.1
Basic Parameter
6.2.1.1
SubNetwork
Fill in SUBNETWORK_ID and SDR_VERSION in the SubNetwork sheet.
Refer to Table 6 -7 for filling instructions.
Table 6-7 Filling Instruction of SubNetwork Sheet

Parameter Name
Content
SUBNETWORK_ID
66
Description
The ID when Subnetwork is
created in OMCB
Parameter Name
6.2.1.2
Content
Description
TEMPLATE_VERSION
4.1.0
Not required to be modified
SDR_VERSION
4.11.10.14P04
Not required to be modified
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 -8 for filling instructions.
Table 6-8 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 to onsite
situation (such as BS8900A,
BS8800 GU360, etc.), for the
CRAN site, choose BS8700.
BSC_ID
BSC ID where the base station

is connected to.
6.2.2
Equipment Parameter
6.2.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-9 Filling Instruction of Clock Sheet

Item
Parameter
Name
Value Range
NE_ID
Network
Element ID
Corresponding to the NE_ID in Base Station

sheet.
CLOCK_PRIORIT
Y
Clock Source
Priority
Value range: 1 to 8.
The priority of clock reference resource. 1
refers to the top priority.
CLOCK_TYPE
Clock Source
Refer to Table 6 -10 for the description of
Item
Parameter
Name
Value Range
Type
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_
MODE
Clock
Synchronizati
on Mode
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_TY
PE
GPS Cable
Type
0: Multiplexing input
1: Distribution input
GPS_RECEIVER
_TYPE
GPS
Receiver
Type
1: GPS
2: GLONASS
3: GPS+GLONASS
GPS_CABLE_DE
LAY
Length of
Cascade
cable(m)
Integer: 0 to 15.
CLOCK_SSM
Enable SSM
Y: Yes
N: No
Must be configured if CLOCK_TYPE is
SyncE
Table 6-10 Value Description of Clock Reference Source

Value
68
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.2.2.2
IpClock
Table 6-11 Configuration Instruction for Parameters Related to IEEE1588 Clock
Item
6.2.2.3
Parameter
Name
Value Range
NE_ID
Network
Element ID
Corresponding to the NE_ID in Base

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_SERVER_IP
IP Address of
1588 Clock
Sync Server
Must be configured for IP 1588 clock

reference source. Valid only when it is
IP over Ethernet transmission type.
IPCLK_IP_NO
IP Link No. of
1588 Clock
Sync Channel
INTEGER: 0 to 19. Existed in IP

sheet.
Time
Table 6-12 Filling Instruction of Time Sheet
Item
6.2.2.4
Parameter
Name
Value Range
NE_ID
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_STA
RT
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.
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 -13 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-13 Filling Instruction of Equipment Sheet

Item
70
Parameter Name
Value Range
NE_ID
Network Element
ID
Network Element ID
TELECOM_OPER
ATOR
Telecom Operator
127 bytes at most, without & ' " < > # %
OPERATOR_PLAN
NED_ID
Network Element
ID planned by
operator

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.
VENDOR_PLANNE
D_ID
Network Element
ID planned by
vendor

Vendor 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.
RADIO_MODE
Radio Mode
UMTS, GSM, GSM+UMTS
BBU_TYPE
BBU Type
BBU Type (BBU-2U refers to B8200, BBU3U 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 this slot only when the BBU Type

is BBU-3U.
BBU_SLOT_10
BBU Slot 10

is BBU-3U.
BBU_SLOT_11
BBU Slot 11

is BBU-3U.
BBU_SLOT_12
BBU Slot 12

is BBU-3U.
Configure UBPG in this slot only when BBU

Type is BBU-3U.
Item
Parameter Name
Value Range
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

is 3U.
BBU_SLOT_17
BBU Slot 17

is 3U.
SHELF2_BBU_SL
OT_1
Shelf 2's BBU Slot

1
Configure the boards for the second

stacked BBU.
SHELF2_BBU_SL
OT_2
Shelf 2's BBU Slot

2
SHELF2_BBU_SL
OT_3
Shelf 2's BBU Slot

3
SHELF2_BBU_SL
OT_4
Shelf 2's BBU Slot

4
SHELF2_BBU_SL
OT_5
Shelf 2's BBU Slot

5
SHELF2_BBU_SL
OT_6
Shelf 2's BBU Slot

6
SHELF2_BBU_SL
OT_7
Shelf 2's BBU Slot

7
SHELF2_BBU_SL
OT_8
Shelf 2's BBU Slot

8
SHELF2_BBU_SL
OT_14
Shelf 2's BBU Slot

14
SHELF2_BBU_SL
OT_15
Shelf 2's BBU Slot

15
RACK_TOPOLOG
Y
Rack Topology
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. R8882S9000C 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 upperlevel 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_MO
Optical Module
1.25G, 2.5G, 3G, 6G. Default value: 1.25G.
Item
Parameter Name
Value Range
DULE_TYPE
Type of FS in Slot 3
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_MO
DULE_TYPE
Optical Module
Type of FS in Slot 4
1.25G, 2.5G, 3G, 6G. Default value: 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.
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.2.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 -14 for the parameter description in this sheet.
Table 6-14 Filling Instruction of RU Sheet

Parameter Name
Content
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
72
Description
Optical Module Type

R8860, R8860E, RSU60,
RSU60E, RU02 use 1.25G
optical ports. R8882 (except
R8882C) uses 2.5G optical
Parameter Name
Content
Description
port. R8882C uses 6G optical
port. The FS optical type
should be consistent with that
of RRU.
6.2.2.6
ANTENNA_TYPE
Antenna Type. ANT:Normal

Antenna, RET:Aisg
VSWR_LOWER
VSWR Lower Limit
VSWR_UPPER
VSWR Upper Limit
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 V4.11.10.14
and later versions.
PaDevice
Configure the power amplifier device of each RU in the PaDevice sheet. Each power
amplifier device occupies one line.
Table 6-15 Filling Instruction of PaDevice Sheet

Item
6.2.2.7
Parameter Name
Value Range
NE_ID
Network Element
ID
RU_NO
RU No.
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.
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-16 Filling Instruction of RxDevice Sheet

Item
6.2.2.8
Parameter Name
Value Range
NE_ID
Network Element
ID
RU_ NO
RU No.
RRU value range: 51 to 201. RSU value

range: 2 to 50.
RX_PORT_NO
Rx Port ID
Integer: 1 to 6.
RECEIVE_FREQ
Central Uplink
Frequency(MHz)
Multiple of 0.2MHz. 0 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 No.
The frequency band of associated RU

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 ID
Integer: 1 to 6.
TMA_NO
TMA No.
Value range: 1 to 96. The value should

be unique.
TM_TYPE
Tower Top
Amplifier type
TMA,A-TMA,A-COM,ETMA,A-ETMA
RX_POWER_GAIN
Tower Top
Amplifier Uplink
Power Gain
TMA: 70 to 150
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 Power
Gain(0.1db)

Invalid : 255
TMA_NOISE
Tower Top
Amplifier Noise
Coefficient(0.1dB)

Invalid: 255
ANT_NO
Connected
Mechanical
Antenna RDN
This field cannot be configured. Do not

modify it.
RET_NO
Connected RET
Antenna RDN
This field cannot be configured. Do not

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

Item
6.2.2.9
Parameter Name
Value Range
NE_ID
Network Element
ID
EPM_BO
ARD
Connected Board
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_PW
R_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_DE
AL_MOD
E
EPm Data
Processing Mode
0: Transparent transmission
1: Parse
Dry Contact
Table 6-18 Filling Instruction of Dry Contact Sheet
Item
Parameter
Name
Value Range
NE_ID
Network
Element ID
Corresponding to the NE_ID in Base Station

sheet.
DRY_CONTACT_
POSITION
Dry
Contact
Position
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.
DRY_CONTACT_
USERLABEL
User Label
128 bytes at most. Default: null. Without & ' " <
>#%/\?@:,
Item
6.2.2.10
Parameter
Name
Value Range
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_
CONTENT
Dry
Contact
Alarm
Code
Valid to input dry contact. For the user-defined

dry contact, refer to the NETOGIATION
Template in 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
Status
Valid only if type is output.

0: Output low level
1: Output high level
PowerOutlet
PowerOutlet refers to the power output port. After the TAM board is configured, the data
in this sheet can be configured.
Table 6-19 Filling Instruction of PowerOutlet Sheet

Item
76
Parameter
Name
Value Range
NE_ID
Network
Element ID
TAM_SHELF
TAM Board
Shelf No.
TAM_SLOT
TAM Board Slot

No.
TAM_PORT
TAM Board Port

No.
TAM_WORKING_CURRENT
Work Current
Configure the maximum current
Item
Parameter
Name
TAM_ALM_MODE
6.2.2.11
Value Range
Value (mA)
value of the specified port.

Value Range
TAM0: 75 to 300
TAM1: 75 to 400
TAM2: 75 to 400
Alarm Detect
Mode
0: currentDetect
1: pulsewidthDetect
AISG
Table 6-20 Filling Instruction of AISG Sheet
Item
Parameter
Name
Value Range
NE_ID
Network
Element ID
AISG_RU_NO
CCU Rack
No.
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_COD
E
Vendor
Code
127 bytes at most.
AISG_VERSIO
N
AISG
Version
1.1
2.0
RET_RU_NO
Connected
RET Device
RU No
Connected RET Device No., the associated

ANTENNA_TYPE must be RET. Mutually
exclusive to AISG_TMA_NO.
RET_PORT_NO
Connected
RET Device
Port No
Connected RET Device Port No, configured in a

pair with RET_RU_NO. Mutually exclusive to
AISG_TMA_NO.
AISG_TMA_NO
Connected
TMA Device
No.
Integer: 1 to 96. TMA_NO in the RxDevice sheet

must be configured in advance. TM_TYPE must
be A-TMA, A-COM or A-ETMA.
Mutually exclusive to RET_RU_NO and
RET_PORT_NO.
Item
Parameter
Name
MULTI_ANT_N
O
Subunits No.
Value range: 1 to 4. 255: Invalid.
AISG_USERLA
BEL
Description
of Selfdefined Field
128 bytes at most, can be blank.

Without & ' " < > # % / \ ? @ : ,
FATHER_PORT
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.2.3
Transmission Parameter
6.2.3.1
Transmission
Value Range
Fill in the transmission information in the Transmission sheet, including

TRANSMISSION_TYPE, TRANSMISSION_MEDIUM, ETHERNET_WORK_MODE, and
FE_BANDWIDTH, etc.
Table 6-21 Filling Instruction of Transmission Sheet

Item
78
Parameter
Name
Value Range
NE_ID
Network Element
ID
TRANSMISSION_TYPE
Transmission
Type
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/GE
BandWidth(kbps
)
If the UES board is

configured, the maximum
bandwidth is 250Mbps.
FE_PHYLAYERPORTNO
FE/GE Physical
Layer Port No.
The physical layer port No.

corresponding to Ethernet.
Different from
E1T1_PHYLAYERPORT_NO.
6.2.3.2
ATM
Fill in this ATM sheet if TRANSMISSION_TYPE is ATM or ATM+IP.
Table 6-22 Filling Instruction of ATM Sheet

Item
6.2.3.3
Parameter Name
Value Range
NE_ID
Network Element
ID
ATM_E1T1_PHYLAYERPORT_NO
ATM E1/T1
Physical Layer
Port No.
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
E1T1
Configure E1T1 physical layer port in the E1T1 sheet. If HDLC or ATM is configured, this
sheet must be filled in.
Table 6-23 Filling Instruction of E1T1 Sheet

Item
Parameter Name
Value Range
NE_ID
Network Element
ID
E1T1_PHYLAYERPORT_NO
E1/T1 Physical
Layer Port No.
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.
6.2.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-24 Filling Instruction of HDLC Sheet

Item
6.2.3.5
Parameter
Name
Value Range
NE_ID
Network
Element ID
HDLC_NO
HDLC Link
No.
Integer: 0 to 15. Unique within the same site.
HDLC_E1T1_PHYLAYE
RPORT_NO
E1/T1
Physical
Layer Port
No.
Integer: 0 to 17.
Must be configured in the E1T1 sheet.
HDLC_TIMESLOT_MA
P
HDLC
Timeslot
Except Timeslot 0, Timeslots 1-31 are

available.Pattern: start of time slot-end of time
slot,... For non-consecutive timeslots,
separate different segments with comma, for
example, 1-5,10-20.
TSI_IN_TIMESLOT_MA
P
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_PHYLAYERP
ORT_NO
TSI Out
Physical
Layer Port
No.
Value range: 0 to 17. It should 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 outtimeslots.
TSI_OUT_NO
TSI Out No.
This field cannot be configured. Do not modify

it.
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.
80
Table 6-25 Filling Instruction of IP Sheet

Item
Parameter
Name
Value Range
NE_ID
Network
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

mask in FE transmission
mode.
IP_VLAN_GATEWAY
IP Gateway
Address

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 Route
Network Mask

STATICROUTE_NEXTHOP_IPADDR
Static Route
Next Hop IP
Address

Path Domain
Integer: 0 to 3. 255:
invalidUMTS multi-path
parameter. 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.
PPP_HDLC_NO
PPP HDLC Link

No.
PATH_DOMAIN

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
Item
Parameter
Name
Value Range
configured in the HDLC
sheet in advance. The
HDLC used should contain
at least one main link.
6.2.3.6
PPP_IP_ADDRESS
Base Station IP
Address
PPPoE IP address, that is,

base station IP address.
PPP_PROTOCOL
PPP
Encapsulation
Select ML-PPP.
PPP_COMPRESSION
Support IP
compress or
not
Whether PPP supports IP

header 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 MLPPP.
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-26 Filling Instruction of SCTP Sheet

Parameter Name
82
Content
Description
NE_ID
Network Element ID
SCTP_NO
SCTP No.
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.
Parameter Name
Content
Description
IP No. of SCTP Channel, must
be defined in the IP sheet. The IP
link is assigned to GSM.
SCTP_IP_NO
SCTP_INOUT_STREAM
SCTP_QOS
6.2.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-27 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.2.4
Radio Parameter
6.2.4.1
GSM Cell
Table 6-28 Filling Instruction of GSM Carrier Sheet
Item
Parameter Name
Value Range
NE_ID
Network Element ID
CELL_ID
Cell No.
GPS_OFFSET
GPS Synchronous Frame

Header Offset
POINT1_RU_N
O
High speed railway cell

entry point 1 RU No.
POINT1 RU NO and POINT2 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.
6.2.4.2
POINT2_RU_N
O
High speed railway cell

entry point 2 RU No.
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.
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_N
O
BCCH preferential Carrier

No.
Do not fill in this item if it is not

required.
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-29 Filling Instruction of RU(GSM) Sheet

Item
Value Range
Network Element
ID
Corresponding to the NE_ID in

Base Station sheet.
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.
GSM Cell Channel

Group No.

If CHANNEL_GROUP_NO is 0, it
indicates no grouping. When
CARRIER_GROUP is 0,
CHANNEL_GROUP_NO must be
0.
This parameter can be configured
in V4.11.10.14 and later versions.
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,
NE_ID
GRU_NO
CHANNEL_GROUP_NO
84
Parameter Name
Item
Parameter Name
Value Range
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(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.
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 Number
dedicated to first
sector
Value range: 0 to 6. The sum of all

sector's carrier number is not
greater than the Total Carrier
Number.
CELL_ID_2
Second GSM Cell

No.
The same as above.
TRX_NUMBER_2
Carrier Number
dedicated to
second sector
The same as above.
CELL_ID_3
Third GSM Cell

No.
The same as above.
TRX_NUMBER_3
Carrier Number
dedicated to third
sector
The same as above.
CELL_ID_4
Fourth GSM Cell
The same as above.
CARRIER_POWER_PARA
Item
Parameter Name
Value Range
No.
TRX_NUMBER_4
Carrier Number
dedicated to fourth
sector
The same as above.
CELL_ID_5
Fifth GSM Cell

No.
The same as above.
TRX_NUMBER_5
Carrier Number
dedicated to fifth
sector
The same as above.
CELL_ID_6
Sixth GSM Cell

No.
The same as above.
TRX_NUMBER_6
Carrier Number
dedicated to sixth
sector
The same as above.
SUB_FREQ_BAND
Branch Frequence
Band
Value range: 0 to 3. 0 or 255:

Disable sub-frequency band.
Tx Mode
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 primarysecondary
antenna receiving
setting
TX_MODE
86
0:Primary and secondary antenna

receiving
1:Primary antenna receiving.
secondary antenna not receiving
2:Secondary antenna receiving.
Item
Parameter Name
Value Range
primary antenna not receiving
GSM_NO
6.2.4.3
GSM Cell Channel

Resource No.
This field cannot be configured. Do

not modify it.
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, 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, non-group),
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 -30 for detailed description of parameters.
Table 6-30 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 Band. If

SUB_FREQ_BAND in RU(GSM)
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
Parameter Name
Content
Description
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.
EXTENSION_CARRIER
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
88
SDR Version Management
7.1
Introduction of Version Management
7.1.1
Introduction of Version Management in OMCBV4.11

OMCBV4.11 supports both SDRV4.11 and SDRV4.09. For SDRV4.09, select Base
Station Software Management. For SDRV4.11, select Multiple Mode Station
Software Management as shown in Figure 7 -64. This guide only focuses on the
SDRV4.11 software management in OMCBV4.11.
In Multiple Mode Station Software Management, the version software can be created,
downloaded, activated, and the SDR running version can be queried, the main interface
is shown in Figure 7 -62.
Figure 7-62 Interface of Multiple Mode Station Software Management
SDRV4.11 version structure:

There are two version packages in the SDRV4.09 version package, one is firmware
package, and the other is software package. Generally, firmware version package is not
required to be upgraded on site (it is even not required in the upgrade from SDRV4.00
to SDRV4.09). The SDRV4.11 version package includes one firmware package, one
PLAT software package, and GSM/UMTS software packages corresponding to different
products as shown in Figure 7 -63.
Figure 7-63 SDRV4.11 Software Version Packages
During the upgrade from SDRV4.00 and SDRV4.09 to SDRV4.11, besides software
version upgrade, the firmware upgrade is also required.
Refer to the upgrade guide of the corresponding version, the detailed procedure is not
specified in this guide. The following contents focus on the basic procedure of version
upgrade and query.
7.1.2
Creating Version
Version creation means the procedure to upload version from client to OMCB server.
Preparation
The link between BSC and OMCB is established successfully.
Procedure
1.
90
Select Multiple Mode Station Software Management as shown in Figure 7 -64.
Figure 7-64 Multiple Mode Station Software Management
2.
In Multiple Mode Station Software Management, click Create Version Package

to upload a version as shown in Figure 7 -65.
Figure 7-65 Clicking Create Version Package
3.
Choose the two version packages to be created, including GSM

(SW_GSM_XXX.pkg) and platform (SW_PLAT_XXX.pkg) version packages as
shown in Figure 7 -66. The sequence of the two packages is not specified.
Generally the software version package is created first.
Figure 7-66 Choosing Version Packages to Be Created
4.
92
After version creation, the corresponding version packages are shown in the left
pane, as shown in Figure 7 -67. The items with COMMON refer to platform
software, and the items with GSM refer to the GSM software.
Figure 7-67 Newly-Created Version Package
7.1.3
Downloading Version
Version download is the procedure to download the created version in OMCB server to
SDR.
Procedure
1.
Click Download as shown in Figure 7 -68.
Figure 7-68 Clicking Download
2.
Choose the items from Packages and Managed Elements, and click Next to
complete version download as shown in Figure 7 -69.
Figure 7-69 Choosing Package and Managed Element
7.1.4
Activating Version
Version activation is to activate the downloaded SDR version as the master version.
Meanwhile, the original SDR running version is switched to the slave version.
Procedure
1.
Click Active as shown in Figure 7 -70.
Figure 7-70 Clicking Active
2.
94
Choose the items from Packages and Managed Elements, and click Next to
complete version activation as shown in Figure 7 -71.
Figure 7-71 Choosing Package and Managed Element
7.1.5
Managing Version
In Station Software Management, the version can be queried, switched, or deleted,
etc.
Procedure
1.
Click Station Software Management as shown in Figure 7 -72.
Figure 7-72 Double-Clicking Station Software Management
2.
In Station Version Management as shown in Figure 7 -73, the software version,

firmware version, hardware information, and patch version can be queried, and the
version can be deleted, switched, or exported, etc.
Figure 7-73 Function Tabs in Station Version Management
96
SDR BTS Commissioning Test

Refer to the corresponding test guide for detailed commissioning test items.
AppA Quick Query of General Information

Conversion Between Absolute Frequency Point
and Frequency
A.1
The conversion between channel No. and absolute frequency point is shown as follows:
Channel No. of GSM900 system:

Uplink: Fl(n)=890+0.2n MHz
Downlink: Fu(n)=935+0.2n MHz 1
frequency point.
124, n means the absolute
Channel No. of E-GSM900 system:

Uplink: Fl(n)=890+0.2n MHz
Downlink: Fu(n)=935+0.2n MHz
0 n 124
Uplink: Fl(n)=890+0.2(n-1024) 975 n 1023

Downlink: Fu(n)=935+0.2(n-1024) 975 n 1023
Channel No. of DCS1800 system:

Uplink: Fl(n)=1710.2+0.2(n-512) MHz
Downlink: Fu(n)=1805.2+0.2(n-512) MHz
512 n 885
IP Address of Each SDR Board
A.2
(Environment No. is 254 by default.)
BBU
Slot 1 (CC-1): 192.Environment No.1.16
Slot 2 (CC-2): 192.Environment No.2.16
Slot 3 (FS-3): 192.Environment No.3.16
98
Slot 5 (UBPG-5): 192.Environment No.5.16
RRU
Remote Rack 2: 200.Environment No.0.2
Remote Rack n: 200.Environment No.0.n
A.3
General SDR Commissioning Commands

Only some general commands are mentioned in this section. Refer to G_TM_SDR
Troubleshooting_R1.0 for details.
A.3.1
SDR Commands in SDRV4.11

The SDR command query mode in SDRV4.11 is different from that in the previous
versions. The general commands are the same as those in SDRV4.09. However, there
are many steps before you type the commands. The following describes the detailed
procedure:
1.
Enter the shell mode.
-bash-3.00$ telnet 172.18.1.2
Log in to SDR
Trying 172.18.1.2...
Connected to 172.18.1.2 (172.18.1.2).
Escape character is '^]'.
(none) login: zte
Type username: zte
Password:
Type password: zte
Processing /etc/profile... Done

# /ushell
Enter the ushell mode
-> Please input password!

->
Type password: zte
***
-> Login success!!
ushell tool menu:
-----------------------------------------------------------------------------'ps'
or
'PS'
list process run on the board
'pr xxx' or
'PR xxx'
'npr xxx' or
'NPR xxx' not take over xxx process printf info
'db xxx' or
'DB xxx'
'ndb xxx' or
'NDB xxx' not debug xxx process printf info
'pad xxx' or
'PAD xxx'
'npad xxx' or
'NPAD xxx'not debug and take over xxx process printf info
'pall'
or
'PALL'
'Q'
or
'q'
'exit'
or
'EXIT'
take over xxx process printf info

debug xxx process printf info
debug and take over xxx process printf info
display current debug and take over info
cancel all process debug and printf info
cancel ushell
xxx is process id you want to debug or take over printf info

-----------------------------------------------------------------------------$$
2.
Use the ps command to query the process No. of MGR and Product_gsm.
$$ps
PID USER
1 root
100
VSZ STAT COMMAND

1452 S
init
2 root
0 SW [softirq-high/0]
3 root
0 SW [softirq-timer/0]
4 root
0 SW [softirq-net-tx/]
5 root
0 SW [softirq-net-rx/]
6 root
0 SW [softirq-block/0]
7 root
0 SW [softirq-tasklet]
8 root
0 SW [softirq-sched/0]
9 root
0 SW [softirq-hrtimer]
10 root
0 SW [softirq-rcu/0]
11 root
0 SW [watchdog/0]
12 root
0 SW [chkeventd/0]
13 root
0 SW< [events/0]
14 root
0 SW< [rt_events/0]
15 root
0 SW< [khelper]
16 root
0 SW< [kthread]
17 root
0 SW< [rt_kthread]
36 root
0 SW< [kblockd/0]
66 root
0 SW [pdflush]
67 root
0 SW [pdflush]
68 root
0 SW< [kswapd0]
69 root
0 SW< [aio/0]
601 root
0 SW [mtdblockd]
640 root
0 SW [fla-thread]
657 root
917m S
/MGR.EXE
665 root
1448 S
telnetd
667 root
1536 S
/bin/sw
Platform command
A.3.2
668 root
1536 S
/bin/sw
669 root
1536 S
/bin/sw
670 root
1536 S
/bin/sw
671 root
1536 S
/bin/sw
672 root
1456 S
-/bin/ash
673 root
1536 S
/bin/sw
820 root
117m S
/Product_gsm.o 76 81
877 root
1460 S
-sh
878 root
9184 R
/ushell
880 root
1448 R
sh -c ps
881 root
1452 R
ps
GSM command
Checking SDR Running Version

Enter the platform mode.
$$pad 657
Enter platform mode
$$
[657]
ushell enter debug mod
Use the VMP command to query Version No.

$$VMP
Type the VMP command.
[ begin to excel fun:VMP
**************** VMP Status Info *************

RELEASE VERSION
The Board Status -------------- MasterBoard
CPU Run Status ---------------- update
Run CC Version ---------------- 4.11.10.14P04
Run CC File Length ------------ 6496668
Bak CC Version ---------------- null
Bak CC File Length ------------ null
Running Status ---------------- S_MasterIdle
Run Package Path -------------- /mnt/flash/SW2/
Run Package Version ----------- 4.11.10.14P04
Bak Package Path -------------- /mnt/flash/SW1/
Bak Package Version ----------- 4.00
********************************************
value = 45(0x2d)
[ end to excel fun:VMP
3.
Check RRU version.
Log in to the RRU board to check RRU version in either of the following methods:
Direct login: Connect the PC to the commissioning network port on the side of RRU
with network cable. Configure the IP address of the PC as 199.33.33.1/24.
Telnet to 199.33.33.33.
Login through CC: Telnet to CC, use telnet 200.254.0.x command (not
necessary to enter the ushell mode in advance), in which x refers to remote Rack
No. After logging in to RRU, type the svi command. Main CPU Version (CPU),
Main FPGA Version (FPGA), and Main IFFPGA Version (DSP) are the required
running versions (marked in red). Confirm the versions instead of recording them.
DTR->svi
Main CPU Version:
Header Version = 0x1010101
Versin Type = 0
Cpu Type = 37
Compressed Size = 988583
Original Size = 4042901
Soft Type = 208
Version Number = 4.00.100b
Create Time = 2008-12- 3 4:18: 1
Slave CPU Version:
Versin Type = 0
Cpu Type = 37
Soft Type = 208
Version Number = 8.11.070e
Create Time = 2008-11- 7 9: 9:23
Main FPGA Version:
Versin Type = 1
Cpu Type = 0
Soft Type = 65744
Create Time = 2008-12- 3 4:18:13
Slave FPGA Version:
Versin Type = 1
Cpu Type = 0
102

Soft Type = 65744
Version Number = 8.11.030a
Create Time = 2008-11- 3 9:35:24
Main IFFPGA Version:
Versin Type = 8
Cpu Type = 0
Soft Type = 524496
Create Time = 2008-12- 3 4:18: 9
Slave IFFPGA Version:
Versin Type = 8
Cpu Type = 0
Soft Type = 524496
Version Number = 4.00.100a
Create Time = 2008-10-31 15: 3:18
value = 20 = 0x14
A.3.3
Checking Link Status of the Board

$$pad 657
$$
[657]
ushell enter debug mod
Type the OSS_DbgShowComm command, the following information is shown (CC boards
are configured at Slot 1 and Slot 2. FS is configured at Slot 3. UBPG is configured at
Slot 5. Three RRUs are configured.)
$$ OSS_DbgShowComm
Rudp Link Table(Board is master):
Item (subsys module unit sunit ) pos state IP(hex) mac sndQ bufQ udpQ work
0 (0 1 0 1 )
L 0 c0fe0110 00:00:00:00:00:00 0
0 (0 1 0 1 )
R 3 c0fe0210 00:00:00:00:00:00 0
0 0
1 (3 1 0 1 )
L 3 c0fe0510 00:00:00:00:00:00 0
0 0
1 (3 1 0 1 )
R 0 ffffffff
2 (1 1 0 1 )
L 3 c0fe0310 00:00:00:00:00:00 0
00:00:00:00:00:00 0
0 0
0 0
0 0
2 (1 1 0 1 )
R 0 ffffffff
3 (17 1 0 1 )
L 3 c8fe0004 00:00:00:00:00:00 0
00:00:00:00:00:00 0
3 (17 1 0 1 )
R 0 ffffffff
4 (16 1 0 1 )
L 3 c8fe0003 00:00:00:00:00:00 0
4 (16 1 0 1 )
R 0 ffffffff
5 (15 1 0 1 )
L 3 c8fe0002 00:00:00:00:00:00 0 0 0
5 (15 1 0 1 )
R 0 ffffffff
00:00:00:00:00:00 0
00:00:00:00:00:00 0
00:00:00:00:00:00 0
0 0
0 0
0 0
0 0
0 0
0 0
0
0
0
GroupTable:
127,255,
value = 2 = 0x2
In the above print information, the IP address of each board is shown in the hexadecimal
format. For example, c8fe0002 in the hexadecimal format equals 200.254.0.2 in the
decimal format. It refers to the RRU in Rack 2.If the value of State is 3, it indicates the
link with the master CC board is available.
A.3.4
Checking Relation of Physical TRX and Logical TRX

Enter the platform mode. Use the ShowPhyLog command to view the relation
between the physical TRX and logical TRX, and the corresponding FS and UBPG
boards of the TRX.
A.3.5
Checking RU Running Information

Log in to the RU. Use the showrru command to view the RRU working frequency, output
power, and VSWR, etc.
104

ZXSDR (V4.11.10.14P04) Engineering Commissioning Guide - R1.4 - 438022

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

ZXSDR (V4.11.10.14P04) Engineering Commissioning Guide - R1.4 - 438022

Enviado por

Direitos autorais:

Formatos disponíveis

ZXSDR

ZTE Confidential Proprietary

2015 ZTE CORPORATION. All rights reserved.