Operation and Maintainance of Hlr9820

5/26/2018 Operation and Maintainance of Hlr9820

1/69

Huawei-UET Joint Telecom IT Center

OPERATION AND MAINTAINANCE

OF HLR9820


2/69


Alarm Management


3/69


Fault Alarm

When a fault alarm arises, its status is Not cleared.

You can use the following methods to clear a fault alarm:

Automatic clear

Manual clear

Reset clear The severity of a fault alarm is higher than that of an event alarm.

If a fault alarm arises, you must clear it. Such an alarm is reported

as a Fault.


4/69


Event Alarm

An event alarm denotes a transient state of a device when an

accident occurs.

An event alarm need not be cleared and is reported as Event.

Some event alarms arise periodically.


5/69


Active Alarm

Active alarms refer to:

Fault alarms that are not cleared

Fault alarms that are not acknowledged

Critical event alarms that are not acknowledged


6/69


Alarm Log and Alarm Serial

Number The alarm log records all alarms.

The alarm system stores the information of all alarms. Each record

has a serial number, that is, the alarm serial number. A serial

number uniquely identifies an alarm record.


7/69


Alarm Severity

The alarm severity identifies the severity of an alarm.

It can be categorized into:

Critical alarm: global fault alarms and event alarms that may

break down the host

Major alarm: local fault alarms and event alarms arises to

boards or circuits

Minor alarm: general fault alarms and event alarms indicating

the maloperation of boards or circuits

Warning: warning fault alarms and event alarms that affect no

system performance


8/69


Customizing Alarms

The color of an alarm record indicates the status of the alarm. You

can use the default color in the system or define a new one.

To set the attributes of alarms, perform the following steps:

Step 1 Choose Start > Programs > Huawei Local

Maintenance Terminal > Local Maintenance Terminal.

The system displays the HLR9820 Local Maintenance Terminal

window.

Step 2 Choose Fault Management > Alarm

Customization.


9/69


Setting Alarm Attributes

Step 1 Choose Start > Programs > Huawei Local Maintenance

Terminal > Local Maintenance Terminal. The system displays the

HLR9820 Local Maintenance Terminal window

Step 2 Choose Fault Management > Alarm Customization.

Step 3 Set the fields in the dialog box.

You can also click Default to use the default settings.

Step 4 Click OK.

----End


10/69



11/69


Browsing the Alarm Information

To browse the

alarm information,

choose Fault

Management >

Browse Alarm or

click


12/69


Querying Alarm Log

Step 1 Choose Fault

Management > Query

Alarm Log or click .


13/69



14/69


Clearing Alarms Manually

You can manually clear fault alarms only.

To manually clear a fault alarm, perform the

following steps:

Step 1 Right-click the fault alarm.

Step 2 Select Manually Refresh.

---End


15/69


Other Functionalities

Deleting Cleared Alarms

Saving the Alarm Information

Printing the Alarms


16/69


Setting the Alarm Box Shield

Severity After you set the shield severity of the alarm box, the BAM server

does not report alarms of lower severities to the alarm box.

Choose Fault Management > Alarm Box Operation > Shield Severity

Set.


17/69


OAM STRUCTURE OF HLR9820


18/69


Structure of the OAM of HLR9820


19/69


Starting the BAM Manager

To start the BAM

Manager, choose Start >

Programs > HLR9820

Operation and

Maintenance Center >HLR9820 BAM Manager.


20/69


LMT

The LMT has the following applications:

HLR9820 Performance Management System

HLR9820 Server Gateway Tool

LMT Service Manager

Local Maintenance Terminal Trace Viewer

Monitor Viewer

Uninstall Local Maintenance Terminal


21/69


LMT Window


22/69


Server Gateway Tool

The server gateway tool is an auxiliary tool of the BAM. It is

responsible for forwarding the alarms of the BAM to the alarm box.

The tool connects with the BAM through the TCP/IP network and

with other devices through serial ports. Thus, the tool exchanges

messages between the TCP/IP network and serial ports.

It runs on: The BAM

The Local area network (LAN) where the BAM resides

Any computer that communicates with the BAM through the TCP/IP network


23/69


DEVICE PANEL


24/69


Device Panel

The device panel shows the configuration of each subrack (frame).

To view the device panel, perform the following steps:

Step 1 On the LMT, click the Device Panel tab.


25/69


Device Panel

Step 2 Double-click a rack.

The Device Panel Management

window, showing the front boards

configured, is displayed


26/69


Device Panel

Step 3 Right-click the frame of the

panel pane.

Step 4 Select Switch Shelf

Direction.

The back panel, showing the back

boards configured, is displayed.


27/69


Viewing the Board Information

Step 1 Right-click the board on the device panel.


28/69


Viewing the Board Information

Step 2 Select Display Board

Status.

The Result information window is

displayed,

Step 3 Specify Report Type.

Step 4 Click Save As.

The information queried is saved.

