Performance Management (SRAN13.1 - 01)

SingleRAN
Performance Management Feature

Parameter Description
Issue 01
Date 2018-04-10
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2019. 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 a 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
Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. i

SingleRAN
Performance Management Feature Parameter Description Contents
Contents
1 Change History.............................................................................................................................. 1
2 About This Document.................................................................................................................. 2
2.1 Applicable RAT.............................................................................................................................................................. 2
2.2 Features in This Document.............................................................................................................................................2
2.3 Differences Between Base Station Types....................................................................................................................... 3
3 Overview of Performance Management................................................................................... 4

3.1 Definition........................................................................................................................................................................4
3.2 Benefits........................................................................................................................................................................... 4
3.3 Architecture.................................................................................................................................................................... 4
4 Technical Description...................................................................................................................8
4.1 Basic Concepts............................................................................................................................................................... 8
4.1.1 Performance Counter................................................................................................................................................... 8
4.1.2 Measurement Object....................................................................................................................................................9
4.1.3 Function Subset......................................................................................................................................................... 10
4.1.4 Function Set............................................................................................................................................................... 10
4.1.5 Measurement Period.................................................................................................................................................. 11
4.2 Performance Counter Statistical Methods.................................................................................................................... 12
4.2.1 Performance Counter Statistical Types......................................................................................................................12
4.2.2 Performance Counter Aggregation Types................................................................................................................. 13
4.3 Counter-based Performance Measurement Process......................................................................................................13
4.4 Performance Counter Help Documents........................................................................................................................ 16
4.5 Northbound Interface....................................................................................................................................................17
4.5.1 Northbound Interface Overview................................................................................................................................ 17
4.5.2 Recommended Interconnection Solution...................................................................................................................17
4.5.3 Related Documents....................................................................................................................................................18
4.6 Schemes for Adding or Deleting Performance Counters and Object Type Parameters............................................... 18
5 Related Features...........................................................................................................................20
6 Network Impact........................................................................................................................... 21
7 Parameters..................................................................................................................................... 22
8 Counters........................................................................................................................................ 23
Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. ii

SingleRAN
Performance Management Feature Parameter Description Contents
9 Glossary......................................................................................................................................... 24
10 Reference Documents............................................................................................................... 25
Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. iii

SingleRAN
Performance Management Feature Parameter Description 1 Change History
1 Change History
This section provides information about the changes in different document versions. There are
two types of changes:
l Technical changes
Changes in features of a specified version
l Editorial changes
Changes in wording or addition of information
SRAN13.1 01 (2018-04-10)
This issue does not include any changes.
SRAN13.1 Draft A (2018-01-15)

SRAN13.1 Draft A (2018-01-15) introduces the following changes to SRAN12.1 04
(2017-12-04)
Change Change Description Paramete

Type r Change
Technical Converged iManager PRS, iManager SONMaster, and None

changes iManager TSP into the mobile agile operation for service
(mAOS). This helps integrate network evaluation, monitoring,
and intelligent optimization. The following sections are
modified:
l 3.3 Architecture
l 4.3 Counter-based Performance Measurement Process
Added the support for NB-IoT by LampSite base stations. For None
details, see 2.3 Differences Between Base Station Types.
Editorial Added a note of not reporting performance counter None

changes measurement data during an NE reset period. For details, see
3.3 Architecture.
Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. 1

SingleRAN
Performance Management Feature Parameter Description 2 About This Document
2 About This Document
2.1 Applicable RAT

This document applies to GSM, UMTS, LTE FDD, LTE TDD, and NB-IoT.
For definitions of base stations described in this document, see section "Base Station
Products" in SRAN Networking and Evolution Overview Feature Parameter Description.
2.2 Features in This Document

This document describes the following features.
Feature ID Feature Name Section
MRFD-210302 Performance Management 3 Overview of

Performance Management
LBFD-004008 Performance Management
TDLBFD-004008 Performance Management
MLBFD-12000408 Performance Management
FBFD-010025 Basic O&M Package 3 Overview of

(specifically the Performance Management
performance management
function)

SingleRAN
Performance Management Feature Parameter Description 2 About This Document
2.3 Differences Between Base Station Types

