SRAN7.

0
Feature Parameter Description


Issue 01
Date 2012-04-28

HUAWEI TECHNOLOGIES CO., LTD.


Copyright Huawei Technologies Co., Ltd. 2012. 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 trademarks 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 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


SingleRAN
Contents

Issue 01 (2012-04-28)

i

Contents
1 Introduction ................................................................................................................................ 1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History .............................................................................................................................. 1-1
2 Basic Functions ........................................................................................................................ 2-1
3 Performance Management Architecture ............................................................................. 3-1
3.1 Overview ....................................................................................................................................... 3-1
3.2 Architecture ................................................................................................................................... 3-1
4 Performance Statistics ............................................................................................................ 4-1
4.1 Performance Statistics .................................................................................................................. 4-1
4.1.1 Basic Concepts ..................................................................................................................... 4-1
4.1.2 Counter Identification ............................................................................................................ 4-2
4.1.3 Counter Help Documents ..................................................................................................... 4-2
4.1.4 Counter Statistics Methods ................................................................................................... 4-2
4.1.5 Aggregation Methods ............................................................................................................ 4-3
4.1.6 Adding and Deleting a Counter ............................................................................................ 4-4
4.2 KPI ................................................................................................................................................. 4-4
4.3 Measurement Management .......................................................................................................... 4-4
4.3.1 Measurement Configuration ................................................................................................. 4-4
5 Performance Management Tool ............................................................................................ 5-1
5.1 M2000 Performance Management Sub-System ........................................................................... 5-1
5.2 PRS ............................................................................................................................................... 5-2
5.3 Performance Data Browse Tool .................................................................................................... 5-2
6 Northbound Interface ............................................................................................................... 6-1
6.1 Northbound Interface Overview .................................................................................................... 6-1
6.1.2 Recommended Interconnection Solution ............................................................................. 6-2
6.1.3 Relevant Document Description ........................................................................................... 6-2
7 Abbreviations ............................................................................................................................. 7-1
8 Reference Documents ............................................................................................................. 8-1

SingleRAN
1 Introduction

Issue 01 (2012-04-28)

1-1

1 Introduction
1.1 Scope
This document describes performance management. Performance management belongs to the O&M for
the WCDMA and GSM networks of Huawei. This document includes the statistical method for
performance data, the mechanism and tool for performance measurement, the northbound interface,
and relevant reference documents.
1.2 Intended Audience
This document is intended for:
Personnel who are familiar with WCDMA and GSM basics
Personnel who need to understand performance management
Personnel who work with Huawei products
1.3 Change History
This section provides information on the changes in different document versions.
There are two types of changes, which are defined as follows:
Feature change: refers to the change in the dynamic power sharing among carriers feature.
Editorial change: refers to the change in wording or the addition of the information that was not
described in the earlier version.
Document Issues
The document issues are as follows:
01 (2012-04-28)
Draft A (2012-02-15)
01 (2012-04-28)
This is the first release of SRAN7.0.
Draft A (2012-02-15)
This is the first draft of the document for SRAN7.0.
Compared with issue SRAN6.0 02(2011-06-30), this issue incorporates the changes described in the
following table.
Change Type Change Description Parameter Change
Feature change None None
SingleRAN
1 Introduction

Issue 01 (2012-04-28)

1-2

Editorial change The document is modified as follows:
1Counter statistics methods are added.
2Counter aggregation methods in the Network Management
System (NMS) are added.
3Description in section 4.3 "Measurement Management" is
optimized.
4Chapter 2 "Basic Functions" is added.
None

SingleRAN
2 Basic Functions

Issue 01 (2012-04-28)

2-1

2 Basic Functions
Performance management provides the following functions:
Verifies whether product-related features are effective.
Detects networks whose performance deteriorates, enabling telecom operators to take measures to
improve network quality.
Troubleshoots network faults and provides suggestions on network quality improvement.
Monitors and optimizes wireless and transport networks, improving user experience and enabling
telecom operators to make full use of existing device resources.
Provides network planning engineers with detailed information required for network expansion.
SingleRAN
3 Performance Management Architecture

