07 GB_OC41_E1_0 ZXG10 IBSC Configuration(V6.20.100e) 141

ZXG10 iBSCConfiguration

ZTE UNIVERSITYZTE University, DameishaYanTian District, Shenzhen,P. R. China518083Tel: (86) 755 26778800Fax: (86) 755 26778999URL: http://ensupport.zte.com.cnE-mail: [email protected]

Content

ZXG10 iBSC Configuration ............................................ 1

1 Configuration Overview............................................. 21.1 Overview.............................................................................. 2

1.2 Logging in Configuration Management Interface......................... 2

1.3 Configuration Management Interface Description ....................... 5

1.4 Data Configuration Flow ......................................................... 7

1.5 Data Configuration Precautions...............................................10

2 Public Resource Configuration................................. 112.1 Overview.............................................................................11

2.2 Configuring GERAN Subnetwork..............................................11

2.3 Configuring BSC Managed Element .........................................13

2.4 Configuring Config Set ..........................................................15

2.5 Configuring BSC Function ......................................................17

3 BSC Physical Configuration...................................... 213.1 Overview.............................................................................21

3.2 Configuring BSC Rack ...........................................................21

3.3 Configuring Shelf and Board...................................................23

4 A-interface Configuration ........................................ 274.1 Overview.............................................................................27

4.2 E1 A-interface Configuration ..................................................27

4.2.1 Configuration Preparation ..............................................27

4.2.2 Configuring Local Office.................................................28

4.2.3 Configuring Adjacent Office............................................30

4.2.4 Configuring SS7 PCM ....................................................32

4.2.5 Configuring Signaling Link Set........................................33

4.2.6 Configuring Signaling Link .............................................34

4.2.7 Configure Signaling Route .............................................35

4.2.8 Configuring Signaling Office ...........................................36

4.2.9 Configuring PLMN/MSC Office.........................................37

4.3 IP A-interface Configuration ...................................................40


4.3.2 Configuring Local Office.................................................41

4.3.3 Configuring Adjacent Office............................................43

4.3.4 Creat IP Interface.........................................................45

4.3.5 Configuring Application Server Process............................49

4.3.6 Configuring Application Server .......................................51

4.3.7 Configuring SIO ...........................................................53

4.3.8 Configuring IP A-interface Service ..................................54

4.3.9 Configuring PLMN/MSC Office.........................................56

5 Ater-interface Configuration.................................... 615.1 Overview.............................................................................61

5.2 Configuration Preparation ......................................................61

5.2.1 Relevant Boards ...........................................................61

5.2.2 Data Planning ..............................................................61

5.3 Configuring Local Office.........................................................62

5.4 Configuring Adjacent Office....................................................64

5.5 Configuring PCM and Trunk Circuit ..........................................65

5.5.1 Configuring SS7 PCM ....................................................65

5.5.2 Configuring A-Interface PCM ..........................................66

5.5.3 Configuring A-Interface Trunk Circuit ..............................67

5.6 Configuring Signaling Link Set................................................68

5.7 Configuring Signaling Link .....................................................69

5.8 Configure Signaling Route......................................................70

5.9 Configuring Signaling Office ...................................................71

6 GB-interface Configuration ...................................... 736.1 Overview.............................................................................73

6.2 E1 GB-interface Configuration ................................................73


6.2.2 Configuring NSE...........................................................74

6.2.3 Configuring BRCH.........................................................75

6.2.4 Configuring NSVC.........................................................77

6.3 IP GB-interface Connection ....................................................79


6.3.2 Configuring RPU Interface .............................................80

6.3.3 Configuring IPGB Interface ............................................82

6.3.4 Configuring Static Route................................................83

6.3.5 Gb Interface Related Configuration .................................84

Related Information..................................................... 1

7 Corresponding Relationship between Logic Board

and Physical Board....................................................... 2

8 OMP Construction...................................................... 5

8.1 Overview.............................................................................. 5

8.2 OMP Configuration Flow.......................................................... 5

8.3 Configuring OMP at Serial Port................................................. 6

8.4 Uploading Configuration File...................................................18

9 Common Configuration Operation ........................... 219.1 Basic Operations of Data Configuration ....................................21

9.2 Performing Switchover between Master Config Set and Slave

Config Set ......................................................................................24

9.3 Exporting Physical Data .........................................................25

9.4 Exporting Radio Data ............................................................27

9.5 Exporting Software Data........................................................29

9.6 Exporting Network Planning Data............................................31

9.7 Performing Configuration Data Backup ....................................33

9.8 Recovering Data Configuration ...............................................35

9.9 Configuring BSC Rack by Template..........................................39

9.10 Data Synchronization ..........................................................42

9.10.1 Performing All Data Synchronization..............................42

9.10.2 Performing Modified Data Synchronization......................43

ZXG10 iBSCConfigurationAfter you have completed this course, you

will be able to:

>> Learn the basic operation of configura-tion

>> Learn the procedure of public resourceconfiguration

>> Lerarn the procedure of BSC physicalconfigurationl

>> Learn the procedure of A-interfaceconfiguration

>> Learn the procedure of Gb-interfaceconfiguration

Confidential and Proprietary Information of ZTE CORPORATION 1

ZXG10 iBSC Configuration

Chapter1 Configuration OverviewAfter you have completed this chapter, you will know:

>> Overview

>> Logging in Configuration Management Interface

>> Configuration Management Interface Description

>> Data Configuration Flow

>> Data Configuration Precautions

1.1 Overview

Configuration management enables user to manage resource dataand status, and provides various data configurations to supportnormal system running. It determines the running mode and sta-tus of ZXG10 BSS.

Data configuration means establishing the relationship betweenthe network management system and network elements such asBSC and BTS. It enables user to perform parameter setting formanagement objects in BSS.

1.2 Logging in ConfigurationManagement Interface

Prerequisites NetNumen M31 client is logged in successfully.

Context This section describes how to log in the configuration managementinterface.

Steps 1. In the topology tree on the left of the main interface of NetNu-men M31 client, right-click on the created GSM NE agent node,and select Start NE on the pop-up menu, as shown in Figure1.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Configuration Overview

FIGURE 1 LOGGING IN CONFIGURATION MANAGEMENT (1)

2. Click Start NE, the system automatically starts this NE.

3. After the NE is started, right-click on it to pop up the shortcutmenu, select NE Management > Configuration Manage-ment, as shown in Figure 2.




4. Click Configuration Management, the configuration man-agement interface is opened, as shown in Figure 3.




END OF STEPS

Postrequisite Configure public resources.

1.3 Configuration ManagementInterface Description

The configuration management interface is shown in Figure 4.



FIGURE 4 CONFIGURATION MANAGEMENT INTERFACE

1. Configuration Management Tool-bar

2. Configuration Management Ele-ment Toolbar

3. Configuration Management Ele-ment Property Tab (Taking MasterConfig Set for Example)

4. Configuration Resource Tree

1. Table 1 shows the toolbar for configuration management.

