zxg10 ibsc (v6.20)

ZXG10 iBSC (V6.20) Engineering Commissioning Guide Internal Use Only▲

ZXG10 iBSC (V6.20)

Engineering Commissioning Guide(2009-V1.0)

ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION.


ZXG10 iBSC (V6.20)Engineering Commissioning Guide (2009-V1.0)

Planned by: GSM Customer Service Dept., ZTE Global After-Sales Service Center

Complied by: Li Wei

Reviewed by: Zhao Yanghao

* * * *

ZTE CORPORATION

Address: ZTE Plaza, Keji Road South, Hi-tech Industrial Park, Nanshan District, Shenzhen, P.R.China

Post code: 518057

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

Hotline: +86 755 26770800 800-830-1118

Fax: +86 755 26770801

* * * *


http://support.zte.com.cn/


Legal Information

All rights reserved. No part of this documentation may be excerpted,

reproduced, translated, annotated or duplicated, in any form or by any means

without the prior written permission of ZTE Corporation.

and are the registered trade marks of ZTE Corporation. The names

and logos of ZTE products are proprietary logos or registered trade marks. The

names of other products and companies mentioned in this manual may be

proprietary to their owners respectively. Without the prior written permission of

ZTE or the owners of third-party trade marks or trade names, this manual does

not grant the reader any permission or right to use any marker appeared in the

manual.

The product described herein conforms to the design requirements of

environment protection and human security. The storage, usage, and discard

of the product should comply with the manual, related contract, or laws and

regulations of related countries.

The actual product may differ from what is described in this standard due to

frequent update of ZTE products and fast development of technologies. Please

contact the local ZTE office for the latest updating information of the product.

For the latest document information, please visit our website:

http://tsm.zte.com.cn


http://tsm.zte.com.cn/


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.



Contents1. 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

3. Check Before Power-on .............................................................................................................................. 1

3.1 Overview ................................................................................................................................................ 1

3.2 Cabinet Power Supply Check ................................................................................................................. 1

3.3 Hardware Check ..................................................................................................................................... 2

3.3.1 Cabinet .......................................................................................................................................... 2

3.3.2 Board ............................................................................................................................................ 3

3.4 Cable Check ............................................................................................................................................ 3

3.4.1 Intra-cabinet Cable ....................................................................................................................... 3

3.4.2 External Cable .............................................................................................................................. 3

3.4.3 Cable Check .................................................................................................................................. 6

3.5 Auxiliary Equipment Check ................................................................................................................... 7

3.5.1 Alarm Box Check ......................................................................................................................... 7

3.5.2 Sensor Check ................................................................................................................................ 7

3.5.3 Maintenance Terminal Check ....................................................................................................... 8

3.6 Other Check ............................................................................................................................................ 8

3.7 Record of Check Before Power-on ........................................................................................................ 8

4. Check After Power-on ................................................................................................................................. 1

4.1 Power on Procedures .............................................................................................................................. 1

4.2 Board Power Supply Check ................................................................................................................... 1

4.3 Fan Wind Test ......................................................................................................................................... 1

4.4 Record of Check after Power-on ............................................................................................................ 2



4.5 Power Off Procedures ............................................................................................................................. 2

5. OMP Installation and Debugging .............................................................................................................. 1

5.1 Prerequisites ............................................................................................................................................ 1

5.2 Brief Procedures ..................................................................................................................................... 1

5.3 Detailed Procedures ................................................................................................................................ 1

5.3.1 Serial Port Configuration OMP .................................................................................................... 1

5.3.2 Upload ZXG10.cfg ..................................................................................................................... 12

5.4 Common Debugging Command ........................................................................................................... 13

5.5 Common Problem Analysis .................................................................................................................. 15

6. SBCX O&M Software Commissioning ..................................................................................................... 1

7. Basic Data Configuration ........................................................................................................................... 1

7.1 Public Resource Configuration .............................................................................................................. 1

7.1.1 GERAN Sub Network Configuration .......................................................................................... 1

7.1.2 BSC Managed Elements Configuration ....................................................................................... 4

7.1.3 Configuration Set ......................................................................................................................... 6

7.1.4 BSC Global Resource Configuration ........................................................................................... 8

7.2 BSC Physical Configuration ................................................................................................................ 10

7.2.1 BSC Rack Configuration ............................................................................................................ 10

7.2.2 Shelf and Board Configuration .................................................................................................. 12

7.2.3 Basic Operation of Data Configuration ..................................................................................... 45

7.2.4 Switchover of Master/Slave Configuration Set ......................................................................... 48

7.2.5 Physical Data Export .................................................................................................................. 49

7.2.6 Radio Data Export ...................................................................................................................... 51

7.2.7 Software Data Export ................................................................................................................. 53

7.2.8 Network Planning & Optimization Data Export ........................................................................ 55

7.2.9 Data Backup ............................................................................................................................... 57

7.2.10 Data Recover ............................................................................................................................ 59

7.2.11 Creating BSC with Template .................................................................................................... 63

7.2.12 BTS Self-Defined Template Export ......................................................................................... 65

7.2.13 Configuring Site by Template .................................................................................................. 67

7.2.14 Commissioning/Debugging State of the BTS Configured Separately .................................... 69



7.2.15 Configuration in Batch of the BTS Commissioning/Debugging State .................................... 71

7.2.16 Setting External Alarm ............................................................................................................. 73

7.3 IP Configuration ................................................................................................................................... 75

7.3.1 Interface Configuration .............................................................................................................. 75

7.3.2 Configuration of Interface Backup Set ...................................................................................... 78

7.3.3 IPOVERE1 Configuration .......................................................................................................... 79

7.3.4 Data Synchronization ................................................................................................................. 83

7.3.5 Attentions to Data Configuration ............................................................................................... 86

7.3.6 Data Configuration Flow ............................................................................................................ 87

8. BTS and Radio Configuration ................................................................................................................... 1

8.1 BTS Physical Equipment Creation ......................................................................................................... 1

8.1.1 BS20 Configuration ...................................................................................................................... 1

8.1.2 BS21 Configuration .................................................................................................................... 15

8.1.3 BS21 (V2.0) Configuration ........................................................................................................ 17

8.1.4 BS30 Configuration .................................................................................................................... 19

8.1.5 BS30 (V1.2) Configuration ........................................................................................................ 21

8.1.6 OB06 Configuration ................................................................................................................... 26

8.1.7 B8018 Configuration .................................................................................................................. 26

8.1.8 B8112 Configuration .................................................................................................................. 34

8.1.9 M8202 Configuration ................................................................................................................. 38

8.1.10 M8206 Configuration ............................................................................................................... 41

8.1.11 S8001 Site Creation .................................................................................................................. 45

8.1.12 BS8200 Site Creation ............................................................................................................... 56

8.2 Site Connection Configuration ............................................................................................................. 56

8.3 Cell Creation ......................................................................................................................................... 61

8.4 Frequency Hopping Creation ............................................................................................................... 65

8.5 TRX Creation ....................................................................................................................................... 67

8.6 Adjacent Interference Cell Configuration ............................................................................................ 70

8.7 Adjacent Reselection Cell Configuration ............................................................................................. 72

8.8 Adjacent Handover Cell Configuration ................................................................................................ 74

8.9 Adjacent Handover and Reselection Cell Configuration ..................................................................... 76



8.10 UTRAN Adjacent Reselection Cell Configuration ............................................................................ 78

8.11 UTRAN Adjacent Handover Cell Configuration ............................................................................... 80

8.12 UTRAN Adjacent Handover and Reselection Cell Configuration .................................................... 82

8.13 GERAN External Cell Configuration ................................................................................................ 84

8.14 UTRAN External Cell Configuration ................................................................................................ 86

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

10. Software Version File Description ........................................................................................................... 1

10.1.1 Version file list (iBSCV6.20.010A for instance) ........................................................................ 1

11. Software Version Management ................................................................................................................ 3

11.1 Summary of Non-SDR BTS Software Load Flow ............................................................................... 4

11.2 Non-SDR Software Version Management Interface ............................................................................ 5

11.3 BSC Software Version Management .................................................................................................... 6

11.3.1 Version File Loaded into Database ............................................................................................. 6

11.3.2 Version Files Created in Batch to OMC ..................................................................................... 9

11.3.3 General Version Creation .......................................................................................................... 11

11.3.4 Specific Version Creation ......................................................................................................... 12

11.3.5 ompcfg.ini Creation .................................................................................................................. 14

11.3.6 Deletion from OMC ................................................................................................................. 15

11.3.7 Version File Added to NE ......................................................................................................... 18

11.3.8 General Version Activation ....................................................................................................... 19

11.3.9 Specific Version Activation/Deactivation ................................................................................ 21

11.3.10 Version File Deleted from NE ................................................................................................ 23

11.3.11 General Version Upgrade ........................................................................................................ 25

11.3.12 NE Version Files Query .......................................................................................................... 26



11.3.13 NE General Version Files Query ............................................................................................ 27

11.3.14 NE Specific Version Files Query ............................................................................................ 28

11.3.15 NE Version Information of a Specific Board Query .............................................................. 29

11.3.16 Version Data Synchronized from NE to OMC ....................................................................... 30

11.4 Non-SDR Software Version Management ......................................................................................... 31

11.5 SDR Software Installation Flow ......................................................................................................... 31

11.6 SDR Software Version Management Interface .................................................................................. 32

11.7 SDR Software Version Management .................................................................................................. 32

11.7.1 BTS Software Packet Creation ................................................................................................. 32

11.7.2 Information Query of Software Packet Version ......................................................................... 1

11.7.3 Information Query of BTS Active/Standby Software Version ................................................. 1

11.7.4 BTS Software Version Rollback ................................................................................................. 3

11.7.5 BTS Standby Software Version Activation ................................................................................ 5

11.7.6 Delete BTS Standby Software Version ...................................................................................... 7

11.7.7 Query of Operation Log of Version Packet ................................................................................ 9

12. A-interface Interconnection ..................................................................................................................... 1

12.1 A-interface Networking Mode ............................................................................................................. 1

12.1.1 Networking between iBSC & 2G CN (MSC) ............................................................................ 1

12.1.2 Networking between iBSC and 3G CN ..................................................................................... 7

1.1 Preparations for Interconnection .......................................................................................................... 14

1.2 Interconnection Data ............................................................................................................................ 15

1.3 Validity Check on Interconnection Data .............................................................................................. 15

1.4 SCN SS7 A-interface Data Configuration ............................................................................................ 18

1.4.1 Create Local NO.7 SSN ............................................................................................................. 18

1.4.2 Create Local Office .................................................................................................................... 20

1.4.3 Create Adjacent Office ............................................................................................................... 24

1.4.4 Create Route .............................................................................................................................. 37

1.5 Check after Interconnection ................................................................................................................. 43

1.5.1 Check Signaling and Traffic Load ............................................................................................. 43

1.5.2 Observe Foreground Board Status ............................................................................................. 43

1.5.3 Observe Background Alarm ....................................................................................................... 43



1.5.4 Observe by Signalling Tracking ................................................................................................. 43

1.5.5 Observe via Dynamic Data Management .................................................................................. 44

1.5.6 Test A Interface .......................................................................................................................... 44

1.5.7 Checklist for A-interface Interconnection .................................................................................. 44

Commissioning ................................................................................................................................................ 1



1. Commissioning Flow

Generally, commissioning of iBSC (including iSMG Server and Client) includes

following procedures:

(1) Preparations

(2) Check before power-on

(3) Check after power-on

(4) OMP installation and debugging

(5) SBCX O&M software debugging

(6) Basic data configuration

(7) Software loading

(8) A interface interconnection and GB interface interconnection

(9) HR/AMR commissioning

(10) Commissioning

Table 1.1-1 shows iBSC commissioning procedure.



Table 1.1-1 iBSC Commissioning Flow

SN Procedure Description

1Commissioning

preparation

Confirm system networking scheme; get IP address of Server, Client, OMP and

SBCX; fetch system configuration parameters (including A interface interconnection

data of MSC and Gb interface interconnection data of SGSN), system debugging tool,

document preparation, software preparation.

2 Check before power-on

Check the installation of racks, cables, modules and voltage of power supply.

For details, please refer to ZXG10 iBSC (V6.20) Installation Manual Hardware

Installation

3 Check after power-on

Check power supply and wind direction from fan

For details, please refer to ZXG10 iBSC (V6.20) Installation Manual Hardware

Installation

4OMP installation and

debugging

Generally, conduct initialization to start parameter setting, and upload version and

activate software

5SBCX O&M software

debugging

It covers NMS overview, networking mode, OMM installation environment

requirements and OMM software installation flow.

6 Data configuration

Configure iBSC physical data, radio data and table synchronization through OMCR.

For details, please refer to ZXG10 NetNumen-G (V6.20) Operation & Maintenance

Center Operation Manual (Configuration Management)

7 Software loading

Conduct version storage, setting and loading board software through OMCR. Reset

boards on iBSC to end version loading

For details, please refer to ZXG10 NetNumen-G (V6.20) Operation & Maintenance

Center Operation Manual (Configuration Management)

8

Installation and

debugging of SBCX

board

Install SBCX board software and conduct performance test

9

A interface

interconnection and GB

interface interconnection

Check MSC transmission and interconnection data. Observe and test after A interface

data configuration and interconnection. Check SGSN transmission and

interconnection data. Observe and test after GB interface data configuration and

interconnection.

10 HR/AMR commissioningHR/AMR commissioning description, hardware replacement, HR/AMR software

configuration, setting static and dynamic HR.

11 Commissioning test

iBSC hardware test, iSMG function test, software version test, call test, handover 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.1 Project Information

Before the equipment debugging, the equipment debugging staff should find the user’s

correct address and contact means, the person in charge from the office party and the

type of the equipment to be installed, and contact with the local representative office in

time to learn the preliminary engineering preparation, and consult the related

documents to learn details about equipment configuration, goods delivery and arrival

status.

2.2 Tools & Instruments

Prepare all the tools and meters that are required in the system debugging. The meters

and tools should be calibrated by the relevant calibration department of the

government.

1. Tools: Phillips screwdriver, flathead screwdriver, diagonal pliers, sharp nose

pliers, adjustable spanner, electric iron, solder wires, soft solder, insulating

adhesive tape, horizontal ruler, coaxial self-loop cable, wire stripper and wire

crimper.

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



performance, including iBSC and iSMG software, Solaris or Windows2000 operating

system, ORACLE database software (Version 10), platform O&M tools (installed with

probes and dynamic management), the tool for observing UDPWATCH print, telnet

tool SecureCRT, DSP OMCR monitoring software and anti-virus software. Follow the

requirements to guarantee normal iBSC commissioning and all of its functions. All

software for field use should be standard versions that have passed test of the research

institute, and it is up to the local office/representative office to request that software to

GSM Customer Service Dept. All of the versions used on site should be the formal

ones.

2.4 Document

The commissioning engineer should also refer to the following documents for

instructions:

ZXG10 iBSC (V6.20) Technical Manual

ZXG10 iBSC (V6.20) Hardware Manual

ZXG10 iBSC (V6.20) Installation Manual (Hardware)

ZXG10 iBSC (V6.20) Maintenance Manual

ZXG10 NetNumen-G (V6.20) Operation & Maintenance Manual

ZXG10 iBSC (V6.20) Test Guide

2.5 System Networking Scheme

Before system debugging, debugging engineers should get a clear picture of the system

network scheme and then draw the networking diagram, including location of every

equipment and connection relationship. For remote networking, please be aware of

locations of routers and switches, and equipment connection relationship as well.

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.

Obtain A/GB interface interconnection data and radio data.



3. Check Before Power-on

After iBSC equipment installation is completed, it must check again before power on

(it is carried out after equipment installation acceptance), to ensure installation is

absolutely correct.

It includes voltage test, hardware check, and cable check.

3.1 Overview

Once iBSC hardware installation is complete, please check the following items

carefully before power-on.

1. Check whether plug-in module installed for rack is consistent with

configuration requirement.

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.

3. Check whether cables (including cables on backplane) between different layers

and different racks are connected correctly and reliably.

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.

3.2 Cabinet Power Supply Check

1. All of the boards are not plugged in the frame. Turn off power at DC power

distribution cabinet side and two -48 V power switches. Turn off -48 V power

switch of rear frame filter.



2. Procedures of check on cabinet power supply are as follows:

(1) Check connection between DC distribution cabinet and cabinet. Check

connection between filter on top of cabinet and power distribution box. Check

connection between busbar in rear part of cabinet and power distribution box.

All of the connection points on busbar should be sealed by insulation tubes.

