concepts in performance measurement

8/3/2019 Concepts in Performance Measurement

1/13

Concepts in Performance Measurement

The manual describes performance management focusing on the performance measurement system.

Performance Measurement

Performance measurement (PM) is to measure the traffic and load information of the

MSOFTX3000 and the communication network. Thus, it can optimize the performance by

providing the following data:

Metrics data

Network planning data

Operation and management data

The PM focuses on how to allocate resources in a better way.

The system measures the traffic and operation related objects in the trunking, switching, and

signaling subsystem of the MSOFTX3000.

The PM objects are as follows:

Number of calls

Traffic

Average seizure duration

Network state monitoring

Equipment operation

The three elements of PM are as follows:

PM entity

PM object

PM time

1.1.2 Traffic

Overview of Traffic

The traffic is the extent to which a subscriber occupies the switching network and the


2/13

switching network units. It is the result of the accumulated points of transient traffic (during a

set period) divided by the PM time. The traffic is in unit of Erl.

A=s A stands for call source traffic. stands for the average times of call during a unit time.

s stands for the average occupation time of each call.

During the time T, the traffic from terminal i into the switching system is:

nihi/T ni stands for the number of calls originated by subscriber terminal i during time T.

hi stands for the average time of the calls originated by subscriber terminal i.

Process of Traffic Measurement

During a PM period and among a specified PM object group such as the trunk of incoming

calls, there will be multiple call processes at the same time. Their start and end time is

unpredictable. Some processes may exceed the limit of the period.

A typical process of traffic measurement is as follows:

1. During the period, the system samples the number of subscribers conversing at 1 Hz, that

is, once per second.

2. The system stores the sampling results in a temporary counter.

3. The system sums up and stores the results of all sampling periods in a traffic counter.

4. At the end of the period, the system multiplies the value in the traffic counter by the

period time to get the total conversing (or trunk occupation) time in the period.

The result of the total conversing time divided by the period is the traffic (traffic intensity)

during the time segment. For example,

PM period: five minutes PM object: outgoing trunk occupied traffic

From the start time, the PM samples the occupancy of the outgoing trunk each second and

sums up the results. Assume that the accumulation of the sampling is 45000, the outgoing

trunk occupied traffic during the time segment is 45000*1/(5*60) =150 Erl.


3/13

1.1.3 Performance Measurement Task

The PM task is the descriptions on a PM operation. It covers the PM object identifiers, PM

time, output metrics and output time. The PM task is the basic management unit of the PM system. It

includes three elements: PM object, PM entity, and PM time.

1.1.4 Performance Measurement Unit

A PM unit is a combination of PM entity and PM object. It reflects the traffic model of a

certain PM object. For instance, the incoming traffic measurement describes the traffic model

of the incoming office direction (a PM object).

1.1.5 Performance Measurement Entity

A PM entity is a specific item in traffic measurement. It can be traffic, number of calls, and

average seizure duration. PM entities, PM sets and PM units form a three-layer structure. Each set

contains a number of units. Each unit contains a number of entities.

The PM entities of the MSOFTX3000 include the original entities and custom entities.

The original entities are those defined by the system, such as the call attempts, the seizure

traffic. original entities. The name and arithmetic algorithms of the custom entity are newly defined.

1.1.6 Performance Measurement Object

Definition

A PM object is the physical or logical entity and the combination of them involved in the PM,

such as an MSC, a cell, an office direction, a destination.

Object type is the type of the physical or logical entity involved in the PM, such as an

MSC, a trunk group, an office direction, or a destination.

Object instance is a specific object. For example, when defining a PM task, if the object

type is Office Direction, the object instances are office direction 0 and office direction 1.

Relation Between PM Unit and PM Object

PM unit determines the type of PM object. One PM unit can correspond with one or more object types.

Multiple object instances can embody one object type.


4/13

is no need to specify PM objects.

