TDD LTE KPI Optimization Guide

TDD LTE KPI Guide_R1.
4
TDD LTE KPI Guide_R1.4 Internal Use Only▲
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do
not agree to the following terms, please notice that you are not allowed to use this document.
Copyright © 2018 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure of this document or any portion of this document, in any form by any
means, without the prior written consent of ZTE CORPORATION is prohibited.
and are registered trademarks of ZTE CORPORATION. ZTE's company name, logo
and product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be trademarks or trade
names of their respective owners. Without the prior written consent of ZTE CORPORATION or the
third party owner thereof, anyone's access to this document should not be construed as granting, by
implication, estopped or otherwise, any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual, relevant
contract or laws and regulations in relevant country (countries).
This document is provided "as is" and "as available". Information contained in this document is subject
to continuous update without further notice due to improvement and update of ZTE CORPORATION's
products and technologies.
ZTE CORPORATION
Address: NO. 55
Hi-tech Road South
Shenzhen
P.R.China
518057
Website: http://support.zte.com.cn
Email: doc@zte.com.cn
ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. I

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. II

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. III
Revision History
Document
Product Version Serial Number Reason for Revision
Version
eNodeB:
TD-LTE_V2.00.020h.0215
This is the initial release.
EMS:V2.00.020h_0215
OMC:V2.00.020h_0215
For the KPI formulas, serial
numbers to version 030 counters
and version 031 counters are
V2.00.030 series
added;
V2.00.031 series
in addition, the definitions of the
traffic flow related indicators are
modified.
The KPI calculation formulas are
V2.00.041 series modified according to the new
product version.
Author
Document
Date Prepared by Reviewed by Approved by
Version
2009-09-09 R1.0
2010-02-28 R1.1
2010-04-15 R1.2 Shen Ting
2010-09-20 R1.3 Shen Ting
2012-05-03 R1.4 Shen Ting
ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. IV

Intended Audience: TDD LTE network planning and optimization engineers
Proposal: Before reading this document, you had better have the following knowledge and skills.
SEQ Knowledge and Skills Reference Material
1 Basic LTE theories LTE Basics and Key Technologies
Basic LTE signaling process and
2 TD-LTE Signaling Process
its meaning
Follow-up document: After reading this document, you may need the following information:
SEQ Reference Material Information
LTE Radio Parameter This guide describes the basic parameters and the
1
Configuration Guide modification suggestions.
This guide involves several parts: engineering
LTE Engineering Optimization
2 optimization workflow and FAQ analysis that includes
Guide (Being developed)
access subject, switch subject, and call-drop subject.
ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. V

About This Document
Summary
Chapter Description
1 Overview This chapter briefs the purpose of this KPI guide.
It also defines and describes the KPIs in different categories.
2 Radio Network KPIs This chapter provides the detailed interpretation of the KPIs in
different categories.
ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. VI

TABLE OF CONTENTS
1 Overview .............................................................................................................. 1
1.1 Purpose ................................................................................................................. 1
1.2 Terms and Abbreviations ...................................................................................... 1
1.3 Conventions .......................................................................................................... 1
2 Radio Network KPIs............................................................................................ 3

2.1 Coverage KPIs ..................................................... Error! Bookmark not defined.
2.1.1 RSRP ................................................................... Error! Bookmark not defined.
2.1.2 RS-CINR .............................................................. Error! Bookmark not defined.
2.1.3 Coverage Rate ..................................................... Error! Bookmark not defined.
2.2 Call Setup Related Indicators ............................................................................... 3
2.2.1 RRC Connection Setup Success Rate (Service Related) ................................... 4
2.2.2 RRC Connection Setup Success Rate ................................................................. 5
2.2.3 E-RAB Setup Success Rate ................................................................................. 8
2.2.4 Successful Air Interface Connection Rate.......................................................... 12
2.2.5 E-RAB Setup Congestion Rate .......................................................................... 14
2.3 Call Retainability Related Indicators................................................................... 18
2.3.1 Call-Drop Rate Caused by Faulty RRC Releases ............................................. 18
2.3.2 Call-Drop Rate Caused by Faulty E-RAB Releases .......................................... 20
2.4 Mobility Management Related Indicators ........................................................... 22
2.4.1 Intra-RAT Handover............................................................................................ 25
2.4.2 Inter-RAT Handover............................................................................................ 31
2.5 Quality Related Indicators .................................................................................. 36
2.5.1 Attach Latency .................................................................................................... 36
2.5.2 State Switch Latency from Idle to Active ............................................................ 38
2.5.3 Latency on the User Plane ................................................................................. 39
2.5.4 Service Interruption Time over Intra-RAT X2 Handover .................................... 40
2.5.5 Service Interruption Time over Intra-RAT S1 Handover .................................... 41
2.5.6 Service Interruption Time over Inter-RAT Handover ......................................... 41
2.5.7 UL BLER ............................................................................................................. 42
2.5.8 DL BLER ............................................................................................................. 43
2.5.9 UL PDU RBLER at MAC .................................................................................... 44
2.5.10 DL PDU RBLER at MAC .................................................................................... 45
2.6 System Resource Related Indicators ................................................................. 45
2.6.1 Traffic Flow Related Indicators ........................................................................... 45
2.6.2 Radio Resource Usage ...................................................................................... 53
ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. VII
FIGURES
Figure 2-1 Access Signaling....................................................................................................... 3

Figure 2-3 Handover Flow from LTE to Another Network ....................................................... 24
Figure 2-4 Handover Flow from a Radio Network to LTE ....................................................... 25
TABLES
Table 2-1 RSRP..........................................................................Error! Bookmark not defined.

Table 2-2 RS-CINR ....................................................................Error! Bookmark not defined.
Table 2-3 Coverage rate ............................................................Error! Bookmark not defined.
Table 2-4 Service Related RRC Connection Setup Success Rate ........................................... 4
Table 2-5 RRC Connection Setup Success Rate ...................................................................... 5
Table 2-6 E-RAB Setup Success Rate ...................................................................................... 8
Table 2-7 Successful Air Interface Connection Rate ............................................................... 12
Table 2-8 E-RAB Setup Congestion Rate................................................................................ 14
Table 2-9 Call-Drop Rate Caused by Faulty RRC Releases ................................................... 18
Table 2-10 Call-Drop Rate Caused by E-RAB Releases ........................................................ 20
Table 2-11 Frequency Handover Success Rate within the eNB ............................................. 25
Table 2-12 Handover Success Rate over X2 .......................................................................... 27
Table 2-13 Handover Success Rate over S1 .......................................................................... 29
Table 2-14 Handover Success Rate from LTE to CDMA ........................................................ 31
Table 2-15 Handover Success Rate from LTE to GSM........................................................... 32
Table 2-16 Handover Success Rate from LTE to WCDMA..................................................... 33
Table 2-17 Handover Success Rate from LTE to TDS............................................................ 35
Table 2-18 Attach Latency ....................................................................................................... 36
Table 2-19 State Switch Latency from Idle to Active ............................................................... 38
Table 2-20 Latency on the User Plane .................................................................................... 39
Table 2-21 Service Interruption Time over Intra-System X2 Handover .................................. 40
Table 2-22 Service Interruption Time over Intra-System S1 Handover .................................. 41
Table 2-23 Service Interruption Time over Inter-RAT Handover ............................................. 41
Table 2-24 UL BLER ................................................................................................................ 42
Table 2-25 DL BLER ................................................................................................................ 43
ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. VIII
Table 2-26 UL PDU RBLER at MAC ........................................................................................ 44

Table 2-27 DL PDU RBLER at MAC ........................................................................................ 45
Table 2-29 Outgoing Service Data Volume over S1 by eNB................................................... 45
Table 2-30 Incoming Service Data Volume over S1 by eNB................................................... 46
Table 2-31 Outgoing Data Volume at IP Layer over S1 by eNB .......................................... 47
Table 2-32 Incoming Data Volume at IP Layer over S1 by eNB .......................................... 48
Table 2-33 Traffic Flow over X2 ............................................................................................... 49
Table 2-34 Throughput at the MAC Layer ............................................................................... 49
Table 2-35 SUD Bit Rate at the PDCP Layer .......................................................................... 50
Table 2-36 Average PUSCH PRB Use Rate ........................................................................... 53
Table 2-37 Average PDSCH PRB Use Rate ........................................................................... 53
Table 2-38 Average PRACH Resource Use Rate ................................................................... 54
Table 2-39 Maximum TX Power and Mean TX Power of the Cell ........................................... 55
Table 2-40 Paging Congestion Rate ........................................................................................ 56
ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. IX

1 Overview
1.1 Purpose
This document serves as an analysis guide to LTE KPIs.
In this document, the KPIs are interpreted in details in different categories.
1.2 Terms and Abbreviations
Abbreviation English Spelling Chinese Meaning

KPI Key performance indicator 关键性能指标
RRC Radio resource control 无线资源控制
eNB Evolved NodeB 演进型基站
Evolved radio access
eRAB 演进的无线接入承载
bearer
MAC Medium access control 媒体接入控制
RLC Radio link control 无线链路控制
Packet data convergence
PDCP 分组数据汇聚协议
protocol
1.3 Conventions
In this document, each KPI is described in the same format, as shown in the following
table:
KPI Name Time Granularity Region Granularity
Meaning
ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. 1

Definition
Counter Description
Remarks
 KPI Name: indicates the name of the performance indicator.
 Time Granularity: indicates that the granularity statistics is based on the time
interval for data recording at the OMC side.
When the Time Granularity at the OMC side is the same as that collected at the
eNB side, save the data collected at the eNB side as one record; when the Time
Granularity at the OMC side is greater than that at the eNB side, combine the data
collected at the eNB side and save it as one record.
The combination methods depend on the collected objects. For objects such as traffic
flow statistics, add up all the collected data at the eNB side; for objects such as the
measurement value of the TX power, save the mean value as one record.
 Region Granularity: indicates that the granularity statistics at the RAN side is
based on the eNB or the cell.
 Meaning: indicates what this KPI measures and the significance of it to the radio
network.
 Definition: includes the formula of this KPI and its related description.
 Counter Description: indicates the counter for measuring the KPI and its related
description.
 Remarks: indicate the additional information that needs attention.

2 Radio Network KPIs Introduction
2.1 Call Setup Related Indicators
Call success rate is a most important indicator of the LTE system performance. It is also a
most important indicator for the operator.
A complete call setup includes multiple layers: paging success rate, RRC connection
setup success rate, and E-RAB assignment setup success rate. A complete call setup
process includes both the mo and mt processes.
The process starts from the UE's reception of the paging message from the base station
to the completion of E-RAB assignment.
The signaling process is detailed, as shown in the following figure: (Ref: 3gpp ts 36.331
and 3gpp ts 23.401):
Figure 2-1 Access Signaling
UE eNB MME SGW PDN GW
(1) RRC Connection Request
(2) RRC Connection Setup
(3) RRC Connection Complete
(4) Service Request (NAS signal)

(5) Initial Contest Setup Request / Attach Accept
(6) RRC Connection Reconfiguration
(7) RRC Connection Reconfiguration Complete
(8) Initial Contest Setup Response
(9) Update Bearer Request

(11) Update Bearer Response
After the E-RAB assignment succeeds, the UE is able to initiate data services such as
web browsing and ftp downloading.

2.1.1 RRC Connection Setup Success Rate (Service Related)
Table 2-1 Service Related RRC Connection Setup Success Rate
KPI Name
Time Granularity Region Granularity
RRC connection setup 15 minutes, 30 minutes, one

