01 gb_oc42_e1_0 zxg10 ibsc configuration(v6.20.614c) 82

8/22/2019 01 GB_OC42_E1_0 ZXG10 iBSC Configuration(V6.20.614c) 82

http://slidepdf.com/reader/full/01-gboc42e10-zxg10-ibsc-configurationv620614c-82 1/78

ZXG10 iBSC Configuration

Course Objectives:

·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

Course Prerequisites:

·Has finished ZXG10 iBSC Structure and Principle

·Familiar with hardware structure and operating principles of iBSC



Contents

1Overview.........................................................................................................................................................1

2Global Resource Configuration....................................................................................................................7

3BSC Physical Configuration.......................................................................................................................13

E1 A Interface Connection............................................................................................................................17

IP A Interface Connection.............................................................................................................................33

E1 Gb Interface Connection.........................................................................................................................55

IP Gb Interface Connection..........................................................................................................................63

Data Synchronization....................................................................................................................................75

i



1 Overview

Configuration management enables user to manage resource data and status, and

provides various data configurations to support normal system running. It determines

the running mode and status of ZXG10 BSS.

Data configuration means establishing the relationship between the network

management system and network elements such as BSC and BTS. It enables user to

perform parameter setting for management objects in BSS.

1.1 Configuration Management of OMCR

Select View > Configuration Management to enter the configuration management

interface, as shown in Figure 1.1 -1.

Figure 1.1-1 Configuration Management Interface

Figure 1.1 -2 shows the layout of the configuration management interface.

1



Figure 1.1-2 Configuration Management Interface Layout

The following describes the functions of the configuration resource tree.

· User can view configured elements in the configuration resource tree.

· User can open the configuration management element attribute tab by double-

clicking the corresponding management element in the configuration resource

tree.

· User can perform various operations by right-clicking on corresponding

management element in the configuration resource tree.

Table 1.1 -1shows the meanings of the buttons in the configuration management tool bar.

Table 1.1-1 Configuration Management Tool Bar Button

2



Chapter 7 IP Gb Interface Connection

Table 1.1 -2describes the meanings of the buttons in the configuration management

element tool bar.

Table 1.1-2 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.

1.2 Configuration Flow

Figure 1.2 -3 shows the configuration flow of iBSC.

3



GB_OC42_E1_0 ZXG10 iBSC Configuration

Figure 1.2-3 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

4




(MCC), MNC (MNC), and OMP IP (OMP_IP).

BSC Physical Configuration

Configure racks, boards, and cable connection of BSC.

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.

1.3 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

5




to avoid the influence of incorrect data on the system running.

6



2 Global Resource Configuration


Figure 2.1 -4shows the flow of Global Resource Configuration.

Figure 2.1-4 Global Resource Configuration Flow

1.5 Create GERAN Subnetwork

[Purpose]

This operation guide guides you how to create a GERAN subnetwork.

7



[Steps]

1．

In the resource tree, right-click the root node, and then select Create > GERANSubnetwork from the shortcut menu. Then fill in configuration data in the pop-

up dialog box, as shown in Figure 2.2 -5.


[Parameter Description]

Subnetwork ID: the ID of GERAN Subnetwork is globally unique.

1.6 Create BSC Managed Element

[Purpose]

This operation guide guides you how to create a BSC Managed Element.

[Steps]

1． In the resource tree, right-click GERAN Subnetwork38, and then select Create

> BSC Managed Element from the shortcut menu. Then fill in configuration

data in the pop-up dialog box, as shown in Figure 2.3 -6.

8






Managed element IP address: Type OMP_IP.

1.7 Apply Mutex Right

[Purpose]

Through this operation, you can apply for an operation right for a BSC managed

element.

[Context]

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

[Steps]

1． In the resource tree, right-click BSC Managed Element, and then select Apply

Mutex Right from the shortcut menu. Select YES from the pop-up confirmation

box.

9




1.8 Create Config Set

[Purpose]

This operation guide guides you how to create a Config Set.

[Context]

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.

[Steps]

1． In the resource tree, right-click BSC Managed Element, and then select Create

> Config Set from the shortcut menu. Then fill in configuration data in the pop-

up dialog box.

Tip:

How to switch a Config Set to the active one?

Select the created Config Set, and then click in the CM Element tool bar.

1.9 Create BSC Function

[Purpose]

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.

[Steps]

1． In the resource tree, right-click BSC Managed Element > Config Set, and then

select Create > BSC Function from the shortcut menu. Then fill in

configuration data in the pop-up dialog box.

10






1． MCC(MCC): Mobile Country Code (MCC) is used to uniquely identify the

home country of the mobile users (or system)

2． Support the maximum length of MNC (MNC3Digits): For mobile network code,

the user can select if supporting 2 or 3 digits MNC, which is not modifiable on

creation.

3． MNC(MNC): Mobile Network Code (MNC) uniquely identifies a specific

PLMN network in a country (decided by MCC).

4． OMP IP(OMP_IP): This parameter specifies the IP address of IPv4 of OMP for

communicating with the background. This parameter must be consistent with IP

configuration of the OMP board. Type OMP_IP.

