eNodeB KPI Reference

eNodeB V100R003C00SPC470
KPI Reference
Issue Date
03 2012-02-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 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: Email: http://www.huawei.com support@huawei.com
Issue 03 (2012-02-28)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
eNodeB KPI Reference
About This Document
About This Document

Intended Audience
This document is intended for:

Network planners Network administrators Network operators
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.
Changes in Issue 03 (2012-02-28)

This is the third commercial release. Compared with Issue 02(2011-11-25), 03 (2012-02-28) incorporates no changes.

This is the sencond commercial release. Compared with Issue 01 (2011-09-30), 02 (2011-11-25) incorporates no changes.

This is the first commercial release. Compared with Issue Draft (2011-01-20), 01 (2011-09-30) incorporates no changes.
Changes in Issue Draft (2011-01-20)

Initial field draft release. Compared with Issue 02 (2010-07-30), changes in Issue Draft (2011-01-20) incorporates changes as follows: The content in the third column of Table 11-1 is modified.
Issue 03 (2012-02-28)
ii
Contents
Contents
About This Document .................................................................................................................... ii 1 Overview......................................................................................................................................... 1 2 Template for KPI Definition ...................................................................................................... 2 3 Accessibility KPIs ......................................................................................................................... 3
3.1 RRC Setup Success Rate (Service) .................................................................................................................. 3 3.1.1 Description .............................................................................................................................................. 3 3.1.2 Definition ................................................................................................................................................ 4 3.2 RRC Setup Success Rate (Signaling) ............................................................................................................... 4 3.2.1 Description .............................................................................................................................................. 4 3.2.2 Definition ................................................................................................................................................ 5 3.3 ERAB Setup Success Rate (VoIP).................................................................................................................... 5 3.3.1 Description .............................................................................................................................................. 5 3.3.2 Definition ................................................................................................................................................ 7 3.4 ERAB Setup Success Rate (All) ...................................................................................................................... 7 3.4.1 Description .............................................................................................................................................. 7 3.4.2 Definition ................................................................................................................................................ 7
4 Retainability KPIs ......................................................................................................................... 9

4.1 Call Drop Rate (VoIP) ...................................................................................................................................... 9 4.1.1 Description .............................................................................................................................................. 9 4.1.2 Definition .............................................................................................................................................. 10 4.2 Service Drop Rate (All).................................................................................................................................. 11 4.2.1 Description ............................................................................................................................................ 11 4.2.2 Definition .............................................................................................................................................. 11
5 Mobility KPIs............................................................................................................................... 12
5.1 Intra-frequency Handover Out Success Rate ................................................................................................. 12 5.1.1 Description ............................................................................................................................................ 12 5.1.2 Definition .............................................................................................................................................. 14 5.2 Inter-frequency Handover Out Success Rate.................................................................................................. 14 5.2.1 Description ............................................................................................................................................ 15 5.2.2 Definition .............................................................................................................................................. 15 5.3 Handover In Success Rate .............................................................................................................................. 15 Issue 03 (2012-02-28) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
Contents
5.3.1 Description ............................................................................................................................................ 15 5.3.2 Definition .............................................................................................................................................. 17 5.4 Inter-RAT Handover Out Success Rate (LTE to CDMA)............................................................................... 17 5.4.1 Description ............................................................................................................................................ 17 5.4.2 Definition .............................................................................................................................................. 18 5.5 Inter-RAT Handover Out Success Rate (LTE to WCDMA) ........................................................................... 19 5.5.1 Description ............................................................................................................................................ 19 5.5.2 Definition .............................................................................................................................................. 20 5.6 Inter-RAT Handover Out Success Rate (LTE to GSM) .................................................................................. 20 5.6.1 Description ............................................................................................................................................ 20 5.6.2 Definition .............................................................................................................................................. 21
6 Service Integrity KPIs ................................................................................................................ 22

6.1 Service Downlink Average Throughput ......................................................................................................... 22 6.1.1 Description ............................................................................................................................................ 22 6.1.2 Definition .............................................................................................................................................. 22 6.2 Service Uplink Average Throughput .............................................................................................................. 23 6.2.1 Description ............................................................................................................................................ 23 6.2.2 Definition .............................................................................................................................................. 23
7 Utilization KPIs ........................................................................................................................... 25

7.1 Resource Block Utilizing Rate ....................................................................................................................... 25 7.1.1 Description ............................................................................................................................................ 25 7.1.2 Definition .............................................................................................................................................. 25 7.2 Average CPU Load ......................................................................................................................................... 26 7.2.1 Description ............................................................................................................................................ 26 7.2.2 Definition .............................................................................................................................................. 26
8 Availability KPIs ......................................................................................................................... 27

8.1 Radio Network Unavailability Rate ............................................................................................................... 27 8.1.1 Description ............................................................................................................................................ 27 8.1.2 Definition .............................................................................................................................................. 27
9 Traffic KPIs .................................................................................................................................. 28

