GSM-BSS_III_03_200908

IBSC Commissioning and Debugging

GSM User Services Department

Chief Engineer Team/Training Team
Learning Objectives

• Through this course, you could:

– Master the commissioning and debugging
process of BSS system
– Get familiar with iBSC stand-alone debugging
– Master the butt joint of A/Gb
– Master the debugging of CS/PS service
Course Content

• Commissioning and debugging process

of BSS system
• iBSC standalone debugging
• A port butt joint and CS service debugging
• Gb butt joint and PS service debugging
 秘密▲
Commissioning and Debugging Process of BSS
System
 （1）Preparation for commissioning and debugging
 （2）Inspection of equipments before powering up
 （3）Inspection of equipments after powering up
 （4）Installation and debugging of ISMG single
plate server (SBCX)
 （5）ISMG client-side installation
 （6）OMP installation and debugging
 （7）Basic data configuration
 (8 ) Software loading
 （9）A port butt joint and service test
 (10) Gb port butt joint and service test
 （11）Commissioning and test
Course Content

• Commissioning and debugging process of

BSS system
• iBSC stand-alone debugging
• A port butt joint and CS service debugging
• Gb port butt joint and PS service debugging
 秘密▲

Basic Data Configuration

 Configuration Steps:
 Create GREAN sub-network
 Create configuration set
 Create BSC managerial network element
 Apply for mutual exclusion privilege
 Create BSC overall resource
 Create BSC rack and shelf single plate
 秘密▲

Basic Data Configuration

 Create GREAN sub-network

 秘密▲

Basic Data Configuration

 Create BSC managerial network element

 秘密▲

Basic Data Configuration

 Apply for mutual exclusion privilege

 秘密▲

Basic Data Configuration

 Create BSC overall resource 1

 秘密▲

Basic Data Configuration

 Create BSC overall resource 2
 秘密▲

Basic Data Configuration

 Create BSC overall resource 3

 秘密▲

Basic Data Configuration

 Create BSC rack

 秘密▲

Basic Data Configuration

 Create BSC shelf

 秘密▲

Basic Data Configuration

 Principle for shelf Configuration

 Single-shelf rack: resource shelf may be configured at any
layer
 Single-shelf rack: resource shelf may be configured at any
layer
resource shelf is generally configured at the 1st and 3rd
layer
Packet switching shelf is generally configured at the 4th
layer
 Double-shelf rack: control shelf may only be configured at the
2nd layer of No. 1 machine cabinet
 Resource shelf is configured at the 1st layer and 3rd layer of No.
1 machine cabinet and any layer of No. 2 machine cabinet
 Packet switching shelf is generally configured at the 4th layer of
No. 1 machine cabinet
 秘密▲

Basic Data Configuration

 Create BSC single plate

 秘密▲

Basic Data Configuration

 Configuration sequence of single plate:

 Control shelf ->OMP single plate of control shelf -
>UIMC single plate of control shelf ->other single
plate of control frame
 Resource shelf ->UIMU single plate of resource
shelf ->other single plate of resource shelf
 Switching shelf -> UIMC, GLI, PSN without
requirement on sequence
 秘密▲

OMP Debugging

 Purpose of debugging:
 The purpose of OMP debugging is to make OMP
load the correct software version and configuration
data with the correct start-up parameters, and make
OMP build the connection with ISMG server.
 After OMP debugging, specific inspection must be
carried out, so as to guarantee the accuracy of
parameters, versions and data, and also build the
connection with ISMG.
 Brief debugging steps:
 OMP version entering database and establishing
ompcfg.ini file.
 Configuring OMP with serial port
 Checking the state of single plate, and confirming
whether OMP debugging is successful or not.
 秘密▲

OMP Debugging

 OMP version entering database

 秘密▲

OMP Debugging

 Create ompcfg.ini File

 On the page of “BSC version entering the
database”, press on Ctrl key, at the same time,
select the records of CPU and FPGA version of
OMP that have already entered the database, and
select “Create ompcfg.ini file” through right-click.
 秘密▲

OMP Debugging

 Configuring OMP with serial port

 Connecting the debugging cables to:

 The debugging port connecting OMP (generally the

DEBUG2-232 port under RMPB plate)

 The serial port of debugged computer

 Debugging the software:

 Debugging the hyper terminal program brought by

windows operating system of the PC

 秘密▲

OMP Debugging

 Configuring OMP with serial port

Carrying out the following 1-5 steps one by one after entering “1- Config MP net
parameters(only for Omp and Cmp)”

Config selection:

