07 ZXSDR BS8800 Project Commissioning Guide (V1.0)

ZXSDR BS8800 Project Commissioning Guide For Internal Use Only
ZXSDR BS8800 GU360

Project Commissioning Guide
(2009-V1.0)
ZTE CORPORATION
Confidential and Proprietary Information of ZTE CORPORATION.

ZXSDR BS8800 GU360 Project Commissioning Guide

(2009-V1.0)
Planned by: GSM Customer Service Department, Mobile Product Support Center
Compiled by: Yang Wen
Reviewed by: Zhao Yanghao
* * * *
ZTE CORPORATION
Address: ZTE Plaza, #889 Bibo Road, Zhangjiang Hi-tech Park, Shanghai, P. R. China
Post code: 201203
Technical support website: http://tsm.zte.com.cn
Hotline: +86 755 26770800 800-830-1118
Fax: +86 755 26770801
* * * *

Legal Information
All rights reserved. No part of this documentation may be
excerpted, reproduced, translated, annotated or duplicated, in
any form or by any means without the prior written permission
of ZTE Corporation.
and are the registered trade marks of ZTE

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

requirements of environment protection and human security.
The storage, usage, and discard of the product shall comply
with the manual, related contract, or laws and regulations of
related countries.
The actual product may differ from what is described in this

standard due to frequent update of ZTE products and fast
development of technologies. Please contact the local ZTE
office for the latest updating information of the product.
For the latest document information, please visit our website:

http://tsm.zte.com.cn

Feedback Table
You are invited to give your suggestions and opinions to improve ZTE user manuals and enjoy
better service by sending emails to Zheng.junhua@zte.com.cn. Thank you for your cooperation!
Document
ZXSDR BS8800 Project Commissioning Guide (V1.0)
Name
Product Document
V1.0
Version No. Version No.
Please provide your information for further contact:
Name Company
Post Code Address
Tel E-mail
Very Good Good Ordinary Bad Very Bad
General View
Work instruction
Convenient to
consult
Logicality
Correct description
Correct content
Comments
Complete content
Well-organized
structure
Illustration to
figures/tables
Straightforward
expression
Comments
on the sub-
manuals
You may give suggestions from any perspective such as the content, structure, details, depth,
expression, figures/tables, special tools, FAQ and so on. The suggestions are not confined to
this document.
Suggestions

Revision Records
Document Prepared/ Prepared/ Total Reason for Contents of Revision
Version No. Revised by Revised on Pages Revision (Key Points Only)
V1.0 Yang Wen 2009-06-15 New
Note 1: This table must be completed before updating the archived document (the document archived in
the archival room of the division or the Company).
Note 2: Fill "None" in "Reason for Revision" and "Contents of Revision" when archiving this document for
the first time.

Preface
This manual introduces the commissioning criteria for ZXSDR BS8800 GU360
(V1.0), including hardware installation, LMT local commissioning, OMCB
remote commissioning, OMCR data configuration, etc., so as to provide unified
engineering commissioning flow and detailed procedures, to regulate and
guide the on-site tasks of the commissioning engineers.

ZXSDR BS8800
Contents
1 General Introduction............................................................................................................1-1
1.1 ZXSDR BTS Introduction...............................................................................................1-1
1.1.1 BBU+RU Architecture.......................................................................................................1-2
1.1.2 OMCB Introduction............................................................................................................1-3
1.1.3 IP Abis Interface.................................................................................................................1-4
1.2 SDR BTS Commissioning Flow......................................................................................1-5
1.3 Chapter Outline..............................................................................................................1-8
1.4 Document Application.....................................................................................................1-9
2 Commissioning Preparations...........................................................................................2-10
2.1 Version Preparations....................................................................................................2-10
2.2 Document Preparations................................................................................................2-10
2.3 Configuration Data Preparation....................................................................................2-11
2.4 Others...........................................................................................................................2-11
3 Hardware Check...................................................................................................................3-1
3.1 Hardware Installation Check..........................................................................................3-1
3.1.1 Checking Boards...............................................................................................................3-1
3.1.2 Checking Internal Jumpers on SA Board......................................................................3-2
3.1.3 Checking Input Power.......................................................................................................3-4
3.1.4 Checking Cable Connections..........................................................................................3-5
3.2 Equipment Power-On and Power-Off.............................................................................3-5
3.2.1 B8200 Power-On and Power-Off....................................................................................3-5
3.2.2 Checklist Before Power-on..............................................................................................3-6
4 Operation and Maintenance Networking of SDR..............................................................4-8

4.1 SDR Operation and Maintenance Networking Diagram.................................................4-8
4.1.1 Networking with Ethernet as Bearer at Abis Interface................................................4-8
4.1.2 Networking with E1/T1 as Bearer at Abis Interface.....................................................4-9
4.2 One Instance................................................................................................................4-10
5 OMCR Data Configuration.................................................................................................5-15

5.1 Configuration of BSC Global Resource........................................................................5-15

5.2 Configuration of Abis and OMCB Interface Boards......................................................5-17
5.2.1 Configuration of Abis Interface Board..........................................................................5-18
5.2.2 Creating an IPBB Board Accessed to OMCB.............................................................5-21
5.3 IP-related Configuration...............................................................................................5-22
5.3.1 Creating an IP Abis Interface.........................................................................................5-22
5.3.2 Creating IPBB Interface of OMCB................................................................................5-25
5.3.3 Interface Configuration with E1 at Abis Interface.......................................................5-27
5.3.4 Interface Configuration with FE at Abis Interface.......................................................5-32
5.4 Logically Configuring a B8800 Site on OMCR.............................................................5-35
5.4.1 Creating a Logical Base Station...................................................................................5-35
5.4.2 Creating a B8200 Rack..................................................................................................5-36
5.4.3 Configuring a B8200 Cell...............................................................................................5-38
5.4.4 Configuring a Transceiver..............................................................................................5-40
6 OMCB Data Configuration.................................................................................................6-43

6.1 Installation of OMCB-OMCR Server Software.............................................................6-43
6.1.1 Modifying deploy-030womcb.properties Configuration File (Log on with user ID
omc) 6-43
6.1.2 Modifying FTP-Related Configuration Files (Log on with user ID omc).................6-46
6.1.3 Modifying the deploy-default.properties File (Log on with User ID omc)...............6-47
6.1.4 Starting OMC-B Server (Log on with User ID omc)..................................................6-48
6.2 Configuring SDR Physical Data with OMCB................................................................6-49
6.2.1 Creating an SDR Management NE..............................................................................6-49
6.2.2 Applying Mutex Right over Management NE.............................................................6-53
6.2.3 Creating Base Station Configuration Set....................................................................6-54
6.2.4 Physical Configuration....................................................................................................6-54
6.2.5 Transmission Configuration...........................................................................................6-62
6.2.6 Clock and Monitoring Configuration.............................................................................6-71
6.2.7 Radio Configuration........................................................................................................6-73
6.3 Configuration in Batch of SDR Physical Data..............................................................6-78
6.4 Version Loading and Querying.....................................................................................6-79
Confidential and Proprietary Information of ZTE CORPORATION. ii

7 LMT Installation and Data Configuration.........................................................................7-86

7.1 Introduction of Debugging Software LMT.....................................................................7-86
7.1.1 LMT Content.....................................................................................................................7-86
7.1.2 LMT Installation................................................................................................................7-87
7.1.3 Connection between LMT and SDR.............................................................................7-89
7.1.4 Offline Configuration.......................................................................................................7-94
7.1.5 Configuration Export and Import...................................................................................7-95
7.2 LMT Configures SDR Base Station..............................................................................7-96
7.2.1 Basic Property Configuration.........................................................................................7-99
7.2.2 Physical Configuration..................................................................................................7-105
7.2.3 Transmission Configuration.........................................................................................7-113
7.2.4 Radio Configuration......................................................................................................7-128
7.3 Version Load...............................................................................................................7-136
7.4 SDR Power-on Inspection (Before and After Link Establishment).............................7-137
7.4.1 General Principle for Passing Power-on Inspection................................................7-137
7.4.2 Information to Be Confirmed After Power-On...........................................................7-139
7.4.3 FAQ..................................................................................................................................7-142
7.4.4 Fast Configuration of Site Data...................................................................................7-143
8 Foreground and Background Data Synchronization....................................................8-147

8.1 Synchronizing Configuration Data to the Foreground................................................8-147
8.2 SDR Foreground and Background Data Synchronization.........................................8-147
9 SDR Commissioning Tests.............................................................................................9-151

9.1 CS Domain Service Test.............................................................................................9-151
9.1.1 Test Preparations...........................................................................................................9-151
9.1.2 Test Objective.................................................................................................................9-151
9.1.3 Test Procedure...............................................................................................................9-151
9.2 PS Domain Service Test.............................................................................................9-152
9.2.1 Test Preparations...........................................................................................................9-152
9.2.2 Test Objective.................................................................................................................9-152
9.2.3 Test Procedure...............................................................................................................9-152
9.2.4 Test Description.............................................................................................................9-153
Confidential and Proprietary Information of ZTE CORPORATION. iii

Appendix A Fast Query of General Information...................................................................9-154

Conversion Between Absolute Frequencies and Frequencies...........................................9-154
SDR Board IP..............................................................................................................................9-154
Confidential and Proprietary Information of ZTE CORPORATION. iv

1 General Introduction
Abstract
This chapter focuses on SDR basic concept and commission flow.
1.1 ZXSDR BTS Introduction

ZXSDR serial BTS are a brand-new series of radio products designed and
produced by ZTE. They use the advanced SDR technology and their hardware
structure is based on the uniform TCA platform of ZTE, innovatively
supporting multiple radio access methods, including GSM, UMTS, CDMA2000,
and WiMAX. In addition, SDR can be smoothly evolved into the Enhanced
EDGE/LTE.
Currently, the GSM networking mainly uses three types of SDR BTS: the first is
indoor macro BTS, such as ZXSDR B8800 GU360; the second is outdoor
macro BTS, such as ZXSDR B8900 GU360; the third is distributed BTS in
which Baseband Unit (BBU) is separate from Remote Radio Unit (RRU), such
as ZXSDR B8200 GU360 + ZXSDR B8860 GU906/GU186. For the structure,
see Figure 1.1 -1.
Confidential and Proprietary Information of ZTE CORPORATION. 1

Figure 1.1-1 Distributed BTS
Compared with the traditional BTS, SDR has the following features aside from
supporting multiple systems such as GSM and UMTS, etc.
1.1.1 BBU+RU Architecture
The separation between baseband and RF can maximize their own

advantages. The baseband can obtain the maximum integrity, while RF
focuses on the maximization of its own power and efficiency. Therefore, the
networking is more flexible. After the separation, the baseband part is called
BBU (base band unit), while the RF part is called RU (radio unit). RU can be
placed in the same cabinet with BBU, such as BS8800, BS8900, etc., it can
also be placed remotely, which is called RRU (remote radio unit). Their
functions are displayed as shown in Figure 1.1 -2:

Figure 1.1-2 Distributed Structure of BBU and RU
BTS is divided into BBU and RU. One BBU can provide baseband resources
for multiple RU. Functions of BBU and RU are as follows:
BBU is responsible for digital baseband signal processing and control

management.
RU is responsible for switchovers between digital baseband signals and

analog signals between BBU and antenna.
BBU is connected to RRU through the baseband-to-RF interface (optical

interface), and it transmits I/Q digital baseband signals and OAM signaling
data.
BBU is connected to BSC/SDR through the Abis/Iub interface.
RRU accesses MS/UE through the Um/Uu interface.
1.1.2 OMCB Introduction
A traditional 2G BTS (such as BTSV2 and BTSV3) is configured and managed

through OMCR (including iSMG), while SDR BTS is configured on LMT or
OMCB. OMCR is used to configure some radio data.
The operation and maintenant center for NoedB (OMCB) is the O&M unit that
manages BTS in the 3GPP. As a dual-mode product supporting GSM and 3G,
SDR also supports OMCB. The single-threaded link OMCR BSC BTS is
changed into the dual-threaded link OMCB BTS (in actural network, OMCB
is placed at BSC or RNC side, and the route channel from OMCB to SDR is

provided by BSC or RNC) and OMCR BSC BTS. For BTS, an upper level
is added, as shown in Figure 1.1 -3.
OMCB OMCR
RNC BSC
SDR
Figure 1.1-3 SDR Network Management Structure
Based on the management mode of UMTS, the board management,

configuration, software downloading, alarms of all SDRs are implemented on
OMCB. In a dual-mode system, the operation and management of GSM
equipment are performed on OMCB, while OMCR only manages the GSM-
related radio configuration and status management. This is a specific feature of
OMCR in SDR environment.
1.1.3 IP Abis Interface
The other major difference between SDR and a traditional 2G BTS is the IP
protocol at Abis/Iub interface. Its physical bearer can be FE/GE or E1/T1 (IP
over E1/T1), but not the E1/T1 of TDM. If E1/T1 is used, BTS can fully use the
existing transmission equipment to save the user investment; if FE/GE is used,
BTS will obtain more bandwidth, which is oriented to the communication
system evolution to all IP. See Figure 1.1 -4 for the transmission network with
FE/GE at Abis/Iub interface:

Figure 1.1-4 Transnmission Network with FE/GE at Abis Interface
Therefore it is the prerequisites that to understand and master BBU+RU

hardware structure, OMCB+OMCR network management structure and IP
networking, etc.
Note: If it is not specified in this book, the BSC interconnected with SDR refers
to ZXG10 iBSCV6.20 in hundred mega or kilo mega platforms.
1.2 SDR BTS Commissioning Flow

The following figure shows the SDR BTS commissioning flow:

Figure 1.2-5 SDR Commissioning Flow
As shown in Figure 1.2 -5, BSC installation commissioning includes hardware

installation, background software installation, BSC data configuration, version
management, interconnection at A and Gb interfaces, and service test, etc. The
background network management software must be installed in the mode of
OMCR+OMCB (it is supported by iSMGV6.20). See related iBSC V6.20
engineering manuals and specifications for details.

For SDR hardware installation please refer to ZXSDR B8200 GU360