9.1 Radio Bearers ................................................................................................................................................. 28 9.1.1 Description ............................................................................................................................................ 28 9.1.2 Definition .............................................................................................................................................. 28 9.2 Downlink Traffic Volume ............................................................................................................................... 29 9.2.1 Description ............................................................................................................................................ 29 9.2.2 Definition .............................................................................................................................................. 29 9.3 Uplink Traffic Volume .................................................................................................................................... 30 9.3.1 Description ............................................................................................................................................ 30 9.3.2 Definition .............................................................................................................................................. 30
10 References................................................................................................................................... 32
Issue 03 (2012-02-28) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iv
Contents
11 Counter List ................................................................................................................................ 33
Issue 03 (2012-02-28)
1 Overview
Overview
With the initial target of downlink peak data rate reaching above 100 Mbit/s, the next-generation Long Term Evolution (LTE) system is developed to meet the increasing demands on higher data rate due to fast expansion of multimedia applications. For a new wireless system like the LTE, a set of Key Performance Indicators (KPIs) are defined for the evaluation of system performance, in particular the performance of the evolved Radio Access Network (eRAN). The comparison between the LTE and the legacy systems such as UMTS or CDMA2000 system is also specified in this document. This document specifies a set of eRAN KPIs to evaluate the performance of the LTE system. Some counters necessary for the KPI calculation are also described in details. Given that the LTE is a new system, the KPIs in this document are drafted ones and subject to change. KPIs should be updated according to the experiences of commercial network management and radio network optimization. The KPIs in this document are classified into categories based on the measurement targets: accessibility, retainability, mobility, service integrity, utilization, availability, and traffic KPIs. This document is organized as follows: firstly we briefly describe the KPI specification template. Then detailed specifications of each KPI are described in terms of the aforementioned seven categories. Finally we provide definitions of relevant counters in Chapter 11 Counter List.
Issue 03 (2012-02-28)
2 Template for KPI Definition
Template for KPI Definition
According to the template, the KPI is defined in terms of the following items. Each KPI has several sub-clauses. KPI name (clause header) It is a descriptive name of the KPI. Descriptions It provides a brief overview of the KPI.
Measurement scope It specifies the KPI monitoring scope. In general, the measurement is made in terms of cells. The KPI value reflects the performance in a cell or a cluster. The associated counters can be obtained from cell statistics. In this document, cluster indicates a group of cells selected by user.
Formula It is used to calculate the KPI. Generally the formula consists of several counters that are specified in other sub-clauses.
Associated counters It contains counters used in the formula. Chapter 11 Counter List provides the counter descriptions.
Issue 03 (2012-02-28)
3 Accessibility KPIs
3
3.1.1 Description
Accessibility KPIs
Accessibility KPIs are used to measure the probability whether services requested by a user can be accessed within specified tolerances in the given operating conditions. The service provided by the E-UTRAN is defined as EPS/ERABs. Radio Resource Control (RRC) connection and System Architecture Evolution (ERAB) setup are the main procedures for accessibility KPIs. The accessibility KPIs can be calculated per cell or cluster. The KPIs at the cluster level are calculated by aggregating all cell counters of the same cluster.
3.1 RRC Setup Success Rate (Service)

According to Reference[1], the RRC connection setup procedure is triggered by various different causes as identified by the establishmentCause field in RRCConnectionRequest message: emergency, highPriorityAccess, mt (Mobile terminating)-Access, mo (Mobile Originating)-Signaling, and mo-Data. The UE sets the establishmentCause in accordance with the information received from upper layers. Causes except mo-signaling are categorized as service-related ones. The mo-signaling cause is a signaling-related cause. This KPI evaluates the RRC setup success rate with service-related causes in a cell or cluster Involved. The KPI is calculated based on the counters measured at eNodeB when the eNodeB receives an RRC Connection Request from the UE, as shown in Figure 3-1. To illustrate the KPI calculation procedures, we briefly discuss how the related counters (number of RRC Connection setup attempts (service) and number of successful RRC setup (service)) are collected. The number of RRC Connection attempts is collected by the eNodeB at measurement point A and the number of successful RRC connection is counted at measurement point C. The related counters are discussed in Chapter 11 Counter List.
Issue 03 (2012-02-28)
Figure 3-1 Measurement point for RRC connection setup
3.1.2 Definition
The RRC setup success rate (service) KPI is defined in Table 3-1. Note that the number of RRC connection setup attempts (service) and the successful RRC connection setup times (service) is collected based on the descriptions in Section 3.1.1 . Table 3-1 RRC setup success rate (service) KPI Name Measurement Scope Formula RRC Setup Success Rate (service) Cell / Cluster
RRCS _ SRservice
RRCConnect ionSuccess service 100% RRCConnect ionAttempt service
Associated Counters Unit
See Chapter 11 Counter List.
Percentage (%)
3.2 RRC Setup Success Rate (Signaling)

3.2.1 Description
This KPI evaluates the RRC setup success rate of the signaling-related cause (mo-signaling) in a cell or a cluster. Like the RRC Setup Success Rate (service), this KPI is used to calculate the RRC setup success rate only when the establishmentCause field is set to mo-signaling in a cell or a cluster.
Issue 03 (2012-02-28) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4
3.2.2 Definition
The RRC setup success rate (signaling) KPI is defined in Table 3-2. Note that the RRC connection setup attempts (signaling) and the successful RRC connection setup counters (signaling) are collected based on the descriptions in Section 3.2.1 . Table 3-2 RRC setup success rate (signaling) KPI Name Measurement Scope Formula RRC Setup Success Rate (signaling) Cell / Cluster
RRCS _ SRother
RRCConnect ionSuccess other 100% RRCConnect ionAttempt other
Percentage (%)
3.3 ERAB Setup Success Rate (VoIP)

