ZXG10 iBSC Configuration

Objectives

After the course, you will be able to

Get familiar with the configuration management window and master the configuration flow
Master iBSC global resource configuration
Master iBSC physical configuration
Understand interconnection parameters of E1 A interface and master interconnection
operation
Understand interconnection parameters of IP A interface and master interconnection
operation
Understand interconnection parameters of E1 Gb interface and master interconnection
operation
Understand interconnection parameters of IP Gb interface and master interconnection
operation

Prerequisites

Has finished ZXG10 iBSC Structure and Principle

Familiar with hardware structure and operating principles
of iBSC

Contents

Overview
Global Resource Configuration
BSC Physical Configuration
E1 A Interface Connection
IP A Interface Connection
E1 Gb Interface Connection
IP Gb Interface Connection
Data Synchronization

Configuration Management of OMCR

Button Description

Configuration Management Tool Bar Button

Button Description

Configuration Management Tool Bar Button

The toolbar for configuration management element might differ according to specific configuration
management elements. User can place the mouse on a button to view its tip. In this table, the
master configuration set is taken as the configuration management element.

Configuration Flow

Configuration Flow

Data Planning
Before configuring data, you need to plan data. All parameters
must be configured according to the data planning.
Hardware Inspection
Before configuring data, you need to check whether the racks,
boards, and cables of iBSC satisfy the data planning and whether
there is any faulty hardware.
Global Resource Configuration
Configure global parameters of BSC that is valid for the entire
BSC, such as MCC (MCC), MNC (MNC), and OMP IP (OMP_IP).
BSC Physical Configuration
Configure racks, boards, and cable connection of BSC.

Configuration Flow

IP A Interface Connection
It refers to the interconnection in the IP bearing mode on A interface.
IP Gb Interface Connection
It refers to the interconnection in the IP bearing mode on a Gb
interface.
E1 A Interface Connection
It refers to the interconnection in the E1 bearing mode on A
interface.
E1 Gb Interface Connection
It refers to the interconnection in the E1 bearing mode on a Gb
interface.
Data Synchronization
The data configured on the OMCR must be sent to iBSC via data
synchronization and the data must be valid.

Configuration Precautions

Data configuration is very important for the entire system. Any mistake in
data configuration will seriously influence the system running. The following
items should be noticed in data configuration and modification
Before performing data configuration, prepare the data related to system
running, such as interconnection data for A-interface and Gb interface.
The data should be accurate and reliable, and a complete data
configuration solution is required. A good data configuration solution not
only makes the data clear to users but also increases the system
reliability
Before modifying any data, perform backup for the current data. After
modifying the data, synchronize it with that at BSC and BTS. Make sure
that the data is correct and perform data backup in time
The configured data in the network management system client takes
effect only after being synchronized with that at BSC and BTS. For
configuration data applied in a running system, the data must be
checked before being transferred to avoid the influence of incorrect data
on the system running.

Contents

Overview
Global Resource Configuration
BSC Physical Configuration
E1 A Interface Connection
IP A Interface Connection
E1 Gb Interface Connection
IP Gb Interface Connection
Data Synchronization

Configuration Flow

Create GERAN Subnetwork

Create BSC Managed Element

Apply Mutex Right

There is only one client that can read and write configuration data under
one BSC managed element. The client can perform configuration only
after mutex right is applied.

Create Config Set

All the configuration data of a BSC is saved in one Config Set. Multiple
Config Sets can be created under one BSC, but there is only one active
Config set.
After a BSC managed Element is created, an active Config Set is
generated automatically.

Create BSC Function

This operation guide guides you how to create a BSC function. The parameters in the
BSC Function are valid for the entire BSC and the cells under the BSC.

Contents

Overview
Global Resource Configuration
BSC Physical Configuration
E1 A Interface Connection
IP A Interface Connection
E1 Gb Interface Connection
IP Gb Interface Connection
Data Synchronization