5． OMP MAC(OMP_MAC): If 0 is filled in, MAC address for OMP is generated

11




based on default foreground rule.

6．

OMC subnet mask(Info4): It is the subnet mask of the OMP IP address.

7． OMC gateway(Info5): Infor5 is the IP address of gateway from OMP to

iOMCR. This parameter can be kept unchanged, default value is ok.

8． OMC server IP(Info6): Info6 is defined by user and set according to network

configuration. Info6 is the IP address that iOMCR uses to setup link with OMP.

Type OMCR_IP.

9． OMCB IP(OMCB): When site connected with BSC is SDR, user shall configure

it. When creating a base station, fill in this IP.

10． Bureau No.(BureauNo): It is defined by the customer and set according to the

network configuration, keeping different in whole topology tree,

11． GE support(GESupport): Select YES.

12



3 BSC Physical Configuration


Figure 3.1 -8 shows the flow of BSC Physical Configuration.

Figure 3.1-8 BSC Physical Configuration Flow

1.11 Create BSC Rack

[Purpose]

This operation guide guides you how to create a BSC rack.

[Steps]

1． In the resource tree, right-click BSC Managed Element > Config Set > BSC

Function > BSC Device Config, and then select Create > BSC Rack from the

shortcut menu. The dialog box shown in Figure 3.2 -9. Click OK.

13



Figure 3.2-9 Create BSC Rack

1.12 Create BSC Shelf

[Purpose]

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

BSC must be 2nd shelf.

[Steps]

1． In the resource tree．select BSC Managed Element > Config Set > BSC Function

> BSC Device Config > BSC Rack1. The BSC rack diagram appears.

2． Right-click 2nd shelf in the BSC rack diagram, and then select Create Shelf from

the shortcut menu. Create a control shelf, as shown in Figure 3.3 -10.

Figure 3.3-10 Create BSC Control Shelf

14




3． Create GE resource shelf in 1st shelf and 3rd shelf in the same way.

4．

Create Switch Shelf in 4th shelf in the same way.

1.13 Create BSC Board

[Purpose]

This operation guide guides you how to create a BSC board.

To create BSC boards, you must obey the following rules:

1． Create the OMP obard of the control shelf first.

2． Before creating service boards, create UIM boards for each shelf.

3． The created boards must exist on the BSC rack and the models must be correct.

[Steps]


> BSC Device Config > BSC Rack1. The BSC rack diagram appears.

2． Create boards in the corresponding slots in the rack diagram based on the

physical configuration of the BSC.

[Board Property]

1． Set Ethernet channel mode of IPI/IPGB/IPBB. Select a GE port according to

data planning. Select Channel mode 3, as shown Figure 3.4 -11.

Figure 3.4-11 Set the channel mode

2． Set PCM information of DTB/SDTB according to data planning, as shown in

Figure 3.4 -12.

15




Figure 3.4-12 Set SDTB PCM information

3． Set User Plane fiber connection, as shown in Figure 3.4 -13.

Figure 3.4-13 Set User Plane fiber connection

16



E1 A Interface Connection

1.14 Overview

1.14.1 A Interface Networking

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

and MSCServer, as shown in Figure 4.1 -14.

Figure 4.1-14 A interface networking 1

Since MSCServer is responsible for dealing with call services, the signaling of

BSC needs to be sent to the MSCServer. In this networking mode, the interfaces

between MGW and MSCServer use SS7. As the STP, MGW forwards the

signaling of iBSC to MSCServer.

Data Configuration Methods

1． Configure two adjacent offices. iBSC is associated with MGW and quasi-

associated with the MSC server.

2． iBSC is associated with MGW. Configure signaling links under MGW.

3． Logically the PCM circuit between iBSC and CN is managed by the MSC

server. Threfore, N7PCM should be configured under MSC Server.

4． You need to configure to signaling office routes. One is to MGW and the other is

to the MSC server.

5． There is no service signaling between iBSC and MGW. Therefore, there is no

need to configure the subsystem 254 (BSSAP) under MGW.

2． iBSC is associated with MGW only. CN provides the MGW signaling point, as

17



shown in Figure 4.1 -15.


In this networking mode, MGW sends the signaling of iBSC to the MSC server

using IP (SIGTRAN) through the MC interface. iBSC ignores signaling forward

from MGW to the MSC server. Therefore, logically MGW and the MSC server

is an entity. Data configuration of iBSC is exactly the same with that for 2G

MSC interconnection.

Data Configuration Methods

1． Regard MGW and the MSC server as an entity. Configure one adjacent office.

2． Configure Mc interface between MGW and the MSC so that the signaling can be

automatically forwarded.

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

the MSCServer signaling point, as shown in Figure 4.1 -16.


In this networking mode, iBSC is connected with MGW and the MSC server

respectively. Since call processing is separated from bearing in 3G CN, the

signaling link connects to the MSC server, while the call relay connects to

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

18




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. In actual configuration, the number of N7PCM (the

trunk circuit to MGW) starts from 0 or 1 after negotiation with CN. The trunk

circuit to the MSC server adopts a larger N7PCM number, 512 for instance.

1.14.2 Data Planning

