Performance Management Description (V200R007C02 - 02)

HUAWEI CSOFTX3000 Mobile SoftSwitch Center
V200R007C02
Performance Management Description
Issue
02
Date
2010-03-15
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.

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

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

HUAWEI CSOFTX3000
Contents
Contents
About This Document.....................................................................................................................1
1 Introduction to the Performance Measurement...................................................................1-1
1.1 Basic Concepts of Performance Measurement................................................................................................1-2
1.1.1 Measurement Subset..............................................................................................................................1-5
1.1.2 Measurement Unit..................................................................................................................................1-6
1.1.3 Measurement Entity...............................................................................................................................1-6
1.1.4 Measurement Task.................................................................................................................................1-6
1.1.5 Measurement Period...............................................................................................................................1-6
1.1.6 Measurement Object..............................................................................................................................1-6
1.1.7 Performance Alarm................................................................................................................................1-7
1.2 Overview of Performance Measurement System Architecture.......................................................................1-8
1.2.1 Performance Measurement System Architecture...................................................................................1-8
1.2.2 Interactions Between Components.........................................................................................................1-9
1.3 Classification of Measurement Elements......................................................................................................1-10
1.3.1 Classification of Performance Measurement Sets................................................................................1-10
1.3.2 Classification of Performance Measurement Units..............................................................................1-11
1.3.3 Classification of Performance Measurement Entities..........................................................................1-18
2 System Function.........................................................................................................................2-1
2.1 Measurement Management.............................................................................................................................2-2
2.2 Querying Measurement Result........................................................................................................................2-2
2.3 Exporting Measurement Result.......................................................................................................................2-2
2.4 Threshold Alarm.............................................................................................................................................2-3
2.5 Customizing Entity..........................................................................................................................................2-3
3 Applications of Performance Measurement.........................................................................3-1

3.1 Routine Maintenance.......................................................................................................................................3-2
3.1.1 Troubleshooting with Performance Measurement Results....................................................................3-2
3.1.2 Checking Running Conditions of All Devices.......................................................................................3-3
3.2 Performance Monitoring.................................................................................................................................3-3
3.2.1 Obtaining Incoming and Outgoing Office Traffic Information.............................................................3-4
3.2.2 Obtaining Tandem Traffic Information..................................................................................................3-4
3.2.3 Measuring Failure Causes for the Entire MSC......................................................................................3-4
3.2.4 Measuring Calls to a Destination...........................................................................................................3-5
Issue 02 (2010-03-15)

Contents
HUAWEI CSOFTX3000
3.2.5 Measuring Traffic in an Office Direction...............................................................................................3-5
3.3 Network Optimization.....................................................................................................................................3-5

3.3.1 Analyzing Traffic Based on Performance Measurement Results..........................................................3-6
3.3.2 Balancing Traffic with Performance Measurement Results...................................................................3-6
3.3.3 Analyzing Connection Rate with Performance Measurement...............................................................3-7
3.3.4 Methods of Improving Call Completion Rate........................................................................................3-8
3.4 Analysis Methods of Performance Measurement Results.............................................................................3-10
3.4.1 Overview of the Analysis Methods......................................................................................................3-10
3.4.2 Example of Analysis............................................................................................................................3-11
4 Common Measurement Tasks.................................................................................................4-1

4.1 Frequently Used Performance Measurement Tasks for the End Office..........................................................4-2
4.2 Frequently Used Performance Measurement Tasks for the Converging Office.............................................4-7
4.3 Frequently Used Performance Measurement Tasks for the Gateway Office................................................4-11
5 KPI System.................................................................................................................................. 5-1

5.1 Basic Telecom Service-Specific KPI..............................................................................................................5-2
5.2 Mobility Management-Specific KPI...............................................................................................................5-2
5.3 Service-Specific KPI.......................................................................................................................................5-3
5.4 Authentication.................................................................................................................................................5-3
ii

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
Figures
Figures
Figure 1-1 Architecture of PM system.................................................................................................................1-8
Issue 02 (2010-03-15)

iii
HUAWEI CSOFTX3000
Tables
Tables
Table 1-1 Comparison between semi-permanent task and period-limited task....................................................1-4
Table 1-2 Example of relation between PM unit and PM object.........................................................................1-4
Table 1-3 PM of BHCA in the CSOFTX3000.....................................................................................................1-5
Table 1-4 How to select PM set..........................................................................................................................1-11
Table 1-5 PM set and its PM units.....................................................................................................................1-12
Table 3-1 Description of factors that affect call completion rate.........................................................................3-7
Table 3-2 Cause of generation of signaling link messages that affect call completion rate.................................3-8
Table 3-3 Link PM data table one......................................................................................................................3-11
Table 3-4 Link PM data table two......................................................................................................................3-12
Table 3-5 Number of subscribers in the VLR....................................................................................................3-13
Table 4-1 PM units in Total Traffic of the end Office.........................................................................................4-2
Table 4-2 PM units in Total Traffic of the Office................................................................................................4-7
Table 4-3 Frequently used performance measurement tasks for the gateway office.........................................4-11
Table 5-1 The name and description of KPI.........................................................................................................5-2
Table 5-2 The name and description of CPI.........................................................................................................5-2
Issue 02 (2010-03-15)

HUAWEI CSOFTX3000
About This Document
About This Document

Intended Audience
This document describes the concepts related to performance management, structure and
functions of the performance management system, and classification and application of
performance measurement entities.
This document is intended for:
l
Engineering technical personnel
Operation and maintenance engineers
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Changes in Issue 01 (2009-12-15)

Initial field trial release.
Changes in Issue 02 (2010-03-15)

Second release.
Issue 02 (2010-03-15)

HUAWEI CSOFTX3000
1 Introduction to the Performance Measurement
Introduction to the Performance

Measurement
About This Chapter

1.1 Basic Concepts of Performance Measurement
1.2 Overview of Performance Measurement System Architecture
1.3 Classification of Measurement Elements
Issue 02 (2010-03-15)

1-1
HUAWEI CSOFTX3000
1.1 Basic Concepts of Performance Measurement

Traffic
The traffic is the extent to which a subscriber occupies the switching network and the switching
network units. It is the result of the accumulated points of transient traffic (during a set period)
divided by the PM time. The unit for traffic is Erl.
A = s
l
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
l
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 a 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,
l
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 45000x1/(5x60) =150 Erl.
Performance Measurement Task

The PM task is the descriptions of a PM operation. It covers the PM object identifiers, PM time,
output entities, and output time.
1-2

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
The PM task is the basic management unit of the PM system. It includes three basic elements:
PM object, PM entity, and PM time.
Performance Measurement Object

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.
l
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.
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 CSOFTX3000 include the original entities and custom entities.
l
The original entities are those defined by the system, such as the call attempts, the seizure
traffic.
The custom entities are defined by the user using specific calculation methods based on the
original entities. The name and arithmetic algorithms of the custom entity are newly
defined.
Performance Measurement Time

The PM time includes the following time information of a PM task:
l
Start date
PM period
PM period type
PM time segment
PM time type
The PM can be performed by day, week, and month.

l
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
The PM tasks can be classified as semi-permanent task and period-limited task in terms of
time.Table 1-1 describes the differences between a semi-permanent task and a period-limited
task.
Issue 02 (2010-03-15)

1-3
HUAWEI CSOFTX3000
Table 1-1 Comparison between semi-permanent task and period-limited task

PM Task
Must Define End Time
How to End
Semi-permanent
Yes
Stopped when deleted or deactivated
Period-limited
No
Stopped at end time
The PM period is the output period of PM result. In the CSOFTX3000, it can be 5 minutes, 15
minutes, 30 minutes, 1 hour, or 1 day.
The CSOFTX3000 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.
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).
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.
Table 1-2 describes an example of relation between PM unit and PM object.
Table 1-2 Example of relation between PM unit and PM object
Traffic Measurement Element
Content
PM set
Bearer traffic
PM unit
Office direction Outgoing Calls
PM object type
Outgoing office direction
PM object instance
Office direction 1, 2, 3, n
Classification of PM Tasks
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.
Busy Hour Call Attempt

Busy hour call attempt (BHCA) reflects the call processing capability of the CSOFTX3000. It
depends on the processing capability of the CPU. It is measured by the total number of calls
processed in the unit time.
1-4

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
Unit: times/hour.
Table 1-3 describes the PM method of BHCA in the CSOFTX3000.
Table 1-3 PM of BHCA in the CSOFTX3000
Traffic Measurement Entity
Content
PM set
Global component
PM unit
CPU seizure ratio traffic
PM entity
Originating call attempt times
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:
l
Telephone User Part (TUP) links
ISDN User Part (ISUP) 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.
1.1.1 Measurement Subset
1.1.2 Measurement Unit
1.1.3 Measurement Entity
1.1.4 Measurement Task
1.1.5 Measurement Period
1.1.6 Measurement Object
1.1.7 Performance Alarm
1.1.1 Measurement Subset

A measurement set is a set of measurement units that have certain common attributes. For
example, the measurement units CPU Load Measurement, IP Traffic Measurement, Performance
Measurement of Board Memory, and Performance Measurement of External Network Interfaces
can be used to measure the performance of boards. Therefore, these measurement units are
classified into a measurement subset, namely, Device.
In the performance management system, you can group multiple measurement entities that have
the same measurement objectives into a measurement unit and then group the measurement units
that have certain common attributes into a measurement subset. This behavior can facilitate
performance measurement.
Issue 02 (2010-03-15)

1-5
HUAWEI CSOFTX3000
1.1.2 Measurement Unit

A measurement unit is an effective combination of measurement objects and measurement
entities. It reflects the performance of a measurement object. For example, the measurement of
CPU usage, whose measurement object is a hardware board, consists of three measurement
entities, Duration For Peak CPU Load, Mean CPU Load, and Maximum CPU Load.
1.1.3 Measurement Entity