Cell
success rate hour, …, one day,…
Meaning
This indicator reflects the acceptance capability of the cell or of the eNB.
Successful RRC connections indicate that the signaling connection succeeds between
the UE and the network.
RRC connection setup involves two scenarios:
1) Service-related RRC connection setup and
2) RRC connection setup for items such as the emergency call, inter-RAT cell
reselection, and registry.
The first scenario is an essential indicator to measure the service-related RRC
connection setup success rate.
Definition
The eNB determines whether to set up the RRC connection after it receives the RRC
connection request from the UE.
The service-related RRC connection setup success rate indicates the ratio between
successful RRC connections and total RRC connection attempts.
The corresponding signaling messages are RRC CONNECTION SETUP COMPLETE
times and RRC CONNECTION REQ times received by the eNB. This indicator requests
that the statistics should be independently collected according to service types.
Calculation formula:
Service-related RRC connection setup success rate=successful service-related RRC
connections/service-related RRC connection attempts x
100%=(C373200000+C373200008)/( C373200000+C373200001+C373200002+C3732
00003+ C373200008+C373200009+C373200010+C373200011)
For the signaling flow chart, see Figure 2-1.
Counter Description

Successful RRC connections (service-related)=

Successful RRC connections (mt-Access type) C373200000;
Successful RRC connections (mo-Data type) C373200008.
RRC connection attempts (service-related)=

RRC connection requests (mt-Access type)
C373200000+C373200001+C373200002+C373200003;
Number of successful RRC connections (mt-Access type) C373200000
Number of RRC connection failures caused by timer expirations (mt-Access type)
C373200001
Number of RRC connection failures caused by eNB acceptance failures (mt-Access
type) C373200002
Number of RRC connection failures caused by the other causes (mt-Access type)
C373200003
Number of RRC connection requests (mo-Data type)
C373200008+C373200009+C373200010+C373200011
Number of successful RRC connections (mo-Data type) C373200008
Number of RRC connection failures caused by timer expirations (mo-Data type)
C373200009
Number of RRC connection failures caused by eNB acceptance failures (mo-Data type)
C373200010
Number of RRC connection failures caused by the other causes (mo-Data type)
C373200011
Remarks
Service-related RRC connection setup is triggered by mt-Access and mo-Data.
2.1.2 RRC Connection Setup Success Rate
Table 2-2 RRC Connection Setup Success Rate
RRC connection setup 15 minutes, 30 minutes, one Cell, eNB

success rate hour,…one day,…
Meaning
This indicator reflects the acceptance capability of the eNB or of the cell. Successful
RRC connections indicate that the control channel between the UE and the network is
established. This lays a foundation for the other services.
Definition

The eNB determines whether to set up the RRC connection after it receives the RRC
connection request.
RRC connection setup success rate indicates the ratio between successful RRC
connections and total RRC connection attempts. The corresponding signaling
messages are RRC CONNECTION SETUP COMPLETE times and RRC
CONNECTION REQ times received by the RNC.
Calculation Formula:
RRC connection setup success rate=number of successful RRC connections/RRC
connection attempts x
100%=(C373200000+C373200004+C373200008+C373200012+C373200016)/(C3732
00000+C373200001+C373200002+C373200003+C373200004+C373200005+C37320
0006+C373200007+C373200008+C373200009+C373200010+C373200011+C373200
012+C373200013+C373200014+C373200015+C373200016+C373200017+C3732000
18+C373200019)
For the signaling flow chart, see Figure 2-1.
Counter Description

Number of successful RRC connections:

Successful RRC connections (mt-Access type) C373200000;
Successful RRC connections (mo-Signaling type) C373200004;
Successful RRC connections (mo-Data type) C373200008;
Successful RRC connections (highPriorityAccess type) C373200012;
Successful RRC connections (emergency type) C373200016.
Number of RRC connection attempts:

Number of RRC connection requests (mt-Access type)
C373200000+C373200001+C373200002+C373200003;
Number of successful RRC connections (mt-Access type) C373200000
Number of RRC connection failures caused by timer expirations (mt-Access type)
C373200001
Number of RRC connection failures caused by eNB acceptance failures (mt-Access
type) C373200002
Number of RRC connection failures caused by the other causes (mt-Access type)
C373200003
Number of RRC connection requests (mo-Signalling type)

C373200004+C373200005+C373200006+C373200007;
Number of succesful RRC connections (mo-Signalling type) C373200004
Number of RRC connection failures caused by timer expirations (mo-Signalling type)
C373200005
Number of RRC conneciton failures caused by eNB acceptance failures (mo-Signalling
type) C373200006
Number of RRC connection failures caused by the other causes (mo-Signalling type)
C373200007
Number of RRC connection requests (mo-Data type)

C373200008+C373200009+C373200010+C373200011
Number of successful RRC connections (mo-Data type) C373200008
Number of RRC connection failures caused by timer expirations (mo-Data type)
C373200009
Number of RRC conneciton failures caused by eNB acceptance failures (mo-Data type)
C373200010
Number of RRC connection failures caused by the other causes (mo-Data type)
C373200011
Number of RRC connection requests (highPriorityAccess type)

C373200012+C373200013+C373200014+C373200015;
Number of successful RRC connections (highPriorityAccess type) C373200012
Number of RRC connection failures caused by timer expirations (highPriorityAccess
type) C373200013
ZTE Confidential Proprietary
Number of RRC©conneciton
2012 ZTE Corporation. All rights
failures caused reserved.
by eNB 7
acceptance failures
(highPriorityAccess type) C373200014
Number of RRC connection failures caused by the other causes (highPriorityAccess
type) C373200015
Remarks
None.
2.1.3 E-RAB Setup Success Rate
Table 2-3 E-RAB Setup Success Rate

E-RAB setup 15 minutes, 30 minutes,
Cell
success rate one hour,…one day,…
Meaning
Successful E-RAB setup indicates that the eNB successfully assigns the links on the
user plane for the UE. This indicator also reflects the service acceptance capability of
the eNB or of the cell.
Definition

Number of successfully established E-RABs (all QCI)=