(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.

3. Start -48V power of DC power distribution cabinet. Measure it with multimeter.

The power should be within the range of -57 V~-40 V.

In the above tests, turn off switch immediately in case of any abnormal condition,

and then make troubleshooting.

Electric Shock

During check, pay attention to switch status to avoid electric shock.

Caution:

Wear antistatic wrist strap when contacting equipment and well arrange grounding.

3.3 Hardware Check

3.3.1 Cabinet

Check cabinets as below.

1. Check stability and neatness of cabinet. Cabinets in a row or a column should

be aligned, with deviation no more than 5 mm. And vertical deviation should be

smaller than 3 mm.

2. Ensure tightness of all fasteners.

3. Components and parts of rack should not fall or damage. Cables should not fall



or break. Labels and tags should be correct, complete and clear.

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.

3.4 Cable Check

It includes check on power cable, grounding cable, intra-cabinet cable and external

cable. The following gives introduction to categories of intra-cabinet cable and external

cable and then describes how to check cable installation. Please refer to ZXG10 iBSC

(V6.20) Installation Manual (Hardware) for details of cable configuration and

connection.

3.4.1 Intra-cabinet Cable

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.

Intra-cabinet cables have been connected before leaving factory, so it is unnecessary to

install on site. Cables between racks should connect based on the connection

relationship.

3.4.2 External Cable

iBSC external cable covers:

● Monitoring cable



Table 3.4-2 Monitoring Cable Connection

S/N Cable Name Quantity A-type cabinet B-type cabinet

1

Fan box monitor

cable

1 P _FAN BOX1 Fan box 1

2 1 P _FAN BOX2 Fan box 2

3 1 P _FAN BOX3 Fan box 3

4 1 P _FAN BOX4Top fan monitor and

control board

5

Environment

monitoring

switcher

1 PWRDB-X5_SENSORS

B1 access control

B2 IR

B3 temperature &

humidity

B4 smog

B5 standby

6Access control

monitoring cable

Upon

configurationPWRDB-X8_DOOR

B1: front door access

control

B2: rear door access

control

7Access control

monitoring cable

Upon

configurationH-MON-009_B1

Access control

sensor

8IR monitoring

cable

Upon


IR microwave

double monitoring

sensor

9

Humidity

monitoring cable

Upon


Temperature &

humidity sensor

Humidity sensorUpon

configuration- -

10Smog monitoring

cable

Upon

configurationH-MON-009_B4 Smog sensor

● 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.

When ZXG10 iBSC equipment connects with transmission equipment and

distribution frame, the shielding layer grounding should be both ends

grounding.



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

NM connection between iBSC and iOMCR adopts 100M Ethernet, as shown in

Figure 3.4-1. It is divided into three parts.

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.

Figure 3.4-1 BCTC Cable

Please refer to Figure 3.4-1 for details of external cable.

3.4.3 Cable Check

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.)

3. Intra-cabinet & inter-cabinet cable

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

(1) Cable should be loose when twisting.

(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.

3.5 Auxiliary Equipment Check

3.5.1 Alarm Box Check

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.

3.5.2 Sensor Check

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.

Smog sensor should be installed on the ceiling above cabinet.



3.5.3 Maintenance Terminal Check

Maintenance terminal should be installed separately from main equipment by glass.

The maintenance terminal should be posted labels as per the type. At least one terminal

should be equipped with modem and has line for remote maintenance.

3.6 Other Check

1. Equipment labels are intact, correct and clear.

2. Boards are placed in correct slots, and the quantity is right.

3. Switches on equipment are all on start position.

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.

3.7 Record of Check Before Power-on

No. Item Result

Data record

RemarksVoltage / No./ DIP position/

Jumper

1 Power supply check

Voltage Test □ OK □ NOK

2 Hardware check

Cabinet check □ OK □ NOK

iBSC board check □ OK □ NOK

3 Cable check

Power cable □ OK □ NOK

Grounding cable □ OK □ NOK

Internal cable □ OK □ NOK

External cable □ OK □ NOK

4 Auxiliary equipment check □ OK □ OK

5 Other check □OK □ OK



4. Check After Power-on

Once check before power-on is complete, power on iBSC equipment in correct

sequence. At that moment, iBSC data have not been configured and boards may be in

normal condition. So, check items after power-on mainly cover check on board power

supply and fan direction.

4.1 Power on Procedures

iBSC power-on procedures are as follows:

1. In DC power distribution cabinet, turn on -48 V power.

2. Turn on -48 V power switches on board in power distribution box on rack top.

3. Turn on -48 V power switches on rear box filter.

4.2 Board Power Supply Check

1. For the first-time power on, plug boards into correct slots. LED of front board

should be on. If it is off, then plug out the board to check whether power is in

normal condition.

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.

4.3 Fan Wind Test

Test procedures:

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



(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.

4.4 Record of Check after Power-on

No. Item Result Data record Remarks

1 Power-on sequence □ OK □ NOK

2Board power supply

status□ OK □ NOK

3 Fan wind test □ OK □ NOK

4.5 Power Off Procedures

1. Turn off -48 V power switches on rear box filter.

2. Turn off -48 V power switches on board in power distribution box on rack top.

3. In DC power distribution cabinet, turn off -48 V power.



5. OMP Installation and Debugging

This chapter describes system running debugging which covers serial port

configuration OMP, loading version to board, and board status check.

5.1 Prerequisites

The followings should be ready before system debugging.

1. System check has been completed and equipment has been powered on.

2. Physical data configuration has been completed via client.

Please refer to Operation Manual (Data Configuration Part) for details.

5.2 Brief Procedures

1. Serial port configuration OMP.

2. Load version on board.

3. Check board status and make sure equipment is running normally.

4. Upload zxg10.cfg.

5.3 Detailed Procedures

This section describes the debugging details.

5.3.1 Serial Port Configuration OMP

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.

Figure 5.3-2 Hperterminal Coneection Description Dialogue Box

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.



Figure 5.3-3 HyperTerminal Connection to Dialogue Box

3. In dialogue box of COM1 Properties, click Restore Defaults, and then click

OK, as shown in Figure 5.3-4.

Figure 5.3-4 HyperTerminal COM1 Properties



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.

The following is print of configuration interactive process. The bold italic is

entered by keyboard.

VxWorks System Boot

Copyright 1984-2002 Wind River Systems, Inc.

CPU: PC PENTIUM3

Version: VxWorks5.5.1

BSP version: 1.2/3

Creation date: Oct 13 2005, 18:37:29

ZZ

Boot Version : 1.08

Boot Build : 43

Boot BSP Ver : 0302.0700

Creation date: Oct 13 2005, 18:37:23



Press any key to stop auto-boot...

2 \\quickly press any key, enter serial port debugging mode

[BSP] BOOT Menu Operation Monitor Task Starting (MAX: 120 Second)...

+-----------------------------------------------------------------+

| B O O T P A S S W O R D N O T I C E |

|-----------------------------------------------------------------|

| 1. Password String: 3GPLAT (CASE NOT SENSITIVE) |

| 2. Input Timeout : 120 Seconds, or else Reboot the Board |

| 3. Max Input Retry: 5 Times, or else Booting bypass boot menu |

+-----------------------------------------------------------------+

Boot Password (3GPLAT or 3gplat)->3gplat \\enter boot password

[BSP] Kill Monitor Task [tBootMoni] Successfully!

BootMode Selection as follow:

0 - Auto boot (boot and get version from omp)

1 - Config MP net parameters (only for Omp and Cmp)

2 - Initialize flash (load flash device and init file system)



3 - Erase all flash (all data on flash will be lost)

4 - Clone flash (clone flash to host image file)

5 - Restore flash (Restore flash from host image file)

6 - Download from pc (down vxworks from pc to flash)

7 - Download self-test program (down test program from pc to flash)

8 - Run release (run the vxworks on flash down by operation 6)

9 - Run the self-test program on flash down by operation 7

r - Return to the original vxworks menu

? - Print this help list

[3GPlat Boot]: 1 \\enter the mode of configuring OMP

parameter

************Init**********

This is two cascade 32M DiskOnChip Millennium Plus Chip - G2

Create tffs device for DOC

/DOC0/ - disk check in progress ... initialized.

dosChkLib : CLOCK_REALTIME is being reset to FRI OCT 28 08:38:54 2005

Value obtained from file system volume descriptor pointer: 0x36a9cc

The old setting was THU JAN 01 00:00:01 1970

Accepted system dates are greater than THU DEC 27 00:00:00 1990

/DOC0/ - Volume is OK

total # of clusters: 31,929

# of free clusters: 13,861



# of bad clusters: 0

total free space: 27,722 Kb

max contiguous free space: 25,595,904 bytes

# of files: 39

# of folders: 5

total bytes in files: 36,070 Kb

# of lost chains: 0

total bytes in lost chains: 0

Flash Ver Dir /DOC0/VER/ already exist!

Config selection:

1 - Set Omp (or Cmp)'s Omc IP and Mac!

2 - Set Omp Boot Paras!

3 - Set OMP Boot Type !

4 - Set Net_Element Bureau No.!

5 - Quit config, return to bootmenu!

6 - print this help list

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

OMP's OMC Ip net mask is set default value 0xFF000000!

OMP's OMC Ip is :129.0.31.12!

OMP's OMC Ip netmask is :0xFF000000!

OMP's OMC Ip is :0x81001f0c!

OMP's OMC Ip netmask is :0xff000000!

Write flash bootcfg.ini file succ!

Please enter Mac in dotted decimal notations, such as 10.10.10.10.10.10!

[Enter OMP's OMC Mac address]: \\directly enter, use default MAC address

Input is null, nothing done!

Please enter Gateway IP (Not include netmask) in dotted notations, such as 0.0.0.0!

[Enter OMP's Gateway Ip address]: \\ directly enter

Input is null, 0 is set!


Please enter OMC Server Ip (Not include netmask) in dotted notations, such as 0.0.0.0!

[Enter OMC Server Ip address]: \\ directly enter

Input is null, 0 is set!


Config selection:

1 - Set Omp(or Cmp)'s Omc Ip and Mac!








Enter your selection (1/2/3/4/5):2 \\enter mode2, set OMC server IP address

Please enter Ip in dotted decimal notations, such as 129.0.0.1!

[Enter OMC Ip address]: 129.0.0.12

OMC Ip is: 129.0.0.12!


OMC FTPSVR IP is: 129.0.0.12!

Write flash /DOC0/VER/ompboot.inf file succ!

[Enter OMC FTPSVR User Name]: uep \\enter OMC server FTP user name

OMC FTPSVR User Name is: uep!


[Enter OMC FTPSVR PassWord]: uep \\ enter OMC server FTP password

OMC FTPSVR PassWord is: uep!


[Enter OMC FTPSVR FilePath]:/tmp/ftp/version/bsc12 \\enter OMC server

ompcfg.ini path (its format is /tmp/ftp/version/bscX)

Input is null, OMC FTPSVR FilePath is tmp/ftp/version/bsc12!


[Enter OMP CFGINFO FileName]: ompcfg.ini \\enter configuration file name

OMP CFGINFO FileName is: ompcfg.ini!




Config selection:

1 - Set Omp (or Cmp)'s Omc Ip and Mac!






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)

[Enter Select]: 0 \\select loading file from OMC server

You Set is :0!


Config selection:






6 - Print this help list



Enter your selection (1/2/3/4/5):4 \\enter mode4, set exchange office No.

Please enter Bureau No. (0~255):!

[Enter Bureau No.]: 12

Bureau No. is: 12!


Config selection:






6 - Print this help list

Enter your selection (1/2/3/4/5):5 \\enter mode5, quickly exit OMP configuration

mode

Quit config and return to BootMenu!

[3GPlat Boot]: 0 \\enter auto-boot mode

[BSP]memCheck 0x00408000 to 0x02408000...OK!

[BSP]memCopy 0x3e000000 to 0x00408000 Size 0x02000000...DONE!

[BSP]memCheck 0x3e000000 to 0x40000000...OK!

[BSP]memCopy 0x00408000 to 0x3e000000 Size 0x02000000...DONE!

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:

SCSMCProc: End all 69 base process power on sucess.

SCSMCProc: Current Proc InnerState is MASTER

SCSMCProc: Current MCM State is WORK

value = 1 = 0x1

Note

Board status of print is “MASTER” and “WORK”, which indicates OMP is in normal

working condition; otherwise, it is abnormal.

5.3.2 Upload ZXG10.cfg

ZXG10.cfg is foreground variable configuration file. Its details are as below:

NOT SEND CIRCUITPOOL = 0 ;whether not report CircuitPool field to

MSC,

;0 is default, which indicates to

report;1 indicates to interconnect with

Bell MSC and not to report this field.

USERPRIENABLE = 0 ; Sri Lanka EGSM/PGSM channel

; distribution strategy. 0: not use

; 1: use

CELL ID CFG = 0 ;CELLID type, 0: CELLID_LAC_CI,

;1: CELLID_CGI

CBC OMCR USED = 1 ;whether use CBC function of FBI

;0: not use, 1: use

FRONTEND IP = 129.0.31.200 ; front end processor IP address

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.

5.4 Common Debugging Command

Enter some debugging commands in HyperTerminal or telnet to view the board running

status.

When telnet logon, both user name and password are zte. Pay attention to uppercase

and lowercase during debugging.

(1) SCSShowMcmInfo

Function: display the relevant information of control process power-on process,

to judge whether board version is running normally.

Usage: enter SCSShowMcmInfo

Output: control process power-on status. If display the following information, it

indicates board process power-on succeeds.

SCSMCProc: End all 119 base process power on success.

SCSMCProc: Current Proc InnerState is MASTER \\board active/standby status

SCSMCProc: Current MCM State is WORK \\WORK indicates process power-on

succeeds

The following information indicates some process power-on fails.

SCSMCProc: Base process pZDB_Startup power on failed.


SCSMCProc: Current MCM State is WAIT_PROC_POWER_ON

(2) SCSShowVerInfo

Function: display board version information



Usage: enter SCSShowVerInfo

Output: board version information. For example:

PLAT_VERSION_ID : ZX3GPF V05.03.30

PLAT_PATCH_DATE_LIST : 2007081000

PLAT_PATCH_DATE_URGENT: 0

CPU VerInfo is:

wLgcBrdType is 20!

wPhyBrdType is 69!

wVerType is 1!

wFuncType is 1!

dwVersionNo (Hex) is 6000A40!

wCpuType is 65535!

dwPCBNum (Hex) is FFFFFFFF!

dwFileSize is 4914848!

dwVerCheckSum is 826659844!

acVerFileName is IBSC_MPX86_2_MP_P4_V6.20.102A_Z.BIN!

FPGA VerInfo is:

wLgcBrdType is 65535!

wPhyBrdType is 69!

wVerType is 2!

wFuncType is 1!

dwVersionNo (Hex) is 3006A!

wCpuType is 65535!

dwPCBNum (Hex) is FFFFFFFF!

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).

Usage: enter NfsShowState

Output: current status of blade server

When blade server is working normally and well communicating with OMP, the

following information will display:

NFS SVR IP: 129.0.31.200

NFS SVR State: ONLINE

NFS SVR Mount State: OK

Local Device Name: /nfsDev

When communication between blade server and OMP is interrupted, the

following information will display:

NFS SVR IP: 129.0.31.200

NFS SVR State: OFFLINE, HeartBeating Timeout

NFS SVR Mount State: UnMounted

(4) Reboot

Function: reset board

Usage: enter reboot

Output: none

5.5 Common Problem Analysis

During the installation and debugging of OMP, some problems may happen. The

followings are some instances and solutions.

(1) No display on HyperTerminal & unable to enter

Problem:

There is no display on HyperTerminal. When entering, no shell prompt



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.

(2) Incorrect rear board DIP switch

Problem:

RUN LED fast flashes (5Hz), ALM LED is off. Continuously print on

HyperTerminal.

Boot Task send to 128.0.31.1 msg succ! \\Note: IP should be 128.0.31.1

Boot Task send to 128.0.31.9 msg succ!

Master OMP Req Mag Send times is 8!

Timer Task send timer message ok!

Boot Task's Timer EV_TIMER_MASTER_OMP_REQ is up!

After a while, reset board and print shows the IP address is not OMP IP address.

boot device : fei

unit number : 2

processor number : 0

host name : host

file name : vxWorks

inet on ethernet (e) : 128.33.43.1:ff000000 \\not OMP IP address

host inet (h) : 128.2.2.128

user (u) : mpx86_2

ftp password (pw) : mpx86_2



flags (f) : 0x0

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.

(3) BOOT version is not the release version

Problem:

The board reset continuously. After reset, HyperTerminal prints.

Booting from network

Loading...

Solution:

The above print indicates BOOT version for debugging. When starting BOOT,

download VxWorks image from debugging PC.

It is necessary to replace release version BOOT. If board supports online

downloading BOOT, online upgrade BOOT version on debugging PC. Please

refer to the relevant document for details. If not, then it is necessary to program

BOOT chip with programmer.

(4) OMP fails to acquire ompcfg.ini on background

Problem:

RUN LED fast flashes (5Hz), ALM LED is off. Continuously print on

HyperTerminal.

0x3a6188 (tBoot): Use new ftp client. Taget: 0x1000081

Retry 8 times connect to OMC ftp server ...!

Finally print:

Get Omp VerInfo from OMC failed!

Get OmpVerInfo failed, Load Cpu VerFile From DOC!

Solution:

The above print indicates BOOT fails to acquire ompcfg.ini from OMC server.

Troubleshoot as follows:



Check whether network connection is in normal condition. For instance, check

whether network cable on OMP rear plug-in card is connected with OMC2

interface, or whether OMC IP of OMP can ping through on server. If not, check

the connection condition of network cable.

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 parameter set in OMP serial port is correct.

Check whether ompcfg.ini file is under the directory saving OMC server

version file.

(5) OMP fails to acquire version file from background

Problem: board resets continuously. After reset, print it in HyperTerminal.

Getting Omp VerInfo from OMC ...!

Get OmpVerInfo from OMC succ! \\succed to acquire ompcfg.ini

After that, print continuously:

0x3a6188 (tBoot): Use new ftp client. Taget: 0x1000081

Retry 4 times connect to OMP ftp server ...!

After printing the following information, board resets:

Connecting Omp ftp server failed!

OMP Download VerFile from OMC failed!

Before Board reset!

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.

(6) It fails to power up database process

Problem:



RUN LED fast flashes (5Hz), ALM LED fast flashes (2Hz). Enter

SCSShowMcmInfo on HyperTerminal or telnet, it displays database process

power up fails.

SCSMCProc: Base process pZDB_Startup power on failed.


SCSMCProc: Current MCM State is WAIT_PROC_POWER_ON

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.

(7) Abnormal reset of OMP or other board

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.



FTP logon OMP, copy Exc_Omp.txt or Exc_pp.txt under /DOC0. If OMP

resets, only copy Exc_Omp.txt; if other board resets, only copy Exc_pp.txt.

(8) When commissioning OMP at 6.20 platform, make sure ZDB file of OMP is in

the format of 6.20.



6. SBCX O&M Software Commissioning

Refer to ZXG10 iBSC (V6.20) OMM Software Installation Manual.



7. Basic Data Configuration

In order to be convenient for debugging and learning, we specially add basic data

configuration in this chapter. For data configuration suggestions, please refer to the

latest ZXG10 NetNumen-G (V6.20) Operation & Maintenance Center Operation

Manual (Configuration Management).

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.

7.1 Public Resource Configuration

This chapter consists of following topics: GERAN sub network, BSC managed

elements, configuration sets, and BSC global resource configuration method and

principles.

The sequence of configuring public resources is shown as in Figure 7.1-5.

GERAN sub network

BSC managed elements

configuration sets

BSC global resource

Figure 7.1-5 Public Resource Configuring Flow

7.1.1 GERAN Sub Network Configuration

GERAN sub network is an objective in the GERAN network North Interface

information model. One GERAN sub network may include one or more than one

managed elements.

7.1.1.1 Creating GERAN Sub Network

In Configuration Resource Tree, right-click OMC and click Create → GERAN

Subnetwork, as shown in Figure 7.1-6.



Figure 7.1-6 Creating GERAN Sub Network 1

Input User label and Subnetwork ID in Create GERAN subnetwork dialog box, as

shown in Figure 7.1-7. Click OK.

Figure 7.1-7 Creating GERAN Sub Network 2

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.

7.1.1.2 Querying/Modifying/Deleting GERAN Sub Network

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.



Figure 7.1-8 Querying GERAN Sub Network

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.

Figure 7.1-9 Deleting GERAN Sub Network 1



Figure 7.1-10 Deleting GERAN Sub Network 2

Click Yes in the confirmation message to delete GERAN sub network.

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.

7.1.2 BSC Managed Elements Configuration

BSC managed elements are the sub-nodes of the GERAN sub network. One managed

element can only be included in one GERAN sub network.

7.1.2.1 Creating BSC Managed Elements

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.



Figure 7.1-11 Creating BSC Managed Elements 1

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.

Figure 7.1-12 Creating BSC Managed Elements 2



7.1.2.2 Querying/Modifying/Deleting BSC Managed Elements

Querying/Modifying/Deleting BSC managed elements are the same with that of

GERAN Sub Network. Please refer to Section 7.1.1.2 Querying/Modifying/Deleting

GERAN Sub Network.

7.1.3 Configuration Set

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.

Master configuration set cannot be created or deleted separately. It must be created at

the same time when creating managed element, and be deleted when deleting the sub

network and managed element. Only one master configuration set can be created under

one managed element. It is necessary to apply mutex right in the managed element

before modifying configuration. The configuration procedures are as follows.

7.1.3.1 Creating Configuration Set

In Configuration Resource Tree, select BSC managed element node and right-click

Create → Config set as shown in Figure 7.1-13.

Figure 7.1-13 Creating BSC Config Set 1



Enter the User Label in the popup window as shown in Figure 7.1-14. Click OK to

generate new config set.

Figure 7.1-14 Creating BSC Config Set 2

7.1.3.2 Querying/Modifying/Deleting ConfigSet

Please refer to Section 7.1.1.2 Querying/Modifying/Deleting GERAN Sub Network.

7.1.3.3 Master/Slave ConfigSet Switch

1. In Configuration Resource Tree, double-click the newly created slave config

set and its properties should be displayed on the right side of window as shown

in Figure 7.1-15.

Figure 7.1-15 Queering Slave ConfigSet Properties

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.



Figure 7.1-16 Confirm Dialog Box of Switching ConfigSet

3. Click OK to complete switching the master and slave config sets.

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.

7.1.4 BSC Global Resource Configuration

BSC global resource configuration is sub node of the configuration set.

7.1.4.1 Creating BSC Function

In Configuration Resource Tree, right-click Master config set and click Create →

BSC function in popup menu as shown in Figure 7.1-17.

Figure 7.1-17 BSC Global Resource Configuration 1

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.

It is necessary to configure the virtual address of iBSC, as shown in Figure 7.1-15.




7.1.4.2 Querying/Modifying/Deleting Configuration

Please refer to Section 7.1.1.2 Querying/Modifying/Deleting GERAN Sub Network.

7.2 BSC Physical Configuration

This chapter describes configuration procedure of BSC physical equipment resources

including the rack, shelves and associated board with each shelf.

7.2.1 BSC Rack Configuration

[Purpose]

To configure a new BSC rack.

[Application]

1. To create a new BSC rack by manually initialization configuration.

2. To create a new BSC rack by adding configuration for site expanding.

[Prerequisites]

1. Public resource configuration is successfully created.

2. Make sure the rack number to configure.

[Procedures]

1. In Configuration Resource Tree, right-click OMC → GERAN Sub network

user label → BSC managed elements user label → Master Config set →

BSC Global Resource ID → BSC device config → Create → BSC rack as

shown in Figure 7.2-19.



Figure 7.2-19 Creating BSC Rack 1

2. Click BSC rack and Create BSC rack dialog box pops up as shown in Figure

7.2-20.

Figure 7.2-20 Creating BSC Rack 2

For the key parameters related with Figure 7.2-20, please refer to Table 7.2-3.

Table 7.2-3 Parameters of Creating BSC Rack

Rack Parameters

Rack ID

Integer type 1 ~ 5

Unit None

Default value 1

DescriptionThe rack number and shelf number are controlled by the DIP switch which

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

3. Click OK and corresponding rack is successfully created.

When creating rack, using the following shortcut button in Table 7.2-4 can adjust the

rack view to the best.

Table 7.2-4 Toolbar in Rack View

Shortcut Button Functions

Fit page

Zoom in

Zoom out

Reset

7.2.2 Shelf and Board Configuration

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-shelf: The resource shelf can be placed at any layer.

● 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.



Switch shelf

Layer 1

No.1 Rack (Master) No.2 Rack

Resource shelf

Control shelf

Resource shelf

Resource shelf

Resource shelf

Resource shelf

Resource shelf

Layer 4

Layer 3

Layer 2

Figure 7.2-21 Shelf Location

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.

Table 7.2-5 Shelf Description

Type Function

CTCIt has global O&M function, global clock function, control panel handling and

Ethernet switch function.

BUSN (Gk,

Mk)

It completes system access. It forms the subsystem for handling service. The

Gk platform only supports configuring Gk BUSN and the Mk platform only

supports Mk BUSN.

PSN It provides the high-capacity and block-free IP switching platform.

Take the one-rack configuration with E1 on both Abis-interface and A-interface as an

example, illustrated as in Figure 7.2-22.



Figure 7.2-22 Configuration Sample

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.

7.2.2.1 Control Shelf and Associated Board Configuration

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]

To create a control shelf along with its boards at a created rack.

[Application]

To create a new BSC control shelf along with its boards by manually initializing

configuration.

[Prerequisites]

1. Rack and public resource is successfully created.

2. Ensure the control shelf and associated boards to be configured.

[Procedures]

1. In Configuration Resource Tree, double-click OMC → GERAN Sub

network user label → BSC managed elements user label → Master Config

set → BSC Global Resource ID → BSC device config → Standard rack

name.

2. Right-click No.2 shelf of Rack 1 and select Create Shelf as shown in Figure

7.2-23.



Figure 7.2-23 Creating Control Shelf

3. Click Create Shelf and a dialog box pops up as shown in Figure 7.2-24.

Figure 7.2-24 Dialog Box of Creating Control Shelf

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.

5. Configuring OMP Board

Before configuring any other board in the control shelf, user should configure



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.

Figure 7.2-25 Creating OMP Board 1

In the Module configuration information tab, select OMP, OMP_SMP_CMP

or RPU from the Module type drop-down list, depending on actual

configuration as shown in Figure 7.2-26. Refer to Table 7.2-6 for module type

description. Click OK to finish configuring OMP board.



Figure 7.2-26 Creating OMP Board 2

Table 7.2-6 Module Type Description

Module Type Description

OMP Operation and maintenance processing board

OMP_SMP_CMPOperation and maintenance processing board/Signaling master

processing board/Calling master processing board

RPU Router protocol unit

Caution:

OMP and OMP_SMP_CMP can be only configured at module 1 and RPU can be only

configured at module 2.

6. Configuring UIMC Board

2 UIMC boards must be configured in active/standby mode and in slot 9 and

slot 10.


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.

Figure 7.2-27 Configuring UIMC Board

7. Configuring CLKG Board

2 CLKG boards must be configured in active/standby mode and in slot 13 and

slot 14.


Figure 7.2-28. Select CLKG in Board function type drop-down list, and select


Click OK.



Figure 7.2-28 Configuring CLKG Board

8. Configuring CHUB Board

2 CHUB boards must be configured in active/standby mode and in slot 15 and

slot 16.


Figure 7.2-29. Select CHUB in Board function type drop-down list, and select


Click OK.



Figure 7.2-29 Creating CHUB Board

9. Configuring CMP Board

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.



Figure 7.2-30 Configuring CMP Board 1

Click Module configuration information, as shown in Figure 7.2-31. User can

modify Module No information if necessary. Click OK.

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.



Figure 7.2-31 Configuring CMP Board 2

7.2.2.2 Resource Shelf and Associated Board Configuration

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]