(V4.00.100) Indoor GSM&UMTS Dual Mode Baseband Unit Hardware
Installation ,ZXSDR R8860 GU906 GU186 (V1.00) Outdoor GSM&UMTS Dual
Mode Macro RRU User Manual, ZXSDR BS8800 GU360 (V4.00) Indoor
GSM&UMTS Dual Mode Macro Node B Hardware Installation Guide, etc. (Log
on to http://tsm.zte.com.cn to download these documents.) This book focuses
on the inspections after installation, to ensure normal commissioning and
debugging.
OMCR data configuration in this book refers to the related operation of SDR at
BSC side, other items for BSC intallation and commissioning are not
mentioned here. The data operation in OMCR falls into four parts: BSC global
resource settings, board configuration at Abis interface, IP interface
configuration, and radio parameter configuration for SDR site.
OMCB is the operation and maintenance center of SDR BTS, on which SDR
data configuration and remote maintenance are performed during
commissioning. This chapter focuses on how to create SDR BTS management
NE (OMCB) in iSMG, and how to configure SDR data in OMCB.
LMT local conmissioning is to connect the debugger to SDR and configure

local data through LMT. You can use LMT to configure transmission-related
information (such as IP address and route), physical information (such as
board configuration and topology relation), and partial radio information (such
as band and central frequency). You can also use it to manage the SDR
version.
Synchronization between foreground and background indicates that, after the

link between foreground and background is established, data at the foreground
is transconfigured to the background, or the data configured on the background
is synchronized with the background. There are four prerequisites for link
establishment between foreground and the background:
The transmission network runs normally.
SDR interface-related parameters are correctly configured in OMCR.
SDR management NE is correctly created in OMCB.
Transmission parameters are correctly configured through LMT.

Note that the items configured in LMT are the same with that in OMCB. During
SDR commissioning, the data at BSC side should be configured in OMCR first
in the following two ways: 1. Configure all data through OMCB, meanwhile
configure SDR transmission parameters through LMT to establish a link
between SDR and OMCB, and then synchronize the data configured in OMCB
to SDR. 2. Configure all data though LMT, meanwhile create a SDR
management NE in OMCB to establish a link between OMCB and SDR, and
then transconfigure SDR data to OMCB. Both the methods are described in
this book, but the first one is recommended.
After data configuration, dialing test and drive test should be performed on site,
so as to figure out and solve any possible issues. Make sure the BTS works
normally, before the commencement of Operators acceptance test.
Note: The SDR transmitted in E1 currently supports remote link establishment.

A set of default data has been configured in the SDR before delivery, which can
be used to establish links between SDR and BSC/OMCB. In this case, data
configuration in LMT is not necessary during commissioning.
1.3 Chapter Outline

See the following outline for the description of the commissioning flow:
Chapter 2: Preperation for SDR commissioning.
Chapter 3: Hardware inspection of SDR equipment.
Chapter 4: The configuration for SDR in OMCR, including board configuration

at Abis interface, board configuration at OMCB interface, RPU virtual address,
and wireless parameter configuration at SDR site, etc. FE port and IPOE are
also described in this chapter.
Chapter 5: The configuration of SDR data in OMCB. If all the configuration in

LMT is complete, its unnecessary to configure the data in OMCB, which only
needs to be transconfigured in the foreground.
Chapter 6: The configuration of SDR data in LMT, including physical

(transmission) configuration and wireless configuration, etc.

Chapter 7: Test items after commissioning. For test procedures and methods,
please refer to 08 ZXSDR B8200&R8860 Test Guide, 08 ZXSDR BS8800 Test
Guide from http://tsm.zte.com.cn.
Appendix A: General information index, including the conversion between

frequency point and frequency, the IP address of each SDR board.
1.4 Document Application

1. This document describes the commissioning procedures for the Indoor
Macro BTS ZXSDR BS8800.
The indoor macro BTS mentioned in this document only applies to GSM single
mode, but not UMTS or GSM+UMTS mode.

2 Commissioning Preparations
Abstract
This chapter focuses on the preparations before commissioning,
including the tools, software, documents, SDR hardware, configuration
data and initialized operation and verification method of CC board.
2.1 Version Preparations

1. SDR version packet file.
2. LMT software packet corresponding with the SDR version.
3. All the version files should be applied by the local offices in

http://support.zte.com.cn.
2.2 Document Preparations

1. BTS Installation Acceptance Report (Confirm that the installation is
complete and has passed the acceptance test).
2. Unpacking Inspection Report (Make sure that boards and other hardware
required for the commissioning have been normally delivered).
3. Engineering Survey Report (Verify the equipment layout, networking,

cabling, and connection relations).
4. ZXSDR BS8800 GU360 (V4.00.100) Hardware Installation Guide,

ZXSDR BS8800 GU360 (V4.00.100) Terrestrial Parameter Reference,
ZXSDR BS8800 GU360 (V4.00.100) Radio Parameter Reference,
ZXSDR BS8800 GU360 (V4.00.100) Terrestrial Parameter Configuration
Guide, ZXSDR BS8800 GU360 (V4.00.100) Radio Parameter
Configuration Guide, ZXSDR BS8800 GU360 (V4.00.100) Centralized
Management Operation Guide, ZXSDR BS8800 GU360 (V4.00.100)
Software Management Operation Guide, ZXG10 iBSC (V6.20)
Configuration Manual (Initial Configuration Guide), and other iBSC
installation and operation manuals. You can download these manuals
and documents from the website http://tsm.zte.com.cn.

5. 08 ZXSDR BS8800 (V4.0) BTS Test Guide.
2.3 Configuration Data Preparation

The configuration data to be prepared includes the BTS configuration data and
the Abis interface interconnection data. The BTS configuration data includes
the site type, the number of carriers per RRU, LAC, CI, and frequency data.
The Abis interface interconnection data includes the GSM site ID, the BTS IP
address, and the IP Abis address of iBSC.
Table 2.3 -1 gives an example of interconnection parameters.
Table 2.3-1 Parameters for the Interconnection Between ZXSDR and iBSC
Parameter Data Instance

GSM site ID 2
Abis interface IP address of BTS 118.18.2.100
IP Abis (virtual) address of iBSC 118.18.1.1
SCTP port number of the remote BSC 14595
Gateway address for access to the remote
118.18.1.1
BSC
Attached below is an example of the BTS configuration data for a certain field
trial.
Site Information
of SDR Field Trial.xls
2.4 Others
1. One commissioning PC (add the configuration information).
Hardware environment:
Typical Configuration Minimum Configuration
a) CPU 2.0 GB 1.8 GB
b) Memory 1 GB 512 MB
c) Hard disk 80 GB 1 GB (Minimum available space)
d) Resolution 1024768 800600

e) CD-ROM CD-ROM CD-ROM
f) Network card 10&100M 10&100M
Software environment
a) OS: Windows 2000 or Windows XP
b) Default language of the OS: English or Simplified Chinese
c) OS pattern: Windows XP or standard Windows
2. Crossover cables (or straight-through cables if the network card of the

commissioning PC supports the auto negotiation function).
3. Two test mobile phones (supporting the basic GSM services and data
services), data lines, SIM cards (make sure that the SIM cards have
been well programmed and the subscribers are legal subscribers
registered in the HLR), and data cards.
4. Personnel and vehicles.

ZXSDR BS8800 (V4.0) Project Commissioning Guide For Internal Use Only
3 Hardware Check
Abstract
This chapter describes the methods for checking ZXSDR hardware, including
board, cable connections, and running status after equipment is powered on.
Before performing the hardware check, make sure that ZXSDR hardware has
been properly installed.
3.1 Hardware Installation Check
3.1.1 Checking Boards

Check whether the types, quantities, and locations of boards are
consistent with the planning.
Figure 3.1-6 Front Panel of B8200 (Slot Numbers Are Marked in Red)
The above figure shows the baseband part of BS8800, which also serves as
B8200 in the distributed BTS. It supports two control and clock boards (CC)
working in active/standby mode, two fiber switching boards (FS) working in
load-sharing mode, and at most five UBPG boards for baseband processing
(The slots of FS boards can also hold UBPG boards, therefore at most five
UBPG boards can be inserted when only one FS board is configured). B8200
can have two power modules, which may work in active/standby or load-
sharing mode depending on the actual needs. Only one SA board and one FA
module can be inserted.
Check whether the board configurations are correct according to the planning.
1
3.1.2 Checking Internal Jumpers on SA Board

Check whether jumpers on the SA board are properly set according to
the actual transmission mode
Jumpers X5 and X6 on the SA board need to be set according to the

actual transmission mode, the locations of which are shown in Figure
3.1 -7 Jumpers on the SA Board. X5 is used to set the E1/T1 mode
whereas X6 is used to set the cabinet number in the case of BBU
cascading.
As shown in Figure 3.1 -7 Jumpers on the SA Board, the right bits of

X5/X6 are the least significant bits and the left bits are the most
significant bits.

Figure 3.1-7 Jumpers on the SA Board
The two least significant bits of X5 are used to set the E1/T1 mode
and the transmission impedance (see Table 3.1 -2). The two most
significant bits are used to set the uplink/downlink long or short line
mode of the E1/T1 (see Table 3.1 -3).
Table 3.1-2 Settings of the Two Least Significant Bits of X5
Bits of X5 [1, 0] E1/T1 Mode

[Shorted, shorted] Reserved
[Shorted, open] T1, 100
[Open, shorted] E1, 120
[Open, open] E1, 75 (default)

By default, the SA board uses the E1 75 mode. Therefore, it is

unnecessary to set the two least significant bits of X5 if the current site
adopts the E1 75 mode.
Table 3.1-3 Settings of the Two Most Significant Bits of X5
Bits of X5 [3, 2] Mode

[Open, open] Uplink short line, downlink short line
[Shorted, shorted] Uplink long line, downlink long line
[Open, shorted] Uplink short line, downlink long line
[Shorted, open] Uplink long line, downlink short line
The uplink and the downlink represent two different transmission

directions. The uplink refers to the direction from BBU to BSC/RNC,
whereas the downlink refers to the direction from BSC/RNC to BBU. The
long or short line represents the receiving mode of E1. The long line
mode is applied when the E1 transmission line is rather long (longer than
1 km), whereas the short line mode is applied when the E1 transmission
line is short.
X6 is used to set the BBU cabinet number in the case of BBU

cascading. It can set at most eight BBU cabinet numbers (in practical
application, at most four BBU cabinets can be cascaded). The value
ranges from 000 to 111, and the default value is 000, as shown in
Table 3.1 -4.
Table 3.1-4 Settings of X6
Bits of X6 [2, 1, 0] BBU Cabinet Number

[Open, open, open] 0
[Open, open, shorted] 1
[Open, shorted, open] 2
[Open, shorted, shorted] 3
[Shorted, open, open] 4
[Shorted, open, shorted] 5
[Shorted, shorted, open] 6
[Shorted, shorted, shorted] 7
3.1.3 Checking Input Power

Check whether polarities of the input power are correctly connected.
Check whether the power input range is 40 V DC to 57 V DC.

PSU (a module for conversion between AC and DC) should be used

when the equipment room uses 220 V AC. Check whether the
fluctuation range of the single-phase voltage is 200 V AC to 240 V AC.
3.1.4 Checking Cable Connections

Check whether FE cables between B8200 and iBSC are correctly
connected if FE connections are applied at Abis interface; if CC
boards is configured in active/standby mode, make sure both boards
are connected with FE cables at Abis interface.
Check whether E1 media between DDF and B8200 are correctly

connected if E1 connections are applied at Abis interface.
Check whether optical fibers from the FS board of B8200 to R8860

are correctly connected.
Check whether the network connection between the debugging port

ETH1 on the CC board and operation and maintenance station LMT is
normal.
Check whether dry contact, the 232 serial port cables and the 485
serial port cables are correctly connected.
3.2 Equipment Power-On and Power-Off
3.2.1 B8200 Power-On and Power-Off

Power-on procedures
1. Pull out all the boards of B8200 except for PM module and FA module.
2. Switch on the power, check whether the RUN indicator on the PM

module is on and the ALM indicator on the PM module is off.
3. Check whether the fan module is running normally, the PWR indicator is
on, and the ALM indicator is off.
4. After the equipment is powered on and fans are running normally, insert
the other boards such as CC, BPC, FS and SA, and then observe
whether each board is in normal status. Note that the running indicator
on a board will be off if the data of the board is not yet configured.

Power-off procedures
Switch off the power supply from the power distribution cabinet or PSU. It
is prohibited to plug or unplug the power cable before verifying PM
module has been powered off.
Note:
1. ALM indicators on the PM module and boards will be flashing at the

beginning of power-on, indicating that PM module and boards are not yet
started. This is normal. When no SA board is inserted, the ALM indicator
on the FA board will be on. Connect cables of the PM module before
powering on the shelf. It is prohibited to plug or unplug the power cable
when the PM module is powered on.
2. Boards in Slots 1 to 8 have two pullers. The left puller has three position
levels whereas the right puller is fixed. Before pulling out a board, pull
the left puller to the outmost position level. When inserting a board, insert
it along guide rails and then push the left puller to the inmost position
level till the board is locked.
3. To remove the fan shelf: Push the locking switch rightward on the lower
part of the front panel and then pull out the fan shelf.
3.2.2 Checklist Before Power-on

Item Requirements and Criteria Results Remarks
Types, quantities, and locations of boards are Pass
consistent with the planning. Fail
Checking
Jumpers on the SA board are correctly set
boards Pass
according to the actual transmission mode and
Fail
cabinet cascading.
Polarities of the input power of B8200/RU (RSU) Pass
are correctly connected. Fail
The input voltage range of B8200/RU (RSU) is Pass
40 V DC to 57 V DC. Fail
Checking If B8200/ RU (RSU) adopts single-phase voltage
input power 220 V as the power supply, the accepted range is
between 200 V AC and 240 V AC. The accepted Pass
frequency range is between 47 Hz and 53 Hz, and Fail
PSU is connected to convert AC to DC to provide
power for B8200.
Checking Cables between FS board and RU (RSU) are Pass

cable
connection correctly connected. Fail
between racks
If FE cable is adopted, the connection between Pass
Checking
FE cables and CC board is correct. Fail
connection at
If E1 cable is adopted, the E1 transmission Pass
Abis interface
between DDF rack and BTS is correct. Fail
Checking the
connection of The network cable port on LMT Client is correctly Pass
LMT Client connected with CC board. Fail
(Optional)
Pass
All the boards have been pulled out.
Fail
Equipment The status of each board is normal after power- Pass
power-on on. Fail
Pass
The shelves are properly grounded.
Fail
Checking
Pass
power-on The equipment has been normally powered on.
Fail
results
Note

4 Operation and Maintenance Networking

of SDR
Abstract
This chapter describes SDR operation and maintenance networking to
understand the meanings of various IP parameters in SDR commissioning.
4.1 SDR Operation and Maintenance Networking Diagram

Based on the previous description of the differences in an SDR BTS and a
traditional 2G BTS, we know that SDR BTS has two network management
systems, including OMCR and OMCB. Most of work is done on OMCB, as
shown in Figure 1.1 -3. In actual networking, OMCB and OMCR can be
installed on two separate servers, or integrated in one network management
system (iSMG) on one server (SBCX). The installation and commissioning in
this manual is based on the case that OMCB and OMCR are installed on one
SBCX.
4.1.1 Networking with Ethernet as Bearer at Abis Interface
Figure 4.1 -8 shows the networking topological view of an OMC-B network

when a ZXSDR BTS is accessed to an iBSC in Ethernet (FE/GE) mode.
At BTS side, iBSC is accessed to a local Ethernet switch at Abis

interface (FE/GE electrical interface or optical interface) and reaches the
IP interface board IPBB (physically, the 1,000 M platform is GIPI and the
100 M platform is BIPI) of iBSC by means of an IP backbone network.
On BSC side, iBSC is connected to OMC-B and BTS by means of

IPBB interface board.
End-to-end communication between ZXSDR BTS and OMC-B Server

is performed with an OMC-B link. OMC-B Client is connected to OMC-B
Server for operation configuration.

Figure 4.1-8 OMC-B Network Topology with FE at Abis Interface
4.1.2 Networking with E1/T1 as Bearer at Abis Interface
Figure 4.1 -9 shows OMC-B networking topological view when ZXSDR BTS is
accessed to iBSC in E1/T1 mode. In this case, the following items should be
paid attention to:
The connection from BTS to iBSC is not by means of Ethernet switch,

but E1/T1, with which the BTS is directly connected to E1 interface board
(DTB) at Abis interface of iBSC;

At Abis interface, iBSC is connected to BTS with E1/T1 interface board

(DTB) instead of IPBB interface board. The BTS message is processed
with on EUIP. In this case, the OMC-B operation and maintenance
gateway of the BTS is the IP address set on the EUIP of iBSC;
OMC-B Server is still accessed to iBSC by means of IPBB board.
Figure 4.1-9 OMC-B Network Topology with E1 at Abis Interface
Note:
RPU is not shown in the above topological view. In fact, RPU is responsible for
route processing for iBSC.
4.2 One Instance

IP address planning

It is suggested to set OMP, OMCR, OMCB and SDR in different network

segment;
It is suggested to set SDR and the corresponding EUIP or IPBB_SDR in

the same network segment;
If SDR and OMCB are not in the same network segment, the route to SDR
network segment should be added in OMCB.
In the same iBSC, different EUIP port addresses cannot be set in the
same network segment; the port addresses on IPBB board cannot be set
in the same network segment.
The following table is an example of IP planning. For the sake of direct

observation, the third section of a BTS IP address identifies the SITEID, as
shown by x in the following table (If there are more than one BSC, the second
section identifies the BSCID, for example, the IP address of Site 6 of BSC5 is
118.5.6.100). The SDR commissioning described below is based on this data.
Table 4.2 Example of IP Address Planning
Configuration Item Configuration Information Mask

IP of the network interface connected
139.1.1.254 255.255.255.0
with OMCB Server in iBSC
OMCB Server IP configured in iBSC 139.1.1.200 255.255.255.0
IpAbis virtual address of iBSC 118.18.1.1 255.255.255.255
IP of the network interface connected
118.18.X.254 255.255.255.0
with BTS in iBSC
IP address configured in BTS 118.18.X.100 255.255.255.0
Networking description
When jointly deployed, OMCB and OMCR are logically two separate NM units
except that they are physically installed on SBCX boards. In this case, iBSC
needs to provide two IP interfaces, connecting respectively to SDR BTS and
OMCB Server; BSC needs to be configured with a virtual address (RPU
interface address). The networking is shown in Figure 4.2 -10.
Connection between SDR and BSC: When E1 is physically used for

access, the interface board on the SDR side is SA and that at BSC side is
DTB or SDTB (EUIP is required for IP access). When FE/GE is used, the
interface board at SDR side is CC and that on the BSC side is IPBB.

Connection between OMCB and BSC: when FE/GE is used, the interface
of OMCB (the external network interface of SBCX) is generally OMC2
(Note). IPBB is used on the BSC side.
Figure 4.2-10 Network Topology of the OMCB Operation and Maintenance System
Note: It is not suggested to use HEART1 (1,000 M interface) as OMCB

