GU - ZXSDR (V4.12) Quick Data Configuration Guide - R1.2

ZXSDR(V4.
12)
Quick
Configuration Guide
Data
ZXSDR(V4.12) Quick Data Configuration 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 2016 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
Address:
Address: NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
Website:
http://dms.zte.com.cn
Email:
TSM.Aftersales@zte.com.cn
ZTE Confidential Proprietary
2016 ZTE CORPORATION. All rights reserved.
Revision History
Product Version
ZXSDR V12.12.40B4.
ZXSDR V12.12.40P55
Document Version
Serial Number
Reason for Revision
1.0
First published
1.2
The Plan template is

changed, and the
instructions for some
fields are updated.
Author
Date
2012-12-28
2012-07-01
2014-02-28
Document Version
Prepared
by
Reviewed by
Approved by
1.0
Ma
Chunxin
He Yijun
Chen Taiming
1.1
Ma Chunxi
n, Zhao Ya
nghao
He Yijun
Chen Taiming
1.2
Ma
Chunxin
He Yijun
Chen Taiming
Intended audience: Base station commissioning staff
II
2016ZTE CORPORATION. All rights reserved.
About This Document

Summary
Chapter
Description
1 Plan Template
It gives a simple introduction to the Plan Template.
2 Plan Template Filling

Specifications
It describes the specifications for filling in the Plan Template.
3 Data Import and Export Functions
It describes the data import and export functions.
4 Explanation of Common
Operations
It gives the explanation of some common operations.
5 Examples of Data Configuration
It gives some examples on data configuration procedure.
III
TABLE OF CONTENTS
1
1.1
1.2
1.3
Plan Template...................................................................................................1
Plan Template....................................................................................................1
Template Acquisition Path..................................................................................1
Description of Template Format.........................................................................2
2
2.1
2.1.1
2.1.2
2.1.3
2.2
2.2.1
2.3
2.3.1
2.3.2
Plan Template Filling Specifications..............................................................4

Ground Plan Template Filling Specifications......................................................4
Basic Parameters...............................................................................................
Equipment Parameters......................................................................................
Transmission Parameters................................................................................
Wireless Plan Template Filling Specifications..................................................29
Description of the Sheets.................................................................................
GSM Wireless Plan Template Filling Specifications.........................................33
RU (GSM) Sheet..............................................................................................
GSM Carrier Sheet..........................................................................................
3
3.1
3.2
3.3
Data Import and Export Functions...............................................................37

Notices in Operation........................................................................................37
Planning Data Import.......................................................................................38
Planning Data Export.......................................................................................39
4
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.2
Explanation of Common Operations............................................................42

Examples of Configuration Scenario................................................................42
Adding BPC Board...........................................................................................
E1 Capacity Expansion/Reduction...................................................................
Batch Configuration Data Modification.............................................................
Snapshot Area Data Recovery.........................................................................
Acquisition of LMT Configuration File...............................................................51
Examples of Data Configuration...................................................................54
IV
FIGURES
Figure 1-1 Generate Template................................................................................................1
Figure 1-2 Template Storage Path..........................................................................................2
Figure 3-1 Planning Data Import...........................................................................................38
Figure 3-2 Set the Path of Plan Templates...........................................................................38
Figure 3-3 View Log File.......................................................................................................39
Figure 3-4 Planning Data Export...........................................................................................39
Figure 3-5 Planning Data Export Window.............................................................................40
Figure 3-6 Data Type............................................................................................................40
Figure 3-7 File Path..............................................................................................................41
Figure 4-1 Add BPC Board...................................................................................................42
Figure 4-2 Import Data to OMC............................................................................................43
Figure 4-3 Data Synchronization..........................................................................................44
Figure 4-4 Incremental Synchronization...............................................................................45
Figure 4-5 Planning Data Export...........................................................................................46
Figure 4-6 Export PLAT Data................................................................................................47
Figure 4-7 Modification to the Transmission Sheet...............................................................47
Figure 4-8 Modification to Parameters in the PhyLayerport Sheet......................................47
Figure 4-9 Batch Configuration Data Modification.................................................................48
Figure 4-10 Batch NEs Operation........................................................................................50
Figure 4-11 Copy Snapshot Area Data to Modify Data..........................................................51
Figure 4-12 Data Synchronization........................................................................................52
Figure 4-13 Only Generate File............................................................................................53
TABLES
Table 2-1 Instructions on Filling in Sheets in Ground Plan Template.......................................4
Table 2-2 The ManagedElement Sheet...................................................................................6
Table 2-3 The IpClock Sheet...................................................................................................9
Table 2-4 The Clock Sheet....................................................................................................10
Table 2-5 The RU Sheet.......................................................................................................12
Table 2-6 The PA Sheet........................................................................................................15

Table 2-7 The FCE Sheet.....................................................................................................16
Table 2-8 The AISG Sheet....................................................................................................18
Table 2-9 The PowerOutlet Sheet.........................................................................................19
Table 2-10 The Epm Sheet...................................................................................................21
Table 2-11 The FiberCable Sheet.........................................................................................22
Table 2-12 The RfCable Sheet..............................................................................................22
Table 2-13 Transmission.......................................................................................................23
Table 2-14 The PhyLayerPort Sheet.....................................................................................24
Table 2-15 The EthernetLink Sheet.......................................................................................25
Table 2-16 The HDLC Sheet.................................................................................................25
Table 2-17 The PPP Sheet...................................................................................................25
Table 2-18 The IpLayerConfig Sheet....................................................................................26
Table 2-19 The Sctp Sheet...................................................................................................27
Table 2-20 The ItfUniBts Sheet.............................................................................................28
Table 2-21 The ServiceMap Sheet........................................................................................29
Table 2-22 Description of Sheets in UMTS Wireless Plan Template.....................................29
Table 2-23 The UMTS Radio Sheet......................................................................................30
Table 2-24 UMTS Sector......................................................................................................30
Table 2-25 UMTSLocal Cell..................................................................................................31
Table 2-26 ULocalCellRelation..............................................................................................33
Table 2-27 Description of Sheets in GSM Wireless Plan Template.......................................33
Table 2-28 RU(GSM) Sheet..................................................................................................34
Table 2-29 GSM Carrier Sheet..............................................................................................36
VI
Plan Template
1.1
Plan Template
The Plan Template consists of the Ground Plan template and Wireless Plan template.
Different modes of products share the same Ground Plan template, but each mode has
a different Wireless Plan template. Therefore, for multi-mode sites, it is necessary to fill
in a Ground Plan template and several Wireless Plan templates.
Since the Ground Plan template supports multi-scenario and multi-mode, it consists of
many sheets, which are complicated to fill in. Starting from V12.12.40P55, we can select
the template according to the network mode, transmission, and scenario. When the
template is acquired, first open the Choose sheet, select the network mode,
transmission type, and special scene based on the field requirement, and click the
Generate Template button. The unwanted irrelevant sheets will are automatically
hidden, which makes the template look simple and convenient for fill-in.
Figure 1-1 Generate Template
1.2
Template Acquisition Path

1.
All
the
Plan
Templates
are
saved
in
the
template
of
the
ZXSDR_OMMB_Tools_V12.12.40 version package, as shown in Figure 1 -2.
OSS_PLAT_CM_Ground_Plan.xls is the Ground Plan Template, and others are
the Wireless Plan Templates of different modes, such as GSM, LET FDD, LTE
TDD, TDS, and UMTS.
Figure 1-2 Template Storage Path
2.
1.3
The Ground Plan Templates and Wireless Plan Templates of the existing sites can
also be exported from the OMMB of the same version. Refer to Chapter 3.3
Planning Data Export for details.
Description of Template Format

1.
Conventions of Table Header

The first row is the database name. Do not modify this row. Otherwise, the data in
the Plan Template will fail to be imported.
The second row is the field name displayed on OMM.
The third row gives the description about the value range of a field.
The fourth row is the specifications, restrictions, and examples of the field data
configuration.
The fifth row provides the attributes of a field: whether the field is Primary Key,
whether it can be modified (W), and whether it is required to be filled in (I).
The configuration data of each site starts from the sixth row.
2.
Conventions of Sheet Arrangement

The first sheet is the TemplateInfo sheet. It contains the description of the
template imported and cannot be modified.
The second sheet is the Index sheet. It provides the functions of different sheets.
The sheets from the third sheet contain the data to be imported. The names and
order of the sheets cannot be changed.
3.
Description of Operators
A (ADD): Add a new record.
M (MODIFY): Modify the record.
D (DELETE): Delete the record.
P (PASS): Do not perform any operation to the record of this row.
Plan Template Filling Specifications

This Guide is based on the Plan Template released with V12.12.40B4.The Plan
Template of different versions may be a little different in the parameters, but the filling
method is almost the same.
2.1
Ground Plan Template Filling Specifications

