FO - NAST3024 LTE KPI Introduction 65P

LTE Radio Network KPI and
Counters
Contents
 Overview of KPIs
 Accessibility KPI and counter
 Retainability KPI and counters
 Mobility KPI and counters
 Integrity KPI and counters
 Availability KPI and counters
 Traffic KPI and counters
 Radio Resource KPI
KPI Overview
 Definition:
 The definitions of Key Performance Indicator (KPI) vary by industries.
 KPIs are important criteria used to evaluate the operation of wireless
networks, for example, wireless call completion rate and wireless call drop
rate.
 A KPI is a value calculated through a series of PIs or counters.
 KPIs reflect the network running status. Therefore, KPI values are
objective criteria and important basis for evaluating network
running status and quality.
© ZTE Corporation. All rights reserved

KPI Related Concepts
 PI
 Although Performance Indicator (PI) as a type of Measure of Performance is
less critical than the KPI, yet it is still used as a reference data to evaluate the
network operation. PI values are obtained through corresponding counters.
 Counter
 Each count corresponds to a counter, and there are thousands of counters in
a system.
 Northbound Counter
 The counter value reported according to the northbound Operation
Management Center (OMC) requirements is computed and reported by a
local counter. Northbound OMC uses these counters to compute KPI values.

Relationship Among KPIs, PIs, Counters, and
Northbound Counters (1)
 All KPIs, PIs, and northbound counters are computed through
original counters, and the corresponding formula are clearly
defined in related standards of ZTE.
 The correctness of original counters and formulas is a
prerequisite for accurate KPI results.
Counter calculate North Counter
calculate PI
calculate KPI

 Counters --- Vegetables
 All KPIs and PIs need to use counters as raw materials for processing and
production.
 Northbound Counters --- Semi-finished Dishes

 Counters reported to northbound counters must be reprocessed by
northbound counters before they become KPIs.

 PIs---Appetizers
 Although a PI is more often than not ignored, yet it has the potential to
become a KPI.
 KPIs---Main Courses
 KPIs are indicators that attract the most attention, and they are the main
course that makes or breaks a meal.

7
Contents
Accessibility
Accessibility
(Category)
Theoretical limit: 100%
Ideal value in a commercial
network: > 98% Initial E-RAB Attach Success Rate Detach Success Rate
Accessibility
RRC Connection RRC

S1-SIG Establish Initial E-RAB Setup
Setup Re-Establishment
Success Rate Success Rate
Added E-RAB Paging Success Rate

Accessibility
Air Interface
RRC Connection Added E-RAB Contention-Based Contention-Free

S1-SIG Establish UE Context Setup
Setup Setup PRACH PRACH
Success Rate Success Rate Performance Performance
E-RAB Setup E-RAB Block Rate

Success Rate (per QCI)
、 Rate, Call Barring Rate

Call Setup Success

Paging Congestion Rate
 Description:
 The KPI shows the probability of dropping a paging record since the waiting
queue is overloaded.
 Signaling Procedure
UE eNB
PAGING
 Formula Definition
 Paging Congestion Rate = Number of paging records discarded at the
eNodeB / Number of paging records received by the eNodeB * 100%
 Paging Congestion Rate = C373394401/C373394400 * 100%

RRC Establishment Success Rate
 Description:
 This KPI shows the probability for a subscriber to be provided with an RRC
connection upon request.
UE EUTRAN
RRCConnectionRequest
RRCConnectionSetup
RRCConnectionSetupComplete
 RRC Establishment Success Rate = Number of successful RRC connection
establishment / (Number of successful RRC connection establishment +
Number of failed RRC connection establishment) * 100%
RRC Re-establishment Success Rate
 Description:
 The KPI shows probability for an end-user to successfully re-establish an RRC
connection at request.
UE eNB
RRCConnectionReestablishmentRequest
1
RRCConnectionReestablishment
2
RRCConnectionReestablishmentComplete
3
 RRC Establishment Success Rate = Number of successful RRC establishments /
Number of RRC Establishment Attempts * 100%