Issue 01 (2012-04-28)

3-1

3 Performance Management Architecture
3.1 Overview
Performance management is a function defined by the Telecommunication Management Network (TMN).
Performance management provides the method of efficiently monitoring network performance, and
facilitates troubleshooting and network optimization.
3.2 Architecture
The main function of performance management includes performance monitoring and reporting that are
based on the statistics and collection of the performance data. Generally speaking, performance
management is applicable to the data reported by the NEs and the operations performed on the
Operating Support System (OSS).
The architecture of performance management is shown in Figure 3-1.
Figure 3-1 Architecture of performance management


The network elements (NEs) include the BSC in the GSM mode, and the RNC and NodeB in the UMTS
mode. The BTS in the GSM mode cannot function as an independent NE. The statistical data of the BTS
is generated and reported by the BSC. The NodeB in the UMTS mode independently generates
statistical data and reports the data to the M2000 through an independent channel.
SingleRAN
3 Performance Management Architecture

Issue 01 (2012-04-28)

3-2

The NEs collect performance data of the network, device, function, service, or other objects. At the end
of each statistical period, the NEs generate related data and report the data to the M2000.
The BSC or RNC saves the statistical results in files. The files are in the format of Huawei private
Measurement Result File (MRF) that is in binary form and may be compressed. The value of the counter
for the NodeB is small. Therefore, the NodeB reports the statistical results in the form of a binary packet
to the M2000 at the end of each statistical period.
The M2000 is the specific carrier of performance management and plays an important role in
performance management architecture. You can process and monitor data through the graphical user
interface (GUI) provided by the M2000.
In addition to the function of querying the original performance data on the M2000, Huawei provides the
comprehensive Performance Report System (PRS). After obtaining the performance data from the
M2000, the PRS pareses and saves the data in the database of the PRS, and regularly summarizes the
data. The PRS also provides the functions of storing key data for an extended time, querying data
flexibly in multiple dimensions, report management, report generation, and report distribution.
SingleRAN
4 Performance Statistics

Issue 01 (2012-04-28)

4-1

4 Performance Statistics
4.1 Performance Statistics
Performance statistics are generated based on real-time measurement for the radio and transmission
networks. Performance statistics consist of a series of pre-defined measurement counters.
You can subscribe to each pre-defined measurement counter for the radio and transmission networks on
the GUI of the M2000. You can enable a measurement by activating a counter and setting the
measurement period. The M2000 collects and saves the measurement results.
4.1.1 Basic Concepts
Measurement counter
Measurement counter (or counter) indicates the service amount (such as request times and service
traffic) that must be collected to complete a measurement. You can regard a measurement counter as
a measurement.
Measurement object
Measurement object indicates the various physical or logical entities that are measured, such as a
BSC, a cell, and the sub-system of a board.
Measurement unit
Measurement unit indicates the effective combination of counters with the same attributes. For
example, hard handover measurement is a measurement unit. It is used to calculate the various
messages in the basic hard handover procedure from the perspective of a cell.
Function set
Function set indicates the set of several measurement units with the same attributes. For example, the
function set Measurements related to Radio Access Bearer (RAB) management consist of the
following measurement units: Measurement of CS RAB assignment modification per RNC,
Measurement of CS RAB release per cell, Measurement of PS RAB assignment setup per RNC.
In the performance management system (M2000), multiple counters with the same measurement
purpose form a measurement unit, and multiple measurement units with the same attribute form a
function set. Through these concepts, the convenience and efficiency of performance measurement is
improved, and users can quickly locate the required counter.

One counter belongs to only one measurement unit; one measurement unit belongs to only one function set.
Measurement period
A measurement period indicates the interval at which NEs report measurement results.
SingleRAN
4 Performance Statistics

Issue 01 (2012-04-28)

4-2

Figure 4-1 Relationships among measurement objects, function sets, measurement units, and counters