Feature Support by Macro, Micro, and LampSite Base Stations
Feature ID Feature Supported Supported by Supporte
Name by Macro Micro Base d by
Base Stations LampSite
Stations Base
Stations
MRFD-210302 Performance Yes Yes Yes

Management
LBFD-004008 Performance Yes Yes Yes

Management
TDLBFD-004008 Performance Yes Yes Yes

Management
MLBFD-12000408 Performance Yes Yes Yes

Management
Among micro base stations, only the BTS3911E/BTS3912E supports NB-IoT.

SingleRAN
Performance Management Feature Parameter Description 3 Overview of Performance Management
3 Overview of Performance Management
3.1 Definition
Performance management is a function defined by the Telecommunication Management
Network (TMN). This feature provides a method of efficiently monitoring network
performance, while facilitating network evaluation, optimization, and troubleshooting.
3.2 Benefits
Performance management helps you:
l Check whether product-related features are effective.
l Detect networks whose performance deteriorates, enabling telecom operators to take
measures to improve network quality.
l Troubleshoot network faults and provide suggestions on network quality improvement.
l Monitor and optimize wireless and transport networks. This improves user experience
and helps telecom operators maximize the usage of existing device resources.
l Offer network planning engineers detailed information required for network expansion.
3.3 Architecture
Performance management includes measurement management, measurement data collection,
real-time performance monitoring, and performance threshold alarms. The NEs, OSS, mAOS,
and NMS jointly provide these functions. Figure 3-1 shows the architecture of performance
management.

SingleRAN
Figure 3-1 Performance management architecture
NMS: network management system mAOS: mobile agile operation for service
XML: Extensible Markup Language MRF: measurement result file
MML: man-machine language FTP: File Transfer Protocol
SFTP: Secure File Transfer Protocol FTPS: File Transfer Protocol over SSL
NE: network element
The following describes the functions of each component in the performance management
architecture.
NEs
NEs in the performance management architecture include:
l BSC and eGBTS on the GSM network
l RNC and NodeB on the UMTS network
l Macro and micro eNodeBs on the LTE network
l MBSC and multimode base station on the SingleRAN network
After receiving performance measurement result subscription from the U2000, NEs collect
performance counters indicating the performance of physical and logical resources on the

SingleRAN
network based on the subscription information, generate corresponding performance data after
each counter statistical period, and report the data to the U2000.
l After each measurement period for periodical performance measurement, the NEs store
the performance data in measurement result files (MRFs) and send the MRFs to the
U2000.
l After each measurement period for real-time performance monitoring, the NEs send
measurement results in binary messages to the U2000.
GBTSs are not presented, because the BSC generates GBTS performance statistics and
reports them to the U2000.
NOTE
If the NE reset period includes the end time of a measurement period, the NE cannot report the
measurement result file. This will lead to the absence of performance counter measurement data between
the start of the current measurement period and the restoration of an NE reset. When the next
measurement period ends after the NE reset, the NE can normally report the measurement result file.
U2000
The U2000 is the platform to execute performance management. Users can register
performance measurement tasks, and process and monitor performance data through the
graphical user interface (GUI). The U2000 provides the following performance management
functions:
l Performance data collection and storage
The U2000 periodically obtains measurement results of performance counters from NEs
based on measurement settings and saves them to the U2000 database. Users can modify
the measurement settings and save them as a template. Users can also view measurement
status, synchronize measurement data, and view synchronization task status.
l Performance data query
On the U2000, users can query performance data saved in the database. The U2000
displays the query results in a table, line chart, or bar chart. The U2000 also allows users
to print and save query results, to query templates and missing data, and to subscribe to
performance data.
l Performance threshold alarms
Users can set alarm thresholds for measurement counters. When a counter value exceeds
a specified threshold, a performance threshold alarm is generated. When the counter
value falls below the threshold, the performance threshold alarm is cleared automatically.
l Performance data export
U2000 performance management provides source data for the NMS and mAOS. For
details of the U2000 performance management subsystems, see the OSS document
Performance Measurement Management.
mAOS&NMS
After obtaining the performance data from the U2000, the mAOS parses and stores the data in
the mAOS database and regularly aggregates the data. The mAOS can store key data for an
extended period, query data flexibly in multiple dimensions, and manage, generate, and
distribute reports.
After NEs send performance MRFs to the U2000, the NMS can obtain the files from specified
directories on the U2000.

