Course Code Course Name

8/14/2019 Course Code Course Name

1/35

The Competency Ladder Certification for the Commercial andTechnical Posts of International Pre-sales Business

Training Material ( Course Code)

Course Code Course Name

Edited by:


2/35

Objectives:

1.

2.

3.

4.

Reference

1.

2.

3.


3/35

Contents

1 Module Functions .........................................................................................................................................1

1.1 Agent Module ..........................................................................................................................................1

1.1.1 Principle of the Agent ...............................................................................................................2

1.1.2 Functions of the Agent ..............................................................................................................2

1.2 DBIO Module ..........................................................................................................................................3

1.2.1 Design Idea ...............................................................................................................................3

1.2.2 Module Functions .....................................................................................................................4

2 Billing System Networking Structure ........................................................................................................5

2.1 Billing System Networking Structure .....................................................................................................5

2.2 External Communication Gateway Node 200 Configuration ................................................................6

2.3 Starting the Gateway Service Program ...................................................................................................9

2.4 Debugging with the Billing System ......................................................................................................10

2.5 Debugging Operations of the Added Node ...........................................................................................11

3 Usage of the Agent ......................................................................................................................................13

3.1.1 Agent Log Management .........................................................................................................13

3.1.2 Agent Authority Management ................................................................................................13

3.2 Interface of the Agent ............................................................................................................................14

3.3 Operations and Usage of the Agent ......................................................................................................16

3.3.1 System Menu ..........................................................................................................................16

3.3.2 User Information Handling Menu ..........................................................................................17

3.3.3 Authentication Data Handling ................................................................................................24

3.3.4 Batch Processing Menu ..........................................................................................................27

-i-


4/35


5/35

1Module Functions

Key points

Indicates the key knowledge in this section

1.1Agent Module

The HLRe database subsystem agent module (the agent for short) provides an

operation platform for the O&M personnel for mobile user management. It can be

placed at the local end or the remote end to access the system through different

communication modes and implement the management of mobile user information in

the local HLR. Fig. 1.1-1 shows the location of the agent in the HLRe system.

Agent module

User database

Configuration

managementsystem

O&M personnel

Configuration

database

Service processing system

DDN/FR/

X.25/PSTN

Agent module(remote)

O&M personnel

DBIO

Fig. 1.1-1 Location of the Agent in the System

The agent communicates with the DBIO through messages. The agent provides a GUI

for the O&M personnel. Through the GUI, the O&M personnel send man-machine

-1-


6/35


7/35

Chapter 3 Usage of the Agent

Measuring the quantity of numbers assigned from number segments.

Measuring the number of users roaming outside the local area, province andcountry and user list and providing the print function.

Measuring the list of subscribed service users and providing the print function.

Backing up and recovering the user database.

Other functions:

Querying operator attribute.

Querying authorized functions.

1.2DBIO Module

1.2.1Design Idea

The DBIO module is the interface for the agent/billing interface to access the database.

It implements various access operations of the user database.

All services of the DBIO related to the agent are implemented in the main thread. If

other tributary threads need to operate the database, separate database connections shall

be established. This ensures in-sequence access of all services to the database.

To solve the problem of lost update possibly caused when multiple agents complete the

handling functions simultaneously, the agents need to query and obtain the

modification check identifier of the related record in the database. The agents need to

provide the check identifier for the DBIO when submitting the service. The DBIO

compares the modification identifier of the record provided by the agents, and

implements corresponding service operations only when the check identifier provided

by the agents is consistent with that in the database.

The DBIO can provide the accurate modification of each record field for the agents.

-3-


8/35


1.2.2Module Functions

Fig. 1.2-2 shows the location of the DBIO in the HLRe system.

Configurationmanagement

process

OMM

Configurationbackgroundsubsystem

Support subsystem

OMMsubsystem

Memory databasemanagement tool

Main controlprocess

DBIO module

Agentprogram

Remotebilling system

DBMAPprocess of the

HDBAgent

HLRDB

Synchronizationprocess

Service process

DBSYNCprocess of the