----End


29/69


Board Management

Resetting a Board

Swapping a Board

Querying CPU Usage

Querying the Memory Usage


30/69


SMU


31/69


Overview

The home location register (HLR) stores the data of all the home

subscribers. The data includes:

Subscriber identification data

Basic service information

Supplementary service information

Operator determined barring (ODB) service information

Roaming restriction information

Customized Applications for Mobile Network Enhanced Logic (CAMEL)

subscription information

General packet radio service (GPRS) subscription information

Subscriber management refers to managing the data of subscribers

in the HLR.


32/69


Functionality

Managing subscriber data

Interfacing business hall (BNH) developed by a third party

In this way, the SMU implements management on the subscriber

data, thus satisfying different management requirements of

operators.


33/69


Structure of SMU


34/69


SMU Client

The HLR9820 SMU client offers an MML-based graphic terminal,

through which you can manage operator data and subscriber data.


35/69


SMU Client Window


36/69


Navigation Tree Pane


37/69


MML Command Pane


38/69


Shortcut Icons in MML Command

Pane


39/69


MML Command Format

Action[Object]:[ParameterList];

Action is an abbreviated verb composed of three upper case letters,

and Object is a noun composed of three to seven upper case

letters.

Some commands may have Action only.

If a command has no parameter, the colon (:) can be omitted.

Parameters are separated by commas (,), and a parameter and its

value are separated by an equal sign (=).

The parameter names must be in uppercase.

The sequence of parameters is defined by each command.


40/69


MML Command Format---Data

Types Data type can be of any one of these formats.

d


41/69


MML Command Format---

Parameter Types

Mandatory parameter (M)

parameters that you must specify.

All the mandatory parameters are highlighted in red.

Conditional parameter (C)

parameters that can be mandatory or optional depending on specific conditions.

Optional parameter (O)

parameters that you need to or you need not specify. Some optional parameters

offer default values. You can use the default values if they do not conflict with

other configurations.


42/69


OPERATOR MANAGEMENT


43/69


Role Management

The authority of each operator has the following two attributes:

Role attribute

It defines the MML commands that the operator can run.

Number segment attribute

It defines the range of number segments that the operator can

manage.


44/69


Adding and Modifying the Rule

To add a role named KI and authorize the corresponding operator to add, query,

and delete KI, run the following command:

ADD ROLE: NAME="KI", RULE= "ADD KI"&"LST KI"&"RMV KI";

To modify the RULE of the role abc and authorize the new RULE to add, modify,

and query the role, run the following command:

MOD ROLE: NAME="abc", RULE="ADD ROLE"&"RMV ROLE"&"MOD ROLE";


45/69


Querying and Removing a Rule

To query the role with the name KI, run the following command:

LST ROLE: NAME="KI";

To delete the role with the name KI, run the following command:

RMV ROLE: NAME="KI";


46/69


Number Segment Management

The number segment can be a range of IMSIs or MSISDNs.

Each operator can manage at most 255 IMSI number segments or

255 MSISDN number segments.

Addi d R i N b


47/69


Adding and Removing a Number

SegmentSuppose the number segment for the operator NKR and set the parameters as

follows:

Start MSISDN: 8613900000000

End MSISDN: 8613900009999

For adding a number segment:

ADD OPRANGE: OPNAME="NKR", BEGINISDN="8613900000000",

ENDISDN="8613900009999";

For removing a number segment:

RMV OPRANGE: OPNAME="NKR", BEGINISDN="8613900000000",

ENDISDN="8613900009999";


48/69


Operator Management

In the HLR9820, the operators comprise:

One system administrator

Multiple operators with the authority level ranging from 1 to 4


49/69


Adding an Operator

The command ADD OPR is a system command

and cannot be run through the Command input

field.

Step 1 On the SMU client, choose MML

Command > System Management > OperatorManagement > Add Operator or choose System

> Add Operator.

Step 2 Specify the fields, and then click OK.

----End


50/69


Modifying an Operator

On the SMU client, choose MML Command >

System Management > Operator

Management > Modify Operator or choose

System > Modify Operator.

The Modify Operator dialog box is displayed

R i d Q i


51/69


Removing and Querying an

Operator To remove the operator KI, run the following command:

RMV OPR: OPNAME="KI";

To query the data of the operator whose role name is ki, run the

following command:

LST OPR: ALL=FALSE, ROLENAME="ki";


52/69


AUTHENTICATION

MANAGEMENT


53/69


Authentication Parameters

Authentication Triplet

Data Stored in the SIM Card

Data Stored in the AuC


54/69


Authentication Triplet

Random challenge (RAND): The RAND is generated by the random

number generator and is used to calculate the other two

parameters in the triplet. It is 16 bytes long.

Signed response (SRES): The SRES is generated through Algorithm

A3 based on RAND and KI. It is used to determine whether theauthentication is passed. It is four bytes long.