The Ground Plan template has 39 sheets. Some of the sheets do not need to be filled in
some scenarios. This Guide introduces the GU related sheets. The specifications of
filling in the sheets are detailed in the following sections.
Table 2-1 Instructions on Filling in Sheets in Ground Plan Template

No.
Description
Managed Network
Element
Managed Element sheet: The NE here refers

to SDR base station. It involves subnetwork and
NE.NE parameters: NE Name,
ManagedElement ID, NE Type, External IP, NE
Version, Longitude, and Latitude.
Cabinet
This sheet is used to configure the data of the

slave cabinet. The primary cabinet and the
auxiliary cabinet are not configured in this
sheet, because the primary cabinet has been
created with the creation of NE. Currently, the
auxiliary cabinet is used to put FCE board.
When FCE is created, the auxiliary cabinet is
created together.
Equipment
This sheet provides the configuration

information of the board on the main rack of
BBU.
Time Device
This sheet contains the Time Device, Time

Zone, and NTP Server IP Address parameters.
IpClock
This sheet is about the 1588 clock

configuration. If master/slave configuration is
used, each site should be configured with two or
more records.
Clock
This sheet provides the configuration of clock

reference source and the configuration of
related parameters when GNSS reference
source is selected. If 1588 clock reference
source is selected, IpClock must be configured
before the configuration of Clock.
RU
Sheet Name
This sheet is about the configuration of RU

device, including RRU and RSU related
No.
Sheet Name
Description
information.
Fiber Device
Optical port device. When the board of RU,

BPL, FS, or BBU is created, the related
information of the optical port device is created
together. The value of the parameter is the
default value. If the default value is not
consistent with the actual value, modify it
through this sheet. Therefore, only the M
operation can be performed in this sheet,
including Optical Port Module, Protocol Type of
Optical Module, FS Optical Module Type, etc.
PA
It is the power amplifier of RU device. PA

related information has been created with the
creation of RU, BPL, or FS. Use the default
value of the parameter. If the default value is not
consistent with the actual value, modify it
through this sheet. Therefore, only the M
operation can be performed in this sheet,
including Radio Mode, Dual Mode Working
Mode, etc.
10
FCE
It is the fan control and environment monitoring

board. The FCEs of the primary cabinet,
auxiliary cabinet, and slave cabinet are all
configured in this sheet. For the auxiliary
cabinet, it is necessary to fill in the Cabinet No,
and the related records will also be generated in
this process.
11
DryContact
This sheet is about dry contact configuration.

Currently, there is dry contact on SA, SE, and
FCE.
12
Tma
TMA equipment related parameters
13
AISG
This sheet is about AISG device configuration. It

is an abstract AISG control port. It is used for
RET to control down tilt and for TMA to amplify
signals
14
PowerOutlet
It is about power output configuration. Currently,

power output exists on the TAM board and RU.
15
EPm
Embedded power supply equipment is a device

connected externally.
16
Fiber Cable
Fiber resource. It is about the connection

between BBU and RU and between RUs.
17
RfCable
RF connection and RF feeder resources. It

refers to the connection among RU port,
antenna, and TMA. If the RU port configured is
connected with the antenna, the antEntity
record will be created automatically according
the contents filled in by the user.
18
RfExtendCable
This sheet is used to configure RF extension

cable. It is about the connection between RU
ports.
No.
Sheet Name
Description
19
Transmission
Overall transmission parameters. The

parameters in this sheet include Transmission
Type, ATM Address, etc. Currently it is only
necessary to fill in this sheet in the GU and the
TDS mode.
20
PhyLayerPort
The physical layer in the IP or the ATM

transmission protocol. Physical layer bearer
includes E1, T1, and Ethernet.
21
Hdlc
HDLC protocol related parameters include

HDLC link No., E1T1 link No., HDLC timeslot,
TSI, etc. This sheet applies only to GU.
22
Ppp
This is the sheet of PPP protocol-related

parameters This sheet applies only to GU.
22
IP Layer Configuration
IP layer parameters configuration.
23
Static Route
Static route parameters configuration.
24
BandwidthResource
This sheet contains bandwidth resource

parameters.
25
SCTP
This sheet is about SCTP parameters

configuration. SCTP protocol provides a stable
and continuous data transfer servers between
two points. It is used in the IP network to
transmit signaling.
28
Itf-UniBTS
OMC channel parameters
29
ServiceMap
This sheet is used to configure the mapping

between service and DSCP.
The sheets of Ground Plan template can be divided into three types, sheets of basic
parameters, sheets of equipment parameters, and sheets of transmission parameters.
The instructions of filling in the data of the functional modules are described in the
following sections.
2.1.1
Basic Parameters
2.1.1.1
ManagedElement
Fill in the basic information of NEs in this sheet, such as External IP, NE Type, NE
version, Longitude, and Latitude.
The filling of this sheet is mandatory. Each NE occupies one row.
Refer to Table 2 -2 for the key parameters.
Table 2-2 The ManagedElement Sheet

Item
RADIOMODE
Parameter
Name
Radio
Mode
SWVERSION
NE version
RNCID
The home
UMTS RNC
No.
operator
Operator
and PLMN
Value Description
Instructions
1:UMTS{UMTS},
2:GSM{GSM},
4:TD-SCDMA{TDSCDMA},
8:CDMA{CDMA},
16:LTE FDD{LTE FDD},
32:TD-LTE{LTE TDD}
For multi-mode versions,
it is necessary to type in
several figures, which
should be separated by
English character ;, for
example, 4;32. 4;32
The property of this

parameter is W, which
means this parameter
can be modified, but
there is a restriction on
the modification, i.e.,
this parameter can only
be modified when the
radio mode is
expanded, e. g., from
GU to GUL, but not from
GUL to GU or from G to
U.
This parameter should
be modified together
with the SWVERSION
parameter.
NE Version, e.g.,
L_V3.10.01
The property of this

parameter is W, which
means this parameter
can be modified, but
there is a restriction on
the modification, i.e., it
can only be modified in
the mode expansion
scenario.
This parameter should
be modified together
with the RADIOMODE
parameter.
For the configuration
specifications, refer to
the chapter of NE
Compatibility in the
ZXSDR OMMB
V12.12.40P55 Release
Notes.doc in the OMMB
version package. For
example: UniRan
12.3(GU_V4.11.10.08P0
5)
0-65535
This parameter must be

configured correct,
otherwise, the report of
northbound data will be
affected.
It must be configured.
Format: operator name
#mcc#mnc&mcc#mnc
For example: China
Item
Parameter
Name
Value Description
Instructions
Telecom#460#01
MAINTAINSTATU
S
Maintenanc
e status
2.1.2
Equipment Parameters
2.1.2.1
Cabinet
0: Normal
2: testing
3: configuring
5: FM testing
6: PM testing
For the newlyconstructed site,

configure it to 0: Normal.
Otherwise, after the
transmission is set up,
the link between the
base station and OMMB
cannot be set up
successfully.
This sheet is used to configure the data of the slave cabinet. Each slave cabinet
occupies one row.
The primary cabinet and the auxiliary cabinet are not configured in this sheet,
because the primary cabinet has been created with the creation of NE. Currently,
the auxiliary cabinet is used to place the FCE board. When FCE is created, the
auxiliary cabinet is created together.
The filling of the fields in this sheet is very simple (refer to the instruction of the
template), and no further description will be given in this Guide.
2.1.2.2
Equipment
This sheet is used to configure the information of the board on the main rack of BBU. All
slots have been listed in the sheet. It is only necessary to fill in the corresponding slot
according to the actual configuration. The sheet supports 2U and 3U BBU configuration.
Each NE occupies one row. One row represents the board configuration of one main
rack of BBU. Because the main rack cannot be deleted, the data in this sheet does not
support the D operation.
IMPORTANT:
It is necessary to fill in three kinds of information for each slot, i.e., board type, radio
mode, and function mode, which should be separated with English character ;. Refer to
the filling instruction and example in the Equipment" sheet for the detailed format.
2.1.2.3
TimeDevice
This sheet is used mainly to configure the NTP Server IP Address, NTP Standby Server
IP Address, Time Zone, and Summer Time Start parameters.
Only when the CC board is configured can this sheet be configured.
2.1.2.4
IpClock
This sheet is used to configure 1588 clock server. When the ClockType in the Clock
sheet is 1500 clock, this sheet is required to be filled in.
This sheet supports the configuration of 1588 slave server. The data of the master
server and the slave server occupies one row respectively.
Table 2-3 The IpClock Sheet

Item
Parameter Name
Value Description
clockType
1588 Clock Device

Type
1: Ordinary clock
2: Boundary clock
It indicates the 1588 clock device type
adopted by the base station.
The parameter must be configured the
same on the master server and the slave
server.
linkPriority
Link Priority
Value range: 1 32.