SingleRAN
For details of the mAOS, see RAN Statistics Performance Visibility in mAOS Product
Documentation.

SingleRAN
Performance Management Feature Parameter Description 4 Technical Description
4 Technical Description
4.1 Basic Concepts

Three measurement elements are mandatory for periodical performance measurement and
real-time performance monitoring: performance counters, object types, and measurement
periods. Function subsets and function sets are introduced to implement layered performance
counter measurement.
4.1.1 Performance Counter

Performance counters, also termed as counters, indicate the number or amount (such as
service request times and traffic) collected for a measurement purpose.
Each performance counter has a unique ID and name. Table 4-1 describes an example
performance counter.
Table 4-1 Performance counter example
ID Name Description
67180678 VS.AMR.DL.RateUp Times of increasing the downlink

rate for adaptive multirate (AMR)
voice services in a cell
Common Performance Counter

Common performance counters, also known as raw 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 U2000 and stored in the U2000 performance
database. You can query the measurement results stored in the performance database.
You can clear common performance counters.

SingleRAN
Extended Performance Counter

Extended performance counters are also defined by NEs. These counters are not selected by
default.
You can select or clear extended performance counters when the U2000 is running.
l If you select such a counter, the measurement results of this counter are saved in the
performance database of the U2000. Then, the measurement results of this counter can
be queried.
l If you clear such a counter, the measurement results of this counter are not saved in the
performance database of the U2000. Then, the measurement results of this counter
cannot be queried.
User-defined Performance Counter

User-defined performance counters are customized by users on the U2000 client. The U2000
allows users to customize performance counters using the following method:
l Method 1: Perform arithmetic operations (add, subtract, multiply, and divide) on
common performance counters and extended performance counters.
User-defined performance counters include the KPIs defined by Huawei and those
defined by telecom operators. For details of the KPIs recommended by Huawei, see KPI
Reference in Huawei HedEx documentation package. The KPIs described in KPI
Reference are based on Huawei's experience in commercial network management and
radio network optimization. You can modify these KPIs or define new KPIs on the
U2000 as required.
l Method 2: Add filter criteria to base counters (common performance counters and
extended performance counters).
Counters that are defined by using this method are also called event-based counters
(EBCs). The common types of EBCs are as follows: accessibility, retainability, mobility,
delay, and cell resource. Each type includes multiple base counters. For example,
Number of RRC Connection Establishment Attempts (Excluding Duplicated
Attempts) is a base counter. You can set the Establishment Cause filter criterion to
RRC_EMERGENCY for this base counter and create an EBC to measure the number
of RRC connection establishment attempts in emergency calls. The default measurement
periods of EBCs do not map the supported measurement periods of base counters.
Currently, EBCs support only the 15-minute measurement period while base counters
support short and long measurement periods. For details of the short and long
measurement periods, see section 4.1.5 Measurement Period. EBC statistics are
collected on the U2000 based on the CHRs reported by NEs through filter criteria such
as access causes, failure causes, service characteristics, and operator IDs.
NOTE
l After you start a measurement task for user-defined performance counters on the U2000 client, the
U2000 automatically enables the measurement of common performance counters and extended
performance counters involved in the user-defined performance counters.
l eNodeBs support the EBC function as of eRAN3.0. RNCs support the EBC function as of RAN15.0.
The measurement period is 15 minutes.
4.1.2 Measurement Object

Object type indicates the various physical or logical entities that are measured, such as a base
station, an Ethernet port, and an RRC connection.

SingleRAN
Performance counters are measured for an object. Table 4-2 lists the example object types of
some NodeB performance counters.
Table 4-2 Object types for performance counters

Counter ID Counter Name Description Object
Type
50333220 VS.BTS.EnergyCons.Addin Total power consumption of NodeB