3.3.1 Description
This KPI is used to evaluate the ERAB setup success rate of the VoIP service in a cell or a cluster. The counters related to this KPI are measured when the eNodeB receives an ERAB Setup Request message or an Initial Context Setup Request message from the MME, as shown in Figure 3-2 according to Reference [2] and Reference [3]. The ERAB is part of the Evolved Packet Service (EPS) bearer. According to Reference [4], an ERAB is one or more Service Data Flows between UE and EPC. The ERAB identity remains unique for the UE even if the UE-associated logical S1-connection (S1 bearer) is released during periods of user inactivity. The ERAB consists of both ERAB radio bearer (between eNodeB and UE, same as the radio bear defined in the EPS bearer) and corresponding S1 bearer (between eNodeB and MME). Figure 3-2 and Figure 3-3 show two scenarios: MME-initiated ERAB setup (Scenario A) and UE-triggered ERAB setup (Scenario B). Scenario B is triggered by the radio bearer setup. Initial Context Setup Request messages are exchanged between eNodeB and MME. If the ERAB Setup Request message or Initial Context Setup Request message requires multiple ERAB setups at the same time, specific counters are incremented for each ERAB .
Issue 03 (2012-02-28)
Figure 3-2 Measurement point for MME-initiated ERAB setup
Figure 3-3 Measurement point for UE-triggered ERAB setup
Issue 03 (2012-02-28)
Number of ERAB Connection setup attempts is collected by the eNodeB at measurement point A and the number of successful ERAB connections is counted at measurement point B, as shown in Figure 3-2 and Figure 3-3. Note that the eNodeB needs to specify the Quality of Service (QoS) Class Identifier (QCI) for VoIP in the ERAB setup message. The voice service can be identified by the QoS information, in particular the QCI in the ERAB Setup Request message. In general, QCI 1 is assigned to the voice service.
3.3.2 Definition
The ERAB setup success rate (VoIP) KPI is defined in Table 3-3. Note that the ERAB setup attempts (VoIP) and the successful ERAB setup counters (VoIP) are collected based on the descriptions in Section 3.3.1 . Table 3-3 ERAB setup success rate (VoIP) KPI Name Measurement Scope Formula Associated Counters Unit Percentage (%) ERAB Setup Success Rate (VoIP) Cell / Cluster
VoIPERABS _ SR
VoIPERABSe tupSuccess 100% VoIPERABSe tupAttempt
3.4 ERAB Setup Success Rate (All)

3.4.1 Description
This KPI can be used to evaluate the ERAB setup success rate of all services including the VoIP service in a cell or a cluster. This KPI is calculated based on the counters (both the ERAB setup attempts (All) and the successful ERAB setup (All) counters) measured at the eNodeB as shown in Figure 3-2.
3.4.2 Definition
The ERAB setup success rate (All) KPI is defined in Table 3-4. The ERAB setup attempts (All) and the successful ERAB setup counters (All) are collected based on the descriptions in Section 3.4.1 .
Issue 03 (2012-02-28)
Table 3-4 ERAB setup success rate (all) KPI Name Measurement Scope Formula ERAB Setup Success Rate (All) Cell / Cluster
ERABS _ SR
ERABSetupS uccess 100% ERABSetupA ttempt
Percentage (%)
Issue 03 (2012-02-28)
4 Retainability KPIs
4
4.1 Call Drop Rate (VoIP)
4.1.1 Description
Retainability KPIs
Retainability KPIs are used to evaluate the network capability to retain services requested by a user for a desired duration once the user is connected to the services. These counters can be calculated per cell or per cluster. The KPIs at the cluster level can be calculated by aggregating all the cell counters. Retainability KPIs are important in evaluating whether the system can maintain the service quality at certain level.
This KPI can be used to evaluate the call drop rate of the VoIP service in a cell or a cluster. The call drop rate is calculated by monitoring the VoIP ERAB abnormal release rate. Each ERAB is associated with the QoS information. The voice service can be distinguished by the specific QCI = 1. ERAB includes both the ERAB radio bearer and corresponding S1 bearer. Any abnormal release on either bearer causes call drop and therefore is counted into the call drop rate. The abnormal release is identified by the CauseIE defined in Reference[3]. The Call Drop Rate (CDR) is defined as Abnormal ERAB release / All released ERAB. Note that there are two different procedures indicating the ERAB release: they are indicated through E-RAB Release Indication and UE Context Release Command as shown in Figure 4-1.
Issue 03 (2012-02-28)
Figure 4-1 Abnormal ERAB release
As shown in Figure 4-1, the abnormal ERAB release counter is incremented when the eNodeB sends an E-RAB Release Indication to the MME or receives an UE Context Release Command message from the MME and the release causes are not Normal Release, User Inactivity, Partial Handover, or Handover triggered. If the message contains several ERAB ID IEs (in the ERAB to Be Release List IE), the counter will be incremented for each individual ERAB. For the eNodeB-initiated abnormal ERAB release, the eNodeB knows whether it is a normal or abnormal ERAB release.
4.1.2 Definition
The call drop rate (VoIP) is defined in Table 4-1. Table 4-1 Call drop rate (VoIP) KPI Name Measurement Scope Formula Associated Counters Unit Percentage (%) Call Drop Rate (VoIP) Cell / Cluster
VoIP _ CDR
VoIPERABAb normal Re lease 100% VoIPERAB Re lease
See chapter 11 Counter List.
Issue 03 (2012-02-28)
10
4.2 Service Drop Rate (All)

4.2.1 Description
This KPI can be used to evaluate the call drop rate of all services in a cell or a cluster, including VoIP service. Similar to the KPI defined in Section 4.1 , this KPI measures abnormal release at the eNodeB.
4.2.2 Definition
Service drop rate (All) is defined in Table 4-2. Table 4-2 Service drop rate (all) KPI Name Measurement Scope Formula Service Drop Rate (All) Cell / Cluster
Service _ CDR
ERABAbnorm al Re lease 100% ERAB Re lease
Percentage (%)
Issue 03 (2012-02-28)
11
5 Mobility KPIs
5
5.1.1 Description
Mobility KPIs
Mobility KPIs are used to evaluate the performance of E-UTRAN mobility, which is critical to the customer experience. Several categories of mobility KPIs are defined based on the following handover types: intra-frequency, inter-frequency, and inter-Radio Access Technology (RAT).
5.1 Intra-frequency Handover Out Success Rate