Cipher key (KC): The KC is generated through Algorithm A8 based on

RAND and KI. It is used as the cipher key for radio channel

encryption. It is eight bytes long.


55/69


Data Stored in the SIMCard

Embedded data: It contains international mobile subscriber identity

(IMSI), KI, and A3 and A8 (authentication algorithms). These

contents are unchangeable.

Temporary network data: It contains temporary mobile subscriber

identity (TMSI), location area identity (LAI), KC, CKSN, and therelated data of the barred services in the PLMN.


56/69


Data Stored in the AuC

Subscriber data: IMSI, used to identify the mobile subscriber.

KI: Individual subscriber authentication key. It is as same as that

saved in the SIM/USIM card.

K4: Ciphering key of KI, used to encrypt or decrypt the KI. It is eight

bytes long.

Serial number of K4: Index of K4, used to obtain the K4. If the valueis 0, it means that the KI is not encrypted with K4. That is, the

current KI is a decrypted value.

Authentication algorithms (A3 and A8): Used to generate the

encryption and authentication.


57/69


K4 Management

The KI is set for the subscriber authentication.

For the sake of security, encrypt the KI with an encrypted key. In the

HLR9820 system, the key is K4. Before loading the KI, load the

related K4 first.

The KI is usually stored in text format in the disk. Loading KI isactually to load this file.

When loading a KI, specify the KI text file and the serial number of the K4 used to

encrypt the KI.


58/69


Adding, Removing and Checking K4

Suppose a K4 with the parameters as follows:

K4 serial number: 2

K4 value: ABCDEF1234567890

Adding a K4:

ADD K4: K4SNO=2, K4VALUE="ABCDEF1234567890";

Removing a K4:RMV K4: K4SNO=2;

Checking K4 values:

CHK K4: K4SNO=2, K4VALUE="ABCDEF1234567890";


59/69


OP Management

The operator variant algorithm configuration field, namely, OP, is

introduced when the MILENAGE algorithm is used.

The same OP can be used for all the subscribers of an operator to

distinguish them from those of other operators.

The HLR9820 supports multiple Ops

You can add, remove, modify and query an OP.


60/69


KI Management

The KI is set for the subscriber authentication.

For the sake of security, encrypt the KI with an encrypted key. In the

HLR9820, the key is K4.


61/69


Loading KI

To load a KI for a subscriber and set the parameters as follows:

IMSI: 460880009123456

KI value: 1234567890ABCDEF1111111111111111

K4 serial number: 2

Card type: SIM

Authentication algorithm type: COMP128_1

Run the following commands:

ADD K4: K4SNO=2, K4VALUE="1234567890123456";

ADD KI: IMSI="460880009123456",

KIVALUE="1234567890ABCDEF1111111111111111",

K4SNO=2, CARDTYPE=SIM, ALG=COMP128_1;


62/69


Querying and Checking KI

To query the KI of the subscriber whose IMSI is 460880009123456,

run the following command:

LST KI: IMSI="460880009123456",

To check the KI of the subscriber whose IMSI is 460000009123456,

run the following command:

CHK KI: IMSI="460000009123456";


63/69


Modifying Card Parameters

This task modifies the USIM or SIM card parameters of subscribers.

If the specified subscriber is roaming and reachable, the HLR sends

a cancel location message to the VLR/SGSN that the subscriber

resides and deletes the related data.

To modify the card type for the subscriber whose IMSI is460880009123456

MOD CARDPARA: IMSI="460880009123456", K4SNO=2,

CARDTYPE=USIM, ALG=MILENAGE, OPSNO=1;


64/69


Modifying Card Parameters

Operation Procedure

Step 1 Create an IMSI file.

Skip this step if you modify the card parameters of the subscribers with

consecutive IMSIs.

Step 2 Log in to the FTP client, and then upload the file to the SMUserver.

Step 3 On the SMU client, run the command MOD CARDPARAto

modify the USIM or SIM card

parameters.

----End


65/69


SUBSCRIBER MANAGEMENT


66/69


Data Stored in the HLR

The data stored in the HLR can be classified into:

Data of GPRS Subscribers

Data of Non-GPRS Subscribers


67/69


Data of the GPRS Subscribers

Subscriber information: including IMSI, MSISDN, and subscriber

status

Basic service information: including the bearer service code

Operator determined barring (ODB) information: including the

information of the GPRS ODB data services

Roaming restriction information: including the information of theroaming restriction service

GPRS subscription information: including GPRS subscription

information, SGSN CAMEL subscription information, GPRS CAMEL

subscription information, and SMS CAMEL subscription information


68/69


Data of the Non-GPRS Subscribers

Subscriber information: including IMSI, MSISDN, subscriber type,

and subscriber status

Basic service information: including the teleservice code and bearer

service code

Supplementary service information: including the call forwardinginformation, call barring information, and closed user information

(CUG)


69/69

Thank you

Documents

Operation and Maintainance of Hlr9820