A measurement entity is the data to be collected for completing a measurement. For example,
Mean CPU Load and BPS of Sent. Measurement entities can be categorized as original entity
and customized entity.
l
Original entity
An original entity refers to an entity defined in the system. For example, Mean CPU Load
and Used Memory Size.
Customized entity
A customized entity refers to an entity that is obtained by combining original entities
through arithmetic according to specific requirements. For example, the entity Number of
IP Packets Successfully Transmitted can be customized by the following formula: Number
of IP packets successfully transmitted = Number of IP packets successfully received +
Number of IP packets successfully sent.
1.1.4 Measurement Task

A measurement task refers to a basic management unit of the performance measurement system.
It is the description for a specific measurement operation.
A measurement task comprises three basic elements:
l
Measurement unit
Measurement object
Measurement period
When creating a measurement task, you can set parameters such as the measurement unit,
measurement object, and measurement period.
1.1.5 Measurement Period

The measurement period refers to the time between the initiation of two successive gatherings
of measurement data. The performance management system supports the following
measurement periods: 5 minutes, 15 minutes, 30 minutes, 1 hour, and 24 hours.
If the measurement tasks are many and the measurement period is short, the system performance
may be affected. Therefore, you are advised to set the measurement period to 1 hour.
1.1.6 Measurement Object

Basic Concepts
l
1-6
Measurement object:
Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
It refers to the target for which a data is collected. It can be a physical entity, a logical entity,
or a combination of physical and logical entities. For example, during the measurement of
the CPU usage for a board, the measurement object is the board.
l
Object type
Type of the physical or logical entity involved in performance measurement, such as
signaling link sets and hardware boards.
Object instance
The objects of the same type are identified by IDs. For example, the front board in slot 1
of subrack 1 is an object instance of hardware boards.
Measurement Object Categories

Based on different operations performed on measurement objects, measurement objects can be
divided into the following categories:
l
Default object
A default measurement object is measured for all object instances. When creating a
measurement task, you need not select the default measurement object manually and also
you cannot deselect it. For example, all boards are selected by default for the CPU Load
Measurement on the CGP. That is, the system obtains objects automatically and adds the
objects to the measurement task.
The default measurement object is applicable to the measurement units that have small
number of measurement objects (no more than 100) but are frequently used.
Global object
The measurement task for a global object is a global measurement in which measurement
objects are not specified. That is, the measurement result is applicable to all the objects.
The global object does not need to be added or deleted during the creation of measurement
tasks. The system automatically obtains the global object and adds it to the measurement
task.
Configuration object
A configuration object is configured on the client before being selected manually during
the creation of a measurement task.
Customized object: An object instance that is not configured before being customized
according to specific requirements during the creation of a measurement task.
1.1.7 Performance Alarm

A value range (upper and lower thresholds) is set for a measurement entity. When the
measurement result of an entity exceeds the thresholds, it indicates that the system operates
abnormally. In this case, the system generates an alarm.
The Performance alarm can notify users of abnormalities to ensure the security of the system.
Performance alarms are classified into two types: threshold alarm and gradient alarm.
l
Threshold alarm:
Thresholds are set for performance measurement entities. When the actual value of an entity
exceeds the thresholds, a threshold alarm is generated.
Issue 02 (2010-03-15)
Gradient alarm:
1-7
HUAWEI CSOFTX3000
Thresholds are set for the change rate of performance measurement entities. When the
actual change rate of an entity exceeds the thresholds, a gradient alarm is generated.
1.2 Overview of Performance Measurement System

Architecture
The CSOFTX3000 PM system is composed of the host, OMU, workstation, and M2000 Server.
1.2.1 Performance Measurement System Architecture
1.2.2 Interactions Between Components
1.2.1 Performance Measurement System Architecture

Figure 1-1 shows the architecture of the performance measurement (PM) system.
Figure 1-1 Architecture of PM system
ME
A piece of network equipment that can be managed through an element manager as part of a
network management system (NMS) is called a managed element. In the PM system, the
performance variables of this managed element are monitored.
The MEs monitor the measurement points of each entity in real time through the performance
measurement process. Whenever the update condition of an entity is satisfied, the ME performs
counting or calculation. During entity monitoring and updating, the ME reports the measurement
data to the OMU periodically.
OMU
The OMU is responsible for the management of devices in the system. The OMU performs the
following functions:
l
1-8
Collects the call detailed records (CDRs), obtains the performance entity, and then saves
the measurement data into the database.
Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
Saves measurement files as binary or .xml format complying with the 3rd Generation
Partnership Project (3GPP) standard, and then sends the files to the access NMS through
the File Transfer Protocol (FTP).
Collects the CDRs, measures the key performance indexes (KPIs) in real time, and then
sends the measurement data to the Web UI.
Serves as a server, receives and processes requests from the Web UI, and returns the
processed result to the Web UI.
NOTE
The KPIs are measured by the OMU in real time to indicate the current status of the network.
Client
The client provides a friendly graphic user interface (GUI) and online help. Through the client,
you can perform the following performance measurement related operations:
l
Configuring MEs
Browsing logs
Checking online user information
Viewing performance alarms
Web UI
The Web UI enables you to issue measurement tasks and view the entity data. Through the Web
UI, you can perform the following operations:
l
Measurement management
Querying statistical data
Managing alarm thresholds
Monitoring
Exporting statistical data
Managing customized entities
Sampling statistical data
1.2.2 Interactions Between Components

Between OMU and Client
The interaction are as follows:
l
Objects of the CSOFTX3000 can be configured through the client.
Alarms generated by the PM module are sent to the client and displayed on the client.
Between Web UI and OMU

l
Issue 02 (2010-03-15)
The navigation tree information of objects can be obtained by the Web UI through the
OMU, such as:
1-9
HUAWEI CSOFTX3000
The list of MEs being measured
The list of measurement object class of an ME
The list of object instances for measurement object class
PM commands can be issued by the Web UI to the OMU, such as:
Command for adding or deleting an object instance
Command for adding or deleting a monitoring task
Command for adding or deleting a customized entity
Command for exporting statistic data
Command for setting the alarm threshold and grads threshold
The performance statistical data on the CSOFTX3000 server can be queried through the
Web UI. The credibility of an entity is measured by judging whether the values of the
entities of an measurement object instance in the measurement period is true. An entity is
deemed incredible in any of the following cases:
In case of time jump, manual adjustment of the system time and (or) time zone, switching
on or off the day light saving time, or discrete time recorded in the CDRs reported by
MEs due to system time jump, the measurement result reported in the first measurement
period after the time transient may be incredible.
The module data is incomplete. In this case, some of the modules do not report CDRs,
or none of the modules reports a CDR.
The module is excessive. In this case, modules unrelated to the current object reports
data of this object.
The granularity period is incomplete. The measurement result in the first granularity
period is incredible, because this period, which begins after a service is started, is not a
complete period.
The OMU returns the real-time KPI data to the Web UI for a real-time measurement task.
Between OMU and Service MEs

The service MEs report the CDRs (Call Detail Records) to the OMU periodically. The OMU
analyzes and processes the received CDRs, obtains the measurement data of each entity, and
then saves the data to the database.
1.3 Classification of Measurement Elements

1.3.1 Classification of Performance Measurement Sets
1.3.2 Classification of Performance Measurement Units
1.3.3 Classification of Performance Measurement Entities
1.3.1 Classification of Performance Measurement Sets

The CSOFTX3000 PM sets are classified as follows:
l
1-10
Bearer Traffic Measurement

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
BSMAP Measurement
Call Connection Procedure Measurement
Call Record
Centrex Traffic Measurement
Combination Condition-Dependent Object Traffic Measurement
Failure Cause Measurement
Global Traffic Measurement
Intelligent Service Measurement
MGW Measurement
MSC Basic Service Traffic Measurement
MSC Internal Operational Status Measurement
MSC Special Service Traffic Measurement
MSCID Traffic Measurement
PDSN Service Measurement
Signaling Procedure Measurement

NOTE
Selecting a Performance Measurement Set:

You can determine the PM set by the attribute of the object. Table 1-4 lists three examples of selecting
PM set.
Table 1-4 How to select PM set
To Measure
Select (PM set)
Outgoing traffic of all subscribers in the office
Total Traffic of the Office
Local office subscriber calling IN subscribers
IN servicess
Duration of signaling link fault
Signaling and Interfaces
In certain cases, one PM activity can be performed by more than one PM task. For instance, to measure
the traffic of a certain office direction, perform the following operations:
l
Select Outgoing Traffic in Trunk Office Directions and Incoming Traffic in Trunk Office
Directions in the set Bearer Traffic.
Select Multi-conditioned Traffic Measurement in the set Call Record.
Select the proper task according to other conditions, such as the demands for the objects and entities.
1.3.2 Classification of Performance Measurement Units

Table 1-5 lists each PM set and its PM units.
Issue 02 (2010-03-15)

1-11
HUAWEI CSOFTX3000
Table 1-5 PM set and its PM units

PM Set
PM Unit
Bearer Traffic
Measurement
Destination Traffic Distribution Measurement Based on Office

Direction
Destination Traffic Measurement
Incoming Office Measurement Based on Office Direction
Incoming Office Traffic Measurement Based on Trunk Group
Outgoing Office Measurement Based on Office Directionn
Outgoing Office Traffic Measurement Based on Trunk Group
Route Overflow Measurement
BSMAP Measurement
Broadcast Paging Measurement

BSC Related Measurement
Location Area Traffic Measurement
Call Connection
Procedure
Measurement
Call Answer Measurement

Call Drop Measurement
Call Proceeding Measurement
MTC Completion Measurement
Call Record
Traffic Dispersion Duration Measurement
Centrex Traffic
Measurement
Centrex Incoming Traffic Measurement