1.1.7 Performance Measurement Time

Definition

The PM time includes the following time information of a PM task:

Start date PM period PM period type PM time segment PM time type

Time Type

The PM can be performed by day, week, and month.

PM by day: implementing PM everyday PM by week: implementing PM on certain days every week

PM by month: implementing PM on certain days every month

Classification of PM Tasks

The PM tasks can be classified as semi-permanent task and period-limited task in terms of time.

Table 1-2 describes the differences between a semi-permanent task and a period-limited task.

PM Period

The PM period is the output period of PM result. In the MSOFTX3000, it can be 1 minute, 5

minutes, 15 minutes, 30 minutes, 1 hour, or 1 day.


5/13

PM Time Segment

The MSOFTX3000 allows you to divide each day into a maximum of three time segments

without an overlap. Within the predefined time segments, the PM is carried out based on the

predefined period and is stopped between the time segments. The time segment and period

determine the daily time mode in which a task is carried out.

1.1.8 Performance Measurement Set

A PM set is a group of PM units sharing the same attributes. For instance, the PM set of the call

connection process is composed of answer PM and call pre-establishment PM.

In general, one type of PM task relates to a PM set. A PM system can be described by several sets.

1.1.9 Busy Hour Call Attempt

Definition

Busy hour call attempt (BHCA) reflects the call processing capability of the MSOFTX3000.

It depends on the processing capability of the CPU. It is measured by the total number of calls

processed in the unit time. Unit: times/hour.

Fixed Line Subscriber in Performance Measurement

In a PM, the non-local subscribers are regarded as fixed line subscribers. Their calls are

transferred through the following links and trunks:

Telephone User Part (TUP) links

ISDN User Part (ISUP) links

Bearer Independent Call Control Protocol (BICC) links

Trunks

Primary Rate Adaptation (PRA) links

Therefore, all incoming calls, outgoing calls, and tandem calls are considered to be related to

the fixed line subscriber, regardless of whether the peer office is the PSTN or a mobile

network. The calls between two mobile subscribers occur only within an office.


6/13

1.2 Other Concepts in Performance Measurement

1.2.1 Performance Measurement Task Status

A PM task covers the following five states in a PM period:

Created Registered Measured Deactivated Completed

Performance Measurement Report

It describes the results of the traffic PM of a certain type, including:

PM object PM entity value PM period Start time End time

The report provides basis for further PM, planning, running and management of the

performances in the entire office and network.


7/13

Output Model

It determines where the system sends PM results. The MSOFTX3000 defines the following

three output models: 1- To the current workstation (WS) 2- To the traffic measurement port

3-To network management (NM) port

1.3 Architecture of Performance Measurement System

1.3.1 Overview of Performance Measurement System Architecture

The MSOFTX3000 PM system is composed of the host, BAM, workstation, and M2000 Server.

Figure 1-2 shows the system structure.

Workstation Functions

General Features of Workstation

The workstation is a subsystem of several functional modules. It provides operation and

maintenance (O&M) interface, through which you can implement the following features:

MML command execution Data configuration Equipment maintenance Fault detection

and elimination Subscriber management PM

The workstation communicates with the BAM in the MML. It runs commands and generates reports.

Workstation Functions in Performance Measurement System

When installing the MSOFTX3000 O&M Center on the workstation, the installer installs the

PM system as an integral component. The software provides a direct operation interface to

register and delete PM tasks, and to browse the status and results of these tasks.


8/13

1.3.3 Functions of M2000

General Features of M2000

The iManager M2000 Mobile Element Management System (M2000 for short) manages and

maintains Huawei mobile network products in the following aspects:

Centralized fault management Centralized performance management Centralized configuration

management Centralized software management Centralized topology management

Centralized security management System management

The M2000 can access the following Huawei mobile network products:

Radio network base station (NodeB) Serving GPRS support node (SGSN) Gateway GPRS support