C373210200+C373210206+C373210212+C373210218+C373210224+C373210230+C
373210236+C373210242+C373210248+C373210254+C373210260+C373210266+C3
73210272+C373210278+C373210284+C373210290+C373210296+C373210302
Number of E-RAB establishment requests (all QCIs)=
C373210200+C373210201+C373210202+C373210203+C373210204+C373210205+C
373210206+C373210207+C373210208+C373210209+C373210210+C373210211+C3
73210212+C373210213+C373210214+C373210215+C373210216+C373210217+C37
3210218+C373210219+C373210220+C373210221+C373210222+C373210223+C373
210224+C373210225+C373210226+C373210227+C373210228+C373210229+C3732
10230+C373210231+C373210232+C373210233+C373210234+C373210235+C37321
0236+C373210237+C373210238+C373210239+C373210240+C373210241+C373210
242+C373210243+C373210244+C373210245+C373210246+C373210247+C3732102
48+C373210249+C373210250+C373210251+C373210252+C373210253+C37321025
4+C373210255+C373210256+C373210257+C373210258+C373210259+C373210260
+C373210261+C373210262+C373210263+C373210264+C373210265+C373210266+
C373210267+C373210268+C373210269+C373210270+C373210271+C373210272+C
373210273+C373210274+C373210275+C373210276+C373210277+C373210278+C3
73210279+C373210280+C373210281+C373210282+C373210283+C373210284+C37
3210285+C373210286+C373210287+C373210288+C373210289+C373210290+C373
210291+C373210292+C373210293+C373210294+C373210295+C373210296+C3732
10297+C373210298+C373210299+C373210300+C373210301+C373210302+C37321
0303+C373210304+C373210305+C373210306+C373210307+C373505375+C373505
376+C373505377+C373505378+C373505379+C373505380+C373505381+C3735053
82+C373505383+C373505384+C373505385+C373505386+C373505387+C37350538
8+C373505389+C373505390+C373505391+C373505392
E-RAB setup success rate=Number of successful E-RAB connections (all

QCIs)/Number of E-RAB connection requests (all QCIs)/ x 100% =
(C373210200+C373210206+C373210212+C373210218+C373210224+C373210230+
C373210236+C373210242+C373210248+C373210254+C373210260+C373210266+C
373210272+C373210278+C373210284+C373210290+C373210296+C373210302)
/(C373210200+C373210201+C373210202+C373210203+C373210204+C373210205+
C373210206+C373210207+C373210208+C373210209+C373210210+C373210211+C
373210212+C373210213+C373210214+C373210215+C373210216+C373210217+C3
73210218+C373210219+C373210220+C373210221+C373210222+C373210223+C37
3210224+C373210225+C373210226+C373210227+C373210228+C373210229+C373
210230+C373210231+C373210232+C373210233+C373210234+C373210235+C3732
10236+C373210237+C373210238+C373210239+C373210240+C373210241+C37321
0242+C373210243+C373210244+C373210245+C373210246+C373210247+C373210
248+C373210249+C373210250+C373210251+C373210252+C373210253+C3732102
54+C373210255+C373210256+C373210257+C373210258+C373210259+C37321026
0+C373210261+C373210262+C373210263+C373210264+C373210265+C373210266
+C373210267+C373210268+C373210269+C373210270+C373210271+C373210272+
C373210273+C373210274+C373210275+C373210276+C373210277+C373210278+C
373210279+C373210280+C373210281+C373210282+C373210283+C373210284+C3
73210285+C373210286+C373210287+C373210288+C373210289+C373210290+C37
3210291+C373210292+C373210293+C373210294+C373210295+C373210296+C373
210297+C373210298+C373210299+C373210300+C373210301+C373210302+C3732
10303+C373210304+C373210305+C373210306+C373210307+C373505375+C37350
5376+C373505377+C373505378+C373505379+C373505380+C373505381+C373505
382+C373505383+C373505384+C373505385+C373505386+C373505387+C3735053
Note:
The E-RAB setup request quantity can be obtained from the E-RAB SETUP REQUEST
message and the INITIAL CONTEXT SETUP REQUEST message.
The E-RAB successful setup quantity can be obtained from the E-RAB SETUP
RESPONSE message and the INITIAL CONTEXT SETUP RESPONSE message.
Counter Description

Number of E-RAB setup successes=sum of the following counters:

Number of E-RAB setup successes in the context setup response (QCI=1)
C373210212
Number of E-RAB setup successes in the context setup response (QCI=4) C373210218
Number of E-RAB setup successes in the bearer establishment response (QCI=1)
C373210254
C373210260
C373210266
C373210272
C373210278
C373210284
C373210290
C373210296
C373210302
Number of the E-RAB establishment requests=sum of previous requests of all QCIs

For details about the counters, see the following attachment:
Field Code Changed
Counters for all
E-RAB establishment requests.xlsx

Remarks
None.
2.1.4 Successful Air Interface Connection Rate
Table 2-4 Successful Air Interface Connection Rate

Successful air
15 minutes, 30 minutes, one
interface connection Cell
hour,…one day,…
rate
Meaning
This indicator reflects the acceptance capability of the cell to accommodate the UE
calls. It directly affects the UE perception of the network.
Definition

As one call setup needs to first trigger the RRC setup, you need to consider both the
RRC connection setup success rate and the E-RAB setup success rate
comprehensively for the radio connection rate.
KPI calculation formula:

Call completion rate=E-RAB setup success rate x RRC connection setup success rate
(service-related) x 100% =
(C373210200+C373210206+C373210212+C373210218+C373210224+C373210230+
C373210236+C373210242+C373210248+C373210254+C373210260+C373210266+C
373210272+C373210278+C373210284+C373210290+C373210296+C373210302)/(C
373210200+C373210201+C373210202+C373210203+C373210204+C373210205+C3
73210206+C373210207+C373210208+C373210209+C373210210+C373210211+C37
3210212+C373210213+C373210214+C373210215+C373210216+C373210217+C373
210218+C373210219+C373210220+C373210221+C373210222+C373210223+C3732
10224+C373210225+C373210226+C373210227+C373210228+C373210229+C37321
0230+C373210231+C373210232+C373210233+C373210234+C373210235+C373210
236+C373210237+C373210238+C373210239+C373210240+C373210241+C3732102
42+C373210243+C373210244+C373210245+C373210246+C373210247+C37321024
8+C373210249+C373210250+C373210251+C373210252+C373210253+C373210254
+C373210255+C373210256+C373210257+C373210258+C373210259+C373210260+
C373210261+C373210262+C373210263+C373210264+C373210265+C373210266+C
373210267+C373210268+C373210269+C373210270+C373210271+C373210272+C3
73210273+C373210274+C373210275+C373210276+C373210277+C373210278+C37
3210279+C373210280+C373210281+C373210282+C373210283+C373210284+C373
210285+C373210286+C373210287+C373210288+C373210289+C373210290+C3732
10291+C373210292+C373210293+C373210294+C373210295+C373210296+C37321
0297+C373210298+C373210299+C373210300+C373210301+C373210302+C373210
303+C373210304+C373210305+C373210306+C373210307+C373505375+C3735053
76+C373505377+C373505378+C373505379+C373505380+C373505381+C37350538
2+C373505383+C373505384+C373505385+C373505386+C373505387+C373505388
+C373505389+C373505390+C373505391+C373505392)
x ( C373200000+
C373200008)/( C373200000+C373200001+C373200002+C373200003+
C373200008+C373200009+C373200010+C373200011)
Counter Description
For details, refer to the counters described in sections 2.1.1 RRC Connection Setup
Success Rate (Service Related) and 2.1.3 E-RAB Setup Success Rate.
Remarks
None.

2.1.5 E-RAB Setup Congestion Rate
This indicator reflects only the E-RAB setup failures caused by limited system capacity.
Table 2-5 E-RAB Setup Congestion Rate

E-RAB setup congestion 15 minutes, 30 minutes, one
Cell
rate hour,…one day,…
Meaning
This indicator reflects the acceptance rejection from the eNB or cell owing to insufficient
system resources.
Definition


E-RAB congestion rate=number of rejected E-RABs / number of E-RAB access requests x
100%
=(C373210201+C373210207+C373210213+C373210219+C373210225+C373210231+C37
3210237+C373210242+C373210249+C373210255+C373210261+C373210267+C3732102
73+C373210279+C373210285+C373210291+C373210297+C373210303) /
(C373210200+C373210201+C373210202+C373210203+C373210204+C373210205+C373
210206+C373210207+C373210208+C373210209+C373210210+C373210211+C37321021
2+C373210213+C373210214+C373210215+C373210216+C373210217+C373210218+C3
73210219+C373210220+C373210221+C373210222+C373210223+C373210224+C373210
225+C373210226+C373210227+C373210228+C373210229+C373210230+C373210231+
C373210232+C373210233+C373210234+C373210235+C373210236+C373210237+C373
210238+C373210239+C373210240+C373210241+C373210242+C373210243+C37321024
4+C373210245+C373210246+C373210247+C373210248+C373210249+C373210250+C3
73210251+C373210252+C373210253+C373210254+C373210255+C373210256+C373210
257+C373210258+C373210259+C373210260+C373210261+C373210262+C373210263+
C373210264+C373210265+C373210266+C373210267+C373210268+C373210269+C373
210270+C373210271+C373210272+C373210273+C373210274+C373210275+C37321027
6+C373210277+C373210278+C373210279+C373210280+C373210281+C373210282+C3
73210283+C373210284+C373210285+C373210286+C373210287+C373210288+C373210
289+C373210290+C373210291+C373210292+C373210293+C373210294+C373210295+
C373210296+C373210297+C373210298+C373210299+C373210300+C373210301+C373
210302+C373210303+C373210304+C373210305+C373210306+C373210307+C37350537
5+C373505376+C373505377+C373505378+C373505379+C373505380+C373505381+C3
73505382+C373505383+C373505384+C373505385+C373505386+C373505387+C373505
388+C373505389+C373505390+C373505391+C373505392), where
the number of E-RAB setup requests originates from the E-RAB SETUP REQUEST
message and the INITIAL CONTEXT SETUP REQUEST message;
The number of rejected E-RABs originates from the INITIAL CONTEXT SETUP FAILURE
message and the E-RAB SETUP RESPONSE message.
"Radio resources not available" is caused by E-RAB setup failures.
As shown in the following figures, the processes interpret how the INITIAL CONTEXT
SETUP FAILURE message and the E-RAB SETUP RESPONSE message are generated:
eNB MME
INITIAL UE MESSAGE (Including the Attach request

message)
INITIAL CONTEXT SETUP REQUEST
INITIAL CONTEXT SETUP FAILURE
Figure 1
UE eNB MME
(1) E-RAB Setup Request /

Session Management Request
(3) RRC Connection Reconfiguration Complete
(4) E-RAB Setup Response
Counter Description

Number of rejected E-RAB accesses=sum of the following items:

QCI1 Number of initial E-RAB setup failures caused by eNB acceptance failures
C373210201
C373210207
C373210213
C373210219
C373210225
C373210231
C373210237
C373210242
C373210249
QCI1 Number of added E-RAB setup failures caused by eNB acceptance failures
C373210255
C373210261
C373210267
C373210273
C373210279
C373210285
C373210291
C373210297
C373210303
Number of E-RAB setup requests=sum of all QCI requests

For specific counters, see the following attachment.
Counters for the

sum of E-RAB setup requests.xlsx

Remarks
None.
2.2 Call Retainability Related Indicators
2.2.1 Call-Drop Rate Caused by Faulty RRC Releases
Table 2-6 Call-Drop Rate Caused by Faulty RRC Releases

Call-drop rate caused by 15 minutes, 30 minutes,
Cell
faulty RRC releases one hour,…one day,…
Meaning
UEs' RRC connections might be released due to exceptions in the eNB. This indicator
reveals the RRC connection continuity of the eNB, and it also affects the UE perception
of the network.
Definition


Call-drop rate caused by faulty RRC releases=Number of faulty RC connection releases
/(number of RRC connection establishment successes+ number of RRC connection
re-establishment successes) x
100%=(C373200023+C373200024+C373200050+C373200051+C373200052+C37320
0053+C373200083)/(C373200060+C373200066+C373200072+C373200000+C37320
0004+C373200008+C373200012+C373200016), where "number of faulty RRC
connection releases" indicates all RRC connection releases excluding the normal RRC
connection releases.
And the causes of normal RRC connection releases are as follows:

Normal releases initiated by the core network;
Releases caused by load balancing initiated by the core network;
Reset request derived from the core network.
See the signaling flow below in the following figures:
UE DCM
RRCConnectionReestablishmentRequest
RRCConnectionReestablishment
RRCConnectionReestablishmentComplete
RRCConnectionReconfiguration
RRCConnectionReconfigurationComplete
Figure 1 RRC connection re-establishment success
UE eNB MME
RRCConnectionRequest
RRCConnectionSetup
RRCConnectionSetupComplete(Including the
Service request message) INITIAL UE MESSAGE（ Including the Service
request message（
INITIAL CONTEXT SETUP REQUEST
RRCConnectionReconfiguration
RRCConnectionReconfigurationComplete
ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights

INITIAL reserved.
CONTEXT SETUP RESPONSE19
Figure 2 RRC connection setup success
UE eNB
RRCConnectionRelease
Counter Description
For specific counters, see the following attachment for details:
Counters for
faulty RRC release caused call-drop rate .xlsx
Remarks
None.
2.2.2 Call-Drop Rate Caused by Faulty E-RAB Releases
Table 2-7 Call-Drop Rate Caused by E-RAB Releases

Call-drop rate caused
15 minutes, 30 minutes, one
by faulty E-RAB Cell
hour,…one day,…
releases
Meaning
This indicator reveals the service continuity capability of the system. It is a most
significant performance indicator reflecting the UE perception of the network.
Definition

The eNB sends the E-RAB release request to the MME out of some exceptional
causes, asking for the release of one or more E-RABs.
The eNB sends UE context release requests to the MME out of any of the following
causes:
Missing UE
Inactivated UE
Faulty eNB
In this scenario, however, all established E-RABs by the UE will also be released.
Here the call-drop rate caused by faulty E-RAB releases indicates the E-RAB release
requests initiated by the eNB rather than by UE inactivation, additionally, this call-drop
rate also involves E-RAB releases of the UE context releases caused by faults in the
eNB.

E-RAB call drop rate=Number of E-RABs (QCI=1 to 9) categorized by the causes
initiated by the eNB rather than by UE inactivation/number of E-RAB setup successes
(QCI =1 to 9)+number of E-RABs (QCI=1 to 9) for entering the cell+number of the
E-RABs available) x
100%=(C373210372+C373210373+C373210374+C373210375+C373210376+C37321
0377+C373210378+C373210379+C373210380
+C373210382+C373210383+C373210384+C373210385+C373210386+C373210387+
C373210388+C373210389+C373210390
+C373210422+C373210423+C373210424+C373210425+C373210426+C373210427+
C373210428+C373210429+C373210430
+C373210432+C373210433+C373210434+C373210435+C373210436+C373210437+
C373210438+C373210439+C373210440
+C373210442+C373210443+C373210444+C373210445+C373210446+C373210447+
C373210448+C373210449+C373210450
+C373210502+C373210503+C373210504+C373210505+C373210506+C373210507+
C373210508+C373210509+C373210510
+C373505345+C373505346+C373505347+C373505348+C373505349+C373505350+
C373505351+C373505352+C373505353)
/
(C373210200+C373210206+C373210212+C373210218+C373210224+C373210230+
C373210236+C373210242+C373210248+C373210254+C373210260+C373210266+C
373210272+C373210278+C373210284+C373210290+C373210296+C373210302+C3
73546103+C373546111+C373546119+C373546127+C373546135+C373546143+C37
3546151+C373546159+C373546167+C373546107+C373546115+C373546123+C373
546131+C373546139+C373546147+C373546155+C373546163+C373546171+C3735
46175+C373546183+C373546191+C373546199+C373546207+C373546215+C37354
6223+C373546231+C373546239+C373546179+C373546187+C373546195+C373546
203+C373546211+C373546219+C373546227+C373546235+C373546243+C3732408
09+C373240810+C373240811+C373240812+C373240813+C373240814+C37324081
5+C373240816+C373240817)
Counter Description
Counters for
E-RAB call-drop rate.xlsx
Remarks
None.
2.3 Mobility Management Related Indicators
1. Introduction to the intra-RAT handover
The handover within the LTE system differs from that in CDMA or WCDMA. Only
hard handovers rather than soft handovers are available. That is, the UE needs to
be disconnected from the serving cell so as to be connected to the target cell.
The triggering causes of the handover are as follows:
 Network coverage triggered handover: When the UE detects that the signal
quality of the neighboring cell is higher than that of the serving cell, additionally,
the signal quality of the serving cell is lower than a certain threshold, the
network triggers the UE to be handed over to the neighboring cell;
 Network overload triggered handover: When the serving cell is overloaded and
its neighboring cell is light loaded, additionally, the UE detects that the signal
quality of the neighboring cell meets a certain threshold, the network triggers
the UE to be handed over to the neighboring cell;
 Service triggered handover: When a certain service initiated by the UE is not

supported in the serving cell, the service is, however, supported by the
neighboring cell. Additionally, the UE detects that the signal quality of the
neighboring cell meets a certain threshold, the network triggers the UE to be
handed over to the neighboring cell;
 UE movement speed triggered handover: When the eNB determines that the
UE's movement speed is higher or lower than a threshold, meanwhile, the

network is deployed with high speed and low speed cells, the eNB triggers the
UE to be handed over to the corresponding cell for better network service.
Handover categories in LTE
Handovers in LTE are categorized as intra-RAT handover and inter-RAT handover.
The intra-RAT handover involves intra-frequency handover and inter-frequency handover

according to the carrier frequency allocation.
The inter-RAT handover involves the handover among LTE, CDMA, WCDMA, and
TD-SCDMA.
An overall system handover performance will be reflected according to the previous

handover categories.
2. Introduction to the handover between LTE and the other systems
Heated competition among operators in the radio operation arena generates networks of
different radio technologies based on different operating licenses and polices.
Nowadays, even for the same operator, considering smooth network upgrade and
provision of good comprehensive services, also tend to build networks of different
technologies based on different operating licenses and policies.
However, the seamless service on the global scale, demanded by the terminal users
around the world, becomes an inevitable trend. Therefore, the inter-RAT handover is
vital.
For LTE, the handover refers to the inter-RAT handover among LTE and CDMA2000,
WCDMA, and TD-SCDMA, and additionally, the handover between the LTE network and
the GSM network or B3G WiMAX network.
The inter-RAT handover capability directly affects the UE (oftentimes high-end users)
perception of the network services.
"Handover" indicates the switching of a mobile signal from one channel or cell to another.
The handover process is almost the same in LTE as in the other systems. That is, the
handover message is delivered between the CN Gateways of two systems. For RAN, no
big difference exists between the inter-RAT handover and the intra-RAT handover.
Two handover flows are illustrated below:

Handover flow from LTE to another network
Handover flow from a radio network to LTE
Note: This handover flow is applied to all inter-RAT handovers between LTE and
another network.
Figure 2-2 Handover Flow from LTE to a Different Network
Source Sourse Target RAN(W/C/T)

UE
eNB MME CN&AN
(1) Measurement Report
(2) Handover Required

(3) Forward Relocation Request
(4) Other RAN Preparation
(5) Forward Relocation Response

(6) Handover Command
(7) RRC Reconfiguretion/
Handover Command
(8) Handover to target RAN
(9) Forward Relocation Complete
(10) Release Resourse

Figure 2-3 Handover Flow from a Radio Network to LTE
Source Sourse Target RAN(W/C/T)

UE
eNB MME CN&AN
(1) Handover initiation

(3) Handover Request
(4) Allocation Resource
(5) Handover Request Ack
(7) Handover command from other RAN
(8) RRC Connection Setup Procedure

/ Handover Confirm
(10) Handover Notify
2.3.1 Intra-RAT Handover
2.3.1.1 Handover Success Rate Inside the eNB
Table 2-8 Frequency Handover Success Rate within the eNB

Intra-frequency
15 minutes, 30
handover
minutes, 1 hour, …, Cell
success rate
one day,…
within the eNB
Meaning
This indicator reflects the handover success rate within the eNB. It aims to
guarantee the continuity of the users' the usage of services in mobility.
This indicator is relevant with system handover capability and network
optimization. It directly affects the UE perception of the network.
Definition

The handover signaling process within the eNB is illustrated in the following
figure:
UE eNB
RRC Reconfiguretion/
Handover Command
RRC Connection Setup Procedure
RRC Connection Reconfiguration /

Handover Confirm
Figure 1

The internal handover of the eNB involves two types: 1) intra-frequency handover
and 2) inter-frequency handover, each of which includes incoming handover and
outgoing handover.
Outgoing intra-frequency handover success rate inside the eNB=Number of

successful outgoing intra-frequency handovers inside the eNB/Number of
outgoing intra-frequency handover requests inside the eNB x
100%=C373250980/(C373250900+C373250901+C373250902+C373250903)
Incoming intra-frequency handover success rate inside the eNB=Number of

successful incoming intra-frequency handovers inside the eNB/Number of
incoming intra-frequency handover requests inside the eNB x 100%
=C373250984 /( C373250940+C373250941+C373250942+C373250943)
Outgoing inter-frequency handover success rate inside the eNB=Number of

successful outgoing inter-frequency handovers inside the eNB/Number of
outgoing inter-frequency handover requests inside the eNB x
100%=C373281880 /( C373281800+C373281801+C373281802+C373281803)
Incoming inter-frequency handover success rate inside the eNB=Number of

successful incoming inter-frequency handovers inside the eNB/Number of
incoming inter-frequency handover requests inside the eNB x 100%=
C373281884 /( C373281840+C373281841+C373281842+C373281843)
Counter Description


Field Code Changed
Handover Related
counters within the eNB.xlsx
Remarks
None.
2.3.1.2 Handover Success Rate over X2
Table 2-9 Handover Success Rate over X2

Handover success 15 minutes, 30 minutes, one
Cell
rate over X2 hour,…, one day…
Meaning
The handover success rate over X2 reflects the handover success rate between eNBs
that are connected over X2.
This indicator is relevant with system handover capability and network optimization. It
directly affects the UE perception of the network.
Definition

The signaling flow over X2 is shown in the following figure:
Source Target
UE MME SGW PDN GW
eNB eNB


Handover Command
(5) SN Status Transfer
(6) Data Forwarding

/ Handover Confirm
(9) Path Switch Request
(10) Create Bearer Request
(13) Create Bearer Response
(14) Path Switch Request Ack
(15) End Marker
(16) End Marker
(17) UE Context Release
Figure 1

The handover over the X2 interface includes intra-frequency handover and
inter-frequency handover, each of which involves two scenarios: incoming and outgoing
handovers.
Outgoing intra-frequency handover over X2:

Outgoing intra-frequency handover success rate over X2= (Number of successful
outgoing intra-frequency handovers over X2/number of outgoing intra-frequency
handover requests over X2) x 100% =
C373261280/(C373261200+C373261201+C373261202+C373261203)
Incoming intra-frequency handover over X2:
Incoming intra-frequency handover success rate over X2= (Number of successful
incoming intra-frequency handovers over X2/number of incoming intra-frequency
handover requests over X2) x
100%=C373261284/(C373261240+C373261241+C373261242+C373261243+C37326
1290)
Outgoing inter-frequency handover over X2:
ZTE Confidential Proprietary
Outgoing © 2012
inter-frequency ZTE Corporation.
handover success All rights
rate overreserved. 28
X2= (Number of successful
outgoing inter-frequency handovers over X2/number of outgoing inter-frequency
handover requests over X2) x
100%=C373292180/(C373292100+C373292101+C373292102+C373292103)
Incoming inter-frequency handover over X2
Counter Description
Field Code Changed
Handover related
counters over X2 within the eNB.xlsx
Remarks
None.
2.3.1.3 Handover Success Rate over S1
Table 2-10 Handover Success Rate over S1

Handover success rate 15 minutes, 30 minutes,
Cell
over S1 one hour,…, one day…
Meaning
When the UE handover between cells are necessary based on the measurement report,
and additionally, no X2 interface is available between the eNBs, the handover over S1 is
required. The handover success rate over S1 reflects the successful UE handovers
through the CN. This indicator is relevant with system handover capability and network
planning. It directly affects the UE perception of the network.
Definition

The handover signaling flow over S1 is shown in the following figure:

Source Target Source Target Source Target
UE PDN GW
eNB eNB MME MME SGW SGW
(2) Handover Required

(13) Handover Command
Handover Command
(15) eNB Status Transfer

(16) Forward SRNS Context
(17) Forward SRNS Context Ack
(18) eNB Status Transfer

(19) Data Forwarding

/ Handover Confirm
(22) Handover Notify
(24) Forward Relocation Complete Ack

Figure 1

The handover over S1 includes intra-frequency handover and inter-frequency handover,
each of which involves two scenarios: incoming and outgoing handovers.
1. Outgoing intra-frequency handover over S1:

Outgoing intra-frequency handover success rate over S1= (Number of successful
outgoing intra-frequency handovers over S1/number of outgoing intra-frequency
handover requests over S1) x 100%= C373271580 /
(C373271500+C373271501+C373271502+C373271503)
2. Incoming intra-frequency handover over S1:
ZTE ConfidentialIncoming
Proprietaryintra-frequency
© 2012handover
ZTE Corporation.
successAllrate
rights reserved.
over 30
S1= (Number of successful
incoming intra-frequency handovers over S1/number of incoming intra-frequency
handover requests over S1) x 100%=C373271584
/( C373271540+C373271541+C373271542+C373271543+C373271589)
3. Outgoing inter-frequency handover over S1:
Counter Description
Field Code Changed
Handover related
counters over S1 between eNBs.xlsx
Remarks
None.
2.3.2 Inter-RAT Handover
2.3.2.1 Handover Success Rate from LTE to CDMA
Table 2-11 Handover Success Rate from LTE to CDMA

15 minutes, 30
Handover success rate
minutes, one hour,…, Cell or eNB
from LTE to CDMA
one day…
Meaning
This indicator reflects the handover successes from LTE to CDMA.
It reflects the stability and reliability of the radio system concerning the inter-RAT
handover.
Also, it partially reflects the radio coverage conditions of the LTE and CDMA
networks.
It serves as a major reference for network planning and optimization and it
Definition

The flow chart for the outgoing inter-RAT signaling process is displayed in Figure
2-2; the flow chart for the incoming inter-RAT signaling process is displayed in
Figure 2-3.
For the LTE system, the inter-RAT handover involves the incoming handover
success rate and outgoing handover success rate.

Outgoing handover success rate from LTE to CDMA=outgoing handover success
rate in the PS domain from EPS to CDMA=(1-outgoing handover failures in the
PS domain from EPS to CDMA)/outgoing handover requests in the PS domain
from EPS to CDMA) x 100%=
C373323012/(C373323008+C373323009+C373323010+C373323011);
Incoming handover success rate from CDMA to LTE=incoming handover

success rate in the PS domain from CDMA to EPS=(incoming handover
successes from CDMA to EPS/incoming handover requests from CDMA to EPS)
x 100%=C373323004/( C373323000+C373323001+C373323002+C373323003)
Counter Description
Field Code Changed
Handover related
counters between LTE and CDMA.xlsx
Remarks
None.
2.3.2.2 Handover Success Rate from LTE to GSM
Table 2-12 Handover Success Rate from LTE to GSM

Cell or eNB
from LTE to GSM one hour,…, one day…
Meaning

This indicator reflects the handover successes from LTE to GSM.

handover.
Also, it partially reflects the radio coverage conditions of the LTE and GSM
networks.
Definition
The flow chart for the outgoing inter-RAT handover signaling process is shown in
Figure 2-2; the flow chart for the incoming inter-RAT handover signaling process
is shown in Figure 2-3.
Outgoing handover success rate from LTE to GSM=outgoing handover success
rate in the PS domain from EPS to GSM=(1-outgoing handover failures in the PS
domain from EPS to GSM)/outgoing handover requests in the PS domain from
EPS to GSM) x 100%= C373333312/(C373333308+C373333309+C373333310+
+C373333311);
Incoming handover success rate from GSM to LTE=incoming handover success
rate in the PS domain from GSM to EPS=(incoming handover successes from
GSM to EPS/incoming handover requests from GSM to EPS) x
100%=(C373333304/( C373333300+C373333301+C373333302+C373333303)
Counter Description
Field Code Changed
Handover related
counters between LTE and GSM.xlsx
Remarks
None.
2.3.2.3 Handover Success Rate from LTE to WCDMA
Table 2-13 Handover Success Rate from LTE to WCDMA


Cell or eNB
from LTE to WCDMA one hour,…, one day…
Meaning
This indicator reflects the handover successes from LTE to WCDMA.
handover.
Also, it partially reflects the radio coverage conditions of the LTE and WCDMA
networks.
Definition
Outgoing handover success rate from LTE to WCDMA=outgoing handover
success rate in the PS domain from EPS to WCDMA=(1-outgoing handover
failures in the PS domain from EPS to WCDMA)/outgoing handover requests in
the PS domain from EPS to WCDMA) x
100%=C373312712/( C373312708+C373312709+C373312710+C373312711);
Incoming handover success rate from WCDMA to LTE=incoming handover
success rate in the PS domain from WCDMA to EPS=(incoming handover
successes from WCDMA to EPS/incoming handover requests from WCDMA to
EPS) x
100%=C373312704/(C373312700+C373312701+C373312702+C373312703).
Counter Description
Field Code Changed
Handover related
counters between LTE and WCDMA.xlsx
Remarks
None.

2.3.2.4 Handover Success Rate from LTE to TD-SCDMA
Table 2-14 Handover Success Rate from LTE to TDS

Cell or eNB
from LTE to TDS one hour,…, one day…
Meaning
This indicator reflects the handover successes from LTE to TDS.
handover.
Also, it partially reflects the radio coverage conditions of the LTE and TDS
networks.
Definition
Outgoing handover success rate from LTE to TDS=outgoing handover success
rate in the PS domain from EPS to TDS=(1-outgoing handover failures in the PS
domain from EPS to TDS)/outgoing handover requests in the PS domain from
EPS to TDS) x
100%=C373312712/( C373312708+C373312709+C373312710+C373312711);
Incoming handover success rate from TDS to LTE=incoming handover success
rate in the PS domain from TDS to EPS=(incoming handover successes from
TDS to EPS/incoming handover requests from TDS to EPS) x 100%=
C373312704/(C373312700+C373312701+C373312702+C373312703).
Counter Description
Field Code Changed
Handover related
counters between LTE and TD-S.xlsx
Remarks
None.

