hlr9820 performance measurement manual

Chapter 1 Overview of Performance Measurement 1-1......................................

1.1 Basic Concepts 1-1......................................................................................1.1.1 Measurement Task 1-1........................................................................1.1.2 Measurement Type 1-2........................................................................1.1.3 Measurement Unit 1-2..........................................................................1.1.4 Measurement Entity 1-2.......................................................................1.1.5 Measurement Object 1-2......................................................................1.1.6 Measurement Time 1-2........................................................................1.1.7 Threshold 1-3.......................................................................................

1.2 Structure of HLR9820 Performance Measurement System 1-4...................1.3 Functions of HLR9820 Performance Measurement System 1-5..................

1.3.1 Task Management Function 1-5..........................................................1.3.2 Result Management Function 1-5........................................................1.3.3 Template Management Function 1-6...................................................1.3.4 Entity Management Function 1-6.........................................................1.3.5 Threshold Management Function 1-6..................................................

Chapter 2 Performance Measurement Operation 2-1.........................................

2.1 Precautions 2-1............................................................................................2.2 System Management 2-1.............................................................................

2.2.1 Logging In to System 2-2.....................................................................2.2.2 Managing Office Information 2-3..........................................................2.2.3 Customizing System Configuration 2-5................................................

2.3 Measurement Task Management 2-6...........................................................2.3.1 Creating Measurement Task 2-6..........................................................2.3.2 Modifying Measurement Task 2-17........................................................2.3.3 Deactivating Measurement Task 2-22...................................................2.3.4 Activating Measurement Task 2-23........................................................2.3.5 Querying Measurement Task 2-23.........................................................2.3.6 Checking Detailed Information of Measurement Task 2-24...................2.3.7 Deleting Measurement Task 2-25..........................................................

2.4 Measurement Result Management 2-26........................................................2.4.1 Querying Measurement Result 2-26......................................................2.4.2 Dumping Measurement Result 2-31......................................................

2.5 Template Management 2-33..........................................................................2.5.1 Creating Templates 2-33........................................................................2.5.2 Modifying Template 2-43........................................................................2.5.3 Deleting Template 2-43..........................................................................

2.6 Custom Entity Management 2-43...................................................................2.6.1 Creating Custom Entity 2-43..................................................................

2.6.2 Modifying Custom Entity 2-45................................................................2.6.3 Deleting Custom Entity 2-46..................................................................

2.7 Example 2-46.................................................................................................2.7.1 Configuration Information 2-46...............................................................2.7.2 Operation Flowchart 2-47.......................................................................2.7.3 Operation Procedure 2-48......................................................................

Chapter 3 Analysis of Performance Measurement Results 3-1.........................

3.1 Analysis Methods 3-1...................................................................................3.2 Analysis of Common Performance Measurement Tasks 3-2.......................

3.2.1 CPU Utilization Measurement 3-2........................................................3.2.2 MAP Performance Measurement 3-4...................................................3.2.3 CPU Performance Measurement 3-5...................................................3.2.4 MTP Signaling Link Measurement 3-6.................................................3.2.5 SCCP Availability Measurement 3-7....................................................3.2.6 SCCP Performance Measurement 3-9................................................

Appendix A Performance Measurement Entity A-1.............................................

A.1 Global Component A-1.................................................................................A.2 HDU Traffic Task A-2...................................................................................

A.2.1 CPU Performance Measurement A-2..................................................A.2.2 MAP Performance Measurement A-2..................................................A.2.3 SCS Performance Measurement A-6...................................................A.2.4 SUB (Subscriber) Performance Measurement A-7..............................A.2.5 SWB (Subscriber with BS) Performance Measurement A-7................A.2.6 SWC (Subscriber with CAMEL) Performance Measurement A-8........A.2.7 SWCS (Subscriber with CB SS) Performance Measurement A-9.......A.2.8 SWG (Subscriber with GPRS) Performance Measurement A-9..........A.2.9 SWL (Subscriber with LCS) Performance Measurement A-10..............A.2.10 SWLK (Subscriber with Lock) Performance Measurement A-10.........A.2.11 SWO (Subscriber with ODB) Performance Measurement A-11...........A.2.12 SWOS (Subscriber with Other SS) PerformanceMeasurement A-12..........................................................................................A.2.13 SWR (Subscriber When Roaming) PerformanceMeasurement A-13..........................................................................................

A.3 Signaling and Interface A-13..........................................................................A.3.1 M3UA Destination Entity Traffic A-13.....................................................A.3.2 M3UA Linkset Flux Traffic A-14.............................................................A.3.3 M3UA Linkset State Traffic A-16............................................................A.3.4 M3UA Signaling Link Traffic A-16..........................................................A.3.5 MTP Dest Signaling Point Traffic A-19...................................................A.3.6 MTP Linkset Traffic A-19........................................................................

A.3.7 MTP Signaling Link Traffic A-19.............................................................A.3.8 MTP3B Signaling DSP Measurement A-21...........................................A.3.9 MTP3B Signaling Link Measurement A-21............................................A.3.10 MTP3B Signaling Linkset Measurement A-23.....................................A.3.11 SAAL Link Measurement and Statistics A-24......................................A.3.12 SCCP Availability Statistic A-25...........................................................A.3.13 SCCP Performance Statistic A-25.......................................................A.3.14 SCCP Utilization Statistic A-26............................................................A.3.15 TCAP Availability Statistics A-27..........................................................A.3.16 TCAP Component Sublayer Performance Statistics A-28...................A.3.17 TCAP Component Utilization Statistics A-29.......................................A.3.18 TCAP Message Utilization Statistics A-30...........................................A.3.19 TCAP Transaction Sublayer Performance Statistics A-31...................

Appendix B MAP Performance Measurement Object Data B-1..........................

Appendix C Acronyms and Abbreviations C-1....................................................

Index .................................................................................................................

Huawei Technologies Proprietary

HUAWEI

HUAWEI HLR9820 Home Location Register Performance Measurement Manual

V600R002


HUAWEI HLR9820 Home Location Register

Performance Measurement Manual

Manual Version T2-031643-20041120-C-1.10

Product Version V600R002

BOM 31161443

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

Website: http://www.huawei.com

Email: [email protected]


Copyright © 2004 Huawei Technologies Co., Ltd.

All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks

, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800, TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN, HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye, Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co., Ltd.

All other trademarks mentioned in this manual are the property of their respective holders.

Notice

The information in this manual is subject to change without notice. Every effort has been made in the preparation of this manual to ensure accuracy of the contents, but all statements, information, and recommendations in this manual do not constitute the warranty of any kind, express or implied.


Summary of Updates

This section provides the update history of this manual and introduces the contents of subsequent updates.

Update History

This manual is updated for a major product version to maintain consistency with system hardware or software versions and to incorporate customer suggestions.

Manual Version Notes

T2-031643-20041008-C-1.00 Initial commercial release

T2-031643-20041120-C-1.10 Second commercial release

Updates of Contents

Updates between manual versions are cumulative. Therefore, the latest manual version contains all updates made to previous versions.

Updates Made between Versions 1.10 and 1.00

3.2.4 "MTP Signaling Link Measurement" is modified.


About This Manual

Release Notes

This manual applies to HUAWEI HLR9820 Home Location Register V600R002.

Organization

This manual introduces the structure and functions of the HLR9820 Performance Measurement System, operation methods, and analysis methods. It comprises the following chapters:

Chapter 1 Overview of Performance Measurement introduces the basic concepts related to performance measurement, and the structure and functions of the HLR9820 Performance Measurement System.

Chapter 2 Performance Measurement Operation introduces the operation methods of performance measurement.

Chapter 3 Analysis of Performance Measurement Results introduces the analysis methods of performance measurement results, and takes some common performance measurement tasks as examples for analysis.

Appendix A Performance Measurement Entity lists all the performance measurement entities, their meanings, and standard measurement points.

Appendix B MAP Performance Measurement Object Data lists all the MAP performance measurement objects.

Appendix C Acronyms and Abbreviations lists all the abbreviations used in the manual.

Intended Audience

The manual is intended for the following readers:

Wireless system engineers O&M technicians/engineers


Conventions

The manual uses the following conventions:

I. General conventions

Convention Description

Arial Normal paragraphs are in Arial.

Boldface Headings are in Boldface.

Courier New Terminal Display is in Courier New.

II. Command conventions


Boldface The keywords of a command line are in Boldface.

italic Command arguments are in italic.

[ ] Items (keywords or arguments) in square brackets [ ] are optional.

{ x | y | ... } Alternative items are grouped in braces and separated by vertical bars. One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets and separated by vertical bars. One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected.

[ x | y | ... ] * Optional alternative items are grouped in square brackets and separated by vertical bars. Many or none can be selected.

III. GUI conventions


< > Button names are inside angle brackets. For example, click the <OK> button.

[ ] Window names, menu items, data table and field names are inside square brackets. For example, pop up the [New User] window.

/ Multi-level menus are separated by forward slashes. For example, [File/Create/Folder].


IV. Keyboard operation

Format Description

<Key> Press the key with the key name inside angle brackets. For example, <Enter>, <Tab>, <Backspace>, or <A>.

<Key1+Key2> Press the keys concurrently. For example, <Ctrl+Alt+A> means the three keys should be pressed concurrently.

<Key1, Key2> Press the keys in turn. For example, <Alt, A> means the two keys should be pressed in turn.

V. Mouse operation

Action Description

Click Press the left button or right button quickly (left button by default).

Double Click Press the left button twice continuously and quickly.

Drag Press and hold the left button and drag it to a certain position.

VI. Symbols

Eye-catching symbols are also used in the manual to highlight the points worthy of special attention during the operation. They are defined as follows:

Caution, Warning, Danger: Means reader be extremely careful during the

operation.

Note, Comment, Tip, Knowhow, Thought: Means a complementary description.

Performance Measurement Manual HUAWEI HLR9820 Home Location Register Table of Contents

Huawei Technologies Proprietary i

Table of Contents

Chapter 1 Overview of Performance Measurement ................................................................... 1-1 1.1 Basic Concepts .................................................................................................................. 1-1

1.1.1 Measurement Task ................................................................................................. 1-1 1.1.2 Measurement Type ................................................................................................. 1-2 1.1.3 Measurement Unit ................................................................................................... 1-2 1.1.4 Measurement Entity ................................................................................................ 1-2 1.1.5 Measurement Object............................................................................................... 1-2 1.1.6 Measurement Time ................................................................................................. 1-2 1.1.7 Threshold ................................................................................................................ 1-3

1.2 Structure of HLR9820 Performance Measurement System .............................................. 1-4 1.3 Functions of HLR9820 Performance Measurement System ............................................. 1-5

1.3.1 Task Management Function.................................................................................... 1-5 1.3.2 Result Management Function ................................................................................. 1-5 1.3.3 Template Management Function ............................................................................ 1-6 1.3.4 Entity Management Function .................................................................................. 1-6 1.3.5 Threshold Management Function ........................................................................... 1-6

Chapter 2 Performance Measurement Operation ...................................................................... 2-1 2.1 Precautions ........................................................................................................................ 2-1 2.2 System Management......................................................................................................... 2-1

2.2.1 Logging In to System .............................................................................................. 2-2 2.2.2 Managing Office Information ................................................................................... 2-3 2.2.3 Customizing System Configuration......................................................................... 2-5

2.3 Measurement Task Management ...................................................................................... 2-6 2.3.1 Creating Measurement Task................................................................................... 2-6 2.3.2 Modifying Measurement Task ............................................................................... 2-17 2.3.3 Deactivating Measurement Task........................................................................... 2-22 2.3.4 Activating Measurement Task............................................................................... 2-23 2.3.5 Querying Measurement Task................................................................................ 2-23 2.3.6 Checking Detailed Information of Measurement Task.......................................... 2-24 2.3.7 Deleting Measurement Task ................................................................................. 2-25

2.4 Measurement Result Management.................................................................................. 2-26 2.4.1 Querying Measurement Result ............................................................................. 2-26 2.4.2 Dumping Measurement Result.............................................................................. 2-31

2.5 Template Management.................................................................................................... 2-33 2.5.1 Creating Templates............................................................................................... 2-33 2.5.2 Modifying Template............................................................................................... 2-43 2.5.3 Deleting Template ................................................................................................. 2-43


Huawei Technologies Proprietary ii

2.6 Custom Entity Management ............................................................................................ 2-43 2.6.1 Creating Custom Entity ......................................................................................... 2-43 2.6.2 Modifying Custom Entity ....................................................................................... 2-45 2.6.3 Deleting Custom Entity.......................................................................................... 2-46

2.7 Example ........................................................................................................................... 2-46 2.7.1 Configuration Information...................................................................................... 2-46 2.7.2 Operation Flowchart.............................................................................................. 2-47 2.7.3 Operation Procedure............................................................................................. 2-48

Chapter 3 Analysis of Performance Measurement Results ...................................................... 3-1 3.1 Analysis Methods............................................................................................................... 3-1 3.2 Analysis of Common Performance Measurement Tasks .................................................. 3-2

3.2.1 CPU Utilization Measurement ................................................................................. 3-2 3.2.2 MAP Performance Measurement............................................................................ 3-4 3.2.3 CPU Performance Measurement ............................................................................ 3-5 3.2.4 MTP Signaling Link Measurement .......................................................................... 3-6 3.2.5 SCCP Availability Measurement ............................................................................. 3-7 3.2.6 SCCP Performance Measurement.......................................................................... 3-9

Appendix A Performance Measurement Entity ..........................................................................A-1 A.1 Global Component ............................................................................................................A-1 A.2 HDU Traffic Task...............................................................................................................A-2

A.2.1 CPU Performance Measurement............................................................................A-2 A.2.2 MAP Performance Measurement ...........................................................................A-2 A.2.3 SCS Performance Measurement............................................................................A-6 A.2.4 SUB (Subscriber) Performance Measurement .......................................................A-7 A.2.5 SWB (Subscriber with BS) Performance Measurement.........................................A-7 A.2.6 SWC (Subscriber with CAMEL) Performance Measurement .................................A-8 A.2.7 SWCS (Subscriber with CB SS) Performance Measurement ................................A-9 A.2.8 SWG (Subscriber with GPRS) Performance Measurement ...................................A-9 A.2.9 SWL (Subscriber with LCS) Performance Measurement .....................................A-10 A.2.10 SWLK (Subscriber with Lock) Performance Measurement ................................A-10 A.2.11 SWO (Subscriber with ODB) Performance Measurement .................................A-11 A.2.12 SWOS (Subscriber with Other SS) Performance Measurement ........................A-12 A.2.13 SWR (Subscriber When Roaming) Performance Measurement ........................A-13

A.3 Signaling and Interface....................................................................................................A-13 A.3.1 M3UA Destination Entity Traffic............................................................................A-13 A.3.2 M3UA Linkset Flux Traffic.....................................................................................A-14 A.3.3 M3UA Linkset State Traffic ...................................................................................A-16 A.3.4 M3UA Signaling Link Traffic .................................................................................A-16 A.3.5 MTP Dest Signaling Point Traffic..........................................................................A-19 A.3.6 MTP Linkset Traffic...............................................................................................A-19 A.3.7 MTP Signaling Link Traffic....................................................................................A-19 A.3.8 MTP3B Signaling DSP Measurement ..................................................................A-21


Huawei Technologies Proprietary iii

