CM3G-303-E1 Introduction To The ZXC10 HLRe Data Configuration

CM3G-303-E1 Introduction to the ZXC10
HLRe Configuration
Course Objective：
·Familiar with the configuration and modification of HLRe system
data, office data and roaming data etc
Contents
1 Overview ..................................................................................................................................................... 2
1.1 Overview of Configuration Management System............................................................................. 2
1.2 Basic Configuration Sequence .......................................................................................................... 2
2 Basic Configuration ................................................................................................................................... 2
2.1 Overview........................................................................................................................................... 2
2.2 Configuration Procedure ................................................................................................................... 2
2.3 Physical Configuration...................................................................................................................... 2
2.3.1 Objective ................................................................................................................................ 2
2.3.2 Preliminary Setup................................................................................................................... 2
2.3.3 Detailed Procedure ................................................................................................................. 2
2.3.4 Adding Racks ......................................................................................................................... 2
2.3.5 Adding Shelves....................................................................................................................... 2
2.3.6 Adding Boards........................................................................................................................ 2
2.3.7 Configuring the MP Module Type.......................................................................................... 2
2.3.8 Configuring the MP Module Capacities................................................................................. 2
2.3.9 Configuring the Module/Unit Relationship............................................................................ 2
2.3.10 Configuring IP Interfaces ..................................................................................................... 2
2.4 Unit Attribute Configuration ............................................................................................................. 2
2.4.1 Objective ................................................................................................................................ 2
2.5 Office Configuration ......................................................................................................................... 2
2.5.1 Objective ................................................................................................................................ 2
i
2.5.2 Preliminary Setup ...................................................................................................................2
2.5.3 Detailed Procedure..................................................................................................................2
2.5.4 Configuring Local Office........................................................................................................2
2.5.5 Configuring Signaling.............................................................................................................2
2.5.6 Configuring Adjacent Office...................................................................................................2
2.6 SS7 Data Configuration.....................................................................................................................2
2.6.1 Objective.................................................................................................................................2
2.6.4 Configuring MTP....................................................................................................................2
2.6.5 Configuring SCCP ..................................................................................................................2
2.6.6 Configuring SSN ....................................................................................................................2
2.6.7 Configuring Narrowband Signaling Link ...............................................................................2
2.7 Sigtran Configuration ........................................................................................................................2
2.7.1 Objective.................................................................................................................................2
2.7.4 Configuring SCTP Basic Connection .....................................................................................2
2.7.5 Configuring ASP.....................................................................................................................2
2.7.6 Configuring AS.......................................................................................................................2
2.7.7 Configuring SIO Positioning AS ............................................................................................2
2.8 HLRe Module Configuration.............................................................................................................2
2.8.1 Objective.................................................................................................................................2
2.9 HLRe Type Configuration .................................................................................................................2
ii
2.9.1 Objective ................................................................................................................................ 2
2.10 Mobile Office Configuration........................................................................................................... 2
2.10.1 Objective .............................................................................................................................. 2
2.10.2 Preliminary Setup................................................................................................................. 2
2.10.3 Detailed Procedure ............................................................................................................... 2
2.11 Database Node Configuration ......................................................................................................... 2
2.11.1 Objective .............................................................................................................................. 2
2.11.2 Preliminary Setup ................................................................................................................. 2
2.12 HDBAGENT DBIO Configuration................................................................................................. 2
2.12.1 Objective .............................................................................................................................. 2
2.13 HDBAGENT MP Configuration..................................................................................................... 2
2.13.1 Objective .............................................................................................................................. 2
2.14 DBIO Configuration........................................................................................................................ 2
2.14.1 Objective .............................................................................................................................. 2
2.15 System Parameter Configuration .................................................................................................... 2
2.15.1 Objective .............................................................................................................................. 2
iii
2.15.3 Detailed Procedure................................................................................................................2
2.16 MP Module Configuration...............................................................................................................2
2.16.1 Objective...............................................................................................................................2
2.16.2 Preliminary Setup .................................................................................................................2
3 HLRe Service Configuration .....................................................................................................................2
3.1 Configuring the Carrier......................................................................................................................2
3.1.1 Objective.................................................................................................................................2
3.2 Configuring the MIN/MDN...............................................................................................................2
3.2.1 Objective.................................................................................................................................2
3.3 Configuring the Global Network MAC .............................................................................................2
3.3.1 Objective.................................................................................................................................2
3.4 Configuring SCP Address ..................................................................................................................2
3.4.1 Objective.................................................................................................................................2
3.5 Configuring Call Parameters .............................................................................................................2
3.5.1 Objective.................................................................................................................................2
iv
3.6 Configuring Call Options.................................................................................................................. 2
3.6.1 Objective ................................................................................................................................ 2
3.7 Configuring Number Conversion...................................................................................................... 2
3.7.1 Objective ................................................................................................................................ 2
3.8 Configuring Digits Collection........................................................................................................... 2
3.8.1 Objective ................................................................................................................................ 2
3.9 Configuring Alert Code..................................................................................................................... 2
3.9.1 Objective ................................................................................................................................ 2
3.10 Configuring Remote Access Code .................................................................................................. 2
3.10.1 Objective .............................................................................................................................. 2
3.11 Configuring Authentication............................................................................................................. 2
3.11.1 Objective .............................................................................................................................. 2
3.11.2 Preliminary Setup ................................................................................................................. 2
3.12 Querying Supplementary Service Code .......................................................................................... 2
3.12.1 Objective .............................................................................................................................. 2
v
3.13 Configuring HLRe Capacity............................................................................................................2
3.13.1 Objective...............................................................................................................................2
3.14 Configuring MDN Assignment........................................................................................................2
3.14.1 Objective...............................................................................................................................2
4 Roaming Configuration..............................................................................................................................2
4.1 Overview ...........................................................................................................................................2
4.2 Configuring VLR Address .................................................................................................................2
4.2.1 Objective.................................................................................................................................2
4.3 Configuring MSC Address ................................................................................................................2
4.3.1 Objective.................................................................................................................................2
4.4 Configuring VLR International Roaming ..........................................................................................2
4.4.1 Objective.................................................................................................................................2
4.5 Configuring MSC International Roaming .........................................................................................2
4.5.1 Objective.................................................................................................................................2
vi
4.6 Configuring DB-MIN/MDN Relation............................................................................................... 2
4.6.1 Objective ................................................................................................................................ 2
4.7 Configuring Area............................................................................................................................... 2
4.7.1 Objective ................................................................................................................................ 2
4.8 Configuring VHLR-MIN/MDN Relation ......................................................................................... 2
4.8.1 Objective ................................................................................................................................ 2
5 Configuration Tools.................................................................................................................................... 2
5.1 Overview of Configuration Tools...................................................................................................... 2
5.2 Synchronizing MP Data .................................................................................................................... 2
5.2.1 Objective ................................................................................................................................ 2
5.3 Synchronizing HLRe Server Data..................................................................................................... 2
5.3.1 Objective ................................................................................................................................ 2
5.4 Backing Up and Restoring HLRe ..................................................................................................... 2
5.4.1 Objective ................................................................................................................................ 2
vii
5.5 Configuring Security Variable...........................................................................................................2
5.5.1 Objective.................................................................................................................................2
6 Example of Simplest Configuration ..........................................................................................................2
6.1 Description of Simplest Configuration ..............................................................................................2
6.2 Configuration Preparation .................................................................................................................2
6.3 Data Configuration ............................................................................................................................2
6.3.1 Basic configuration .................................................................................................................2
6.3.2 Service Data Configuration ....................................................................................................2
6.3.3 Roaming Data Configuration..................................................................................................2
viii
1 Overview
Key Points:
z Basic configuration sequence
1.1 Overview of Configuration Management System

The data configuration management system is a database management system with
complete functions and is used to manage the resources of the switch. It has visual and
friendly interfaces and provides the required configuration data for the normal
operation of the HLRe, such as the system subscriber capacity, inter-office signaling
mode, and supported service types. The data configuration determines the operation
mode and status of the switch. It is the core part of the whole HLRe system and the
most frequently used part in the background maintenance system.
1.2 Basic Configuration Sequence

The ZXC10-HLRe configuration database is very large, and the data is complicated
and interrelated. Therefore, data must be configured in a specific order. Figure 1.2-1
shows the basic configuration sequence of the ZXC10-HLRe.
Basic configuration
Service configuration
Roaming configuration
Data synchronization
and backup
Figure 1.2-1 Basic Data Configuration Sequence of the HLR
1
CM3G-303-E1 Introduction to the ZXC10 HLRe Configuration
Specific steps:
1. Basic configuration: Includes physical configuration, switching office

configuration, SS7 data configuration, and Sigtran configuration.
2. Service configuration: Includes HLRe office capacity configuration, MDN/MIN

number segment configuration, call parameter and option configuration,
authentication configuration, remote access code configuration, SCP address
configuration, and MDN allocation configuration.
3. Roaming configuration: Includes MSC address configuration, VLR address

configuration, MSC international roaming configuration, VLR international
roaming configuration, area configuration, MIN/MDN and data node, and
virtual HLR relation configuration.
4. Data synchronization and backup: Use the backup tool to synchronize data
configuration from background to the foreground, and back up configured data.
2
2 Basic Configuration
Key points
· Overview of basic configuration
· Configuration procedure
· Physical configuration
· Unit attribute configuration
· Exchange configuration
· SS7 data configuration
· Sigtran configuration
· HLRe module configuration
· HLRe type configuration
· Mobile office configuration
· Database node configuration
· HDBAGENT DBIO configuration
· HDBAGENT MP configuration
· DBIO configuration
· System parameter configuration
· MP module configuration
2.1 Overview
As an exchange, to communicate with other entities in the network, HLRe needs to be
configured with relevant data, including exchange configuration, mobile office
configuration, HLRe system type and HLRe module configuration. To interwork with
NE in the SCN domain, HLRe needs to be configured with SS7 data. To interwork with
NE in the IP domain, HLRe needs to be configured with Sigtran.
3
2.2 Configuration Procedure

Because a lot of data needs to be configured and they are related with each other, it is
necessary to follow the sequence to configure data, especially for new office.
Generally, configuring new office needs to follow the sequence:
1. Physical configuration: Module → Rack → Shelf → Slot
2. Own exchange configuration: Own exchange → Signaling → Adjacent office
3. SS7 data configuration: MTP → SCCP → SSN → Narrowband signaling
4. Sigtran configuration
5. Node configuration of modules and relation configuration of modules
S Caution:
Because a lot of data needs to be configured and they are related with each other, it is
necessary to follow the above sequence strictly to configure data including modifying
configuration.
2.3 Physical Configuration
2.3.1 Objective
The HLRe service function requires the support of hardware system. Physical
configuration is to configure hardware platform attributes and functions of HLRe
through the background interface including attributes of rack, shelf, board, attributes
and functions of MP module, relation between peripheral unit and MP module,
communication mode and port of HLRe entity with other entities in the network.
2.3.2 Preliminary Setup

· The O&M server and the O&M client work normally.
· The database is correctly connected.
· The hardware installation of the foreground is completed successfully, cables are

connected correctly and safely, and the foreground is powered on normally.
· The communication between the foreground and background is normal.
4
Chapter 2 Basic Configuration
2.3.3 Detailed Procedure
The sequence of physical configuration is: Add rack → Add new shelves for the rack
→ Configure circuit board for shelves → Configure MP module type → Configure MP
capacity → Configure module/unit relation → Configure IP interface
Here follow the configurations in each step.
2.3.4 Adding Racks
Log in to the ZTE Unified Management System platform. Select Application →

Configuration to enter the Configuration Management window as shown in Figure
2.3-1.
Figure 2.3-1 Main Interface of Configuration Management
From the navigation tree in Figure 2.3-1, expand Base data configuration → Node
configuration and right-click Physical configuration to pop up the menus as shown in
Figure 2.3-2.
5
Figure 2.3-2 Shortcut Menu of Adding IP Rack
Select Add IP Rack to pop up the Add Rack window as shown in Figure 2.3-3.
Figure 2.3-3 Interface of Adding an IP Rack
Input 1 in Rack, select IP Rack as RackType and click OK to add the rack
configuration. The window after the configuration is shown in Figure 2.3-4.
6
Figure 2.3-4 Adding an IP Rack Finished
2.3.5 Adding Shelves
In Figure 2.3-4, select the newly added rack and right-click it to pop up the menus as
shown in Figure 2.3-5.
7
Figure 2.3-5 Shortcut Menus of Adding Shelves
Select Add Shelf to add shelves of the rack as shown in Figure 2.3-6.
Figure 2.3-6 Selecting Shelf Type
Configure the location and type of shelves. Because OMP is in slot 11 on shelf 2 on
rack 1, the first shelf added for new deployment must be shelf 2. The type of shelf is
8
BCTC Shelf by default.
After the configuration, click OK to add the shelf as shown in Figure 2.3-7.
Figure 2.3-7 Shelf Configured
2.3.6 Adding Boards
The board types available to the HLRe system are shown in Table 2.3-1.
Table 2.3-1 Board Types Available to HLRe
Logical Board Name on