TABLE 1 CONFIGURATION MANAGEMENT TOOLBAR

Toolbar Button Description

Lock Screen

Logout

Refresh

Forward

Backward

Help

2. Table 2 shows the toolbar for configuration management ele-ment.

TABLE 2 CONFIGURATION MANAGEMENT ELEMENT TOOLBAR


Modify

Cancel




Save

Close

CloseAll

Help

Switch to masterconfiguration set

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

3. Configuration management element attribute tab

i. User can view the attribute details of a configuration man-agement element in this tab.

ii. User can perform various operations through the toolbar inthis tab.

4. Configuration resource tree

i. User can view configured elements in the configuration re-source tree.

ii. User can open the configuration management element at-tribute tab by double-clicking the corresponding manage-ment element in the configuration resource tree.

iii. User can perform various operations by right-clicking oncorresponding management element in the configurationresource tree.

1.4 Data Configuration Flow

Figure 5 shows the data configuration flow.



FIGURE 5 DATA CONFIGURATION FLOW

1. Public resource configuration

Public resource configuration includes configuring GERAN sub-network, BSC management element, config set, and BSC func-tion. It is the basis of data configuration.

2. BSC physical equipment configuration

BSC physical equipment configuration includes configuring BSCrack, shelf, and board.

3. A/Ater interface configuration

A/Ater interface configuration is performed after BSC physicalequipment is configured.

i. User can adopt the full-E1 mode or the full-IP mode ac-cording to actual condition.



If TC is internal and A-interface transmission uses E1 forboth user plane and control plane, then E1 A-interface con-figuration is adopted.

If TC is internal and A-interface transmission uses IP forboth user plane and control plane, then IP A-interface con-figuration is adopted.

If TC is external and Ater interface transmission uses E1 forboth user plane and control plane, then E1 Ater interfaceconfiguration is adopted.

ii. User can also combine different transmission modes foruser plane and control plane according to actual require-ment. For example, adopt E1 for user plane and IP forcontrol plane, or adopt IP for user plane and E1 for controlplane.

4. GB interface configuration

If GPRS/EDGE service is to be commissioned, user must per-form Gb interface configuration according to actual condition.

If Gb interface transmission uses E1, then E1 Gb interface con-figuration is adopted.

If Gb interface transmission uses IP, then IP Gb interface con-figuration is adopted.

5. External cell configuration

External cell configuration includes configuring GERAN externalcell and UTRAN external cell.

6. Site and radio configuration

Site and radio configuration includes configuring site, cascadedsite, cell, frequency hopping, transceiver, adjacent cell interfer-ence/handover/reselection/handover&reselection, and UTRANadjacent cell handover/reselection/handover&reselection.

7. Other configurations

Other configurations are optional according to actual require-ment. It includes alarm parameter configuration and systemcontrol parameter configuration.

8. Software loading

Software loading includes loading BSC board software and BTSboard software. It guarantees the board's normal running.

After the configuration is completed, user can perform dynamicdata configuration according to actual requirement.



Caution:

For each type of configuration mentioned above, it is recom-mended to perform data synchronization after the configurationis completed. In other words, perform all data synchronization ormodified data synchronization to synchronize the configured datawith that at BSC to make it validate; otherwise, the configureddata is only virtual data in the network management system.

1.5 Data Configuration Precautions

Data configuration is very important for the entire system. Anymistake in data configuration will seriously influence the systemrunning. The following items should be noticed in data configura-tion and modification.

1. Before performing data configuration, prepare the data relatedto system running, such as interconnection data for A-interfaceand Gb interface. The data should be accurate and reliable,and a complete data configuration solution is required. A gooddata configuration solution not only makes the data clear tousers but also increases the system reliability.

2. Before modifying any data, perform backup for the currentdata. After modifying the data, synchronize it with that at BSCand BTS. Make sure that the data is correct and perform databackup in time.

3. The configured data in the network management system clienttakes effect only after being synchronized with that at BSC andBTS. For configuration data applied in a running system, thedata must be checked before being transferred to avoid theinfluence of incorrect data on the system running.

Caution:

Because a large amount of parameters are involved in data config-uration, this manual only introduces some important parametersand parameters that must be modified. Such parameters shouldbe configured according to the configuration specification. For pa-rameters not introduced, the default setting is adopted.


Chapter2 Public ResourceConfiguration

After you have completed this chapter, you will know:

>> Overview

>> Configuring GERAN Subnetwork

>> Configuring BSC Managed Element

>> Configuring Config Set

>> Configuring BSC Function

2.1 Overview

Public resource configuration includes configuring GERAN subnet-work, BSC management element, config set, and BSC function.

2.2 Configuring GERANSubnetwork

Prerequisites The configuration management interface is opened successfully.

Context A GERAN subnetwork contains one management element, and thesubnetwork's ID is same as that of the management element.

This section introduces how to configure the GERAN subnetwork.

Steps 1. In the configuration resource tree, right-click on OMC and se-lect Create > GERAN Subnetwork, as shown in Figure 6.



FIGURE 6 CONFIGURING GERAN SUBNETWORK (1)

2. Click GERAN subnetwork, and the Create GERAN Subnet-work dialog box appears, as shown in Figure 7. Input relevantparameter values.


3. Click OK. After the operation is completed, the newly config-ured GERAN subnetwork node appears on the configurationresource tree, as shown in Figure 8.


Chapter 2 Public Resource Configuration


END OF STEPS

Postrequisite Configure the BSC management element.

2.3 Configuring BSC ManagedElement

Prerequisites The GERAN subnetwork is configured successfully.

Context The BSC managed element is sub-node of the GERAN subnetworknode. A managed element can only be contained in one GERANsubnetwork.

This section introduces how to configure the BSC managed ele-ment.

Steps 1. In the configuration resource tree, right-click on the GERANSubnetwork node and select Create > BSC Managed Ele-ment, as shown in Figure 9.



FIGURE 9 CONFIGURING BSC MANAGED ELEMENT (1)

2. Click BSC Managed Element, and the Create BSCmanagedelement dialog box appears, as shown in Figure 10.




Caution:

When configuring Managed element IP address, make surethat the setting is consistent with the IP address configured forthe serial port of OMP of iBSC. The setting must be unique fordifferent managed elements.

3. Click OK. After the operation is completed, the newly config-ured BSC managed element node appears on the configurationresource tree, as shown in Figure 11.


END OF STEPS

Postrequisite Configure the config set.

2.4 Configuring Config Set

Prerequisites The BSC management element is configured successfully.

Context The system provides multiple sets of configuration data for thenetwork management elements. User can configure multiple dataconfiguration sets, one is the master config set while others areslave config sets. After the configuration is completed, user canswitch between the master config set and the slave config set.

User can perform foreground-background operations for the mas-ter config set, such as data synchronization and dynamic opera-tion.

The master config set can not be created or deleted individually.It is created automatically when the management element is con-figured, and is deleted simultaneously when the subnetwork node