Table 4.1 -3 shows describes the interconnection data.

Table 4.1-3 Data Planning of E1 A Connection

Name Meaning Value

MSC Signaling Point / N/A

MGW Signaling Point / 2.200.1

BSC Signaling Point / 2.200.7

AMConnection relationship between

MGW and BSCAM Sure

SSF Sub-Service Field Signal code

SPC Type Signaling Point Code Type SPC 14

No.7 PCM N7PCM number of A interface0,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 No.7 Signaling link code 7

Link error calibration method / Basic

E1 Frame mode / Double frame

1.14.3 Configuration Flow

Figure 4.1 -17 shows the flow of E1 A Interface Connection.

19




Figure 4.1-17 E1 A Interface Connection Flow

20




1.15 Configuring Board

[Purpose]

This operation guide guides you how to configure or query boards of the E1 A interface

unit.

[Steps]

1． Query the PCM Information of SDTB2 Board. Right-click the SDTB2

board．select Board Property．as shown in Figure 4.2 -18.

Figure 4.2-18 Query SDTB2

2． Query if the SPB2 board has been created.

3． Query the DSP Configuration Information of SDTB2 board．as shown in Figure

4.2 -19.

21




Figure 4.2-19 Query DRTB2

1.16 Create Local Office

[Purpose]

For the BSC, local office is itself. This operation guide guides you how to create a BSC

signaling point and other related properties.

[Steps]


Function > Office Relate Config, and then select Create > Local Office from

the shortcut menu. The dialog box shown in Figure 4.3 -20. Click OK.

22




Figure 4.3-20 Create Local Office


1． No.7 type: In the case of E1 bearing, select Narrow band.

2． OPC (14 bits): Type the Signalling point code of BSC.

Note．

After the local office is created, Local No.7 SSN is automatically created.

1.17 Create Adjacent Office

[Purpose]

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.

[Steps]

1． In the resource tree ． select BSC Managed Element > Config Set > BSC

Function > Office Relate Config > iBS38. The configuration interface appears.

2．

In the Adjacent Office tab page, click the button. Fill in configuration

23




parameters in the pop-up dialog box, as shown in Figure 4.4 -21.

Figure 4.4-21 Create Adjacent Office


1． Office type: Select MGW according to data planning.

2． SPT type: SEP indicates the signaling-end node. STP indicates the signaling

forward node. SETP indicates the signaling forward node or signaling-end node.

3． SSF : Its configuration needs to be consistent with that at the CN side.

4． DPC : Signalling point code of the adjacent office.

Note．

After the adjacent office is created, Adjacent No.7 SSN is automatically created.

1.18 Create No.7 PCM

[Purpose]

This example guides you how to create No.7 PCM to an adjacent office.

24




[Steps]

1．

In the resource tree．

double click BSC Managed Element > Config Set > BSCFunction > Office Relate Config > iBS38. The configuration interface appears.

2． In the No.7 PCM tab page, click the button. Fill in configuration parameters

in the pop-up dialog box, as shown in Figure 4.5 -22.

Figure 4.5-22 Create No.7 PCM


1． Office ID: Select the office ID of MGW.

2． Unit: Select the Rack /Shelf/Slot No. of the corresponding SDTB.

3． No.7 PCM : The N7PCM number must be consistent with that at the CN side.

1.19 Create No.7 Link Set

[Purpose]

This example guides you how to create a singling link group. The total of two signaling

link groups from iBSC to an adjacent office can be created.

[Steps]

25




1． In the resource tree．double click BSC Managed Element > Config Set > BSC


2． In the No.7 Link Set tab page, click the button. Fill in configuration


Figure 4.6-23 Create No.7 Link Set



2． Link error calibration method : Select Basic according to data planning. This

parameter must be consistent with that at the CN side.

3． Type of signaling link set : Select 64K link group according to data planning.

This parameter must be consistent with that at the CN side.

1.20 Create No.7 Link

[Purpose]

This example guides you how to create a singling link. Each signaling link must belong

to a signaling link set.

[Steps]


> Office Relate Config > iBS38. The configuration interface appears.

2． In the No.7 Link Set tab page, click the button. Fill in configuration


26




Figure 4.7-24 Create No.7 Link


1． Link set: Select No.7 Link Set which this No.7 link belong to.

2． PCM: PCM where the NO.7 link is located.

3． Start TS : Time slot where the NO.7 link is located at the PCM.

4． SMP module : The module number of the home CMP module which the No.7

link belongs to.

5． Link code SLC : Set link code. Currently, the user can configure up to 16 links

to a office. The signaling link codes (SLC) for these links shall be different.

Regardless of these 16 links distributed into one or two link sets, it shall meet

above restrictions.

1.21 Create No.7 Route

[Purpose]

This example guides you how to create a singling route. Each signaling route can

belong to one or two link sets.

27




[Steps]

1．

In the resource tree．

select BSC Managed Element > Config Set > BSC Function> Office Relate Config > iBS38. The configuration interface appears.

2． In the No.7 Route tab page, click the button. Fill in configuration parameters


Figure 4.8-25 Create No.7 Route


1． Link set 1: Select the link set which the No.7 Route belongs to.