RRC Reconfiguration Success Rate
 Description:
 The KPI shows probability for an end-user to successfully reconfigure a RRC
connection (not for Handover) at request.
 Measurement Method
 Counters at eNodeB side are designed to enable the corresponding
measurement, which are split into sub-counters per failure cause:
 Number of successful RRC connection reconfiguration (not for Handover)
 Number of failed RRC connection reconfiguration (not for Handover)
 RRC Reconfiguration Success Rate(non handover) = Number of successful
RRC Reconfiguration (non handover) / Number of RRC Reconfiguration
attempts (non handover) × 100%

E-RAB Setup Success Rate
 Description:
 The KPI shows probability for an end-user to successfully setup a ERAB at request.
eNB MME eNB MME
INITIAL CONTEXT SETUP REQUEST E-RAB SETUP REQUEST
INITIAL CONTEXT SETUP RESPONSE E-RAB SETUP RESPONSE
 E-RAB Setup Success Rate = (Number of successful initial E-RAB + Number of
successful added E-RAB establishment) / (Number of successful initial E-RAB
establishment + Number of failed initial E-RAB establishment + Number of
successful added E-RAB establishment + Number of failed added E-RAB
establishment) * 100%

E-RAB Modify Success Rate
 Description:
 The KPI shows probability for an end-user to be provided with a modified E-
RAB at request within the E-RAB Modification procedure.
measurement, which are split into sub-counters per QCI and per failure cause:
 Number of successful bearers modification per QCI
 Number of failed Bearers modification per QCI and per failure cause (admission
control failure, Uu interface failure, handover trigger, parameter error, other reason).
 E-RAB Modify Success Rate = Number of E-RABs successfully modified the
QoS parameter/ Number of E-RABs attempted to modify the QoS parameter
× 100%

UE Context Establishment Success Rate
 Description:
 The KPI shows probability for an end-user to successfully establish UE context
at each attempt.
eNB MME
INITIAL CONTEXT SETUP REQUEST
INITIAL CONTEXT SETUP RESPONSE
 UE Context Establishment Success Rate = Number of successful UE Context
establishment / Number of UE Context establishment attempts × 100%

Security Mode Success Rate
 Description:
 The KPI shows probability for an end-user to successfully configure AS
security at request.
measurement, which are split into sub-counters per failure cause:
 Number of successful security mode configuration
 Number of failed security mode configuration
 Security Mode Success Rate = Number of successful Security Mode / Number
of Security Mode attempts × 100%

Contents
Retainability
 Theoretical limit: 0%
 Ideal value in a commercial network: < 2%
Retainability
(Category)
UE E-RAB E-RAB Drop

UE E-RAB RRC Drop Rate Active E-RAB
Retainability Rate
Retainability Drop Rate
Per QCI (Per QCI)
How Often Percentage
E-RAB UL Data E-RAB DL Data

E-RAB Duration
Volume Volume
Time per QCI Drop
Per QCI Drop Per QCI Drop
QoS Before Drop

RRC Drop Rate
 Description:
 The KPI shows probability for an end-user to lose the RRC connection.
measurement, which are split into sub-counters per release cause:
 Number of abnormal RRC connection release per release cause (These counters are
provided on per cell basis granularity in a non-overlapping 15 minute periodicity, at
the beginning of which they are re-initialized with the default value.)
 Number of successfully established RRC connection, including initial RRC
connection establishment and handover in/out RRC connection(These counters are
provided on per cell basis granularity in a non-overlapping 15 minute periodicity.
This measurement is obtained by accumulating the number of established RRC
connections during the measurement period.)
 RRC Drop Rate = Number of RRC connection released abnormally by eNodeB
/ Number of successful RRC establishments × 100%

RRC Abnormal Release Rate
 Description:
 The KPI shows percentage of RRC abnormal release among RRC release due
to all causes.
measurement, which are split into sub-counters per establishment cause and
per failure cause:
 Number of abnormal RRC connection release
 Number of normal RRC connection release
 RRC Drop Rate = Number of RRC connection released abnormally by eNodeB
/ Number of successful RRC establishments × 100%