Link priority of IP clock
networkProtocol
PTP Network
Protocol
1:IPV4,
2:IPV6,
3: Ethernet
transType
IP Clock
Transmission
Mode
Transmission mode of 1588 clock

packets:
0: Multicast
1: Unicast
2: Hybridcast
syncServerAddr
1588
Synchronization
Server IP Address
This item must be configured for IP 1588

clock reference source. This attribute is
valid only when Ethernet transmission is
used.
Used IP Layer
Configuration by
1588 IPClock
It is the IP link used to configure UDP

link.
The planning data import process
refIpLayerConfig
Item
Parameter Name
Value Description
automatically creates the UDP link of
1588 clock according to the IP link.
The value of this parameter is from the
ipNo field in the IpLayerConfig sheet.
Therefore, it is required that the ipNo
field has been configured.
The Ethernet bearer link and the UDP
link are mutually exclusive. This
parameter is mutual exclusive with the
refEthernetLink field. It is only necessary
to fill in one of them.
refEthernetLink
vid
2.1.2.5
Used Ethernet
Link No.
The value of this parameter is from the

ethernetLinkNo field in the
EthernetLink sheet. Therefore, it is
required that the ethernetLinkNo field
has been configured.
The Ethernet link and the UDP link are
mutually exclusive. This parameter is
mutual exclusive with the
refIpLayerConfig field. It is only
necessary to fill in one of them.
VLAN ID
The value of the parameter is from one

of the values of the vlanMembership
field in the EthernetLink sheet.
The value of this parameter should be
the same as the value of a VLAN in the
Ethernet link.
Clock
This sheet is used to configure clock reference source. If clock reference resource is
configured, it is required to fill in this sheet.
One clock reference source occupies one row. One NE can be configured with two or
more clock reference sources of different priority.
Table 2-4 The Clock Sheet

Item
clockSyncMode
clockType
10
Parameter
Name
Value Description
Clock
Synchronization
Mode
This parameter is used to synchronize

base station and clock reference source.
0: Frequency synchronization
1: Phase synchronization
Clock
Reference
1: Inner GNSS
2: Outer facepanel GNSS
Item
clockPriority
receiverHardwareType
receiverType
receiverOperatingMode
minStarNum
Parameter
Name
Value Description
Source Type of
Clock Device
3: Outer backpanel GNSS

17: RRU inner GNSS
4: 1PPS+TOD
5: GNSS cascade clock
14: 1PPS+TOD backup
6: BITS-2MHz clock
7: BITS-2Mbps clock
8: Line clock-local board
13:SyncE clock,
10:SyncE+1588 clock},
11:1588{1588}
Clock Priority of
Clock
Reference
Source Type
Value range: 1 8.
This parameter indicates the priority of
clock reference resource.1 refers to the
top priority.
GNSS Receiver
Hardware Type
1: USR1_A
2: Outer compass receiver
3: RGPS
4: UCI_RGPS
5:UCI_COMPASS
If built-in GNSS is used, this parameter is
invalid and does not need to be
configured.
External plane GNSS CDMA: 0,2,3,4;
TDS: 4,5; TDL:4.5
External backplane GNSS value range:
0,4,5
GNSS Receiver
Working Type
1: GPS
2:GLONASS
3:GPS+GLONASS
5: COMPASS
7: COMPASS priority
8: GPS priority
13: Receiver self-adaptive
Receiver
Operating
Mode
This parameter is used to configure the

operating mode of GNSS receiver.
"Survey In" is recommended but "Fixed
Mode" is not recommended.
1: Survey In
2: Fixed Mode
For GU, LTE-FDD, TD-SCDMA, and
LET-TDD, this parameter can be
configured. For other products, this
parameter cannot be configured.
GNSS
Minimum
Number of
long:[1..4]
It indicates the minimum number of
satellites for satellite timing. It is also the
Item
enableSyncE
isSSM
2.1.2.6
Parameter
Name
Value Description
Search Stars
parameter of satellite alarm threshold

and the default value is 4.
Enable SyncE o
r not
1: Yes,
0: No
This parameter can be configured only
when clockType is SyncE+1588 clock.
Enable SSM
1: Yes
0: No
This parameter can be configured only
when clockType is SyncE+1588 clock
or SyncE clock.
This parameter indicates whether the
clock upload mode is Synchronization
Status Message (SSM).SSM is the
quality level for sending timing signals
through the timing synchronization link in
the synchronization network. The node
clock in the synchronization network
obtains the parent-node clock
information by reading the SSM, and
performs related operations on the clock
of local node, such as tracing and
changeover. Meanwhile the
synchronization message of local node is
sent to the subordinate node.
RU
This sheet is used to configure RU and related information. The filling of this sheet is
mandatory. Each RU occupies one row.
IMPORTANT:
RU falls into RRU and RSU. There are two kinds of RSU configuration: 1. Configure
RSU in the primary cabinet. If the RSU rack has been created during the creation
process of the primary cabinet, configure the RSU directly in this sheet; 2. Configure
RSU in the slave cabinet. It is necessary to create the slave cabinet in the Cabinet sheet
and then configure RSU in this sheet.
Table 2-5 The RU Sheet

Item
RUDevice
12
Parameter Name
RU Board, incl.
RRU and RSU
Value Description
Format: RackNo, ShelfNo, SlotNo,
The value ranges are:
RackNo: RRU:51..201, RSU:2..50
Item
Parameter Name
Value Description
ShelfNo: 1
SlotNo: 1
e.g., 51,1,1
radioMode
functionMode
connectModeWithUpRack
diversityMode
rruGnssCableLength
Radio Mode
For multi-mode configuration, the

values need to be separated by
English character ;, for example,
4;32
0:ALL,
1:UMTS,
2:GSM,
4:TD-SCDMA,
8:CDMA,
16:LTE FDD,
32:TD-LTE
Function Mode
Its value is related to the RU type.

0:GSM/LTE FDD Mixed
Mode(Ignore the radio mode of
PA),
1:UMTS Single Mode,
2:GSM Single Mode,
5:LTE-FDD Single-carrier,
1280:LTE-FDD Single Mode,
1281:LTEFDD Two-carrier,
100663297:LTE-IR,
452984833:LTE-IR,
452984841:LTE-IR(IQ
Compressed),
50331653:TD-SCDMA IR,
24:GSM/UMTS Mixed Mode,
26:GSM/LTE FDD Mixed Mode
Uplink Connection
Mode
This parameter indicates the

attributes of RU optical port device
set. It is an optional parameter and
should be configured according to
the actual requirements.
0:single up-link optical line,
1:double master & slave optical
lines,
2:multiple load-sharing optical lines
Diversity
Reception Mode
This parameter is used to configure

the attributes of RU RF port device
set. It is an optional parameter and
should be configured according to
the actual requirements.
0: Normal diversity reception
1: Cross diversity reception
RRU GNSS Cable

Length
long:[0..8000]
step:1
Item
Parameter Name
Value Description
unit: m
It indicates the length of the feeder
from RRU GNSS antenna to the
receiver. This feeder is used to
improve the clock precision. This
attribute should be filled in
according to the on-site survey
result. It is an optional parameter.
It needs to be configured when
RRU is R8964T S2600 and the
clock type is RRU inner GNSS.
2.1.2.7
FiberDevice
This sheet is used to configure optical port related information. The filling of this sheet is
optional.
Optical port device data will be created with the creation of the boards with optical port
device such as RU, BPL, and FS. If the values of the optical port device related
parameters are not consistent with the default values, they may need to be modified in
this sheet. Therefore, only the Modify (M) operation is allowed in this sheet, while the
Add (A) or Delete (D) operations cannot be performed.
In other cases, do not fill in this sheet.
2.1.2.8
PA
This sheet is used to configure the PA related information of RU devices. The filling of
this sheet is optional.
PA related parameters will be created with the creation of RU. When the values of the PA
parameters are inconsistent with the default values, they may need to be modified in this
sheet. In other cases, it is not necessary to fill in this sheet. Therefore, only the Modify
(M) operation is allowed in this sheet, while the Add (A) or Delete (D) operations
cannot be performed
Table 2-6 The PA Sheet
14
Item
Parameter
Name
RUDevi
RU Board of
Value Description
Item
Parameter
Name
Value Description

ShelfNo: 1
SlotNo: 1
ce
PA
port
Port No. no
the
RU
device of PA
long
suppBa
nd
Frequency
Band ID
It is the frequency band ID of the port on the RU device of

PA. It is used together with the RU Device and port to define
one PA.
E.g.: 51,1,1
Note: For multi-mode configuration, the values need to be