HDBAgent

Service process

Service process

Fig. 1.2-2 Location in the HLR/AUC System

1. Configuration management process: It implements the synchronization of

configuration data with the configuration background.

2. OMM module: It processes functions of the OMM.

3. DBIO main control process: It processes the configuration information change

message of the configuration management process, forwards the request

messages from the agent and remote billing system to the service process,

controls the number of service processes of the DBIO module, notifies the

service processes and the synchronization process of the related configuration

information change, processes the request messages from the memory database

management tool, and returns the results.

4. DBIO module service process: It processes the request messages from the agent

and remote billing system, operates the user database according to the related

requests, and returns the processing results through the DBIO main control

process.

5. DBIO module synchronization process: It processes the request messages of the

HDBAgent (related user database operations), returns the processing results, and

processes the configuration information change messages from the main control

process.

-4-


9/35

2Billing System Networking Structure

Key points

Indicates the knowledge in this section.

2.1Billing System Networking Structure

In the HLR LAN, the connection of the billing and number allocation system of the

carrier is the most important connection. To ensure the security of the HLR LAN, the

billing network of the carrier shall be isolated through the layer-3 equipment such as a

router, as shown in Fig. 2.1-3.

The router that connects two LANs shall be configured with at least two Ethernet ports.

One Ethernet port connects to the ZXC10-HLR system LAN, and the other connects to

the billing system LAN of the carrier. This ensures the network security of the ZXC10-

HLR system.

At present, the ZXC10HLR system is connected to the remote billing system through

the 134 server.

-5-


10/35


Router

HLR SWITCH 1 Billing and provisioning system SWITCH

HLR SWITCH 2

M

P129 134 140

Carrier's LANHLR LAN

Billing server

150

Fig. 2.1-3 Connections Between the HLR and the Billing System LAN

2.2External Communication Gateway Node 200 Configuration

After the HLR134 server is installed with the External communication gateway

program, it supports the functions of node 200. The configuration is as follows:

1. Configure the dual IP address of the 134 server, and then add the IP address of

node 200, as shown in Fig. 2.2-4.

-6-


11/35


Fig. 2.2-4 Dual IP Configuration of the 134 Node

2. Check the C:\WINNT\tcpout.ini file, and modify the address of the remote

agent. You can refer to the following configuration. The IP address shall be the

actual IP address of the remote agent.

[RemoteInfo]

Remote1=Name(happserver),Node(134)

Remote2=Name(al),Node(201),IP(194.136.9.201),Connect(S)



The remote service access console uses the IP address allocated in the

configuration file to connect to ZTE access server through port 3000. Fig. 2.2-5

shows the access connection.

ZTE access server and the remote service access console implement the

corresponding service functions through asynchronous messages. Each service

-7-


12/35


request shall contain the user name and password for executing the command.

At present, the user name and password are provided by the ZXC10-HLR

system, but they are not encrypted.

Note: ZTE access server can be an independent physical entity, or placed on the

OMM Server.

ZTE HLR database 153 ZTE accessserver 134/200

201 202 203 204 205

Remote serviceaccess console

TCP connection

Port number 3000

IP address:

Access console 1:

X.X.X.201

Access console 2:

X.X.X.201

Access console 3:

X.X.X.201

Fig. 2.2-5 Remote Service Access Connection

3. The external gateway includes the following information:

Gateway program: tcpout.exe (c:\zxc10\)

Gateway configuration file: tcpout.ini (c:\winnt\)

Gateway watchdog: tcpdog.exe (c:\zxc10\)

4. The system module that needs to provide or support remote access functions

includes:

HLR agent server program DBIO: cogsrv.exe (c:\zxc10, providing an open

interface)

HLR configuration console system: ochcli.exe (setting the operation authority of

the remote access node 201)

System service license file: license.zcl (c:\winnt\)

-8-


13/35


2.3Starting the Gateway Service Program

1. After the 134/200 background program is installed, and the 134 server is

restarted, you can see the virtual 200 gateway server through the 134

background MSS communication system, as shown in Fig. 2.3-6.

