Huawei_LTE_KPI_Optimization.pdf

www.DigiTrainee.com Company Confidential
Huawei
eRAN KPI introduction (eRAN 6.0)

Contents
1. KPI System Overview
2. KPI Detail Description
3. Recommended KPIs

1. KPI System Overview

KPI System Overview
Radio Network KPI :
Focus on the radio
network performance
Service KPI :
Focus on the user
experience
LTE KPIs
Accessability Retainability Integrity
Mobility Latency
•RRC SETUP
SR
•ERAB
Setup SR
(VoIP/ALL)
•Call Setup
SR
(VoIP/ALL)
•Call Drop
Rate
(VoIP/ALL)
•Call Setup
Complete
Rate
(VoIP/ALL)
•Service
UL/DL
Throughput
•HHO SR (
Intra/Inter
Frequency
)
•HO in SR
•Inter-RAT
HHO SR
•Access
Latency
•Service
Latency
•Interrupt
Latency
•Radio
Network
Unavailabi
lity Rate
Availability
•Cell UL/DL
Traffic
Volume
•Radio
Bearer
Number
Utilization
•UL/DL
RB
Utility
Rate
Traffic

KPI Attained Approach
o In general, there are two approaches to define/attain KPIs:
 By statistics /Counter:
Most of KPIs are attained by this approach, such as RRC Success Rate, HHO
Success Rate…
 By drive test / Stationary test:
Some KPIs should be attained by drive test, such as Attach Latency, Handover
late cy…

Measurement Object for Counter
Measurement Object
Measurement
Unit 1
Measurement
Unit 2
……
Counter 1 Counter 2 Counter 3 Counter 4 Counter 5 Counter 6 Counter 7
Measurement
Family 1
……
Measurement
Family 2
…… ……
o Each measurement result is related to a specific measurement object.
o Counters are organized by Measurement Unit/Family.

o Collection methods (TS 32.403)
 CC (Cumulative Counter), for example, Attempted RRC connection establishments;
 GAUGE (dynamic variable), used when data being measured can vary up or down
during the period of measurement, for example, Maximum E-RAB Setup time;
 DER (Discrete Event Registration), when data related to a particular event are
captured every nth event is registered, where n can be 1 or larger, for example,
Cell Unavailable Time, Mean E-RAB Setup time;
 SI (Status Inspection), for example, Average Number of simultaneous E-RABs;
o Reporting period
 The measurement results are collected in a pre-defined reporting period, and this
reporting period, in general, is configurable at EMS, for example, 15mins,
60 i s…
Collection Method and Reporting Period

2. KPI Detail Description

KPI Detail Description
o Accessibility
o Retainability
o Mobility
o Availability
o Utilization
o Traffic
o Integrity
o Latency

Accessibility (1) – RRC Setup Success Rate
o RRC Setup Success Rate (service)
The RRC setup procedure is trigged by different reasons as identified by the
establishmentCause field in the RRCConnctionRequest message: emergency,
highPriorityAccess, mt-Access, mo-Signaling, mo-Data, delayTolerantAccess-v1020.
The UE sets the establishmentCause and received by eNodeB. Causes except mo-
Signaling are categorized as service related ones, and the cause of mo-Signaling is
categorized as signal related ones.
This KPI evaluates the RRC setup success rate with service related causes in a cell or
cluster.
%
100
_
_
_ Service 

service
service
Attempt
Connection
RRC
Success
Connection
RRC
SSR
RRC
o RRC Setup Success Rate (Signal)
This KPI evaluates the RRC setup success rate with signal
related causes (mo-Signalling) in a cell or cluster.
%
100
_
_
_ Signal 

Signal
Signal
Attempt
Connection
RRC
Success
Connection
RRC
SSR
RRC

Accessibility (2) – Counter Mapping for
RRC SSR
L.RRC.ConnReq.Att…
L.RRC.ConnReq.Succ …

Accessibility (3) – QCI Definition
o LTE-SAE QoS Class Identifier
There are 9 QCIs defined in 3GPP TS 23.203. Each of QCI has its QoS
requirements, and each E-RAB will has the attribute of QCI.

Accessibility (4) – ERAB Setup Success Rate
o VoIP ERAB Setup Success Rate
This KPI can be used to evaluate the ERAB setup
success rate of VoIP service (QCI 1 service) in a
cell or cluster.
_ _
_ _ 100%
_ _
VoIP ERAB SetupSuccess
VoIP ERAB SSR
VoIP ERAB SetupAttempt
 