separated by English character ;, e.g., 4;32
radioMo
de
Radio mode
of PA
dualMod
e
Dual-mode
Working
Mode of PA
branchB
and
Subfrequency
Band
0:ALL,
1:UMTS,
2:GSM,
4:TD-SCDMA,
8:CDMA,
16:LTE FDD,
32:TD-LTE
The allocation method of PA resources in dual-mode, for
example, 2G+2U indicates the PA supports two GSM carriers
and two UMTS cells.
1,2,3,255: Invalid
The sub-frequency band supported by PA.
Sub-frequency is the special attribute owned by GSM. Only
the RU of 900M and 1800M use sub-frequency.
900M (BandVIII) sub-frequency consists of:
1: Work band: UL 890MHz-915MHz, DL 935MHz-960MHz;
1800M(BandIII) sub-frequency consists of: 900M (BandVIII)
sub-frequency consists of:
1: Work band: UL 1710MHz-1765MHz, DL 1805MHz1860MHz

2: Work band: UL1730MHz-1785MHz, DL 1825MHz1880MHz
txCenter
Freq
Tx
Central
Frequency
Point
rxCenter
Freq
Rx Central
Frequency
Point
This parameter is not related to PA. It is the central

transmission frequency point of Tx Channel.
The configuration of txCenterFreq is increased by 10 M on
the basis of 3GPP protocol.
The value range should be selected according to the
frequency band of the equipment. Every frequency band can
be set as 0Modification to this parameter requires
prudence.0 indicates automatic calculation by SDR.
This parameter is not related to PA. It is the central
transmission frequency point of Rx Channel.
The configuration of txCenterFreq is increased by 10 M on
the basis of 3GPP protocol.
The value range should be selected according to the
frequency band of the equipment. Every frequency band can
Parameter
Name
Item
Value Description
be set as 0 Modification to this parameter requires
prudence. 0 indicates automatic calculation by SDR.
2.1.2.9
FCE
This sheet is used to configure the FCE board (fan control and environment control).
One FCE board occupies one row.
The FCEs of the primary cabinet, auxiliary cabinet, and slave cabinet are all configured
in this sheet.
Before configuring the FCE of the slave cabinet, make sure the slave cabinet has been
configured in the Cabinet sheet.
In the process of configuring the FCE of the auxiliary cabinet, it is not necessary to
create an auxiliary cabinet separately, because the cabinet will be created automatically
by this sheet when the CTRL_AUX_CABINET_NO field (auxiliary cabinet No.) is filled in.
2.1.2.10
DryContact
This sheet is about dry contact configuration. The filling of this sheet is optional.
Dry contact data will be created when the SA, SE, and FCE boards are created. This
sheet also supports the configuration of customized dry contact.
Table 2-7 The FCE Sheet

Item
Value Description
Dry Contact
Info
Dry contact needs to be configured on the

slot, shelf, and rack of the SA, SE, FCE, and
RU board.
For example: 51,1,1
dryNo
Dry Contact No.
It indicates the No. of the dry contact alarm to

be configured. The boards that support dry
contact alarms include the SA, SE, and FCE
boards, and RF boards.
userLabel
Dry contact
It contains 128 bytes at most. Default: null.
DryContact Board
16
Parameter
Name
Item
Value Description
description
Do not use symbols like & ' " < > # % / \ ? @ :

,
Dry Contact
Type
0: Input dry contact

1: Output dry contact
outDryType
Output Dry
Contact Status
It is used to configure the output dry contact

configuration status. This parameter is valid
only when the dry contact type is output dry
contact.
0: Output low level. 1: Output high level.
outDryName
Output Dry
Contact Name
The output dry contact description is userdefined. This parameter is valid only when
the dry contact type is output dry contact. It
contains 128 bytes at most
Alarm Status
This parameter is used to configure dry

contact alarms. It is valid only when the dry
contact type is input dry contact.
0: Alarm when closed
1: Alarm when open
Dry Contact
Alarm Name

contents of dry contact alarms. This
parameter is valid only when the dry contact
type is output dry contact. The user can
either define the contents of the dry contact
or choose the dry contact alarm
preconfigured in the system.
dryType
almStatus
almNo
2.1.2.11
Parameter
Name
Tma
This sheet is used to configure TMA equipment. The filling of this sheet is optional. One
TMA occupies one row.
The configuration in this sheet is used to configure TMA gain and other related
parameters.
2.1.2.12
AISG
This sheet is used to configure the PA related information of AISG devices. The filling of
this sheet is optional. One AISG device occupies one row.
The configuration of this sheet is used to configure AISG devices. It is used for RET to
control down tilt and for TMA to amplify signals.
It is necessary to configure RfCable. Only when RF connection is configured can AISG

devices work normally.
Table 2-8 The AISG Sheet

Item
Value Description
Aisg Board
RU Board Info

which should be configured in the
RU sheet in advance.
ShelfNo: 1
SlotNo: 1
For example: 51,1,1
uniqueId
Device Serial
Number
Value range: 1 32.

This is the unique SN of the device.
devType
Device Type
1:RETC,
17:MULTI_RET,
3:ATMA,
90:NOTCH_FILTER,
2:MULTI_TMA,
241:ACOM,
226:AETMA,
209:NSNRET,
210:LGPTMA
Users should select a device type
according to the actual situation.
vendorCode
Vendor Code
127 bytes at most
aisgVersion
AISG Version
1:1.1
2:2.0
multiAntNo
Multi-sub-unit No.
Value range: 1 4. 255: Invalid.
userLabel
Customized
Descriptive Field
It contains 128 bytes at most, and

can be left unconfigured.
Do not use symbols like & ' " < > # %
/\?@:,
Superior Channel
Integer: 0 12.
It is used for SDTMA device of NSN
private protocol. The value for other
devices is 0.
selfPort
Local Channel
Integer: 0 12.
It is used for SDTMA device of NSN
private protocol. The value for other
devices is 0.
antNo
Connected
Antenna
It indicates the antenna connected

with RF cable.
fatherPort
18
Parameter Name
Item
Parameter Name
Value Description
For GU and LTE FDD, the value of
the parameter is from the value of
the antEntityNo field, which is in the
RfCable sheet and should be
configured in advance.
For TDS and LTE TDD, the value of
the parameter is from the value of
the antEntityNo field, which is in the
IrAntGroup sheet and should be
configured in advance.
Connected TMA
Device
tmaNo
2.1.2.13
Value: 1 96. The TmaNo field in the

TMA sheet should have been
configured.
PowerOutlet
This sheet is used to configure the power output port. The filling of this sheet is optional.
Only when the TAM board or the RU of some models is configured can the data in this
sheet be configured.
The power output mainly supplies power for AISG equipment.
RU has two voltage output ports, NSBT (old RU) and AISG (new RU). After the switch of
NSBT is enabled, the AISG port will also output voltage. Both can be connected with
AISG devices and supply power to AISG devices.
The TAM board is used mainly to supply power for TMA. There are 6 ports on this board,
and each port can support the power supply of one device.
One power output port occupies one row. The same power output device can be
configured with two or more power output port records, but the values of the
switchStatus field and the voltage field must be consistent.
Table 2-9 The PowerOutlet Sheet

Item
PowerOutlet Board
Parameter Name
Value Description
PowerOutletBoard
Info
Currently, only the TAM board and some

RU models support power output.
It is required that TAM should have
been configured in the Equipment
sheet or the RU supporting power
output have been configured in the RU
sheet.
Format: RackNo, ShelfNo, SlotNo, for
example, 51,1,1
Item
Value Description
Switch Status
0: Close
1: AISG RS485{AISG RS485},
2: NSBT RS485{NSBT RS485}
If the TAM board is configured, set this
parameter as 0.If RU is configured, set
this parameter as 1 or 2 according to
the actual situation.
voltage
Voltage
0:140,
1:220,
4294967295: Invalid
The voltage of AISG and NSBT.
port
Port No.
Value Range: 0~5

Power Output Port No.
Working Current
Value (Ma)
It indicates the working current value of

the port.
Value Range:
{voltage == 0}[75..400],
{voltage == 1}[75..300],
{voltage == 4294967295}[0..
4294967295]
Alarm Detection
Mode
0: currentDetect
1: pulsewidthDetect
When the current on this port is
abnormal, alarms will be reported. This
attribute is used to set the detection
mode of output current.
Under Current
Alarm Threshold
Percent
Value Range: 20~80,100

When the actual current of the TAM
board power supply channel is less than
Working Current Value*local
value/100, under current alarm is
reported.
Over Current
Alarm Threshold
Percent
Value Range: 100,120~180

When the actual current of the TAM
board power supply channel is greater
than Working Current Value*local
value/100, over current alarm is
reported.
Switch Status
Value Range:
0: Close
1: Open
switch status of whether to enable
current control.
switchStatus
currentValue
almDetectMode
lowerLimitPercent
upperLimitPercent
portSwitchStatus
20
Parameter Name
2.1.2.14
Epm
This sheet is used to configure embedded power equipment.
Table 2-10 The Epm Sheet