or the management element node is deleted. There can only beone master config set under a management element.

This section introduces how to configure the slave config set.

Steps 1. In the configuration resource tree, right-click on the BSCManaged Element node and select Create > Config Set, asshown in Figure 12.

FIGURE 12 CONFIGURING CONFIG SET (1)

2. Click Config Set, and the Create Config Set dialog box ap-pears, as shown in Figure 13. Input relevant parameter values.




3. Click OK. After the operation is completed, the newly config-ured config set node appears on the configuration resourcetree, as shown in Figure 14.


END OF STEPS

Postrequisite Configure the BSC function.

2.5 Configuring BSC Function

Prerequisites The config set is configured.

Context The BSC function is sub-node of the config set node. All global re-source managed objects are located under the BSC function node.

This section introduces how to configure the BSC function.

Steps 1. In the configuration resource tree, right-click on the ConfigSet node and select Create > BSC Function, as shown inFigure 15.



FIGURE 15 CONFIGURING BSC FUNCTION (1)

2. Click BSC Function, and the Create BSC Function dialog boxappears. User can click the icon to display all sub-tabs, asshown in Figure 16. Input relevant parameter values.


Basic Property tab:

MCC(MCC)



Configure this parameter according to actual situation. Itcan not be modified after being configured.

Support MNC 3 digits(MNC3Digits)


MNC(MNC)


OMP IP(OMP_IP)

This parameter must be consistent with Managed ele-ment IP address in Configuring BSC Managed Element.

OMP MAC(OMP_MAC)

Configure this parameter according to actual situation.

OMC subnet mask(Info4)


OMC server IP(Info6)

SBCXs IP address. Configure this parameter according toactual situation.

OMCB IP(OMCB)

If the dual-mode site BS8200 is configured, then the IPaddress of OMCB must be configured.

SNTP server IP

This parameters value is the same as OMP IP(OMP_IP).

Net type(Net)


SP type(SPType)


Bureau No.(BureauNo)

Configure this parameter according to actual situation. Itcan not be repeated under the same server, and can not bemodified after being configured.

Support GE(GESupport)

Configure this parameter according to actual situation. Ifit is set to "Yes", then only the gigabit resource shelf canbe configured in the BSC rack as resource shelf; otherwise,only the megabit resource shelf can be configured in theBSC rack as resource shelf. The gigabit resource shelf andthe megabit resource shelf can not be configured togetherin the BSC rack.

Support TC type(TCType)


Radio Basic Property tab:

DCS1800/PCS1900 supported(FuncExt)



Configure this parameter according to actual situation. It cannot be modified after being configured.

3. Click OK. After the operation is completed, the newly config-ured BSC function node appears on the configuration resourcetree, as shown in Figure 17.


END OF STEPS

Postrequisite Configure BSC physical equipments.


Chapter3 BSC PhysicalConfiguration


>> Overview

>> Configuring BSC Rack

>> Configuring Shelf and Board

3.1 Overview

BSC physical equipment configuration includes configuring BSCrack, shelf, and board.

3.2 Configuring BSC Rack

Prerequisites 1. The public resource is configured successfully.

2. The number of racks to be configured is decided.

Context Configure a new BSC rack manually, and configure data related tothe rack.

Steps 1. In the configuration resource tree, right-click on the BSC De-vice Config node and select Create > BSC Rack, as shownin Figure 18.



FIGURE 18 MANUALLY CONFIGURING BSC RACK (1)

2. Click BSC Rack, and the Create BSC Rack dialog box appears,as shown in Figure 19. Select Rack No. and Rack type. Atmost two racks can be configured.


3. Click OK. After the operation is completed, the newly config-ured BSC rack node appears on the configuration resource tree.In the manual configuration mode, shelves and boards are notconfigured in the rack. Figure 20 shows an example of theconfigured rack.


Chapter 3 BSC Physical Configuration


END OF STEPS

Postrequisite Configure shelf and board.

3.3 Configuring Shelf and Board

Prerequisites The BSC rack is configured successfully.

Context This section introduces how to configure control shelf, resourceshelf, packet switching shelf, and relevant boards.

Steps 1. In the configuration resource tree, double-click the BSC Racknode to be configured with shelf and board.



2. Right-click on the second shelf of the rack, click Create Shelfin the pop-up menu, and the Create Shelf dialog box appears.Select Control shelf as Shelf type, as shown in Figure 21.

FIGURE 21 CONFIGURING SHELF AND BOARD (1)

3. Click OK to create the control shelf, as shown in Figure 22.



Chapter 3 BSC Physical Configuration

4. Configure boards according to the actual requirement, asshown in Figure 23.


Note:

In control shelf, the OMP board must be configured first,then the UIMC board, and then other boards.

The SBCX board 1 need not be configured.

5. Repeat step 1 ~ step 4 to configure resource shelf (or gigabitresource shelf), packet switching shelf, and relevant boards.Figure 24 shows the configuration result.

1. Single Board Computer of X86, server board




Note:

In resource shelf/gigabit resource shelf, the UIMU/GUIM boardmust be configured first.

END OF STEPS

Postrequisite Configure A-interface data.


Chapter4 A-interface ConfigurationAfter you have completed this chapter, you will know:

>> Overview

>> E1 A-interface Configuration

>> IP A-interface Configuration

4.1 Overview

A-interface data configuration includes configuring signaling andservice channels between iBSC and MSC, and configuring inter-connection between iBSC and MSC.

iBSC supports two interface types: E1 A-interface and IP A-inter-face. Different transmission modes have different bottom-layerbearer protocols, including signaling and service protocols. Suchdifference also causes different configurations.

For signaling, if IP A-interface configuration is used, then theM3UA protocol is adopted. This protocol bears the originalSCCP protocol, thus it is necessary to configure signaling pointand sub-system number. If E1 A-interface configuration isused, signaling link and route are replaced by SCTP and ASlocation.

For services, if E1 A-interface configuration is used, then thePCM service channel (the rate is 64 kbps) is configured. If IPA-interface configuration is used, only the local IP address andport should be configured, and the IP-UDP-RTP layer bears theservice data.

4.2 E1 A-interface Configuration

4.2.1 Configuration Preparation

4.2.1.1 Relevant Boards

The following lists relevant boards when E1 A-interface configura-tion is used.

1. DTB/SDTB board: used for E1 A-interface access.

2. SPB board: used for SS7 signaling processing.



3. DRTB board2: used for service data processing, implementingtranscoding and rate adaptation.

4.2.1.2 Data Planning

When E1 A-interface configuration is used, it is necessary to planthe following data to make them consistent with that at MSC.

Local office and adjacent office

Signaling point code

Adjacent office properties

Sub-service field

Protocol type

Start timeslot number

Number of timeslots

Signaling link code

Signaling link type

SS7 PCM No.

Link error calibration method

4.2.2 Configuring Local Office

Prerequisites The BSC function is configured successfully.

Context Through this task, user can configure a uniquely identified localoffice in the network.

