GSM-BSS - II - 07 - 200909 ZXSDR Series Base Station Configuration and Commissioning 145

ZTE GSM-BSS Products After-Sales Competency Certification Training Manual
ZXSDR Series Base Station Configuration and Commissioning

Course Objectives
Know the SDR BTSs commissioning flow Know the SDR BTSs configuration and commissioning method with OMCR tool Know the SDR BTSs configuration and commissioning method with LMT tool
Contents
1 Commissioning Preparation ...................................................................................................................... 1 1.1 ZXSDR Stations Introduction ........................................................................................................... 1 1.1.1 BBU+RRU ............................................................................................................................. 2 1.1.2 OCMB .................................................................................................................................... 3 1.1.3 IP Abis Interface ..................................................................................................................... 4 1.2 Commissioning Procedure ................................................................................................................ 5 1.3 Software, Documentation and Data Collection ................................................................................. 8 1.3.1 Preparing Versions ................................................................................................................. 8 1.3.2 Preparing Documents ............................................................................................................. 8 1.3.3 Preparing the Configuration Data .......................................................................................... 9 1.4 Hardware Installation Checking ...................................................................................................... 10 1.4.1 Checking the Hardware Installation ..................................................................................... 10 1.4.2 Powering On or Powering Off the Equipment ..................................................................... 13 1.5 OMC Environment Setting ............................................................................................................. 15 1.5.1 Operation and Maintenance Networking Diagram of SDR ................................................. 15 1.5.2 When an Abis Interface Uses Ethernet as the Bearer ........................................................... 15 1.5.3 When an Abis Interface Uses E1/T1 as the Bearer............................................................... 16 1.5.4 One Example ........................................................................................................................ 17 2 OMCR Data Configuration..................................................................................................................... 21 2.1 BSC Global Resources Configuration............................................................................................. 21 2.2 Abis and OMCB Interface Configuration ....................................................................................... 23 2.2.1 Abis Interface Configuration ................................................................................................ 24 2.2.2 OMCB Interface Configuration ........................................................................................... 27
i
2.3 IP Related Configuration .................................................................................................................28 2.3.1 Create IP Abis Interface ........................................................................................................28 2.3.2 Create IPBB Interface to OMCB ..........................................................................................30 2.3.3 Set E1 Abis Interface ............................................................................................................31 2.3.4 Set FE Abis Interface ............................................................................................................37 2.4 B8200 Configuration on OMCR......................................................................................................39 2.4.1 Create Logical Site ...............................................................................................................39 2.4.2 Create B8200 Rack ...............................................................................................................40 2.4.3 Configure B8200 Cells .........................................................................................................42 2.4.4 Configure B8200 TRX..........................................................................................................44 3 OMCB Data Configuration .....................................................................................................................47 3.1 OMCB-OMCR Server Environment Configuration ........................................................................47 3.1.1 Modifying the deploy-030womcb.properties Configuration File (as an OMC User) ...........47 3.1.2 Modifying FTP-related Configuration Files (as an OMC User) ...........................................48 3.1.3 Modifying the deploy-default.properties File (as an OMC User) .........................................49 3.1.4 Starting the OMC-B Server (as an OMC User) ....................................................................50 3.2 SDR Site Physical Data Configuration ............................................................................................50 3.2.1 Create SDR Site Management Element ................................................................................51 3.2.2 Set the Exclusive Operation Right ........................................................................................54 3.2.3 Create the Site Configuration Set .........................................................................................55 3.2.4 Create the Site Physical Parameters ......................................................................................55 3.3 Transmission Parameters Configuration ..........................................................................................61 3.4 Clock and Dry Contact Parameters Configuration ..........................................................................71 3.5 Radio Parameters Configuration ......................................................................................................72 4 LMT Installation, Configuration and Power On Checking ..................................................................79 4.1 LMT Introduction ............................................................................................................................79
ii
4.1.1 LMT Content Introduction ................................................................................................... 79 4.1.2 LMT Installation .................................................................................................................. 79 4.1.3 Connection between LMT and SDR .................................................................................... 83 4.1.4 Offline Configuration ........................................................................................................... 86 4.1.5 Configuration Export and Import ......................................................................................... 87 4.2 SDR Site Configuration on LMT .................................................................................................... 88 4.2.1 Basic Properties Configuration ............................................................................................ 90 4.2.2 Physical Parameters Configuration ...................................................................................... 95 4.2.3 Transmission Parameters Configuration ............................................................................ 103 4.2.4 Radio Parameters Configuration ........................................................................................ 117 4.3 Software Uploading ...................................................................................................................... 124 4.4 SDR Site Power on and Checking................................................................................................. 125 4.4.1 Power on Checking Criteria ............................................................................................... 125 4.4.2 Site Information Confirmation ........................................................................................... 126 4.4.3 Common Problems and Handling ...................................................................................... 128 4.4.4 Site Quick Setting Methods ............................................................................................... 129 5 Commissioning and Testing................................................................................................................... 133 5.1 System Data Transmission and Synchronization .......................................................................... 133 5.1.1 System Software Transmission .......................................................................................... 133 5.1.2 System Data Synchronization ............................................................................................ 133 5.2 Circuit Service Testing .................................................................................................................. 134 5.2.1 Test Preparations ................................................................................................................ 134 5.2.2 Test Purpose ....................................................................................................................... 134 5.2.3 Test Procedure .................................................................................................................... 134 5.3 Packet Service Testing .................................................................................................................. 134 5.3.1 Test Preparations ................................................................................................................ 134
iii
5.3.2 Test Purpose ........................................................................................................................135 5.3.3 Test Procedure.....................................................................................................................135 5.3.4 Test Description ..................................................................................................................136 Appendix A Abbreviation Table................................................................................................................137
iv
1 Commissioning Preparation
1.1 ZXSDR Stations Introduction
ZXSDR is a series of wireless BTS products designed and manufactured by ZTE CORPORATION. Employing the advanced Software Defined Radio (SDR) technology and the uTCA-based hardware architecture, ZXSDR BTS supports all the current wireless access modes, including GSM, UMTS, CDMA2000 and WiMAX access, and can smoothly evolve to Enhanced EDGE/LTE. Three types of ZXSDR BTS are used in the current GSM networks: 1) 2) 3) Indoor macro BTS, such as ZXSDR B8800 GU360; Outdoor macro BTS, such as ZXSDR B8900 GU360; Distributed BTS, such as ZXSDR B8200 GU360 + ZXSDR B8860 GU906/GU186. The distributed BTS is a type of BTS whose BBU and RRU are separated from each other.Figure 1.1-1 shows the architecture of a distributed BTS.
ZXSDR Series Base Station Commissioning Manual
Figure 1.1-1
Distributed BTS
Compared with conventional BTS, the ZXSDR BTS supports numerous systems such as GSM and UMTS and has made great improvements as described in the following sections.
1.1.1 BBU+RRU
When the baseband part is separated from Radio Frequency (RF) part, their respective advantages can be better utilized. The baseband part can attain the maximum integration whereas RF part can attain the maximum power and efficiency. Furthermore, the networking becomes more flexible. The baseband part is called Base Band Unit (BBU), whereas RF part is called Remote Radio Unit (RRU).Figure 1.1-2 shows the functions of BBU and RRU.
Chapter 1
Commissioning Preparation
Figure 1.1-2
Separation of the BBU and the RRU
BTS is divided into the BBU and the RRU. One BBU can be shared by multiple RRU equipment. The functions of BBU and RRU are described as follows: BBU processes digital baseband signals and implements control and management. RRU converts digital baseband signals into analog signals between BBU and the antenna. BBU is connected with RRU via the baseband-RF interface (an optical interface). It transmits I/Q digital baseband signals and OAM signaling data. BBU is connected with BSC/Node B via Abis/Iub interface. RRU provides MS/UE access via Um/Um interface.
1.1.2 OCMB
The configuration and management of conventional 2G BTS (such as BTSV2 and BTSV3) is performed through OMCR (including the iSMG). In contrast, the configuration of ZXSDR BTS is mostly performed through LMT or OMCB (OMCR completes the configuration of some wireless data only). The Operation and Maintenance Center for Node B (OMCB) is the operation and maintenance unit defined by 3GPP to manage Node B. As dual-mode products supporting GSM and 3G systems, ZXSDR BTS also supports OMCB. Today, the old single-thread link mode (OMCRBSCBTS) is changed to the dual-thread link mode (OMCBBTS and OMCRBSCBTS) and then one more entity exists above BTS, as shown inFigure 1.1-3.
OMCB
OMCR
RNC
BSC
SDR
Figure 1.1-3
Network Management Structure of the ZXSDR BTSs
In the management model of the WCDMA system, the OMCB performs the board management, configuration, software downloading, and alarm functions for the ZXSDR BTS. When working in the dual mode, the OMCB also performs these GSM operation and maintenance functions whereas the OMCR undertakes GSM-related wireless configuration and status management only.
1.1.3 IP Abis Interface

As described previously, the hardware structure of ZXSDR BTS is improved to BBU+RRU and OMCB is added for network management. A distinctive difference between ZXSDR BTS and conventional 2G BTS is that the IP protocol is applied on Abis or Iub interface as for ZXSDR BTS and the physical bearer can be FE/GE or E1/T1 (IP over E1/T1) instead of TDM E1/T1. The benefit of E1/T1 is that the existing transmission equipment can be fully utilized and thus the user's investment can be saved, whereas the benefit of FE/GE is that a greater bandwidth can be obtained and this caters to the evolution of communication systems towards IP networks. Figure 1.1-4 shows a transmission network using FE/GE on Abis or Iub interface.
Chapter 1
Router Switch PCM/X.25/DDN.. . Router
BBU
Switch
iBSC
Figure 1.1-4
Using FE/GE on Abis Interface
Therefore, it is necessary to thoroughly understand the BBU+RRU hardware structure and the OMCB+OMCR NMS structure and master the knowledge about IP networking before debugging ZXSDR BTS. Unless otherwise stated, BSC mentioned in this document for interconnection with ZXSDR BTS refer to ZXG10 iBSC.
1.2 Commissioning Procedure

Figure 1.2-1 shows the commissioning process of ZXSDR BTS.
BSC Installation Commissioning
Hardware Check
OMCR Data Configuration
Local Commissioning of LMT
OMCB Data Configuration
Installation & Configuration Check

No
Is link created?
Yes
Synchronize Data on Foreground and Background
Service Testing
End
Figure 1.2-1
Debugging Process of the ZXSDR BTS
As shown in Figure 1.2-1, the BSC installation commissioning involves hardware installation, NMS software installation, BSC data configuration, version management, A/Gb interface interconnection and service testing. The NMS software must be installed in OMCR+OMCB mode (iSMGV6.20 supports the OMCR+OMCB mode). The hardware installation of ZXSDR BTS is described in the documents of ZXSDR BTS, such as ZXSDR B8200 GU360 (V4.00.100) Hardware Installation Guide, ZXSDR R8860 GU906 GU186 (V1.00) User's Manual, and ZXSDR BS8800 GU360 (V4.00) Hardware Installation Guide. You can access the website http://tsm.zte.com.cn to
6
Chapter 1
download these documents. This document describes only the check to be performed after the installation so as to guarantee the normal commissioning of the equipment. The OMCR data configuration mentioned in this document refers to the ZXSDR-related data configuration on the BSC side. The other configuration performed during BSC installation commissioning is not described in this document. The data configuration on OMCR covers four parts: 1) 2) 3) 4) Settings about BSC global resources; Abis interface board configuration; IP interface configuration; Radio parameter configuration of ZXSDR sites.
OMCB is the operation and maintenance center for ZXSDR BTS. During the commissioning, you can configure the data of ZXSDR BTS through OMCB. In addition, the remote maintenance of ZXSDR BTS is also implemented through OMCB. This chapter describes the methods for creating the ZXSDR BTS management NE (OMCB) on iSMG and configuring the data of ZXSDR BTS on OMCB. LMT can be used to perform local debugging: Connect the commissioning PC to ZXSDR and perform data configuration locally through LMT software on the commissioning PC. You can use LMT to configure transmission-related data (such as IP addresses and routes), physical configuration data (such as board configuration data and topology relation data) and some radio configuration data (such as frequency band data and central frequency data) and to perform ZXSDR version management. The synchronization between the foreground and the background refers to the synchronization of data from the foreground to the background or vice versa Three conditions must be met before you can create a connection between the foreground and the background: The ZXSDR-related interface parameters have been correctly configured on OMCR. The ZXSDR management NE has been correctly created on OMCB. The transmission parameters have been correctly configured on LMT. It should be noted that the data configured on LMT is the same as that configured on OMCB. During the commissioning of ZXSDR, configure the data on the BSC side
7
through OMCR and then configure the data on the ZXSDR side. You may configure the data on the SDR side in two ways: 1) configure all the data through OMCB, then configure the transmission parameters of ZXSDR on LMT so that LMT establishes a connection with the background, and finally synchronizes the data from OMCB to ZXSDR; 2) configure all the data on LMT, then create the ZXSDR management NE on OMCB so that the NE establishes a connection with the foreground, and finally sends the configuration data of ZXSDR to the background. Although both methods are described in this document, the first method is recommended. After configuring the data, go to the site to perform the call quality test (CQT) and the drive test (DT) so as to discover and solve problems. After confirming that BTS operates normally, ask the customer to perform the acceptance test.
1.3 Software, Documentation and Data Collection