Centrex Internal Traffic Measurement
Centrex Outgoing Traffic Measurement
Combination
Condition-Dependent
Object Traffic
Measurement
Combination Condition-Dependent Object Traffic Measurement
Failure Cause
Measurement
Failure Cause Measurement
Global Traffic
Measurement
CPU Usage Measurement

Incoming Terminating Traffic Measurement
Incoming Traffic Measurement
Intra-office Traffic Measurement
Originating Outgoing Traffic Measurement
Originating Traffic Measurement
1-12

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
PM Set
PM Unit
Originating Outgoing Traffic Measurement
Outgoing Traffic Measurement
Terminating Traffic Measurement
Transit Traffic Measurement
VLR Subscriber Measurement
VLR License-Limited Subscriber Measurement
VoBB Subscriber Originating Traffic Measurement
VoBB Subscriber Terminating Traffic Measurement
Roaming Call Measurement
TLDN Usage Rate Measurement
Special Traffic Measurement
Intelligent Service
Measurement
Fixed-to-IN Traffic Measurement

Intelligent Service Resource Measurement
IN-to-Fixed Traffic Measurement
IN-to-IN Traffic Measurement
IN-to-Mobile Traffic Measurement
Mobile-to-IN Traffic Measurement
SCP Intelligent Trigger Traffic Measurement
Calling WIN Overlay Traffic Measurement
Traffic Distribution and Duration
MGW Measurement
Inter-MGW Path Measurement

Intra-Office Traffic Measurement over TDM Circuit Between
MGW Pair
Intra-Office Traffic Measurement of IP Inter-MGW Media types
Between an MGW Pair
MSC Basic Service

Traffic Measurement
Assignment Procedure Measurement

Assignment Procedure Measurement Based on Service Type
Authentication Service Measurement
BSC Related Handoff Measurement
CREF Measurement 1
Handoff Measurement
Issue 02 (2010-03-15)

1-13
HUAWEI CSOFTX3000
PM Set
PM Unit
Inter-Office Handoff Measurement
Inter-MSC Handoff Failure Measurement
Location Management Service Measurement
Registration Service Measurement
Inter-Office Handoff Measurement Processed by the Agent MSCe
MSC Internal
Operational Status
Measurement
MSC Special Service
Traffic Measurement
Inter-Module Traffic Distribution Measurement

ByPass Measurement
CC Traffic Measurement
Roaming Restriction Based on Cells and Number Segment
Measurement
CFW Service Measurement
CVE Traffic Measurement
CRBT Measurement
CT Traffic Measurement
CT800 Measurement
CW Traffic Measurement
Connect to Specified Number when Auth or GT route Failure
Measurement
End-to-End Voice Privacy Traffic Measurement
EPACA Measurement
Flow Control Service Cut Apex Measurement
Flow Control Traffic Measurement
HLR Message Exchange Measurement
Inside Flow Control Traffic Measurement
InterSystemPage Measurement
InterSystemPage2 Measurement
IP-TDM Rerouting Measurement
Traffic Measurement of the IP QoS Flow Control
IWF Measurement
Location Based Service Measurement
1-14

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
PM Set
PM Unit
Location Updating Flow Control Measurement
LOOPBACK SSP Measurement
MCByPass Measurement
New Number Activation Notification Measurement
OTA Measurement
Rerouting Measurement
Roaming Restriction Based on User Zone Authorized
Measurement
Short Message Service Measurement
SIP Redirection Measurement
Voice Mailbox Notification Measurement
Voice Privacy Measurement
VPDC Measurement
Wireless Call Navigating Measurement
Wireless Number Ported Measurement
MSCID Traffic
Measurement
Incoming Traffic Measurement (MSCID)

Incoming Terminating Traffic Measurement (MSCID)
Intra-office Traffic Measurement (MSCID)
MTC Completion Measurement (MSCID)
Originating Traffic Measurement (MSCID)
Originating Outgoing Traffic Measurement (MSCID)
Outgoing Traffic Measurement (MSCID)
Short Message Service Measurement (MSCID)
Terminating Traffic Measurement (MSCID)
Transit Traffic Measurement (MSCID)
VLR Subscriber Measurement (MSCID)
TLDN Usage Rate Measurement (MSCID)
Signaling Procedure
Measurement
A-Interface Signaling Procedure Error Measurement

CD-Interface Signaling Procedure Measurement
H.248 Global Traffic Measurement
Issue 02 (2010-03-15)

1-15
HUAWEI CSOFTX3000
PM Set
PM Unit
H.248 SCTP Link Measurement
IP Traffic Statistic
IP QoS Measurement Between Two End Stations
ISUP Abnormality Measurement
ISUP Circuit Group Performance Measurement
ISUP Message Measurement
ISUP Message Using Measurement
ISUP Network Performance Measurement
ISUP Node Performance Measurement
IUA Link Set Traffic
IUA Linkset State Traffic Measurement
IUA Signaling Link Traffic
M2PA Link Traffic Measurement
M2UA Link Traffic Measurement
M2UA Link Traffic Measurement
M2UA Linkset Traffic Measurement
M3UA Destination Entity Traffic Measurement
M3UA Destination Entity Traffic
M3UA Linkset Flux Traffic
M3UA Linkset State Traffic Measurement
M3UA Local Entity Traffic Measurement
M3UA Service Indicator Traffic Measurement
M3UA Signaling Link Traffic
MAP Signaling Procedure Error and Timeout Measurement
MAP+ Signaling Procedure Measurement
MGW Message Measurement
H.248 MGW Measurement
H.248 MGW Transaction Measurement
MTP3B DSP Measurement
MTP3B Signaling Link Measurement
1-16

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
PM Set
PM Unit
MTP3B Signaling Linkset Measurement
MTP Destination Signaling Point Traffic Measurement
MTP DSP Traffic
MTP Link Set Traffic
MTP Original Signaling Point Traffic Measurement
MTP Policing Measurement
MTP Service Indicator Traffic Measurement
MTP Signaling Link Traffic Measurement
MTP Signaling Link Traffic
SAAL Link Measurement
SCCP and SUA Total Statistic Measurement
SCCP Performance Statistic
SCCP Quality of Service Traffic Measurement
SCCP Traffic Statistic
SCCP Utilization Statistic
SCTP Load Measure
SCTP Traffic Measurement
SIP Message Measurement
SUA Destination Entity Measurement
SUA Linkset Statistic Measurement
SUA Link Statistic Measurement
SUA Traffic Statistic Measurement
SUA Utilization Statistic Measurement
T-Interface Signaling Procedure Measurement
TCAP Component Utilization Statistic
TCAP Component Sublayer Performance Statistic
TCAP Message Utilization Statistic
TCAP Transaction Sublayer Performance Statistic
TUP Abnormality Measurement
TUP Circuit Group Performance Measurement
Issue 02 (2010-03-15)

1-17
HUAWEI CSOFTX3000
PM Set
PM Unit
TUP Message Usage Measurement
TUP Network Performance Measurement
TUP Node Performance Measurement
PDSN Service
Measurement
PDSN Traffic Measurement
NOTE
Refer to the online Help for the meaning of PM entity and standard PM point.
1.3.3 Classification of Performance Measurement Entities

The performance measurement entities can be classified based on the counter types, object
attributes, and measurement purposes.
A performance measurement (PM) task includes the following three elements:
l
PM object
PM entity
PM time
The three elements determine a unique PM task. The task is the basic management unit of the
performance system. It should include one or more sets, units, entities, objects, and time of the
PM.
The PM entity is one of the three elements in any PM model. It is a value that must be collected
for a specific purpose, such as the traffic, call times, MOC connection times, and trunk outgoing
call occupancy times.
NOTE
Selecting a Performance Measurement Entity:

To focus on specific items, select the ones you need in the output report. If you select too many entities,
the report will lose its focus. For instance, a signaling and interface PM task focuses on the fault duration
of the signaling link. Therefore, the following should be included in the selected static entities:
l
Signaling link unavailable duration
Signaling link fault duration
Apart from the available static entities that can be selected, you can also select customized PM entities.
For details on how to customize PM entities.
The PM entities can be classified into the following types based on counter types:
1-18
Count
Traffic
Duration
Device number
Occurrence
Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
PM entities can be of different PM objects. Based on the attributes of the different objects
involved, the entities are classified as follows:
l
Fixed PM entities
Semi-fixed PM entities
Task-matched PM entities
Dynamic PM entities
Count-based Performance Measurement Entities

This type of PM entity is defined in the form of "number of xxx or xxx times". When an event
related to this entity occurs, one of the entities will be added or subtracted.
For instance:
l
PM unit: Originating Outgoing Traffic Measurement
PM entity: Call Attempts (ORGOEX)
Standard flow PM point: The PM starts when the MSCe determines the call is an outgoing
call after it receives a CM Service Request message/INVITE or an Additional Service
Request message and analyzes the called number.
The PM entity specifies the count of times local subscribers originate outgoing calls.
Traffic-volume-based Performance Measurement Entities

Traffic volume is the collection of instant traffic during a specified period.
For instance:
l
PM unit: Originating Outgoing Traffic Measurement
PM entity: Answered Traffic (ORGOEX)
Standard flow PM point: The traffic of a call is measured from called parties answering
calls to call release.
This PM entity indicates the outgoing calls originated by local subscribers from called parties
answering calls to call release.
Duration-based Performance Measurement Entities

This type of PM entity is used to measure the duration of a certain event, such as the session
duration and equipment congestion duration.
The two ways to measure the duration-Based PM entities are as follows:
l
Calculate them by scanning, for instance:

PM unit: M3UA Signaling Link Traffic Measurement
PM entity: Unavailable Duration
Standard flow PM point: The PM starts when the M3UA link becomes unavailable, and
stops when the M3UA link is restored to normal.
Calculate the average duration of a certain event through other entities, for instance:
PM unit: Internal TDM selection between MGW
PM entity: Average seizure duration
Issue 02 (2010-03-15)