o ERAB Setup Success Rate (All)
This KPI can be used to evaluate the ERAB setup
success rate of all services including the VoIP
service in a cell or a cluster.
_
_ ( ) 100%
_
ERAB SetupSuccess
ERAB SSR ALL
ERAB SetupAttempt
 

Accessibility (5) – Counter Mapping for
ERAB SSR
ERAB Setup Attempt Counters
ERAB Setup Success Counters
ERAB Setup Attempt Counters
ERAB Setup Success Counters

Accessibility (6) – Call Setup Success Rate
o VoIP Call Setup Success Rate (VoIP CSSR)
This KPI evaluates the success rate of the whole setup procedure for VoIP service (QCI
1 service) in a cell or cluster, which mainly includes three phases : RRC setup phase, S1
Signaling connection establishment phase and VoIP E-RAB setup phase:
_ 1 _ _
_ * * 100%
_ 1 _ _
Service
Service
RRC ConnectionSuccess S SIGConnectionEstablishSuccess VoIP ERAB SetupSuccess
VoIP CSSR
RRC ConnectionAttempt S SIGConnectionEstablishAttempt VoIP ERAB SetupAttempt
 
o Call Setup Success Rate (ALL)
This KPI can be used to evaluate the call setup success rate of all services including
the VoIP service in a cell or a cluster. This KPI mainly includes three phases : RRC
setup phase, S1 Signaling connection establishment phase and service E-RAB setup
phase:
_ 1 _
( ) * * 100%
_ 1 _
Service
Service
RRC ConnectionSuccess S SIGConnectionEstablishSuccess ERAB SetupSuccess
CSSR ALL
RRC ConnectionAttempt S SIGConnectionEstablishAttempt ERAB SetupAttempt
 

Accessibility (7) – Counter Mapping for CSSR

Retainability (1) – Call Drop Rate
o VoIP Call Drop Rate
This KPI can be used to evaluate the call drop rate of VoIP service (QCI 1 service) in a cell
or cluster, the call drops happen when eNode initiate active ERAB (with data in buffer)
release process by E-RAB Release Indication or UE Context Release Request message with
Cause field with abnormal reasons (the cause other than : Normal Release, Detach,User
Inactivity, cs fallback triggered, UE Not Available For PS Service,or Inter-RAT redirection),
and all of the other E-RAB releases are consider as normal E-RAB release.
%
100
Re
_
_
Re
_
_
_ 

lease
ERAB
VoIP
lease
Abnormal
ERAB
VoIP
CDR
VoIP

Retainability (1) – Call Drop Rate
o Call Drop Rate(ALL)
This KPI can be used to evaluate the call drop rate of all services in a cell or a cluster,
including VoIP service.
_ Re
( ) 100%
_ Re
ERAB Abnormal lease
CDR ALL
ERAB lease
 
o Call Drop Rate(Always Online)
This KPI can be used to evaluate the call drop rate of all the services, including the VoIP
services, when the always online state is active. In always online state, the E-RAB
number of UE entering the un-synchronous state from synchronous state will be
considered for the KPI calculating.
_ 100%
Re
ERABAbnormalReleaseOfAlwaysOnline
AlwaysOnline CDR
ERAB leaseOfAlwaysOnline
 

Retainability (2) – Counter Mapping for Call
Drop Rate
Normal and Abnormal
release Counters based on
the cause
Normal and Abnormal
release Counters based on
the cause

Retainability (3) - Call Setup Complete Rate
_ 1 _ _ Re
( ) * * * 100%
_ 1 _ _ Re
Service
Service
RRC ConnectionSuccess S SIGConnectionEstablishSuccess ERAB SetupSuccess ERAB Normal lease
CSTR ALL
RRC ConnectionAttempt S SIGConnectionEstablishAttempt ERAB SetupAttempt ERAB lease
 
o VoIP Call Setup Complete Rate (VoIP CSTR)
This KPI evaluates the call Setup Complete Rate for VoIP service (QCI 1 service) in a cell
or cluster, which means the rate of the VoIP service can be normally terminated once
user do the attempt to setup the service. And it can include 4 phases: RRC setup phase,
S1 Signaling connection establishment phase, VoIP E-RAB setup phase and VoIP service
E-RAB release phase;
o Call Setup Complete Rate (ALL)
The similar as upper KPI, this KPI will evaluate the success rate in totally for 4 phases:
RRC setup phase, S1 Signaling connection establishment phase, service E-RAB setup
phase and service E-RAB release phase;
_ 1 _ _ _ _ Re
_ * * *
_ 1 _ _
Service
Service
RRC ConnectionSuccess S SIGConnectionEstablishSuccess VoIP ERAB SetupSuccess VoIP ERAB Normal lease
VoIP CSTR
RRC ConnectionAttempt S SIGConnectionEstablishAttempt VoIP ERAB SetupAttempt Vo
 100%