E-RAB Drop Rate
 Description:
 This KPI shows the probability for an a subscriber to loss the E-RAB, such as
an event being released by the eNodeB due to overload control.
eNB MME
1E-RAB RELEASE INDICATION
 E-RAB Drop Rate = Number of Abnormally Released E-RAB / Number of
Successfully Established E-RAB * 100%

E-RAB Abnormal Release Rate
 Description:
 The KPI shows percentage of E-RAB abnormal release among E-RAB release
due to all causes.
per failure cause:
 Number of abnormal E-RAB Release
 Number of normal E-RAB Release
 E-RAB Abnormal Release rate = Number of E-RABs released abnormally /
Total number of E-RABs released × 100%

Active E-RAB Drop Rate
 Description:
 The KPI shows probability for an end-user to lose the E-RABs when it is active,
i.e. there was data in the buffer in any of the directions.
per failure cause:
 Number of abnormally released active E-RABs per QCI and per release cause
 Number of successfully established E-RABs per QCI, including local E-RABs
establishments and handover in E-RABs
 Active E-RAB Drop Rate = Number of active E-RABs released abnormally /
Number of E-RABs successfully established × 100%

E-RAB Release Success Rate
 Description:
 The KPI shows percentage of E-RAB successfully released upon EPC request
(E-RAB RELEASE COMMAND).
measurement, which are split into sub-counters per QCI:
 Number of E-RAB release attempt per QCI triggered by EPC (E-RAB RELEASE
COMMAND)
 Number of successful E-RAB Release per QCI triggered by EPC (E-RAB RELEASE
COMMAND)
 E-RAB Release Success Rate = 1 - Number of E-RABs failed to release /
Number of E-RABs released × 100%

Contents
Mobility
 Successful Handover Categories
Intra-Freq Intra-Freq Inter-Freq Inter-Freq LTE to UMTS UMTS to LTE LTE to GSM GSM to LTE
Intra-eNodeB Inter-eNodeB Inter-eNodeB Intra-eNodeB
Inter-RAT HO Success Rate
X2 Based HO S1 Based HO
All Incoming HO All Outgoing HO

Per Cell Per Cell
Contention Based Contention Free
HO HO
Intra-RAT HO Success Rate

All Incoming HO All Outgoing HO
Per Cell Pair Per Cell Pair
Troubleshooting

Mobility
UE Source eNB Target eNB MME Serving Gateway
 Handover 1. Measurement Control

0. Area Restriction Provided
packet data packet data
 Handover Preparation Success UL allocation Legend
Rate
L3 signalling
2. Measurement Reports
L1/L2 signalling
3. HO decision
User Data
Theoretical limit: 100%

4. Handover Request
Handover Preparation

5. Admission Control
Ideal value in a commercial

6. Handover Request Ack
DL allocation

RRC Conn. Reconf. incl.
7.
mobilityControlinformation
network：99%
Latency
Detach from old cell
Deliver buffered and in transit
and
packets to target eNB
synchronize to new cell
Interruption Time
Handover Execution
 (Step 4 – Step 6) 8. SN Status Transfer
Data Forwarding
 Handover Execution Success Rate Buffer packets from

Source eNB
9. Synchronisation
 Theoretical limit: 100% 10. UL allocation + TA for UE
11. RRC Conn. Reconf. Complete
 Ideal value in a commercial packet data

packet data
12. Path Switch Request
network: 98%
13. User Plane update
request
End Marker
14. Switch DL path
HO In: Step 6 – Step 11
Handover Completion
packet data
 End Marker
15.User Plane update
response
HO Out: Step 7 – Step 17

16.Path Switch Request Ack

17. UE Context Release
 Mobility Success Rate 18. Release

Resources

 Ideal value in a commercial
network: 97%