Configuration Description Slot No.
Board Background
One system is configured with one pair of
OMP MP/2 In slots 11/12 on shelf 2 on rack 1
active/standby OMPs and RPU module.
Any slots except slots 13/14 and
Configure them in pairs according to the capacity.
SMP MP/2 slots occupied by other boards
Each pair of boards can bear 200,000 subscribers.
which are fixed
CLKG CLKG Configure one pair for one system. In slots 13/14 on shelf 2 on rack 1
If HLRe is embedded with SGW, it is necessary to Usually in slots 5/6 and 11/12,
SPB SPB configure SPB board according to the system however the fixed boards in these
capacity to interwork NE in SS7. slots have the priority
9
Logical Board Name on

Configuration Description Slot No.
Board Background
USI USI Configure one pair for one system. In slots 3/4 on shelf 2 on rack 1
Configure one pair for one system for connecting IP
SIPI SIG In slots 1/2 on shelf 2 on rack 1
signaling network.
UIMC UIM Configure one pair for one shelf. In slots 9/10 of each shelf
Configure one pair for one system, for tandem of
CHUB CHUB In slots 15/16 on shelf 2 on rack 1
control plane with three shelves above.
In Figure 2.3-7, select the proper slot according to the rules in Table 2.3-1 and
right-click it. For example, add OMP, select slot 11 and right-click it to pop up the
window as shown in Figure 2.3-8.
Figure 2.3-8 Shortcut Menus for Adding Boards
Select Add Board to add boards as shown in Figure 2.3-9.
10
Figure 2.3-9 Selecting Boards
Add other boards as required and the window after configuration is shown in Figure
2.3-10.
Figure 2.3-10 Boards Configured
11
Configure SIPI and USI in active/standby mode. Add a board in a slot manually,
right-click this board and select 1+1 backup mode. The standby board will be added
automatically as shown in Figure 2.3-11.
Figure 2.3-11 1+1 Backup Mode Configuration Interface
2.3.7 Configuring the MP Module Type
After configuring the MP board, configure the MP module type. In Figure 2.3-10,
select the MP board in slot 11 and right-click it as shown in Figure 2.3-12.
12
Figure 2.3-12 Shortcut Menu of Configuring MP Module Type
Select Configure Module Type to enter the Configure module type (read only)
window as shown in Figure 2.3-13.
Figure 2.3-13 Configuring MP Module Type
13
Select CPU 1 and double-click it to pop up the Configure module type window as
Figure 2.3-14 Selecting Board Type
Generally, module 1 is configured as OMP and module 2 is configured as RPU. After

the configuration is finished, the window is shown in Figure 2.3-15.
14
Figure 2.3-15 Interfaces after Selecting Board Type
Configure the type of MP in slot 7 as SMP, with the configuration method as shown in
the above figure.
2.3.8 Configuring the MP Module Capacities
In Figure 2.3-10, select MP in slot 11 and right-click it as shown in Figure 2.3-16.
15
Figure 2.3-16 Constant Configuration Window
Select Configure Content Const to pop up the Configure Content Const window as
16
Figure 2.3-17 Constant Configuration Window
Module: Module number in the Configure module type window
From OMP: Select Yes to download data from OMP otherwise the data cannot be
downloaded.
VUserMax: Maximum subscribers supported by module, configured as required. It is

50,000 by default and the maximum number is 200,000.
VOffice: Maximum adjacent offices supported by the system.
All above parameters can adopt the default. Configure the data of SMP in slot 7 in the
same way.
2.3.9 Configuring the Module/Unit Relationship
OMP is the control management module of the entire HLRe. Only after configuring
other peripheral boards subordinate to OMP, OMP can monitor the running of the
entire system and can ensure the stable running.
In Figure 2.3-10, select MP in slot 11 and right-click it to pop up the menus as shown
17
in Figure 2.3-18.
Figure 2.3-18 Shortcut Menu of Configuring Module/Unit Relationship
Select Configure Module/unit relationship and double-click the OMP module in

Module Type column. Then, all boards subordinate to this module are shown in the
Available Unit column as shown in Figure 2.3-19.
18
Figure 2.3-19 Configuring Module/Unit Relationship
Select all boards and click Add to add all boards to the right frame. The configuration
result is shown in Figure 2.3-20.
19
Figure 2.3-20 Configuring Module/Unit Relationship Finished
After the configuration, click Close to exit the module/unit relationship configuration.
2.3.10 Configuring IP Interfaces
If HLRe needs to communicate with other NE’s in the IP signaling network through the
IP mode, it is necessary to configure IP interfaces, including IP address of SIPI, virtual
address of SMP and IP address of USI.
In Figure 2.3-10, select the Physical configuration node and right-click it to pop up
the IP address configuration menus as shown in Figure 2.3-21.
20
Figure 2.3-21 Shortcut Menu of Configuring IP Interface
Select Config IP Interface to pop up the Configure IP Interface (read only) window
as shown in Figure 2.3-22.
21
Figure 2.3-22 Main Interface of Configuration Management
Select SMP and click Add to pop up the Add IP Interface (read only) window as
22
Figure 2.3-23 Configuring Virtual Address of SMP
For example, set IpNo to 1 and input 192.200.99.160 in IpAddr, which must be
consistent with the local IP address when other office configures association and be in
the same network segment as the opposite IP address. The subnet mask and broadcast
address adopt the default configuration.
The former four bits of MAC address are fixed. The fifth bit of MAC address is D0 –
FF. The sixth bit of MAC address has no restriction. Usually the MAC address of a
virtual address is all 0's.
The configuration procedure of SIPI IP interface is similar to SMP configuration. The

IP address of SIPI must be in the same network segment where SMP IP address is
found.
SMP communicates with USI through the back plane of BCTC shelf. To make SMP
access physical database and synchronize data between memory database and physical
database, configure 191-panel address of USI to interwork with HDBAgent. Refer to
the SMP configuration procedure for the configuration.
y Note:
HDBAgent communicates with DBIO through fixed IP address [191.office ID.node
23
ID.1]. To realize the communication between SMP and HDBAgent, it is necessary to

configure USI route gateway address i.e., configure 191 panel IP address of USI.
2.4 Unit Attribute Configuration
2.4.1 Objective
If HLRe is embedded with SGW, the signal transmission for the communication
between HLRe with the entity in SS7 adopts E1 or T1. Therefore, it is necessary to
configure the relevant properties according to the actual transmission.


The parameters in this interface are usually adopted by default. No modification is

required.
2.5 Office Configuration
2.5.1 Objective
The exchange configuration mainly includes two parts, one is the configuration of local
exchange and the other is the configuration of adjacent exchange.


24
The procedure of configuring exchange is: Own exchange → Signaling → Adjacent

office. The following details the specific contents of respective configuration items.
y Note:
HLRe needs not to be configured with SIP exchange.
2.5.4 Configuring Local Office
Select Office configuration to enter the default interface Configuration of Local

Office as shown in Figure 2.5-1.
Figure 2.5-1 Local Office Configuration
Test Code: Sequence (less than 15 digits) used for testing the messages between the
current office and the adjacent office.
Exchange Office Type: Select one or multiple types for local exchange according to
the actual situation and local office requirements.
25
Basic Network Type: Select the network type of local exchange as required.
Interface Network Type: Network type when the NE serves as the interface network
SPC Type: Exclusive choice. Select one according to actual conditions.
Restart Time: Set as required. When SPC is set to Signaling End Point (SEP),
Restart Time does not need to be configured.
Input or select data in the tab and click to complete the data configuration of
local exchange.
2.5.5 Configuring Signaling
In Figure 2.5-1, select Signaling Configuration to enter the Signaling Configuration

tab as shown in Figure 2.5-2.
Figure 2.5-2 Signaling Configuration Page
Network Type: It is the Network Type displayed in the Configuration of Local Office
tab.
14-/24-bit SPC: 14-bit or 24-bit SPC can be selected. ZXC10 can be compatible with
26
the two SPCs. Both kinds of codes consist of three sub codes. Select the SCP type as
required and input the code.
Network Appearance: It is the network appearance of local exchange. The network

appearance of NE’s of the same type keeps consistent.
Region Code: It is an identifier for this region.
User Type: User type that can be processed in the signaling system. Multiple choices
are allowed. Usually for HLRe NE, only selection of SCCP User is enough.
Input SPC code, network appearance and region code as required, select user type and
click to complete the signaling configuration.
2.5.6 Configuring Adjacent Office
Adjacent exchange refers to the exchange office that has signaling link connections
with the current exchange office. The signaling link can be either SS7 or IP link.
Adjacent exchange configuration is used to establish the signaling link relationship
between the adjacent exchange and the local exchange.
In Figure 2.5-1, select Adjacent Office Configuration to enter the Adjacent Office
Configuration tab as shown in Figure 2.5-3.
Figure 2.5-3 Interface for Configuring Adjacent Offices
27
Click to enter the Add Adjacent office information window shown in Figure
2.5-4.
Figure 2.5-4 Adding Adjacent Office
Adjacent Office ID: A numeric sequence used to identify the adjacent exchange,
between 1 and 256.
Adjacent Office Name: It can be set according to the office network.
Sub-service Field (SSF): It is a No.7 signaling concept. The options include national
SPC, national standby SPC, international SPC and international standby SPC.
Signaling Point Code (SPC): 14-bit or 24-bit SPC can be selected. ZXC10 can be
compatible with the two SPCs. In China, it is 24-bit SPC. There are two modes:
decimal system and binary system. The system can get the binary code automatically
after inputting the decimal code.
Adjacent Office Network Type: It is the network type of adjacent office and is selected
according to the actual situation of adjacent office.
Toll area code: The toll area code is the area code of the adjacent exchange.
28
SCP Type: It indicates whether the adjacent exchange serves as a signaling point,
signaling transfer point or signaling point/signaling transfer point.
Protocol Type: It includes Chinese Standard, ITU-T Standard and ANSI Standard.
Connection Mode: The associated mode is adopted if there is an associated signaling

link between the local exchange and the adjacent exchange. Otherwise, the
quasi-associated mode is adopted.
Field Type: It is the domain type used by the service between local exchange and
adjacent office, including SCN (circuit domain) and IP domain. IP domain can be used
only between 3G devices.
Mark: It indicates the code type and other properties.
Adjacent Office Type: It indicates the type of the adjacent office. Please select it as
required.
For example, to add the adjacent office MSCe and to adopt the associated IP signaling
mode with the local exchange. The Add adjacent office information window is
Figure 2.5-5 Interface for Configuring Adjacent Office Parameters
29
After the data configuration, click OK to finish adding adjacent offices and return to
the window shown in Figure 2.5-4. Add other adjacent offices and if it is unnecessary
to add more adjacent offices then click Cancel to exit the Add adjacent office
information window. The window that appears after finishing adding the adjacent
offices is shown in Figure 2.5-6.
Figure 2.5-6 Adding Adjacent Offices Finished
2.6 SS7 Data Configuration
2.6.1 Objective
If HLRe is embedded with SGW, to interwork with NEs in SS7, it is necessary to

configure the proper SS7 data.

30
The sequence for configuring SS7 data is as follows:
MTP → SCCP → SSN → Narrowband signaling link.
y Note:
In most cases, it is unnecessary to configure MTP shield and SCCP shield.
2.6.4 Configuring MTP
Click Base data configuration → Node configuration → No.7 data configuration →

MTP configuration from the navigation tree. The MTP Configuration window is
displayed as shown in Figure 2.6-1.
Figure 2.6-1 MTP Configuration Interface
MTP configuration sequence: Signaling link set → Signaling link → Signaling route
31
→ Signaling office direction. The sequence of deleting configuration is reverse.
The default tab of MTP configuration is about the signaling link set configuration.
1. Signaling link set configuration
The default tab in Figure 2.6-1 is the signaling link set configuration tab.
Signaling Link Group: It is the set of signaling links connecting two signaling
points. Multiple signaling links between a local exchange and an adjacent office
form a signaling link set.
Associated Office ID: It is the adjacent office directly connected by the current
signaling link set, namely, the exchange directly connected through SS7 link in
the adjacent office configuration.
Link Number: It takes effect after the signaling link configuration.
Signaling Link Group Type: It is configured in the signaling link configuration