g all boards for a NodeB
1542455297 VS.FEGE.TxBytes Number of bytes successfully Ethernet

transmitted on the Ethernet port
port
1526726657 L.RRC.ConnReq.Msg Number of RRC Connection RRC

Request messages (including connection
retransmitted messages)
received in a cell
4.1.3 Function Subset

Function subsets are introduced to implement layered performance counter management.
Function subset indicates the effective combination of counters with the same attributes. For
example, hard handover measurement is a function subset. It is used to calculate the various
messages in the basic hard handover procedure from the perspective of a cell.
4.1.4 Function Set

A function set indicates a set of several function subsets with the same attributes. For
example, the function set Measurements related to Radio Access Bearer (RAB)
management consists of the following function subsets: Measurement of CS RAB
assignment modification per RNC, Measurement of CS RAB release per cell, and
Measurement of PS RAB assignment setup per RNC.
In the performance management system (U2000), multiple counters with the same
measurement purpose form a function subset, and multiple function subsets with the same
attribute form a function set. With these concepts, you can perform performance measurement
more conveniently and efficiently, and easily locate the required counter.
A performance counter belongs to only one function subset, and a function subset belongs to
only one function set. Figure 4-1 shows the relationships between object types, function sets,
function subsets, and performance counters.

SingleRAN
Figure 4-1 Relationships between object types, function sets, function subsets, and
performance counters
4.1.5 Measurement Period

Measurement period indicates the interval at which NEs report measurement results.
NEs report measurement results to the U2000 based on specified periods. The U2000
analyzes the results and then saves the results to the database. Therefore, you can query the
measurement result of the required period. The periods for reporting measurement results vary
according to performance counters and NE types. Table 4-3 lists the measurement periods
supported by NEs.
Table 4-3 Measurement periods supported by NEs

RAT NE Type Supported Measurement Default
Periods (Minute) Measurement
Period
(Minute)
GSM BSC6000 GSM 15, 60, and 1440 60

BSC6900 GSM 15, 60, and 1440 60
BSC6910 GSM
eGBTS 15 and 60 60
UMTS BSC6810 UMTS 5, 30, and 1440 30

BSC6900 UMTS 5, 30, and 1440 30
BSC6910 UMTS
NodeB 15 and 60 60
LTE eNodeB 15 and 60 60
SingleRA BSC6900 GU 15, 60, and 1440 60

N BSC6910 GU
3900 & 5900 15 and 60 60

series multimode
base stations

SingleRAN
NOTE
l Measurement periods are classified into short measurement periods (5- and 15-minute) and long
measurement periods (15-, 30-, and 60-minute). Note that the short and long measurement periods
cannot be set to 15 minutes concurrently.
l A maximum of 1000 counters in a 5-minute or 15-minute measurement period can be selected at a
time for an NE. This helps save storage space of the U2000.
4.2 Performance Counter Statistical Methods
4.2.1 Performance Counter Statistical Types

Table 4-4 describes the performance counter statistical types.
Table 4-4 Performance counter statistical types

Statistical Description Example
Type
SCAN Counts the number of sampling times in Sampling Times of PDCH

a statistical period. The accumulated Measurement
sample value increases by 1 at each time If the sampling interval is 5
when the number of sampling times is seconds and statistical period
increased by 1. The initial value is 0. is 30 minutes, the value of
this counter is 360.
ACC Obtains accumulated sample values in a Total Number of Sampled

statistical period. You can divide the Available PDCHs
accumulated sample values by the The value of this counter is
number of sampling times to obtain the the total number of PDCHs
average counter value. 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 Number of UEs in

dynamically increased or decreased. The CELL_DCH State for Cell
variable is of int or float type. After the
statistical period ends, the variable value
is the statistical result.
PEG The number of events is increased by 1 Number of Incoming Hard

each time. Handover Attempts for
Cell

SingleRAN
Statistical Description Example

Type
PDF Perform distribution statistics based on For Number of Times that