2.4 Quality Related Indicators
2.4.1 Attach Latency
Table 2-15 Attach Latency

Attach latency None Cell
Meaning

The Attach time indicates the time required for the UE to complete the network registry.
It is a most important KPI to measure the UE perception upon network access.
ZTE defines the Attach latency procedure as 30 steps, as shown in the following figure:
UE eNB MME
Detach
State
1. Delay for RACH
Scheduling Period
2. RACH Premble
3. Processing
delay in eNB
4. TA+ Scheduling Grant

5. Processing
delay in UE
6. RRC Connection Request
7. Processing
delay in eNB
8. RRC Connection Setup
9. Processing
delay in UE
10. RRC Connection Setup Complete
+NAS Attach Request, PDN Connection Request 11. Processing
delay in eNB
12. Initial UE Message

13. Processing
delay in MME
14. DOWNLINK NAS TRANSPORT
Authentication
15. DLInformationTransfer
Authentication
16. Processing
delay in UE 17. DLInformationTransfer
Authentication
18. UPLINK NAS TRANSPORT
Authentication 19. Processing
delay in MME
20. DOWNLINK NAS TRANSPORT
Security
21. DLInformationTransfer
Security
22. Processing
delay in UE 23. DLInformationTransfer
Security
24. UPLINK NAS TRANSPORT
Security 25. Processing
delay in MME
26. Connection Setup
27. Processing
delay in eNB
28. Safety Mode Command +
29. Processing RRC Connection Reconfiguration
delay in UE
Active 30. RRC Connection Reconfiguration Complete

State
Figure 1
Definition
This indicator represents the period from PRACH access to network registry
completion.
Counter Description
None.
Remarks
It is recommended that this indicator should be measured at the UE side.

2.4.2 State Switch Latency from Idle to Active
Table 2-16 State Switch Latency from Idle to Active

State switch latency
None Cell
from idle to active
Meaning
The State switch time from idle to active indicates the time required for the UE to switch
from the idle state to the active state. This indicator directly affects time consumed in
processes such as call (E-RAB) setup and TAU. It is a most important KPI measuring
the network access latency and hence has direct impact on the UE perception of the
network.
The figure below illustrates the time required during the 18 steps when the UE switches
from idle to active, defined by LST1 and recognized by most manufacturers.
UE eNB MME
IDLE
State
1. Delay for RACH
Scheduling Period
2. RACH Premble
3. Processing
delay in eNB
4. TA+ Scheduling Grant

5. Processing
delay in UE
6. RRC Connection Request
7. Processing
delay in eNB
8. RRC Connection Setup
9. Processing
delay in UE
10. RRC Connection Setup Complete
+NAS Service Request 11. Processing
delay in eNB
12. Connection Request

13. Processing
delay in MME
14. Connection Setup
15. Processing
delay in eNB
16. Safety Mode Command +
17. Processing RRC Connection Reconfiguration
delay in UE
Active 18. RRC Connection Reconfiguration Complete

State
Figure 1
Definition

This latency indicates the time consumed by the UE from PRACH access to RRC
connection reconfiguration completion.
Counter Description
None.
Remarks
It is recommended that this indicator should be measured at the UE side.
2.4.3 Latency on the User Plane
Table 2-17 Latency on the User Plane

Latency on the
None Cell
user plane
Meaning
According to LSTI, the latency on the user plane involves three parts: air interface
latency, EPC latency and E2E latency, as shown in the following figure.
The air interface latency is tested in the condition of good channel quality and no UEs.
The latency test is performed through ping.
UE eNB EPC (PDN GW) App. Server

RAN latency
EPC latency
E2E latency
Definition
In the case of pre-scheduling, it is required that air interface latency (bilateral) should be
less than 5 ms, and the E2E latency should be less than 10 ms.
Counter Description
None.

Remarks
None.
2.4.4 Service Interruption Time over Intra-RAT X2 Handover
Table 2-18 Service Interruption Time over Intra-System X2 Handover

Service
interruption time 15 minutes, 30 minutes, 1
Cell
over intra-system hour, …, one day,…
X2 handover
Meaning
This indicator measures the service interruption period when the UE experiences the
X2 handover in the LTE network. Users are directly affected by excessively long
service interruption time, especially for real time service such as VoIP. Therefore, this
is a most important indicator for UEs' perception of the network services.
Definition
Two sub-indicators are involved in handover latency over X2 in the system: UL latency
and DL latency.
UL latency=the time at which the destination eNB received the first UL data packet
after the X2 handover-the time at which the source eNB received the last UL data
packet before the X2 handover
DL latency=the time at which the destination eNB received the first DL data packet
after the X2 handover-the time at which the source eNB received the last DL data
packet before the X2 handover
Counter Description
Temporarily unavailable.
Remarks
None.

2.4.5 Service Interruption Time over Intra-RAT S1 Handover
Table 2-19 Service Interruption Time over Intra-System S1 Handover

Service
Cell
over intra-system hour, …, one day,…
S1 handover
Meaning
This indicator measures the service interruption period when the UE experiences the
S1 handover in the LTE network. Users are directly affected by excessively long
service interruption time, especially for the real time service such as VoIP. Therefore,
this is a most important indicator for UEs' perception of the network services.
Definition
Two sub-indicators are involved in handover latency over S1 in the system: UL latency
and DL latency.
UL latency=the time at which the destination eNB received the first UL data packet
after the S1 handover-the time at which the source eNB received the last UL data
packet before the S1 handover
DL latency=the time at which the destination eNB received the first DL data packet
after the S1 handover-the time at which the source eNB received the last DL data
packet before the S1 handover
Counter Description
Remarks
None.
2.4.6 Service Interruption Time over Inter-RAT Handover
Table 2-20 Service Interruption Time over Inter-RAT Handover

Service
Cell
over inter-RAT hour, …, one day,…
handover
Meaning
This indicator measures the service interruption time on the user plane when the
UE experiences the inter-RAT handover. Users are directly affected by
excessively long service interruption time, especially for the real time service
such as VoIP. Therefore, this is a most important indicator for UEs' perception of
the network services.
Definition
Two sub-indicators are involved in the inter-RAT handover latency: UL latency
and DL latency.
UL latency=the time at which the destination eNB received the first UL data
packet after the inter-RAT handover-the time at which the source eNB received
the last UL data packet before the inter-RAT handover
DL latency=the time at which the destination eNB received the first DL data
packet after the inter-RAT handover-the time at which the source eNB received
the last DL data packet before the inter-RAT handover
Counter Description
Remarks
None.
2.4.7 UL BLER
Table 2-21 UL BLER

15 minutes, 30 minutes,
UL BLER Cell
1 hour, …, one day,…
Meaning

UL BLER is a main indicator reflecting signal transmission quality over the radio
interface.
It is also the base, on which the RRM is controlled, and hence it affects the
performance concerning the handover, power control, and acceptance of the system.
This indicator shows not only the network coverage conditions, but also network
interference conditions.
In this regard, the UL BLER also reflects the quality of network planning and that of its
relevant algorithm.
Definition
This indicator reflects the CRC error rate received in the statistical periodicity in the UL
TB.
UL BLER=(number of received CRC errors in the UL TBs/total number of received UL
TBs) x 100%=C373454802 / C373454803
Counter Description
Number of received faults in the UL TBs=number of error TBs in the UL C373454802
Total number of received UL TBs=Total of TBs in the UL C373454803
Remarks
Here the transmission blocks indicate the integrated TBs rather than separated TBs.
2.4.8 DL BLER
Table 2-22 DL BLER

15 minutes, 30 minutes, 1
DL BLER Cell
hour, …, one day,…
Meaning
DL BLER is a main indicator reflecting signal transmission quality over the radio
interface.
It is also the base, on which the RRM is controlled, and hence it affects the
performance concerning the handover, power control, and acceptance of the system.
This indicator shows not only the network coverage conditions, but also network
interference conditions.
In this regard, the DL BLER also reflects the quality of network planning and that of its
relevant algorithm.
Definition

This indicator reflects the CRC error rate received in the statistical periodicity in the DL
TB.
DL BLER=(number of received CRC errors in the DL TBs/total number of received DL
TBs) x 100%=C373454800/ C373454801
Counter Description
Number of received faults in the DL TBs=number of DL cell CRC Error Blocks
C373454800
Total number of received DL TBs=Number of DL cell Total Blocks C373454801
Remarks
Here the transmission blocks indicate the integrated TBs rather than separated TBs.
2.4.9 UL PDU RBLER at MAC
Table 2-23 UL PDU RBLER at MAC

UL PDU
RBLER at Cell
MAC
Meaning
The UL PDU RBLER at MAC is a main quality indicator of the packet services.
Addtionally, it is also a major task of network optimization of the packet services.
It implies the performance of the Hybrid Automatic Repeat Request (HARQ).
Definition
This indicator reflects the the ratio of the TB retransmission failures in the UL
within the measurement period.
UL PDU RBLER at MAC=number of total TB RPEs in the UL/number of total UL
TBs in the cell=C373454814/C373454803
Counter Description
Number of total TB RPEs in the UL=C373454814
Number of total TBs of the cell in the UL= C373454803
Remarks
Here the transmission blocks indicate the integrated TBs rather than separated
TBs.

2.4.10 DL PDU RBLER at MAC
Table 2-24 DL PDU RBLER at MAC

DL PDU
RBLER at Cell
MAC
Meaning
The DL PDU RBLER at MAC is a main quality indicator of the packet services.
Addtionally, it is also a major task of network optimization of the packet services.
It implies the performance of the Hybrid Automatic Repeat Request (HARQ).
Definition
This indicator reflects the the ratio of the TB retransmission failures in the DL
within the measurement period.
DL PDU RBLER at MAC=number of total TB RPEs in the DL/number of total DL
TBs in the cell=C373454815/C373454801
Counter Description
Number of total TB RPEs in the DL=C373454815
Number of total TBs of the cell in the DL= C373454801
Remarks
Here the transmission blocks indicate the integrated TBs rather than separated
TBs.
2.5 System Resource Related Indicators
2.5.1 Traffic Flow Related Indicators
2.5.1.1 Outgoing Service Data Volume over S1 by eNB
Table 2-25 Outgoing Service Data Volume over S1 by eNB

Outgoing service
data volume eNB
over S1 by eNB
Meaning
This indicator reflects the UL data service transmission rate on the GTPU layer
over the S1 interface of the eNodeB. It also reflects the system load over the S1
interface.
Definition
This indicator is used to collect the traffic flow of the user plane over the S1
interface. As the data flow might differ from the UL to the DL, two sub-indicators
are involved: outgoing service traffic flow over S1 and incoming service traffic
flow over S1.
Note that here "UL" and "DL" are concerned with the eNB.

Outgoing service traffic flow over S1= Volume of service data sent over S1 by the
eNB
The unit is kbyte/s.
Counter Description
Volume of service data sent over S1 by the eNB C373800000
Remarks
None.
2.5.1.2 Incoming Service Data Volume over S1 by eNB
Table 2-26 Incoming Service Data Volume over S1 by eNB

Incoming service
data volume eNB
over S1 by eNB
Meaning
This indicator reflects the DL data service transmission rate on the GTPU layer
over the S1 interface of the eNodeB. It also reflects the system load over the S1
interface.
Definition

This indicator is used to collect the traffic flow of the user plane over the S1
interface. As the data flow might differ from the UL to the DL, two sub-indicators
are involved: outgoing service traffic flow over S1 and incoming service traffic
flow over S1.

Incoming service traffic flow over S1= Volume of service data received over S1
by the eNB
Counter Description
Volume of service data received over S1 by the eNB C373800001
Remarks
None.
2.5.1.3 Outgoing Data Volume at IP Layer over S1 by eNB
Table 2-27 Outgoing Data Volume at IP Layer over S1 by eNB