and takes effect after the configuration of signaling link.
As shown in Figure 2.6-1, click to enter the Add signaling link group
window shown in Figure 2.6-2.
Figure 2.6-2 Signaling Link Group Configuration
For example, for the MSCe offices configured in the above adjacent office
configuration, it is necessary to configure the signaling link sets between them.
32
Select Signaling Link Group 1 and Associated Office ID 2 and click OK to

configure signaling link as shown in Figure 2.6-3.
Figure 2.6-3 Signaling Link Group Configured
y Note:
A link set can be deleted only when it contains no signaling link and this link set does
not exist in any signaling route.
One adjacent office can be configured with one signaling link set only.
2. Signaling link configuration
As shown in Figure 2.6-1 click the Signaling Link Configuration tab shown in
Figure 2.6-4.
33
Figure 2.6-4 Signaling Link Configuration
Signaling Link No: The serial number allocated by the system to the signaling
link uniformly.
Signaling Link Group: It is the link group number to which this link belongs.
Module No.: It refers to the number of SMP module processing this link
signaling messages.
Link Code: The code of a signaling link in a signaling link set should be
consistent with that in the peer office. The code range is 0 - 15.
Carrier Link Type: It includes TDM Signaling Link 1 and IP Signaling Link.
Usually, SS7 link is connected from SPB. Therefore, its carrier link type is set to
TDM Signaling Link 1.
Signaling Link Type: It includes 64K narrow-band signaling link, n*64K

narrow-band signaling link, 2M narrow-band signaling link and M2PA
signaling link.
Whether link is self-loop or not: This option works only after the physical link
is self-looped.
34
In Figure 2.6-4, click to enter the Add signaling link window as shown in
Figure 2.6-5.
Figure 2.6-5 Adding Signaling Link
For example, select 1 in Signaling Link No., 64k narrow-band signaling link in
Signaling Link Type, 1 in Signaling Link Group, 0 in Link Code, 3 in Module
No. and TDM Signaling Link 1 in Carrier Link Type and click OK to add the
signaling link. The window after the addition is shown in Figure 2.6-6.
35
Figure 2.6-6 Adding Signaling Link Finished
y Note:
When selecting link code, it is required to keep it be consistent with that of the opposite
office; otherwise, the signaling link cannot work normally. The signaling ink can be
deleted only after deactivation.
3. Signaling route configuration.
As shown in Figure 2.6-1, click Signaling Rout Configuration to enter the

Signaling Route Configuration tab shown in Figure 2.6-7.
36
Figure 2.6-7 Signaling Route Configuration Interface
Signaling Route No.: The serial number allocated by the system to the signaling
route uniformly.
Signaling link set 1 and Signaling link set 2: A signaling route can contain two
signaling link sets and they shall be specified here.
Link Alignment Mode: It indicates the signaling link set arrangement mode on
a signaling route. Generally, Random Order is selected.
As shown in Figure 2.6-7, click to enter the Add signaling route window
37
Figure 2.6-8 Adding Signaling Route
Select 1 in Signaling Route No., 1 in Signaling Link Group 1, null in

Signaling Link Group 2 and Random Order in Link Alignment Mode and
click OK to add signaling route. The window that appears after the
configuration is shown in Figure 2.6-9.
38
Figure 2.6-9 Adding Signaling Route Finished
y Note:
The signaling route cannot be modified and deleted after being used at the signaling
office direction configuration.
4. Signaling office direction configuration
As shown in Figure 2.6-1, click Signaling Office ID Configuration to enter the

Signaling Office ID Configuration tab shown in Figure 2.6-10.
39
Figure 2.6-10 Signaling Office Direction Configuration Interface
Signaling Office ID: The number assigned uniformly by the system to all the
signaling office directions
Normal Route: The signaling route used in normal conditions. It is the shortest
route among all signaling routes to the peer exchange.
Assistant Route 1: It is selected when the normal route fails. Generally, it is

longer than the normal route.
Assistant Route 2: Assistant route 2 is selected when assistant route 1 fails.

Generally, it is longer than assistant route 1.
Assistant Route 3: Assistant route 3 is selected when assistant route 2 is not

through. It is longer than assistant route 2.
As shown in Figure 2.6-10, click to enter the Add signaling office ID

40
Figure 2.6-11 Adding Signaling Office ID
Select the signaling office ID to be added and the route mode of this signaling
office ID, such as normal route and alternative routes 1, 2 and 3.
For example, the adjacent office 2 MSCe communicates with the local exchange
through SS and, so the office direction needs to be added here. Select 2 as
Signaling Office ID, 1 as Normal Route and Null as Assistant Route and click
OK to add the signaling office. The window after the configuration is shown in
Figure 2.6-12.
41
Figure 2.6-12 Signaling Office Direction Configured
2.6.5 Configuring SCCP
The SCCP configuration covers the GT selector and GT data.
The function of GT number configuration is to serve SCCP routing. In the CDMA

system, MAP signaling between entities in SS7 and HLRe in the network is sent via
SCCP. All entities are directly connected. So such signaling can also be transferred via
signaling transfer points. After SCCP receives messages from the MAP application
layer, it will send, receive, or transfer these messages according to the routing labels in
the messages.
The function of GT translation is to translate the routing label in the GT number format
offered by the application layer into the destination signaling point or the GT format of
STP and the DPC + SSN format (global name format and destination signaling point
code + subsystem number), and select the GT format or the DPC+SSN format for
transmission according to the actual network transmission characteristics.
HLRe usually needs only three kinds of GT selectors as shown in
Table 2.6-1.
42
Table 2.6-1 GT Selectors of HLRe System
GT
Numbering Translation
Translation Configuration Description
Plan Type
Selector
It is used to call route selection and short
ISDN/telephon
message terminating route selection. In this
1 e numbering 0
selector configure MDNs of all subscribers
plan 1
belonging to this HLRe and point to this HLRe.
Used for mobility management route selection,
short message notification response, short
message originating and terminating response.
In this selector configure IMSIs of all
Land mobile subscribers belonging to this HLRe and point to
2 numbering 0 this HLRe.
plan 6 Configure MC number to point associated MC
or STP (MC non associated).
Configure MSC number to point associated
MSC or STP (MSC non associated).
Configure HLRe number of this office.
Used for transferring short message or short
ISDN/telephon message notification.
3 e numbering 128 In this selector configure MDNs of all
plan 1 subscribers belonging to this HLRe and point to
the associated MC or STP (MC non associated).
Click Base data configuration → Node configuration → No.7 data configuration →

SCCP configuration from the navigation tree. The SCCP Configuration window is
displayed shown in Figure 2.6-13.
43
Figure 2.6-13 SCCP Configuration Interface
1. GT selector configuration
In Figure 2.6-13, the default tab is the GT Translation Data tab. Click to
enter the Add GT translation selector (read only) window as shown in Figure
2.6-14.
44
Figure 2.6-14 GT Translation Selector Configuration
Interface parameter description:
GT Translation Selector: It is the unique number identifying GT selector,

ranges from 1 to 255 starting from 1. The configured GT selector is not
contained in this drop-down list box.
GT Type: It includes GT1 – GT4. Usually, it is GT4.
Country Code: It is the country code. If a GT number contains country code, it

is considered as a national GT number and the GT translation is performed with
the national maximum and minimum lengths. Otherwise, the GT translation is
performed with the international maximum and minimum lengths.
Numbering Plan: It is the numbering plan to which the GT selector belongs.
Address Attribute: It includes international number and national number.

Usually, the international number is selected.
45
GT Translation Selector Type: It can be 0 or 128.
National Minimum/Maximum Bit Length: The minimum and maximum bit

lengths of national GT number are 5 and 15 respectively.
International Minimum/Maximum Bit Length: The minimum and maximum

bit lengths of international GT number are 5 and 15 respectively.
Match Direction: It includes Minimum match and Maximum match. Usually,

Maximum match is selected by default.
Use default GT when GT is not found: If the SCCP GT number in this selector
cannot be found, this translation fails usually. When this option is selected, the
translation result is replaced by the default GT number. The precondition is that
user adds the default GT number in this selector. The default GT number is
configured in the selector attribute.
Configure the three necessary GT selectors of HLRe according to
Table 2.6-1. The windows are shown in Figure 2.6-15, Figure 2.6-16 and Figure
2.6-17.
46
Figure 2.6-15 GT1 Configuration Interface
47
48
The GT selector configured is shown in Figure 2.6-18.
49
Figure 2.6-18 GT Selector Configured
2. GT translation data configuration
As show in Figure 2.6-13, select the GT Translation Data tab to enter the GT
translation data configuration tab shown in Figure 2.6-19.
50
Figure 2.6-19 GT Translation Data Configuration
As show in Figure 2.6-19 click to enter the Add GT translation data

Figure 2.6-20 Adding GT Translation Data
Taking the configuration of translation data of GT1 for example, according to
51
Table 2.6-1, it is necessary to configure the MDNs of all subscribers belonging

to this HLRe. As show in Figure 2.6-20, set GT Translation Selector to 1, GT
Code to 861330804 and SPC Office ID to 0 and adopt the default for other
options, shown in Figure 2.6-21.
Figure 2.6-21 GT1 Translation Data Configuration
After the configuration, click OK to configure the translation data of GT1.
According to the contents in
Table 2.6-1, configure the translation data of GT2 and GT3.
2.6.6 Configuring SSN
As local addressing information used by SCCP, the SSN is used to identify SCCP users
connected with a single node. When a correct SSN is configured, the SCCP can send
messages to these subsystems, and related functional units will be able to work.
As shown in Figure 2.6-1, click Base data configuration → Node configuration →

No.7 data configuration → SSN configuration from the navigation tree. The SSN
Configuration window is displayed which is shown in Figure 2.6-22.
52
Figure 2.6-22 SSN Configuration Interface
SSN data configuration in the system has been automatically generated upon
completion of the adjacent office configuration. Check whether the SSN configuration
is complete as required after the configuration of adjacent office.
S Caution:
Usually, SSN configuration is automatically generated after the configuration of

adjacent office. Do not modify the configuration at will.
2.6.7 Configuring Narrowband Signaling Link
Configuring narrowband signaling link is to configure the bearer link property at the
bottom layer, to ensure that the signaling link can communicate normally.
This section focuses on the attribute configuration of bearer link of MTP3 on SPB.
y Note:
In the case of Sigtran, when SCTP bearer protocol of IP signaling link is M2UA or
M2PA, the contents in the two tabs M2UA Configuration and M2PA Configuration
need to be configured. At present, the SCTP bearer protocol is usually M3UA, so
53
M2UA or M2PA need not to be configured here.
As shown in Figure 2.6-1, click Base data configuration → Node configuration →

No.7 data configuration → Narrow-band signaling link configuration from the
navigation tree. The default narrowband signaling configuration tab, MTP3 bearer
link configuration, is displayed, shown in Figure 2.6-23.
Figure 2.6-23 Signaling Link Configuration Interface
As shown in Figure 2.6-23, click to enter the Add Type1 Narrow-band

Signaling Link Configuration window, shown in Figure 2.6-24.
54
Figure 2.6-24 MTP3 Bearer Link Configuration
Signaling Link No.: It is configured in configuring MTP. Here select it as required.
SPB Unit No.: It is generated automatically when configuring boards in the physical
configuration.
CPU No.: It is set as required, which is 1 usually.
SPB E1 No.: It is configured according to the actual physical connection, ranging from
0 to 15.
Originating TS No.: It is configured according to the actual physical connection,

ranging from 1 to 31, which ensure that the configurations at the two ends are
consistent.
TS number: It is generated by the system by default.
For example, select 1 in Signaling Link No., 0 in SPB E1 No., and 16 in Originating
TS No., and click OK to configure the MTP3 bearer link as shown in Figure 2.6-25.
55
Figure 2.6-25 MTP3 Bearer Link Configured
2.7 Sigtran Configuration
2.7.1 Objective
If HLRe inter works with NEs in IP signaling network through IP signaling, the
corresponding Sigtran data needs to be configured. Specifically, when the domain
attribute of adjacent office is IP, this part of data should be configured.
The O&M server and the O&M client work normally.
The database is correctly connected.
The hardware installation of the foreground is completed successfully, cables are

The communication between the foreground and background is normal.
The sequence of configuring Sigtran is as follows:

56
SCTP basic connection → ASP → AS → AS configuration of SSN positioning → AS

configuration of SIO positioning.
Click Base data configuration → Node configuration → Sigtran configuration

from the navigation tree. The Sigtran Configuration window is displayed, shown in
Figure 2.7-1.
Figure 2.7-1 Sigtran Configuration Interface
2.7.4 Configuring SCTP Basic Connection
If HLRe NE and the NE in IP signaling network need to communicate with MSCe,

basic connection of SCTP must be configured.
As shown in Figure 2.7-1, select SCTP Basic Connection Configuration and click
to enter the Add SCTP basic connection window, shown in Figure 2.7-2.
57
Figure 2.7-2 Adding Basic Connection of SCTP
SCTP Association ID: It is the global ID of association.
Module No.: It is the SMP module No., to which this association belongs.
SCTP Protocol Type: It refers to the SCTP bearer protocol type, including M3UA,
M2UA, SUA, M2PA, IUA, BICC and H248. For HLRe NE, the SCTP bearer protocol
usually selects M3UA.
Opposite-end Office ID: It is the opposite end office ID for the SCTP basic connection.
When the domain property of adjacent office is IP domain, it is necessary to establish
SCTP basic connection with the adjacent office.
Local Port No.: It is the local port No. for establishing association. The local port No
must be consistent with the opposite port No. The port No. ranges from 1 to 65535.
Opposite-end Port No.: It is the opposite port No. for establishing association. The
local port No. must be consistent with the opposite port No. The port No. ranges from 1
to 65535.
58
Outgoing/Incoming Stream Number: It is the outgoing/incoming stream number.

Stream is a unidirectional logical channel in association. The data is transmitted on the
same stream in sequence. It is 16 by default.
MSC Server ID: It identifies an MSC Server.
Coupling Application Property (Association Application Property): It is selected as

required. If one end is Client, the other end is Server.
Maximum Retry Times: SCTP provides the reliable transmission of messages and has
own retransmission mechanism. This configuration item stipulates the maximum retry
times of SCTP. If the maximum retry times are exceeded, the system reports that the
transmission fails. It is 5 by default.
Local IP Address: It is the IP address of SMP to which this association belongs,

configured at the IP address interface configuration. It must be in the network segment
where SIPI IP address is.
Opposite-end IP Address: It is the IP address of the opposite SMP to which the

association belongs.
In Figure 2.7-3, the adjacent office MSCe is 1, port No. is 3000, local IP address is
192.200.99.160, the opposite IP address is 192.200.99.180, and the local end
communicates with MSCe as Server.
59
Figure 2.7-3 SCTP Basic Connection Configuration
After the proper data is configured, click OK to complete the SCTP basic connection
configuration, with the window shown in Figure 2.7-4. You can configure the proper
SCTP basic connection according to the actual networking.
60
Figure 2.7-4 SCTP Basic Connection Configured
2.7.5 Configuring ASP
As show in Figure 2.7-1, select ASP Configuration to enter the ASP (Application
Server Process) tab, shown in Figure 2.7-5.
61
Figure 2.7-5 ASP Configuration Interface
As shown in Figure 107, click to enter the Add ASP information window,
Figure 2.7-6 Adding an ASP Configuration
Application Server Process ID: It is the global ID of ASP.
SCTP Association ID: It is configured in the SCTP Basic Connection Configuration

tab, which can be selected as required.
62
Self-loop or not: Select whether to self-loop ASP.
Locked or not: Select whether to lock ASP.
As shown in Figure 2.7-6, input the proper data and click OK to add ASP, with the
window, shown in Figure 2.7-7.
Figure 2.7-7 ASP Configured
2.7.6 Configuring AS
As shown in Figure 2.7-1, select the AS Configuration to enter the AS configuration

tab, shown in Figure 2.7-8.
63
Figure 2.7-8 AS Configuration Interface
As shown in Figure 111, click to enter the Add AS information.
64
Figure 2.7-9 Adding AS
Application Server No.: It is the global ID of AS.
Load Balancing Mode N/K Value: The load balancing number is N+K. Where, N
indicates that one AS needs at least N ASPs. In case of less than N ASPs, AS cannot
work normally. This option works when the Service Mode is Load Balancing.
Routing Context ID: Use negotiation between two NEs and identify one field of AS
uniquely. This value can be configured at will but the values at the two ends must be
consistent.
Adapting Layer Protocol: It includes M2UA, M3UA, SUA and IUA. Users can select
it as required.
Usage ID: It includes SGP, IPSP_SERVER, IPSP_CLIENT and ASP. Users can
select it as required.
65
Service Mode: It includes OVERRIDE and Load Balancing. Users can select it as
required.
Application Server Supported User Type/Subsystem: It is the user type/subsystem

supported by AS. The options are available after selecting Adapting Layer Protocol.
Application Server Process ID: It is configured in the ASP configuration. Users can
select it as required.
The example of configuration data is shown in Figure 2.7-10. Where the ASP1 is
established between adjacent office MSCe and local office. The application server
identifier is IPSP_SERVER, the adaptation layer is M3UA, the service mode is
OVERRIDE and the user type supported by application server is SCCP User.
Figure 2.7-10 AS Configuration Interface
After the proper data is configured, click OK to complete the AS configuration, with
the window shown in Figure 2.7-11.
66
Figure 2.7-11 AS Configured
2.7.7 Configuring SIO Positioning AS
As shown in Figure 2.7-1, select AS Configuration of SIO Positioning to enter the

AS Configuration of SIO Positioning tab, shown in Figure 2.7-12.
67
Figure 2.7-12 AS Configuration of SIO Positioning
As shown in Figure 2.7-12, click to enter the Add AS configuration of SIO

positioning window, shown in Figure 2.7-13.
Figure 2.7-13 Adding AS Configuration of SIO Positioning
Office ID: ID of the adjacent office
Service Indicator: It identifies the opposite user type of AS, including

SCCP/TUP/ISUP/BICC/ALCAP/H248.
Application Server No.: It is the global number of the corresponding AS.
68
Input the relevant data as required and click OK to complete the relevant configuration
with the window shown in Figure 2.7-14.
Figure 2.7-14 SIO Positioning AS Configured
2.8 HLRe Module Configuration
2.8.1 Objective
Configure all modules of the system, including HDBAgent, DBIO and MAP, ensuring
that data between the foreground and background is consistent.

69
Click Base data configuration → HLRe module configuration from the navigation
tree. The HLRe module configuration window is displayed as shown in Figure 2.8-1.
Figure 2.8-1 HLRe Module Configuration Interface
As shown in Figure 117, click to enter the Add HLRe MODULE window,
70
Figure 2.8-2 Adding a Module
Add module No. as required and select the corresponding module type. For example,
the module types 1, 3 and 4 are HLR MAP, module type 134 is DBIO and module
types 141 and 142 are HDB Agent. The window after the configuration is shown in
Figure 2.8-3.
Figure 2.8-3 Module Configuration
71
2.9 HLRe Type Configuration
2.9.1 Objective
Configure the HLRe system type.

Click Base data configuration → HLRe module configuration from the navigation
tree. The HLRe type configuration window is displayed as shown in Figure 2.9-1.
Figure 2.9-1 HLRe Type Configuration
72
The HLRe system includes three types: As both Master and Charged HLR, as Master
HLR and as Charged HLR.
As Charged HLR only: The HLR system serves as Charged HLR. No service is
loaded when the status of the monitored HLR is normal. Only when the status of the
monitored HLR is down, service of the monitored HLR will be taken over.
As Master HLR only: This HLR system has no disaster recovery function, and can
function only as ordinary HLR.
As both Master HLR and Charged HLR: The HLR system serves as ordinary HLR
when the status of the monitored HLR is normal. When the status of monitored HLR is
down, the service of the monitored HLR will be taken over at the same time.
Enable Monitor: When HLR has disaster recovery function, the monitor function can
be enabled. It is used to monitor all signaling of the master HLR, collect dynamic
information of user and synchronize it to the disaster recovery HLR simultaneously.
In most cases, adopt the defaults. In case of particular requirements, modify the system
type.
In this window, the Country Code (CC), International outgoing prefix and Domestic
outgoing prefix can also be configured.
Country Code (CC): It refers to the country code or region code, consisting of three
digits. For example, The CC of China is 86, CC of America is 1 and that of Hong Kong
is 852.
International outgoing prefix: Prefix for international outgoing calls. It is 00 for

China, 011 for America, 001 for Hong Kong, 0011 for Australia and 810 for Russia.
Domestic outgoing prefix: It is the prefix number for domestic outgoing calls.
Modify Country Code, International outgoing prefix and domestic outgoing prefix as
required.
2.10 Mobile Office Configuration
2.10.1 Objective
Configure the relevant parameters for mobile office of HLRe.
73

Click Base data configuration → Mobile office configuration from the navigation
tree. The Mobile office configuration window is displayed as shown in Figure 2.10-1.
Figure 2.10-1 Mobile Office Data Configuration
Click to enter the Add mobile office (read only) window as shown in Figure
2.10-2.
74
Figure 2.10-2 Adding Mobile Office
HLR Type: It is configured in the HLRe type configuration.
HLR Name: HLR office name
HLR SwitNum: It is the serial No., allocated for each switching center by operator,
ranging from 0 to 255
HLR MarkID: In the CDMA network, MS judges roaming based on a pair of

identification codes (SID, NID). The SID consists of 15 bits. This network first uses the
512 numbers, which are 110010 from bit 14 to bit 9. Each mobile local network is
allocated with one SID number determined by the operators.
HLRIN: Its coding format is MCC+MNC+09+ H0H1H2H3+0000 and the GT code of

national signaling is surely HLRIN.
When HLR Type is Master, some parameters will be grey in color, which cannot be
configured. When HLR Type is Charged, configure the following parameter as shown
in Figure 2.10-3.
75
Figure 2.10-3 Monitored Property Parameter Configuration of Charged HLRe
Long-term Take-over: If it is checked, the disaster recovery HLRe takes over the
service of monitored HLRe when the monitored HLRe status is down. It will take over
the service no matter whether the status of the monitored HLRe recovers. If it is not
checked, the disaster recovery HLRe takes over the service of monitored HLRe only
when the status of the monitored HLRe is down. Once the monitored HLRe status
recovers, the disaster recovery HLRe switches over the service back to monitored
HLRe.
Status of the HLR under supervision: It includes two status: one is normal and the
other is down. Only when the status of the monitored HLR is down, the disaster
recovery HLR takes over the monitored HLR service.
Service Permission: It indicates whether to support the following supplementary

services when the service of the disaster recovery HLR is taken over.
Input the relevant data as required and click OK to complete the mobile office data
configuration, with the window shown in Figure 2.10-4.
76
Figure 2.10-4 Mobile Office Data Configured
2.11 Database Node Configuration
2.11.1 Objective
Configure the HLRe database node.

Click Base data configuration → DataBase mode configuration from the navigation
tree. The Database node configuration window is displayed as shown in Figure
2.11-1.
77
Figure 2.11-1 Database Node Configuration
Click to enter the Add database node window as shown in Figure 2.11-2.
Figure 2.11-2 Adding Database Node
78
Active database name: It is the name of the database.
Active server name: It is the name of database server. You can input the IP address of
database server.
Node: Database Node
Active server node: It is the active node of database server.
Standby server node: It is the standby node of database server.
Database type: It is database type, including SQL Server and ORACLE.
Node capacity (MS): It is the node capacity.
DBIO password: It is null usually.
DBMAP password: It is null usually.
Input the proper data as required, as shown in Figure 2.11-3.
Figure 2.11-3 Database Node Configuration
Click OK to add the database node. The database node configured is shown in Figure
79
2.11-4.
Figure 2.11-4 Database Node Configured
2.12 HDBAGENT DBIO Configuration
2.12.1 Objective
Configure HDBAGENT DBIO node.

Click Base data configuration → HDBAGENT DBIO configuration from the

80
navigation tree. The HDBAGENT DBIO window is displayed as shown in Figure

2.12-1.
Figure 2.12-1 HDBAGENT DBIO Node Configuration
Add nodes 141 and 142 as required. Input 141 and 142 in Node and click Add to add
two nodes to Available node. After all data are added, click to save the data. The
window after the data configuration is shown in Figure 2.12-2.
81
Figure 2.12-2 HDBAGENT DBIO Data Configured
2.13 HDBAGENT MP Configuration
2.13.1 Objective
Configure HDBAGENT MP node.

Click Base data configuration → HDBAGENT MP configuration from the