1.22 Create No.7 Office

[Purpose]

This example guides you how to create a singling office. Each office can use up to four

No.7 routes.

[Steps]


> Office Relate Config > iBS38. The configuration interface appears.

2． In the No.7 Office tab page, click the button. Fill in configuration


28




Figure 4.9-26 Create No.7 Route



2． Route 1: 0 represents invalid, no any router associated. Multiple signaling router

under signaling office has the active/standby relationship.

1.23 Set PLMN/MSC Office

[Purpose]

This operation guide guides how to add carrier information.

[Steps]


Function, and then select Set PLMN/MSC Office/SGSN Office/RNC Office

from the shortcut menu, as shown in Figure 4.10 -27.

29




Figure 4.10-27 Set PLMN/MSC Office

2． Select the MSC Office tab page to set the MSC information. Click Add, as


Figure 4.10-28 Add MSC Office

30





1．

NRI of MSC: NRI ID, each iBSC can be configured with 16 adjacent MSCoffices at most, and each adjacent MSC office has a NRI ID. It is consistent with

the configuration data at CN side.

2． Load allocate ratio of MSC: It is the load allocation ratio of MSC. While

configuring each adjacent MSC office, the user shall configure load allocation

ratio for this MSC; it is used to select MSC for unknown NRI and NULL-NRI

by iBSC. This parameter is consistent with the data at CN side.

3． Office ID : Office ID of signaling point. For the message sent to a MSC, iBSC is

responsible for selecting a signaling point office as the target IP address under

this MSC. In the dropdown list box, user can only select adjacent office

(signaling point) under this MSC NE.

4． A Interface Type : Select it as required.

3． Select the PLMN tab page, and then select the BSC that is automatically created.

Update the configuration parameters. Click Modify, as shown in Figure 4.10

-29.

Figure 4.10-29 Modify PLMN


1． Length of MSC NRI: It indicates how many bits are composed of NRI

31




parameter in TMSI or PTMSI. If iBSC belongs to multiple MSC Pools, the

MSC Pools that have an overlapping area must have the same NRI range and

NRI length; consistent with that at CN side.

2． MSC NULL-NRI ID: If MSC is overloaded, this parameter can be allocated to a

MS. It indicates iBSC can select another MSC to access while the MS accesses

at the next time; it shall be consistent with that at CN side.

3． MSC version ID : It is used to identify version number of MSC; consistent with

that at CN side.

4． MSC ID : Only effective at iBSC side; FlexA allows iBSC to connect up to 16

MSCs

5． MSC CN ID : While configuring each adjacent MSC office, configure GLOBAL

CN ID for this MSC. This value shall be assigned to MSC by the operator;

consistent with that at CN side.

32



IP A Interface Connection

1.24 Overview


Table 5.1 -4 describes the interconnection data.

Table 5.1-4 Data Planning of IP A Connection

Name Meaning Value

MSC Signaling Point / 2.253.1

MGW Signaling Point / N/A

BSC Signaling Point / 2.7.1

AMConnection 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 Ainterface on the control plane

172.28.1.7

IPI_UPReal interface of iBSC A

interface on the user plane172.28.3.7

CS_CPControl plane virtual address of

iBSC A interface172.28.2.7

CS_UPUser plane virtual address of

iBSC A interface172.28.4.7

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_MGWGateway from iBSC to the virtual

address of MGW172.28.3.254

ASP Protocol Type / M3UA

ASP Property / Server

ASP Local Port / 3007

ASP Remote Port / 3007

AS Service Mode / Participate

33




Figure 5.1 -30shows the flow of E1 A Interface Connection.

Figure 5.1-30 IP A Interface Connection Flow

34





[Purpose]

This operation guide guides you how to configure or query boards of the IP A interface

unit.

[Steps]

1． Query basic information of the IPI board. Right-click the IPI board, and then

select Board Property from the shortcut menu, as shown in Figure 5.2 -31.

Figure 5.2-31 Query IPI

2． Set DSP Configuration Information of AIPB, as shown in Figure 5.2 -32.

35




Figure 5.2-32 Set AIPB

1.26 Create IP A Interface

When interface A uses IP bearing, you need to configure the real and virtual addresses

of the control and user planes.

1.26.1 Create Real Interface IP

[Purpose]

The real address interface is on the IPI board. This operation guide guides you how to

create the real address of the IPI board.

[Steps]

1． In the resource tree ． select BSC Managed Element > Config Set > BSC

Function > IP Related Config. The configuration interface appears, as shownin Figure 5.3 -33.

Figure 5.3-33 IP Related Config

36




2． Create IP A interface control plane real IP. In the Interface tab page, click the

button. Fill in configuration parameters in the pop-up dialog box, as shown

in Figure 5.3 -34.

Figure 5.3-34 Create IP A Interface Control Plane Real IP

3． Create IP A interface user plane real IP in the same way, as shown in Figure 5.3

-35.

37




Figure 5.3-35 Create IP A Interface User Plane Real IP


1． Board function type: A interface board is IPI．

2． Subsystem:module:unit:sunit: Select the board or module on which the IP

address is to be created.