Fig. 2.3-6 MSS Communication System of 134 Background

2. The system automatically runs the gateway watchdog program, as shown in Fig.

2.3-7.

Fig. 2.3-7 Gateway Watchdog Program

3. Through the 134 ZXC10-MSS external communication gateway program, you

can check the connection status of node 200 and other remote agent nodes, as

shown in Fig. 2.3-8.

-9-


14/35


Fig. 2.3-8 ZXC10-MSS External Communication Gateway

2.4Debugging with the Billing System

After the above program runs normally, configure the actual IP address of the remote

node 201 in the gateway configuration file C:\WINNT\tcpout.ini. The node

communicates with the remote billing server through the gateway address of the router.

The file content is as follows:

[Setup]

AreaCode=971 Area code

PostOffice=4 Office ID

LocalNode=200 Local node

ListenPort=3000 Port number

OMMServer=129 OMM server node number

JFServer=130 Billing server node number

OMMMp=2

ConnectOMMServer=1

ConnectJFServer=0

-10-


15/35


16/35


Fig. 2.5-9 Authority Configuration of the Remote Agent

3. In the existing signaling tracing system, you can trace and test the remote node,

and record the interaction information between the remote node and the DBIO

interface, as shown in Fig. 3.2-10.

2.5-1 DBIO Tracing Settings in Signaling Tracing

-12-


17/35

3Usage of the Agent

Key points

Indicates the knowledge in this section.

3.1.1Agent Log Management

The DBIO module in the HLRe system provides data services for the agent, and logs

the operations related to the agent in the log database. It allows the system

administrator or maintenance personnel to query the operation log of the agent. The log

of the agent supports the query authority protection function. To facilitate the

management and maintenance of the system, various important operations related to

the agent are recorded, including:

Operations on the agent such as login and exit.

Operations on the agent such as querying, modifying and deleting important data

of mobile users and subscription service.

Various management operations implemented by the maintenance console on the

account of the agent.

3.1.2Agent Authority Management

The agent can complete the subscription, deletion and authority register of mobile

users, and directly modify the related user data in the HLRe. Therefore, to prevent the

user data from being damaged, the authority management of the agent is quite

important.

The HLRe system provides complete authority management for the agent system. The

authorities are as follows:

Querying the existing authority directory and account directory of the system.

Managing the authority group of the agent.

Managing accounts of the agent.

-13-


18/35


Managing the virtual HLR sections under the agent account.

Providing an easy, simple and practical operation interface.

3.2Interface of the Agent

Start the agent system, as shown in Fig. 3.2-10.

Fig. 3.2-10 ZXC10-MSS Service Agent Interface

This interface consists of menu bar, toolbar, status bar and main window. Besides, there

are some shortcut buttons, such as Minimize, Maximize and Close buttons.

The main menu includes: System (S), User Information Handling (I), Authentication

Data Handling (A), Batch Processing (B), Window (W) and Help (H). Various menu

commands are executed to implement the operations provided by the Agent.

1. System menu command (S) (Alt+S)

The system menu provides these commands:

Get database

configuration (G)Ctrl+G

Gets the database configuration from the server (such as

MIN or MDN range, and DB node).

Agent operators

attributes (U)Ctrl+U

Queries the information such as operation authority of the

operator of the agent (query the virtual HLR configuration

of the operator).

Exit (X) Exits the agent system.

-14-


19/35


2. User information processing menu command (I) (Alt+I)

The user information handling menu provides these commands:

Single Allocation (A) Ctrl+A Creates a user and sets the user information.

Query Ctrl+QQueries or modifies the basic data and subscribed services

of the user (single or batch query).

Delete User (D) Ctrl+D Deletes a User

Change MDN(N) Ctrl+H Changes the MDN of the user.

Location Information (L) Ctrl+LQueries or modifies the location information about the

mobile user and the MS status.

MS status (T) Ctrl+T Queries or modifies the MS status and the approval data.

3. Authentication data handling (A) (Alt+A )

Single Add (A) Adds the authentication information before adding a user.