navigation tree. The HDBAGENT MP window is displayed as shown in Figure 2.13-1.
82
Figure 2.13-1 HDBAGENT MP Node Configuration
Add nodes 141 and 142 as required. Input 141 and 142 in Node and click Add to add
the two nodes to Available node. After all data is added, click to save the data.
The window after the data configuration is shown in Figure 2.13-2.
83
Figure 2.13-2 HDBAGENT MP Data Configured
2.14 DBIO Configuration
2.14.1 Objective
Configure DBIO parameters.

Click Base data configuration → DBIO configuration from the navigation tree. The
DBIO configuration window is displayed as shown in Figure 2.14-1.
84
Figure 2.14-1 DBIO Parameters Configuration
Usually, the DBIO parameters adopt the default setting. No modification is required.
If it is required to be modified due to a particular requirement, set the relevant
parameter as required and click to save the modified data.
2.15 System Parameter Configuration
2.15.1 Objective
Configure system parameters.

85
Click Base data configuration → System parameter configuration from the

navigation tree. The System parameter configuration window is displayed as shown
in Figure 2.15-1.
Figure 2.15-1 Configuring System Parameters
Usually, the system parameters adopt the default setting. No modification is required.
If it is required to be modified due to a particular requirement, set the relevant
parameter as required and click to save the modified data.
2.16 MP Module Configuration
2.16.1 Objective
Configure the SMP module.
86

Click Base data configuration → MP Module configuration from the navigation tree.
The MP module configuration window is displayed as shown in Figure 2.16-1.
Figure 2.16-1 Module configuration interface
Click to enter the Add MP module window, as shown in Figure 2.16-2.
87
Figure 2.16-2 Adding MP
Select the module No. of MPNo_Master, namely, the module No. of SMP. For
example, select modules 3 and 4 and click OK to add the MP mode. The window after
the addition is shown in Figure 2.16-3.
Figure 2.16-3 Adding MP Module Finished
88
3 HLRe Service Configuration
Key points
· Configuring the Carrier
· Configuring the MIN/MDN
· Configuring the Global Network MAC
· Configuring SCP Address
· Configuring Call Parameters
· Configuring Call Options
· Configuring Number Conversion
· Configuring Digits Collection
· Configuring Alert Code
· Configuring Remote Access Code
· Configuring Authentication
· Querying Supplementary Service Code
· Configuring HLRe Capacity
· Configuring MDN Assignment
3.1 Configuring the Carrier
3.1.1 Objective
Configure the information related to the carrier.
89

The communication between the foreground and the background is normal.
1. Click Service data Configuration → Carrier configuration from the navigation

tree.
The Carrier configuration window is displayed as shown in Figure 3.1-1.
Figure 3.1-1 Carrier Configuration
2. Click to enter
The Add carrier dialog box as shown in Figure 3.1-2.
90
Chapter 3 HLRe Service Configuration
Figure 3.1-2 Adding Carrier Information
3. Enter the carrier code and carrier name, and click OK.
The configuration of the carrier is completed. The carrier information

configuration is shown in Figure 3.1-3.
Figure 3.1-3 Carrier Information Configured
91
3.2 Configuring the MIN/MDN
3.2.1 Objective
Configure the Mobile Station Identification Number (MIN) segment and the Mobile
Directory Number (MDN) segment of the subscribers belonging to the HLRe.

Click Service data Configuration → MIN/MDN configuration from the navigation

tree.
The MIN/MDN configuration window is displayed as shown in Figure 3.2-1.
Figure 3.2-1 MIN/MDN Configuration
92
1. MIN configuration
In the MIN configuration tab (default tab in MIN/MDN configuration), click
to enter the Add MIN dialog box as shown in Figure 3.2-2.
Figure 3.2-2 Adding MIN Segment
Enter the start MIN, end MIN, MCC, and MNC, and click OK. For example,
enter 0908400001 in Start MIN, 0908409999 in End MIN, 460 in MCC, and
03 in MNC as shown in Figure 3.2-3.
93
Figure 3.2-3 Adding MIN Segment
The MIN segment configured is displayed as shown in Figure 3.2-4.
Figure 3.2-4 MIN Segment Configured
94
2. MDN configuration
In the MIN/MDN configuration window as shown in Figure 3.2-1, select MDN

configuration.
The MDN configuration tab is displayed as shown in Figure 3.2-5.
Figure 3.2-5 MDN Segment Configuration
Click to enter the Add MDN dialog box as shown in Figure 3.2-6.
95
Figure 3.2-6 Adding MDN Segment
Enter the start MDN and end MDN. For example, enter 8613308400001 in Start
MDN and 8613308409999 in End MDN as shown in Figure 3.2-7.
Figure 3.2-7 Adding MDN Segment (Example)
3. Click OK.
The MDN segment configuration is displayed as shown in Figure 3.2-8.
96
Figure 3.2-9 MDN Segment Configured
3.3 Configuring the Global Network MAC
3.3.1 Objective
Configure the global network Mobile Access Code (MAC).

1. Click Service data Configuration → Global network MAC configuration from

the navigation tree.
97
The Global network MAC configuration window is displayed as shown in

Figure 3.3-1.
Figure 3.3-1 Global Network MAC Configuration
The default range of MACs in the system ranges from 130 to 139. You can add
or delete it according to actual situation.
2. In the Global network MAC configuration window as shown in Figure 3.3-1,
click .
The Add access code MAC window is displayed as shown in Figure 3.3-2.
Figure 3.3-2 Adding MAC
3. Enter the MAC to be added and then click OK.

98
To delete a MAC, select the MAC to be deleted in the window as shown in
Figure 3.3-1 and click .
3.4 Configuring SCP Address
3.4.1 Objective
Configure the Service Control Point (SCP) data related to the HLRe.
The SCP address can be divided into Global Title (GT) and Sub-System Number
(SSN).

1. Click Service data Configuration → SCP address configuration from the

navigation tree.
The SCP address configuration window is displayed as shown in Figure 3.4-1.
99
Figure 3.4-1 SCP Address Configuration
2. Click to enter the Add SCP address data dialog box.
3. Select the address type.
If you select PC_SSN as the address type, the dialog box is displayed as shown
in Figure 3.4-2.
100
Figure 3.4-2 Adding PC_SSN
The following describes the parameters in the dialog box:
Address type: Type of the SCP address. It is PC_SSN.
SCP description: Description of the SCP.
Type: The SSN type of the HLRe.
PC Code: Signaling point code of the HLRe. It is a decimal code converted to

binary code.
SSN: SSN address.
Backup MSCID: Set the backup MSCID information here.
MSC MarkID: MarkID of the backup MSC.
MSC SwitNum: SwitNum of the backup MSC.
If you select GlobalTitle as the address type, the dialog box is displayed as
101
Figure 3.4-3 Adding GT
The following describes the parameters in the dialog box:
Address type: Type of the SCP address. It is Global Title here.
SCP description: Description of the SCP.
Contains signaling point code: If the GT address contains the signaling point
code (SCP), select it and enter the SCP in Signaling point code followed.
Contains subsystem number: If the GT address contains the subsystem number

(SSN), select it and enter the SSN in Subsystem number followed.
Global title setting: Set the mode of the GT.
Coding mode: Coding mode of the GT address.
Coding Plan: The numbering plan adopted by the GT address.
102
Route Setting: Set the route selection mode here.
Address coding: Set the specific GT address here.
Backup MSCID: Backup MSC ID.
MSC MarkID: MarkID of the backup MSC.
MSC SwitNum: SwitNum of the backup MSC.
4. Enter the related parameters according to actual situation and click OK. The
SCP address configured is displayed as shown in Figure 3.4-4.
Figure 3.4-4 SCP Address Configured
3.5 Configuring Call Parameters
3.5.1 Objective
Configure call parameters.
103

1. Click Service data Configuration → Call parameter configuration from the

navigation tree.
The Call parameter configuration window is displayed as shown in Figure

3.5-1.
Figure 3.5-1 Call Parameter Configuration
The Call parameter configuration window contains the following parameters:
Times of new subscriber SSD update retransmission (times): The maximum

number of times the SSD update allowed for new subscribers.
Times of old subscriber SSD update retransmission (times): The maximum
104
number of times the SDD update allowed for old subscribers.
Times to PIN retry (times): The maximum number of times that the PIN can be
re-entered during PIN service operation.
RFC service operations (times): Number of RFC service operations.
RFC access code: The access code of Remote Feature Control (RFC) service.
When a subscriber dials this access code, the system will guide the subscriber to
implement the RFC service.
MDN length (digits): Length of the MDN.
Time of forwarding on no reply (second): The time that the call forwarding on
no reply is triggered.
2. Specify the related parameters and click .
Normally, the default values are used. You can also modify the parameters
according to actual requirements. After modifying the parameters, click .
3.6 Configuring Call Options
3.6.1 Objective
Configure the service options related to calls.

1. Click Service data Configuration → Call options configuration from the

navigation tree.
The Call options configuration window is displayed as shown in Figure 3.6-1.
105
Figure 3.6-1 Call Options Configuration
The Call options configuration window contains the following parameters:
Call permitted when the RUI restricted: When the PIN needs to be entered,
you can specify whether the HLR supports RUI-allowed calls or not.
Call permitted during forwarding registration: When a subscriber activates

the call forwarding service and forwards the incoming call to another subscriber,
he should inform the subscriber to which the call is forwarded and ask for his
consent for the sake of courtesy. This process is courtesy call. When a subscriber
activates the call forwarding service, the CDMA system can automatically
originate a call to the forwarded-to number according to actual requirement,
allowing the called party to query the forwarded-to party. This function can be
implemented when a subscriber activates the Call Forwarding on Busy (CFB),
Call Forwarding Default (CFD), Call Forwarding No Answer (CFNA), and Call
Forwarding Unconditional (CFU).
Information instruction: Whether to notify the forwarded party when a

subscriber subscribes to the CFU or not.
Combine the Pins of SPINI and SPINA: Whether to combine the PIN of
106
SPINI and SPINA services.
Single Delinquent Supported, Restrict Voice Service, Support MAH service

and Support RFC service: Select the above mentioned services as required.
Forwarding tone playback mode: The tone-playing mode of the MSC when
the call to a subscriber is forwarded. It can be:
No tone playback: The HLR does not specify the tone play mode. The MSC
determines the tone play mode.
Parallel tone playback: The tone play mode of the MSC is parallel when the
call is forwarded. Serial tone playback: The tone play mode of the MSC is
serial when the call is forwarded.
Short message bearer service: There are seven short message bearer services
namely, expand protocol enhanced service, cell paging service, cell message
service, voice information notification, roaming notification, failed call
notification, and roaming cancellation notification.
If Roaming notification and Failed call notification are selected, you need to
specify the following parameters:
Roam notification access code: The number of the SMS roaming prompt
center.
FCN access code: The number of the SMS call failure prompt center.
Local SMC address: GT of the local short message service center.
2. Specify related parameters and click .
The call option configuration is completed.
3.7 Configuring Number Conversion
3.7.1 Objective
The HLR may receive a large quantity of numbers of different format when processing
signaling. For unified processing, the HLR converts them into the internal format.
When sending signaling, the HLR converts the numbers from internal format to the
signaling format. The purpose of number conversion configuration is to support the
number conversion.
107
The internal mode means converting the number into the internal format, which is
country code + area code or access code + number.
The signaling mode means converting the number into the format for signaling
transmission.

1. Click Service data configuration → Digit conversion configuration from the

navigation tree.
The Digit conversion configuration window is displayed as shown in Figure

3.7-1.
Figure 3.7-1 Number Conversion Configuration
108
2. Click to enter the Add digit conversion dialog box as shown in Figure
3.7-2.
Figure 3.7-2 Adding Digit Conversion
The Add digit conversion dialog box contains the following parameters:
Selector: Number conversion type. It can be internal mode or signaling mode.

