FO - NAST3023 LTE FDD Key Performance Indicators Description Guide 48P

FDD LTE Key Performance Indi
cators Description Guide

Objectives
 After having learned this training course, you sho
uld be able to understand:
 Basic knowledge of FDD LTE KPIs
 Categories of FDD LTE KPIs
 Formulas of FDD LTE KPIs
Contents
 Basic Knowledge of FDD LTE KPIs
 FDD LTE eNodeB KPIs
 FDD LTE Network KPIs
 Other FDD LTE KPIs
References
 Counters, Definitions, and Numbering Conventions
For more information, refer to the NetNumen M31(LTE) NE Management System eNo
deB Performance Counter Reference at the following URL:
http://tsm.zte.com.cn/tsm/FileCenter/File.aspx?Mode=read&FileID=30341574
 Formulas
For more information, refer to the NetNumen M31(LTE) NE Management System eNo
deB Key Performance Indicator Reference at the following URL:
http://tsm.zte.com.cn/tsm/FileCenter/File.aspx?Mode=read&FileID=30341576
© ZTE Corporation. All rights reserved

Counter Example
Counter
Counter
Measurement Measurement Measurement
Counter Name Sequence
Object Number Type
Number
Statistics of RRC Number of Successful mt-
Cell Type 37320 Connection Access RRC Connection C373200000
Establishment Establishment
Example

Counter Structure
Measuremen
t Object Measuremen
ID: 780-799
t Type
Counter KPI/PI
• Cell Type ID: 373320-373399
• eNodeB Type
• eNodeB IP Link • Statistics of RRC ID: C + KPI ID: 310500-
Type connection Measurement 310799
• Cell Pair Type establishment Type Number +
• Statistics of E- XXX • RRC connection
RAB establishment
• Statistics of time • Number of success rate
• Type of a cell pair successful mt- • Other
• Other Access RRC
connection
establishment
• Number of PI ID: 310500-
unsuccessful mt- 310799
Access RRC
connection
establishment • Paging
(timer timeout) congestion rate
• Other • Other

Reporting Procedure
 This reporting procedure is described as follows:

 Step 1 The RNLC subsystem reports data to the OAM using the event-triggered reporting
mechanism.
 Step 2 The CMAC, RNLU, BRS, or OSS subsystem reports data to the OAM every 10
seconds.
 Step 3 The OAM synchronizes data with the OMC for each measurement object every 15
minutes.

KPI Overview
 Description
 Mobile subscriber (Serviceability + Reliability): An FDD LTE can provi
de a mobile subscriber with high-quality, reliable, and long-term ser
vices.
 Mobile operator (Serviceability + Reliability + Traffic): An FDD LTE ca
n provide as many mobile subscribers as possible with high-quality, r
eliable, and long-term services.
 Dependency
 System performance: UE + eNodeB + Transport + EPC
 Applicable environments: Bandwidth configuration, radio access, mo
bility speed, service type, and so on
 Categories
 FDD LTE eNodeB KPIs
 FDD LTE Network KPIs

Contents
FDD LTE eNodeB KPIs
 Latency
 C-Plane Latency
 U-Plane Latency
 Throughput (Mono-UE)
 Peak UE Data Rate
 Average UE Data Rate
 Cell Edge UE Data Rate
 Cell Capacity (Multi-UE)
 Peak Cell Throughput
 Average Cell Throughput
 Cell-Edge UE Throughput

U-Plane Latency
 Round Trip Time
Combined EPC Application Server
eNodeB
UE
ping
Measured Round Trip Time

 Dependency
 Radio frequency: Under cell, mid-cell, and cell edge
 Neighbor cell loading: Unloaded and loaded
 Scheduling algorithm: Pre-scheduled and non-scheduled
 Ping size: 32 B, 1000 B, and 1500 B

C-Plane Latency
 State Transition Time
 Signaling Procedure

Throughput (Mono-UE)
 Peak UE Data Rate
Transmission E.g. Gateways,

Routers,
Firewalls
Terminal BS Application Server