Parameter
Name
Item
Connected
Board
It indicates the board for BBU to connect

with the embedded power device (SA/
SE/RU).
For example: 51,1,1
powerType
Built-in Power
Device Type
0:ZXDU58 B900,
1:ZXDU58 B121,
2:ZXDU68 B201,
3:ZXDU150,
4:ZXDU45,
5:ZXDU75,
6:ZXDU58 B121(V4.5),
7:ZXDU68 B201(V5.0),
8:ZXDU68 W301,
9:ZXDU68 S301,
10:ZXDU58 B121(V2.2),
11:ZXDU68 B201(V5.0R99M03),
100:Shelter JZ9
dataProcessMode
Data
Processing
Mode of builtin power
device
0: Transparent transmission
1: Base station parse
refSdrDeviceGroup
2.1.2.15
Value Description
FiberCable
This sheet is used to configure fiber connection, i.e., the topology of fiber connection.
Refer to Table 2 -11Error: Reference source not found for the key parameters in this
sheet.
Table 2-11 The FiberCable Sheet

Item
ref1FiberDevice
Parameter
Name
Optical Port of
Previous Hop in
Value Description
Format: (RackNo,ShelfNo,BoardNo):Pot
If RRU is used, the port No. is 1 and 2, for
Item
ref2FiberDevice
2.1.2.16
Parameter
Name
Value Description
Topology
Structure
example, (1,1,3):0
Optical Port of
Next Hop in
Topology
Structure
Format: (RackNo,ShelfNo,BoardNo):Pot
Only RRU can be used, and the port No. is 1
and 2, for example, (51,1,1):1
RfCable
This sheet is used to configure RF connection.
RF connection shows the connection relation between RU port, antenna, and TMA.
One connection relation occupies one row. Therefore, only two of RU port, antenna, and
TMA can be configured in one row. In the same NE, the same connection relation cannot
be repeated.
Table 2-12 The RfCable Sheet

Item
refRfDevice
antEntityNo
retDeviceType
22
Parameter Name
Value Description
RU Port Info
It indicates the RF port connected with the

RF cable, i.e., the RU port.
Format: (RackNo,ShelfNo,BoardNo):Port
If RU device is used, the port No. is 1 and
2, for example, (1,1,3):1
Antenna Entity
Number
It indicates the antenna connected with RF

cable.
Value range: 1 65535. For TDS or LTE
TDD, this value may come from the value
of the antEntityNo field in the IrAntGroup
sheet. For other modes, a record of
antenna entity will be generated
automatically according to this No.
RET Device Type
It indicates the type of the device

connected with the antenna entity. If
antEntityNo is configured, this parameter
should also be configured.
0: Non-RET
1: Uni-antenna RET
2: Uni-direction TMA
3: Continuous power antenna system
4: Bi-direction TMA
5: LNA
17: Multi-antenna RET
Item
refTma
2.1.2.17
Parameter Name
TMA No.
Value Description
It indicates the TMA connected with the RF
cable.
The value is from the value of the tmaNo
field, which is in the Tma sheet and
should have been configured.
RfExtendCable
This sheet is used to configure RF extension cable. It shows the connection relation
between two RU ports (RxOut and RxIn). The filling of this sheet is optional and should
be based on the actual situation.
2.1.3
Transmission Parameters
2.1.3.1
Transmission
This sheet is used to configure GU transmission mode, transmission medium, and ATM
transmission address. In GU mode, it is required to fill in this sheet.
Table 2-13 Transmission
ATMConfigType
ubrNumber
2.1.3.2
ATM
type
configuration
No. of UBR AAL2

PVC
It is used to configure the normal scenario

and high-load scenario in the case of ATM
transmission mode.
Normal: Normal scenario;
HighLoad: High-load scenario
It is used to configure the quantity of AAL2.
For the site that uses the ATM transmission
mode and still has the broadband link
congestion alarm after the high-load scenario
is adopted, we can add the quantity of AAL2
to solve the problem. Each site can be
configured with at most 19 AAL2 links. Refer
to
Chapter
4.1.2
E1
Capacity
Expansion/Reduction for details.
PhyLayerPort
This sheet is used to configure physical layer port. The filling of this sheet is mandatory.
One physical layer port occupies one row, and an NE can occupy two or more rows.
It is the physical layer of IP or ATM transmission. Physical layer bearer includes, E1, T1,
and Ethernet.
Table 2-14 The PhyLayerPort Sheet

Item
operatingMode
egressPeakBitRate
Parameter
Name
Operating
Mode
This parameter needs to be configured only

when the refGeDevice field is configured.
Refer to the Ground Plan template for the
detailed values.
Transmitting
Bandwidth
This parameter needs to be configured only

when the refGeDevice field is configured.
The values are as detailed below:
{operatingMode==0}[100..1000000] step
100,
{operatingMode==1}[100..10000] step 100,
{operatingMode==2}[100..100000] step 100,
{operatingMode==3}[100..1000000] step
100,
{operatingMode==4}[100..100000] step 100
It is required to be configured when STM-1
is configured.
codeType
2.1.3.3
Value Description
EthernetLink
This sheet is used to configure Ethernet link, VLAN ID, etc. When Ethernet transmission
is used, it is required to fill in this sheet.
The configuration is about the Ethernet link layer between SDR and upper-level NE.
Table 2-15 The EthernetLink Sheet

Item
mtu
vlanMembership
24
Parameter Name
Value Description
Connection Object
long:[256..1800] byte
VLAN No.
Format: VALN;VLAN. Separate

every two VLANs with English
character ; if there are two or more
VLANs.
VALN:long:[1..4094]
For example:1;2
Item
Parameter Name
Used Physical
Layer Port
refPhyLayerPort
2.1.3.4
Value Description
The value of this parameter is from
the value of the phyLayerPortNo
field in the PhyLayerPort sheet.
Hdlc
This sheet is about HDLC channel related configuration. Refer to Table 2 -16 for the
details of the main parameters.
Table 2-16 The HDLC Sheet

Item
2.1.3.5
Parameter Name
Value Description
hdlcNo
HDLC Link Number
[0..16]
refPhyLayerPort
Used Physical Layer

Port
The value is the same as the value

of the phyLayerPortNo field in the
PhyLayerPort sheet
timeSlotBitMap
Time Slot Bit Mapping
If the value is set as 0, it means

this time slot is not used.
Ppp
This sheet is about PPP link related configuration. Refer to Table 2 -17 for the details of
the main parameters in this sheet.
Table 2-17 The PPP Sheet

Item
Parameter Name
Value Description
pppLinkNo
PPP Link No.
[0..15]
localIp
Base Station IP
IPV4
protocolType
PPP Encapsulation
Type
0:PPP{PPP},
1:ML-PPP{ML-PPP}
refHdlc
Used HDLC Channel
The value of this parameter is from

the value of hdlcNo in the HDLC
sheet.
mpCode
Long/short Sequence
of MP Head
2: Long sequence
6: Short sequence
0xFF: Invalid
mpClass
MP Priority
{mpCode==2}[1..8],
{mpCode==6}[1..4],
0xFF: Invalid
ipCompress
Whether Support IP
Compression
1: Yes
0: No
Item
isUsedToFECascade
2.1.3.6
Parameter Name
Whether Used for FE
Cascading
Value Description
1: Yes
0: No
IpLayerConfig
This sheet is about IP related configuration. When IP transmission is used, it is required
to fill in this sheet.
This sheet is used mainly to configure Gateway IP, Network Mask, Prefix Length of IPv6
address, Used Ethernet Link, IP Domain, and VLAN ID.
Table 2-18 The IpLayerConfig Sheet

Item
Value Description
IP Address
It is the IP address of the base station. When

the PPP link is used, this IP cannot be
configured. It can be configured as IPv4
address or IPv6 address. The IPv4 address
format is decimal notation separated by dots,
e.g., 10.0.0.1.IPv6 address is hexadecimal
notation separated by colon, e.g.,
2011:0db8:85a3:0000:1319:8a2e:0370:7366.
The IPv4 address of the 127 subnetwork and
the 200 subnetwork cannot be configured.
Gateway IP
Gateway
When the PPP link is used, network mask
cannot be configured. It can be IPv4 address
or IPv6 address. The IPv4 address format is
decimal notation separated by dots, e.g.,
10.0.0.1.IPv6 address is hexadecimal
notation separated by colon, e.g.,
2011:0db8:85a3:0000:1319:8a2e:0370:7366.
networkMask
Network Mask
Subnet Mask
When the PPP link is used, network mask
cannot be configured. Only IPv4 address can
be configured.
prefixLength
Prefix Length
Prefix length configuration. Only IPv6