A.3.9 MTP3B Signaling Link Measurement ...................................................................A-21 A.3.10 MTP3B Signaling Linkset Measurement ............................................................A-23 A.3.11 SAAL Link Measurement and Statistics .............................................................A-24 A.3.12 SCCP Availability Statistic ..................................................................................A-25 A.3.13 SCCP Performance Statistic...............................................................................A-25 A.3.14 SCCP Utilization Statistic....................................................................................A-26 A.3.15 TCAP Availability Statistics.................................................................................A-27 A.3.16 TCAP Component Sublayer Performance Statistics ..........................................A-28 A.3.17 TCAP Component Utilization Statistics ..............................................................A-29 A.3.18 TCAP Message Utilization Statistics ..................................................................A-30 A.3.19 TCAP Transaction Sublayer Performance Statistics ..........................................A-31

Appendix B MAP Performance Measurement Object Data.......................................................B-1

Appendix C Acronyms and Abbreviations .................................................................................C-1

Index ................................................................................................................................................ i-1

Performance Measurement Manual HUAWEI HLR9820 Home Location Register Chapter 1 Overview of Performance Measurement


1-1

Chapter 1 Overview of Performance Measurement

This chapter introduces the basic concepts related to performance measurement, and the structure and functions of the performance measurement system. It includes the following sections.

1.1 Basic Concepts Performance measurement, also named performance management or traffic measurement, refers to the various measurement activities carried out in the equipment and ambient communication networks. It includes traffic measurement, system resource measurement, signaling procedure measurement, and failure cause measurement. In the HLR9820 system, performance measurement focuses on system resource measurement and signaling procedure measurement.

Through performance measurement, you can learn the information of equipment operation, signaling exchange, and resource utilization. Measurement results provide references for operation management, planning, monitoring, and optimization of communication networks. In addition, the results provide detailed resource utilization in case of communication resource exhaust.

1.1.1 Measurement Task

A measurement task describes a specific performance measurement operation. It is a basic measurement unit of the HLR9820 Performance Measurement System. A measurement task contains three elements:

Measurement entity Measurement object Measurement time

The three elements determine a measurement task uniquely. When creating a measurement task, make sure to include all of the following parameters:

Measurement type Measurement unit Measurement entity Measurement object Measurement time

The HLR9820 Performance Measurement System supports a maximum of 128 measurement tasks.



1-2

1.1.2 Measurement Type

A measurement type is a collection of certain measurement units with certain identical properties. For example, HLR database unit (HDU) traffic measurement consists of CPU performance measurement and mobile application part (MAP) performance measurement.

1.1.3 Measurement Unit

A measurement unit, such as CPU Performance Measurement, MAP Performance Measurement, MTP Signaling Link Measurement, is a valid combination of a measurement entity and a measurement object. It reflects the traffic of a certain measurement object.

1.1.4 Measurement Entity

A measurement entity, also called a measurement index, is a parameter for which data is collected during measurement, such as call attempts and average seizure ratio.

Measurement entity includes two types, namely, original entity and custom entity.

I. Origianl Entity

The HLR 9820 Performance Measurement System provides some basic measurement entities, namely, original entities.

II. Custom Entity

Besides the original entities provided by the system, you can customize entities as needed. The customized entities are called custom entities. A custom entity is combined by original entities according to arithmetic expressions.

To customize an entity, use either of the following methods:

Define a new name and a calculation formula for the entity. Use the original name and define a new calculation formula for the original entity.

1.1.5 Measurement Object

A measurement object defines the object of a measurement task. It can be a physical entity, a logical entity, or their combination. For example, if you measure the signaling load of a link, the link is the measurement object.

1.1.6 Measurement Time

Measurement time includes the following necessary time information:

Start date Measurement days



1-3

Measure period Measurement time type Measurement time segment

I. Measurement Period

Measurement period specifies the interval that a measurement task outputs the measurement result.

In the HLR9820 Performance Measurement System, the available measurement periods include: 1 minute, 5 minutes, 15 minutes, 30 minutes, 1 hour, and 1 day. By default, the measurement period is 15 minutes.

II. Measurement Time Segment

The HLR9820 Performance Measurement System allows you to carry out measurement tasks in three time segments in a day. During each time segment, the measurement task is carried out according to specified measurement period. When a time segment expires, the measurement stops. Time segments cannot overlap with each other.

Measurement time segment and measurement period determine the time mode of a task in routine running.

III. Measurement Time Type

Measurement time type specifies the operation mode of a measurement task. It includes the following types:

Measure every day

Carries out measurement every day.

Measure day(s) every week

Carries out measurement on specified days in a week. For example, you can specify a measurement task to be carried out on Monday, Wednesday, and Friday of each week.

Measure day(s) every month

Carries out measurement on specified dates in a month. For example, you can specify a measurement task to be carried out on the 1st, 5th, and 13th of each month.

1.1.7 Threshold

Threshold, including upper threshold and lower threshold, is a standard defined for observing measurement entities before performance measurement.

If the measured value of a measurement entity is over the upper threshold or under the lower threshold, the equipment may be running abnormally. The setting of thresholds



1-4

helps to remind you of certain equipment status. Note that not all measurement entities have thresholds.

1.2 Structure of HLR9820 Performance Measurement System Figure 1-1 shows the structure of the HLR Performance Measurement System.

LMT BAM

Performancemeasurement process 1

...



Figure 1-1 Structure of HLR9820 Performance Measurement System

As shown in Figure 1-1, the HLR9820 Performance Measurement System includes the following parts:

I. LMT

LMT refers to local maintain terminal, providing a man-machine interaction interface. The LMT implements the following functions:

Receiving performance measurement commands and sending the commands to the back administration module (BAM).

Receiving performance measurement results from the BAM and displaying the results upon query.

II. BAM

BAM refers to back administration module, functioning as the communication bridge between the LMT and SAU. It implements the following functions:

Analyzing and converting the performance measurement requests from the LMT. Maintaining and managing performance measurement task queues. Interacting with performance measurement processes and sending performance

measurement queues to corresponding host modules correctly. Receiving the performance measurement data reported by the SAU and saving

the data to the BAM database. Outputting performance measurement reports to the specified output equipment

according to the specified mode.



1-5

III. Perforamnce Measurement Process

The performance measurement process collects equipment information and signaling information, converts the information into measurement results, and sends the results to the BAM. It implements the following functions:

Counting and timing various measurement entities when corresponding events occur.

Fulfilling the performance measurement requests from the LMT according to the interface protocol with the BAM.

Constituting application layer protocols to ensure transmission of measurement results to the BAM without error.

1.3 Functions of HLR9820 Performance Measurement System

The HLR9820 Performance Measurement System helps you to manage various performance measurements. To be specific, it provides the following functions:

1.3.1 Task Management Function

Task management function includes:

Creating Measurement Task Modifying Measurement Task Deactivating Measurement Task Activating Measurement Task Querying Measurement Task Checking Detailed Information of Measurement Task Deleting Measurement Task

1.3.2 Result Management Function

Result management function includes:

Result query function

Supports the query based on entity type, report type, time type, and any combination of them, and supports the query based on data with specific conditions.

Result display function

Supports display of measurement results in form of list and graphics. The graphic display includes histogram, folded line chart, and pie chart, providing you with clear and visual performance measurement reports.

Result saving function



1-6

Supports saving measurement results in printing file, in text file, or in the BAM database. This function facilitates analysis of performance measurement results in the future.

1.3.3 Template Management Function

The HLR9820 Performance Measurement System supports management of the following templates:

Entity template Object template Time template Task template

You can set the information commonly used for performance measurement into templates and save them in the system. When creating measurement tasks, you can invoke the templates to get the preset information. This simplifies the operation and improves the efficiency.

1.3.4 Entity Management Function

Besides the original entities, the HLR9820 Performance Measurement System allows you to customize entities by combining original entities according to arithmetic expressions. This function helps you to collect useful performance measurement data and observe the running status of the existing network flexibly.

After creating measurement entities, you can modify and delete them as needed.

1.3.5 Threshold Management Function

The HLR9820 Performance Measurement System provides a threshold alarm function. This function helps you to monitor the network running status and detect unreasonable performance data in time, thus assisting system maintenance.

You can set thresholds for the measurement entities of specific measurement tasks. You may set the upper threshold or the lower threshold only, or set them both. If the measured value of a measurement entity exceeds the upper or lower threshold during performance measurement, the HLR9820 Performance Measurement System will report an alarm to the Alarm System automatically. You can analyze the cause of the abnormal measurement value according to the alarm information, and then clear the fault.

Performance Measurement Manual HUAWEI HLR9820 Home Location Register Chapter 2 Performance Measurement Operation


2-1

Chapter 2 Performance Measurement Operation

To help you acquaint and master the performance measurement operation, this chapter introduces:

Operation methods of performance measurement Operation example of performance measurement

2.1 Precautions If a workstation fails to execute a performance measurement operation due to insufficient authority, a prompt box as shown in Figure 2-1 is displayed, prompting failure of executing the operation.

Figure 2-1 Insufficient authority alarm

In this case, you must:

1) In the HLR9820 Operation and Maintenance System of the BAM, add the operation authority to the workstation.

Notes

Only the system administrator can add operation authority.

2) Re-log in to the performance management system from the workstation.

For details, see HUAWEI HLR9820 Home Location Register Operation Manual – Routine Operation.

2.2 System Management This section details how to manage the HLR9820 Performance Management System.

The system management involves:

Logging In to System



2-2

Managing Office Information Customizing System Configuration

2.2.1 Logging In to System

To execute a performance measurement operation, you must log in to the performance management system correctly.

To log in to that system, proceed as follows:

1) In the workstation, select [Start/Programs/HLR9820 Administration System/HLR9820 Performance Management System].

The [Operator Login] dialog box is displayed, as shown in Figure 2-2.

Figure 2-2 [Operator Login] dialog box

2) Set login information as below: In the [Operator] box, type a user name (the default is "Admin"). In the [Password] box, type the corresponding password. In the [Office] list, select the login office.

3) Click <OK>.

The [HLR9820 Performance Management System] window is displayed, as shown in Figure 2-3.



2-3

(1) Menu bar (2) Toolbar (3) Navigation tree pane (4) Prompt window (5) Status bar

Figure 2-3 Performance management system

2.2.2 Managing Office Information

This section guides you through the management of office information. Managing office information involves:

Setting Office Information Modifying Office Information Deleting Office Information

I. Setting Office Information

If the office needed is not found in the [Office] list as shown in Figure 2-2, you must set the office information as below:

1) In the [Operator Login] dialog box shown in Figure 2-2, click <Office...>.

The [Manage Office Information] dialog box is displayed, as shown in Figure 2-4.



2-4

Figure 2-4 Managing office information

2) Set office information as below: In the [Office name] box, type the name of the office where the BAM resides.

If the name typed is identical with the existing office, this operation is to modify the IP address of the office.

In the [IP address] box, type the IP address of the BAM.

The IP address must be unique.

3) Click <Set>.

The configured office information is added to the [Office] list.

4) Click <OK> to close the [Manage Office Information] dialog box.

II. Modifying Office Information

If the IP address of the office is incorrect, you must modify the office information as below. Otherwise, you are unable to log in to the performance management system normally.

1) Select [System/Office Management].

The [Manage Office Information] dialog box is displayed.

2) In the [Office] list, select the office to be modified.

The information of the selected office is displayed in the [Office name] and [IP address] boxes.

3) In the [IP address] box, modify the BAM IP of the office, and then click <Set>, 4) Click <OK>.

III. Deleting Office Information

You can delete needless office information as below:



2-5

1) Select [System/Office Management].

The [Manage Office Information] dialog box is displayed.

2) In the [Office] list, select the office to be deleted.

The information of the selected office is displayed in the [Office name] and [IP address] boxes.

3) Click <Delete>.

The system prompts "Are you sure you want to continue?"

4) Click <OK>.

The selected office disappears from the [Office] list.

5) Click <OK> again.

2.2.3 Customizing System Configuration

System configuration involves:

Command timeout System lock time

By customizing system configuration, you can set the command timeout time and system lock time according to actual requirements.

To customize the system configuration, proceed as follows:

1) Select [System/System Customization…].

The [System Customization] dialog box is displayed, as shown in Figure 2-5.

Figure 2-5 Customizing system configuration

The following explains the parameters in the figure:

Command Timeout

Value: Ranges from 10 seconds to 3600 seconds.

The default value is 80 seconds.



2-6

System Lock Time

Value: Ranges from 0 to 1440 minutes.

0 indicates no auto lock function.

The default value is 20 minutes.

2) Type a command timeout time in the [Command Timeout] box and a system auto lock time in the [System Lock Time] box.

3) Click <OK>.

2.3 Measurement Task Management This section guides you through the management of measurement tasks.

This section involves:

Creating Measurement Task Modifying Measurement Task Deactivating Measurement Task Activating Measurement Task Querying Measurement Task Checking Detailed Information of Measurement Task Deleting Measurement Task

2.3.1 Creating Measurement Task

Figure 2-6 shows the procedure of creating a measurement task.



2-7

Configure basic information

Configure object information

Configure entity information Select a task template

Are thresholds needed?

Configure thresholds

Configure other information

End

Is a task template created?

Start

Configure time information

Yes

Yes

No

No

Figure 2-6 Measurement task creation flowchart

The following describes the procedure of creating a performance measurement task:

I. Configuring Basic Information

To configure the basic information of the measurement task, proceed as follows:

1) Select [Task/Create Task...].

The [Create a New Task] dialog box is displayed, as shown in Figure 2-7.



2-8

Figure 2-7 Creating a new performance measurement task

2) Configure the basic information of the new task as below: In the [Task name] box, type a task name. In the [Task description] box, type brief description of the task. In the [Traffic task type] list, select a type for the new performance

measurement task. In the [Measurement unit] list, select a corresponding measurement unit

based on the task type selected.

If task templates are created and you are required to create measurement tasks using task templates, select a task template in the [Task template] list, and then go to Configuring Other Information. Otherwise, go to Configuring Entity Information.

II. Configuring Entity Information

To configure the entity information, proceed as follows:



2-9

1) Click the [Entity] tab.

The [Entity] dialog box is displayed, as shown in Figure 2-8.

Note:

If custom entities are created, they will be displayed in [Available custom entities].

Figure 2-8 Configuring entity information

2) Select entities of the measurement task. If entity templates are set and available, select an entity template in the [Entity

template] list. If entity templates are unavailable, select an entity according to the following

operations:

Note:

Selecting custom entities is similar to selecting original entities.



2-10

Operation Result

In [Available static entities], select a measurement entity, and then click .

The measurement entity selected is added to [Selected static entities].

Click . All measurement entities in [Available static entities] are added to [Selected static entities].

In [Selected static entities], select a measurement entity, and then click .

The measurement entity selected from [Selected static entities] is transferred to [Available static entities].

Click . All measurement entities selected from [Selected static entities] are transferred to [Available static entities].

III. Configuring Object Information

To configure the object, proceed as follows:

1) Click the [Object] tab.

The [Object] dialog box is displayed.

The dialog box varies with measurement tasks, as shown in Figure 2-9 and Figure 2-10.

2) Add an object instance. If object templates are set and available, select an object template in the

[Object template] list. If object templates are unavailable, add an object according to the following

operations:



2-11

Figure 2-9 [Object] dialog box 1

As shown in Figure 2-9, you can do as follows:

a) Click <Select Object Data>.

The [Select Object Data] dialog box is displayed.

b) In [Select Object Data], select an object instance check box, and then click <OK>.

The selected object instance is added to [List of Object Instances which have been set].



2-12


As shown in Figure 2-10, you can do as follows:

a) In [Network identifier] and [Code of], set proper parameters.

The <Add Object Instance> button becomes available.

b) Click <Add Object Instance>.

The configured object instance is added to [List of Object Instances which have been set].

IV. Configuring Time Information

To configure the time information, proceed as follows:

1) Click the [Time] tab.

The [Time] dialog box is displayed, as shown in Figure 2-11.



2-13

Figure 2-11 Configuring time information

2) Set the time information of measurement task. If time templates are set and available, select a time template in the [Time

template] list. If the time template is unavailable, set the time information as below:

− Select the "Start Date" check box, and then set the date to start the measurement.

The default is the current date.

− Select the "Statistics Duration" check box, and then set how long the measurement lasts.

The value ranges from 1 day to 1024 days.

This item can be set only after the "Start Date" is selected.

If this item is not selected, the performance measurement task continues permanently.

− In the [Measure Period] list, select a time to determine how often the measurement result is output.

− Under [Measure Date(s)], select the date(s) to measure.

Option Result

Measure every day The system measures every day.



2-14

Option Result


You can select several days. Then the system measures only in the selected days every week.


You can select several dates. Then the system measures only in the selected dates every month.

− Under [Measure Time Segment], tune the slider to set time segments of the measurement task.

Indicator of slider Result

Top Only the first time segment can be set.

Middle Both the first and second time segments can be set.

Bottom Three time segments can be set.

Start Time x (x = 1, 2, and 3) indicates the start time of time segment x, and End Time x indicates the end time of time segment x. Both the start time and end time range from 00:00 to 23:59. The end time must be greater than the start time.

The second time segment cannot overlap the first one. The third time segment cannot overlap the first and second time segments.

V. Configuring Threshold Information

You can set upper and lower thresholds to monitor some important measurement entities. Thus, an alarm is generated when an entity exceeds the upper or lower threshold.

Note:

Configure thresholds for the measurement entity with the threshold property only. Otherwise, go to Configuring Other Information.

To configure the threshold, proceed as follows:

1) Click the [Threshold] tab.

The [Threshold] dialog box is displayed, as shown in Figure 2-12.



2-15

Figure 2-12 Configuring threshold information

2) Set thresholds of measurement entities.

Note:

You can set thresholds for a maximum of four measurement entities. You can set the upper or lower threshold, or both. The upper threshold must be

greater than the lower.

For set thresholds of measurement entities, proceed as below.

Operation Result

In [Entity Threshold List], select a measurement entity, and then set the lower threshold in the [Lower Threshold] box and upper threshold in the [Upper Threshold] box. Then click <Set Threshold>.

The thresholds of measurement entity are set. Meanwhile, the threshold information is added to [List of Thresholds which have been set].

In [List of Thresholds which have been set], select the thresholds to be deleted, and then click <Delete Threshold>.

The selected thresholds are deleted. Meanwhile, the records of the selected thresholds disappear from [List of Thresholds which have been set].



2-16

VI. Configuring Other Information

Other information includes:

Sampling parameters Output device of measurement reports Output arrangement of measurement reports

To configure other information, proceed as follows:

1) Click the [Other] tab.

The [Other] dialog box is displayed, as shown in Figure 2-13.

Figure 2-13 Configuring other information

2) Set the sampling parameter, output device, and output arrangement. Sampling parameter

The default is 100% for sampling rate or 65535 for sampling counts.



2-17

Not all measurement units have sampling parameters.

Output device

You can select one or multiple devices below to output measurement reports:

− Current workstation

− Traffic performance port

− Network manager port

Output arrangement

Select an output mode for measurement reports.

Option Result

PerPeriod Output Outputs measurement results every measurement period.

Specific Output Outputs measurement results at the specified time.

Over Threshold Output

Outputs measurement results only when the measurement value exceeds the thresholds.

3) Click <OK>.

The system prompts "Operation succeeded".

4) Click <OK>.

In the [Task] tab, the measurement task appears in the "Task list (All)" navigation tree.

2.3.2 Modifying Measurement Task

After creating a performance measurement task, you can modify its configuration information according to the actual conditions. Modifying measurement task has no impact on the running status of the measurement task, but it may change the measurement result.

Note:

After modifying the configuration of a performance measurement task, you can query the measurement results before and after the modification in the same task result list.

The modification of a measurement task may involve:

I. Modifying Name

To modify the name of the measurement task, proceed as follows:



2-18

Step Operation

1 In the navigation tree "Task list (All)", right-click the task to be modified. A shortcut menu is displayed.

2 Select [Modify Task Name]. The [Modify Task Name] dialog box is displayed.

3 In the [Task Name] box, modify the name of measurement task.

4 Click <OK>. The system prompts "Operation succeeded".

5 Click <OK>.

II. Modifying Output Arrangement of Measurement Reports

To modify the output arrangement of measurement reports, proceed as follows:

Step Operation


2 Select [Modify Task Output Mode]. The [Modify Output Mode] dialog box is displayed.

3

In [Output Arrangement], modify the output mode of measurement reports. If you select "PerPeriod Output", the system outputs reports every

measurement period. If you select "Specific Output", the system outputs reports at the specified

time. If you select "Over Threshold Output", the system outputs reports only

when the measurement value exceeds the thresholds.


5 Click <OK>.

III. Modifying Output Device of Measurement Reports

To modify the output device of measurement reports, proceed as follows:

Step Operation


2 Select [Modify Output Device]. The [Modify Output Device] dialog box is displayed.



2-19

Step Operation

3

In [Output Device], modify the output device of measurement reports. Current workstation Traffic performance port Network manager port


5 Click <OK>.

IV. Modifying Entity Information

Note:

If custom entities exist in the measurement task, they will appear in [Available custom entities] or [Selected custom entities]. Modifying the information of custom entities is similar to modifying that of original ones.

To modify the entity information, proceed as follows:

Step Operation


2 Select [Modify Measurement Entities]. The [Modify Measurement Entities] dialog box is displayed.

3

In the [Entity] tab, modify the entity information of the performance measurement task. In [Available static entities],

Select an entity, and then click . The selected measurement entity is added to [Selected static entities]. Click .

All measurement entities in [Available static entities] are added to [Selected static entities].

In [Selected static entities], Select an entity, and then click .






2-20

Step Operation

5 Click <OK>.

V. Modifying Time Information

To modify the time information, proceed as follows:

Step Operation

1 In the navigation tree "Task list (All)", right-click the measurement task to be modified. A shortcut menu is displayed.

2 Select [Modify Time Info]. The [Modify Time Info] dialog box is displayed.

3 In the [Time] tab, modify the time information of the measurement task.


5 Click <OK>.

VI. Modifying Sampling Parameter

Note:

Not all measurement units have sampling parameters.

To modify the sampling parameters, proceed as follows:

Step Operation


2 Select [Modify Sampling Parameter]. The [Modify Time Info] dialog box is displayed.

3 In [Sampling Parameter], modify the sampling parameters of the measurement task.


5 Click <OK>.



2-21

VII. Adding Threshold of Measurement Entity

To add thresholds for a measurement entity, proceed as follows:

Step Operation


2 Select [Set Task Threshold]. The [Set Task Threshold] dialog box is displayed.

3

In [Entity Threshold List], select a measurement entity, set the lower threshold in the [Lower Threshold] box and upper threshold in the [Upper Threshold] box, and then click <Set Threshold>. The threshold information of measurement entity is added to [List of Thresholds which have been set].


5 Click <OK>.

VIII. Deleting Threshold of Measurement Entity

To delete the threshold of a measurement entity, proceed as follows:

Step Operation


2 Select [Delete Task Threshold]. The [Delete Task Threshold] dialog box is displayed.

3 In [List of Thresholds which have been set], select the threshold to be deleted, and then click <Delete Threshold>.

4 Click <OK>. The system prompts "Do you want to delete?"


6 Click <OK>.

IX. Adding Measurement Object Instance

To add a measurement object instance, proceed as follows:



2-22

Step Operation


2 Select [Add Measurement Object Instance]. The [Add Measurement Object Instance] dialog box is displayed.

3 Add a measurement object instance to [List of Object Instances which have been set].


5 Click <OK>.

X. Deleting Measurement Object Instance

To delete a measurement object instance, proceed as follows:

Step Operation


2 Select [Delete Measurement Object Instance]. The [Delete Measurement Object Instance] dialog box is displayed.

3 In [List of Object Instances which have been set], select the measurement object instance to be modified, and then click <Delete Object Instance>. The system prompts "Do you want to delete?"


5 Click <OK>.

2.3.3 Deactivating Measurement Task

When a measurement task is running, you can deactivate the task to stop outputting measurement results temporarily without losing task information. To deactivate the task, proceed as follows:

Step Operation

1 In the navigation tree "Task list (All)", right-click the task to be deactivated. A shortcut menu is displayed.

2 Select [Deactivate Task]. The system prompts "Operation succeeded".



2-23

Step Operation

3 Click <OK>. The status of measurement task changes to "Inactive".

2.3.4 Activating Measurement Task

After deactivating the measurement task, you must activate it again before it outputs measurement results.

Step Operation

1 In the navigation tree "Task list (All)", right-click the task to be activated. A shortcut menu is displayed.

2 Select [Activate Task]. The system prompts "Operation succeeded".

3 Click <OK>. The status of measurement task changes to "Running".

2.3.5 Querying Measurement Task

This operation helps you query different types of measurement tasks based on different conditions.

To query the measurement task, proceed as follows:

1) In the navigation tree "Task list (All)", right-click the task to be queried.

The [Query the task] dialog box is displayed, as shown in Figure 2-14.



2-24

Figure 2-14 Querying measurement task

2) Select the tasks to be queried, and then click <OK>.

Only measurement tasks complying with the conditions are displayed in the "Task list (All)" navigation tree.

2.3.6 Checking Detailed Information of Measurement Task

To check the detailed information of a measurement task, proceed as follows:

1) In the navigation tree "Task list (All)", right-click the task to be checked.

A shortcut menu is displayed.

2) Select [Detailed Task Info].

The [Task information] window is displayed, as shown in Figure 2-15.



2-25

Figure 2-15 Detailed information of measurement task

Operation Result

Click the [Basic Information] tab.

Basic information of the measurement task is displayed, including the task ID and task name.

Click the [Entity Information] tab.

Entity information of the measurement task is displayed, including the type and name of entity.

Click the [Object Information] tab.

Object information of the measurement task is displayed, including the name and instance of object.

2.3.7 Deleting Measurement Task

After the measurement task is completed, you can only delete it manually.

The HLR9820 performance measurement system supports at most 128 measurement tasks at the same time.

To avoid that the number of measurement tasks exceeds 128, you must delete needless tasks periodically.



2-26

Caution:

Be careful when deleting a measurement task. Once the task is deleted, all the information and results will be lost, no matter whether the task is completed.

To delete a measurement task, proceed as follows:

Step Operation

1 In the navigation tree "Task list (All)", right-click the task to be deleted. A shortcut menu is displayed.

2 Select [Delete Task]. The system prompts "Do you want to delete?"


4 Click <OK>. The deleted task disappears from the navigation tree "Task list (All)".

2.4 Measurement Result Management This section details the management of measurement results, including:

Querying Measurement Result Dumping Measurement Result

2.4.1 Querying Measurement Result

To query the measurement result of a measurement task, proceed as follows:

1) In the navigation tree "Task List (All)", right-click the task to be queried.


2) Select [Query Task Result].

The [Query Task Result] dialog box is displayed, as shown in Figure 2-16.



2-27

Figure 2-16 Querying measurement result

3) Set query conditions as below: In [Entity Style], select the entity style output in the result.

Option Result

Original Displays the original entities only.

Evolve Displays all the original entities, including those non-redefined and redefined.

Brief Displays all the original and custom entities except those used in the calculation formulas of custom entities.

Detailed Displays all the entities.

In [Report Type], select the type of report.

Option Result

Normal Displays the measurement result of each measurement period in the output report.

Sum by Period

Displays the measurement value of each measurement period in the output report. The value is the sum of measurement values of all entities in different measurement objects.

Sum by Object

Displays the measurement value of each entity in the output report. The value is the sum of measurement values of the entity in all measurement periods.



2-28

Option Result

Sum by Period and Object

Displays the sum of measurement values of different entities in all measurement periods.

In [Time Type], select the type of time.

Option Result

- Queries the output results of the measurement periods before the current time only.

Continuous Queries the results output from the start time of start date to the end time of end date.

Segment Queries the results output from the start time to end time every day from the start date to end date.

When setting "Time Type" to "Continuous" or "Segment", you need to specify the start date/time and end date/time in [Time].

4) Click <Query>.

The [MAP Performance Measurement] window is displayed, as shown in Figure 2-17.

Figure 2-17 Performance measurement result

Operation Result

Click the [Result List] tab. The [Result List] window is displayed.

Click the [Detailed Information] tab.

The [Detailed Information] window is displayed.

Click the [Graphics Display] tab. The [Graphics Display] window is displayed.



2-29

The following details the three windows respectively:

[Result List] window

Figure 2-17 shows the [Result List] window of performance measurement results.

This window displays all measurement results in the table. Every line of the table is a group of measurement results.

The line title can be measurement time (results are sorted by time) or measurement object (results are sorted by object). The row title is measurement entity name.

Through clicking the measurement entity name, you can sort measurement results of the entity according to ascending or descending order.

Right-click the [Result list] window.

A shortcut menu is displayed, as shown in Figure 2-18.

Figure 2-18 Shortcut menu

Operation Result

Select [Refresh Task Result].

The latest measurement results are displayed in the [Result List] window.

Select [Print]. The measurement results are printed.

Select [Print Preview]. The print page can be previewed.

Select [Save As...]. The measurement results are saved as an Excel file on the current workstation.

Select [Sort by Time]. The measurement results are sorted by time.

Select [Sort by Object]. The measurement results are sorted by object.

[Detailed Information] window

Figure 2-19 shows the [Detailed Information] window of performance measurement results.



2-30

Figure 2-19 Detailed information of performance measurement results

This window displays output results of measurement tasks within a certain measurement period in the table. The output results involve:

– Entity name

– Entity value

– Entity unit

You can query output results of different measurement periods according to the following table:

Operation Result

Click . The results output in the first measurement period are displayed.

Click .

The results output before the current measurement period are displayed. If the results output in the first measurement period are displayed, the system prompts "It is the first item!" The operation failed.

Click .

The results output after the current measurement period are displayed. If the results output in the last measurement period are displayed, the system prompts "It is the last item!" The operation failed.

Click . The results output in the last measurement period are displayed.

[Graphics Display] window

Figure 2-20 shows the [Graphics Display] window of performance measurement results.



2-31

Figure 2-20 Graphics display of performance measurement results

This window visualizes all measurement results by graphics. The following table describes operations and results.

Operation Result

Select "Specific Object". The graphics is displayed by measurement object.

Select "Specific Time". The graphics is displayed by measurement time.

Click . The results of the previous measurement object or specified time are displayed.

Click . The results of the next measurement object or specified time are displayed.

Select options in the list at the right of .

The graphics display of specified measurement results involves:

Histogram chart Folded line chart Pie chart