1.3.1 Preparing Versions
1. 2. The Version package files of ZXSDR. LMT software packages matching the ZXSDR version. representative office must submit an application on the website
http://support.zte.com.cn to download all the required versions.
1.3.2 Preparing Documents

1. BTS Installation Acceptance Report (Confirm that the installation is completed 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 B8200 GU360 (V4.00.100) Hardware Installation Guide, ZXSDR B8200 GU360 (V4.00.100) Terrestrial Parameter Reference, ZXSDR B8200 GU360
8
Chapter 1
(V4.00.100) Radio Parameter Reference, ZXSDR B8200 GU360 (V4.00.100) Terrestrial Parameter Configuration Guide, ZXSDR B8200 GU360 (V4.00.100) Radio Parameter Configuration Guide, ZXSDR B8200 GU360 (V4.00.100) Centralized Management Operation Guide, ZXSDR B8200 GU360 (V4.00.100) Software Management Operation Guide, ZXSDR R8860 GU906 GU186 (V1.00) User's Manual, ZXG10 iBSC (V6.20) Configuration Manual (Initial Configuration Guide), and iBSC installation and operation manuals. You can download these manuals and documents from the website http://tsm.zte.com.cn. 5. 08 ZXSDR B8200&R8860 (V4.0) BTS Test Guide.
1.3.3 Preparing the Configuration Data

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 1.3-1 gives an example of interconnection parameters.
Table 1.3-1 Parameters for the Interconnection Between ZXSDR and iBSC Parameter GSM site ID Abis interface IP address of BTS IP Abis address (virtual) of iBSC SCTP port number of the remote BSC Gateway address for access to the remote BSC 2 118.18.2.100 118.18.1.1 14595 118.18.1.1 Data Instance
Attached below is an example of the BTS configuration data for a certain field trial.
Site Information of SDR Field Trial.xls
1.4 Hardware Installation Checking

1.4.1 Checking the Hardware Installation
1.4.1.1 Checking Boards Check whether the types, quantities, and locations of boards are consistent with the planning.
Figure 1.4-1
Front Panel of B8200 (Slot Numbers Are Marked in Red)
As shown in Figure 1.4-1, B8200 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 (because the slots of FS boards can also hold UBPG boards. 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.4.1.2 Checking 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. Figure 1.4-2 shows locations of the two 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 1.4-2, the right bits of X5/X6 are the least significant bits and the left bits are the most significant bits.
10
Chapter 1
Figure 1.4-2
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 1.4-1). The two most significant bits are used to set the uplink/downlink long or short line mode of the E1/T1 (see Table 1.4-2).
Table 1.4-1 Settings of the Two Least Significant Bits of X5 Bits of X5 [1, 0] [Shorted, shorted] [Shorted, open] 11 Reserved T1, 100 E1/T1 Mode
[Open, shorted] [Open, open]
E1, 120 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 1.4-2 Settings of the Two Most Significant Bits of X5 Bits of X5 [3, 2] [Open, open] [Shorted, shorted] [Open, shorted] [Shorted, open] Mode Uplink short line, downlink short line Uplink long line, downlink long line Uplink short line, downlink long line 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 may be cascaded). The value ranges from 000 to 111 and is 000 by default, as shown in Table 1.4-3.
Table 1.4-3 Settings of X6 Bits of X6 [2, 1, 0] [Open, open, open] [Open, open, shorted] [Open, shorted, open] [Open, shorted, shorted] [Shorted, open, open] [Shorted, open, shorted] [Shorted, shorted, open] [Shorted, shorted, shorted] 0 1 2 3 4 5 6 7 BBU Cabinet Number
1.4.1.3 Checking the Input Power Check whether polarities of the input power are correctly connected.
12
Chapter 1
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. 1.4.1.4 Checking Cable Connections Check whether FE cables between B8200 and iBSC are correctly connected if FE connections are applied on the Abis interface. Check whether E1 media between DDF and B8200 are correctly connected if E1 connections are applied on the 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 LMT is normal. Check whether dry contact, the 232 serial port cables and the 485 serial port cables are correctly connected.
1.4.2 Powering On or Powering Off the Equipment

1.4.2.1 Powering On or Powering Off B8200 1. 2. Power on B8200 Pull out all the boards of B8200 except for PM module and FA module. Switch on the power, check whether the RUN indicator on the PM module is on and whether the ALM indicator on the PM module is off. 3. Check whether the fan module is running normally, whether the PWR indicator is on, and whether the ALM indicator is off. 4. After verifying that B8200 has been powered on normally 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. Power off B8200 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
13
been powered off. 1. Note: ALM indicators on the PM module and boards will blink 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 before verifying PM module has been powered off. 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 outermost position level. For board insertion, you should insert the board along guide rails and then push the left puller to the innermost position level till the board is locked. 1.4.2.2 Checklist Before Power-on
Item Requirements and Criteria Types, quantities, and locations of boards are consistent Check boards with the planning. Jumpers on the SA board are correctly set according to the actual transmission mode and cabinet cascading. Polarities of the input power of B8200/R8860 are correctly connected. The input voltage range of B8200/R8860 is 40 V DC to Check the input power 57 V DC. The fluctuation range of the single-phase voltage is 200 V AC to 240 V AC. The frequency fluctuation range is 47 Hz to 53 Hz, and PSU is connected to convert AC power into DC power for B8200/R8860 if B8200/R8860 adopts single-phase 220 V AC. Check cabinet cable connections Check Abis interface connections Check the Cables between FS board and R8860 are correctly connected. FE cables to the CC board are correctly connected if FE connections are applied on the Abis interface. E1 media between DDF and BTS are correctly connected if E1 connections are applied on the Abis interface. The network interface on LMT is correctly connected to 14 Results Remarks
Pass Fail Pass Fail Pass Fail Pass Fail
Pass Fail
Chapter 1
Item connections of LMT CC board.
Requirements and Criteria
Results
Remarks
All the boards have been pulled out. Power on the equipment Check power-on results Note The status of each board is normal after power-on. The shelves are properly grounded. The equipment has been normally powered on.
1.5 OMC Environment Setting

1.5.1 Operation and Maintenance Networking Diagram of SDR
From the previous description of the differences in an SDR base station and a traditional 2G base station, we know that the SDR base station has two network management systems, that is, an OMCR and an OMCB. Most of work is done on the OMCB, as shown in Figure 1.1-3. In actual networking, we may install the OMCB and the OMCR on two standalone servers, or integrate them in one network management system (iSMG) and install them on one server (SBCX). The installation and debugging in this manual assume that the OMCB and the OMCR are installed on one SBCX.
1.5.2 When an Abis Interface Uses Ethernet as the Bearer

Figure 1.5-1 shows the networking topological view of an OMC-B network when a ZXSDR base station is accessed to an iBSC in Ethernet (FE/GE) mode. On the base station side, the iBSC is accessed to a local Ethernet switch by means of an 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 the iBSC by means of an IP backbone network); On the base station controller side, the iBSC is connected to the OMC-B network and the base station by means of the IPBB interface board. End-to-end communication between the ZXSDR base station and an OMC-B server employs an OMC-B link. The OMC-B client is connected to the OMC-B server and completes the operation configuration.
15
OMC-B link end-to-end communication
OMC-B Client
OMC-B Server
Ethernet switch for OMC-B
IPBB or GIPI(electric or fibre interface)

BS8200 GU360 PM PM SA CC CC
FS FS BP BP BP BP
F A
FE1 FE2 FE3 FE4
FE1 FE2 FE3 FE4
IPBB or GIPI
iBSC Ethernet switch for SDR Ethernet switch for iBSC
May also be merged into one L3 switch
WAN router for SDR
May also be WAN router for iBSC merged into one L3 switch
IP backbone
OMC-B network topology for ZXSDR (with Abis interface based on FE)
Figure 1.5-1
OMC-B Network Topology when an Abis Interface is FE
1.5.3 When an Abis Interface Uses E1/T1 as the Bearer

Figure 1.5-2 shows the networking topological view of an OMC-B network when the ZXSDR base station is accessed to an iBSC in E1/T1 mode. In this case, you should pay attention to the following: No Ethernet switch is used on the base station side. By means of E1/T1, the base station is directly connected to the E1 interface board (DTB) of the Abis interface of the iBSC;
16
Chapter 1
The Abis interface of the iBSC is connected to the base station by means of an E1/T1 interface board (DTB) instead of an IPBB interface board. It processes base station information on an EUIP. In this case, the OMC-B operation and maintenance gateway of the base station is the IP address set on the EUIP of the iBSC; The OMC-B server is still accessed to the iBSC by means of an IPBB board.
OMC-B link end-to-end communication
OMC-B Client
OMC-B Server
Ethernet switch for OMC-B
BS8200 GU360 PM PM SA CC CC
FS FS BP BP BP BP
F A
DTB
EUIP
FE1 FE2 FE3 FE4
IPBB or GIPI
iBSC
OMC-B network topology for ZXSDR (with Abis interface based on E1)
Figure 1.5-2
OMC-B Network Topology when an Abis Interface is E1
Note The above topological view does not set out any RPU. In fact, the RPU of the iBSC is responsible for route processing.
1.5.4 One Example