Each mode comprises calling, called, call forwarding, and default (the default
means it can be any of the first three modes). Normally, it is set to default.
Number: The number to be converted.
Min number length: The shortest number in number conversion.
Max number length: The longest number in number conversion.
Delete/modify length: Length of the number deleted or modified.
Diversion method: It can be full replace, add area number, add country area
code, or delete number.
· Full replace: Query the match record of the number to be converted in the
configuration library and use the match record to replace the prefix of the
number to be converted. For example, if the match record of 8613302050001 is
86133→133, the number 8613302050001 will be converted to 13302050001.
109
· Add area number: Query the match record of the number to be converted in the
configuration library and insert the area code into the number to be converted.
The configuration library must specify the position where the area code is
inserted. For example, if the area code is 25, and the match record of 862870251
is 862 → Add area code (Place to be converted: 2), the new number is
86252870251.
· Add country area code: Query the match record of the number to be converted
in the configuration library, and insert the country code and area code into the
number. The configuration library specifies the position where the country code
and area code to be inserted. For example, if the number to be converted is
2870251, and the match record is 28 → Add country code + area code, the new
number is 86252870251 (the country code is 86 and area code is 25).
· Delete number: Query the match record in the configuration library according
to the number to be converted, number type and conversion mode. Delete the
number from the start digit. Suppose the number to be converted is
8613302050001, and the match record is 86 → Delete mode, the new number
will be 13302050001.
Diversion offset: The position from which the number is converted. It is valid
when the diversion method is full replace or adds area number only.
Add/Modify number: The number after conversion.
Number attribute: The properties include digits type, national property,

available property, provision property, encoding design, and encoding plan. Each
property can be specified through configuration management or by the
HLRMAP. For the property to be specified through configuration management,
the value of that property must be provided.
For example, if it is configured that the number attribute is to be specified

through configuration management, you need to enter the value of the number
type. For the functional interfaces provided to the HLRMAP, the system first
judges whether the property is specified through configuration management. If
yes, the value of that property in the configuration library will be output;
otherwise, the value provided by the HLRMAP will be output. The value of each
property should be controlled separately.
110
3. Specify the parameters according to actual situation and click OK.
Figure 3.7-3 Number Conversion Configured
3.8 Configuring Digits Collection
3.8.1 Objective
When the HLR requests that the MSC performs a remote user indicate (RUI) operation,
it collects the control number set to be used.

111
1. Click Service data configuration → Digit collection configuration from the

navigation tree.
The Digit collection control configuration window is displayed as shown in

Figure 3.8-1.
Figure 3.8-1 Number Collection Configuration
The Digit collection control configuration window contains the following

parameters:
Digit Collection Control Value: Allow digits to be received and collected

before the end of the announcement: Accept the numbers received before the
end of the announcement.
Allow digits received before and during an announcement to cut the

announcement off: Stop the announcement once the numbers are received.
Clear Digits: Clear the number pressed by the subscriber so as to enter the new
control key. It is null by default.
112
Enter Digits: Send the number pressed by the subscriber. It is # by default.
Allowed Digits: The numbers that can be pressed by a subscriber. By default all
are selected.
Special Interdigit Time: The special digits that can be pressed by a subscriber.
Maximum Collect and Minimum Collect: The maximum/minimum number of

digits to be collected for the subscriber.
Max Interaction Time: The time allowed to input a string of digits.
Initial Interdigit Time, Normal Interdigit Time and Special Interdigit Time:
The input time for the initial digit, common digits and special digits.
2. Configure the related parameters and click . Normally, default values are
used. You can also modify the related parameters and click .
3.9 Configuring Alert Code
3.9.1 Objective
If a mobile subscriber activates the CFU service and expects to notify the forwarded
subscriber, you can configure the alert data.

1. Click Service data configuration → Alert code configuration from the

navigation tree.
The Alert code configuration window is displayed as shown in Figure 3.9-1.
113
Figure 3.9-1 Alert Code Configuration
The Alert code configuration window contains the following parameters:
Pitch: Pitch of the alert tone. It can be High pitch, Low pitch, or Medium pitch.
Alert Action: Specifies the action after the alert.
Cadence: Cadence of the alert.
2. Configure the related parameters and click . Normally, default values are
used. You can also modify the related parameters according to actual situation,
and then click .
3.10 Configuring Remote Access Code
3.10.1 Objective
Configure the operation authority of the remote agent.
114

1. Click Service data Configuration → Remote interface code configuration from

The Remote interface code configuration window is displayed as shown in

Figure 3.10-1.
Figure 3.10-1 Remote Access Code Configuration
2. Click to enter the Add remote interface code dialog box as shown in
Figure 3.10-2.
115
Figure 3.10-2 Adding Remote Interface Code
3. Enter the node number of the remote agent, authorize it with related right, and
click OK.
The remote agent configured is displayed as shown in Figure 3.10-3.
Figure 3.10-3 Remote Access Code Configured
116
y Note:
The Node No. entered must be consistent with that assigned to the remote node in the
configuration file tcpout.ini. Otherwise, the configuration cannot be valid, and
communication failure may occur.
3.11 Configuring Authentication
3.11.1 Objective
Configure the authentication parameters of the system.

1. Click Service data Configuration → Authorization configuration from the

navigation tree.
The Authorization configuration window is displayed as shown in Figure

3.11-1.
117
Figure 3.11-1 Authentication Configuration
2. Configure the related parameters. Normally, the default configuration is

recommended. You can also modify the related parameters according to actual
situation.
3.12 Querying Supplementary Service Code
3.12.1 Objective
Query the default supplementary service codes of the system.

118
Click Service data Configuration → Supplementary service code configuration

from the navigation tree.
The Supplementary service code configuration window is displayed as shown in

Figure 3.12-1.
Figure 3.12-1 List of Supplementary Service Codes
The Supplementary service code configuration window contains the following

parameters.
ID: ID of the supplementary service.
Name: Name of the supplementary service.
Operation Code: Operation code of the supplementary service.
119
3.13 Configuring HLRe Capacity
3.13.1 Objective
Configure the HLRe capacity.

1. Click Service data Configuration → HLRe office capacity configuration from

The HLRe office capacity configuration window is displayed as shown in

Figure 3.13-1.
Figure 3.13-1 HLRe Office Capacity Configuration
120
2. Click add .
The Add HLRe office capacity dialog box is displayed as shown in Figure
3.13-2.
Figure 3.13-2 Adding HLRe Capacity
Because the service processing of the HLRe is completed by the SMP module,
the configuration here is to configure the capacity of the SMP module in fact.
3. Select the module No., and click Default Setting.
The default values are added to the Current Value column as shown in Figure
3.13-3.
121
Figure 3.13-3 Default Configuration of HLRe Capacity
You can also modify the value in Current Value and click OK.
The HLRe capacity configured is displayed as shown in Figure 3.13-4.
122
Figure 3.13-4 HLRe Office Capacity Configured
3.14 Configuring MDN Assignment
3.14.1 Objective
Assign all the MDNs of the subscribers belonging to the HLRe to SMPs evenly.

1. Click Service data Configuration → MDN assign configuration from the

navigation tree.
123
The MDN assign configuration window is displayed as shown in Figure

3.14-1.
Figure 3.14-1 MDN Assignment Configuration
2. Click add .
The Add MDN assign window is displayed as shown in Figure 3.14-2.
Figure 3.14-2 Adding MDN Assignment
124
3. Select its default configuration and click OK.
All the MDNs belonging to the HLRe are assigned to the SMPs of the system
evenly according to the system default configuration. The MDN assignment
configured is displayed as shown in Figure 3.14-3.
Figure 3.14-3 MDN Assignment Configured
125
4 Roaming Configuration
Key points
· Overview of roaming configuration
· Configuring VLR address
· Configuring MSC address
· Configuring VLR international roaming
· Configuring MSC international roaming
· Configuring DB-MIN/MDN relation
· Configuring area
· Configuring VHLR-MIN/MDN relation
4.1 Overview
After location update, the MS may roam to other places in the country or even overseas.
To support national roaming and international roaming, you must configure the
MSC/VLR address and MSC/VLR international roaming data.
To facilitate the management of subscriber numbers by area or service attributes, the

system allows the carrier to manage number segments separately. Each number
segment belongs to a virtual HLR. Therefore, you must configure area management
and virtual HLR, and allocate the MIN/MDN segments to the related area and virtual
HLR.
4.2 Configuring VLR Address
4.2.1 Objective
The purpose of VLR address configuration is to judge the roaming level of the
subscriber in location updating and providing a VLRIN for the HLR Reset message.
127

1. Click Roam data Configuration → VLR address configuration from the

navigation tree.
The VLR address configuration window is displayed as shown in Figure 4.2-1.
Figure 4.2-1 VLR Address Configuration
2. Click to enter the Add VLR address dialog box as shown in Figure 4.2-2.
128
Chapter 4 Roaming Configuration
Figure 4.2-2 Adding VLR Address
The Add VLR address dialog box contains the following parameters:
VLR MarkID: The System IDentification (SID) of the network where the VLR
is located.
VLR SwitNum: The number of the switch in the network where the VLR is
located.
VLRIN: GT of the VLR in the HLR. The format is

MCC+MNC+09+M1M2M3+100.
3. Enter the related data, for example, enter 19542 in VLR MarkID, 1 in VLR
SwitNum, and 460030944123100 in VLRIN as shown in Figure 4.2-3.
129
Figure 4.2-3 VLR Address Configuration (Example)
4. Click OK.
The VLR address configured is displayed as shown in Figure 4.2-4.
Figure 4.2-4 VLR Address Configured
130
4.3 Configuring MSC Address
4.3.1 Objective
In a mobile terminated call, the MSC finds the address of the called party in the HLRe.
Therefore, you must configure the MSC address.

1. Click Roam data Configuration → MSC address configuration from the

navigation tree.
The MSC address configuration window is displayed as shown in Figure

4.3-1.
Figure 4.3-1 MSC Address Configuration
131
2. Click to enter the Add MSC address dialog box as shown in Figure
4.3-2.
Figure 4.3-2 Adding MSC Address
The Add MSC address dialog box contains the following parameters:
MSC MarkID: The SID of the network where the MSC is located.
VLR SwitNum: The number of the switch in the network where the MSC is
located.
3. Enter the related data, for example, enter 19542 in MSC MarkID and 1 in MSC
SwitNum as shown in Figure 4.3-3.
Figure 4.3-3 MSC Address Configuration (Example)
132
4. Click OK.
The MSC address configured is displayed as shown in Figure 4.3-4.
Figure 4.3-4 MSC Address Configured
4.4 Configuring VLR International Roaming
4.4.1 Objective
Configure the international roaming VLR data, which is used to judge whether the
subscriber is an international roaming subscriber in location update or not.

133
1. Click Roam data Configuration → VLR international roam configuration

The VLR international roam configuration window is displayed as shown in

Figure 4.4-1.
Figure 4.4-1 VLR International Roaming Data Configuration
2. Click to enter the Add VLR international roam dialog box as shown in
Figure 4.4-2.
134
Figure 4.4-2 Adding VLR International Roaming Data
The Add VLR international roam dialog box contains the following
parameters:
Country ID: Code of the country to which the VLR belongs.
Country name: Name of the country to which the VLR belongs.
Operator name: Name of the operator that manages the VLR.
VLR MarkID: The SID of the network where the VLR is located.
VLR SwitNum: The number of the switch in the network where the VLR is
located.
VLRIN: GT of the VLR. The format is MCC+MNC+09+M1M2M3+100.
3. Enter the related parameters, for example, enter 86 in Country ID, China in
Country name, unicom in Operator name, 14560 in VLR MarkID, 1 in VLR
SwitchNum, and 460030944569100 in VLRIN as shown in Figure 4.4-3.
135
Figure 4.4-3 VLR International Roaming Data Configuration (Example)
4. Click OK.
The VLR international data configured is displayed as shown in Figure 4.4-4.
136
Figure 4.4-4 VLR International Roaming Data Configured
4.5 Configuring MSC International Roaming
4.5.1 Objective
In a mobile terminated call, the MSC finds the address of the called party in the HLRe.
Therefore, you must configure the MSC international roaming data for the international
roaming service.

1. Click Roam data Configuration → MSC international roam configuration
137
The MSC international roam configuration window is displayed as shown in

Figure 4.5-1.
Figure 4.5-1 MSC International Roaming Data Configuration
2. Click to enter the Add international roam dialog box as shown in Figure
4.5-2.
138
Figure 4.5-2 Adding MSC International Roaming Data
The Add international roam dialog box contains the following parameters:
Country ID: Code of the country to which the MSC belongs.
Country Name: Name of the country to which the MSC belongs.
Operator name: Name of the operator that manages the MSC.
MSC MarkID: The system identification (SID) of the network where the MSC
is located.
MSC SwitNum: The number of the switch in the network where the MSC is
located.
MSCIN: GT of the MSC. The format is MCC+MNC+09+M1M2M3+100.
3. Enter the related parameters, for example, enter 86 in Country ID, China in
Country name, unicom in Operator name, 14560 in VLR MarkID, 1 in VLR
SwitchNum, and 460030944569100 in VLRIN as shown in Figure 4.5-3.
139
Figure 4.5-3 MSC International Roaming Data Configuration (Example)
4. Click OK.
The MSC international roaming data configured is displayed as shown in Figure