Click the blank place behind the graphic bar of measurement entity.

The icon is displayed.

Click . The [Color] dialog box is displayed. You can specify the graphic color of entity value.

2.4.2 Dumping Measurement Result

You can dump measurement reports to the BAM database for analysis.



2-32

To dump measurement results, proceed as follows:

1) In the navigation tree "Task List (All)", right-click the measurement task to be dumped.


2) Select [Dump Task Result].

The [Dump Task Result] dialog box is displayed, as shown in Figure 2-21.

Figure 2-21 Dumping measurement results

3) Set conditions of dumping measurement results. In the [Time Type] list, select the type of time.

Option Result

ALL All measurement results are saved.

CON The results output from the start time of start date to the end time of end date are saved.

SEG The results output from the start time to end time every day from the start date to the end date are saved.

When setting "Time Type" to "CON" or "SEG", under [Settings], you need to specify:

– Start date

– Start time



2-33

– End date

– End time

4) Click <OK>.


5) Click <OK>.

The measurement results are saved to the BAM database.

2.5 Template Management When creating a great deal of measurement tasks, you can create a template to reduce repetitive work because certain parameters of tasks are always the same.

Four types of templates are available:

Entity template

Define the measurement type, measurement unit, measurement entity, and threshold.

Object template

Define the measurement type, measurement unit, measurement object, and object instance.

Time template

Define time parameters.

Task template

Combine the above templates.

2.5.1 Creating Templates

You must create templates before using them. The following introduces how to create an entity template, object template, time template, and task template separately.

I. Creating Entity Template

To create an entity template, proceed as follows:

1) In navigation tree, click the [Template] tab.

The "Template list" is displayed.

2) In the extended navigation tree "Template list", right-click "Entity Template".


3) Select [Create Entity Template].

The [Create Entity Template] dialog box is displayed, as shown in Figure 2-22.



2-34

Figure 2-22 Creating entity template

4) Configure the basic information of the entity template. In [Name], type a name for the entity template. In [Description], type a brief description of the entity template. In [Traffic task type], select a type for the new performance measurement

task. In [Measurement unit], select a measurement unit based on the task type

selected. 5) Select measurement entities.

Note:

If custom entities are created, they will be displayed in [Available custom entities]. Selecting custom entities is similar to selecting original entities.



2-35

Operation Result

In [Available static entities], select a measurement entity, and then click .

The measurement entity selected is added to [Selected static entities].

Click . All measurement entities in [Available static entities] are added to [Selected static entities].

In [Selected static entities], select a measurement entity, and then click .



6) Click the [Threshold] tab.

The [Threshold] dialog box is displayed, as shown in Figure 2-23.

Note:

You can set thresholds for the measurement entities with threshold property only. You can set thresholds for four measurement entities at most. You can set the upper or lower threshold, or both. The upper threshold must be

greater than the lower one.



2-36

Figure 2-23 Configuring threshold information

Operation Result

In [Entity Threshold List], select a measurement entity, and then set the lower threshold in the [Lower Threshold] box and upper threshold in the [Upper Threshold] box. Then click <Set Threshold>.

The thresholds of measurement entity are set. Meanwhile, the threshold information is added to [List of Thresholds which have been set].

In [List of Thresholds which have been set], select the thresholds to be deleted, and then click <Delete Threshold>.

The selected thresholds are deleted. Meanwhile, the records of selected thresholds disappear from [List of Thresholds which have been set].

7) Click <OK>.


8) Click <OK>.



2-37

The entity template is displayed under the "Entity Template" navigation tree in the [Template] tab.

II. Creating Object Template

To create an object template, proceed as follows:



2) In the extended "Template list" navigation tree, right-click "Object Template".


3) Select [Create Object Template].

The [Create Object Template] dialog box is displayed, as shown in Figure 2-24.

Figure 2-24 Creating object template

4) Configure the basic information of the object template. In [Name], type a name for the object template. In [Description], type a brief description of the object template.



2-38

In [Traffic task type], select a type for the new performance measurement task.

In [Measurement unit], select a measurement unit based on the task type selected.

5) Configure the object information.

The [Object] dialog box varies with measurement tasks, as shown in Figure 2-25 and Figure 2-26.


Operation Result

Click <Select Object Data>. The [Select Object Data] dialog box is displayed.

In [Select Object Data], select an object instance from the check box, and then click <OK>.

The object instance selected is added to [List of Object Instances which have been set].



2-39


Operation Result

In [Network identifier] and [Code of], configure proper parameters.

The button <Add Object Instance> becomes available.

Click <Add Object Instance>. The object instance is added to [List of Object Instances which have been set].

6) Click <OK>.


7) Click <OK>.

The object template is displayed under the "Object Template" navigation tree in the [Template] tab of the pane.

III. Creating Time Template

To create a time template, proceed as follows:



2) In the extended "Template list" navigation tree, right-click "Time Template".


3) Select [Create Time Template].



2-40

The [Create Time Template] dialog box is displayed, as shown in Figure 2-27.

Figure 2-27 Creating time template

4) Configure the basic information of the time template. In [Name], type a name for the time template. In [Description], type a brief description of the time template.

5) Set the time information of measurement task as below: In [Start Date], set the date to start the measurement.

The default is the current date.

In [Statistics Duration], set how long the measurement lasts.

The value ranges from 1 day to 1,024 days

This item can be configured only after the "Start Date" is selected.

If this item is not selected, the performance measurement task continues permanently.

In [Measure Period], set how often to output the measurement result. In [Measure Date(s)], set the date(s) to measure.



2-41

Option Result

Measure every day Measure every day


You can select several days. Then the system measures only in selected days every week.


You can select several dates. Then the system measures only in selected dates every month.

In [Measure Time Segment], tune the slider to set time segments of measurement task.

Indicator of slider Result

Top Only the first time segment can be set.

Middle Both the first and second time segments can be set.

Bottom Three time segments can be set.

Start Time x (x = 1, 2, and 3) indicates the start time of time segment x, and End Time x indicates the end time of time segment x. Both the start time and end time range from 00:00 to 23:59. The end time must be greater than the start time.

The second time segment cannot overlay the first one. The third time segment cannot overlay the first and second time segments.

6) Click <OK>.


7) Click <OK>.

The object template is displayed in the "Entity Template" navigation tree.

IV. Creating Task Template

To create a task template, proceed as follows:



2) In the extended "Template list" navigation tree, right-click "Entity Template".


3) Select [Create Task Template].

The [Create Task Template] dialog box is displayed, as shown in Figure 2-28.



2-42

Figure 2-28 Creating task template

4) Configure the basic information of task template. In [Name], type a name for the task template. In [Description], type a brief description of the task template. In [Traffic task type], select a type for the new performance measurement

task. In [Measurement unit], select a measurement unit based on the task type

selected. 5) Configure parameters in the [Entity] tab, [Object] tab, [Time] tab, and [Threshold].

For details, see section 2.3.1 Creating Measurement Task.

6) Click <OK>.


7) Click <OK>.



2-43

The object template is displayed under the "Entity Template" navigation tree.

2.5.2 Modifying Template

After creating templates, you can modify the configuration information according to the actual requirements.

Step Operation

1 In the navigation tree "Template list", right-click the template to be modified. A shortcut menu is displayed.

2 Select [Modify Template]. The [Modify Template] dialog box is displayed.

3 Modify the configuration information in the template.


5 Click <OK>.

2.5.3 Deleting Template

You can delete the created template if necessary.

Step Operation

1 In the navigation tree "Template list", right-click the template to be deleted. A shortcut menu is displayed.

2 Select [Delete Template]. The system prompts "Do you want to delete?"

3 Click <OK>. The deleted template disappears from the navigation tree "Template list".

2.6 Custom Entity Management The HLR9820 provides the basic measurement entities, that is, the original entities. To meet your own specific requirements, you can define some entities based on those original ones using arithmetic expressions.

2.6.1 Creating Custom Entity

When original entities cannot satisfy actual performance measurement requirements, you can create a custom entity.

To create a custom entity, proceed as follows:



2-44

1) In navigation tree, click the [Entity] tab.

The "Entity list" is displayed.

2) Right-click in the "Entity list" pane.


3) Select [Set Custom Entity].

The [Set Custom Entity] dialog box is displayed, as shown in Figure 2-29.

Figure 2-29 Creating custom entity

4) In the [Measure Unit] list, select the measurement unit to which the custom entity belongs.

5) Select the type of the custom entity. In [New entity], click "Define" to activate the [Define] area. In [Redefined original entity], click "Redefine" to activate the [Redefine] area.

6) Based on the type of custom entity, configure parameters under [Define] or [Redefine].

Under [Define], you can define a new entity by defining the entity name and calculation formula newly.

– In [Entity Alias], type the alias of the custom entity.

The length ranges from 1 to 9 characters, beginning with letters only.



2-45

– In [Entity Name], type the name of the custom entity.

The length ranges from 1 to 20 characters.

– In [Entity Unit], select the unit of custom entity, including Times, Second, MilliSecond, %, Byte, and No Unit.

– In [Entity Type], select the type of measurement value, including Integer, Float, Time, and BCD Code.

Under [Redefine], you can redefine an original entity.

You can adopt the name of the original entity, but redefine a new calculation formula to overlap the measurement result of the original entity.

In the [Entity] list, select the original entities to be redefined.

7) Under [Calculation], determine the calculation formula of custom entity.

That is, assemble the original entities selected from the [Entity] list to a calculation formula according to the arithmetic expressions.

8) Click <OK>.


9) Click <OK>.

The custom entity is displayed in the "Entity list" of navigation tree.

2.6.2 Modifying Custom Entity

After creating the custom entity, you can modify its configuration information according to the actual requirements.

To modify a custom entity, proceed as follows:

Step Operation

1 In the "Entity list" navigation tree, right-click the custom entity to be modified. A shortcut menu is displayed.

2 Select [Modify Custom Entity]. The [Modify Custom Entity] dialog box is displayed.

3 Under the [Define] or [Redefine] area, modify the configuration information.

4 Under [Calculation], modify the calculation formula of custom entity.


6 Click <OK>.



2-46

2.6.3 Deleting Custom Entity

You can delete a created custom entity if necessary.

Note:

Do not delete the running custom entity. Otherwise, the measurement values of this entity will not be displayed in the measurement result.

To delete a custom entity, proceed as follows:

Step Operation

1 In the navigation tree "Entity list", right-click the custom entity to be deleted. A shortcut menu is displayed.

2 Select [Delete Custom Entity]. The system prompts "Do you want to delete?".


4 Click <OK>. The deleted custom entity disappears from the "Entity list" navigation tree.

2.7 Example Suppose the measurement type in this example is "HDU Traffic Task", and the measurement unit is "MAP Performance Measurement".

Check the MAP standard operations, such as location update and supplementary service operations.

2.7.1 Configuration Information

Table 2-1 lists the configuration information of MAP performance measurement tasks.

Table 2-1 Configuration information of the MAP performance measurement task

Parameter Configuration information

Task name MAP Performance Measurement

Task description MAP Performance Measurement

Traffic task type HDU Traffic Task

Measurement unit MAP Performance Measurement



2-47


Entity

Operation_Req Operation_Positiversp Operation_Abort Operation_Timeout Unauthorized_Requesting_Network Unknown_Subscriber Unidentified_Subscriber Roaming_Not_Allowed Illegal_Subscriber Ss_Error_Status Ss_Not_Available System_Failure

Custom entity

Measurement unit: MAP Performance Measurement Entity Alias: OPRR Entity Name: Operation_Rsp_Rate Entity Unit: % Entity Type: Float Calculation: Operation_Positiversp/Operation_Req

Object

UPDL PRMN INSD ATHF SRIF

Time Measure period: 1 hour Others: Default

Threshold

Other

Sampling Parameter: None Output Device: Current Workstation, Traffic Performance Port, and Network Manager Port Output Arrangement: PerPeriod Output

2.7.2 Operation Flowchart

Figure 2-30 shows the operation flowchart.



2-48

Create a custom entity

Create a measurement task

Query the measurement result

End

Start

Delete the measurement task

Create a task template

Figure 2-30 Operation procedure

2.7.3 Operation Procedure

The operation procedure is described as follows:

I. Creating Custom Entity

To create a custom entity, proceed as follows:

1) In the navigation tree, click the [Entity] tab.

The "Entity list" is displayed.

2) Right-click in the "Entity list" navigation tree.


3) Select [Set Custom Entity].

The [Set Custom Entity] dialog box is displayed, as shown in Figure 2-31.



2-49

Figure 2-31 Creating custom entity

4) In the [Measure Unit] list, select "MAP Performance Measurement". 5) Click "Define" to activate the [Define] area.

In [Entity Alias], type "OPRR". In [Entity Name], type "Operation_Rsp_Rate". In [Entity Unit], select "%". In [Entity Type], select "Float".

6) Determine the calculation formula to "Operation_Positiversp/Operation_Req".

Step Operation

1 Under [Calculation], select "Operation_Positiversp" in the [Entity] list.

2 Click .

3 Under [Calculation], select "Operation_Req" in the [Entity] list.

Figure 2-32 shows the custom entity configured.



2-50

Figure 2-32 Configuration information of custom entity

7) Click <OK>.


8) Click <OK>.

The custom entity is displayed in the "Entity list" of the navigation tree.

II. Creating Task Template

To create a task template, proceed as follows:

1) In the navigation tree, click the [Template] tab.


2) In the extended "Template list" navigation tree, right-click "Task Template".


3) Select [Create Task Template].

The [Create Task Template] dialog box is displayed, as shown in Figure 2-33.



2-51

Figure 2-33 Creating task template

4) Configure the basic information of task template. In [Name], type "MAP Performance Measurement Template". In [Description], type "MAP Performance Measurement Template". In [Traffic task type], select "HDU Traffic Task". In [Measurement unit], select "MAP Performance Measurement".

5) Click the [Entity] tab.

The [Entity] dialog box for configuring entity is displayed.

6) Select measurement entities.



2-52


Selected static entities


Selected custom entities Operation_Rsp_Rate

7) Click the [Object] tab.

The [Object] dialog box is displayed.

8) Click <Select Object Data>.

The [Select Object Data] dialog box is displayed.

9) In the [Select Object Data] dialog box, select "UPDL", "PRMN", "INSD", "ATHF", and "SRIF", and then click <OK>.

The selected object instances are added to [List of Object Instances which have been set].

10) Click the [Time] tab.

The [Time] dialog box is displayed.

11) Select "1 hour" in the [Measure Period] list, and keep default values for others.

Note:

Because the measurement entity of this task template has no threshold property, setting thresholds is unnecessary.

Figure 2-34 shows the task template configured.



2-53

Figure 2-34 Configuration information of task template

12) Click <OK>.


13) Click <OK>.

The object template is displayed in the "Task Template" navigation tree of the pane.

III. Creating Measurement Task

To create a measurement task, proceed as follows:

1) Select [Task/Create Task].

The [Create a New Task] dialog box is displayed, as shown in Figure 2-35.



2-54

Figure 2-35 Creating measurement task

2) Configure the basic information of new task as follows: In [Task name], type "MAP Performance Measurement". In [Task description], type "MAP Performance Measurement". In [Traffic task type], select "HDU Traffic Task". In [Measurement unit], select "MAP Performance Measurement".

3) In the [Task template] list, select "MAP Performance Measurement Template", as shown in Figure 2-36.