This KPI can be used to evaluate the intra-frequency Handover out success rate in a cell or a cluster. The intra-frequency handover (HO) includes both inter-eNodeB and intra-eNodeB scenarios. To illustrate the KPI calculation, we briefly discuss how the related counters (number of intra-frequency HO attempts and number of successful intra-frequency HO attempts) are collected. Intra-eNodeB HO scenario is shown in Figure 5-1. The HO attempt counter is collected at point B. When the eNodeB sends an RRCConnectionReconfiguration message to the UE, it decides to perform a handover. The eNodeB counts the number of attempts to perform intra-eNodeB intra-frequency HO in the source cell. The success HO counters are collected at point C. The eNodeB counts the number of successful intra-eNodeB intra-frequency HOs in the source cell when the eNodeB receives the RRCConnectionReconfigurationComplete message from the UE.
Issue 03 (2012-02-28)
12
5 Mobility KPIs
Figure 5-1 Scenario for Intra-frequency Intra-eNB HO
Two scenarios are available for the inter-eNodeB HO, as shown Figure 5-2 and Figure 5-3. The HO attempts are collected at point B. When the Source-eNodeB (S-eNodeB) sends an RRCConnectionReconfiguration message to the UE, it decides to perform an inter-eNodeB HO. In this KPI, the source and target cells of the handover are at the same frequency. The number of inter-eNodeB intra-frequency HO attempts is measured at the source cell. The number of inter-eNodeB intra frequency success HOs is collected at point C as shown in Figure 5-2 and Figure 5-3. During a handover with the source and target cells at the same frequency, the number of successful inter-eNodeB intra-frequency HOs is measured in the source cell when the S-eNodeB receives a UE Context Release message from the Target-eNodeB (T-eNodeB) or a UE Context Release Command message from the MME, indicating that the UE access to the T-eNodeB is successful. Figure 5-2 Scenario A for intra-frequency inter-eNodeB HO
Issue 03 (2012-02-28)
13
5 Mobility KPIs
Figure 5-3 Scenario B for intra-frequency inter-eNodeB HO
5.1.2 Definition
The intra-frequency handover out success rate is defined in Table 5-1. Note that the HO attempts and the successful HO counters are collected based on the descriptions in Section 5.1.1 . Table 5-1 Intra-frequency handover out success rate KPI Name Measurement Scope Formula Associated Counters Unit Percentage (%)
IntraFreqHOOut _ SR IntraFreqHOOutSucces s 100% IntraFreqHOOutAttemp t
Intra-frequency Handover Out Success Rate Cell / Cluster
5.2 Inter-frequency Handover Out Success Rate

Similar to Intra-frequency Handover Out Success Rate, the target eNodeB and source eNodeB are at different frequencies.
Issue 03 (2012-02-28)
14
5 Mobility KPIs
5.2.1 Description
This KPI can be used to evaluate the inter-frequency handover out success rate in a cell or a cluster. Note that the measurement points for the associated counters are the same as those for the intra-frequency HO scenario described in 5.1.1 . The target LTE cell operates at the frequency different from that of the source LTE cell, which is the only difference. As shown in Figure 5-1, if the source and target cells at different frequencies are controlled by the same eNodeB, the eNodeB counts the number of intra-eNodeB inter-frequency HO attempts at point B and the successful intra-eNodeB inter-frequency HOs at point C in the source cell. As shown in Figure 5-2, if the handover source and target cells are at different frequencies, the eNodeB counts the number of inter-eNodeB inter-frequency HO attempts at point B and the successful intra-eNodeB inter-frequency HOs at point C in the source cell.
5.2.2 Definition
The inter-frequency handover out success rate is defined in Table 5-2. Note that the HO attempts and the successful HO counters are collected based on the descriptions in Section 5.2.1 . Table 5-2 Inter-frequency handover out success rate KPI Name Measurement Scope Formula Associated Counters Unit Percentage (%)
InterFreqHOOut _ SR InterFreqHOOutSucces s 100% InterFreqHOOutAttemp t
Inter-frequency Handover Out Success Rate Cell / Cluster
5.3 Handover In Success Rate

5.3.1 Description
This KPI can be used to evaluate the handover in success rate in a cell or a cluster. The HO includes both inter-eNodeB and intra-eNodeB scenarios. To illustrate the KPI calculation, we briefly discuss how related counters (number of HO attempts and number of successful HOs) are collected. Intra-eNodeB HO scenario is shown in Figure 5-4. The HO attempt counters are collected at point B. When the eNodeB sends an RRCConnectionReconfiguration message to the UE, it decides to perform a HO. The eNodeB counts the number of intra-eNodeB handover attempts in the target cell. The success HO counter is collected at point C. The eNodeB counts the number of successful intra-eNodeB HOs in the target cell when the eNodeB receives an RRCConnectionReconfigurationComplete message from the UE.
Issue 03 (2012-02-28)
15
5 Mobility KPIs
Figure 5-4 Intra-eNodeB HO
Two scenarios are available for the inter-eNodeB HO, as shown in Figure 5-5 and Figure 5-6. The HO attempts are collected at point B in the target cell when the T-eNodeB sends a Handover Request Acknowledge message to the S-eNodeB or the MME. The number of successful inter-eNodeB HOs is measured in the target cell at point C when the T-eNodeB receives an RRCConnectionReconfigurationComplete message from the UE. Figure 5-5 Scenario A for Inter-eNodeB HO
Issue 03 (2012-02-28)
16
5 Mobility KPIs
Figure 5-6 Scenario B for Inter-eNodeB HO
5.3.2 Definition
The Handover in success rate is defined in Table 5-3. Note that the HO attempts and the successful HO counters are collected based on the descriptions in Section 5.3.1 . Table 5-3 Handover in success rate KPI Name Measurement Scope Formula Associated Counters Unit Percentage (%)
HOIn _ SR HOInSucces s 100% HOInAttemp t
Handover In Success Rate Cell / Cluster
5.4 Inter-RAT Handover Out Success Rate (LTE to CDMA)