4.1.2 Counter Identification
ID Name Description
67180678 VS.AMR.DL.RateUp Number of DL Rate Increases for AMR Services for Cell

ID is the unique identification of a counter. It is used for the interconnection between the M2000 and the
NMS manufactured by a third party.
Name indicates the short name of a counter. You must name a counter in the way that customers can
understand the meaning of the counter through the name.
Description indicates the brief description for a counter. It is the extended description of the counter
name.
4.1.3 Counter Help Documents
The content of the Performance Counter Reference is organized by measurement object as shown in
the following figure. For the measurement object, measurement unit, counter, and relevant help
information, see the BSC6900 Performance Counter Reference and NodeB Performance Counter
Reference.


4.1.4 Counter Statistics Methods
The following table lists counter statistics methods:
SingleRAN
4 Performance Statistics

Issue 01 (2012-04-28)

4-3

Statistics
Method
Description Example
SCAN Counts the number of sampling
times in a statistical period. The
accumulated sample value
increases by 1 at each time when
the number of sampling times is
increased by 1. The initial value is 0.
Sampling Times of PDCH Measurement
If the sampling interval is 5 seconds and
statistical period is 30 minutes, the value of
this counter is 360.
ACC Obtains accumulated sample values
in a statistical period. You can divide
the accumulated sample values by
the number of sampling times to
obtain the average counter value.
Total Number of Sampled Available
PDCHs
The value of this counter is the total
number of PDCHs that are sampled every
five seconds.
You can also obtain the average counter
value in 30 minutes.
GAUGE Counts the variable whose value can
be dynamically increased or
decreased. The variable is of int or
float type. After the statistical period
ends, the variable value is the
statistical result.
Number of UEs in CELL_DCH State for
Cell
PEG The number of events is increased
by 1 each time.
Number of Incoming Hard Handover
Attempts for Cell
PDF Perform distribution statistics based
on intervals.
For Number of Times that DL
Throughput of HSDPA Services Within
Each Range, interval distribution for
statistics is as follows:
[0]: 0 < = x < 32 kbps
[1]: 32 < = x < 64 kbps
[2]: 64 < = x < 256 kbps
[3]: 256 < = x < 512 kbps
[13]: 12288 kbps < = x

4.1.5 Aggregation Methods
Aggregation method indicates how to aggregate counter values by time or object on the M2000. The
following table lists aggregation methods:
Aggregation Method Description
SUM Sum of all samples.
MAX Maximum value of all samples.
MIN Minimum value of all samples.
AVG Average value of all samples.
SingleRAN
4 Performance Statistics

Issue 01 (2012-04-28)

4-4


4.1.6 Adding and Deleting a Counter
In a new version, a counter is added, because a new feature is added, or the original feature and
statistical process are improved and supplemented.
A counter that is used in the current version may not be used or may be replaced by other counters in the
next version, because the algorithm is changed or the counter is optimized.
4.2 KPI
Key Performance Index (KPI) reflects the user perception and resource usage efficiency.
For the detailed definition of KPI formula recommended by Huawei, see the KPI Reference in the HedEx
document package. The KPIs in this section are summarized based on the experience of Huawei
commercial network management and radio network optimization. The contents of the KPIs in this
section are only for reference. Users can modify or customize a KPI based on actual requirements
through the M2000.
4.3 Measurement Management
4.3.1 Measurement Configuration
After you set the measurement counters, measured objects, and measurement period for an NE on the
M2000, the NE reports the counter measurement results (performance data) to the M2000 when the
measurement period begins. The mediation service of the M2000 server analyzes the packets reported
by NEs into a uniform format. The performance service saves the data required by users to the
performance database. Through the northbound interface of the M2000, the performance data of NEs
can be provided to the NMS for northbound users to analyze.
SingleRAN
4 Performance Statistics

Issue 01 (2012-04-28)

4-5

Figure 4-2 M2000 performance measurement