Steps 1. In the configuration resource tree, right-click on OMC >GERAN Subnetwork > BSC Managed Element > ConfigSet > BSC Function > A/Ater Interface Related Config,and select > Create > Local Office in the pop-up menu, asshown in Figure 25.

2. Dual Rate Transcoder Board


Chapter 4 A-interface Configuration

FIGURE 25 CONFIGURING LOCAL OFFICE (1)

2. Click Local Office, and the Create Local Office dialog boxappears, as shown in Figure 26.

No.7 type: when E1 A-interface configuration is used, se-lect Narrow band.

Net appearance info: set this parameter with the samevalue as that at MSC.

OPC (14 bits): set this parameter according to planneddata.

OPC (24 bits): iBSC often uses 14-bit signaling point codeinstead of 24-bit signaling point code.




3. Click OK to finish configuring the local office.

Note:

After the local office is successfully configured, the local office'ssignaling subsystem is generated automatically.

END OF STEPS

Postrequisite Configure adjacent office.

4.2.3 Configuring Adjacent Office

Prerequisites The local office is configured successfully.

Context Adjacent office configuration includes configuring adjacent officesignaling point and other relevant data. The former operation isused to uniquely identify the adjacent office while the latter op-eration facilitates the interaction between the local office and theadjacent office.

Steps 1. In the configuration resource tree, double-click the Local Of-fice node under OMC > GERAN Subnetwork > BSC Man-aged Element > Config Set > BSC Function > A/Ater In-



terface Related Config, and click the icon in the AdjacentOffice tab on the right.

2. The Create Adjacent Office dialog box appears, as shown inFigure 27. Input the parameter values.

Office type: when E1 A-interface configuration is used,the adjacent cell data of MSC SERVER should be configured,and the adjacent cell data of MGW is configured accordingto actual requirement.

SPT type: set this parameter according to planned data.

SSF: set this parameter according to planned data.

SPC type: MSC usually adopts 14-bit signaling point code(SPC 14) to communicate with iBSC.

DPC: set this parameter according to planned data.

AM: set this parameter according to actual condition.

FIGURE 27 CONFIGURING ADJACENT OFFICE (1)

3. Click OK to finish configuring the adjacent office.



Note:

After the adjacent office is successfully configured, the adja-cent office's signaling subsystem is generated automatically.

END OF STEPS

Postrequisite Configure SS7 PCM.

4.2.4 Configuring SS7 PCM

Prerequisites The local office and the adjacent office are configured successfully.

Context Configuring SS7 PCM is used for configuring SS7 PCM service chan-nel.


terface Related Config, and click the icon in the No.7PCM tab on the right.

2. In the Create No.7 PCM dialog box, click the icon tosend PCMs on the left to Selected PCM on the right, as shownin Figure 28.



FIGURE 28 CONFIGURING SS7 PCM (1)

3. Click OK to finish configuring SS7 PCM.

END OF STEPS

Postrequisite Configure signaling link set.

4.2.5 Configuring Signaling Link Set


Context A signaling link set contains multiple signaling links.


terface Related Config, and click the icon in the No.7Link Set tab on the right.

2. The Create No.7 Link Set dialog box appears, as shown inFigure 29. Input the parameter values.



FIGURE 29 CONFIGURING SIGNALING LINK SET (1)

3. Click OK to finish configuring the signaling link set.

END OF STEPS

Postrequisite Configure signaling link.

4.2.6 Configuring Signaling Link

Prerequisites The local office and the signaling link set are configured success-fully.

Context Configuring the signaling link is used for configuring SS7 PCM sig-naling link properties and its home physical link.


terface Related Config, and click the icon in the No.7Link tab on the right.

2. The Create No.7 Link dialog box appears, as shown in Figure30. Input the parameter values.



FIGURE 30 CONFIGURING SIGNALING LINK (1)

3. Click OK to finish configuring the signaling link.

END OF STEPS

Postrequisite Configure signaling route.

4.2.7 Configure Signaling Route


Context This section introduces how to configure SS7 signaling route.


terface Related Config, and click the icon in the No.7Route tab on the right.

2. The Create No.7 Route dialog box appears, as shown inFigure 31. Input the parameter values.



FIGURE 31 CONFIGURE SIGNALING ROUTE (1)

3. Click OK to finish configuring the signaling route.

END OF STEPS

Postrequisite Configure signaling office.

4.2.8 Configuring Signaling Office

Prerequisites The local office and the signaling route are configured successfully.

Context This section introduces how to configure SS7 signaling office.


terface Related Config, and click the icon in the No.7Office tab on the right.

2. The Create No.7 Office dialog box appears, as shown inFigure 32. Input the parameter values.



FIGURE 32 CONFIGURING SIGNALING OFFICE (1)

3. Click OK to finish configuring the signaling office.

END OF STEPS

Postrequisite Configure PLMN/MSC office.

4.2.9 Configuring PLMN/MSC Office

Prerequisites A-interface data configuration is completed.

Context iBSC supports multiple operators and multiple MSC offices. It alsosupports that various operators share a same physical network.Configuring PLMN/MSC office is used for associate operators andMSC offices.

Steps 1. In the configuration resource tree, right-click on OMC >GERAN Subnetwork > BSC Managed Element > ConfigSet > BSC Function > Set PLMN/MSC Office/SGSNOffice, as shown in Figure 33.



FIGURE 33 CONFIGURING PLMN/MSC OFFICE (1)

2. Click Set PLMN/MSC Office/SGSN Office, and configureMSC in the MSC Office tab, as shown in Figure 34.

NRI of MSC(NRI): set this parameter with the same valueas NRI at the core network. If iBSC does not support FLEXA, 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 iBSCdoes not support FLEX A, do no configure this parameters.

Selected number: this parameter is related to multi-sig-naling point function. When the multi-signaling-point func-tion is enabled, this parameter's value can not be zero.




3. Configure PLMN in the PLMN tab, as shown in Figure 35.

MCC

MNC

Length of MSC NRI: set this parameter with the samevalue as that at CN. If iBSC does not support FLEX A, dono configure this parameter.

MSC NULL-NRI ID: set this parameter with the samevalue as that at CN. If iBSC does not support FLEX A, donot configure this parameter.

MSC version ID: set this parameter with the same valueas that at CN.

MSC CN ID: set this parameter with the same value as thatat CN. If iBSC does not support FLEX A, do not configurethis parameter.




END OF STEPS

Postrequisite Perform Gb interface configuration.

4.3 IP A-interface Configuration



The following lists relevant boards when IP A-interface configura-tion is used.

1. IPAB3/IPI board4: interface board, which is responsible for IPpacket resolution.

2. AIPB board5: user-plane processing board, which implementsRTP protocol processing.


When IP A-interface configuration is used, it is necessary to planthe following data to make them consistent with that at MSC.


3. IP A interface Board4. IP Interface Board5. A Interface ip Processing Board





Sub-service field

Application server process

i. Protocol type

ii. The local IP address and the opposite IP address

