Huawei ERAN KPI Introduction
Huawei ERAN KPI Introduction
www.huawei.com
Recommended KPIs
LTE KPIs
RRC Call Drop HHO SR Radio UL/DL Cell UL/DL Access Service
SETUP SR Rate ( Intra/Inter Network RB Traffic Latency UL/DL
ERAB (VoIP/ALL) Frequency) Unavailabil Utility Volume Throughput
Service
Setup SR ity Rate Rate Radio
Call Setup HO in SR Latency
(VoIP/ALL) Complete Bearer
Inter-RAT Interrupt
Call Setup Rate Number
HHO SR Latency
SR (VoIP/ALL)
(VoIP/ALL)
By statistics /Counter:
Most of KPIs are attained by this approach, such as RRC Success Rate, HHO Success Rate
Measurement Object
Measuremen Measuremen
Measurement Measuremen
t t
Unit 1 t Unit 2
Family 1 Family 2
Reporting period
KPI Collection
Yes
Global KPI is good ?
No
Finish
Page7
HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential
Agenda
Recommended KPIs
RRC _ ConnectionSuccessservice
RRC _ SSRService 100%
RRC _ ConnectionAttempt service
This KPI evaluates the RRC setup success rate with signal
related causes (mo-Signalling) in a cell or cluster.
RRC _ ConnectionSuccessSignal
RRC _ SSRSignal 100%
RRC _ ConnectionAttempt Signal
L.RRC.ConnReq.Att
L.RRC.ConnReq.Succ
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.
ERAB _ SetupSuccess
ERAB _ SSR ( ALL) 100%
ERAB _ SetupAttempt
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:
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:
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. VoIP _ ERAB _ Abnormal Re lease
VoIP _ CDR 100%
VoIP _ ERAB _ Re lease
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.
ERAB _ Abnormal Re lease
CDR( ALL) 100%
ERAB _ Re lease
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.
ERABAbnormalReleaseOfAlwaysOnline
AlwaysOnline _ CDR 100%
ERAB Re leaseOfAlwaysOnline
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;
RRC _ ConnectionSuccessService S1SIGConnectionEstablishSuccess VoIP _ ERAB _ SetupSuccess VoIP _ ERAB _ Normal Re lease
VoIP _ CSTR * * * 100%
RRC _ ConnectionAttemptService S1SIGConnectionEstablishAttempt VoIP _ ERAB _ SetupAttempt VoIP _ ERAB _ Re lease
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;
RRC _ ConnectionSuccessService S1SIGConnectionEstablishSuccess ERAB _ SetupSuccess ERAB _ Normal Re lease
CSTR ( ALL ) * * * 100%
RRC _ ConnectionAttemptService S1SIGConnectionEstablishAttempt ERAB _ SetupAttempt ERAB _ Re lease
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);
RRC _ ConnectionSuccessService S1SIGConnectionEstablishSuccess ERAB _ SetupSuccess ERABAbnormalReleaseOfAlwaysOnline
CSTR ( AlwaysOnline) * * * 100%
RRC _ ConnectionAttempt Service S1SIGConnectionEstablishAttempt ERAB _ SetupAttempt ERAB Re leaseOfAlwaysOnline
IntraF _ HOOutSuccess
IntraF _ HOOut _ SR 100%
IntraF _ HOOutAttempt
HOInSuccess
HOIn _ SR 100%
HOInAttempt
HO in Attempt Counters
HO in Success Counters
IRATHO _ L 2W _ SuccessOut
IRATHO _ L 2W _ SRout 100%
IRATHO _ L 2W _ AttemptOut
This KPI can be used to evaluate the inter-RAT handover success rate from LTE to GERAN in a cluster.
IRATHO _ L 2G _ SuccessOut
IRATHO _ L 2G _ SRout 100%
IRATHO _ L 2G _ AttemptOut
IRATHO _ L 2C _ SuccessOut
IRATHO _ L 2C _ SRout 100%
IRATHO _ L 2C _ AttemptOut
C point, HO Success
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.
This KPI evaluates the DL RB (Resource Block) utility rate of a cell or cluster.
DLRB _ Used
DLRB _ UtilityRate 100%
DLRB _ Available
This KPI evaluates the UL RB (Resource Block) utility rate of a cell or cluster.
ULRB _ Used
ULRB _ UtilityRate 100%
ULRB _ Available
The ULRB_Availbable and DLRB_Available are fix values, which can be calculated by system
bandwidth.
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
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
MaxUserNumber
AvgUserNumber _ DLData
MaxUserNumber _ DLData
AvgUserNumber _ ULData
MaxUserNumber _ ULData
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.
RadioBearers
RadioBearers _ QCI _ 1
RadioBearers _ QCI _ 9
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
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.
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.
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.
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.
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.
CellDLTrafficVolume
CellDLAveThp
CellDLTransferTime
Same with the cell downlink average throughput, this set of KPI reflects the cell capacity, and the
meaning is also similar with it.
CellULTrafficVolume
CellULAveThp
CellULTransferTime
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.
CellDLMaxTrafficVolumeforEach1s (bit )
CellDLMaxThp
1000(ms )
Same with the cell downlink maximum throughput. It is calculated based on maximum value of
downlink traffic volume which are transferred at each second.
CellULMaxTrafficVolumeforEach1s (bit )
CellULMaxThp
1000(ms )
Refer to TS 32.450
This grouped KPI can be used to evaluate the latency of access phase.
AccessLatency_Attach
AccessLatency_Idle2Active
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).
ServiceLatency _ Ping _ 32bytes
ServiceLatency _ Ping _ 1460bytes
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) .
ControlPla ne _ Interrupt _ IntraLTE _ HO
ControlPla ne _ Interrupt _ IRATHO _ L 2C
ControlPla ne _ Interrupt _ IRATHO _ L 2W
ControlPla ne _ Interrupt _ IRATHO _ L 2G
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.
Recommended KPIs