intervals. DL Throughput of HSDPA
Services Within Each
Range, interval distribution
for statistics is as follows:
[0]: 0 ≤ x < 32 kbit/s
[1]: 32 kbit/s ≤ x < 64 kbit/s
[2]: 64 kbit/s ≤ x < 256 kbit/s
[3]: 256 kbit/s ≤ x < 512
kbit/s
[13]: 12288 kbit/s ≤ x
4.2.2 Performance Counter Aggregation Types

Performance counter aggregation types indicate how to aggregate counter values by time or
by object on the U2000. Table 4-5 lists the aggregation types.
Table 4-5 Aggregation types

Aggregation Description Example
Type
SUM Sum of all samples. Number of bytes in the IP

packets received on the SCTP
MAX Maximum value of all samples. Maximum IP packet receive rate

on the SCTP
MIN Minimum value of all samples. Minimum IP packet receive rate

on the SCTP
AVG Average value of all samples. Average IP packet receive rate

on the SCTP
4.3 Counter-based Performance Measurement Process

After you set the performance counters, object types, and measurement periods for an NE on
the U2000, the NE reports the counter measurement results (performance data) to the U2000
when the measurement period begins. The mediation service of the U2000 server parses the
packets reported by NEs and converts them into data of a uniform format. The performance
service saves the data required by users to the performance database. Through the northbound
interface of the U2000, the NE performance data can be sent to the NMS for northbound users
to analyze.
Figure 4-2 shows the performance measurement process.

SingleRAN
Figure 4-2 Counter-based performance measurement process
The following table describes the basic process of counter-based U2000 performance
measurement.
No. Procedur Description

e
1 Register On the U2000 client, set the measurement counters, object types, and
measurem period, and deliver measurement tasks to the performance management
ent tasks (PM) mediation through the PM server.
2 Deliver The PM mediation delivers the measurement counters, object types,

measurem and period to NEs.
ent tasks
3 Generate The NEs generate the performance measurement results based on the
measurem measurement period.
ent results
4 Report The NEs report the performance measurement results to the U2000
measurem server.
ent results The protocol used by an NE to report the performance measurement
results is determined by NE attributes. Different NEs may use different
protocols to report performance measurement results.

SingleRAN
No. Procedur Description

e
5 Parse The PM mediation parses the performance measurement results.

measurem
ent results
6 Import The U2000 server saves the parsed performance measurement results
measurem to the performance database.
ent results
7 Query Users query reported performance measurement results through the

results on U2000 client.
the U2000
client
8 Export The performance data in the database can be exported to the NMS
performan through the U2000 northbound interface.
ce data The Nastar can use a data collection tool to obtain performance data
based on the IP address of the U2000 server, user name, password, and
the path for saving performance data.
The mAOS allows you to use the task management function to collect
data from the U2000, save the data in a file on the mAOS, and import
data in the file to the database as scheduled for subsequent query and
analysis.
Figure 4-3 EBC-based performance measurement process

SingleRAN
The following table describes the basic process of EBC-based U2000 performance
measurement.
No. Procedure Description
1 Register Users set and activate measurement counters on the U2000 client
measurement and deliver the counters to the EBC management module through
tasks the performance server.
2 Deliver CHR The EBC management module converts activated measurement

event counters into CHR events that need to be subscribed to, and
measurement delivers the events to eNodeBs (through the Trace Server) and
tasks RNCs.
3 Deliver The EBC management module delivers counter-defined script

counter- files to the Trace Server and SAU for counter pre-calculation.
defined script
files
4 Report CHR eNodeBs and RNCs report CHR files to which the EBC
files subscribes to the Trace Server and SAU.
4 Calculate The Trace Server and SAU use the counter-defined script files to
counters process CHR files and generate counter statistical results.
5 Generate result The Trace Server and SAU report counter pre-calculation results
files to the EBC export module which then generates counter result
files.
6 Query counters The mAOS collects counter result files generated by the EBC
export module as scheduled, parses the files, and saves the files to
the database for you to query on the client.
7 Export The northbound module converts the counter results files

performance generated by the EBC export module into northbound counter
data result files in XML format for the NMS to use.
4.4 Performance Counter Help Documents