3． MAC address: MAC address must be in the range of [00-D0-D0-A0-00-00, 00-

D0-D0-A0-9F-FF] or [00-19-C6-3E-30-10, 00-19-C6-4E-30-0F].

4． IP address/Subnet mask : Fill in the address of IPI_CP or IPI_UP.

1.26.2 Create Virtual Interface IP

[Purpose]

The virtual address of IP A interface is on the RPU. This operation guide guides you

how to create the virtual address of the RPU.

[Steps]

1． In the resource tree, select BSC Managed Element > Config Set > BSC

Function > IP Related Config. The configuration interface appears, as shown

in Figure 5.3 -36.

38





2． Create IP A interface control plane virtual IP. In the Interface tab page, click

the button. Fill in configuration parameters in the pop-up dialog box, as


Figure 5.3-37 Create IP A interface Control Plane Virtual IP.

3． Create IP A interface user plane virtual IP in the same way, as shown in Figure

5.3 -38.

39




Figure 5.3-38 Create IP A Interface User Plane Virtual IP


1． Board function type: Virtual IP is created on the RPU.

2． Subsystem:module:unit:sunit: Select the board or module on which the IP

address is to be created.

3． Port No.: The port number of an RPU must be unique.

4． IP address : Fill in the address of CS_CP or CS_UP according to data planning.

5． Subnet mask : The subnet mask of virtual IP is set to “255.255.255.255”.

4． Create SMP Virtual IP. In the Interface tab page, click the button. Fill in

configuration parameters in the pop-up dialog box, as shown in Figure 5.3 -39.

Note．

IP A services are required to correspond to SMP, so it is necessary to crate the virtualaddress of the SMP, which must be consistent with Virtual IP(CS_CP).

40




Figure 5.3-39 Create SMP Virtual IP


1． Board function type: Select SMP.

2． Subsystem:module:unit:sunit: Select the number of the SMP module to be

created.

3． Port No.: Port No. of SMP is 65530 by default.

4． IP address/Subnet mask : It is set to Control Plane Virtual IP(CS_CP).

1.27 Create Static Route

[Purpose]

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

the CN.

[Steps]

1． In the resource tree, double click BSC Managed Element > Config Set > BSC

Function > IP Related Config. The configuration interface shown in Figure

5.4 -40.

41





2． Create static route to MSC. In the Static Route tab page, click the button.

Fill in configuration parameters in the pop-up dialog box, as shown in Figure

5.4 -41.

Figure 5.4-41 Create static route to MSC

3． Create a static route to MGW in the same way, as shown in Figure 5.4 -42.

42




Figure 5.4-42 Create static route to MGW


1． Static route prefix: Indicates the network segment of the destination network.

Fill in IP address prefix of MSC_Virtual into Static route prefix of the control

plane and IP address prefix of MGW_Virtual into Static route prefix of the user

plane.

2． Next hop type: Select IP.

3． Next hop IP address : When next hop type is IP, the user can set this IP address.

This indicates all messages at target network segment, which is confirmed by

static route prefix and subnetmask, are sent to this IP address. Fill in

GW_to_MSC into Next hop IP address of the user plane. Fill in GW_to_MGW

into Next hop IP address of the control plane.

1.28 Create Local Office

[Purpose]

For the BSC, local office is itself. This operation guide guides you how to create a BSC

signaling point and other related properties.

43




[Steps]

1．

In the resource tree, BSC Managed Element > Config Set > BSC Function >Office Relate Config, and then select Create > Local Office from the shortcut

menu. The dialog box shown in Figure 5.5 -43. Click OK.

Figure 5.5-43 Create Local Office


1． No.7 type: In the case of IP bearing, select IP.

2． OPC (14 bits): Type the Signalling point code of BSC.

Note．

After the local office is created, Local No.7 SSN is automatically created.

1.29 Create Adjacent Office

[Purpose]

This operation guide guides you how to create an Adjacent Office ． In the case of IP

bearing, CN provides the singaling point of the MSC server of the adjacent office.

44




[Steps]

1．

In the resource tree, double click BSC Managed Element > Config Set > BSCFunction > Office Relate Config > iBS38. The configuration interface appears.

2． In the Adjacent Office tab page, click the button. Fill in configuration


Figure 5.6-44 Create Adjacent Office


1． Office type: Select MSC server according to data planning.

2． SPT type: SEP indicates the signaling-end node. STP indicates the signaling

forward node. SETP indicates the signaling forward node or signaling-end node.

3． SSF : Its configuration needs to be consistent with that at the CN side.

4． DPC : Adjacent Office． signalling point code.

Note．

After the adjacent office is created, Adjacent No.7 SSN is automatically created.

45




1.30 Create ASP

[Purpose]

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.

[Steps]



2．

In the ASP tab page, click the button. Fill in configuration parameters in the pop-up dialog box, as shown in Figure 5.7 -45.

Figure 5.7-45 Create ASP Basic Config

46




Figure 5.7-46 Create ASP IP Config


1． ASP ID: Fill in an ASP number, which starts from 1 normally.

2． SCTP ID: SCTP ID that corresponds to ASP. ASP corresponds to SCTP one by

