Sie sind auf Seite 1von 66

ZXG10 iBSC Configuration

Contents

Configuration flow
Public resource configuration
BSC physical configuration
A-interface configuration
Gb interface configuration

Configuration flow

Contents

Configuration flow
Public resource configuration
BSC physical configuration
A-interface configuration
Gb interface configuration

Public resource configuration


BSC

function

GERAN

subnetwork

Public resource

Config

set

BSC

managed element

Configuring GERAN subnetwork (1)

Configuring GERAN subnetwork (2)

Configuring BSC managed element (1)

Configuring BSC managed element (2)

Configuring config set (1)

Configuring config set (2)

Configuring BSC function (1)

Configuring BSC function (2)

Key parameters of BSC function

MCC,MNC
Support MNC 3 digits
OMP IP,OMP MAC
OMC sever IP,OMC subnet mask
OMCB IP
SNTP sever IP
Net type
Sp type
Bureau No
Support GE
Support TC type
DCS1800/PCS1900 supported

Contents

Configuration flow
Public resource configuration
BSC physical configuration
A-interface configuration
Gb interface configuration

BSC physical configuration


BSC rack configuration

BSC physical
configuration
Board configuration

Shelf configuration

Configuring BSC rack (1)

Configuring BSC rack (2)

Configuring BSC rack (3)

Category of iBSC shelf

Control shelf

Switch shelf

iBSCShelf

Resource shelf/Gigabit resource shelf

Configuring shelf (1)

Configuring shelf (2)

Configuring shelf (3)

Configuring boards (1)

Configuring boards (2)

Configuring boards (3)

Result

1. In control shelf, the


OMP board must be
configured first, then
the UIMC board, and
then other boards.
2. The SBCX board need
not be configured.
3. In resource shelf/gigabit
resource shelf, the
UIMU/GUIM board must
be configured first.

Contents

Configuration flow
Public resource configuration
BSC physical configuration
A-interface configuration
Gb interface configuration

Related boards of IP A-interface configuration

IPAB/IPI board

Interface board, which is responsible for IP packet


resolution.

AIPB board

User-plane processing board, which implements RTP


protocol processing.

Data planning of IP A-interface configuration

Local office and adjacent office


Signaling point code
Adjacent office properties
Sub-service field
Application server process

Protocol type
The local IP address and the opposite IP address
The local port number and the opposite port number
Application property

Application server

Supported adaptation-layer protocols


Service mode

IP A-interface configuration
1

Configuring
local office

Configuring
adjacent
office

Configuring
IP interface

Configuring
DHD
JGDJ
application
J
serverD process

Configuring
PLMN/MSC
office

Configuring
IP A-interface
service

Configuring
SIO

Configuring
DHD JGDJ
application
DJ
server

Configuring local office (1)

Configuring local office (2)

Configuring adjacent office

Configuring IP interface

1.Configuring

IPI interface
address

3.Configuring
staticroute

2.Configuring

RPU interface

Configuring IPI interface address (1)

Configuring IPI interface address (2)

Configuring RPU interface

Subnet mask is
255.255.255.255

Configuring static route

If the IP address (at most


four IP addresses can be
configured) of IPI interface
is in the different network
segment from that of iBSC
and MSC, it is necessary to
configure static route.
If no IP address of IPI
interface is in the different
network segment from that
of iBSC and MSC, it is not
necessary to configure
static route

Configuring application server process (1)

Configuring application server process (2)

ASP Basic Config tab

Module: The SCTP's home signaling module number.


Protocol type: For IP A, select M3UA.
Office ID: The opposite office ID of SCTP.
Property: It must match the property of MSC SERVER.
Local port: It must be consistent with the opposite port
number at MSC SERVER.
Remote port: It must be consistent with the local port
number at MSC SERVER.

IP Config tab

Local IP ADDR: RPU interface's IP address.


Remote IP ADDR: It must be consistent with the IP address
of MSC SERVER.

Configuring application server

Configuring application server

Protocol: Select M3UA.


Exist context: Select False.
Tag: For IP A, select IPSP.
Service mode: Usually, select Participate, that is,
multiple ASPs bear the service.
Mode N: It refers to the minimum number of
ASPs required for AS service in the participate
mode.
Mode K: It refers to the number of backup ASPs
in the participate mode.
ASP number: In the participate mode, ASP
number =Mode N + Mode K.