1-19
HUAWEI CSOFTX3000
Standard flow PM point: It is calculated on the OMU.

Average Seizure Duration = (Direct Path Seizure Traffic + Bypass Path Seizure Traffic) x
Sampling period/Call seizures
Call seizures = Direct Path Seizure Times + Bypass Path Seizure Times
Device-number-based Performance Measurement Entities

This type of PM entity is used to measure the number of installed devices, available devices,
and blocked devices. The purpose of this PM is to check the installation and maintenance states
of a certain type of device. You can query the task result at the end of the period.
For instance:
l
PM unit: Office Direction Outgoing Calls
PM entity: Avail Bothway Circuit Num
Standard flow PM point: This entity is processed by the MSC internally. The system
calculates circuit numbers at the end of a PM period.
The PM entity indicates the average number (integer) of available circuits in the bi-directional
incoming trunk circuit in the office direction in the period (Integer).
Occurrence-based Performance Measurement Entities

This PM entity is measured by recording the absolute occurrence time of a certain event, resulting
in an output in the format of "xxxx (year) xx (month) xx (day) xx (hour) xx (minute) xx (second)
[xx (millisecond)]".
This type of PM entities are included in the PM units such as CPU Usage. The PM entities take
the form of "xxx time".
For instance:
l
PM unit: CPU Seizure Ratio Traffic
PM entity: Peak Seizure Time
Standard flow PM point: The seizure peak occurs.
The PM entity indicates the initial peak time in the PM period.
Fixed Performance Measurement Entities

They are the PM entities whose storage space is fixedly allocated in the global metering area.
For instance:
l
PM unit: causes of global failure
PM entity: CAUSE025_Times of releases before pick-up
Standard flow PM point: This entity is measured by the MSC when calls are disconnected.
Disconnection messages with unknown causes are received when callees hear ringing but have
not answered the calls, or disconnection cause values of normal call clearing from callers are
received.
For fixed PM entities, there is only one object.
1-20

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
Semi-Fixed Performance Measurement Entities

These are PM entities whose storage space is required to be allocated according to the data
configured in the global metering area.
For instance:
l
PM unit: Office Direction Outgoing Calls
PM entity: Bid Times
Standard flow PM point: For the radio access network (RAN), the callee sends RAB
ASSIGN REQ or BSSMAP ASSIGN REQ. Multiple times of PM are required for multiple
connections. For the trunk, the SETUP message is received from CCB.
For the RAN, the PM entity indicates the number of assignments sent to the RAN based on the
office direction, after the local mobile subscriber receives a call. For the trunk, the PM entity
indicates the number of outgoing call attempts on the circuit in the observed office direction.
In general, semi-permanent PM objects are unique. It is feasible to allocate global storage space
by maximum configuration.
Task-Matched Performance Measurement Entities

Their storage space is allocated according to the PM task in the global metering area. When you
create a task of task-matched PM entity, the result area is used as a counter area. Therefore, in
general, the counter for this type of entities does not exist.
For instance:
l
PM unit: Traffic Distribution by Office Destinations
PM entity: Call Connected Times
Standard flow PM point: The MSC receives the ACM message from the peer office.
The PM entity indicates the connection times of the call in the office direction and to the
destination.
The PM involves such objects as "Destination" and "Office direction No". If the storage space
is allocated by the combination of destination, office direction No. and PM entity, then the
required size of storage space should be large. As for this type of PM entities, storage space is
allocated only when required.
Dynamic Performance Measurement Entities

During initiation, the system assigns a public storage space to all dynamic PM entities as a
counter area regardless of whether the corresponding tasks are created. Similar to task-matched
PM entities, the system applies for a temporary counter area for the object of the dynamic PM
entities in the public counter area only when the corresponding tasks are created. This temporary
counter area is released after the tasks are completed. During initialization, the system does not
assign a public counter area to the task-matched PM entities. The system dynamically assigns a
result storage area for the task-matched PM entities and uses it as a counter area only when the
corresponding tasks are created.
For instance:
l
Issue 02 (2010-03-15)
PM unit: H.248 MGW Basic Measurement

1-21
1-22
HUAWEI CSOFTX3000
PM entity: Unavailable Duration of MGW
Standard flow PM point: from the time the MGW fails to the time the MGW recovers

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
2 System Function
System Function
About This Chapter

2.1 Measurement Management
2.2 Querying Measurement Result
2.3 Exporting Measurement Result
2.4 Threshold Alarm
2.5 Customizing Entity
Issue 02 (2010-03-15)

2-1
HUAWEI CSOFTX3000
2 System Function
2.1 Measurement Management

Measurement management provides function of creating, modifying, and deleting a
measurement task as well as querying detailed information about a measurement task.
The performance management system supports a maximum of 200 measurement tasks. You can
select a system-defined measurement period. Measurement entities are classified by
measurement unit, thus, facilitating the management and maintenance.
The system provide an automatic measurement function for certain frequently-used
measurement units. That is, the measurement units automatically start measurement tasks after
the OMU is installed and started. If the icon before the measurement unit is bright, it indicates
that the measurement unit has active measurement task; if it is a gray icon, it indicates that there
is no running measurement task. The measurement units that support automatic measurement
are provided by the equipment manufacturer.
CAUTION
When a performance measurement task is created, the system collects and exports measurement
data, which occupies system resources. Meanwhile, implementation of excessive measurement
tasks concurrently affects the efficiency of the service processing. Thus, you need to pay
attention to the following points when creating measurement tasks.
l
Delete the tasks that are not required timely.
Export the measurement results from the OMU timely in the case that the measurement results
are overwritten 60 days after being generated.
The recommended measurement period is one hour.
2.2 Querying Measurement Result

You can timely query measurement results through the performance management system.
The query of measurement results supports the following functions:
l
The measurement results can be queried by object, entity, and period.
The measurement results can be displayed by different sequences.
The queried results can be displayed in a broken line chart and bar chart, which offers an
easy-to-use, clear, and effective performance measurement report.
The queried results can be saved as a .xls, .txt, or .csv file to a local terminal to analyse.
2.3 Exporting Measurement Result

You can export measurement results through the performance management system for further
analysis.
The system can export measurement results in the following modes:
l
2-2
Real-time mode
Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
2 System Function
The system exports the generated measurement results and displays the results in a .xls file
for query.
l
Scheduled mode
You can create an exporting task to have the system export the measurement results that
are generated in a period.
For example, you can create a scheduled exporting task to export the measurement results
of the CPU Load Measurement generated between 10:00 to 12:00 every day. In this case,
you can directly view the measurement results in the specified directory.
2.4 Threshold Alarm

To facilitate system maintenance, the performance management system provides the threshold
alarm function to help users monitor network running status and detect unreasonable
measurement results.
You can set the thresholds for a specific measurement entity of a measurement task. When the
measurement result of the entity exceeds the thresholds, the performance management system
generates a threshold alarm to the alarm system. Then users can analyze the abnormalities of
measurement results based on the threshold alarm information and then clear the alarm.
Threshold alarm management supports the following functions:
l
You can set thresholds as well as query, modify and delete the thresholds.
Users can view the threshold alarms on the alarm system.
When the measurement task is deactivated, or the measurement object is deleted, or the
result of an measurement entity measured in the next measurement period does not exceed
the threshold, the alarms on the alarm system are deleted automatically.
2.5 Customizing Entity

The performance management system provides the function of customizing entity for users to
collect the measurement data according to the actual requirement and to flexibly observe the
running status of the network. You can customize an entity by calculating the entities of the
same measurement units using the arithmetic of addition, subtraction, multiplication, and
division.
Customized entity management provides the following functions:
l
You can customize a measurement entity, modify, and delete a customized entity.
After an entity is customized, the related measurement tasks make statistics of the
customized entity. You can query and export the measurement results of the customized
entity.
The customized entity has the following limitations:

l
An original entity can be used to customize an entity. A customized entity, however, cannot
be used to customize other entities.
The original entities that are used to customize an entity must belong to the same
measurement unit.
Issue 02 (2010-03-15)

2-3
HUAWEI CSOFTX3000
3 Applications of Performance Measurement
Applications of Performance Measurement
About This Chapter

3.1 Routine Maintenance
3.2 Performance Monitoring
3.3 Network Optimization
3.4 Analysis Methods of Performance Measurement Results
Issue 02 (2010-03-15)

3-1
HUAWEI CSOFTX3000
3.1 Routine Maintenance

Routine maintenance includes troubleshooting based on PM results and checking running
conditions of all devices.
At present, more and various devices are running on the network; therefore, the routine
maintenance (RM) of the devices becomes more difficult. The CSOFTX3000 PM system
provides RM functions with a variety of counters and an efficient management of data analysis.
3.1.1 Troubleshooting with Performance Measurement Results
3.1.2 Checking Running Conditions of All Devices
3.1.1 Troubleshooting with Performance Measurement Results

Analyzing the Cause
By registering the PM unit Global Call Failure Causes, you can obtain the causes of all call
failures. Based on the PM of the fault causes, you can know the general causes of the call failures.
You can analyze and locate the problem by implementing relevant PM tasks.
NOTE
The global failure cause measurement is the PM of the cause values of calls released before answered. For
calls released after the conversation ends, the fault cause value is not measured.
Locating Failure Cause with Performance Measurement Tasks