IP address planning The following table is an example of IP address planning. For the sake of direct
17
observation, the third digit of a base station IP address is used to represent a site number, as shown by x in the following table. The SDR commissioning described below is based on Table 1.5-1.
Table 1.5-1 Configuration Item IP address of the network interface between the IBSC and the Omcb Server OMCB server IP address configured for the IBSC IpAbis virtual address of the iBSC IP address of the network interface between the IBSC and the BTS IP address configured for the BTS
Example of IP Address Planning Configuration Information 139.1.1.254 139.1.1.200 118.18.1.1 118.18.X.254 118.18.X.100 Mask 255.255.255.0 255.255.255.0 255.255.255.255 255.255.255.0 255.255.255.0
Networking description When jointly deployed, an OMCB and an OMCR are logically two separate NM units except that they are physically installed on SBCX boards. In this case, the iBSC needs to provide two IP interfaces, connected respectively to an SDR base station and an OMCB server; the BSC needs to be configured with a virtual address (RPU interface address). The networking is shown in Figure 1.5-3 Connection between the SDR and the BSC: When E1 is physically used for access, the interface board on the SDR side is SA and that on the BSC side is DTB (EUIP is required for the access of IP); when FE/GE is used, the interface board on the SDR side is CC and that on the BSC side is IPBB. Connection between the OMCB and the BSC: when FE/GE is used, the interface of the OMCB (that is, the external network interface of the SBCX) is generally HEART1. IPBB is used on the BSC side.
BIPP_SDR/ EUIP_SDR 118.18.2.254
OMCB
BIPP_OMCB
RPU
SDR
139.1.1.200
139.1.1.254
118.18.1.1
18.18.2.100
Figure 1.5-3 Network Topology of the OMCB Operation and Maintenance System
18
Chapter 1
Add a route In the example as shown in Figure 1.5-3, the IP address of the OMCB server and that of the SDR are not in the same network segment IP. Therefore, it is necessary to add a route from an OMCB gateway to an SDR network segment. In the Linux system, the command used to add a route is as follows: route add -net destination network address gw next hop address netmask network mask interface ip 1. Command used to add a route In this example, the IP address of the OMCB server is 139.1.1.200. Its gateway address, that is, the IPBB_OMCB address, is 139.1.1.254. The IP address of the SDR is in the network segment 118.18.1.0. Then, the command used to add a route to the iBSC virtual address on the OMCB (that is, the 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 addition, you may view route status by using the netstat nr command. 3. Set a permanent route After you have added a route by using the route add command, to prevent the configured route being lost due to the restart of the SBCX, you may edit the /etc/rc.d /rc.local file as a root user and add the following line to this file: #route add net 118.18.1.0 gw 139.1.1.254 netmask 255.255.255.0 eth1 Thus, each time the SBCX is started, the route will be automatically added. 4. Restart the SBCX and then check Exit from all processes and restart the SBCX. Then, recheck whether the route is normal by using the netstat nr command. 5. Verification after the route addition Exit from all processes and restart the SBCX. Then, recheck whether the route is normal by using the netstat nr command.
19
From the SBCX, you can successfully ping the IP address of the SDR, that is, the 118 network segment address of the CC board in this example. After you have telneted the cc, you may connect to the RRU by using the rlogin RRU IP command. Make sure that there are quotation marks. The format of the RRU IP is as follows: 200.environment No.0.rack No., for example, 200.254.0.2. #telnet 118.18.2.100 CC->rlogin 200.254.0.2 DTR->******** The execution of this command is equivalent to telneting to the RRU.
20
2 OMCR Data Configuration

Note The data configuration in this chapter is based on Table 1.5-1. [Objective] 1. 2. Set the global resource configuration parameters of the BSC; Complete the Abis interface board and OMCB interface board configuration of the BSC; 3. Complete the IP interface configuration of the Abis interface, OMCB interface, and BSC virtual address; 4. Complete the logical site and radio parameter configuration of the SDR;
[Preliminary Setup] 1. A correct operating system and a correct database, together with the iOMCRV6.20 which consists of the OMCR and OMCB, have been installed. In addition, all of them run normally. 2. The A interface and the Gb interface of the iBSC have been interconnected. Dialing test is normal; 3. The IP address of the SDR site, that of the Abis interface on the BSC, that of the OMCB interface, that of the OMCB server, and the virtual address of the BSC have been planned. The corresponding module number and Abis interface location of the SDR on the BSC have been planned;
2.1 BSC Global Resources Configuration

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 the iOMCRV6.10. 2. Click the icon in the left configuration resource tree window, and select
[OMCGERAN subnetworkBSC management elementConfig SetBSC

21
function]. 3. Double click [BSC function] to pop up the Create BSC function dialog box, as shown in Figure 2.1-1. Click to enter the modification mode. According to the planned addresses, set OMCB IP and IP Abis, as shown in Figure 2.1-1 and Figure 2.1-2. Click OK to finish the creation.
Figure 2.1-1
Setting BSC Global Resource Attributes
22
Chapter 2
Figure 2.1-2
Setting the iBSC Virtual Address
2.2 Abis and OMCB Interface Configuration

When commissioning an SDR, pay attention to the following iBSC configuration: The Abis interface uses the IP mode. If FE is physically used, the Abis interface uses IPBB as the interface board; if E1/T1 is physically used, the Abis interface uses DTB as the interface board. Meantime, EUIP (the physical board is EIPI) must be increased. OMCB network management is provided for the SDR base station. The OMCB server must be accessed to the iBSC by means of IPBB. The IPBB to which the OMCB is accessed and that to which the Abis interface is accessed may be the same board or different boards. About EIPI: 1. Together with DTB, EIPI provides E1-/T1-based IP access. An EIPI board has no external interface or back board. One EIPI board plus two DTB boards can support up to 64 E1/T1 interfaces. 2. After HW data is accessed to an interface unit and undergoes HDLC protocol processing in the 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
23
switching network, the user plane data is sent to the GUP/GUP2 for further processing. By means of the control plane switching network, the control plane data is sent to the CMP for further processing.
2.2.1 Abis Interface Configuration

When the Abis interface uses IPOverE1: 1. Create a DTB board at the Abis interface, and add an Abis interface PCM in the PCM Information tab, as shown in Figure 2.2-1.
Figure 2.2-1 PCM Attribute Configuration
Parameter description: PCM type: Select EUIP when the iBSC is connected with an SDR site in IP OVER E1 mode.
24
Chapter 2
Frame mode: Select the multi-frame format when the iBSC is connected with an SDR site in IP OVER E1 mode. 1. Create an EUIP board. Its attribute configuration is shown in Figure 2.2-2. In HDLC Configuration Information, connect 2MHW inside the EUIP board with E1 of the DTB board at the Abis interface, as shown in Figure 2.2-3:
Figure 2.2-2
Creating Basic Information of EUIP Board
Parameter description: Channel mode: for GE platform channel, select Channel mode 5 (1 GE port for inner); for FE platform channel, select Channel mode 2 (4 FE ports for inner).
25
Figure 2.2-3
HDLC Configuration of the EUIP Board
Parameter description: Hdlc No.: Allocate an HDLC No. to each E1. This HDLC No. needs to be referenced when IP Over E1 is configured. Euip 2MHW No.: It is used to identify the 2MHW No. in the EUIP. DT Unit No.: unit No. of the DTB board in use. DT PCM No.: E1 No. of the DTB board in use. TS Config Information: correspondence 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 The EUIP board and the DTB board must be in the same frame.
26
Chapter 2
Active/standby EUIP is not supported. (because the PPP link platform currently does not support active/standby EUIP). When the Abis interface uses FE When the Abis interface uses FE access mode, there is no need to configure DTB board or EUIP board of the Abis resource frame. You need to configure IPBB interface board of the Abis resource frame, as shown in Figure 2.2-4:
Figure 2.2-4
IPBB Board Configuration in the Case of SDR Access
2.2.2 OMCB Interface Configuration

The configuration method is the same as that of the IPBB board accessed to the FE Abis interface, as shown in Figure 2.2-4. The IPBB board accessed to the OMCB that accessed to the SDR may use different network interfaces of the same board, but both the network interfaces need to be configured with different network segments.
27
2.3 IP Related Configuration

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

1. Click the icon in the left configuration resource tree window. Locate the
current directory to [Config SetBSC functionIP-related config Interface Config]. 2. Right click Interface Config, and select [CreateInterface], as shown in Figure 2.3-1.
Figure 2.3-1
Creating an IP Interface
28
Chapter 2
3.
In the pop-up Interface Information Selection dialog box, select an RPU type to create an IP Abis interface, that is, the iBSC virtual address. For details, see Figure 2.3-2:
Figure 2.3-2
Selecting an RPU Board to Create an IP Abis Interface
Parameter description: Board function type: Select RPU as the board function type of IP ABIS; Module:subsystem:unit:sunit: to be automatically set by the system; 1. Fill in the basic information of the created IP ABIS interface. For details, see Figure 2.3-3:
Figure 2.3-3 29
IP Abis Interface Configuration
Parameter description: Port No.: 1 by default, not the same concept as the port No. of IP Over E1; MAC address: It is a virtual address and there does not exist any network card entity. You may set this address as you like. Make sure that this MAC address does not conflict with that of the EUIP or IPBB; Board function type: RPU; IP address: IP Abis which the background of the iBSC is configured with; Subnet mask: Four digits (that is, 255.255.255.255.) must be masked.
2.3.2 Create IPBB Interface to OMCB

1. Click the icon current in the left configuration resource tree window, and locate the to [Configuration SetBSC Global Resource
directory
IdentityIP-related Configuration Interface Configuration]. 2. Right click Interface Configuration, and select [CreateInterface], as shown in Figure 2.3-1. 3. In the pop-up Interface Information Selection dialog box, select an IPBB type to create an IPBB interface, as shown in Figure 2.3-4:
Figure 2.3-4
Creating the IPBB Interface Accessed to the OMCB
4.
Fill in the basic information of the created IPBB interface, as shown in Figure 2.3-5:
30
Chapter 2
Figure 2.3-5
Configuration of the IPBB Interface Accessed to the OMCB
Parameter description: Port No.: When the IPBB uses an RGE R back card, it provides one external GE port. Select 1 as the port No. here. When the IPBB uses an RMNIC back card, it provides four external FE ports. Select 1, 2, 3 or 4 as the port No. according to the actual connection. MAC address: It can be randomly set within 00-C0-D0-xx-xx-xx, but must be different from the MAC address of any other port. (or set the MAC address as follows: 00-DO-D0-A0- (frame No. slot No. + slot No.)-port No.)???) IP address: address of the IPBB port connected with the OMCB server, to be used as the gateway address from the OMCB server to the SDR. Subnet mask: set 3 digits, that is, 255.255.255.0;
2.3.3 Set E1 Abis Interface

Create an EUIP interface accessed in E1 mode
31
[Operating Procedures] 1. Click the icon current in the left configuration resource tree window, and locate the to [Configuration SetBSC Global Resource
directory
IdentityIP-related ConfigurationInterface Configuration]. 2. Right click Interface Configuration, and select [CreateInterface], as shown in Figure 2.3-1. 3. In the pop-up Interface Information Selection dialog box, select an EUIP type to create an EUIP interface, as shown in Figure 2.3-6:
Figure 2.3-6
Creating the EUIP Interface Accessed to the SDR
4.
Fill in the basic information of the created EUIP interface, as shown in Figure 2.3-7:
32
Chapter 2
Figure 2.3-7
EUIP Interface Configuration
Parameter description: 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: Different IPOE ports must have a unique MAC address. Set the MAC address as follows: 00-DO-D0-A0- (frame No. slot No. + slot No.)-port No.). IP address: address of the base station gateway. It is the real address of the iBSC to the base station. In the same iBSC, different EUIP links should not be in the same network segment. This IP address must be in the same network segment as the SDR. Create IPOverE1 configuration 1. Click the icon in the left configuration resource tree window, and locate the
current directory to [Config SetBSC functionIP related ConfigIPOverE1 Configuration].
33
2.
Right-click
IPOverE1
configuration,
and
select
[CreateIPOverE1
Configuration], as shown in Figure 2.3-8:
Figure 2.3-8
Creating IP Over E1
3.
Set corresponding parameters in the pop-up IPOverE1 configuration interface, as shown in Figure 2.3-9:
34
Chapter 2
Figure 2.3-9
IP Over E1 Parameter Configuration
Parameter description: Port No.: associated with the port No. in the EUIP interface configuration. HDLC No.: associated with the HDLC No. in the EUIP board attribute-HDLC configuration information. Start TS and End TS: timeslot resource used by an E1 link. The default start timeslot and end timeslot are respectively 1 and 31 unless stated otherwise. 4. Click the icon current in the left configuration resource tree window, and locate the to [Config SetBSC functionIP related
directory
ConfigIPOVERE1 ConfigurationIPOverE1 Configuration]. 5. Right-click on the IPOverE1 configuration instance configured in the previous step, and select PPP Configuration, as shown in Figure 2.3-10:
35
Figure 2.3-10
Creating PPP
6.
Set corresponding parameters in the pop-up PPP Parameter Configuration. For details, see Figure 2.3-11:
Figure 2.3-11 PPP Parameter Configuration
Parameter description:
36
Chapter 2
Peer IP: IP address of the base station. Mpno sign: When a site is configured with multiple transmission lines, the ML-PPP protocol will be used. In this case, Mpno is effective. HdrCmpCfginfo sign: effective when PPP is configured with compressed transmission. Keep time and Keep granularity: For example, if the keep alive duration is 25s and the keep alive granularity is 5s, detection frames will be sent once every 25/5=5s. That is, messages will be sent five times within the keep live duration. If no answer information is received for five consecutive times, it indicates that broken link has occurred to the PPP.
2.3.4 Set FE Abis Interface

If the Abis interface uses FE access mode, there is no need to configure an EUIP interface accessed in E1 mode or IPOverE1. You may configure a separate IPBB interface accessed in FE mode as you configure the IPBB interface of the OMCB server. For module, subsystem, unit, and sub-unit, select the IPBB board information of Abis access. The IP address is the real address of the iBSC to an SDR site. Specific procedures are as follows: [Operating Procedures] 1. Click the icon current in the left configuration resource tree window, and locate the to [Configuration SetBSC Global Resource
directory
IdentityIP-related Configuration Interface Configuration]. 2. Right click Interface Configuration, and select [CreateInterface], as shown in Figure 2.3-1. 3. In the pop-up Interface Information Selection dialog box, select an IPBB type to create an IPBB interface. For details, see Figure 2.3-12:
37
Figure 2.3-12
Creating an IPBB Interface Accessed to the OMCB
4.
Fill in the basic information of the created IPBB interface. For details, see.
Figure 2.3-13
Configuration of the IPBB Interface Accessed to the SDR
Parameter description: Port No.: When the IPBB uses an RGE R back card, it provides one external GE port. Select 1 as the port No. here. When the IPBB uses an RMNIC back card, it provides four external FE ports. Select 1, 2, 3, or 4 as the port No. according to actual connection. MAC address: It can be randomly set within 00-C0-D0-xx-xx-xx, but must be different from the MAC address of any other port. (or set the MAC address as follows: 00-DO-D0-A0- (frame No. slot No. + slot No.)-port No.)???) IP address: the address of the IPBB connected with the OMCB server, to be used as the gateway address from the OMCB server to the SDR. Subnet mask: set 3 digits, that is, 255.255.255.0;
38
Chapter 2
2.4 B8200 Configuration on OMCR

[Objective] 1. Complete the logical configuration of an SDR site.
21. Complete the cell configuration and transceiver configuration of the SDR site. [Preliminary Setup] 1. A BSC management NE has been successfully created; its parameters have been set. 2. 3. A BSC board has been correctly configured. IP-related configuration has been correctly completed.
2.4.1 Create Logical Site

[Operating Procedures] 1. Click the icon current directory in the left configuration resource tree window, and locate the to [OMCGERAN subnetworkBSC management
elementConfig SetBSC functionSite Config]. 2. Right-click on the site node, and select [CreateSite], as shown in Figure 2.4-1.
Figure 2.4-1
Creating an SDR site on the OMCR
3.
Click [Site]. The interface as shown in Figure 2.4-2 pops up.
39
Figure 2.4-2
Creating the Configuration Information of an SDR Site on the OMCR
Parameter description: Site ID: It must be consistent with the GSM site No. configured for the OMCB and the LMT. Site type: type of the actually installed BBU. Access type: The SDR uses the IP access mode by default. Bandwidth limit(Kb): bandwidth 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.
2.4.2 Create B8200 Rack

1. Click the icon current directory in the left configuration resource tree window, and locate the to [OMCGERAN subnetworkBSC management
elementConfig SetBSC functionSite Config].

40
Chapter 2
2.
Right-click on the site node, and select [CreateSite Rack], as shown in Figure 2.4-3.
Figure 2.4-3
Creating an SDR Rack on the OMCR
3. In the pop-up [Create Rack] dialog box, click OK to create a corresponding rack. Double-click the site rack node in the left configuration resource tree, and the rack view as shown in Figure 2.4-4 appears.
Figure 2.4-4 41
B8200 Rack on the OMCR
2.4.3 Configure B8200 Cells

elementConfig SetBSC functionSite Config]. 2. Right-click on the site node, and select [CreateCell], as shown in Figure 2.4-5.
Figure 2.4-5
Creating the Cell of an SDR Site on the OMCR
3.
As shown in Figure 2.4-6, set related cell parameters in the Create Cell dialog box, and click OK. BCCH ARFCN(BcchArfcn) can not be modified here, it can only be modified when adding a carrier, as shown in Figure 2.4-9:
42
Chapter 2
Figure 2.4-6
Cell Configuration Information of an SDR site on the OMCR (1)
4.
If users need to configure GPRS or EDGE parameters, they may set Support GPRS (PsSupport) to be Support GPRS in the [Basic params 1] tab. The corresponding page will display, as shown in Figure 2.4-7.
Figure 2.4-7
Cell Configuration Information of an SDR Site on the OMCR (2) 43
2.4.4 Configure B8200 TRX

elementConfig SetBSC functionSite ConfigSite IDCell]. 2. Right-click on the Cell node, and select [CreateTrx], as shown in Figure 2.4-8.
Figure 2.4-8
Creating a Transceiver
3.
Click [Trx], and the interface as shown in Figure 2.4-9 appears. Configure the transceiver according to network optimization planning parameters. Click OK to complete the configuration.
44
Chapter 2
Figure 2.4-9
Transceiver Configuration Information
4.
Configure IP information, input DspMarkSeq and PortNo, as shown in Figure 2.4-10.
Figure 2.4-10
IP Information of the Transceiver
45
Parameter description: Bipb Unit: unit No. of the BIPB board. DspSunit: DSP No. of the BIPB board. DspMarkSeq: Each DSP has 28 DSP mark sequence numbers. The DSP mark sequence numbers of each DSP bear the service of a transceiver. PortNo: The port No. of each transceiver must be unique.
46
3 OMCB Data Configuration

3.1 OMCB-OMCR Server Environment Configuration
To ensure that the OMCB server can establish a link to the foreground SDR, we need to check and modify some configuration files.
3.1.1 Modifying the deploy-030womcb.properties Configuration File (as an OMC User)

1. 2. Log as an omc user on to the OMCB server, Enter the ums-svr\deploy directory: $cd ums-svr\deploy $vi deploy-030womcb.properties
Before the 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
# #
################################################################################ # # 47
# 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-DirectB06C-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-DirectB09C-ftpIP=10.61.56.231 userdefined-zxwomc-common-nodeb-api.OMC-DirectB8912-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-DirectB8812-ftpIP=10.61.56.231 userdefined-zxwomc-common-nodeb-api.OMC-DirectZXSDR_B8200_GU360-ftpIP=10.61.56.231 userdefined-zxwomc-common-nodeb-api.OMC-DirectZXSDR_B8800_GU360-ftpIP=10.61.56.231 userdefined-zxwomc-common-nodeb-api.OMC-DirectZXSDR_B8900_GU360-ftpIP=10.61.56.231 userdefined-zxwomc-common-nodeb-api.OMC-IpoaALL-ftpIP=10.61.56.231 userdefined-zxwomc-common-nodeb-api.OMC-DirectPicoNodeB-ftpIP=10.61.56.231 userdefined-zxwomc-common-nodeb-api.OMC-IpoaPicoNodeB-ftpIP=10.61.56.231
Modify this file according to the type of the SDR managed by this OMCB and the connection mode between the SDR and the BSC.
3.1.2 Modifying FTP-related Configuration Files (as an OMC User)

1. In the FTP port configuration file applied by the OMC-B, the port No. is 21 by default. You must modify this port No. as a value equal to or greater than 1,024: $cd ums-svr\tools\ftpserver\conf $more uep-psl-ftpserver-port.conf ## Ftp server port number FtpServer.server.config.port=21
48
Chapter 3
2.
View the actual port mapping information of the system (as a root user):
3.
Modify the port No. in the uep-psl-ftpserver-port.conf file as a value after the above-mentioned FTP mapping. In this example, the port No. is 21111. After the 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 the FTP port No. of the system: Use vi to modify the value of listen_port in the /etc/vsftpd/vsftpd.conf file as 10021 as a root user does. Make sure that the result is consistent with the following:
5.
Then, modify (also as a root user) the corresponding port of FTP(tcp) in /etc/services as 1111. Make sure that the result is consistent with the following:
3.1.3 Modifying the deploy-default.properties File (as an OMC User)

1. Log as an omc user on to the OMCB server, and enter the ums-svr\deploy directory: $cd ums-svr\deploy
49
2.
Open the deploy-default.properties file. $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 the same as the port configuration of the ftpserver 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.
3.1.4 Starting the OMC-B Server (as an OMC User)

Start (as an omc user) OMCB NM application service in the bin directory. The screen displays that FTP service can be normally started. Enter normal start process as follows:
When the following prompt appears, it indicates that the server has been successfully started:
3.2 SDR Site Physical Data Configuration

Note Please perform configuration operations in the order as described in this chapter. Otherwise, your configuration operations will fail.
50
Chapter 3
[Objective] Configure SDR physical data as planned. [Preliminary Setup] 1. 2. 3. Know about the name, No., and type of each SDR site; Know about physical transmission type (E1/T1 or Ethernet). Know about the corresponding interface location and module No. of each SDR site on the iBSC; 4. Know about the IP address of each SDR base station, that of the iBSC interface which corresponds to each base station, and the IP virtual address of the iBSC; 5. Know about the planned IP address of each site, together with the frequency band of each RRU;
3.2.1 Create SDR Site Management Element

[Operating Procedures] 1. Open Configuration Management. Log in to ISMG server from the client and enter Configuration Management, as shown in Figure 3.2-1.
51
Figure 3.2-1
Entering Configuration Management
2. 1)
Create a GERAN subnet. In the configuration resource tree, right-click on the OMC node, and select [CreateGERAN subnetwork], as shown in Figure 3.2-2.
Figure 3.2-2
Creating a GERAN Subnet (1)
2)
In the pop-up Create GERAN subnetwork dialog box, input User label and Subnetwork ID, and click OK, as shown in Figure 3.2-3.
Figure 3.2-3
Creating a GERAN Subnet (2)
3)
In the configuration resource tree, right-click on the created GERAN subnetwork node, and select [CreateBase Station], as shown in Figure 3.2-4.
52
Chapter 3
Figure 3.2-4
Creating a Base Station Management NE
4)
Input configuration data in the Base Station dialog box according to actual planning, as shown in Figure 3.2-5.
Figure 3.2-5
Configuring Basic Parameters of a Base Station Management NE
53
ManagedElement ID: It should be consistent with the GSM site No. of a base station; ManagedElement IP Address: Input the IP address of the base station used for OMC-B communication; ManagedElement Type: Select ZXSDR B8200 GU360. IPOA: It is used for the IP configuration of the A interface. At present, the A interface seldom uses FE for transmission. Do not configure IPOA. Click OK to finish the creation. Note Management NE Identity and IP Address of Management NE are key data for the interconnection between an SDR base station and an OMCB. You may establish a link with the base station after having set both of them.
3.2.2 Set the Exclusive Operation Right

1. Right-click on the Base Station node, and select [Apply Mutex Right] in the pop-up menu, as shown in Figure 3.2-6:
Figure 3.2-6
Applying for Mutually Exclusive Authority
2.
Click YES in the Information dialog box, as shown in Figure 3.2-7.
54
Chapter 3
Figure 3.2-7 Prompt
3.
After the mutex right application succeeds, the corresponding node will be marked with a green lock, as shown in Figure 3.2-8.
Figure 3.2-8
Obtaining Mutually Exclusive Authority
3.2.3 Create the Site Configuration Set

[Operating Procedures] Right-click on the base station node, and select to create base station config set. Input User Label and use default values for other parameters, as shown in Figure 3.2-9.
Figure 3.2-9
Creating Base Station Configuration Set
3.2.4 Create the Site Physical Parameters

Note Transmission configuration varies with E1/T1 access and FE access. In this section, whether a step is configured in the case of E1/T1 access, FE access, or in any case will be clarified. Please pay attention while reading! [Operating Procedures]
55
1. 1)
Create base station Earth Resource management. Click [Base Station Config SetCreateBase Station Equipment Resource Management], the Base Station Equipment Resource Managememt interface appears, as shown in Figure 3.2-10.
Figure 3.2-10
Creating Base Station Earth Resource Management
Parameter description: Base Station ID: to be filled in as planned; Transmission Medium: input FE or E1 according to actual condition; NTP Server IP Address: input the IP address of an NTP Server. If there is no special NTP server, input the IP address of an OMCB server; Transmission Type: all IP by default; Support SummerTime: make a choice according to an actual area;
56
Chapter 3
Clock Sync mode: default GPS frequency synchronization; Radio Mode: WCDMA, GSM, and WCDMA/GSM, which respectively mean supporting only the WCDMA system, supporting only the GSM system and supporting the W network and G network common-mode; 2. 1) Configure the BBU of a physical rack. Select [Base Station Config SetBase Station Equipment Resource ManagementRack ConfigurationRack 1]. Double click the main rack to pop up the rack block diagram. The CC board at Slot 1 and the SA board at Slot 13 are added by default. Configure boards at corresponding slots according to actual physical configuration. Figure 3.2-11 takes for example the PM board at Slot 14:
Figure 3.2-11
Creating a BBU on the OMCB
2)
Right click Slot 14 to pop up the above dialog box. Select the PM board and click Add. Then click OK to finish the addition. Note: the baseband processing board type of GSM should be consistent with physical selection, that is, a UBPG board. Figure 3.2-12 shows the configured BBU panel.
57
Figure 3.2-12
BBU Panel on the OMCB
3. 1)
Configure the RRU of a physical rack. Select [Base Station Config SetBase Station Equipment Resource Management Rack Configuration Rack 2], and create an RRU, as shown in Figure 3.2-13.
Figure 3.2-13
Creating an RRU Rack on the OMCB
2)
Click the R8860 rack and create a board on the panel, as shown in Figure 3.2-14. DTR-D indicates DCS1800. DTR-E indicates E-GSM 900.
58
Chapter 3
Figure 3.2-14
Creating an RRU Board on the OMCB
4.
Antenna configuration Select [Base Station Configuration SetBase Station Earth Resource ManagementAntenna ConfigurationCreateAntenna Configuration] to add antennas for RRUs. Two feeders come out of each RRU. Select ANT as the antenna type, as shown in Figure 3.2-15:
59
Figure 3.2-15
Creating an RRU Antenna on the OMCB
5.
Rack topology configuration Select [Base Station Configuration SetBase Station Earth Resource ManagementRack ConfigurationRack Topology Configuration] to enter the interface as shown in Figure 3.2-16:
60
Chapter 3
Figure 3.2-16
Creating SDR Rack Topology on the OMCB
Parameter description: Port ID: connected with a board: It refers to the port No. of the FS board connected with an RRU; Child Rack No.: It refers to an RRU rack. Its number starts with 2; Child port ID: It refers to the port through which a lower rack is connected with a higher one; RRU Connection Mode: If there is no cascading, adopt the star connection mode; otherwise, adopt the chain connection mode.
3.3 Transmission Parameters Configuration

Note When creating base station equipment resource, if Transmission Medium is FE, the following Step 2, 3 and 4 are unnecessary; if Transmission Medium is E1, the following Step 1 is unnecessary.
61
The following section will clarify which parameters are configured in the following two cases: FE configuration or E1/T1 configuration. 1. Ethernet configuration It is configured in the case of FE only. Click [Base Station Config SetBase Station Equipment Port Resource Layer
ManagementIUB
TransmissionGlobal
ManagementCreateEthernet] to enter the interface as shown in Figure 3.3-1:
Figure 3.3-1
Ethernet Parameter Configuration
Parameter description: Slot No.: It refers to the CC board location on the BBU (unchangeable); Working Mode: adaptive by default; Link Object: select IPbone for a directly connected site or BTS for a cascaded site; Bandwidth(Kbps): select 100,000k for FE configuration; select 1,984k in the case of E1 configuration.
62
Chapter 3
2.
E1/T1 connection configuration It is configured in the case of E1/T1 only. Right-click [Base Station Config SetBase Station Equipment Resource ManagementIUB TransmissionPhysical Layer Management], and select [CreateE1/T1 Line Configuration] from the pop-up menu. Configure E1/T1 connection in the E1/T1 Link Relative Configuration dialog box, as shown in Figure 3.3-2.
Figure 3.3-2
E1/T1 Connection Configuration
Parameter description: Link Type: select BSC if an SDR base station is connected to the BSC in star mode; select Base Station if an SDR base station is connected with a higher SDR base station in chain mode. E1/T1 Link ID: 0-7 represents the first pair of E1/T1 to the eighth pair of E1/T1 of an SA board; the default value is 0, that is, the first pair of E1/T1; Use the default values for other parameters. 3. High-level Data Link Control (HDLC) configuration
63
It is configured in the case of E1/T1 only. Right-click [Base Station Config SetBase Station Equipment Resource ManagementIUB TransmissionPhysical Layer Management], and select [CreateHigh-Level Data Link Control] from the pop-up menu. Configure HDLC in the High-Level Data Link Control dialog box, as shown in Figure 3.3-3.
Figure 3.3-3
HDLC Configuration
Configure the timeslot used by an SDR base station as planned in Timeslot Mapping Diagram. 4. Point-to-Point Protocol (PPP) configuration It is configured in the case of E1/T1 only. Right-click [Base Station Config SetBase Station Equipment Resource ManagementIUB TransmissionGlobal Port Management]. Select
[CreatePPP Configuration] from the pop-up menu. Configure related

64
Chapter 3
parameters in the PPP Configuration dialog box, as shown in Figure 3.3-4.
Figure 3.3-4 PPP Configuration
Parameter description: Link Type: select HDLC; Bearer Protocol: select PPP; Base Station IP: fill in the planned IP address of the SDR base station. No.: modify the corresponding HDLC Link No. as 0. 5. Qos bandwidth configuration It must be configured whether in the case of E1/T1 or FE. Click [Base Station Config SetBase Station Equipment Resource
ManagementIUB TransmissionGlobal Port ManagementCreateQOS Bandwidth Config]. The QOS Bandwidth Configuration dialog box appears,
65
as shown in Figure 3.3-5.
Figure 3.3-5
QoS Bandwidth Configuration
Parameter description: Rack No.: frame No., and slot No. are used to locate a CC board; Port ID: 0 indicates the port accessed in FE mode; Traffic Quality Priority: 0 by default; Bandwidth of QOS(kbps): to be filled in according to actual transmission bandwidth. 6. Global port configuration It must be configured whether in the case of E1/T1 or FE. Click [Base Station Config SetBase Station Equipment Resource
ManagementIUB TransmissionGlobal Port ManagementCreateGlobal Port Configuration]. The Global Port Configuration dialog box appears, as shown in Figure 3.3-6:
66
Chapter 3
Figure 3.3-6
Global Port Configuration
Parameter description: Port Type: two options: IP Over Ethernet or 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: select 0. VLAN ID: fill in with 65535 if no VLAN is used. 7. IP attribute configuration It must be configured whether in the case of E1/T1 or FE. Select [Base Station Config SetBase Station Equipment Resource Management IUB TransmissionIP/Static Router Layer ManagementIP Parameter Configuration]. The IP parameer Configuration dialog box appears, as shown in Figure 3.3-7:
67
Figure 3.3-7
IP Attribute Configuration
Parameter description: IP Address: fill in with the actually planned value; Subnetwork Mask: fill in with the actually planned value; Gateway Address: fill in with the IP address of the IPBB to the SDR side; Bandwidth(kbps): to be filled in as configured; Radio Mode: GSM; Use default values for other parameters. 8. Static route configuration It must be configured whether in the case of E1/T1 or FE. If SDR and iBSC (virtual address, i.e. the address of an RRU) are not in the same network segment, a static route must be configured. If SDR and iBSC are in the same network segment, there is no need to configure any static route.
68
Chapter 3
9.
SCTP configuration It must be configured whether in the case of E1/T1 or FE. Select [Base Station Config SetBase Station Equipment Resource ManagementIUB TransmissionTransmission Layer
ManagementCreateSCTP Configuration], as shown in Figure 3.3-8.
Figure 3.3-8
SCTP Configuration
Parameter description: Radio Mode: select GSM; No. 0 Local IP Address: fill in with the IP address of an SDR site. Select ineffective for other local addresses. Local Port Number: to be kept consistent with site No.; Remote Port Number: It is 0x3900+CMP module No. In this example, the
69
module No. is 3. If converted into decimal system, the remote port No. is 14595. Remote IP Address: fill in with the planned address of an RPU Use default values for other parameters. 10. OMCB connection It must be configured whether in the case of E1/T1 or FE. Select [Base Station Configuration SetBase Station Earth Resource ManagementIUB Transmission Configuration (all IP)Transmission Layer ManagementCreate OMCB Connection], as shown in Figure 3.3-9:
Figure 3.3-9
OMCB Connection Configuration
Parameter description: Base Station OMC IP Address: select the IP address of a base station by default; Base Station OMC Gateway: fill in with the IP address of an RPU. Use default values for other parameters.
70
Chapter 3
3.4 Clock and Dry Contact Parameters Configuration

1. Clock source priority configuration Select [Base Station Config SetBase Station Equipment Resource ManagementClock Source Priority Configuration]. The Clock Source Priority Configuration dialog box appears, as shown in Figure 3.4-1.
Figure 3.4-1
Clock Source Priority Configuration
Parameter description: External Clock Source ID: only embedded GPS and line clock-this board are supported at present. 2. Environment monitoring and dry contact configuration Configure environment monitoring and dry contact according to actual conditions, as shown in Figure 3.4-2 and Figure 3.4-3. If there is no connection, use the default value.
71
Figure 3.4-2
Creating Environment Monitoring on the OMCB
Figure 3.4-3
Creating Main Contact Point on the OMCB
3.5 Radio Parameters Configuration

1. Central frequency band configuration Select [Base Station Config SetBase Station Radio Resource
ManagementCreateCentral Frequency Config]. The Central Frequency Config dialog box appears, as shown in Figure 3.5-1.
72
Chapter 3
This frequency is the central frequency of downlink frequency band. Because SDR base station is dual-mode, considering the UMTS limit to such sites, the SDR base station can only have 15 MHz bandwidth, that is, 7.5 MHz downlink bandwidth and 7.5 MHz uplink bandwidth. It is recommended to configure the bandwidth as the central frequency band 5 M.
Figure 3.5-1
Configuring Central Frequency on the OMCB
2.
Configure sector parameters Select [Base Station Config SetBase Station Radio Resource
ManagementCreateGSM Sector Parameter Config]. The GSM Sector Parameter Config dialog box appears, as shown in Figure 3.5-2.
73
Figure 3.5-2
Configuring GSM Sector on the OMCB
Sector number corresponds to a physical cell number. GPS Synchronous Frame Header Offset adopts the default value 1. 3. GSM RU parameter configuration Select [Base Station Config SetBase Station Radio Resource
ManagementCreateGSM RU Parameter Config]. Figure 3.5-3 and Figure 3.5-4 show the GSM RU Parameter Config dialog box. Configure radio parameters for the RRU of which the rack No. is 2.
74
Chapter 3
Figure 3.5-3
Configuring GSM RU on the OMCB (1)
75
Figure 3.5-4
Configuring GSM RU on the OMCB (2)
Parameter description: RU Type: to be selected according to the model on the RRU name plate; Static Power Level: to be set as required network optimization; Carrier wave power config parameter: to be configured according to the number of carriers; in fact, Sector 1 is configured with three carriers. The maximum transmission power of an RRU is 60W, so the actual power of each carrier should not exceed 20W. Extended interface: If a cell has only one RRU, select not enable extended interface. If the cell has multiple RRUs, select enable extended interface; Related Radio Rack No.: select Invalidation; Related Radio Shelf No.: select Invalidation; Related Radio Slot No.: select Invalidation.
76
Chapter 3
Note Description of the maximum configuration: Each site of an SDR base station can be configured with up to 24 cells. Each cell can be configured with up to 36TRX. Each site can be configured with up to 60TRX. A BP board can process up to 12 TRXs; a BBU can be configured with up to five BP boards. 4. GSM carrier configuration Select [Base Station Config Set Base Station Radio Resource
ManagementCreateGSM Carrier Wave Parameter Config]. The GSM Carrier Wave Parameter Config dialog box appears, as shown in Figure 3.5-5. Configure carrier for each sector.
Figure 3.5-5
Configuring GSM Carrier on the OMCB
77
Parameter description: Sector Number: select the cell this carrier belongs to; Logical Carrier Frequency Number.: It refers to the configured carrier number; IRC: to be set as required. The default value is not to be used; Channels Mode: to be selected as required. The default value is single channel; Frequency Band: select the actually configured carrier band (select 900 M in this example). Child Frequency Band: select Invalidation.
78
4 LMT Installation, Configuration and Power On Checking

4.1 LMT Introduction
The software packet of the SDR often contains two files: one is the foreground software - software specification package, the other is the debugging software LMT. See Figure 4.1-1.
Figure 4.1-1
External Interface of ZXSDR R8860
4.1.1 LMT Content Introduction

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 use the
LoadTool to load and run it, or test and activate it on the BTS. EOMS_EFMS JRE LMTSetup.exe readme.txt The copy version of the O&M and fault management Java operating environment installation file DMS and PMS installation program executable files Installation program readme file
4.1.2 LMT Installation

Load the JRE in running the LMT. If the JRE is not installed in the debugger, the JRE should be installed under
79
the
LMT
directory.
The
path
is
\.....\BLMT_v4.00.101b2\JRE\jre-6u2-windows-i586-p.exe.
(If
different
LMT
version and the JRE have been installed in the debugger, re-installation is not required.) 1. 1) Install JRE Enter the JRE program directory \BLMT_v4.00.101b2\JRE\, and double-click jre-6u2-windows-i586-p.exe. The installation interface is displayed, as shown in Figure 4.1-2
Figure 4.1-2
JRE Installation Welcome Interface
2)
Click Accept (A) to start the installation. The progress bar is displayed to show the installation status. See the Figure 4.1-3.
80
Chapter 4
LMT Installation, Configuration and Power On Checking
Figure 4.1-3
JRE Installation Progress
3)
Wait for the completion of the Java installation until the interface is displayed, as shown in Figure 4.1-4. Click Finish (F) to end the JRE installation.
Figure 4.1-4
JRE Installation Finish
81
2. 1)
Set the environment variable Right-click My Computer, and select System Properties -> Advanced -> Environment Variables -> Path -> Edit. Add ; after the value of the path environment variable, and then add the installation path of the Jar. The default installation path of the Jar is C:\Program Files\Java\jre1.6.0_02\bin. See Figure 4.1-5.
Figure 4.1-5
Set Environment Variable
2.
Copy the ump file to the root directory of volume C The ump file is required by the old versions of LMT. BLMT_v4.00.101b and higher versions do not need this file, that is, this step can be omitted.
1)
Copy the ump file under \.....\BLMT_v4.00.101b2\EOMS_EFMS to the root directory of volume C.
2)
Change the IP address of this file to the IP address of the active CC board (IP address format: 192.environment variable.slot number.16. The environment number of the CC board is 254 by default). If this file does not exist, you can create a new text file and rename it to ump, and then remove its extension name. See Figure 4.1-6. where, the 192.254.1.16 is the IP address of the CC board (for a CC board with two slots, the IP address should be 192.254.2.16), the admin and nodeblmt are the user name and password for logging in to the LMT, and
82
Chapter 4
the Chinese indicates the language environment.
Figure 4.1-6
Create A ump File
4.1.3 Connection between LMT and SDR

To establish the connection between the debugger and the SDR, you should configure the debugger with an IP address in the network segment of the CC board. BBU board IP calculation Each board on the BBU has a fixed internal IP address, and the address is related to its slot. The format is: 192.environment number.slot number.16 For the slot number of each board, see the red mark in Figure 1.4-1, the environment number is an ID used to identify the SDR in the same network. In a same BSC, different environment numbers should be set for different SDRs. The default environment number is 254 which can be edited by using the following command. It is recommended to use the BS number as the environment number. Telnet to the CC board, and enter BspSetEnvId new environment number to modify the environment number. CC->BspSetEnvId 210 value = 0 =0x0 CC-> When the modification is complete, press Ctrl + x or enter Reboot to reset the CC board. Then, log in with the new environment number. IP configuration of the debugger
83
In debugging, the debugger is connected to the ETH1 interface of the CC board in the SDR by the network cable. To establish the connection between the debugger and the SDR, you should configure the debugger with an IP address in the network segment of the CC board, and this IP address should not be the same as the one in the SDR. To visit all boards in the SDR conveniently, the subnet mask should be 255. 255. 0. 0, with an optional gateway. See Figure 4.1-7.
Figure 4.1-7
Configure the IP Address of the Debugger
Login of the debugger to the SDR 1. Connect the network port of the debugger with the ETH1 interface of the active CC board The CC board can only be inserted in slot 1 or 2 of the BBU. If there is only one CC board, it must be the active CC board. You can just connect the debugger with the ETH1 interface of the CC board by the network cable. If each slot has a CC board, power on and observe the MS indicator. If a MS indicator is on, the
84
Chapter 4
corresponding board is the active CC board which should be connected to the debugger. If you use the LMT to perform the data configuration for the SDR, it is recommended to pull out the standby CC board before the configuration. Insert the standby CC board when the active CC board is configured completely and runs normally. 2. Start the login interface Try to ping the active CC board IP address of the BTS on the debugger. When you confirm the connection between the debugger and the SDR, double click \.....\BLMT_v4.00.101b2\EOMS_EFMS\EOMS.jar to start the LMT. The login interface is shown in Figure 4.1-8.
Figure 4.1-8
LMT Login Interface
3.
Create login site information Click the Station on the login interface. The Add Information of the base station dialog box is displayed as shown in Figure 4.1-9. Input Station Name and Station IP. Station IP indicates the IP address of the CC board that is connected to the debugger by the network cable.
85
Figure 4.1-9
Configure the IP Address of the Debugger
4.
Log in to the BS Create a site, and select a BS. Select Log in to BS (Online Configuration) as the login mode, and click Login. Then, perform the sequent online SDR data configuration. If the LMT cannot log in to the SDR, check whether the debugger can ping the IP of the CC board, and then confirm whether the IP address in the ump file is consistent with that of the CC board to be connected; if the CC board is being reset, the LMT cannot visit it until the CC board is normal.
5.
Prompt in the login process In the login process, the background should communicate with the BS to obtain the dynamic and alarm information. The login process will take about half a minute. Then, the base station configuration interface is displayed. If you can not log in to the SDR, select Offline Configuration in Logging in Type in Figure 4.1-8 to perform the offline data configuration.
4.1.4 Offline Configuration

The online configuration is the most common configuration mode, that is, configure the B8200 foreground ZDB table directly. The data configured in this mode takes effect immediately. The offline configuration is to modify the configuration on the debugger. The configuration result is saved as a XML file under a specified directory. The offline configuration does not need the connection to the foreground B8200, thus does not affect the B8200.
86
Chapter 4
A local configuration file should be specified for the offline configuration. See Figure 4.1-10. The sequent configurations are performed based on this configuration file. Backup the configured data to the debugger, and import the data into the SDR through the online mode as required.
Figure 4.1-10
LMT Offline Login Interface
4.1.5 Configuration Export and Import

The configuration export is to export the B8200 foreground ZDB table in the XML format to a directory of the MLT client. Exporting the configured data in online or offline mode can implement the data backup. You can also import the data to other SDR BSs of the same type, and modify individual data to implement the fast data configuration. Configuration data export When the data is to be exported, select Export Configuration Data from the drop-down menu of System, as shown in Figure 4.1-11, and set the saving path of the exported file.
87
Figure 4.1-11 Exporting Configuration Data
Configuration data import When the data should be imported, select Entire Table Configuration in the drop-down menu of System. Then, select Existing Data. If the original configuration data in the BS should be reserved, backup the data, because the imported data will overwrite the original data. Press OK. A progress bar is displayed to show the loading progress. When the loading is complete, a success prompt dialog box is displayed. No data in SDR Generally, there is configuration data in the SDR by default. If there is no data in the SDR, a prompt dialog box is displayed when the LMT is connected with the SDR. Then, the configuration data should also be imported. Note The BS8200 will be restarted after the entire table configuration.
4.2 SDR Site Configuration on LMT

The ZXSDR is a BS with internal ALL-IP structure. It only supports IP access in the Abis interface, but the physical bearer can be the FE or E1/T1. The LMT configures the BS in steps as shown in the following table. For the E1/T1 access and FE access, their configurations of transmission resources are different to some extent. The differences are marked in bright blue and yellow respectively in the table. The unmarked parts are the common configuration of the E1/T1 and FE.
88
Chapter 4
Table 4.2-1 Step Data Category Step
LMT Configures the SDR Configuration Connection Parameter with BSC GSM site number
Step 1.1 BTS Configuration
Basic property configuration of the BTS Configurations of B8200 board and R8860 rack and board Clock reference source configuration Environment monitoring configuration PA controller configuration Serial port configuration Topology structure configuration Dry contact configuration Configure FE parameters
Step 1
Step 1.2
None
Step 1.3
None
Step 2.1 Ground Step 2 Resource Configuration Step 2.4 Step 2.5 Step 2.2 Step 2.3
None None None None None
Step 3.1
(when the Abis uses the IP transmission) Configure E1/T1 connection
None
Step 3.2
(when the Abis uses the E1/T1 transmission) Configure HDLC channel
None
Step 3.3 Transmission Step 3 Resource Configuration Step 3.4
parameters (when the Abis uses the E1/T1 transmission) Configure PPP parameters (when the Abis uses the E1/T1 transmission)
None
The IP address used by the BTS to access the BTS controller None None Remote IP address and remote port number
Step 3.5 Step 3.6 Step 3.7 Step 3.8 Step 4.1 Radio Step 4 Resource Configuration Step 4.2 Step 4.3 Step 4.4 Step 5 Version Step 5.1 89
Configure global port parameters Configure IP parameters Configure SCTP parameters Configure 0MC-B parameters Configure RF unit central frequency Configure the GSM sectors Configure GSM carriers Configure GSM RU Version Configuration
Cell frequency configuration range None None None None
Step
Data Category Configuration
Step
Configuration
Connection Parameter with BSC
4.2.1 Basic Properties Configuration

Description before the configuration: Currently, the delivery CC data is the configuration of the W BTS by default. The data should be deleted for reconfiguration. Because of the interrelation between the data, the deletion should comply with the descending principle. Otherwise, the existence of next data will cause that the former data cannot be deleted. Configuration Steps: 1. 1) Set basic property Open Set Basic Property menu Right-click Base Station in the configuration interface. The pop-up menu is displayed as shown in Figure 4.2-1. select Configure Basic Attribute.
Figure 4.2-1
Set Basic Property
2)
Set basic parameter
90
Chapter 4
Figure 4.2-2
Basic Parameter of Basic Property
Parameter description: NodeB ID: indicates the site number of the Node B allocated by RNC in WCDMA system. If the B8200 is only used for GSM, use the default value. 3) Set other parameters as shown in Figure 4.2-3 and Figure 4.2-4.
91
Figure 4.2-3
Basic Property Parameters (1)
Figure 4.2-4
Basic Property Parameters (2)
92
Chapter 4
SNTP Server address: it indicates the time server used by the BTS. Write down the actual IP address. When there is no time server, the BTS will start the timing from 2000-1-1 0: 0: 0 automatically. You can set the BTS time manually through LMT. When there is no independent time server, you can fill in the IP address of OMCB. Transmission mode: the physical transmission type of the 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, the ALL-IP transmission is used in the network layer, regardless of the physical transmission type. Power work mode: it is used to set the operation mode of two PMs, that is, 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 PMs are working simultaneously at any time. When one module is faulty, the other will take over all the job and ensure normal operation of the system. The B8200 can operate normally with only one PM. It can support a maximum of two PMs. FS work mode: a maximum of two FS boards can be configured on the BBU. The two FS boards can operate in active/standby mode or load sharing mode. Perform settings according to actual configuration requirement. Radio Mode: it indicates the radio system used for setting the BTS. You can select GSM, WCDMA, or WCDMA/GSM. The selection is determined based on the type of RF unit which is connected to the FS board of the B8200. When all RF units are of GSM system, select GSM; when all RF units are of WCDMA system, select WCDMA; when the RF units are of GSM and WCDMA systems, select WCDMA/GSM. GSM station No.: it indicates the site identification of the GSM allocated by the BSC. It is the planning data which should be consistent with the site ID that is used when the site is configured on the OMCR. This site ID also acts as the SCTP port number that is used when the SCTP connection is established
93
between the B8200 and the BSC. The BBU obtains the radio configuration parameters through the OMCR. If the site ID is configured incorrectly, the BTS cannot obtain the correct radio parameters and access. Transmission medium: it indicates the transmission medium used by the Abis interface. You can select E1, T1, FE, SAT, or Invalid. The E1/T1 indicates the E1/T1 cable, FE indicates Fast Ethernet, SAT indicates Satellite, that is, satellite transmission, and Invalid indicates that the field is invalid. Time zone: set the parameter based on the time zone that the BTS locates in. It is China GMT+8:00 by default. Clock synchronization period: it indicates how often (in hour) the BTS performs the time synchronization with the preset time server of the SNTP Server. Use the default value. Support power-down control: when the power is faulty, the NodeB will disconnect the external boards automatically (including FS UBPG) to spare 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. Therefore, do not select it. 2. Set clock reference source In the maintenance navigation tree interface, right-click Configuration management -> NodeB -> Configure Clock Reference. The Configure Clock Reference dialog box appears. Modify the clock reference source extracted by the BTS in the dialog box. Generally, the site transmission uses the line clock, as shown in Figure 4.2-5. If there are multiple clock sources, set second clock, third clock, and so on.
94
Chapter 4
Figure 4.2-5
Set Clock Reference Source
3.
Set the 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 the BTS time, uncheck the option Query BTS Time. Then, the date and time are 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 the SDR time through the OMCB.
4.2.2 Physical Parameters Configuration

1. 1) Configure the main rack 1 (BBU) Add board Double-click Main Rack 1. The BBU configuration interface appears. Add the board based on the actual configuration (it is recommended to insert the FS board into slot 3, because the FS board can not be inserted into slot 4 in old versions). To add a board, right-click on the corresponding slot and select Add Board, and then select the board type on the pop-up interface. See Figure 4.2-7 for the example of adding a UBPG board in slot 6.
95
Figure 4.2-6
UBPG Board Configured with the BBU
Note Both slot 1 and 2 on the main rack 1 are configured with a CC board that cannot be deleted by the LMT (but can be deleted from the OMCB). If one of the slots has no CC board, the BTS can still run normally. Check the board status 2) After adding the board, learn whether there is alarm on the board. Right-click on the board and select Board Status Legend. The board prompt is displayed. 3. 1) Configure the remote rack (RRU) Add rack Right-click BTS and select Add Rack. The Add RRU rack dialog box appears.
96
Chapter 4
Figure 4.2-7
Add RRU Rack
Parameter description: RRU Shelf Type: R8840 indicates the WCDMA FR unit, while R8860 indicates the shared RF unit of the WCDMA and GSM. In this example, select R8860 according to the actual hardware configuration. Rack Name: Write down the name according the planning. It is recommended to use a simple name, such as G2_1 which indicates the first RRU of the second cell in the GSM site. 2) Add antenna Click and confirm. The RRU rack interface is displayed. Add two antennas and a DTR board on this interface. Figure 4.2-10 shows the operation interface.
97
Figure 4.2-8
Add the Antenna of RRU Rack
Parameter description: Board Type: you can select ANT which indicates the common antenna, or RET which indicates the EDT. Select based on the actual antenna type. This parameter is not related to the WCDMA or GSM system. Other parameters will be extracted by the system automatically according to the clicking position. The creation method of the second antenna is the same. 2) Add carrier
98
Chapter 4
Figure 4.2-9
Add the DTR of the RRU
Parameter description: DTR-C indicates the carrier of the GSM900 DTR-D indicates the carrier of the DCS900 DTR-E indicates the carrier of the E-GSM900 3) Completed RRU configuration The configured remote rack is shown in Figure 4.2-12, and the DTR is configured to be the GSM900 (DTR-C).
99
Figure 4.2-10
Configured RRU Rack
4. 1)
Configure the topology structure Open the topology configuration When the RRU configuration is complete, double-click Topology under Ground Resource Management in the left Maintain navigation tree. The topology structure interface is displayed as shown in Figure 4.2-11. Right-click on the interface and select Add. Then, you can configure the topology relation between racks.
100
Chapter 4
Figure 4.2-11
Topology Structure Interface
4)
Add a topology relation Configure the connection between the BBU and the RRU, or between RRUs as needed. The configuration in the following figure is to connect the port 0 (LC1) of rack 3 (RRU) to the port 0 (TX0/RX0) of slot 3 (FS board) on rack 1 (BBU).
101
Figure 4.2-12
Topology Structure Settings
Parameter description: Higher level/Lower level: in the star connection, the BBU is the higher level, RRU the lower level; in the chain connection, the RRU near the BBU is the higher level, the RRU far from the BBU is the lower level. port ID: each FS board of the BBU provides six fiber interfaces to be connected to the RRU. The optical interfaces on the front panel of the FS board are numbered 0, 1, 2, 3, 4, 5 from left to right; the RRU provides two fiber interfaces through the DTR board: LC1 and LC2. The LC1 is used to connect the BBU or upper-level RRU, while the LC2 is used to cascade to the lower-level RRU. Topology Type: Star indicates that the RRU is connected to the BBU directly, while Chain indicates multiple cascaded RRU. 5) Add more topology relations By using the above method, add the configuration data of topology for each pair of BBU and RRU or each pair of RRUs which are directly connected with each other. After configuring the rack and topology structure, you should configure
102
Chapter 4
the transmission resources of the Abis interface.
4.2.3 Transmission Parameters Configuration