iii. The local port number and the opposite port number.

iv. Application property: matching that of MSC

If MSC is at the server end, then configure the client atiBSC.

If MSC is at the client end, then configure the server atiBSC.

Application server

i. Supported adaptation-layer protocols

ii. Service mode

4.3.2 Configuring Local Office








No.7 type: When A-interface adopts full IP configuration,select IP; when A-interface control plane adopts IP trans-mission mode and A-interface user plane adopts E1 trans-mission mode, select Narrow band and IP.

Net appearance info: set this parameter with the samevalue as that at MSC.

OPC (14 bits): set this parameter according to planneddata.






Note:


END OF STEPS


4.3.3 Configuring Adjacent Office








Office type: selectMSC SEVER. For IP A, only MSC SEVERoffice should be configured, MGW does not need to config-ure the office. This is different from the configuration forE1 A.

SPT type: set this parameter according to planned data.

SSF: set this parameter according to planned data.

SPC type: MSC usually adopts 14-bit signaling point code(SPC 14) to communicate with BSC.

DPC: set this parameter according to planned data.

AM: For IP A, select AM sure.





Note:


END OF STEPS

Postrequisite Configure IP interface.

4.3.4 Creat IP Interface

4.3.4.1 Configuring IPI Interface Address

Prerequisites 1. The BSC function is configured successfully.

2. The IPI board is configured successfully.

Context This section introduces how to configure the IP A-interface ad-dress.

Steps 1. In the configuration resource tree, double-clickOMC>GERANSubnetwork > BSC Managed Element > Config Set > BSC

Function > IP Related Config, and click the icon in theInterface tab on the right.

2. The Create Interface dialog box appears, as shown in Figure39. Input the parameter values.

Board function type: When A-interface adopts full IPconfiguration, select IPI; when A-interface control planeadopts IP transmission mode and A-interface user planeadopts E1 transmission mode, select IPAB.

MAC address: Input the MAC address of the GIPI rearboard's network port.

IP address: Set this parameter according to planned data.

Subnet mask: Set this parameter according to planneddata.



FIGURE 39 CONFIGURING IPI INTERFACE ADDRESS (1)

3. Click OK to create the IP A-interface, as shown in Figure 40.

FIGURE 40 CONFIGURING IPI INTERFACE ADDRESS (2)

END OF STEPS

Postrequisite Configure RPU interface.

4.3.4.2 Configuring RPU Interface




Context Configure RPU interface, that is, configure the virtual IP addressof iBSC.




Board function type: Select RPU.


Subnet mask: 255.255.255.255

FIGURE 41 CONFIGURING RPU INTERFACE (1)

3. Click OK to create the RPU interface, as shown in Figure 42.




END OF STEPS

Postrequisite Configure static route.

4.3.4.3 Configuring Static Route

Prerequisites The IPI interface address is configured successfully.

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


Function > IP Related Config, and click the icon in theStatic Router tab on the right.

2. The Create Static Router dialog box appears, as shown inFigure 43. Input the parameter values.

Static router prefix: Set this parameter according toplanned data.

Static router subnetmask: Set this parameter accordingto planned data. For example, set Static router prefix tobe 192.168.1.0, and set Static router subnet mask tobe 255.255.255.0. It indicates that, for MSCs of which theIP address is within [192.168.1.1, 192.168.1.254], iBSCsends data to these MSCs via the current route.

Next hop type: Select IP.

Next hop IP address: Set this parameter according toplanned data. It refers to the IP address of the nearestelement of iBSC. It means the IP address of the router orMSC. 6.

6. When there is no router between iBSC and MSC



FIGURE 43 CONFIGURING STATIC ROUTE

3. Click OK to finish configuring the single static route.

END OF STEPS

Postrequisite Configure application server process.

4.3.5 Configuring Application ServerProcess


Context This task configures the instance of application server process,which is used as the active or standby process of the applicationserver.


terface Related Config, and click the icon in the ASP tabon the right.

2. The Create ASP dialog box appears, as shown in Figure 44.Input the parameter values.

ASP Basic Config tab



Module: The SCTP's home signaling module number. TheSCTP is maintained by the module's bearer and signaling.Set this parameter according to planned data.

Protocol type: For IP A, select M3UA.

Office ID: The opposite office ID of SCTP.

Property: Client or server. It must match the property ofMSC SERVER. For SCTP, one end is client and the other endis server. The SCTP connection is initiated from the client.

Local port: It must be consistent with the opposite portnumber at MSC SERVER.

Remote port: It must be consistent with the local portnumber at MSC SERVER.

IP Config tab

Local IP ADDR: RPU interface's IP address

Remote IP ADDR: It must be consistent with the IP ad-dress of MSC SERVER.

Note:

User can configure multiple local IP addresses and opposite IPaddresses. It is required that at least one set of IP addressescan keep normal communication.



FIGURE 44 CONFIGURING APPLICATION SERVER PROCESS

3. Click OK to finish configuring the application server process.

END OF STEPS

Postrequisite Configure application server.

4.3.6 Configuring Application Server

Prerequisites The application server process is configured successfully.

Context Application server is the logical entity of the service's specific rout-ing key. Application server contains a group of unique applicationserver processes, one process or a few processes are in active sta-tus for service processing.


terface Related Config, and click the icon in the AS tabon the right.

2. The Create AS dialog box appears, as shown in Figure 45.Input the parameter values.



Protocol: Select M3UA.

Exist context: Select False.

Tag: For IP A, select IPSP, that is, iBSC connects MSCSERVER via SigTran. IPSP provides internal point-to-pointapplication within IP domain. Whether IPSP_SEVER orIPSP_CLIENT is selected should be consistent with theapplication property of the application server processcontained in this application server.

Service mode: Usually, select Participate, that is, mul-tiple ASPs bear the service.

Mode N: It refers to the minimum number of ASPs requiredfor AS service in the participate mode. Set this parameteraccording to planned data.

Mode K: It refers to the number of backup ASPs in theparticipate mode. Set this parameter according to planneddata.

ASP number: In the participate mode, ASP number =Mode N + Mode K.

FIGURE 45 CONFIGURING APPLICATION SERVER (1)

3. Click OK to create the application server, as shown in Figure46.



FIGURE 46 CONFIGURING APPLICATION SERVER (2)

END OF STEPS

Postrequisite Configure SIO.

4.3.7 Configuring SIO

Prerequisites The application server process is configured successfully.

Context SIO means locating SCCP service to the application server for aMSC office, and then a application server process of that applica-tion server processes the SCCP service.


terface Related Config, and click the icon in the SIO tabon the right.

2. The Create SIO dialog box appears, as shown in Figure 47.Input the parameter values.

Office ID: It is necessary to configure SIO information forall adjacent offices of MSC SERVER.

OPC: Signaling point code of iBSC.

SIO: Select SCCP.

Application server ID: Set this paramter according toplanned data.



FIGURE 47 CONFIGURING SIO (1)