interface. If SBCX in active/standby mode is placed at the Slots 1/2, 3/4, or 5/6,
7/8, the backplane in the Version 060201 and later adopts HEART1 and
HEART2 interfaces for the communication between two SBCX, therefore the
two interfaces cannot serve as external interfaces.
Add a route
In the example as shown in Figure 4.2 -10, the IP address of OMCB server
and that of SDR are not in the same network segment. Therefore, it is
necessary to add a route from an OMCB gateway to SDR network segment.
In Linux system, the command to add a route is as follows:
route add -net destination network address gw next-hop-address netmask

network mask interface ip
1. Command to add a route
In this example, the IP address of OMCB server is 139.1.1.200. Its gateway

address (IPBB_OMCB address) is 139.1.1.254. The IP address of SDR is
in the network segment 118.18.1.0. Then, the command to add a route to
the iBSC virtual address on OMCB (SBCX) is as follows:
#route add net 118.18.1.0 gw 139.1.1.254 netmask 255.255.255.0 eth1
2. View route status
After the route is added, its status can be viewed with the command
netstat nr.

3. Set a permanent route
After adding the route with the command route add, to prevent the
configured route being lost due to restarting SBCX, it is suggested to log on
with user ID root to add the following line to the file /etc/rc.d /rc.local:
#route add net 118.18.1.0 gw 139.1.1.254 netmask 255.255.255.0 eth1
Thus, each time SBCX is started, the route will be automatically added.
4. Check after SBCX restart
Quit all processes and restart SBCX. Check whether the route is normal
with the command netstat nr.
5. Verify after adding route
Quit all processes and restart SBCX. Check whether the route is
normal with the command netstat nr.
From SBCX, you can successfully ping the IP address of SDR, which
is the 118 network segment address of CC board in this example.
After you have telneted CC board, you may connect to RRU by using
the command rlogin RRU IP. Make sure that there are quotation
marks. The format of RRU IP is as follows: 200.(Environment No.).0.
(101+FS Port No.), the default Environment No. is 254.
According to the silkscreen sequence, the FS Port Nos. from right to

left are 0, 1, 2, 3, 4, 5.
To comfirm to the installation regulations, the relation between FS Port

No. and RSU Slot No. on RRU layer is:
1. FS Port 5 is corresponding to RSU Slot 1;
For example, FS Port 0 is corresponding to RSU IP address:

200.254.0.101.
#telnet 118.18.2.100
CC->rlogin 200.254.0.101
DTR->********
With this command you can telnet to RRU.

5 OMCR Data Configuration
Abstract
This chapter describes the SDR BTS configuration at OMCR side.
Configuration at A interface and Gb interface will not be described in this
manual.
Note: The data configuration in this chapter is based on Table 4.2 .
[Objective]
1. Set the configuration parameters for BSC global resource;
2. Configure BSC boards at Abis interface and OMCB interface;
3. Complete the IP configuration at Abis interface, OMCB interface and BSC

virtual address;
4. Configure SDR logical sites and radio parameters;
[Preliminary Setup]
1. Operating system, database, and iOMCRV6.20 NM with OMCR and OMCB

are correctly installed and run normally.
2. Interconnection of iBSC at A interface and Gb interface of iBSC is

complete. Dialing test is normal;
3. The IP address related information has been planned, including SDR site
IP, BSC IP at Abis interface, BSC virtual address, IP at OMCB interface,
and OMCB server address, etc. SDR corresponding module number and
Abis interface location on BSC have been planned.
5.1 Configuration of BSC Global Resource

1. Create the GERAN subnet configuration, BSC management NE
configuration, configuration set configuration, BSC global resource
configuration, and BSC physical equipment configuration according to the
mode in iOMCRV6.10.

2. Click the icon in the left configuration resource tree window, and locate
the current directory to [OMCGERAN Subnet User IDBSC
Management NE User IDConfiguration Set IDBSC Global Resource
ID].
3. Double click [BSC Global Resource ID], and a window [BSC Global
Resource] pops up, as shown in Figure 5.1 -11. Click to enter the
modification mode. According to the planned addresses, set OMCB IP
in the Basic Property page and IP Abis in the IP Property, as
shown in Figure 5.1 -12. Click OK to finish the creation.
Figure 5.1-11 Setting BSC Global Resource Properties

Figure 5.1-12 Setting iBSC Virtual Address
5.2 Configuration of Abis and OMCB Interface Boards

During SDR commissioning, the following aspects should be paied attention to:
IP at Abis interface. If FE is physically used, IPBB is used as the interface

board at Abis interface; if E1/T1 is physically used, DTB is used as the
interface board at Abis interface. Besides, EUIP (the physical board is
EIPI) should be added.
OMCB NM is a special feature of SDR. OMCB server accesses to iBSC

through IPBB, which can be the same board or different boards, used for
the access at Abis interface.
About EIPI:
1. EIPI and DTB or SDTB/SDTB2 provide IP access based on E1-/T1. An

EIPI board has no external interface or rear board. One EIPI board plus
two DTB boards or one SDTB board can support up to 64 E1/T1 interfaces.
2. After HW data is accessed to an interface unit and processed with HDLC

protocol in EIPI, its payload is sent to a service processing unit, where user
plane data and control plane data are separated. By means of a user plane
switching network, the user plane data is sent to GUP/GUP2 for further

processing. By means of the control plane switching network, the control

plane data is sent to CMP for further processing.
5.2.1 Configuration of Abis Interface Board
When Abis interface uses IPOverE1:
1. Create a DTB board at Abis interface, and add an Abis interface PCM in
the PCM Information page, as shown in Figure 5.2 -13:
Figure 5.2-13 PCM Property Configuration
Parameter description:
PCM type: Select EUIP when iBSC is connected with an SDR site in
IPOVERE1 mode.
Frame mode: Select the multi-frame format when iBSC is connected with an
SDR site in IPOVERE1 mode.

2. Create an EUIP board, and configure its property as shown in Figure 5.2
-14. In HDLC Information, connect 2MHW inside EUIP with the E1 of DTB
board at Abis interface, as shown in Figure 5.2 -15:
Figure 5.2-14 Creating Basic Information of EUIP Board
Channel mode: Select Channel mode 5 for a 1,000 M platform (one inward GE
port);
Select Channel mode 2 for a 100 M platform (four inward FE ports).

Figure 5.2-15 HDLC Configuration of EUIP Board
HDLC No.: Allocate an HDLC No. to each E1. This HDLC No. needs to be
referenced when IPOverE1 is configured.
EUIP 2MHW No.: It is used to identify 2MHW No. in EUIP.
DT unit No.: unit No. of DTB board in use.
DT PCM No.: E1 No. of DTB board in use.
TS configuration information: corresponding relationship between EUIP 2MHW

timeslots and DT PCM timeslots. Add the timeslot resource in actual use to the
right timeslot table. Select 31 timeslots unless stated otherwise.
Note:
EUIP board and DTB or SDTB/SDTB2 board must be in the same frame.

EUIP does not support active/standby mode. (Because the PPP link platform
currently does not support active/standby mode).
When Abis interface uses FE
It is unnecessary to configure DTB board or EUIP board in BUSN for Abis

interface connection, but to configure IPBB interface board in BUSN for Abis
interface connection, as shown in Figure 5.2 -16:
Figure 5.2-16 IPBB Board Configuration in the Case of SDR Access
5.2.2 Creating an IPBB Board Accessed to OMCB
The configuration method is the same as that of IPBB board accessed to FE

Abis interface, as shown in Figure 5.2 -16.
IPBB board accessed to OMCB and that accessed to SDR may use different
network interfaces of the same board, but both network interfaces need to be
configured with different network segments.

5.3 IP-related Configuration

[Objective]
1. Complete the IPBB (OMCB) interface configuration, and link iBSC and
OMCB server.
2. Configure the IP Abis virtual address of iBSC.
3. Complete the IP interface configuration at Abis interface, and link SDR with
iBSC.
[Preliminary Setup]
1. The boards related to Abis and OMCB interfaces have been successfully
created.
2. IP addresses of Abis interface, IP Abis interface, and IPBB (OMCB)

interface have been planned.
5.3.1 Creating an IP Abis Interface
1. Click the icon in the left configuration resource tree window. Locate the
current directory to [Configuration SetBSC Global Resource IDIP-
related Configuration Interface Configuration].
2. Right click Interface Configuration, and select [CreateInterface], as

shown in Figure 5.3 -17.

Figure 5.3-17 Creating an IP Interface
3. In the pop-up dialog box Select Interface Information, select RPU as

Board function type to create an IP Abis interface, that is, the iBSC virtual
address. For details, see Figure 5.3 -18:
Figure 5.3-18 Selecting RPU as Board Function Type to Create an IP Abis Interface

Board function type: Select RPU as the board function type of IP ABIS;
Module: subsystem: unit: sub-unit: It is automatically set by the system;
4. Fill in the basic information of the created IP ABIS interface. For details,
see Figure 5.3 -19:
Figure 5.3-19 IP Abis Interface Configuration
Port No.: Default value is 1. If more than one virtual address is configured on
RPU, the port No. of each address cannot be the same;
MAC address: It is a virtual address without network card entity, which can be
set randomly. Make sure this MAC address does not conflict with that of EUIP
or IPBB;
Board function type: RPU;
IP address: IP Abis configured in OMCR.
Subnet mask: All the four fields must be filled in (that is, 255.255.255.255.).

5.3.2 Creating IPBB Interface of OMCB
the current directory to [Configuration SetBSC Global Resource IDIP-

3. In the pop-up dialog box Select Interface Information, select IPBB as

Board function type to create an IPBB interface, as shown in Figure 5.3
-20:
Figure 5.3-20 Creating IPBB Interface Accessed to OMCB
4. Fill in the basic information of the created IPBB interface, as shown in

Figure 5.3 -21:

Figure 5.3-21 Configuration of IPBB Interface Accessed to OMCB
Port No.: When IPBB uses an RGE R rear board, it provides one external GE
port. Select 1 as the port No. here. When IPBB uses an RMNIC rear board, it
provides four external FE ports. Select 1, 2, 3 or 4 as the port Nos. according
to the actual condition.
MAC address: It can be randomly set within the range of [00-D0-D0-A0-00-00,

00-D0-D0-A0-9F-FF] or [00-19-C6-3E-30-10, 00-19-C6-4E-30-0F], but should
be different from the MAC address of any other ports. (Or set the MAC address
as follows: 00-DO-D0-A0- (Rack No.16+Shelf No.)-(Slot No.16+Port No.)).
Subinterface ID: Keep the default value.
Subinterface Port No.: Keep the default value.
IP address: The address of IPBB port connected with OMCB server, which will
be used as the gateway address from OMCB server to SDR.
Subnet mask: Set 3 fields, that is, 255.255.255.0;

5.3.3 Interface Configuration with E1 at Abis Interface
Create an EUIP interface accessed in E1 mode
[Operating Procedures]
related ConfigurationInterface Configuration].

3. In the pop-up dialog box Select Interface Information, select EUIP as

Borad function type to create an EUIP interface, as shown in Figure 5.3
-22:
Figure 5.3-22 Creating an EUIP Interface Accessed to the SDR
4. Fill in the basic information of the created EUIP interface, as shown in

Figure 5.3 -23:

Figure 5.3-23 EUIP Interface Configuration
Port No.: Allocate one port No. to each EUIP real address. This port No. is
used to associate with that in IPOverE1. When the PPP protocol is used, the
effective port No. ranges from 1 to 190. When the ML-PPP protocol is used,
the effective port No. ranges from 191 to 254.
MAC address: Unnecessary to configure.
IP address: The BTS gateway address, which is iBSC real address to BTS.
Under the same iBSC, different EUIP links should not be in the same network
segment. This IP address should be in the same network segment as SDR.
Subnet mask: 255.255.255.0, or even smaller, such as 255.255.252.0.
Create IPOverE1 configuration
related ConfigurationIPOVERE1 Configuration].
2. Right click IPOVERE1 configuration, and select [CreateIPOVERE1

Configuration], as shown in Figure 5.3 -24:
Figure 5.3-24 Creating IPOverE1
3. Set corresponding parameters in the pop-up IPOverE1 configuration

interface, as shown in Figure 5.3 -25:

Figure 5.3-25 IPOverE1 Parameter Configuration
Port No.: When PPP transmission protocol is adopted on link layer, the Port
No. should be set as that configured in the EUIP interface parameter. When
ML-PPP transmission protocol is adopted on link layer, the Port No. is not
related to EUIP configuration, which is only required to be different from each
other in one ML-PPP, generally set as 1, 2, 3, 4.
HDLC No.: It is associated with HDLC No. in the EUIP board attribute - HDLC
configuration information.
Start TS - End TS: It refers to timeslot resource used by E1 link. The default
Start TS is 1, and End TS is 31, unless specified.
related ConfigurationIPOVERE1 ConfigurationIPOVERE1
Configuration IPOverE1 ID (IPOVERE1 configuration instance
configured in the previous step)].
5. Right click IPOverE1 ID, and select PPP Parameter Configuration, as

shown in Figure 5.3 -26:
Figure 5.3-26 Creating PPP
6. Set corresponding parameters in the pop-up window PPP Configuration.

For details, see Figure 5.3 -27:
Figure 5.3-27 PPP Configuration

Peer IP: BTS IP address.
Mpno sign: When PPP transmission protocol is adopted in the link layer, this
parameter is invalid; when ML-PPP transmission protocol (a site is configured
with multiple transmission links) is adopted in the link layer, Mpno sign is valid,
which should be set as corresponding EUIP Port No.
HdrCmpCfginfo sign: it is valid when PPP is configured with compressed

transmission.
Keep time(s), keep granularity: For example, if the keep time(s) is 25s and the
keep granularity is 5s, detection frames will be sent once every 25/5=5s. That
is, messages will be sent five times within the keep time. If no reply is received
for five consecutive times, it indicates that there is broken links in PPP.
5.3.4 Interface Configuration with FE at Abis Interface
If Abis interface uses FE access mode, there is no need to configure an EUIP

interface accessed in E1 mode or IPOverE1, but to configure a separate IPBB
interface accessed in FE mode in the same method as the configuration of
IPBB interface of OMCB server. For module, subsystem, unit, and sub-unit,
select the IPBB board information of Abis access. The IP address is iBSC real
address to an SDR site. Specific procedures are as follows:

3. In the pop-up dialog box Select Interface Information, select IPBB as

Board function type to create an IPBB interface. For details, see Figure 5.3
-20:

Figure 5.3-28 Creating an IPBB Interface Accessed to OMCB
4. Fill in the basic information of the created IPBB interface. For details, see
Figure 5.3 -21:
Figure 5.3-29 Configuration of IPBB Interface Accessed to SDR
Port No.: There is one outward GE optical interface on the front panel of IPBB.
If RGE R rear board is adopted, there is one external GE electrical interface
(the same interface as front panel). If RMNIC rear board is adopted, there are
four external FE interfaces. Therefore select 1 when GE interface is required;
select 1, 2, 3 or 4 when FE interface is required.

MAC address: It can be randomly set within the range of [00-D0-D0-A0-00-00,

00-D0-D0-A0-9F-FF] or [00-19-C6-3E-30-10, 00-19-C6-4E-30-0F], but should
be different from the MAC address of any other ports. (Or set the MAC address
as follows: 00-DO-D0-A0- (Rack No.16+Shelf No.)-(Slot No.16+Port No.)).
Subinterface ID: Keep the default value.
Subinterface Port No.: Keep the default value.
IP address: The address of IPBB port connected with OMCB server, which will
be used as the gateway address from OMCB server to SDR.
Subnet mask: Set 3 fields, that is, 255.255.255.0.
5.4 Logically Configuring a B8800 Site on OMCR

[Objective]
1. Complete the logical configuration of an SDR site.
2. Complete the cell configuration and transceiver configuration of SDR site.
[Preliminary Setup]
1. A BSC management NE has been successfully created; its parameters

have been set.
2. BSC boards have been correctly configured.
3. IP-related configuration has been correctly completed.
5.4.1 Creating a Logical Base Station
Note: OMCR is not related to the logical configuration of SDR, therefore the
OMCR configuration of BS8800, BS8900 and B8200 are the same.
IDBTS Configuration].
2. Right click BTS Configuration, and select [CreateSite], as shown in

Figure 5.4 -30.

Figure 5.4-30 Creating an SDR site on OMCR
3. The interface pops up as shown in Figure 5.4 -31.
Figure 5.4-31 Creating Configuration Information of an SDR Site on OMCR
Site ID: It must be consistent with GSM site No. configured for OMCB and LMT.
Site type: type of the actually installed BBU.
Access type: SDR uses IP access mode by default.

Bandwidth limit (Kb): It refers to the bandwidth constraint allowed by a bearer