1 - Set Omp(or Cmp)‘s Omc Ip and Mac! // Set the IP address and MAC address of
OMP, etc

2 - Set Omp Boot Paras! // Set the boot parameters of OMP

3 - Set OMP Boot Type ! // Set the start mode of OMP, making it start
from OMC

4- Set Net_Element Bureau No.! // Set iBSC’s Bureau No.

5 - Quit config, return to bootmenu! // Enter 0 after quit, and re-boot OMP
 秘密▲

OMP Debugging

 Check the state of single plate

 After the normal start-up of OMP, the “RUN” light

corresponding on MPX86 single plate shall slow flash;

 Under the prompt of super terminal -> input

“SCSShowMcmInfo”, and then click “enter”, the following

content shall appear:

SCSMCProc: End all 69 base process power on sucess.

SCSMCProc: Current Proc InnerState is MASTER

SCSMCProc: Current MCM State is WORK

value = 1 = 0x1

OMP debugging reference file

 秘密▲

OMP Debugging

 Three common-use commands:

 SCSShowMcmInfo

 SCSShowVerInfo

 ifShow

 Processing of three common faults:

 There’s no prompt after entering super terminal －－3gzte

 ftp connection always times out when OMP downloads the

version from background －－－

 Inspection of OMP boot parameter and background version

file
 After the successful loading of version, OMP still re-boot

again and again －－foreground configuration data

 Whether or not is compatible with the version
 秘密▲

Debugging of Peripheral Single Plate

 Brief debugging steps:

 Version entering the database
 Create general version
 Add the version to network element
 Activate the version
 Check the current version
 秘密▲

Debugging of Peripheral Single Plate

 Version entering the database－－ transmit the

version file from ISMG client-side to under the path
of “ISMG server/tmp/ftp/version/bscX”
 Single version entering the database and bulk
versions entering the database
 秘密▲

Debugging of Peripheral Single Plate

 Version entering the database

 秘密▲

Debugging of Peripheral Single Plate

 Create general version －－indicates what kind of

version some type of single plate should load upon
the startup, and the preference of such version is
lower than that of special version.
 秘密▲

Debugging of Peripheral Single Plate

 Add the version to network element －－for

transmitting the version file on ISMG server to the
hard disk of OMP single plate
 秘密▲

Debugging of Peripheral Single Plate

 Version activation －－conducting version switching,

and if reset is selected, not only carries out
database operation, but also switches the currently-
operating version of single plate; otherwise, only the
version information of database changes, and single
plate still operates under the former version.
 秘密▲

Debugging of Peripheral Single Plate

 Check the information of currently-operating version

of single plate
 秘密▲

Debugging of Peripheral Single Plate

 Two common faults:

 The version fails to enter the database, ftp fault
prompted－－check the content of hosts file; the
version fails to be added to network element, f tp fault
promoted －－check the ftp configuration of deploy-
gsmomcr01.properties file in ISMG server (IP is eth6
Intranet IP, port 20021)
Course Content

• Commissioning and debugging process of

BSS system
• iBSC stand-alone debugging
• A port butt joint and CS service
debugging
• Gb port butt joint and PS service debugging
The Role of A port Butt Joint during the 秘密▲

Commissioning & Debugging and Maintenance

Process of CS Service
 A port is interface between the controller of base station and
the core network MSC or MGW; it’s a standard interface,
supporting the butt joint of equipments from different
manufacturers.
 A port butt joint is among the preconditions for the
commissioning of CS service. Upon the commissioning, only
three items are guaranteed, i.e. A port and abis port are
correctly commissioned and debugged and the state of cell is
normal, may the system enter the terminal registration
networking and accordingly enter the service debugging stage.
 During the network maintenance stage, should the core
network change the A port data of some iBSC or A port cutover
of iBSC, or something wrong happens to CS service, etc, the
radio side maintainer should check or correct all butt joint
related data of A port. Therefore, mastering A port butt joint
skills is the basic technique for every radio engineer.
 秘密▲

A Port Butt Joint Process

 Inspection of butt joint condition

 Negotiation on butt joint data
 Configure iBSC overall resource data, iBSC physical
data and A port data
 Debug A port physical layer, MTP layer, SCCP layer
and BSSAP layer in order
 Service debugging
 秘密▲

Inspection of Butt Joint Condition

 iBSC installation and debugging are finished, and all

single plates operate normally
 Core network operates normally
 The preparation for transmission from iBSC to the
Core is done (E1 cable/optical fiber wiring finished)
 秘密▲