Configuration Flow

Create BSC Rack

This operation guide guides you how to create a BSC shelf. The control shelf
of the BSC must be 2nd shelf.

Create BSC Board

Create the OMP obard of the control shelf first.

Before creating service boards, create UIM boards for
each shelf.
The created boards must exist on the BSC rack and the
models must be correct.

Board Property

Contents

Overview
Global Resource Configuration
BSC Physical Configuration
E1 A Interface Connection
IP A Interface Connection
E1 Gb Interface Connection
IP Gb Interface Connection
Data Synchronization

A Interface Networking

iBSC is associated with MGW only. CN provides two signaling points

MGW and MSCServer.

Configure two adjacent offices. iBSC is associated with MGW and quasiassociated with the MSC server.
iBSC is associated with MGW. Configure signaling links under MGW.
Logically the PCM circuit between iBSC and CN is managed by the MSC
server. Threfore, N7PCM should be configured under MSC Server.
You need to configure to signaling office routes. One is to MGW and the other
is to the MSC server.
There is no service signaling between iBSC and MGW. Therefore, there is no
need to configure the subsystem 254 (BSSAP) under MGW.

A Interface Networking

iBSC is associated with MGW only. CN provides the MGW signaling

point.

Regard MGW and the MSC server as an entity. Configure one adjacent office.
Configure Mc interface between MGW and the MSC so that the signaling can
be automatically forwarded.

A Interface Networking

iBSC is associated with MGW and the MSC server respectively. CN

provides the MSCServer signaling point.

In this networking mode, iBSC is connected with MGW and the MSC server
respectively.
No signaling needs to be sent to MGW. Therefore, logically MGW and the MSC
server is an entity.
Data configuration of iBSC is the same with that for 2G MSC interconnection.
The only difference is that only signaling is being transmitted without voice
channels although the trunk circuit to the MSC server is configured as N7PCM.

Data Planning
Name

Meaning

Value

MSC Signaling Point

N/A

MGW Signaling Point

BSC Signaling Point

/
/

2.200.1
2.200.7

AM

Connection relationship
between MGW and BSC

AM Sure

SSF
SPC Type

Sub-Service Field
Signaling Point Code Type

Signal code
SPC 14

No.7 PCM

N7PCM number of A interface

0,1,2,3 (corresponding to
PCM 9,10,11,12 of SDTB)

No.7 Link/Start TS

PCM and time slot where the

interface A signaling link is
located

PCM 9/TS 16

Link code SLC

Link error calibration method
E1 Frame mode

No.7 Signaling link code

/
/

7
Basic
Double frame

Configuration Flow

Configuring Board

Create Local Office

For the BSC, local office is itself. This operation guide guides you how to create a BSC
signaling point and other related properties.

Create Adjacent Office

In this example, iBSC is associated with MGW. CN provides Signalling point code of
MGW. Therefore, you just need to created the adjacent office MGW.

Create No.7 PCM

Create No.7 Link Set

The total of two signaling link groups from iBSC to an adjacent office can
be created.

Create No.7 Link

Each signaling link must belong to a signaling link set.

Create No.7 Route

Each signaling route can belong to one or two link sets.

Create No.7 Office

Each office can use up to four No.7 routes.

Set PLMN/MSC Office

Contents

Overview
Global Resource Configuration
BSC Physical Configuration
E1 A Interface Connection
IP A Interface Connection
E1 Gb Interface Connection
IP Gb Interface Connection
Data Synchronization

Data Planning
Name
MSC Signaling Point

Meaning
/

Value
2.253.1

MGW Signaling Point /

N/A

BSC Signaling Point

2.7.1

AM

Connection relationship between MSC and BSC

AM Sure

SSF

Sub-Service Field

Signal code

SPC Type

Signaling Point Code Type

SPC 14

IPI_CP

Real interface of iBSC A interface on the control plane 172.28.1.7

IPI_UP