3. Click OK to finish configuring SIO, as shown in Figure 48.

FIGURE 48 CONFIGURING SIO (2)

END OF STEPS

Postrequisite Configure IP A-interface service.

4.3.8 Configuring IP A-interfaceService

Prerequisites The AIPB board of IP A-interface user plane is configured success-fully.

Context IP A-interface service configuration means setting DSP service's IPaddress and UDP port number for AIPB.

Steps 1. In the configuration resource tree, double-click the BSC Racknode under OMC > GERAN Subnetwork > BSC Managed



Element > Config Set > BSC Function > BSC Device Con-fig, right-click the AIPB board in the rack, and click Set IPPort in the pop-up menu, as shown in Figure 49.

FIGURE 49 CONFIGURING IP A-INTERFACE SERVICE (1)

2. In the Set IP Port dialog box, set IP address7 and Startnumber of port for DSP on AIPB, as shown in Figure 50.

7. User plane virtual IP address



FIGURE 50 CONFIGURING IP A-INTERFACE SERVICE (2)

END OF STEPS

Postrequisite Configure PLMN/MSC office.

4.3.9 Configuring PLMN/MSC Office

Prerequisites A-interface data configuration is completed.

Context iBSC supports multiple operators and multiple MSC offices. It alsosupports that various operators share a same physical network.Configuring PLMN/MSC office is used for associate operators andMSC offices.

Steps 1. In the configuration resource tree, right-click on OMC >GERAN Subnetwork > BSC Managed Element > ConfigSet > BSC Function > Set PLMN/MSC Office/SGSNOffice, as shown in Figure 51.




2. Click Set PLMN/MSC Office/SGSN Office, and configureMSC in the MSC Office tab, as shown in Figure 52.

NRI of MSC(NRI): set this parameter with the same valueas NRI at the core network. If iBSC does not support FLEXA, 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 iBSCdoes not support FLEX A, do no configure this parameters.

Selected number: this parameter is related to multi-sig-naling point function. When the multi-signaling-point func-tion is enabled, this parameter's value can not be zero.




3. Configure PLMN in the PLMN tab, as shown in Figure 53.

MCC

MNC

Length of MSC NRI: set this parameter with the samevalue as that at CN. If iBSC does not support FLEX A, dono configure this parameter.

MSC NULL-NRI ID: set this parameter with the samevalue as that at CN. If iBSC does not support FLEX A, donot configure this parameter.

MSC version ID: set this parameter with the same valueas that at CN.

MSC CN ID: set this parameter with the same value as thatat CN. If iBSC does not support FLEX A, do not configurethis parameter.




END OF STEPS




This page is intentionally blank.


Chapter5 Ater-interfaceConfiguration


>> Overview

>> Configuration Preparation

>> Configuring Local Office

>> Configuring Adjacent Office

>> Configuring PCM and Trunk Circuit

>> Configuring Signaling Link Set

>> Configuring Signaling Link

>> Configure Signaling Route

>> Configuring Signaling Office

5.1 Overview

5.2 Configuration Preparation

5.2.1 Relevant Boards

The following lists relevant boards when E1 Ater interface config-uration is used.

1. DTB/SDTB board: used for E1 Ater interface access.

2. SPB board: used for SS7 signaling processing.

3. TIPB board8: used for service data processing, implementingTDM packet and IP packet conversion.

5.2.2 Data Planning

When E1 Ater interface configuration is used, it is necessary toplan the following data to make them consistent with that at iTC.



8. aTer Interface Processing Board




Sub-service field

Protocol type

Start timeslot number

Number of timeslots

Signaling link code

Signaling link type

SS7 PCM No.

Link error calibration method

5.3 Configuring Local Office



If A-interface data is configured, then Ater interface and A-inter-face share one local signaling point at iBSC, and it is not necessaryto configure the local office.




Chapter 5 Ater-interface Configuration


No.7 type: When E1 Ater interface configuration is used,select Narrow band.

Net appearance info: Set this parameter with the samevalue as that at iTC.

OPC (14 bits): Set this parameter according to planneddata.




Note:


END OF STEPS




5.4 Configuring Adjacent Office

Prerequisites 1. The local office is configured successfully.

2. When configuring BSC function, set Support TC type(TC-Type) to be Outer TC.





Office type: Two adjacent offices should be configured forAter interface: iTC and MSC.

SPT type: Set this parameter according to planned data.

SSF: Set this parameter according to planned data.

SPC type: iTC usually adopts 14-bit signaling point code(SPC 14) to communicate with BSC.

DPC: Set this parameter according to planned data.

AM: Set this parameter according to actual condition.





Note:


END OF STEPS

Postrequisite Configure PCM and trunk circuit.

5.5 Configuring PCM and TrunkCircuit

5.5.1 Configuring SS7 PCM




Context Configuring SS7 PCM is used for configuring SS7 PCM service chan-nel at Ater interface.


terface Related Config, and click the icon in the No.7PCM tab on the right.

2. In the Create No.7 PCM dialog box, click the icon tosend PCMs on the left to Selected PCM on the right, as shownin Figure 57.

FIGURE 57 CONFIGURING SS7 PCM (1)

3. Click OK to finish configuring SS7 PCM.

END OF STEPS

Postrequisite Configure A-interface PCM.

5.5.2 Configuring A-Interface PCM


Context Configuring A-interface PCM is used for establishing the corre-sponding relationship between the PCM system number of MSCat A-interface and the PCM system number of iTC at A-interface.




terface Related Config, and click the icon in the A In-terface PCM tab on the right.

2. In the Create A Interface PCM dialog box, set iTC office IDand MSC office ID, and PCM system number at iTC and at MSC,as shown in Figure 58.

FIGURE 58 CONFIGURING A-INTERFACE PCM

3. Click OK to finish configuring a single A-interface PCM.

END OF STEPS

Postrequisite Configure A-interface trunk circuit.

5.5.3 Configuring A-Interface TrunkCircuit

Prerequisites A-interface PCM is configured successfully.

Context Configuring A-interface trunk circuit is used to configure the times-lot circuit number of A-interface PCM.


terface Related Config, and click the icon in the A In-terface Trunk tab on the right.

2. In the Create A Interface Trunk dialog box, clickto select the left circuit number to Created Circuit No. on theright, as shown in Figure 59.



FIGURE 59 CONFIGURING A-INTERFACE TRUNK CIRCUIT

3. Click OK to finish configuring A-interface trunk circuit.

END OF STEPS

Postrequisite Configure signaling link set.

5.6 Configuring Signaling Link Set


Context A signaling link set contains multiple signaling links.


terface Related Config, and click the icon in the No.7Link Set tab on the right.

2. The Create No.7 Link Set dialog box appears, as shown inFigure 60. Input the parameter values.



FIGURE 60 CONFIGURING SIGNALING LINK SET (1)

Note:

For Ater interface, set Office ID to be iTC.

For A-interface, set Office ID to be MSC. The control-planedata can be transmitted via iTC or directly sent to MSC fromiBSC.