5.4.1 Description
This KPI can be used to evaluate the inter-RAT handover out success rate in a cell or a cluster. As suggested by the KPI name, this KPI measures the performance of the inter-RAT handover from LTE to CDMA. To illustrate the KPI calculation, we briefly discuss how the related
Issue 03 (2012-02-28)
17
5 Mobility KPIs
counters (number of inter-RAT HO from LTE to CDMA attempts and number of successful inter-RAT HOs) are collected. As shown in Figure 5-7, the measurement for inter-RAT HO from LTE to CDMA attempt is collected at point B where the eNodeB sends a MobilityFromEUTRACommand message to the UE and decides to perform a handover to the CDMA system. The measurement of successful inter-RAT HO (from LTE to CDMA) is performed at point C where the UE sends a UE Context Release Command message to the eNodeB through the MME after accessing the CDMA system. Figure 5-7 Inter-RAT handover (LTE to CDMA)
5.4.2 Definition
The inter-RAT handover out success rate (from LTE to CDMA) is defined in Table 5-4. Note that the inter-RAT HO attempts (from LTE to CDMA) and the successful inter-RAT HO (from LTE to CDMA) counters are collected based on the descriptions in Section 5.4.1 .
Issue 03 (2012-02-28)
18
5 Mobility KPIs
Table 5-4 Inter-RAT handover out success rate (LTE to CDMA) KPI Name Measurement Scope Formula Associated Counters Unit Percentage (%)
IRATHO _ L 2C _ SR IRATHO _ L2C _ Success 100% IRATHO _ L 2C _ Attempt
Inter-RAT Handover Out Success Rate (LTE to CDMA) Cell / Cluster
5.5 Inter-RAT Handover Out Success Rate (LTE to WCDMA)

5.5.1 Description
This KPI can be used to evaluate the inter-RAT handover out success rate in a cell or a cluster. As suggested by the name, this KPI measures the performance of the inter-RAT handover from LTE to WCDMA. To illustrate the KPI calculation, we briefly discuss how the related counters (number of inter-RAT HO (from LTE to WCDMA) attempts and number of successful inter-RAT HOs) are collected. As shown in Figure 5-8, the measurement for inter-RAT HO (LTE to WCDMA) attempt is collected at point B where the eNodeB sends a MobilityFromEUTRACommand message to the UE and decides to perform a handover to the WCDMA system. The measurement of successful inter-RAT HO (from LTE to WCDMA) is performed at point C where the UE sends a UE Context Release Command message to the eNodeB through the MME after accessing the WCDMA system.
Issue 03 (2012-02-28)
19
5 Mobility KPIs
Figure 5-8 Inter-RAT handover (LTE to WCDMA)
5.5.2 Definition
The inter-RAT Handover out success rate (LTE to WCDMA) is defined in Table 5-5. Note that the inter-RAT HO attempts (from LTE to WCDMA) and the successful inter-RAT HO (from LTE to WCDMA) counters are collected based on the descriptions in Section 5.5.1 . Table 5-5 Inter-RAT handover out success rate (LTE to WCDMA) KPI Name Measurement Scope Formula Associated Counters Unit Percentage (%)
IRATHO _ L 2W _ SR IRATHO _ L 2W _ Success 100% IRATHO _ L2W _ Attempt
Inter-RAT Handover Out Success Rate (LTE to WCDMA) Cell / Cluster
5.6 Inter-RAT Handover Out Success Rate (LTE to GSM)

5.6.1 Description
This KPI can be used to evaluate the inter-RAT handover out success rate in a cell or a cluster. As suggested by the name, this KPI measures the performance of the inter-RAT handover from LTE to GSM. To illustrate the KPI calculation, we briefly discuss how related counters
Issue 03 (2012-02-28) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20
5 Mobility KPIs
(number of inter-RAT HO (from LTE to GSM) attempts and number of successful inter-RAT HOs) are collected. As shown in Figure 5-8, the measurement for inter-RAT HO (LTE to GSM) attempt is collected at point B where the eNodeB sends a MobilityFromEUTRACommand message to the UE and decides to perform the handover to the GSM system. The measurement of successful inter-RAT HO (from LTE to GSM) is performed at point C where the UE sends a UE Context Release Command message to the eNodeB through the MME after accessing the GSM system.
5.6.2 Definition
The inter-RAT Handover out success rate KPI (LTE to GSM) is defined in Table 5-6. Note that the inter-RAT HO attempts (from LTE to GSM) and the successful inter-RAT HO (LTE to GSM) counters are collected based on the descriptions in Section 5.6.1 . Table 5-6 Inter-RAT handover out success rate (LTE to GSM) KPI Name Measurement Scope Formula
IRATHO _ L2G _ SR IRATHO _ L 2G _ Success 100% IRATHO _ L2G _ Attempt
Inter-RAT Handover Out Success Rate (LTE to GSM) Cell / Cluster
Percentage (%)
Issue 03 (2012-02-28)
21
6 Service Integrity KPIs
6
6.1.1 Description
Service Integrity KPIs
The service integrity KPIs indicate the E-UTRAN impacts on the service quality provided to the end-user. The service integrity KPIs can be calculated per cell or per cluster. The KPIs at the cluster level can be calculated by aggregating all the cell counters.
6.1 Service Downlink Average Throughput