at NGMN network edge
DownlinkorUplinkDataStream
 Assumption
 Loading: Single cell, unloaded
 UE speed: Stationary mode
 Location: Under cell (good RF conditions)
 MIMO configuration: DL 2*2 MIMO, UL 1*2 SIMO
 Dependency
 Operating bandwidth
 UE category
 UE UL/DL RB limitation

 Average UE Data Rate
 Assumption
 Loading: 1 UE in the serving cell, neighbor cell loaded
 Location: Uniformly-distributed locations over the signal quality range
 Dependency
 UE category
 UE distribution in each signal range

 Cell-Edge UE Data Rate
 Assumption
 Loading: 1 UE in the serving cell, neighbor cell loaded
 Location: Cell edge
 Dependency
 UE category
 UE SINR at the cell edge

Throughput (Multi-UE)
 Peak Cell Throughput
 Assumption
 Loading: Multiple cells, loaded (70%)
 UE Speed: Stationary mode
 Location: Good RF conditions
 Dependency
 UE category: TBS limitation, 64QAM in UL
 Environment: Dense urban, urban, suburban, and rural
 Scheduling algorithm

 Average Cell Throughput
Typical UE Distribution Model
 Assumption
 Loading: Multiple cells, loaded
 UE speed: Stationary Mode
 Location: Uniformly-distributed over the signal quality range
 Dependency
 UE category (TBS limitation, 64QAM in UL)
 UE distribution in each signal range, scheduling algorithm

 Cell-Edge UE Throughput
 Assumption
 Loading: Multiple cells, loaded (70%)
 Location: Cell edge
 Dependency
 UE category (TBS limitation, 64QAM in UL)
 Environment: Dense urban, urban, suburban, and rural
 Scheduling algorithm
 UE SINR at the cell edge

Contents
FDD LTE Network KPIs
 Accessibility
 RRC Establishment Success Rate
 E-RAB Setup Success Rate
 Retainability
 E-RAB Drop Rate
 Mobility
 Handover Success Rate
 Availability
 Cell Availability
 Integrity
 Packet Loss Rate
 DL PDCP SDU Latency

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

Accessibility
KPI RRC Connection

S1-SIG Establish Initial E-RAB Setup
RRC
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
KPI E-RAB Setup E-RAB Block Rate

Success Rate (per QCI)
Call Setup Success

、 Rate, Call Barring Rate

RRC Establishment Success Rate
 Description
 This KPI shows the probability for a subscriber to be provided with an RRC
 connection upon request.
 Formula
 RRC Establishment Success Rate = Number of successful RRC connection establishm
ent / (Number of successful RRC connection establishment + Number of failed RRC
connection establishment) * 100%

E-RAB Setup Success Rate
 Description
 This KPI shows the probability for a subscriber to be provided with an E-RAB request
 including initial and added context setup procedures.
eNB MME eNB MME
INITIAL CONTEXT SETUP REQUEST E-RAB SETUP REQUEST

1 3
INITIAL CONTEXT SETUP RESPONSE E-RAB SETUP RESPONSE

2 4
 Formula
 E-RAB Setup Success Rate = (Number of successful initial E-RAB + Number of successful added E-RAB establish
ment) / (Number of successful initial E-RAB establishment + Number of failed initial E-RAB establishment + Nu
mber of successful added E-RAB establishment + Number of failed added E-RAB establishment) * 100%

Retainability
 Theoretical limit: 0%
 Ideal value in a commercial network: < 2%
Retainability
(Category)
KPI
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

E-RAB Drop Rate
 Description
 This KPI shows the probability for an a subscriber to loss the E-RAB, such as a
n event being released by the eNodeB due to overload control.
E-RAB Released by the eNodeB))
eNB MME
E-RAB RELEASE INDICATION

1
 Formula
 E-RAB Drop Rate = Number of Abnormally Released E-RAB / Number of Successfully
 Established E-RAB * 100%

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
 Handover
 Handover Preparation Suc
cess Rate

Theoretical limit: 100%

Ideal value in a commer
cial network ： 99%

(Step 4 – Step 6)
 Handover Execution Succe
ss Rate


cial network: 98%

HO In: Step 6 – Step 11

HO Out: Step 7 – Step
17
 Mobility Success Rate