Negotiation on Butt Joint Data

 Determine the networking mode

 Straight-connected networking between MSC of

R99 and iBSC

 After iBSC and R4 version (including R4),

networking comprises three types:

 Straight-connection between iBSC and MGW, and
semi-straight-connection between iBSC and MSC; the
core network provides two signaling points
 iBSC only straightly connects with MGW, and the core
network provides MSC with a signaling point
 There’re physical connections between iBSC and MGW,
and IBSC and MSC; the core network provides MSC
with a signaling point
 秘密▲

Negotiation on Butt Joint Data

 Two methods for data configuration :

 Straight-connection between iBSC and MGW, and
semi-straight-connection between iBSC and MSC; the
core network provides two signaling points
 Under other three networking modes, data
configuration is the same
 秘密▲

Negotiation on Butt Joint Data

 The data configuration when the core network

provides
Serial MSC
Configuration items with one signalingNotes
point
No.
Local signaling
1 point Refers to the signaling point code adopted by the iBSC
Sub-system of
local signaling — 0/1 is used for SCCP management, and 254 refers to
2 0/1/254 BSSAP.
The type of adjacent office is MSC Server, and the
3 adjacent office (1) connection mode is straight-connection
Sub-system of
local signaling — 0/1 is used for SCCP management, and 254 refers to
0/1/254 BSSAP.
4
5 No. 7 PCM PCM that No. 7 signaling locates
Signaling link set
6 (1 set) One signaling link set includes several signaling links
Indicate the N7PCM and time slot the link locates, the
CMP module number and signaling link code (SLC)
 秘密▲

Negotiation on Butt Joint Data

 Data configuration when the core network provides

MSCConfiguration
Serial
with twoitems
signaling points Notes
No.
Refers to the signaling point code adopted by the
1 Local signaling point iBSC
Sub-system of local 0/1 is used for SCCP management, and 254 refers to
2 signaling BSSAP.
MGW, straight-connection
3 Adjacent office (2) MSC Server, semi-straight-connection
Sub-system of MGW：0/1 (SCCP management)
adjacent
4 signaling MSC Server：0/1(SCCPmanagement), 254(BSSAP)
5 No. 7 PCM Configured under MSC Server
6 Signaling link set (1 set) Configured under MGW
7 No. 7 signaling link Configured under MGW
Since signaling link set is configured under MGW,
should select MGW’s office direction number and
8 Signaling route (1) signaling link set under MGW
 秘密▲

Negotiation on Butt Joint Data

 Verification of butt joint data:

 Mobile Country Code (MCC)

 Mobile Network Code (MNC)

 MGW’s signaling point: 14 bit signaling point code (decimal

format) or 24 bit signaling point code (decimal format)
 MSCServer’s signaling point: 14 bit signaling point code
(decimal format) or 24 bit signaling point code (decimal
format)
 iBSC’s signaling point: 14 bit signaling point code (decimal
format) or 24 bit signaling point code (decimal format)
 Sub-service field of SSF(SubServiceField)

 Subsystem number of SSN (Sub System Number) SCCP

 A port PCM number (determine CIC code: CIC=PCM

code×32+No. of time slot)
 Type of signaling link set: 64K or 2M signaling
 秘密▲

Negotiation on Butt Joint Data

 Verification of butt joint data:

 Link error correction method: fundamental error
correction/prevention and circling retransmitting correction
 No. 7 signaling link code (SLC) (64K signaling link)

 No. of PCM that No. 7 signaling link locates (64K signaling

link)
 Time slot that No. 7 signaling link locates (64K signaling
link)
 E1 adopted by No. 7 signaling (2M HSL high speed
signaling link)
 E1 Port’s frame format (dual-frame or multi-frame,
corresponding to PCM verification mode no CRC or CRC)
 Resistance of E1 circuit (75 ohm/120 ohm)

 Optical fiber multiplexing structure ITU AU-4/ITU AU-

3/SONET STS-3
 Optical fiber PCM arrangement mode ITUT G.707/Tributary

 APS protection mode (1+1/1:1)

 秘密▲

Negotiation on Butt Joint Data

 Signaling point code:

 Firstly, both parities are required to determine 14 bit code or 24 bit code is adopted .
For the coded-decimal notation providing for the other party, it is required to be
converted to 14 bit or 24 bit binary coding, which is then converted to such format as
3-8-3 (14 bit code) or 8-8-8 (24 bit code), and then followed by data configuration.
Conversion process is as shown as follows:
 The coded-decimal notation of 14 bit signaling point code is 367
 Firstly, converted 367 to binary coding 101101111, and if the number of bits is less than