node (GGSN) Charging Gateway (CG) Home location register (HLR)

Mobile switching center server (MSC Server) Media gateway (MGW) Radio Network Controller

(RNC)

Functions of M2000 in Performance Management System

The M2000 provides the interface for the network management center to manage PM tasks. It

retrieves the necessary PM data from the host PM process through the counterpart in the BAM.

1.3.4 Performance Measurement Process of Host

The PM process collects the following data: Call processing data Equipment data

Signaling data Intelligent service data

The PM process combines all the data into the result of PM task, and then transmits the result The PM

process combines all the data into the result of PM task, and then transmits the result

to the BAM. Table 1-5 lists the features of PM process.


9/13

The PM system helps you manage the PM. You can register and delete tasks on the

workstation. The process of the PM management is as follows:

1. The system sends commands to the host through the BAM.

2. The host processes the commands and exports reports.

3. At the end of the PM period, the host sends the results to the BAM.

4. The BAM stores the results of all tasks in the hard disk. 5. The BAM sends all the results to the M2000.

6. The M2000 stores the results used for the report in the database.

1.3.5 BAM Functions

General Features of BAM

Table 1-6 lists the features provided by the BAM.


10/13

BAM Functions in Performance Measurement System

The BAM internal PM process can serve as the media among the M2000, PM console, and

host PM process. It maintains and manages the task queue, and cooperates with the host PM

process to ensure error-free transmission. The database stats stores the results of the PM task

in the BAM. One task corresponds to a database table. When the task is deleted, the table is

also deleted. For instance, table RESULT16 stores the results of task 16. Each table can store

up to 500,000 records. When the table reaches its full storage, the oldest records are replaced

by new ones. In addition, the system converts the protocols of the service request sent from

local maintenance terminal (LMT) using the M2000, before it is processed further in the

BAM.

1.4 Functions of Performance Measurement System

1.4.1 Overview of System Functions

The workstation is a man-machine interactive interface. You can select either the GUI or the

MML mode for the PM. On the workstation, you can query the data in real time, manage

tasks, entities, templates, and thresholds, and customize entities. These functions are


11/13

described in the following sections.

The MSOFTX3000 supports up to 128 tasks. Each task contains up to 255 entities. The period

can be 1 minute, 5 minutes, 30 minutes, 1 hour, or 1 day.

1.4.2 Task Management

Overview of Task Management

The task management functions are as follows:

Creating a Task Deleting a Task Modifying a Task Deactivating and Activating a Task

Querying Task Information Querying Task Result Restoring a Task

Creating a Task

In general, the PM entities are organized and managed under the PM units. You may, however,

want to put all the entities that reflect the same switching service function into one task, and

have the results output together, especially when generating PM reports.

Deleting a Task

On completing a task, the system does not automatically delete the task. You have to delete it.

When a task is deleted, the result is automatically deleted.

Modifying a Task

You can change the name, description, PM entity, PM object, and PM time of a task.

Deactivating and Activating a Task

You can deactivate a PM task from implementation. The task will not be deleted.

The Activate operation is the reverse of the Deactivate operation. You can activate a

deactivated task and export the results.

Querying Task Information

You can query the following static data information of a task in the host:

Task status

Its PM function set


12/13

Task time attribute

PM entities

Object type

Querying Task Result

You can query the result of a task, and browse the statistical content in the table form or data

chart.

Restoring a Task

The PM system backs up the data related to a performance task. You can restore the task after

switching over or restarting any board.

When you switch over a board, the BAM recovers the related task on the board.

1.4.3 Performance Measurement Entity Customization

You can customize a PM entity by combining the original entities in the system through

arithmetic calculations. To collect performance data and to observe the network status flexibly,

you can perform the following operations with a customized PM entity:

Creating, modifying, and deleting the customized PM entity

Dynamically refreshing the entity list Creating a PM task with customized entities


13/13

concepts in performance measurement

Documents