The call failure information obtained from the measurement of Global Call Failure Causes is
not clear enough. You must implement a detailed PM based on the measurement units such as
Call Connection Traffic, Traffic Distribution by Office Destinations, Office Direction Outgoing
Office Traffic, and Office Direction Incoming Office Traffic to obtain further information such
as:
l
Location of the call that causes the failure.
The direction in which the calls frequently fail.
On which equipment the failure occurs most.
The types of calls that frequently fail
Call Connection Traffic helps to obtain the connection information and failure cause for the call
connection types such as:
l
National Outgoing Call
International Outgoing Call
GSM Originated Call
WCDMA Originated Call
GSM Terminated Call
WCDMA Terminated Call
You can create only one PM task to measure different types of call connections respectively.
Destination Code Traffic provides you with the information of the calls to a certain office
direction. You can use one PM task to measure the destination numbers of an office direction.
3-2

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
The destination is the number of a certain prefix in the call number analysis table, which is set
by running ADD CNACLD. For example, set the number of prefix 010 as 0, and 0 is called a
destination.
Office Direction Outgoing Office Traffic and the Office Direction Incoming Office Traffic help
to obtain the call situation and the failure cause for the incoming and outgoing calls through a
certain trunk group. One PM task is required to measure the incoming and outgoing traffic of
each office direction and the call loss due to faulty trunk.
Destination Code Traffic helps to obtain the call situation and failure cause for calls made from
the local office to a certain destination. By setting the PM task, you can measure the call situation
and failure cause of each prefix. Measuring the destination can help you obtain the connection
situation of a call after the call is transferred many times.
Finding the Final Cause with Multi-conditioned Traffic Measurement

With the PM unit Multi-conditioned Traffic Measurement, you can observe the behavior of
subscribers or incoming calls once the factors that affect the call completion rate are related to
certain subscribers. It records the dialed number and attributes of each call made by a specific
subscriber. You can analyze the records after a day's PM, or view them after a PM period.
Measuring Signaling Globally to Detect Hidden Problems

You can use a certain PM entity, and the maintenance and command logs to find the hidden
problems.
l
Use Signaling and Interfaces to measure the MTP, TUP, ISUP and TCAP.
Use the periodical PM to find out the time and occurrence number of certain faults that are
not repeated, and to analyze the cause.
3.1.2 Checking Running Conditions of All Devices

Although it is impossible to determine the running conditions of the equipment through the PM,
you can detect the faults in the equipment by viewing the PM result, especially the call loss
causes related with the equipment, such as call loss caused by switch equipment congestion.
This way, you can detect and rectify the errors in time.
You can create a failure cause measurement PM task in the following ways:
l
Select Failure Cause Measurement as the PM unit
Configure other information as required
After the task is complete, check the output report for the entity values. This way you can obtain
the running condition of the equipment.
3.2 Performance Monitoring

This section describes the performance monitoring, including obtaining incoming and outgoing
office traffic information, learning tandem traffic information, and measuring failure causes.
Performance monitoring provides the following functions:
l
Issue 02 (2010-03-15)
Detects the bottleneck of the network load.

3-3

l
Improves the QoS.
Finds the potential of the equipment.
HUAWEI CSOFTX3000
3.2.1 Obtaining Incoming and Outgoing Office Traffic Information

3.2.2 Obtaining Tandem Traffic Information
3.2.3 Measuring Failure Causes for the Entire MSC
3.2.4 Measuring Calls to a Destination
3.2.5 Measuring Traffic in an Office Direction
3.2.1 Obtaining Incoming and Outgoing Office Traffic Information

The ratio of intra-office traffic to outgoing or incoming traffic determines the trunk group
configuration type of the local office. If the outgoing and incoming traffic takes a large
proportion, more outgoing and incoming trunks should be configured accordingly in the local
office.
To obtain the information on the incoming and outgoing traffic, do as follows:
1.
2.
Register one Total Traffic of the Office tasks for the outgoing traffic, and one for the
incoming traffic.
l
PM units: Outgoing Office Traffic and Incoming Office Traffic
Output items: Call Attempts (or seizures) and Calls Connected (Calls Answered)
Set other information as required.

When the task is complete, check the output report to obtain the traffic information on the
subscriber.
3.2.2 Obtaining Tandem Traffic Information

The tandem information can be reflected by the tandem traffic in the tandem office. In the
CSOFTX3000 PM system, the tandem traffic can be measured in two ways:
l
Selecting Transit Calls as the PM unit, and setting the other information as required.
Selecting Call Connection Traffic as the PM unit and Transfer Traffic as the PM object,
and setting the other information as required.
After the task is complete, check the output report to obtain the information on the tandem office.
3.2.3 Measuring Failure Causes for the Entire MSC

It is essential to measure the failure cause of the entire MSC. The PM results help you maintain
and manage the MSC. In the CSOFTX3000 PM system, you can measure the failure cause in
the following way:
l
Select Failure Cause Measurement as the PM unit.
Select the output of all entities by default.
Set the other information as required.
After the task is complete, check the output report to determine the failure cause of the entire
switch.
3-4

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
3.2.4 Measuring Calls to a Destination

In the CSOFTX3000 PM system, you can measure the calls by selecting three different PM
units:
l
Destination Code Traffic

Fill in Destination and Office Direction No. as the PM objects and set the other information
as required. When the task is complete, check the output report to obtain the information
on the traffic to the destination.
Traffic Distribution by Office Destinations

Type a specific destination code as the PM object and set the other information as required.
When the task is complete, check the output report to obtain the information on the traffic.
Multi-conditioned Traffic Measurement

Select Called number under Restriction Condition. Select the called number of a specific
destination as the PM object under Called number and set the other information as required.
When the task is complete, check the output report to obtain the information on the traffic
to a certain called number.
3.2.5 Measuring Traffic in an Office Direction

The traffic in a certain office direction can be measured using the following methods:
l
Bearer traffic office direction PM

Select Outgoing Traffic in Trunk Office Directions and Incoming Traffic in Trunk Office
Directions as the PM units, select the office direction to be measured, and set other
information as required. After the task is complete, combine the output reports to obtain
the information on the traffic of the office direction.
Multi-conditioned PM
Select Multi-conditioned Traffic Measurement as the PM unit, select the office direction
(incoming or outgoing) as the PM object, and set other information as required. After the
task is complete, combine all the output reports to obtain the information on the traffic of
the office direction.
3.3 Network Optimization

This section describes the network optimization, including analyzing traffic, balancing traffic,
and analyzing the call completion rate based on performance measurement.
In the routine operation of the switch, network optimization is an important maintenance job,
which involves the following:
l
Trunk circuit adjustment
Signaling link adjustment
Observation of various call completion rates
Observation of service seizure information
The PM of various operation entities such as traffic and load of the office and its surrounding
telephony network, provides traffic data reference for the following:
Issue 02 (2010-03-15)

3-5

l
Network planning
Network running
Network measurement
Network management
HUAWEI CSOFTX3000
You can enhance the performance of the network by allocating resources properly based on these
traffic data.
3.3.1 Analyzing Traffic Based on Performance Measurement Results
3.3.2 Balancing Traffic with Performance Measurement Results
3.3.3 Analyzing Connection Rate with Performance Measurement
3.3.4 Methods of Improving Call Completion Rate
3.3.1 Analyzing Traffic Based on Performance Measurement

Results
"Busy" means that the number of calls or the traffic is large. More number of calls leads to the
increase of CPU occupancy, but does not have much impact on the call completion rate. The
traffic reflects the resource seizure rate. According to the Erlang formula (A=s), when the traffic
is high there is a significant call loss.
NOTE
A stands for the traffic of the call source.
stands for the average number of calls in one unit.
S is the average seizure duration.
Therefore, the PM and monitoring of the traffic of each critical resource, such as a trunk, is the
precondition for analyzing the busy traffic.
The PM sets used to observe the global traffic or the traffic of each component include:
l
Total Traffic of the Office
Bearer Traffic
Global H.248 measurement
These PM sets help you to obtain the performance data of different resources. When the traffic
of a certain resource exceeds the threshold of the convergent ratio, you must rebalance it. For
example, if there are too many people accessing the network and there are many long-duration
calls in a certain cell, the traffic is too heavy, and the call loss could be high. In this case, the
expansion of the capacity is recommended.
The traffic is often distributed unevenly because the data is not set properly. Thus, certain
resources of the MSC are heavily occupied, or heavy traffic occurs during certain time such as
holidays. In this case, you must take corresponding measures based on the PM data.
NOTE
The call loss (ratio) is the ratio of the number of call failures to the total number of calls.
3.3.2 Balancing Traffic with Performance Measurement Results

3-6

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
During the data configuration, there are two types of balancing methods:
l
Static
Dynamic
"Static" is a forecast method used to balance the traffic. You can distribute the traffic load in
average to each resource, and can calculate the expected variation. "Dynamic" is a feedback
method used to balance the traffic. You can focus on the effectiveness of traffic balancing, and
optimization of data configuration. When configuring the data, you cannot predict the number
of subscribers or the number ranges with heavy traffic. You can detect the data that is improperly
configured through the PM.
CPU Seizure Ratio Traffic reflects the traffic of each module. By comparing the traffic of the
modules, you can find the module with the most or least traffic, and accordingly take measures.
Traffic Distribution by Office Destinations helps you to recognize the traffic to an office
direction and a destination code.
Incoming Calls in Mobile Office Directions, Outgoing Calls in Mobile Office Directions,
Incoming Traffic in Trunk Office Directions, and Outgoing Traffic in Trunk Office Directions
measure the traffic based on office directions. You can find out whether traffic is heavy in an
office direction or on a trunk and whether congestion lasts for a long time by analyzing the PM
data.
Traffic balancing means to utilize the resources thoroughly. For the office with small capacity
or in the case of heavy traffic, it can increase the call completion rate greatly.
3.3.3 Analyzing Connection Rate with Performance Measurement

The call completion rate is a great concern of subscribers. Usually, it is affected by the factors
specified in Table 3-1
Table 3-1 Description of factors that affect call completion rate
Issue 02 (2010-03-15)
Factor
Description
Unusually Busy Subscribers
It is the direct and fundamental factor that

