Issue: 01

Performance
Management
Overview
Can I monitor and analyze performance data of each NE and each
network on a common platform?

eNodeB

eNodeB
Too many NEs
Too many counters GSM
to be monitored
UMTS
Too many LMTs to
be logged in

Yes. Performance management of U2000 can fulfill these

requirements.

As a functional module of U2000, performance management is used to monitor and analyze network
performance data. This module periodically collects the performance counter data of networks,
devices, functions, services, or other objects from NEs and saves and manages the data in a
centralized manner. NE performance data and OSS performance data can be provided to the NMS
through northbound interfaces for northbound users to analyze.

• Monitors network running • Verifies network

status. configurations.
• Monitors signal connection Performance • Identifies network
status changes. measurement problems.
• Provides network device • Plans network
running data. optimization policies.

How does the performance measurement module collect

counter results?

I have the U2000 system, but I

still do not know how to set
measurement. Show me.

We will cover this in greater detail. But first we need to go over

some basic concepts of performance measurement.
Information required in a measurement task must be issued to related NEs to collect
statistics of the counter value of an attribute for the NEs. A measurement task must
contain three basic factors.

Three Factors of Performance

1 Measurement Object
Whose attributes are
Counter measured Period

Three Factors of
Performance Measurement
 Counter-What attributes are measured?
Measurement counters rely on measurement objects. Each measurement object
maps one or more measurement counters. That is, a measurement object has
specific measurement items.
Common
counter
System
counter Extended
counter
Counter User-defined System
counter addition/
counter
User-defined or subtraction/ or
System multiplication/
counter User-defined
counter division
counter
• Common counter: KPIs defined on NEs. Measurement
is set by default on U2000 for this type of counter.
• Extended counter: counters defined on NEs. You need to manually
set measurement for this type of counter on U2000.  Common counters,  Counter
measured by default Type

 Object-Whose attributes are measured?

A measurement object can be a physical entity (such as a board or a subrack) or a

logical entity (such as a cell or a neighboring cell). The first and second types of
objects are configured on the NE side.

Type 1 objects Type 2 objects

 Measurement is set by default.  Measurement is not set by default.
 You can manually cancel the measurement.  You can manually set the measurement.
Object

Type 4 objects
 Measurement is set by default but the number of
objects is restricted.
 Only neighboring LTE cell objects are supported.
Type 3 objects
 You need to set specific object features for type 3
objects to create object instances.
 You can manually set the measurement.

 Period-Interval at which counters are measured

The following tabs displayed on the U2000 client indicate different
measurement periods supported by NEs.

Short measurement periods Common measurement periods

5 minutes 15 minutes 30 minutes

60 minutes 24 hours

The measurement periods defined at the NE side and vary with the NE type. It is not
recommended to change the measurement periods. If you need to change them,
contact Huawei technical support to evaluate the change impact.

2 Overall Performance Management Process

Performance management module

Northbound
4 6 export
1 1. Set counters, objects, and periods for
3 measurement.
5 DB
2. Subscribe to measurement. NEs
periodically report performance results
to U2000.
2 3. U2000 saves performance results to
the database.
Three result display modes
4. A threshold alarm is generated if the
•Table
threshold alarm trigger conditions are
•Bar chart met.
•Line chart 5. Query performance statistical results in
NE the database.
6. Export results through the northbound
interface.
 Why can't performance results
be queried? Why is the table empty? (This
could cause confusion among
customers)

Use the diagnosis tool to

find the cause.

U2000 supports diagnosing object loss, diagnosing

suspicious result values, and diagnosing result
column loss. Use the functions as required.
Portal for result loss
diagnosis
2 Specify diagnosis
criteria. Diagnosis process, results,
handling suggestions, and FAQs
are displayed on the U2000 client.

The diagnosis tool helps me find the cause, but

can I find the missing data?

I need a data report!

(A new source of Yes. Manual supplementary
confusion for collection can help find the
customers) missing data.

Portal for result

synchronization
2 Right-click a record in the Status
Query
performance
column and choose Synchronize
results again.
Result from the shortcut menu. Great! I can view
the queried
Specify result
results in
synchronization
a table, line chart,
criteria.
or bar chart.

U2000 also provides the automatic supplementary collection

function. When the connection to an NE is restored or the
performance service starts, if some results are missing, the
performance measurement module starts automatic
supplementary collection.

Some Performance Management Specifications

Maximum storage Total number of Maximum number of function
Total number of
duration of counters in query subsets that can be used in a
query templates
performance data criteria template
30 days 150 2000 10

For details, see

"Technical Specifications of Performance Measurement Management" of "Performance Measurement Management"
in U2000 Help.

Copyright © Huawei Technologies Co., Ltd.