Outgoing data
volume at IP 15 minutes, 30 minutes, 1
eNB
layer over S1 by hour, …, one day,…
eNB
Meaning
This indicator reflects the traffic flow at the transmission layer over the S1
interface. It is irrelevant to the transmission media.
Definition
As the data flow might differ from the UL to the DL, two sub-indicators are
involved: outgoing traffic flow at the IP layer over S1 and incoming traffic flow at
the IP layer over S1.
Note that here the packet headers are included.

Outgoing traffic flow at IP layer over S1= sum of data volume sent from the IP
addresses to the IP layer over the S1 interface
Counter Description

Volume of data sent at the IP layer over the S1 interface by the eNB
C373800002
Remarks
None.
2.5.1.4 Incoming Data Volume at IP Layer over S1 of eNB
Table 2-28 Incoming Data Volume at IP Layer over S1 by eNB

Incoming data
volume at IP 15 minutes, 30 minutes, 1
eNB
layer over S1 by hour, …, one day,…
eNB
Meaning
This indicator reflects the traffic flow at the transmission layer over the S1
interface. It is irrelevant to the transmission media.
Definition
As the data flow might differ from the UL to the DL, two sub-indicators are
involved: outgoing traffic flow at the IP layer over S1 and incoming traffic flow at
the IP layer over S1.
Note that here the packet headers are included.

Incoming traffic flow at IP layer over S1= sum of data volume received by the IP
addresses from the IP layer over the S1 interface
Counter Description
Volume of data received at the IP layer over the S1 interface by the eNB
C373800003
Remarks
None.

2.5.1.5 Traffic Flow over X2 (Temporarily Unavailable)
Table 2-29 Traffic Flow over X2

Traffic flow over 15 minutes, 30 minutes, 1
eNB
X2 hour, …, one day,…
Meaning
This indicator reflects the system load over the X2 interface.
Definition
This indicator is used to collect the traffic flow of the IP layer at the transport layer
over X2. As the data flow might differ from the UL to the DL, two sub-indicators
are involved: UL traffic flow over X2 and DL traffic flow over X2.

UL traffic flow over X2=sum of the data rate sent from the IP address over X2 to
the transport IP layer
DL traffic flow over X2=sum of the data rate received from the transport IP layer
to the IP address over X2
The unit is bit/s.
Counter Description
None.
Remarks
None.
2.5.1.6 Throughput at the MAC Layer
Table 2-30 Throughput at the MAC Layer

Throughput
at the MAC Cell
layer
Meaning
This indicator reflects the system load at the MAC layer. It also indicates the
network load and system processing capability to some extent.

Definition
The statistics is collected from UL and DL separately.
Note that "DL" indicates the direction from the eNB to the UE; "UL" indicates the
direction from the UE to the eNB.

UL throughput of the cell at the MAC layer=data rate received at the MAC layer
DL throughput of the cell at the MAC layer=data rate sent from the MAC layer
Data rate received at the MAC layer equals the number of PDUs sent by the UE
and received by the eNB x PDU load at the MAC layer in the UL.
Data rate sent from the MAC layer equals the number of PDUs sent by the eNB x
PDU load at the MAC layer in the DL.
UL throughput at the MAC layer of the eNB=sum of the data rate received at the
MAC layer of all cells within the eNB (temporarily unavailable)
DL throughput at the MAC layer of the eNB=sum of data rate sent from the MAC
layer of all cells within the eNB (temporarily unavailable)
The unit is Mbit/s.
Counter Description
UL throughput at the MAC layer of the cell is reflected by the following data:
UL maximum throughput at the MAC layer of the cell C373343723
UL minimum throughput at the MAC layer of the cell C373343724
UL mean throughput at the MAC layer of the cell C373343725
DL throughput at the MAC layer of the cell is reflected by the following data
DL maximum throughput at the MAC layer of the cell C373343720
DL minimum throughput at the MAC layer of the cell C373343721
DL mean throughput at the MAC layer of the cell C373343722
Remarks
UL data rate at the MAC layer of the cell=sum of UL and DL TB Block Size of all
TTI scheduling/total TTIs
2.5.1.7 SDU Bit Rate at the PDCP Layer
Table 2-31 SUD Bit Rate at the PDCP Layer

SUD bit rate

at the PDCP Cell
layer
Meaning
This indicator reflects the system user plane load at the PDCP layer. It also
indicates the network load and system processing capability to some extent.
Definition
The statistics is collected from UL and DL separately.
Note that "DL" indicates the direction from the eNB to the UE;
"UL" indicates the direction from the UE to the eNB.

UL SDU bit rate at the PDCP layer of the cell (including all QCIs)=data rate
received at the PDCP layer of the cell, sum of all QCIs
DL SDU bit rate at the PDCP layer of the cell (including all QCIs)=data rate sent
by the PDCP layer of the cell, sum of all QCIs
UL SDU bit rate at the PDCP layer of the eNB=sum of the data rate received at
the PDCP layer of all cells within the eNB (temporarily unavailable)
DL SDU bit rate at the PDCP layer of the eNB=sum of the data rate sent by the
PDCP layer of all cells within the eNB (temporarily unavailable)
The unit is kbit/s.
Counter Description

UL SDU bit rate at the PDCP layer of the cell (including all QCIs)=sum of the
following items:
UL mean PDCP SDU bit rate on the user plane of the cell (QCI=1)C373374204
UL maximum PDCP SDU bit rate on the user plane of the cell C373374240
UL mean PDCP SDU bit rate on the control plane of the cell C373374200
DL SDU bit rate at the PDCP layer of the cell (including all QCIs)=sum of the
following items:
DL mean PDCP SDU bit rate on the user plane of the cell (QCI=1) C373374213
DL maximum PDCP SDU bit rate on the user plane of the cell C373374241
DL mean PDCP SDU bit rate on the control plane of the cell C373374202
Remarks
-UL SDU bit rate at the PDCP layer of the cell= sum of throughput received at the
PDCP layer of the cell during all TTIs/sum of all TTIs;
-DL SDU bit rate at the PDCP layer of the cell=sum of throughput sent at the
PDCP layer of the cell during all TTIs/total TTIs

2.5.2 Radio Resource Usage
2.5.2.1 Average PUSCH PRB Use Rate
Table 2-32 Average PUSCH PRB Use Rate

Average PUSCH 15 minutes, 30 minutes,
Cell
PRB use rate 1 hour, …, one day,…
Meaning
This indicator reflects the radio resource usage of the system. It serves as a basis
for system expansion and algorithm improvement.
Definition
This indicates the usage of the PRB assigned to the PUSCH.
Average PUSCH PRB use rate=mean value of all PUSCH PRB use rates during
all TTIs=number of actually used PUSCH PRBs within the cell/number of
available PUSCH PRBs within the cell = C373424600 / C373424601
Counter Description
Number of actually used PUSCH PRBs within the cell C373424600
Number of available PUSCH PRBs within the cell C373424601
Remarks
PUSCH PRB use rate in a TTI=number of used PUSCH PRBs each TTI/total
PUSCH PRBs each TTI
2.5.2.2 Average PDSCH PRB Use Rate
Table 2-33 Average PDSCH PRB Use Rate

Average PDSCH 15 minutes, 30 minutes,
Cell
PRB use rate 1 hour, …, one day,…
Meaning
This indicator reflects the radio resource usage of the system. It serves as a basis
for system expansion and algorithm improvement.
Definition

This indicates the usage of the PRB assigned to the PDSCH.

Average PDSCH PRB use rate=mean value of all PDSCH PRB use rates during
all TTIs=number of actually used PDSCH PRBs within the cell/number of
availalble PDSCH PRBs within the cell = C373424602 / C373424603
Counter Description
Number of actually used PDSCH PRBs within the cell C373424602
Number of available PDSCH PRBs within the cell C373424603
Remarks
PDSCH PRB use rate in a TTI=number of used PDSCH PRBs each TTI/total
PDSCH PRBs each TTI
2.5.2.3 Average PRACH Resource Use Rate
Table 2-34 Average PRACH Resource Use Rate

Average PRACH 15 minutes, 30 minutes,
Cell
resource use rate 1 hour, …, one day,…
Meaning
This indicator reflects the network access capability to some extent. It serves as a
basis for system parameter improvement.
Definition
Average PRACH resource use rate=number of used PRACH resources/total of
UL occupied PRBs of the cell=C373424634 / C373424608=used PRACH
resources at the carrier frequency within the cell/total used PRBs in the UL within
the cell
Counter Description
Number of used PRACH resources at the carrier frequency within the cell
C373424634
Total of used PRBs in the UL within the cell C373424608
Remarks

PRACH resources consist of those in the time domain, frequency domain, and
code domain.
Number of used PRACH resources indicates the amount of PRACH that are
successfully analyzed by the eNB for Preamble, including public Preamble and
dedicated Preamble.
2.5.2.4 Maximum/Mean TX Power Use Rate of the Cell (Temporarily

Unavailable)
Table 2-35 Maximum TX Power and Mean TX Power of the Cell

Maximum/mean
15 minutes, 30 minutes,
TX power usage Cell
1 hour, …, one day,…
of the cell
Meaning
This indicator reflects the TX power use rate, that is, the maximum DL load and
mean DL load of the system during a period.
As the link budget and capacity simulation are performed according to the preset
DL load during network planning, statistics collection concerning the DL TX
power use rate of cells in the actual network benefits the network expansion
planning and network optimization.
Definition
Maximum TX power use rate of the cell=max. TX power of the cell/configured
max. TX power of the cell x 100%
Mean TX power use rate of the cell=mean TX power of the cell/configured max.
TX power of the cell x 100%
Counter Description
None.
Remarks
The maximum TX power of the cell indicates the maximum value of all test points
(10 ms for example) during a period (15 minutes for example).
The mean TX power of the cell indicates the mean value of all test points in the
statistical period.

2.5.2.5 Paging Congestion Rate
Table 2-36 Paging Congestion Rate

Paging 15 minutes, 30 minutes,
Cell
congestion rate 1 hour, …, one day,…
Meaning
This indicator reflects the paging channel resource usage at the RAN side. It can
also affect the UE perception of the network.
Definition
The paging congestion rate reflects the paging message transfer failures owing
to resource restriction.
Paging congestion rate=paging congestion times/paging transfer times x 100%=
C373394401 / (C373394400 + C373394401), in which, paging transfer
times=paging congestion times + successful paging transfer times=C373394400
+ C373394401
Counter Description
(1) Paging congestion times: indicate the paging transfer failures.
When the eNB sends the paging message to the UE, the FP cannot insert the
paging record into the PCCH frame owing to "full paging occasions".
C373394401
(2) Successful paging transfer times: indicates the paging transfer successes.
When the eNB receives the RRCConnectionSetupComplete message from the
UE as a paging message response, you can infer that the paging transfer
succeeds.C373394400
Remarks
None.
3 Radio Network KPIs Query Guide
3.1 Creating an Index

This procedure describes how to create an index, which includes KPI and PI.
The maintenance engineers can create customized indexes, which can be used for
setting
the alarm thresholds for the threshold task.

Some common indexes are predefined in the system. The maintenance engineers can
create customized index based on their needs.
Prerequisite
Counters and formulas used by the performance index are known.
Steps
1. On the menu bar of the client window, select Performance > Counter and Index
Management. The Counter and Index Management tab is displayed.
2. On the Model Management tab in the left pane, expand the Resource Type
navigation tree.
3. Select an index type to be created (This procedure uses the creation of a KPI as an
example). The existing indexes of the MO type are displayed on the Counter and
Index Management tab, see Figure 3-4.
Figure 3-4 Counter and Index Management Tab
4. Click “add” . The Add Index dialog box is displayed. Set the basic information of the
index, see Figure 3-5.

Figure 3-5 Add Index-Basic Information Tab
5. Click the Index Formula tab. Edit the formula based on the counters and operators.
a. In the Select counters and indices area, expand the counters and indexes, see
Figure 3-6.