causes the low rate in end offices.
Excessive message flow between modules
It results in insufficient network resource. It

is caused by the improper arrangement of the
trunk circuits and signaling links.
Significant differences in the circuit utilization

rates of different trunk groups in an office
direction
None
Call loss due to unallocated or incorrect

number
It is required that the senior office should

define the prefix of each end office in detail.
Otherwise, the call loss of unallocated or
wrong numbers occurs to numbers from the
incoming trunk calls because the prefix is
wrong.

3-7
HUAWEI CSOFTX3000

NOTE
During a PM period, it is measured as: call completion rate = number of connections / number of call
attempts x 100%
With the help of various PM tools, you can check whether the call completion rate is affected
by the preceding factors. The PM results provide reference for troubleshooting. The following
means can be used for analysis:
l
Global Call Failure Causes

Obtain the causes of the current faults and the number of faults. Compare them with the
previous data to find out the major cause that leads to the decrease of the call completion
rate.
Incoming Traffic in Trunk Office Directions and Outgoing Traffic in Trunk Office
Directions
Select all the office directions and all the PM entities. Check the fault causes on each office
direction to find out the office direction in which exceptions have occurred.
Multi-conditioned Traffic Measurement

You can find out in which office direction the calls are disconnected, and the causes of the
disconnection.
3.3.4 Methods of Improving Call Completion Rate

Maintaining CSOFTX3000 Regularly
l
Dial test each trunk line regularly. Check the equipment connection for any possible
damage.
Fix the transmission faults and the faults in the peer office.
Analyze SS7 messages to make sure that the signaling links are intact.
Familiarizing with Key Signaling Link Messages

There are several link messages that affects call completion rate. Table 3-2 describes the causes
of message generation.
Table 3-2 Cause of generation of signaling link messages that affect call completion rate
Message Names
Cause of Generation
SEC
Cannot apply for internal resources such as the CCB.

Link is unstable between office directions, and the call is released.
Cannot apply MPTY resources.
3-8
CFL
Cannot connect the call at the MSC. The MSC can only send this
message to represent call connection failure.
LOS
In fixed network, when the called subscriber is not working or faulty,

such as hang-up overtime, the subscriber line is locked. The MSC
returns the LOS when the locked subscriber line is being called.
Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
Message Names
Cause of Generation
For mobile terminated (MT) calls in mobile network, when the called
subscriber cannot be reached due to BSS faulty, the MSC sends the
LOS message.
Configuring Auto Transmission of Caller Number in Certain Types of Calls

For toll calls, automatic paging, and special service number services in which the called party
requests the caller number, you must configure the system to auto send the caller number, in
order to reduce the number of messages sent between offices. Otherwise, there will be GRQ/
GSM messages on the SS7 link, which may increase the burden of the link and the system.
Configuring Prefix Data Properly

When configuring prefix data, you should set the number segments properly. Adjust the
minimum number length of the local office and peer office to avoid the occurrences of
unallocated number, wrong number or routing error.
Assume that only the office number 211 exists in the local network. If you set the prefix to 2,
the calls with the prefix 22 to 29 and 212 to 219 seize the outgoing trunks, which results in call
loss. If the minimum number length is set too short, more SAM and SAO messages are generated,
and the time required to set up a call is longer. In this case, many subscribers release the calls
before call connection is established because their patience is worn out.
Optimizing the Load Among Modules

When configuring trunk and link data in a multi-module system, perform the following
operations:
l
Maintain equal traffic load of each module
Minimize the number of inter-module messages
Keep the speech channel and the preferred link in the same module. The circumstance in which
a module is configured with speech channels but with no links should not occur.
If the call is transferred through the STP, include the speech channel in the module connecting
to the STP. This ensures security between modules, reduces load among modules, and avoids
the transfer of SS7 messages among modules.
In a general networking model, there are two peer tandem exchanges serving as the senior offices
of the integrated GMSC. Therefore, you can include the trunk and signaling links which connect
to the two tandem exchanges into two modules.
When there are two peer LSTPs providing links locally, you can also include the trunk lines in
two modules by office direction. Set the linkset in the module to a certain office direction as the
preferred route for signaling to a certain office direction.
Recommending the Use of SS7 Trunk Circuit

There are several circuit selection modes for SS7 trunk circuit:
l
Issue 02 (2010-03-15)
Maximum
3-9

l
Minimum
Master/slave
Cyclic
HUAWEI CSOFTX3000
Select Master/slave as the preferred selection mode.

When you select the Maximum or the minimum circuit selection mode, if one of the two
interconnected offices starts from the circuit with the minimum CIC (that is, select the minimum
CIC first), the other should start from the circuit with the maximum CIC.
As the SS7 trunk circuit is bi-directional, dual-seizure may occur. Therefore, set each MSC to
control half of all the circuits. When dual-seizure occurs, the slave party releases the occupation,
and the call is re-initiated on another idle circuit. In general, the MSC with greater SPC controls
the circuits of even number CIC, and the other one controls the circuits of odd number CIC.
Balancing the Load Among Links in the Linkset

Set the right link selection mask to balance the load of different links in the same linkset.
Promoting the Use of Supplementary Services

Promote the use of supplementary services to the end users. This reduces influence on call
completion rate by human factors. Try to make them use the CFB. If the end user has multiple
communication tools, such as beeper, mobile phone, the call can be forwarded to voice mailbox
or secretary station if the MS is busy.
Expanding System Capacity

Expand the capacity of the system according to the increase in the number of subscribers and
office directions. The expansion effectively relieves the MSC from the bottleneck and overload
situation.
By analyzing the PM data, you can find the cause of call loss. For instance, when you find that
the traffic in a line is almost one, which means that it is too high, add more trunk resources.
3.4 Analysis Methods of Performance Measurement Results

3.4.1 Overview of the Analysis Methods
3.4.2 Example of Analysis
3.4.1 Overview of the Analysis Methods

Usually, there are four different analysis methods of the performance measurement results,
which are as follows:
Analyzing a Specific Performance Measurement Entity

This type of data analysis can help you to determine whether there is an abrupt change, which
indicates abnormality of the system.
3-10

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
For example, if there is a slump in the Number of Successful Authentication during the same
time segment, it indicates that the authentication processing function of the system could be
faulty.
Comparing Performance Measurement Entities of a Specific Performance

Measurement Unit
This method can help you to determine whether the results of PM entities are normal.
For example, for Call Pre-establishment, Delivery SUCC Rate Mobile To Mobile Setup should
be greater than Delivery SUCC Rate Mobile To Mobile SUCC Setup.
Comparing Performance Measurement Entities of the Same Performance

Measurement Object
This method helps you to determine whether the load sharing between PM objects is proper.
For instance, in MTP signaling link PM, you can find whether the load shared among links is
proper by measuring the load of the links to the same DSP.
Comparing Performance Measurement Entities in the Same Time Segment

This kind of data analysis can determine the problem when different parts work together.
For instance, you can detect errors of the MAP signaling in the location update procedure by
comparing and analyzing PM entities in Location Management service and MAP Standard
Operations.
Long-Term Analysis of Performance Measurement Units

This method helps to determine the long-term status of the network based on the long-term PM
results, for example, the status of the network in a month or quarter. You can obtain better
optimization measures for network performance planning based on the PM results and identify
hidden problems through the analysis of the long-term PM results.
3.4.2 Example of Analysis

Analysis of Signaling Link Load Sharing
l
Background description
There are two link sets with the same priority to the same HLR. Each link set includes two
links.
Test data
For instance, the PM unit is Traffic over MTP Signaling Links. Table 3-3 lists the PM
entity data of the two signaling links of different linksets.
Table 3-3 Link PM data table one
Issue 02 (2010-03-15)
PM Entity
PM Data of Link 0 (in

Link Set 0)

Link Set 1)
Snd Seizure Ratio
0.2

3-11
HUAWEI CSOFTX3000
PM Entity

Link Set 0)

Link Set 1)
Rcv Seizure Ratio
0.3
0.3
Data analysis
Generally, the service load of different signaling links that have the same priority and are
led to the same Destination Signaling Point (DSP) should be equal. The PM data shows
that the ratio of signaling link for transmission of links 0 and 2 is severely disproportional,
while the receiving occupation percentage is basically equal. This indicates that the loadsharing processing during the local-end signaling transmission is faulty.
Handling Method
The load-sharing between the signaling links is implemented through the signaling link set
mask and the signaling link mask. On checking the relevant data configuration, you can
discover that the signaling link set mask and signaling link mask are set to the same bit.
After modifying the data, the load-sharing can be restored to the normal status.
Analysis of Signaling Link Overload

l
There are two signaling links to a certain HLR, namely links 0 and 1.
Test data
For instance, the PM unit is Traffic over MTP Signaling Links. Table 3-4 lists the PM
entity data of the two signaling links to HLR.
Table 3-4 Link PM data table two

PM Entity
PM Data of Link 0
PM Data of Link 1
Snd Seizure Ratio
0.12
0.13
Rcv Seizure Ratio
0.18
0.19
Data analysis
The maximum load of SS7 link is 0.2erl. The performance data PM is made on the data in
one time segment; therefore, if the Ratio of Signaling Link for Receiving is 0.18 or 0.19,
the transient occupation percentage may exceed 0.2. Thus, it may lead to the loss of the
signaling message packets.
Handling method
Add more signaling links to the HLR to increase the success rate of message sending and
receiving.
Measuring Number of VLR Subscribers

l
Count the number of subscribers in the local MSC/VLR.
3-12

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
l
Test data
For instance, the PM unit is Traffic Measurement For VLR Subscriber. Table 3-5 lists the
counting result of local VLR subscribers and roaming VLR subscribers.
Table 3-5 Number of subscribers in the VLR

PM Entity
Result
VLR Subscriber of Local
Over 30,000
VLR Subscriber of Roaming
Over 20,000
Data analysis
In a non-tourism inland city, there cannot be a high percentage of roaming subscribers under
VLR. This may be due to error in the data configuration procedure.
Handling method
Run LST RMUSRTP to check the roaming subscriber type data, and it is found that the
local number segment is incomplete.
Run ADD RMUSRTP to add local number segment information. Measure again the next
day, and it is found that the result is normal.
Issue 02 (2010-03-15)

3-13
HUAWEI CSOFTX3000
4 Common Measurement Tasks
Common Measurement Tasks
About This Chapter

4.1 Frequently Used Performance Measurement Tasks for the End Office
4.2 Frequently Used Performance Measurement Tasks for the Converging Office
4.3 Frequently Used Performance Measurement Tasks for the Gateway Office
Issue 02 (2010-03-15)

4-1
HUAWEI CSOFTX3000
4.1 Frequently Used Performance Measurement Tasks for

the End Office
Table 4-1 PM units in Total Traffic of the end Office
4-2
PM Unit
PM Set
Objective
Registration
Time Segment
PM Period
Originating
Traffic
Measureme
nt
Global Traffic
Measurement
This PM unit
mainly handles the
calls originated by
the MSs of the
local MSC,
regardless of the
attributes of the
called parties. The
PM involves many
processing stages
before the MSC
analyzes the called
numbers and
determines the call
attributes.
07:00 to 22:00
one hour
Incoming
Traffic
Measureme
nt
Global Traffic
Measurement
This PM unit
mainly handles the
calls terminated
by the subscribers
of the local MSC,
regardless of the
attributes of the
caller. The MSC
determines that it
belongs to the
terminating traffic
by analyzing the
called number.
07:00 to 22:00
one hour
Outgoing
Calls
Global Traffic
Measurement
This PM unit
mainly handles the
outgoing traffic
originated by the
subscriber of the
local MSC. The
MSC determines
that the calls are
outgoing calls by
analyzing the
called number.
07:00 to 22:00
one hour

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
Issue 02 (2010-03-15)
PM Unit
PM Set
Objective
Registration
Time Segment
PM Period
Incoming
Calls
Global Traffic
Measurement
This PM unit
mainly handles the
incoming traffic in
this office
direction. The
MSC determines
that the calls are
incoming calls by
analyzing the
called number.
07:00 to 22:00
one hour
Originating
Outgoing
Traffic
Measureme
nt
Global Traffic
Measurement
This PM unit
mainly handles the
outgoing traffic
originated by the
subscriber of the
local MSC. The
MSC analyzes the
called number and
determines that it
is outgoing traffic.
07:00 to 22:00
one hour
Incoming
Terminating
Traffic
Measureme
nt
Global Traffic
Measurement
This PM unit
mainly handles the
traffic in this
office direction.
The MSC
determines that
the calls are
incoming
terminating calls
by analyzing the
called numbers.
07:00 to 22:00
one hour
Intra-MSC
Calls
Measureme
nt
Global Traffic
Measurement
This PM unit
mainly handles
traffic processing
in this office
direction, that is,
the traffic of calls
between mobile
subscribers in the
local office.
07:00 to 22:00
one hour

4-3
HUAWEI CSOFTX3000
4-4
PM Unit
PM Set
Objective
Registration
Time Segment
PM Period
Transit
Traffic
Measureme
nt
Global Traffic
Measurement
This PM unit
mainly handles the
traffic in this
office direction,
that is, the traffic
of incoming trunk
calls transferred
by the MSC
through outgoing
trunks.
07:00 to 22:00
one hour
Failure
Cause
Measureme
nt
Failure Cause
Measurement
This PM unit
focuses on the call
release due to a
certain cause.
00:00 to 24:00
one hour
Traffic
Dispersion
Duration
Measureme
nt
Call Record
The PM object can

be a traffic flow
defined by the
following
conditions:
00:00 to 24:00
one hour
Caller number
Incoming office
direction
Outgoing office
direction
Called number
Call type

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
Issue 02 (2010-03-15)
PM Unit
PM Set
Objective
Registration
Time Segment
PM Period
Destination
Traffic
Measureme
nt
Bearer Traffic
Measurement
This PM unit
supports the
following
functions:
07:00 to 22:00
one hour
Focuses on the
traffic of a
specific
destination
code
Used as
reference data
for network
management
and
maintenance
Helps
subscribers
understand the
reason for low
completion rate
of the
destination
code
Improves the
network
management
and control
capability to
efficiently
utilize the
network
resources when
the network is
congested
Call Answer Call Connection

Measureme Procedure
nt
Measurement
This PM unit
focuses on the
answer
information of
calls in the entire
MSC.
00:00 to 24:00
one hour
Call Drop
Measureme
nt
This PM unit
focuses on the
drop information
of calls in the
entire MSC.
00:00 to 24:00
one hour
Call Connection
Procedure
Measurement

4-5
HUAWEI CSOFTX3000
4-6
PM Unit
PM Set
Objective
Registration
Time Segment
PM Period
CPU Usage
Measureme
nt
Global Traffic
Measurement
This PM unit
focuses on items
such as CPU usage
and congestion in
service modules. It
is designed for
CCU, CSU, and
SGU.
00:00 to 24:00
one hour
VLR
Subscriber
Measureme
nt
Global Traffic
Measurement
This PM unit
focuses on the
number of
different types of
subscribers in the
local MSC.
00:00 to 24:00
one hour
Inter-Office
Handoff
Measureme
nt
MSC Basic
Service Traffic
Measurement
This PM unit
focuses on the
handover
information of the
local MSC.
00:00 to 24:00
one hour
Assignment
Procedure
Measureme
nt
MSC Basic
Service Traffic
Measurement
This PM unit
focuses on the
assignment
processing on the
MSCe.
00:00 to 24:00
one hour
Location
Managemen
t Service
Measureme
nt
MSC Basic
Service Traffic
Measurement
This PM unit
focuses on the
location update of
a specific LAI.
00:00 to 24:00
one hour
MTP
Signaling
Link Traffic
Measureme
nt
Signaling
Procedure
Measurement
This PM unit
focuses on the
working
information of an
MTP link.
00:00 to 24:00
one hour
H.248
MGW
Measureme
nt
Signaling
Procedure
Measurement
This PM unit
focuses on the sent
and received
messages,
encoded and
decoded
messages, and
security applied
messages on a
media gateway
(MGW).
00:00 to 24:00
one hour
You are
recommended
to register
another task
with a period
of 30 minutes.

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000

the Converging Office
Table 4-2 PM units in Total Traffic of the Office
Issue 02 (2010-03-15)
PM Unit
PM set
Objective
Registration
Time Segment
PM Period
Destination
Traffic
Measureme
nt
Bearer Traffic
Measurement
This PM unit
supports the
following
functions:
07:00 to 22:00
one hour
Focuses on the
traffic of a
specific
destination
code
Used as
reference data
for network
management
and
maintenance
Helps
subscribers
know the
reason for low
completion
rate of the
destination
code
Improves the
network
management
and control
capability to
efficiently
utilize the
network
resources
when the
network is
congested

4-7
HUAWEI CSOFTX3000
4-8
PM Unit
PM set
Objective
Registration
Time Segment
PM Period
Destination
Traffic
Distribution
Measureme
nt Based on
Office
Direction
Bearer Traffic
Measurement
This PM unit
focuses on the
traffic from an
office direction
to a certain
destination code.
00:00 to 24:00
one hour
Outgoing
Office
Measureme
nt Based on
Office
Directionn
Bearer Traffic
Measurement
This PM unit
supports the
following
functions:
00:00 to 24:00
one hour
Focuses on the
traffic of calls
carried on the
outgoing
circuit of each
office
direction, and
the running
status of the
circuits
Provides
reference for
network
maintenance
and
management

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
PM Unit
PM set
Objective
Registration
Time Segment
PM Period
Incoming
Office
Measureme
nt Based on
Office
Direction
Bearer Traffic
Measurement
This PM unit
supports the
following
functions:
00:00 to 24:00
one hour
00:00 to 24:00
one hour
Outgoing
Office
Traffic
Measureme
nt Based on
Trunk
Group
Issue 02 (2010-03-15)
Bearer Traffic
Measurement
Focuses on the
traffic of calls
carried on the
incoming
circuit of each
office
direction, and
the running
status of the
circuits
Provides
reference for
network
maintenance
and
management
Traces calls
from the peer
office to the
local office,
that is, trace
the entire
process of a
call with the
cooperation of
multiple
offices
This PM unit
focuses on the
traffic carried by
the outgoing
trunk circuit in
each trunk group
(including bidirectional), and
the installation
and operation of
the trunk circuit
in each office
direction
(including bidirectional).

4-9
HUAWEI CSOFTX3000
4-10
PM Unit
PM set
Objective
Registration
Time Segment
PM Period
Incoming
Office
Traffic
Measureme
nt Based on
Trunk
Group
Bearer Traffic
Measurement
This PM unit
focuses on the
traffic carried by
the incoming
trunk circuit in
each trunk group
(including bidirectional), and
the installation
and operation of
the trunk circuit
in each office
direction
(including bidirectional).
00:00 to 24:00
one hour
Transit
Traffic
Measureme
nt (MSCID)
MSCID Traffic
Measurement
This PM unit
mainly handles
the traffic in this
office direction,
that is, the traffic
of trunk
incoming calls
transferred by the
office through
outgoing trunks.
07:00 to 22:00
one hour
Failure
Cause
Measureme
nt
Failure Cause
Measurement
This PM unit
mainly handles
the call
disconnections in
the entire MSC
and monitors the
abnormal
disconnections.
00:00 to 24:00
one hour

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
PM Unit
PM set
Objective
Registration
Time Segment
PM Period
Traffic
Dispersion
Duration
Measureme
nt
Call Record
The PM object
can be a traffic
flow defined by
the following
conditions:
00:00 to 24:00
one hour
Caller number
Incoming
office
direction
Outgoing
office
direction
Called number
segment
Call attributes