14, add 0 at the fore, i.e. 00000101101111;
 Then, subdivide according to the mode of 3-8-3, acquire 000-00101101-111
 Convert 3 sections to coded-decimal notation separately, acquire the signaling point 0-
45-7 which should be configured on the final interface
 秘密▲

Negotiation on Butt Joint Data

 The arrangement mode of optical fiber PCM : ITUT G.707 and

Tributary
 One channelized 155M STM-1 supports 63 E1

 Optical fiber arrangement mode defines the arrangement

mode of 63 E1. During butt joint, it requires both parities to

adopt the same arrangement mode; if the arrangement
modes of both parities differs, the signaling link of some E1
is connected or under normal communication, however, the
signaling of other E1 fails to be connected or two-way
silence during the communication.
 When the arrangement modes differ, the E1 of both parties

may correspond as follows:

 1,4,7,10,13,16,19,23,26,29,32,35,38,41,45,48,51,54,57,60,

63。
 秘密▲

Negotiation on Butt Joint Data

 Optical fiber multiplexing structure ITU AU-4/ITU AU-3/SONET

STS-3
 Optical fiber multiplexing structure requires the accordant

setting by both parities, and ITU AU-4 is generally adopted.

 APS protection mode (1+1/1:1)
 If the setting by both parties differs, and under the

circumstance that the master optical fiber is normal, APS

protection mode will not influence the butt joint; however if
the master optical fiber fails, it will result in the failure of the
protection of optical fiber APS, and accordingly influence
the service; therefore, both parities should negotiate to
adopt the same APS protection mode with regard to butt
joint.
 秘密▲

A Port Data Configuration

 Tree node under iOMCRV6.10 version

 Under iOMCRV6.10 version, only has one local
signaling point and one node, other data is under
the foldout of right chart.
 秘密▲

Checking after Butt Joint

 Check the state of flashing light of DTB plate

 If E1 light flashes slowly, indicate MSC signal is receivable, which
only represent it’s connected with the physical layer.
 If E1 light fails to flash, it requires checking the transmission;
confirm which location has transmission interruption by adopting
self-loop hop by hop.
 Check the state of SPB plate:
 If the signaling is accessed directly through SPB plate, the
indicator of E1 where No. 7 signaling link locates flashes fast,
which means that the signaling MTP2 layer is normal.
 If the indicator of E1 where No. 7 signaling link locates flashes
slowly, it means that the physical layer is connected, and however
the link isn’t connected. For this situation, may adopt the self-loop
for E1 where No. 7 signaling locates, and decide whether the
iBSC internal data and connection are normal by observing
whether the indicator flashes fast. If it flashes fast after self-loop, it
requires checking whether the data configuration of No. 7
complies with MSC side.
 秘密▲

Checking after Butt Joint

Background alarm inspection:

 Check whether there’s PCM alarm on A port DTB
and SPB plate
// If required, firstly examine the
transmission fault
 Check the alarm of iBSC, if any of the following
situations exists: the signaling point is inaccessible,
No. 7 signaling L3 alarm appears
//If the signaling point is inaccessible, means
all links are in interrupted state; if there’s No. 7
signaling link L3 alarm, it requires eliminating the
fault of this link.
 秘密▲

Checking after Butt Joint

 Observation of dynamic data management:

 Enter [dynamic data management] of [view], select
the corresponding [BSC dynamic data management],
and carry out blocking/deblocking operation for all A
port PCM
 No. 7 signaling should be in service state, and A port
PCM should be in deblocking state.
 秘密▲

Checking after Butt Joint

 Testing of A port PCM blocking and deblocking:

 Enter [dynamic data management] of [view], select
the corresponding [BSC dynamic data management],
and carry out blocking/deblocking operation for all A
port PCM
 Meanwhile, track A port signaling, and confirm there’s
blocking/deblocking verification in the signaling; and
block/deblock the verification message.
 秘密▲

Service Test

 After A port signaling link is confirmed normal, it

requires conducting the basic service test:
 Updating of handset location
 Handset calling
 Handset being called
 A port PCM call test
 秘密▲

Service Test

 After A port signaling link is confirmed normal, it

requires conducting the basic service test:
 Updating of handset location
 Handset calling
 Handset being called
 A port PCM call test
Course Content

• Commissioning and Debugging Process of

BSS System
• iBSC Stand-alone Debugging
• A Port Butt Joint and CS Service Debugging
• Gb Port Butt Joint and PS Service
Debugging
 秘密▲