2-55

Figure 2-36 Selecting task template

4) Click the [Other] tab.

The [Other] dialog box is displayed.

5) Set the sampling parameter, output device, and output arrangement as below:

Sampling Parameter None

Current Workstation

Traffic Performance Port Output Device

Network Manager Port

Output Arrangement Output the report every measurement period

Figure 2-37 shows the measurement task configured.



2-56

Figure 2-37 Configuration information of measurement task

6) Click <OK>.


7) Click <OK>.

The measurement task appears in the "Task list (All)" navigation tree.

IV. Querying Measurement Result

After the measurement task runs at least one measurement period, the measurement result is output. You can query it at this time.

To query the result of measurement task, proceed as follows:

1) In the "Task List (All)" navigation tree, right-click the "MAP Performance Measurement".




2-57

2) Select [Query Task Result].

The [Query Task Result] dialog box is displayed, as shown in Figure 2-38.

Figure 2-38 Querying measurement result

3) Set query conditions as below: In [Entity Style], select "Detailed". In [Report Type], select "Normal". In [Time Type], select "Continuous". In [Time], specify the start date/time and end date/time to query the result

based on the actual requirements. 4) Click <Query>.

The [MAP Performance Measurement] window is displayed, as shown in Figure 2-39.



2-58

Figure 2-39 Performance measurement result

Different tabs list different information, as described below:

Operation Result

Click the [Result List] tab. The performance measurement results are listed.

Click the [Detailed Information] tab.

The detailed information of performance measurement results is listed.

Click the [Graphics Display] tab.

The graphics display of performance measurement result is listed.

V. Deleting Measurement Task

When the measurement task is completed and unnecessary, you can delete this measurement task.

To delete the measurement task, proceed as follows:

1) In the "Task List (All)" navigation tree, right-click the "MAP Performance Measurement".


2) Select [Delete Task].

The system prompts "Do you want to delete?"

3) Click <OK>.


4) Click <OK>.



2-59

This measurement task disappears from the "Task list (All)" navigation tree.

Performance Measurement Manual HUAWEI HLR9820 Home Location Register Chapter 3 Analysis of Performance Measurement Results


3-1

Chapter 3 Analysis of Performance Measurement Results

This chapter introduces how to analyze:

Performance measurement results Common performance measurement tasks

3.1 Analysis Methods You can analyze performance measurement data using the following methods:

Analyzing a certain measurement entity separately

You can decide whether the value of the measurement entity is within the reasonable range using this method. An excessive high or low value indicates an exception.

Take the CPU utilization measurement for example: You can determine whether to add CPUs by analyzing whether the CPU is overload.

Comparing data of a certain measurement entity in different time

You can determine whether there is a burst, which is related to the exception of system handling.

Take the MAP performance measurement for example: If the times of successful authentication reduce dramatically within a certain time segment, an exception may occur to the authentication function of the system. You must handle it immediately.

Comparing data of different measurement entities in the same measurement unit

You can determine whether relations of different measurement entities are normal using this method.

Take the MAP performance measurement for example: If the proportions of response times and request times of the MAP operation are within the specified range, you can determine that the relation between the MAP operation request and MAP operation response is normal.

Comparing the same measurement entities between the same type of measurement objects

You can determine whether the load sharing mode between the same types of measurement objects is rational using this method.



3-2

Take the MTP signaling link measurement for example: You can determine whether the load sharing of a signaling link is rational by comparing the loads of other links to the same destination signaling point (DSP).

Comparing data of multiple measurement units in the same time segment

You can determine the fault related to cooperation between different parts using this method.

Take the MTP signaling link measurement for example: You can determine whether the load sharing of a signaling transfer point (STP) is rational by comparing loads of links to different STPs.

Analyzing measurement results in a long time

Long-time analysis means analyzing the performance measurement results collected in a long term. You can use the method to:

– Determine the working status of a network in a month, in a quarter, or even in a year.

– Provide references for network optimization.

– Find out potential problems.

Take the MAP performance measurement for example: By analyzing variations of MAP operations and subscriber numbers in busy hour for a long time, you can determine the variation of the traffic model of local subscribers. If a burst occurs, you must analyze the cause to determine whether the system is faulty.

3.2 Analysis of Common Performance Measurement Tasks During HLR9820 deployment and routine operation, you need to create performance measurement tasks to test the system performance and running status. The following introduces the common measurement tasks and analyzes important performance measurement results.

Note:

The configuration information of each measurement task below is for reference only. You can adjust its configuration based on the onsite conditions and customer's requirements.

3.2.1 CPU Utilization Measurement

This task is to measure the utilization and congestion of CPUs in the modules such as WCSU, WCCU, and WBSG.



3-3

I. Configuration Information

Table 3-1 lists the configuration information of the CPU utilization measurement task.

Table 3-1 Configuration information of the CPU utilization measurement task


Traffic task type Global Component

Measurement unit CPU Seizure Ratio Traffic

Entity

Average Seizure Ratio Congestion Times Congestion Duration Overload Times Overload Duration Peak Seizure Ratio Peak Seizure Time Peak Seizure Duration

Object All objects

Time Measure Period: 1 hour Others: Default

Threshold Upper Threshold of Average Seizure Ratio: "80%"

Other Set as required.

Note:

"Average Seizure Ratio" refers to the average utilization of the CPU. Average Seizure Ratio < 80%

"Peak Seizure Ratio" refers to the peak value of CPU utilization. Peak Seizure Ratio < 95%.

II. Analyzing Performance Measurement Data

If the "Average Seizure Ratio" or "Peak Seizure Ratio" of the CPU exceeds the threshold, the CPU of the module measured is overloaded.

The CPU overload may be caused by:

Insufficient system capacity Equipment fault High traffic in a certain time segment



3-4

3.2.2 MAP Performance Measurement

This task is to measure whether the MAP standard operations such as location update and supplementary service operations are normal.


Table 3-2 lists the configuration information of the MAP performance measurement task.

Table 3-2 Configuration information of the MAP performance measurement task



Measurement unit MAP Performance Measurement

Entity


Custom entity

Measurement unit: MAP Performance Measurement Entity Unit: % Entity Type: Float Calculation: Operation_Positiversp/Operation_Req

Object

UPDL ATHF INSD SRIF PRMN

Time Set Measure Period: 1 hour Others: Default

Threshold None




3-5

Note:

Operation_Positiversp/Operation_Req > 99% "Operation_Positiversp/Operation_Req" is the calculation formula of the custom entity. It indicates the ratio between the positive responses of MAP operations and the total MAP operation requests, that is, the success rate of MAP operations. It is used to evaluate the signaling handling stability of the HLR 9820 system.


Once a MAP operation fails, the operation originator must send another MAP operation request. For example, if the location update request fails, the subscriber must send another location update request. If the measurement value exceeds the thresholds, it has no great impact on the system. However you must find out the cause by analyzing measurement values of other measurement entities.

3.2.3 CPU Performance Measurement

This task is to measure the HDU handling capability and CPU utilization.


Table 3-3 lists the configuration information of the CPU performance measurement task.

Table 3-3 Configuration information of the CPU performance measurement task



Measurement unit CPU Performance Measurement

Entity

Occupationratio Useratio Iowaitratio Idleratio Cpupeak

Object HDU_1 HDU_2


Threshold None




3-6

Note:

"Occupationratio" refers to the ratio of the operating system occupying the CPU in the measurement period. Occupationratio < 80%

"Cpupeak" refers to the ratio of CPU peak time in the measurement period. Cpupeak < 95%


If the measurement value of "Occupationratio" or "Cpupeak" exceeds the threshold, the CPU of the HDU is overloaded.

The CPU overload may be caused by:

Insufficient system capacity Equipment fault

3.2.4 MTP Signaling Link Measurement

This task is to observe the working status of MTP link.

I. Configuration information

Table 3-4 lists the configuration information of MTP signaling link measurement task.

Table 3-4 Configuration information of the MTP signaling link measurement task


Traffic task type Signaling and Interface

Measurement unit MTP Signaling Link Traffic

Entity

Fault Times Fault Duration Unavail Duration Snd Seizure Ratio Rcv Seizure Ratio Congestion Times Congestion Duration

Custom entity

Measurement unit: MTP signaling Link Traffic Entity Unit: % Entity Type: Float Calculation: Snd Seizure Ratio + Rcv Seizure Ratio

Object Data of all objects



3-7



Threshold None


Note:

"Snd Seizure Ratio" indicates the seizure ratio of the MTP signaling link in transmitting signaling messages. "Rcv Seizure Ratio" indicates the seizure ratio of the MTP signaling link in receiving signaling messages. The two measurement items apply to observe the load of the MTP signaling link. Normally, both "Snd Seizure Ratio" and "Rcv Seizure Ratio" shall be less than 40%.


Normally, the maximum unidirectional load of the MTP signaling link should be less than 40%. That is, the seizure ratio of transmitting or receiving should be less than 40%. If the measurement value of "Snd Seizure Ratio" or "Rcv Seizure Ratio" exceeds the threshold, it indicates that the MTP signaling link is overloaded.

The overload of the MTP signaling link may be caused by:

High signaling traffic Increased subscriber number Insufficient link number

3.2.5 SCCP Availability Measurement

This task is to observe the running status of the local SCCP.


Table 3-5 lists the configuration information of the SCCP availability measurement task.

Table 3-5 Configuration information of the SCCP availability measurement task



Measurement unit SCCP Availability Statistic



3-8


Entity

Local SCCP Unavailability: Node Failure Local SCCP Unavailability: Maintenance Made Busy Local SCCP Unavailability: Congestion Local SCCP Unavailability Duration: All Reasons Local SCCP Availability: All Reasons

Custom entity

Measurement unit: SCCP Availability Statistic Entity Unit: % Entity Type: Float Calculation: Local SCCP Unavailability Duration: All Reasons/3600

Object All objects

Time Measure Period: "1 hour" Other: default

Threshold None


Note:

Local SCCP Unavailability Duration: All Reasons/3600 < 0.01%. "Local SCCP Unavailability Duration: All Reasons/3600" refers to the calculation formula of the custom entity. It indicates the ratio between the unavailable duration of the local SCCP and the measurement period due to all reasons such as system faults, congestion, or maintenance operations. The unit is second. In this measurement task, the "Measure Period" is 1 hour, that is, 3600 seconds.


If the measurement value of "Local SCCP Unavailability Duration: All Reasons/3600" exceeds the threshold 0.01%, then you need to analyze the measurement values of other original entities to find out the reason.

The local SCCP unavailability may be caused by:

System fault System congestion Maintenance operation



3-9

3.2.6 SCCP Performance Measurement

This task is to observe the running status of the SCCP route.


Table 3-6 lists the configuration information of SCCP performance measurement task.

Table 3-6 Configuration information of the SCCP performance measurement task



Measurement unit SCCP Performance Statistic

Entity

RF: No Translation for an Address of Such Nature RF: No Translation for this Specific Address RF: Signaling Network Failure RF: Signaling Network Congestion RF: Subsystem Failure(Unavailable) RF: Subsystem Congestion RF: Unequipped Subsystem RF: Reason Unknown RF: Address Syntax Error

Custom entity

Measurement unit: SCCP Performance Statistic Entity Unit: % Entity Type: Float Calculation: Sum of all original entities/3600

Object All objects

Time Measure Period: 1 hour Others: default.

Threshold None


Note:

Sum of all original entities/3600 < 0.01% "Sum of all original entities/3600" refers to the calculation formula of the custom entity. It indicates the times of SCCP routing failures caused by all reasons every second. In this measurement task, the "Measure Period" is "1 hour", that is, 3600 seconds.



3-10


If the measurement value of "sum of all original entities/3600" exceeds the threshold 0.01%, the times of SCCP routing failure exceed the maximum range allowed. You need to analyze other measurement values of other original entities to find out the reason.

The SCCP routing failures may be caused by:

Invalid addressing information Incorrect translation of valid address Unavailable DSP Network congestion System fault System congestion System uninstallation Addressing information containing syntax errors

Performance Measurement Manual HUAWEI HLR9820 Home Location Register Appendix A Performance Measurement Entity


A-1

Appendix A Performance Measurement Entity

A.1 Global Component

Measurement entity Meaning and standard measurement point

Meaning: Average seizure ratio Average Seizure Ratio Measurement point: HLR internal timer expires.

Meaning: Number of congestions Congestion Times

Measurement point: HLR internal timer expires.

Meaning: Congestion duration Congestion Duration

Measurement point: HLR internal timer expires.

Meaning: Number of times that the CPU utilization exceeds specified threshold Overload Times Measurement point: HLR internal timer expires.

Meaning: Duration from the moment the CPU is overloaded to the time overload is released Overload Duration Measurement point: HLR internal timer expires.

Meaning: Transient peak CPU utilization in a measurement period Peak Seizure Ratio Measurement point: Seizure ratio reaches the peak.

Meaning: Occurrence time of transient peak CPU utilization in a measurement period

Peak Seizure Time Measurement point: Seizure ratio reaches the peak for the first time.

Meaning: Duration of transient peak CPU utilization in a measurement period Peak Seizure

Duration Measurement point: Seizure ratio reaches the peak.



A-2

A.2 HDU Traffic Task

A.2.1 CPU Performance Measurement


Meaning: Ratio of the time that the operating system occupies the CPU Occupationratio Measurement point: The operating system occupies the CPU.

Meaning: Ratio of the time that applications occupy the CPU Useratio

Measurement point: An application occupies the CPU.

Meaning: Ratio of the time that the CPU waits for I/O operation Iowaitratio

Measurement point: The CPU waits for I/O operation.

Meaning: Ratio of the time that the CPU is idle Idleratio

Measurement point: The CPU is idle.

Meaning: CPU peak time ratio Cpupeak

Measurement point: CPU peak occurs.

A.2.2 MAP Performance Measurement


Meaning: Operation request

Operation_Req Measurement point: MAP standard operation requests are counted when the MAP operation request is received or sent.

Meaning: Normal response to operation Operation_Positiversp Measurement point: No error is contained in the MAP

operation response received or sent.

Meaning: The operation is aborted (not due to timeout) Operation_Abort Measurement point: Abort, Close, or Notice message,

which is not caused by timeout, is received or sent.

Meaning: Operation timeout Operation_Timeout

Measurement point: Local operation times out.

Meaning: Operation duration

Operation_Interval Measurement point: The operation request is received or sent (till the operation is terminated normally or abnormally).



A-3


Meaning: The requested network is unauthorized. Unauthorized_ Requesting_Network Measurement point: Error is contained in the MAP


Meaning: Subscriber ID does not exist in HLR database.Unknown_Subscriber Measurement point: Error is contained in the MAP


Meaning: Subscriber ID does not exist in VLR database.Unedentified_Subscriber Measurement point: Error is contained in the MAP


Meaning: The short message center (SMC) delivers messages to a subscriber, but the MS is switched off.

Absent_Subscribersm Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Roaming is forbidden by the HLR. Roaming_Not_Allowed Measurement point: Error is contained in the MAP


Meaning: Authentication fails during service request or location update.

Illegal_Subscriber Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the HLR when the requested bearer service is not provided. Bearer_Service_Not_

Provisioned Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the HLR when the requested teleservice is not provided. Teleservice_Not_

Provisioned Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the VLR when the terminal equipment proves to be illegal in an MTC.

Illegal_Equipment Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the HLR when the subscriber who has barring of incoming calls (BAIC) service active is called. Call_Barred Measurement point: Error is contained in the MAP operation response received or sent.



A-4


Meaning: Message returned by the HLR when the call-forwarding times exceed the specified limit during the SendRoutingInfo procedure. Forwarding_Violation Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: CUG check fails in SendRoutingInfo procedure.

Cug_Reject Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the HLR when the requested supplementary service (SS) is mutually exclusive with basic service (BS). Illegal_Ss_Operation Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the HLR when the current status of a supplementary service fails to meet that required for supplementary service operation. Ss_Error_Status Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the HLR when the supplementary service required for the SS operation is not provided. Ss_Not_Available Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the HLR when the subscriber is not authorized for the SS operation. Ss_Subscription_

Violation Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the HLR when an SS operation conflicts with other SS status.

Ss_Incompatibility Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: The function requested by the subscriber is not supported.

Facility_Not_Supported Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the VLR when the MS is switched off; or message returned by the HLR when the VLR originates Erase Subscriber to clear related subscriber data. Absent_Subscriber

Measurement point: Error is contained in the MAP operation response received or sent.



A-5


Meaning: Message returned by the HLR when SM queue list is too full to store new SMC address. Message_Waiting_

List_Full Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned when the system fails. System_Failure Measurement point: Error is contained in the MAP


Meaning: Mandatory parameters are missing in the received signaling during protocol check.

Data_Missing Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Data of received signaling is out of specified scope during protocol check. Unexpected_Data_

Value Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the HLR when registering the call barring service fails due to wrong password. Pw_Registration_FailureMeasurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the HLR when activating/deactivating call-barring service with wrong password. Negative_Pw_Check Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Roaming number is not available in the VLR when the HLR requests for the roaming number. No_Roaming_Number_

Available Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the HLR when the number of password attempts exceeds the specified limit. Number_Of_Pw_

Attemps_Violation Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: Message returned by the HLR when the MSISDN of the subscriber is changed.

Number_Changed Measurement point: Error is contained in the MAP operation response received or sent.



A-6


Meaning: The intelligent subscriber is regarded busy. Busy_Subscriber Measurement point: Error is contained in the MAP


Meaning: The intelligent subscriber makes no response to the paging.

No_Subscriber_Reply Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: HLR does not support the AnyTimeInterrogation request from the gsmSCF.

Ati_Notallowed Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: The HLR does not support the OR interrogation from the GMSC, or the calls to the specified subscriber to be optimally routed. Or_Notallowed Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: This message is returned by the VLR or HLR when the coding scheme of USSD string is unknown.

Unknown_Alphabet Measurement point: Error is contained in the MAP operation response received or sent.

Meaning: The called subscriber is busy when the network originates USSD request.

Ussd_Busy Measurement point: Error is contained in the MAP operation response received or sent.

A.2.3 SCS Performance Measurement


Meaning: The total number of CFU subscribers TOTALCFUSUB Measurement point: Subscribers who subscribe to the CFU

service exist in the database.

Meaning: The total number of CFB subscribers TOTALCFBSUB Measurement point: Subscribers who subscribe to the CFB


Meaning: The total number of CFNRy subscribers TOTALCFNRYSUB Measurement point: Subscribers who subscribe to the

CFNRy service exist in the database.



A-7


Meaning: The total number of CFNRc subscribers TOTALCFNRCSUB Measurement point: Subscribers who subscribe to the

CFNRc service exist in the database.

Meaning: The total number of CW subscribers TOTALCWSUB Measurement point: Subscribers who subscribe to the CW


Meaning: Total number of call hold subscribers TOTALHOLDSUB Measurement point: Subscribers who subscribe to the call

hold service exist in the database.

A.2.4 SUB (Subscriber) Performance Measurement


Meaning: The total number of subscribers in the HLR TOTALSUB

Measurement point: Subscribers exist in the database.

Meaning: The total number of 3G subscribers in the HLR TOTAL3GSUB Measurement point: Subscribers whose card type is USIM exist

in the database.

Meaning: The total number of 2G subscribers in the system TOTAL2GSUB Measurement point: Subscribers whose card type is SIM exist in

the database.

A.2.5 SWB (Subscriber with BS) Performance Measurement


Meaning: The total number of 3G BS20 subscribers in the HLR

TOTAL3GBS20SUB Measurement point: Subscribers who subscribe to the BS20 service exist in the database.

Meaning: The total number of 3G BS30 subscribers in the HLR

TOTAL3GBS30SUB Measurement point: Subscribers who subscribe to the BS30 service exist in the database.



A-8

A.2.6 SWC (Subscriber with CAMEL) Performance Measurement


Meaning: The total number of OCSI subscribers in the HLRTOTALOCSISUB Measurement point: Subscribers who subscribe to the

OCSI service exist in the database.

Meaning: The total number of TCSI subscribers in the HLRTOTALTCSISUB Measurement point: Subscribers who subscribe to the

TCSI service exist in the database.

Meaning: The total number of SMSCSI subscribers in the HLR

TOTALSMSCSISUB Measurement point: Subscribers who subscribe to the SMSCSI service exist in the database.

Meaning: The total number of DCSI subscribers in the HLRTOTALDCSISUB Measurement point: Subscribers who subscribe to the

DCSI service exist in the database.

Meaning: The total number of VTCSI subscribers in the HLR

TOTALVTCSISUB Measurement point: Subscribers who subscribe to the VTCSI service exist in the database.

Meaning: The total number of MCSI subscribers in the HLRTOTALMCSISUB Measurement point: Subscribers who subscribe to the

MCSI service exist in the database.

Meaning: The total number of SSCSI subscribers in the HLR

TOTALUCSISUB Measurement point: Subscribers who subscribe to the SSCSI service exist in the database.

Meaning: The total number of UCSI subscribers in the HLRTOTALUCSISUB Measurement point: Subscribers who subscribe to the

UCSI service exist in the database.

Meaning: The total number of GPRSCSI subscribers in the HLR

TOTALGPRSCSISUB Measurement point: Subscribers who subscribe to the GPRSCSI service exist in the database.



A-9

A.2.7 SWCS (Subscriber with CB SS) Performance Measurement


Meaning: The total number of subscribers for all the barring services

TOTALALLBARSSSUBMeasurement point: Subscribers who subscribe to all the barring services exist in the database.

Meaning: The total number of BOC subscribers TOTALBOCSUB Measurement point: Subscribers who subscribe to the

BOC service exist in the database.

Meaning: The total number of BAOC subscribers TOTALBAOCSUB Measurement point: Subscribers who subscribe to the

BAOC service exist in the database.

Meaning: The total number of BOIC subscribers TOTALBOICSUB Measurement point: Subscribers who subscribe to the

BOIC service exist in the database.

Meaning: The total number of BOIC-exHC subscribers TOTALBOICEXHCSUB Measurement point: Subscribers who subscribe to the

BOIC-exHC service exist in the database.

Meaning: The total number of BIC subscribers TOTALBICSUB Measurement point: Subscribers who subscribe to the

BIC service exist in the database.

Meaning: The total number of BAIC subscribers TOTALBAICSUB Measurement point: Subscribers who subscribe to the

BAIC service exist in the database.

Meaning: The total number of BIC-Roam subscribers TOTALBICROAMSUB Measurement point: Subscribers who subscribe to the

BIC-Roam service exist in the database.

A.2.8 SWG (Subscriber with GPRS) Performance Measurement


Meaning: The total number of GPRS subscribers in the HLR

TOTALGPRSSUB Measurement point: Subscribers who subscribe to the GPRS service exist in the database.



A-10

A.2.9 SWL (Subscriber with LCS) Performance Measurement


Meaning: The total number of LCS subscribers in the HLR

TOTALLCSSUB Measurement point: Subscribers who subscribe to the LCS service exist in the database.

A.2.10 SWLK (Subscriber with Lock) Performance Measurement


Meaning: The total number of subscribers for MscLockIN

TOTALMSCLOCKINSUB Measurement point: Subscribers who subscribe to the incoming lock in CS domain exist in the database.

Meaning: The total number of subscribers for MscLockIN

TOTALMSCLOCKOUTSUBMeasurement point: Subscribers who subscribe to the outgoing lock in CS domain exist in the database.

Meaning: The total number of subscribers for SgsnLock

TOTALSGSNLOCKSUB Measurement point: Subscribers who subscribe to the GPRS lock in PS domain exist in the database.

Meaning: The total number of subscribers for SabLockIn

TOTALSABLOCKINSUB Measurement point: Subscribers who subscribe to the subscriber-applied incoming barring exist in database exist in the database.

Meaning: The total number of subscribers for SabLockOut

TOTALSABLOCKOUTSUB Measurement point: Subscribers who subscribe to the subscriber-applied outgoing barring exist in database exist in the database.



A-11

A.2.11 SWO (Subscriber with ODB) Performance Measurement


Meaning: The total number of subscribers for OdbIncomingCalls

TOTALODBICSUB Measurement point: Subscribers who subscribe to the ODB IC (including BAIC, BICROAM) service exist in the database.

Meaning: The total number of subscribers for OdbOutgoingCalls

TOTALODBACSUB Measurement point: Subscribers who subscribe to the ODB OC (including BAOC, BOIC, BOICEXHC, BOCROAM) service exist in the database.

Meaning: The total number of subscribers for OdbRoaming

TOTALODBROAMSUB Measurement point: Subscribers who subscribe to the ODB ROAM service exist in the database.

Meaning: The total number of subscribers for OdbSS TOTALODBSSSUB Measurement point: Subscribers who subscribe to the

ODBSS service exist in the database.

Meaning: The total number of subscribers for OdbOutgoingEntertainment

TOTALODBENTSUB Measurement point: Subscribers who subscribe to the ODB outgoing entertainment service exist in the database.

Meaning: The total number of subscribers for OdbOutgoingInformation

TOTALODBRNFSUB Measurement point: Subscribers who subscribe to the ODB outgoing information service exist in the database.

Meaning: The total number of subscribers for OdbPlmnBar1

TOTALODBPLMN1SUB Measurement point: Subscribers who subscribe to the ODB HPLMN specific data type1 service exist in the database.





A-12






A.2.12 SWOS (Subscriber with Other SS) Performance Measurement


Meaning: The total number of CUG subscribers TOTALCUGSUB Measurement point: Subscribers who subscribe to the CUG


Meaning: The total number of ECT subscribers TOTALECTSUB Measurement point: Subscribers who subscribe to the ECT


Meaning: The total number of MPTY subscribers TOTALMPTYSUB Measurement point: Subscribers who subscribe to the MPTY


Meaning: The total number of AoCI subscribers TOTALAOCISUB Measurement point: Subscribers who subscribe to the AoCI


Meaning: The total number of AoCC subscribers TOTALAOCCSUB Measurement point: Subscribers who subscribe to the AoCC


Meaning: The total number of CLIP subscribers TOTALCLIPSUB Measurement point: Subscribers who subscribe to the CLIP


Meaning: The total number of CLIR subscribers TOTALCLIRSUB Measurement point: Subscribers who subscribe to the CLIR




A-13


Meaning: The total number of COLP subscribers TOTALCOLPSUB Measurement point: Subscribers who subscribe to the COLP


Meaning: The total number of COLR subscribers TOTALCOLRSUB Measurement point: Subscribers who subscribe to the COLR


A.2.13 SWR (Subscriber When Roaming) Performance Measurement


Meaning: The total number of subscribers roaming outside the local PLMN

TOTALROAMSUB Measurement point: Subscribers who are roaming outside the local PLMN exist in the database.

Meaning: The total number of subscribers roaming outside the home PLMN country

TOTALINTERROAMSUBMeasurement point: Subscribers who are roaming outside the local PLMN country exist in the database.

Meaning: The total number of active subscribers TOTALACTIVESUB Measurement point: Subscribers who are roaming exist

in the database.

A.3 Signaling and Interface

A.3.1 M3UA Destination Entity Traffic


Meaning: Total inaccessible times of an M3UA destination entity Inaccessible

Times Measurement point: Measured by M3UA destination entity.

Meaning: Inaccessible duration of an M3UA destination entity Inaccessible Duration Measurement point: Measured by M3UA destination entity.



A-14

A.3.2 M3UA Linkset Flux Traffic


Meaning: Total messages transmitted by an M3UA link setNumber of Message Transmitted Measurement point: The measured signaling link of the

link set sends MSUs.

Meaning: Total bytes transmitted by an M3UA link set Bytes of Message Transmitted Measurement point: The measured signaling link of the

link set sends bytes.

Meaning: Total messages received by an M3UA link set Number of Message Received Measurement point: The measured signaling link of the

link set receives MSUs.

Meaning: Total bytes received by an M3UA link set Bytes of Message Received Measurement point: The measured signaling link of the

link set receives bytes.

Meaning: Total data messages transmitted by an M3UA link set Number of Data

Message Transmitted Measurement point: The measured signaling link of the link set sends data messages.

Meaning: Total bytes of the data messages transmitted by an M3UA link set Bytes of Data Message

Transmitted Measurement point: The measured signaling link of the link set sends data bytes.

Meaning: Total data messages received by an M3UA link set Number of Data

Message Received Measurement point: The measured signaling link of the link set receives data messages.

Meaning: Total bytes of the data messages received by an M3UA link set Bytes of Data Message

Received Measurement point: The measured signaling link of the link set receives data bytes.

Meaning: Total ASPM messages transmitted by an M3UA link set Number of ASPM

Message Transmitted Measurement point: The measured signaling link of the link set sends ASPM messages.

Meaning: Total bytes of the ASPM messages transmitted by an M3UA link set Bytes of ASPM

message Transmitted Measurement point: The measured signaling link of the link set sends ASPM messages.



A-15


Meaning: Total ASPM messages received by an M3UA link set Number of ASPM

Message Received Measurement point: The measured signaling link of the link set receives ASPM messages.

Meaning: Total bytes of the ASPM messages received by an M3UA link set Bytes of ASPM

Message Received Measurement point: The measured signaling link of the link set receives ASPM messages.

Meaning: Total SSNM messages transmitted by an M3UA link set Number of SSNM

Message Transmitted Measurement point: The measured signaling link of the link set sends SSNM messages.

Meaning: Total bytes of the SSNM messages transmitted by an M3UA link set Bytes of SSNM

Message Transmitted Measurement point: The measured signaling link of the link set sends SSNM messages.

Meaning: Total SSNM messages received by an M3UA link set Number of SSNM

Message Received Measurement point: The measured signaling link of the link set receives SSNM messages.

Meaning: Total bytes of the SSNM messages received by an M3UA link set Bytes of SSNM

Message Received Measurement point: The measured signaling link of the link set receives SSNM messages.

Meaning: Total MGMT messages transmitted by an M3UA link set Number of MGMT

Message Transmitted Measurement point: The measured signaling link of the link set sends MGMT messages.

Meaning: Total bytes of the MGMT messages transmitted by an M3UA link set Bytes of MGMT

Message Transmitted Measurement point: The measured signaling link of the link set sends MGMT messages.

Meaning: Total MGMT messages received by an M3UA link set Number of MGMT

Message Received Measurement point: The measured signaling link of the link set receives MGMT messages.

Meaning: Total bytes of the MGMT messages received by an M3UA link set Bytes of MGMT

Message Received Measurement point: The measured signaling link of the link set receives MGMT messages.



A-16


Meaning: Total disconnection times of the M3UA link Link Disconnection Times Measurement point: The link is disconnected.