To configure resource shelf along with associated boards at a created rack.

[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]


2. Ensure the resource shelf and associated boards to be configured.

3. OMP and CMP boards are successfully created.

[Procedures]



BSC Global Resource ID → BSC device config → Standard rack name.

2. Right-click the corresponding position of the rack and select Create Shelf as


Figure 7.2-32 Creating Resource Shelf




Figure 7.2-33 Dialog Box of Creating Resource Shelf

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.

5. Configuring UIMU Board

2 UIMU boards must be configured at slot 9 and 10.

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.

Figure 7.2-34 Configuring UIMU Board 1



At the Board connection information tab, set the data as defaulted as shown

in Figure 7.2-35 and click OK.

Figure 7.2-35 Configuring UIMU Board 2

6. Configuring SPB2 Board (including SPB2, GIPB2 and LAPD2)

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:

● Slot 16 cannot support serial port;

● 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.

At the Basic Information tab, select SPB2, GIPB2, or LAPD2 in Board

function type drop-down list, and we take LAPD2 as an example in following

figure.

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.



Figure 7.2-36 Creating LAPD Board 1

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.

Figure 7.2-37 Creating LAPD Board 2

Click OK to finish configuring LAPD2 board.

7. Configuring DTB Board



DTB board can be configured at any slot except slot 9, 10, 15 and 16.



At the Basic Information tab, select DTB in Board function type drop-down

list.

Figure 7.2-38 Creating DTB Board 1

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.

Figure 7.2-39 Creating DTB Board 2

8. Configuring GUP2 Board (including DRTB2 and BIPB2)

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.

(1) Configuring DRTB2 Board



At the Basic Information tab, select DRTB2 in Board function type drop-

down list.



Figure 7.2-40 Configuring DRTB2 Board 1

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.

Table 7.2-7 Trunk Parameter Explanation

Trunk Parameter Explanation

FR1 Full rate voice version 1

HR1 Half rate voice version 1

FR1_HR1 Full rate voice version 1, Half rate voice version 1

FR2 Full rate voice version 2

FR1,2 Full rate voice version 1, 2

FR2_HR1 Full rate voice version 2; Half rate voice version 1

FR12_HR1 Full rate voice version 1,2; Half rate voice version 11

FR3_HR3 Full rate voice version 3; Half rate voice version 3

FR123_HR3 Full rate voice version 1, 2, 3; Half rate voice version 3



Trunk Parameter Explanation

FR123_HR13 Full rate voice version 1, 2, 3; Half rate voice version 1, 3

Figure 7.2-41 Configuring DRTB Board 2

(2) Configuring BIPB2 Board



At the Basic Information tab, select BIPB2 in Board function type drop-

down list.



Figure 7.2-42 Creating BIPB Board 1


Selected DSP drop-down lists based on own needs as shown in Figure 7.2-43.

Click OK to finish creating BIPB2 board.



Figure 7.2-43 Creating BIPB Board 2

9. Configuring UPPB2 Board

UPPB2 board is recommended to plug at the slot 5~8 and 11~14. If it is

plugged at any slot from slot 1~4,or 15~16, the adjacent slot of UPPB2

master/slave board can be configured with the board that do not require the

internal media port such as the DTB, SDTB2.



At the Basic Information tab, select UPPB2 in Board function type drop-

down list.



Figure 7.2-44 Creating UPPB2 Board 1


Selected DSP drop-down lists based on own needs as shown in Figure 7.2-45.

Click OK to finish creating UPPB2 board.



Figure 7.2-45 Creating UPPB Board 2

10. Configure the other resource shelf according to above method.

Caution:

1. If IP SS7 at A-interface is required to configuration onsite, NMIC board must be

created at resource shelf and creating procedures are similar with that of above board.

2. If A-interface and MSC should be inter-connected via optical port, SDTB2 board

is required to create in the resource shelf and creating method is similar with that of

other board. SDTB2 board can be plugged at any slot except slot 9 and 10. It takes the

priority to be plugged at slot 17. If it is plugged at other slot other than slot 17, the

adjacent slots of master/slave board cannot be configured with the boards of HW wire

resource such as DTB and GUP2.



11. Configuring EUIP Board

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.

Figure 7.2-46 Creating EUIP Board

Caution:

1. EUIP is the processing board of IP OVER E1. It is necessary to configure when IP

OVER E1 is used.

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.

Figure 7.2-47 Creating EUIP Board

Caution:

1. EUIP 2MHW No. matches DT PCM No.

2. The time slot of EUIP 2MHW (1~31) matches that of DT PCM (1~31).

12. Configuring IPBB Board

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.

Figure 7.2-48 Creating IPBB Board

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.

7.2.2.3 Switching Shelf and Associated Board Configuration

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]

To configure switching shelf along with associated boards at a created rack.

[Application]

To create a new BSC switching shelf along with its boards by manually initializing

configuration.

[Prerequisites]


2. Ensure the switching shelf and associated boards to be configured.

[Procedures]



BSC Global Resource ID → BSC device config → Create → BSC rack →

Standard rack name.

2. Right-click No.4 shelf of rack 1 and select Create Shelf as shown in Figure

7.2-49.



Figure 7.2-49 Creating Switching Shelf


Figure 7.2-50 Dialog Box of Creating Switching Shelf

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.

5. Creating UIMC Board



Two UIMC boards, which fulfill the control plan switching function, must be

configured at slot 15 and 16.


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.

Figure 7.2-51 Creating UIMC Board

6. Creating PSN Board

2 PSN boards, which fulfill the data switching function between wire and card,

must be configured at slot 7 and 8.


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.

Figure 7.2-52 Creating PSN Board

7. Creating GLI Board

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:

GLIQV is the logical name of GLI.




in Figure 7.2-53.

At the Basic Information tab, select GLI in Board function type drop-down

list.

Figure 7.2-53 Creating GLI Board 1

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.



Figure 7.2-54 Creating GLI Board 2

7.2.3 Basic Operation of Data Configuration

Basic operation of data configuration includes: Query Configuration, Add

Configuration, Modify Configuration, and Delete Configuration.

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.



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.

Figure 7.2-55 Applying for Mutex Permission

(2) Click Apply for mutex permission, and a prompt window pops up, as


Figure 7.2-56 Prompt Window