Detailed information about performance indicator definitions and calculation formulas of the
NEs are described in the performance counter reference released with the NE software.
Content in performance counter reference is organized by object type. Figure 4-4 uses
BSC6900 GSM Performance Counter Reference as an example.
Figure 4-4 Content organization

SingleRAN
4.5 Northbound Interface
4.5.1 Northbound Interface Overview

The northbound interface is an interface between the Element Management System (EMS)
and the NMS, as shown in Figure 4-5. The U2000 in the following figure is the EMS.
Figure 4-5 Position of the northbound interface
The U2000 opens the northbound interface for performance files to support the capability of
integrating with the NMS manufactured by a third party. It is recommended that the
northbound interface for performance files adopt the XML format, which is defined by 3GPP
protocols for performance measurement result files. File export delay through this interface is
short and the U2000 is least affected.
The file interface can periodically export performance data from the database to files based on
preset export criteria. The NMS can obtain the exported performance files from a specified
path on the U2000 by using the FTP/SFTP. If the NMS provides the IP address of a server and
specifies a path on the server, the U2000 can upload files to the path on the server.
For details of the northbound performance file interface, see U2000 Northbound Performance
File Interface Developer Guide (NE-Based).
4.5.2 Recommended Interconnection Solution

For Huawei NEs, a counter ID uniquely identifies a counter and does not change according to
NE versions.
If counter IDs meet the interconnection requirements, you are advised to interconnect the
NMS with the U2000 based on counter IDs to reduce the impact of counter name difference
on the NMS.
Counter names are longer that counter IDs and may vary based on NE versions.

SingleRAN
NOTE
If counter names are used to interconnect the U2000 with the NMS, the size of a performance result file
on the northbound interface is large, which affects file transfer and parsing efficiency.
4.5.3 Related Documents

When interconnecting the NMS manufactured by a third party through the northbound
interface, you can refer to the following documents:
l U2000 Northbound Performance File Interface Developer Guide (NE-Based)
This document is released with the U2000 software. This document is intended to
provide the guidance on how to interconnect the NMS manufactured by a third party
with the U2000 through the northbound performance file interface. This document
includes the mechanism of the performance file interface, performance file format, and
user commissioning guide.
l Performance Counter List
This document is released with the NE mediation. It includes the definition of counters
supported by the NE of the relevant version and the format of counter objects.
l NE Performance Counter Changes
This document is released with the NE software. It includes the counter change between
the current NE version and earlier versions. You must modify the counters in the NMS
according to this document before NMS upgrade. For any counter change problem,
contact the onsite engineers.
4.6 Schemes for Adding or Deleting Performance Counters

and Object Type Parameters
In normal cases, performance counters are added in a new version for the following reasons:
l New features are introduced.
l Original features and statistical processes are optimized.
Performance counters may be deleted for the following reasons:
l The performance counters are no longer used (related algorithms are changed or the
performance counter design is optimized) or will be replaced by other performance
counters due to feature changes.
l Object types for the performance counters are deleted due to hardware, function, or
feature changes.
In addition, some parameters of an object type may be deleted or replaced by other parameters
after configuration model optimization. Adding or deleting performance counters and object
type parameters has impact on northbound interface interconnection.
Therefore, performance counters and object type parameters to be deleted will be reserved for
two NE versions: the current version and the later version. Table 4-6 describes the schemes
for deleting performance counters and object type parameters.

SingleRAN
Table 4-6 Schemes for deleting performance counters and object type parameters
Scenario Scheme (N-N+1) Scheme (N
+2)
Old performance l Old performance counters are reserved, and Old

counters are statistics about these performance counters are performance
replaced by new reported properly or are null values. counters are
performance l Statistics about new performance counters are deleted.
counters. reported properly.
Old performance Old performance counters are reserved, and statistics Old
counters are about these performance counters are reported performance
deleted. properly or are null values. counters are
deleted.
Old object type l Old object type parameters are reserved and Old
parameters are reported. The parameter value validity depends on performance
deleted or replaced the validity of values for the corresponding counters are
by other parameters in the configuration model. deleted.
parameters due to l New object type parameters are reported properly.
configuration
model
optimization.
Table 4-7 lists the documents containing information about deleted performance counters and
object type parameters.
Table 4-7 Documents containing information about disused performance counters and object
type parameters
Document Name Description
Disuse Performance This document is released with the NE software and describes all
Counter List deleted counters, and counters and object types to be deleted in this
version. It also provides disuse statements that describe the
schemes and reasons for deleting these counters or object types.
Performance Disuse statements describing the schemes for deleting performance