Note the transmission configuration for E1/T1 access is different from that for FE access. Note that each step in this section will declare that whether this step is configured for E1/T1, FE, or both E1/T1 and FE. Description before the 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. If the OMCB parameter table is configured, then after the connection between SDR and iBSC is established, no modification is allowed on the LMT. It is recommended not to configure the OMCB parameter table during the debugging phase. Configuration procedure 1. E1/T1 cable It is configured only for E1/T1 access. In the left window of the 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 4.2-13.
103
Figure 4.2-13
E1/T1 Connection Management
Parameter description Board Name: it indicates the board from which the SDR accesses the E1/T1. For the B8200, although the E1/T1 is accessed physically from the SA board, the SA board performs no operation over the E1/T1. The co-team handling is completed by the CC board, therefore, the E1/T1 is accessed logically from the CC board. Thus, the board here is CC by default, and it cannot be edited. Link ID: it indicates the pair of E1 lines to be used. The SA board introduces eight pairs of E1 lines which correspond to links ranging from 0 to 7. In the figure, the link ID of the E1 line is 0, that is, use the first pair of E1 lines (No.1 and No.2 E1 lines). The link ID configured in this step will be referenced later in the HDLC channel parameter configuration. The E1 link used by a HDLC channel is identified by the link ID of this E1 link. Link type: it indicates the remote equipment type to which the E1 link is connected. Select BSC for the GSM network. Note Make sure that you have set the transmission medium to E1 or T1 in the Other
104
Chapter 4
parameters tab in the Configure Basic Attribute dialog box; oherwise, the E1/T1 cable can not be added. 3. Ethernet Parameters This option is configured only for FE/GE access. Click Transmission Resource -> IP Bearing Configuration -> Ethernet Parameter, right-click at the blank area on the right, and select Add. The configuration interface of Ethernet parameters is displayed, as shown in Figure 4.2-14 .
Figure 4.2-14
Ethernet Parameter Configuration
Parameter description Board Name: select the board where the IP interface of the Abis locates. Currently, you can only select CC for the GSM. Ethernet port ID: currently, you can only select 0 from the drop-down box. Working mode: it indicates the operation mode of the Abis interface, that is, duplex or rate. There are six options. Generally, Adaptive is selected by default. Connection object: it indicates the equipment to which the Abis interface is
105
connected directly. You can select IPbone or BTS. When the SDR is connected to the BSC directly, select IPbone; when the SDR is cascaded to the upper level BTS, select BTS. Configured bandwidth(kbps): it indicates the total bandwidth (unit: kbps) of the Abis interface. This parameter sets the upper limit of available total transmission bandwidth of the Abis interface of the BTS. The value can not exceed the physical processing capability of the interface. A BTS can be configured with multiple IP addresses, and it supports the setting of available bandwidths for different IP address. Therefore, the total bandwidth used by all IP addresses in one BTS can not exceed the configured value. 4. HDLC parameters This option is configured only for E1/T1 access. In the left window of the LMT, select Maintain navigation Tree -> Configuration management -> Transmission Resource -> IP Bearing Configuration -> HDLC Parameter. Then, right-click in the HDLC Parameter window on the right to add a message, as shown in Figure 4.2-15.
Figure 4.2-15
HDLC Parameter Configuration
106
Chapter 4
Parameter description: HDLC ID: it indicates the ID of the HDLC, 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 a HDLC. The HDLC ID configured in this step will be referenced later in the PPP parameter configuration. Bearing type: select E1. Link ID No.: it indicates the ID of the E1 link where the HDLC channel locates, that is, the link number configured in E1/T1 connection. If you add link 0 and link 1 in E1/T1 connection configuration, there will be two options here: 0, 1. TS-bit mapping relation: it indicates the ID of the E1 timeslot occupied by the HDLC channel. A HDLC channel uses 1 - 31 timeslots 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 used for synchronization. 5. PPP parameters This option is configured only for E1/T1 access. In the left window of the LMT, select Maintain navigation Tree -> Configuration management -> Transmission Resource -> IP Bearing
Configuration -> PPP Parameter. Then, right-click in the PPP Parameter window on the right to add a message. Figure 4.2-16, Figure 4.2-17, and Figure 4.2-18 show parameter details..
107
Figure 4.2-16 PPP Parameter Management (1)
108
Chapter 4
Parameter description PPP ID: it indicates the ID of the PPP, 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 needs no modification. Bear protocoltype: when the SDR is connected to the BSC/RNC through a pair of E1 lines, select PPP; when the SDR is connected to the BSC/RNC through two pairs of E1 lines, select ML-PPP (MultiLink-PPP). MP header style: 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 to Long Sequence Number or Short Sequence Number, this parameter can be set (1 by default); when the MP header format is invalid, this parameter is also invalid (255 by default). Link ID No.: Link 0, Link 1, Link 2, etc. are used to set the HDLC channel
109
(HDLC ID) used by the PPP link respectively. When Bear protocoltype is set to PPP, only link 0 is valid; when Bear protocoltype is set to ML-PPP, you can select multiple links according to the planning, as shown in Figure 4.2-19.
Parameter description Base Station IP: it indicates the IP address that the SDR uses to communicate with the iBSC. Note that this address is the external address of the SDR. Do not set it to 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 the SDR are accessed by using the 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 the iBSC. Quality protocolType: it is not supported currently. Authorize: it indicates whether the user authentication is required, including the PAP and CHAP protocols. It is not required here. Support IP compress: it indicates whether to support the IP compression or not. Configure the compression parameters when the IP/UDP header compression is
110
Chapter 4
used. The maximum value of NONTCP CID is set to 512. Others can use the default value. Select No unless specified otherwise. 6. Global Port Parameters This option should be configured for both E1/T1 and FE accesses. Click Transmission Resource -> IP Bearing Configuration -> Global Port Parameter, right-click at the blank area on the right, and select Add. The configuration interface of global port parameters is displayed.
Figure 4.2-20
Configuring Global Port Parameters
Parameter description: Global Port ID: it is generated automatically, starting with 1. Working mode: it indicates the mode of IP bearer (data link layer protocol): Ethernet/PPP. When the data link layer uses the PPP encapsulation, select IP over PPP, when the data link layer uses the Ethernet encapsulation, select IP over Ethernet. Port ID of link layer: it indicates the port number used in the BTS protocol stack subsystem. For example, the PPP uses No. 3 - No. 34 global ports that
111
corresponds to No. 0 - No. 31 link layer ports. This parameter is generated by the system automatically, and needs no modification. Using VLAN: it is not selected currently. Vlan ID: when the Using VLAN is selected, this parameter is valid. Its value ranges from 2 - 4094. This parameter is invalid when the value is 65535. 7. IP parameters This option should be configured for both E1/T1 and FE accesses. Click Transmission Resource -> IP Bearing Configuration -> IP Parameter, right-click at the blank area on the right, and select Add. The configuration interface of IP parameters is displayed.
Figure 4.2-21
IP Property Configuration
Parameter description IP ID: it indicates the ID of the IP used by the protocol stack. IP Address: it indicates the IP that the BTS uses to access the BTS controller. It is in grey and is not editable.
112
Chapter 4
subnet mask: this parameter is in grey and is not editable. Gateway address: it indicates the IP address of the IPPB of the BTS controller. 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 the BSC data. Configured bandwidth(kbps): it indicates the available bandwidth of the current IP (a SDR BTS can be configured with multiple IP addresses). The bandwidth configured in FE parameters is the total bandwidth of the SDR BTS. For E1 access, it can be set to N*1984. N indicates the number of the E1 lines (the 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). Class of Service: 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 the 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 the BTS IP address configured in PPP Parameter Management. It is the bandwidth to be set here. 8. SCTP parameters This option should be configured for both E1/T1 and FE accesses. The configurations of E1, T1, and Ethernet are the same on the transmission layer. The 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 Resource -> IP Bearing Configuration -> SCTP Parameter, right-click at the blank area on the right, and select Add. The configuration interface of SCTP parameters is displayed, as shown in Figure
113
4.2-22 and Figure 4.2-23.
Figure 4.2-22
SCTP Parameter Management (1)
Parameter description Association ID: it indicates the unique identification of the association in the BTS. It is 0 by default. Radio Mode: select GSM for the GSM network. Local IP address: select the local IP address from the IP address list configured in IP Parameters. It indicates the IP address that the BTS uses to establish the connection with the IBSC. You can just select the actual IP address that the BTS uses to access the IBSC. Local port ID: it indicates the port number that the BTS uses to establish the SCTP connection with the IBSC. Its value ranges from 1 to 1536. This port ID is the SITE_ID used in layer 3, that is, the 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 basic property
114
Chapter 4
parameters of the BTS.
Figure 4.2-23
SCTP Parameters Management (2)
Remote port ID: it indicates the SCTP port ID used by the iBSC. specifically, it is the port ID that is used to establish the SCTP connection between the IBSC and the BTS. This port ID can be calculated based on the following algorithm on the IBSC: The value of remote port ID = 0 x 3900 + the CMP module number belongs to the local BTS. Where, the OMP module number is 1, while the RPU module number is 2. Currently, one iBSC can support a maximum of three pairs of active/standby CMPs. Each CMP has two modules. The module numbers are 3, 4, 5, 6, 7, and 8, corresponding to the corresponding remote port IDs 14595 - 14600. For an office where the OMP and CMP are combined (such as single-frame or dual-frame office), the 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 the IBSC. The IP address configured on the IBSC for the BTS to access must be consistent with the IPAbis virtual address configured by the IBSC.
115
Number of streams: it is 6 by default. QoS: Select EF Service. Maximum number of data retransmission: use default value. 9. OMCB parameters This option should be configured for both E1/T1 and FE accesses. Click Transmission Resource -> IP Bearing Configuration -> OMCB Parameters, right-click at the blank area on the right, and select Add. The configuration interface of OMCB parameters is displayed, as shown in Figure 4.2-24.
Figure 4.2-24
OMCB Parameters
Parameter description Base station inner IP: It is configured by default, and is not editable. RNC operation and maintenance IP: it indicates the Abis interface virtual address of the IBSC, instead of the port address of the OMCB access board IPBB.
116
Chapter 4
QoS: Select EF Service(0xB8).
4.2.4 Radio Parameters 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 the 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, note that the 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 Wireless Resource Managment -> RF Unit Central Frequency Configuration, right-click at the blank area on the right, and select Add. The RF unit central frequency configuration interface is displayed. See Figure 4.2-25.
117
Figure 4.2-25
RF Unit Central Frequency Configuration
Parameter description Board Name: It indicates an RRU board. Radio Mode: Select GSM, WCDMA or WCDMA/GSM according to the radio system of the BTS. Father Frequency: Select a proper band from the drop-down box based on the RRU hardware type which can be identified by the delivery nameplate. Centre Frequency: It indicates the downlink central frequency. Because the bandwidth of the current RRU version is limited within 15 MHz, that is, it can receive signals within the range of the central frequency 7.5 MHz (it is not guaranteed to receive the out-band signals). Therefore, note that the 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 The GSM sectors, GSM RU, and GSM carriers are configured in Wireless Resource Management.
118
Chapter 4
1)
GSM sectors This step is used to configure the logical and physical cells of the site. The sector number indicates the logical cell ID. The sector numbers configured here are the base of the sector numbers in the GSM carriers. The sector numbers in the following GSM carriers is selected based on these sector numbers. The GSM sectors configured here should corresponds to the cell numbers under the BTS in the 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, as shown in Figure 4.2-26.
Figure 4.2-26
GSM Sector Configuration
Parameter description Sector ID: 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
119
currently. You can configure this parameter freely). It reflects the relation between the physical cell number and the sector number. GPS Synchronized Frame Header Offset: set it by default if the GPS is not used. Figure 4.4-29 shows the configured GSM sectors.
Figure 4.2-27
Configured GSM Cells
2)
GSM RU The number of carriers configured for the RU is related to the configurations of the GSM sectors and GSM carriers. For the configuration interface, see Figure 4.2-28 and Figure 4.2-29.
120
Chapter 4
Figure 4.2-28
GSM RU Configuration (1)
Figure 4.2-29
GSM RU Configuration (2)
Parameter description
121
Sector ID: it indicates the number of a sector configured in Configure GSM Sectors. All configured GSM sectors will be displayed in the drop-down box 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. Carrier Number: it is determined based on the RU type and the planning. The RU60 supports a maximum of six carriers, while the 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: the static power of carriers can be divided into 10 levels. This parameter is configured based on the network planning. Receive Passage Attenuation: it uses default value. RF Extended Port: when a cell has multiple RRUs, use the RF extension; when a cell has only one RRU, do not use the RF extension, that is, use the independent operation mode. 3) GSM carriers Click Wireless Resource Management -> GSM Carrier, right-click at the blank area on the right, and select Add. The GSM Carrier dialog box is displayed. Add carriers for the sector according to the number of carriers in the sector configured in the GSM RU.
122
Chapter 4
Figure 4.2-30
GSM Carrier Configuration
Parameter description Sector ID: it indicates the logical sector number that is consistent with the cell ID configured on the 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 ID: it indicates the logical carrier number in the selected sector. The number corresponds to the transceiver number configured under the cell of the BTS on the iOMCR. BCCH Carrier Frequency Or Not: 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 Or Not: it indicates that 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, i.e. OTSR. Dual Channel Mode indicates the
123
four-diversity receiving. Carrier Number: this parameter is related to the combined operation mode. It indicates the number of physical carriers that the logical carrier needs the support of. For the 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, user can set the number manually. Father Frequency: it indicates the actual operation band of the carrier. Sub 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 the iOMCR.
4.3 Software Uploading

All SDR versions are loaded in specification package from the LMT. If the connection is established with the iBSC, you can load the version from the OMCB. Figure 4.3-1 shows the software version loading interface.
124
Chapter 4
Figure 4.3-1
LMT Software Version Management
The basic procedure of the version loading is as follows: 1. 2. 3. Click Archive to put a specification package into the LMT. Click Load to load the specification package to the foreground. 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.
4.4 SDR Site Power on and Checking