address can be configured.
refEthernetLink
Used Ethernet
Link No.
This is the Ethernet link used to bear IP. The

value is from the value of "ethernetLinkNo"
field, which is in the EthernetLink sheet and
should have been configured.
ipField
IP Domain
ipAddr
gatewayIp
26
Parameter
Name
Value range: [0..3]. 255: Invalid.

It is the information of the domain which IP
address belongs to. 255 indicates that it
Item
Parameter
Name
Value Description
does not belong to any domain.
vid
radioMode
2.1.3.7
VLAN ID
It should be the same as a VLAN in

refEthernetLink.
Radio Mode
It must be configured.
It is used to generate the content in the
ServiceMap sheet in association. It is not
configured, the setup of common channel
will end in failure.
StaticRoute
Static route is not required to be configured for GSM or UMTS mode.
2.1.3.8
BandwidthResource
This sheet is used to configure bandwidth resource group and bandwidth resource. It is
required to fill in this sheet when multi-mode is used.
It is not necessary to configure this sheet in GSM single mode, UMTS single mode, or
GU dual-mode.
2.1.3.9
Sctp
This sheet is about SCTP related configuration, including mainly Local Port Number,
Used IP Layer Configuration, Remote Port Number, Remote Address, Number of In-andout Streams, DSCP, Used Bandwidth Resource, and Radio Standard.
Table 2-19 The Sctp Sheet

Item
Parameter Name
Value Description
localPort
Local Port Number
[1..65535]
refIpLayerConfig
Used IP Layer
Configuration
The value comes from the value of

ipNo in the IpLayerConfig sheet.
remotePort
Remote Port
Number
[0..65535]
remoteAddr
Remote Address
IP address
inOutStreamNum
Number of In-andout Streams
[2..6]
dscp
DSCP
[0..63]
Item
refBandwidthResource
radioMode
2.1.3.10
Parameter Name
Value Description
Used Bandwidth
Resource
The value is from the value of

groupNo, or resourceNo in the
BandwidthResource sheet. The
filling of this field is optional.
Radio Mode
1:UMTS{UMTS},
2:GSM{GSM},
4:TD-SCDMA{TD-SCDMA},
8:CDMA{CDMA},
16:LTE FDD{LTE FDD},
32:TD-LTE{LTE TDD}
If there are two or more modes,
separate them with English
character ;, for example, 4;32
In the LTE FDD mode and the LTE
TDD mode, the records of S1AP and
X2AP will be created according to
the value of SCTP. It is consistent
with the configuration created
through the GUI configuration
module.
ItfUniBts
This sheet is about OMC channel related configuration.
Table 2-20 The ItfUniBts Sheet

Item
28
Parameter Name
Value Description
itfUniBtsNo
OMC Interface Link

Number
[1..65535]
itfUniBtsType
Type of Operation
and Maintenance
Interface
0:IPINIP,
1:IPOA,
2: Independent Networking
refIpLayerConfig
Used IP Layer
Configuration

ipNo in the IpLayerConfig
sheet.
gatewayIp
OMC Gateway IP
It is the virtual address on the RPU

at the RNC side. For the UMTS
mode, it is usually set as
10.9.X.63.
omcServerIp
OMC Server IP
For the UMTS mode, it is the IP

address of eth6:2.
omcNetworkMask
OMC Network Mask
Network Mask
Used Bandwidth
Item
Dscp
2.1.3.11
Parameter Name
Value Description
Resource
"ResourceNo" in the
BandwidthResource sheet.
DSCP
[0..63]
ServiceMap
This sheet is about service and DSCP mapping related configuration. One mode
occupies one row. In multi-mode, one NE needs several pieces of records.
It is not necessary to configure this sheet in GSM single mode, UMTS single mode, or
GU dual-mode.It is automatically created in association with the radioMode field in the
IPLayerConfig sheet.
Table 2-21 The ServiceMap Sheet

Parameter
Name
Item
2.2
Value Description
refIpLayerConfig
Used IP Layer
Configuration

ipNo in the IpLayerConfig sheet.
Used
Bandwidth
Resource

"ResourceNo" in the
BandwidthResource sheet.
refOperator
Operator Name
The value is the same as the value of

operatorName in the Operator sheet.
Wireless Plan Template Filling Specifications

There are four sheets in the UMTS Wireless Plan template, as detailed in Table 2 -22.
Table 2-22 Description of Sheets in UMTS Wireless Plan Template

No.
Sheet Name
Description
UMTS Radio
Configuration information of UMTS radio mode
UMTS Sector
Configuration information of UMTS sector
UMTS Local Cell
Configuration information of UMTS local cell
ULocalCellRelation
Configuration information of UMTS local cell

relation
2.2.1
Description of the Sheets
2.2.1.1
UMTS Radio
This sheet is used to configure UMTS global information. Refer to Table 2 -23 for the
Table 2-23 The UMTS Radio Sheet

Item
2.2.1.2
Parameter Name
Value Description
nodeBId
NodeB ID
[0..65535]
paShareRatio
Power-sharing Ratio
[0..50]
enableDPT
Enable Dynamic Power

Track (DPT)
1: Yes
0: No
maxUplinkCE
Maximum Number of
Uplink CE
[1..3840],[65535..65535]
65535: Invalid
maxDownlinkCE
Maximum Number of
Downlink CE
[1..3840],[65535..65535]
65535: Invalid
UMTS Sector
This sheet is about UMTS sector related configuration. Refer to Table 2 -24 for the
Table 2-24 UMTS Sector

Item
userLabel
30
Parameter Name
Value Description
Sector Name
[0..199]
txType
Tx Type
0: No Diversity
2:2-RRU NOT DIV
5:3-RRU NOT DIV
3:4-RRU NOT DIV
4:5-RRU NOT DIV
7:6-RRU NOT DIV
8:MIMO{MIMO}
txDevice
Tx Device
(RackNo, ShelfNo, SlotNo):portNo;

(RackNo, ShelfNo, SlotNo):portNo)
For example: (51,1,1):1;(51,1,1):2
rxType
Rx Type
1: No Diversity
2:Diversity
9:2-RRU NOT DIV
4:2-RRU DIV
11:3-RRU NOT DIV
6:3-RRU DIV
Item
Parameter Name
Value Description
8:4-RRU NOT DIV
3:4-RRU DIV
10:5-RRU NOT DIV
5:5-RRU DIV
12:6-RRU NOT DIV
7:6-RRU DIV
13:MIMO{MIMO}
rxDevice
2.2.1.3
Rx Device
(RackNo, ShelfNo, SlotNo):portNo;

(RackNo, ShelfNo, SlotNo):portNo)
eg:(51,1,1):1;(51,1,1):2
UMTS Local Cell

This sheet is about UMTS local related configuration. Refer to Table 2 -25 for the details
of the main parameters.
Table 2-25 UMTSLocal Cell

Item
Parameter
Name
Value Description
Local Cell
Description
[0..199]
Automatically
Assign
Baseband
Resource
1: Yes
0: No
If there is no special
requirement, it is recommended
to configure this parameter as
1, i.e., assignment baseband
resource automatically.
refBpDevice
Baseband
Resource
Assignment
Fill in the slot No. of the BPC

and BPK board. For the BPK_d
board that has multiple units, the
format should be Slot No.#Unit
No.; the unit No. is 0 by default.
Separate the Nos. with & if
there is more than one BP board.
In Shelf 2, the actual Slot No.
should be Slot No. of the BP
boards + 20, starting from 24.
It can be left blank. If it is not
configured, it means the
baseband resource board of
cells is automatically allocated.
USectorId
UMTS Sector
ID
[1..30]
txFreq
Tx Frequency
userLabel
isAutoAssignBasebandResource
{parent.band==1}[21100..21700],
{parent.band==2}[19300..19900],
Item
Parameter
Name
Value Description
{parent.band==3}[18050..18800],
{parent.band==4}[21100..21550],
{parent.band==5}[8690..8940],
{parent.band==7}[26200..26900],
{parent.band==8}[9250..9600]
UMTS
Reception
Filter
Bandwidth
50:5M,
48:4.8M,
46:4.6M,
44:4.4M,
42:4.2M,
38:3.8M
cellRadius
Cell Radius
2500: 2.5km
5000: 5km
10000: 10km
20000: 20km
40000: 40km
80000: 80km
120000: 120km
240000: 240km
txOffset
Downlink
Delay Offset
[-63..63]
Default: 0.
rxOffset
Uplink Delay
Offset
[-63..63]
Default: 0.
maxDlPwr
Local Cell Max

Tx Power
[1..200],[255..255]
When it is configured to 255, it
means the cell power is
allocated at the RNC.
supportSpeed
Support
Speed
0: 0-250km/h
1: 250-350km/h
coverageType
Coverage
Type
0: Indoor
1: Outdoor
enableEnergySaving
Enable
Electric-saving
Mode
1: Yes
0: No
enable2msGain
Support 2ms
Gain
0:Enable,
1:Disable
enableVAM
Support VAM
Function
1: Yes
0: No
enhancedVamEnable
Enable E-VAM
Function
1: Yes
0: No
enableDynCode
Enable
Dynamic Code
1: Yes
0: No
refOperator
Operator
operatorName
rcvFilterBandwidth
32
2.2.1.4
ULocalCellRelation
This sheet is used to configure UMTS dual-carrier cells. Refer to Table 2 -26 for the
Table 2-26 ULocalCellRelation

Parameter
Name
Item
2.3
Value Description
ref1ULocalCell
Primary Cell ID
The value of this parameter comes

from the value of USectorId" in the
"UMTS Local Cell" sheet.
ref2ULocalCell
Secondary Cell
ID
The value of this parameter comes

from the value of USectorId" in the
"UMTS Local Cell" sheet.
GSM Wireless Plan Template Filling

Specifications
There are two sheets in the GSM Wireless Plan template, as detailed in Table 2 -27 .
Table 2-27 Description of Sheets in GSM Wireless Plan Template

No.
2.3.1
Sheet Name
Description
RU(GSM)
Fill in the resource using status of the PAs on the

RU, including Carrier Number, Carrier Power,
GSM Cell Channel Resource No., and Multi-carrier
Combination Group No.
GSM Carrier
Fill in the TRX information allocated to each GSM

cell.
RU (GSM) Sheet
Fill in RU properties in GSM network in the RU(GSM) sheet, including Carrier Number,
Carrier Power, GSM Cell Channel Resource No., Multi-carrier Combination Group No .,
Rx Mode, and Tx Mode. The PA of each RU occupies one line. For the RUs with two PA
units (RSU82 and R8882), fill in two lines at most.
Table 2-28 RU(GSM) Sheet

Item
Parameter Name
Value Description
gCellEquipmentFuncNo
GSM Cell Channel

Resource No.
Each PA corresponds to a No.,

which is unique.
TxDevice
Transmission Port
Select the Tx port (i.e., PA) of an

RU. NOTE: The Tx ports of
Item
Parameter Name
Value Description
R8882 are ports 1 and 4 (this is
different from that in
OMCBV4.11).
multiCarrierGroupNo
Multi-carrier
Combination Group No.
For non-MCUM, set this

parameter as 0.
channelGroupNo
GSM Cell Channel

Group No.
For non-MCUM, set this

parameter as 0.
carrierPower
Carrier Power
This parameter is used to

configure the Tx power of each
carrier, which should be accurate
to 1W.
powerLevel
Static Power
Attenuation Level of
Carrier
For GU RUs of DTR, ADTR,

RSU 82, and R8882, the value
range is 0-6.
Tx Mode
0:Normal mode: Each PA

transmit different carriers
independently.
1:DPCT: Two PAs transmit the
same carrier, which is applicable
only to RU02.
2:DDT: Two PAs transmit the
same carrier, but not at the same
time (there is DDT delay
between the two carriers).
3:Antenna hopping: Two
antennas transmit different
carriers in turn.
rxMode
Rx Mode
0:2-antenna diversity reception:

Corresponding to normal
transmission mode
1:4-antenna diversity reception:
Corresponding to DPCT, DDT,
and antenna hopping
ddtOffset
DDT Delay
DDT Delay
rxConfig
Primary-secondary
antenna receiving
setting
Whether to use primary and

secondary reception
simultaneously or use one of
them depends on the actual
antenna connection in the field.
When the Tx Mode is normal
mode and the Rx Mode is 2antenna diversity reception, this
parameter needs to be
configured.
CELL_ID_x
Cell No.
The cell No. of the carriers.
GPS Synchronized
Frame Head Offset
When GPS clock is configured,

this parameter should be
configured. Otherwise, it is not
necessary to configure this
parameter.
txMode
gpsOffset_x
34
Item
carrierNum_x
hsrCellOutInletFlag_x
ISBCCH_x
bcchCarrierNo_x
2.3.2
Parameter Name
Value Description
Number of Used
Carriers
The total number of carriers in

CELLx on the PA.
End ID of High-speed
Railway Cell
It is the End ID of High-speed

Railway Cell. In the scenario of
high speed railways configured
with mutli-carrier combination
group, it is used to identify
whether a PA is the PA at the
very edge of the cell. This
parameter can be left
unconfigured.
Is BCCH Preferred
Channel
It defines whether a PA is the

BCCH preferred PA when there
are two or more PAs in a cell.
Default: No
When MCUM is used,
ISBCCH_x cannot be
configured.
BCCH Preferential
Carrier No.
It defines the carrier preferred by

BCCH when there are two or
more carriers on the PA.
Default: No
When MCUM is used,
bcchCarrierNo_x cannot be
configured.
GSM Carrier Sheet

Fill in carrier related information in the GSM Carrier sheet, including trxNo,
operatingMode, mainBand, etc.
When single-channel is used, the corresponding multiCarrierGroupNo of RRU should be
0 (no grouping). When dual-channel or multi-channel is configured,
multiCarrierGroupNo should not be 0, i.e., they must be grouped.
The total number of carriers in the same frequency band or sub-frequency band of the
same cell cannot be greater than the total number of carriers of the frequency band or
sub-frequency band, which are provided by the channel used by the cell.
Refer to Table 2 -29 for detailed description of parameters.
Table 2-29 GSM Carrier Sheet

Item
Parameter Name
Value Description
SubNetwork
SubNetwork ID
It is the SubNetwork ID
MEID
ManagedElement
ID
NE ID
cellNo
Cell No.
The Cell No. should be corresponding
Item
Parameter Name
Value Description
to the e Cell No. at OMCR side.
Logic Carrier
Frequency No.
The Logic Carrier Frequency No.

should be corresponding to the TRX
No. at OMCR side.
operatingMode
Operating Mode
Select single carrier (0) in general

cases.
Select dual-carrier when DDT and
DPCT are used.
Select multi-carrier when MCUM is
used.
multiCarrierGroupNo
Multi-carrier
Combination Group
No.
It defines the Multi-carrier

Combination Group No. The value
should be set as 0 in the single
carrier mode.
mainBand
Parent Frequency
Band
It defines the Tx frequency band

supported by the PA.
Sub frequency
band
It defines the value of sub-frequency

band, which is usually set as 255.
The TRX on which sub-frequency is
configured can only use the carriers
of the PA configured with the same
sub-frequency band. The subfrequency band is configured in the
PA sheet. Refer to related Technical
Notice for details.
Use IRC
It defines whether to enable the

"ZGO-04-01-005 Uplink Interference
Rejection Combining (IRC)" feature,
which can improve the uplink
receiving signal quality. Default: 1.
STIRC is the enhanced IRC, which is
not stable currently. So it is not
recommended to select STIRC.
isExtendTrx
Extend carrier
frequency
This parameter should be configured

in the ultra-wide coverage scenario.
Two timeslots are combined into one
(in this case, each TRX has 4
timeslots instead of 4 timeslots), so
as to improve TA to increase the
coverage distance of the site.
isExtendTrx and RfExtend (in the
RfExtendCable sheet) are two
different concepts which are not
related to each other in any way. Do
not mix them.
mcumRxSelMode
Is uplink signal
selected according
to CIR
It defines whether CIR or RxLev is

used as the basis to select the RRU
to receive uplink/downlink signals,
when MCUM is used. Default: 0, i.e.,
RxLev
trxNo
branchBand
enableIRC
36
Item
mcumTxSelMode
Parameter Name
Select RU
transmission
Value Description
It defines whether to use some RUs
or all RUs to transmit signals, when
MCUM is used. Default: 0, i.e., select
all RUs.
Data Import and Export Functions

V4.12 OMMB plan data import and export functions have the following features:
3.1
3.2
1.
The data can be exported by template type (Wireless Plan Template or Ground
Plan Template).
2.
The NE and object range can be defined to import and export parameters.
3.
The exported data, after being edited, can be imported again in to OMMB.
Notices in Operation
1.
It is required to perform data backup before batch data modification (please refer to
the corresponding manual for data backup),
2.
Before performing batch data modification, make sure there is no user operating
NE data and there is no time-consuming and resource-consuming tasks running on
the server.
3.
Make sure the export only the managed NE object to be modified to save memory
resource.
4.
In an overall network parameter modification, at most 500 base stations can be

modified each time.
Planning Data Import

After the filling of Plan Template is completed, choose Configuration Management >
Planning Data Import on OMMB.
Figure 3-3 Planning Data Import
Select the path for storing the Plan Template and import data.
Figure 3-4 Set the Path of Plan Templates
After the data is imported completely, right-click the record and choose Result File to
view the log.
38
Figure 3-5 View Log File
3.3
Planning Data Export