This KPI consists of nine sub-KPIs that are mapped to nine QCIs. These sub-KPIs can be used to evaluate the busy-hour downlink (DL) throughput of a service with a specific QCI per user in each cell. It reflects the end-user experience.
6.1.2 Definition
The service downlink average throughput is defined in Table 6-1 and can refer to Reference [6] . There are nine different sub-KPIs for each QCI. The formulas for each KPI are mapped to corresponding counters.
Issue 03 (2012-02-28)
22
Table 6-1 Service DL average throughput KPI Name Measurement Scope Formula Service DL Average Throughput Cell / Cluster
DLAverageT hroughput_ QCI _ 1 DLAverageT hroughput_ QCI _ 2 DLAverageT hroughput_ QCI _ 3 DLAverageT hroughput_ QCI _ 4
DLAverageT hroughput_ QCI _ 5 DLAverageT hroughput_ QCI _ 6
DLAverageT hroughput_ QCI _ 7 DLAverageT hroughput_ QCI _ 8 DLAverageT hroughput_ QCI _ 9

Associated Counters Unit kbit/s See Chapter 11 Counter List.
6.2 Service Uplink Average Throughput

6.2.1 Description
This KPI consists of nine sub-KPIs that are mapped to nine QCIs. These sub-KPIs can be used to evaluate the busy hour uplink (UL) throughput of a service (with a specific QCI) per user in each cell. It reflects the end-user experience.
6.2.2 Definition
The service uplink average throughput is defined in Table 6-2. There are nine sub-KPIs for each QCI. The formula for each KPI is mapped to its corresponding counter.
Issue 03 (2012-02-28)
23
Table 6-2 Service UL average throughput KPI Name Measurement Scope Formula Service UL Average Throughput Cell / Cluster
ULAverageT hroughput_ QCI _ 1 ULAverageT hroughput_ QCI _ 2 ULAverageT hroughput_ QCI _ 3 ULAverageT hroughput_ QCI _ 4
ULAverageT hroughput_ QCI _ 5 ULAverageT hroughput_ QCI _ 6
ULAverageT hroughput_ QCI _ 7 ULAverageT hroughput_ QCI _ 8 ULAverageT hroughput_ QCI _ 9

Associated Counters Unit kbit/s See Chapter 11 Counter List.
Issue 03 (2012-02-28)
24
7 Utilization KPIs
7
7.1 Resource Block Utilizing Rate
7.1.1 Description
Utilization KPIs
Utilization KPIs are used to evaluate the capability to meet the traffic demand and other characteristics in specific internal conditions.
This KPI consists of two sub-KPIs: uplink resource block (RB) utilizing rate and downlink RB utilizing rate. These two sub-KPIs can be used to evaluate the busy-hour DL and UL RB utilizing rate in each cell or cluster.
7.1.2 Definition
The UL and DL RB utilizing rate KPIs are defined in Table 7-1. These two KPIs are calculated by dividing the total number of used RBs by the number of available RBs.
Issue 03 (2012-02-28)
25
7 Utilization KPIs
Table 7-1 RB utilizing rate KPI Name Measurement Scope Formula Resource Block Utilizing Rate Cell / Cluster
RB _ URDL
RB _ Used DL 100% RB _ Available DL
RB _ URUL
RB _ UsedUL 100% RB _ Available UL
NOTE The RB_AvailableDL and RB_AvailableUL are fixed values, which can be calculated through the system bandwidth.
Percentage (%)
7.2 Average CPU Load

7.2.1 Description
This KPI is used to evaluate the CPU usage in busy hours. It indicates the system loading.
7.2.2 Definition
The average CPU load is defined in Table 7-2. The CPU load is calculated by averaging the CPU usage ratio in the measurement period. Table 7-2 Average CPU load KPI Name Measurement Scope Formula Associated Counters Unit Percentage (%) Average CPU Load CPU
MeanCPUUti lity
Issue 03 (2012-02-28)
26
8 Availability KPIs
8
8.1.1 Description
Availability KPIs
Availability is the percentage of time that a cell is available. A cell is available when the eNodeB can provide EPS bearer services. Availability can be measured at the cell level for a variety of hardware/software faults..
8.1 Radio Network Unavailability Rate

This KPI provides the percentage of time of a cell in order to evaluate the degradation of the network performance caused by the unavailable cells in busy hours on the radio network.
8.1.2 Definition
The radio network unavailability rate is defined in Table 8-1. This KPI is calculated based on the time of all cell service unavailability on the radio network (cluster). Table 8-1 Radio network unavailability rate KPI Name Measurement Scope Formula
RAN _ Unavail _ Rate
Radio Network Unavailability Rate Radio network (cluster)
Cluster
CellUnavailTime 100%
TheTotalNu mberOfCellsInCluster *{SP} * 60
NOTE The "SP" indicates the report period of counters in minute.
Percentage (%)
Issue 03 (2012-02-28)
27
9 Traffic KPIs
9
9.1 Radio Bearers
9.1.1 Description
Traffic KPIs
Traffic KPIs are used to measure the traffic volume on the LTE Radio Access Network (RAN). Based on traffic types, the traffic KPIs are classified into the following categories: radio bearers, downlink traffic volume, and uplink traffic volume.
The radio bearers KPIs consist of nine sub-KPIs mapped to nine QCIs. This set of KPIs can be used to evaluate the average radio bearers in a cell or a cluster. The radio bearer for each QCI is based on the number of active RRC connections for each QCI according to the QCI defined in the QoS information.
9.1.2 Definition
The radio bearer KPIs are defined in Table 9-1, including nine different sub-KPIs specific to each QCI. The formulas for each KPI are mapped to corresponding counters.
Issue 03 (2012-02-28)
28
9 Traffic KPIs
Table 9-1 Radio bearers KPI Name Measurement Scope Formula Radio Bearers Cell / Cluster
RadioBeare rs _ QCI _ 1 RadioBeare rs _ QCI _ 2 RadioBeare rs _ QCI _ 3 RadioBeare rs _ QCI _ 4

