Professional Documents
Culture Documents
eUTRAN Radio Orange Group Indicators v4
eUTRAN Radio Orange Group Indicators v4
The work performed in this document is based on the contribution of the different LTE MCOs and
other entities in the Orange Group.
A network status indicator is used in order to measure the Radio Access Network characteristics.
There is no associated target or objective. A performance indicator is used to measure the
performance of the Radio Access Network.
For MCOs which have more than one eUTRAN suppliers, they have to report the values separately as
indicated under Morpheus.
The type of aggregation used to calculate the final KPIs is crucial for consistent results. Each KPI
needs to be aggregated in time and space domain, and in case of multi-vendor environment
additional, multi-vendor calculation rule needs to be applied. Moreover, the type of aggregation
depends on the metrics, this is a case for multi-vendor environment in particular, where weighting
different KPIs (calculated for each vendor separately) is often more relevant than summarizing
counters from different vendors (ratios are comparable between different vendors but expressions
contributing to these ratios might be incomparable).
The two tables below present recommended aggregations in time/space domain and for multivendor
environment.
4G Traffic (BH)
... = ∑ PDCP_ SDU _ VOLUME, average over the BH for the 7 busiest
days of the month (first calculate BH for each day of the month and
then pick the seven highest values and calculate the average)
Performance Indicators
Ratio =
∑counters
, over the whole month unless stated otherwise in
∑counters
KPI descriptions
Load Indicators
General aggregation: Ratio =
∑counters , over the whole month, or
∑counters
average over the BH for the 7 busiest days of the month (please
check ‘Periodicty’ field in the KPI’s description) (first calculate BH
for each day of the month and then pick the seven highest values
and calculate the average).
If the KPI is not expressed as a ratio but it is just a counter then in
order to calculate the value at the network level (or any level other
than cell) the following aggregation should be used:
sum(KPI * traffic_DL) / sum(traffic_DL) for DL and sum(KPI *
traffic_UL) / sum(traffic_UL) for UL.
Throughput Indicators
Ratio =
∑counters , average over the whole month or over the BH’s
∑counters
within the whole month (please check ‘Periodicty’ field in the KPI’s
description).
Carrier Aggregation
General aggregation: =
∑
counters
, over the whole month.
∑
counters
If the KPI is not expressed as a ratio but it is just a counter then in
VoLTE
General aggregation: =
∑counters , over the whole month.
∑counters
If the KPI is not expressed as a ratio but it is just a counter then in
order to calculate the value at the network level (or any level other
than cell) the following aggregation should be used:
sum(KPI * traffic_DL) / sum(traffic_DL) for DL and sum(KPI *
traffic_UL) / sum(traffic_UL) for UL.
busiest days of the month (first calculate BH for each day of the month and then
pick the seven highest values and calculate the average)
4G DCR Nb of 4G Dropped Calls vendor1 + Nb of 4G Dropped Calls vendor2
, over the whole
Nb of 4G Ended Calls vendor1 + Nb of 4G Ended Calls vendor2
month
4G CSSR & ERAB Nb of ERAB Att vendor1 * KPI vendor1 + Nb of ERAB Att vendor2 * KPI vendor2
SSR Nb of ERAB Att vendor1 + Nb of ERAB Att vendor2
Mobility KPIs Numvendor1 + Num vendor2
, (over the whole month)
(HOSR, CSFB…) Denomvendor1 + Denomvendor2
4G Paging Discard
Rate
4G Avergaed
Reported CQI
4G Radio Downlink Nb of PDCP_SDUDL vendor1 * KPI vendor1 + Nb of PDCP_SDU_DL vendor2 * KPI vendor2
,
Delay Nb of PDCP_SDU_DL vendor1 + Nb of PDCP_SDU_DL vendor2
(over the whole month)
Nb of PDCP SDU DL
ALU
VS.DLPdcpPduSentByPdcp (qci1…qci9)
Ericsson
pmPdcpLatPktTransDl
Huawei
L.Traffic.DL.PktDelay.Relay.Num
Nokia
PDCP_SDU_DL
Total Mac volume transmitted over Uplink SCH (GB) Removed, for definition refer to v1.1
Total Mac volume transmitted over Uplink SCH (GB) BH Removed, for definition refer to v1.1
4G/LTE DL Traffic Volume (GBytes)
4G/LTE DL Traffic Volume (GBytes) at BH
4G/LTE UL Traffic Volume (GBytes)
4G/LTE UL Traffic Volume (GBytes) at BH
PERFORMANCE INDICATORS
4G/LTE Call Setup Success Rate
RRC Success Rate Removed, for definition refer to v1.1
ERAB Setup Success Rate (ALL)
4G/LTE Drop Call Rate (ALL)
4G/LTE Paging Discard Rate
4G/LTE Average Reported CQI
IntraRAT HO Success Rate
Inter-RAT HO Success Rate (LTE to WCDMA)
Inter-RAT HO Success Rate (LTE to GSM)
Inter-RAT HO Success Ratio (LTE to WCDMA)
CS Fallback – Mbytes per Redirection to WCDMA/GSM Removed, for definition refer to v1.1
CS Fallback – Mbytes per PS Handover to WCDMA Removed, for definition refer to v1.1
CS Fallback to WCDMA Ratio
CS Fallback Success Rate (4G side only)
4G/LTE Radio Downlink Delay
LOAD INDICATORS
Average Nb of Users (UE’s RRC Connected)
Average Nb of Users BH (UE’s RRC Connected)
Physical Resource Blocks Load DL
Physical Resource Blocks Load UL
Average Number of UE Scheduled per TTI DL
Average Number of UE Scheduled per TTI UL
Average Number of UE Scheduled per Active TTI DL
Average Number of UE Scheduled per Active TTI UL
Average Number of UE Queued DL
Importance
Importance
KPI to be monthly provided to Corporate via Morpheus (will appear in dashboards)
KPI that might appear in Morpheus in the future and is worth monitoring by local experts
MAPPING BETWEEN OLD NAMES (V2.1) AND NEW NAMES (V3.) FOR SOME OF THE KPIS
KPIS
Unit Integer
Goal To compare the number of 4G/LTE cells.
Granularity Network
Periodicity Monthly value, value of the last day of the month.
Number of Local Cell Identity (LC_CI) on air in the network
Calculation rule
Outdoor & indoor cells have to be included.
Repeaters should not be included.
Vendor formula
ALU
E///
NA extract from network inventory database
Huawei
NSN
ZTE
Comments
Definition Number of 4G/LTE geographical sites with cells on air on the network.
Unit Integer
Goal To compare the number of 4G/LTE sites.
Granularity Network
Periodicity Monthly value, value of the last day of the month.
A geographical site is defined by its address & its type (outdoor or indoor).
Calculation rule This indicator includes outdoor & indoor sites (macro, micro, pico, indoor).
Repeaters are not taken into account.
Vendor formula
ALU
E///
Huawei NA extract from network inventory database
NSN
ZTE
Comments
A mono cell counts for one, a bi-sector site counts for one if the antennas are located on the
same building or on the same pylon.
The network load hypothesis used within planning tool simulations should be noticed as
coverage is load dependent
1 Mbps used as an assumption to be coherant with the same throughput used for HSDPA (LTE
considered as a capacity solution)
Definition Percentage of the own population covered by 4G/LTE service with on air cells.
Vendor formula
ALU
E/// NA extract from planning tool
Huawei
NSN
Comments
When population is defined on areas, take the ratio of this population function of the area
coverage.
The visitor population is not taken into account; only home population is taken for calculation.
Load hypothesis have to be notified as coverage is load dependent.
1 Mbps used as an assumption to be coherant with the same throughput used for HSDPA (LTE
considered as a capacity solution)
Indicator Name
4G/LTE DL Traffic Volume (GBytes)
Cumulative data traffic volume carried by the LTE access network in downlink
Definition
during whole period
Unit GBytes
Goal To measure the PS traffic in the LTE network
Granularity Network
Periodicity Cumulative within a Month
Total number of DRB packets (PDCP SDUs) successfully transmitted (RLC
acknowledged by UE) in the downlink.
This KPI computes the total PDCP SDU traffic volume over the whole month.
- This traffic is observed from the first hour of the 1st day of the month till the last
hour of the last day of the month
Vendor formula
ALU (VS.DRBPdcpSduKbytesDL*1024)/(1000*1000*1000)
LR13.3&14.1&15.1
Huawei
Huawei
[L.Thrp.bits.DL]/(8*{1000}*{1000}*}*{1000})
eRAN
6.0&8.0&11.0
Indicator Name
4G/LTE DL Traffic Volume (GBytes) at BH
Volume transferred in the LTE access network in downlink at the LTE network
busy hour of the period for downlink.
Definition
Traffic at the BH of the month should be calculated as the average of the traffic of
the seven highest daily busy hours.
Unit GBytes
- Average of Traffic of all cells at the network busy hour, for the 7 highest values of
the month.
Vendor formula
ALU (VS.DRBPdcpSduKbytesDL*1024)/(1000*1000*1000)
LR13.3&14.1&15.1
Huawei
[L.Thrp.bits.DL]/(8*{1000}*{1000}*}*{1000})
eRAN
6.0&8.0&11.0
- This traffic is observed from the first hour of the 1st day of the month till the last
hour of the last day of the month
Vendor formula
ALU
(VS.DRBPdcpSduKbytesUL*1024)/(1000*1000*1000)
LR13.3&14.1&15.1
Huawei
[L.Thrp.bits.UL]/(8*{1000}*{1000}*}*{1000})
eRAN
6.0&8.0&11.0
- Average of Traffic of all cells at the network busy hour, for the 7 highest values of
the month.
Vendor formula
ALU
(VS.DRBPdcpSduKbytesUL*1024)/(1000*1000*1000)
LR13.3&14.1&15.1
E///
pmPdcpVolUlDrb /(8*1000*1000)
L13B&14B&15B
Huawei
eRAN [L.Thrp.bits.UL]/(8*{1000}*{1000}*}*{1000})
6.0&8.0&11.0
Comments
Retransmissions not included
Percentage of established calls over the requested ones for all types of connections.
Definition
A call is established when the UE has established its E-Radio Access Bearer(s).
Where RRC_SR:
Nb of RRC Messages " RRCConnectionSetupComplete"
RRCsuccessrate =
Nb of RRC Messages " RCConnectionRequest"
S1_SR
Calculation rule
Nb of first messages recieved from MME after sending " Initial UE Message"
S1 _ SuccessRate =
Nb of UE Initial Messages sent to the MME
ERAB_Initial_SetupSuccess
ERAB _ SR =
ERAB_Initial_SetupAttempt
S1 signalling part is not included in this KPI in this version of the document, the
introduction of the S1 part can be considered in the next releases.
Vendor formula
ALU
100 * RRC.ConnEstabSucc.Sum/ (VS.RrcConnectionRequestWithoutRepetition )
LR13.3&14.1&15.1
*(S1SIG.ConnEstabAtt- VS.S1ConnectionEstablishmentFailure )/S1SIG.ConnEstabAtt
* (SAEB.EstabInitSuccNbr/ SAEB.EstabInitAttNbr)
100*((L.RRC.ConnReq.Succ.Emc + L.RRC.ConnReq.Succ.HighPri +
L.RRC.ConnReq.Succ.Mt + L.RRC.ConnReq.Succ.MoData +
Huawei
L.RRC.ConnReq.Succ.DelayTol)/(L.RRC.ConnReq.Att.Emc +
eRAN
L.RRC.ConnReq.Att.HighPri + L.RRC.ConnReq.Att.Mt +
6.0&8.0&11.0
L.RRC.ConnReq.Att.MoData + L.RRC.ConnReq.Att.DelayTol))
* (L.S1Sig.ConnEst.Succ/L.S1Sig.ConnEst.Att)
*(L.E-RAB.InitSuccEst/L.E-RAB.InitAttEst)
RL60
100* ([SIGN_CONN_ESTAB_COMP]) / ([SIGN_CONN_ESTAB_ATT_MO_S]+
[SIGN_CONN_ESTAB_ATT_MT]+ [SIGN_CONN_ESTAB_ATT_MO_D]+
SIGN_CONN_ESTAB_ATT_DEL_TOL+ SIGN_CONN_ESTAB_ATT_HIPRIO+
[SIGN_CONN_ESTAB_ATT_EMG])
*{([EPS_BEARER_STP_COM_INI_QCI1]+[EPS_BEARER_STP_COM_INI_QCI_2]
+[EPS_BEARER_STP_COM_INI_QCI_3]+[EPS_BEARER_STP_COM_INI_QCI_4]
+[EPS_BEAR_STP_COM_INI_NON_GBR]) /
([EPS_BEARER_STP_ATT_INI_QCI_1])+[EPS_BEARER_STP_ATT_INI_QCI_2]
+[EPS_BEARER_STP_ATT_INI_QCI_3] +[EPS_BEARER_STP_ATT_INI_QCI_4]
+[EPS_BEAR_STP_ATT_INI_NON_GBR])}
NSN
RL60&70&FL15 RL 70, FL15A
[SIGN_CONN_ESTAB_COMP/
(SIGN_CONN_ESTAB_ATT_MO_S + SIGN_CONN_ESTAB_ATT_MT +
SIGN_CONN_ESTAB_ATT_MO_D + SIGN_CONN_ESTAB_ATT_OTHERS +
SIGN_CONN_ESTAB_ATT_EMG)]
*
[S1_SIGN_CONN_ESTAB_SUCC_UE/ S1_SIGN_CONN_ESTAB_ATT_UE]
*
[(ERAB_INI_SETUP_SUCC_QCI1+ERAB_INI_SETUP_SUCC_QCI2
+ERAB_INI_SETUP_SUCC_QCI3+ERAB_INI_SETUP_SUCC_QCI4
+ERAB_INI_SETUP_SUCC_QCI5+ERAB_INI_SETUP_SUCC_QCI6
+ERAB_INI_SETUP_SUCC_QCI7+ERAB_INI_SETUP_SUCC_QCI8
+ERAB_INI_SETUP_SUCC_QCI9)/
(ERAB_INI_SETUP_ATT_QCI1+ERAB_INI_SETUP_ATT_QCI2
Remark1:
1. S1 SSR is not available for RL/60
2. RRC reestablishment M8008C4/M8008C5
3. Initial ERAB SSR =
(M8006C206+M8006C207+M8006C208+M8006C209+M8006C210+M8006C21
2+M8006C213+M8006C214)/
(M8006C188+M8006C189+M8006C190+M8006C191+M8006C192+M8006C19
3+M8006C194+M8006C195+M8006C196)
Comments
Definition
Percentage of ERAB Setups completed over the requested ones.
Unit Ratio (%)
Goal Measures the accessibility of the services from the customer point of view.
Granularity Network
Periodicity Monthly value (average value from the first day to the last day of the month on a network
basis).
The KPI describes the setup success ratio of the elementary E-RAB setup procedure used to
setup the E-RAB between MME and UE.
It indicates the E-UTRAN contribution to network accessibility for the end-user, not the whole
end-to-end service accessibility.
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. This KPI is calculated based on the counters (both the
Calculation rule ERAB setup attempts (All) and the successful ERAB setup (All) counters) measured at the
eNodeB.
ERABSetupSuccess
ERABS _ SR = x100%
ERABSetupAttempt
Vendor formula
100*L.E-RAB.SuccEst/L.E-RAB.AttEst
100*EPS_BEARER_SETUP_COMPLETIONS/EPS_BEARER_SETUP_ATTEMPTS
Remark:
1. The suggested NSN formula for EUTRAN E-RAB Setup Success Rate is a formula
NSN recommended by NSN. It should be noted though that the formula includes EPS Bearer
RL60&70&FL15 counters (not ERAB counters) – EPS Bearer is used to transport data between the UE
and PGW while ERABS refer to the connection between the UE and SGW. An
alternative definition may look as follows:
100* E_RAB_SETUP_SUCC/E_RAB_SETUP_ATT
2. RL70and FL15A Counters to exclude VoLTE: ERAB_ADD_SETUP_SUCC_QCI1
ERAB_ADD_SETUP_SUCC_QCI1
(M8006C215) and ERAB_ADD_SETUP_ATT_QCI1 (M8006C197)
Comments
Ratio between the number of drop calls over the total number of normal connection releases
Definition
for Data PS .
This KPI describes the ratio of abnormally released (dropped) E-RABs from user perspective
point of view.
This KPI can be used to evaluate the call drop rate of all services in a cell or a cluster, including
Calculation rule VoIP service.
ERABAbnormalReleases
DCR = x100%
ERABReleases(ALL)
Calculation
difficulty
Vendor formula
100*(VS.AbnormalERABReleasePerQCI +VS.ERABReleasedDueToRadioLinkFailurePerQCI +
ALU VS.OtherAbnormalERABReleasePerQCI )/
LR13.3&14.1&15.1 (VS.AbnormalERABReleasePerQCI+VS.ERABReleasedDueToRadioLinkFailurePerQCI +
VS.OtherAbnormalERABReleasePerQCI +VS.NormalERABRelease)
100*(EPC_EPS_BEARER_REL_REQ_RNL+EPC_EPS_BEARER_REL_REQ_OTH
+ENB_EPS_BEARER_REL_REQ_RNL+ENB_EPS_BEARER_REL_REQ_TNL
+ENB_EPS_BEARER_REL_REQ_OTH)
/(EPC_EPS_BEARER_REL_REQ_NORM
+EPC_EPS_BEARER_REL_REQ_DETACH+EPC_EPS_BEARER_REL_REQ_RNL
+EPC_EPS_BEARER_REL_REQ_OTH+ENB_EPSBEAR_REL_REQ_RNL_REDIR
+ENB_EPS_BEARER_REL_REQ_NORM+ENB_EPS_BEARER_REL_REQ_RNL
+ENB_EPS_BEARER_REL_REQ_TNL+ENB_EPS_BEARER_REL_REQ_OTH
+ PRE_EMPT_GBR_BEARER +PRE_EMPT_NON_GBR_BEARER)
NSN
FL-15A
RL60&70&FL15
100*(ERAB_REL_HO_PART + ERAB_REL_ENB - ERAB_REL_ENB_RNL_INA -
ERAB_REL_ENB_RNL_RED + EPC_EPS_BEARER_REL_REQ_RNL +
EPC_EPS_BEARER_REL_REQ_OTH - (ERAB_REL_HO_PART_QCI1 +
ERAB_REL_ENB_QCI1 - ERAB_REL_ENB_RNL_INA_QCI1 -
ERAB_REL_ENB_RNL_RED_QCI1))
/
(ERAB_REL_ENB + ERAB_REL_HO_SUCC + ERAB_REL_HO_PART +
EPC_EPS_BEARER_REL_REQ_NORM + EPC_EPS_BEARER_REL_REQ_DETACH +
EPC_EPS_BEARER_REL_REQ_RNL + EPC_EPS_BEARER_REL_REQ_OTH -
(ERAB_REL_ENB_QCI1 + ERAB_REL_HO_PART_QCI1 +
EPC_EPS_BEAR_REL_REQ_N_QCI1 + EPC_EPS_BEAR_REL_REQ_D_QCI1 +
EPC_EPS_BEAR_REL_REQ_R_QCI1 + EPC_EPS_BEAR_REL_REQ_O_QCI1))
Comments
Calculation rule This KPI describes the paging request discard ratio on RRC level.
Calculation
difficulty
Vendor formula
ALU
100* VS.S1PageAttemptsDiscarded/VS.S1PageAttemptsFromMMEs
LR 13.3&14.1&15.1
100*L.Paging.Dis.Num/ L.Paging.S1.Rx
Huawei
Remark:
eRAN 6.0&8.0&11.0
a new counter available in eRAN 6.0: L.Paging.Dis.PchCong – counts paging discarded due to
paging channel congestion .
100*DISC_RRC_PAGING / RRC_PAGING_REQUESTS
NSN
RL60&70&FL15 100*sum([M8008C2]) / sum([M8008C1])
Comments
Definition Reported CQI averaged over the network over the whole month.
Unit None
Goal Asses the quality of the radio part .
Calculation rule This KPI describes the quality of the LTE radio part.
Calculation
difficulty
Vendor formula
(1*CQI1+2*CQI2+3*CQI3+4*CQI4+5*CQI5+6*CQI6+7*CQI7+8*CQI8+9*CQI9+10*CQI10+11
*CQI11+12*CQI12+13CQI13+14CQI14+15CQI15)/
(CQI0+CQI1+CQI2+CQI3+CQI4+CQI5+CQI6+CQI7+CQI8+CQI9+CQI10+CQI11+CQI12+CQI1
ALU
3+CQI14+CQI15)
LR
13.3&14.1&15.1 where CQIx=VS.Rank1WBCqi.x + VS.Rank2Layer0WBCqi.x + VS.Rank2Layer1WBCqi.x
(L13013 + L13014 + L13015)
and x=0,1…15
(1*L.ChMeas.CQI.DL.1+ 2*L.ChMeas.CQI.DL.2+3*L.ChMeas.CQI.DL.3+
4*L.ChMeas.CQI.DL.4+ 5*L.ChMeas.CQI.DL.5
+ 6*L.ChMeas.CQI.DL.6+ 7*L.ChMeas.CQI.DL.7+ 8*L.ChMeas.CQI.DL.8+
9*L.ChMeas.CQI.DL.9+ 10*L.ChMeas.CQI.DL.10
+ 11*L.ChMeas.CQI.DL.11+ 12*L.ChMeas.CQI.DL.12+ 13*L.ChMeas.CQI.DL.13+
Huawei
14*L.ChMeas.CQI.DL.14+ 15*L.ChMeas.CQI.DL.15)
eRAN /( L.ChMeas.CQI.DL.0+ L.ChMeas.CQI.DL.1+ L.ChMeas.CQI.DL.2+L.ChMeas.CQI.DL.3+
6.0&8.0&11.0 L.ChMeas.CQI.DL.4+ L.ChMeas.CQI.DL.5
+ L.ChMeas.CQI.DL.6+ L.ChMeas.CQI.DL.7+ L.ChMeas.CQI.DL.8+ L.ChMeas.CQI.DL.9+
1L.ChMeas.CQI.DL.10
+ L.ChMeas.CQI.DL.11+ L.ChMeas.CQI.DL.12+ L.ChMeas.CQI.DL.13+ L.ChMeas.CQI.DL.14+
L.ChMeas.CQI.DL.15)
(1*[UE_REP_CQI_LEVEL_01]+ 2*[UE_REP_CQI_LEVEL_02]+
NSN 3*[UE_REP_CQI_LEVEL_03]+ 4*[UE_REP_CQI_LEVEL_04]+ 5*[UE_REP_CQI_LEVEL_05]
RL60&70&FL15 + 6*[UE_REP_CQI_LEVEL_06]+ 7*[UE_REP_CQI_LEVEL_07]+
8*[UE_REP_CQI_LEVEL_08]+ 9*[UE_REP_CQI_LEVEL_09]+ 10*[UE_REP_CQI_LEVEL_10]
Comments
Definition This KPI can be used to evaluate the intra-RAT handover success rate in a cell or a cluster.
This KPI describes the success ratio for the handover execution phase, when the source eNB receives
information that the UE successfully is connected to the target cell within own eNB and for the inter eNB
X2 and the inter eNB S1 based handover execution phase, when the source eNB receives information that
the UE successfully is connected to the target cell within target eNB.
Calculation rule
IntraEnodebHO_Success + InterEnodebX2HO_Success + InterEnodebS1HO_Success
IntraRATHO _ SR = x100%
IntraEnodebHO_Attempt + InterEnodebX2HO_Attempt + InterEnodebS1HO_Attempt
100*(HO.IntraEnbOutSucc.Sum +VS.OutgoingInterENodeBX2HOSuccess
+VS.OutgoingInterENodeBS1HOSuccess)/
ALU
(VS.OutgoingIntraENodeBHOAttempt+VS.OutgoingInterENodeBX2HOAttempt+VS.OutgoingInterEN
LR odeBS1HOAttempt)
13.3&14.1&15.1
100*(`LC12746 `+`LC12707`+`LC12721`)/(`LC12745`+`LC12706`+`LC12720`)
E///
L13B&14B&15B 100* (pmHoExeSuccLteIntraF + pmHoExeSuccLteInterF)
s1 and x2 included
100*(L.HHO.IntraeNB.IntraFreq.ExecSuccOut+L.HHO.IntraeNB.InterFreq.ExecSuccOut+L.HHO.Inter
eNB.IntraFreq.ExecSuccOut+L.HHO.IntereNB.InterFreq.ExecSuccOut)/(
Huawei
L.HHO.IntraeNB.IntraFreq.PrepAttOut + L.HHO.IntraeNB.InterFreq.PrepAttOut
eRAN +L.HHO.IntereNB.IntraFreq.PrepAttOut+ L.HHO.IntereNB.InterFreq.PrepAttOut)
6.0&8.0&11.0
s1 and x2 included
NSN 100*(SUCC_INTRA_ENB_HO+SUCC_INTER_ENB_HO+INTER_ENB_S1_HO_SUCC) /
RL60&70&FL15 (INTRA_ENB_HO_PREP+INTER_ENB_S1_HO_PREP+INTER_ENB_HO_PREP)
Comments
4.2.7. INTER-
INTER-RAT HO SUCCESS RATE
RATE (LTE TO WCDMA)
This KPI can be used to evaluate the inter-RAT handover out success rate in a cell or a cluster.
Definition As suggested by the name, this KPI measures the performance of the inter-RAT handover
from LTE to WCDMA.
This KPI describes the success ratio for the inter RAT handover execution phase, when the source eNB
receives information that the UE successfully is connected to the target cell (WCDMA).
Vendor formula
ALU
100*VS.OutgoingPSHOToUtraFddSuccess/VS.OutgoingPSHOToUtraFddAttempt
LR
13.3&14.1&15.1
Huawei
100*L.IRATHO.E2W.ExecSuccOut/ L.IRATHO.E2W.PrepAttOut
eRAN
6.0&8.0&11.0
NSN 100*ISYS_HO_SUCC / ISYS_HO_PREP
RL60&70&FL15
Comments
4.2.8. INTER-
INTER-RAT HO SUCCESS RATE (LTE TO GSM)
GSM)
This KPI can be used to evaluate the inter-RAT handover out success rate in a cell or a cluster.
Definition This KPI measures the performance of the inter-RAT handover
from LTE to GSM.
This KPI describes the success ratio for the inter RAT handover execution phase, when the source eNB
receives information that the UE successfully is connected to the target cell (GSM).
Vendor formula
100*VS.CCOToGeranSuccess /VS.CCOToGeranAttempt
ALU
LR 100*(`LC12763_0`+`LC12763_1`+`LC12763_2`+`LC12763_3`+`LC12763_4`+`LC12763_5`)/
13.3&14.1&15.1 (`LC12762_0`+`LC12762_1`+`LC12762_2`+`LC12762_3`+`LC12762_4`+`LC12762_5`)
E/// N/A
Huawei
100*L.IRATHO.E2G.ExecSuccOut
eRAN / L.IRATHO.E2G.PrepAttOut
6.0&8.0&11.0
NSN N/A
Comments
4.2.9. INTER-
INTER-RAT HO RATIO
RATIO (LTE TO WCDMA)
This KPI can be used to evaluate the performance of the network on the basis of the number of attempted
Definition handovers in reference to the number of established eRABs
This KPI describes the ratio of inter RAT handover attempts over successfully established
eERABs.
Calculation rule
IRATHO_L2W_Attempt
IRATHO _ L2W _ RATIO = x100%
ERABSetupSuccess
Vendor formula
ALU
100* VS.OutgoingPSHOToUtraFddAttempt/(SAEB.EstabInitSuccNbr +SAEB.EstabAddSuccNbr)
LR
13.3&14.1&15.1
Huawei
100* L.IRATHO.E2W.PrepAttOut/ L.E-RAB.SuccEst
eRAN
6.0&8.0&11.0
NSN 100* ISYS_HO_PREP / EPS_BEARER_SETUP_COMPLETIONS
RL60&70&FL15
Comments
This KPI describes the ratio of CSFB to WCDMA attempts (redirection and PSHO)
over successfully established eERABs.
Vendor formula
(VS.RedirectionToUtraFdd.#6+ VS.EnhancedRedirectionToUtraFdd#4+
ALU
VS.OutgoingCsFallbackPSHOToUtraFddAttempt)/
LR 13.3&14.1&15.1 (SAEB.EstabInitSuccNbr +SAEB.EstabAddSuccNbr)
Huawei
Huawei
eRAN L.CSFB.E2W/L.E-RAB.SuccEst
6.0&8.0&11.0
(CSFB_REDIR_CR_ATT+ CSFB_PSHO_UTRAN_ATT)/
EPS_BEARER_SETUP_COMPLETIONS
NSN
Remark:
RL60&70&FL15 CSFB_REDIR_CR_ATT counter is updated in case of CSFB to UTRAN or GSM, therefore
if redirection to GSM is acvtivated than this formula is incomparable with other vendors
Comments
Successful CSFB:
Redirection
The eNodeB sends an RRC Connection Release message to a UE to perform a CSFB to
2G/3G
Handover
The eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME
Calculation rule
CSFB_redir ection to_ GSM + CSFB_redir ection_to_ WCDMA + CSFB _ L 2W _ Success ( HO ) + CSFB _ L 2 G _ Succes ( HO )
CSFB _ SR = x 100 %
CSFB_Prepa ration_Att empt
This KPI does not match requirements for all the vendors and the proposed
definitions need to be tested in the field.
This KPI reflects only 4G side and does not give any view on the CSFB procedure
on 3G /2G side.
Vendor formula
100*(VS.RedirectionToUtraFdd.#6+ VS.EnhancedRedirectionToUtraFdd.#4
+ VS.RedirectionToGeran.#4
ALU +VS.OutgoingCsFallbackPSHOToUtraFddSuccess +VS.CsFallbackCCOToGeranSuccess)
LR /
13.3&14.1&15.1 (VS.CsFallbackRequest)
Remark:
If no screenings are mentioned it means all the screening should be considered
E/// N/A
Huawei
100*(L.RRCRedirection.E2W.CSFB+L.RRCRedirection.E2G.CSFB
eRAN +L.IRATHO.E2W.CSFB.ExecSuccOut+ L.IRATHO.E2G.CSFB.ExecSuccOut)
6.0&8.0&11.0 /L.CSFB.PrepAtt
Comments
4.2.12. 4G/LTE
4G/LTE RADIO DOWNLINK DELAY
The effective DL Latency time comprises the time from PDCP DRB SDU entering the
buffer until the first data has been transmitted to the UE.
Calculation rule /
Number of DRB packets for downlink Latency measurements
Vendor formula
LR15.1
14214
E///
pmPdcpLatTimeDl/pmPdcpLatPktTransDl
L13B&14B&15B
Huawei
eRAN L.Traffic.DL.PktDelay.Time/L.Traffic.DL.PktDelay.Num
6.0&8.0&11.0
PDCP_SDU_DELAY_DL_DTCH_MEAN
NSN
RL60&70&FL15 The above counter should be aggregated as follows:
Comments
Vendor formula
E///
pmRrcConnLevSum/ pmRrcConnLevSamp
L13B&14B&15B
Huawei
eRAN L.Traffic.User.Avg
6.0&8.0&11.0
NSN sum([SUM_RRC_CONN_UE])/sum([DENOM_RRC_CONN_UE])
RL60&70&FL15 sum([M8001C318])/sum([M8001C319])
Comments
Nokia additional counters
CELL_LOAD_ACT_UE_AVG ( at least one non-GBR DRB)
sum([M8001C223])
4.3.2. AVERAGE
AVERAGE NB OF USERS BH (UE’S RRC CONNECTED)
Vendor formula
ALU
LR 13.3&14.1&15.1 RRC.Conn.AVG=`LC13201_Cum`/`LC13201_NbEvt`
E///
L13B&14B&15B pmRrcConnLevSum/ pmRrcConnLevSamp
Huawei
eRAN L.Traffic.User.Avg
6.0&8.0&11.0
NSN sum([SUM_RRC_CONN_UE])/sum([DENOM_RRC_CONN_UE])
RL60&70&FL15 sum([M8001C318])/sum([M8001C319])
Comments
This KPI is calculated by dividing the total number of used RBs by the number of available
RBs.
Average of the physical resource blocks load of all cells at the network busy hour, for the 7
highest values of the month.
Vendor formula
VS.DLPRBUsed(12032)
100*(pmPrbUsedDlAilgHighPrio + pmPrbUsedDlAilgTot
+ pmPrbUsedDlBcch + pmPrbUsedDlDtch
+ pmPrbUsedDlFirstTrans
E///
+ pmPrbUsedDlMbms + pmPrbUsedDlPcch
L13B&14B&15B + pmPrbUsedDlReTrans +pmPrbUsedDlSrbFirstTrans)/
pmPrbAvailDl
Huawei
eRAN 100*L.ChMeas.PRB.DL.Used.Avg / L.ChMeas.PRB.DL.Avail
6.0&8.0&11.0
NSN
avg([DL_PRB_UTIL_TTI_MEAN])/10
RL60&70&FL15
Comments
This KPI is calculated by dividing the total number of used RBs by the number of available
RBs.
Average of the physical resource blocks load of all cells at the network busy hour, for the 7
highest values of the month.
Vendor formula
VS.ULPRBUsed(12033)
100*
(pmPrbUsedUlAilgTot
E///
+ pmPrbUsedUlDtch+ pmPrbUsedUlSrb)
L13B&14B&15B /
pmPrbAvailUl
Huawei
eRAN 100* L.ChMeas.PRB.UL.Used.Avg / L.ChMeas.PRB.UL.Avail
6.0&8.0&11.0
NSN
avg([UL_PRB_UTIL_TTI_MEAN])/10
RL60&70&FL15
Comments
Average of the number of UEs scheduled per TTI of all cells at the network busy hour, for
the 7 highest values of the month.
Vendor formula
ALU
VS.NbUeScheduledPerDLTTI.Cum/{Observation_Period_ms}
LR 13.3&14.1&15.1
E///
pmSchedActivityUeDl/{Observation_Period_ms}
L13B&14B&15B
Huawei
eRAN L.Traffic.SUNPT.DL.Avg
7.0&8.0&11.0
sum([SUM_ACT_UE_SCHED_DATA_DL]/
NSN
sum([DENOM_ACT_UE_SCHED_DATA_DL]
RL60&70&FL15
sum([M8001C297]/ sum([M8001C298]
Comments
Average of the number of UEs scheduled per TTI of all cells at the network busy hour, for
the 7 highest values of the month.
Vendor formula
ALU VS.NbUeScheduledPerULTTI.Cum//{Observation_Period_ms}
LR 13.3&14.1&15.1
Huawei L.Traffic.SUNPT.UL.Avg
eRAN
7.0&8.0&11.0
Comments
Average of the number of UEs scheduled per TTI of all cells at the network busy hour, for
the 7 highest values of the month.
Vendor formula
E///
L13B&14B&15B pmSchedActivityUeDl/ pmSchedActivityCellDl
Comments
Average of the number of UEs scheduled per TTI of all cells at the network busy hour, for
the 7 highest values of the month.
Vendor formula
VS.NbUeScheduledPerULTTI.Cum/VS.NbUeScheduledPerULTTI.NbEvt
ALU
13002
LR 13.3&14.1&15.1
E///
pmSchedActivityUeUl/ pmSchedActivityCellUl
L13B&14B&15B
Comments
Vendor formula
FDD
VS.DLRlcBurstTime/(3600*1000)
(12124)/(3600*1000)
ALU
LR 13.3&14.1&15.1 TDD
VS.NbActiveUEInDLPerTypeService.Cum/
VS.NbActiveUEInDLPerTypeService.NbEvt
13216
E///
L13B&14B&15B Remark:
Sampling interval 1 ms (TTI)
Cell load (BH)= pmActiveUeDlSum/3600000
NSN sum([SUM_ACTIVE_UE_DATA_DL]/sum([DENOM_ACTIVE_UE_DATA_DL])
RL60&70&FL15 sum([M8001C264])/sum([M8001C265])
Comments
Huawei L.Traffic.ActiveUser.UL.Avg
eRAN
6.0&8.0&11.0
Remark: only eRAN 6.0 counter is good to define Cell load (due to sampling
NSN sum([SUM_ACTIVE_UE_DATA_UL]/sum([DENOM_ACTIVE_UE_DATA_UL])
RL60&70&FL15 sum([M8001C266])/sum([M8001C267])
Comments
Volume_ of _ Traffic
Average_ Throughput=
Total _ Time_ of _ Transmission
With:
Volume_ of _ Traffic= ∑ SDU_ PDCP_ Size
Total_ Time_ of _ Transmission = ∑ Time_ of _ transmission
Calculation rule
NOTE:
This formula takes into account the total volume of traffic, including ‘the last TTI’,
which might not be fully used and thus the throughput may be pessimistic.
The difference between between throughput with the last TTI and without the last
TTI depends on the traffic pattern and may differ from one network/cell to another.
For some cells both throughput can be almost identical while for some other
throughput without the lats TTI may be even 4-5 times higher.
At the moment it is not possible to define throughput without the last TTI for the
main suppliers in the Group (ALU, E//, HUA, Nokia)
Vendor formula
ALU
LR VS.DRBPdcpSduKbytesDL*8* 1024/ VS.NbUeScheduledPerDLTTI.NbEvt
13.3&14.1&15.1 14201*8*1024/13001
NSN 8*sum([PDCP_SDU_VOL_DL])/sum([ACTIVE_TTI_DL])
RL60&70&FL15 8*sum([M8012C20])/sum([M8012C90])
Comments
Volume_ of _ Traffic
Average_ Throughput=
Total_ Time_ of _ Transmission
With:
Volume_ of _ Traffic= ∑ SDU_ PDCP_ Size
Total_ Time_ of _ Transmission = ∑ Time_ of _ transmission
Calculation rule
NOTE:
This formula takes into account the total volume of traffic, including ‘the last TTI’,
which might not be fully used and thus the throughput may be pessimistic.
The difference between between throughput with the last TTI and without the last
TTI depends on the traffic pattern and may differ from one network/cell to another.
For some cells both throughput can be almost identical while for some other
throughput without the lats TTI may be even 4-5 times higher.
At the moment it is not possible to define throughput without the last TTI for the
main suppliers in the Group (ALU, E//, HUA, Nokia)
Vendor formula
ALU
LR VS.DRBPdcpSduKbytesDL*8* 1024/ VS.NbUeScheduledPerDLTTI.NbEvt
13.3&14.1&15.1
E/// pmPdcpVolDlDrb/ (pmSchedActivityCellDl/1000)
L13B&14B&15B
Huawei
eRAN L.Thrp.bits.DL/ L.Thrp.Time.Cell.DL.HighPrecision
6.0&8.0&11.0
NSN 8*sum([PDCP_SDU_VOL_DL])/sum([ACTIVE_TTI_DL])
RL60&70&FL15 8*sum([M8012C20])/sum([M8012C90])
Comments
Volume_ of _ Traffic
Average_ Throughput=
Total_ Time_ of _ Transmission
With:
Volume_ of _ Traffic= ∑ SDU_ PDCP_ Size
Total_ Time_ of _ Transmission = ∑ Time_ of _ transmission
Calculation rule
NOTE:
This formula takes into account the total volume of traffic, including ‘the last TTI’,
which might not be fully used and thus the throughput may be pessimistic.
The difference between between throughput with the last TTI and without the last
TTI depends on the traffic pattern and may differ from one network/cell to another.
For some cells both throughput can be almost identical while for some other
throughput without the lats TTI may be even 4-5 times higher.
At the moment it is not possible to define throughput without the last TTI for the
main suppliers in the Group (ALU, E//, HUA, Nokia)
Vendor formula
ALU
VS.DRBPdcpSduKbytesUL*8*1024/ VS.NbUeScheduledPerULTTI.NbEvt
LR 14202*8*2014/13002
13.3&14.1&15.1
E///
L13B&14B&15B pmPdcpVolUlDrb/( pmSchedActivityCellUl/1000)
Huawei
eRAN L.Thrp.bits.UL / L.Thrp.Time.Cell.UL.HighPrecision
6.0&8.0&11.0
8*Sum[PDCP_SDU_VOL_UL]/ sum[ACTIVE_TTI_UL]
NSN
RL60&70&FL15 8*sum[M8012C19]/sum[M8012C89]
Comments
Volume_ of _ Traffic
Average_ Throughput=
Total_ Time_ of _ Transmission
With:
Volume_ of _ Traffic= ∑ SDU_ PDCP_ Size
Total_ Time_ of _ Transmission = ∑ Time_ of _ transmission
Calculation rule
NOTE:
This formula takes into account the total volume of traffic, including ‘the last TTI’,
which might not be fully used and thus the throughput may be pessimistic.
The difference between between throughput with the last TTI and without the last
TTI depends on the traffic pattern and may differ from one network/cell to another.
For some cells both throughput can be almost identical while for some other
throughput without the lats TTI may be even 4-5 times higher.
At the moment it is not possible to define throughput without the last TTI for the
main suppliers in the Group (ALU, E//, HUA, Nokia)
Vendor formula
ALU
VS.DRBPdcpSduKbytesUL*8*1024/ VS.NbUeScheduledPerULTTI.NbEvt
LR 14202*8*2014/13002
13.3&14.1&15.1
8*Sum[PDCP_SDU_VOL_UL]/ sum[ACTIVE_TTI_UL]
NSN
RL60&70&FL15 8*sum[M8012C19]/sum[M8012C89]
Comments
Volume_ of _ Traffic
Total _ Time_ of _ Transmission
Average_ Throughput=
Average_ Nb _ of _ Users_ ActTTI
With:
Volume_ of _ Traffic= ∑ SDU_ PDCP_ Size
Total_ Time_ of _ Transmission = ∑ Time_ of _ transmission
At the moment it is not possible to define throughput without the last TTI for the
main suppliers in the Group (ALU, E//, HUA, Nokia)
Vendor formula
VS.DRBPdcpSduKbytesDL*8* 1000
1000/
00 (VS.NbUeScheduledPerDLTTI.Cum)
Remark:
ALU
Definition excluding last TTI is avialble only at the RLC PDU level
LR
(Downlink RLC burst size - Downlink RLC PDU size in last TTI)*8*1024/
13.3&14.1&15.1
(Downlink
(Downlink RLC burst time - Downlink RLC last TTI time)
screenings #0, 1,2
(12126 – 12127)*8*1024/(12124 – 12125)
E///
pmPdcpVolDlDrb/ (pmSchedActivityUeDl/1000)
L13B&14B&15B
Remark:
L.Thrp.bits.DL/ L.Thrp.Time.DL
Huawei
Remark:
eRAN If the last TTI is to be excluded then the following formula should be used:
6.0&8.0&11.0 (L.Thrp.bits.DL - L.Thrp.bits.DL.LastTTI)/L.Thrp.Time.DL.RmvLastTTI
* this formula cannot be used for benchmarking against other suplliers
8*sum([PDCP_SDU_VOL_DL])/ (sum([SUM_ACT_UE_SCHED_DATA_DL]))
8*sum([M8012C20])/(sum([M8001C297]))
NSN Remark:
RL60&70&FL15 Definition excluding last TTI:
Σ IP_TPUT_VOL_DL_QCI_1…9/
Σ IP_TPUT_NET_TIME_DL_QCI_1…9
Comments
Volume_ of _ Traffic
Total _ Time_ of _ Transmission
Average_ Throughput=
Average_ Nb _ of _ Users_ ActTTI
With:
Volume_ of _ Traffic= ∑ SDU_ PDCP_ Size
Total_ Time_ of _ Transmission = ∑ Time_ of _ transmission
At the moment it is not possible to define throughput without the last TTI for the
main suppliers in the Group (ALU, E//, HUA, Nokia)
Vendor formula
ALU
LR VS.DRBPdcpSduKbytesUL*8* 1000/ (VS.NbUeScheduledPerULTTI.Cum)
13.3&14.1&15.1
pmPdcpVolUlDrb/ (pmSchedActivityUeUl/1000)
E///
Remark:
L13B&14B&15B E// definition: pmUeThpVolUl/pmUeThpTimeUl/1000
excludes the volume received in the first 4 data receptions of an UL buffer transfer and the
TTI emptying the UL buffer. This E// definition cannot be used for benchmarking.
L.Thrp.bits.UL / L.Thrp.Time.UL
Huawei
Remark:
eRAN
If the last TTI is to be excluded then the following formula should be used:
6.0&8.0&11.0 (L.Thrp.bits.UL - L.Thrp.bits.UE.UL.LastTTI)/L.Thrp.Time.UE.UL.RmvLastTTI
* this formula cannot be used for benchmarking against other suplliers
Comments
VS.NbUECaActivatedCell (13052)
Screenings:
ALU #0 2DL activation.
LR15.1 #1 3DL activation.
(13052_0_Cum+ 13052_1_Cum)/ (3052_0_NbEvt + 13052_1_NbEvt)
Huawei
eRAN 8.0&11.0 L.Traffic.User.SCell.Active.DL.Avg
CA_SCELL_ACTIVE_UE_AVG/100
NSN M8001C496/100
RL60&70&FL15
E-UTRAN Average UEs with an Activated SCell in DL
Comments
This KPI describes the ratio between abnormal E-RAB releases and abnormal and normal
E-RAB releases for CA UEs .
Calculation rule
ERABAbnormalReleases_CA_UE's
DCR = x100%
ERABReleases_CS_UE' s
ALU N/A
E/// N/A
NSN
N/A
Comments
With:
Volume_ of _ Traffic= ∑ SDU_ PDCP_ Size
Total_ Time_ of _ Transmission = ∑ Time_ of _ transmission
This KPI is yet to be checked and validated in the field.
Vendor formula
N/A
Remark:
ALU For L15.1 RLC PDU throuput for CA users
VS.DLRlcBurstSize_9*8/81024/VS.DLRlcBurstTime_9
12126_9*8*1024/ 12124_9
E/// N/A
Huawei
eRAN L.Thrp.bits.DL.CAUser/L.Thrp.Time.DL.CAUser
6.0&8.0&11.0
NSN
N/A
Comments
4.6. VOLTE
It is assumed that statistically RRC SSR and S1 SSR for VoLTE is the same as for any
other type of
of service. The ERAB component considers initial setups of QCI 5 and
QCI1 ERABS, as it is assumed that both are needed to setup a voice over LTE call.
It also has to be noted that RRC, S1 and ERAB QCI5 need to be established only
when transition from idle to connected takes place while ERAB QCI1 is usualy
approach.
established when a new VoLTE call start which may question validity of this approach
Where RRC_SR:
Nb of RRC Messages " RRCConnectionSetupComplete"
RRCsuccessrate =
Nb of RRC Messages " RCConnectionRequest"
S1_SR
Nb of first messages recieved from MME after sending " Initial UE Message"
S1 _ SuccessRate =
Nb of UE Initial Messages sent to the MME
RRC SR
(RRC.ConnEstabSucc.Sum/ VS.RrcConnectionRequestWithoutRepetition )
ALU
S1 SR
LR14.1& 15.1 (S1SIG.ConnEstabAtt- VS.S1ConnectionEstablishmentFailure )/S1SIG.ConnEstabAtt
RAB SR
[(SAEB.EstabInitSuccNbr.QCI1+SAEB.EstabAddSuccNbr.QCI1)/(
SAEB.EstabInitAttNbr.QCI1+SAEB.EstabAddAttNbr.QCI1)] *
RRC SR
100* (pmRrcConnEstabSucc /( pmRrcConnEstabAtt-pmRrcConnEstabAttReatt))
S1 SR
(pmS1SigConnEstabSucc)/(pmS1SigConnEstabAtt)
E///
L13B&14B&15B
RAB SR
[(pmErabEstabSuccInitQci [1]+pmErabEstabSuccAddedQc[1])/
(pmErabEstabAttInitQci [1]+ pmErabEstabAttAddedQci[1])]*
[(pmErabEstabSuccInitQci[5]+pmErabEstabSuccAddedQci[5])/
(pmErabEstabAttInitQci[5]+ pmErabEstabAttAddedQci[5])]
RRC SR
(L.RRC.ConnReq.Succ.Emc + L.RRC.ConnReq.Succ.HighPri +
L.RRC.ConnReq.Succ.Mt + L.RRC.ConnReq.Succ.MoData +
L.RRC.ConnReq.Succ.DelayTol)/(L.RRC.ConnReq.Att.Emc +
L.RRC.ConnReq.Att.HighPri + L.RRC.ConnReq.Att.Mt + L.RRC.ConnReq.Att.MoData
Huawei
+ L.RRC.ConnReq.Att.DelayTol)
eRAN
6.0&8.0&11.0 S1 SR
L.S1Sig.ConnEst.Succ /L.S1Sig.ConnEst.Att)
RAB SR
( L.E-RAB.SuccEst.QCI.1 / L.E-RAB.AttEst.QCI.1 )*
(L.E-RAB.SuccEst.QCI.5 / L.E-RAB.AttEst.QCI.5)
RRC SR
(SIGN_CONN_ESTAB_COMP) /
(SIGN_CONN_ESTAB_ATT_MO_S+SIGN_CONN_ESTAB_ATT_MT+
SIGN_CONN_ESTAB_ATT_MO_D+SIGN_CONN_ESTAB_ATT_DEL_TOL+
SIGN_CONN_ESTAB_ATT_HIPRIO+SIGN_CONN_ESTAB_ATT_EMG)
S1 SR
NSN Not available
RL60&70&FL15
RAB SR
(EPS_BEARER_STP_COM_INI_QCI1 +EPS_BEAR_SET_COM_ADDIT_QCI1) /
(EPS_BEARER_STP_ATT_INI_QCI_1 +EPS_BEARER_STP_ATT_ADD_QCI_1)
RL 70, FL15A
[SIGN_CONN_ESTAB_COMP/
(SIGN_CONN_ESTAB_ATT_MO_S + SIGN_CONN_ESTAB_ATT_MT +
Comments
The E-RAB Setup Success Rate (VoIP) KPI indicates the E-RAB setup success rate of
Definition the voice over IP (VoIP) services in a cell or radio network.
The KPI describes the setup success ratio of the elementary E-RAB setup procedure
used to setup the E-RAB between MME and UE. It indicates the E-UTRAN
contribution to network accessibility for the end-user, not the whole end-to-end
service accessibility. This KPI can be used to evaluate the ERAB setup success rate of
the VoIP service in a cell or a cluster. This KPI is calculated based on the counters
Calculation rule (both the ERAB setup attempts (QCI1) and the successful ERAB setup (QCI1)
counters) measured at the eNodeB.
ERAB_Ini_SetupSuc_QCI1 + ERAB_Add_SetupSuc_QCI1
ERAB _ SR =
ERAB_Ini_SetupAtt_QCI1 + ERAB_Add_SetupAtt_QCI1
Huawei
eRAN L.E-RAB.SuccEst.QCI.1 / L.E-RAB.AttEst.QCI.1
6.0&8.0&11.0
(EPS_BEARER_STP_COM_INI_QCI1 +EPS_BEAR_SET_COM_ADDIT_QCI1) /
(EPS_BEARER_STP_ATT_INI_QCI_1 +EPS_BEARER_STP_ATT_ADD_QCI_1)
NSN
RL60&70&FL15 RL 70, FT-15A
[(ERAB_INI_SETUP_SUCC_QCI1+ ERAB_ADD_SETUP_SUCC_QCI1)/
(ERAB_INI_SETUP_ATT_QCI1+ ERAB_ADD_SETUP_ATT_QCI1)]
Comments
Ratio between the number of drop calls over the total number of normal connection releases
Definition
for VolTE .
This KPI describes the ratio of abnormally released (dropped) E-RABs for VolTE (QCI1) from
user perspective point of view.
This KPI can be used to evaluate the call drop rate of all services in a cell or a cluster.
Calculation rule
ERABAbnormalReleases_QCI1
DCR = x100%
ERABReleases_QCI1
100x
(VS.AbnormalERABReleasePerQCI_#0+VS.ERABReleasedDueToRadioLinkFailurePerQ
ALU CI_#0 + VS.OtherAbnormalERABReleasePerQCI_#0 )/
LR 14.1&15.1 (VS.NormalERABRelease_#0 + VS.AbnormalERABReleasePerQCI_#0+
VS.ERABReleasedDueToRadioLinkFailurePerQCI_#0 +
VS.OtherAbnormalERABReleasePerQCI_#0 )
RL60& RL70
(EPC_EPS_BEAR_REL_REQ_R_QCI1 + EPC_EPS_BEAR_REL_REQ_O_QCI1 +
ENB_EPS_BEAR_REL_REQ_R_QCI1 + ENB_EPS_BEAR_REL_REQ_T_QCI1 +
ENB_EPS_BEAR_REL_REQ_O_QCI1)/
([EPC_EPS_BEAR_REL_REQ_N_QCI1]+ [EPC_EPS_BEAR_REL_REQ_D_QCI1] +
EPC_EPS_BEAR_REL_REQ_R_QCI1 + EPC_EPS_BEAR_REL_REQ_O_QCI1 +
ENB_EPS_BEAR_REL_REQ_RD_QCI1 + ENB_EPS_BEAR_REL_REQ_N_QCI1 +
ENB_EPS_BEAR_REL_REQ_R_QCI1 + ENB_EPS_BEAR_REL_REQ_T_QCI1 +
ENB_EPS_BEAR_REL_REQ_O_QCI1)
FL-15A
100*(ERAB_REL_HO_PART_QCI1 + ERAB_REL_ENB_QCI1 -
ERAB_REL_ENB_RNL_INA_QCI1 - ERAB_REL_ENB_RNL_RED_QCI1 -
ERAB_REL_ENB_RNL_RRNA_QCI1)
/
(ERAB_REL_ENB_QCI1 + ERAB_REL_HO_PART_QCI1 +
EPC_EPS_BEAR_REL_REQ_N_QCI1 + EPC_EPS_BEAR_REL_REQ_D_QCI1 +
EPC_EPS_BEAR_REL_REQ_R_QCI1 + EPC_EPS_BEAR_REL_REQ_O_QCI1)
Comments
VS.NbVoIPBearersPerCellPerPlmn.Cum/ VS.NbVoIPBearersPerCellPerPlmn.NbEvt
13204
Remark1:
This counter counts the number of VoIP bearers per cell per PLMN
Remark2:
Alternative formula:
ALU VS.NbBearersPerCellPerQCIPerPlmn_0_Cum/VS.NbBearersPerCellPerQCIPerPlmn_0_NbEvt
LR14.1 & 15.1 13217_0_Cum/13217_0_NbEvt
Remark3:
In order to calculate the number of active UE’s with data in the buffer the following counters
should be used:
- 13215 - Number of active UEs in uplink per type of service
VS.NbActiveUEInULPerTypeService.0 (VoIP)
- 13216 - Number of active UEs in downlink per type of service
VS.NbActiveUEInDLPerTypeService.0 (VoIP)
pmErabQciLevSum/ pmErabLevSamp
E/// L14B&15B
L.Traffic.User.VoIP.Avg
Huawei
eRAN 7.0 Remark1:
&8.0&11.0 The number of UEs in RRC_CONNECTED mode performing services with QCI 1
Sum([SUM_SIMUL_ERAB_QCI_1])/ sum([DENOM_SUM_SIMUL_ERAB])
NSN
RL60&70&FL15 sum([M8006C45]) / sum([M8006C54)
Comments
4.6.5. INTER-
INTER-RAT HO SUCCESS RATE FOR SRVCC (LTE TO WCDMA)
WCDMA)
Definition
This KPI can be used to evaluate the inter-RAT handover success rate from LTE to WCDMA in a cell or
This KPI describes the success ratio for the inter RAT handover execution phase for SRVCC, where
successes are considered when the source eNB receives a UE CONTEXT RELEASE COMMAND
message from the MME after the UE is handed over from the E-UTRAN to a WCDMA network.
L14B
100* pmHoPrepSuccSrvcc / pmHoPrepAttSrvcc
E/// L14B&15B
L15B
100* pmHoExeSuccSrvcc / pmHoPrepAttSrvcc
Huawei
100* L.IRATHO.SRVCC.E2W.ExecSuccOut/ L.IRATHO.SRVCC.E2W.PrepAttOut
eRAN
6.0&8.0&11.0
Comments
4.6.6. INTER-
INTER-RAT HO SUCCESS RATE FOR SRVCC (LTE TO GSM)
GSM)
This KPI can be used to evaluate the inter-RAT handover success rate from LTE to GSM in a cell or a
Definition cluster for SRVCC.
This KPI describes the success ratio for the inter RAT handover execution phase for SRVCC, where
successes are considered when the source eNB receives a UE CONTEXT RELEASE COMMAND
message from the MME after the UE is handed over from the E-UTRAN to a GERAN.
Huawei
100* L.IRATHO.SRVCC.E2G.ExecSuccOut/ L.IRATHO.SRVCC.E2G.PrepAttOut
eRAN
6.0&8.0&11.0
Comments
5. REFERENCES
12
13
14
6. DOCUMENT HISTORY
V1.1 Maciej Urbanowicz (Editor) Section 3.1.9, Section 3.1.10, Section 3.1.11, Section 3.1.12 :
Sergiu Mihailov New traffic KPIs have been added in the document. New KPIs
Miruna Stanescu measure traffic at the PDCP layer, as opposed to traffic at MAC
Octavian Budurca layer, new counters measure only user data (no control information
and padding bits) ad are not impacted by pre-allocation.
Section 3.3.3, Section 3.3.4 : formulas for ALU and E// have been
corrected.
Section 3.3.5, Section 3.3.6 : New KPIs with aim to reflect load in the
network.
V2.0 Maciej Urbanowicz (Editor) Section 3.1.5 E// ackunknowledge traffic included
Augusto Del Cacho section 3.1.6 E// ackunknowledge traffic included
Section 3.1.7 E// new formula for L12B & L13B
Section 3.1.8 E// new formula for L12B & L13B
Section 3.2.1 KPI name changed, S1 SSR part inlcuded for ALU, E//
and Huawei. New formula for NSN RL50.
Section 3.2.3 E// new formula for L12B and L13B , NSN new formula
for RL50