one.

3． Module: Select the number of the home CMP module.

4． Office ID: Select the office ID of the MSC server.

5． Property: The application property of SCTP. For SCTP, one side is client, the

other is server, and the SCTP connection is initiated from client.

6． Protocol type: Select M3UA.

7． Local port/Remote port: SCTP port number. Local port indicates the BSC side,

while Remote port indicates the CN side.

8． Local IP address 1: It is one of IP adresses at SMP virtual port. For SCTP, an

association can own multiple IP addresses, currently 4 to the max extent. Input

IP address of CS_CP here.

9． Remote IP address1: Input IP address of MSC_Virtual provided by the CN side.

1.31 Create AS

[Purpose]

47




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.

[Steps]



2． In the AS tab page, click the button. Fill in configuration parameters in the

pop-up dialog box, as shown in Figure 5.8 -47.

Figure 5.8-47 Create AS Basic Config

Figure 5.8-48 Create ASP ID for AS


48




1． Application server ID: It starts from 1.

2．

Protocol: Select M3UA.

3． Tag: Configure ASP as the server. Select IPS_Server so that the setting is

consistent with ASP.

4． Server Mode : Select Participate so that the setting is consistent with CN.

5． ASP ID : Select ASP ID used by this AS.

1.32 Create SIO

[Purpose]

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

[Steps]


Function > Office Relate Config > iBS38. The configuration interface appeas.

2． In the SIO tab page, click the button. Fill in configuration parameters in the

pop-up dialog box, as shown in Figure 5.9 -49.

Figure 5.9-49 Create SIO


1．

Office ID: Select the office ID of the MSC server.

49




2． OPC: Select BSC Signaling Point Code.

3．

SIO : Select SCCP.

4． Application server ID : Select AS used by this SIO.

5． Tag : PCM is invalid value

1.33 Create User Plane Service

[Purpose]

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

virtual address of the user plane.

[Steps]


Function > BSC Device Config. The Rack Configure interface appears.

2． Right click the AIPB board, and then select Set IP Port from the shortcut menu,

as shown in Figure 5.10 -50.

Figure 5.10-50 Set IP Port

3． Set the IP port and the virtual IP address of the user plane, as shown in Figure

5.10 -51.

50




Figure 5.10-51 Create User Plane Service


1． IP address: Select IP address of CS_UP.

2． Subunit: Indicates the DSP number on the AIPB.

3． Start number of port : The start number of port interval of each SDP is 1200.

1.34 Set PLMN/MSC Office

[Purpose]


[Steps]



51





Figure 5.11-52 Set PLMN/MSC Office

2． Select the MSC Office tab page to set the MSC information. Click Add, as


52




Figure 5.11-53 Add MSC Office


1． NRI of MSC: NRI ID, each iBSC can be configured with 16 adjacent MSC

offices at most, and each adjacent MSC office has a NRI ID. It is consistent with

the configuration data at CN side.

2． Load allocate ratio of MSC: It is the load allocation ratio of MSC. While

configuring each adjacent MSC office, the user shall configure load allocation

ratio for this MSC; it is used to select MSC for unknown NRI and NULL-NRI

by iBSC. This parameter is consistent with the data at CN side.

3． Office ID : Office ID of signaling point. For the message sent to a MSC, iBSC is

responsible for selecting a signaling point office as the target IP address under

this MSC. In the dropdown list box, user can only select adjacent office

(signaling point) under this MSC NE.

4． A Interface Type : Select it as required.


Update the configuration parameters. Click Modify, as shown in Figure 5.11

-54.


53





1．

Length of MSC NRI: It indicates how many bits are composed of NRI parameter in TMSI or PTMSI. If iBSC belongs to multiple MSC Pools, the

MSC Pools that have an overlapping area must have the same NRI range and

NRI length; consistent with that at CN side.

2． MSC NULL-NRI ID: If MSC is overloaded, this parameter can be allocated to a

MS. It indicates iBSC can select another MSC to access while the MS accesses

at the next time; it shall be consistent with that at CN side.

3． MSC version ID : It is used to identify version number of MSC; consistent with

that at CN side.

4． MSC ID : Only effective at iBSC side; FlexA allows iBSC to connect up to 16

MSCs

5． MSC CN ID : While configuring each adjacent MSC office, configure GLOBAL

CN ID for this MSC. This value shall be assigned to MSC by the operator;

consistent with that at CN side.

54



E1 Gb Interface Connection

1.35 Overview


Table 6.1 -5describes the interconnection data.

Table 6.1-5 Data Planning of E1 Gb Connection

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


Figure 6.1 -55shows the flow of E1 Gb Interface Connection.

55



Figure 6.1-55 E1 Gb Interface Connection Flow


[Purpose]

This operation guide guides you how to configure or query boards of the E1 Gb

interface unit.

[Steps]

1． Set PCM Information of the GIPB2 board. Right-click the GIPB2 board, and

then select Board Property from the shortcut menu, as shown in Figure 6.2 -56.

56




Figure 6.2-56 Set GIPB2

2． Set DSP Configuration Information of UPPB2, as shown in Figure 6.2 -57.