A.3.3 M3UA Linkset State Traffic


Meaning: Total unavailable times of the M3UA link set Unavailable Times

Measurement point: The link set is unavailable.

Meaning: Unavailable duration of the M3UA link set Unavailable Duration Measurement point: The measurement starts when the link set

is unavailable and stops when the link set is available.

A.3.4 M3UA Signaling Link Traffic


Meaning: Total messages transmitted by an M3UA link Number of Message Transmitted Measurement point: The measured signaling link sends

MSUs.

Meaning: Total bytes transmitted by an M3UA link Bytes of Message Transmitted Measurement point: The measured signaling link sends

bytes.

Meaning: Total messages received by an M3UA link Number of Message Received Measurement point: The measured signaling link receives

MSUs.

Meaning: Total bytes received by an M3UA link Bytes of Message Received Measurement point: The measured signaling link receives

bytes.

Meaning: Total data messages transmitted by an M3UA link Number of Data

Message Transmitted Measurement point: The measured signaling link sends data messages.



A-17


Meaning: Total bytes of the data messages transmitted by an M3UA link Bytes of Data Message

Transmitted Measurement point: The measured signaling link sends data bytes.

Meaning: Total data messages received by an M3UA link Number of Data Message Received Measurement point: The measured signaling link receives

data messages.

Meaning: Total bytes of the data messages received by an M3UA link Bytes of Data Message

Received Measurement point: The measured signaling link receives data bytes.

Meaning: Total ASPM messages transmitted by an M3UA link Number of ASPM

Message Transmitted Measurement point: The measured signaling link sends ASPM messages.

Meaning: Total bytes of the ASPM messages transmitted by an M3UA link Bytes of ASPM

message Transmitted Measurement point: The measured signaling link of the link set sends ASPM messages.

Meaning: Total ASPM messages received by an M3UA linkNumber of ASPM Message Received Measurement point: The measured signaling link receives

ASPM messages.

Meaning: Total bytes of the ASPM messages received by an M3UA link Bytes of ASPM

Message Received Measurement point: The measured signaling link receives ASPM messages.

Meaning: Total SSNM messages transmitted by an M3UA link Number of SSNM

Message Transmitted Measurement point: The measured signaling link sends SSNM messages.

Meaning: Total bytes of the SSNM messages transmitted by an M3UA link Bytes of SSNM

Message Transmitted Measurement point: The measured signaling link sends SSNM messages.

Meaning: Total SSNM messages received by an M3UA link Number of SSNM

Message Received Measurement point: The measured signaling link receives SSNM messages.



A-18


Meaning: Total bytes of the SSNM messages received by an M3UA link Bytes of SSNM

Message Received Measurement point: The measured signaling link receives SSNM messages.

Meaning: Total MGMT messages transmitted by an M3UA link Number of MGMT

Message Transmitted Measurement point: The measured signaling link sends MGMT messages.

Meaning: Total bytes of the MGMT messages transmitted by an M3UA link Bytes of MGMT

Message Transmitted Measurement point: The measured signaling link sends MGMT messages.

Meaning: Total MGMT messages received by an M3UA link Number of MGMT

Message Received Measurement point: The measured signaling link receives MGMT messages.

Meaning: Total bytes of the MGMT messages received by an M3UA link Bytes of MGMT

Message Received Measurement point: The measured signaling link receives MGMT messages.

Meaning: Total disconnection times of the M3UA link Disconnection Times

Measurement point: A link is disconnected.

Meaning: Total congestion times of the M3UA link Congestion Times

Measurement point: The M3UA link is congested.

Meaning: Congestion duration of the M3UA link

Congestion Duration Measurement point: The measurement starts when the M3UA link is congested and stops when the M3UA link is recovered.

Meaning: Total unavailable times of the M3UA link Unavailable Times

Measurement point: The M3UA is unavailable.

Meaning: Unavailable duration of the M3UA link

Unavailable Duration Measurement point: The measurement starts when the M3UA link is unavailable and stops when the M3UA link is available.



A-19

A.3.5 MTP Dest Signaling Point Traffic


Meaning: Inaccessible times of an MTP destination signaling point (DSP) Inaccessible Times Measurement point: Measured on MTP layer 3.

Meaning: Inaccessible duration of an MTP DSP Inaccessible Duration Measurement point: Measured on MTP layer 3.

A.3.6 MTP Linkset Traffic


Meaning: Unavailable times of an MTP link set Unavailable Times

Measurement point: Measured on MTP layer 3.

Meaning: Unavailable duration of an MTP link set Unavailable Duration Measurement point: Measured on MTP layer 3.

A.3.7 MTP Signaling Link Traffic


Meaning: Available duration of a signaling link, that is, the duration within which the link is capable of transmitting or receiving messages Service Duration


Meaning: Unavailable duration of a signal link due to various reasons Unavail Duration Measurement point: Measured on MTP layer 3.

Meaning: Number of signaling link failures, for example, out of service. Fault Times Measurement point: Measured on MTP layer 3.

Meaning: Unavailable duration of a signal link due to failures Fault Duration




A-20


Meaning: Number of successful local management inhibiting operations for a signaling link Local Lin Times Measurement point: Measured on MTP layer 3.

Meaning: Duration of local management inhibiting of a signaling link upon successful local management inhibiting operation Local Lin Duration


Meaning: Number of successful remote management inhibiting operations for a remote signaling link Remote Lin Times Measurement point: Measured on MTP layer 3.

Meaning: Duration of remote management inhibiting of a signaling link upon successful remote management inhibiting operation

Remote Lin Duration


Meaning: Number of signaling link failures due to remote processor fault Rpo Times Measurement point: Measured on MTP layer 3.

Meaning: Unavailable duration of a signaling link due to the remote processor failure Rpo Duration Measurement point: Measured on MTP layer 3.

Meaning: Number of MSUs sent on the signaling link Msu Snd Num


Meaning: Number of SIF and SIO octets received Msu Rcv Num


Meaning: Number of octets sent on the signaling link Octets Snd Num


Meaning: Number of octets received from the signaling link Octets Rcv Num


Meaning: Percentage of signaling information sent on the signaling link Snd Seizure Ratio Measurement point: Measured on MTP layer 3.

Meaning: Percentage of signaling information received from the signaling link Rcv Seizure Ratio Measurement point: Calculated at BAM.



A-21


Meaning: Number of signaling link congestions Congestion Times


Meaning: Duration of signaling link congestion Congestion Duration Measurement point: Measured on MTP layer 3.

Meaning: Number of transfer-prohibited messages received Rcv Tfp Num


Meaning: Number of signaling link switchovers due to transmission failure Local Auto

Switchover Times Measurement point: Measured on MTP layer 3.

A.3.8 MTP3B Signaling DSP Measurement


Meaning: Inaccessible times of an MTP3B DSP DSP Inaccessible Times Measurement point: Measured by MTP3B.

Meaning: Inaccessible duration of an MTP3B DSP DSP Inaccessible Duration Measurement point: Measured by MTP3B.

Meaning: Number of the received transfer prohibited (TFP) signals that are related to an MTP3B DSP DSP Received TFP

Times Measurement point: The TFP messages of this DSP are received, and the DSP is reachable and available.

A.3.9 MTP3B Signaling Link Measurement


Meaning: Working duration of an MTP3B signaling link Link Work Duration Measurement point: The signaling link receives a LINK

ACTIVATE message.

Meaning: Number of signaling link failures (such as out-of-service)

Link Failed Times Measurement point: The signaling link receives an SLT FAILURE, OUT OF SERVICE, or CHANAGEOVER message.



A-22


Meaning: Unavailable duration of an MTP3B signaling link due to failures

Link Failed Duration Measurement point: The link receives an SLT FAILURE, OUT OF SERVICE, or CHANAGEOVER message.

Meaning: Number of successful local management inhibiting operations for an MTP3B signaling link Link Local Inhibit

Times Measurement point: The OM receives an LIA message from peer end after originating an LIN request.

Meaning: Duration of local management inhibiting upon successful local management inhibiting operation

Link Local Inhibit Duration

Measurement point: The measurement starts when the OM receives the LIA message from the peer end after originating an LIN request and stops when the OM receives an LUA (link enable) message.

Meaning: Number of successful remote link inhibiting operations for an MTP3B signaling link Link Remote Inhibit

Times Measurement point: The OM receives the LIN message from the peer end and returns an LIA message.

Meaning: Duration of remote management inhibiting upon successful remote management inhibiting operation

Link Remote Inhibit Duration

Measurement point: The measurement starts when the OM receives the LIA message from the peer end after originating an LIN request and stops when the OM receives an LUA (link enable) message.

Meaning: Number of MTP3B signaling link switchovers due to link unavailability Link Local Change

Over Times Measurement point: The MTP3B signaling link receives a COA message or the time-controlled switchover completes.

Meaning: Number of MSUs sent through an MTP3B link Link sent MSUs Measurement point: The measured signaling link sends

MSUs.

Meaning: Number of MSUs that MTP3B receives from the signaling link

Link Received MSUs Measurement point: The measured signaling link receives MSUs.

Meaning: Number of octets of the signaling information field (SIF) and service information octets (SIO) sent on an MTP3B signaling link Link Sent SIFSIO

Octets Measurement point: The measured signaling link sends an SIF or SIO.



A-23


Meaning: Number of octets of the signaling information field (SIF) and service information octets (SIO) received from an MTP3B signaling link Link Received

SIFSIO Octets Measurement point: The measured signaling link sends an SIF or SIO.

Meaning: Congestion times of an MTP3B signaling link Link Congestion Times Measurement point: The measured signaling link receives

the LINK CONGESTED message sent from the SAAL.

Meaning: Congestion duration of an MTP3B signaling link Link Congestion Duration Measurement point: The measured signaling link receives

the LINK CONGESTED message sent from the SAAL.

Meaning: Percentage of signaling link bandwidth used for sending signaling information Link Sending Used

Rate Measurement point: Calculated at BAM

Meaning: Percentage of signaling link bandwidth used for receiving signaling information Link Receiving Used

Rate Measurement point: Calculated at BAM

A.3.10 MTP3B Signaling Linkset Measurement


Meaning: Unavailable times of an MTP3B signaling link set Linkset Unavailable Times

Measurement point: The last available link in the link set receives an SLT FAILURE, OUT OF SERVICE, or CHANAGEOVER message and becomes unavailable.

Meaning: Unavailable duration of an MTP3B signaling link setLinkset Unavailable Duration

Measurement point: The measurement starts when the last available link in the link set receives an SLT FAILURE, OUT OF SERVICE, or CHANAGEOVER message and becomes unavailable, and stops when the link set is recovered.



A-24

A.3.11 SAAL Link Measurement and Statistics


Meaning: Duration of link in the In-Service state Duration of link in the In-Service state Measurement point: The signaling link is in the In-Service

state during periodic test.

SAAL link Failure (All reason)

Meaning: SAAL link Failure (All reasons except the failure from NO_RESPONSE expiration, excessive error rate, and excessive duration of congestion)

Meaning: Number of signaling link failures due to TIMER_NO_RESPONSE expiration SAAL link

failure(NO_RESPONSE timer expiration) Measurement point: The TIMER_NO_RESPONSE

specified in Q.2110 expires.

SAAL link failure(Excessive error rate)

Meaning: SAAL link failure due to excessive error rate

Meaning: Duration of SAAL signaling link failures due to congestion timeout SAAL link

failure(Excessive duration of congestion) Measurement point: The TIMER_NO_CREDIT specified

in Q.2144 expires.

Meaning: Times that the SAAL fails to complete the location procedure within the specified time SAAL link alignment

failure Measurement point: The SAAL fails to complete the locating procedure within the specified time.

NO of MAA_ERR. indication whit Error Type SD loss

Meaning: Number of MAA_ERROR indication with the error type "SD loss"

Receipt of unsolicited or inappropriate PDU

Meaning: Receipt of unsolicited or inappropriate PDUs

NO of Error reports from SSCOP to LM

Meaning: Number of errors reported from the SSCOP to the LM due to other reasons

NO of Unsuccessful retransmission Meaning: Number of unsuccessful retransmissions



A-25

A.3.12 SCCP Availability Statistic


Meaning: Unavailability times of a local SCCP due to failures Local SCCP

Unavailability: Node Failure Measurement point: The local SCCP is set unavailable

due to node failure.

Meaning: Unavailability times of a local SCCP due to O&M operations

Local SCCP Unavailability: Maintenance Made Busy

Measurement point: The local SCCP is set unavailable due to maintenance operations.

Meaning: Unavailability times of a local SCCP due to congestion Local SCCP

Unavailability: Congestion Measurement point: The local SCCP is set unavailable

due to congestion.

Meaning: Unavailability duration of a local SCCP Local SCCP Unavailability Duration: All Reasons

Measurement point: The measurement starts when the local SCCP is unavailable due to system failure, congestion, or maintenance operations, and stops when the local SCCP is recovered.

Meaning: Local SCCP recovered Local SCCP Availability: All Reasons

Measurement point: The local SCCP is set available after system failure is cleared, congestion is released, or maintenance operations are finished.

A.3.13 SCCP Performance Statistic


Meaning: Number of SCCP routing failures due to invalid addressing information Rf: No Translation for

an Address of Such Nature Measurement point: The SCCP receives the invalid

addressing information.

Meaning: Number of SCCP routing failures due to incorrect translation of valid address Rf: No Translation for

this Specific Address Measurement point: The SCCP can not find the translation result of a specific address.

Meaning: Number of SCCP routing failures due to signaling point unavailable Rf: Signalling Network

Failure Measurement point: The DSP is unavailable when the SCCP sends messages.



A-26


Meaning: Number of SCCP routing failures due to network congestion Rf: Signalling Network

Congestion Measurement point: The DSP is congested when the SCCP sends messages.

Meaning: Number of SCCP routing failures due to system failure Rf: Subsystem Failure

(unavailable) Measurement point: The system is faulty when the SCCP sends or receives messages.

Meaning: Number of SCCP routing failures due to system congestion

Rf: System Congestion Measurement point: The system is congested when the SCCP sends or receives messages.

Meaning: Number of SCCP routing failures due to subsystem un-installed Rf: Unequipped

Subsystem Measurement point: The subsystem is not installed when the SCCP sends or receives messages.

Meaning: Number of SCCP routing failures due to unknown reason

Rf: Reason Unknown Measurement point: SCCP routing fails due to unknown faults.

Meaning: Number of SCCP routing failures due to grammar errors in the addressing information Rf: Address Syntax

Error Measurement point: The SCCP detects that the grammar in the addressing information is incorrect.

A.3.14 SCCP Utilization Statistic


Meaning: Number of sending messages returned as the SCCP routing function cannot transfer connectionless service message

Sccpu: UDTS Messages Sent

Measurement point: When the local SCCP receives UDT messages, it performs routing function to determine if UDT addressing information packet includes insufficiently translated information, or if related subsystem or signaling point is unavailable. If yes, SCCP returns the packets to the source when the optional field is set to "Loopback upon errors".



A-27


Meaning: Number of the UDT messages that cannot be sent to the DSP Sccpu: UDTS

Messages Received Measurement point: The SCCP inlet receives UDTS messages.

Meaning: Number of the messages processed by the SCCP Sccpu: Total

Messages Measurement point: The SCCP receives SCCP messages from MTP, or receives SCCP user information.