_ _Re
IP ERAB lease


Retainability (3) - Call Setup Complete Rate
o Call Setup Complete Rate (Always Online)
The similar as upper KPI, this KPI will evaluate the success rate in totally for 4
phases: RRC setup phase, S1 Signaling connection establishment phase,
service E-RAB setup phase and service E-RAB release phase (when the always
online state is active);
_ 1 _
( ) * * *
_ 1 _
Service
Service
RRC ConnectionSuccess S SIGConnectionEstablishSuccess ERAB SetupSuccess ERABAbnormalReleaseOfAlway
CSTR AlwaysOnline
RRC ConnectionAttempt S SIGConnectionEstablishAttempt ERAB SetupAttempt
 100%
Re
sOnline
ERAB leaseOfAlwaysOnline


Retainability (4) - Counter Mapping for
CSCR

Mobility (1) – Intra-LTE Handover (Out)
Success Rate
o Intra-frequency Handover Out Success Rate
This KPI can be used to evaluate the intra-frequency
handover out success rate in a cell or cluster.
%
100
_
_
_
_ 

pt
HOOutAttem
IntraF
ss
HOOutSucce
IntraF
SR
HOOut
IntraF
o Inter-frequency Handover Out Success Rate
This KPI can be used to evaluate the inter-frequency
handover out success rate in a cell or cluster.
%
100
_
_
_
_ 

pt
HOOutAttem
InterF
ss
HOOutSucce
InterF
SR
HOOut
InterF

Mobility (2) – Counter Mapping for
Intra-LTE HO SR
Handover Attempt
Counters
Handover Success
Counters

Mobility (3) - Intra-LTE Handover In
Success Rate
o Handover In Success Rate
This KPI can be used to evaluate the handover
in success rate in a cell or cluster.
%
100
_ 

t
HOInAttemp
s
HOInSucces
SR
HOIn

Mobility (4) - Counter Mapping for
Intra-LTE HO In SR
HO in Attempt
Counters
HO in Success
Counters

Mobility (5) – Inter-RAT Handover
Success Rate
o Inter-RAT Handover Success Rate (LTE to WCDMA)
This KPI can be used to evaluate the inter-RAT handover
success rate from LTE to WCDMA in a cluster.
%
100
_
2
_
_
2
_
_
2
_ 

AttemptOut
W
L
IRATHO
SuccessOut
W
L
IRATHO
SR
W
L
IRATHO out
o Inter-RAT Handover Success Rate (LTE to GERAN)
This KPI can be used to evaluate the inter-RAT handover success rate from LTE to GERAN
in a cluster.
%
100
_
2
_
_
2
_
_
2
_ 

AttemptOut
G
L
IRATHO
SuccessOut
G
L
IRATHO
SR
G
L
IRATHO out

Mobility (6) – Inter-RAT Handover
Success Rate
o Inter-RAT Handover Success Rate (LTE to CDMA2000)
This KPI can be used to evaluate the inter-RAT handover success rate from LTE to
CDMA2000 in a cluster.
_ 2 _
_ 2 _ 100%
_ 2 _
out
IRATHO L C SuccessOut
IRATHO L C SR
IRATHO L C AttemptOut
 

Mobility (7) – Counter Mapping for
Inter-RAT HO SR
B point , HO attempt, and
distinguish the target system by
a ele e t targetRAT-Type i
the message
C point, HO
Success

Availability (1) - Radio Network
Unavailability Rate
o Radio Network Unavailability Rate
This KPI provides the percentage of time that a cell is unavailable in order to evaluate
the degradation of the network performance caused by the unavailable cells. It is
calculated based on the time of all cell unavailability in the radio network (cluster).
Where the {SP} denotes the reports period of counters, and the unit is minutes.

Availability (2) – Counter Mapping for RAN
Unavailability Rate

Utilization (1) – DL/UL RB Utility Rate
o Uplink Resource Block Utility Rate
This KPI evaluates the UL RB (Resource Block) utility rate of a cell or cluster.
%
100
_
_
_ 

Available
ULRB
Used
ULRB
e
UtilityRat
ULRB
The ULRB_Available and DLRB_Available are fix values, which can be calculated by
system bandwidth.
o Downlink Resource Block Utility Rate
This KPI evaluates the DL RB (Resource Block) utility rate of a cell or cluster.
%
100
_
_
_ 