Handover Preparation and Execution
Handover Start Point Stop Point
Outgoing The source eNodeB decides to The source eNodeB sends the RRC
handover perform a handover. Connection Reconfiguration message
preparation to the UE.
Outgoing The source eNodeB sends the The source eNodeB receives the UE
handover RRC Connection Reconfiguration Context Release message from the
execution message to the UE. destination eNodeB.
Incoming The destination eNodeB receives The destination eNodeB returns the
handover the Handover Request message Handover Response message to the
preparation from the source eNodeB. source eNodeB.
Incoming The destination eNodeB receives The destination eNodeB sends the
handover the RRC Connection UE Context Release message to the
execution Reconfiguration Complete source eNodeB.
message from the UE.

Cell Handover and Cell Pair Handover
 The outgoing handover preparation success rate for each handover

pair measures the handover preparation from the serving cell to a
certain neighbor cell. Here are two typical examples:
 In the event of the handover from cell A to cell B, the Intra-eNodeB Intra-freq
Outgoing Handover Preparation Success Rate per Cell pair is measured in cell A.
 In the event of the handover from cell B to cell A, the Intra-eNodeB Intra-freq
Outgoing Handover Preparation Success Rate per Cell pair is measured in cell B.
 The outgoing handover success rate contains all outgoing handover

preparation successes from the serving cell to all neighbor cells.
 The measurement of these two KPIs can facilitate us in sifting two
cells that suffer most handover preparation failures, performing
neighbor cell optimization, and even deleting unusable neighbor
cells.

Intra-eNodeB Handover Success Rate
 Description
 The intra-eNodeB handover success rate measures the service continuity
when a subscriber is on the move. This KPI is perceptible to the subscribers,
depending on system handover processing capabilities and network planning.
 Intra-frequency handover success rate = Number of intra-frequency
handover successes / Number of intra-frequency handover requests * 100%
 Inter-frequency handover success rate = Number of inter-frequency
handover successes / Number of inter-frequency handover requests * 100%

Intra-eNodeB Handover Success Rate
UE EUTRAN
Measurement Report
RRC Connection Reconfiguration 2
3
RRC Connection Reconfiguration Complete
4

5
RRC Connection Reestablishment Request

6
 If the eNodeB receives the RRC Connection Reconfiguration Complete message

in step 4, it indicates that the handover is successful.
 If the eNodeB receives the RRC Connection Reestablishment Request message in
step 6, it indicates that the handover is unsuccessful.
Inter-eNodeB X2 Handover Success Rate
 Description:
 The inter-eNodeB X2-interface handover success rate measures the handover
successes when the UE moves between the eNodeBs over the X2 interface. This
KPI is perceptible to the subscribers being on the move, depending on system
handover processing capabilities and network planning.
 Outgoing intra-frequency X2-interface handover success rate = Number of
outgoing intra-frequency X2-interface handover successes / Number of outgoing
intra-frequency X2-interface handover attempts (serving cell) * 100%
 Incoming intra-frequency X2-interface handover success rate = Number of
incoming intra-frequency X2-interface handover successes / Number of incoming
intra-frequency X2-interface handover attempts (serving cell) * 100%
 Outgoing inter-frequency X2-interface handover success rate = Number of
outgoing inter-frequency X2-interface handover successes / Number of outgoing
inter-frequency X2-interface handover attempts (serving cell) * 100%
 Incoming inter-frequency X2-interface handover success rate = Number of
incoming inter-frequency X2-interface handover successes / Number of incoming
inter-frequency X2-interface handover attempts (serving cell) * 100%

Inter-eNodeB X2 Handover Success Rate
SOURCE TARGET MME
UE
EUTRAN EUTRAN
Measurement Report
Handover Request
1 2
Handover Request Acknowledge
3 4

5
6
Handover Preparation Failure
7
RRC Connection Reconfiguration

8

9

10
11
Path Switch Request
12 Path Switch Request Ack

18
13 Path Switch Request Failure
14 Path Switch Request Ack
UE Context Release
16 15
UE Context Release
17

Inter-eNodeB S1 Handover Success Rate
 Description:
 When the eNodeB decides to perform a handover according to the UE measurement report and
meanwhile the destination cell is not connected to the eNodeB through the X2 interface, the inter-
eNodeB S1-interface handover success rate measures the S1-interface handover performed through the
EPC. This KPI is perceptible to the subscribers being on the move, depending on system handover
processing capabilities and network planning.
 Outgoing intra-frequency S1-interface handover success rate = Number of outgoing intra-frequency