3. Click OK to finish configuring the signaling link set.

END OF STEPS

Postrequisite Configure signaling link.

5.7 Configuring Signaling Link


Context Configuring the signaling link is used for configuring SS7 PCM sig-naling link properties and its home physical link.


terface Related Config, and click the icon in the No.7Link tab on the right.

2. The Create No.7 Link dialog box appears, as shown in Figure61. Input the parameter values.



FIGURE 61 CONFIGURING SIGNALING LINK (1)

3. Click OK to finish configuring the signaling link.

END OF STEPS

Postrequisite Configure signaling route.

5.8 Configure Signaling Route


Context This section introduces how to configure SS7 signaling route.


terface Related Config, and click the icon in the No.7Route tab on the right.

2. The Create No.7 Route dialog box appears, as shown inFigure 62. Input the parameter values.



FIGURE 62 CONFIGURE SIGNALING ROUTE (1)

3. Click OK to finish configuring the signaling route.

END OF STEPS

Postrequisite Configure signaling office.

5.9 Configuring Signaling Office

Prerequisites The local office and the signaling route are configured successfully.

Context This section introduces how to configure SS7 signaling office.


terface Related Config, and click the icon in the No.7Office tab on the right.

2. The Create No.7 Office dialog box appears, as shown inFigure 63. Input the parameter values.



FIGURE 63 CONFIGURING SIGNALING OFFICE (1)

3. Click OK to finish configuring the signaling office.

END OF STEPS



Chapter6 GB-interfaceConfiguration


>> Overview

>> E1 GB-interface Configuration

>> IP GB-interface Connection

6.1 Overview

Gb interface data configuration includes configuring data channelsbetween iBSC and SGSN, and configuring interconnection betweeniBSC and SGSN.

iBSC supports two interface types: E1 Gb interface and IP Gb in-terface. Different transmission modes have different bottom-layerbearer protocols. Such difference also causes different configura-tions.

6.2 E1 GB-interface Configuration



The following lists relevant boards when E1 Gb interface configu-ration is used.

1. GIPB board9: It is used for E1 Gb interface access and signalingprocessing.

2. UPPB board10: It is used for service data processing.


When E1 Gb interface configuration is used, it is necessary to planthe following data to make them consistent with that at SGSN.

NSE ID

9. Gb Interface Processing Board10. User Plane Processing Board



Starting timeslot and access rate of Gb interface bearer link.

Data link connection identifier of NSVC

NSVC ID

6.2.2 Configuring NSE


Context NSEI is the identifier of the network service entity. Under one NSE,multiple NSVCs can be configured at Gb interface, and multipleBVCs (cell) can be configured at radio interface. Data of such cellscan be transmitted via any NSVC under the same NSEI, and theseNSVC share the load. iBSC can be configured with multiple NSEIs.

Steps 1. In the configuration resource tree, right-click on OMC >GERAN Subnetwork > BSC Managed Element > ConfigSet > BSC Function > Gb Interface Related Config >SGSN Office > NSE Config, and select Create > NSE, asshown in Figure 64.

FIGURE 64 CONFIGURING NSE (1)

2. Click NSE, and the Create NSE dialog box appears, as shownin Figure 65. Input the parameter values.

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

Type of sub-network: For E1 Gb, select Frame relay.


Chapter 6 GB-interface Configuration


3. Click OK to finishing configuring NSE.

END OF STEPS

Postrequisite Configure BRCH.

6.2.3 Configuring BRCH


2. The Gb interface PCM line information is configured on the GIPBboard successfully.

Context BRCH is the physical channel of Gb interface.

Steps 1. In the configuration resource tree, right-click on OMC >GERAN Subnetwork > BSC Managed Element > ConfigSet > BSC Function > Gb Interface Related Config >SGSN Office > BRCH Config, and select Create > BRCH,as shown in Figure 66.



FIGURE 66 CONFIGURING BRCH (1)

2. Click BRCH, and the Create BRCH dialog box appears, asshown in Figure 67. Input the parameter values.

Link: Make sure that all BRCHs on GIPB differ from eachother.

Unit: GIPB unit number, and the GIPB processes thisBRCH.

CPU ID: CPU number, and the CPU processes this BRCH.

PCM timeslot: The minimum timeslot number of theBRCH, it must be consistent with that at SGSN.

Access rate: Number of BRCH's timeslots, it must be con-sistent with that at SGSN.

MCC start timeslot: The value range is 0 ~ 127. ForBRCHs on one CPU of GIPB, the range of [MCC start times-lot, MCC start timeslot + Access rate] can not be over-lapped.



FIGURE 67 CONFIGURING BRCH (2)

3. Click OK to finish configuring the BRCH.

END OF STEPS

Postrequisite Configure NSVC.

6.2.4 Configuring NSVC

Prerequisites NSE is configured successfully.

Context NSVC is the virtual channel at Gb interface. One BRCH can beconfigured with one or multiple NSVCs.

Steps 1. In the configuration resource tree, right-click on OMC >GERAN Subnetwork > BSC Managed Element > ConfigSet > BSC Function > Gb Interface Related Config >SGSN Office > NSE Config > NSE ID, and select Create >NSVC, as shown in Figure 68.



FIGURE 68 CONFIGURING NSVC (1)

2. Click NSVC, and the Create NSVC dialog box appears, asshown in Figure 69. Input the parameter values.

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

DLCI: It must be consistent with that at SGSN.



FIGURE 69 CONFIGURING NSVC (2)

3. Click OK to finishing configuring NSVC.

END OF STEPS

Postrequisite None

6.3 IP GB-interface Connection



The following lists relevant boards when IP Gb interface configu-ration is used.

1. IPGB board11: It is used for IP Gb interface access and dataissuing at control plane and user plane.

2. UPPB board: It is used for service data processing.

11. IP Gb interface Board




When IP Gb interface configuration is used, it is necessary to planthe following data to make them consistent with that at SGSN.

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 end-point.

Signaling weight

Data weight

For dynamic NSE configuration:

Pre-configured SGSN IP address.

Pre-configured SGSN UDP port number

6.3.2 Configuring RPU Interface


Context Configure RPU interface, that is, configure the virtual IP addressof iBSC.




Board function type: Select RPU.


Subnet mask: 255.255.255.255




3. Click OK to create the RPU interface, as shown in Figure 71.


END OF STEPS

Postrequisite Configure IPGB interface.



6.3.3 Configuring IPGB Interface


2. The IPGB board is configured successfully.

Context This section introduces how to configure the IP Gb interface ad-dress.




Board function type: Select IPGB.

MAC address: Input the MAC address of the GIPI rearboard's network port.


Subnet mask: Set this parameter according to planneddata.

FIGURE 72 CONFIGURING IPGB INTERFACE (1)



3. Click OK to create the IP Gb interface.

END OF STEPS

Postrequisite Configure static route.

6.3.4 Configuring Static Route

Prerequisites The IPGB interface address is configured successfully.