Meaning: Number of messages destined to the local SCCP subsystem

Sccpu: Messages for Local Subsystem

Measurement point: The DPC of the SCCP messages and the DPC of the SCCP user information received by SCCP indicate the local signaling point, and the subsystems specified in the messages are available.

Meaning: Number of messages that require SCCP global title (GT) translation

Sccpu: Messages that Need Global Title Translation

Measurement point: The SCCP receives a GT routing indication for a called address in an MTP message, or receives a connectionless message, or a message that does not contain DPC in its connection request.

Meaning: Number of connectionless service (including class 0 and 1) messages sent by the SCCP Sccpu: All the

Connectionless Messages Sent Measurement point: The local SCCP outlet sends

connectionless messages.

Meaning: Number of connectionless service messages received by the SCCP Sccpu: All the

Connectionless Messages Received Measurement point: The local SCCP inlet receives

connectionless messages.

Meaning: Number of messages sent by the SCCP to a standby subsystem Sccpu: Messages for

the Backup Subsystem Measurement point: The decoding flag is set to "Decode to

standby subsystem.

A.3.15 TCAP Availability Statistics


Meaning: Unavailability of a local TCAP due to failures TCAP Availability: Failure Measurement point: None.



A-28


Meaning: Unavailability of a local TCAP due to O&M operations TCAP Availability:

Maintenance Made Busy Measurement point: A dialog is released in maintenance

operation.

Meaning: Unavailability of a local TCAP due to congestion TCAP Availability: Congestion Measurement point: None.

Meaning: Unavailable duration of a local TCAP due to various reasons TCAP Availability:

Unavailability Duration Measurement point: A dialog is released in maintenance

operation.

A.3.16 TCAP Component Sublayer Performance Statistics


Meaning: Number of unrecognized components TCAP CSLP: Unrecognized Component

Measurement point: The TCAP receives or sends components with unrecognized tuples.

Meaning: Number of components incorrectly typed TCAP CSLP: Mistyped Component Measurement point: The TCAP receives or sends

components with unrecognized tuples.

Meaning: Number of components with incorrect structure TCAP CSLP: Badly Structured Component

Measurement point: The TCAP receives components with incorrect structure.

Meaning: Number of unrecognized link IDs TCAP CSL Performance: Unrecognized Link ID (invoke)

Measurement point: The TCAP receives INVOKE components that contain unrecognized link IDs.

Meaning: Number of unexpected return results TCAP CSLP: Return Result (rr) Unexpected Measurement point: The TCAP receives unexpected return

results.

Meaning: Number of unrecognized INVOKE IDs in return results TCAP CSLP:

Unrecognized Invoke ID (rr) Measurement point: The TCAP receives unrecognized

INVOKE ID in return results.

Meaning: Number of unexpected return errors TCAP CSLP: Return Error (re) Unexpected Measurement point: The TCAP receives unexpected return

errors.



A-29


Meaning: Number of unrecognized INVOKE IDs in return errors TCAP CSLP:

Unrecognized Invoke ID (re) Measurement point: The TCAP receives unrecognized

INVOKE ID in return errors.

A.3.17 TCAP Component Utilization Statistics


Meaning: Number of INVOKE components sent from the current node TCAP CU: Invoke

Component Sent Measurement point: The TCAP sends an INVOKE-INV message.

Meaning: Number of INVOKE components received by the current node TCAP CU: Invoke

Component Received Measurement point: The TCAP receives an INVOKE-INV message.

Meaning: Number of return result "Last INVOKE components" sent from the current node TCAP CU: Last Result

Component Sent Measurement point: The TCAP sends return result "Last INVOKE components".

Meaning: Number of return result "Last INVOKE components" received by the current node TCAP CU: Last Result

Component Received Measurement point: The TCAP receives return result "Last INVOKE components".

Meaning: Number of return result "Non-last INVOKE components" sent from the current node TCAP CU: Not Last

Result Component Sent Measurement point: The TCAP sends return result

"Non-last INVOKE components".

Meaning: Number of return result "Not-last INVOKE components" received by the current node TCAP CU: Not Last

Result Component Received Measurement point: The TCAP receives return result

"Non-last INVOKE components".

Meaning: Number of return error components sent from the current node TCAP CU: Return

Error Component Sent Measurement point: The TCAP sends return error "RE component".



A-30


Meaning: Number of return error components received by the current node TCAP CU: Return

Error Component Received Measurement point: The TCAP receives return error "RE

component".

Meaning: Number of Reject components sent from the current node TCAP CU: Reject

Component Sent Measurement point: The TCAP sends a Reject component.

Meaning: Number of Reject components received by the current node TCAP CU: Reject

Component Received Measurement point: The TCAP receives a Reject component.

A.3.18 TCAP Message Utilization Statistics


Meaning: Number of invoke messages sent from the current node TCAP MU: Invoke

Message Sent Measurement point: The TCAP sends an INVOKE-INV message.

Meaning: Number of INVOKE messages received by the current node TCAP MU: Invoke

Message Received Measurement point: The TCAP receives an INVOKE-INV message.

Meaning: Number of return result "Last INVOKE message" sent from the current node TCAP MU: Last Result

Message Sent Measurement point: The TCAP sends return result "Last INVOKE message".

Meaning: Number of return result "Last INVOKE message" received by the current node TCAP MU: Last Result

Message Received Measurement point: The TCAP receives return result "Last INVOKE message".

Meaning: Number of return result "Non-last INVOKE message" sent from the current node TCAP MU: Not Last

Result Message Sent Measurement point: The TCAP sends return result "Non-last INVOKE message".

Meaning: Number of return result "Non-last INVOKE message" received by the current node TCAP MU: Not Last

Result Message Received Measurement point: The TCAP receives return result

"Non-last INVOKE message".



A-31


Meaning: Number of return error messages sent from the current node TCAP MU: Return

Error Message Sent Measurement point: The TCAP sends return error "RE message".

Meaning: Number of return error messages received by the current node TCAP MU: Return

Error Message Received Measurement point: The TCAP receives return error "RE

message".

Meaning: Number of Reject messages sent from the current node TCAP MU: Reject

Message Sent Measurement point: The TCAP sends a Reject message.

Meaning: Number of Reject messages received by the current node TCAP MU: Reject

Message Received Measurement point: The TCAP receives a Reject message.

A.3.19 TCAP Transaction Sublayer Performance Statistics


Meaning: Number of P-ABORT messages (with the cause of unrecognized message type) generated due to syntax check failure of the message received from the peer end TCAP TSL P:

Message Type Unknown (p_abort) Measurement point: An error occurs in the syntax check

(with the cause of unrecognized message type) on the message received by the TCAP from the peer end.

Meaning: Number of P-ABORT messages (with the cause of incorrect transaction part) generated due to syntax check failure of the message received from the peer end TCAP TSL P:

Incorrect Transaction Portion (p_abort) Measurement point: An error occurs in the syntax check

(with the cause of incorrect transaction part) on the message received by the TCAP from the peer end.

Meaning: Number of P-ABORT messages (with the cause of transaction part format error) generated due to syntax check failure of the message received from the peer end

TCAP TSL P: Badly Formatted Transaction Portion (p_abort)

Measurement point: An error occurs in the syntax check (with the cause of transaction part format error) on the message received by the TCAP from the peer end.



A-32


Meaning: Number of P-ABORT messages (with the cause of unrecognized transaction ID) generated due to syntax check failure of the message received from the peer end TCAP TSL P:

Unrecognized TID (p_abort) Measurement point: An error occurs in the syntax check

(with the cause of unrecognized transaction ID) on the message received by the TCAP from the peer end.

Meaning: Number of P-ABORT messages (with the cause of restricted transaction sublayer resource) generated due to unavailability of resource for call setup TCAP TSL P:

Resource Limitation (p_abort) Measurement point: The TCAP receives a message and

prepares to set up a call, but finds that no resource is available.

Performance Measurement Manual HUAWEI HLR9820 Home Location Register Appendix B MAP Performance Measurement Object Data


B-1

Appendix B MAP Performance Measurement Object Data

This appendix describes the MAP performance measurement objects.

Object data Meaning

UPDL updateLocation

CNCL cancelLocation

PRMN provideRoamingNumber

INSD insertSubscriberData

DLSD deleteSubscriberData

SNDP sendParameters

REGS registerSS

ERAS eraseSS

ACTS activateSS

DEAS deactivateSS

INTS interrogateSS

ATHF authenticationFailureReport

RGPW registerPassword

GTPW getPassword

PUSD processUnstructuredSS-Data

SRIF sendRoutingInfo

UPGL updateGprsLocation

SRIG sendRoutingInfoForGprs

FLRT failureReport

NMPG noteMsPresentForGprs

HRST HLRReset

FWCK forwardCheckSsIndication

SRIS sendRoutingInfoForSM

RPSM reportSmDeliveryStatus

NTSP noteSubscriberPresent

Performance Measurement Manual HUAWEI HLR9820 Home Location Register Appendix B MAP Performance Measurement Object Data


B-2

Object data Meaning

ASWR alertServiceCentreWithoutResult

SAUI sendAuthenticationInfo

RSDT restoreData

SNDI sendIMSI

PUSR processUnstructuredSS-Request

USSR unstructuredSS-Request

USSN unstructuredSS-Notify

IFMS informServiceCentre

ALSC alertServiceCentre

RDSM readyForSM

PGMS purgeMS

PVSI provideSubscriberInfo

ATIG anyTimeInterrogaton

SRIL sendRoutingInfoForLCS

Performance Measurement Manual HUAWEI HLR9820 Home Location Register Appendix C Acronyms and Abbreviations


C-1

Appendix C Acronyms and Abbreviations

A

ATI Any Time Interrogation

B

BAIC Barring of All Incoming Calls

BAM Back Administration Module

BCD Binary-Coded Data

C

CPU Central Processing Unit

COA Changeover Acknowledgement signal

D

DPC Destination Point Code

DSP Destination Signaling Point

G

GMSC Gateway Mobile Switching Center

GSM Global System for Mobile Communications

GT Global Title

H

HDU HLR Database Unit

HLR Home Location Register

I

ID Identity

IP Internet Protocol



C-2

L

LIA Link Inhibit Acknowledgement signal

LIN Link Inhibit signal

LMT Local Maintain Terminal

LUA Link Uninhibit Acknowledgement signal

M

M3UA MTP3-User Adaptation Layer

MAP Mobile Application Part

MTC Mobile Terminated Call

MGMT Management system

MTP Message Transfer Part

MTP3B Message Transfer Part (broadband)

MSU Message Signal Unit

O

OM Operations and Maintenance

S

SAAL Signaling ATM Adaptation Layer

SCCP Signaling Connection and Control Part

SIF Signaling Information Filed

SIO Service Information Octet

SMC Short Message Center (used for SMS)

SMS Short Message Service

SPC Signaling Point Code

STP Signaling transfer point

T

TCAP Transaction Capabilities Application Part

U



C-3

UDT Unit Data

USSD Unstructured Supplementary Service Data

V

VLR Visitor Location Register

Performance Measurement Manual HUAWEI HLR9820 Home Location Register Index


i-1

Index

A acronyms and abbreviations

A, C-1

B, C-1

C, C-1

D, C-1

H, C-1

I, C-1

L, C-2

M, C-2

O, C-2

S, C-2

T, C-2

U, C-2

V, C-3

activating measurement task, 2-23

analysis method, 3-1

analysis, common performance measurement task,

3-2

analysis, performance measurement result, 3-1

B basic concept, 1-1

C checking detailed information of measurement task,

2-24

CPU performance measurement, 3-5

CPU utilization measurement, 3-2

creating custom entity, 2-43

creating measurement task, 2-6

creating template, 2-33

custom entity

creating, 2-43

deleting, 2-46

modifying, 2-45

custom entity management

creating custom entiy, 2-43

modifying custom entity, 2-45, 2-46

customizing system configuration, 2-5

D deactivating measurement task, 2-22

deleting custom entity, 2-46

deleting measurement task, 2-25

deleting template, 2-43

dumping measurement result, 2-31

E entity management function, 1-6

example, 2-46

L logging in to system, 2-2

M managing office information, 2-3

MAP performance measurement, 3-4

MAP performance measurement object data, B-1

measurement entity, 1-2

measurement object, 1-2

measurement result analysis

CPU performance measurement, 3-5

CPU utilization measurement, 3-2

MAP performance measurement, 3-4

MTP signaling link measurement, 3-6

SCCP availability measurement, 3-7

SCCP performance measurement, 3-9

measurement system functions

entity management, 1-6

result management, 1-5

task management, 1-5

template management, 1-6



i-2

threshold management, 1-6

measurement system, structure, 1-4

measurement task, 1-1

activating, 2-23

checking, 2-24

creating, 2-6

deactivating, 2-22

deleting, 2-25

modifying, 2-17

querying, 2-23

measurement task management

activating measurement task, 2-23

checking detailed information of measurement

task, 2-24

creating measurement task, 2-6

deactivating measurement task, 2-22

deleting measurement task, 2-25

modifying measurement task, 2-17

querying measurement task, 2-23

measurement time, 1-2

measurement type, 1-2

measurement unit, 1-2

modifying custom entity, 2-45

modifying measurement task, 2-17

modifying template, 2-43

MTP signaling link measurement, 3-6

P performance measurement entity

global component, A-1

HDU traffic task

CPU performance measurement, A-2

MAP performance measurement, A-2

SCCP performance measurement, A-6

SUB (subscriber) performance measurement,

A-7

SWB (subscriber with BS) performance

measurement, A-7

SWC (subscriber with CAMEL) performance

measurement, A-8

SWCS (subscriber with CB SS) performance

measurement, A-9

SWG (subscriber with GPRS) performance

measurement, A-9

SWL (subscriber with LCS) performance

measurement, A-10

SWLK (subscriber with lock) performance

measurement, A-10

SWO (subscriber with ODB) performance

measurement, A-11

SWOS (subscriber with other SS) performance

measurement, A-12

SWR (subscriber when roaming) performance

measurement, A-13

signaling and interface

M3UA destination entity, A-13

M3UA linkset flux traffic, A-14

M3UA linkset state traffic, A-16

M3UA signaling link traffic, A-16

MTP linkset traffic, A-19

MTP signaling link traffic, A-19

MTP signaling point traffic, A-18

MTP3B signaling DSP measurement, A-21

MTP3B signaling link measurement, A-21

MTP3B signaling linkset measurement, A-23

SAAL measurement and statistics, A-23

SCCP availability statistics, A-24

SCCP performance statistics, A-25

SCCP utilization statistics, A-26

TCAP availability statistics, A-27

TCAP component sublayer performance

statistics, A-28

TCAP component utilization statistics, A-28

TCAP message utilization statistics, A-30

TCAP transaction sublayer performance

statistics, A-31

Q querying measurement result, 2-26

querying measurement task, 2-23

R result management function, 1-5



i-3

S SCCP availability measurement, 3-7

SCCP performance measurement, 3-9

system management

customizing system configuration, 2-5

logging in to system, 2-2

managing office information, 2-3

T task management function, 1-5

task result

dumping, 2-31

querying, 2-26

template

creating, 2-33

deleting, 2-43

modifying, 2-43

template management

creating template, 2-33

deleting template, 2-43

modifying template, 2-43

template management function, 1-6

threshold, 1-3

threshold management function, 1-6

i.

hlr9820 performance measurement manual

Documents