Query (Q) Queries or modifies the authentication information.

Authentication Indication (U)The authentication indication can initiate SSD update or

unique query from the HLR.

4. Batch processing menu command (B) (Alt+B)

The batch processing menu provides these commands:

File Conversion (F) Ctrl+FConverts the text file into the file in ZTE file format. It is

used to batch add users.

Batch Add

Authentication (A)

Adds authentication information about a batch of users

before adding them.

Batch Number Allocation

(B)Ctrl+B Adds a batch of users (providing default settings)

5. Window (W) (Alt+W)

The window menu provides these commands:

Cascade (C) Cascades parent and child windows.

Tile (T) Tiles current windows.

Minimize All Minimizes all child windows.

6. Help menu command (H) (Alt+H)

The Help menu provides the following commands:

About the Agent (A) Shows version information about the system

-15-


20/35


3.3Operations and Usage of the Agent

3.3.1System Menu

The System menu provides these functions: obtaining database configuration, querying

the operation authority of the current login account and exiting the operating system of

the agent.

1. Obtaining database configuration

The agent obtains some configurations from the configuration database (such as

database node, MIN range, service processor node), especially when the system

configuration changes are not synchronized to the DBIO, the changedconfiguration can be obtained through this menu.

2. Querying the operator attributes of the agent

The operation authorities that can be queried include: operations permitted for

the current login operator and mobile user number range managed by the

operator. These authorities are allocated by the ZXC10-MSS authority

management system.

The detailed operation procedure is as follows:

-16-


21/35


Select System > Agent Operators Attribute, or click the corresponding icon

on the toolbar. The Agent Operators Attributes dialog box appears, as shown

in Fig. 3.3-11.

Fig. 3.3-11 Agent Operators Attributes

The following key content can be obtained from the dialog box:

The user SYSTEM can perform 16 agent operations, including adding a user,

querying and modifying user information, querying and modifying user location

information and querying MS status.

The mobile user number range managed by the user SYSTEM is given in two

forms: MIN and MDN.

After the completion of the query, clickOK.

3.3.2User Information Handling Menu

The user information handling menu provides these functions for the user: adding a

mobile user (registration), querying/modifying mobile user information, changing

MDN, querying/modifying/deleting mobile user location information, and

querying/modifying MS status.

-17-


22/35


23/35


Permitted roaming area:

It includes four options: local roaming, intra-province roaming,

national roaming and international roaming. This service is

related to the registration and call.

Route ID:

Outgoing call trigger: The carrier defines the call redirecting service.

SPINI trigger: The service operation PIN code of the carrier.

SMS data

SMS outgoing call restriction, SMS incoming call restriction,

transmitting to other MC directly, forced to use indirect route,

SMS authority and destination user RC.

Supplementary service:

Whether to combine PINs:It specifies whether to combine the PINs of the SPINA and the

SPINI. If they are combined, enter the combined PIN.

Remote feature control (RFC):It indicates whether to allow other terminals to remotely control

the user. If yes, enter the SFCPIN.

Voice message access (VMA):

It indicates whether the user has the ability to extract the voice

mail information. If yes, authorize, activate and register the

VMAPIN.

PIN interception and access:

SPINA: If this function is authorized, other service operations of

the user cannot be performed.

SPINI: If this function is authorized, it requires the user to enter

the PIN when the user performs other service operations.

Call forwarding serviceincludes:

CFU, CFD, CFNA, CFB and CFNR time.

Other service authority: CD, CT, CW, DND and CC.

Message waiting notice

(MWN):

It specifies whether to notify the user when there is a short

message for the user.

Preferred language (PL): It is the prompt language for the user at the network side.

Password call acceptance

(PCA):

When the user acts as a callee, it requires the caller to enter the

password.

Selective call acceptance

(SCA):

When the user acts as a callee, it requires the caller to enter the

password.

Number identification

Calling number 1 (MS side) display authority, calling number 2

(network side) display authority, calling number display

restriction authority and beyond calling number display

restriction authority.

-19-


24/35