Choose Configuration Management > Planning Data Export on OMMB.
Figure 3-6 Planning Data Export
Figure 3 -7 shows the Planning Data Export window.
Figure 3-7 Planning Data Export Window
Select the subnetwork or NE to be export in the pane on the right of the window. The
description of the parameters to be exported is as shown below.
1.
Data area: Select Modify area or Snapshot area.

Modify area: It means exporting the configuration data in the Modify area of the
choosen managed element.
Snapshort area: It means exporting the configuration data in the Snapshot area of
the choosen managed element.
2.
Export file: Select the number of the files to be exported.

Single: All configuration data is saved in one Excel file.
Multiple: The data exported is divided by the number of subnetworks, i.e., the data
of each subnetwork is saved as an Excel file.
3.
Data Type: Select the type of the template to be exported. Either Ground Plan
template the Plan template of different modes can be exported.
Figure 3-8 Data Type
4.
40
File path: Select the storage path of the Plan template and set the name of the
exported data.
Figure 3-9 File Path
Explanation of Common Operations
4.1
Examples of Configuration Scenario
4.1.1
Adding BPC Board

It is necessary to add BPC at Slot 6. In the Equipment sheet, modify the value of
MODIND of the original data of the BPC at Slot 6 from A to M.The modification
method is as shown in Figure 4 -10.
Figure 4-10 Add BPC Board
After the data modification is completed, import the data into OMMB through the Plan
template.
42
Figure 4-11 Import Data to OMC
After the planning data is successfully imported, perform data synchronization.
Figure 4-12 Data Synchronization
Select Incremental Synchronization to synchronize the data to SDR.
44
Figure 4-13 Incremental Synchronization
Note:
Only generate file is used to generate the xml file that can be imported into LMT.
4.1.2
E1 Capacity Expansion/Reduction
For the sites using ATM (E1), the medication of E1 number is a very common scenario in
the field. The data medication flow in this scenario is detailed in the following example.
Example: NodeB 201 uses ATM (E1) transmission. There are two pieces of E1 in the
initial site commissioning, and now the transmission needs to be expanded to four
pieces of E1. The operation process is as shown below:
1.
Export the PLAT template of the existing site.
Figure 4-14 Planning Data Export
2.
46
Select PUBLIC for NE Mode to export the Snapshot Area PLAT template of the site.
Figure 4-15 Export PLAT Data
3.
Open the exported PLAT template, and modify the format of the Transmission
sheet according to the following description.
The MODIND of the first record is D, which means deleting the related PVC and
AAL data generated previously when there are two pieces of E1.
The MODIND of the second record is A, which means generating PVC, AAL, and
other related parameters according to the new number of E1 links.
Figure 4-16 Modification to the Transmission Sheet
4.
Add two pieces of E1 records in the PhyLayerPort sheet.
Figure 4-17 Modification to Parameters in the PhyLayerport Sheet
5.
4.1.3
After the modification to the above two sheets is completed, import the data to
OMMB and synchronize the data to SDR.
Batch Configuration Data Modification

In V4.12, data modification can be performed on GUI. The batch data modification flow
is as detailed below:
Example: For OMMBV12.12.40, the Maintenance Status field is set as 3 by default.
For a newly-commissioned site, the value of the field should be modified to 0 after the
planning data is exported, so as to make sure the link with OMMB can be established
normally after the transmission is normal.
1.
Open Batch Configuration Data Modification.
Figure 4-18 Batch Configuration Data Modification
48
2.
Select the NE to be modified, and click the configuration tree.
3.
Select the site to be modified, right-click it to select Select Column and Modify,
and then select the target value in the pop-up dialog box, and then click Save to
finish
the
batch
data
modification.
After the modification, perform
incremental synchronization.
4.1.4
Snapshot Area Data Recovery

Data in the Snapshot Area are the data currently running in SDR. Data in the Modify
Area are the data saved in OMMR, which can be modified and synchronized to SDR
through all-data synchronization or incremental synchronization. In some scenarios, data
in the Snapshot Area need to be recovered in the Modify Area with the following method.
Open Configuration Management > Batch NEs Operation.
Figure 4-19 Batch NEs Operation
Select the site and click Copy Snapshot Area Data to Modify Area to recover the data
from the Snapshot Area to the Modify Area.
50
Figure 4-20 Copy Snapshot Area Data to Modify Data
4.2
Acquisition of LMT Configuration File

When commissioning a base station on site, the engineers usually use EOMS to view
the data and configuration.
The EOMS of V4.12 only supports the data import and export of the configuration file in
XML format. The process of acquiring the XML-format file is as follows:
1.
Open Configuration Management > Data Synchronization on OMMB.
Figure 4-21 Data Synchronization
2.
Select the NE for configuration file export from the NE tree on the left.
For the Synchronization Mode, select Only Generate File.
52
Figure 4-22 Only Generate File
3.
After the data is successfully synchronized, the configuration data file is

automatically
generated,
which
is
saved
under
the
/home/netnumen/ommb/ums/ums-svr/cmdata/sync/subnet+
+/nodeb/nodeb***/zdb/modbdown.xml directory on the OMMB Server.
++: the subnet No.
***: the NodeB ID
Examples of Data Configuration

This chapter describes the data configuration for the five common transmission modes
used in the UMTS scenario.
1.
NodeB201: ATM transmission

Ground plan template: Pure ATM transmission is used, and the data configuration
is relatively simple. ATM Configure Type should be configured to Normal.
Wireless plan template: configure four RRUs, among which RRU53 and RRU54 are
configured as STSR cells, and the rest are configured as the OTSR cells.
2.
NodeB202: FE Transmission
Ground plan template: the O&M address and service address are separated and
planned in different VLANs. For the configuration in the field, the two addresses
can be the same.
3.
NodeB203: IPOE
4.
NodeB204: ATM+IP transmission
5.
NodeB205: IPOE+FE transmission; the RRU for the wireless plan template should
be configured to cross diversity reception.
OSS_PLAT_CM_Groun OSS_UMTS_CM_Wirel
d_Plan_en.zip
ess_Plan_en.zip
54

GU - ZXSDR (V4.12) Quick Data Configuration Guide - R1.2

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

GU - ZXSDR (V4.12) Quick Data Configuration Guide - R1.2

Caricato da

Copyright:

Formati disponibili

ZXSDR(V4.

ZXSDR(V4.12) Quick Data Configuration Guide

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

ZXSDR(V4.12) Quick Data Configuration Guide

Reason for Revision

The Plan template is

Intended audience: Base station commissioning staff

2016ZTE CORPORATION. All rights reserved.

ZTE Confidential Proprietary

ZXSDR(V4.12) Quick Data Configuration Guide

About This Document

It gives a simple introduction to the Plan Template.

2 Plan Template Filling

It describes the specifications for filling in the Plan Template.

3 Data Import and Export Functions

It describes the data import and export functions.

It gives the explanation of some common operations.

5 Examples of Data Configuration

It gives some examples on data configuration procedure.

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

ZXSDR(V4.12) Quick Data Configuration Guide

Plan Template Filling Specifications..............................................................4

Data Import and Export Functions...............................................................37

Explanation of Common Operations............................................................42

Examples of Data Configuration...................................................................54

2016ZTE CORPORATION. All rights reserved.

ZTE Confidential Proprietary

ZXSDR(V4.12) Quick Data Configuration Guide

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

ZXSDR(V4.12) Quick Data Configuration Guide

Table 2-6 The PA Sheet........................................................................................................15

2016ZTE CORPORATION. All rights reserved.

ZTE Confidential Proprietary

ZXSDR(V4.12) Quick Data Configuration Guide

Figure 1-1 Generate Template

Template Acquisition Path

ZXSDR(V4.12) Quick Data Configuration Guide

Figure 1-2 Template Storage Path

Description of Template Format

Conventions of Table Header

Conventions of Sheet Arrangement

2016ZTE CORPORATION. All rights reserved.

ZTE Confidential Proprietary

ZXSDR(V4.12) Quick Data Configuration Guide

ZXSDR(V4.12) Quick Data Configuration Guide

Plan Template Filling Specifications

Ground Plan Template Filling Specifications

Table 2-1 Instructions on Filling in Sheets in Ground Plan Template

Managed Element sheet: The NE here refers

This sheet is used to configure the data of the

This sheet provides the configuration

This sheet contains the Time Device, Time

This sheet is about the 1588 clock

This sheet provides the configuration of clock

This sheet is about the configuration of RU

2016ZTE CORPORATION. All rights reserved.

ZTE Confidential Proprietary

ZXSDR(V4.12) Quick Data Configuration Guide

Optical port device. When the board of RU,

It is the power amplifier of RU device. PA