Available
DLRB
Used
DLRB
e
UtilityRat
DLRB

Utilization (2) – Counter Mapping for RB
Utility Rate

Utilization (3) – Average CPU Load
o Average CPU Load
This KPI is used to evaluate the CPU usage in busy hours. It indicates the system
loading. The CPU load is calculated by averaging the CPU usage ratio in the
measurement period.
MeanCPUUtility

Utilization (4) – Counter Mapping for
Average CPU Load

Traffic (1) – Active Users
_
AvgUserNumber ULData
o Active Users
This group of KPIs consist of 6 KPIs, which are used to evaluate the user numbers which
has the RRC connection in the cell, the user numbers with uplink data in the buffer or
with downlink data in the buffer, and also give the average user number and maximum
user number in a cell or cluster.
_
AvgUserNumber DLData
_
MaxUserNumber DLData
_
MaxUserNumber ULData
AvgUserNumber
MaxUserNumber

Traffic (2) – Counter Mapping for Active
Users

Users

Traffic (5) – Radio Bearers
o Radio Bearers
The radio bearers KPIs consist of ten sub-KPIs, one is for the total of radio bearers and
the other nine are for nine QCIs. This set of KPIs can be used to evaluate the average
radio bearers in a cell or a cluster. The radio bearer for each QCI is based on the number
of active RRC connections for each QCI according to the QCI defined in the QoS
information.
……
9
_
_QCI
rs
RadioBeare
1
_
_QCI
rs
RadioBeare
RadioBearers

Traffic (6) – Counter Mapping for Radio
Bearers

Traffic (7) - Traffic Volume
o Downlink Traffic Volume
Similar to the radio bearers KPIs, the downlink traffic volume KPIs consist of ten sub-
KPIs, one is for the total of traffic volume for DRBs and the other nine are for nine QCIs.
This group of KPIs can be used to evaluate the DL traffic volume in a cell, which is
measured at the PDCP layer excluding the PDCP header
…… 9
_
_QCI
olume
DLTrafficV
_ _1
DLTrafficVolume QCI
o Uplink Traffic Volume
Similar to the downlink traffic volume KPIs, the uplink traffic volume KPIs consist of ten
sub-KPIs, one is for the total of traffic volume for DRBs and the other nine are for nine
QCIs. This group of KPIs can be used to evaluate the uplink traffic volume in a cell. The
KPIs are measured at the PDCP layer excluding the PDCP header.
1
_
_QCI
olume
ULTrafficV 9
_
_QCI
olume
ULTrafficV
……
DLTrafficVolume
ULTrafficVolume

Traffic (8) - Counter Mapping for Traffic
Volume

Traffic (9) - Counter Mapping for Traffic
Volume

Service Integrity (1) – Service Average
Throughput
o Service Downlink Average Throughput
This KPI consist of nine sub-KPIs mapped into nine QCIs (QCI 1~9), they evaluate the
downlink throughput of a service with a specific QCI per user in each cell, it reflects the
end-user experience.
o Service Uplink Average Throughput
Same with the service downlink average throughput, this set of KPIs consist of nine
sub-KPIs mapped into nine QCIs (QCI 1~9), and the meaning is also similar with it.
1
_
_QCI
hroughput
ULAverageT
……
9
_
_QCI
hroughput
ULAverageT
1
_
_QCI
hroughput
DLAverageT
……
9
_
_QCI
hroughput
DLAverageT
The total downlink traffic volume at PDCP layer of each QCI and total duration for
transmitting them are measured within a measurement period. Then the average
throughput of each QCI is obtained at the end of the measurement period.

Service Integrity (2) – Cell Average
Throughput
o Cell Downlink Average Throughput
This KPI evaluates the cell downlink average throughput when there are data transferring
at downlink. It reflects the cell capacity.
The total downlink traffic volume at PDCP layer of cell and total duration for transmitting
which is measured within a measurement period. Then the average throughput of cell is
obtained at the end of the measurement period.
o Cell Uplink Average Throughput
Same with the cell downlink average throughput, this set of KPI reflects the cell
capacity, and the meaning is also similar with it.
CellDLTrafficVolume
CellDLAveThp
CellDLTransferTime

CellULTrafficVolume
CellULAveThp
CellULTransferTime