2. Querying/modifying subscriber information.

Select User Information Handling > Query, or click the appropriate icon onthe toolbar to display the dialog box, as show in Fig. 3.3-13.

Fig. 3.3-13 Querying User Information

There are three query methods: querying a user, batch querying users and

querying unallocated MIN.

1) Querying a user: Query user information according to the MIN or MDN, modify

or delete the mobile user.

In the Query Mode pane, select Query a user, and enter the MIN or MDN of

the mobile user to be queried, and then click OK. The user information which

satisfies the conditions appears on the lower part of the screen.

Select the user, and clickQuery to display user information. In this case, you

can modify the user information. After the modification, click Submit. The

system prompts the operation success or failure according to the modification

results. To cancel the modification, clickReset.

2) Batch search: Query a batch of (up to 50 users) MDNs, ESNs and related MINs

according to the entered MDN or MIN at a time. You can query, modify or

-20-


25/35


delete any of the mobile users.

In the Query Mode pane, select Batch Search, and enter the MIN or MDN ofthe users to be queried, and then clickOK. The user information which satisfies

the conditions appears on the lower part of the screen.

Select any user to be queried from the list, and then click Query to display the

user information. In this case, you can modify the user information.

3) Querying unallocated MINs: Query a bath of (up to 50 users) unallocated MINs

according to the entered MIN.You can select any of the mobile users.

3. User location information

Select User Information Handling > Location Information. The interface

appears, as shown in Fig. 3.3-14.

Fig. 3.3-14 User Location Information

1) Enter the MIN or MDN of the mobile user to be queried, and then clickQuery

to display, the user location information and user status information, including:

User location information

Whether the MS is activated.

The MSC(MSCID) and VLR(VLRID, VLRIN) where the user is located.

-21-


26/35


SMS address. There are three types of SMS address, BCD (default), IP(used for

data services) and SS7. These three types of SMS address are used for different

services.

User status information

User status: register, defaulting, and so on.

Whether the SMS is authorized.

Whether a short message is not sent out, that is, whether there is an SMSPDF

flag.

2) Modify (delete) user location

After querying the user location information, modify (or delete) the MSCID,

VLRID and VLRIN, and then click OK. If the operation succeeds, the system

displays a prompt, as shown in Fig. 3.3-15.

Fig. 3.3-15 Operation Success Prompt

4. Deleting a user

Caution: If a user is deleted from the user database, the user data cannot be

restored. Perform this operation with caution.

-22-


27/35


Select User Information Handling > Delete User to display the interface as


Fig. 3.3-16 Deleting a User

Confirm the user to be deleted according to the MIN or MDN of the mobile user.

To delete the authentication data when deleting the MDN or subscription

information, select Delete Authentication Information, and then click OK.

The system displays a confirmation dialog box as shown in Fig. 3.3-17. If you

clickOK, the user is deleted.

Fig. 3.3-17 Confirmation Dialog Box

-23-


28/35


5. Changing phone number

To change a phone number is to change the MDN of a user but without changingthe user authentication data and subscription information. Select User

Information Handling > Change MDN to display the interface as shown in

Fig. 3.3-18.

Fig. 3.3-18 Changing the MDN

The system provides two number change methods, by MIN or by MDN. Select

the method according to actual situation. By default, the system queries and

changes the number according to the MIN of the MS.

To select the MIN of the MS to change the number, enter the 10-digit MIN. To

select the MDN of the MS to change the number, enter the 11-digit MDN. In the

New Mobile Phone Number MDN pane, enter the new MDN, and then click

OK. The agent prompts whether the operation succeeds.

3.3.3Authentication Data Handling

1. Adding the authentication data of a user (the authentication data of a single user

must be added before the number is allocated).

-24-


29/35


Select Authentication Data Handling > Single Add to display the interface as


Fig. 3.3-19 Adding the Authentication Data of a User

Set the parameters, and then clickOKto add the authentication data of a user, or

clickCancel to cancel the operation.

Enter the three user authentication parameters: MIN, ESN and A-KEY.

