Professional Documents
Culture Documents
Huawei eRAN KPI Introduction - eRAN2.1-0801
Huawei eRAN KPI Introduction - eRAN2.1-0801
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
(VoIP/Data) Frequency) Unavailabil Utility Volume Throughput
• ERAB • Service
ity Rate Rate
Setup SR • Call Setup • HO in SR • Radio Latency
(VoIP/Data) Complete Bearer
• Inter-RAT • Interrupt
Rate Number
• Call Setup HHO SR Latency
SR (VoIP/Data)
(VoIP/Data)
• By statistics /Counter:
Most of KPIs are attained by this approach, such as RRC Success Rate, HHO Success Rate…
Measurement Object
Measurement Measurement
Measurement Measurement …… ……
Family 1 Unit 1 Unit 2 Family 2
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, 60mins…
Recommended KPIs
The RRC setup procedure is trigged by different reasons as identified by the establishmentCause
field in the RRCConnctionRequest message: emergency, highPriorityAccess, mt-Access, mo-
Signalling, mo-Data.
The UE sets the establishmentCause and received by eNodeB. Causes except mo-Signalling
are categorized as service related ones, and the cause of mo-Signalling is categorized as signal
related ones.
This KPI evaluates the RRC setup success rate with service related causes in a cell or cluster.
This KPI evaluates the RRC setup success rate with signal
related causes (mo-Signalling) in a cell or cluster.
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.
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 two phases : RRC setup
phase and VoIP E-RAB setup phase:
This KPI evaluates the success rate of the whole setup procedure for data service
(except QCI 1 service) in a cell or cluster, which mainly includes two phases : RRC setup
phase and data 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 ERAB 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, User Inactivity, Partial Handover, or Handover
triggered), and all of the other E-RAB releases are consider as
normal E-RAB release.
This KPI can be used to evaluate the call drop rate of data service
(except QCI 1 service) in a cell or cluster,
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 3 phases: RRC setup phase, VoIP E-
RAB setup phase and VoIP service E-RAB release phase;
The similar as upper KPI, this KPI will evaluate the success rate in totally for 3 phases: RRC
setup phase, data service E-RAB setup phase and data service E-RAB release phase;
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
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 _ UtilityRat e 100 %
DLRB _ Available
This KPI evaluates the UL RB (Resource Block) utility rate of a cell or cluster.
ULRB _ Used
ULRB _ UtilityRat e 100 %
ULRB _ Available
The ULRB_Availbable and DLRB_Available are fix values, which can be calculated by system
bandwidth.
Active Users
This group of KPIs consist of 4 KPIs, which are used to evaluate 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
AvgUserNumber _ ULData
MaxUserNumber _ ULData
Radio Bearers
The radio bearers KPIs consist of nine sub-KPIs mapped into nine QCIs (QCI 1~9), the radio bearers
of each QCI is based on the number of active RRC connections of each QCI.
This set of KPIs can be used to evaluate the average radio bearer number of a cell or cluster.
RadioBearers _ QCI _ 1
……
RadioBearers _ QCI _ 9
Similar to the radio bearers KPIs, the DL traffic volume KPIs consist of nine sub-KPIs mapped into nine
QCIs (QCI 1~9), they can be used to evaluate the DL traffic volume of each QCI in a cell or cluster,
which is measured at RLC layer excluding the RLC header and RLC retransmission.
Similar to the radio bearers KPIs, the UL traffic volume KPIs consist of nine sub-KPIs mapped into nine
QCIs (QCI 1~9), they can be used to evaluate the UL traffic volume of each QCI in a cell or cluster,
which is measured at RLC layer excluding the RLC header and RLC retransmission.
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.
Refer to TS 32.450
Access Latency
This grouped KPI can be used to evaluate the latency of access phase.
AccessLatency_Attach
AccessLatency_Idle2Active
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).
ServiceLat ency _ Ping _ 32bytes
ServiceLat ency _ Ping _ 1460 bytes
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