Table 4-1 Process of M2000 performance measurement
Step Procedure Description
1 Register
measurement tasks
On the M2000 client, set the measurement counters, objects, and
period, and deliver measurement tasks to the performance
management (PM) mediation through the PM server.
2 Deliver
measurement tasks
The PM mediation delivers the measurement counters, objects, and
period to NEs.
3 Generate
measurement
results
The NEs generate the performance measurement results based on
the measurement period.
4 Report
measurement
results
The NEs report the performance measurement results to the
M2000 server.
5 Parse measurement
results
The PM mediation parses the performance measurement results.
6 Import measurement
results
The M2000 invokes the result import function to import the parsed
performance measurement results to the performance database.
7 Query results on the
M2000 client
If you have subscribed to the M2000 measurement results, you can
query the reported performance measurement results on the
M2000 client.
SingleRAN
4 Performance Statistics

Issue 01 (2012-04-28)

4-6

Step Procedure Description
8 Export performance
data
Through the M2000 northbound interface, users can export the
performance data in the database to the NMS.
The Nastar uses a data collection tool to obtain performance data
based on the preset IP address of the M2000 server, user name,
password, and save path of the performance data.
The PRS allows users to create scheduled tasks. Triggered by
these tasks, the PRS periodically collects data from the M2000,
saves data into files stored in a specified directory, and imports data
in the files into the database for follow-up data query and analysis.

Counters Type and Description
Counter Type Description
System
counter
Common
counter
Common counters are the key counters defined by NEs.
These counters are selected by default. If you do not clear these counters, all
the measurement results of these counters are reported to the M2000 and
stored in the M2000 performance database. You can query the measurement
results stored in the performance database.
You can clear common counters.
Extended
counter
Extended counters are also counters defined by NEs.
These counters are not selected by default. The measurement results of the
selected extended counters are reported to the M2000. Then, the M2000
determines whether to store the measurement results in the M2000
performance database as required.
You can select or clear extended counters when the M2000 is running.

If you select an extended counter, the measurement results of this
extended counter are saved in the performance database of the M2000.
Then, you can query the measurement results of the selected extended
counter.

If you clear an extended counter, the measurement results of this extended
counter are not saved in the M2000 performance database. As a result, the
measurement results of this cleared extended counter cannot be queried.
Custom counter Custom counters refer to the counters that are defined by adding, subtracting,
multiplying, and dividing system counters. The sources of Custom counters
are as follows:

Automatically imported when the M2000 is installed. The counter name
begins from [UDC]. These Custom counters are displayed after the relevant
NE mediation software is installed.

Defined by users on the M2000 client. Custom counters can be nested to
create other Custom counters. You can add, modify, and delete Custom
counters when the M2000 is running.

Performance Measurement Period
A measurement period refers to the interval for NEs to report performance measurement results.
SingleRAN
4 Performance Statistics

Issue 01 (2012-04-28)

4-7

NEs report measurement results to the M2000 based on specified periods. The M2000 analyzes the
results and then saves the results in the database. Therefore, you can query the measurement result
of the corresponding period. The periods for reporting measurement results vary according to
measurement counters. Different types of NEs support different measurement periods. The supported
measurement periods are one or a multiple of 5 minutes, 15 minutes, 30 minutes, 60 minutes, and 24
hours. The NodeB does not support the 5-minute period.
Short measurement periods refer to 5-minute and 15-minute periods. The total number of counters
measured in a 5-minute period must be less than 1,000, but those measured in a 15-minute period
are not limited.
Common measurement periods refer to 30-minute, 60-minute, and 24-hour periods. The 15-minute
period of the NodeB is also common.
History measurement periods refer to the periods that are manually changed when the measurement
periods supported by an NE can be changed.
The system limits the number of short measurement period counters to reduce the impacts of the short
counter measurement period on the M2000 storage capacity.
SingleRAN
5 Performance Management Tool

Issue 01 (2012-04-28)

5-1

5 Performance Management Tool
The performance management tool includes the M2000 performance management sub-system, PRS,
and performance data browse tool.
5.1 M2000 Performance Management Sub-System
The M2000 performance management sub-system is a basic and important function module on the
M2000.
Through the M2000 performance management sub-system, you can conveniently configure the
measurement object, counter, and period; timely query the performance measurement results;
effectively monitor network devices; flexibly configure counter thresholds; and use the function of
exporting performance data on the M2000 to the NMS manufactured by a third party. The M2000 is the
performance data source for the PRS.
For the detailed description of the M2000 performance management sub-system, see the M2000 online
help.
Figure 5-1 M2000 performance management subsystem
M2000performance
management
Performancedata
collectionandstorage
Performancethreshold
alarms
Performancedataquery
Performancedataexport
PMunitsonNEs PMunitsonNEs PMunitsonNEs
DCN


Performance data collection and storage
The M2000 periodically obtains measurement results of performance counters from NEs based on
measurement settings and saves them to the M2000 database. Users can modify the measurement
settings and save them as a template. In addition, users can view measurement status, synchronize
measurement data, and view synchronization task status.
Performance data query
On the M2000, users can query performance data saved in the database. The M2000 displays the
query results in a table, line chart, or bar chart. The M2000 also allows users to print and save query
results, to query templates and missing data, and to subscribe to performance data.
Performance threshold alarms
SingleRAN
5 Performance Management Tool

Issue 01 (2012-04-28)

5-2

Users can set alarm thresholds for measurement counters. When a counter value exceeds a specified
threshold, a performance alarm is generated. When the counter value falls below the threshold, the
performance alarm is cleared automatically.
Performance data export
M2000 performance management provides source data for the NMS, Nastar, and PRS.
5.2 PRS
In addition to the function of querying the original performance data on the M2000, Huawei provides the
PRS that is used to provide comprehensive functions for users.
At present, the PRS is a product independent of the M2000. The deployment of the PRS is flexible. You
can deploy the PRS on the M2000 or deploy the PRS separately. You are advised to deploy the PRS
separately so that the PRS can share loads on the M2000 in a better way and provide more powerful
capability for processing and storing performance data. Another advantage of deploying the PRS
separately is that the PRS can support the data of the NEs managed by multiple M2000s. The PRS
supports the NEs manufactured by other vendors by using other techniques.
The FTP transmission mode is used between the PRS and M2000. For the BSC or RNC, the PRS
obtains the NE data in the MRF format from the M2000. For the NodeB, the M2000 saves the statistical
data in an MRF formatted file. The PRS obtains the performance data stored in the M2000, and then
parses and saves the data in the database of the PRS, and regularly summarizes the data. The PRS
also provides the functions of storing key data for an extended time, querying data flexibly in multiple
dimensions, report management, report generation, and report distribution.
For the detailed description of the PRS, see the PRS online help.
5.3 Performance Data Browse Tool
The performance data browse tool belongs to the local maintenance terminal (LMT). It provides the
function of browsing counter data on the LMT of the NE. This tool is used only when the M2000 fails to
be accessed.
The performance data browse tool is a stand-alone tool. You can connect the tool to the NE and
download the performance data stored on the NE. However, the downloaded performance data can be
displayed on the interface. The performance data browse tool does not provide complicated functions,
such as summarization and calculation. Also, the efficiency of running the tool is low. Therefore, you are
advised to only use this tool if the M2000 fails to be accessed. This tool can only view original data.
SingleRAN
6 Northbound Interface

Issue 01 (2012-04-28)

6-1

6 Northbound Interface
6.1 Northbound Interface Overview
The northbound interface is an interface between the Element Management System (EMS) and the
NMS.
Figure 6-1 Location of the northbound interface


The M2000 opens the northbound performance file interface to support the capability of integrating with
the NMS manufactured by a third party.
The file interface is a common performance interface. It periodically exports performance data from the
database into files based on preset export criteria. The NMS can obtain the exported performance files
from a specified path on the M2000 by using the FTP. In addition, if the NMS provides the IP address of a
server and specifies a path on the server, the M2000 can upload files to the path on the server.
Interface
Protocol
Functions Feature Scenarios
File interface
(NE-based)
Periodically exports performance data
into files.
Generates one configuration file for
each NE in each period.
Exports only the original data of NEs. It
does not support the export of
multiple-period aggregation data and
user-defined counter data.
Saves the exported files in XML format.
This format is commonly used and
complies with 3GPP specifications.
Short delay for
file export
No impact on the
database
Recommended.
Applicable in scenarios
where short delay for
file export and little
impact on the M2000
are required.

SingleRAN
6 Northbound Interface

Issue 01 (2012-04-28)

6-2

For the detailed description of the performance file northbound interface, see the M2000 Northbound
Performance File Interface Developer Guide (NE-Based).
6.1.2 Recommended Interconnection Solution
On the condition of meeting the requirements of integrating with the NMS manufactured by a third party,
the following solutions are recommended based on the features of the NMS and NEs. The solutions are
provided to reduce the impacts of counter differences in different NE versions on the NMS manufactured
by a third party.
Interconnection by using counter ID
The counter ID is used to identify a counter in the Huawei NE system. The counter name indicates the
name of a counter. The counter ID uniquely identifies a counter. The counter ID is unique in various
NE versions. Using the counter ID during NMS interconnection reduces the impacts of counter name
change on the NMS manufactured by a third party. In addition, the counter name is long. If the counter
name is used during NMS interconnection, the size of the northbound interface performance file is
large, affecting file transfer and parsing efficiency.
The counter name may be changed. Therefore, you are advised not to use the counter name for NMS
interconnection.
6.1.3 Relevant Document Description
When integrating the NMS manufactured by a third party through the northbound interface, you can refer
to the following documents:
M2000 Northbound Performance File Interface Developer Guide (NE-Based)
This document is released with the M2000 document. This document is intended to provide the
guidance on how to integrate the NMS manufactured by a third party with the northbound performance
file interface. This document includes the mechanism of the performance file interface, performance
file format, and user commissioning guide.
Performance Counter List
This document is released with the NE adaptation layer document. It includes the definition of the
counters supported by the NE of the relevant version and the format of the counter object.
NE Performance Counter Changes
This document is released with the NE document. It includes the counter change between this NE
version and earlier versions. You must modify the counter in the NMS manufactured by a third party
according to this document before the upgrade. For any counter change problem, contact the on-site
engineer.
SingleRAN
7 Abbreviations

Issue 01 (2012-04-28)

7-1

7 Abbreviations
Abbreviations Full Name
BSC Base Station Controller
EMS Element Management System
FTP File Transfer Protocol
GSM Global System for Mobile Communications
GUI Graphical User Interface
HSDPA High Speed Downlink Packet Access
KPI Key Performance Indicator
LMT Local Maintenance Terminal
MML Man-Machine Language
MRF Measurement Result File
NE Network Element
NMS Network Management System
OSS Operating Support System
PRS Performance Report System
QoS Quality of Service
RNC Radio Network Controller
TMN Telecommunication Management Network
UMTS Universal Mobile Telecommunications System
WCDMA Wideband Code Division Multiple Access
XML Extensible Markup Language

SingleRAN
8 Reference Documents

Issue 01 (2012-04-28)

8-1

8 Reference Documents
The documents related to performance management and statistics provided by Huawei are as follows:
Document Name Release Mode
BSC6900 Performance Counter Changes Released with the BSC6900.
BSC6900 Performance Counter Reference Released with the BSC6900.
BSC6900 Performance Counter List Released with the BSC6900.
KPI Reference Released with the BSC6900.
NodeB Performance Counter Changes Released with the NodeB.
NodeB Performance Counter Reference Released with the NodeB.
NodeB Performance Counter List Released with the NodeB.
M2000 Performance Measurement Management User Guide Released with the M2000.
M2000 Performance Report Management User Guide Released with the M2000.
M2000 Northbound Performance File Interface Developer Guide
(NE-Based)
Released with the M2000.
PRS Product Description Released with the PRS.
PRS Performance Report Management Released with the PRS.
PRS Performance Report Reference Released with the PRS.