cial network: 97%
MobilitySR HO. Pr eparationSR  HO.ExecutionSR

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 to
preparation the UE.
Outgoing The source eNodeB sends the RRC The source eNodeB receives the UE
handover Connection Reconfiguration message Context Release message from the
execution to the UE. destination eNodeB.
Incoming The destination eNodeB receives the The destination eNodeB returns the
handover Handover Request message from the Handover Response message to the source
preparation source eNodeB. eNodeB.
Incoming The destination eNodeB receives the The destination eNodeB sends the UE
handover RRC Connection Reconfiguration Context Release message to the source
execution Complete message from the UE. eNodeB.

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 ce
rtain neighbor cell. Here are two typical examples:
 In the event of the handover from cell A to cell B, the Intra-eNodeB Intra-freq Out
going 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 Out
going 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 ce
lls that suffer most handover preparation failures, performing neighb
or cell optimization, and even deleting unusable neighbor cells.

Intra-eNodeB Handover Success Rate
 Description
 The intra-eNodeB handover success rate measures the service continuity whe
n a subscriber is on the move. This KPI is perceptible to the subscribers, depe
nding on system handover processing capabilities and network planning.
 Formulas
 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 handove
r successes / Number of inter-frequency handover requests * 100%

Intra-eNodeB Handover Success Rate
Note:
 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-Interface Handover Success Ra
te
 Description
 The inter-eNodeB X2-interface handover success rate measures the handover
successes when the UE moves between the eNodeBs over the X2 interface. Th
is KPI is perceptible to the subscribers being on the move, depending on syst
em handover processing capabilities and network planning.
 Formulas
 Outgoing intra-frequency X2-interface handover success rate = Number of o
utgoing intra-frequency X2-interface handover successes / Number of outgoi
ng intra-frequency X2-interface handover attempts (serving cell) * 100%
 Incoming intra-frequency X2-interface handover success rate = Number of in
coming intra-frequency X2-interface handover successes / Number of incomi
ng intra-frequency X2-interface handover attempts (serving cell) * 100%
 Outgoing inter-frequency X2-interface handover success rate = Number of o
utgoing inter-frequency X2-interface handover successes / Number of outgoi
ng inter-frequency X2-interface handover attempts (serving cell) * 100%
 Incoming inter-frequency X2-interface handover success rate = Number of in
coming inter-frequency X2-interface handover successes / Number of incomi
ng inter-frequency X2-interface handover attempts (serving cell) * 100%

Inter-eNodeB X2-Interface Handover Success Ra
te

Inter-eNodeB S1-Interface Handover Success Ra
te
 Description
 When the eNodeB decides to perform a handover according to the UE measureme
nt report and meanwhile the destination cell is not connected to the eNodeB throug
h the X2 interface, the inter-eNodeB S1-interface handover success rate measures th
e S1-interface handover performed through the EPC. This KPI is perceptible to the s
ubscribers being on the move, depending on system handover processing capabiliti
es and network planning.
 Formulas
 Outgoing intra-frequency S1-interface handover success rate = Number of outgoin
g intra-frequency S1-interface handover successes / Number of outgoing intra-freq
uency S1-interface handover attempts (serving cell) * 100%
 Incoming intra-frequency S1-interface handover success rate = Number of incomin
g intra-frequency S1-interface handover successes / Number of incoming intra-freq
 Outgoing inter-frequency S1-interface handover success rate = Number of outgoin
g inter-frequency S1-interface handover successes / Number of outgoing inter-freq
 Incoming inter-frequency S1-interface handover success rate = Number of incomin
g inter-frequency S1-interface handover successes / Number of incoming inter-freq

Inter-eNodeB S1-Interface Handover Success Ra
te

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

Availability
 Availability
 Cell availability Important and

Theoretical limit: 100% Demanding

Ideal value in a commercial network: > 99.995%
measurement_period -  RRU.CellUnavailableTime.[cause]
CellAvaila bility  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 t
ime indicates the time interval between cell establishment and cell deletion. By counting the cell in-servic
e time, this KPI forms a foundation for analyzing system failures and measuring system stability.
 Formulas
 Cell Availability = In-Service Time / Measurement Granularity Time
 Cell Availability = C373230700 / Measurement Granularity Time * 100%

Integrity
QCI Reso Priori Packet Packet Error Example Services
urce ty Latency Loss
Type Budget Rate
 UL/DL Packet L 1 2
(NOTE 1)
100 ms
(NOTE 2)
10-2 Conversational Voice
(NOTE 3)
oss Rate 2 4 150 ms 10-3 Conversational Video (Live
(NOTE 3) GBR Streaming)
 DL PDCP SDU 3
