Beruflich Dokumente
Kultur Dokumente
ZTE CORPORATION
Planned by: GSM Customer Service Dept., ZTE Global After-Sales Service Center
* * * *
ZTE CORPORATION
Address: ZTE Plaza, Keji Road South, Hi-tech Industrial Park, Nanshan District, Shenzhen, P.R.China
* * * *
Legal Information
and are the registered trade marks of ZTE Corporation. The names
and logos of ZTE products are proprietary logos or registered trade marks. The
names of other products and companies mentioned in this manual may be
proprietary to their owners respectively. Without the prior written permission of
ZTE or the owners of third-party trade marks or trade names, this manual does
not grant the reader any permission or right to use any marker appeared in the
manual.
The actual product may differ from what is described in this standard due to
frequent update of ZTE products and fast development of technologies. Please
contact the local ZTE office for the latest updating information of the product.
Preface
This manual specifies the commissioning regulations of ZXG10 iBSC (V6.20)
products, including BSC, ZXG10 iSMG Server and Client. It unifies the
commissioning procedure, and also instructs the commissioning engineers to do the on-
site commissioning.
Contents
1. Commissioning Flow...................................................................................................................................1
2. Commissioning Preparation......................................................................................................................1
2.1 Project Information.................................................................................................................................1
2.2 Tools & Instruments...............................................................................................................................1
2.3 Software..................................................................................................................................................1
2.4 Document................................................................................................................................................2
2.5 System Networking Scheme..................................................................................................................2
9. GB Interface Configuration......................................................................................................................1
9.1 E1 GB Interface Configuration..............................................................................................................1
9.1.1 NSE Configuration.......................................................................................................................1
9.1.2 BRCH Configuration....................................................................................................................2
9.1.3 NSVC Configuration....................................................................................................................5
9.2 IP GB interface Configuration................................................................................................................8
9.2.1 NSE Configuration.......................................................................................................................8
9.2.2 IPGB Port Configuration............................................................................................................11
Commissioning................................................................................................................................................1
1. Commissioning Flow
Generally, commissioning of iBSC (including iSMG Server and Client) includes
following procedures:
(1) Preparations
(10) Commissioning
SN Procedure Description
Confirm system networking scheme; get IP address of Server, Client, OMP and
Commissioning SBCX; fetch system configuration parameters (including A interface interconnection
1
preparation data of MSC and Gb interface interconnection data of SGSN), system debugging tool,
document preparation, software preparation.
Check the installation of racks, cables, modules and voltage of power supply.
2 Check before power-on For details, please refer to ZXG10 iBSC (V6.20) Installation Manual Hardware
Installation
Check power supply and wind direction from fan
3 Check after power-on For details, please refer to ZXG10 iBSC (V6.20) Installation Manual Hardware
Installation
OMP installation and Generally, conduct initialization to start parameter setting, and upload version and
4
debugging activate software
SBCX O&M software It covers NMS overview, networking mode, OMM installation environment
5
debugging requirements and OMM software installation flow.
Configure iBSC physical data, radio data and table synchronization through OMCR.
6 Data configuration For details, please refer to ZXG10 NetNumen-G (V6.20) Operation & Maintenance
Center Operation Manual (Configuration Management)
Conduct version storage, setting and loading board software through OMCR. Reset
boards on iBSC to end version loading
7 Software loading
For details, please refer to ZXG10 NetNumen-G (V6.20) Operation & Maintenance
Center Operation Manual (Configuration Management)
Installation and Install SBCX board software and conduct performance test
8 debugging of SBCX
board
Check MSC transmission and interconnection data. Observe and test after A interface
A interface
data configuration and interconnection. Check SGSN transmission and
9 interconnection and GB
interconnection data. Observe and test after GB interface data configuration and
interface interconnection
interconnection.
HR/AMR commissioning description, hardware replacement, HR/AMR software
10 HR/AMR commissioning
configuration, setting static and dynamic HR.
iBSC hardware test, iSMG function test, software version test, call test, handover test,
11 Commissioning test new function test. For details, please refer to ZXG10-iBSC (V6.20) Test Guide. Once
all of the services are in normal condition, the commissioning is complete.
Note: This version does not include GPRS/EDGE commissioning and HR/AMR
commissioning test. They will be supplemented in later version.
2. Commissioning Preparation
To guarantee smooth equipment commissioning, the equipment debugging persons
should make enough preparation before the equipment debugging, including the project
information, system networking schemes, tools, software and documents.
2. Instruments and meters: ground resistance tester, multimeter, test mobile phone
(with SIM card), BER test device.
3. Others: laptop (with NETTERM, FTP tool, PCANYWHERE, Quartus II, anti-
virus software installed), network cable, crossover network cable, logic
downloading cable, PC monitor, keyboard, serial port cable, USB serial
converter, serial-to-RJ45 commissioning cable.
2.3 Software
Prepare the relevant software of correct versions according to required functions and
2.4 Document
The commissioning engineer should also refer to the following documents for
instructions:
Debugging engineers should give proposals for IP address planning and route
configuration according to the networking diagram, and then make a decision after
reaching an agreement with the client.
3.1 Overview
Once iBSC hardware installation is complete, please check the following items
carefully before power-on.
2. Check whether all modules are in correct positions and well touched. If
necessary, please plug out and in for twice. Meanwhile, check whether screws
on boards are fixing tightly. The rear boards should be also checked.
4. Check whether cables between iBSC and BTS, and cables among A interface,
Gb interface, SVB, OMP, server, client, router, alarm box and HUB are
correctly connected.
5. Check whether DC voltage is within the permitted range (nominal value: -48 V;
range: -57 V ~ -40 V).
6. Check whether rack ground and lightning protection ground are correctly
connected.
7. Check whether all of the selecting switches and control switches are in
specified positions.
(2) Measure resistance of -48 V power against -48 V ground on busbar with
multimeter. No short circuit exists.
(3) Measure resistance of -48 VGND, PE, GND on busbar with multimeter. No
short circuit exists.
(4) Check whether -48 V power cable of fan shelf is connected correctly.
In the above tests, turn off switch immediately in case of any abnormal condition,
and then make troubleshooting.
Electric Shock
Caution:
Wear antistatic wrist strap when contacting equipment and well arrange grounding.
3.3.1 Cabinet
3. Components and parts of rack should not fall or damage. Cables should not fall
Confidential and Proprietary Information of ZTE CORPORATION.
ZXG10 iBSC (V6.20) Engineering Commissioning Guide Internal Use Only▲
4. Upon completing rack installation, please clean both inside and surface of rack.
5. Ensure that protection bags of cables are fastened tightly after arranging cables
so as to avoid dust and animals entering cabinet.
3.3.2 Board
Before powering on iBSC equipment, please check the type, quantity and position of
every module. Also check whether controlling switch is correct or not.
Please refer to ZXG10 iBSC (V6.20) Hardware Manual during check. And ensure
boards on the rack are in correct position. Besides, check the type and quantity
according to packing list and contract configuration.
For those are not well plugged in or not in good touch, please plug out and plug in
again. At the same time, pay attention to its method.
Intra-cabinet cables include power supply cable, system clock cable, reference clock
cable, IP access cable, control plane connection cable, PD485 power cable, user plane
connection optical fiber and fan monitor cable.
● Monitoring cable
● Transmission cable
E1 trunk cable
There are two types of E1 cables in ZXG10 iBSC system. One is 75 Ω coaxial
trunk, and the other is 120 Ω twisted pair trunk. Configure it as per the actual
requirement.
Optical fiber
Connect ZXG10 iBSC and MSC/MGW with optical fiber. LC/PC connectors
are used at both ends of optical fiber without directivity.
One end of optical fiber is connected with TX of SDTB board, the other end is
connected with RX of opposite equipment. For another optical fiber, one end is
connected with RX of SDTB board, the other end is connected with TX of
opposite equipment. Optical fiber should be in pair.
Ethernet cable
Connect ZXG10 iBSC and MSC/MGW, SGSN, SDR with FE. One end of
Ethernet cable is connected with FEx of RMINC on BIPI board or GIPI board.
The other end is connected with the responding port of the opposite end
(MSC/MGW, SGSN or SDR) through the network equipment such as switch.
● Power cable
● Grounding cable
● iOMCR Ethernet
Two cables are connected between OMP and HUB. They are respectively led
from OMC2 interfaces on RMPB of both active and standby OMP. It is noted
that there are two interfaces marked as OMC on RMPB, i.e. OMC1 and OMC2.
But only OMC2 can act as NM connection interface.
The cable connecting SBCX with HUB is led from NM connection interface on
RSVB of SBCX. There are three NM interfaces on RSVB, i.e. OMC1, OMC2
and OMP1. OMC1, which is corresponding to eth3 of SBCX, is generally
configured as the network port of OMCR server. It is used to communicate with
client and Minos server. OMC2, which is corresponding to eth4 of SBCX, is
generally configured as the network port of OMCR server. It is connected with
iBSC via GIP or BIPI to communicate with SDR. OMP1, which is
corresponding to eth6 of SBCX, is generally configured as the internal network
address. It is communicate with OOMP.
The cable connecting GIPI/BIPI and HUB is led from FE interface on RMNIC
of GIPI/BIPI. It is noted that there are four FE interfaces on RMNIC. The used
FE interface can be set on client.
1. Power cable
It covers cable from power to power box, cable from power box to busbar, and
cable from busbar to power socket on rear board of power box. All of the cables
should be connecting reliably with correct polarity.
2. Grounding cable
Check whether -48 V GND and PE are connecting correctly and reliably. PE is
connected with the PE terminal at the right side of cabinet top. (There is one PT
terminal at both right side and left side of cabinet top. Seen from the back of
cabinet, the terminal at the left side is the left side PE terminal and the one at
the right side is the right one.)
Clock cable and power alarm cable are connecting correctly and reliably. The
route rand packing distance are correct. The locker should not be peaked or
overlapped.
4. External cable
(2) Router should be arranged as per the requirement and packing distance should
be uniform.
(3) The route should be smooth. Cable inside rack should not be cross. Cable
outside rack should be bundled.
(4) Cable on trough or cabling ladder should be in order. All of the cables are
bundled. There is no damage to cable surface.
(5) Cable should be surplus. The packing belt head should be neat and in order.
Alarm box should be installed at the highlighted position. The height of installation
position should be appropriate for easy operation. Power cable and network cable
should be placed in the trough. No stub exposes. The alarm box should be installed
reliably. If several alarm boxes are parallel, apparent marks should be made for
identification.
Infrared sensor is installed at proper position. Its detective range covers the important
entrance of equipment room.
Temperature sensor and humidity sensor should be installed near cabinet. The distance
should not be more than 1 m.
4. The working ground, protection ground and lightning protection ground are in
sound condition. The ground resistance meets technique requirement. Rack lap
resistance is 0.1 Ω ~ 0.3 Ω. Equipment room grounding resistance should be
less than 1 Ω. The specification of fuse should meet the requirement. The pins
on rear board are not distorted or shortcut. There is no shortcut between anode
and cathode.
2. Turn on -48 V power switches on board in power distribution box on rack top.
2. When board is powered on, board software and hardware are automatically
initialized. After that, see whether board is in normal condition based on the
LED indication.
Please refer to ZXG10 iBSC (V6.20) Hardware Manual for details of board
LED.
1. If there is board in the box under fan box, then plug it out.
2. Power up equipment, fan in P power box on the top layer of cabinet starts
normally.
3. Put a 20 cm long paper slip into the box under power box. If the paper slip is
not blowing up (which indicates fan is not working), or it is blowing downward
Confidential and Proprietary Information of ZTE CORPORATION.
ZXG10 iBSC (V6.20) Engineering Commissioning Guide Internal Use Only▲
(which indicates wind direction is wrong), check iBSC (V6.20) internal power
cable connection and fan.
4. If paper slip is blowing upward, it indicates the wind is coming from the rack
bottom. Under this condition, fan is working normally and wind direction is
also correct.
2. Turn off -48 V power switches on board in power distribution box on rack top.
5.1 Prerequisites
The followings should be ready before system debugging.
1. System check has been completed and equipment has been powered on.
4. Upload zxg10.cfg.
Create OMP boot files via NE client, create a configuration file named ompcfg.ini in
the folder under OMC sever software installation directory of ums-
svr\tmp\ftp\version\bscX (X is office No., which is configured in the background
configuration management. It is not the office No. displayed on DIP switch on rear
board.)
When starting OMP board, ask server for this boot file to load OMP version file. At this
moment, configure some parameters communicated with OMC server, including OMP
NM address, OMC server address, office No., ftp user name and password, startup
mode.
This section takes No.12 office for example to describe how to configure OMP via
serial port. The details are as follows.
1. Connect OMP debug serial port (DEBUG2-232 interface under RMPB board) with
debugging PC serial port. The debugging PC can be OMC NM client. Run the
HyperTerminal program self-brought by operating system, enter the newly-built
connection name in Connection Description and select its icon, as shown in
Figure 5.3-2.
2. Click OK, and pop up the dialogue box Connect To, select the serial port
connected with foreground (in this instance, COM1 connects with foreground),
and finally click OK, as shown in Figure 5.3-3.
3. In dialogue box of COM1 Properties, click Restore Defaults, and then click
OK, as shown in Figure 5.3-4.
4. After logon HyperTerminal, when popping up “Press any key to stop auto-
boot...”, immediately press any key to stop auto-boot, and then start
configuring OMP parameters.
CPU: PC PENTIUM3
Version: VxWorks5.5.1
ZZ
Boot Build : 43
[BSP] BOOT Menu Operation Monitor Task Starting (MAX: 120 Second)...
+-----------------------------------------------------------------+
| B O O T PA S S W O R D NOTICE |
|-----------------------------------------------------------------|
+-----------------------------------------------------------------+
************Init**********
Accepted system dates are greater than THU DEC 27 00:00:00 1990
/DOC0/ - Volume is OK
# of bad clusters: 0
# of files: 39
# of folders: 5
# of lost chains: 0
Config selection:
Enter your selection (1/2/3/4/5):1 \\enter mode1, set OMP IP and MAC
Please enter IP (may include net mask) in dotted notations, such as 129.0.0.1:ff0
00000!
[Enter OMP's OMC Ip address]: 129.0.31.12 \\OMP IP address, consistent with the
setting of iOMCR
[Enter OMP's OMC Mac address]: \\directly enter, use default MAC address
Please enter Gateway IP (Not include netmask) in dotted notations, such as 0.0.0.0!
Please enter OMC Server Ip (Not include netmask) in dotted notations, such as 0.0.0.0!
Config selection:
Enter your selection (1/2/3/4/5):2 \\enter mode2, set OMC server IP address
[Enter OMC FTPSVR User Name]: uep \\enter OMC server FTP user name
[Enter OMC FTPSVR PassWord]: uep \\ enter OMC server FTP password
Config selection:
Enter your selection (1/2/3/4/5):3 \\enter mode3, select start type of OMP boot
Please Set OMP Boot Type :( 0 is Boot From OMC; 1 is Boot From Local Flash)
Config selection:
Enter your selection (1/2/3/4/5):4 \\enter mode4, set exchange office No.
Config selection:
Enter your selection (1/2/3/4/5):5 \\enter mode5, quickly exit OMP configuration
mode
5. After auto-booting, OMP downloads version file and FPGA file from OMC
server.
After OMP normally starts, RUN LED on MPX86 board slowly flashes; under
the HyperTerminal prompt ->, enter SCSShowMcmInfo, and then enter, pop up
the following prompt:
value = 1 = 0x1
Note
Board status of print is “MASTER” and “WORK”, which indicates OMP is in normal
working condition; otherwise, it is abnormal.
; 1: use
;1: CELLID_CGI
ZXG10.cfg should be ftp uploaded to directory /DOC0/CFG of OMP & CMP boards.
Then, reset OMP & CMP boards to make the configuration take effect.
When OMP and CMP lack this configuration file, they can run normally. Under this
condition, the foreground variable uses the default value. So, the uploading operation
can be done after OMP and CMP are running normally.
ZXG10.cfg is issued with the version, which is positioned under the directory of MP
version, e.g. iBSCV6.20.100a\Release\MPX86_2\MP.
When telnet logon, both user name and password are zte. Pay attention to uppercase
and lowercase during debugging.
(1) SCSShowMcmInfo
(2) SCSShowVerInfo
PLAT_PATCH_DATE_LIST : 2007081000
PLAT_PATCH_DATE_URGENT: 0
wLgcBrdType is 20!
wPhyBrdType is 69!
wVerType is 1!
wFuncType is 1!
wCpuType is 65535!
dwFileSize is 4914848!
dwVerCheckSum is 826659844!
acVerFileName is IBSC_MPX86_2_MP_P4_V6.20.102A_Z.BIN!
wLgcBrdType is 65535!
wPhyBrdType is 69!
wVerType is 2!
wFuncType is 1!
wCpuType is 65535!
dwFileSize is 73632!
dwVerCheckSum is 315893148!
acVerFileName is MPX862_03_040703_FPGA_106.rbf!
(3) NfsShowState
Function: display the current status of blade server (front end processor).
When blade server is working normally and well communicating with OMP, the
following information will display:
(4) Reboot
Output: none
Problem:
MPX86_2-> displays.
Solution:
When board CPU version is running, the serial port output will be prohibited.
Its solution is to enter 3gzte, and then enter to see whether the prompt shows
up.
Check whether both ends of serial port cable are connected correctly.
Manually reset board to see whether there exists print on serial port. If not, the
serial port cable may go wrong.
Problem:
RUN LED fast flashes (5Hz), ALM LED is off. Continuously print on
HyperTerminal.
After a while, reset board and print shows the IP address is not OMP IP address.
unit number :2
processor number :0
Solution:
The above print indicates this board is not OMP. If the slot is correct (11 or 12
slot), then check whether rear board DIP switch is correct. Rack No. should be
0 and frame No. should be 1.
Problem:
Loading...
Solution:
The above print indicates BOOT version for debugging. When starting BOOT,
download VxWorks image from debugging PC.
Problem:
RUN LED fast flashes (5Hz), ALM LED is off. Continuously print on
HyperTerminal.
Finally print:
Solution:
The above print indicates BOOT fails to acquire ompcfg.ini from OMC server.
Troubleshoot as follows:
Check whether ftp service on OMC server is in normal condition. For instance,
try to ftp logon server on client (using server 129 address set in OMP serial
port). Use uep user name and see whether it succeed to logon.
Check whether ompcfg.ini file is under the directory saving OMC server
version file.
Give up master.
Solution:
The above print indicates ompcfg.ini has been acquired successfully. But it fails
to acquire version file.
Check whether the directory for saving OMC server version file has the
relevant version file.
Problem:
RUN LED fast flashes (5Hz), ALM LED fast flashes (2Hz). Enter
SCSShowMcmInfo on HyperTerminal or telnet, it displays database process
power up fails.
Solution:
The main reason for database process power-on failure is that ZDB file on OMP
does not exist or data configuration has error. If it is a new OMP board,
generally it lacks ZDB file.
FTP logon OMP, user name and password are omc/omc (or zte/zte). If using
OMP 128 address, it allows anonymity logon. View whether CfgTable.ZDB and
DBVer.ZDB are in the directories of /DOC0/DATA1 and /IDE0/DATA1. At
least one directory has ZDB file. Database process will preferentially read ZDB
file under /DOC0/DATA1.
If there is no ZDB file on OMP, then get ZDB from OMC server or use the
backup ZDB. And then upload it to OMP. ZDB file includes CfgTable.ZDB and
DBVer.ZDB. Generally, upload to both /DOC0/DATA1 and /IDE0/DATA1. If
the size of ZDB file is about tens of M, only upload to /IDE0/DATA1. Under
this condition, make sure that there is no ZDB file under the directory of
/DOC0/DATA1.
If there is ZDB file but it fails to power up, turn on DBS subsystem print in
UDPWatch on debugging PC. Find the reason for database process power-on
failure based on print.
Problem:
OMP board version has been running. But it resets in the course of running.
Other boards also reset during running.
Solution:
When OMP or other board resets, it is necessary to send the record file to R&D
Center to make analysis.
(8) When commissioning OMP at 6.20 platform, make sure ZDB file of OMP is in
the format of 6.20.
Note: this chapter describes the configuration differences between iBSC6.10 and iBSC
6.20, including iBSC6.20 supporting gigabit platform, SPB2 board, DTB2 board,
GUP2 board, IP Abis interface, IP Gb interface, IP A interface.
GERANsubnetwork
BSCmanagedelements
configurationsets
BSCglobalresource
Input User label and Subnetwork ID in Create GERAN subnetwork dialog box, as
shown in Figure 7.1-7. Click OK.
Note:
About the user label for each configuration objective, user can input the detailed
objective name for easy identifying. User label can also be auto-generated by software
(e.g. managed objective name+ID, in the degree-increasing sequence) and nothing is
required to input.
After GERAN Sub network is successfully created, the nodes should be displayed in
the topology tree as shown in Figure 7.1-8. Double-click the node and the
configuration properties of this objective should be displayed on the right of the Config
Management view.
In property page, click shortcut menu in the config management to modify the
properties. After modification is completed, click to save the parameters. Click to
ignore the modification.
In Configuration Resource Tree view, right-click created GERAN sub network for
example SS as shown in Figure 7.1-9 and click Delete in the popup menu. Delete in the
popup menu as shown in Click Yes in the confirmation message to delete GERAN sub
network as shown in Figure 7.1-10.
Caution:
If the property page of deleted GRAN sub network is opened, after deleting this
GERAN sub network, system should popup a message shown Managed objective is
deleted, please close its property page.
BSC managed elements are the sub-nodes of the GERAN sub network. One managed
element can only be included in one GERAN sub network.
In Configuration Resource Tree, right-click created GERAN sub network node, and
go to Create → BSC managed element in the popup menu, as shown in Figure 7.1-
11.
Enter the parameters in the Create BSC Managed Element dialog box and click OK,
the corresponding managed element is created in topology tree as shown in Figure 7.1-
12.
Master configuration set data is used to synchronize with the iBSC network elements.
It can be conducted with iBSC-iOMCR operations such as the data synchronization,
dynamic operations. ZXG10 NetNumen-G provides multi configuration sets and user
can create many configuration sets and switch them based on own needs. Notice that
after configuration set switch, user must synchronize all table so that the data will
comes into effect.
In Configuration Resource Tree, select BSC managed element node and right-click
Create → Config set as shown in Figure 7.1-13.
Enter the User Label in the popup window as shown in Figure 7.1-14. Click OK to
generate new config set.
2. Select the slave config set to switch and click the in the shortcut button and
a window pops up as shown in Figure 7.1-16.
Caution:
After switching the master and slave config sets, user must conduct data
synchronization hence the new master config set can come into effect in iBSC system.
In Configuration Resource Tree, right-click Master config set and click Create →
BSC function in popup menu as shown in Figure 7.1-17.
In the popup window, click to display all the contents. Enter proper parameters and
click OK as shown in Figure 7.1-18.
Caution:
The parameters for MCC, MNC, MNC3Digits, FuncExt cannot be modified after
creation. Please follow strictly as the data plan. The address of SNTP server is set
OMC SERVER IP instead of the IP address of OMP.
IBSC6.20 supports the gigabit platform. Modify the above marked parameters upon the
actual configuration.
[Purpose]
[Application]
[Prerequisites]
[Procedures]
2. Click BSC rack and Create BSC rack dialog box pops up as shown in Figure
7.2-20.
For the key parameters related with Figure 7.2-20, please refer to Table 7.2-3.
Rack Parameters
Rack ID
Integer type 1~5
Unit None
Default value 1
The rack number and shelf number are controlled by the DIP switch which
Description
currently can support 2 racks maximally.
Rack Parameters
Rack type
Integer type Standard rack
Unit None
Default value Standard rack
Description Currently only one rack type is available
When creating rack, using the following shortcut button in Table 7.2-4 can adjust the
rack view to the best.
ZXG10 iBSC system consists of three types of shelf: control shelf, resource shelf and
switch shelf. According to configuring position, configuration falls into following
categories:
● One-rack: the control shelf must be placed at the 2nd layer; the resource shelves
are usually placed at the 1st and 3rd layer; the switch shelf is usually placed at
the 4th layer.
● Double-Rack: the control shelf must be placed at the 2nd layer of the No.1 rack;
the resource shelves are usually placed at the 1st and 3rd layer of the No.1 rack,
and any layer of the No.2 rack; the switch shelf is usually placed at the 4th layer
of No.1 rack.
The shelf position of a double-rack in ZXG10 iBSC system is shown as in Figure 7.2-
21.
Refer to Table 7.2-5 for the classification and functions of each shelf. Refer to ZXG10
iBSC (V6.20) Hardware Manual for the configured boards and their description.
Type Function
It has global O&M function, global clock function, control panel handling and
CTC
Ethernet switch function.
It completes system access. It forms the subsystem for handling service. The
BUSN (Gk,
Gk platform only supports configuring Gk BUSN and the Mk platform only
Mk)
supports Mk BUSN.
PSN It provides the high-capacity and block-free IP switching platform.
Following shelf/board configuring procedures are based on the above supposed data.
Caution:
If BUSN is the Gk platform, it supports configuring GUIM board, SPB2 board and
GUP2 board.
If BUSN is the Mk platform, it supports configuring UIMU board, SPB board and GUP
board.
Control shelf is the control center of the ZXG10 iBSC system. It manages and controls
whole system, provides the control plane signaling handling for iBSC system, and
provides the clock supply and clock synchronization for system.
[Purpose]
[Application]
To create a new BSC control shelf along with its boards by manually initializing
configuration.
[Prerequisites]
[Procedures]
2. Right-click No.2 shelf of Rack 1 and select Create Shelf as shown in Figure
7.2-23.
3. Click Create Shelf and a dialog box pops up as shown in Figure 7.2-24.
4. Enter User Label, and select Control Shelf in Rack Type. Click OK and the
shelf with corresponding code and type is successfully created at the rack.
Before configuring any other board in the control shelf, user should configure
Confidential and Proprietary Information of ZTE CORPORATION.
ZXG10 iBSC (V6.20) Engineering Commissioning Guide Internal Use Only▲
OMP board first. OMP board must be configured in active/standby mode and in
slot 11 and slot 12.
Right-click slot 11, select Create board and a dialog box pops up as shown in
Figure 7.2-25.
In the Basic information tab, select OMP in Board function type drop-down
list, and select 1+1 backup mode or No backup mode depending on actual
configuration.
Caution:
OMP and OMP_SMP_CMP can be only configured at module 1 and RPU can be only
configured at module 2.
Right-click slot 9, select Create board and a dialog box pops up as shown in
Figure 7.2-27. Select UIMC in Board function type drop-down list, and select
1+1 backup mode or No backup mode depending on actual configuration.
Select Yes or No in the Clock check drop-down list and click OK.
Right-click slot 13, select Create board and a dialog box pops up as shown in
Figure 7.2-28. Select CLKG in Board function type drop-down list, and select
1+1 backup mode or No backup mode depending on actual configuration.
Click OK.
Right-click slot 15, select Create board and a dialog box pops up as shown in
Figure 7.2-29. Select CHUB in Board function type drop-down list, and select
1+1 backup mode or No backup mode depending on actual configuration.
Click OK.
CMP boards (1~6 pieces) may be plugged at the slot 1~8. The number of CMP
boards is optional according to the configuring capacity.
Right-click the corresponding slot in Control shelf, and click Create board in
the popup menu as shown in Figure 7.2-30.
Select Board function type as CMP, and select 1+1 backup mode or No
backup mode from Backup mode drop-down list, depending on actual
configuration.
Note:
If user need more than 1 CMP board, repeat Procedure 9. Then only difference is that
user needs to change Module No. The Module No must be different from 3 to 8.
Resource shelf, as a general service shelf, can be configured with all kinds of service
processing boards to constitute the general service processing subsystems. Resource
shelf can be configured with Abis-interfaces unit, A-interface unit, PCU unit and TC
unit. Two resource shelves constitute one RCBU (Resources board Configuration Basal
Unit). User can only add RCBU for system expansion.
[Purpose]
[Application]
1. To create a new BSC resource shelf along with its boards by manually
initializing configuration.
2. To create a new BSC resource shelf along with its boards for system expansion
configuration.
[Prerequisites]
[Procedures]
2. Right-click the corresponding position of the rack and select Create Shelf as
shown in Figure 7.2-32.
3. Click Create Shelf and a dialog box pops up as shown in Figure 7.2-33.
4. Enter User Label, and select Resource Shelf in Rack Type drop-down list.
Click OK and the shelf with corresponding code and type is successfully
created at the rack. Label the corresponding Slot No at the bottom of shelf.
Right-click required slot and click Create board in the popup menu as shown
in Figure 7.2-34.
At the Basic Information tab, select UIMU in Board function type drop-
down list, and select 1+1 backup mode or No backup mode depending on
actual configuration. Select Yes or No in the Clock check drop-down list.
At the Board connection information tab, set the data as defaulted as shown
in Figure 7.2-35 and click OK.
When BUSN is the Gk platform, it only configures SDTB2, SPB2 and GUP2
boards instead of SPB and GUP boards in iBSC6.10.
SPB board can be plugged at any slot but slot 9 and 10. If SPB board is created
at slot 15/16, there are some special restrictions described as below:
● If board is plugged in slot 15/16, the 8K clock base cannot be picked. If E1/T1
SPB board is configured, only one board can be plugged at either slot 15 or 16.
If E1/T1 SPB board is not configured, two boards can be plugged at both slot
15 and 16.
Right-click the board position at the rack, select Create board and a dialog box
pops up as shown in Figure 7.2-34.
Note:
1. If LAPD2 is selected in Board function type drop-down list, the Module No. is
depending on the actual configuration of CMP. PCM type in the PCM Information tab
can be automatically set as PCM at Abis.
2. If SPB2 is selected in Board function type drop-down list, the Module No. is 1.
PCM type in the PCM Information tab can be automatically set as PCM at A.
3. If GIPB2 is selected in Board function type drop-down list, the Module No. is 1.
PCM type in the PCM Information tab can be automatically set as PCM at GB.
In the PCM Information tab, user can select the parameters form Frame mode
and PCM No. drop-down lists based on own needs as shown in Figure 7.2-37.
The frame mode can be configured as Double frame, Multi-frame or Non-
frame.
Caution:
If LAPD2 board is configured, the E1 for external link will be reduced and less than
16. Usually 8 pieces of PCM can be configured.
DTB board can be configured at any slot except slot 9, 10, 15 and 16.
Right-click the board position at the rack, select Create board and a dialog box
pops up as shown in Figure 7.2-38.
At the Basic Information tab, select DTB in Board function type drop-down
list.
In the PCM Information tab, user can select the parameters form PCM Type,
Frame mode and PCM No. drop-down lists based on own needs as shown in
Figure 7.2-39. The frame mode can be configured as Double frame, Multi-
frame or Non-frame. Click OK to finish configuring DTB board.
Caution:
The frame mode configured at both ends of onsite PCM line must be consistent with
each other.
If GUP2 is used as BIPB board, it takes the priority to be plugged at slot 5~8
and 11~14. If it is plugged at any slot from slot 1~4,or 15~16, the adjacent slot
of GUP2 master/slave board can be configured with the board that do not
require the internal media port such as the DTB, SDTB2. If GUP2 is used as
DRTB2 board, it can be configured at any slot except 9 and 10.
Right-click the board position at the rack, select Create board and a dialog box
pops up as shown in Figure 7.2-40.
At the Basic Information tab, select DRTB2 in Board function type drop-
down list.
At DSP configuration information tab, user can select the parameters form
Trunk group, and Selected DSP drop-down lists based on own needs as shown
in Figure 7.2-41. Refer to Table 7.2-7 to learn the trunk parameter explanation.
Click OK to finish creating DTRB board.
Right-click the board position at the rack, select Create board and a dialog box
pops up as shown in Figure 7.2-42.
At the Basic Information tab, select BIPB2 in Board function type drop-
down list.
At DSP configuration information tab, user can select the parameters form
Selected DSP drop-down lists based on own needs as shown in Figure 7.2-43.
Click OK to finish creating BIPB2 board.
Right-click the board position at the rack, select Create board and a dialog box
pops up as shown in Figure 7.2-44.
At the Basic Information tab, select UPPB2 in Board function type drop-
down list.
At DSP configuration information tab, user can select the parameters form
Selected DSP drop-down lists based on own needs as shown in Figure 7.2-45.
Click OK to finish creating UPPB2 board.
Caution:
Right-click the slot on shelf, select Create board and a window pops up as shown in
Figure 7.2-46.
At the Basic Information tab, select EUIP in Board function type drop-down list.
Caution:
2. The path mode is selected upon the platform. If the platform is Gk one, select Path
Mode 5. If the platform is Mk one, select Path Mode 1.
At the HDLC Config tab as shown in Figure 7.2-29, add EUIP 2MHW No. and its
corresponding DT PCM No. The EUIP 2MHW No. max supports 64 E1, as shown in
Figure 7.2-47. Click OK to complete configuration.
Caution:
Right-click the slot on shelf, select Create board and a window pops up as shown in
Figure 7.2-48.
At the Basic Information tab, select IPBB in Board function type drop-down list.
Caution:
1. This IPBB board is the interface board for connecting with OMCB.
2. The path mode is selected upon the type of switch connecting with IPBB. If the
switch is of Mk type, select Path Mode 2. If the switch is of Gk type, select Path Mode
3.
3. Path Mode 2 is corresponding with RMINC and Path Mode 3 is corresponding with
RGER.
Switching shelf provides the IP switching function for the user data of iBSC internal
functionary entities, and it also provides QoS function for various users.
[Purpose]
[Application]
To create a new BSC switching shelf along with its boards by manually initializing
configuration.
[Prerequisites]
[Procedures]
2. Right-click No.4 shelf of rack 1 and select Create Shelf as shown in Figure
7.2-49.
3. Click Create Shelf and a dialog box pops up as shown in Figure 7.2-50.
4. Enter User Label, and select Switching Shelf in Rack Type drop-down list.
Click OK and the shelf with corresponding code and type is successfully
created at the rack. Label the corresponding Slot No at the bottom of shelf.
Two UIMC boards, which fulfill the control plan switching function, must be
configured at slot 15 and 16.
Right-click required slot and click Create board in the popup menu as shown
in Figure 7.2-51.
At the Basic Information tab, select UIMC in Board function type drop-
down list, and select 1+1 backup mode or No backup mode depending on
actual configuration. Select Yes or No in the Clock check drop-down list.
2 PSN boards, which fulfill the data switching function between wire and card,
must be configured at slot 7 and 8.
Right-click required slot and click Create board in the popup menu as shown
in Figure 7.2-52.
At the Basic Information tab, select PSN in Board function type drop-down
list, and click OK to finish PSN configuration.
GLI boards, which fulfill the Gigabyte Ethernet switching function, may be
plugged at slot 1~6 or slot 9~14. The board number is optional as per the
capacity and the boards must be configured in pairs. Configuration should stick
to the increasing sequence from left to right.
Note:
Right-click required slot and click Create board in the popup menu as shown
in Figure 7.2-53.
At the Basic Information tab, select GLI in Board function type drop-down
list.
At Board connection information tab, user can select proper parameters for
Connect type, Port No. and Connect unit as shown in Figure 7.2-54. Click
OK to finish GLI board configuration.
Note:
The parameter of Connect Unit is 911, whereas 1 stands for No.1 rack, 1 stands for
No.1 shelf, and 9 means No.9 slot.
1. Query Configuration
It indicates that the user checks the data of the managed object after the data
configuration.
2. Add Configuration
Add managed objects for the system, and set property value for them.
3. Delete Configuration
Delete existing managed objects and their configuration data in the system.
4. Modify Configuration
Modify the configuration data for the existing managed objects in the system.
In initial state, the shortcut button on the toolbar of the managed object
configuration is inactivated, which indicates modification is disabled. The user
should Apply for mutex permission to activate the button.
Confidential and Proprietary Information of ZTE CORPORATION.
ZXG10 iBSC (V6.20) Engineering Commissioning Guide Internal Use Only▲
Note:
The purpose to Apply for mutex permission is to avoid simultaneous data operation in multiple Clients,
which may lead to irregular data.
Take the data modification of master configuration set for instance, the
procedures include:
(1) Right click BSC Management NE Label, select Apply for mutex
permission from the drop-down list as shown in Figure 7.2-55.
(2) Click Apply for mutex permission, and a prompt window pops up, as
shown in Figure 7.2-56.
(3) Click Yes, and the mutex permission is applied successfully. An icon
will be shown on the topology tree as Figure 7.2-57. The shortcut
button has already been activated, which means that the user can
modify the configuration data under this management NE.
(4) After the data modification, right click BSC Management NE Label,
and select Release mutex permission from the drop-down list as
shown in Figure 7.2-58. After permission release, the configuration
data under this management NE can be operated by other users.
Caution:
Mutex permission can be released automatically by the system after the user log off
from the Client. In addition, the permission can also be acquired by force from other
Clients.
Purpose
Prerequisites
1. BSC management NE is created successfully, and a master configuration set is created in the system.
2. A slave configuration set that will be switched as the master one is created successfully.
Procedures
1. In Configuration Resource Tree, double click the slave configuration set just created,
whose property sub-view will be displayed in the right window of the Configuration
Management view as shown in Figure 7.2-59.
2. Click the slave configuration set to be switched, and then the shortcut button (Switch to
master configuration set) in the shortcut menu of the configuration management object. A
3. Click OK to complete the switchover between the data of master and slave configuration set.
The slave configuration set is switched as the master one as shown in Figure 7.2-61.
Follow-up Task
After the switchover, the data should be synchronized, in order to make the data of the new master
configuration set valid at the foreground.
Purpose
Prerequisites
Procedures
1. In Configuration Resource Tree, right click BSC Global Resource Label; select Export
as Excel→ Export Physical Data from the drop-down list as shown in Figure 7.2-62.
2. Click Export Physical Data, and a dialogue box to Save data pops up, select the directory
to save exported data file, input File Name as shown in Figure 7.2-63.
3. Click Save to export data, and then a prompt indicating the data is exported successfully
pops up as shown in Figure 7.2-64.
The exported physical data is saved as Excel format, the path is suggested to be:
\ISMG-V6.20.000a-\ums-clnt\template\excel\exceldata
Purpose
Prerequisites
Procedures
select Export into Excel → Data Export in the popup menu as shown in
Figure 7.2-65.
2. Click Data Export and a save window pops up. Select the save directory for
the exporting file and input the file name, as shown in Figure 7.2-66.
The exporting data is saved in the format of Excel. It is recommended to save the file
in the following directory.
.. \ISMG-V6.20.000a-\ums-clnt\template\excel\exceldata
Purpose
Prerequisites
Procedures
1. In Configuration Resource Tree, right click BSC Global Resource Label; select Export
as Excel → Export Software Data from the drop-down list as shown in Figure 7.2-68.
2. Click Export Software Data, and a dialogue box to Save data pops up, select the directory
to save exported data file, input File Name as shown in Figure 7.2-69.
3. Click Save to export data, and then a prompt indicating the data is exported successfully
pops up as shown in Figure 7.2-70.
The exported physical data is saved as Excel format, the path is suggested to be:
\ ISMG-V6.20.000a-\ums-clnt\template\excel\exceldata
Purpose
To export network planning & optimization data already configured in the system.
Prerequisites
Procedures
1. In Configuration Resource Tree, right click BSC Global Resource Label; select Export
as Excel→ Export Network Planning & Optimization Data from the drop-down list as
shown in Figure 7.2-71.
2. Click Network Planning & Optimization Data, and a dialogue box to Save data pops up,
select the directory to save exported data file, input File Name as shown in Figure 7.2-72.
3. Click Save to export data, and then a prompt indicating the data is exported successfully
pops up as shown in Figure 7.2-73.
The exported physical data is saved as Excel format, the path is suggested to be:
\ ISMG-V6.20.000a-\ums-clnt\template\excel\exceldata
Purpose
To back up data.
Prerequisites
Procedures
2. Click Data Backup and a window pops up. Select proper Storage path, enter
File name prefix and Backup remark and select managed elements to
backup as shown in Figure 7.2-75. If only master config set are to backup,
please only select the Only backup active ConfigSet(s).
Purpose
To recover data.
Prerequisites
Procedures
4. Select the config set to recover and click OK. A window pops up indicating
that the config set is added in BSC management NE ID, as shown in Figure 7.2-
80.
5. After recovering, user can click to set master configuration set, and a window
pops up as shown in Figure 7.2-81.
Confidential and Proprietary Information of ZTE CORPORATION.
ZXG10 iBSC (V6.20) Engineering Commissioning Guide Internal Use Only▲
6. User can select master config set to switch, and click Default to set the master
config set. Click OK to complete the switch as shown in Figure 7.2-82.
After completion, the recovered configuration set is shown in the topology tree.
If Set Master Configuration Set is executed after data recovery, the
configuration set recently switched as master one will be labeled as shown in
Confidential and Proprietary Information of ZTE CORPORATION.
ZXG10 iBSC (V6.20) Engineering Commissioning Guide Internal Use Only▲
Figure 7.2-83.
Caution:
After the data is recovered and switched as master configuration set, all table
synchronization should be executed to make it valid.
Information
Purpose
Prerequisites
Procedures
2. Click Create BSC Rack with Template, a window pops up as shown in Figure 7.2-85,
select Template Type and Template as per requirement.
If System is selected, all the available templates in the system are displayed in the drop-
down list of Template.
If Self-defined is selected, all the available templates defined by the user in the system are
displayed in the drop-down list of Template.
Caution:
Generally speaking, it should be initial state when creating with template, there should
not be BSC rack in the system. Otherwise if the BSC rack No. in the self-defined
3. Click OK to complete creation. The created BSC Rack label is displayed on the
Configuration Resource Tree, and the shelves and boards in the rack are configured
according to the template as shown in Figure 7.2-86.
Purpose
To export the BTS created by the user and its configuration data as self-defined template.
Prerequisites
The BTS and its configuration data to be exported have been created successfully, and BCCH TRX has
been configured in the BTS.
Procedures
1. In Configuration Resource Tree, right click to select Template from the drop-down list as
shown in Figure 7.2-87.
2. Click Export BTS Template, a window pops up as shown in Figure 7.2-88. The template
name to save this template is set by the user.
3. Click OK and a prompt pops up indicating the template is exported successfully as shown in
Figure 7.2-89. The exported template is saved by default in .ztd format in the path
%OMCHOME%\ums-clnt\template\xml\bts.
Purpose
Prerequisites
Procedures
2. Click Create Site by template and a window pops up as shown in Figure 7.2-
91.
(1) Input Site ID, and select Module No. and Template Type depending on actual
configuration.
Caution:
Site ID can be re-set in the view, thus the site ID conflict between self-defined BTS
and existing BTS which leads to unsuccessful creation can be avoided.
Note:
(2) Click Cmm Config, and configure PCM, refer to 8.1.1 BS20 Configuration.
(3) Click Radio Config to configure the site parameters. The detailed method will
be described in 8.3 Cell Creation and 8.5 TRX Creation.
Purpose
Commissioning indicates the BTS can work normally; Debugging indicates the BTS cannot work
Prerequisites
Note:
The BTS is in commissioning state by default after it is created successfully.
Procedures
1. In Configuration Resource Tree, right click BTS ID, select Debugging from the drop-
down list as shown in Figure 7.2-92.
2. Click Debugging, an icon will be displayed in front of the original BTS ID icon ,
3. To recover commissioning state, in the Configuration Resource Tree, right click BTS ID,
select Commissioning from the drop-down list as shown in Figure 7.2-93.
4. Click Commissioning, the icon in front of site ID icon disappears, which indicates
the BTS is in commissioning state.
Information
Commissioning indicates the BTS can work normally; Debugging indicates the BTS cannot work normally
Purpose
Prerequisites
Note:
The BTS is in commissioning state by default after it is created successfully.
Procedures
Purpose
Prerequisites
Procedures
2. Click Set external alarm and a window pops up as shown in Figure 7.2-97.
For each dry contract node, User can select 0 or 1 from drop-down list.
Note:
Confidential and Proprietary Information of ZTE CORPORATION.
ZXG10 iBSC (V6.20) Engineering Commissioning Guide Internal Use Only▲
7.3 IP Configuration
[Purpose]
[Prerequisites]
[Procedures]
1. In Configuration Resource Tree, right click Configuration Set →BSC Global Resource
Label → IP Configuration → Interface Configuration → Create → Interface as shown
in Figure 7.3-98.
3. To configure EUIP interface information, enter the IP address and mask to access to EUIP from
SDR as shown in Figure 7.3-100.
4. Repeat Procedure 1 to create RPU (IPABIS) interface as shown in Figure 7.3-101, select RPU as
Board function type.
5. Configure RPU interface information as shown in Figure 7.3-102. Enter the virtual address to
access to iBSC from SDR, the mask should be 255.255.255.255.
6. Repeat Procedure 1 to create IPBB interface as shown in Figure 7.3-103, select IPBB.
7. Configure IPBB interface information as shown in Figure 7.3-104. Input the IP address and mask
to connect to iBSC from OMCB, which serve as the gateway address from OMCR to SDR.
[Purpose]
[Prerequisites]
[Procedures]
1. In Configuration Resource Tree, right click to select Configuration Set → BSC Global
Resource Label → IP Configuration → Interface Backup Group → Create → Interface
as shown in Figure 7.3-105.
2. Select corresponding sub-system, module, unit, sub-unit, port No. of IPBB board as shown in
Figure 7.3-106.
[Purpose]
[Prerequisites]
[Procedures]
1. In Configuration Resource Tree, right click Configuration Set →BSC Global Resource
Label → IP Configuration → IPOVERE1 Configuration → Create →IPOVERE1
Configuration as shown in Figure 7.3-107.
2. Enter EUIP board information and IPOVERE1 initial TS and terminate TS as shown in Figure
7.3-108.
Caution:
3. In Configuration Resource Tree, right click Configuration Set → BSC Global Resource Label
→ IP Configuration → IPOVERE1 Configuration XXX → PPP Parameter Configuration as
shown in Figure 7.3-109.
4. Configure PPP parameter, enter the IP address of SDR as shown in Figure 7.3-110. For the
configuration of SDR IP address, please refer to the Chapter IV of ZXSDR B8200 GU906&R8860
(V3.06) Commissioning Guide.
After data configuration, synchronization should be carried out to validate the data in
BSC and BTS. Data synchronization includes all table synchronization and incremental
synchronization.
Purpose
Prerequisites
Procedures
1. Right-click GERAN sub network for example ME6, and click Config Data
management → Synchronize all tables in the popup menu, as shown in
Figure 7.3-111.
2. Click Synchronize all tables to check the validation of global data, after which
click OK and a window pops up as shown in Figure 7.3-112.
Caution:
Save it indicates to save the data in OMP hardware, it is suggested to select Yes in
order to avoid data loss.
Caution:
All table synchronization only works for the data in master configuration set.
Purpose
If part of the data is modified, in order to speed up synchronization, only the modified tables need to be
synchronized. This item focuses on the incremental synchronization.
Prerequisites
Procedures
1. In Configuration Resource Tree, right click BSC Management NE User ID, select
Config Data Management → Synchronize modified tables from the drop-down list as
shown in Figure 7.3-114.
2. Execute global data validation check and click OK, a window pops up as shown in Figure
7.3-115.
Caution:
Save it indicates to save the data in OMP hardware, it is suggested to select Yes in
order to avoid data loss.
3. After the parameters are configured properly as per requirement, click OK to start
synchronization, and then a window pops up as shown in Figure 7.3-116.
Caution:
Incremental synchronization only works for the data in master configuration set.
Data configuration is the core operation of BSC system, which is of great importance
in the entire system. Any faults in the data configuration may affect the system running
normally. Therefore the operator should pay attention to the following points when
configuring and modifying data:
1. Before data configuration, relevant data for system running should be prepared
2. Before any data modification, the current data should be backed up; after the
modification is complete, the data is synchronized to BSC and BTS, and confirmed
with its validity; at this time the data should be backed up again.
3. The data configured and modified in NM Client should be valid after synchronizing
to BSC and BTS. The modification to the current running system data should be
checked carefully before transmitting, so as to ensure normal system running with
correct data.
Caution:
Since many parameters should be configured, only the important ones and the ones
must be configured are listed in this book, which should be configured according to the
instruction; other non-specified parameters should keep the default values, which are
not mentioned here.
Public resource
configuration
External site
configuration
Transparent channel
configuration
(Optional)
Other configuration
(Optional)
Software
Figure 7.3-117 installation
Data Configuration Flow
BSC physical equipment configuration includes creating BSC rack, shelves and
boards, etc. See 7.3 BSC Physical Configuration for details.
(1) The use can select All E1 or All IP mode according the on-site environment.
● With internal TC, and E1 mode for A interface transmission on user plane and
control plane, E1 at A interface should be configured.
● With external TC, and E1 mode for Ater interface transmission on user plane
and control plane, E1 at Ater interface should be configured.
(2) The configuration can be selected according to the on-site needs, so that the
transmission modes on user plane and control plane can be different (E1 on
user plane, IP on control plane; or IP on user plane, E1 on control plane).
4. GB Interface Configuration
BTS and radio configuration includes creating various BTS, BTS cascade, cell,
frequency hopping, transceiver, neighbour cell interference / switchover /
reselection / switchover & reselection, creating UTRAN neighbour cell
switchover / reselection / switchover & reselection. See Chapter 8 BTS and
Radio Configuration for details.
8. Other Configuration
9. Software Installation
After the configuration, the user can operate on dynamic data or cell radio.
Caution:
It is suggested to synchronize data after the operation according to each chapter, i.e. all
table synchronization or incremental synchronization, so as to synchronize the data
configured to BSC and make it valid at foreground, otherwise the virtual data in NM
system cannot be valid.
● V2 BTS includes BTS (V2.0), BS21, BS21 (V2.0), BS30, BS30 (V7.2), and
OB06.
The methods to create all the above BTS physical equipment are described below.
Purpose
Note:
Prerequisites
Procedures
2. Click Site and a window pops up as shown in Figure 8.1-119. Select BS20 for
Site type. Refer to Table 8.1-8 for the relevant parameters.
● The following parameters are important including User label, Site type, Clock
resource, Module number, Connect mode, Access type, Serial No.
Note:
Site Parameters
User label
Integer type Character string: 1~40
Unit None
Default value None
Description Unique user label (letters or numbers) given to every cell.
Site ID
Integer type 1 ~ 1536
Unit None
Default value 1
Description The site code in home BSC
Site Type
BS20, BS21, BS21V20, BS30, BS30V12, OB06, B8018, B8112, M8202, M8206,
Integer type
S8001, B8200
Unit None
Default value BS20
Description Select the site type to create.
Longitude
Integer type -180.0000 ~ 180.0000
Unit Degree
Default value 180
Description Identify the longitude of site.
Latitude
Integer type -90.0000 ~ 90.0000
Unit Degree
Default value 90
Description Identify the latitude of site.
Clock source
Integer type Internal, network, GPS, IP
Unit None
Default value Internal
Internal synchronization indicates that the internal crystal oscillator is adopted to
generate 13M clock, there is no reference resource, which is easy to offset;
network synchronization indicates that the clock is delivered from BSC with E1,
Description which is synchronized in BTS.
Currently all the sites supports internal synchronization and network
synchronization. Only 8000 series BTS supports GPS synchronization, only SDR
(B8200) supports IP synchronization.
Module No.
Integer type Depending actual configuration
Site Parameters
User label
Unit None
Default value 3
Description Configure the module depending on the actual data plan.
Access Mode
Optional values E1 access, IP access
Unit None
Default value E1 access
If the BTS type is BS20, BS21, BS21V20, BS30, BS30V12, OB06 or M8202,
this parameter keeps the default value E1 access, which cannot be modified. If the
Parameter
BTS type is B8018, B8112 or M8206, the parameter can be E1 access or IP
description
access according to the on-site situation. If BTS type is S8001 or B8200, this
parameter keeps the default value IP access, which cannot be modified.
Satellite Mode at Abis Interface
Optional value Yes, No
Unit None
Default value No
Parameter
Configure according to the on-site situation.
description
Permitted Access Bandwidth (Kb)
Optional values 1 ~ 65535
Unit Kb
Default value 1
Parameter If BTS type is S8001 or B8200, this parameter can be modified to describe the on-
description site access bandwidth.
GPS Frame No. Offset
Optional
0 ~ 42431
values
Unit None
Default value 0
It refers to the frame No. offset value configured in each GSM cell in GSM entire
Parameter
network synchronization, when all the SDR adopts the same Frame No. reference.
description
This parameter is effective only when Clock Resource is set as GPS synchronization.
Serial No.
Optional
None
values
Unit None
Default value 00-00-00-00-00-00 00-00-00-00-00-00
Site Parameters
User label
This parameter can be modified when BTS type is S8001. The former 12 digits refer
Parameter
to S8001 MAC address, and the latter 12 digits refer to the authentication sequence
description
number (currently all digits are 0).
5. Click site rack and a window pops up as shown in Figure 8.1-121. Enter proper
parameters and click OK. Double-click the site rack ID and rack map should
display.
Right-click the blank space at the upper part as shown in Figure 8.1-122. Select
Create Shelf in the popup menu.
Create shelf dialog box pops up as shown in Figure 8.1-123. Click OK.
Note:
PDM board is created after the creation of common shelf.
Right-click the CMM panel position and select Create Shelf in the popup menu
as shown in Figure 8.1-124.
In the popup window, select CMM for Panel Type, BSC for Connection
Model, and Connect for the PCM Connection Type as shown in Figure 8.1-
125.
Click the Connect button and a window pops up as shown in Figure 8.1-126.
This figure has list the PCM number available for BSC.
● Set Abis Pool No. and select time slot number from the TS No. drop-list, click
● According to the actual time slot needs, click to allocate OMU time slot
number.
Caution:
For E1, OMU time slot number is 16 and 25 ~ 31. For T1, OMU time slot number is 16
~ 23.
Right-click the proper position as shown in Figure 8.1-128, and click Create
Panel.
Create shelf dialog box pops up as shown in Figure 8.1-129, click OK.
Right-click CDU position and select Create Panel as shown in Figure 8.1-130.
Create panel dialog box pops up as shown in Figure 8.1-131. User can select
CDU10M, CDU8M, CEU or RDU in the Panel Type drop-down list. Click
OK to competed configuration. The creating method of the other AEM in the
same layer is the same.
Right-click TRM panel position and select Crate Panel as shown in Figure 8.1-
132.
Create panel dialog box pops up as shown in Figure 8.1-133. User can select
proper parameters in the Panel Type drop-down list. Select TX/RX in the list
of TX/RX Board, click Add, and configure the connection status between this
TRM and TX/RX. Generally only the Level 1 TX and RX on the left should be
configured. Click OK to complete configuration.
Note:
1. There are four types panel: TRM, STRU, SPAU, and TRME, where TRME is
EDGE TRX, STRU and SPAU are used for 80W configuration;
2. In this interface, the value of Panel Type is related with that of Panel No.. For
BS20, if the panel No. is 2 or 4, the panel type should be TRM, STRU or TRME; if the
panel No. is 3 or 5, the panel type should be TRM, SPAU, or TRME.
9. User can add slave rack referring to the method of creating master rack.
Select the slave rack type and click OK to complete configuring slave rack.
Caution:
Purpose
Prerequisites
Procedures
1. The method of configuring BS21 site is similar with that of configuring BS20;
the only difference is that the site type is BS21.
User only needs to create No.3 shelf, and the No.1 and 2 shelves are created
Confidential and Proprietary Information of ZTE CORPORATION.
ZXG10 iBSC (V6.20) Engineering Commissioning Guide Internal Use Only▲
automatically by system.
Right-click the blank space at the upper part as and select Create Shelf as
shown in Figure 8.1-136.
3. The method of creating AEM, CMM and TRM panels are similar with that of
BS20. The panels are successfully created as shown in Figure 8.1-138.
Purpose
Prerequisites
Procedures
1. The method of configuring is similar with that of configuring BS20; the only
difference is that the site type is BS21 (V2.0).
User only needs to create No.3 shelf, and the No.1 and 2 shelves are created
automatically by system.
Right-click the blank space at the upper part as and select Create Shelf as
shown in Figure 8.1-139.
3. The method of creating AEM, CMM and TRM panels are similar with that of
BS20. The panels are successfully created as shown in Figure 8.1-141.
Purpose
Prerequisites
Procedures
1. The method of configuring BS21 site is similar with that of configuring BS20;
the only difference is that the site type is BS30.
User only needs to create No.3 shelf, and the No.1 and 2 shelves are created
automatically by system.
Right-click the blank space at the upper part as and select Create Shelf as
shown in Figure 8.1-142.
3. The method of creating AEM, CMM and TRM panels are similar with that of
BS20. The panels are successfully created as shown in Figure 8.1-144.
Purpose
Prerequisites
Procedures
1. The method of configuring BS30 (V1.2) site is similar with that of configuring
BS20; the only difference is that the site type is BS30V12.
Right-click the blank space at the lower part as and select Create Shelf as
shown in Figure 8.1-145.
Right-click the DPM position and select Create Panel as shown in Figure 8.1-
147.
Create panel dialog box pops up as shown in Figure 8.1-148. Click OK.
Caution:
If there are more than one rack on site, recourse shelf is required to increase.
(2) Configure DPM and TRM panels in the same way. The divider of BS30 (V1.2)
can only be the DPM in the same layer.
Purpose
Prerequisites
Procedures
1. For initial configuration refer to Configuring BS20, the only difference is that
the Site Type selected is OB06.
2. The method of configuring Common Shelf, resource shelf, and PDM, AEM,
CMM, and TRM panels is the same with that of BS20.
Purpose
Prerequisites
Procedures
1. For initial configuration refer to Configuring BS20, the only difference is that
the Site Type selected is B8018.
Right-click the blank space at the upper part as shown in Figure 8.1-153. Select
Create Shelf in the popup menu.
Create shelf dialog box pops up as shown in Figure 8.1-154. Click OK.
Note:
Caution:
If the Access Mode is set as E1 Access in Figure 8.1-119, it should be EIB board here,
while if the Access Mode is IP Access, it should be FIB board. The configuration mode
is the same.
Right-click the EIB panel position and select Create Shelf in the popup menu
as shown in Figure 8.1-155.
Create panel dialog box pops up as shown in Figure 8.1-156. Click OK.
For E1 access, the creation procedures are the same with that of BS20.
For IP access, the creation procedures are the same with that of FIB board.
Create shelf dialog box pops up as shown in Figure 8.1-158. Click OK.
AEM includes four options: CDU10M, CDU8M, CEU, RDU and FCU. The
configuring method is the same with that of BS20.
Caution:
Note:
For double-TRX DTRU, BTS should be configured with two panels and two
slots. System should allocate separately panel for each logical TRX.
Right-click slot no. 2 in B8012 radio shelf and click Create Panel in the popup
menu as shown in Figure 8.1-159.
A window pops up as shown in Figure 8.1-160, select DTRU for Board Type,
Select TX/RX in the list of TX/RX board, click Add, and configure the
connection status between this DTRU and TX/RX. Generally only the Level 1
TX and RX on the left should be configured. Choose IRC and TRX Supports
Antenna Hopping according to the on-site situation.
Note:
1. IRC (Interference Reject Coalition): IRC interference refuses the combination, is
similar to MRC. When the diversity antenna is used, the two antennas (or, one
crossover polarity antenna) receives the radio signals at the same time and sends the
better (Stronger) signals to BTS receiver unit.
2. TRX Supports Antenna Hopping: It indicates the same carrier is transmitted by
two antennas by turns, which enables the receiver enhance receiving quality when
adopting diversity reception. When it is configured, the transmitting ports TX1 and
TX2 of the two carriers in dual-density should be connected to different transmitting
antennas.
DTRU panel has 5 kinds of work modes, please refer to Table 8.1-10.
Caution:
After DTRU right panel and left panel both are configured, user can right-click the
panel property to modify the work mode. If Dual Carrier is changed into Single
Carrier, click OK in Figure 8.1-160, the right panel should be deleted automatically.
Purpose
Prerequisites
Procedures
1. For initial configuration refer to Configuring BS20, the only difference is that
the Site Type selected is B8112.
Right-click the blank space at the upper part as shown in Figure 8.1-162. Select
Create Shelf in the popup menu.
Create rack dialog box pops up as shown in Figure 8.1-163. Click OK.
Note:
PDM board can be created after the creation of common shelf.
AEM includes four options: CDU10M, CDU8M, CEU, RDU and FCU. The
configuring method is the same with that of BS20.
Caution:
FCU can only be configured at two even slots, it is invalid to configure other AEM
board in adjacent slots,.
Create shelf dialog box pops up as shown in Figure 8.1-165. Click OK.
Caution:
In Figure 8.1-119, for E1 access, here is EIB. In Figure 8.1-119, for IP access, here is
FIB, the configuration steps are the same.
For E1 access, the creation procedures are the same with that of B8018.
For IP access, the creation procedures are the same with that of FIB board.
Right-click the EAM position and select Create Panel in the popup menu as
shown in Figure 8.1-166.
Create panel dialog box pops up as shown in Figure 8.1-167. Click OK.
Purpose
Prerequisites
Procedures
1. For initial configuration refer to Configuring BS20, the only difference is that
the Site Type selected is M8202.
Right-click the blank space at the upper part and select Create Shelf in the
popup menu as shown in Figure 8.1-169.
Create shelf dialog box pops up as shown in Figure 8.1-170. Click OK.
Note:
PDM board is created after the creation of common shelf.
Right-click the resource shelf position and select Create Shelf in the popup
menu as shown in Figure 8.1-171.
Create shelf dialog box pops up as shown in Figure 8.1-172. Click OK.
There are five panel types: CDU10M, CDU8M, CEU, RDU, and MDUP. The
creation procedures are the same with that of B8018.
Purpose
Prerequisites
Procedures
1. For initial configuration refer to Configuring BS20, the only difference is that
the Site Type selected is M8206.
Right-click the blank space at the upper part and select Create Shelf in the
popup menu as shown in Figure 8.1-174.
Create shelf dialog box pops up as shown in Figure 8.1-175. Click OK.
Note:
PDM board is created after the creation of common shelf.
Caution:
In Figure 8.1-119, for E1 access, here is EIB. In Figure 8.1-119, for IP access, here is
FIB, the configuration steps are the same.
For E1 access, the creation procedures are the same with that of B8018.
For IP access, the creation procedures are the same with that of FIB.
Right-click the resource shelf position and select Create Shelf in the popup
menu as shown in Figure 8.1-176.
Create shelf dialog box pops up as shown in Figure 8.1-177. Click OK.
Panel type is MDUP. The creation procedures are the same with that of B8018.
Caution:
Purpose
Prerequisites
There are two modes for IP transmission, including IP Over IP and IP Over E1.
3. BIPB board is created on BSC rack, and DSP No. supporting IP is available.
See the DSP No. configuration in the sub-view of DSP Configuration
Information.
2. DTB board is created on BSC rack, and PCM in EUIP Type should be
configured.
3. EUIP board is created on BSC rack, and the configuration in the sub-view
of HDLC Configuration Information is complete.
4. BIPB board is created on BSC rack, and DSP No. supporting IP is available.
Caution:
Configuration procedures for IP Over IP and IP Over E1 are generally the same except
for the situation to create interface: RPU and IPBB interface should be created in IP
Over Ip mode; RPU and EUIP interface should be created in IP Over E1 mode.
Procedures
(2) Click Interface, and a window pops up as shown in Figure 8.1-180. Select
RPU as Board Function Type.
(3) Click Next, and a window pops up as shown in Figure 8.1-181. Enter proper
parameters and click OK to complete configuration.
(2) Double click BSC Global Resource Label, select IP Information sub-view,
change the IPABIS address with the IP address configured in Figure 8.1-181
and save it, as shown in Figure 8.1-182.
Caution:
If the iBSC virtual address configured on RPU is modified, CMP (or the OMP in the
same environment with CMP), IPBB and BIPB board should be reset after each
modification.
Caution:
The procedures and parameter description are the same for creating IPBB and EUIP
interfaces. Take the procedures to create IPBB interface for example:
(2) Click Interface, and a window pops up as shown in Figure 8.1-184, select
IPBB as Board Function Type.
(3) Click Next, a window pops up as shown in Figure 8.1-185. Enter proper
parameters, click OK to complete configuration.
Caution:
Static route needs to be created only when S8001 and RPU are not in the same network
section.
(2) Click Static Route, and a window pops up as shown in Figure 8.1-187. Enter
proper parameters, click OK to complete creation. See Table 8.1-11 for related
parameters.
The procedures to create BTS node label of S8001 site is the same as create that
of BS20, except for:
Note:
Initial rack map is created after the creation of BTS node.
Information
BS8200 is GSM/W dual-mode BTS, physical data and WCDMA radio parameter are
configured in OMCB, the radio parameter in GSM equipment is configured the same
as other BTS.
This item focuses on creating BTS node label, initial rack map of BS8200 sites at GSM
side.
Purpose
Prerequisites
Procedures
The procedures to create the BTS node label and initial rack map are the same as that
of BS20, except that the BTS Type is set as BS8200.
To save the transmission and cost, user can configure the sites by connecting several
sites together.
Prerequisites
Procedures
Note:
Suppose the upper level site is BTS (V2.0) and site ID is 2, the lower level site is
BS21.
Configure the BS21 site ID, initial rack map, shelf and AEM and TRM panels,
referring to Section 8.1.2 BS21, as shown in Figure 8.2-189.
(1) Right-click CMM position and select Create Panel as shown in Figure 8.2-
190.
(2) Select CMM in Panel Type dropdown list, BSC in Connection Model
dropdown list, 2 in Rack No. dropdown list, Connect in Connection Type
dropdown list as shown in Figure 8.2-191.
This figure has list the PCM number available for BSC. Select proper PCM
number.
When configuring cascading sites, make sure that the O&M link of the master
rack in cascading sites should be configured according to the limitation to
power-off bypass, which indicates that the O&M link of the master rack in V2
sites should be configured at the Ports A and D symmetrically, and those in
B8018, B8112, M8202, M8206 should be configured at Ports A and E
symmetrically. See Table 8.2-12 for power-off bypass description.
Caution:
Due to the power-off bypass limitation, the existing port between upper-level cascading
site and BSC should be queried before selecting PCM No. as shown in Figure 8.2-192,
so as to locate the port for the connection between upper-level and lower-level sites.
(4) Click OK to complete the configuration of a PCM line as shown in Figure 8.2-
193.
● Set Abis Pool NO. and select time slot number from the TS No. drop-list, click
● Depending on the actual time slot needs, click to allocate OMU time
slot number.
Caution:
(5) Click OK to complete CMM configuration. Generally only one CMM panel is
installed as default. User can install the second CMM panel based on own
needs.
To create cell.
Prerequisites
2. If the cell supports GPRS or EDGE, NSE and UPPB boards should be created
first.
Procedures
● User label
● BTS ID
The value range is 1~6, which can be adjusted according to the quantity of the
cell created. The default value should be kept.
● Cell type
● MCC (Country Code), MNC (Network Code), LAC (Location Area Code), CI
(Cell Identity), NCC (Network Color Code) and BCC (Base station Color
Code).
The above mentioned are negotiable data, which can be configured as per on-
site environment. The combination of MCC+MNC+LAC+CI is unique.
● Frequency band
● Subcell used
● SGSN label
● DSP label
Note:
After the cell is created, switchover control, power control, UTRAN cell control,
UTRAN switchover control, adjacent cell reselection 1are also selected, in which
adjacent cell reselection can be created separately, while the others can only be
Prerequisites
Procedures
To create TRX.
Prerequisites
Procedures
2. Click TRX and a window pops up as shown in Figure 8.5-201. If the site is the
IP-access one, the window IP information will be added. Configure all
parameters and click OK to complete configuration.
● Sub-Cell ID
When creating a cell, the parameter Use sub-cell should be configured as Yes.
Select First Sub-Cell or Second Sub-Cell as per the on-site location of the TRX.
● TRX Type
For a common cell, this parameter should be configured as Common TRX; for
an extension cell which does not support sub-cell, TRX Type should be
Extension TRX; for an extension cell which supports sub-cell, it should be
Extension TRX in Sub-Cell 1, which is not specified in Sub-Cell 2.
Only one BCCH TRX should be configured within a cell. If a BCCH TRX has
already been configured in the cell, this parameter is set as No and cannot be
modified when re-creating the TRX.
● Frequency hopping
● Frequency point
Select the physical location of the carrier frequency panel corresponding with
● TSC
Caution:
If it is configured as BCCH TRX, all the TSC in this TRX channel should be consistent
with the BCC (Base station Color Code) in its cell.
● PDCH
IP Information Sub-view:
It refers to the DSP in BIPB board supporting IP, which is configured according
to on-site environment.
● Port No.
Prerequisites
BSC, site, cell and GERAN external cell are all successfully created.
Procedures
2. Input User label and parameters in Create Adjacent Interference cell dialog
box as shown in Figure 8.6-203.
Click , and select target cell from the interface as shown in Figure
8.6-204.
Prerequisites
BSC, site, cell and GERAN external cell are all successfully created.
Procedures
206.
Note:
When creating a cell, this cell is defaulted as the reselection cell of itself by system.
Prerequisites
BSC, site, cell and GERAN external cell are all successfully created.
Procedures
Prerequisites
BSC, site, cell and GERAN external cell are all successfully created.
Procedures
Note:
The user can double click Adjacent cell switchover and reselection in the
Configuration Resource Tree, click in the view on the right, and a window pops
up as shown in Figure 8.9-212.
Caution:
If the cell is used as the adjacent cell of a switchover OR reselection cell, it cannot be
used as the adjacent cell of a switchover AND reselection cell.
Prerequisites
BSC, site, and UTRAN external cell are all successfully created.
Procedures
Prerequisites
BSC, site, and UTRAN external cell are all successfully created.
Procedures
Prerequisites
BSC, site, and UTRAN external cell are all successfully created.
Procedures
Note:
The user can double click UTRAN Adjacent cell switchover and reselection in the
Configuration Resource Tree, click in the view on the right, and a window pops
up as shown in Figure 8.12-221.
Caution:
If the cell is used as the adjacent cell of a UTRAN switchover OR UTRAN reselection
cell, it cannot be used as the adjacent cell of a UTRAN switchover AND reselection
cell.
Prerequisites
Procedures
Cell type, MCC, MNC, Frequency band, BCCH frequency, LAC, CI, NCC,
BCC
Caution:
If it is set as Yes for GPRS service supported, the sub-view GPRS properties should be
added in Figure 8.13-224. Generally the default parameters in the sub-view should be
kept.
Prerequisites
Procedures
UTRAN cell type, MCC, MNC, Frequency, LAC, RNC ID, C ID, Scrambling
code, TX diversity indication, Route area code
Caution:
If the TDD is selected as UTRAN Cell Type, user should add UTRAN adjacent cell
bandwidth and add parameters for Whether Sync Case/TSTD is applied in Figure
8.14-226. Besides, the value range of UTRAN Adjacent Cell Frequency is
correspondingly changing.
9. GB Interface Configuration
9.1 E1 GB Interface Configuration
Information
Purpose
Prerequisites
Note:
Procedures
2. Click NSE and Create NSE box should pop up as shown in Figure 9.1-228.
Input proper parameters by referring Table 9.1-13 and click OK.
NSE Parameters
NSE ID
Integer type 0 ~ 65535
Unit None
Default value 0
Description To identify NSE. It should be consistent with SGSN configuaration.
Subnet type
Integer type Frame trunk, IP
Unit None
Default value Frame trunk
To identify subnet type. As per the protocol48.018, there are two types in
Description subnet: frame trunk and IP.
For E1 GB interface, select frame trunk.
Purpose
Prerequisites
Procedures
2. Click BRCH and Create BRCH box should pop up as shown in Figure 9.1-
230. Input proper parameters by referring Table and click OK.
BRCH Parameters
SGSN ID
Integer type Depending on actual configuration of SGSN
Unit None
Default value 1
Once supporting Flex GB, iBSC connects with multiple SGSNs. It
Description
distinguishes those SGSNs.
Physical Link
Integer type 1 ~ 1000
Unit None
Default value 1
Description To identify physical link
Unit
BRCH Parameters
Integer type Depending on actual configuration of GIPB (or GIPB2)
Unit None
Default value None
Description To identify GIPB unit
CPU ID
Integer type 1, 2, 3, 4
Unit None
Default value 1
CPU sub card coding. This relation between CPU ID and PCM ID is: CPU1
Description manages PCM9 ~ PCM12; CPU2 manages PCM13 ~ PCM16; CPU3
manages PCM17 ~ PCM20; CPU4 manages PCM21 ~ PCM24.
Channel
Integer type 1 ~ 256
Unit None
Default value 1
Description This channel ID is a CPU internal link logical ID.
MCC Start Time Slot
Integer type 0 ~ 127
Unit None
Default value 0
Signaling link corresponds to the MCC start time slot number. One CPU at
present consists of two MCCs. Each MCC has 128 time slots. Now only the
Description
No. 2 MCC is in use.
Note: different BRCH cannot occupy the same MCC timeslot.
PCM
Integer type 9 ~ 24
Unit None
Default value None
PCM number of accessing GIPB. This relation between CPU ID and PCM ID
Description is: CPU1 manages PCM9 ~ PCM12; CPU2 manages PCM13 ~ PCM16;
CPU3 manages PCM17 ~ PCM20; CPU4 manages PCM21 ~ PCM24.
Start Time Slot
Integer type 0 ~ 31
Unit None
Default value 0
Description Link start time slot of accessing PCM
Access Rate
Integer type 0 ~ 31
Unit None
Default value 0
BRCH Parameters
Description Access rate
N391
Integer type 5 ~ 30
Unit None
Default value 6
Polling timer for all PVC status. Each T391 local end sends one STATUS
ENQUIRY message to the opposite end. STATUS ENQUIRY only performs
Description
Link Integrity Verification. One total status enquiry is performed every N391
period.
N392
Integer type 3~8
Unit None
Default value 3
Error detection counter. If the latest N393 STATUS ENQUIRY error is more
than that of N392, report the equipment fault to the upper level. If there is
Description
N392 no error link integration verification, report the fault relief to the upper
level.
N393
Integer type 4 ~ 10
Unit None
Default value 4
State detection counter. If the latest N393 STATUS ENQUIRY error is more
than that of N392, report the equipment fault to the upper level. If there is
Description
N392 no error link integration verification, report the fault relief to the upper
level.
T391
Integer type 500 ~ 3000
Unit 10 ms
Default value 1000
Complete state detection polling counter. Each T391 local end sends one
Description
STATUS ENQUIRY message to the opposite end.
Purpose
Prerequisites
Procedures
2. Click NSVC and Create NSVC box should pop up as shown in Figure 9.1-232.
Input proper parameters by referring to the following table and click OK.
NSVC Parameters
User Label
Integer type Characters or number or combination of both: 1~40
Unit None
Default value None
Description Unique label given to function.
NSVC ID
Integer type 0 ~ 65535
Unit None
Default value None
Description NSVC ID
DLCI
Integer type 16 ~ 991
Unit None
Default value 100
The DLCI value should be consistent with the SGSN. It is a planned value. The
Description
DLCI value cannot be the same at the same BRCH.
BRCH link
NSVC Parameters
Integer type Depending on actual configuration
Unit None
Default value Depending on actual configuration
It is a selection list and its data come from the BRCH. 5 pieces of NSVC
Description
maximally can be configured at one BRCH.
BE
Integer type 100 ~ 200
Unit bit
Default value 100
Excessive size of the burst packet. In the Tc period, the max excessive size of
Description
the burst packet user.
BC
Integer type 640 ~ 30720
Unit KB
Default value 640
Committed burst packet size, usually set as 640KB× Number of Time Slot. In
Description
the Tc period, the max committed burst packet size of one user.
TC(Network testing time)
Integer type 1000 ~ 1500
Unit 10 ms
Default value 1000
Description Network testing time
Information
Purpose
Prerequisites
Note:
Procedures
2. Click NSE and Create NSE box should pop up as shown in Figure 9.2-234.
Input proper parameters by referring Table 9.2-16 and click OK.
NSE Parameters
NSE ID
Integer type 0 ~ 65535
Unit None
Default value 0
Description To identify NSE.
Subnet type
Integer type Frame trunk, IP
Unit None
Default value Frame trunk
To identify subnet type. As per the protocol48.018, there are two types in
Description subnet: frame trunk and IP.
For IP GB interface, select IP, and Configuration Mode is valid.
Configuration mode
Integer type Dynamic configuration, static configuration
Unit None
Default value Static configuration
It indicates the acquisition mode of the opposite end node. The static
configuration is to configure the node of SGSN on BSC. The dynamic
Description configuration is to acquire the SGSN node via the signaling flow. When
selecting Dynamic Configuration, the parameters Pre-config SGSN IP and Pre-
config SGSN UDP are valid.
Pre-config SGSN IP
Integer type Valid IP address
NSE Parameters
NSE ID
Integer type 0 ~ 65535
Unit None
Default value 0
Description To identify NSE.
Unit None
Default value 0.0.0.0
When Dynamic Configuration is used, the opposite end node ((IP+UDPPORT)
is acquired from the opposite end via the configuration flow. One of the
Description
opposite ends should be known to facilitate signaling exchange. Pre-config
SGSN IP address is the one of the opposite end in the configuration flow.
Pre-config SGSN UDP port
Integer type 0 ~ 65535
Unit None
Default value 0
When Dynamic Configuration is used, the opposite end node (IP+UDPPORT)
is acquired from the opposite end via the configuration flow. One of the
Description opposite ends should be known to facilitate signaling exchange. Pre-config
SGSN UDP port address is the one of the opposite end (SGSN) in the
configuration flow.
Purpose
Prerequisites
2. If the user needs to create the opposite end (IPGB), it is unnecessary to create the
IP address of IPGB board and the RPU loop address in advance.
Procedures
2. Click IPGB Port and a window pops up as shown in Figure 9.2-236, add the
two IP ports of local and opposite ends. The IP address is the address set by
RPU. UDP port No. is consistent with SGSN. Input the proper port type by
referring to the following table.
3. Add IP configuration: BSC global resource →IP Information, input RPU address
in IPGB of the virtual IP address.
Note:
Due to version changes, the followings may be different from the actual condition. For
any question, please contact ZTE.
Logical
Physical board
board Version type Version file name Remarks
type
type
MP CPU iBSC_MPX86_2_MP_P4_V6.20.010A_Z.BIN OMP version
MPX86
FPGA MPX86_04_040704_FPGA107.RBF file
RPU version
MPX86 RPU CPU iBSC_MPX86_2_RPU_P4_ V6.20.010A _Z.BIN
file
MP CPU iBSC_MPX86_2_MP_P4_ V6.20.010A _Z.BIN SMP version
MPX86
FPGA MPX86_04_040704_FPGA107.RBF file
iBSC_UIM_2_UIM_8260_ V6.20.010A _Z.BIN
UIM_2 UIM CPU UIMC
iBSC_UIM_2_UIM_755_ V6.20.010A _Z.BIN
version file
UIM
CPU iBSC_UIM_2_UIM_8260_ V6.20.010A _Z.BIN GUIMU
GUIM
version file
— FPGA GIUM_03_060803_FPGA_108.bin
CHUB
CHUB CHUB CPU iBSC_CHUB_CHUB_8245_ V6.20.010A _Z.BIN
version file
ICM version
ICM ICM CPU IBSC_ICM_ICM_852_V6.20.010A_Z.BIN
file
With 852
DTB DTB CPU iBSC_DTB_DTB_852_V6.20.010A_Z.BIN
subcard, DTB
iBSC_GLIQV_GLI_CPU0_XSCALE_ V6.20.010A
CPU Process-in
_Z.BIN
cell
MICROCODE iBSC_GLIQV_GLI_INGRESS_ V6.20.010A.UOF
GLIQV GLI
iBSC_GLIQV_GLI_CPU1_XSCALE_ V6.20.010A
CPU Process-out
_Z.BIN
cell
MICROCODE iBSC_GLIQV_GLI_EGRESS_ V6.20.010A.UOF
Logical
Physical board
board Version type Version file name Remarks
type
type
FPGA GLIQV_00_040201_FPGA.BIN
CPU IBSC_MNIC_2_IPI_23XX_V6.20.010A_Z.BIN EIPI version
EUIP
MICROCODE UC_IBSC_MNIC_2_IPI_V6.20.010A.UOF file
CPU IBSC_MNIC_2_IPBB_23XX_V6.20.010A_Z.BIN
EIPI/BIPI/GIPI IPBB
MICROCODE UC_IBSC_MNIC_2_IPBB_V6.20.010A.UOF BIPI/GIPI
CPU IBSC_MNIC_2_IPGB_23XX_V6.20.010A_Z.BIN version file
IPGB
MICROCODE UC_IBSC_MNIC_2_IPGB_V6.20.010A.UOF
iBSC_PSN_PSN_860_ V6.20.010A _Z.BIN
PSN PSN CPU PSN version
iBSC_PSN_PSN_852_ V6.20.010A _Z.BIN
file
CPU iBSC_SDTB_SDTB_860_ V6.20.010A _Z.BIN SDTB
SDTB_00_040301_FPGA_104.RBF version file,
select the
correspondin
SDTB SDTB
FPGA g FPGA file
SDTB_01_040302_FPGA_105.RBF
upon actual
condition of
PCB board
SPB CPU iBSC_SPB_SPB_85XX_ V6.20.010A _Z.BIN
SPB LAPD CPU iBSC_SPB_LAPD_85XX_ V6.20.010A _Z.BIN
GIPB CPU iBSC_SDTB_SDTB_860_ V6.20.010A _Z.BIN GIPB
BIPB CPU iBSC_VTCD_BIPB_8260_ V6.20.010A _Z.BIN
BIPB DSP iBSC_VTCD_DSPC6414_BIPB_ V6.20.010A.BIN
DRTB CPU iBSC_VTCD_DRTB_8260_ V6.20.010A _Z.BIN
VTCD DRTB DSP iBSC_VTCD_DSPC6414_AMREN_ V6.20.010A.BIN
VTCD
UPPB CPU iBSC_VTCD_UPPB_8260_ V6.20.010A _Z.BIN
version file
UPPB DSP iBSC_VTCD_DSPC6414_UPPB_ V6.20.010A.BIN
The major procedures for SDR software loading include: BTS software packet
creation, software packet download, software packet activation. By way of creating
BTS software packet, the system copies the software from local server to ZXG10
NetNumen-G server, and modifies the background database; by way of downloading
version packet, the system uploads the software from ZXG10 NetNumen-G server via
FTP to the SDR under corresponding iBSC; by way of activating version packet, the
system sets the standby inactivated version packet of corresponding SDR as current
running version packet.
Start
Select software
version
Import software
into database
End
Figure 11.1-237 Software Load Flow
Select the software version according to the actual demands. The version
information should include software ID and version number.
The procedure is to create, delete or modify the version record of the general
software. After the general software is set, it can be used to load the same kind
of software in batch.
Notice OMP to load the general software to all the boards that run the software.
After the version upgrade, if the new version cannot start up or there are some
severe faults due to some reason, the system may break down. Therefore, the
original version should be saved before the version upgrade. If the above case
occurs, resume the normal running status with the original version.
Notice OMP to load a pre-set specific software version to a specific board and
then run the software. Because the specific software version has priority over
the general software version, if the board pre-loaded with a general software
version and then a specific software version, the specific software version will
run on the board.
Send a query command to a foreground board, the board will reply ZXG10
NetNumen-G server with its running version information which is then
forwarded to the client and displayed at the client.
[Purpose]
[Prerequisites]
[Procedures]
Click the button and select the version file from the popup box as
shown in Figure 11.3-241 below. Click Open to load the content into Figure 11.3-
240, as shown in Figure 11.3-242.
[Purpose]
[Prerequisites]
[Procedures]
Click the button and select the storage path to version files from the popup
box as shown in Figure 11.3-245 below. Click Open to load content into Figure 11.3-
244, as shown in Figure 11.3-246.
2. The users may check the files or click Select all or Select none, then click the
button Execute to complete creation. The Result column will show Operation
Successful, as shown in Figure 11.3-247 below.
3. Exit the dialog box to complete batch creation, as shown in Figure 11.3-248
below.
[Purpose]
[Prerequisites]
[Procedures]
1. Select a file that is to be set as the general version, right-click it to select Create
General Version File, as shown in Figure 11.3-249 below.
2. Click Create General Version File and a box pops up indicating that the general
version has been created successfully, as shown in Figure 11.3-250 below.
The users may find this version in the BSC general software tab, as shown in
Figure 11.3-251 below.
[Purpose]
[Prerequisites]
[Procedures]
1. Select a file that is to be set as the specific version, right-click it to select Create
Specific Version File, as shown in Figure 11.3-252 below.
2. Click Create Specific Version File and a box pops up as shown in Figure 11.3-
253 below.
3. Input Rack NO., Shelf No., Slot No. and CPU NO., and then click OK. A
message box will pop up, as shown in Figure 11.3-254 below.
4. Click OK and a box pops up indicating that the specific version has been created
successfully, as shown in Figure 11.3-255 below.
The users may find this version in the BSC specific software tab, as shown in
Figure 11.3-256 below.
[Purpose]
[Prerequisites]
2. Related MPX FPGA and BIN files have been created to OMC.
[Procedures]
1. Select both MPX FPGA and BIN files created in OMC and right-click to select
Create ompcfg.ini, as show in Figure 11.3-257 below.
2. Click Create ompcfg.ini and a box pops up as shown in Figure 11.3-258. Select
OMP or OMP+CMP+SMP as the MP type from the down-drop list and click
OK.
[Purpose]
[Prerequisites]
[Procedures]
Notes:
1. If the version to be deleted is not created as a general version or specific version, it
can be directly deleted from OMC in the BSC store software sub-view.
2. If the version to be deleted is created as the general version or specific version, it
should firstly be deleted from OMC in the BSC general software or BSC specific
software sub-view, and then deleted in the BSC store software sub-view.
1. In the BSC specific software sub-view, highlight and right-click the proper
version file to select Delete from OMC, as shown in Figure 11.3-260 below.
2. Click Delete from OMC and a box pops up as shown in Figure 11.3-261 below.
This version does not exist in the sub-view any more, as shown in Figure 11.3-
262 below.
3. In the BSC store software sub-view of BSC software management1 tab, select
the proper version and right-click it to choose Delete from OMC, as shown in
Figure 11.3-263 below.
4. Click Delete from OMC and a box pops up as shown in Figure 11.3-264 below.
This version does not exist in the sub-view any more, as shown in Figure 11.3-
266 below.
[Purpose]
[Prerequisites]
[Procedures]
2. Click Add version file to NE and a box pops up as shown in Figure 11.3-268
below.
[Purpose]
[Prerequisites]
2. The general version file has been added to NE, but not activated yet.
[Procedures]
1. In the BSC general software sub-view, right-click the proper version file and
select Activate as shown in Figure 11.3-270 below.
2. Click Activate and a box pops up. Select Reset from the drop-down list
depending on actual configuration as shown in Figure 11.3-271 below.
[Purpose]
[Prerequisites]
2. For the activation operation, the specific version file has been created and added
to NE, but not activated yet.
3. For the deactivation operation, the specific version file has been created and
added to NE and activated.
[Procedures]
1. In the BSC specific software sub-view, right-click the proper specific version and
select Activate as shown in Figure 11.3-274 below.
2. Click Activate and a box pops up as shown in Figure 11.3-275. Select DSP
Physical No. and Reset from the drop-down list depending on actual
configuration, and then click OK.
3. After the operation, click OK, a box pops up as shown in Figure 11.3-276 below.
4. Click OK and a box pops up as shown in Figure 11.3-277 below. The operation is
performed successfully.
5. The users can deactivate an activated version file. Right-click it and select Cancel
activation in Figure 11.3-278 below.
6. Click Cancel activation and a box pops up to indicate the result as shown in
Figure 11.3-279.
[Purpose]
[Prerequisites]
[Procedures]
Notes:
1. If the version has not been created as the general version or specific version, it can
1. Create ompcfg.ini.
2. In the BSC store software sub-view, right-click the proper version file and select
Delete version file from NE, as shown in Figure 11.3-280 below.
3. Click Delete version file from NE and a box pops up as shown in Figure 11.3-
281 below.
[Purpose]
[Prerequisites]
[Procedures]
1. In the BSC general software sub-view, right-click the proper general version file
and select Upgrade, as shown in Figure 11.3-283 below.
3. Select the proper items and click OK. A box pops up as shown in Figure 11.3-285
below.
4. Click OK to reset. A box pops up indicating the operation has been performed
successfully as shown in Figure 11.3-286.
[Purpose]
[Prerequisites]
[Procedures]
[Purpose]
[Prerequisites]
[Procedures]
[Purpose]
[Prerequisites]
[Procedures]
[Purpose]
[Prerequisites]
[Procedures]
2. Input the Rack No., Shelf No., Slot No. and CPU No. of the proper board and
click OK. Upon successful operation the NE version information is displayed as
shown in Figure 11.3-291 below.
[Purpose]
[Prerequisites]
[Procedures]
The operations on BTS software management are similar to those on BSC software
management. For detailed information, refer to 11.3 BSC Software Version
Management.
Software packet can be downloaded to main control panel CCH, which is managed and
distributed to each board by CC.
Download: Download the software packet from OMM server to BTS main control
panel.
Activate: OMM sends a command to BTS, requiring the BTS to restart and run the
standby software.
1. Expand the Configuration resource tree, right click SDR version packet management and a short-cut
menu pops up, click Create → BTS version packet as shown in Figure 11.7-296.
Figure 11.7-296
2. Select and open the software packet, a window pops up as shown in Figure 11.7-297.
Figure 11.7-297
3. Click OK, and the loading progress is shown in the system. After the loading, software version is
generated in the Configuration resource tree as shown in Figure 11.7-298.
Figure 11.7-298
4. Double click on the software version, the version properties and software operation toolbar will be
displayed on the right column, see Figure 11.7-299.
Figure 11.7-299
5. Click on the button (download), a window pops up, chick OK to enter the interface as shown in
Figure 11.7-300.
Figure 11.7-300
6. Select the BTS to be loaded or updated, right click and the short-cut menu pops up, click version
packet to download, a prompt message will be shown as Figure 11.7-301 indicating the downloading
command is sent successfully.
Figure 11.7-301
7. Close the version packet downloading interface, return to version packet property sub-view, click
version packet operation log interface, observe the downloading result of the version packet,
Successful value indicates the version packet is downloaded successfully as shown in Figure 11.7-
302.
Figure 11.7-302
8. Click the button (Activate) on the toolbar, a window pops up, click OK to enter the interface as
shown in Figure 11.7-303.
Figure 11.7-303
9. Select the BTS to be activated with its software version, right click and the short-cut menu pops up,
click to activate the version packet. A message indicating the version packet activation command is
sent successfully will be shown in the right column as Figure 11.7-304.
Figure 11.7-304
10. Close version packet activation window, return to operation log in version packet property sub-view,
where message indicating successful operation will be displayed as Figure 11.7-305.
Figure 11.7-305
Abstract
Query the file information of the software version packet already loaded into the
database.
Premise
Procedures:
Double click a software version packet in the resource management tree, enter version
packet property view, and click the file information of the version packet.
Result:
The file information of the version packet will be shown in the right columns as Figure
11.7-306.
Figure 11.7-306
Abstract
Premise
Procedures:
Figure 11.7-307
2. Click the button (Query information), a window pops up; click OK to enter the
interface as shown in Figure 11.7-308.
Figure 11.7-308
3. Select the BTS to be queried, and click OK. Only the BTS in normal ( )
connection status can be queried.
Result:
Figure 11.7-309
Figure 11.7-310
Abstract
Roll back to original version after updating the BTS software version.
Premise
Procedures:
1. Double click the SDR software version management node in the Configuration
Resource Tree to enter the interface as shown in Figure 11.7-311
Figure 11.7-311
Figure 11.7-312
3. Select the BTS to be queried, and click OK. The system jumps to the
software version information page at the foreground, where active and
standby versions are displayed as Figure 11.7-313.
Figure 11.7-313
4. Select the BTS whose version will be rolled back, right click and the short-
cut menu pops up. Click version packet switchover, a prompt window pops
up, click OK.
Version rollback will cause BTS restart, it will be completely out of service!
Result:
BTS restarts and loads standby version software. The previous version No. will be
displayed in the current active version information when querying according to this
subject.
Abstract
Premise
Procedures:
1. Double click the SDR software version management node in the Configuration
Resource Tree to enter the interface as shown in Figure 11.7-314.
Figure 11.7-314
2. Click the button (Query information), a window pops up, click OK to enter the
interface as shown in Figure 11.7-315.
Figure 11.7-315
3. Select the BTS to be queried, and click OK. The system jumps to the software
version information page at the foreground, where active and standby versions are
displayed as Figure 11.7-316.
Figure 11.7-316
4. Select the BTS whose standby version will be activated, right click and the short-
cut menu pops up. Click standby version packet activation, a prompt window pops
up, click OK.
Standby Version activation will cause BTS restart, it will be completely out of service!
Result
BTS restarts and loads standby version software. The previous standby version No.
will be displayed in the current active version information when querying according
to this subject.
Abstract
Premise
Procedures:
1. Double click the SDR software version management node in the Configuration
Resource Tree to enter the interface as shown in Figure 11.7-317.
Figure 11.7-317
2. Click the button (Query information), a window pops up, click OK to enter the
interface as shown in Figure 11.7-318.
Figure 11.7-318
3. Select the BTS to be queried, and click OK. The system jumps to the software
version information page at the foreground, where active and standby versions are
displayed as Figure 11.7-319.
Figure 11.7-319
4. Select the BTS whose standby version will be deleted, right click and the short-cut
menu pops up. Click to delete standby version packet, a prompt window pops up,
click OK.
Result:
Standby version packet is deleted successfully, standby version information will not
be displayed in the BTS version information as Figure 11.7-320
Figure 11.7-320
Abstract
Query the operation log of a version packet, including sending download command,
download result, activating result, etc.
Premise:
Procedures:
1. Double click a software version packet in the resource management tree to enter
the sub-view of version packet properties.
2. Click the button (Query) on the toolbar to enter the interface as shown in
Figure 11.7-321.
Figure 11.7-321
Result:
Query result is displayed in the operation log of version packet as shown in Figure
11.7-322.
Figure 11.7-322
iBSC TC MSC
A interface
In this case, iBSC has only one MSC as its adjacent office. The iBSC A-interface data
must be configured as follows:
The signaling point of local office should be configured, as shown in the figure below.
SSN is used to manage the users based on SCCP protocol. 0 and 1 are for SCCP
management, and 254 for BSSAP management.
As shown in the figure below, Office type should be set as MSCSERVER and AM set
as AM SURE. Other parameters including SSF, SPC type, DPC must be consistent
with MSC.
The No.7 link set consists of several signaling links. Usually one link set is enough
for an adjacent office.
Designate PCM, TS, SMP module, and Link code SLC in the figure below.
The No.7 route specifies the link set to transmit signaling. At most two link sets are
available. Office ID is the office of the link set. As shown in the figure below, because
there is only one MSC as the adjacent office, Office ID should be set as 1. Linkset is
the configured link set under the adjacent office. Because there is only one link set, the
users only need to select 1 in the Linkset 1 down-drop list.
The No.7 office route specifies the route to transmit signaling to an adjacent office. At
most four routes are available. In the figure below, only Route 1 is available.
10. FLEXA is a new function in iBSC 6.20, which indicates one BSC can be
connected with multiple MSC, each of which consists of a MSC POOL. This
function can be enabled/disabled in global resource interface as the following
figure:
After this function is enabled, information of the operator and MSC office should be set.
Information to be added into MSC office direction information include office direction,
MSC ID, MSC network route ID and MSC load sharing ratio (the information can be
queried at CN side, which is configured the same as CN side), as well as multiple
signaling point office direction (the same configuration as that at A interface), poll
times (self-defined).
Set relevant data in the operator’s information page. MSC NRI length, MSC NULL-NRI ID and MSC
CN ID should be queried on CN side, which should be configured with the same value, otherwise the
mobile cannot access to the network.
Note: Even if FLEX A is not supported on iBSC side, the MSC CN ID mentioned
above should be configured with the same value as CN side, otherwise the mobile
cannot access to the network. Other parameters are not required to be configured, the
default values should be kept.
3G CN introduces MSCServer and MGW. After the introduction of 3GPP R4, in the
principles of separating control and bearing, MSC is composed of MSC Server and
MGW. MSC Server controls services and calls, while MGW controls bearing. The 3G
CN networking is as follows:
IMS Domain
SCP HLR/
SDP AUC
MGCF
SMSC
PSTN Internet
IM-
MGW
NO.7 Signalling Network
GMSCS/
SSP
GGSN
GMGW
Packet Switch
Network
Circuit Switch MSCS/VLR/
Network SSP
MGW SGSN
BSC RNC
The following part describes three networking modes between iBSC and 3G CN.
iBSC is associated with MGW only. CN provides the signaling points for MGW and
MSCServer. The networking topology is as follows:
MSC
iBSC MGW Server
A interface SS7
Because MSCServer processes with calls and services, iBSC signaling should be sent
to MSCServer for processing. In this networking mode, MGW and MSCServer are
connected via SS7, and MGW serves as STP (signaling transfer point) to forward iBSC
signaling to MSCServer.
iBSC has 2 adjacent offices, namely, MGW and MSCServer. It is associated with
MGW and quasi-associated with MSCServer.
iBSC is associated with MGW. The signaling link is configured under MGW.
There is no service link between iBSC and MGW, thus SSF254 (BSSAP) is not
required to be configured under MGW.
Two office routes should be configured, one of which to MGW, and the other to
MSCServer.
2. Configure Local No.7 SSN 0, 1 and 254. SSN is used to manage the users based
on SCCP protocol. 0 and 1 are for SCCP management, and 254 for BSSAP
management.
8. Configure MGW signaling link set, which consists of several signaling links.
Usually one link set is enough for the connection to an adjacent office.
9. Configure the MGW No.7 link. Designate PCM, TS, CMP module, and Link
code SLC.
10. Configure the No.7 route. The No.7 route specifies the link set to transmit
signaling. At most two link sets are available. Adjacent Office ID refers to the
office of the link set. Because the link set is configured under MGW, the office ID
of MGW and the link set under MGW should be selected.
11. Configure the No.7 office route to MGW. Select the No.7 route configured in
Procedure 10.
12. Configure the No.7 office route to MSCServer. Select the No.7 route configured in
Procedure 10.
Signaling Sub-System
No.7 PCM
Signaling Link
Signaling Route
iBSC is associated with MGW only. CN provides the signaling point for MGW. The
networking topology is as follows:
MSC
iBSC MGW
Server
A interface MC interface
In the form of IP (Sigtran), the signaling goes through MGW and MSCServer via MC
interface. The transmission between MGW and MSCServer is not controlled by iBSC.
Therefore, MGW and MSCServer can be viewed as a whole. iBSC data configuration
is the same as 2G MSC interconnection.
iBSC is associated with both MGW and MSCServer. CN provides the signaling point
for MSCServer. The networking topology is as follows:
er elay
Voic MGW
iBSC
A in te MSC
r face Server
iBSC has physical connection with both MGW and MSCServer. Because 3G CN
separates voice processing and bearing, the signaling link is connected to MSCServer
while the voice relay is connected to MGW. And because no signaling is transferred to
MGW, MGW and MSCServer can be viewed as a whole too. iBSC data configuration
is the same as 2G MSC interconnection.
The only difference is that although the voice trunk circuit to MSCServer is configured
as No.7 PCM, only the signaling is transferred. In actual operation, the users may
consult the CN and set the NO.7 PCM number of MGW trunk circuit from 0 (or 1),
and set the NO.7 PCM number of MSCServer trunk circuit from large numbers such as
512.
1. Installation and debugging of iBSC has been finished. All boards can run
normally.
5. Related data for A-interface interconnection has been obtained from MSC.
CIC
signaling point. The 14-digit signaling point code of BSC is in the decimal 3-8-
3 format. However, different vendors may have different division methods,
such as the 6-8 format and the 7-7 format. The signaling point data given by
MSC are usually the data after the division. For example, the MSC may give a
signaling point 18-50. It is not the decimal number 1850. If MSC adopts the 7-
7 format, the signaling point is 1+38+2 (decimal, 3-8-3 format). If MSC adopts
the 6-8 format, the signaling point is 2+70+2 (decimal, 3-8-3 format. Pay
attention to its difference with BSCV2 decimal 4658 format). Therefore, the
users should first know how MSC divides the signaling point code to guarantee
consistent binary codes at both sides.
Algorithm:
The decimal 18 is the binary 10010, and 0010010 as a 7-digit binary number.
The decimal 50 is the binary 110010, and 0110010 as a 7-digit binary number.
Every signaling message at the A interface has a signaling point code and it can
be viewed by tracked signaling. The signaling point code is hexadecimal. If the
tracked signaling has the testing and maintenance messages on the uplink and
downlink signaling network, it indicates BSC and MSC have correct signaling
point configurations.
Usually SLC starts coding from 0 and the signaling TS are usually at TS16.
However, not all the vendors set TS16 as the default MSC signaling TS and the
users should pay attention to it.
4. Network Type
The SIO (service information octet) SSF contains the 2-bit NI (network
identification) of 00/01/10/11, respectively representing international network
(international active), international standby network, national network (national
active), and national standby network. The content of SIO SSF is national
active 1000 or national standby 1100.
For the MSC interconnection, the domestic network types are mostly NIS
(national standby, 14-digit). But the international network types are mostly NI
(national active). If MSC and BSC have different network type configurations,
the following signaling message will show repeatedly:
Query R_N7SSN STATUS bits and make sure all the STATUS bits are 0.
Configure the local office and adjacent office with the signaling subsystem
number 0, 1 and 254. The subsystem ID bit usually represents a signal
subsystem. The direction number of the local office is usually set as 0 and that
of the adjacent office is set according to the actual data configuration. Other
parameters are set by default.
[Purpose]
[Prerequisites]
[Procedures]
2. Click Local NO.7 SSN and then to enter the interface to create local
No.7 SSN as shown in Figure 12.5-324.
[Purpose]
[Prerequisites]
[Procedures]
[Purpose]
[Prerequisites]
BSC and the primary signaling node of local office have been created successfully.
[Procedures]
2. Click and a box pops up as shown in Figure 12.5-328 below. Input the
correct parameters and click OK to complete creation. Refer to Table
12.5-20 for related parameters.
[Purpose]
[Prerequisites]
BSC and the primary signaling nodes of local office and adjacent office have been
created successfully.
[Procedures]
2. Click Adjacent NO.7 SSN, and then and a box pops up as shown in
Figure 12.5-330 below. Input the correct parameters and click OK to
complete creation. Refer to Table 12.5-21 for related parameters.
[Purpose]
[Prerequisites]
BSC and the primary signaling nodes of local office and adjacent office have been
created successfully.
[Procedures]
2. Click and a box pops up as shown in Figure 12.5-332 below. Input the
correct parameters and click OK to complete creation. Refer to Table
12.5-22 for related parameters.
[Purpose]
Caution:
If the A interface to be configured is for broadband, it’s unnecessary to create No.7 link
set and hence this section can be ignored during the configuration.
[Prerequisites]
BSC and the primary signaling nodes of local office and adjacent office have been
created successfully.
[Procedures]
2. Click and a box pops up as shown in Figure 12.5-334 below. Input the
correct parameters and click OK to complete creation. Refer to Table
12.5-23 for related parameters.
[Purpose]
[Prerequisites]
BSC and the primary signaling nodes of local office and adjacent office have been
created successfully.
[Procedures]
2. Click and a box pops up as shown in Figure 12.5-336 below. Input the
correct parameters and click OK to complete creation. Refer to Table
12.5-24 for related parameters.
[Purpose]
[Prerequisites]
BSC and the primary signaling nodes of local office have been created successfully.
[Procedures]
1. Click and a box pops up as shown in Figure 12.5-338 below. Input the
correct parameters and click OK to complete creation. Refer to Table
12.5-25 for related parameters.
[Purpose]
[Prerequisites]
BSC and the primary signaling nodes of local office have been created successfully.
[Procedures]
2. Click and a box pops up as shown in Figure 12.5-340 below. Input the
correct parameters and click OK to complete creation. Refer to Table
12.5-26 for related parameters.
Traffic load of speech TCH at A interface is smaller than 0.7 Erlang/CIC Timeslot;
The incoming signaling load of CCSS7 link is smaller than 0.2 Erlang/Link;
And the outgoing signaling load of CCSS7 link is smaller than 0.2 Erlang/Link.
If the E1 indicator flashes quickly, it indicates the DTB can receive MSC
signals.
If it flashes slowly, check if the SS7 data configuration is consistent with that
of MSC.
Access the main interface of the client and select Faulty Management →
Management View.
1. Check if there is PCM alarm in DTB and SPB, which are connected to
the A interface.
If there are, it means signaling at the two ends has problems and needs further
check.
Access the signalling tracking interface of the client, open the configuration box, and
select A interface and the SS7 link to be tracked.
Click View → Dynamic Data Management and select the corresponding BSC
dynamic data management to configure PCM, observe PCM/TS status and make
operation and maintenance.
For A-interface test, the call test should be made on each link and every CIC TS. For
detailed information, please refer to ZXG10 iBSC (V6.20) Test Guide and ZXG10 iBSC
(V6.20) Commissioning Test Record.
Commissioning
After iBSC commissioning, basic function/performance tests should be conducted on
iBSC and iOMCR. The tests include iBSC hardware test, OMCR function test,
software version test, call service test, handover test and new function test. For detailed
information, the users may refer to ZXG10 iBSC (V6.20) Test Guide and ZXG10 iBSC
(V6.20) Commissioning Test Record.
Appendix A Abbreviations
Abbreviations Full Name
A
AC Address Control
AGCH Access Grant Channel
AUC Authentication Center
B
BCH Broadcast Channel
BCCH Broadcast Control Channel
iBSC Base Station Controller
BSC Base Station Controller
BSIC Base Station Identity Code
BSS Base Station Subsystem
BSSGP BSS GPRS Protocol
BTS Base Transceiver Station
BVC BSSGP Virtual Connection
BVCI BSSGP Virtual Connection Identifier
C
CBCH Cell Broadcast Channel
CCCH Common Control Channel
CEPT Conference of European Posts and Telecommunications
CGF Charging Gateway Function
C/I Carrier-To-Interference Ratio
CM Connection Management
CS-i Coding Scheme (GPRS)
D
DTB Digital Trunk Board
E
ECSD Enhanced Circuit Switched Data
EDGE Enhanced Data Rates For GSM Evolution
EGPRS Enhanced GPRS
EIR Equipment Identity Register
ETSI European Telecommunications Standards Institute
F
FACCH Fast Associated Control Channel
FCCH Frequency Correction Channel
FDMA Frequency Division Multiple Access
G