S1-interface handover successes / Number of outgoing intra-frequency S1-interface handover attempts
(serving cell) * 100%
 Incoming intra-frequency S1-interface handover success rate = Number of incoming intra-frequency
S1-interface handover successes / Number of incoming intra-frequency S1-interface handover attempts
 Outgoing inter-frequency S1-interface handover success rate = Number of outgoing inter-frequency
S1-interface handover successes / Number of outgoing inter-frequency S1-interface handover attempts
 Incoming inter-frequency S1-interface handover success rate = Number of incoming inter-frequency
S1-interface handover successes / Number of incoming inter-frequency S1-interface handover attempts

Inter-eNodeB S1 Handover Success Rate
UE SOURCE MME TARGET
EUTRAN EUTRAN
Measurement Report
Handover Required
1 Handover Request
2

4
Handover Command
3
Handover Command
5
Handover Failure 6

7

8

10

11
Handover Notify
12
UE Context Release Command

13
UE Context Release Command

14

Inter-System Handover Success Rate
 The inter-system handover success rate consists of both incoming and outgoing handover
between the LTE network and the CDMA network, between the LTE network and the UMTS
network, between the LTE network and the GSM network. This example shows a handover
from the CDMA network to the LTE network.
UE CDMA MME TARGET

EUTRAN
Measurement Report
Handover Required
Handover Request
1

2
Handover Command
Handover Failure 3
RRC Connection Reconfiguration Complete 4

5
Handover Notify
6

Contents
Integrity
QCI Resou Priorit Packet Packet Error Example Services
 UL/DL Packet rce
Type
y Latency
Budget
Loss
Rate (NOTE 2)
(NOTE 1)
Loss Rate 1 2 100 ms 10-2 Conversational Voice
(NOTE 3)
 DL PDCP SDU 2 4 150 ms 10-3 Conversational Video (Live Streaming)

(NOTE 3) GBR
Latency 3 3 50 ms 10-3 Real Time Gaming
(NOTE 3)
4 5 300 ms 10-6 Non-Conversational Video (Buffered

(NOTE 3) Streaming)
5 1 100 ms 10-6 IMS Signalling

(NOTE 3)
6 Video (Buffered Streaming)

