Escolar Documentos
Profissional Documentos
Cultura Documentos
ZTE CORPORATION
Planned by: GSM Customer Service Department, Mobile Product Support Center
* * * *
ZTE CORPORATION
Address: ZTE Plaza, #889 Bibo Road, Zhangjiang Hi-tech Park, Shanghai, P. R. China
* * * *
Legal Information
All rights reserved. No part of this documentation may be
excerpted, reproduced, translated, annotated or duplicated, in
any form or by any means without the prior written permission
of ZTE Corporation.
Feedback Table
You are invited to give your suggestions and opinions to improve ZTE user manuals and enjoy
better service by sending emails to Zheng.junhua@zte.com.cn. Thank you for your cooperation!
Document
ZXSDR BS8800 Project Commissioning Guide (V1.0)
Name
Product Document
V1.0
Version No. Version No.
Please provide your information for further contact:
Name Company
Post Code Address
Tel E-mail
Very Good Good Ordinary Bad Very Bad
General View
Work instruction
Convenient to
consult
Logicality
Correct description
Correct content
Comments
Complete content
Well-organized
structure
Illustration to
figures/tables
Straightforward
expression
Comments
on the sub-
manuals
You may give suggestions from any perspective such as the content, structure, details, depth,
expression, figures/tables, special tools, FAQ and so on. The suggestions are not confined to
this document.
Suggestions
Revision Records
Document Prepared/ Prepared/ Total Reason for Contents of Revision
Version No. Revised by Revised on Pages Revision (Key Points Only)
Note 1: This table must be completed before updating the archived document (the document archived in
the archival room of the division or the Company).
Note 2: Fill "None" in "Reason for Revision" and "Contents of Revision" when archiving this document for
the first time.
Preface
This manual introduces the commissioning criteria for ZXSDR BS8800 GU360
(V1.0), including hardware installation, LMT local commissioning, OMCB
remote commissioning, OMCR data configuration, etc., so as to provide unified
engineering commissioning flow and detailed procedures, to regulate and
guide the on-site tasks of the commissioning engineers.
Contents
1 General Introduction............................................................................................................1-1
1.1 ZXSDR BTS Introduction...............................................................................................1-1
1.1.1 BBU+RU Architecture.......................................................................................................1-2
1.1.2 OMCB Introduction............................................................................................................1-3
1.1.3 IP Abis Interface.................................................................................................................1-4
1.2 SDR BTS Commissioning Flow......................................................................................1-5
1.3 Chapter Outline..............................................................................................................1-8
1.4 Document Application.....................................................................................................1-9
2 Commissioning Preparations...........................................................................................2-10
2.1 Version Preparations....................................................................................................2-10
2.2 Document Preparations................................................................................................2-10
2.3 Configuration Data Preparation....................................................................................2-11
2.4 Others...........................................................................................................................2-11
3 Hardware Check...................................................................................................................3-1
3.1 Hardware Installation Check..........................................................................................3-1
3.1.1 Checking Boards...............................................................................................................3-1
3.1.2 Checking Internal Jumpers on SA Board......................................................................3-2
3.1.3 Checking Input Power.......................................................................................................3-4
3.1.4 Checking Cable Connections..........................................................................................3-5
3.2 Equipment Power-On and Power-Off.............................................................................3-5
3.2.1 B8200 Power-On and Power-Off....................................................................................3-5
3.2.2 Checklist Before Power-on..............................................................................................3-6
1 General Introduction
Abstract
This chapter focuses on SDR basic concept and commission flow.
Currently, the GSM networking mainly uses three types of SDR BTS: the first is
indoor macro BTS, such as ZXSDR B8800 GU360; the second is outdoor
macro BTS, such as ZXSDR B8900 GU360; the third is distributed BTS in
which Baseband Unit (BBU) is separate from Remote Radio Unit (RRU), such
as ZXSDR B8200 GU360 + ZXSDR B8860 GU906/GU186. For the structure,
see Figure 1.1 -1.
Compared with the traditional BTS, SDR has the following features aside from
supporting multiple systems such as GSM and UMTS, etc.
BTS is divided into BBU and RU. One BBU can provide baseband resources
for multiple RU. Functions of BBU and RU are as follows:
The operation and maintenant center for NoedB (OMCB) is the O&M unit that
manages BTS in the 3GPP. As a dual-mode product supporting GSM and 3G,
SDR also supports OMCB. The single-threaded link OMCR BSC BTS is
changed into the dual-threaded link OMCB BTS (in actural network, OMCB
is placed at BSC or RNC side, and the route channel from OMCB to SDR is
provided by BSC or RNC) and OMCR BSC BTS. For BTS, an upper level
is added, as shown in Figure 1.1 -3.
OMCB OMCR
RNC BSC
SDR
The other major difference between SDR and a traditional 2G BTS is the IP
protocol at Abis/Iub interface. Its physical bearer can be FE/GE or E1/T1 (IP
over E1/T1), but not the E1/T1 of TDM. If E1/T1 is used, BTS can fully use the
existing transmission equipment to save the user investment; if FE/GE is used,
BTS will obtain more bandwidth, which is oriented to the communication
system evolution to all IP. See Figure 1.1 -4 for the transmission network with
FE/GE at Abis/Iub interface:
Note: If it is not specified in this book, the BSC interconnected with SDR refers
to ZXG10 iBSCV6.20 in hundred mega or kilo mega platforms.
OMCR data configuration in this book refers to the related operation of SDR at
BSC side, other items for BSC intallation and commissioning are not
mentioned here. The data operation in OMCR falls into four parts: BSC global
resource settings, board configuration at Abis interface, IP interface
configuration, and radio parameter configuration for SDR site.
OMCB is the operation and maintenance center of SDR BTS, on which SDR
data configuration and remote maintenance are performed during
commissioning. This chapter focuses on how to create SDR BTS management
NE (OMCB) in iSMG, and how to configure SDR data in OMCB.
Note that the items configured in LMT are the same with that in OMCB. During
SDR commissioning, the data at BSC side should be configured in OMCR first
in the following two ways: 1. Configure all data through OMCB, meanwhile
configure SDR transmission parameters through LMT to establish a link
between SDR and OMCB, and then synchronize the data configured in OMCB
to SDR. 2. Configure all data though LMT, meanwhile create a SDR
management NE in OMCB to establish a link between OMCB and SDR, and
then transconfigure SDR data to OMCB. Both the methods are described in
this book, but the first one is recommended.
After data configuration, dialing test and drive test should be performed on site,
so as to figure out and solve any possible issues. Make sure the BTS works
normally, before the commencement of Operators acceptance test.
Chapter 7: Test items after commissioning. For test procedures and methods,
please refer to 08 ZXSDR B8200&R8860 Test Guide, 08 ZXSDR BS8800 Test
Guide from http://tsm.zte.com.cn.
The indoor macro BTS mentioned in this document only applies to GSM single
mode, but not UMTS or GSM+UMTS mode.
2 Commissioning Preparations
Abstract
This chapter focuses on the preparations before commissioning,
including the tools, software, documents, SDR hardware, configuration
data and initialized operation and verification method of CC board.
2. Unpacking Inspection Report (Make sure that boards and other hardware
required for the commissioning have been normally delivered).
Table 2.3-1 Parameters for the Interconnection Between ZXSDR and iBSC
Attached below is an example of the BTS configuration data for a certain field
trial.
Site Information
of SDR Field Trial.xls
2.4 Others
1. One commissioning PC (add the configuration information).
Hardware environment:
b) Memory 1 GB 512 MB
Software environment
3. Two test mobile phones (supporting the basic GSM services and data
services), data lines, SIM cards (make sure that the SIM cards have
been well programmed and the subscribers are legal subscribers
registered in the HLR), and data cards.
3 Hardware Check
Abstract
This chapter describes the methods for checking ZXSDR hardware, including
board, cable connections, and running status after equipment is powered on.
Before performing the hardware check, make sure that ZXSDR hardware has
been properly installed.
Figure 3.1-6 Front Panel of B8200 (Slot Numbers Are Marked in Red)
The above figure shows the baseband part of BS8800, which also serves as
B8200 in the distributed BTS. It supports two control and clock boards (CC)
working in active/standby mode, two fiber switching boards (FS) working in
load-sharing mode, and at most five UBPG boards for baseband processing
(The slots of FS boards can also hold UBPG boards, therefore at most five
UBPG boards can be inserted when only one FS board is configured). B8200
can have two power modules, which may work in active/standby or load-
sharing mode depending on the actual needs. Only one SA board and one FA
module can be inserted.
Check whether the board configurations are correct according to the planning.
1
ZXSDR BS8800 Project Commissioning Guide For Internal Use Only
The two least significant bits of X5 are used to set the E1/T1 mode
and the transmission impedance (see Table 3.1 -2). The two most
significant bits are used to set the uplink/downlink long or short line
mode of the E1/T1 (see Table 3.1 -3).
Check whether dry contact, the 232 serial port cables and the 485
serial port cables are correctly connected.
1. Pull out all the boards of B8200 except for PM module and FA module.
3. Check whether the fan module is running normally, the PWR indicator is
on, and the ALM indicator is off.
4. After the equipment is powered on and fans are running normally, insert
the other boards such as CC, BPC, FS and SA, and then observe
whether each board is in normal status. Note that the running indicator
on a board will be off if the data of the board is not yet configured.
Power-off procedures
Switch off the power supply from the power distribution cabinet or PSU. It
is prohibited to plug or unplug the power cable before verifying PM
module has been powered off.
Note:
2. Boards in Slots 1 to 8 have two pullers. The left puller has three position
levels whereas the right puller is fixed. Before pulling out a board, pull
the left puller to the outmost position level. When inserting a board, insert
it along guide rails and then push the left puller to the inmost position
level till the board is locked.
3. To remove the fan shelf: Push the locking switch rightward on the lower
part of the front panel and then pull out the fan shelf.
cable
connection correctly connected. Fail
between racks
If FE cable is adopted, the connection between Pass
Checking
FE cables and CC board is correct. Fail
connection at
If E1 cable is adopted, the E1 transmission Pass
Abis interface
between DDF rack and BTS is correct. Fail
Checking the
connection of The network cable port on LMT Client is correctly Pass
LMT Client connected with CC board. Fail
(Optional)
Pass
All the boards have been pulled out.
Fail
Equipment The status of each board is normal after power- Pass
power-on on. Fail
Pass
The shelves are properly grounded.
Fail
Checking
Pass
power-on The equipment has been normally powered on.
Fail
results
Note
Abstract
This chapter describes SDR operation and maintenance networking to
understand the meanings of various IP parameters in SDR commissioning.
Figure 4.1 -9 shows OMC-B networking topological view when ZXSDR BTS is
accessed to iBSC in E1/T1 mode. In this case, the following items should be
paid attention to:
Note:
RPU is not shown in the above topological view. In fact, RPU is responsible for
route processing for iBSC.
If SDR and OMCB are not in the same network segment, the route to SDR
network segment should be added in OMCB.
In the same iBSC, different EUIP port addresses cannot be set in the
same network segment; the port addresses on IPBB board cannot be set
in the same network segment.
Networking description
When jointly deployed, OMCB and OMCR are logically two separate NM units
except that they are physically installed on SBCX boards. In this case, iBSC
needs to provide two IP interfaces, connecting respectively to SDR BTS and
OMCB Server; BSC needs to be configured with a virtual address (RPU
interface address). The networking is shown in Figure 4.2 -10.
Connection between OMCB and BSC: when FE/GE is used, the interface
of OMCB (the external network interface of SBCX) is generally OMC2
(Note). IPBB is used on the BSC side.
Figure 4.2-10 Network Topology of the OMCB Operation and Maintenance System
Add a route
In the example as shown in Figure 4.2 -10, the IP address of OMCB server
and that of SDR are not in the same network segment. Therefore, it is
necessary to add a route from an OMCB gateway to SDR network segment.
After the route is added, its status can be viewed with the command
netstat nr.
After adding the route with the command route add, to prevent the
configured route being lost due to restarting SBCX, it is suggested to log on
with user ID root to add the following line to the file /etc/rc.d /rc.local:
Thus, each time SBCX is started, the route will be automatically added.
Quit all processes and restart SBCX. Check whether the route is normal
with the command netstat nr.
Quit all processes and restart SBCX. Check whether the route is
normal with the command netstat nr.
From SBCX, you can successfully ping the IP address of SDR, which
is the 118 network segment address of CC board in this example.
After you have telneted CC board, you may connect to RRU by using
the command rlogin RRU IP. Make sure that there are quotation
marks. The format of RRU IP is as follows: 200.(Environment No.).0.
(101+FS Port No.), the default Environment No. is 254.
#telnet 118.18.2.100
CC->rlogin 200.254.0.101
DTR->********
Abstract
This chapter describes the SDR BTS configuration at OMCR side.
Configuration at A interface and Gb interface will not be described in this
manual.
[Objective]
[Preliminary Setup]
3. The IP address related information has been planned, including SDR site
IP, BSC IP at Abis interface, BSC virtual address, IP at OMCB interface,
and OMCB server address, etc. SDR corresponding module number and
Abis interface location on BSC have been planned.
2. Click the icon in the left configuration resource tree window, and locate
the current directory to [OMCGERAN Subnet User IDBSC
Management NE User IDConfiguration Set IDBSC Global Resource
ID].
3. Double click [BSC Global Resource ID], and a window [BSC Global
Resource] pops up, as shown in Figure 5.1 -11. Click to enter the
modification mode. According to the planned addresses, set OMCB IP
in the Basic Property page and IP Abis in the IP Property, as
shown in Figure 5.1 -12. Click OK to finish the creation.
About EIPI:
1. Create a DTB board at Abis interface, and add an Abis interface PCM in
the PCM Information page, as shown in Figure 5.2 -13:
Parameter description:
PCM type: Select EUIP when iBSC is connected with an SDR site in
IPOVERE1 mode.
Frame mode: Select the multi-frame format when iBSC is connected with an
SDR site in IPOVERE1 mode.
2. Create an EUIP board, and configure its property as shown in Figure 5.2
-14. In HDLC Information, connect 2MHW inside EUIP with the E1 of DTB
board at Abis interface, as shown in Figure 5.2 -15:
Parameter description:
Channel mode: Select Channel mode 5 for a 1,000 M platform (one inward GE
port);
Parameter description:
HDLC No.: Allocate an HDLC No. to each E1. This HDLC No. needs to be
referenced when IPOverE1 is configured.
Note:
EUIP board and DTB or SDTB/SDTB2 board must be in the same frame.
EUIP does not support active/standby mode. (Because the PPP link platform
currently does not support active/standby mode).
IPBB board accessed to OMCB and that accessed to SDR may use different
network interfaces of the same board, but both network interfaces need to be
configured with different network segments.
1. Complete the IPBB (OMCB) interface configuration, and link iBSC and
OMCB server.
3. Complete the IP interface configuration at Abis interface, and link SDR with
iBSC.
[Preliminary Setup]
1. The boards related to Abis and OMCB interfaces have been successfully
created.
1. Click the icon in the left configuration resource tree window. Locate the
current directory to [Configuration SetBSC Global Resource IDIP-
related Configuration Interface Configuration].
Figure 5.3-18 Selecting RPU as Board Function Type to Create an IP Abis Interface
Parameter description:
Board function type: Select RPU as the board function type of IP ABIS;
4. Fill in the basic information of the created IP ABIS interface. For details,
see Figure 5.3 -19:
Parameter description:
Port No.: Default value is 1. If more than one virtual address is configured on
RPU, the port No. of each address cannot be the same;
MAC address: It is a virtual address without network card entity, which can be
set randomly. Make sure this MAC address does not conflict with that of EUIP
or IPBB;
Subnet mask: All the four fields must be filled in (that is, 255.255.255.255.).
1. Click the icon in the left configuration resource tree window, and locate
the current directory to [Configuration SetBSC Global Resource IDIP-
related Configuration Interface Configuration].
Parameter description:
Port No.: When IPBB uses an RGE R rear board, it provides one external GE
port. Select 1 as the port No. here. When IPBB uses an RMNIC rear board, it
provides four external FE ports. Select 1, 2, 3 or 4 as the port Nos. according
to the actual condition.
IP address: The address of IPBB port connected with OMCB server, which will
be used as the gateway address from OMCB server to SDR.
[Operating Procedures]
1. Click the icon in the left configuration resource tree window, and locate
the current directory to [Configuration SetBSC Global Resource IDIP-
related ConfigurationInterface 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.
IP address: The BTS gateway address, which is iBSC real address to BTS.
Under the same iBSC, different EUIP links should not be in the same network
segment. This IP address should be in the same network segment as SDR.
1. Click the icon in the left configuration resource tree window, and locate
the current directory to [Configuration SetBSC Global Resource IDIP-
related ConfigurationIPOVERE1 Configuration].
Parameter description:
Port No.: When PPP transmission protocol is adopted on link layer, the Port
No. should be set as that configured in the EUIP interface parameter. When
ML-PPP transmission protocol is adopted on link layer, the Port No. is not
related to EUIP configuration, which is only required to be different from each
other in one ML-PPP, generally set as 1, 2, 3, 4.
HDLC No.: It is associated with HDLC No. in the EUIP board attribute - HDLC
configuration information.
Start TS - End TS: It refers to timeslot resource used by E1 link. The default
Start TS is 1, and End TS is 31, unless specified.
4. Click the icon in the left configuration resource tree window, and locate
the current directory to [Configuration SetBSC Global Resource IDIP-
related ConfigurationIPOVERE1 ConfigurationIPOVERE1
Configuration IPOverE1 ID (IPOVERE1 configuration instance
configured in the previous step)].
Parameter description:
Mpno sign: When PPP transmission protocol is adopted in the link layer, this
parameter is invalid; when ML-PPP transmission protocol (a site is configured
with multiple transmission links) is adopted in the link layer, Mpno sign is valid,
which should be set as corresponding EUIP Port No.
Keep time(s), keep granularity: For example, if the keep time(s) is 25s and the
keep granularity is 5s, detection frames will be sent once every 25/5=5s. That
is, messages will be sent five times within the keep time. If no reply is received
for five consecutive times, it indicates that there is broken links in PPP.
[Operating Procedures]
1. Click the icon in the left configuration resource tree window, and locate
the current directory to [Configuration SetBSC Global Resource IDIP-
related Configuration Interface Configuration].
4. Fill in the basic information of the created IPBB interface. For details, see
Figure 5.3 -21:
Parameter description:
Port No.: There is one outward GE optical interface on the front panel of IPBB.
If RGE R rear board is adopted, there is one external GE electrical interface
(the same interface as front panel). If RMNIC rear board is adopted, there are
four external FE interfaces. Therefore select 1 when GE interface is required;
select 1, 2, 3 or 4 when FE interface is required.
IP address: The address of IPBB port connected with OMCB server, which will
be used as the gateway address from OMCB server to SDR.
[Preliminary Setup]
Note: OMCR is not related to the logical configuration of SDR, therefore the
OMCR configuration of BS8800, BS8900 and B8200 are the same.
[Operating Procedures]
1. Click the icon in the left configuration resource tree window, and locate
the current directory to [OMCGERAN Subnet User IDBSC
Management NE User IDConfiguration Set IDBSC Global Resource
IDBTS Configuration].
Parameter description:
Site ID: It must be consistent with GSM site No. configured for OMCB and LMT.
1. Click the icon in the left configuration resource tree window, and locate
the current directory to [OMCGERAN Subnet User IDBSC
Management NE User IDConfiguration Set IDBSC Global Resource
IDSite Configuration Site ID (the base station configured in the
previous step)].
2. Right click Site ID, and select [CreateSite Rack], as shown in Figure 5.4
-32.
1. Click the icon in the left configuration resource tree window, and locate
the current directory to [OMCGERAN Subnet User IDBSC
Management NE User IDConfiguration Set IDBSC Global Resource
IDSite ConfigurationSite ID].
2. Right click Site ID, and select [CreateCell], as shown in Figure 5.4 -34.
3. As shown in Figure 5.4 -35, set related cell parameters in the Create
Cell interface. Then click OK. BCCH ARFCN (BCCH Absolute Radio
Frequency No.) cannot be set here, but is configured when creating BCCH
TX, as shown in Figure 5.4 -38:
4. If users need to configure GPRS or EDGE parameters, they may set the
item Support GPRS (PsSupport) as Support GPRS in the [Basic
Params 1] page. The corresponding page will display, as shown in Figure
5.4 -36.
1. Click the icon in the left configuration resource tree window, and locate
the current directory to [OMCGERAN Subnet User IDBSC
Management NE User IDConfiguration Set IDBSC Global Resource
IDSite ConfigurationSite IDCell].
2. Right click the Cell, and select [CreateTRX], as shown in Figure 5.4 -37.
3. Click [Trx], and the interface as shown in Figure 5.4 -38 will pop up.
Configure the transceiver according to network optimization & planning
parameters. Click OK to complete the configuration.
4. Configure IP information and type the DSP MarkSeq (DSP Mark Sequence
No.) and Port No., as shown in Figure 5.4 -39.
Parameter description:
DSPSunit: DSP No. of BIPB board. There are 14 DSP on the GUP board of
100M platform, there are 15 DSP on the GUP2 board of 1,000M platform.
DSP MarkSeq: Each DSP has 16 (on GUP board) or 28 (on GUP2 board) DSP
mark sequence numbers, each of which bear the service of a transceiver.
Port No.: port No. of each transceiver, which is a unique No. in the same BSC.
Abstract
OMC-B is a background NMS of ZXSDR base station. It is used to configure
the transmission data, physical data, and some radio data of ZXSDR base
station, and function as an LMT (Local Maintenance Terminal) in a more
flexible way.
1. Log on with user ID omc to OMCB server, and enter the directory ums-
svr\deploy:
$cd ums-svr\deploy
$vi deploy-030womcb.properties
#########################################################################
# #
#########################################################################
#########################################################################
# #
#########################################################################
#########################################################
#########################################################
# #
# #
#########################################################
#########################################################
ums.locale=zh_CN
ums.product=zxwomc
ums.version.main=R6.20.000d-B4.00.100d
ums.version.patch=
ums.version.integral=true
#########################################################################
# #
# NODEB configuration #
#########################################################################
########################################################################
# 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=139.1.1.200
userdefined-zxwomc-common-nodeb-api.OMC-DirectZXSDR_B8800_GU360-
ftpIP=139.1.1.200
userdefined-zxwomc-common-nodeb-api.OMC-DirectZXSDR_B8900_GU360-
ftpIP=139.1.1.200
userdefined-zxwomc-common-nodeb-api.OMC-IpoaALL-ftpIP=139.1.1.200
userdefined-zxwomc-common-nodeb-api.OMC-DirectPicoNodeB-ftpIP=10.61.56.231
userdefined-zxwomc-common-nodeb-api.OMC-IpoaPicoNodeB-ftpIP=10.61.56.231
1. In the FTP port configuration file applied by OMC-B, the default port No. 21
should be modified with a value equal to or larger than 1,024:
$cd ums-svr\tools\ftpserver\conf
$more uep-psl-ftpserver-port.conf
FtpServer.server.config.port=21
2. View the actual port mapping information of the system (Log on with user
ID root):
3. Modify the port No. in the uep-psl-ftpserver-port.conf file with the value
generated after the above-mentioned FTP mapping. In this example, the
port No. is 21111. After modification, the content of the file is as follows:
$more uep-psl-ftpserver-port.conf
FtpServer.server.config.port=21111
Log on to vi editor with user ID root, to modify the value of listen_port in the
file /etc/vsftpd/vsftpd.conf as 10021. Make sure that the result is consistent with
the following content:
5. In the user ID root, modify the port No. corresponding with FTP (tcp) in
/etc/services as 1111. Make sure that the result is consistent with the
following content:
$cd ums-svr\deploy
$vi deploy-030womcb.properties
\userdefined-uep-psl-ftpserver.port
Make sure that the value of this field is consistent with that configured at
ftpserver port enabled by OMC-B service, that is, the above-configured 21111.
userdefined-uep-psl-ftpserver.port=21111
If the value of this field is not 21111, then manually modify it.
Log on with user ID omc, enable OMCB NM application service in the bin
directory. It displays that FTP service can be normally started. Enter normal
starting process as follows:
When the following prompt appears, it indicates that the server has been
successfully started:
Note:
Please perform configuration operations in the order as described in this
chapter. Otherwise, the configuration operations may fail.
[Objective]
[Preliminary Setup]
3. Know about the corresponding interface location and module No. of each
SDR site in iBSC.
4. Know about the IP address of each SDR base station, IP address of the
iBSC interface corresponding to each base station, and the virtual IP
address of iBSC;
5. Know about the planned IP address of each site, and the frequency band
of each RRU;
[Operating Procedures]
a) In the configuration resource tree, select an OMC node, and right click
[CreateGERAN Subnet], as shown in Figure 6.2 -41.
Parameter description:
The management NE ID should be consistent with the GSM site No. of a base
station;
Note:
Management NE ID and IP Address of Management NE are key data for
the interconnection between SDR BTS and OMCB. A link can be established
with the base station after both of them have been set.
1. Right click Base Station Management NE, and select Apply Mutex
Right, as shown in Figure 6.2 -45:
2. Click Yes in the pop-up prompt box, as shown in Figure 6.2 -46.
3. After successful application for mutex right, the node in the NM interface
will be marked with a green lock, as shown in Figure 6.2 -47.
[Operating Procedures]
Note:
Transmission configuration for E1/T1 access and FE access is different. In
each procedure of this section, it will be clarified that whether it is configured
only in E1/T1 access, or FE access, or in both cases. Please pay attention
while reading.
[Operating Procedures]
Parameter description:
NTP Server IP: Fill in the IP address of NTP Server. If there is no specific NTP
Server, fill in the IP address of OMCB Server, or 127.0.0.1;
From the bottom up, BS8800 rack includes B8200 rack (Shelf 1), FCE layer
(Shelf 2), Fan layer (Shelf 3), PDM layer (Shelf 4), RRU layer (Shelf 5).
CC board at Slot 1 of B8200 and PDM board at PDM layer are added
by default. Configure boards at corresponding slots according to
actual physical configuration. Here is an example of PM board at Slot
14, Shelf 1 as shown in Figure 6.2 -50:
Right click at Slot 14, the above dialog box pop up. Select PM board
and click Add. Then click OK to finish the addition. Note: GSM
baseband processing board type should be consistent with physical
Note: Slot 5 can be used for SE extension board for alarm monitoring,
therefore during commissioning, it is suggested to configure UBPG at
Slot 8, then Slot 7 and Slot 6, but better not at Slot 5.
Boards on fan layer and PDM layer are not required to be configured.
Antenna
TTR20 ( -x), GRSU20 ( -x) ,x=B,C,D,E
combiner)
Antenna combiner)
Thus the rack of BS8800 has been created as shown in the following
figure:
3. Antenna configuration
Parameter description:
Shelf No.: It refers to the shelf connected with RRU feeder, here Shelf 6 is
selected.
Slot No.: It refers to the feeder location. There are at most 12 feeders in
the rack, which are numbered with 1-12 from left to right.
Parameter description:
Port ID: It refers to the port No. of FS board connected with RRU (which is
numbered with 5, 4, 3, 2, 1 from left to right).
Child Port ID: It refers to the port through which a child rack is connected with a
higher-level one;
RRU Connection Mode: For the RU directly connected with BBU, if there is no
other cascade RU, select Star; if there is other cascade RU, select Chain. For
the RU connected with BBU indirectly, this item is invalid.
Note:
During the creation of base station ground resource, if Transmission Medium
is FE, it is unnecessary to configure the following Procedures 2, 3 and 4; if
Transmission Medium is E1, it is unnecessary to configure the following
Procedure 1. It will be clarified whether the parameters are configured in the
case of FE or E1/T1.
1. Ethernet configuration
Parameter description:
Rack No.:
Shelf No.:
Link Object: Select IPbone for a directly connected site, or BTS for a
cascaded site;
Bandwidth: Select 10,000k in the case of FE; select 1,984k in the case of
E1.
Parameter description:
E1/T1 Link ID: 0-7 represents 1 st-8th pair of E1/T1 of an SA board; the
default value is 0, which refers to the first pair of E1/T1; keep the default
values for other parameters.
Parameter description:
Base Station IP: Fill in the planned IP address of SDR base station.
Parameter description:
Rack No., Shelf No., and Slot No. are used to locate a CC board;
Parameter description:
Rack No., Shelf No., and Slot No. are located to the CC board configured
with data.
7. IP parameter configuration
Parameter description:
If SDR and iBSC (RPU virtual address, i.e. IPAbis address) are not in the
same network segment, a static route must be configured; otherwise there
is no need to configure any static route.
9. SCTP configuration
Parameter description:
No.0 Local IP Address: Fill in with the IP address of an SDR site. Select
Invalid for other local addresses.
Parameter description:
Link ID:
Base Station OMC IP Address: Keep the IP address of the BTS by default.
Base Station OMC Gateway: Fill in with IPAbis address (RPU virtual address).
IP Tos
Parameter description:
External Clock Source ID: Only internal-GPS and line clock-this board are
supported at present.
Parameter description:
Note:
Description of the maximum configuration: Each site of an SDR base station
can be configured with up to 24 cells, each cell with up to 36 TRX, and each
site with up to 60 TRX. A BP board can process up to 12 TRX; a BBU can be
configured with up to 5 BP boards.
Parameter description:
Logical Carrier Frequency No.: It refers to the carrier No. in the cell;
SDR Configuration
Template.xls
The tool for configuration in batch and its user manual will be provided
otherwise.
After the link between SDR and OMCB in iBSC has been established, the SDR
version can be downloaded from OMCB to activate. To operate on the version
on OMCB, click [View BTS Software Version Management].
Click the configuration resource tree on the left side of the View manu, select
[BTS Software Version Management SDR Software Version Management
SDR Version Packet Management], right click [Create BTS Version Packet]
as shown in the following figures.
Click OK, with the version packet, all the version files will be saved into the
background NM. In the manu SDR Version Packet Management, double
click the nwly-created version packet, and an operation interface pops up as
shown in Figure 6.4 -77
2. Version download
a) As shown in the operation interface in Figure 6.4 -78, click the download button ,a
dialog box for confirmation pops up. Click OK, a dialog box to select BTS pops up as
shown in Figure 6.4 -79.
b) In Figure 6.4 -79, check the box of the BTS which needs to download version, right click
to select Version Packet Download.
3. Version Activation
a) In Figure 6.4 -80, click activation button , a dialog box for confirmation pops up. Click
OK, a dialog box to select BTS pops up as shown in Figure 6.4 -81.
b) In Figure 6.4 -81, check the box of the BTS which needs to download version, right click
to select Version Packet Activation.
4. Version Query
a) In the configuration resource tree on the left, double click [BTS Software Version
Management SDR Software Version Management], click the Version Query
button pops up as shown in Figure 6.4 -82.
b) In Figure 6.4 -83, check the box of the BTS which needs to query version, click OK to
complete the query.
Abstract
The chapter introduces LMT installation, as well as data configuration and
version upgrade for SDR by using LMT. Besides, it also describes the
equipment check after power-on.
1. You can see the following LMT software contents after unzipping the file
BLMT_v4.00.101a.rar:
EOMS The special software version of EOMS and EFMS. You can
load and run it with LoadTool, or test and activate it on BTS.
Load JRE when running LMT. If JRE is not installed on the PC for
commissioning, JRE under LMT directory should be installed. The path
is \.....\BLMT_v4.00.101b2\JRE\jre-6u2-windows-i586-p.exe. (If a different LMT
version and JRE have been installed on the commissioning PC, re-installation
is not required.)
1. Install JRE
Each board on BBU has a fixed internal IP address, which is related to its slot.
The format is:
For the Slot No. of each board, see the red mark in Figure 3.1 -6. The
Environment No. is used to identify a specific SDR in the same network. The
default Environment No. is 254 which can be edited by using the following
Confidential and Proprietary Information of ZTE CORPORATION. 87
ZXSDR BS8800 Project Commissioning Guide For Internal Use Only
command. (Note: The address in 192 field is the internal address at ETH1
interface. In actual networking, it rarely happens that multiple SDR ETH1
interfaces are connected with each other, thus, the Environment No. is not
required to be modified.)
CC board can only be inserted at Slots 1 and 2 of BBU. If there is only one
CC board, it must be the active one. You can connect commissioning PC
with ETH1 interface of CC board through the network cable. If CC boards
are inserted at both Slot 1 and Slot 2, power on and observe MS indicator.
The board, whose MS indicator is on, is the active CC board, which should
be connected to commissioning PC.
Click the Site Management on the logon interface. The dialog box is
displayed as shown in Figure 7.1 -91. In the figure, BTS Name is
recommended to be a plain name. For example, a CC board at Slot 1 of
SDR with environment No. 100 can be named as CC100_1; BTS IP
indicates the IP address of CC board that is connected to commissioning
PC through the network cable.
4. Logon to BTS
The Configuration Export is to export the SDR foreground data in XML format
to a directory of LMT Cient. By way of exporting the configured data in online or
offline mode, the data can be backed up, or imported to other SDR base
station of the same type, single data can be modified for quick data
configuration. (Note: The tool SdrQuickConf can be used to configure SDR
physical data in batch.)
To import data, select Log Off in the drop-down list of System. Then, select
Log On to import the existing configuration data.
Note:
BS8800 will restart after the entire table configuration.
In default mode, log on to LMT with user ID root (whose password is NULL).
To strengthen the LMT application security, the password for user ID root
should be modified.
As shown in Figure 7.1 -96, select Change Password in the drop-down list of
System, a dialog box pops up as shown in Figure 7.1 -97. Enter the original
password and new password, click OK to put the new password into effect.
Data Connection
Step Step Configuration
Category Parameter with BSC
Step BTS Step Basic attribute
GSM site ID
1 Configuratio 1.1 configuration of BTS
n Step Configurations of rack None
1.2 and board
Data Connection
Step Step Configuration
Category Parameter with BSC
Step Clock reference source
None
1.3 configuration
Step Environment monitoring
None
2.1 configuration
Step PA controller
None
Ground 2.2 configuration
Step Resource Step
Serial port configuration None
2 Configuratio 2.3
n Step Topology structure
None
2.4 configuration
Step
Dry contact configuration None
2.5
Configuration of FE
Step parameters (for IP
None
3.1 transmission at Abis
interface)
Configuration of E1/T1
Step connection (for E1/T1
None
3.2 transmission at Abis
interface)
Configuration of HDLC
Step channel parameters (for
None
Transmissi 3.3 E1/T1 transmission at Abis
Step on Resource interface)
3 Configuratio Configuration of PPP
The IP address
n Step parameters (for E1/T1
used by BTS to
3.4 transmission at Abis
access BSC
interface)
Step Configuration of global
None
3.5 port parameters
Step Configuration of IP
None
3.6 parameters
Step Configuration of SCTP Remote IP address
3.7 parameters and remote port No.
Step Configuration of 0MC-B
3.8 parameters
Step Radio Step Configuration of RF unit Cell frequency
4 Resource 4.1 central frequency configuration range
Configuratio Step Configuration of GSM None
n 4.2 sectors
Data Connection
Step Step Configuration
Category Parameter with BSC
Step Configuration of GSM
None
4.3 carriers
Step
Configuration of GSM RU None
4.4
Version
Step Step
Configuratio Version Configuration None
5 5.1
n
Configuration Steps:
Parameter description:
NodeB ID: indicates the site ID of the BTS, which should be consistent
with the GSM site ID.
Set other parameters as shown in Figure 7.2 -100 and Figure 7.2
-101.
Parameter description:
SNTP Server Address: It indicates the time server used by BTS. Fill in with the
actual IP address.
If there is no time server, BTS will start timing from 2000-1-1 0:0:0
automatically. The BTS time can be set manually on LMT. If there is no
independent time server, fill in the IP address of OMCB.
Power Operation Mode: it is used to set the working modes of two PM (power
modules), such as the active/standby mode or load-sharing mode. The
active/standby mode indicates that only one PM is active at one time, the other
module is in standby mode. When the active PM is faulty, the standby module
will take over the job. Then, the original standby module is switched to the
active module. The load-sharing mode indicates that both PM are working
simultaneously. When one module is faulty, the other will take over all the jobs
and ensure normal operation of the system. B8200 can operate normally with
only one PM. It can support a maximum of two PM.
Radio System: It is used to set the radio system of the BTS, including GSM,
WCDMA, or WCDMA/GSM. The selection is based on the type of RF unit
which is connected to FS board of B8200. When all RF units are used for GSM
system, select GSM; when all RF units are used for WCDMA system, select
WCDMA; when some RF units are used for GSM and the others are for
WCDMA, select WCDMA/GSM.
GSM Site ID: It indicates the site identification of GSM allocated by BSC. It is
the planning data which should be consistent with the site ID used to configure
the site on OMCR. This site ID also serves as SCTP port No. that is used when
SCTP connection is established between B8200 and BSC. BBU obtains the
radio configuration parameters through OMCR. If the site ID is configured
incorrectly, BTS cannot obtain the correct radio parameters or access.
Time Zone: Set the parameter based on the time zone that BTS locates in. It is
China GMT+8:00 by default.
Clock Synchronization Period: It indicates how often (in hour) BTS performs
the time synchronization with the preset time server of SNTP Server. Use the
default value.
Support Power off Control: When the power is faulty, NodeB will disconnect the
external boards automatically (including FS UBPG) to save the power in the
storage battery. This option is designed for users to select whether to allow the
strategy. Currently, the function is not supported, which should not be checked
here.
In LMT, the BS8800 rack from the bottom up include BBU (B8200 rack, Shelf
1), FCE layer (Shelf 2), Fan layer (Shelf 3), PDM layer (Shelf 4) and RRU layer
(Shelf 5).
a) Add board
Figure 7.2-103 Configuring the UBPG Board of the BBU on BS8800 Rack
Note: both Slots 1 and 2 on the Main Rack 1 are configured with a CC
board that cannot be deleted on LMT (but can be deleted on OMCB). If
one of the slots has no CC board, BTS can still run normally.
After adding the board, to know whether there is an alarm on the board,
right-click on the board and select Board Status Illustration. A prompt
of the board is displayed as follows.
a) Add rack
Right-click the BTS, and select Add Rack as shown in Figure 7.2 -106.
The type of RSU is selected according to the following table; antenna is
configured with ANT be default.
RU Type Remote Rack Remote Rack Board Type BS8800/BS8900 Board
Name Type
RU60 ZXSDR R8860 DTR ( -x), x=B,C,D,E (internal DRSU (-x), x=B,C,D,E
combiner) (internal combiner)
RU02 with ZXSDR R8802 TTR ( -x) ,x=B,C,D,E (without GRSU ( -x), x=B,C,D,E
antenna combiner) (without combiner)
TTR20 ( -x), x=B,C,D,E GRSU20 ( -x) ,x=B,C,D,E
(internal combiner) (internal combiner)
RU02 without ZXSDR R8802E TTR20 ( -x), x=B,C,D,E GRSU20 ( -x) ,x=B,C,D,E
antenna (without combiner) (without combiner)
b) RU configuration result
Parameter description:
Board Port ID: Each FS board of BBU provides six fiber interfaces to be
connected to RU. The optical interfaces on the front panel of FS board
are numbered with 0, 1, 2, 3, 4, 5 from left to right.
By using the above method, add the configuration data of topology for
each pair of BBU and RU or each pair of RUs which are directly
connected. After configuring the rack and topology structure, you
should configure the transmission resources at Abis interface.
Note:
The transmission configuration for E1/T1 access is different from that for FE
access. Note that in each step in this section, it will declare whether it is
configured for E1/T1, FE, or both E1/T1 and FE.
If the planned SDR address and the iBSC virtual address are not in
the same network segment, Static Route Parameters should be
configured.
Configuration procedure
1. E1/T1 cable
Parameter description:
Board Name: It indicates the board from which SDR accesses E1/T1. For
B8200, although E1/T1 is accessed physically from SA board, SA board
performs no operation over E1/T1. The co-team handling is completed by
CC board, therefore, E1/T1 is accessed logically from CC board. Thus, CC
board is adopted by default, which cannot be edited.
Link ID: It indicates the pair of E1 cables to be used. There are eight pairs
of E1 cables led out from SA board which correspond to Link ID Nos. 0 to 7.
In the figure, the link ID of E1 cable is 0, that is, use the first pair of E1
cables (No.1 and No.2 E1 cables). The link ID configured in this step will be
referenced later in the HDLC channel parameter configuration; it also
identifies the E1 link used in a HDLC channel
Note:
Ensure that you have set the transmission medium as E1 or T1 in Set Basic
Property -> Other Related Parameters. Otherwise, E1/T1 cable can not be
added.
2. Ethernet Parameters
Confidential and Proprietary Information of ZTE CORPORATION. 109
ZXSDR BS8800 Project Commissioning Guide For Internal Use Only
Parameter description
Board Name: Select the board where the IP port of Abis interface locates.
Select CC for GSM.
3. HDLC parameters
Parameter description:
HDLC ID: It indicates HDLC ID, starting with 0. The number is increased by
1 each time when a record is added. This parameter is set automatically by
the system, and needs no modification. Each E1 should be configured with
one HDLC. The HDLC ID configured in this step will be referenced later in
the PPP parameter configuration.
Link ID: It indicates the ID of E1 link where HDLC channel locates, that is,
the Link ID configured in E1/T1 cable. If you add Links 0 and 1 in E1/T1
Configuration, there will be two options available: 0, 1.
4. PPP parameters
Parameter description
PPP ID: It indicates PPP ID, starting with 0. The number is increased by 1
each time when a record is added. This parameter is set by the system
automatically, and no modification is needed.
Link ID: Link 0, Link 1, and Link 2 are used to set HDLC channel (HDLC ID)
used by PPP link respectively. When the PPP Encapsulation Type is set
as PPP, only link 0 is valid; when the PPP Encapsulation Type is set as
ML-PPP, you can select multiple links based on the planning. See Figure
7.2 -116.
Parameter description
BTS IP: It indicates the IP address that SDR uses to communicate with
iBSC. Note that this address is the external address of SDR. The address
Parameter ID
Link Layer Port ID: It indicates the internal port number used in BTS
protocol stack subsystem. For example, PPP uses Global Ports No. 3 - No.
34 that corresponds to Link Layer Ports No. 0 - No. 31. This parameter is
generated by the system automatically, and needs no modification.
Vlan ID: When the box [Use VLAN] is checked, this parameter is valid. Its
value ranges from 2 - 4094. This parameter is invalid when the value is
65535.
6. IP parameters
Parameter description
When the data configuration is complete, the IP address and the gateway
address are obtained automatically after the synchronization with BSC
data.
Note:
The IP address, subnet mask, and gateway address on this interface are in
grey. When the site is started, these options will be filled in automatically. For
example, the IP address is BTS IP address configured in PPP Parameter
Management. It is the bandwidth to be set here.
7. SCTP parameters
The configurations of E1, T1, and Ethernet are the same on the
transmission layer. SCTP belongs to the transmission layer that is above
the IP layer. It can not perceive whether the data link layer is PPP or
Ethernet, therefore, the SCTP configuration is the same for E1 or Ethernet
accesses.
Parameter description
[Local Port ID]: it indicates the port number that BTS uses to establish
SCTP connection with iBSC. Its value ranges from 1 to 1536. This port ID is
SITE_ID used in layer 3, that is, GSM Site ID in the background network
management. It is set by the system automatically, and is not editable.
8. OMCB parameters
Parameter description
Configuration description
GSM sectors
GSM carriers
GSM RU
Configuration steps:
Because the bandwidth of RRU is limited within 10 M, that is, it can receive
signals within the range of the central frequency 5 M (it is not guaranteed
to receive the out-band signals). Therefore, it is noted that frequency of the
logical transceiver cannot exceed this range. For example, when the central
frequency is 945 MHz, the range is 940 - 950. In absolute frequency, the
range is 25 - 75. The central frequency configured here is the downlink
central frequency.
Parameter description
[Band Name]: Select a proper band from the pull-down list based on the
RRU hardware type which can be identified by the delivery nameplate.
GSM sectors, GSM RU, and GSM carriers are configured in Radio
Resources.
a) GSM sectors
This step is used to configure logical and physical cells of the site. The
sector number indicates the logical cell ID. The sector numbers
configured here are the base of sector numbers in GSM carriers. The
sector numbers in the following GSM carriers are selected based on
these sector numbers.
Click Radio Resources -> GSM Sector, right-click at the blank area on
the right, and select Add. The GSM sector configuration interface is
displayed. See Figure 7.2 -123.
Parameter description
[Physical Cell ID]: It must be the same as the sector number, ranging
from 1 to 984. This parameter is invalid in GSM. (The physical cell ID is
not involved currently. You can configure this parameter freely). It
reflects the relation between physical cell number and sector number.
b) GSM RU
Parameter description
[RF Extension Port]: when a cell has multiple RRU, use RF extension;
when a cell has only one RRU, do not use RF extension, that is, use
the independent operation mode.
[Multi-carrier Combination]
[Sector x Number]: it indicates the sector number, that is, the sector
that is configured on the remote rack (RRU) mentioned above. Set
sector (1) only.
c) GSM carriers
Click Radio Resources -> GSM Carrier, right-click at the blank area
on the right, and select Add. The GSM Carrier Configuration interface
is displayed. Add carriers for the sector based on the number of carriers
in the sector that is configured in GSM RU.
Parameter description
[BCCH Carrier]: do not set this parameter. The system will select a
BCCH carrier based on the background OMCR configuration when the
site is started.
Note:
The parameter tables of GSM sectors, GSM RU, and GSM carriers are
configured in descending way.
The number of carriers configured in each sector should not be less than
that configured in iOMCR.
(including RRU) are connected to the master CC link. The SDR power-on
inspection is considered passed only when all the conditions above in bold are
satisfied.
To query the state between boards (including RRU) and the master CC link
board, perform the following operations:
CC->OSS_DbgShowComm
Item (subsys module unit sunit ) pos state IP(hex) mac sndQ bufQ udpQ work
0 (0 1 0 1 ) L 0 c0fe0110 00:00:00:00:00:00 0 0 0 0
0 (0 1 0 1 ) R 3 c0fe0210 00:00:00:00:00:00 0 0 0 0
1 (3 1 0 1 ) L 3 c0fe0510 00:00:00:00:00:00 0 0 0 0
1 (3 1 0 1 ) R 0 ffffffff 00:00:00:00:00:00 0 0 0 0
2 (1 1 0 1 ) L 3 c0fe0310 00:00:00:00:00:00 0 0 0 0
2 (1 1 0 1 ) R 0 ffffffff 00:00:00:00:00:00 0 0 0 0
GroupTable:
127,255,
value = 2 = 0x2
In the above printed information, IP addresses of these boards are in hex. If the
State value is 3, the board is connected to the master CC board link.
Confidential and Proprietary Information of ZTE CORPORATION. 131
ZXSDR BS8800 Project Commissioning Guide For Internal Use Only
Telnet to RRU, and enter d 0x0e001020. The printed data is October 7, 2008 or
later. You need to record this.
DTR->d 0x0e001020
0e001020: 2008 1213 1428 0000 0000 0000 0000 0000 * ....(..........*
0e001030: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001040: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001050: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001060: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001070: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001080: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001090: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e0010a0: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e0010b0: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e0010c0: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e0010d0: 4454 525f 6130 3100 3100 0000 0000 0000 *DTR_a01.1.......*
0e0010e0: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e0010f0: 0000 0000 0000 0000 0000 0000 0000 0000 *................*
0e001100: d000 000b 0000 0000 0000 0000 0000 0000 *................*
0e001110: 0100 0000 0000 0000 0000 0000 0000 0000 *................*
value = 21 = 0x15
Telnet to RRU, and then enter the svi command. Main CPU Version (CPU),
Main FPGA Version (FPGA), and Main IFFPGA Version (DSP) are the required
versions (For versions, see the red label). You do not need recording this.
DTR->svi
Versin Type = 0
Cpu Type = 37
Versin Type = 0
Cpu Type = 37
Versin Type = 1
Cpu Type = 0
Versin Type = 1
Cpu Type = 0
Versin Type = 8
Cpu Type = 0
Versin Type = 8
Cpu Type = 0
value = 20 = 0x14
7.4.3 FAQ
2. If there is an Optical Port Frame Loss alarm on RRU, change the optical
module at the RRU side to make an attempt.
Ftp to RRU, and put the lost calibration file to RRU manually. If the file
does not exist, obtain it from the normal RRU.
4. When there are application monitoring alarm and board communication link
disconnection alarm on RRU, it is likely that RRU is not powered on if the
fiber and optical module are in good condition. Connect RMB board
converting from the serial port to the network interface to ALM interface of
RRU, and then telnet to 199.33.33.33 and query the current operation of
RRU by running the hr command, or perform the following operations to put
DSP, CPU, and FPGA versions of RRU manually: enter the root directory,
and replace the cur.swv under the rru directory, the cur.swv under the
rru\dsp, and the cur.swv under the rru\fpga directory. If manually putting the
three versions in RRU is unsuccessfully, delete cur.swv, enter the bin
command, and put the three versions manually again.
When a site is configured, export its configuration data, import the data into
another site with the same or similar configuration, and then modify a few data,
thus achieving fast configuration of BTS data. The export and import methods
of the configuration data are described in Section 7.1.5. The following only
describes the data to be modified after import.
Figure 7.4-130 Data to Be Modified After Import of Configuration Data Site Number
Figure 7.4-131 Data to Be Modified After Import of Configuration Data BTS IP Address
4. SCTP parameters. First delete the existing SCTP parameters and then add
new SCTP parameters.
5. RF Unit Central Frequency, GSM Sector, GSM RU, and GSM Carrier.
Modify these parameters according to the planning.
Abstract
The preceding chapters describes data configuration on OMCR, OMCB, and
LMT respectively.
Right-click the popup shortcut menu in the management NE, and select entire
table synchronization or increment synchronization to send the configuration
data.
Note:
The base station will restart in the whole table synchronization.
On the site, right-click and select BTS Data Configuration Wizard (SDR). The
interface as shown in Figure 8.2 -133 is displayed. Select Use the foreground
to configure, and then click Next. The Data Parallel Upload tab is displayed.
Select NE to be uploaded, as shown in Figure 8.2 -134.
Click Next, and the dialog box as shown in Figure 8.2 -135 is popped up if
OMCB and BTS link are normal. In Figure 8.2 -135, Switch to Master indicates
whether the configuration exported from LMT servers as the master
configuration. Click OK. The configuration is exported. The LMT configuration
is uploaded.
Abstract
This chapter describes the basic service tests and how to test these services.
For more information, see 08 ZXSDR B8200&R8860 (V4.0) Test Guide.
3. Prepare two cellular phones ( A and B) and related fittings, and two SIM
cards which can be used in the local network.
4. LAC, CI, and frequency of this site are confirmed consistent with the
planning data and the background data.
5. Obtain the frequency planning table for all cells of the site.
6. The calling uses the first party release mode (at the handover side).
3. a. (1) A calls B, and receives the prompt tone (ring back tone). (2) B
answers successfully. The voice is good. (3) A hooks on normally.
b. Repeat above calling steps. B hooks on normally.
4. a. (1) B calls A, and receives the prompt tone (ring back tone). (2) A
answers successfully. The voice is good. (3) B hooks on normally.
b. Repeat the above calling steps. A hooks on normally.
6. Repeat steps 1 5 to test other cells of the SDR site until all cells are
tested.
2. Prepare a cellular phone to test GPRS/EDGE service and a SIM card that
has subscribed PS service.
5. PC and the cellular phone meet the connection conditions, including the
data line, Bluetooth, and infrared transmission.
2. Install the driver of cellular phone Modem on the PC to ensure that Modem
runs normally.
3. Establish a new dial-up connection on the PC: write down the phone
number, ISP, username and password in the dial-up connecting setting.
5. When the dial-up connection is successful, open FTP tool software on the
PC.
6. In the FTP tool software, type IP, username, and password of FTP server to
log into FTP server.
7. Download a file from FTP server to PC. The file size must be greater than
500 K.
8. Record the size, download period and download speed of the file. The file
must be download successfully and the downloaded file can be used.
9. Upload a file from PC to FTP server. The file size must be larger than 500
K.
10. Record the size, upload period and upload speed of the file. The file must
be uploaded successfully and the uploaded file can be used.
APN: Access Port Name. APN consists of two parts: network ID and
operator ID. The network ID defines the external network of GGSN
connection. The Operator ID defines PLMN GPRS network that contains
GGSN.
In the FTP test of GPRS test, APN, username, password, and IP address
are provided by the operator.
SDR Board IP
BBU
RRU