4.4.1 Power on Checking Criteria
On rack 1 of the LMT (BBU), there is no alarms on the 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
125
time check failure besides these alarms. There is no alarm on the FS board and the UBPG board (The board state indicator is green. There is no alarm on the RRU either (The board state indicator is green). All the boards (including the 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 the boards (including the RRU) and the master CC link board, perform the following operation: Telnet to the CC, and the enter the OSS_DbgShowComm command. The following information is displayed (the CC board is configured in slot 1; the FS board is configured in slot 3; the 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 work 0(0 1 0 1) L 0 0(0 1 0 1) R 1(3 1 0 1) L 1(3 1 0 1) R 2(1 1 0 1) L 2(1 1 0 1) R 3(17 1 0 1) L 3(17 1 0 1) R 4(16 1 0 1) L 4(16 1 0 1) R 5(15 1 0 1) L 5(15 1 0 1) R GroupTable: 127,255, value = 2 = 0x2
state 0 3 3 0 3 0 3 0 3 0 3 0
IP(hex) c0fe0110 c0fe0210 c0fe0510 ffffffff c0fe0310 ffffffff c8fe0004 ffffffff c8fe0003 ffffffff c8fe0002 ffffffff
mac 00:00:00:00:00:00
sndQ 0 0 0 0 0 0 0 0 0 0 0 0
bufQ 0 0 0 0 0 0 0 0 0 0 0 0
udpQ 0 0 0 0 0 0 0 0 0 0 0 0
00:00:00:00:00:00 00:00:00:00:00:00 00:00:00:00:00:00 00:00:00:00:00:00 00:00:00:00:00:00 00:00:00:00:00:00 00:00:00:00:00:00 00:00:00:00:00:00 00:00:00:00:00:00 00:00:00:00:00:00 00:00:00:00:00:00
0 0 0 0 0 0 0 0 0 0 0
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.
4.4.2 Site Information Confirmation

1. Confirm the version of the SDR specification package. Telnet to the CC, and then enter ShowBMCVersion. Then, the 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 the EPLD version of the RRU. Telnet to the RRU, and enter d 0x0e001020. The printed data is October 7, 2008
126
Chapter 4
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 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 the versions of the CPU, DSP, and FPGA. Telnet to the RRU, and then enter the svi command. The Main CPU Version (CPU), Main FPGA Version (FPGA), and Main IFFPGA Version (DSP) are the required versions (For the 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: Header Version = 0x1010101 Versin Type = 0 Cpu Type = 37 Compressed Size = 950694 Original Size = 3908697 Soft Type = 208 Version Number = 8.11.070e Create Time = 2008-11- 7 9: 9:23 Main FPGA Version: Header Version = 0x1010101 Versin Type = 1 Cpu Type = 0
127
* ....(..........* *................* *................* *................* *................* *................* *................* *................* *................* *................* *................* *DTR_a01.1.......* *................* *................* *................* *................*
Compressed Size = 2671144 Original Size = 2671144 Soft Type = 65744 Version Number = 4.00.100b Create Time = 2008-12- 3 4:18:13 Slave FPGA Version: Header Version = 0x1010101 Versin Type = 1 Cpu Type = 0 Compressed Size = 922995 Original Size = 1193707 Soft Type = 65744 Version Number = 8.11.030a Create Time = 2008-11- 3 9:35:24 Main IFFPGA Version: Header Version = 0x1010101 Versin Type = 8 Cpu Type = 0 Compressed Size = 81374 Original Size = 81374 Soft Type = 524496 Version Number = 4.00.100b Create Time = 2008-12- 3 4:18: 9 Slave IFFPGA Version: Header Version = 0x1010101 Versin Type = 8 Cpu Type = 0 Compressed Size = 87228 Original Size = 87228 Soft Type = 524496 Version Number = 4.00.100a Create Time = 2008-10-31 15: 3:18 value = 20 = 0x14
4.4.3 Common Problems and Handling

1. If there is an Optical Port Signal Loss alarm on the FS board, confirm whether the optical modules on the FS board and at the RRU side are faulty or the RRU is powered on. If the optical modules are normal and the RRU is powered on, then the problem is the fiber. 2. If there is an Optical Port Frame Loss alarm on the RRU, change the optical module at the RRU side to make an attempt. 3. If there is a Calibration File Loss alarm on the RRU, Ftp to the RRU, and put the lost calibration file to the RRU manually. If the file does not exist, obtain it from the normal RRU.
128
Chapter 4
4.
When there are application monitoring alarm and board communication link disconnection alarm on the RRU, it is likely that the RRU is not powered on if the fiber and optical module are in good condition. Connect the RMB board converting from the serial port to the network interface to the ALM interface of the RRU, and then telnet to 199.33.33.33 and query the current operation of the RRU by running the hr command, or perform the following operations to put the DSP, CPU, and FPGA versions of the 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 the RRU is unsuccessfully, delete cur.swv, enter the bin command, and put the three versions manually again.
4.4.4 Site Quick Setting Methods

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 the BTS data. The export and import methods of the configuration data are described in 4.1.5. The following only describes the data to be modified after import. 1. Site number of the BTS. Modify the site number.
129
Figure 4.4-1
Data to Be Modified After Configuration Data Imported Site Number
2. 3.
Topology structure. Adjust the structure as needed. PPP parameters. Adjust the parameters according to actual requirement.
Figure 4.4-2
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.
130
Chapter 4
Figure 4.4-3
Alarm Information Query
5.
Adjust paramters, such as RF Central Frequency, GSM Sector, GSM RU, and GSM Carrier, according to the planning.
131
5 Commissioning and Testing

5.1 System Data Transmission and Synchronization
5.1.1 System Software Transmission
When the configuration is complete, the configuration data is saved on the OMC-B background server. To make the data take effect, send it to the BS in the foreground through entire 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 BS will be restarted in the entire table synchronization.
5.1.2 System Data Synchronization

If the created SDR site is already configured by the 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 the BS management NE will be switched to connection status. At this time, you can configure the data through the OMCB and synchronize the data with the foreground, or transconfigure the data configured in the foreground to the background. 1. On the site, right-click the site node to start the BTS Data Configuration Wizard (SDR). Select to use foreground data for configuration, and then click Next. In the parallel data upload tab displayed, select the NE to be transconfigured. 2. If the link between OMCB and BTS is normal, the Parallelly Online Upload Data Result interface appears. User can check Switch to Master in the interface to make the configuration exported from the LMT servers as the active configuration. Click OK. The configuration is exported. The LMT configuration is transconfigured.
133
5.2 Circuit Service Testing

5.2.1 Test Preparations
1. 2. 3. The iBSC equipment is subscribed and normal. The core network equipment is subscribed and normal. Prepare two cellular phones ( A and B) and related fittings, and two SIM cards which can be used in the local network. 4. The LAC, CI, and frequency of the BS are confirmed consistent with the planning data and the background data. 5. 6. Obtain the frequency planning table for all cells of the BS. The calling uses the first party release mode (at the handover side).
5.2.2 Test Purpose

It is to confirm that the CS domain service is normal.
5.2.3 Test Procedure

1. 2. 3. Select a cell to be tested. Use A to lock the BCCH frequency of the cell. 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 above calling steps. A hooks on normally. 5. 6. Use A to lock other frequencies of the cell. Repeat steps 1 5 to test other cells of the SDR BS until all cells of the SDR BS are tested.
5.3 Packet Service Testing

5.3.1 Test Preparations
1. A ftp server is prepared for access and runs normally.
134
Chapter 5
Commissioning and Testing
2.
Prepare a cellular phone to test GPRS/EDGE service and a SIM card that have subscribed the PS service function.
3. 4.
FTP tool software, such as CuteFTP and LeapFTP, is installed on the PC. Account information is already set in the cellular phone, including APN, username, password, and IP address.
5.
The PC and the cellular phone meet the connection conditions, including the data line, Bluetooth, and infrared transmission.
5.3.2 Test Purpose

It is to confirm that the GPRS/EGDE data service of the BTS is normal through FTP.
5.3.3 Test Procedure

1. Connect the cellular phone to the PC through a data line, Bluetooth, or infrared transmission. 2. Install the driver of the cellular phone Modem on the PC to ensure that the 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. 5. Click to create a new dial-up connection to perform dial-up connection. When the dial-up connection is successful, open the FTP tool software on the PC. 6. In the FTP tool software, enter the IP, username, and password of the FTP server to log into the FTP server. 7. Download a file from the FTP server to the PC. The size of the file 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 the PC to the FTP server. The size of the file must be greater 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.
135
5.3.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 the GGSN connection. The Operator ID defines the PLMN GPRS network that contains the GGSN. In the FTP test of GPRS test, APN, username, password, and IP address are provided by the network operator. When the MS originates PDP context activation, the SGSN organizes the complete APN using the network ID and operator ID, and then obtains the IP address of the GGSN corresponding to the APN through DNS resolution.
136
Appendix A Abbreviation Table

Abbreviation A AFS AGND AHS ANT B BBU BCCH BNC BSC BSS BTS C CIB CM CPRI CS CTU D DCHP DCMM DDT DFCA DGND DPCT DTX E EDGE EFS EGSM900 F FAQ FCLK FPGA Frequently Asked Questions Frame Clock Field Programmable Gate Array 137 Enhanced Data Rates for GSM Evolution Enhanced Full Rate Speech Enhanced Global System for Mobile Communications Dual -carrier Channel Processor Dual -carrier Controller & Maintenance Module Delay Diversity Transmission Dynamic Frequency and Channel Allocation Digital Ground Dual Power Combining Transmission Discontinuous Transmission CTU Interface Board Configuration Management Common Public Radio Interface Control & Switch Board Control Translation Unit Base Band Unit Broadcast Control Channel Bayonet Nut Connector Base Station Controller Base Station Subsystem Base Transceiver Station Adaptive Full-Rate Speech Analog Ground Adaptive Half-Rate Speech Antenna Full Name
FS G GERAN GMSK GND GPRS GSM H HDLC HEATER HSDPA HSUPA HW I IP IRC L LAPD LAPDm LAU LMT LNA LTE LVDS M MAC MM MMI MS MTBF MTTR O OAM P PA PBCCH PC PCM PDH PDM
Fiber Switch Board
GSM/EDGE Radio Access Network Gaussian Filtered Minimum Shifting Keying Ground General Packet Radio Service Global System for Mobile Communications
High Level Data Link Controller Heater High Speed Downlink Packet Access High Speed Uplink Packet Access High Way Line
Internet Protocol Interference Rejection Combining
Link Access Procedure on the D-channel Link Access Procedure Dm (mobile D) Channel Low noise Amplifier Unit Local Maintenance Terminal Low Noise Amplifier Long Term Evolution Low Voltage Differential Signal
Media Access Control Mobility Management Man-Machine Interface Mobile Station Mean Time Between Failures Mean Time To Repair
Operation/Administration & Maintenance
Power Amplifier Packet Broadcast Control Channel Personal Computer Pulse Code Modulation Plesiochronous Digital Hierarchy Power Distribution Module 138
Appendix A
Abbreviation Table
PE PGND PLMN PRACH PS PTCCH PWR R RLC RR RRU RST RX RXD S SDCCH SDH SDR SWR SYNC T TA TCH TDM TDMA TRAU TRX TS TX V VSWR
Protective Earth Protective Ground Public Land Mobile Network Packet Random Access Channel Packet Switch Packet Timing advance Control Channel Power
Radio Link Control Radio Resource management Remote Radio Unit Reset Receiver Receiver for diversity
Separate Dedicated Control Channel Synchronous Digital Hierarchy Software Defined Radio Standing Wave Ratio Synchronous Communication
Tower Amplifier Traffic Channel Time Division Multiplexing Time Division Multiple Access Transcoding and Rate Adaptation Unit Transceiver Board Time Slot Transmitter
Voltage Standing Wave Ratio
139

GSM-BSS - II - 07 - 200909 ZXSDR Series Base Station Configuration and Commissioning 145

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

GSM-BSS - II - 07 - 200909 ZXSDR Series Base Station Configuration and Commissioning 145

Hochgeladen von

Copyright:

Verfügbare Formate

ZTE GSM-BSS Products After-Sales Competency Certification Training Manual

ZXSDR Series Base Station Configuration and Commissioning

ZXSDR Series Base Station Commissioning Manual

Separation of the BBU and the RRU

ZXSDR Series Base Station Commissioning Manual

Network Management Structure of the ZXSDR BTSs

1.1.3 IP Abis Interface

Router Switch PCM/X.25/DDN.. . Router

Using FE/GE on Abis Interface

1.2 Commissioning Procedure

ZXSDR Series Base Station Commissioning Manual

BSC Installation Commissioning

OMCR Data Configuration

Local Commissioning of LMT

OMCB Data Configuration

Installation & Configuration Check

Synchronize Data on Foreground and Background

Debugging Process of the ZXSDR BTS

ZXSDR Series Base Station Commissioning Manual

1.3 Software, Documentation and Data Collection

http://support.zte.com.cn to download all the required versions.

1.3.2 Preparing Documents

1.3.3 Preparing the Configuration Data

Site Information of SDR Field Trial.xls

ZXSDR Series Base Station Commissioning Manual

1.4 Hardware Installation Checking

Front Panel of B8200 (Slot Numbers Are Marked in Red)

Jumpers on the SA Board

ZXSDR Series Base Station Commissioning Manual

[Open, shorted] [Open, open]

E1, 120 E1, 75 (default)

1.4.2 Powering On or Powering Off the Equipment

ZXSDR Series Base Station Commissioning Manual

Pass Fail Pass Fail Pass Fail Pass Fail

Pass Fail Pass Fail Pass Fail Pass Fail

Item connections of LMT CC board.

Requirements and Criteria

Pass Fail Pass Fail Pass Fail Pass Fail

1.5 OMC Environment Setting

1.5.2 When an Abis Interface Uses Ethernet as the Bearer

ZXSDR Series Base Station Commissioning Manual

OMC-B link end-to-end communication

Ethernet switch for OMC-B

IPBB or GIPI(electric or fibre interface)

FE1 FE2 FE3 FE4

FE1 FE2 FE3 FE4

iBSC Ethernet switch for SDR Ethernet switch for iBSC

May also be merged into one L3 switch

WAN router for SDR

OMC-B Network Topology when an Abis Interface is FE

1.5.3 When an Abis Interface Uses E1/T1 as the Bearer

Ethernet switch for OMC-B

FE1 FE2 FE3 FE4

OMC-B Network Topology when an Abis Interface is E1

1.5.4 One Example

ZXSDR Series Base Station Commissioning Manual

ZXSDR Series Base Station Commissioning Manual

2 OMCR Data Configuration

2.1 BSC Global Resources Configuration

[OMCGERAN subnetworkBSC management elementConfig SetBSC

ZXSDR Series Base Station Commissioning Manual

Setting BSC Global Resource Attributes