link. For an SDR accessed in E1 mode, the bandwidth is set as 2,048Kb; for an
SDR accessed in FE mode, the bandwidth is set as 10,000Kb.
5.4.2 Creating a B8200 Rack
IDSite Configuration Site ID (the base station configured in the
previous step)].
2. Right click Site ID, and select [CreateSite Rack], as shown in Figure 5.4
-32.
Figure 5.4-32 Creating an SDR Rack on OMCR
3. In the pop-up Create Rack prompt box, click OK to create a

corresponding rack. Double click Site Rack ID in the configuration
resource tree. The rack diagram as shown in Figure 5.4 -33 appears.

Figure 5.4-33 B8200 Rack on OMCR
5.4.3 Configuring a B8200 Cell
IDSite ConfigurationSite ID].
2. Right click Site ID, and select [CreateCell], as shown in Figure 5.4 -34.
Figure 5.4-34 Creating the Cell of an SDR Site on OMCR
3. As shown in Figure 5.4 -35, set related cell parameters in the Create
Cell interface. Then click OK. BCCH ARFCN (BCCH Absolute Radio

Frequency No.) cannot be set here, but is configured when creating BCCH
TX, as shown in Figure 5.4 -38:
Figure 5.4-35 Cell Configuration Information of an SDR site on OMCR (1)
4. If users need to configure GPRS or EDGE parameters, they may set the
item Support GPRS (PsSupport) as Support GPRS in the [Basic
Params 1] page. The corresponding page will display, as shown in Figure
5.4 -36.

Figure 5.4-36 Cell Configuration Information of an SDR Site on OMCR (2)
5.4.4 Configuring a Transceiver
IDSite ConfigurationSite IDCell].
2. Right click the Cell, and select [CreateTRX], as shown in Figure 5.4 -37.
Figure 5.4-37 Creating a Transceiver

3. Click [Trx], and the interface as shown in Figure 5.4 -38 will pop up.
Configure the transceiver according to network optimization & planning
parameters. Click OK to complete the configuration.
Figure 5.4-38 Transceiver Configuration Information
4. Configure IP information and type the DSP MarkSeq (DSP Mark Sequence
No.) and Port No., as shown in Figure 5.4 -39.

Figure 5.4-39 IP Information of Transceiver
Bipb unit: Unit No. of BIPB board.
DSPSunit: DSP No. of BIPB board. There are 14 DSP on the GUP board of
100M platform, there are 15 DSP on the GUP2 board of 1,000M platform.
DSP MarkSeq: Each DSP has 16 (on GUP board) or 28 (on GUP2 board) DSP
mark sequence numbers, each of which bear the service of a transceiver.
Port No.: port No. of each transceiver, which is a unique No. in the same BSC.

6 OMCB Data Configuration
Abstract
OMC-B is a background NMS of ZXSDR base station. It is used to configure
the transmission data, physical data, and some radio data of ZXSDR base
station, and function as an LMT (Local Maintenance Terminal) in a more
flexible way.
This chapter describes how to configure SDR data on OMCB.
OMC-B environment creation involves operations on ZXSDR, iBSC and

background OMC-B software. We can use OMC-B only when we have
completed the data configuration of the three and keep data correct.
6.1 Installation of OMCB-OMCR Server Software

To ensure that OMCB server can establish a link to the foreground SDR, we
need to check and modify some configuration files.
6.1.1 Modifying deploy-030womcb.properties Configuration File (Log on with

user ID omc)
1. Log on with user ID omc to OMCB server, and enter the directory ums-
svr\deploy:
$cd ums-svr\deploy
$vi deploy-030womcb.properties
Before modification, the content of this file is as follows:
#########################################################################
# #
#property file format: name=value
#note: space is forbidden between name,'=' and value #

#########################################################################
#########################################################################
# #
# redefine the attributes in deploy-default.properties #
#########################################################################
#########################################################
#########################################################
# #
# Normal configuration, application can directly read and use them #
# #
#########################################################
#########################################################
ums.locale=zh_CN
ums.product=zxwomc
ums.version.main=R6.20.000d-B4.00.100d
ums.version.patch=
ums.version.integral=true
ums.name.zh_CN=ZXWR-OMM Operation and Maintenance Management System
ums.name.en_US=ZXWR-OMM Operation and Maintenance Management System
#########################################################################
# #
# NODEB configuration #
#########################################################################

########################################################################
# NodeB FTP configuration
# macro name: "OMC-" + "Direct-"(or "Ipoa-") + BaseStation type + "-ftpIP";
# BaseStation type includes B09, B09A and so on, #
# if the IP address is for all BaseStation type, just use "ALL" . #
# if specific BaseStatcion type and "ALL" are both configured, the configuration of specific
BaseStation
# type is adopted.
# example:
# userdefined-zxwomc-common-nodeb-api.OMC-DirectB09-ftpIP=118.106.38.18
# userdefined-zxwomc-common-nodeb-api.OMC-DirectB09A-ftpIP=118.106.38.18
# userdefined-zxwomc-common-nodeb-api.OMC-DirectALL-ftpIP=118.106.38.18
# userdefined-zxwomc-common-nodeb-api.OMC-IpoaB09A-ftpIP=128.30.1.2
# userdefined-zxwomc-common-nodeb-api.OMC-IpoaB09-ftpIP=128.30.1.2
# userdefined-zxwomc-common-nodeb-api.OMC-IpoaALL-ftpIP=128.30.1.2
########################################################################
userdefined-zxwomc-common-nodeb-api.OMC-ftpUser=ftpuser
userdefined-zxwomc-common-nodeb-api.OMC-ftpPassword=ftp123
userdefined-zxwomc-common-nodeb-api.OMC-DirectB09-ftpIP=10.61.56.231
userdefined-zxwomc-common-nodeb-api.OMC-DirectB09A-ftpIP=10.61.56.231
userdefined-zxwomc-common-nodeb-api.OMC-DirectB03C-ftpIP=10.61.56.231
userdefined-zxwomc-common-nodeb-api.OMC-DirectSHELTER-ftpIP=10.61.56.231
userdefined-zxwomc-common-nodeb-api.OMC-DirectBBUA-ftpIP=10.61.56.231
userdefined-zxwomc-common-nodeb-api.OMC-DirectBBUB-ftpIP=10.61.56.231

userdefined-zxwomc-common-nodeb-api.OMC-DirectBBUC-ftpIP=10.61.56.231
userdefined-zxwomc-common-nodeb-api.OMC-DirectB8812-A-ftpIP=10.61.56.231
userdefined-zxwomc-common-nodeb-api.OMC-DirectB8812-B-ftpIP=10.61.56.231
userdefined-zxwomc-common-nodeb-api.OMC-DirectBS8800-ftpIP=10.61.56.231
userdefined-zxwomc-common-nodeb-api.OMC-DirectZXSDR_B8200_GU360-
ftpIP=139.1.1.200
ftpIP=139.1.1.200
ftpIP=139.1.1.200
userdefined-zxwomc-common-nodeb-api.OMC-IpoaALL-ftpIP=139.1.1.200
userdefined-zxwomc-common-nodeb-api.OMC-DirectPicoNodeB-ftpIP=10.61.56.231
userdefined-zxwomc-common-nodeb-api.OMC-IpoaPicoNodeB-ftpIP=10.61.56.231
Set OMCB address. Select corresponding lines according to SDR type

managed by this OMCB and the connection mode between SDR and BSC.
6.1.2 Modifying FTP-Related Configuration Files (Log on with user ID omc)
1. In the FTP port configuration file applied by OMC-B, the default port No. 21
should be modified with a value equal to or larger than 1,024:
$cd ums-svr\tools\ftpserver\conf
$more uep-psl-ftpserver-port.conf
## Ftp server port number
FtpServer.server.config.port=21
2. View the actual port mapping information of the system (Log on with user
ID root):

3. Modify the port No. in the uep-psl-ftpserver-port.conf file with the value
generated after the above-mentioned FTP mapping. In this example, the
port No. is 21111. After modification, the content of the file is as follows:
$more uep-psl-ftpserver-port.conf
## Ftp server port number
FtpServer.server.config.port=21111
4. Modify system FTP port No.:
Log on to vi editor with user ID root, to modify the value of listen_port in the
file /etc/vsftpd/vsftpd.conf as 10021. Make sure that the result is consistent with
the following content:
5. In the user ID root, modify the port No. corresponding with FTP (tcp) in
/etc/services as 1111. Make sure that the result is consistent with the
following content:
6.1.3 Modifying the deploy-default.properties File (Log on with User ID omc)
1. Log as with user ID omc to OMCB server:
$cd ums-svr\deploy
2. Open the file deploy-default.properties.

$vi deploy-030womcb.properties
3. Search for the field userdefined-uep-psl-ftpserver.port in the file.
\userdefined-uep-psl-ftpserver.port
Make sure that the value of this field is consistent with that configured at
ftpserver port enabled by OMC-B service, that is, the above-configured 21111.
userdefined-uep-psl-ftpserver.port=21111
If the value of this field is not 21111, then manually modify it.
6.1.4 Starting OMC-B Server (Log on with User ID omc)
Log on with user ID omc, enable OMCB NM application service in the bin
directory. It displays that FTP service can be normally started. Enter normal
starting process as follows:
When the following prompt appears, it indicates that the server has been
successfully started:
6.2 Configuring SDR Physical Data on OMCB
Note:
Please perform configuration operations in the order as described in this
chapter. Otherwise, the configuration operations may fail.

[Objective]
Configure SDR physical data as planned.
[Preliminary Setup]
1. Know about SDR name, site ID, and site capacity.
2. Know about physical transmission type (E1/T1 or Ethernet).
3. Know about the corresponding interface location and module No. of each
SDR site in iBSC.
4. Know about the IP address of each SDR base station, IP address of the
iBSC interface corresponding to each base station, and the virtual IP
address of iBSC;
5. Know about the planned IP address of each site, and the frequency band
of each RRU;
6.2.1 Creating an SDR Management NE
1. Open Configuration Management.
Log on from Client to iSMG NM software and enter Configuration Management,

as shown in Figure 6.2 -40.

Figure 6.2-40 Entering Configuration Management
2. Create a GERAN subnet
a) In the configuration resource tree, select an OMC node, and right click
[CreateGERAN Subnet], as shown in Figure 6.2 -41.
Figure 6.2-41 Creating a GERAN Subnet (1)
b) In the pop-up [Create GERAN Subnet] interface, type User label

and Subnetwork ID, and click OK to complete the creation, as

Figure 6.2-42 Creating a GERAN Subnet (2)
c) In the configuration resource tree, select the created GERAN subnet

node, and right click [CreateBase Station], as shown in Figure 6.2
-43.
Figure 6.2-43 Creating a Base Station Management NE
d) Type configuration data in the following pop-up dialog box according

to the actual planning, as shown in Figure 6.2 -44.

Figure 6.2-44 Configuring Basic Parameters of a Base Station Management NE
The management NE ID should be consistent with the GSM site No. of a base
station;
In the field of IP Address of Management NE, type the IP address of base

station used for OMC-B communication;
Select ZXSDR BS8800 GU360 as Management NE Type.
Note:
Management NE ID and IP Address of Management NE are key data for
the interconnection between SDR BTS and OMCB. A link can be established
with the base station after both of them have been set.

6.2.2 Applying Mutex Right over Management NE
1. Right click Base Station Management NE, and select Apply Mutex
Right, as shown in Figure 6.2 -45:
Figure 6.2-45 Applying Mutex Right
2. Click Yes in the pop-up prompt box, as shown in Figure 6.2 -46.
Figure 6.2-46 Prompt for Applying Mutex Right
3. After successful application for mutex right, the node in the NM interface
will be marked with a green lock, as shown in Figure 6.2 -47.

Figure 6.2-47 Obtaining Mutex Right
6.2.3 Creating Base Station Configuration Set
Note: If SDR physical, transmission, wireless configurations have been

completed with LMT, the procedures mentioned from 6.2.3 to 6.2.7 can be
omitted. After the link is established between foreground and background, it
can be directly transconfigured from foreground.
Right click [Base Station Management NE Create Base Station

Configuration Set]. In this tab, type user ID and keep default values for the
other items, as shown in Figure 6.2 -48.
Figure 6.2-48 Creating Base Station Configuration Set
6.2.4 Physical Configuration
Note:
Transmission configuration for E1/T1 access and FE access is different. In
each procedure of this section, it will be clarified that whether it is configured
only in E1/T1 access, or FE access, or in both cases. Please pay attention
while reading.
1. Create base station ground resource management.

a) Click [Base Station Configuration Set Create Base Station

Ground Resource Management], as shown in Figure 6.2 -49.
Figure 6.2-49 Creating Base Station Ground Resource Management
Base station ID: Fill in as planned;
Transmission medium: Input FE or E1 according to actual condition;
NTP Server IP: Fill in the IP address of NTP Server. If there is no specific NTP
Server, fill in the IP address of OMCB Server, or 127.0.0.1;
Transmission type: The default value is Full IP;
Daylight saving time: Select according to the actual condition;
Clock synchronization mode: Keep the default GPS frequency synchronization;

Wireless system: UMTS, GSM, and UMTS/GSM, which respectively support

only WCDMA, only GSM and UMTS/GSM dual-mode;
GSM site No.: Fill in as planned;
2. Configuring BS8800 physical rack
From the bottom up, BS8800 rack includes B8200 rack (Shelf 1), FCE layer
(Shelf 2), Fan layer (Shelf 3), PDM layer (Shelf 4), RRU layer (Shelf 5).
a) Creating boards on B8200 rack
Select [Base Station Configuration Set Base Station Ground

Resource Management Rack Configuration Rack 1]. Double
click the main rack of BS8800, and the rack diagram pops up.
CC board at Slot 1 of B8200 and PDM board at PDM layer are added
by default. Configure boards at corresponding slots according to
actual physical configuration. Here is an example of PM board at Slot
14, Shelf 1 as shown in Figure 6.2 -50:
Figure 6.2-50 Creating a BBU on OMCB
Right click at Slot 14, the above dialog box pop up. Select PM board
and click Add. Then click OK to finish the addition. Note: GSM
baseband processing board type should be consistent with physical

configuration, which means a UBPG board should be adopted. Figure

6.2 -51 shows the BBU panel after configuration.
Note: Slot 5 can be used for SE extension board for alarm monitoring,
therefore during commissioning, it is suggested to configure UBPG at
Slot 8, then Slot 7 and Slot 6, but better not at Slot 5.
Figure 6.2-51 B8200 Rack Diagram on OMCB
b) Creating boards on FCE layer
Select [Base Station Configuration Set Base Station Ground

Resource Management Rack Configuration Rack 1]. Double
click the main rack of BS8800, and the rack diagram pops up.
Create FCE board as shown in the following figure:
Figure 6.2-52 FCE Layer Diagram on OMCB
c) Creating boards on RRU layer
Select [Base Station Configuration SetBase Station Equipment

Resource Management Rack Configuration Rack 1]. Double click
the main rack of BS8800, and the rack diagram pops up.
Boards on fan layer and PDM layer are not required to be configured.
Configure RSU type on RRU layer according to the following table.
Table 6.2-1 Parameters Related to RU Type
RU Type Remote Board Type on BS8800/BS8900 Board Type
Rack Name Remote Rack
RU60 ZXSDR DTR ( -x), x=B,C,D,E DRSU (-x ), x=B,C,D,E (internal
R8860 (internal combiner) combiner)
RU02 ZXSDR TTR ( -x) ,x=B,C,D,E GRSU ( -x), x=B,C,D,E (without
with R8802 (without combiner) combiner)
Antenna
TTR20 ( -x), GRSU20 ( -x) ,x=B,C,D,E
x=B,C,D,E (internal (internal combiner)
combiner)
RU02 ZXSDR TTR20 ( -x), GRSU20 ( -x) ,x=B,C,D,E
without R8802E x=B,C,D,E (without (without combiner)
Antenna combiner)
In the above table, the value of x can be NULL, B, C, D, E, which are

corresponding respectively to 2.1G, 850M, 900M, 1800M, and 1900M.
Note: In the bands GSM900M and EGSM900M, the boards can be

different, but the configurations at the background are the same.
Create 3 GRSU-D boards on RRU layer as shown in the following

figure:
Figure 6.2-53 RRU Layer Diagram on OMCB

Thus the rack of BS8800 has been created as shown in the following
figure:
Figure 6.2-54 BS8800 Rack Diagram on OMCB
3. Antenna configuration
Select [Base Station Configuration Set Base Station Ground Resource

Management Antenna Configuration Create Antenna
Configuration] to add antennas for RRU. Two feeders come out of each
RRU. Select ANT as the antenna type, as shown in Figure 6.2 -55:

Figure 6.2-55 Creating Antenna on OMCB
Rack No.: It refers to the Rack No. of BS8800.
Shelf No.: It refers to the shelf connected with RRU feeder, here Shelf 6 is
selected.
Slot No.: It refers to the feeder location. There are at most 12 feeders in
the rack, which are numbered with 1-12 from left to right.
4. Rack topology configuration