(NOTE 3)
3 50 ms 10-3 Real Time Gaming
4 5 300 ms Non-Conversational Video

Latency
10-6
(NOTE 3) (Buffered 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
(NOTE 6) video, etc.

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 reac
hes the eNodeB, to the time when the UE receives this PDCP SDU, that is to say, all fragments of this PDCP SDU rece
ives a successful HARQ response.
 Formula
 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 t
he 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 foundati
on for network optimization.
 Formula
 Average Downlink IP Packet Latency (QCI 1 – 9) = Total Downlink IP Packet Latency (QCI 1 – 9 ) / Number of All PDCP S
DUs (Downlink QCI 1 – 9)

Uplink/Downlink Packet Loss Rate
 Description
 This KPI measures the ratio of discarded PDCP SDUs to received PDCP SDUs due t
o the timeout of the TimeDisCard timer, when no, partial, or all fragments are tran
smitted 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 increm
ented by 1.

Downlink: When the PDCP layer of the eNodeB sends the PDCP SDU to the RLC layer, this counter is inc
remented 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 consecu
tive.

Downlink: When the PDCP layer of the eNodeB sends the PDCP SDU to the RLC layer, the SN is not con
secutive.
 Formula
 Air Interface or eNodeB Packet Loss Rate = Number of Discarded Packets over th
e Air Interface or eNodeB / Number of All Packets over the Air Interface or eNode
B

Contents
Traffic Type - Number of RRC Connections
 Description
 This KPI counts the number of RRC connections, which is used to measure the U
E 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 numb
er of RRC connections is incremented by 1.

When the eNodeB triggers the RRC establishment successfully due to the handover, th
e number of RRC connections is incremented by 1.

When the eNodeB releases the RRC connection, the number of RRC connections is decr
emented 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 numb
er of RRC connections is incremented by 1.
 Formulas
 Maximum Number of RRC Connections (Sampling Counter)
 Average Number of RRC Connections (Sampling Counter)

Traffic Type – Average Number of QCI-Based UE
s
 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.
 Signaling Procedure (Sampling Counter)
 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
 Formula
 This KPI is counted by averaging the measured values of all sampling points w
ithin a specific measurement cycle.

Traffic Type – Number of Activated QCI-Based U
Es
 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 num
ber or maximum number.
 This KPI indicates the number of in-service UEs in the system, which forms a f
oundation for evaluating system capacity and capabilities.
 N/A
 Formula
 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.

Resource Allocation
Cell & System Resources
( Category )
Total UL PDCCH Usage

PRB Usage
UL - C PRB Usage UL - U PRB Usage PRACH Usage PRACH PRACH

Propagation Delay Message Load
UL PRB Usage Paging

per QCI Congestion Rate
Total D L Avg CPU Load Avg DSP Load

PRB Usage
DL - U PRB Usage Avg DL

DL - C PRB Usage
Transmission Power
Avg UL
DL PRB Usage
Interference
per QCI
© ZTE Corporation. All rights reserved Per PRB

FO - NAST3023 LTE FDD Key Performance Indicators Description Guide 48P

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

FO - NAST3023 LTE FDD Key Performance Indicators Description Guide 48P

Hochgeladen von

Copyright:

Verfügbare Formate

FDD LTE Key Performance Indi

cators Description Guide

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

 This reporting procedure is described as follows:

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

Measured Round Trip Time

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

Transmission E.g. Gateways,

Terminal BS Application Server

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

Initial E-RAB Attach Success Rate Detach Success Rate

KPI RRC Connection

Added E-RAB Paging Success Rate

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

KPI E-RAB Setup E-RAB Block Rate

Call Setup Success

© 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

How Often Percentage

E-RAB UL Data E-RAB DL Data

QoS Before Drop

© ZTE Corporation. All rights reserved

E-RAB RELEASE INDICATION

© ZTE Corporation. All rights reserved

Inter- RAT HO Success Rate

All Incoming HO All Outgoing HO

Intra- RAT HO Success Rate

© ZTE Corporation. All rights reserved

MobilitySR HO. Pr eparationSR  HO.ExecutionSR

© ZTE Corporation. All rights reserved

Handover Start Point Stop Point

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

4 5 300 ms Non-Conversational Video

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved