NetNumen U31 R06

Unified Element Management System

Performance Management Description

Version: V12.14.30

ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn

LEGAL INFORMATION
Copyright 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History
Revision No.

Revision Date

Revision Reason

R1.0

2014-11-30

First edition

Serial Number: SJ-20141121113158-004

Publishing Date: 2014-11-30 (R1.0)

SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

Contents
Chapter 1 Implementation Principle ......................................................... 1-1
Chapter 2 Basic Concepts ......................................................................... 2-1
Chapter 3 Performance Management Functions..................................... 3-1
3.1 Performance Index Management......................................................................... 3-1
3.2 Measurement Task Management......................................................................... 3-1
3.3 Performance Data Query .................................................................................... 3-1
3.4 Performance Data Export.................................................................................... 3-2
3.5 Performance Data Recollection ........................................................................... 3-2
3.6 Performance Threshold Alarm............................................................................. 3-4

Glossary .......................................................................................................... I

I
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

This page intentionally left blank.

II
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

Chapter 1

Implementation Principle
For the overall performance management flow in the NetNumen U31 system, see Figure
1-1.
Figure 1-1 Overall Performance Management Flow

The overall performance management flow in the NetNumen U31 system includes creating
a measurement task, storing performance data, displaying performance data, exporting
data through the northbound interface, and checking thresholds.
1. After a performance measurement task is created on the NetNumen U31, the
NetNumen U31 server delivers the task to the NE.
2. The NE reports the performance data to the NetNumen U31 server in accordance with
the granularity and other conditions specified in the measurement task.
3. The NetNumen U31 server stores the performance data in its database.
4. Maintenance personnel query the performance data, which can be displayed on the
client in accordance with customized query conditions.

1-1
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

NetNumen U31 R06 Performance Management Description

5. If any threshold task is created, that is, a threshold for an index is set, the NetNumen
U31 server enables threshold-based determination when the NE reports performance
data. If the index reaches the threshold, a corresponding alarm is reported and
displayed on the client.
6. The performance data from the NE can be sent to the upper-layer NMS through the
northbound interface of the NetNumen U31 server so that maintenance personnel can
analyze the data.

1-2
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

Chapter 2

Basic Concepts
MOC
MOC is the combination of objects with the same properties, such as the IMSI number.

MO
MO can be a physical entity, a logical entity or the combination of the physical entity and
logical entity, which needs to be measured, such as the entire office and a destination
code.

PO
PO is the basic measurement unit and can measure different MO indexes. Each MO type
has several POs. You can select a PO based on the index to be measured, such as the
IMSI flow measurement.

Counter
Counter is a specific measurement index contained in the PO. Each PO has several
counters. A counter may consist of the following items:
l
l
l
l

Counter ID: ID of a performance index.

Description: Description of the performance counters.
Triggers: The measurement triggering point describes the triggering process of a
performance counter.
Collection Method: Collection methods of the performance counters.
Collection methods of the performance counters are described in Table 2-1.
Table 2-1 Collection Method
Value

Name

Description

CC

Accumulation

It traces the accumulated changes of an event in the collection

Counter

granularity (such as PDP activation), and the value of the

counter generally is incremented in an unidirectional way.

Gauge

Measurement

It traces the event data that changes continuously in the

Counter

aspect of time, and it can change bidirectionally (meaning that

it can increase or decrease).

Sample

Sampling

It replaces the old data in the counter according to the

Counter

reported event data, and the collected data when the collection
granularity period ends is the latest reported event data.

2-1
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

NetNumen U31 R06 Performance Management Description

Value

Name

Description

TA

Time Average

It samples the value of continuously changing even data every

Counter

10 seconds, and calculates and reports the average value of

all 10 - second data when the collection granularity ends.

Max

Maximum Value

It generally obtains the event data every 10 seconds (the data

Counter

may be the sampling value of the continuous event data, or

may be the variation of the data over 10 seconds), and only
the maximum result is saved in the counter. In addition, data
reported by this counter is the maximum value of a module
or a unit over the collection granularity period. Data of each
module or unit is independent, therefore, it is meaningless to
combine them by module, and they cannot be provided to
the background as the original data for calculating the peak
KPI of the NE.

Peak

Peak Value

It calculates the peak data of an event in the whole NE using

Counter

the peak value algorithm, and the results of this counter are
gathered and displayed on the OMP.

SIMax

Maximum

Some internal counters for resource management are saved

Counter for

in the measured network element which reads these counters

Status Check

according to the preset sampling frequency. The measurement

value for the status check is very important at the beginning of
each collection cycle. At the end of each collection cycle, a
valid collection result is calculated according to all sampling
within this period. SIMax is applied for the maximum occasion.

SIMin

Minimum

Some internal counters for resource management are saved

Counter for

in the measured network element which reads these counters

Status Check

according to the preset sampling frequency. The measurement

value for the status check is very important at the beginning of
each collection cycle. At the end of each collection cycle, a
valid collection result is calculated according to all sampling
within this period. SIMin is applied for the minimum occasion.

SIMean

Average

Some internal counters for resource management are saved

Counter for

in the measured network element which reads these counters

Status Check

according to the preset sampling frequency. The measurement

value for the status check is very important at the beginning of
each collection cycle. At the end of each collection cycle, a
valid collection result is calculated according to all sampling
within this period. SIMean is applied for the average occasion.

KPI
KPI is used as the criterion for evaluating the stability and security of the network operation.

2-2
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

Chapter 2 Basic Concepts

KPI is a compound counter customized by maintenance engineers through arithmetic

operation based on several counters, including:
l

User-defined KPI
This kind of KPI is created on the NetNumen U31 client by maintenance engineers
through arithmetic operation based on the existing counters. You can view, modify
and delete the created KPI.

System-defined KPI
This kind of KPI is defined by the system. The maintenance engineers can only view
the KPI on the NetNumen U31 client. The modification and deletion operation are not
allowed.

Note:
A KPI can be used to query performance data or create a threshold task.

PI
PI is used as the criterion for evaluating the equipment performance. Similar to KPI, the
PI is obtained through arithmetic operation based on several counters. You can create PIs
as needed.

Note:
A PI can only be used to query performance data.

Collection Granularity
Collection granularity is the period of collecting the performance data from the front-end
NE. The collection granularity can be set to 5 minutes, 15 minutes, and 1 hour etc.

Query Granularity
Query granularity is the period of querying the performance data based on the
measurement task. The query granularity can be set to 5 minutes, 15 minutes, 30
minutes, 1 hour and 1 day.

2-3
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

NetNumen U31 R06 Performance Management Description

Note:
The query granularity must be greater than or equal to the collection granularity preset in
the measurement task.

Performance Measurement Task

A performance measurement task defines how to collect, store and transmit performance
data, and how to display and handle the data.
The performance measurement task specifies the time and period of collection, the specific
PO index and the type of performance data to be collected.
After a performance measurement task is created on the NetNumen U31 client, the system
automatically collects specified performance parameters within the preset period. The
system also gives the statistical result of network performance, from which maintenance
engineers can know the network operation status in time.

Performance Threshold Task

The performance threshold task is also called the QoS task. QoS is a network security
mechanism and technology used to solve problems, such as network delay and
congestion. In an overloaded or congested network, QoS can protect important services
from being delayed or discarded and ensure high-efficiency of the network operation.
In a performance threshold task, the time and the specific PO index, for which the threshold
calculation is performed, are defined. If the calculation result exceeds the preset threshold
range, a performance threshold crossing alarm is generated and reported to the fault
management system, reminding you of the network operation errors.

2-4
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

Chapter 3

Performance Management
Functions
Table of Contents
Performance Index Management................................................................................3-1
Measurement Task Management................................................................................3-1
Performance Data Query............................................................................................3-1
Performance Data Export ...........................................................................................3-2
Performance Data Recollection ..................................................................................3-2
Performance Threshold Alarm....................................................................................3-4

3.1 Performance Index Management

The performance indexes are consists of:
l
l
l

Counter
Key Performance Index (KPI)
Ordinary Performance Index (PI)

Some common performance indexes are predefined in the system. The maintenance
engineers can create customized KPIs or PIs based on their needs. The customized index
also can be used for setting the alarm threshold task.

3.2 Measurement Task Management

A measurement task defines how to collect, store, and transmit performance data and
how to process and present the performance data. The system collects performance data
and generates the measurement report based on task scheduling rules and the specific
granularity.
For a performance measurement task, the maintenance engineer specifies the NE to
be measured, the MO type, the time interval for collecting performance data, and the
entire period for collecting performance data. The NetNumen U31 server delivers the
measurement task to the NE. The NE reports the performance data to the NetNumen
U31 server in accordance with the granularity and other conditions specified in the
measurement task.

3.3 Performance Data Query

The NetNumen U31 supports querying performance data manually based on:
3-1
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

NetNumen U31 R06 Performance Management Description

User-defined conditions
The maintenance engineers query NE performance data based on customized
conditions.

Tasks
The maintenance engineers query NE performance data related to the task based on
performance measurement task.

Templates
The maintenance engineers execute the performance data query template manually,
and queries NE performance data based on the preset conditions in the template.

3.4 Performance Data Export

The NetNumen U31 system supports exporting the performance query data in the following
two ways:
l

Manually exporting the performance data

After querying the performance data, you can manually export the performance data
into files in CSV, XLS, XLSX, XML, TXT, PDF or HTM formats.

Automatically exporting the performance data periodically

The system supports querying the performance data by using a template task, and
then exporting the data into files in CSV, XLS, XLSX, XML, TXT, PDF or HTM formats.
In addition, NetNumen U31 can send the query result to a specified Email address or
to an FTP server.

3.5 Performance Data Recollection

For how to recollect performance data in the NetNumen U31 system, see Figure 3-1.

3-2
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

Chapter 3 Performance Management Functions

Figure 3-1 Flow of Recollecting Performance Data

If the collected performance data in the NetNumen U31 is incomplete, recollect the NE
performance data through automatic or manual recollection.
1. The NetNumen U31 server delivers a performance measurement task to an NE under
its management.
2. When a measurement period comes, the NE reports the performance data specified
in the measurement task to the NetNumen U31 server.
3. The NetNumen U31 server gathers and stores the performance data.
4. The NetNumen U31 server determines whether any performance data in a specified
period is missing. Maintenance personnel can manually check whether any data is
missing.
5. For the missing NE performance data, the NetNumen U31 server sends a request to
the NE for data recollection. Maintenance personnel also can manually recollect the
missing performance data.
6. The NE reports the missing performance data to the server.
7. The NetNumen U31 server displays the NE performance data on the client in
accordance with the customized query conditions.

3-3
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

NetNumen U31 R06 Performance Management Description

3.6 Performance Threshold Alarm

For the flow of generating and removing a performance threshold alarm in the NetNumen
U31 system, see Figure 3-2.
Figure 3-2 Flow of Generating and Removing a Performance Threshold Alarm

The performance threshold management function monitors the values of tested indexes.
If users have set a threshold task and thresholds for a certain index, the NetNumen U31
server will enable threshold-based determination upon data report. If the index value
exceeds the threshold, a corresponding threshold alarm is reported and displayed on the
client.
3-4
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

Chapter 3 Performance Management Functions

1. When a measurement period comes, an NE reports the performance data specified in

the measurement task to the NetNumen U31 server.
2. The NetNumen U31 server checks whether any threshold has been preset for indexes
measured in the measurement period.
3. If a threshold is preset, the NetNumen U31 server compares the reported performance
data with the preset threshold.
4. The NetNumen U31 server determines whether the NE performance index value
meets the alarm generating/removing conditions.
5. If the NE performance index value has met the alarm generating/removing conditions,
the NetNumen U31 server continues checking whether a threshold alarm for this
performance index.
l Have a threshold alarm for this performance index: Update the alarm information
l Have no threshold alarm for this performance index: Exists in the current system
6. If the NE performance index value has met the alarm generating conditions, and no
threshold alarm for this index exists in the current system, a corresponding threshold
alarm is generated. If the NE performance index value has met the alarm removing
conditions, and a threshold alarm for this index exists in the current system, a
notification message is generated notifying to remove the threshold alarm.

3-5
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

NetNumen U31 R06 Performance Management Description

This page intentionally left blank.

3-6
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential

Glossary
FTP
- File Transfer Protocol
KPI
- Key Performance Indicator
KPI
MO
- Measured Object
MOC
- Measurement Object Class
NE
- Network Element
NMS
- Network Management System
PI
- Performance Index
PO
- Performance Object
QoS
- Quality of Service

I
SJ-20141121113158-004|2014-11-30 (R1.0)

ZTE Proprietary and Confidential