Figure 6.2-57 Set UPPB2

1.37 Set PLMN/SGSN Office

[Purpose]


[Steps]



57





Figure 6.3-58 Set PLMN/SGSN Office

2． Select the SGSN Office tab page, and then input the configuration parameters,


Figure 6.3-59 Set SGSN Office


1． SGSN ID :only effective at iBSC side; Flex Gb allows iBSC to connect up to 16

SGSNs.

58




2． NRI of SGSN : Each adjacent SGSN office has a NRI ID; consistent with that

at CN side.


Update the configuration parameters. Click Modify, as shown in Figure 6.3 -60.



1． Length of SGSN NRI : Length of SGSN NRI. It shall be consistent with that at

CN side on configuration. Type 255 if the Flex Gb is not support.

2． SGSN version ID : It is used to identify version number of SGSN; consistent

with that at CN side.

3．

SGSN ID : Only effective at iBSC side; FlexGb allows iBSC to connect up to 16SGSNs.

4． SGSN CN ID: While configuring each adjacent SGSN office, configure

GLOBAL CN ID for this SGSN. This value shall be assigned to SGSN by the

operator; consistent with that at CN side.

1.38 Create NSE

[Purpose]

59




This step guides you how to create NSE of E1 Gb interface.

[Steps]


Function > Gb Interface Relate Config > SGSN Office1 > NSE Config, and

then select Create > NSE from the shortcut menu. Then fill in configuration

data in the pop-up dialog box.

Figure 6.4-61 Create NSE


1． NSE ID : It must be consistent with that at the CN side.

2． Subnetwork type : In the case of E1 bearing, select frame relay. In the case of IP

bearing, select IP.

1.39 Create BRCH

[Purpose]

This step guides you how to create BRCH.

[Steps]


Function > Gb Interface Relate Config > BRCH Config , and then select

60




Create > BRCH from the shortcut menu. Then fill in configuration data in the

pop-up dialog box.

Figure 6.5-62 Create BRCH


1． Unit: Select Slot/Shelf/Rack of GIPB2.

2． CPU ID : CPU1 manages PCM9 ~ PCM12; CPU2 manages PCM13 ~ PCM16;

CPU3 manages PCM17 ~ PCM20; CPU4 manages PCM21 ~ PCM24.

3． Channel : This parameter is an internal logical link ID for CPU.

4． MCC start TS : Start timeslot number that corresponds to MCC interface at

signaling link. At present, one CPU has two MCCs and each MCC has 128

timeslots. Only the MCC channel numbered 2 is used. Note: Different bearer

channels cannot occupy the same MCC timeslot.

5． PCM No. : PCM number of the GIPB board in use.

6． PCM TS : This parameter defines the starting timeslot number of PCM that the

link accesses.

7． Access rate: the number of consecutive timeslots beginning from the start

timeslot.

61




1.40 Create NSVC

[Purpose]

This step guides you how to create NSVC.

[Steps]


Function > Gb Interface Relate Config > SGSN Office1 > NSE Config >

NSE70, and then select Create > NSVC from the shortcut menu. Then fill in

configuration data in the pop-up dialog box, as shown in Figure 6.6 -63.

Figure 6.6-63 Create NSVC


1． NSVC ID: This parameter should be consistent with that at CN side.

2． DLCI : DLCI shall be consistent with that at CN side, which is a planning value.

DLCI on a BRCH cannot be repeated.

3． BRCH link: Identify BRCH at GB interface. Each BRCH can set 5 NSVCs to

the max extent.

62



IP Gb Interface Connection

1.41 Overview


Table 7.1 -6describes the interconnection data.

Table 7.1-6 Data Planning of IP Gb Connection

Name Meaning Value

NSEI NSE ID 71

IP_Gb Real Interface IP of IPGB board 172.28.5.7/24

IP_Gb_Virtual Virtual IP of RPU for IP Gb 172.28.6.7

iBSC endpoint port Local iBSC UDP port No. 32800

SGSN_IPVirtual address of the remote

SGSN10.63.209.233

SGSN endpoint port Remote SGSN UDP port No. 40007

GW_to_SGSN Address of the gateway fromiBSC to the remote SGSN

172.28.5.254

Signal Weight / 10

Data Weight / 10


Figure 7.1 -64shows the flow of IP Gb Interface Connection.

63



Figure 7.1-64 IP Gb Interface Connection Flow


[Purpose]

This operation guide guides you how to configure or query boards of the E1 Gb

interface unit.

[Steps]

1． Query basic information of the IPGB board. Right-click the IPGB board, and

then select Board Property from the shortcut menu, as shown in Figure 7.2 -65.

64




Figure 7.2-65 Query IPGB

2． Set DSP Configuration Information of UPPB2, as shown in Figure 7.2 -66.

Figure 7.2-66 Set UPPB2

1.43 Set PLMN/SGSN Office

[Purpose]


[Steps]


65






Figure 7.3-67 Set PLMN/SGSN Office

2． Select the SGSN Office tab page, and then input the configuration parameters,


Figure 7.3-68 Set SGSN Office


1． SGSN ID :only effective at iBSC side; Flex Gb allows iBSC to connect up to 16