Service Integrity (3) – Cell Maximum
Throughput
o Cell Downlink Maximum Throughput
This KPI evaluates the cell downlink maximum throughput when there are data
transferring at downlink. It reflects the cell capacity. It is calculated based on maximum
value of downlink traffic volume which are transferred at each second.
o Cell Uplink Maximum Throughput
Same with the cell downlink maximum throughput. It is calculated based on maximum
value of downlink traffic volume which are transferred at each second.
1 ( )
1000( )
CellULMaxTrafficVolumeforEach s bit
CellULMaxThp
ms

1 ( )
1000( )
CellDLMaxTrafficVolumeforEach s bit
CellDLMaxThp
ms


Service Integrity (4) – Counter Mapping for
Service Average Throughput

Service Integrity (5) – Measurement Principle for
Throughput
Refer to TS 32.450

Service Integrity (6) – Counter Mapping for
Service Average Throughput

Service Integrity (7) – Counter Mapping for Cell
Average Throughput

Service Integrity (8) – Counter Mapping for Cell
Maximum Throughput

Latency (1)
o Access Latency
This grouped KPI can be used to evaluate the
latency of access phase.
o AccessLatency_Attach
Defined as the duration from the time the UE
send AttachRequest message to the time the
UE send AttachComplete message message
o AccessLatency_Idle2Active
Defined as the duration from (UE in idle mode)
the time the UE send RRCConnectionRequest
message to the time the UE send
RRCConnectionReconfiguration message

Latency (2)
o Control Plane HO Interrupt Latency
This grouped KPI can be used to evaluate the control plane interrupt latency during the
handover, we can further distinguish them by different handover scenarios.
This KPIs is measured through drive test. Defined as the duration from the time the UE
receives the handover command（RRCConnectionReconfiguration after
MeasurementReport) to the time the UE send the handover confirm message
(RRCConectionReconfigurationComplete) .
HO
IntraLTE
Interrupt
ne
ControlPla _
_
_
C
L
IRATHO
Interrupt
ne
ControlPla 2
_
_
_
W
L
IRATHO
Interrupt
ne
ControlPla 2
_
_
_
G
L
IRATHO
Interrupt
ne
ControlPla 2
_
_
_
o Service Latency
This grouped KPI can be used to evaluate the latency of a particular service, we can
distinguish them by different services, this KPI will be attained by drive test (or
stationary test).
bytes
Ping
ency
ServiceLat 32
_
_
bytes
Ping
ency
ServiceLat 1460
_
_

Latency (3)
o User Plane HO Interrupt Latency
This grouped KPI can be used to evaluate the
user plane interrupt latency during the
handover, we can further distinguish them by
different handover scenarios.
The user plane interrupt latency is different
when observed at different layers, for example,
at IP layer or RLC layer or MAC layer.
This KPIs is measured through drive test.
Defined as the duration from the last RLC layer
package received before the handover, to the
first RLC layer package received after handover.
It can be observed in Probe.
HO
IntraLTE
Interrupt
UserPlane _
_
_
C
L
IRATHO
Interrupt
UserPlane 2
_
_
_
G
L
IRATHO
Interrupt
UserPlane 2
_
_
_
W
L
IRATHO
Interrupt
UserPlane 2
_
_
_

3. Recommended KPI

Recommended KPIs
o The recommended KPIs at this phase include:
KPI Class KPI Name
Accessibility
RRC Setup Success Rate (service)
RRC Setup Success Rate (Signal)
ERAB Setup Success Rate (ALL)
Retainability Call Drop Rate (ALL)
Mobility Intra-frequency Handover Out Success Rate
Traffic
Radio Bearers for Total and QCI 1~9
Downlink Traffic Volume for Total and QCI 1~9
Uplink Traffic Volume for Total and QCI 1~9
Integrity
Service Downlink Average Throughput for QCI 1~9
Service Downlink Average Throughput for QCI 1~9

Performance Data Manager
(iManager PRS V100R006 Product Description V1.1)
The PRS is a platform used to manage mobile network performance reports
and analyze network performance.

Customizing Reports
(iManager PRS V100R006 Product Description V1.1)

Restrictions on Measurement Activations
o The period of measurement on northbound
interface should be for 15mconsist with
southbound interface. So far, Huawei support
15minutes and 60minutes periods as default.
o There is no restrictions on the number of NE
objects, measurement objects minutes and 60
minutes measurement periods. M2000 can
provide all measurement results of all
managed NEs via northbound performance
file interface.

Huawei_LTE_KPI_Optimization.pdf

More Related Content

What's hot

Similar to Huawei_LTE_KPI_Optimization.pdf

Recently uploaded

Huawei_LTE_KPI_Optimization.pdf