the Gateway Office
Table 4-3 Frequently used performance measurement tasks for the gateway office
Issue 02 (2010-03-15)
PM Unit
PM Set
Objective
Registration
Time
Segment
PM Period
CPU Usage
Measurement
Global Traffic
Measurement
This
performance
unit collects
data about CPU
usages of all
service
modules, for
example, the
CCU and BSG.
00:00-24:00
One hour

You are advised

to register one
more task with a
measurement
period of 30
minutes.
4-11
HUAWEI CSOFTX3000
4-12
PM Unit
PM Set
Objective
Registration
Time
Segment
PM Period
Incoming Traffic
Measurement
Global Traffic
Measurement
This PM unit
collects data
about
processing of
incoming
traffic, for
example,
Incomplete
Dialing Times,
Seizure Times,
Call
Completion
Times, and
Answer Times.
The
CSOFTX3000
determines
whether calls
from trunks are
incoming calls
through
analysis.
00:00-24:00
One hour
Originating
Traffic
Measurement
Global Traffic
Measurement
This PM unit
collects data
about
processing of
outgoing traffic,
for example,
Answer Times,
Seizure Times,
Address
Incomplete
Times, and
Address Invalid
Times. The
CSOFTX3000
judges whether
calls are
outgoing calls
through
analysis of
called numbers.
00:00-24:00
One hour

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
Issue 02 (2010-03-15)
PM Unit
PM Set
Objective
Registration
Time
Segment
PM Period
MAP+ Signaling
Procedure
Measurement
Signaling
Procedure
Measurement
This PM unit
collects data
about MAP
standard
operations
between NEs
using MAP as
the interface
signaling. It
mainly collects
data about user
error types
carried in MAP
standard
operations.
00:00-24:00
One hour
Incoming Office
Traffic
Measurement
Based on Trunk
Group
Bearer Traffic
Measurement
This PM unit
collects data
about the status
of and traffic
over all
incoming trunk
circuits in the
specified trunk
office direction.
00:00-24:00
One hour
Outgoing Office
Traffic
Measurement
Based on Trunk
Group
Bearer Traffic
Measurement
This PM unit
collects data
about the status
of and traffic
over all
outgoing trunk
circuits in the
specified trunk
office direction.
00:00-24:00
One hour

4-13
HUAWEI CSOFTX3000
4-14
PM Unit
PM Set
Objective
Incoming Office
Measurement
Based on Office
Direction
Bearer Traffic
Measurement
This PM unit
00:00-24:00
collects data
about the status
of and traffic
over all
incoming
circuits in each
mobile office
direction. It
provides
reference data
for maintenance
and network
management.
All incoming
calls are traced
in detail.
One hour
Outgoing Office
Measurement
Based on Office
Directionn
Bearer Traffic
Measurement
This PM unit
00:00-24:00
collects data
about the status
of and traffic
over all
outgoing
circuits in each
mobile office
direction. It
provides
reference data
for maintenance
and network
management.
One hour

Registration
Time
Segment
PM Period
Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
Issue 02 (2010-03-15)
PM Unit
PM Set
Objective
Registration
Time
Segment
PM Period
H.248 Global
Traffic
Measurement
Signaling
Procedure
Measurement
This PM unit
collects data
about H.248
messages
received from
or sent to the
specified MGW
controlled by
the local MSC,
for example,
Unavailable
Times,
Unavailable
Duration,
Number of Sent
Messages, and
Bytes of Sent
Messages.
00:00-24:00
One hour
MTP Signaling
Link Traffic
Measurement
Signaling
Procedure
Measurement
This PM unit
collects data
about MTP
links.
00:00-24:00
One hour
M3UA Signaling
Link Traffic
Signaling
Procedure
Measurement
This PM unit
collects data
about M3UA
links.
00:00-24:00
One hour

4-15
HUAWEI CSOFTX3000
4-16
PM Unit
PM Set
Objective
Registration
Time
Segment
PM Period
IP Traffic
Statistic
Signaling
Procedure
Measurement
This PM unit
collects data
about forward
traffic of the
IFM, traffic of
various service
applications
(such as
M3UA), and
bandwidth
usage. It
provides
reference data
for data
configuration,
traffic analysis,
and status
analysis of the
communication
between the
IFM and the IP
network.
00:00-24:00
One hour
H.248 MGW
Measurement
Signaling
Procedure
Measurement
This PM unit
collects data
about
transaction-type
H.248 messages
transmitted
between the
MSC and a
certain MGW.
00:00-24:00
One hour

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
5 KPI System
KPI System
About This Chapter

The key performance indexes (KPIs) are used to reflect the quality of service (QoS) of the
network and the performance of the equipment on the network.
The KPI system is formulated to help maintenance engineers:
l
Understand the performance measurement system for communication equipment.
Establish performance evaluation systems.
Optimize the services and equipment based on the performance measurement results.
NOTE
This section only provides general reference to the description and calculation formula of KPIs. The KPIs
about a certain network can be specified based on actual conditions.
5.1 Basic Telecom Service-Specific KPI

5.2 Mobility Management-Specific KPI
5.3 Service-Specific KPI
5.4 Authentication
Issue 02 (2010-03-15)

5-1
HUAWEI CSOFTX3000
5 KPI System
5.1 Basic Telecom Service-Specific KPI

The basic telecom service-specific KPI reflects the quality of the procedures vital to the
successful implementation of the basic telecom services, such as the assignment procedure,
paging procedure, and connection procedure.
Table 5-1 The name and description of KPI
Name
Description
Assignment Success Ratio
It is used to evaluate the assignment

procedure on the radio access network
(RAN).
Paging Success Ratio
It is used to evaluate the environment of the

RAN.
Call Completion Ratio
It is used to evaluate the call connection on

the switching network.
Call Answer Ratio
It is used to evaluate the call answer rate.
Answered Traffic
It is used to evaluate the traffic of subscribers.
5.2 Mobility Management-Specific KPI

This measurement unit is aimed at measuring the capability of the network to retain a service
for a subscriber under given conditions for a requested period once the service is accessed.
Table 5-2 The name and description of CPI
5-2
Name
Description
Location Update Success Ratio
It is used to evaluate the location update

procedure.
Authentication Success Ratio
It is used to evaluate the authentication

procedure.
Intra-office Handoff Success Ratio
It is used to evaluate the call continuity when

the MS keeps moving within the domain of a
specific MSCe.
Inter-office Handoff Success Ratio
It is used to evaluate the call continuity when

the MS keeps moving among different
MSCe.

Issue 02 (2010-03-15)
HUAWEI CSOFTX3000
5 KPI System
5.3 Service-Specific KPI

The service-specific KPI reflects the processing of services. Apart from the short message
service (SMS) and PDSN service mentioned here, each office may provide feature services such
as the location service and number portability service. To learn the quality of these special
services, the offices can define the desired KPIs.
Name
Description
SMS Origination Success Ratio
It is used to evaluate the origination of the

SMS service.
SMS Termination Success Ratio
It is used to evaluate the termination of the

SMS service.
PDSN Origination Success Ratio
It is used to evaluate the origination of the

PDSN service.
PDSN Termination Success Ratio
It is used to evaluate the termination of the

PDSN service.
5.4 Authentication
The system load-specific KPI reflects the utilization of system resources and provides important
evidence for resource utilization and planning.
Issue 02 (2010-03-15)
Name
Description
Number of Subscribers Registered with the

VLR
It is used to take statistics on various

subscribers in the VLR and evaluate the usage
of the VLR.
Processor Load
It is used to evaluate the processing

capabilities of the processors.
Load over Signaling Links
It is used to evaluate the load of the signaling

links.
Load over Trunk Circuits
It is used to evaluate the load of the trunk

circuits.

5-3

Performance Management Description (V200R007C02 - 02)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Performance Management Description (V200R007C02 - 02)

Hochgeladen von

Copyright:

Verfügbare Formate

HUAWEI CSOFTX3000 Mobile SoftSwitch Center

Performance Management Description

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

3 Applications of Performance Measurement.........................................................................3-1

Huawei Proprietary and Confidential

3.3 Network Optimization.....................................................................................................................................3-5

4 Common Measurement Tasks.................................................................................................4-1

5 KPI System.................................................................................................................................. 5-1

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

About This Document

About This Document

Engineering technical personnel

Operation and maintenance engineers

Changes in Issue 01 (2009-12-15)

Changes in Issue 02 (2010-03-15)

Huawei Proprietary and Confidential

1 Introduction to the Performance Measurement

Introduction to the Performance

About This Chapter

Huawei Proprietary and Confidential

1 Introduction to the Performance Measurement

1.1 Basic Concepts of Performance Measurement

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.

Process of traffic measurement:

The system stores the sampling results in a temporary counter.

PM period: five minutes

PM object: outgoing trunk occupied traffic

Performance Measurement Task

Huawei Proprietary and Confidential

1 Introduction to the Performance Measurement

Performance Measurement Object

Performance Measurement Entity

Performance Measurement Time

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

Huawei Proprietary and Confidential

1 Introduction to the Performance Measurement

Table 1-1 Comparison between semi-permanent task and period-limited task

Must Define End Time

Stopped when deleted or deactivated

Stopped at end time

Performance Measurement Unit

Office direction Outgoing Calls

Outgoing office direction

Busy Hour Call Attempt

Huawei Proprietary and Confidential

1 Introduction to the Performance Measurement

CPU seizure ratio traffic

Originating call attempt times

Fixed Line Subscriber in Performance Measurement

Telephone User Part (TUP) links

ISDN User Part (ISUP) links