Management Rack Configuration Rack Topology Configuration] to
enter the interface as shown in Figure 6.2 -56:

Figure 6.2-56 Creating SDR Rack Topology on OMCB
Port ID: It refers to the port No. of FS board connected with RRU (which is
numbered with 5, 4, 3, 2, 1 from left to right).
Child Slot No.: It refers to RRU shelf, numbered from 1;
Child Port ID: It refers to the port through which a child rack is connected with a
higher-level one;
RRU Connection Mode: For the RU directly connected with BBU, if there is no
other cascade RU, select Star; if there is other cascade RU, select Chain. For
the RU connected with BBU indirectly, this item is invalid.

6.2.5 Transmission Configuration
Note:
During the creation of base station ground resource, if Transmission Medium
is FE, it is unnecessary to configure the following Procedures 2, 3 and 4; if
Transmission Medium is E1, it is unnecessary to configure the following
Procedure 1. It will be clarified whether the parameters are configured in the
case of FE or E1/T1.
1. Ethernet configuration
It is configured in the case of FE only.
Click [Base Station Configuration Set Base Station Ground Resource

Management IUB Transmission Configuration (Full IP) Global Port
Management Create Ethernet] to enter the interface as shown in
Figure 6.2 -57:
Figure 6.2-57 Ethernet Parameter Configuration

Rack No.:
Shelf No.:
Slot No.: It refers to the location of CC board on B8200 rack

(unchangeable);
Working Mode: The default value is adaptive;
Link Object: Select IPbone for a directly connected site, or BTS for a
cascaded site;
Bandwidth: Select 10,000k in the case of FE; select 1,984k in the case of
E1.
2. E1/T1 connection configuration
It is configured in the case of E1/T1 only.
Right click [Base Station Configuration Set Base Station Equipment

Resource Management IUB Transmission Configuration (Full IP)
Physical Layer Management]. Select [Create E1/T1 Line Configuration]
from the pop-up menu. Configure E1/T1 connection in the pop-up window
[E1/T1 Line Configuration], as shown in Figure 6.2 -58.
Figure 6.2-58 E1/T1 Connection Configuration

Link Type: Select BSC if an SDR base station is connected to BSC in

star mode; select Base Station if an SDR base station is connected
with an upper-level SDR base station in chain mode.
E1/T1 Link ID: 0-7 represents 1 st-8th pair of E1/T1 of an SA board; the
default value is 0, which refers to the first pair of E1/T1; keep the default
values for other parameters.
3. High-Level Data Link Control (HDLC) configuration
Right click [Base Station Configuration Set Base Station Ground

Physical Layer Management]. Select [Create HDLC] from the pop-up
menu. Configure HDLC in the pop-up window [HDLC], as shown in Figure
6.2 -59.
Figure 6.2-59 HDLC Configuration
Configure the timeslot used by an SDR base station as planned in

Timeslot Mapping Diagram.

4. Point-to-Point Protocol (PPP) configuration
Right click [Base Station Configuration Set Base Station Ground

Global Port Management]. Select [Create PPP Configuration] from the
pop-up menu. Configure related parameters in the pop-up window [PPP
Configuration], as shown in Figure 6.2 -60.
Figure 6.2-60 PPP Configuration
Link Type: Select HDLC;
Bearer Protocol: If only one E1 cable is adopted at Abis interface, select

PPP; if multiple E1 cables are adopted, select ML-PPP;
Base Station IP: Fill in the planned IP address of SDR base station.
Quality Protocol: Select Not Support.
No. 0: Modify the corresponding HDLC ID as the one set in the

previous HDLC configuration. When adopting PPP, only one link is
configured; when adopting ML-PPP, multiple links can be configured.

5. Qos bandwidth configuration
It must be configured in the cases of E1/T1 and FE.

Management Create QOS Bandwidth Configuration], as shown in
Figure 6.2 -61.
Figure 6.2-61 Qos Bandwidth Configuration
Rack No., Shelf No., and Slot No. are used to locate a CC board;
Port ID: If 0 is selected, it indicates the port accessed in FE mode;
Traffic Quality Priority: Keep the default value 0;
Bandwidth of QOS: Fill in according to actual transmission bandwidth.
6. Global port configuration

Management Create Global Port Configuration], as shown in Figure
6.2 -62:
Figure 6.2-62 Global Port Configuration
Port Type: IP Over Ethernet / IP Over PPP. If the transmission medium is

FE, select IP Over Ethernet. If the transmission medium is E1, select IP
Over PPP.
Rack No., Shelf No., and Slot No. are located to the CC board configured
with data.
Port ID.: Keep the default value 0.
VLAN ID: Keep the default 65535 if no VLAN is used.
7. IP parameter configuration

Management IUB Transmission Configuration (Full IP) IP and Route
Management IP Parameter Configuration], as shown in Figure 6.2 -63:

Figure 6.2-63 IP Parameter Configuration
IP Address: In E1 transmission, it is not required to set, but will be

automatically filled in with SDR IP address after the link between
foreground and background is established. In FE transmission, it should be
filled in with the BTS IP address planned actually.
Subnetwork Mask: In E1 transmission, it is not required to set, but will be

automatically filled in with 255.0.0.0 after the link between foreground and
background is established. In FE transmission, it should be filled in with
the value planned actually, generally 255.255.255.0 or 255.255.255.252.
Gateway Address: In E1 transmission, it is not required to set, but will be

automatically filled in with corresponding EUIP port address after the link
between foreground and background is established. In FE transmission, it
should be set as the corresponding IPBB port address of SDR (Note that it
is not the IPBB address connected to OMCB).
Bandwidth: Set as 1,984kb in E1 transmission; set as 10,000kb in FE

transmission.
Radio Mode: GSM;
Keep the default values for other items.

8. Static route configuration
If SDR and iBSC (RPU virtual address, i.e. IPAbis address) are not in the
same network segment, a static route must be configured; otherwise there
is no need to configure any static route.
9. SCTP configuration

Management IUB Transmission Configuration (Full IP) Transmission
Layer Management Create SCTP Configuration], as shown in Figure
6.2 -64.
Figure 6.2-64 SCTP Configuration
Radio Mode: Select GSM.

No.0 Local IP Address: Fill in with the IP address of an SDR site. Select
Invalid for other local addresses.
Local Port No.: Keep consistent with Site No.
Remote Port No.: It is 0x3900 (14,592 in decimal numeral) +CMP module

No. (where the BTS locates). In this case, the BTS is in Module No.3,
therefore, the remote port No. is 14,592+3=14,595.
Remote IP Address: Fill in IPAbis address (RPU virtual address).
Keep default values for other items.
10. OMC-B link

Management IUB Transmission Configuration (Full IP) Transmission
Layer Management Create OMC-B Link], as shown in Figure 6.2
-65:
Figure 6.2-65 OMCB Link Configuration

Link ID:
Base Station OMC IP Address: Keep the IP address of the BTS by default.
Base Station OMC Gateway: Fill in with IPAbis address (RPU virtual address).
IP Tos
Keep the default values for other items.
6.2.6 Clock and Monitoring Configuration
1. Clock source priority configuration

Management Clock Source Priority Configuration], as shown in Figure
6.2 -66:
Figure 6.2-66 Clock Source Priority Configuration
External Clock Source ID: Only internal-GPS and line clock-this board are
supported at present.
2. Environment monitoring configuration and dry contact
Configure environment monitoring and dry contact according to actual

condition, as shown in Figure 6.2 -67 and Figure 6.2 -68. If there is no
connection, keep the default value.

Figure 6.2-67 Creating Environment Monitoring on OMCB
Figure 6.2-68 Creating Dry Contact on OMCB
6.2.7 Radio Configuration
1. Central frequency configuration
Select [Base Station Configuration Set Base Station Radio Resource

Management Create Central Transmitting Frequency], as shown in
Figure 6.2 -69.

This frequency is the central frequency of a downlink frequency band. The

stable working bandwidth for RU60/RU80 is 10M, the central frequency is
used to set RU working bandwidth range. The actual carrier frequency
should be within 5M of the central frequency. RU02/RU02E is not limited
by the 10M bandwidth, thus it is not required to set central frequency.
Figure 6.2-69 Configuring Central Frequency on OMCB
2. Configuring sector parameters

Management Create GSM Sector Parameter Configuration], as

Figure 6.2-70 Configuring GSM Sector on OMCB
A sector No. corresponds to a physical cell No. For GPS synchronous

frame header offset, keep the default value 1.
3. GSM RU parameter configuration

Management Create RU Parameter Configuration], as shown in
Figure 6.2 -71 and Figure 6.2 -72.This tab is used to configure radio
parameters for RU at Slot 1, Shelf 5.

Figure 6.2-71 Configuring GSM RU on OMCB (1)
Figure 6.2-72 Configuring GSM RU on OMCB (2)

RU Type: Select according to the model on the RRU name plate;
RU Type BS8800/BS8900 Board Remote Rack Board Type on Remote

Type Name Rack
RU60 DRSU (-x ), x=B,C,D,E ZXSDR R8860 DTR ( -x), x=B,C,D,E

(internal combiner) (internal combiner)
RU02 with GRSU ( -x), x=B,C,D,E ZXSDR TTR ( -x) ,x=B,C,D,E

Antenna R8802
(without combiner) (without combiner)
GRSU20 ( -x) ,x=B,C,D,E ZXSDR TTR20 ( -x), x=B,C,D,E

(internal combiner) R8802 (internal combiner)
RU02 without GRSU20 ( -x) ,x=B,C,D,E ZXSDR TTR20 ( -x), x=B,C,D,E

Antenna R8802E
(without combiner) (without combiner)
Static Power Level: Set as per the requirement of network optimization;
Carrier Power Configuration Parameter: Configure according to the

quantity of carriers. Pay attention that when using RU60, the sum of
transmission power of all the carriers cannot exceed 60W.
RF Extension Interface: If a cell has only one RU, select Disable RF

extension interface. If the cell has multiple RU, select Enable RF
extension interface;
Related RF Rack No.: If RF extension is enabled, select the rack No. of

related RU; if RF extension is disabled, this item is invalid.
Related RF Shelf No.: If RF extension is enabled, select the shelf No. of

Related RF Slot No.: If RF extension is enabled, select the slot No. of

Support Intelligence Power Off: For RU02, select according to on-site

condition; for RU60/RU80, select No, which means this function is not
available.

Note:
Description of the maximum configuration: Each site of an SDR base station
can be configured with up to 24 cells, each cell with up to 36 TRX, and each
site with up to 60 TRX. A BP board can process up to 12 TRX; a BBU can be
configured with up to 5 BP boards.
4. GSM carrier configuration

Management Create GSM Carrier Parameter Configuration], as
shown in Figure 6.2 -73. Configure carriers for each sector.
Figure 6.2-73 Configuring GSM Carrier Wave on OMCB
Sector No.: Select the cell where this carrier is located;
Logical Carrier Frequency No.: It refers to the carrier No. in the cell;
Use IRC or Not: Set as required. The default value is No IRC;
Channels Mode: Select according to on-site situation. The default value is

Single Channel;
Frequency Band: select the actually configured frequency band (900 M in

this case).

Sub-Frequency Band: Set according to on-site situation; if there is no sub-

frequency band, set this item as Invalid.
6.3 Configuration in Batch of SDR Physical Data

Currently, tools are available for the configuration in batch of SDR physical
data, which saves your effort to configure on LMT or OMCB. Fill in an Excel
template with the configuration data of each SDR site, convert the template into
xml file with the tool, and download data through LMT or OMCB.
Attatched please refer to a sample for SDR configuration template:
SDR Configuration
Template.xls
The tool for configuration in batch and its user manual will be provided
otherwise.
6.4 Version Loading and Querying

SDR version can be processed through LMT locally, or through OMCB
remotely. If the SDR version has been loaded and activated through LMT, this
chapter can be omitted.
After the link between SDR and OMCB in iBSC has been established, the SDR
version can be downloaded from OMCB to activate. To operate on the version
on OMCB, click [View BTS Software Version Management].
1. Creating SDR version packet
Click the configuration resource tree on the left side of the View manu, select
[BTS Software Version Management SDR Software Version Management
SDR Version Packet Management], right click [Create BTS Version Packet]
as shown in the following figures.

Figure 6.4-74 Creating Version Packet
Figure 6.4-75 Selecting Version Packet
a) Open the Version Packet, a window pops up as shown in Figure 6.4

-76. Fill in User ID.

Figure 6.4-76 Selecting Version Packet
Click OK, with the version packet, all the version files will be saved into the
background NM. In the manu SDR Version Packet Management, double
click the nwly-created version packet, and an operation interface pops up as
shown in Figure 6.4 -77
Figure 6.4-77 Operation Interface for Version Packet
2. Version download

a) As shown in the operation interface in Figure 6.4 -78, click the download button ,a
dialog box for confirmation pops up. Click OK, a dialog box to select BTS pops up as
Figure 6.4-78 Clicking Version Download Button
Figure 6.4-79 Downloading Version Packet

b) In Figure 6.4 -79, check the box of the BTS which needs to download version, right click
to select Version Packet Download.
3. Version Activation
a) In Figure 6.4 -80, click activation button , a dialog box for confirmation pops up. Click
OK, a dialog box to select BTS pops up as shown in Figure 6.4 -81.
Figure 6.4-80 Clicking Version Packet Activation Button
Figure 6.4-81 Activating Version Packet

b) In Figure 6.4 -81, check the box of the BTS which needs to download version, right click
to select Version Packet Activation.
4. Version Query
a) In the configuration resource tree on the left, double click [BTS Software Version
Management SDR Software Version Management], click the Version Query
button pops up as shown in Figure 6.4 -82.
Figure 6.4-82 Clicking Version Packet Query Button
Figure 6.4-83 Querying Version Packet

b) In Figure 6.4 -83, check the box of the BTS which needs to query version, click OK to
complete the query.

7 LMT Installation and Data Configuration
Abstract
The chapter introduces LMT installation, as well as data configuration and
version upgrade for SDR by using LMT. Besides, it also describes the
equipment check after power-on.
7.1 Introduction of Debugging Software LMT

The software packet of SDR contains two files: one is the foreground software -
software specification package for SDR running, the other is the debugging
software LMT as shown in Figure 7.1 -84.
Figure 7.1-84 External Interface of ZXSDR R8860
7.1.1 LMT Content
1. You can see the following LMT software contents after unzipping the file
BLMT_v4.00.101a.rar:
EOMS The special software version of EOMS and EFMS. You can
load and run it with LoadTool, or test and activate it on BTS.
EOMS_EFMS The copy version of O&M and fault management.
JRE Java operating environment installation file.
LMTSetup.exe Executable file for DMS and PMS installation programs.
readme.txt The readme file for installation program.

7.1.2 LMT Installation
Load JRE when running LMT. If JRE is not installed on the PC for
commissioning, JRE under LMT directory should be installed. The path
is \.....\BLMT_v4.00.101b2\JRE\jre-6u2-windows-i586-p.exe. (If a different LMT
version and JRE have been installed on the commissioning PC, re-installation
is not required.)
1. Install JRE
a) Enter the JRE program directory \BLMT_v4.00.101b2\JRE\, and

double-click jre-6u2-windows-i586-p.exe. The installation interface
pops up as shown in the following figure.
Figure 7.1-85 JRE Installation Welcome Interface
b) Click Accept (A) to start installation. The progress bar is displayed to

show the installation status. See the Figure 7.1 -86.

Figure 7.1-86 JRE Installation Progress
c) After the completion of Java installation, an interface as shown in

Figure 7.1 -87 pops up. Click Finish (F) to end JRE installation.
Figure 7.1-87 JRE Installation Completes

2. Set the environment variable
d) Right-click My Computer, and select Attribute Advance

Environment Variable Path Edit. Add ; after the value of
path environment variable, and then add the installation path of Jar.
The default installation path of Jar is C:\Program
Files\Java\jre1.6.0_02\bin. See Figure 7.1 -88.
Figure 7.1-88 Setting Environment Variable
7.1.3 Connection between LMT and SDR
To establish the connection between commissioning PC and SDR, you should

configure the commissioning PC with an IP address in the same network
segment of CC board.
IP calculation for BBU board
Each board on BBU has a fixed internal IP address, which is related to its slot.
The format is:
192.(Environment No.).(Slot No.).16
For the Slot No. of each board, see the red mark in Figure 3.1 -6. The
Environment No. is used to identify a specific SDR in the same network. The
default Environment No. is 254 which can be edited by using the following
command. (Note: The address in 192 field is the internal address at ETH1
interface. In actual networking, it rarely happens that multiple SDR ETH1
interfaces are connected with each other, thus, the Environment No. is not
required to be modified.)
Telnet to CC board, and enter BspSetEnvId New Environment No. to modify