Context When the IP address (at most four IP addresses can be configured)of IPGB interface is in the different network segment from that ofiBSC and SGSN, it is necessary to configure static route. If no IPaddress of IPI interface is in the different network segment fromthat of iBSC and MSC, it is not necessary to configure static route.


Function > IP Related Config, and click the icon in theStatic Router tab on the right.

2. The Create Static Router dialog box appears, as shown inFigure 73. Input the parameter values.

Static router prefix: Set this parameter according toplanned data.

Static router subnetmask: Set this parameter accordingto planned data. For example, set Static router prefix tobe 192.168.1.0, and set Static router subnet mask to be255.255.255.0. It indicates that, for SGSNs of which theIP address is within [192.168.1.1, 192.168.1.254], iBSCsends data to these SGSNs via the current route.

Next hop type: Select IP.

Next hop IP address: Set this parameter according toplanned data. It means the IP address of the router orSGSN12.

12. When there is no router between iBSC and SGSN.



FIGURE 73 CONFIGURING STATIC ROUTE

3. Click OK to finish configuring the single static route.

END OF STEPS

Postrequisite Perform configuration related to Gb interface.

6.3.5 Gb Interface RelatedConfiguration

6.3.5.1 Configuring NSE


Context NSEI is the identifier of the network service entity. iBSC can beconfigured with multiple NSEIs.

Steps 1. In the configuration resource tree, right-click on OMC >GERAN Subnetwork > BSC Managed Element > ConfigSet > BSC Function > Gb Interface Related Config >SGSN Office > NSE Config, and select Create > NSE, asshown in Figure 74.




2. Click NSE, and the Create NSE dialog box appears, as shownin Figure 75. Input the parameter values.

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 forpoint-to-point private network. Manual negotiation be-tween iBSC and SGSN is required, that is, configuring thecombination of NSVC's endpoints manually.

Pre-configured SGSN IP address: IP address of SGSN.This parameter must be configured for dynamic configura-tion.

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




3. Click OK to finish configuring NSE.

END OF STEPS

Postrequisite Configure IPGB endpoint.

6.3.5.2 IPGB

Configuring IPGB Local EndpointPrerequisites NSE is configured successfully.

Context Configuring IPGB's local endpoint includes configuring the virtualaddress of RPU at iBSC and the UDP port number interconnectedwith SGSN.

Steps 1. In the configuration resource tree, right-click on OMC >GERAN Subnetwork > BSC Managed Element > ConfigSet > BSC Function > Gb Interface Related Config >SGSN Office > IPGB Endpoint Config, and select Create >IPGB Endpoint, as shown in Figure 76.



FIGURE 76 CONFIGURING IPGB LOCAL ENDPOINT (1)

2. Click IPGB Endpoint, and the Create IPGB Endpoint dialogbox appears, as shown in Figure 77. Input the parameter val-ues.

IP address: The virtual address of RPU of iBSC. It mustbe 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.



FIGURE 77 CONFIGURING IPGB LOCAL ENDPOINT (2)

3. Click OK to finish configuring the local endpoint.

END OF STEPS

Postrequisite If NSE adopts the static configuration, then the subsequenttask is configuring the remote endpoint of IPGB.

If NSE adopts the dynamic configuration, then the IPGB con-figuration is completed.

Configuring IPGB Remote EndpointPrerequisites NSE is configured successfully.

Context Configuring IPGB's remote endpoint includes configuring the IP ad-dress and the UDP port number of Gb interface at SGSN, which isinterconnected with iBSC. The remote endpoint is only configuredwhen NSE adopts the static configuration.

Steps 1. In the configuration resource tree, right-click on OMC >GERAN Subnetwork > BSC Managed Element > ConfigSet > BSC Function > Gb Interface Related Config >SGSN Office > IPGB Endpoint Config, and select Create >IPGB Endpoint, as shown in Figure 78.



FIGURE 78 CONFIGURING IPGB REMOTE ENDPOINT (1)

2. Click IPGB Endpoint, and the Create IPGB Endpoint dialogbox appears, as shown in Figure 79. Input the parameter val-ues.

IP address: The virtual address of SGSN. It must be thesame 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.



FIGURE 79 CONFIGURING IPGB REMOTE ENDPOINT (2)

3. Click OK to finish configuring the remote endpoint.

END OF STEPS

Postrequisite None


Related InformationAfter you have completed this course, you

will be able to:

>> Know the relationship between logicalboard and physical board

>> Know the procedure of OMP construc-tion

>> Know the common configuration oper-ation



Chapter7 CorrespondingRelationship betweenLogic Board and PhysicalBoard


TABLE 3 CORRESPONDING RELATIONSHIP BETWEEN LOGIC BOARD ANDPHYSICAL BOARD OF IBSC

Physical Board Name Logic Board Name

IPBB

IPAB

IPGB

GIPI

IPI

IPBB

IPAB

BIPI

IPGB

EIPI EIPI

CHUB CHUB

CLKG CLKG

ICM ICM

CMP CMP

DTB DTB

GLI GLI

BIPB2

AIPB

DRTB2

UPPB2

GUP2

TIPB2


Chapter 7 Corresponding Relationship between Logic Boardand Physical Board

Physical Board Name Logic Board Name

BIPB

DRTB

TIPB

GUP

UPPB

OMP OMP

PSN PSN

SDTB2 SDTB2

SDTB SDTB

SPB2

GIPB2

SPB2

LAPD2

SPB

GIPB

SPB

LAPD

SBCX SVR

UIMC UIMC

GUIM GUIM

UIMU UIMU



This page is intentionally blank.


Chapter8 OMP ConstructionAfter you have completed this chapter, you will know:

>> Overview

>> OMP Configuration Flow

>> Configuring OMP at Serial Port

>> Uploading Configuration File

8.1 Overview

By creating the OMP boot file at NetNumen client, a configura-tion file ompcfg.ini will be generated under the directory ums-svr\tmp\ftp\version\bscX. Here, X reresents the office number,which is configured at background, and it is not the office numberred from the DIP switch of backplane.

When the OMP board is being started, the ompcfg.ini file is readfrom NetNumen server to load the OMP version file. It requires toconfigure parameters for communication between OMP and Net-Numen server, and such parameters include:

IP address of OMP

IP address of NetNumen server

Office number

FTP user name and password

OMP startup mode

8.2 OMP Configuration Flow

Figure 80 shows the OMP configuration flow.

FIGURE 80 OMP CONFIGURATION FLOW



8.3 Configuring OMP at Serial Port

Prerequisites 1. The system is checked and the equipment is powered on.

2. The physical configuration of iBSC is completed. For config-uration details, refer to ZXG10 BSS Base Station SubsystemInitial Configuration Guide.

3. If OMP is of a

07 GB_OC41_E1_0 ZXG10 IBSC Configuration(V6.20.100e) 141

Documents

Transcript of 07 GB_OC41_E1_0 ZXG10 IBSC Configuration(V6.20.100e) 141