Select Require Authentication and SSD Sharing according to the system

requirements.

The terminal type is classified according to the protocol: IS-54-B, IS-136, IS-95,

IS-95-A, IS-88, IS-94 and IS-91.

For the authentication algorithm version, accept the default value.

2. Querying (modifying) user authentication data

Select Authentication Data Handling > Query. The authentication data dialog

box appears on the user interface of the agent, as shown in Fig. 3.3-20.

-25-


30/35


The query can be implemented according to MIN or MDN of the user. Enter the

MIN or MDN of the user, and then click Query to display the user

authentication data. Modify the authentication data on the interface, and then

clickOK.

Fig. 3.3-20 Querying Authentication Data

3. Authentication indication

Select Authentication Data Handling > Authentication Indication to display

the interface as shown in Fig. 3.3-21.

You can query the information according to the MIN or MDN of the user. Enter

the MIN or MDN, and then click Query to display the user authentication

information. The SSD sharing can be selected according to the system

requirements.

-26-


31/35


According to the system requirements, select the corresponding authentication

indication SSD update or Unique query, and then click OK to implement

the authentication indication. SSD update includes the unique query

procedure, so the Unique query turns grey when SSD update is selected.

Fig. 3.3-21 Authentication Indication Interface

3.3.4Batch Processing Menu

1. File conversion

The file conversion function converts the text files with MIN, ESN and A_KEY

into format files (*.ZXC) which meet the requirements of the agent for batch

adding users.

Select Batch Processing > File Conversion to display the interface as shown in

Fig. 3.3-22.

Enter the file name and path of the file (original file) to be converted and the

converted file and the number of users to be processed (In principle, this number

shall be less than or equal to the number of existing MINs in the original file,

that is, the number of users), and then clickOK. The agent automatically reads

the content of the original file and forms a file in specific format (*.ZXC).

Note: The extension of the converted file shall be ZXC. Through the Batch

adding users function, the system can read such type of files and support batch

-27-


32/35


number allocation.

Fig. 3.3-22 File Conversion Dialog Box

The original text file shall be recorded in the format of MIN, A_KEY and ESN,

as shown in Fig. 3.3-23.

Fig. 3.3-23 Original Text File Format

Batch adding authentication information

-28-


33/35


Select Batch Processing > Batch Add Authentication Information to display

the interface as shown in Fig. 3.3-24.

Fig. 3.3-24 Batch Adding Authentication Information

In the File path or file name to be processed field, enter the format file name

(*.ZXC) and path, and specify the output file name and path for recording the

batch adding results. For other parameters, accept the default settings: Such as

require authentication, SSD sharing, termination type and authentication

algorithm version. After setting these parameters, click OK to batch add

authentication information.

Batch allocating numbers

This function is used to batch allocate MS numbers for the MINs to which the

authentication information is added in batches.

1) Select Batch Processing > Batch Number Allocation, or click the appropriate

icon on the toolbar to display the interface as shown in Fig. 3.3-25.

In the start MIN and start MDN text boxes, enter the MIN and MDN, and enter

the number of users to be added (In principle, this number shall be less than or

equal to the number of all MINs of the file in batch adding authentication

information, that is, the number of users).

Specify the batch number allocation and output path and file. This file is used to

save the records of successfully allocated numbers, and it can be used to batch

allocate numbers again.

During the procedure of adding a user, if the user number conflicts with the

-29-


34/35


existing user number in the database, the system prompts that the IMSI or

ISDN already exists in the database. You can select Abort, Retry or

Ignore according to actual situation. The specific description is as follows:

Abort: Terminate the batch processing operation.

Retry: Retry to write the current MS record.

Ignore: Skip this MS and read the next piece of MS data.

Fig. 3.3-25 Opening the Batch Number Allocation Dialog Box

-30-


35/35


2) For the subscription information about batch allocated numbers, set the

parameters in the default setting dialog box, as shown in Fig. 3.3-26.

Fig. 3.3-26 Default Setting Dialog Box

Course Code Course Name

Documents

Transcript of Course Code Course Name