the Environment No.
CC->BspSetEnvId 210
value = 0 =0x0
CC->
When the modification is complete, press Ctrl + x or enter Reboot command

to reset CC board. Then, log on with the new Environment No.
What if I forget the internal IP address of CC board (i.e. the environment

No.)?
1. Connect the PC for commissioning directly with the ETH1 interface of

active CC board;
2. The IP address of the PC for commissioning is set as 192.1.1.1 (It can be

set randomly, but should be different from SDR board address). The mask
is set as 255.0.0.0.
3. In the cmd window of the PC for commissioning, execute arp a

command, the IP addresses of each SDR board will be displayed.
IP configuration of the commissioning PC
When commissioning, the commissioning PC is connected to ETH1 interface of

CC board in SDR through the network cable. To establish the connection
between commissioning PC and SDR, you should configure the commissioning
PC with an IP address in the same network segment with CC board, and this
IP address should not be the same as the one in SDR. To access to all boards
in SDR conveniently, the subnet mask should be 255. 255. 0. 0, the gateway
can be optional. See Figure 7.1 -89.

Figure 7.1-89 Configuring IP Address of Commissioning PC
Logon to SDR through commissioning PC
1. Connect the network port of commissioning PC with the ETH1 interface of

the active CC board
CC board can only be inserted at Slots 1 and 2 of BBU. If there is only one
CC board, it must be the active one. You can connect commissioning PC
with ETH1 interface of CC board through the network cable. If CC boards
are inserted at both Slot 1 and Slot 2, power on and observe MS indicator.
The board, whose MS indicator is on, is the active CC board, which should
be connected to commissioning PC.
If LMT is used to configure SDR data, it is recommended to pull out the

standby CC board before configuration. Insert the standby CC board after
the active CC board is configured completely and runs normally.
2. Start the logon interface

Try to ping the IP address of the active CC board of BTS on commissioning

PC. After the connection between commissioning PC and SDR is
established, double click \.....\BLMT_v4.00.101b2\EOMS_EFMS\EOMS.jar
to start LMT. See the interface as shown in the following figure. In most
cases, log on with user ID root (without password by default) or admin (with
password nodelmt by default).
Figure 7.1-90 LMT Logon Interface
3. Create logon site information
Click the Site Management on the logon interface. The dialog box is
displayed as shown in Figure 7.1 -91. In the figure, BTS Name is
recommended to be a plain name. For example, a CC board at Slot 1 of
SDR with environment No. 100 can be named as CC100_1; BTS IP
indicates the IP address of CC board that is connected to commissioning
PC through the network cable.

Figure 7.1-91 Configuring the IP Address of Commissioning PC
4. Logon to BTS
Create a site, and select a BTS. Select Log On to BTS (Online

Configuration) as the logon mode, and click Logon to configure SDR data
online.
If it cannot be accessed to SDR through LMT, check whether

commissioning PC can ping the IP address of CC board, and then confirm
whether the IP address in the ump file is consistent with that of CC board
to be connected; if the CC board is being reset, LMT cannot access to it
until it is normal.
5. Prompt in the logon process
In the logon process, the background should communicate with BTS to

obtain the dynamic and alarm information as shown in Figure 7.1 -92. This
process will take about half a minute. Then, the BTS configuration
interface is displayed, as shown in Figure 7.1 -93.

Figure 7.1-92 LMT Online Logon Process
Figure 7.1-93 LMT Configuration Interface
If it is unavailable to log on to SDR, select Log On to BTS (Offline

Configuration) in Figure 7.1 -90 to configure the data offline.
7.1.4 Offline Configuration
The online configuration is commonly used to configure the BS8800 foreground

data directly. The data configured in this mode takes effect immediately.

The offline configuration is to modify the configuration on commissioning PC.

The configuration result is saved as an XML file under a specified directory.
The offline configuration does not need to connect to the foreground BS8800,
thus the operation of BS8800 will not be affected.
A local configuration file should be specified for the offline configuration as

shown in Figure 7.1 -94. The follow-up configurations are performed based on
this configuration file. Backup the configured data to commissioning PC, and
import the data into SDR through the online mode of OMCB or LMT.
Figure 7.1-94 LMT Offline Logon Interface
7.1.5 Configuration Export and Import
The Configuration Export is to export the SDR foreground data in XML format
to a directory of LMT Cient. By way of exporting the configured data in online or
offline mode, the data can be backed up, or imported to other SDR base
station of the same type, single data can be modified for quick data
configuration. (Note: The tool SdrQuickConf can be used to configure SDR
physical data in batch.)
Configuration data export
To export data, select Export Configuration Data in the drop-down list of

System as shown in Figure 7.1 -95. Then, set the path for the exported file.

Figure 7.1-95 Configuration Data Export
Configuration data import
To import data, select Log Off in the drop-down list of System. Then, select
Log On to import the existing configuration data.
Note:
BS8800 will restart after the entire table configuration.
7.1.6 LMT Password Modification
In default mode, log on to LMT with user ID root (whose password is NULL).
To strengthen the LMT application security, the password for user ID root
should be modified.
As shown in Figure 7.1 -96, select Change Password in the drop-down list of
System, a dialog box pops up as shown in Figure 7.1 -97. Enter the original
password and new password, click OK to put the new password into effect.

Figure 7.1-96 Selecting Change Password
Figure 7.1-97 Changing Pasword
7.2 Configuration of SDR Base Station on LMT

ZXSDR is a base station with internal ALL-IP structure. It only supports IP
access at Abis interface, but the physical bearer can be FE or E1/T1.
The configuration procedures of base station on LMT are shown in the

following table. There are differences in the configuration of transmission
resource between E1/T1 access and FE access, which are marked in bright
blue and yellow respectively in the table. The unmarked parts are required to
be configured both in E1/T1 access and FE access.
Table 7.2-5 LMT Configures SDR
Data Connection
Step Step Configuration
Category Parameter with BSC
Step BTS Step Basic attribute
GSM site ID
1 Configuratio 1.1 configuration of BTS
n Step Configurations of rack None
1.2 and board

Data Connection
Step Clock reference source
None
1.3 configuration
Step Environment monitoring
None
2.1 configuration
Step PA controller
None
Ground 2.2 configuration
Step Resource Step
Serial port configuration None
2 Configuratio 2.3
n Step Topology structure
None
2.4 configuration
Step
Dry contact configuration None
2.5
Configuration of FE
Step parameters (for IP
None
3.1 transmission at Abis
interface)
Configuration of E1/T1
Step connection (for E1/T1
None
interface)
Configuration of HDLC
Step channel parameters (for
None
Transmissi 3.3 E1/T1 transmission at Abis
Step on Resource interface)
3 Configuratio Configuration of PPP
The IP address
n Step parameters (for E1/T1
used by BTS to
access BSC
interface)
Step Configuration of global
None
3.5 port parameters
Step Configuration of IP
None
3.6 parameters
Step Configuration of SCTP Remote IP address
3.7 parameters and remote port No.
Step Configuration of 0MC-B
3.8 parameters
Step Radio Step Configuration of RF unit Cell frequency
4 Resource 4.1 central frequency configuration range
Configuratio Step Configuration of GSM None
n 4.2 sectors

Data Connection
Step Configuration of GSM
None
4.3 carriers
Step
Configuration of GSM RU None
4.4
Version
Step Step
Configuratio Version Configuration None
5 5.1
n
7.2.1 Basic Attribute Configuration
Description before configuration:
Currently, the SDR data configured by default before delivery (on CC

board) is for the SDR in UMTS system, which should be deleted and
replaced with GSM configuration data during onsite commissioning.
Due to the interrelation between data, the deletion should start from
the data at the lowest level. Otherwise, the data at upper level may
not be deleted.
Configuration Steps:
1. Set basic attribute
a) Open Configure Basic Attribute menu
Right-click BTS in the configuration interface as shown in Figure 7.2

-98. Select Configure Basic Attribute.

Figure 7.2-98 Configure Basic Attribute
b) Set basic parameter
Figure 7.2-99 Basic Parameters of Basic Attribute
NodeB ID: indicates the site ID of the BTS, which should be consistent
with the GSM site ID.
Set other parameters as shown in Figure 7.2 -100 and Figure 7.2
-101.

Figure 7.2-100 Basic Parameters 1 of Basic Attribute
Figure 7.2-101 Basic Parameters 2 of Basic Attribute
SNTP Server Address: It indicates the time server used by BTS. Fill in with the
actual IP address.

If there is no time server, BTS will start timing from 2000-1-1 0:0:0
automatically. The BTS time can be set manually on LMT. If there is no
independent time server, fill in the IP address of OMCB.
Transmission Type: The physical transmission type of Abis interface

determines the encapsulation of data link layer. For Ethernet twisted pair
transmission, the data link layer is Ethernet encapsulation; for E1/T1
transmission, the data link layer is PPP encapsulation. However, ALL-IP
transmission is used in the network layer, regardless of the physical
transmission type.
Power Operation Mode: it is used to set the working modes of two PM (power
modules), such as the active/standby mode or load-sharing mode. The
active/standby mode indicates that only one PM is active at one time, the other
module is in standby mode. When the active PM is faulty, the standby module
will take over the job. Then, the original standby module is switched to the
active module. The load-sharing mode indicates that both PM are working
simultaneously. When one module is faulty, the other will take over all the jobs
and ensure normal operation of the system. B8200 can operate normally with
only one PM. It can support a maximum of two PM.
FS Operation Mode: A maximum of two FS boards can be configured on BBU.

The two FS boards can operate in active/standby mode or load-sharing mode,
which is set based on the actual configuration requirement.
Radio System: It is used to set the radio system of the BTS, including GSM,
WCDMA, or WCDMA/GSM. The selection is based on the type of RF unit
which is connected to FS board of B8200. When all RF units are used for GSM
system, select GSM; when all RF units are used for WCDMA system, select
WCDMA; when some RF units are used for GSM and the others are for
WCDMA, select WCDMA/GSM.
GSM Site ID: It indicates the site identification of GSM allocated by BSC. It is
the planning data which should be consistent with the site ID used to configure
the site on OMCR. This site ID also serves as SCTP port No. that is used when
SCTP connection is established between B8200 and BSC. BBU obtains the
radio configuration parameters through OMCR. If the site ID is configured
incorrectly, BTS cannot obtain the correct radio parameters or access.

Transmission Medium: it indicates the transmission medium used by Abis

interface. You can select E1, T1, FE, SAT, or Invalid. E1/T1 refers to E1/T1
cable, FE refers to Fast Ethernet, SAT for satellite transmission, and Invalid
indicates that the field is invalid.
Time Zone: Set the parameter based on the time zone that BTS locates in. It is
China GMT+8:00 by default.
Clock Synchronization Period: It indicates how often (in hour) BTS performs
the time synchronization with the preset time server of SNTP Server. Use the
default value.
Support Power off Control: When the power is faulty, NodeB will disconnect the
external boards automatically (including FS UBPG) to save the power in the
storage battery. This option is designed for users to select whether to allow the
strategy. Currently, the function is not supported, which should not be checked
here.
2. Set clock reference source
In the maintenance navigation tree interface, right-click Configuration

Management -> NodeB -> Set Clock Reference Source. The interface Set
Clock Reference Source pops up. In the interface, modify the clock reference
source extracted by BTS. Generally, line clock is adopted in site transmission
as shown in the following figure. If there are multiple clock sources, set the
second clock, the third clock, etc. in the same way.

Figure 7.2-102 Set Clock Reference Source
3. Set BTS time
In the navigation tree maintenance interface, right-click Configuration

Management -> NodeB -> BTS Time Property. Then, you can query the BTS
time. To modify BTS time, uncheck the option Query BTS Time to make the
date and time editable. Click the date to be modified, select the current date,
and double-click to confirm. The time can be edited directly. When the link
between the foreground and the background is established, you can modify
SDR time through OMCB.
7.2.2 Physical Configuration
In LMT, the BS8800 rack from the bottom up include BBU (B8200 rack, Shelf
1), FCE layer (Shelf 2), Fan layer (Shelf 3), PDM layer (Shelf 4) and RRU layer
(Shelf 5).
1. Configure the BBU of BS8800 rack
a) Add board
Double-click Main Rack 1. The BBU configuration interface pops up.

Add the board based on the actual configuration (it is recommended to
insert FS board into Slot 3, because FS board can not be inserted into
Slot 4 in previous versions). To add a board, right-click on the
corresponding slots and select Add Board, and then select the board

type on the pop-up interface. See the following example of adding a

UBPG board in Slot 7.
Figure 7.2-103 Configuring the UBPG Board of the BBU on BS8800 Rack
Note: both Slots 1 and 2 on the Main Rack 1 are configured with a CC
board that cannot be deleted on LMT (but can be deleted on OMCB). If
one of the slots has no CC board, BTS can still run normally.
b) Check board status
After adding the board, to know whether there is an alarm on the board,
right-click on the board and select Board Status Illustration. A prompt
of the board is displayed as follows.

Figure 7.2-104 Board Indicator Prompt
2. Configure FCE rack
Add FCE for the board as shown in the following figure:
Figure 7.2-105 Configuring FCE Board on the FCE Layer
3. Configure RRU layer
a) Add rack
Right-click the BTS, and select Add Rack as shown in Figure 7.2 -106.
The type of RSU is selected according to the following table; antenna is
configured with ANT be default.
RU Type Remote Rack Remote Rack Board Type BS8800/BS8900 Board
Name Type
RU60 ZXSDR R8860 DTR ( -x), x=B,C,D,E (internal DRSU (-x), x=B,C,D,E
combiner) (internal combiner)
RU02 with ZXSDR R8802 TTR ( -x) ,x=B,C,D,E (without GRSU ( -x), x=B,C,D,E
antenna combiner) (without combiner)
TTR20 ( -x), x=B,C,D,E GRSU20 ( -x) ,x=B,C,D,E
(internal combiner) (internal combiner)
RU02 without ZXSDR R8802E TTR20 ( -x), x=B,C,D,E GRSU20 ( -x) ,x=B,C,D,E
antenna (without combiner) (without combiner)

Figure 7.2-106 Add RSU Board on RRU Layer
b) RU configuration result
The configuration result of RU layer is shown in the following figure, in

which RSU is configured as GSM1800 (GRSU20-D).
Figure 7.2-107 RU Rack after Configuration
4. Topology structure Configuration
a) Open the topology configuration interface

When the RU configuration is complete, double-click the Topology

Structure under the directory tree Ground Resource Management.
The topology structure interface is displayed as shown in Figure 7.2
-108. Right-click on the interface and select Add. Then, you can
configure the topology relation between racks.
Figure 7.2-108 Topology Structure Interface
b) Add a topology relation
Configure the connection between BBU and RRU, or between different

RRU as needed. The configuration in the following figure is to connect
Port 0 (LC1) at Slot 1, Shelf 5 (RSU) to Port 5 (TX0/RX0) at Slot 3,
Shelf 1 (FS board).

Figure 7.2-109 Topology Structure Settings
Upper Level/Lower Level: In the star connection, BBU is the upper

level, RU is the lower level; in the chain connection, the RU near BBU
is the upper level, the RU far from BBU is the lower level.
Board Port ID: Each FS board of BBU provides six fiber interfaces to be
connected to RU. The optical interfaces on the front panel of FS board
are numbered with 0, 1, 2, 3, 4, 5 from left to right.
Topology Type: Star indicates that RU is connected to BBU directly,

while Chain indicates multiple cascaded RU.
c) Add more topology relations
By using the above method, add the configuration data of topology for
each pair of BBU and RU or each pair of RUs which are directly
connected. After configuring the rack and topology structure, you
should configure the transmission resources at Abis interface.

7.2.3 Transmission Configuration
Note:
The transmission configuration for E1/T1 access is different from that for FE
access. Note that in each step in this section, it will declare whether it is
configured for E1/T1, FE, or both E1/T1 and FE.
Description before configuration
For E1 access, seven items should be configured: E1/T1 cable, HDLC

parameters, PPP parameters, global port parameters, IP parameters,
SCTP parameters, and OMCB parameters.
For FE access, only five items should be configured: Ethernet

parameters, global port parameters, IP parameters, SCTP
parameters, and OMCB parameters.
If the planned SDR address and the iBSC virtual address are not in
the same network segment, Static Route Parameters should be
configured.
After the connection between SDR and iBSC is established, no

modification is allowed on LMT. Thus when configuring in the local
environment, it is recommended to disconnect the transmission at
Abis interface first, confirm theres no need to modify the data before
re-connecting the transmission.
Configuration procedure
1. E1/T1 cable
It is configured only for E1/T1 access.
In the left window of LMT, select Maintenance Navigation Tree ->

Configuration Management -> Transmission Resources -> Physical
Bearer -> E1/T1 Cable. Then, right-click in the E1/T1 Cable window on the
right, and add a message. See Figure 7.2 -110.

Figure 7.2-110 E1/T1 Connection Management
Board Name: It indicates the board from which SDR accesses E1/T1. For
B8200, although E1/T1 is accessed physically from SA board, SA board
performs no operation over E1/T1. The co-team handling is completed by
CC board, therefore, E1/T1 is accessed logically from CC board. Thus, CC
board is adopted by default, which cannot be edited.
Link ID: It indicates the pair of E1 cables to be used. There are eight pairs
of E1 cables led out from SA board which correspond to Link ID Nos. 0 to 7.
In the figure, the link ID of E1 cable is 0, that is, use the first pair of E1
cables (No.1 and No.2 E1 cables). The link ID configured in this step will be
referenced later in the HDLC channel parameter configuration; it also
identifies the E1 link used in a HDLC channel
Link Type: It indicates the remote equipment type to which E1 link is

connected. Select BSC for GSM network.
Note:
Ensure that you have set the transmission medium as E1 or T1 in Set Basic
Property -> Other Related Parameters. Otherwise, E1/T1 cable can not be
added.
2. Ethernet Parameters
This option is configured only for FE/GE access.
Click Transmission Resources -> IP Transmission -> Ethernet

Parameters, right-click at the blank area on the right, and select Add. The
configuration interface of Ethernet parameters is displayed, as shown in
Figure 7.2 -111.
Figure 7.2-111 Ethernet Parameter Configuration
Parameter description
Board Name: Select the board where the IP port of Abis interface locates.
Select CC for GSM.
Ethernet Port ID: Select 0 from the drop-down list.
Working Mode: It indicates the operation mode at Abis interface, including

duplex or rate. There are six options. Generally, Adaptive is selected by
default.
Connection Object: It indicates the equipment to which Abis interface is

connected directly. You can select IPbone or BTS. When SDR is
connected to BSC directly, select IPbone; when SDR is cascaded to the
upper level BTS, select BTS.
Configured Bandwidth: It indicates the total bandwidth (kbps) at Abis

interface. This parameter sets the upper threshold of the available total

transmission bandwidth at Abis interface of BTS. The value cannot exceed

the physical processing capability of the interface. Because a BTS can be
configured with multiple IP addresses, and it supports the settings of
available bandwidths of different IP addresses. The total bandwidth used by
all IP addresses in one BTS cannot exceed the configured value.
3. HDLC parameters
This option is configured only for E1/T1 access.

Configuration Management -> Transmission Resources -> IP
Transmission -> HDLC Parameters. Then, right-click in the HDLC
Parameters window on the right column to add a message. See Figure
7.2 -112.
Figure 7.2-112 HDLC Parameter Configuration
HDLC ID: It indicates HDLC ID, starting with 0. The number is increased by
1 each time when a record is added. This parameter is set automatically by
the system, and needs no modification. Each E1 should be configured with
one HDLC. The HDLC ID configured in this step will be referenced later in
the PPP parameter configuration.
Bearer Type: Select E1.

Link ID: It indicates the ID of E1 link where HDLC channel locates, that is,
the Link ID configured in E1/T1 cable. If you add Links 0 and 1 in E1/T1
Configuration, there will be two options available: 0, 1.
Timeslot Bitmap: It indicates the ID of E1 timeslot occupied by HDLC

channel. One HDLC channel uses Timeslots 1 - 31 of the E1 by default.
You can select as needed. For E1 transmission, the timeslot range is 1 -
31, and Timeslot 0 is used for synchronization; for T1 transmission, the
timeslot range is 1 - 23, and Timeslot 0 is also used for synchronization.
4. PPP parameters
This option is configured only for E1/T1 access.

Configuration Management -> Transmission Resources -> IP
Transmission -> PPP Parameters. Then, right-click in the PPP
Parameters window on the right, and add a message. See Figure 7.2
-113, Figure 7.2 -114, and Figure 7.2 -115.
Figure 7.2-113 PPP Parameter Management (1)

PPP ID: It indicates PPP ID, starting with 0. The number is increased by 1
each time when a record is added. This parameter is set by the system
automatically, and no modification is needed.
PPP Encapsulation Type: When SDR is connected to BSC/RNC through a

pair of E1 lines, select PPP; when SDR is connected to BSC/RNC through
two pairs of E1 lines, select ML-PPP (MultiLink-PPP).

MP Header Format: When the PPP encapsulation type is ML-PPP, Long

Sequence Number indicates the 24 bit is used to identify the ML-PPP
frame sequence number, while Short Sequence Number indicates that the
12 bit is used to identify the ML-PPP frame sequence number; when the
PPP encapsulation type is PPP, this parameter is invalid.
MP Priority: When the MP header format is set as Long Sequence

Number or Short Sequence Number, this parameter can be set as 1 by
default as a priority; when the MP header format is invalid, this parameter is
also invalid (255 by default).
Link ID: Link 0, Link 1, and Link 2 are used to set HDLC channel (HDLC ID)
used by PPP link respectively. When the PPP Encapsulation Type is set
as PPP, only link 0 is valid; when the PPP Encapsulation Type is set as
ML-PPP, you can select multiple links based on the planning. See Figure
7.2 -116.
BTS IP: It indicates the IP address that SDR uses to communicate with
iBSC. Note that this address is the external address of SDR. The address

format shouldnt be 192.Environment Number.Slot Number.16, because

192.x.x.16 is the format of the internal address of each SDR board. This
address is required only when other boards of SDR are accessed by using
LMT or through the active CC board. The address 192.x.x.16 is similar to
the internal address 128.x.x.x of the control panel on iBSC.
Quality Protocol: it is not supported currently.
Need Authentication: It indicates whether the user authentication is

required, including PAP and CHAP protocols. It is not required here.
Support IP Compression: It indicates whether to support IP compression or

not. Configure the compression parameters when IP/UDP header
compression is used. The maximum value of NONTCP CID is set as 512.
Others can use the default value. Select No unless specified otherwise.
5. Global Port Parameters
This option should be configured for both E1/T1 and FE accesses.
Click Transmission Resources -> IP Transmission -> Global Port

configuration interface of global port parameters is displayed.
Figure 7.2-117 Global Port Parameters

Parameter ID
Global Port ID: It is generated automatically, starting with 1.
Operation Mode: It indicates the mode of IP bearer (data link layer

protocol): Ethernet/PPP. When the data link layer uses PPP encapsulation,
select IP over PPP; when the data link layer uses Ethernet encapsulation,
select IP over Ethernet.
Link Layer Port ID: It indicates the internal port number used in BTS
protocol stack subsystem. For example, PPP uses Global Ports No. 3 - No.
34 that corresponds to Link Layer Ports No. 0 - No. 31. This parameter is
generated by the system automatically, and needs no modification.
Use VLAN: It is not selected currently.
Vlan ID: When the box [Use VLAN] is checked, this parameter is valid. Its
value ranges from 2 - 4094. This parameter is invalid when the value is
65535.
6. IP parameters
Click Transmission Resources -> IP Transmission -> IP Parameters,

right-click at the blank area on the right, and select Add. The configuration
interface of IP parameters is displayed.

Figure 7.2-118 IP Property Configuration
IP ID: It indicates IP ID used by the protocol stack.
IP Address: It indicates the IP that BTS uses to access BSC. It is in grey

and is not editable.
Subnet Mask: This parameter is in grey and is not editable.
Gateway Address: It indicates the IP address of IPPB or EUIP

corresponding to SDR. This parameter is in grey and is not editable.
When the data configuration is complete, the IP address and the gateway
address are obtained automatically after the synchronization with BSC
data.
[Subnet Mask]: it indicates the subnet mask of the IP address mentioned

above. The first byte of the subnet mask cannot be 0, and all four bytes
cannot be 255 at one time.
[Configured Bandwidth]: it indicates the available bandwidth of the current

IP (a SDR base station can be configured with multiple IP addresses). The
bandwidth configured in FE parameters is the total bandwidth of SDR base

station. For E1 access, it can be set to N*1984. N indicates the number of

E1 lines (bandwidth of each E1 line is 2048 kbps. Each E1 line has 32
timeslots, but only 31 timeslots are available. Therefore, the actual
bandwidth is 2048 * 31 / 32 = 1984).
[Bearer Service Type]: it indicates the COS priority corresponding to the IP

address. It is used to select the corresponding IP with priority based on
different priorities of services. A BTS can be configured with multiple IP
addresses. This option determines the service type that the current IP
address can bear. For details of COS priority, see the appendix.
Note:
The IP address, subnet mask, and gateway address on this interface are in
grey. When the site is started, these options will be filled in automatically. For
example, the IP address is BTS IP address configured in PPP Parameter
Management. It is the bandwidth to be set here.
7. SCTP parameters
The configurations of E1, T1, and Ethernet are the same on the
transmission layer. SCTP belongs to the transmission layer that is above
the IP layer. It can not perceive whether the data link layer is PPP or
Ethernet, therefore, the SCTP configuration is the same for E1 or Ethernet
accesses.
Click Transmission Resources -> IP Transmission -> SCTP

configuration interface of SCTP parameters is displayed. See Figure 7.2
-119 and Figure 7.2 -120.

Figure 7.2-119 SCTP Parameter Management (1)
[Association ID]: it indicates the unique identification of association in

BTS. It is 0 by default.
[Radio System]: select GSM for GSM network.
[Local IP address]: select the local IP address from IP address list

configured in IP Parameters. It indicates the IP address that BTS uses to
establish the connection with iBSC. You can just select the actual IP
address that BTS uses to access iBSC.
[Local Port ID]: it indicates the port number that BTS uses to establish
SCTP connection with iBSC. Its value ranges from 1 to 1536. This port ID is
SITE_ID used in layer 3, that is, GSM Site ID in the background network
management. It is set by the system automatically, and is not editable.
When the local site ID is configured, the local port ID is generated

automatically here. If the value is null, you should set the local site ID in Set
Basic Property of BTS.

Figure 7.2-120 SCTP Parameters Management (2)
[Remote Port ID]: it indicates SCTP port ID used by iBSC. Specifically, it is

the port ID that is used to establish SCTP connection between iBSC and
BTS. This port ID can be calculated based on the following algorithm on
iBSC:
The value of remote port ID = 0 x 3900 + CMP module number belongs to

the local BTS.
Where, OMP module number is 1, while RPU module number is 2.

Currently, one iBSC can support a maximum of three pairs of
active/standby CMP. Each CMP has two modules. The module numbers
are 3, 4, 5, 6, 7, and 8, corresponding to the corresponding remote port ID
14595 - 14600. For an office where OMP and CMP are combined (such as
single-frame or dual-frame office), CMP module number is 1. The remote
port ID is 0 x 3900 + 1 = 0 x 3901 = 14593.
[Remote IP Address]: it indicates the IP Abis address (a virtual address)

on iBSC. IP address configured on iBSC for BTS to access must be
consistent with the IPAbis virtual address configured by iBSC.
[I/O Flow Number]: it is 6 by default.

[QoS]: Select EF Service.
[Maximum Data Retransmission Times]: It is configured by default.
[Maximum Retransmission Interval]: It is configured by default.
[Heartbeat Detection Interval]: It is configured by default.
8. OMCB parameters
Click Transmission Resources -> IP Transmission -> OMCB

configuration interface of OMCB parameters is displayed. See Figure 7.2
-121.
Figure 7.2-121 OMCB Parameters
[BTS Internal IP Address]: It is configured by default, and is not editable.
[O&M Network Management Address]: it indicates the Abis interface

virtual address of iBSC, instead of the port address of OMCB access board
IPBB.

[QoS]: Select EF Service (0xB8).
7.2.4 Radio Configuration
Configuration description
The following items should be configured in this section:
RF unit central frequency
GSM sectors
GSM carriers
GSM RU
Configuration steps:
1. RF unit central frequency configuration
Because the bandwidth of RRU is limited within 10 M, that is, it can receive
signals within the range of the central frequency 5 M (it is not guaranteed
to receive the out-band signals). Therefore, it is noted that frequency of the
logical transceiver cannot exceed this range. For example, when the central
frequency is 945 MHz, the range is 940 - 950. In absolute frequency, the
range is 25 - 75. The central frequency configured here is the downlink
central frequency.
Click Radio Resources -> Configure RF Unit Central Frequency, right-

click at the blank area on the right, and select Add. The RF unit central
frequency configuration interface is displayed. See Figure 7.2 -122.

Figure 7.2-122 RF Unit Central Frequency Configuration
[Board Name]: It indicates an RRU board.
[RF Operation Mode]: Select GSM, WCDMA or WCDMA/GSM according

to the radio system of BTS.
[Band Name]: Select a proper band from the pull-down list based on the
RRU hardware type which can be identified by the delivery nameplate.
[Transmitting Central Frequency]: It indicates the downlink central

frequency.
Because the bandwidth of the current RRU version is limited within 15 M,

that is, it can receive signals within the range of central frequency 7.5 M
(it is not guaranteed to receive the out-band signals). Therefore, it is noted
that frequency of the logical transceiver cannot exceed this range. For
example, when the central frequency is 945 MHz, the supported frequency
range is 937.5 MHz - 952.5 MHz. In absolute frequency, the range is 12 -
87.
2. Radio resource configuration

GSM sectors, GSM RU, and GSM carriers are configured in Radio
Resources.
a) GSM sectors
This step is used to configure logical and physical cells of the site. The
sector number indicates the logical cell ID. The sector numbers
configured here are the base of sector numbers in GSM carriers. The
sector numbers in the following GSM carriers are selected based on
these sector numbers.
GSM sectors configured here should correspond to the cell numbers

under BTS in OMCR.
Click Radio Resources -> GSM Sector, right-click at the blank area on
the right, and select Add. The GSM sector configuration interface is
displayed. See Figure 7.2 -123.
Figure 7.2-123 GSM Sector Configuration

[Sector No.]: It indicates the number of a sector, ranging from 1 to 24.

It indicates the number of cells configured under this site,
corresponding to the BSC side.
[Physical Cell ID]: It must be the same as the sector number, ranging
from 1 to 984. This parameter is invalid in GSM. (The physical cell ID is
not involved currently. You can configure this parameter freely). It
reflects the relation between physical cell number and sector number.
[GPS Synchronization Frame Header Offset]: set it by default if GPS

is not used.
For the GSM cell configuration, see the following figure.
Figure 7.2-124 Configured GSM Cells
b) GSM RU
The number of carriers configured for RU is related to the

configurations of GSM sectors and GSM carriers. For the configuration
interface, see Figure 7.2 -125 and Figure 7.2 -126.

Figure 7.2-125 GSM RU Configuration (1)
Figure 7.2-126 GSM RU Configuration (2)

[Sector No.]: it indicates the number of a sector configured in

Configure GSM Sectors. All configured GSM sectors will be displayed
in the pull-drop list here.
[RU Type]: select RU60, RU02, or RU02E based on the actual

environment.
[Board Name]: It indicates the name of a RF board. It is DTR for

RU60.
[Number of Carriers]: it is determined based on RU type and the

planning. RU60 supports a maximum of six carriers, while RU02
supports a maximum of two carriers.
[Carrier Power Configuration]: It indicates the output power of each

carrier. Its value is equal to 60 W/number of carriers. Number of
carriers x carrier power 60 W
[Static Power Level of Carrier]: the static power of carriers can be

divided into ten levels. This parameter is configured based on the
network planning.
[Receiving Channel Attenuation]: it is not set by default.
[RF Extension Port]: when a cell has multiple RRU, use RF extension;
when a cell has only one RRU, do not use RF extension, that is, use
the independent operation mode.
[Board Intelligent Power-off]
[Multi-carrier Combination]
[Sector x Number]: it indicates the sector number, that is, the sector
that is configured on the remote rack (RRU) mentioned above. Set
sector (1) only.
[Sector x Number of Carriers]: the number of carriers of the sector

should be consistent with that is configured before. Set the number of
carriers of sector (1) only.
c) GSM carriers

Click Radio Resources -> GSM Carrier, right-click at the blank area
on the right, and select Add. The GSM Carrier Configuration interface
is displayed. Add carriers for the sector based on the number of carriers
in the sector that is configured in GSM RU.
Figure 7.2-127 GSM Carrier Configuration
[Sector No.]: it indicates the logical sector number that is consistent

with the cell ID configured on iOMCR. It corresponds to the sector
number in GSM sector configuration. The logical carriers indicate the
logical cells in the sector (or cells in iOMCR).
[Logical Carrier No.]: it indicates the logical carrier number in the

selected sector. The number corresponds to the transceiver number
configured under the cell of BTS on iOMCR.