4.5-4.
Figure 4.5-4 MSC International Roaming Data Configured
140
4.6 Configuring DB-MIN/MDN Relation
4.6.1 Objective
Configure how the MIN/MDN segments are distributed to databases, that is, configure
the subscriber data of all the MIN/MDN segments in the HLRe to each database.

1. Click Roam data Configuration → DB-MIN/MDN relations configuration

The DB-MIN/MDN relations configuration window is displayed as shown in

Figure 4.6-1.
141
Figure 4.6-1 DB-MIN/MDN Relation Configuration
The MIN/MDN of the whole HLRe already configured is listed in the right
lower part of the window.
2. Select the node number of the database and the MIN to be allocated, and click
Add.
The MIN is allocated as shown in Figure 4.6-2.
142
Figure 4.6-2 MIN Number Segment Allocated
3. Select the MDN number tab and allocate the MDN.
The MDN allocated is displayed as shown in Figure 4.6-3.
143
Figure 4.6-3 MDN Number Segment Allocated
4.7 Configuring Area
4.7.1 Objective
Configure the MIN, MDN, MSC, VLR, HLR, local prefix, forwarding barring prefix,
and restricted voice number of each area.

1. Click Roam data Configuration → Area configuration from the navigation tree.
144
The Area configuration window is displayed as shown in Figure 4.7-1.
Figure 4.7-1 Area Configuration
The area is divided into three levels namely, country, province, and city. Data
cannot be added or deleted from countries and provinces. Data configuration can
be performed to cities only.
If you select an area configured, the attributes of that area are displayed in the
lower part of the left pane, and the configuration data including the MIN, MDN,
MSC, VLR and HLR of that area is displayed in the right pane. You can query
the specific information by selecting the related tab.
2. Add area.
· Right-click Whole country and select Add area from the shortcut menu.
The Add area dialog box is displayed as shown in Figure 4.7-2.
145
Figure 4.7-2 Adding Area
Area code: Area code of the area configured. If the area configured is a province,
the area code must be 0.
Area name: Name of the area configured.
HLR range belongs: Specifies whether the services of that area are handled by
the local HLR or not. It can be This HLR or Other HLRs.
Voice Mailbox Number: Number of the voice mailbox in that area.
· Enter the related data, for example, enter 0 in Area code, jiangsu in Area name,
This HLR in HLR range belongs, and 123 in Voice mailbox number as shown
in Figure 4.7-3.
146
Figure 4.7-3 Area Configuration (Example)
· Click OK.
The area configured is displayed as shown in Figure 4.7-4.
Figure 4.7-4 Adding a Province
147
· Right-click Jiangsu, and then add the cities such as Nanjing and Suzhou in the
same way.
The province and cities configured are as shown in Figure 4.7-5.
Figure 4.7-5 Adding Cities
3. Configure MIN of the area.
· As shown in Figure 4.7-5, select the city to be configured, for example, Nanjing.
· In the Area-MIN tab, select a MIN segment (for example, the MIN segment
with MIN ID of 1) and click Add.
The MIN segment is added to the Configured MIN number segments of that
area as shown in Figure 4.7-6.
148
Figure 4.7-6 Adding Area-MIN
To delete a MIN segment, select that MIN segment and click Delete. If that
number segment is already added to the virtual HLR, you must delete the virtual
HLR first.
4. Configure the MDN of the area.
· Select Area-MDN, as shown in Figure 4.7-5
The Area-MDN tab is displayed as shown in Figure 4.7-7.
149
Figure 4.7-7 Area-MDN Configuration
· Select the city (for example, Nanjing) and the MDN segment to be added (for
example, the MDN segment with MDN ID of 1), and click Add.
The MDN segment is added to the Configured MDN number segments of that
area as shown in Figure 4.7-8.
150
Figure 4.7-8 Area-MDN Configured
To delete a MDN segment, select that MDN segment and click Delete. If that
number segment is already added to the virtual HLR, you must delete the virtual
HLR first.
5. Configure the VLR of that area.
· Select Area-VLR, as shown in Figure 4.7-5,
The Area-VLR tab is displayed as shown in Figure 4.7-9.
151
Figure 4.7-9 Area-VLR Configuration
· Select the city (for example, Nanjing) and the VLR to be configured (for
example, the VLR with VLR ID of 1), and click Add.
The VLR is added to the Configured HLRs of that area as shown in Figure
4.7-10.
152
Figure 4.7-10 Area-VLR Configured
To delete a VLR, select the VLR to be deleted and click Delete.
6. Configure the MSC of that area.
· As shown in Figure 4.7-5, select Area-MSC.
The Area-MSC tab is displayed as shown in Figure 4.7-11.
153
Figure 4.7-11 Area-MSC Configuration
· Select the city (for example, Nanjing) and the MSC to be added (for example,
the MSC with MSC ID of 1), and click Add.
The MSC is added to the Configured MSC of that area as shown in Figure
4.7-12.
154
Figure 4.7-12 Area-MSC Configured
To delete the MSC, select the MSC to be deleted and click Delete.
7. Configure the HLR of that area.
· Select Area-HLR, as shown in Figure 4.7-5,
The Area-HLR tab is displayed as shown in Figure 4.7-13.
155
Figure 4.7-13 Area-HLR Configuration
· Select the city (for example, Nanjing) and the HLR to be added (for example,
the HLR with HLR SwitchNum of 1), and click Add.
The HLR is added to the Configured HLR of that area as shown in Figure
4.7-14.
156
Figure 4.7-14 Area-HLR Configured
To delete the HLR, select the HLR to be deleted and click Delete.
8. Configure the prefix of that area.
· Select Area-prefix, as shown in Figure 4.7-5,
The Area-prefix tab is displayed as shown in Figure 4.7-15.
157
Figure 4.7-15 Area-prefix Configuration
The area-prefix configuration involves Local prefix, Forwarding barring prefix,

and Restricted voice number.
The default tab is Local Prefix as shown in Figure 4.7-15.
· Select the city Nanjing and click .
The dialog box is displayed as shown in Figure 4.7-16, where you can set the
forwarding prefix.
Figure 4.7-16 Adding Local Prefix
158
The forwarding prefix includes the prefix of fixed telephone and mobile phone.
You can select it from Attribute.
· Enter the correct data, for example, enter 2635441 in Mobile/fixed forwarding
prefix and Fixed telephone in Attribute, and click OK.
The data is added to the configuration library as shown in Figure 4.7-17. You
can cancel the operation by clicking Cancel.
Figure 4.7-17 Local Prefix Configured
· As shown in Figure 4.7-17, select the Forwarding barring prefix tab.
The Forwarding barring prefix tab is displayed as shown in Figure 4.7-18.
159
Figure 4.7-18 Forwarding Barring Prefix Configuration
The dialog box is displayed as shown in Figure 4.7-19, where you can set the
forwarding barring prefix.
Figure 4.7-19 Adding Forwarding Barring Prefix
160
· Enter the correct data, for example, enter 8613357887799 in Forwarding

forbidden prefix, and click OK.
The data is added to the configuration library as shown in Figure 4.7-20. You
can cancel the operation by clicking Cancel.
Figure 4.7-20 Forwarding Barring Prefix Configured
· In Figure 4.7-20, select Restricted voice number.
The Restricted voice number tab is displayed as shown in Figure 4.7-21.
161
Figure 4.7-21 Restricted Voice Number Configuration
The dialog box as shown in Figure 4.7-22 is displayed.
Figure 4.7-22 Adding Restricted Voice Number
· Enter the restricted voice number, for example 16899168, and click OK.
The restricted voice number configured is displayed as shown in Figure 4.7-23.
162
Figure 4.7-23 Restricted Voice Number Configured
4.8 Configuring VHLR-MIN/MDN Relation
4.8.1 Objective
To facilitate the management of subscriber numbers by area or service attributes, the

system allows the carrier to separately manage different number segments, making
different number segments belong to different virtual HLRs.

163
1. Click Roam data Configuration → VHLR-MIN/MDN relations configuration

The VHLR-MIN/MDN relations configuration window is displayed as shown

in Figure 4.8-1.
Figure 4.8-1 VHLR-MIN/MDN Relation Configuration
2. Click to enter the Virtual HLR information dialog box as shown in

Figure 4.8-2.
164
Figure 4.8-2 Adding VHLR Information
3. Enter the related information of the VHLR, for example, enter 1 in Virtual HLR
ID and Nanjing hlr in Virtual HLR name, and click Next.
The Virtual HLR/MIN relation configuration dialog box is displayed as

Figure 4.8-3 Assigning MIN to VHLR
165
4. Select the MIN to be assigned and click Add. After the MIN is assigned to the
virtual HLR, click Next.
The Virtual HLR/MDN relation configuration dialog box is displayed as

Figure 4.8-4 Assigning MDN to VHLR
5. Select the MDN to be assigned and click Add. After the MDNs assigned to the
virtual HLR, click OK.
Figure 4.8-5 and Figure 4.8-6 show the MIN and MDN assigned to the VHLR.
166
Figure 4.8-5 VHLR-MIN Configured
Figure 4.8-6 VHLR-MDN Configured
167
5 Configuration Tools
Key points:
· Overview of configuration tools
· Synchronizing MP data
· Synchronizing HLRe server data
· Backing up and restoring HLRe
· Configuring security variable
5.1 Overview of Configuration Tools

The data configuration system comprises two parts in terms of structure:
· Background: With the server as the centre and of the Client/Server structure.
· Foreground: With the MPs as the core.
The data configuration performed in the background is saved in the background

database only. The data becomes valid only after being loaded to the foreground.
5.2 Synchronizing MP Data
5.2.1 Objective
To send the data configured in the background to the MPs of the foreground to validate
the configuration.


· The communication between the foreground and the background is normal.
169
1. Click Configuration tools → MP Data Synchronization from the navigation

tree.
The MP data synchronization window is displayed as shown in Figure 5.2-1.
Figure 5.2-1 MP Data Synchronization
The MP data synchronization window contains the following parameters and

shortcut icons:
Transmission mode: Specifies the data transmission mode. Only Total is valid.
Synchronization Tables: Types of the synchronization tables, which include

R_CONST Table, Complete Table, and Changed Table.
R_CONST Table: Transfers the specified tables only. It can reduce the system
load caused by the data transfer between the foreground and the background.
Complete Table: Transfers all the tables. The data transfer speed is very slow.
This option is selected in deployment only.
Changed Table: Transfers the tables modified only.
170
Chapter 5 Configuration Tools
Synchronization Option: It can be Primary/Secondary or Save to Disk.
Timer: Set the wait-for-foreground-response time. The

wait-for-foreground-response time refers to the time that the foreground returns
response to the background after the background sends the data to it. It is 30
seconds by default. You can modify this value.
: Selects all the MPs in the foreground.
: Clears all the MPs selected.
: Synchronizes data.
: Synchronizes notification.
2. Select the MPs to be synchronized and the synchronization table, and click
S Caution:
When synchronizing data for the first time, synchronize the R_CONST Table first and
then the Complete Table.
To load data to a module, select the module and perform the synchronization
separately.
5.3 Synchronizing HLRe Server Data
5.3.1 Objective
To send the service data configured in the background to the MPs, DBIO, and
HDBAgent of the foreground.


171
1. Click Configuration tools → HLRe Server Data Synchronization from the

navigation tree.
The HLRe Server data synchronization window is displayed as shown in

Figure 5.3-1.
Figure 5.3-1 HLRe Service Data Synchronization
The meaning of the parameters in the HLRe Server data synchronization

window is the same as that in Figure 5.2-1.
2. Select the MPs to be synchronized and the synchronization table, and click
S Caution:
When synchronizing data for the first time, synchronize the R_CONST Table first and
then the Complete Table.
172
To load data to a module, select the module and perform the synchronization
separately.
5.4 Backing Up and Restoring HLRe
5.4.1 Objective
To back up the configuration data to disks.
To restore the system data using the data files saved in the disk.