66




SGSNs.

2．

NRI of SGSN : Each adjacent SGSN office has a NRI ID; consistent with that atCN side.


Update the configuration parameters. Click Modify, as shown in Figure 7.3 -69.



1． Length of SGSN NRI : Length of SGSN NRI. It shall be consistent with that at

CN side on configuration. Type 255 if the Flex Gb is not support.

2． SGSN version ID : It is used to identify version number of SGSN; consistent

with that at CN side.

3． SGSN ID : Only effective at iBSC side; FlexGb allows iBSC to connect up to 16

SGSNs.

4． SGSN CN ID: While configuring each adjacent SGSN office, configure

GLOBAL CN ID for this SGSN. This value shall be assigned to SGSN by the

operator; consistent with that at CN side.

67




1.44 Create IP Gb Interface

When interface Gb uses IP bearing, you need to configure the real and virtual addresses

of IP Gb.

1.44.1 Create Real Interface IP

[Purpose]

The real address interface is on the IPGB board. This operation guide guides you how

to create the real address of the IPGB board.

[Steps]


Function > IP Related Config. The configuration interface as shown in Figure

7.4 -70.


2． In the Interface tab page, click the button. Fill in configuration parameters


68




Figure 7.4-71 Create IP Gb Real Interface IP

1.44.2 Create Virtual Interface IP

[Purpose]

The virtual address of the IP Gb interface is on the RPU. This operation guide guides

you how to create the virtual address of IP Gb.

[Steps]



7.4 -72.


2． In the Interface tab page, click the button. Fill in configuration parameters


Figure 7.4-73 Create IP Gb Virtual IP

69




1.45 Create Static Route

[Purpose]

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

the SGSN.

[Steps]



7.5 -74.


2． Create static route to MSC. In the Static Route tab page, click the button.

Fill in configuration parameters in the pop-up dialog box, as shown in Figure

7.5 -75.

70




Figure 7.5-75 Create static route to SGSN


1． Static route prefix: Indicates the network segment of the destination network.

Input IP address prefix of SGSN_IP.

2． Next hop type: Select IP.

3． Next hop IP address : When next hop type is IP, the user can set this IP address.

This indicates all messages at target network segment, which is confirmed by

static route prefix and subnetmask, are sent to this IP address.．．GW_to_SGSN.

1.46 Create NSE

[Purpose]

This step guides you how to create NSE of IP Gb interface.

[Steps]


Function > Gb Interface Relate Config > SGSN Office1 > NSE Config, and

then select Create > NSE from the shortcut menu. Then fill in configuration

data in the pop-up dialog box.

Figure 7.6-76 Create NSE


71




1． NSE ID : It must be consistent with that at the CN side.

2．

Subnetwork type : In the case of E1 bearing, select frame relay. In the case of IP bearing, select IP.

3． Configuration type : In the static mode, you need to configure IP and ports of

local endpoint and remote endpoint. In the dynamic mode, you only need to

configure IP and port of the local endpoint.

4． Pre-configured SGSN IP address/UDP port : It indicates the SGSN UDP port

configured at BSC side while SGSN is connected in IP mode. Consistent with

that at CN side. You can modify this parameter only if the Configuration Type is

dynamic configuration.

1.47 Create IPGB Endpoint

[Purpose]

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.

[Steps]


Function > Gb Interface Relate Config > SGSN Office1 > IPGB Endpoint

Config, and then select Create > IPGB Endpoint from the shortcut menu. Then

fill in configuration data in the pop-up dialog box, as shown in Figure 7.7 -77.

72




Figure 7.7-77 Create IPGB Local Endpoint

2． Continue to create the IPGB remote endpoint, as shown in Figure 7.7 -78.

Figure 7.7-78 Create IPGB Remote Endpoint


73




1． NSE ID : NSE which the IPGB endpoint belongs to.

2．

IP address : Input IP address of IP_Gb_Virtual for the local endpoint. Input IPaddress of SGSN_IP for the remote endpoint.

3． UDP port : Input the UDP port assigned for the service.

4． Signal weight/Data weight : weight refers to the frequency to select this

endpoint on transmitting signals.

74



Data Synchronization

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

1.49 Check Validity of Global Data

[Purpose]

This step guides you how to check Validity of Global Data to make sure that the data is

correct and complies with the standard.

[Steps]

1． In the resource tree, right-click BSC Managed Element, and then select Config

Data Managed Element > Check Validity of Global Data from the shortcut

menu, as shown in Figure 8.2 -79.

Figure 8.2-79 Check Validity of Global Data

1.50 Synchronize Data

[Purpose]

This step guides you how to synchronize data.

[Steps]

75



1． In the resource tree, right-click BSC Managed Element, and then select Config

Data Managed Element > Synchronize All Data or Config Data Managed

Element > Synchronize Modified Data from the shortcut menu, as shown in

Figure 8.3 -80.

Figure 8.3-80 Synchronize Data


1． Synchronize All Data : Uploads all tables under the config set.

2．

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

01 gb_oc42_e1_0 zxg10 ibsc configuration(v6.20.614c) 82

Documents