Gb Port Protocol Stack

Gb port is the interface between the controller of base station and SGSN.

The physical medium supports two types: E1 and IP.

 秘密▲

Network Service Entity Identity (NSEI)

 In the BSSGP layer of GPRS protocol stack, for the purpose of

facilitating the management,
 Each GPRS cell is assigned with one BSSGP virtual

connection BVC (NSEI＋BVCI)

 One BVC must be affiliated to one NSE, and NSE is the

network service equipment entity, which is uniformly

encoded and identified with NSEI
 Generally, one BSC is defined as one service entity, and for

the purpose of extensibility, in ZXG10 system, several

NSEs are allowed to hung under BSC
 Value range: 0~65535
 Notes: uniformly planned by SGSN side.
 秘密▲

BSSGP Virtual Connection Identity (BVCI)

 BSSGP virtual connection (BVC) provides an approach for

communication between different BSSGP entities
 The transmission of BSSGP PDU between the peer-to-peer
PTP (point-to-point), PTM (point-to-multipoints) and the
signaling entity is based on BVC.
 There’s one identity for each virtual connection, i.e. BVCI,
which may make the bottom-layer network service layer
effectively route the BSSGP PDU to the peer-to-peer entities.
Under one network service entity (NSE), each GPRS cell may
be solely identified by BVCI; one network service entity has
and only has one signaling BVC (BVCI=0); the virtual
connection of BVIC=1 is reserved for the purpose of PTM, and
BVCI of all GPRS cells is encoded starting from 2.
 Value range: 0~65535.

 Notes: suggest adopting STIEID+BTSID for planning.

 秘密▲

Bearer Channel (BRCH)

 Bearer channel is the physical channel of Gb port;

under the circumstance of adopting E1 for
transmission, it means that between iBSC and
SGSN, data communication is realized through
that/those time slot(s) of that E1.
 Value range: N/A

 Notes: N/A
 秘密▲

Router Area Code (RAC)

 Similar as the method through which GSM system manages a

set of cells with the location area,
 GPRS further refines the management layers; divide one
location area into several routing areas, which are identified
with RAI (MCC＋MNC＋LAC＋RAC).
 When MS cell in attach state is reselected, if RAI of new and
old cells changes, initiates the “routing area update” flow. For
MS under STANDBY state, SGSN knows the information of its
routing area; under such circumstance, when grouped data or
circuit service data is transmitted in the network, will call MS in
the routing area. RAI can’t stride cross SGSN.
 Value range: 0~255
 Notes: suggest setting RAC with 0 for the whole network,
making RAC fail and only rely on the size of LA
 秘密▲

Negotiation on Butt Joint Data

 Network service entity identity (NSEI)

 Bearer channel (BRCH)
 Network service virtual connection identity (NSVCI)
 Data link control identity (DLCI)
 Router area code
 秘密▲

Briefed Configuration Flow

 Configure the Gb port plate and the processing plate of PS
service user interface
 Configure network service entity (NSE)
 Configure bearer channel (BRCH)
 Configure network service virtual connection (NSVC)
 Modify cell-supported GPRS/EDGE service and set RAC
 Gb port link state inspection
 PS service test
 秘密▲
Configure the Gb Port Plate and the Processing
Plate of PS service User Interface
 UPPB------1 CPU and 14 DSP, PCB plate is VTCD
 GIPB-------4 CPUs, 16 path E1 access capability,
and the physical plate is SPB
 秘密▲

Configure NSE
 秘密▲

Configure NSVC (continued)

 秘密▲

Configure NSVC
 秘密▲
Modify the Cell-supported GPRS/EDGE Service and
Set RAC
 秘密▲

Gb Port Link State Inspection

 At dynamic management interface, check the state

of SGSN and NSVC.
 At NSVC management interface, each NSVC should
be in service state without congestion
 秘密▲

Gb Port Link State Inspection

 Signaling tracking tool tracks Gb port FR and NS

message, and if there’s NS hand shaking message,
means the link layer is connected.
 秘密▲

PS Service Test

 Function test: whether or not may carry out the

attachment, and download /wap/ping/ftp
 Performance index test: rate, packet loss ratio and
delay
 Test the performance of GPRS service under four
code modes, i.e. CS1-CS4
 Test the performance of EDGE service under nine
code modes, i.e. MCS1-MCS9
 秘密▲

Course Review

 Commissioning and debugging process of BSS

system
 iBSC stand-alone debugging
 A port butt joint and CS service debugging
 Gb port butt joint and PS service debugging