Click Configuration tools → HLRe backup and restoration from the navigation tree.
The HLRe backup/restoration window is displayed as shown in Figure 5.4-1.
173
Figure 5.4-1 Data Backup and Restoration
1. Back up data.
1) As shown in Figure 5.4-1, select Restore from file under Operation, enter the
file name in Input SQL file name, and click
Figure 5.4-2 Confirming Whether to Back Up Data
2) Click OK.
The system automatically backs up the database to the SQL file specified. After
the database is backed up, the message box is displayed as shown in Figure
5.4-3.
174
Figure 5.4-3 Message Prompting Successful Backup of Database
2. Restore data.
1) As shown in Figure 5.4-1, select Backup to file under Operation and the name
of the file to be restored under File list, and click .
Figure 5.4-4 Confirming Whether to Restore Data
2) Click OK.
The system automatically restores the data saved in specified SQL file to the
database. After that, the message box is displayed as shown in Figure 5.4-5.
Figure 5.4-5 Message Prompting Successful Data Restoration
5.5 Configuring Security Variable
5.5.1 Objective
Configure the security variable.
175


1. Click Configuration tools → Security variable from the navigation tree.
The Security variable window is displayed as shown in Figure 5.5-1.
Figure 5.5-1 Security Variable Configuration
: Displays service variable.
: Performs overload control.
: Sends parameters.
176
2. Select a module, for example, module 1, and click .
The service variable parameters of module 1 are displayed as shown in Figure

5.5-2.
Figure 5.5-2 Service Variable Parameters of Module 1
3. Double-click the service variable parameter to be set, for example, TACP

dialogue ID alarm threshold.
The Parameter Setting dialog box is displayed as shown in Figure 5.5-3.
Figure 5.5-3 Service Variable Parameter Configuration
177
4. Modify the parameter and click OK.
5. Click to load the parameter set to the foreground.
You can modify the overload control parameters of each module in the same
way.
S Caution:
The modification of system security variables may affect services and system
performance. Normally, the default configuration is recommended. If some parameters
need to be modified, modify them with great care.
178
6 Example of Simplest Configuration
This chapter introduces the data configuration for the basic services of the HLRe.
Key points:
· Description of simplest configuration
· Configuration preparation
· Data configuration
6.1 Description of Simplest Configuration

The simplest configuration refers to the configuration required to implement the basic
services of the HLRe. Connected with the MSCe through the IP domain, the HLRe
implements basic voice services.
6.2 Configuration Preparation

Prepare the following data for the HLRe simplest configuration:
1. HLRe data
Area code: 90
Office No.: 13
Signaling point code: 9-0-9
MDN number segment: 861330840 – 861330849
MIN number segment: 090840 – 090849
SMP association IP address: 192.200.99.160
SIPI address: 192.200.99.212
HLR MarkID: 12345
HLRIN: 460030912340000
2. MSCe data
179
Signaling point code: 9-0-8
SMP association IP address: 192.200.99.180
MSCe/VLR MarkID: 12345
MSCe/VLR IN: 460030944234100
6.3 Data Configuration
6.3.1 Basic configuration
For the basic configuration, the data configuration provided below is given for your
reference. For the configuration of other parameters, default values can be used.
1. Physical configuration
Add rack, shelves, and boards. Configure the MP type, board attributes, SMP
virtual address, and SIPI by referring to Physical Configuration. Table 6.3-1 lists
the boards to be added for the simplest configuration.
Table 6.3-1 Board Configuration in Simplest Configuration
Board Name Slot No. Description
Module type: MT_3G_OMP_SMP_CMP

MP 11/12
Virtual address: 192.200.99.160
UIM 9/10 SCType1: SCT_3G_GCS, other SCTypes: null.
SIPI 1 IP: 192.200.99.212
USI 3 Route address to HDBAgent: 191.13.100.1
CLKG 13/14
2. Office configuration
Configure local office data, signaling data, and adjacent office data by referring to Office Configuration. See
Table 6.3-2 for the data configured.
180
Chapter 6 Example of Simplest Configuration
Table 6.3-2 Office Data Configuration
Parameter Value
Configuration of Local Office
Test Code 1234
Exchange Office Type Local Exchange
Basic Network Type China Mobile Communication Network
SPC Type Signaling End Point
Signaling configuration
24-bit SPC 9–0–9
Network Appearance 1
Region Code 90
User Type SCCP User
Adjacent Office Configuration
Adjacent Office ID 1
SSF National SPC
Adjacent Office Name MSCe
Toll Area Code 90
24-bit SPC 9–0–8
SPC Type Signaling End Point
Protocol Type Chinese Standard
Connection Mode Associated
Field Type IP
Mark Gloable code
Adjacent office type Local Exchange, MSCE
MSC code 12345
3. SCCP configuration
Configure GT selector and GT by referring to Configuring SCCP. See Table

6.3-3 for the GT data configured.
Table 6.3-3 GT Configuration
GT SP Office
Numbering Plan Translation Type GT Number
Selector Direction
ISDN/telephone 133084
1 0 0
numbering plan 1 86133084
181
4600309084
Land mobile 0
2 0 46003091234000
numbering plan 6
1 460030944234100
4. Sigtran configuration
Configure Sigtran by referring to Sigtran Configuration. See Table 6.3-4 for the
data configured.
Table 6.3-4 Sigtran Configuration
Parameter Value
SCTP Basic Connection Configuration
SCTP Association ID 1
Module No. 1
SCTP Protcol Type M3UA
Opposite-end office ID 1
Local Port No. 3000
Opposite-end Port No. 3000
Outgoing Stream Number 16
Incoming Stream Number 16
MSC Server ID 0
Coupling Application Property Server side
Local IP Adress 192.200.99.160
Opposite-end IP Address 192.200.99.180
ASP Configuration
Application Server Process ID 1
SCTP Association ID 1
AS Configuration
Application Server No. 1
Usage ID IPSP_SERVER
Adapting Layer Protocol M3UA
Service Mode OVERRIDE
Application Server Supported User
SCCP User
Tyype/Subsystem
Application Server Process ID 1
AS Configuration of SIO Positioning
Office ID 1
Service Indicator SCCP
Application Server No. 1
182
5. HLRe module configuration
Add module 1, module 134, and module 140 by referring to HLRe Module
Configuration. See Table 6.3-5 for the data configured.
Table 6.3-5 HLRe Module Configuration
Parameter Value
Module 1 HLR MAP
Module 134 DBIO
Module 140 HDBAgent
6. HLRe type configuration
Configure the HLRe type by referring to HLRe Type Configuration. See Table
6.3-6 for the data configuration.
Table 6.3-6 HLRe Type Configuration
Parameter Value
System type AS Master HLR only
Country code 86
International outgoing prefix 00
Domestic outgoing prefix 0
7. HLRe office configuration
Configure the HLRe office data by referring to Mobile Office Configuration.

See Table 6.3-7 for the data configuration.
Table 6.3-7 HLRe Office Configuration
Parameter Value
HLR type Master
HLR Name HLRe
HLR SwitNum 1
HLR MarkID 12345
HLRIN 460030912340000
8. Database configuration
Configure the database by referring to Database Node Configuration. See Table

183
Table 6.3-8 Database Configuration
Parameter Value
Active Database Name HLRDB
Active Server Name 129.90.13.150
Node 150
Active Server Node 151
Standby Server Node 152
Database Type SQL Server
Node Capacity 100000
DBIO password Null
DBMAP password Null
9. MP module configuration
Configure the MP modules by referring to MP Module Configuration. See Table

Table 6.3-9 MP Module Configuration
Parameter Value
MPNo_Master 1
6.3.2 Service Data Configuration
For the HLRe service configuration, the data configuration provided below is given for
your reference. For the configuration of other parameters, default values can be used.
1. Configuration of carrier
Configure the carrier data by referring to Configuring the Carrier. See Table
Table 6.3-10 Operator Data Configuration
Parameter Value
Carrier code 1
Carrier name Unicom
2. MIN/MDN configuration
Configure the MIN/MDN number segment by referring to Configuring the MIN/MDN . See
184
Table 6.3-11 for the data configuration.
Table 6.3-11 MIN/MDN Configuration
Parameter Value
MIN 090840 – 090849
MDN 861330840 – 861330849
3. Configuration of number conversion
Configure the number conversion by referring to Configuring Number

Conversion. See Table 6.3-12 for the data configuration.
Table 6.3-12 Configuration of Number Conversion
Parameter Value
select Default inner Default signaling
number 133→86133 86133→133
6.3.3 Roaming Data Configuration
International roaming data needs not to be configured. Except the MSCe/VLR address
and other parameters use the default value.
Table 6.3-13 Lists the configuration of the local MSCe/VLR address.
Table 6.3-13 Configuration of Local MSCe/VLR Address
Parameter Value
MSCe/VLR MarkID 12345
MSCe/VLR SwitNum 1
MSCe/VLR IN 460030944234100
185

CM3G-303-E1 Introduction To The ZXC10 HLRe Data Configuration

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CM3G-303-E1 Introduction To The ZXC10 HLRe Data Configuration

Uploaded by

Copyright:

Available Formats

CM3G-303-E1 Introduction to the ZXC10

1.1 Overview of Configuration Management System............................................................................. 2

1.2 Basic Configuration Sequence .......................................................................................................... 2

2 Basic Configuration ................................................................................................................................... 2

2.2 Configuration Procedure ................................................................................................................... 2

2.3 Physical Configuration...................................................................................................................... 2

2.3.1 Objective ................................................................................................................................ 2

2.3.2 Preliminary Setup................................................................................................................... 2

2.3.3 Detailed Procedure ................................................................................................................. 2

2.3.4 Adding Racks ......................................................................................................................... 2

2.3.5 Adding Shelves....................................................................................................................... 2

2.3.6 Adding Boards........................................................................................................................ 2

2.3.7 Configuring the MP Module Type.......................................................................................... 2

2.3.8 Configuring the MP Module Capacities................................................................................. 2

2.3.9 Configuring the Module/Unit Relationship............................................................................ 2

2.3.10 Configuring IP Interfaces ..................................................................................................... 2

2.4 Unit Attribute Configuration ............................................................................................................. 2

2.4.1 Objective ................................................................................................................................ 2

2.4.2 Preliminary Setup................................................................................................................... 2

2.4.3 Detailed Procedure ................................................................................................................. 2

2.5 Office Configuration ......................................................................................................................... 2

2.5.1 Objective ................................................................................................................................ 2

2.5.3 Detailed Procedure..................................................................................................................2

2.5.4 Configuring Local Office........................................................................................................2

2.5.5 Configuring Signaling.............................................................................................................2

2.5.6 Configuring Adjacent Office...................................................................................................2

2.6 SS7 Data Configuration.....................................................................................................................2

2.6.2 Preliminary Setup ...................................................................................................................2

2.6.3 Detailed Procedure..................................................................................................................2

2.6.4 Configuring MTP....................................................................................................................2

2.6.5 Configuring SCCP ..................................................................................................................2

2.6.6 Configuring SSN ....................................................................................................................2

2.6.7 Configuring Narrowband Signaling Link ...............................................................................2

2.7 Sigtran Configuration ........................................................................................................................2

2.7.2 Preliminary Setup ...................................................................................................................2

2.7.3 Detailed Procedure..................................................................................................................2

2.7.4 Configuring SCTP Basic Connection .....................................................................................2

2.7.5 Configuring ASP.....................................................................................................................2

2.7.6 Configuring AS.......................................................................................................................2

2.7.7 Configuring SIO Positioning AS ............................................................................................2

2.8 HLRe Module Configuration.............................................................................................................2

2.8.2 Preliminary Setup ...................................................................................................................2

2.8.3 Detailed Procedure..................................................................................................................2

2.9 HLRe Type Configuration .................................................................................................................2

2.9.2 Preliminary Setup................................................................................................................... 2

2.9.3 Detailed Procedure ................................................................................................................. 2

2.10 Mobile Office Configuration........................................................................................................... 2

2.10.1 Objective .............................................................................................................................. 2

2.10.2 Preliminary Setup................................................................................................................. 2

2.10.3 Detailed Procedure ............................................................................................................... 2

2.11 Database Node Configuration ......................................................................................................... 2

2.11.1 Objective .............................................................................................................................. 2

2.11.2 Preliminary Setup ................................................................................................................. 2

2.11.3 Detailed Procedure ............................................................................................................... 2

2.12 HDBAGENT DBIO Configuration................................................................................................. 2

2.12.1 Objective .............................................................................................................................. 2

2.12.2 Preliminary Setup................................................................................................................. 2

2.12.3 Detailed Procedure ............................................................................................................... 2

2.13 HDBAGENT MP Configuration..................................................................................................... 2

2.13.1 Objective .............................................................................................................................. 2

2.13.2 Preliminary Setup................................................................................................................. 2

2.13.3 Detailed Procedure ............................................................................................................... 2

2.14 DBIO Configuration........................................................................................................................ 2