[BCCH Carrier]: do not set this parameter. The system will select a
BCCH carrier based on the background OMCR configuration when the
site is started.
[Use IRC]: it indicates whether to use IRC function. It is not selected by

default.
[Channel Mode]: when a logical carrier uses a physical carrier, select

Single Channel Mode; when a logical carrier uses multiple physical
channels, select Multiple Channel Mode, that is, OTSR. The Dual
Channel Mode indicates the four-diversity receiving.
[Number of Carriers]: this parameter is related to the combined

operation mode. It indicates the number of physical carriers that the
logical carrier needs. For iOMCR, the number of carriers is configured
based on the logical carrier. Therefore, this parameter is not required.
In Single Channel Mode, the number of carrier is 1; in Dual Channel
Mode, the number of carriers is 2; in Multiple Channel Mode, the
number of carriers ranges from 1 to 12. You can set it manually.
[Parent Frequency]: it indicates the actual operation band of carrier.
[Child Frequency]: it is not set.
Note:
The parameter tables of GSM sectors, GSM RU, and GSM carriers are
configured in descending way.
The number of carriers configured in each sector should not be less than
that configured in iOMCR.
7.3 Version Load

All SDR versions are load in specification package from LMT. If connection is
established with iBSC, you can load the version from OMCB. For the software
version loading, see the following figure.

Figure 7.3-128 LMT Software Version Management
The basic procedure of version loading is as follows:
1. Click Archive to put a specification package into LMT.
2. Click Load to load the specification package to the foreground.
3. Check Specification Package Information to check the version

information in the specification package.
4. The loaded specification package is in standby status. Select the

specification package to be activated in Version Operation Information,
and click Associated Configuration Data.
When the data association is configured, click Specification Package to

activate and run the current version.
7.4 SDR Power-on Inspection (Before and After Link

Establishment)
7.4.1 General Principle for Passing Power-on Inspection
On rack 1 of LMT (BBU), there is no alarms on CC board, except alarm for

electric signal loss alarm on the El/T1 link, PPP link down alarm, and SCTP
coupling disconnection alarm. If no SNTP server is configured, there is also an
alarm for SNTP time check failure besides these alarms. There is no alarm on
FS board and UBPG board (The board state indicator is green). There is no
alarm on RRU either (The board state indicator is green). All the boards
(including RRU) are connected to the master CC link. The SDR power-on
inspection is considered passed only when all the conditions above in bold are
satisfied.
To query the state between boards (including RRU) and the master CC link
board, perform the following operations:
Telnet to CC, and then enter the OSS_DbgShowComm command. The

following information is displayed (CC board is configured in slot 1; FS board is
configured in slot 3; UBPG board is configured in slot 5, and three RRU are
configured):
CC->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 0
0 (0 1 0 1 ) R 3 c0fe0210 00:00:00:00:00:00 0 0 0 0
1 (3 1 0 1 ) L 3 c0fe0510 00:00:00:00:00:00 0 0 0 0
1 (3 1 0 1 ) R 0 ffffffff 00:00:00:00:00:00 0 0 0 0
2 (1 1 0 1 ) L 3 c0fe0310 00:00:00:00:00:00 0 0 0 0
2 (1 1 0 1 ) R 0 ffffffff 00:00:00:00:00:00 0 0 0 0
3 (17 1 0 1 ) L 3 c8fe0004 00:00:00:00:00:00 0 0 0 0
3 (17 1 0 1 ) R 0 ffffffff 00:00:00:00:00:00 0 0 0 0
4 (16 1 0 1 ) L 3 c8fe0003 00:00:00:00:00:00 0 0 0 0
4 (16 1 0 1 ) R 0 ffffffff 00:00:00:00:00:00 0 0 0 0
5 (15 1 0 1 ) L 3 c8fe0002 00:00:00:00:00:00 0 0 0 0
5 (15 1 0 1 ) R 0 ffffffff 00:00:00:00:00:00 0 0 0 0
GroupTable:
127,255,
value = 2 = 0x2
In the above printed information, IP addresses of these boards are in hex. If the
State value is 3, the board is connected to the master CC board link.
7.4.2 Information to Be Confirmed After Power-On
1. Confirm the version of SDR specification package.
Telnet to CC, and then enter ShowBMCVersion. Then, information of the

current specification package is displayed, namely the activated SDR version.
You do not need to record this.
2. Record the generation date of EPLD version of RRU.
Telnet to RRU, and enter d 0x0e001020. The printed data is October 7, 2008 or
later. You need to record this.
DTR->d 0x0e001020
0e001020: 2008 1213 1428 0000 0000 0000 0000 0000 * ....(..........*
0e001030: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001040: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001050: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001060: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001070: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001080: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001090: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e0010a0: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e0010b0: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e0010c0: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e0010d0: 4454 525f 6130 3100 3100 0000 0000 0000 *DTR_a01.1.......*
0e0010e0: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e0010f0: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001100: d000 000b 0000 0000 0000 0000 0000 0000 *................*
0e001110: 0100 0000 0000 0000 0000 0000 0000 0000 *................*
value = 21 = 0x15
3. Confirm versions of CPU, DSP, and FPGA.

Telnet to RRU, and then enter the svi command. Main CPU Version (CPU),
Main FPGA Version (FPGA), and Main IFFPGA Version (DSP) are the required
versions (For versions, see the red label). You do not need recording this.
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
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
7.4.3 FAQ
1. If there is an Optical Port Signal Loss alarm on FS board, confirm whether

the optical modules on FS board and at the RRU side are faulty or RRU is
powered on. If optical modules are normal and RRU is powered on, then
the fiber goes wrong.
2. If there is an Optical Port Frame Loss alarm on RRU, change the optical
module at the RRU side to make an attempt.
3. If there is a Calibration File Loss alarm on RRU, as shown in Figure 7.4

-129,
Figure 7.4-129 Alarm Information Query
Ftp to RRU, and put the lost calibration file to RRU manually. If the file
does not exist, obtain it from the normal RRU.

4. When there are application monitoring alarm and board communication link
disconnection alarm on RRU, it is likely that RRU is not powered on if the
fiber and optical module are in good condition. Connect RMB board
converting from the serial port to the network interface to ALM interface of
RRU, and then telnet to 199.33.33.33 and query the current operation of
RRU by running the hr command, or perform the following operations to put
DSP, CPU, and FPGA versions of RRU manually: enter the root directory,
and replace the cur.swv under the rru directory, the cur.swv under the
rru\dsp, and the cur.swv under the rru\fpga directory. If manually putting the
three versions in RRU is unsuccessfully, delete cur.swv, enter the bin
command, and put the three versions manually again.
7.4.4 Fast Configuration of Site Data
When a site is configured, export its configuration data, import the data into
another site with the same or similar configuration, and then modify a few data,
thus achieving fast configuration of BTS data. The export and import methods
of the configuration data are described in Section 7.1.5. The following only
describes the data to be modified after import.
1. Site number of BTS. Modify the required site number.

Figure 7.4-130 Data to Be Modified After Import of Configuration Data Site Number
2. Topology structure. Adjust the structure as needed.
3. PPP parameters. Adjust the parameters as needed.

Figure 7.4-131 Data to Be Modified After Import of Configuration Data BTS IP Address
4. SCTP parameters. First delete the existing SCTP parameters and then add
new SCTP parameters.
Figure 7.4-132 Alarm Information Query

5. RF Unit Central Frequency, GSM Sector, GSM RU, and GSM Carrier.
Modify these parameters according to the planning.

8 Foreground and Background Data

Synchronization
Abstract
The preceding chapters describes data configuration on OMCR, OMCB, and
LMT respectively.
8.1 Synchronizing Configuration Data to the Foreground

When the configuration is complete, the data is saved on the OMC-B
background server. To make the data take effect, send it to base station in the
foreground through whole table synchronization or increment synchronization.
Right-click the popup shortcut menu in the management NE, and select entire
table synchronization or increment synchronization to send the configuration
data.
Note:
The base station will restart in the whole table synchronization.
8.2 SDR Foreground and Background Data Synchronization

If the created SDR site is already configured by LMT and the network
transmission is normal, a link will be established automatically between the
foreground and the background. Then, the green icon in front of base station
management NE will be switched to connection status. At this time, you can
configure the data through OMCB and synchronize the data with the
foreground, or upload the data configured in the foreground to the background.
1. Upload SDR data to OMCB
On the site, right-click and select BTS Data Configuration Wizard (SDR). The
interface as shown in Figure 8.2 -133 is displayed. Select Use the foreground

to configure, and then click Next. The Data Parallel Upload tab is displayed.
Select NE to be uploaded, as shown in Figure 8.2 -134.
Figure 8.2-133SDR Foreground Data Uploading (1)

Figure 8.2-134 SDR Foreground Data Uploading (2)
Click Next, and the dialog box as shown in Figure 8.2 -135 is popped up if
OMCB and BTS link are normal. In Figure 8.2 -135, Switch to Master indicates
whether the configuration exported from LMT servers as the master
configuration. Click OK. The configuration is exported. The LMT configuration
is uploaded.

Figure 8.2-135 SDR Foreground Data Uploading (3)

9 SDR Commissioning Tests
Abstract
This chapter describes the basic service tests and how to test these services.
For more information, see 08 ZXSDR B8200&R8860 (V4.0) Test Guide.
9.1 CS Domain Service Test

9.1.1 Test Preparations
1. iBSC equipment is commissioning and normal.
2. The core network equipment is commissioning and normal.
3. Prepare two cellular phones ( A and B) and related fittings, and two SIM
cards which can be used in the local network.
4. LAC, CI, and frequency of this site are confirmed consistent with the
planning data and the background data.
5. Obtain the frequency planning table for all cells of the site.
6. The calling uses the first party release mode (at the handover side).
9.1.2 Test Objective
It is to confirm that CS domain service is normal.
9.1.3 Test Procedure
1. Select a cell to be tested.
2. Use A to lock BCCH frequency of the cell.
3. a. (1) A calls B, and receives the prompt tone (ring back tone). (2) B
answers successfully. The voice is good. (3) A hooks on normally.
b. Repeat above calling steps. B hooks on normally.
4. a. (1) B calls A, and receives the prompt tone (ring back tone). (2) A
answers successfully. The voice is good. (3) B hooks on normally.
b. Repeat the above calling steps. A hooks on normally.

5. Use A to lock other frequencies of the cell.
6. Repeat steps 1 5 to test other cells of the SDR site until all cells are
tested.
9.2 PS Domain Service Test

9.2.1 Test Preparations
1. A ftp server is prepared for access and runs normally.
2. Prepare a cellular phone to test GPRS/EDGE service and a SIM card that
has subscribed PS service.
3. FTP tool software, such as CuteFTP and LeapFTP, is installed on PC.
4. Account information is already set in the cellular phone, including APN,

username, password, and IP address.
5. PC and the cellular phone meet the connection conditions, including the
data line, Bluetooth, and infrared transmission.
9.2.2 Test Objective
It is to confirm that GPRS/EGDE data service is normal through FTP.
9.2.3 Test Procedure
1. Connect the cellular phone to PC through a data line, Bluetooth, or infrared

transmission.
2. Install the driver of cellular phone Modem on the PC to ensure that Modem
runs normally.
3. Establish a new dial-up connection on the PC: write down the phone
number, ISP, username and password in the dial-up connecting setting.
4. Click to create a new dial-up connection to perform dial-up connection.
5. When the dial-up connection is successful, open FTP tool software on the
PC.
6. In the FTP tool software, type IP, username, and password of FTP server to
log into FTP server.

7. Download a file from FTP server to PC. The file size must be greater than
500 K.
8. Record the size, download period and download speed of the file. The file
must be download successfully and the downloaded file can be used.
9. Upload a file from PC to FTP server. The file size must be larger than 500
K.
10. Record the size, upload period and upload speed of the file. The file must
be uploaded successfully and the uploaded file can be used.
9.2.4 Test Description
APN: Access Port Name. APN consists of two parts: network ID and
operator ID. The network ID defines the external network of GGSN
connection. The Operator ID defines PLMN GPRS network that contains
GGSN.
In the FTP test of GPRS test, APN, username, password, and IP address
are provided by the operator.
When MS originates PDP context activation, SGSN organizes the

complete APN using the network ID and operator ID, and then obtains IP
address of the GGSN corresponding to APN through DNS resolution.

Appendix A Fast Query of General

Information
Conversion Between Absolute Frequencies and Frequencies
Conversion relations between frequency numbers and absolute frequencies:
Frequency numbers of GSM900 system:
Uplink: Fl (n) = 890 + 0.2 n MHz
Downlink: Fu (n) = 935 + 0.2 n MHz 1 n 124, where n is the

absolute frequency
Frequency numbers of E-GSM900 system:
Uplink: Fl (n) = 890 + 0.2 n MHz
Downlink: Fu (n) = 935 + 0.2 n 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
Frequency numbers 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
SDR Board IP
BBU
Slot 1 (CC-1): 192.environment number.1.16
Slot 2 (CC-2): 192.environment number.2.16
Slot 3 (FS-3): 192.environment number.3.16
Slot 5 (UBPG-5): 192.environment number.5.16
RRU
Remote rack 2: 200.environment number.0.2

Remote rack n: 200.environment number.0.n

07 ZXSDR BS8800 Project Commissioning Guide (V1.0)

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

07 ZXSDR BS8800 Project Commissioning Guide (V1.0)

Încărcat de

Drepturi de autor:

Formate disponibile

ZXSDR BS8800 Project Commissioning Guide For Internal Use Only

ZXSDR BS8800 GU360

Confidential and Proprietary Information of ZTE CORPORATION.

ZXSDR BS8800 GU360 Project Commissioning Guide

Compiled by: Yang Wen

Reviewed by: Zhao Yanghao

Post code: 201203

Technical support website: http://tsm.zte.com.cn

Hotline: +86 755 26770800 800-830-1118

Fax: +86 755 26770801

Confidential and Proprietary Information of ZTE CORPORATION.

and are the registered trade marks of ZTE

The product described herein conforms to the design

The actual product may differ from what is described in this

For the latest document information, please visit our website:

Confidential and Proprietary Information of ZTE CORPORATION.

Confidential and Proprietary Information of ZTE CORPORATION.

V1.0 Yang Wen 2009-06-15 New

Confidential and Proprietary Information of ZTE CORPORATION.

Confidential and Proprietary Information of ZTE CORPORATION.

4 Operation and Maintenance Networking of SDR..............................................................4-8

5 OMCR Data Configuration.................................................................................................5-15

5.1 Configuration of BSC Global Resource........................................................................5-15

6 OMCB Data Configuration.................................................................................................6-43

Confidential and Proprietary Information of ZTE CORPORATION. ii

7 LMT Installation and Data Configuration.........................................................................7-86

8 Foreground and Background Data Synchronization....................................................8-147

9 SDR Commissioning Tests.............................................................................................9-151

Confidential and Proprietary Information of ZTE CORPORATION. iii

Appendix A Fast Query of General Information...................................................................9-154

Confidential and Proprietary Information of ZTE CORPORATION. iv

1.1 ZXSDR BTS Introduction

Confidential and Proprietary Information of ZTE CORPORATION. 1

Figure 1.1-1 Distributed BTS

1.1.1 BBU+RU Architecture

The separation between baseband and RF can maximize their own

Confidential and Proprietary Information of ZTE CORPORATION. 2

Figure 1.1-2 Distributed Structure of BBU and RU

BBU is responsible for digital baseband signal processing and control

RU is responsible for switchovers between digital baseband signals and

BBU is connected to RRU through the baseband-to-RF interface (optical

BBU is connected to BSC/SDR through the Abis/Iub interface.

RRU accesses MS/UE through the Um/Uu interface.

1.1.2 OMCB Introduction

A traditional 2G BTS (such as BTSV2 and BTSV3) is configured and managed

Confidential and Proprietary Information of ZTE CORPORATION. 3

Figure 1.1-3 SDR Network Management Structure

Based on the management mode of UMTS, the board management,

1.1.3 IP Abis Interface

Confidential and Proprietary Information of ZTE CORPORATION. 4

Figure 1.1-4 Transnmission Network with FE/GE at Abis Interface

Therefore it is the prerequisites that to understand and master BBU+RU

1.2 SDR BTS Commissioning Flow

Confidential and Proprietary Information of ZTE CORPORATION. 5

Figure 1.2-5 SDR Commissioning Flow

As shown in Figure 1.2 -5, BSC installation commissioning includes hardware

Confidential and Proprietary Information of ZTE CORPORATION. 6

For SDR hardware installation please refer to ZXSDR B8200 GU360

LMT local conmissioning is to connect the debugger to SDR and configure

Synchronization between foreground and background indicates that, after the

The transmission network runs normally.

SDR interface-related parameters are correctly configured in OMCR.

SDR management NE is correctly created in OMCB.