(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.

Figure 7.2-57 Successful Application of the Mutex Permission

(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.

Figure 7.2-58 Mutex Permission Release



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.

7.2.4 Switchover of Master/Slave Configuration Set

Purpose

Switch the slave configuration set as the master one.

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.

Figure 7.2-59 Checking the Properties of Slave Configuration Set

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



window pops up as shown in Figure 7.2-60.

Figure 7.2-60 Dialogue Box for Master/Slave Configuration Set Switchover

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.

Figure 7.2-61 Switchover Completion

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.

7.2.5 Physical Data Export

Purpose

To export the physical data already configured from the system.

Prerequisites

Configured physical data is available.



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.

Figure 7.2-62 Exporting Physical Data 1

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



The exported physical data is saved as Excel format, the path is suggested to be:

\ISMG-V6.20.000a-\ums-clnt\template\excel\exceldata

7.2.6 Radio Data Export

Purpose

To export configuration data.

Prerequisites

The configured data is available.

Procedures

1. In Configuration Resource Tree, right-click BSC Global Resource Label,



select Export into Excel → Data Export in the popup menu as shown in

Figure 7.2-65.

Figure 7.2-65 Exporting Data 1

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.




3. Click Save to complete exporting. A successful prompt pops up as shown in

Figure 7.2-67.


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

7.2.7 Software Data Export

Purpose

To export software data already configured in the system.

Prerequisites

Configured software data is available.



Procedures


as Excel → Export Software Data from the drop-down list as shown in Figure 7.2-68.

Figure 7.2-68 Exporting Software Data 1

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.








\ ISMG-V6.20.000a-\ums-clnt\template\excel\exceldata

7.2.8 Network Planning & Optimization Data Export

Purpose

To export network planning & optimization data already configured in the system.

Prerequisites

Configured network planning & optimization data is available.

Procedures




as Excel→ Export Network Planning & Optimization Data from the drop-down list as


Figure 7.2-71 Exporting Network Planning & Optimization Data 1

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.








\ ISMG-V6.20.000a-\ums-clnt\template\excel\exceldata

7.2.9 Data Backup

Purpose

To back up data.

Prerequisites

Make sure the data is available.

Procedures

1. In Configuration Resource Tree, right-click Management → Data



Management → Data Backup as shown in Figure 7.2-74.

Figure 7.2-74 Data Backup 1

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).

Figure 7.2-75 Data Backup 2



3. After configuring proper parameters, click OK to backup and a window pops up

as shown in Figure 7.2-76.

Figure 7.2-76 Data Backup Result

7.2.10 Data Recover

Purpose

To recover data.

Prerequisites

Make sure the data to recover is available.

Procedures

1. In Configuration Resource Tree, right-click Management → Data

Management → Data Recovery as shown in Figure 7.2-77.



Figure 7.2-77 Data Recovery 1

2. Click Data Recovery and a window pops up as shown in Figure 7.2-78.


3. Click Select the file to backup in the popup window as shown in

Figure 7.2-79.




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.

Figure 7.2-80 Data Recovery Result

5. After recovering, user can click to set master configuration set, and a window




Figure 7.2-81 Master Config Set

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.

Figure 7.2-82 Switch Completed

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



Figure 7.2-83.

Figure 7.2-83 Data Recovery Result

Caution:

After the data is recovered and switched as master configuration set, all table

synchronization should be executed to make it valid.

7.2.11 Creating BSC with Template

Information

Purpose

To create a BSC rack with a template.

Prerequisites

1. Public resource configuration has been created successfully.

2. The rack quantity to be configured has been decided.

Procedures

1. In Configuration Resource Tree, right click BSC Equipment Configuration; select

Create → Create BSC Rack with Template from the drop-down list as shown in Figure

7.2-84.



Figure 7.2-84 Create BSC Rack with Template 1

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.

Figure 7.2-85 Create BSC Rack with Template 2

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



template is conflicted with the existing one, it cannot be created successfully.

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.

Figure 7.2-86 Result after Creating BSC Rack with Template

7.2.12 BTS Self-Defined Template Export

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


Figure 7.2-87 Exporting Self-Defined BTS Template 1

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.


7.2.13 Configuring Site by Template

Purpose

To configure site by template.

Prerequisites

BSC is successfully created.

Procedures

1. In Configuration Resource Tree, right-click Site Config → Create → Create

site by template as shown in Figure 7.2-90.



Figure 7.2-90 Configuring Site by Template 1

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.



Figure 7.2-91 Configuring Site by Template 2

Note:

Currently three templates are supported: BS20_S444, B8018_S333, and B8112_S222.

(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.

3. After completing configuration, click OK.

7.2.14 Commissioning/Debugging State of the BTS Configured Separately

Purpose

To configure the commissioning/debugging state of the BTS configured separately.

Commissioning indicates the BTS can work normally; Debugging indicates the BTS cannot work



normally which requires debugging.

Prerequisites

BSC and BTS are created successfully.

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.

Figure 7.2-92 Debugging of the BTS Configured Separately

2. Click Debugging, an icon will be displayed in front of the original BTS ID icon ,



which indicates the BTS is in debugging state.

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.

Figure 7.2-93 Commissioning of the BTS Configured Separately

4. Click Commissioning, the icon in front of site ID icon disappears, which indicates

the BTS is in commissioning state.

7.2.15 Configuration in Batch of the BTS Commissioning/Debugging State

Information

Commissioning indicates the BTS can work normally; Debugging indicates the BTS cannot work normally



which requires debugging.

Purpose

To configure in batch the BTS commissioning/debugging state.

Prerequisites

BSC and BTS are created successfully.

Note:

The BTS is in commissioning state by default after it is created successfully.

Procedures

1. In Configuration Resource Tree, right click BTS Configuration, select

Commissioning/Debugging in Batch from the drop-down list as shown in Figure 7.2-94.

Figure 7.2-94 Commissioning/Debugging in Batch 1



4. Click Commissioning/Debugging in Batch, a window pops up as shown in

Figure 7.2-95. The site for commissioning or debugging can be selected, click

OK to complete the configuration.

Figure 7.2-95 Commissioning/Debugging in Batch 2

7.2.16 Setting External Alarm

Purpose

To set external alarms.

Prerequisites

BSC and rack are successfully created.

Procedures

1. In Configuration Resource Tree, right-click Site rack, click Set external

alarm in the popup menu, as shown in Figure 7.2-96.



Figure 7.2-96 Setting External Alarm 1

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.

● Set 0: report alarm when receive signal 0.

● Set 1: report alarm when receive signal 1

Figure 7.2-97 Setting External Alarm 2

Note:



Currently, the site can support 12 dry contract nodes.

3. After configuration completed, click OK.

7.3 IP Configuration

7.3.1 Interface Configuration

[Purpose]

To complete configuring the IP Information of IP OVER E1 and IPBB (OMCB).

[Prerequisites]

BSC has been created successfully.

[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.

Figure 7.3-98 Creating IP Interface

2. Select EUIP to create EUIP interface as shown in Figure 7.3-99.



Figure 7.3-99 Creating EUIP Interface

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.

Figure 7.3-100 Creating EUIP Interface

4. Repeat Procedure 1 to create RPU (IPABIS) interface as shown in Figure 7.3-101, select RPU as

Board function type.



Figure 7.3-101 Create RPU Interface

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.

Figure 7.3-102 Creating RPU (IPABIS) Interface

6. Repeat Procedure 1 to create IPBB interface as shown in Figure 7.3-103, select IPBB.



Figure 7.3-103 Creating IPBB Interface

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.

Figure 7.3-104 Creating IPBB Interface

7.3.2 Configuration of Interface Backup Set

[Purpose]

To configure IPBB (OMCB) interface backup.

[Prerequisites]


[Procedures]

1. In Configuration Resource Tree, right click to select Configuration Set → BSC Global

Resource Label → IP Configuration → Interface Backup Group → Create → Interface




Figure 7.3-105 Creating Interface Backup Group

2. Select corresponding sub-system, module, unit, sub-unit, port No. of IPBB board as shown in

Figure 7.3-106.

Figure 7.3-106 Creating IPBB Interface Backup Group

7.3.3 IPOVERE1 Configuration

[Purpose]



To complete the relevant configuration of IP OVER E1.

[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.

Figure 7.3-107 Creating IPOVERE1 Configuration

2. Enter EUIP board information and IPOVERE1 initial TS and terminate TS as shown in Figure

7.3-108.




Caution:

E1 No. is consistent with HDLC No. configured in EUIP board.

3. In Configuration Resource Tree, right click Configuration Set → BSC Global Resource Label

→ IP Configuration → IPOVERE1 Configuration XXX → PPP Parameter Configuration as





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.



Figure 7.3-110 PPP Parameter Configuration

7.3.4 Data Synchronization

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.

7.3.4.1 Synchronizing Tables

Purpose

To synchronize all tables

Prerequisites

1. Make sure that BSC managed elements exist.

2. The connection link between foreground and background is normal.

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.



Figure 7.3-111 Synchronizing All Tables 1

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.

Figure 7.3-112 Synchronizing All Tables 2

Caution:

Save it indicates to save the data in OMP hardware, it is suggested to select Yes in

order to avoid data loss.

3. Completing configurations and click OK. If synchronization succeeds, a global

check success message appears as shown in Figure 7.3-113.



Figure 7.3-113 Synchronizing All Tables Successful

Caution:

All table synchronization only works for the data in master configuration set.

7.3.4.2 Synchronizing Modified Tables

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

1. Make sure that BSC managed elements.

2. The connection link between foreground and background is normal.

3. iBSC modified tables exist.

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


Figure 7.3-114 Synchronizing Modified Tables 1

2. Execute global data validation check and click OK, a window pops up as shown in Figure

7.3-115.



Figure 7.3-115 Synchronizing Modified Tables 2

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.

Figure 7.3-116 Synchronizing Modified Tables Successfully

Caution:

Incremental synchronization only works for the data in master configuration set.

7.3.5 Attentions to Data Configuration

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



(such as the interconnection data at A interface or GB interface, etc.), the data

should be reliable and served with a complete data configuration plan. A good plan

can not only make the data clear and in order, but also enhance the system

reliability.

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.

7.3.6 Data Configuration Flow

The data configuration flow is shown in Figure 7.3-117.



Public resource configuration

BSC physical equipment configuration

External site configuration

BTS and radio configuration

Other configuration (Optional)

Software installation

E1 for A interface configuration

E1 for Ater interface configuration

IP for A interface configuration

Internal TC , E1 for Ainterface transmission

External TC , E1 for Aterinterface transmission

Internal TC , IP for A interface transmission

E1 for GB interface configuration

IP for GB interface configuration

E1 for GB interface transmission

IP for GB interface transmission

Transparent channel configuration

(Optional)

Figure 7.3-117 Data Configuration Flow

1. Public Resource Configuration

Public resource configuration is the basis of the whole data configuration,

including creating GERAN sub-net, BSC management NE, configuration set,

BSC global resource, etc. See 7.2 Public Resource Configuration for details.



2. BSC Physical Equipment Configuration

BSC physical equipment configuration includes creating BSC rack, shelves and

boards, etc. See 7.3 BSC Physical Configuration for details.

3. A/Ater Interface Configuration

After configuring BSC physical equipment, the configuration at A interface or

Ater interface should be executed.

(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

If GPRS/EDGE service is required on site, configuration at GB interface should

be executed as per the specific needs.

● With E1 mode for GB interface transmission, E1 at GB interface should be

configured. See 9.1 E1 GB Interface Configuration.

● With IP mode for GB interface transmission, IP at GB interface should be

configured. See 9.2 IP GB Interface Configuration.

5. External Site Configuration

External site configuration includes creating GERAN and UTRAN external

sites.

6. BTS and Radio 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.



7. Transparent Channel Configuration

Transparent channel configuration is optional, the user can select according to

the needs.

8. Other Configuration

Other configuration is also optional, including alarm parameter configuration,

module parameter configuration, etc. the user can select according to the needs.

9. Software Installation

Software installation is the prerequisite for normal board operation, which

includes the software version installation of BSC and BTS boards. See chapter

11 Software Version Management for details.

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.



8. BTS and Radio Configuration

Abstract

This chapter focuses on the physical configuration and radio configuration of BTS

equipment.

8.1 BTS Physical Equipment Creation

The system supports V2 and V3 BTS.

● V2 BTS includes BTS (V2.0), BS21, BS21 (V2.0), BS30, BS30 (V7.2), and

OB06.

● V3 BTS includes B8018, B8112, M8202, M8206, S8001, and BS8200.

The methods to create all the above BTS physical equipment are described below.

8.1.1 BS20 Configuration

Purpose

To configure BS20 site.

Note:

BS20 is corresponding with the product in the model of BTS (V2.X).

Prerequisites


Procedures



BSC Global Resource ID → BSC device config → Create → Site as shown in

Figure .



Figure 8.1-118 Configuring BS20 1

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:

Serial No. only indicates IP site, which is invalid for E1 site.



Table 8.1-8 Site Parameters

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

Integer typeBS20, BS21, BS21V20, BS30, BS30V12, OB06, B8018, B8112, M8202, M8206,

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

Description

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,

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

Parameter

description

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

BTS type is B8018, B8112 or M8206, the parameter can be E1 access or IP

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

descriptionConfigure according to the on-site situation.

Permitted Access Bandwidth (Kb)

Optional values 1 ~ 65535

Unit Kb

Default value 1

Parameter

description

If BTS type is S8001 or B8200, this parameter can be modified to describe the on-

site access bandwidth.

GPS Frame No. Offset

Optional

values0 ~ 42431

Unit None

Default value 0

Parameter

description

It refers to the frame No. offset value configured in each GSM cell in GSM entire

network synchronization, when all the SDR adopts the same Frame No. reference.

This parameter is effective only when Clock Resource is set as GPS synchronization.

Serial No.

Optional

valuesNone

Unit None

Default value 00-00-00-00-00-00 00-00-00-00-00-00



Site Parameters

User label

Parameter

description

This parameter can be modified when BTS type is S8001. The former 12 digits refer

to S8001 MAC address, and the latter 12 digits refer to the authentication sequence

number (currently all digits are 0).

3. Click OK to create the site ID.

4. In Configuration Resource Tree, right-click Site ID → Create → Site rack



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.




6. Creating Common Shelf and Panels

(1) Creating Common Shelf

Right-click the blank space at the upper part as shown in Figure 8.1-122. Select

Create Shelf in the popup menu.

Figure 8.1-122 Creating BS20 Common Shelf 1

Create shelf dialog box pops up as shown in Figure 8.1-123. Click OK.



Figure 8.1-123 Creating BS20 Common Shelf 2

Note:

PDM board is created after the creation of common shelf.

(2) Creating CMM Panel

Right-click the CMM panel position and select Create Shelf in the popup menu


Figure 8.1-124 Creating CMM Panel 1

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.




Select proper PCM number and click OK to complete PCM configuration as


● Set Abis Pool No. and select time slot number from the TS No. drop-list, click

to combine the parameters to the recourse pool.

● 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.




The relationship between OMU TS configuration and actual TRX quantity is

shown in Table 8.1-9.

Table 8.1-9 OMU TS Configuration

TRX QuantityConfigured Channel

Quantity

Communication

Bandwidth

Peak Requirement of

Signaling Bandwidth

6 1 64 kbps 0~30 kbps

7~16 2 128 kbps 30~75 kbps

17~26 3 192 kbps 75 kbps~120 kbps

27~36 4 256 kbps 120 kbps~180 kbps

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.

7. Creating Resource Shelf and Panel



(1) Creating Resource Shelf

Right-click the proper position as shown in Figure 8.1-128, and click Create

Panel.

Figure 8.1-128 Creating BS20 Resource Shelf 1

Create shelf dialog box pops up as shown in Figure 8.1-129, click OK.

Figure 8.1-129 Creating BS20 Resource Shelf 2

(2) Creating AEM Panel

Right-click CDU position and select Create Panel as shown in Figure 8.1-130.



Figure 8.1-130 Creating CDU Panel 1

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.

Figure 8.1-131 Creating CDU Panel 2



(3) Creating TRM Panel

Right-click TRM panel position and select Crate Panel as shown in Figure 8.1-

132.

Figure 8.1-132 Creating TRM Panel 1

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.



Figure 8.1-133 Creating TRM Panel 2

8. TRM panel is successfully created as shown in Figure 8.1-134.

Figure 8.1-134 BS20 Rack Map

9. User can add slave rack referring to the method of creating master rack.

In Configuration Resource Tree, right-click Site ID → Create → Site rack,

and a dialog box pops up as shown in Figure 8.1-135.



Figure 8.1-135 Creating Slave Rack

Select the slave rack type and click OK to complete configuring slave rack.

Caution:

Currently, four types of master-slave rack combinations are available: BS20+B8018,

BS21/BS21V20+M8202, BS30/BS30V12+M8202, OB06+B8112. The site type is

determined according to the master rack.


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.

2. Creating shelf and Panels

(1) Creating Shelf

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


Figure 8.1-136 Creating BS21 Shelf 1

Create panel dialog box pops up as shown in Figure 8.1-137. Click OK to

complete configuration.




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.


8.1.3 BS21 (V2.0) Configuration

Purpose

To configure BS21 (V2.0)

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).

2. Creating Shelf and Panels

(1) Creating Shelf







Figure 8.1-139 Creating BS21 (V2.0) Shelf 1








Figure 8.1-141 BS21 (V2.0) Rack Map


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.


(1) Creating Shelf








8.1.5 BS30 (V1.2) Configuration

Purpose

To configure BS30 (V1.2)

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








(2) Creating CMM Board

The creation procedures are the same with that of BS20.

(3) Creating DPM Panel



Right-click the DPM position and select Create Panel as shown in Figure 8.1-

147.

Figure 8.1-147 Creating DPM Panel 1

Create panel dialog box pops up as shown in Figure 8.1-148. Click OK.

Figure 8.1-148 Creating DPM Panel 2

(4) Creating TRM Panel

The creation procedures are the same with that of BS20.




Caution:

If there are more than one rack on site, recourse shelf is required to increase.


Right-click the resource shelf position as shown in Figure 8.1-149. Select


Figure 8.1-149 Creating BS30 (V1.2) Resource Shelf 1

Create shelf dialog box pops up as shown in Figure 8.1-150. Click OK



Figure 8.1-150 Creating BS30 (V1.2) Resource Shelf 2

(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.

4. BS30 (V1.2) is successfully configured as shown in Figure 8.1-151.

Figure 8.1-151 BS30 (V1.2) Rack Map



8.1.6 OB06 Configuration

Purpose

To configure OB06 site

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.

3. OB06 is successfully configured as shown in Figure 8.1-152.

Figure 8.1-152 OB06 Rack Map

8.1.7 B8018 Configuration

Purpose

To configure B8018 site.



Prerequisites


Procedures


the Site Type selected is B8018.

2. Creating Common Shelf and Panel




Figure 8.1-153 Creating B8018 Common Shelf 1





Note:


(2) Creating EIB/FIB Panel

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.

Creating EIB Panel

Right-click the EIB panel position and select Create Shelf in the popup menu


Figure 8.1-155 Creating EIB Panel 1




Figure 8.1-156 Creating EIB Panel 2

(3) Creating CMB Panel

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.





Figure 8.1-157 Creating B8018 Resource Shelf 1






AEM includes four options: CDU10M, CDU8M, CEU, RDU and FCU. The

configuring method is the same with that of BS20.

Caution:

FCU takes up two slots, therefore if FCU is to be configured at Slot 9, CDU10M

should be configured in Slot 1 first, and Slot 8 cannot be configured with any AEM.

(3) Configuring DTRU

Note:

DTRU Panel support EDGE.

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.



Figure 8.1-159 Create DTRU Panel 1

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.

Figure 8.1-160 Create DTRU Panel 2

DTRU panel has 5 kinds of work modes, please refer to Table 8.1-10.

Table 8.1-10 DTRU Work Mode

Working Mode Description

In dual-carrier mode, diversity

reception of 4 uplinks, DPCT and

DDT are not configured.

Diversity reception of 4 uplinks, DPCT and DDT are not

configured. DTRU can be configured with two panels.

In single-carrier mode, Diversity

Reception of 4 Uplinks is configured.

Diversity reception of 4 uplinks is configured. The left

board and TX/RX relation of DTRU are configured, the

right board displays on the rack map without any

configuration data.


Reception of 4 Uplinks and DPCT are

configured.

Diversity reception of 4 uplinks and DPCT are

configured. The left board and TX/RX relation of DTRU

are configured, the right board displays on the rack map

without any configuration data.


Reception of 4 Uplinks and DPCT are

configured, when Delay Count value

is valid.

In this case the Delay Count parameter is valid.

In dual-carrier mode, diversity

reception of 4 uplinks, DPCT and

DDT are not configured.

Diversity reception of 4 uplinks, DPCT and DDT are

configured. The left board and TX/RX relation of DTRU

are configured, the right board displays on the rack map

without any configuration data.



Select proper parameters by referring above table and click OK to configure

DTRU. DTRU panel is configured successfully.

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.

3. DTRU panel is configured successfully as shown in Figure 8.1-161.

Figure 8.1-161 B8018 Rack Map



8.1.8 B8112 Configuration

Purpose

To configure B8112 site.

Prerequisites


Procedures


the Site Type selected is B8112.








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,.










(2) Creating EIB/FIB Panel

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.

The creation procedures are the same with that of B8018.



(3) Creating CMB Panel

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.

(4) Creating DTRU Panel


(5) Creating EAM Panel

Right-click the EAM position and select Create Panel in the popup menu as


Figure 8.1-166 Creating EAM Panel 1




Figure 8.1-167 Creating EAM Panel 2

4. EAM panel is configured successfully as shown in Figure 8.1-168.

Figure 8.1-168 B8112 Rack Map

8.1.9 M8202 Configuration

Purpose

To configure M8202 site.

Prerequisites




Procedures


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.

Figure 8.1-169 Creating M8202 Common Shelf 1





Note:


(2) Creating EIB and CMB Panel




Right-click the resource shelf position and select Create Shelf in the popup


Figure 8.1-171 Creating M8202 Resource Shelf 1






There are five panel types: CDU10M, CDU8M, CEU, RDU, and MDUP. The

creation procedures are the same with that of B8018.

(3) Creating DTRU


4. M8202 is configured successfully as shown in Figure 8.1-173.

Figure 8.1-173 M8202 Rack Map

8.1.10 M8206 Configuration

Purpose

To configure M8206 site.



Prerequisites


Procedures


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.






Note:


(2) Creating EIB/FIB

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.


(3) Creating CMB

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







(2) Creating AEM

Panel type is MDUP. The creation procedures are the same with that of B8018.



(3) Creating MTRU


Caution:

MTRU supports EDGE service.

4. M8206 is configured successfully as shown in Figure 8.1-178.

Figure 8.1-178 M8206 Rack Map

8.1.11 S8001 Site Creation

Purpose

To create S8001 sites.

Prerequisites

There are two modes for IP transmission, including IP Over IP and IP Over E1.

When IP Over IP is configured, the prerequisites include:



1. BSC is created successfully.

2. IPBB board is created on BSC rack.

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.

When IP Over E1 is configured, the prerequisites include:


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

1. Creating RPU Interface

(1) In Configuration Resource Tree, right click IP Configuration, select Create

→ Interface as shown in Figure 8.1-179. Or in the sub-node Interface

Configuration of IP Configuration, select Create → Interface.



Figure 8.1-179 Creating RPU Interface 1

(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. Enabling RPU Virtual Address

(1) In Configuration Resource Tree, apply for mutex property in BSC

Management NE Label, so that the parameters can be modified.

(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.



Figure 8.1-182 Enabling RPU Virtual Address

(3) Release mutex property in BSC Management NE Label.

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.

3. Creating IPBB/EUIP Interface

Caution:

The procedures and parameter description are the same for creating IPBB and EUIP

interfaces. Take the procedures to create IPBB interface for example:


→ Interface as shown in Figure 8.1-183. Or in the sub-node of Interface

Configuration of IP Configuration, right click Create → Interface.



Figure 8.1-183 Creating IPBB Interface 1

(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.




4. Creating Static Route

Caution:

Static route needs to be created only when S8001 and RPU are not in the same network

section.


→ Static Route as shown in Figure 8.1-186. Or in the sub-node of Static

Route of IP Configuration, right click Create → Static Route.



Figure 8.1-186 Creating Static Route 1

(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.



Figure 8.1-187 Creating Static Route 2

Table 8.1-11 Static Route Parameters

Static Route Parameters

User ID

Optional

valuesThe character string with the length of 40 at maximum.

Unit None

Default

valueNone

Parameter

descriptionA name to be identified by the user.

Static Route ID

Optional

values1 ~ 2048

Unit None




Default

value1

Parameter

descriptionIdentify the static route No.

Static Route Network Prefix

Optional

valuesNone

Unit None

Default

value0.0.0.0

Parameter

description

The prefix of network section, for example: the prefix of Network Section 10 is

10.0.0.0, and that of Network Section 192.168 is 192.168.0.0.

Static Route Network Mask

Optional

valuesNone

Unit None

Default

value0.0.0.0

Parameter

description

Network section mask, which identify a network section with the IP prefix

mentioned above, such as 255.0.0.0 and 255.255.0.0.

Next Hop

Optional

valuesIP, Interface, IP & Interface

Unit None

Default

valueIP

Parameter

descriptionThe Next Hop is configured as IP address, keep the default value.

Next Hop IP Address

Optional

valuesConfiguration according to the on-site situation.

Unit None

Default

value0.0.0.0

Parameter

descriptionFill in iBSC gateway address.

Management Distance

Optional

values1 ~ 254

Unit None




Default

value1

Parameter

description

A parameter of RIP protocol, which indicates that the management distance

reduces 1 (16 at most) after each router is passed; if the management distance is

0, the router discards data packet. The parameter remains the default value.

Route Allocation Label

Optional

values1 ~ 255

Unit None

Default

value3

Parameter

description

It refers to the label when route protocol is converted from RIP protocol to other

protocol (such as OSPF, IS-IS).

5. Creating S8001 Sites

The procedures to create BTS node label of S8001 site is the same as create that

of BS20, except for:

● BTS Type is S8001;

● Besides creating the parameters essential for BS20 configuration, S8001

activates two parameters for configuration including Permitted Access

Bandwidth (kb) and Sequence No. see Table 8.1-8 for parameter description.

Note:

Initial rack map is created after the creation of BTS node.

6. See Figure 8.1-188 for a sample after creation.



Figure 8.1-188 S8001 Rack Map Sample

8.1.12 BS8200 Site Creation

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

This item focuses on BS8200 sites.

Prerequisites


2. BTS physical data is configured in OMCB.

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.

8.2 Site Connection Configuration

Purpose

To save the transmission and cost, user can configure the sites by connecting several

sites together.



Prerequisites

BSC and upper level site are successfully created.

Procedures

1. Creating Lower Level Site

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.

Figure 8.2-189 Configuring Site Connection 1

2. Creating CMM Panel

(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.


(3) Click Connect and a window pops up as shown in Figure 8.2-192.




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.

Table 8.2-12 Power-Off Bypass Description

Site Type Port Description

V2 series BTS Ports AB are symmetrical with Ports DE.

B8018 Ports ABCD are symmetrical with Ports EFGH.

B8112 Ports ABC are symmetrical with Ports EFG.



Site Type Port Description

M8202Port A is symmetrical with Port E; there are no corresponding ports to

Ports BCD, which cannot be used for ring network connection.

M8206Port A is symmetrical with Port E; there are no corresponding ports to

Ports BCD, which cannot be used for ring network connection.

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



to combine the parameters to the recourse pool.

● Depending on the actual time slot needs, click to allocate OMU time

slot number.

Caution:

OMU time slot number is 16 and 25 ~ 31.

(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.

3. The site connection is successfully configured. User can double-click in

Configuration Resource Tree to query Connection Mode parameters

(Connect BSC) in property page as shown in Figure 8.2-194.


8.3 Cell Creation

Purpose

To create cell.



Prerequisites

1. BSC and site are successfully created.

2. If the cell supports GPRS or EDGE, NSE and UPPB boards should be created

first.

Procedures

1. In Configuration Resource Tree, right-click Site ID, click Create → Cell in

the popup menu as shown in Figure 8.3-195.

Figure 8.3-195 Creating Cell 1

2. Click to display all contents as shown in Figure 8.3-196. Configure other

parameter information in Create cell dialog box. Click OK.

Figure 8.3-196 Creating Cell 2



Sub-view Basic Parameter 1:

● User label

It must be configured by the user.

● 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

It should be configured according to the on-site situation. If S8001 cell is to be

created, select Pico Cell as the 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

It is configured as per on-site environment. Frequency band limits the

frequency point range of the cell, for example, if the frequency band is

GSM850, the frequency point range is 128 ~ 251.

● Subcell used

It is configured as per on-site environment.

● GPRS service supported

It is configured as per on-site environment. If it is set as Support GPRS or

Support EDGE, the corresponding GPRS or EDGE parameter settings

interface will pops up.

● Dynamic HR support indication

It is configured as per on-site environment. If it is set as Yes, the Use cell

dynamic HR parameter is activated and able to be configured.

● SMS cell broadcast used

It is configured as per on-site environment. If this function is required by the



user, it should be set as Yes.

● Use cell AMR parameter

It is configured as per on-site environment. If it is set as No, the system adopts

the AMR parameters configured in BSC by default; if it is set as Yes, the

system adopts the AMR parameters configured in the sub-views of AMR half-

rate parameters and AMR full-rate parameters.

● Common control channel configuration

It identifies the combination mode of common control channel, which should

be consistent with the on-site configuration of cell common control channel.

GPRS Basic Properties Sub-view:

● SGSN label

Select SGSN No. as per on-site requirement.

● NSE (Network Service Entity) label

NSE ID has been configured when selecting GB interface configuration.

● BSSGP virtual connection label

It identities only one GPRS cell in an NSE.

● Route Area Code

Network negotiation data, which is selected as per on-site requirement.

● UPPB Unit No.

It is selected as per the board slot configured on site.

● DSP label

It is selected from the DSP No. already configured.

3. Click OK to complete creation as shown in Figure 8.3-197.

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



modified, but not created or deleted separately.

Figure 8.3-197 Configuring Cell 3

8.4 Frequency Hopping Creation

Purpose

To create frequency hopping.

Prerequisites

BSC and site are successfully created.



Procedures

1. In Configuration Resource Tree, right-click Cell node, and click Create →

Frequency Hopping System as shown in Figure 8.4-198.

Figure 8.4-198 Configuring Frequency Hopping System 1

2. Click Frequency Hopping System and a window pops up as shown in Figure

8.4-199. Configure frequency hopping parameters. Click OK to complete

configuration.

Figure 8.4-199 Configuring Frequency Hopping System 2

Frequency hopping mode

It is selected as per on-site requirement.

MA frequency list – No.

It should be configured within the frequency point range set in Frequency



band parameter when creating the cell.

8.5 TRX Creation

Purpose

To create TRX.

Prerequisites

BSC, site and TRX boards are all successfully created.

Procedures


TRX in the popup menu as shown in Figure 8.5-200.

Figure 8.5-200 Configuring TRX 1

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.



Figure 8.5-201 Configuring TRX 2

● 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.

● BCCH carrier frequency

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.

TRX Information Sub-view

● Frequency hopping

It is configured as per the requirement whether it supports frequency hopping.



If it is set as Yes, the succeeding frequency point parameter is changed into

Frequency hopping No. parameter automatically.

● Frequency point

If frequency hopping is not supported, enter frequency point as per on-site

requirement.

● Frequency hopping No.

If frequency hopping is supported, select in the configured frequency hopping

system according to on-site environment.

● Physical panel location

Select the physical location of the carrier frequency panel corresponding with

the TRX as per on-site requirement, click to complete

configuration.

Channel Information Sub-view:

● TSC

It is configured according to on-site requirement, or configured separately in

the interface of each TS by the user.

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

TS is adopted in PDTCH according to on-site configuration. Only dynamic TS

is configured.

IP Information Sub-view:

● BIPB Unit No.

It is configured according to on-site environment.

● BIPB DSP No.

It refers to the DSP in BIPB board supporting IP, which is configured according



to on-site environment.

● DSP label sequence No.


● Port No.

It should be the IP port No. specified in TRX during IP access, which is

configured according to on-site environment.

8.6 Adjacent Interference Cell Configuration

Purpose

To configure adjacent interference cell

Prerequisites

BSC, site, cell and GERAN external cell are all successfully created.

Procedures


Adjacent interference cell in the popup menu as shown in Figure 8.6-202.



Figure 8.6-202 Configuring Adjacent Interference Cell 1

2. Input User label and parameters in Create Adjacent Interference cell dialog

box as shown in Figure 8.6-203.


● [DN of the relative cell]

Click , and select target cell from the interface as shown in Figure

8.6-204.




3. Click OK to complete the configuration.

8.7 Adjacent Reselection Cell Configuration

Purpose

To configure adjacent reselection cell

Prerequisites


Procedures


Adjacent cell reselection in the popup menu as shown in Figure 8.7-205.

Figure 8.7-205 Configuring Adjacent Cell Reselection 1

2. Configure Create Adjacent cell reselection parameters as shown in Figure 8.7-



206.


● [DN of the relevant cell]

Click and a window pops up as shown in Figure 8.7-207. Select

the cell or GERAN external cell as the reselection cell.




Note:

When creating a cell, this cell is defaulted as the reselection cell of itself by system.


8.8 Adjacent Handover Cell Configuration

Purpose

To configure adjacent handover cell.

Prerequisites


Procedures


Adjacent cell handover in the popup menu as shown in Figure 8.8-208.

Figure 8.8-208 Configuring Adjacent Cell Handover 1



2. Configure Create Adjacent cell handover parameters as shown in Figure 8.8-

209.


[DN of the relevant cell]


the cell or GERAN external cell as the handover cell.





8.9 Adjacent Handover and Reselection Cell Configuration

Purpose

To configure adjacent handover and reselection cell

Prerequisites


Procedures


Adjacent cell handover and reselection in the popup menu as shown in

Figure 8.9-211.

Figure 8.9-211 Configuring Adjacent Cell Handover and Reselection 1

2. Configure Adjacent cell handover and reselection parameters, as shown in

Figure 8.9-212.




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.

● DN of the relevant cell


the cell or GERAN external cell as the handover and reselection cell. Tick off

the parameter mutual if it is necessary to mutually set as handover and

reselection cell.





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.

8.10 UTRAN Adjacent Reselection Cell Configuration

Purpose

To configure UTRAN adjacent reselection cell

Prerequisites

BSC, site, and UTRAN external cell are all successfully created.

Procedures


UTRAN adjacent cell reselection in the popup menu as shown in Figure 8.10-

214.



Figure 8.10-214 Configuring UTRAN Adjacent Cell Reselection 1

2. Configure Create UTRAN adjacent cell reselection parameters, as shown in

Figure 8.10-215.






UTRAN target cell from the list to configure selected cell as UTRAN adjacent

cell reselection cell.



8.11 UTRAN Adjacent Handover Cell Configuration

Purpose

To configure UTRAN adjacent handover cell

Prerequisites


Procedures


UTRAN adjacent cell handover in the popup menu as shown in Figure 8.11-

217.



Figure 8.11-217 Configuring UTRAN Adjacent Cell Handover 1

2. Configure UTRAN adjacent cell handover parameters as shown in Figure 8.11-

218.






UTARN adjacent cell handover from the list.



8.12 UTRAN Adjacent Handover and Reselection Cell Configuration

Purpose

To configure UTRAN adjacent handover and reselection cell

Prerequisites


Procedures

1. In Configuration Resource Tree, right-click Cell node, and click Create→

UTRAN adjacent cell handover and reselection in the popup menu as shown

in Figure 8.12-220.



Figure 8.12-220 Configuring UTRAN adjacent Cell Handover and Reselection 1

2. Configure UTRAN adjacent cell handover and reselection parameters as shown

in Figure 8.12-221.

Figure 8.12-221 Configuring UTRAN adjacent Cell Handover and Reselection 2

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.



UTARN adjacent cell handover from the list.



Figure 8.12-222 Creating UTRAN Adjacent Cell Switchover and Reselection 3


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.

8.13 GERAN External Cell Configuration

Purpose

To configure GERAN external cell

Prerequisites

BSC was successfully created.

Procedures

1. In Configuration Resource Tree, right-click External cell config and click

Create → GERAN external cell in the popup menu, as shown in Figure 8.13-

223. Or right-click External cell config→ GERAN external cell config and



click Create → GERAN external cell.

Figure 8.13-223 Configuring External Cell 1

2. Configure he parameters as shown in Figure 8.13-224. Click OK to complete

configuration.

Figure 8.13-224 Configuring External Cell 2

Cell type, MCC, MNC, Frequency band, BCCH frequency, LAC, CI, NCC,

BCC

The above mentioned are negotiable data, which should be configured

according to on-site planning.

GPRS service supported




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.

8.14 UTRAN External Cell Configuration

Purpose

To configure UTRAN external cell

Prerequisites


Procedures

1. In Configuration Resource Tree, right-click External cell config and click

Create → UTRAN external cell in the popup menu, as shown in Figure 8.14-

225. Or right-click External cell config → UTRAN external cell config and

click Create → UTRAN external cell.

Figure 8.14-225 Created GERAN External Cell 1

2. Configure he parameters as shown in Figure 8.14-226. Click OK to complete

configuration.



Figure 8.14-226 Created GERAN External Cell 2

UTRAN cell type, MCC, MNC, Frequency, LAC, RNC ID, C ID, Scrambling

code, TX diversity indication, Route area code

The above mentioned are negotiable data, which should be configured

according to on-site planning.

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

9.1.1 NSE Configuration

Information

NSE is used when the cell supports GPRS/EDGE.

Purpose

To configure Network Service Entity (NSE).

Prerequisites


Note:

The lower node SGSN is automatically created.

Procedures

1. In Configuration Resource Tree, right-click GB interface related config →

Create → NSE as shown in Figure 9.1-227. Or in SGSN office ID → NSE

config, right-click Create → NSE.

Figure 9.1-227 Creating NSE 1

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.




Table 9.1-13 NSE Parameters

NSE Parameters

NSE ID


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

Description

To identify subnet type. As per the protocol48.018, there are two types in

subnet: frame trunk and IP.

For E1 GB interface, select frame trunk.

9.1.2 BRCH Configuration

Purpose

To configure Broadcast Channel (BRCH) at GB interface

Prerequisites

1. BSC was successfully created.

2. GIPB board and Gb interface PCM were successfully created.

Procedures

1. In Configuration Resource Tree, right-click GB interface related config, and

click Create → BRCH in the popup menu as shown in Figure 9.1-229. Or in

GB interface related config → BRCH config, right-click Create → BRCH.



Figure 9.1-229 Creating BRCH 1

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.

Figure 9.1-230 Creating BRCH 2

Table 9.1-14 BRCH Parameters

BRCH Parameters

SGSN ID

Integer type Depending on actual configuration of SGSN

Unit None

Default value 1

DescriptionOnce supporting Flex GB, iBSC connects with multiple SGSNs. It

distinguishes those SGSNs.

Physical Link


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

Description

CPU sub card coding. This relation between CPU ID and PCM ID is: CPU1

manages PCM9 ~ PCM12; CPU2 manages PCM13 ~ PCM16; CPU3

manages PCM17 ~ PCM20; CPU4 manages PCM21 ~ PCM24.

Channel


Unit None

Default value 1

Description This channel ID is a CPU internal link logical ID.

MCC Start Time Slot


Unit None

Default value 0

Description

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

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

Description

PCM number of accessing GIPB. This relation between CPU ID and PCM ID

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

Description

Polling timer for all PVC status. Each T391 local end sends one STATUS

ENQUIRY message to the opposite end. STATUS ENQUIRY only performs

Link Integrity Verification. One total status enquiry is performed every N391

period.

N392

Integer type 3 ~ 8

Unit None

Default value 3

Description

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

N392 no error link integration verification, report the fault relief to the upper

level.

N393

Integer type 4 ~ 10

Unit None

Default value 4

Description

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

N392 no error link integration verification, report the fault relief to the upper

level.

T391


Unit 10 ms

Default value 1000

DescriptionComplete state detection polling counter. Each T391 local end sends one

STATUS ENQUIRY message to the opposite end.

9.1.3 NSVC Configuration

Purpose

To configure Network Service Virtual Connection (NSVC)

Prerequisites

1. BSC was successfully created.

2. NSE and Gb interface BRCH were successfully created.



Procedures

1. In Configuration Resource Tree, right-click NSE ID, and click Create →

NSVC in the popup menu as shown in Figure 9.1-231.

Figure 9.1-231 Creating NSVC 1

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.



Figure 9.1-232 Creating NSVC 2

Table 9.1-15 NSVC Parameters

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


Unit None

Default value None

Description NSVC ID

DLCI


Unit None

Default value 100

DescriptionThe DLCI value should be consistent with the SGSN. It is a planned value. The

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

DescriptionIt is a selection list and its data come from the BRCH. 5 pieces of NSVC

maximally can be configured at one BRCH.

BE


Unit bit

Default value 100

DescriptionExcessive size of the burst packet. In the Tc period, the max excessive size of

the burst packet user.

BC


Unit KB

Default value 640

DescriptionCommitted burst packet size, usually set as 640KB× Number of Time Slot. In

the Tc period, the max committed burst packet size of one user.

TC(Network testing time)


Unit 10 ms

Default value 1000

Description Network testing time

9.2 IP GB interface Configuration

9.2.1 NSE Configuration

Information

NSE is used when the cell supports GPRS/EDGE.

Purpose

To configure Network Service Entity (NSE).

Prerequisites


Note:



The lower node SGSN is automatically created.

Procedures

1. In Configuration Resource Tree, right-click GB interface related config →

Create → NSE as shown in Figure 9.2-233. Or in SGSN office ID → NSE

config, right click Create → NSE.


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.




Table 9.2-16 NSE Parameters

NSE Parameters

NSE ID


Unit None

Default value 0

Description To identify NSE.

Subnet type

Integer type Frame trunk, IP

Unit None

Default value Frame trunk

Description

To identify subnet type. As per the protocol48.018, there are two types in

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

Description

It indicates the acquisition mode of the opposite end node. The static

configuration is to configure the node of SGSN on BSC. The dynamic

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


Unit None

Default value 0

Description To identify NSE.

Unit None

Default value 0.0.0.0

Description

When Dynamic Configuration is used, the opposite end node ((IP+UDPPORT)

is acquired from the opposite end via the configuration flow. One of the

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


Unit None

Default value 0

Description

When Dynamic Configuration is used, the opposite end node (IP+UDPPORT)

is acquired from the opposite end via the configuration flow. One of the

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.

9.2.2 IPGB Port Configuration

Purpose

To configure IPGB port.

Prerequisites

1. BSC global resource and IPGB board were successfully created.

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

1. In Configuration Resource Tree, right-click SGSN Office ID, select Create

→　IPGB Port in the drop-down list as shown in Figure 9.2-235. Or in SGSN

office ID　 IPGB port config, right-click Create → IPGB Port.



Figure 9.2-235 Creating IPGB Port 1

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.



Figure 9.2-236 Creating IPGB Port 2

Table 9.2-17 IPGB Port Parameters

IPGB Port Parameters

NSE ID

Integer type Depending on actual configuration

Unit None

Default value None

Description

When selecting Local Port for Port Type, NSE ID is the one of the same BSC

global resource and with IP for the subnet type. When selecting Opposite Port

for Port Type, NSE ID is the one of the same BSC global resource, with IP

for the subnet type and static configuration for the configuration type.

IP Address

Integer type In the format of 4 bits, i.e. xxx.xxx.xxx.xxx (xxx is 0 ~ 255)

Unit None

Default value None

Description

When selecting Local Port for Port Type, it is configured as the IP address

unoccupied by IP Abis interface of RPU (the IP address for IP Abis in IP

Information page of BSC global resource). When selecting Opposite Port for

Port Type, it is configured as the opposite IP address, which is consistent with

the opposite data.

UDP Port

Integer type for local port: 32768 ~ 32928

for opposite port: 0 ~ 65535



IPGB Port Parameters

Unit None

Default value None

Description To set the value of UDP port.

Port Type

Integer type The local and opposite end ports

Unit None

Default value Local port

DescriptionTo set the type of port. Different types of ports influence the integer type and

default value of UDP port.

Signaling Weight


Unit None

Default value 10

Description

To set the value of signaling weight. It indicates the selection frequency of

the port when sending signaling. If it is the local port, it is the frequency of

selecting the source port as the local one when sending signaling to the

opposite end. Also, when the dynamic configuration is adopted, it is the

frequency of selecting the weight value as the target port when sending the

weight value to SGSN. When the opposite port weight acquired in static

configuration and the opposite port weight acquired in dynamic configuration

are sending signaling to the opposite port, it indicates the selection frequency.

For instance:

If the weights of two ports are both 10, their frequencies are the same. If the

weight of port 1 is 10 and that of port 2 is 20, the frequency of the latter is

twice by that of the former.

Data Weight


Unit None

Default value 10

DescriptionTo set the value of data weight. It indicates the selection frequency of the port

when sending data.

Unit No. of IPGB Board

Integer type The actual unit No. of IPGB board

Unit None

Default value None

Description

When selecting Local port for Port Type, it is marked on the position where

configures IPGB board of BSC. When selecting Opposite port for Port Type,

it is the set value 65535, which is invalid.

3. Add IP configuration: BSC global resource →IP Information, input RPU address

in IPGB of the virtual IP address.



10. Software Version File Description

10.1.1 Version file list (iBSCV6.20.010A for instance)

Note:

Due to version changes, the followings may be different from the actual condition. For

any question, please contact ZTE.

Physical board

type

Logical

board

type

Version type Version file name Remarks

MPX86MP CPU iBSC_MPX86_2_MP_P4_V6.20.010A_Z.BIN OMP version

file FPGA MPX86_04_040704_FPGA107.RBF

MPX86 RPU CPU iBSC_MPX86_2_RPU_P4_ V6.20.010A _Z.BINRPU version

file

MPX86MP CPU iBSC_MPX86_2_MP_P4_ V6.20.010A _Z.BIN SMP version

file FPGA MPX86_04_040704_FPGA107.RBF

UIM_2 UIM CPU

iBSC_UIM_2_UIM_8260_ V6.20.010A _Z.BIN

iBSC_UIM_2_UIM_755_ V6.20.010A _Z.BINUIMC

version file

GUIM

UIMCPU iBSC_UIM_2_UIM_8260_ V6.20.010A _Z.BIN GUIMU

version file

— FPGA GIUM_03_060803_FPGA_108.bin

CHUB CHUB CPU iBSC_CHUB_CHUB_8245_ V6.20.010A _Z.BINCHUB

version file

ICM ICM CPU IBSC_ICM_ICM_852_V6.20.010A_Z.BINICM version

file

DTB DTB CPU iBSC_DTB_DTB_852_V6.20.010A_Z.BINWith 852

subcard, DTB

GLIQV GLI

CPUiBSC_GLIQV_GLI_CPU0_XSCALE_ V6.20.010A

_Z.BINProcess-in

cellMICROCODE iBSC_GLIQV_GLI_INGRESS_ V6.20.010A.UOF

CPUiBSC_GLIQV_GLI_CPU1_XSCALE_ V6.20.010A

_Z.BINProcess-out

cellMICROCODE iBSC_GLIQV_GLI_EGRESS_ V6.20.010A.UOF



Physical board

type

Logical

board

type

Version type Version file name Remarks

FPGA GLIQV_00_040201_FPGA.BIN

EIPI/BIPI/GIPI

EUIPCPU IBSC_MNIC_2_IPI_23XX_V6.20.010A_Z.BIN EIPI version

fileMICROCODE UC_IBSC_MNIC_2_IPI_V6.20.010A.UOF

IPBBCPU IBSC_MNIC_2_IPBB_23XX_V6.20.010A_Z.BIN

BIPI/GIPI

version file

MICROCODE UC_IBSC_MNIC_2_IPBB_V6.20.010A.UOF

IPGBCPU IBSC_MNIC_2_IPGB_23XX_V6.20.010A_Z.BIN

MICROCODE UC_IBSC_MNIC_2_IPGB_V6.20.010A.UOF

PSN PSN CPU

iBSC_PSN_PSN_860_ V6.20.010A _Z.BIN

iBSC_PSN_PSN_852_ V6.20.010A _Z.BINPSN version

file

SDTB SDTB

CPU iBSC_SDTB_SDTB_860_ V6.20.010A _Z.BIN SDTB

version file,

select the

correspondin

g FPGA file

upon actual

condition of

PCB board

FPGA

SDTB_00_040301_FPGA_104.RBF

SDTB_01_040302_FPGA_105.RBF

SPB

SPB CPU iBSC_SPB_SPB_85XX_ V6.20.010A _Z.BIN

LAPD CPU iBSC_SPB_LAPD_85XX_ V6.20.010A _Z.BIN

GIPB CPU iBSC_SDTB_SDTB_860_ V6.20.010A _Z.BIN GIPB

VTCD

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

DRTB DSP iBSC_VTCD_DSPC6414_AMREN_ V6.20.010A.BIN

UPPB CPU iBSC_VTCD_UPPB_8260_ V6.20.010A _Z.BINVTCD

version file

UPPB DSP iBSC_VTCD_DSPC6414_UPPB_ V6.20.010A.BIN



11. Software Version Management

Abstract

Software load involves the following major procedures: import the version file to the

database, add the version to the NE, create general version, activate the version, and so

on. By importing the version to the database and OMC, the system copies the local

software to ZXG10 NetNumen-G server and modifies the background database. By

synchronizing the NE, the system then uploads ZXG10 NetNumen-G server via FTP to

the corresponding iBSC OMP and modifies OMP database. By creating general

version, the system generates general version at the background and modifies the

related data forms in the background database. By creating specific version, the system

generates the specific version in iOMCR and modifies the related data forms in the

background database. By activating general version, the system generates the general

version at the foreground and modifies the related data forms in the foreground

database. By updating general version, the system modifies the general version at both

foreground and background. By activating specific version, the system generates the

specific version at the foreground and modifies the related data forms in the foreground

database. By deactivating specific version, the system deletes the specific version at the

foreground and modifies related data forms in the foreground database. By deletion

from NE, the system deletes the foreground version, and by deletion from OMC, it

deletes the background version. This chapter will elaborate on the software version

management.

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.

Confidential and Proprietary Information of ZTE CORPORATION. 3


11.1 Summary of Non-SDR BTS Software Load Flow

The main flow of software load is shown in Figure 11.1-237 below.

Select software version

Import software into database

Set general software version

Set specific software version

Activate general software version

Activate specific software version

Query running iBSC software

Start

End

Figure 11.1-237 Software Load Flow

1. Select software version

Select the software version according to the actual demands. The version

information should include software ID and version number.

2. Import software to database

Before the software is loaded, it should be firstly imported to the database. By

executing Create Version File to OMC or Create Version Files in Batch to

OMC, the system copies the software from the client to ZXG10 NetNumen-G

server, and then through Synchronizing Version Data to NE, the system FTPs



the software form ZXG10 NetNumen-G server to corresponding iBSC OMP. At

the same time, the version information is written in both the foreground and

background databases.

3. Set general software version

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.

4. Load general software version

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.

5. Set specific software version

This procedure is to create, modify or delete the specific software of a specific

board.

6. Load specific software 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.

7. Query the running foreground software

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.

11.2 Non-SDR Software Version Management Interface

Log on to ZXG10 NetNumen-G client and select the menu View → Software Version

Management to open the Software Version Management interface, as shown in

Figure 11.2-238 below.



Figure 11.2-238 Software Version Management Interface

11.3 BSC Software Version Management

11.3.1 Version File Loaded into Database

[Purpose]

It focuses on loading BSC version file to database.

[Prerequisites]

1. Communication between the client and the server is normal.

2. Related BSC version file is available to be loaded into database.

[Procedures]

1. In the Software Version Management interface, double click OMC → GERAN

subnet → BSC managed element → BSC software management, and double-

click BSC software management. As shown in Figure 11.3-239 below, select

the BSC store software in the sub-menu on the right.



Figure 11.3-239 Create Version File to OMC 1

2. Click in the toolbar and a window pops up as shown

in Figure 11.3-240 below.


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.





3. Click OK to complete creation, as shown in Figure 11.3-243 below.




11.3.2 Version Files Created in Batch to OMC

[Purpose]

Create BSC version files in batch to OMC.

[Prerequisites]


2. Related iBSC version files for batch creation are available.

[Procedures]

1. Click in the toolbar in Figure 11.3-239 and a box

pops up as shown in Figure 11.3-244 below.

Figure 11.3-244 Create Version Files In Batch To OMC 1

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.


11.3.3 General Version Creation

[Purpose]

Create general BSC software version.

[Prerequisites]


2. Related BSC version file has been created to OMC.

[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.



Figure 11.3-249 Create General Version 1

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



11.3.4 Specific Version Creation

[Purpose]

Create specific software version.

[Prerequisites]




2. Related BSC version file has been created to OMC.

[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.

Figure 11.3-252 Create Specific Version 1

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



11.3.5 ompcfg.ini Creation

[Purpose]

Create ompcfg.ini for the application in foreground and background.

[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.



Figure 11.3-257 Create ompcfg.ini 1

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.


3. As shown in Figure 11.3-259, a box pops up indicating that the operation is

executed successfully.


11.3.6 Deletion from OMC

[Purpose]

Delete BSC version from OMC.

[Prerequisites]


2. The BSC version to be deleted is not activated.



[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.

Here is an example of deleting a BSC specific version:

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.

Figure 11.3-260 Delete from OMC 1

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



4. Click Delete from OMC and a box pops up as shown in Figure 11.3-264 below.




5. Click OK and a box pops up as shown in Figure 11.3-265 below.


This version does not exist in the sub-view any more, as shown in Figure 11.3-

266 below.


11.3.7 Version File Added to NE

[Purpose]

Add BSC version to NE.

[Prerequisites]

Communication between the client and the server is normal.

[Procedures]

1. In the sub-views of BSC software management, right-click the proper version

and select Add version file to NE, as shown in Figure 11.3-267 below.



Figure 11.3-267 Add Version File to NE 1

2. Click Add version file to NE and a box pops up as shown in Figure 11.3-268

below.


3. Click OK and a box pops up as shown in Figure 11.3-269 below.


11.3.8 General Version Activation

[Purpose]

Activate general software version.

[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.

Figure 11.3-270 Activate General Version 1

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.


Click OK and a box pops up for confirmation as shown in Figure 11.3-272.


3. Click OK and a box indicating successful operation pops up as shown in Figure

11.3-273.




11.3.9 Specific Version Activation/Deactivation

[Purpose]

Activate and deactivate specific version.

[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.



Figure 11.3-274 Activate Specific Version 1

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.



Figure 11.3-278 Cancel Activation 1

6. Click Cancel activation and a box pops up to indicate the result as shown in

Figure 11.3-279.

Figure 11.3-279 Cancel Activation 2

11.3.10 Version File Deleted from NE

[Purpose]

Delete the BSC version file from NE.

[Prerequisites]


2. The version file to be deleted is not activated.

[Procedures]

Notes:

1. If the version has not been created as the general version or specific version, it can



be directly deleted from OMC in the BSC store software sub-view.

2. If the version 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.

Here is an example of deleting a BSC specific version:

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.

Figure 11.3-280 Delete Version File from NE 1

3. Click Delete version file from NE and a box pops up as shown in Figure 11.3-

281 below.


4. Click OK and a box pops us as shown in Figure 11.3-282 below.




11.3.11 General Version Upgrade

[Purpose]

Upgrade the BSC general version.

[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.

Figure 11.3-283 Upgrade General Version 1

2. Click Upgrade and a box pops up as shown in Figure 11.3-284 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.


11.3.12 NE Version Files Query

[Purpose]

Query NE version files.

[Prerequisites]


[Procedures]

In the Software Version Management interface, double click OMC → GERAN

subnet → BSC managed element → BSC software management, and click in

the toolbar in Figure 11.3-287.



Figure 11.3-287 iBSC Stored Software Version Query Result

11.3.13 NE General Version Files Query

[Purpose]

Query NE general version files.

[Prerequisites]




[Procedures]




Figure 11.3-288 iBSC General Software Version Query Result

11.3.14 NE Specific Version Files Query

[Purpose]

Query the NE specific version files.

[Prerequisites]


[Procedures]






Figure 11.3-289 BSC Specific Software Version Query Result

11.3.15 NE Version Information of a Specific Board Query

[Purpose]

Query NE version information of a specific board.

[Prerequisites]


[Procedures]


subnet → BSC managed element → BSC software management, and click

in the toolbar . A box pops up as shown in Figure

11.3-290 below.

Figure 11.3-290 Query NE Version Information 1



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.

Figure 11.3-291 Query NE Version Information 2

11.3.16 Version Data Synchronized from NE to OMC

[Purpose]

Synchronize the BSC version data from NE to OMC.

[Prerequisites]


[Procedures]


subnet → BSC managed element → BSC software management, and click

in the toolbar . A box pops up as shown in Figure

11.3-292 below.

Figure 11.3-292 Synchronize Version Data from NE to OMC 1

2. Click OK to execute synchronization. After synchronization is completed, a box

pops up as shown in Figure 11.3-293 below.



Figure 11.3-293 Synchronize Version Data from NE to OMC 2

11.4 Non-SDR Software Version Management


subnet → BSC managed element → BTS software management, and double click

BTS software management. As shown in Figure 11.4-294 below.

Figure 11.4-294 BTS Software Version Management

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.

11.5 SDR Software Installation Flow

Take B8200 GU360 for instance, software packet is adopted as SDR software.

Software packet can be downloaded to main control panel CCH, which is managed and

distributed to each board by CC.

The operation procedures of the software packet include:

Load to database: Load the software packet to OMM system.

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.

11.6 SDR Software Version Management Interface

Log on to OMM, click View → Software Version Management, the Software Version Management

interface is shown in Figure 11.6-29511.6.

Figure 11.6-295 Software Version Management Interface

11.7 SDR Software Version Management

11.7.1 BTS Software Packet Creation

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


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

The site will restart after successful activation.



11.7.2 Information Query of Software Packet Version

Abstract

Query the file information of the software version packet already loaded into the

database.

Premise

Software version management view is accessed.

BTS software packet loaded into database is available.

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

11.7.3 Information Query of BTS Active/Standby Software Version

Abstract

Query the information of current and standby BTS software versions.

Premise



The BTS works normally.

The connection between BTS and NM server is normal.

OMM software version management sub-view has been accessed.

Procedures:

1. Double click SDR software version management node in Configuration Resource

Tree to enter the interface as shown in Figure 11.7-307.

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:

The system jumps to software version information page at foreground, where

active and standby versions are displayed as shown in Figure 11.7-309.

Figure 11.7-309

Double click a queried message of BTS version, detailed software version

information will be shown in Detailed Version Information of a Single NE as

Figure 11.7-310.

Figure 11.7-310

11.7.4 BTS Software Version Rollback

Abstract

Roll back to original version after updating the BTS software version.



Premise

BTS works normally.



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

2. Click the button (Query information), a window pops up; click OK to

enter the interface as shown in Figure 11.7-312.

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.

11.7.5 BTS Standby Software Version Activation

Abstract

Activate BTS standby software version and make it as active version.

Premise

BTS works normally.


OMM software version sub-view has been accessed.

Procedures:


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


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.

11.7.6 Delete BTS Standby Software Version

Abstract

To delete the standby software version that is useless in the BTS.

Premise

BTS works normally.



Procedures:


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


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

11.7.7 Query of Operation Log of Version Packet

Abstract

Query the operation log of a version packet, including sending download command,

download result, activating result, etc.

Premise:

Software version management sub-view has been accessed.



There is BTS software packet loaded in the database.

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

3. Set query conditions and click OK.

Result:

Query result is displayed in the operation log of version packet as shown in Figure

11.7-322.

Figure 11.7-322



12. A-interface Interconnection

12.1 A-interface Networking Mode

12.1.1 Networking between iBSC & 2G CN (MSC)

The networking topology is shown in the figure below.

iBSC TC

A interface

MSC

In this case, iBSC has only one MSC as its adjacent office. The iBSC A-interface data

must be configured as follows:

1. Configure signaling point of local office

The signaling point of local office should be configured, as shown in the figure below.

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.



3. Configure the adjacent office

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.

4. Configure the adjacent No.7 SSN 0, 1 and 254.

5. Configure No.7 PCM



6. Configure the No.7 link set

The No.7 link set consists of several signaling links. Usually one link set is enough

for an adjacent office.

7. Configure the No.7 link

Designate PCM, TS, SMP module, and Link code SLC in the figure below.



8. Configure the No.7 route

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.

9. Configure the No.7 office route



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.

12.1.2 Networking between iBSC and 3G CN

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:



HLR/AUC

SCP

SMPSCE

GGSN

GMSCS/SSP

PSTNSMSC

OMC

SDP

SGSN

BSC

Internet

Packet Switch Network

NO.7 Signalling Network

Packet Swtich Network

RNC

Circuit Switch Network

GMGW

MGW

MSCS/VLR/SSP

MGCF

IM-MGW

IMS Domain

The following part describes three networking modes between iBSC and 3G CN.

12.1.2.1 Networking Mode 1

iBSC is associated with MGW only. CN provides the signaling points for MGW and

MSCServer. The networking topology is as follows:

iBSC

A interface

MGWMSCServer

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 A interface should be configured as follows:

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.

Logically, PCM circuit between iBSC and CN is logically managed by

MSCServer. Therefore, N7PCM should be configured under MSCServer.

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.

1. Configure Local office.

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.

3. Configure Adjacent office 1. Office type should be set as MGW and AM as AM

SURE. Other parameters including SSF, SPC type, DPC should be consistent

with CN.



4. Configure the MGW No.7 SSN 0 and 1.

5. Configure Adjacent office 2. Office type should be set as MSCSERVER and

AM as AM QUASI. Other parameters including SSF, SPC type, DPC should be

consistent with CN.



6. Configure the MSCServer No.7 SSN 0, 1 and 254.

7. Configure the MSCServer N7PCM.

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.

The data configuration is shown in the following figures:

Local Office Signaling Point

Signaling Sub-System

Adjacent Office Data

Adjacent Office Sub-System

No.7 PCM



Signaling Link Set

Signaling Link

Signaling Route

Signaling Office Route


iBSC is associated with MGW only. CN provides the signaling point for MGW. The

networking topology is as follows:



iBSC

A interface

MGWMSCServer

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.

This networking mode is widely adopted.


iBSC is associated with both MGW and MSCServer. CN provides the signaling point

for MSCServer. The networking topology is as follows:

iBSCVoice relay

MGW

MSCServer

A interface

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.1 Preparations for Interconnection

Make sure the follow work is done before A-interface interconnection:



1. Installation and debugging of iBSC has been finished. All boards can run

normally.

2. Installation and debugging of the server is done.

3. MSC runs normally and the A-interface data configuration is done.

4. Transmission between iBSC and MSC is normal.

5. Related data for A-interface interconnection has been obtained from MSC.

1.2 Interconnection Data

To guarantee a successful interconnection, the data should be adjusted at both sides of

A interface and MSC until both configurations are consistent.

MSC signaling point: 14-digit signaling point code (decimal, 3-8-3

format) or 24-digit signaling point code

iBSC signaling point: 14-digit signaling point code (decimal, 3-8-3

format) or 24-digit signaling point code

PCM number of A interface

CIC

SS7 link TS (time slot)

SLC (SS7 link code)

E1 number for SS7 link

Link error connection method: usually the basic error correction

method

Type of signaling link group: usually the 64K narrowband signaling

link group

Frame format of E1 interface

SSF (sub-service field)

1.3 Validity Check on Interconnection Data

1. Signaling Point Code

If the signaling point is unreachable, the reason is usually improper division of



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.

Therefore, the decimal number 18-50 corresponds to the binary 0010010-

0110010, which is 1+38+2 (decimal, 3-8-3 format. Pay attention to its

difference with BSCV2 decimal 2354 format). Other division algorithms such

as the 6-8 format are not detailed here.

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.

2. Type of Signaling Point

The type of signaling points should meet the following requirements: in

ZXG10 iOMCR, BSC is set as 1 (SEP: signaling end point), MSC is set as 3

(STEP: signaling transfer end point).

3. Signaling Link Code

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

ITU-T CCSS7 has 4 types of NI (network identification): 00 IN (international



network, 24-digit), 01 INS (international standby network, 14-digit), 10 NI

(national network, 24-digit) and 11 NIS (national standby network, 14-digit).

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:

Signaling network testing and maintenance message

Unknown A message (unknown A-interface message)

5. Subsystem Status Enquiry

Query R_N7SSN STATUS bits and make sure all the STATUS bits are 0.

6. Frame Format of E1 Interface and SPB/DTB Impedance Settings

(1) Frame Format of E1 Interface

The default frame format is usually the double-frame format. Currently,

DTB/SPB can support multi-frame CRC check format. Non-framing format

can be provided for the future.

(2) DTB/SPB Transmission Impedance Settings

The default transmission impedance of DTB/SPB is 75 ohm. However, the

international field widely uses the 120-ohm wire (twisted pair). Inconsistent

impedances may cause failed connection at A interface or frequent transient

link disconnections.

7. Clock Sync Extraction Position

Currently, ZXG10 iBSC extracts clock from the first E1 of SPB.

8. Configuration of Local NO.7 SSN

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.

9. Link Error Correction Method

Usually the basic error correction method is adopted.

10. Type of Signaling Link Group

Usually the 64K narrowband signaling link group is adopted.

1.4 SCN SS7 A-interface Data Configuration

This section mainly introduces the A-interface resource configuration of SCN SS7.

1.4.1 Create Local NO.7 SSN

[Purpose]

Create local No.7 SSN.

[Prerequisites]


[Procedures]

1. In Configuration Resource Tree, right click OMC → GERAN subnet

→ BSC managed element → Config Set → BSC global resource → A

interface related config, as shown in Figure 12.5-323 below. Right-click

A/Ater interface related config to select Create → Local NO.7 SSN.



Figure 12.5-323 Create Local NO.7 SSN 1

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.

Figure 12.5-324 Create Local NO.7 SSN 2

Table 12.5-18 Parameters of Local NO.7 SSN



Parameters of Local NO.7 SSN

User label

Type & Range Character string with the length of 1~40 at most

Unit None

Default Value None

Description Identify the user name

Subsystem NO.

Type & Range Integer type: 0~255

Unit None

Default Value 0

DescriptionID of the subsystem. For actual configuration, three types of 0, 1 and 254

should be created.

System Tag

Type & Range Only one subsystem, backup subsystem

Unit None

Default Value Only one subsystem

Description Set the subsystem as only one subsystem or backup subsystem

Backup Sub-System Office ID

Type & Range 0

Unit None

Default Value 0

DescriptionOnly when System tag is set as Backup subsystem will this parameter be

valid.

Backup Sub-System No.

Type & Range 0~255

Unit None

Default Value 0

DescriptionOnly when System tag is set to Backup subsystem will this parameter be

valid.

1.4.2 Create Local Office

1.4.2.1 Create Primary Node for Local Office

[Purpose]

Create the primary node for local office.

[Prerequisites]


[Procedures]



1. In Configuration Resource Tree, right click to select OMC → GERAN

subnet → BSC managed element → Config Set → BSC global

resource → A/Ater interface related config → Create → Local office,

as shown in Figure 12.5-325 below.

Figure 12.5-325 Create Local Office 1

2. Click Local Office and a box pops up as shown in Figure 12.5-326

below. Input the correct parameters and click OK to complete creation.

Refer to Figure 12.5-326 for related parameters.



Figure 12.5-326 Create Local Office 2

Table 12.5-19 Parameters of Local Office

Parameters of Local Office

User label


Unit None

Default Value None


Network type

Type & Range CTCN, CMCN, CUCN, RLTN, CNC, NFTN, Net 7, Net 8

Unit None

Default Value CTCN

Description Select the network type according to the actual conditions

Netapp info

Type & Range Netapp disabled, Netapp enabled

Unit None

Default Value Netapp disabled

Description It refers to whether the network appearance is valid

Net appearance

Type & Range 0~8

Unit None

Default Value 0




Description

If Netapp info is set to Netapp disabled, this parameter is invalid. To

separate the public SCTP coupling traffic of SG and ASP (applied server

program), Net appearance is used to recognize SS7 signaling network.

OPC (14 bits)

Type & Range

Main signaling zone 0~7

Sub-signaling zone 0~255

Signaling point 0~7

Unit None

Default Value 0, 0, 0

Description

For China’s GSM network, 14-bit signaling code is used between MSC and

BSC.

Main signaling zone the 3 highest among the 14 signaling points

Sub-signaling zone the 8 bits in the middle

Signaling point the 3 lowest bits

This parameter should be consulted with other devices.

OPC (24 bits)

Type & Range

Main signaling zone 0~255

Sub-signaling zone 0~255

Signaling point 0~255

Unit None


Description

For China’s GSM network, 24-digit signaling point code is used between

MSC and other entities.

Main signaling zone the 8 highest among the 24 signaling points

Sub-signaling zone the 8 bits in the middle

Signaling point the 8 lowest bits

This parameter should be consulted with other devices.

TUP user support

Type & Range Yes, No

Unit None

Default Value No

Description Decide if the system supports TUP user

ISUP user support


Unit None

Default Value No

Description It indicates whether the system supports ISUP user

SCCP user support


Unit None

Default Value Yes




Description It indicates whether the system supports SCCP user

1.4.3 Create Adjacent Office

1.4.3.1 Create Primary Node for Adjacent Office

[Purpose]

Create the primary node for adjacent office.

[Prerequisites]

BSC and the primary signaling node of local office have been created successfully.

[Procedures]


→ BSC managed element → Config Set → BSC global resource →

A/Ater interface related config → Local office → Create → Adjacent

office, as shown in Figure 12.5-327 below. Select Adjacent Office and

click .

Figure 12.5-327 Create Adjacent Office 1

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.



Figure 12.5-328 Create Adjacent Office 2

Table 12.5-20 Parameters of Adjacent Office

Parameters of Adjacent Office

User label


Unit None

Default Value None


Office ID

Type & Range 1~64

Unit None

Default Value 1

Description Number the adjacent office

Office type

Type & Range MGW, MSCSERVER, SMLC




Unit None

Default Value MGW

DescriptionMark the type of the adjacent office: MGW office, MSCSERVER office or

iBSC SMLC office

Office code

Type & Range 8-digit decimal integer

Unit None

Default Value 00000000

Description Number the office

Domain type

Type & Range DOMAIN SCN, DOMAIN IP

Unit None

Default Value DOMAIN SCN

Description

It indicates the domain type of the adjacent office viewed from the local

office.

If adjacent office is associated to the local office, it should be configured

according to the actual connection type. For example, TDM/ATM

connection is configured as DOMAIN SCN, and IP connection is configured

as DOMAIN IP. If it is quasi-associated to the local office via SG and

DOMAIN IP signaling point and the local office is DOMAIN SCN

signaling point, SG is configured as DOMAIN SCN and quasi-associated

DOMAIN IP signaling point as DOMAIN IP. Or if it is quasi-associated to

the local office via SG and DOMAIN SCN signaling point and the local

office is DOMAIN IP signaling point, SG is configured as DOMAIN IP and

quasi-associated DOMAIN SCN signaling point as DOMAIN SCN.

STEP type

Type & Range SEP, STP, STEP

Unit None

Default Value STEP

Description Configure the type of signaling point

SSF

Type & RangeGlobal signaling code, Global backup signaling code, Signaling code,

Backup signaling code

Unit None

Default Value Global signal code

Description The users should select the type according to the network type

DPC

Type & Range 14-digit code range: 0~7, 0~255, 0~7

24-digit code range: 0~255, 0~255, 0~255

Unit None





Description

Configure the signaling point code for the adjacent office, which varies with

the SSF parameters. For Global signal code/Global backup signal code, it is

24-digit; and for Signal code/Backup signal code, it is 14-digit.

AM

Type & Range AM SURE, AM QUASI, AM NONE

Unit None

Default Value AM SURE

Description It indicates the association mode according to the actual configuration

Test ID

Type & Range NEED TEST, DO NOT NEED TEST

Unit None

Default Value NEED TEST

Description It indicates whether test is needed, usually NEED TEST

Protocol type

Type & Range CHINA, ITU, ANSI

Unit None

Default Value CHINA

Description Select protocol type

Band flag


Unit None

Default Value No

Description It refers to whether broadband is supported

1.4.3.2 Create Adjacent NO.7 SSN

[Purpose]

Create adjacent No.7 SSN.

[Prerequisites]

BSC and the primary signaling nodes of local office and adjacent office have been

created successfully.

[Procedures]



A/Ater interface related config, double click the data already

configured, as shown in Figure 12.5-329.



Figure 12.5-329 Create Adjacent NO.7 SSN 1

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.



Figure 12.5-330 Create Adjacent NO.7 SSN 2

Table 12.5-21 Parameters of Adjacent NO.7 SSN

Parameters of Adjacent NO.7 SSN

User label


Unit None

Default Value None


Subsystem NO.

Type & Range 0~255

Unit None

Default Value 0

Description Number the subsystem of adjacent office

System tag

Type & Range Only one subsystem, Backup subsystem

Unit None

Default Value Only one subsystem

Description Set the subsystem as Only one subsystem or Backup subsystem

Backup system office ID

Type & Range 0, 1

Unit None

Default Value 0

DescriptionOnly when System tag is set as Backup subsystem can this parameter be

valid.

Backup subsystem NO.

Type & Range 0~255

Unit None

Default Value 0

DescriptionOnly when System tag is set as Backup subsystem can this parameter be

valid.

1.4.3.3 Create NO.7 PCM

[Purpose]

Create No.7 PCM.

[Prerequisites]





[Procedures]

1. In Configuration Resource Tree, unfold OMC → GERAN subnet →

BSC managed element → Config Set → BSC global resource →


configured, and meanwhile select NO.7 PCM as shown in Figure 12.5-

331.

Figure 12.5-331 Create NO.7 PCM 1






Figure 12.5-332 Create NO.7 PCM 2

Table 12.5-22 Parameters of NO.7 PCM

Parameters of NO.7 PCM

User label

Type & Range Character string with the length 40 at most

Unit None

Default Value None


N7PCM

Type & Range 0~1023

Unit None

Default Value 1

Description Number No.7 PCM

Unit

Type & Range Depend on the actual system configuration

Unit None

Default Value Depend on the actual system configuration

Description None

PCM



Parameters of NO.7 PCM

Type & Range 9~24

Unit None


Description None

1.4.3.4 Create NO.7 Link Set

[Purpose]

Create NO.7 link set.

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]



[Procedures]




configured, meanwhile select NO.7 Link set, as shown in Figure 12.5-

333 below.



Figure 12.5-333 Create NO.7 Link Set 1






Figure 12.5-334 Create NO.7 Link Set 2

Table 12.5-23 Parameter of NO.7 Link Set

Parameter of NO.7 Link Set

User label

Type & Range Characters string with the length of 40 at most

Unit None

Default Value None


Signaling link set No.

Type & Range 1~512

Unit None

Default Value 1

DescriptionNumber the link set. There are at most two signalling link sets under one

adjacent office, and only one link set is recommended.

Link error calibration method

Type & Range Basic, PCR

Unit None

Default Value Basic

Description

This parameter decides the link error calibration method and it should be set

in compliance with the operator’s requirements and link transmission delay.

Basic: It is a non-compel method of positive/negative

acknowledgement, retransmission and correction. It can ensure that in

normal status the signal units are transferred correctly, in sequence and non-

repeatedly and in abnormal status it can control retransmission and make

calibrations.

PCR (preventive cyclic retransmission): It is a non-compel method of

positive acknowledgement, cyclic retransmission and correction. If there are

no new signal units or link units for transmission, the system will

automatically resend the signal units that are stored in the retransmission

buffer and haven’t got positive acknowledgements, that is, PCR. If there are

new signal units, the system will stop cyclic retransmission and give priority

to new unit transmission.

Generally speaking, Basic error calibration method is adopted for

transmission delays less than 15ms, and PCR is for delays over 15ms.

Type of signaling link set

Type & Range 64 K link group, 2 M link group

Unit None

Default Value 64 K link group

Description Set the type of signaling link set



1.4.3.5 Create NO.7 Link Data

[Purpose]

Create NO.7 link data.

[Prerequisites]



[Procedures]




configured, and meanwhile select NO.7 Link, as shown in Figure 12.5-

335 below.



Figure 12.5-335 Create NO.7 link 1




Figure 12.5-336 Create NO.7 link 2

Table 12.5-24 Parameters of NO.7 link

Parameters of NO.7 link

User label

Type & Range Character string with the length of 40 at most

Unit None

Default Value None


Link

Type & Range 1~5000

Unit None

Default Value 1

Description Number the signalling link. Every link set can have at most 16 links.



Parameters of NO.7 link

Unit


Unit None


Description None

PCM


Unit None


Description None

TS

Type & Range 1 ~ 31

Unit None

Default Value 1

Description Configure TS according to actual conditions

SMP module


Unit None


Description Mark the SMP module number of the signalling link

Link code SLC

Type & Range 0~15

Unit None

Default Value 0

Description

Configure the link code. Currently one office can be configured with at

most 16 links whose SLCs should be different. No matter if the 16 links

belong to the same link or two links, they should meet the above

requirement.

Link info

Type & Range Link is not self-loop, Link is self-loop

Unit None

Default Value Link is not self-loop

Description Set if the link is self-loop

1.4.4 Create Route

1.4.4.1 Create NO.7 Route

[Purpose]

Create NO.7 route.



[Prerequisites]

BSC and the primary signaling nodes of local office have been created successfully.

[Procedures]




configured, meanwhile select NO.7 route, as shown in Figure 12.5-337

below.

Figure 12.5-337 Create NO.7 Route 1






Figure 12.5-338 Create NO.7 Route 2

Table 12.5-25 Parameters of NO.7 Route

Parameters of NO.7 Route

User label


Unit None

Default Value None


Route

Type & Range 1~1000

Unit None

Default Value 1

Description Number the signaling route

Office ID

Type & Range Comply with the office ID during the adjacent office configuration

Unit None

Default Value Comply with the office ID during the adjacent office configuration

Description Select from the configured adjacent office IDs

Linkset 1

Type & Range 0~1

Unit None

Default Value 0

Description 0 indicates there is no Linkset 1.

Linkset 2

Type & Range 0~1

Unit None



Parameters of NO.7 Route

Default Value 0

Description 0 indicates there is no Linkset2.

Link arrangement mode

Type & RangeRandom, SLS_bit0, SLS_bit1, SLS_bit2, SLS_bit3, SLS_bit0~1,

SLS_bit1~2, SLS_bit2~3

Unit None

Default Value Random

Description Depend on actual configuration

1.4.4.2 Create NO.7 Office Route

[Purpose]

Create No.7 office route.

[Prerequisites]

BSC and the primary signaling nodes of local office have been created successfully.

[Procedures]




configured, meanwhile select NO.7 office config, as shown in Figure

12.5-339 below.



Figure 12.5-339 Create NO.7 Office Route 1






Figure 12.5-340 Create NO.7 Office Route 2

Table 12.5-26 Parameters of NO.7 Office

Parameters of NO.7 Office

User label


Unit None

Default Value None


Office ID

Type & Range Depend on the actual configuration

Unit None

Default Value Select from drop-down list

Description Number the office

Route 1


Unit None

Default Value 0

DescriptionIt is the number of normal route. 0 indicates invalid route or there is no

such a route.

Route 2


Unit None

Default Value 0

DescriptionIt is the number of Alternative Route 1. 0 indicates invalid route or there is

no such a route.

Route 3


Unit None

Default Value 0


no such a route.

Route 4


Unit None

Default Value 0


no such a route.



1.5 Check after Interconnection

1.5.1 Check Signaling and Traffic Load

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.

1.5.2 Observe Foreground Board Status

1. Observe the DTB indicator

If the E1 indicator flashes quickly, it indicates the DTB can receive MSC

signals.

If the E1 indicator doesn’t flash, the transmission should be checked. Locate

the disconnected transmission by link-by-link self-loop.

2. Observe the SPB indicator

If it flashes quickly, it indicates the signaling is normal.

If it flashes slowly, check if the SS7 data configuration is consistent with that

of MSC.

1.5.3 Observe Background Alarm

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.

2. Query iBSC alarms for unreachable signaling points or SS7 L3 alarms.

If there are, it means signaling at the two ends has problems and needs further

check.

1.5.4 Observe by Signalling Tracking

Access the signalling tracking interface of the client, open the configuration box, and

select A interface and the SS7 link to be tracked.



1.5.5 Observe via Dynamic Data Management

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.

1.5.6 Test A Interface

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.

1.5.7 Checklist for A-interface Interconnection

No. Item Result Data Record Remark

1 State of foreground boards ð OK ð NOK

2 Background alarms ð OK ð NOK

3 Observation of signaling tracking ð OK ð NOK

4 Observation of dynamic data management ð OK ð NOK



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




GGSN Gateway GPRS Support Node

GMSC Gateway MSC

GMSK Gaussian Minimum Shift Keying

GPRS General Packet Radio Service

GSM Global System for Mobile Communication

GTP GPRS Tunnel Protocol

H

HLR HOME Location Register

HSCSD High-Speed Circuit Switched Data

I

IMSI International Mobile Subscriber Identity

IP Internet Protocol

IR Incremental Redundancy

ISDN Integrated Services Digital Network

ISUP

IWF Inter-Working Function

L

LA Link Adaptation

LLC Logic Link Control

LQC Link Quality Control

M

MAC Medium Access Control

MAP Mobile Application Protocol

MCS Modulation and Coding Scheme (EDGE)

MGW Media GateWay

MM Mobile Management

MS Mobile Station

MSC Mobile Switching Center

MTP Message Transfer Part

N

NE Network Element

NMS Network Management System

NSEI Network Service Entity Identifier

NSS Network Switching Subsystem

NSVCI Network Service Virtual Connection Identifier

O

OMP Operation & Maintenance Processor board

OMS Operation and Maintenance Subsystem

OSI Open System Interconnect

P




PACCH Packet Associated Control CHannel

PAGCH Packet Access Grant CHannel

PBCCH Packet Broadcast Control CHannel

PCCCH Packet Common Control CHannel

PCH Paging Channel

PCM Pulse Code Modulation

PCU Packet Control Units

PDN Public Data Networks

PDP Packet Data Protocol

PDTCH Packet Data Traffic Channel

PLMN Public Land Mobile Network

PNCH Packet Notification Channel

PPCH Packet Paging Channel

PRACH Packet Random Access Channel

PSTN Public Switched Telephone Network

PTCCH Packet Timing advance Control Channel

Q

QoS Quality of Service

R

RACH Random Access Channel

RAID Redundant Array of Independent Disk

RAN Radio Access Network

RLC Radio Link Control

RPE-LTP Regular Pulse Excitation-Long Term Prediction

RRM Radio Resources Management

S

SACCH Slow Associated Control Channel

SCCP Signaling Connection Control Part

SCH Synchronization Channel

SDCCH Standalone Dedicated Control Channel

SGSN Serving GPRS Support Node

SIM Subscriber Identity Module

SMC Short Message Center

SNDCP Subnetwork Dependent Convergence Protocol

SNMP Simple Network Management Protocol

SPB Signaling Process Board

SS7 Signaling System 7

SSF Sub-Service Field

STP Signaling Transfer Point

T




TACS Total Access Communication System

TAI Timing Advance Index

TBF Temporary Block Flow

TCH Traffic Channel

TDMA Time Division Multiple Access

TLLI Temporary Logical Link Identity

TMSI Temporary Mobile Subscriber Identity

TRAU Transcoding and Rate Adaptation Unit

U

USF Uplink State Flag

V

VLR Visitor Location Register

VPN Virtual Private Network

8-PSK 8 Phase Shift Keying


zxg10 ibsc (v6.20)

Documents