Counter Reference counters are provided in the Description field. This document is y
into the NE HedEx documentation package.

SingleRAN
Performance Management Feature Parameter Description 5 Related Features
5 Related Features
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None

SingleRAN
Performance Management Feature Parameter Description 6 Network Impact
6 Network Impact
System Capacity
No impact.
Network Performance
No impact.

SingleRAN
Performance Management Feature Parameter Description 7 Parameters
7 Parameters
There are no specific parameters associated with this feature.

SingleRAN
Performance Management Feature Parameter Description 8 Counters
8 Counters
There are no specific counters associated with this feature.

SingleRAN
Performance Management Feature Parameter Description 9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

SingleRAN
Performance Management Feature Parameter Description 10 Reference Documents
10 Reference Documents
1. BSC6900 GSM Performance Counter Reference

2. BSC6910 GSM Performance Counter Reference
3. GSM KPI Reference
4. BSC6900 UMTS Performance Counter Reference
5. BSC6910 UMTS Performance Counter Reference
6. WCDMA KPI Reference
7. eNodeB KPI Reference
8. 3900 & 5900 Series Base Station Performance Counter Reference
9. U2000 Performance Measurement Management User Guide
10. U2000 Performance Report Management User Guide
11. U2000 Northbound Configuration File Interface Developer Guide

Performance Management (SRAN13.1 - 01)

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Performance Management (SRAN13.1 - 01)

Caricato da

Copyright:

Formati disponibili

SingleRAN

Performance Management Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. i

3 Overview of Performance Management................................................................................... 4

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. ii

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. iii

SRAN13.1 Draft A (2018-01-15)

Change Change Description Paramete

Technical Converged iManager PRS, iManager SONMaster, and None

Editorial Added a note of not reporting performance counter None

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. 1

2 About This Document

2.1 Applicable RAT

2.2 Features in This Document

Feature ID Feature Name Section

MRFD-210302 Performance Management 3 Overview of

TDLBFD-004008 Performance Management

MLBFD-12000408 Performance Management

FBFD-010025 Basic O&M Package 3 Overview of

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. 2

2.3 Differences Between Base Station Types

MRFD-210302 Performance Yes Yes Yes

LBFD-004008 Performance Yes Yes Yes

TDLBFD-004008 Performance Yes Yes Yes

MLBFD-12000408 Performance Yes Yes Yes

Among micro base stations, only the BTS3911E/BTS3912E supports NB-IoT.

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. 3

3 Overview of Performance Management

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. 4

Figure 3-1 Performance management architecture

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. 5

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. 6

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. 7

4.1 Basic Concepts

4.1.1 Performance Counter

Table 4-1 Performance counter example

67180678 VS.AMR.DL.RateUp Times of increasing the downlink

Common Performance Counter

You can clear common performance counters.

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. 8

Extended Performance Counter

User-defined Performance Counter

4.1.2 Measurement Object

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. 9

Table 4-2 Object types for performance counters

50333220 VS.BTS.EnergyCons.Addin Total power consumption of NodeB

1542455297 VS.FEGE.TxBytes Number of bytes successfully Ethernet

1526726657 L.RRC.ConnReq.Msg Number of RRC Connection RRC

4.1.3 Function Subset

4.1.4 Function Set

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. 10

4.1.5 Measurement Period

Table 4-3 Measurement periods supported by NEs

GSM BSC6000 GSM 15, 60, and 1440 60

UMTS BSC6810 UMTS 5, 30, and 1440 30

LTE eNodeB 15 and 60 60

SingleRA BSC6900 GU 15, 60, and 1440 60

3900 & 5900 15 and 60 60

Issue 01 (2018-04-10) Copyright © Huawei Technologies Co., Ltd. 11

4.2 Performance Counter Statistical Methods