Real interface of iBSC A interface on the user plane

172.28.3.7

CS_CP

Control plane virtual address of iBSC A interface

172.28.2.7

CS_UP

User plane virtual address of iBSC A interface

172.28.4.7

Data Planning
Name

Meaning

Value

MSC_Virtual

Virtual address of MSC

10.63.208.238

GW_to_MSC

Gateway from iBSC to the

virtual address of MSC

172.28.1.254

MGW_Virtual

MGW virtual address

10.63.207.237

GW_to_MGW

Gateway from iBSC to the

virtual address of MGW

172.28.3.254

ASP Protocol Type

M3UA

ASP Property

Server

ASP Local Port

3007

ASP Remote Port

3007

AS Service Mode

Participate

Configuration Flow

Configuring Board

Create IP A Interface

Create Real Interface IP

The real address interface is on the

IPI board.

Create IP A Interface

Create Virtual Interface IP

The virtual address of IP A interface is on the

RPU.

Create Static Route

Since iBSC and CN are not in the
same network segment, you need to
add a route to the CN.

Create Local Office

Create Adjacent Office

Create ASP
The signaling to an office is handled by
an application server. Each application
server can include multiple application
server processes. Each application
server process works in the Participate
mode.

Create AS

Create SIO

You need to set SIO locating information for all the MSC server adjacent offices.

Create User Plane Service

This operation guide guides you how
to create IP port on the user plane and
set the virtual address of the user
plane.

Set PLMN/MSC Office

Contents

Overview
Global Resource Configuration
BSC Physical Configuration
E1 A Interface Connection
IP A Interface Connection
E1 Gb Interface Connection
IP Gb Interface Connection
Data Synchronization

Data Planning
Name

Meaning

Value

NSEI

NSE ID

70

NSVCI

NSVC ID

71

BRCH

Gb bearing channel

PMC9 (TS1~TS31)

DLCI

23

E1 Frame mode

Double frame

Configuration Flow

Configuring Board

Set PLMN/SGSN Office

Create NSE

Create BRCH

Create NSVC

Contents

Overview
Global Resource Configuration
BSC Physical Configuration
E1 A Interface Connection
IP A Interface Connection
E1 Gb Interface Connection
IP Gb Interface Connection
Data Synchronization

Data Planning
Name

Meaning

Value

NSEI

NSE ID

IP_Gb

Real Interface IP of IPGB 172.28.5.7/24

board

IP_Gb_Virtual

Virtual IP of RPU for IP Gb

172.28.6.7

iBSC endpoint port

Local iBSC UDP port No.

32800

SGSN_IP

Virtual address of the remote 10.63.209.233

SGSN

SGSN endpoint port

Remote SGSN UDP port No.

GW_to_SGSN

Address of the gateway from 172.28.5.254

iBSC to the remote SGSN

Signal Weight
Data Weight

71

/
/

40007

10
10

Configuration Flow

Configuring Board

Set PLMN/SGSN Office

Create IP Gb Interface
The real address interface is on the
IPGB board.

The virtual address of the IP Gb interface

is on the RPU.

Create Static Route

Create NSE

Create IPGB Endpoint

This step guides you how to create IPGB
endpoint. In this example, NSE
Configuration Type is static. You need to
configure both local endpoint and remote
endpoint.

Contents

Overview
Global Resource Configuration
BSC Physical Configuration
E1 A Interface Connection
IP A Interface Connection
E1 Gb Interface Connection
IP Gb Interface Connection
Data Synchronization

Overview

OMCR configures iBSC data in the offline mode.

Therefore, after the data are configured, you need to send
the configured data to the foreground via data
synchronization.

Check Validity of Global Data

This step guides you how to check Validity of Global Data

to make sure that the data is correct and complies with the
standard.

Synchronize Data

Synchronize All Data : Uploads all tables under the config set.
Synchronize Modified Data : Uploads the changed tables under the
config set.