Figure 3-6 Add Index-Index Formula Tab
6. Click the Preset Threshold tab to set the alarm threshold, see Figure 3-7.

Figure 3-7 Add Index-Preset Threshold Tab
7. Click OK.
– End of Steps –
3.2 Creating a Measurement Task

This procedure describes how to create (or add) a performance measurement task.
In the performance measurement task, the maintenance engineers specify the NE to be
measured, the MO type, the time interval for collecting performance data, and the time
period for collecting performance data. Based on the preset conditions, the measurement
task collects the performance data from NEs.
Prerequisite
A plan has been designed for the NE to be measured, the PO, the time interval for collecting
performance data, and the entire period for collecting performance data.
Steps
1. On the menu bar of the client window, select Performance > Measurement Task
Management. The Measurement Task Management tab is displayed.
2. To create a measurement task, perform one of the following steps:
l On the toolbar, click .
l From the NE Tree in the left pane, right-click an NE, and select Add Measurement

Task from the shortcut menu.

l From the measurement task list, right-click an existing task, and select Add
Measurement Task from the shortcut menu.
3. On the Measurement Task tab, select an NE type from the NE type list, an MO type
from the MO type list, a Task Type and a PO on the PO tree, see Figure 4-1.
Figure 4-1 Add Measurement Task-Measurement Task Tab
4. Click the Location tab and select an NE(s) and an MO(s) corresponding to the NE(s),
see Figure 4-2.

Figure 4-2 Add Measurement Task-Location Tab
5. Click the General tab and set the general information of the measurement task, see
Figure 4-3.
Figure 4-3 Add Measurement Task-General Tab
6. Click OK.
The newly created measurement task is displayed on the Measurement Task
Management tab, see Figure 4-4.

Figure 4-4 Measurement Task Management Tab
– End of Steps –
3.3 Creating a Query Template and Query Data
3.3.1 Creating a Query Template

This procedure describes how to create (add) a query template.
Maintenance engineers can save the query conditions in a query template for future use.
In addition, the query template can also be used by a query template task.
The conditions included in a query template are the index/counter to be queried, the NE
to be queried, and the period to be queried.
Prerequisite
A performance measurement task is created, and the query conditions to be set are
included in the performance measurement task.
Steps
1. On the menu bar of the client window, select Performance > Query Template
Management. The Template Management tab is displayed.
2. On the left Template Management pane, right-click History Performance Data
Query Template. On the template management toolbar, click the button. The Add
Template dialog box is displayed, seeFigure 5-2.

Figure 5-2 New Template Dialog Box
3. Enter a name in the Name text box. Select Operation mode and Access Type of the
template.
4. Click OK. The Add Query Template dialog box is displayed, see Figure 5-3
Figure 5-3 Add Query Template—Index/Counter Selection Tab
5. Select the counter and index to be queried.

6. Click the Object Selection tab. Select the NE to be queried, see Figure 5-4.

Figure 5-4 Add Query Template—Object Selection Tab
7. Click the Time Selection tab. Configure the Query granularity, Time settings,
Effective date, and Effective time, see Figure 5-5.
Figure 5-5 Add Query Template—Time Selection Tab
8. Click OK. The query template is successfully created.

3.3.2 Querying History Performance Data by Templates

Prerequisite
l The measurement task related to NE is created and has been operating for a period
of time.
l The collected performance data is stored in the performance database on the
NetNumen U31 server.
l The template for the performance data query is created.
Steps
l For the History Performance Data Query Template, the querying NE, period and
performance indexes are predefined in the template. The maintenance person can
perform the following steps to execute the template directly.
1. On the menu bar of the NetNumen U31 client, select Performance > Template
Task Management. The Template Task Management tab is displayed.
2. In the left Template Management pane, click History performance Data Query
Template.
3. In the right Template Management tab, right-click a template, and select Query
by Template from the shortcut menu.
4 Radio Network KPIs Optimization
4.1 Optimization of the Access KPI
The signaling process comprises three phases:
 RRC setup process
This process includes initial transfer and security control mode;
 E-RAB establishment process
Currently, the E-RAB establishment rarely fails.
 Radom access process
Multiple problems of random access lead to no RRC connection response, causing call
failure.
Therefore, solving random access failures is the key to improving the connection success
rate.

Figure 4-1 Analysis of Connection Success Rate
DT data
N
Attach Fail
RRC connection Y Random access

setup failure problem
Initial transfer Y Authentication and

failure encryption problem
RRC connection Y E-RAB establishment

reconfiguration problem
failure
Exceptions
End
4.1.1 Problem Analysis of the Random Access Process
The random access process is based on either contention or non-contention. The

difference lies in that the contention-based random access flow requires that the UE
randomly selects a random prefix from the contention-based random access prefixes
according to the algorithms; the non-contention based random access flow defines that
the eNB assigns the non-contention random access prefix for the UE through the
dedicated DL signaling. The initial access process is based on the contention mechanism,
while the handover flow is based on the non-contention mechanism.

Figure 4-2 Contention-Based Random Access
UE eNB
1 Random Access Preamble

（MSG1）
Random Access Response 2

（MSG2）
3 Scheduled Transmission
（MSG3）
Contention Resolution 4
（MSG4）
MSG1: The UE transmits random access preamble in the PRACH;
MSG2: The MAC layer of the eNB responds to the random access and thus sends a
message in the PDSCH.
MSG3: The RRC layer of the UE sends an RRC Connection Request in the PUSCH.
MSG4: The RRC layer of the eNB sends an RRC Connection Setup message in the
PDSCH.
Till now, the contention resolution of the contention-based random access flow is
complete. The RRC layer of the UE sends the RRC Connection Setup Complete
message to the eNB.
From the perspective of the UE, the random access failure might occur due to one of the
following assumptions:
Whether the UE receives the MSG2 upon its sending of MSG1;
Whether the UE sends the MSG3 successfully;
Whether the UE properly receives the MSG4.

4.1.1.1 Whether the UE Receives the MSG2 upon its Sending of MSG1
Figure 4-3 Analysis of MSG1
PRACH Trigger，cause：
connection request
N
Whether MSG1 is sent? Troubleshoot the terminals
Y
Analyze problems in the UL
according to the packets received
N N in PRACH of the MTS
Whether the PDCCH is
Whether MSG2 is received?
received?
Y
Y Analyze problems in the DL
together with RSRP and SINR
MSG3 process analysis
When the MSG2 is not received by the UE after MSG1 is sent, the UE retransmits the
MSG1 according to the PRACH transmission period. If the PDCCH of MSG2 is not
received, the UE can separately analyze the problems both the UL and the DL.
UL:
1. Determine whether MSG1 is received in the UL according to the packets received in

PRACH of the MTS.
2. Check whether the reception success rate in the UL of the MTS is > -99 dBm. If such
value persists, handle the interference such as GPS cross timeslot interference in the
UL.
3. PRACH related parameter adjustment: Increase the expected PRACH RX power,

extend the power ramping step of PRACH, and lower the detection threshold of the
absolute prefix of PRACH.
DL:

1. The UE cannot receive the RA_RNTI scrambled PDCCH. Check whether the DL
RSRP is >-119 dBm and SINR>-3 dB. The DL coverage problems can be handled
through the adjustment of engineering parameters, RS power, and PCI.
2. Adjustment of the PDCCH related parameters: increase the initial value of the CCE
aggregation degree of the public space.
4.1.1.2 Whether the UE Sends the MSG3 Successfully
Figure 4-4 Analysis of MSG3
MSG2 is received by the

UE
N
Check the UL authorization
Whether the PUSCH of MSG3 is sent?
message carried on MSG2
Whether the eNB receives the RRC N

UL problems troubleshooting
connection request?
MSG4 analysis process
According to the random access flow, if the MSG3 is not transmitted upon the UE’s
reception of MSG2, check whether the authorization message carried on MSG3 is correct.
If the PUSCH of MSG3 is sent by the UE, check the signaling at the eNB as to whether
the RRC Connection Request is received on the eNB side. If the RRC Connection Setup
is sent from the eNB side whereas the request is yet received at the foreground, analyze
the MSG4 process, as indicated in section 2.1.3; if the RRC Connection Request is not
received at the eNB side, you can infer that faults occur in the UL.
1. Check whether the RX power of the UL channel in MTS > -99 dBm. If such value
persists, handle the UL interference problems.

2. Check whether the MSG3 power parameters carried in the RAR are proper. Adjust
the TX power of MSG3 when needed.
4.1.1.3 Whether the UE Properly Receives the MSG4
“MSG4 fail” occurs in the random access process. The failure reason says “failure at
MSG4 due to CT timer expired”, in which, “CT timer” indicates the conflict test timer. That
is, the UE starts the CT timer to await the MSG4 after the UE sends the MSG3. If the time
expires before the MSG4 is received, random access fails. The analysis is detailed in
Figure 4-5.
Figure 4-5 Analysis of MSG4 Failure
RRC Connection Setup request

is sent by the eNB
1. Adjust the coverage according to

RSRP and SINR
Whether the UE receives the PDCCH N 2. Adjust the aggregation degree of

of MSG4 the dedicated PDCCH
3. Increase the power offset of

PDCCH DCI 1A
Y
N Y
Whether the UE receives MSG4 Whether the PDCCH is Check the message carried in the
retransmitted retransmitted PDCCH
Y Solve the PDSCH

reception problem
End
Check whether the UE receives the PDCCH. If the PDCCH is not received, solve the
PDCCH reception problem in terms of DL signal analysis and parameters.
Check whether PDSCH is received after PDCCH is received multiple times.
Determine whether the received PDCCH is retransmitted.

Check whether the DCI format of the retransmitted message is correct.
When PDSCH is not received, check the MCS used by the PDSCH and the PA
parameter configuration. Increase the distributed RB number in the PDSCH.
4.1.2 Problem Analysis of Authentication and Encryption
None.
4.1.3 Problem Analysis of E-RAB Establishment
None as currently no E-RAB establishment fails.
4.2 Optimization of the Handover KPI
When any exception occurs, we should check whether the eNB and the transmission
work properly. If positive, analyze the handover process.
During the handover process, perform the following steps to analyze the exceptions:
Is the handover command received upon the sending of measurement report?
Is MSG1 sent successfully at the destination side after receiving the reconfiguration
command?
Is MSG2 is received after MSG1 is delivered successfully?
Figure 4-6 shows the overall process flow diagram of the handover problem analysis.
When a certain process has problem, we can check the corresponding process step to
solve it out.

Figure 4-6 Process of Analyzing Handover Problem
Measurement
Report
Is handover
No command
received?
Flow 1
Yes
Is MSG1 sent
No
sucessfully?
Flow 2
Yes
Is RAR
No
received?
Flow 3
Yes
Send
reconfiguration
complete
（ MSG3（
End
4.2.1 No Handover Command Received upon the Sent Measurement

Report
This problem often occurs at field and it is relatively difficult to be located and solved. See
Figure 4-7 for the analysis process of it.
The eNB has not received the measurement report (can be checked through the
background signaling tracing):
Check whether the coverage point is reasonable. This can be determined by checking
several factors, including checking whether the coverage of RSRP and SINR in the
measurement report is good, if the UE is at cell edge or limited uplink power exists

(determined by the path loss estimated at the downlink EU). If any of these problems
exists, adjust the coverage and handover parameter to solve it.
For field test, it is suggest that the coverage of RSRP at handover point is greater than
-120dBm and SINR no less than -5dB.
Check if any uplink interference by checking the MTS at background. For example, the
BS noise floor when without EU accessed is about -98db at 20M bandwidth condition. It
must be some uplink interference if the noise floor is too high in the condition of without
user connected. If any, check if it is caused by losing lock of GPS in other neighbor cells
first. As the current version does not support the function of locating interference source
through background tool, it can only be troubleshot by closing the nearby sites and
performing CW test with Scanner.
The eNB has received the measurement report:

1. No handover command sent to the UE:
i. Confirm if the destination cell is missing neighbor cell, which is relatively easy
to be checked out from the background, just by checking the background
signaling tracing information to see if the eNB sends handover request to the
destination cell after receiving the measurement report. It can also be
determined from the foreground. When access to or hand over to the source
eNB, there should be a PCI carried by the UE measurement report in the
neighbor list in the field “MeasObjectToAddModList” of the reconfiguration
command. If negative, it is the problem of neighbor missing. Refer to Error!
Reference source not found. for details. If it is confirmed that the problem is
caused by neighbor list missing, add neighbor cell.
ii. If the measurement report is received after neighbor cell is configured, the
source eNB will send the handover request to the destination eNB over the
X2 or S1 interface (if no X2 association is configured). Now it is necessary to
check whether the destination eNB has not sent HO request
acknowledgement to the source eNB (Step 4 in Error! Reference source
not found.), or HANDOVER PREPARATION FAILURE signaling is returned.
In this case, the source eNB will not send the handover command to the UE
either.
Now we need to locate the problem from the following three aspects:

 Several factors including the destination eNB preparation failure, RNTI

preparation failure, and PHY/MAC parameter configuration exception and so
on may lead to returning a HANDOVER PREPARATION FAILUE
message from the destination eNB.
 Transmission link exception may result in no response from the destination

eNB;
 Destination eNB status exception may cause no response from the destination
eNB.
2. Handover command sent to the UE:
The coverage of the reported point on the measurement report should be checked. If it
is checked as a weak field or a strong interfered area, it is recommended to solve the
coverage problem by adjusting engineering parameters first. If coverage cannot be
adjusted easily, adjust handover parameters.

Figure 4-7 Process Flow When No Handover Command Received upon the Sent
Measurement Report
Flow 1
Has the serving

cell received the
measurement
report?
No
Yes
Is it neighbor
No
missing?
Is the coverage of the
tested point
Check if any reasonable?
Solve the problem Yes
problem in target
of target eNB
eNB status, Yes
abnormality and Yes
admission
transmission
parameter and
transmission? Is there uplink Optimize neighbor
interference ? cell
No Yes
No
Optimize coverage Check and

and handover remove the
parameter interference
Is the problem
No
solved?
Yes
End
4.2.2 MSG1 Sending Exception at Destination Cell
In normal condition, the coverage of the reported cell on the measurement report is better
than that of the source cell. Whereas the possibility of the destination cell’s coverage
changes abruptly cannot be ruled out. So the handover problem caused by the coverage
of the testing environment can be excluded. For this kind of problem, it is suggested to

adjust coverage preferentially. If coverage cannot be adjusted easily, adjust handover

parameters.
If the coverage is stable and sending cannot be done normally, then it is required to
check whether there is uplink interference at the eNB. Refer to Error! Reference source
not found. for details about this problem.
Flow 2
Is the coverage of
testing point
reasonable?
Yes
Is there
interference in
No uplink of cell?
Yes
Check and
remove the
interference
Optimize the
coverage and/or
handover
parameters
Is the problem
No
solved?
Yes
End
4.2.3 RAR Reception Exception
For the exceptional RAR received the wireless environment of the testing point need to
be checked. The process to solve this kind of problem is similar as optimizing coverage
first. If coverage optimization is not feasible, adjust handover parameter.

Flow 3
Optimize coverage
and handover
parameter
No
Is the problem
solved?
Yes
End

4.3 Problem Analysis of Call Drops
Call drops in TDD LTE indicate that the UE is in connected state after it finishes the
process of RRCConnectionReconfigurationComplete. The link asynchronism in both
the UL and DL, however, occurs later owing to interference, weak fields, or other causes.
The re-establishment is then triggered but rejected. All releases that are not initiated by
the UE are deemed as call drops.
 No Response from RRC Re-establishment Request
Figure 4-8 No Response from RRC Re-establishment Request
 RRC Connection Re-establishment Rejected

Figure 4-9 RRC Connection Re-establishment Rejected
 Exceptional RRC Connection Release Received
Figure 4-10 Exceptional RRC Connection Release Received
For call drop problems caused by exceptional releases, the RRC connection
re-establishment mechanism is introduced. Two concerns are listed below:
 Causes of the re-establishments
 Causes of re-establishment failures
Based on the previous two concerns, the analysis of call drops is illustrated below:

Figure 4-11 Analysis of Call Drops in TDD LTE
Call drops in TDD

LTE networks
Exceptional RRC RRC re-

release caused establishment
call drops related call drops
Type A Type B
Call drops caused by

exceptions in the Bugs of the version
devices on the eNB side RRC re-
Trigger RRC re- Under warranty
establishment Exceptions of the network
establishment
rejected
B-1
B-2
DL interference
Improper settings UL interference Without DCI0,
1 Poor PUCCH
Handover exceptions RLC sent max
SR sent max times 1 Neighboring cell
for the timer times before RLF
Power before relation;
caused call drops UL DATA 2 Handover parameters
2 UL RRU
interference
Random access fails
upon UL_DATA.
MSG1 to MSG4 transfer
to the random access
process
For call drop problems, you need to first determine whether it is the coverage and
interference problem. Use the CNT tool to check the values of the DL RSRP and SINR. If
the RSRP <-115 and SINR < -3, you can infer that the ratio of call drops is high. To check
the UL interference, use the test tool at the eNB side.
The following problem analysis is based on the call drop cases occurred during the
network optimization in the Japanese projects.
4.3.1 Re-Establishment Cause
4.3.1.1 Improper Setting for Timer Related Parameters
The recommended timer related parameters are provided in Table 4-1:

Table 4-1 Recommended Timer Related Parameters
Recommended
Field Name Meaning
Value
The timer for UE to detect radio link
byT310_Ue 2000 ms
failure(T310_UE)
The timer for UE to detect radio link failure and
byT311_Ue 30000 ms
switch to idle(T311_UE)
The timer for UE to wait for RRC connection
byT300 2000 ms
response (T300)
The timer for UE to wait for RRC connection
byT301 2000 ms
re-establishment response (T301)
The Timer for UE to Wait for RRC Connection
byT302 1s Request Retry After Reception of RRC Connection
Reject (T302)
byT304 1000 ms The timer for UE to wait for handover successfully
byT304_Cc The timer for UE to wait for handover
4000 ms
o successfully(cco)
byT320 5 min The priority timer for cell reselection (T320)
Maximum number of consecutive out-of-sync
byN310 6
indications (N310_UE)
Maximum number of consecutive in-sync indications
byN311 1
(N311)
The parameters shown in the previous table are recommended default values. If call
drops occur, check the corresponding time periods and then consider timer adjustment
globally. For details, refer to TDD LTE Network Parameter Optimization Guide.
4.3.1.2 UL Interference
The UL interference includes
 Interference between users;
 Interference caused by device faults;
 Interference caused by band interference
In most cases, UL interference results in handover failures, re-establishment failures, and

call drops.

4.3.1.3 Interference in the DL
Interference in the DL is another cause for call drops. Usually, no main coverage cell is
available. The RSRP for both the server cell and the neighboring cells are close while the
SINR is poor, causing the demodulation signals to be very weak. Thus, call drops occur.
As in the Japanese project, omni-directional antennas are used, the roofing parameters
cannot be modified. The temporary solution is reduce the power and set the super cell. A
regular solution, however, conforms to the following priority:
1. Modification of the roofing parameters;
2. Modification of the coverage and handover related parameters;
3. Adjustment of the power.
As for the scenario with directional antennas, more cases and analysis will be added in
later document versions.
4.3.1.4 Handover Preparation
In regular cases, if the UE fails to report MR at good timing, the signals of the server cell
jitter fast, causing call drops. The reason is that either handover demands are not met or
the handover is performed too early. The handover parameters are A3_offset, TTT, and
Hysterisis. Too complicated or too simple settings for the three parameters will cause call
drops owing to bad timing. The three parameters are displayed on the IE tree, as shown
in Figure 4-12.

Figure 4-12 Handover Parameters
The signaling of handover failure obtained from the CNT tool is displayed in the blue
circle, and the signaling of handover success is displayed in the red circle, as shown in
Figure 4-13.
Figure 4-13 Signaling of Handover Failure vs. Signaling of Handover Success
4.3.1.5 No Handover Commands Upon Measurement Reports
As the UE is entitled to detect all cells of all bands and once the report demands are met,
the MR will be reported. If the setting of the neighboring cell relation is improper on the
OMC, the eNB will not issue the handover commands. In signaling, no handover
command is issued after the UE produces multiple MRs, and thus the radio link expiration,
followed by call drops.

4.3.2 UE Triggered Re-Establishment
4.3.3 No Response from the UE Triggered Re-Establishment
Currently, no such phenomenon as “no response from the UE triggered re-establishment”

is found. If such cases should occur, relevant analysis will be added in later versions.
According to the experience from network optimization work, the previously-mentioned

phenomenon is triggered when the UE sends the re-establishment message due to
relatively weak coverage field strength, exceptional UL power, and interferences.
According to the solving flow of the call drop problem, you need to first determine whether
it is a common or specific problem; then check whether hardware alarms are reported in
the server cell or target cell where call drops occur before checking the coverage,
interference, and parameter settings.
4.3.3.1 RRC Connection Reestablishment Reject
The signaling for the “RRC Connection Reestablishment Reject” problem is displayed as
shown in Figure 4-14.
Figure 4-14 RRC Connection Reestablishment Reject
In most cases, “RRC Connection Reestablishment Reject” is due to the version problem,
packet errors in the UL/DL, and equipment faults.

TDD LTE KPI Optimization Guide

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

TDD LTE KPI Optimization Guide

Uploaded by

Copyright:

Available Formats

TDD LTE KPI Guide_R1.

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. I

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. II

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. IV

Intended Audience: TDD LTE network planning and optimization engineers

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. V

About This Document

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. VI

2 Radio Network KPIs............................................................................................ 3

Figure 2-1 Access Signaling....................................................................................................... 3

Table 2-1 RSRP..........................................................................Error! Bookmark not defined.

Table 2-26 UL PDU RBLER at MAC ........................................................................................ 44

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. IX

This document serves as an analysis guide to LTE KPIs.

In this document, the KPIs are interpreted in details in different categories.

1.2 Terms and Abbreviations

Abbreviation English Spelling Chinese Meaning

KPI Name Time Granularity Region Granularity

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. 1

KPI Name Time Granularity Region Granularity

 KPI Name: indicates the name of the performance indicator.

 Remarks: indicate the additional information that needs attention.

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. 2

2 Radio Network KPIs Introduction

2.1 Call Setup Related Indicators

Figure 2-1 Access Signaling

UE eNB MME SGW PDN GW

(1) RRC Connection Request

(2) RRC Connection Setup

(3) RRC Connection Complete

(4) Service Request (NAS signal)

(6) RRC Connection Reconfiguration

(7) RRC Connection Reconfiguration Complete

(8) Initial Contest Setup Response

(9) Update Bearer Request

(11) Update Bearer Response

(12) Update Bearer Response

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. 3

2.1.1 RRC Connection Setup Success Rate (Service Related)

Table 2-1 Service Related RRC Connection Setup Success Rate

RRC connection setup 15 minutes, 30 minutes, one

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. 4

Successful RRC connections (service-related)=

RRC connection attempts (service-related)=

2.1.2 RRC Connection Setup Success Rate

Table 2-2 RRC Connection Setup Success Rate

KPI Name Time Granularity Region Granularity

RRC connection setup 15 minutes, 30 minutes, one Cell, eNB

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. 5

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. 6

Number of successful RRC connections:

Number of RRC connection attempts:

Number of RRC connection requests (mo-Signalling type)

Number of RRC connection requests (mo-Data type)

Number of RRC connection requests (highPriorityAccess type)

2.1.3 E-RAB Setup Success Rate

Table 2-3 E-RAB Setup Success Rate

KPI Name Time Granularity Region Granularity

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. 8

Number of successfully established E-RABs (all QCI)=

E-RAB setup success rate=Number of successful E-RAB connections (all

ZTE Confidential Proprietary © 2012 ZTE Corporation. All rights reserved. 10

Number of E-RAB setup successes=sum of the following counters:

Number of the E-RAB establishment requests=sum of previous requests of all QCIs