Configuring SIO

Configuring SIO

Office ID: It is necessary to configure SIO


information for all adjacent offices of
MSC SERVER.
OPC: Signaling point code of iBSC.
SIO: Select SCCP.
Application server ID: Set this parameter
according to planned data.

Configuring IP A-interface service (1)

Configuring IP A-interface service (2)

Configuring PLMN/MSC office (1)

Configuring PLMN/MSC office (2)

Configuring PLMN/MSC office (2)

NRI of MSC(NRI): Set this parameter with the


same value as NRI at the core network. If iBSC
does not support FLEX A, do not configure this
parameter.
Load allocate ratio of MSC: This parameter defines
theservice load ratio among multiple MSCs. For
example, if theservice load ratio of two MSCs are
2 and 3, then it indicatesthat the load ratio
between the two MSCs is 2:3. If iBSC does not
support FLEX A, do no configure this
parameters.
Selected number: This parameter is related to
multi-signaling point function. When the multisignaling-point function is enabled, this
parameter's value can not be zero.

Configuring PLMN/MSC office (3)

Configuring PLMN/MSC office (3)

MCC
MNC
Length of MSC NRI: Set this parameter with the
same value as that at CN. If iBSC does not
support FLEX A, do no configure this parameter.
MSC NULL-NRI ID: Set this parameter with the
same value as that at CN. If iBSC does not
support FLEX A, do not configure this parameter.
MSC version ID: Set this parameter with the same
value as that at CN.
MSC CN ID: Set this parameter with the same
value as that at CN. If iBSC does not support
FLEX A, do not configure this parameter.

Contents

Configuration flow
Public resource configuration
BSC physical configuration
A-interface configuration
Gb interface configuration

Related boards of IP Gb interface configuration

IPGB board

It is used for IP Gb interface access and data issuing at


control plane and user plane.

UPPB board

It is used for service data processing.

Data planning of IP Gb interface configuration

NSE ID
IP address and UDP port number of IPGB's local endpoint
Signaling weight
Data weight
For static NSE configuration

IP address and UDP port number of IPGB's remote endpoint


Signaling weight
Data weight

For dynamic NSE configuration

Pre-configured SGSN IP address


Pre-configured SGSN UDP port number

IP Gb interface configuration

2.Configuring NSE

IP Gb
interface
configuration

3.Configuring IPGB endpoint,


including local endpoint and
remote endpoint

1.Configuring IP interface
The configuration steps of IP
interface (IP Gb) is same as
that of IP A

Configuring NSE (1)

Configuring NSE (2)

Configuring NSE (2)

NSE ID: It must be consistent with that at SGSN.


Type of sub-network: For IP Gb, select IP.
Configure type: There are two configuration modes:
Static and Dynamic.

Static configuration is used for point-to-point private network.


Manual negotiation between iBSC and SGSN is required, that
is, configuring the combination of NSVC's endpoints
manually.

Pre-configured SGSN IP address: IP address of


SGSN.This parameter must be configured for dynamic
configuration.
Pre-configured SGSN UDP port: UDP port of SGSN. This
parameter must be configured for dynamic
configuration.

Configuring IPGB local endpoint (1)

Configuring IPGB local endpoint (2)

Configuring IPGB local endpoint (2)

IP address: The virtual address of RPU of iBSC.


It must be the same as that at SGSN.
UDP port: It must be the same as that at SGSN.
Endpoint type: Select Local endpoint.
Signal weight: It must be the same as that at
SGSN.
Data weight: It must be the same as that at
SGSN.

Configuring IPGB remote endpoint (1)

The remote endpoint


is only configured
when NSE adopts the
static configuration.

Configuring IPGB remote endpoint (2)

Configuring IPGB remote endpoint (2)

IP address: The virtual address of SGSN. It must


be the same as that at SGSN.
UDP port: It must be the same as that at SGSN.
Endpoint type: Select Remote endpoint.
Signal weight: It must be the same as that at
SGSN.
Data weight: It must be the same as that at
SGSN.