(NOTE 4) 6 300 ms 10-6 TCP-based (e.g., www, e-mail, chat, ftp,
p2p file sharing, progressive video, etc.)
7 Non- Voice,
(NOTE 3) GBR 7 100 ms 10-3 Video (Live Streaming)
Interactive Gaming
8
(NOTE 5) 8 Video (Buffered Streaming)
300 ms 10-6 TCP-based (e.g., www, e-mail, chat, ftp,
p2p file
9 9 File sharing, progressive video, etc.

(NOTE 6)

Downlink PDCP SDU Latency
 Description:
 This KPI indicates average downlink PDCP SDU latency based on the QCI type, from the
time when a PDCP SDU reaches the eNodeB, to the time when the UE receives this PDCP
SDU, that is to say, all fragments of this PDCP SDU receives a successful HARQ response.
 Average Downlink PDCP SDU Latency = Total Latency of All PDCP SDUs / Number of All
PDCP SDUs

Downlink IP Packet Latency
 Description:
 This KPI indicates average downlink IP packet latency, from the time when the eNodeB receives the IP
packet through the S1 or X2 interface, to the time when the first fragment of this IP packet is
transmitted by the eNodeB through the air interface. It measures the time interval at which the service
is processed by the eNodeB, which forms a strong foundation for network optimization.
UE EUTRAN SGW
IP Packet 1
1
1st Fragment of IP Packet 1

2
 Average Downlink IP Packet Latency (QCI 1 – 9) = Total Downlink IP Packet Latency (QCI 1 – 9 ) /
Number of All PDCP SDUs (Downlink QCI 1 – 9)

Uplink/Downlink Packet Loss Rate
 Description:
 This KPI measures the ratio of discarded PDCP SDUs to received PDCP SDUs due
to the timeout of the TimeDisCard timer, when no, partial, or all fragments are
transmitted through the eNodeB or air interface. It should be noted that PDCP
SDUs vary from QCI to QCI (1 – 9), from uplink to downlink.
 Counters
 Number of All PDCP SDUs
 Uplink: When the PDCP layer of the eNodeB receives the PDCP SDU from the UE, this
counter is incremented by 1.
 Downlink: When the PDCP layer of the eNodeB sends the PDCP SDU to the RLC layer, this
counter is incremented by 1.
 Number of Discarded PDCP SDUs
 Uplink: When the PDCP layer of the eNodeB receives the PDCP SDU from the UE, the SN is
not consecutive.
 Downlink: When the PDCP layer of the eNodeB sends the PDCP SDU to the RLC layer, the
SN is not consecutive.
 Air Interface or eNodeB Packet Loss Rate = Number of Discarded Packets over the
Air Interface or eNodeB / Number of All Packets over the Air Interface or eNodeB

Cell BLER
 Description:
 The KPI shows the probability of an TB transmission error in a cell.
measurement:
 Number of uplink TB CRC errors in a cell
 Number of uplink TBs in a cell
 Number of downlink TB CRC errors in a cell
 Number of downlink TBs in a cell
 Number of uplink Initial TB CRC errors in a cell
 Number of uplink Initial TBs in a cell
 Number of downlink Initial TB CRC errors in a cell
 Number of downlink Initial TBs in a cell
 Cell BLER = Error Number of TBs / Total Number of TBs × 100%

Contents
Availability
 Availability
Important and
 Cell availability Demanding
 Ideal value in a commercial network: > 99.995%
measuremen t_period -  RRU.CellUn availableT ime.[cause ]

CellAvailability  cause
100
measurement _ period
 Dependency
 Software + Hardware
 Unavailable Time = Unplanned downtime only (excluding planned downtime)
 Physical meaning
 365 * 24 * 60 * (1-99.995%) = 26.28 min cell out-of-service time

Cell Availability
 Description:
 The cell availability measures the ratio of in-service time to measurement
granularity time. The in-service time indicates the time interval between cell
establishment and cell deletion. By counting the cell in-service time, this KPI forms
a foundation for analyzing system failures and measuring system stability.
 Signaling Procedure CRM CCM CCMI
The DRM may initializes the

cell deletion due to one of
the following reasons: EV_CRM_CCM_CELL_CONFIG_REQ
1. Normal cell deletion
2. Cell establishment timeout EV_CRM_CCM_CELL_CONFIG_REQ
3. Cell establishment failure
4. Manual
blocking/unblocking
5. Auditing failure When being power on, the CCM
6. S1 link disconnection starts the timer every 15 minutes
to report the service time of After the RNLU/CMAC/RRU is
each cell to the PM, and then successfully configured, the cell
clears statistical data. service start time is recorded.
EV_CRM_CCM_CELL_DEL_REQ
EV_CRM_CCM_CELL_DEL_REQ
After the RNLU/CMAC/RRU is

successfully deleted, the cell
service stop time is recorded.
 Cell Availability = In-Service Time / Measurement Granularity Time
 Cell Availability = C373230700 / Measurement Granularity Time * 100%
Availability of OAM link
 Description:
 The KPI shows probability for eNodeB to loss OAM link with EMS.
measurement:
 OAM link in-connection time
 Availability of OAM link = OAM link available time / Gr × 100%

Availability of SCTP link
 Description:
 The KPI shows probability for eNodeB to loss SCTP link with neighbor
eNodeB or MME.
measurement:
 SCTP link in-connection time
 Availability of SCTP link = SCTP link available time / Gr × 100%

KPI Overview
 Definition:
rate.

KPI Overview
 Definition:
rate.

KPI Overview
 Definition:
rate.

Contents
Traffic Type - Number of RRC Connections
 Description:
 This KPI counts the number of RRC connections, which is used to measure the UE access
to the system for call hold. It involves the following two counters:
 Average number of RRC connections
 Maximum number of RRC connections.
 When the eNodeB receives the RRC Establishment Complete message, the number of
RRC connections is incremented by 1.
 When the eNodeB triggers the RRC establishment successfully due to the handover, the
number of RRC connections is incremented by 1.
 When the eNodeB releases the RRC connection, the number of RRC connections is
decremented by 1.
 When the eNodeB reestablishes the RRC connection in another cell, the number of RRC
connections is decremented by 1.
 When the eNodeB reestablishes the RRC connection back to the serving cell, the number
of RRC connections is incremented by 1.
 Maximum Number of RRC Connections (Sampling Counter)
 Average Number of RRC Connections (Sampling Counter)

Traffic Type – Average Number of QCI-Based
UEs
 Description:
 This KPI measures the average number of E-RAB connections, which evaluates
network traffic. It should be noted that this KPI varies from QCI to QCI.
 Initial E-RAB establishment success
 Added E-RAB establishment success
 Incoming E-RAB handover success
 Incoming E-RAB modification success (changing the new QCI to the old QCI)
 Outgoing E-RAB handover success
 Outgoing E-RAB modification success (changing the old QCI to the new QCI)
 E-RAB release.
 This KPI is counted by averaging the measured values of all sampling points within
a specific measurement cycle

Traffic Type – Number of Activated QCI-Based
UEs
 Description:
 This KPI counts the number of UEs in the cache during a specified time
period. It can be measured based on a specific QCI, uplink or downlink,
average number or maximum number.
 This KPI indicates the number of in-service UEs in the system, which forms a
foundation for evaluating system capacity and capabilities.
 N/A
 This KPI is counted when any data is present in the E-RAB cache of QCI i
every sampling cycle (100 ms), as defined in the 3GPP TS.

Contents
RSRP
 RSRP indicates an absolute value of received signal strength. To

some extent, it can reflect distance between UEs and eNodeBs.
Therefore, this KPI value can measure the cell coverage. RSRP is
defined as the linear average over the power contributions of the
resource elements (RE) that carry cell-specific reference signals (RS)
within the considered measurement frequency bandwidth.
 Assume RSRP threshold is A, then RSRP coverage index (percentage)
= The number of test point with RSRP≥A/Total number of drive test
points .
 Before computing the RSRP, exclude abnormal test points whose
RSRP value is far beyond the normal value.
 Within coverage areas, the TD-LTE network coverage must have a
more than 95% probability of RSRP > -105dBm.
 When a test antenna is put on car roof, there must be a more than
95% probability of RSRP>－95dBm.
RS-CINR
 RS-CINR indicates carrier-to-interference ratio on RS channel

measured by UE. It is one of the key indexes to indicate channel
quality.
 Carrier to Interference plus Noise Ratio (CINR) is the ratio of
carrier to the noise and interference, which is measured by UE in
drive test. In the emulation tool CNP, RS-CINR=serving cell RSRP
/(neighbor cell RSRP+N); where, N is the thermal noise power.
more than 95% probability of RS-CINR >0dB.

PDCCH SINR
 PDCCH SINR indicates the quality of PDCCH.

 Formula: PDCCH SINR = (PDCCH receive power of the best
serving cell/ PDCCH interference in the cell).
 The quality requirement of PDCCH can be met if PDCCH SINR>-
1.6dB.

Coverage
 Wireless network coverage reflects the availability of a network.

 RSRPR, and RSRQ  S, where:
 RSRP indicates downlink reference signal received power;
 RSRQ indicates the signal quality of received reference signal;
 R and S indicate RSRP and RSRQ thresholds. Before calculation,

exclude abnormal tested points whose RSRP value or RSRQ value
is far beyond the normal value.
more than 95% probability of RSRP  -105dBm, and RSRQ > -
13.8dB.

Average PUSCH PRB Utilization
 This index reflects radio resource utilization (in relation to PRBs

assigned to the PUSCH) and provides the basis for optimizing
system algorithms and deciding whether the system requires
expansion.
 Average PUSH PRB utilization = Average value of utilization of all
TTI PUSCH PRBs in a statistical cycle = Number of carrier-
occupied PUSCH PRBs/Total number of cell-occupied PRBs in the
uplink
 TTI PUSCH PRB utilization = Number of PUSCH PRBs occupied
per TTI/ Total number of PUSCH PRBs per TTI

Average PDSCH PRB Utilization
 This index indicates the utilization of PRBs assigned to the

PDSCH.
 Average PDSH PRB utilization = Average value of utilization of all
TTI PDSCH PRBs in a statistical cycle = Number of cell-occupied
PRBs in the downlink/Total number of cell-occupied PRBs in the
uplink
 TTI PDSCH PRB utilization = Number of PDSCH PRBs occupied
per TTI/ Total number of PDSCH PRBs per TTI

Average PRACH Resource Utilization
 This index reflects the system access capability and provides the
basis for optimizing system parameters to some extent.
 Average PRACH resource utilization ＝ Number of PRACH
resources in use/Number of configured PRACH resources
 Namely, = Number of carrier-occupied PRACHs/Number of cell-
occupied PRBs in the uplink
 PRACH resources are a collection of time domains, frequency
domains, and code domains.
 The number of PRACH resources in use is the number of PRACHs
which the eNodeB successfully resolves their preamble, including
public and dedicated preambles.

Maximum/Average Carrier Transmit Power
Utilization (Temporarily Unavailable)
 By statistically obtaining the maximum and average carrier transmit
power values allows you to estimate the maximum and average
downlink system loads within a specific period, thereby knowing the
carrier transmit power utilization within this period. During network
planning, the system implements link budge calculation and capacity
emulation according to preset downlink loads. Therefore, to
calculate downlink carrier transmit utilization of each network cells
has great significance in network expansion planning and network
optimization.
 Maximum carrier transmit power utilization ＝ Maximum carrier
transmit power/Configured maximum carrier transmit power × 100%
 Average carrier transmit power utilization ＝ Average carrier transmit
power/Configured maximum carrier transmit power × 100%

FO - NAST3024 LTE KPI Introduction 65P

Uploaded by

Document Information

Original Title

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

FO - NAST3024 LTE KPI Introduction 65P

Uploaded by

Copyright:

Available Formats

LTE Radio Network KPI and

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

Counter calculate North Counter

© ZTE Corporation. All rights reserved

 Northbound Counters --- Semi-finished Dishes

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

RRC Connection RRC

Added E-RAB Paging Success Rate

RRC Connection Added E-RAB Contention-Based Contention-Free

E-RAB Setup E-RAB Block Rate

、 Rate, Call Barring Rate

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

eNB MME eNB MME

INITIAL CONTEXT SETUP REQUEST E-RAB SETUP REQUEST

INITIAL CONTEXT SETUP RESPONSE E-RAB SETUP RESPONSE

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

INITIAL CONTEXT SETUP REQUEST

INITIAL CONTEXT SETUP RESPONSE

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

UE E-RAB E-RAB Drop

E-RAB UL Data E-RAB DL Data

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

1E-RAB RELEASE INDICATION

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

 Successful Handover Categories

Inter-RAT HO Success Rate

All Incoming HO All Outgoing HO

Intra-RAT HO Success Rate

© ZTE Corporation. All rights reserved

 Handover 1. Measurement Control

packet data packet data

 Handover Preparation Success UL allocation Legend

Theoretical limit: 100%

Ideal value in a commercial

 Handover Execution Success Rate Buffer packets from

 Theoretical limit: 100% 10. UL allocation + TA for UE

11. RRC Conn. Reconf. Complete

 Ideal value in a commercial packet data

HO In: Step 6 – Step 11

HO Out: Step 7 – Step 17

 Mobility Success Rate 18. Release

 Theoretical limit: 100%

© ZTE Corporation. All rights reserved

Handover Start Point Stop Point

© ZTE Corporation. All rights reserved

 The outgoing handover preparation success rate for each handover

 The outgoing handover success rate contains all outgoing handover

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

RRC Connection Reconfiguration 2

RRC Connection Reconfiguration Complete