RadioBeare rs _ QCI _ 5 RadioBeare rs _ QCI _ 6
RadioBeare rs _ QCI _ 7 RadioBeare rs _ QCI _ 8 RadioBeare rs _ QCI _ 9

Associated Counters See Chapter 11 Counter List.
9.2 Downlink Traffic Volume

9.2.1 Description
Similar to the radio bearers KPIs, the downlink traffic volume KPIs consist of nine sub-KPIs mapped to nine QCIs. This group of KPIs can be used to evaluate the DL traffic volume for each QCI in a cell, which is measured at the RLC layer excluding the RLC header and RLC retransmission.
9.2.2 Definition
The downlink traffic volume KPIs are defined in Table 9-2. Nine sub-KPIs are mapped to each QCI. The formulas for each KPI are mapped to corresponding counters.
Issue 03 (2012-02-28)
29
9 Traffic KPIs
Table 9-2 DL traffic volume KPI Name Measurement Scope Formula DL Traffic Volume Cell / Cluster
DLTrafficVolume_ QCI _ 1 DLTrafficVolume_ QCI _ 2
DLTrafficVolume_ QCI _ 3
Associated Counters Unit Bit See Chapter 11 Counter List.
9.3 Uplink Traffic Volume

9.3.1 Description
Similar to the downlink traffic volume KPIs, the uplink traffic volume KPIs consist of nine sub-KPIs mapped to nine QCIs. This group of KPIs can be used to evaluate the uplink traffic volume for each QCI in a cell. The KPIs are measured at the RLC layer excluding the RLC header and RLC retransmission.
9.3.2 Definition
The uplink traffic volume KPIs are defined in Table 9-3, including nine sub-KPIs mapped to each QCI. The formulas for each KPI are mapped to corresponding counters.
Issue 03 (2012-02-28)
30
9 Traffic KPIs
Table 9-3 UL traffic volume KPI Name Measurement Scope Formula UL Traffic Volume Cell / Cluster
ULTrafficVolume_ QCI _ 1 ULTrafficVolume_ QCI _ 2
ULTrafficVolume_ QCI _ 3
Associated Counters Unit Bit See Chapter 11 Counter List.
Issue 03 (2012-02-28)
31
10 References
10
References
[1] 3rd Generation Partnership Project (3GPP), "Evolved Universal Terrestrial Radio Access (E-UTRA), Radio Resource Control (RRC); Protocol Specification, (Release 8)", TS36.331 v8.3.0, September 2008. [2] 3rd Generation Partnership Project (3GPP), "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)", TS36.300 v8.6.0, September 2008. [3] 3rd Generation Partnership Project (3GPP), "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 8)", TS36.413 v8.3.0, September 2008. [4] 3rd Generation Partnership Project (3GPP), "Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 8)", TS23.401 v8.4.0, December 2008. [5] 3rd Generation Partnership Project (3GPP), "Technical Specification Group Services and System Aspects: Policy and charging control architecture (Release 8)", TS23.203 v8.3.1, September 2008. [6] eNodeB Performance Counter Reference.
Issue 03 (2012-02-28)
32
11 Counter List
11
Table 11-1 KPI-related counter list KPI RRC Setup Success Rate (Service) Parameter in KPI Formula RRCConnectionAtte mptservice
Counter List
Table 11-1 provides a counter list including all counters relevant to the KPI calculation. In each KPI specification, one or several parameters are used to calculate the KPI as shown in the KPI formula. Each parameter is mapped to a counter. For details on each counter, see the Reference [6]. Note that only QCI 1 is for VoIP service (conversational voice). According to Table6.1.7 in Reference [5], QCI 7 can also be assigned to non-conversational voice. In this document, QCI 7 is not considered as the VoIP service in the KPI calculation.
Mapped Counters (Described in the Reference [6]) L.RRC.ConnReq.Att.Emc + L.RRC.ConnReq.Att.HighPri + L.RRC.ConnReq.Att.Mt + L.RRC.ConnReq.Att.MoData L.RRC.ConnReq.Succ.Emc + L.RRC.ConnReq.Succ.HighPri + L.RRC.ConnReq.Succ.Mt + L.RRC.ConnReq.Succ.MoData L.RRC.ConnReq.Att.MoSig L.RRC.ConnReq.Succ.MoSig L.E-RAB.AttEst.QCI.1 L.E-RAB.SuccEst.QCI.1 L.E-RAB.AttEst L.E-RAB.SuccEst L.E-RAB.AbnormRel.QCI.1
RRCConnectionSucc essservice
RRC Setup Success Rate (Signaling)
RRCConnectionAtte mptother RRCCommectionSuc cessother
ERAB Setup Success Rate (VoIP)
VoIPERABSetupAtt empt VoIPERABSetupSuc cess
ERAB Setup Success Rate (All) Call Drop Rate (VoIP)
ERABSetupAttempt ERABSetupSuccess VoIPERABAbnorma lRelease
Issue 03 (2012-02-28)
33
11 Counter List
KPI
Parameter in KPI Formula VoIPERABRelease
Mapped Counters (Described in the Reference [6]) L.E-RAB.AbnormRel.QCI.1 + L.E-RAB.NormRel.QCI.1
Service Drop Rate (ALL)
ERABAbnromalRele ase ERABRelease
L.E-RAB.AbnormRel L.E-RAB.AbnormRel + L.E-RAB.NormRel L.HHO.IntraeNB.IntraFreq.ExecAttOut + L.HHO.IntereNB.IntraFreq.ExecAttOut L.HHO.IntraeNB.IntraFreq.ExecSuccO ut + L.HHO.IntereNB.IntraFreq.ExecSuccO ut L.HHO.IntraeNB.InterFreq.ExecAttOut + L.HHO.IntereNB.InterFreq.ExecAttOut L.HHO.IntraeNB.InterFreq.ExecSuccO ut + L.HHO.IntereNB.InterFreq.ExecSuccO ut L.HHO.IntraeNB.ExecAttIn + L.HHO.IntereNB.ExecAttIn
Intra-frequency Handover Out Success Rate
IntraFreqHOOutAtte mpt IntraFreqHOOutSucc ess
Inter-frequency Handover Out Success Rate
InterFreqHOOutAtte mpt InterFreqHOOutSucc ess
Handover In Success Rate
HOInAttempt
HOInSuccess Inter-RAT Handover Out Success Rate (LTE to CDMA) IRATHO_L2C_Atte mpt IRATHO_L2C_Succ ess IRATHO_L2W_Atte mpt IRATHO_L2W_Suc cess IRATHO_L2G_Atte mpt IRATHO_L2G_Succ ess DLAverageThroughp ut_QCI_n
L.HHO.IntraeNB.ExecSuccIn + L.HHO.IntereNB.ExecSuccIn L.IRATHO.E2C.ExecAttOut L.IRATHO.E2C.ExecSuccOut L.IRATHO.E2W.ExecAttOut L.IRATHO.E2W.ExecSuccOut L.IRATHO.E2G.ExecAttOut L.IRATHO.E2G.ExecSuccOut L.Thrp.bits.DL.QCI.1 / L.Thrp.Time.DL.QCI.1
Inter-RAT Handover Out Success Rate (LTE to WCDMA)
Inter-RAT Handover Out Success Rate (LTE to GSM)
Service DL Average Throughput
Issue 03 (2012-02-28)
34
11 Counter List
KPI
Parameter in KPI Formula
Mapped Counters (Described in the Reference [6]) L.Thrp.bits.DL.QCI.2 / L.Thrp.Time.DL.QCI.2 L.Thrp.bits.DL.QCI.3 / L.Thrp.Time.DL.QCI.3 L.Thrp.bits.DL.QCI.4 / L.Thrp.Time.DL.QCI.4 L.Thrp.bits.DL.QCI.5 / L.Thrp.Time.DL.QCI.5 L.Thrp.bits.DL.QCI.6 / L.Thrp.Time.DL.QCI.6 L.Thrp.bits.DL.QCI.7 / L.Thrp.Time.DL.QCI.7 L.Thrp.bits.DL.QCI.8 / L.Thrp.Time.DL.QCI.8 L.Thrp.bits.DL.QCI.9 / L.Thrp.Time.DL.QCI.9
Service UL Average Throughput
ULAverageThroughp ut_QCI_n
L.Thrp.bits.UL.QCI.1 / L.Thrp.Time.UL.QCI.1 L.Thrp.bits.UL.QCI.2 / L.Thrp.Time.UL.QCI.2 L.Thrp.bits.UL.QCI.3 / L.Thrp.Time.UL.QCI.3 L.Thrp.bits.UL.QCI.4 / L.Thrp.Time.UL.QCI.4 L.Thrp.bits.UL.QCI.5 / L.Thrp.Time.UL.QCI.5 L.Thrp.bits.UL.QCI.6 / L.Thrp.Time.UL.QCI.6 L.Thrp.bits.UL.QCI.7 / L.Thrp.Time.UL.QCI.7 L.Thrp.bits.UL.QCI.8 / L.Thrp.Time.UL.QCI.8 L.Thrp.bits.UL.QCI.9 / L.Thrp.Time.UL.QCI.9
Resource Block Utilizing Rate Average CPU Load
RB_UsedDL RB_UsedUL MeanCPUUtility
L.ChMeas.PRB.DL.Used.Avg L.ChMeas.PRB.UL.Used.Avg L.Board.CPU.MeanProcessorUsage
Issue 03 (2012-02-28)
35
11 Counter List
KPI Radio Network Unavailability Rate Radio Bearers
Parameter in KPI Formula CellUnavailTime RadioBearers_QCI_n
Mapped Counters (Described in the Reference [6]) L.Cell.Unavail.Dur.Sys + L.Cell.Unavail.Dur.Manual L.Traffic.DRB.QCI.1 L.Traffic.DRB.QCI.2 L.Traffic.DRB.QCI.3 L.Traffic.DRB.QCI.4 L.Traffic.DRB.QCI.5 L.Traffic.DRB.QCI.6 L.Traffic.DRB.QCI.7 L.Traffic.DRB.QCI.8 L.Traffic.DRB.QCI.9
DL Traffic Volume
DLTrafficVolume_Q CI_n
L.Thrp.bits.DL.QCI.1 L.Thrp.bits.DL.QCI.2 L.Thrp.bits.DL.QCI.3 L.Thrp.bits.DL.QCI.4 L.Thrp.bits.DL.QCI.5 L.Thrp.bits.DL.QCI.6 L.Thrp.bits.DL.QCI.7 L.Thrp.bits.DL.QCI.8 L.Thrp.bits.DL.QCI.9
UL Traffic Volume
ULTrafficVolume_Q CI_n
L.Thrp.bits.UL.QCI.1 L.Thrp.bits.UL.QCI.2 L.Thrp.bits.UL.QCI.3 L.Thrp.bits.UL.QCI.4 L.Thrp.bits.UL.QCI.5 L.Thrp.bits.UL.QCI.6 L.Thrp.bits.UL.QCI.7 L.Thrp.bits.UL.QCI.8 L.Thrp.bits.UL.QCI.9
Issue 03 (2012-02-28)
36

eNodeB KPI Reference

Uploaded by

Copyright:

Available Formats

eNodeB KPI Reference

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

eNodeB KPI Reference

Uploaded by

Copyright:

Available Formats

eNodeB V100R003C00SPC470

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.