• Author / Uploaded
• edydjunaedi_45760992

Citation preview

LTE RAN KPI FORMULA Document Number Release Date Version Version Date Document Owner Classification Control Status

: NQM/RNQ/Standard/2 : 5 July 2017 : 1.0 : 5 July 2017 : Network Quality Management : INTERNAL : Controlled

PT Telekomunikasi Seluler 2017

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 1 of 93

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 2 of 93

Contents 1.

INTRODUCTION ............................................................................................................................................. 5 1.1 1.2 1.3

2.

RRC SETUP SUCCESS RATE ............................................................................................................................. 6 2.1 2.2 2.3 2.4 2.5

3.

DEFINITION ....................................................................................................................................................29 GENERIC FORMULA .........................................................................................................................................29 SIGNALING FLOW ............................................................................................................................................30 KPI FORMULA ................................................................................................................................................31 KPI SIMULATION.............................................................................................................................................38

INTRA FREQUENCY HANDOVER SUCCESS RATE ........................................................................................... 38 6.1 6.2 6.3 6.4 6.5

7.

DEFINITION ....................................................................................................................................................18 GENERIC FORMULA .........................................................................................................................................19 SIGNALING FLOW ............................................................................................................................................19 KPI FORMULA ................................................................................................................................................20 KPI SIMULATION.............................................................................................................................................29

SDR – SERVICE DROP RATE .......................................................................................................................... 29 5.1 5.2 5.3 5.4 5.5

6.

DEFINITION ....................................................................................................................................................12 GENERIC FORMULA .........................................................................................................................................13 SIGNALING FLOW ............................................................................................................................................13 KPI FORMULA ................................................................................................................................................14 KPI SIMULATION.............................................................................................................................................18

CSSR (CALL SETUP SUCCESS RATE) ............................................................................................................... 18 4.1 4.2 4.3 4.4 4.5

5.

DEFINITION ......................................................................................................................................................6 GENERIC FORMULA ...........................................................................................................................................6 SIGNALING FLOW ..............................................................................................................................................6 KPI FORMULA ..................................................................................................................................................7 KPI SIMULATION.............................................................................................................................................12

E-RAB SETUP SUCCESS RATE ........................................................................................................................ 12 3.1 3.2 3.3 3.4 3.5

4.

OBJECTIVE .......................................................................................................................................................5 SCOPE.............................................................................................................................................................5 VERSION..........................................................................................................................................................5

DEFINITION ....................................................................................................................................................38 GENERIC FORMULA .........................................................................................................................................38 SIGNALING FLOW ............................................................................................................................................39 KPI FORMULA ................................................................................................................................................40 KPI SIMULATION.............................................................................................................................................43

CSFB SUCCESS RATE ..................................................................................................................................... 44 7.1 7.2 7.3

DEFINITION ....................................................................................................................................................44 GENERIC FORMULA .........................................................................................................................................44 SIGNALING FLOW ............................................................................................................................................44

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 3 of 93

7.4 7.5 8.

KPI FORMULA ................................................................................................................................................45 KPI SIMULATION.............................................................................................................................................47

3G CS FALLBACK SUCCESS RATE ................................................................................................................... 48 8.1 8.2 8.3 8.4 8.5

9.

DEFINITION ....................................................................................................................................................48 GENERIC FORMULA .........................................................................................................................................48 SIGNALING FLOW ............................................................................................................................................49 KPI FORMULA ................................................................................................................................................50 KPI SIMULATION.............................................................................................................................................53

USER DOWNLINK THROUGHPUT ................................................................................................................. 53 9.1 9.2 9.3 9.4 9.5

10. 10.1 10.2 10.3 10.4 10.5 11. 11.1 11.2 11.3 11.4 12. 12.1 12.2 12.3 12.4 12.5 13. 13.1 13.2 13.3 13.4 13.5 14. 14.1 14.2 14.3 14.4

DEFINITION ....................................................................................................................................................53 GENERIC FORMULA .........................................................................................................................................53 SIGNALING FLOW ............................................................................................................................................53 KPI FORMULA ................................................................................................................................................54 KPI SIMULATION.............................................................................................................................................57 CELL DOWNLINK THROUGHPUT .............................................................................................................. 58 DEFINITION ....................................................................................................................................................58 GENERIC FORMULA .........................................................................................................................................58 SIGNALING FLOW ............................................................................................................................................58 KPI FORMULA ................................................................................................................................................58 KPI SIMULATION.............................................................................................................................................60 CELL DOWNLINK DIMENSIONING THROUGHPUT ..................................................................................... 61 DEFINITION ....................................................................................................................................................61 GENERIC FORMULA .........................................................................................................................................61 SIGNALING FLOW ............................................................................................................................................61 KPI FORMULA ................................................................................................................................................61 USER UPLINK THROUGHPUT.................................................................................................................... 63 DEFINITION ....................................................................................................................................................63 GENERIC FORMULA .........................................................................................................................................63 SIGNALING FLOW ............................................................................................................................................63 KPI FORMULA ................................................................................................................................................63 KPI SIMULATION.............................................................................................................................................66 CELL UPLINK THROUGHPUT ..................................................................................................................... 67 DEFINITION ....................................................................................................................................................67 GENERIC FORMULA .........................................................................................................................................67 SIGNALING FLOW ............................................................................................................................................67 KPI FORMULA ................................................................................................................................................67 KPI SIMULATION.............................................................................................................................................69 CELL UPLINK DIMENSIONING THROUGHPUT ........................................................................................... 70 DEFINITION ....................................................................................................................................................70 GENERIC FORMULA .........................................................................................................................................70 SIGNALING FLOW ............................................................................................................................................70 KPI FORMULA ................................................................................................................................................70

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 4 of 93

15. 15.1 15.2 15.3 15.4 15.5 16. 16.1 16.2 16.3 16.4 16.5 17. 17.1 17.2 17.3 17.4 17.5 18. 18.1 18.2 18.3 18.4 18.5 19. 19.1 19.2 19.3 19.4 19.5 20. 20.1 20.2 20.3 20.4

DL TRAFFIC VOLUME ............................................................................................................................... 72 DEFINITION ....................................................................................................................................................72 GENERIC FORMULA .........................................................................................................................................72 SIGNALING FLOW ............................................................................................................................................72 KPI FORMULA ................................................................................................................................................72 KPI SIMULATION.............................................................................................................................................74 UL TRAFFIC VOLUME ............................................................................................................................... 75 DEFINITION ....................................................................................................................................................75 GENERIC FORMULA .........................................................................................................................................75 SIGNALING FLOW ............................................................................................................................................75 KPI FORMULA ................................................................................................................................................75 KPI SIMULATION.............................................................................................................................................77 DL PRB UTILIZATION ................................................................................................................................ 78 DEFINITION ....................................................................................................................................................78 GENERIC FORMULA .........................................................................................................................................78 SIGNALING FLOW ............................................................................................................................................78 KPI FORMULA ................................................................................................................................................78 KPI SIMULATION.............................................................................................................................................80 UL PRB UTILIZATION ................................................................................................................................ 80 DEFINITION ....................................................................................................................................................80 GENERIC FORMULA .........................................................................................................................................81 SIGNALING FLOW ............................................................................................................................................81 KPI FORMULA ................................................................................................................................................81 KPI SIMULATION.............................................................................................................................................83 MAXIMUM RRC CONNECTED USERS........................................................................................................ 83 DEFINITION ....................................................................................................................................................83 GENERIC FORMULA .........................................................................................................................................83 SIGNALING FLOW ............................................................................................................................................83 KPI FORMULA ................................................................................................................................................84 KPI SIMULATION.............................................................................................................................................85 AVERAGE RRC CONNECTED USERS .......................................................................................................... 86 DEFINITION ....................................................................................................................................................86 GENERIC FORMULA .........................................................................................................................................86 SIGNALING FLOW ............................................................................................................................................86 KPI FORMULA ................................................................................................................................................86

APPENDIX ............................................................................................................................................................ 88 A.

MINUTES OF MEETING KPI STANDARDIZATION 4G (21 JUNE 2017) ............................................................................88

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 5 of 93

1.

Introduction

1.1

Objective

This document describes all the description and formula for Key Performance Indicator (KPI), performance indicator (PI) of all LTE RAN vendor’s equipment (Huawei, Nokia, ZTE & Ericsson) to be used for RAN Network Planning, Roll-Out, Operation, Optimization and Traffic engineering in all Telkomsel department. This Document also provide a reference guideline for standard definition of KPI used by Telkomsel and must be followed by all stakeholder for every project that have correlation with performance. Formula reference that used in this document is user perceive behavior mapping into specific OSS counters, represented in formula calculation for accessibility, retainability, integrity & Mobility

1.2

Scope

This Document is used as LTE RAN performance reference for all Telkomsel project include achievement calculator for all department/division such as a.

Network Performance Improvement (NPI) KPI Baseline & target

b.

Swap & Modernization KPI baseline & Target

c.

New Site integration QC Acceptance

d.

Network Audit & Benchmarking

e.

Management KPI Achievement

f.

Traffic analysis & engineering

g.

Customer complaint performance analysis

h.

Management KPI Dashboard performance reference

i.

Other performance reference

1.3

Version

This document is defined based on following Vendor Software release: •

Nokia: LTE16

•

Ericsson: L16

•

Huawei: eRAN11.1

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 6 of 93

•

ZTE: LR15

2.

RRC Setup Success Rate

2.1

Definition

This KPI shows the setup success ratio for the RRC connection establishment elementary procedure, used to set up a radio connection from a UE to an eNB (involves SRB1 establishment). Note: -

2.2

Include all RRC causes: MO data, MT, high Priority, MO signaling, delay tolerant and emergency

Generic Formula

𝑅𝑅𝐶 𝑆𝑒𝑡𝑢𝑝 𝑆𝑅 = 100% ×

2.3

Signaling Flow

#𝑅𝑅𝐶_𝑆𝑢𝑐𝑐𝑒𝑠𝑠 #𝑅𝑅𝐶_𝐴𝑡𝑡𝑒𝑚𝑝𝑡𝑠 − #𝑅𝑅𝐶_𝑅𝑒𝑎𝑡𝑡𝑒𝑚𝑝𝑡𝑠

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 7 of 93

2.4

KPI Formula

2.4.1

Huawei KPI Name RRC Setup SR

Counter Name L.RRC.ConnReq.Att.Emc

L.RRC.ConnReq.Att.HighPri

L.RRC.ConnReq.Att.Mt

L.RRC.ConnReq.Att.MoSig

L.RRC.ConnReq.Att.MoData

L.RRC.ConnReq.Att.DelayTol

L.RRC.ConnReq.Succ.Emc L.RRC.ConnReq.Succ.HighPri

Formula 100*(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.Succ.MoSig) / (L.RRC.ConnReq.Att.Emc + L.RRC.ConnReq.Att.HighPri + L.RRC.ConnReq.Att.Mt + L.RRC.ConnReq.Att.MoData + L.RRC.ConnReq.Att.DelayTol + L.RRC.ConnReq.Att.MoSig)

Counter Description Number of RRC connection setup attempts with a cause value of emergency performed by UEs in a cell (retransmission excluded) Number of RRC connection setup attempts with a cause value of highPriorityAccess performed by UEs in a cell (retransmission excluded) Number of RRC connection setup attempts with a cause value of mt-Access performed by UEs in a cell (retransmission excluded) Number of RRC connection setup attempts with a cause value of mo-Signalling performed by UEs in a cell (retransmission excluded) Number of RRC connection setup attempts with a cause value of mo-Data performed by UEs in a cell (retransmission excluded) Number of RRC connection setup attempts with a cause value of delayTolerantAccess-v1020 performed by UEs in a cell (retransmission excluded) Number of RRC Connection Setup Complete messages with a cause value of emergency received from UEs in a cell Number of RRC Connection Setup Complete messages with a cause value of highPriorityAccess received from UEs in a cell

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 8 of 93

Counter Name L.RRC.ConnReq.Succ.Mt

Counter Description Number of RRC Connection Setup Complete messages with a cause value of mt-Access received from UEs in a cell

L.RRC.ConnReq.Succ.MoSig

Number of RRC Connection Setup Complete messages with a cause value of mo-signalling received from UEs in a cell

L.RRC.ConnReq.Succ.MoData

Number of RRC Connection Setup Complete messages with a cause value of mo-Data received from UEs in a cell

L.RRC.ConnReq.Succ.DelayTol

Number of RRC Connection Setup Complete messages with a cause value of delayTolerantAccess-v1020 received from UEs in a cell

2.4.2

Nokia KPI Name Formula RRC Setup Success 100*(SIGN_CONN_ESTAB_COMP) Rate / (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)

Counter ID

Counter Name

M8013C17

SIGN_CONN_ESTAB_ATT_MO_S

M8013C18

SIGN_CONN_ESTAB_ATT_MT

M8013C19

SIGN_CONN_ESTAB_ATT_MO_D

M8013C21

SIGN_CONN_ESTAB_ATT_EMG

M8013C31

SIGN_CONN_ESTAB_ATT_HIPRIO

M8013C34

SIGN_CONN_ESTAB_ATT_DEL_TOL

Counter Description The number of Signaling Connection Establishment attempts for mobile originated signaling. From UE's point of view, the transition from ECM-IDLE to ECMCONNECTED has started. The number of Signaling Connection Establishment attempts for mobile terminated connections. From UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED is started. The number of Signaling Connection Establishment attempts for mobile originated data connections. From UE's point of view, the transition from ECMIDLE to ECM-CONNECTED is started. Number of Signaling Connection Establishment attempts for emergency calls. The number of Signaling Connection Establishment attempts for highPriorityAccess connections. From UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED is started. The number of Signaling Connection Establishment attempts for delayTolerantAccess connections. From

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 9 of 93

Counter ID

Counter Name

Counter Description UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED is started.

M8013C5

SIGN_CONN_ESTAB_COMP

ZTE KPI Name RRC Setup SR

This measurement provides the number of successful RRC Connection Setups.

2.4.3

Counter ID

Formula 100*(C373200000+C373200004+C373200008 +C373200012+C373200016+C373200120) / (C373200084+C373200085+C373200086 +C373200087+C373200088+C373200124) 100*(RRC.ConnEstabSucc.CauseMtAccess + RRC.ConnEstabSucc.CauseMoSignalling + RRC.ConnEstabSucc.CauseMoData + RRC.ConnEstabSucc.CauseHighPriorityAccess + RRC.ConnEstabSucc.CauseEmergency + RRC.ConnEstabSucc.CauseDelayTolerantAccess) / ( RRC.ConnEstabAtt.CauseMtAccess + RRC.ConnEstabAtt.CauseMoSignalling + RRC.ConnEstabAtt.CauseMoData + RRC.ConnEstabAtt.CauseHighPriorityAccess + RRC.ConnEstabAtt.CauseEmergency + RRC.ConnEstabAtt.CauseDelayTolerantAccess)

Counter Name

C373200000

RRC.ConnEstabSucc.CauseMtAccess

C373200004

RRC.ConnEstabSucc.CauseMoSignalling

Counter Description The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment.The counter is used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is mt-Access. The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment.The counter is used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is mo-Signalling.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 10 of 93

Counter ID

Counter Name

C373200008

RRC.ConnEstabSucc.CauseMoData

C373200012

RRC.ConnEstabSucc.CauseHighPriorityAccess

C373200016

RRC.ConnEstabSucc.CauseEmergency

C373200084

RRC.ConnEstabAtt.CauseMtAccess

C373200085

RRC.ConnEstabAtt.CauseMoSignalling

C373200086

RRC.ConnEstabAtt.CauseMoData

C373200087

RRC.ConnEstabAtt.CauseHighPriorityAccess

C373200088

RRC.ConnEstabAtt.CauseEmergency

Counter Description The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment.The counter is used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is mo-Data. The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment.The counter is used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is highPriorityAccess. The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment.The counter is used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is emergency. The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is mt-access. Each RRCConnectionRequest message received is added to the counter. The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is mo-Signalling. Each RRCConnectionRequest message received is added to the counter. The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is mo-Data. Each RRCConnectionRequest message received is added to the counter. The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is highPriorityAccess. Each RRCConnectionRequest message received is added to the counter. The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is emergency. Each RRCConnectionRequest message received is added to the counter.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 11 of 93

Counter ID

Counter Name

Counter Description

C373200120

RRC.ConnEstabSucc.CauseDelayTolerantAccess

C373200124

RRC.ConnEstabAtt.CauseDelayTolerantAccess

The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment.The counter is used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is delayTolerantAccess. The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is delayTolerantAccess. Each RRCConnectionRequest message received is added to the counter.

2.4.4

Ericsson

KPI Name RRC Setup SR

Formula 100*(pmRrcConnEstabSucc/(pmRrcConnEstabAttpmRrcConnEstabAttReatt))

Counter Name pmRrcConnEstabSucc pmRrcConnEstabAtt pmRrcConnEstabAttReAtt

Description The total number of successful RRC Connection Establishments. The total number of RRC Connection Request attempts. The total number of RRC Connection Request attempts that are considered as re-attempts.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 12 of 93

2.5

KPI Simulation

3.

E-RAB Setup Success Rate

3.1

Definition

The E-RAB Setup Success Rate is defined as the ratio of successful call setups, divided by the total number of call setup attempts for the initial context setup and the added bearer. Note: The formula is considering Initial E-RAB Establishment and Added E-RAB establishment. -

The Initial Context Setup procedure is triggered by the MME by sending the INITIAL CONTEXT SETUP REQUEST. This message includes information regarding the default E-RAB to set up

-

The added bearer is established if the user requires different QoS of that offered by the initial bearer, or if the user requires connectivity to different PDN. Added bearers are configured to run in parallel to the existing initial bearer

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 13 of 93

3.2

Generic Formula

𝐸𝑅𝐴𝐵 𝑆𝑒𝑡𝑢𝑝 𝑆𝑅(%) = 100% 𝑥 3.3

Signaling Flow

Initial E-RAB Setup:

Additional E-RAB setup:

#𝐸𝑅𝐴𝐵_𝑆𝑢𝑐𝑐𝑒𝑠𝑠 #𝐸𝑅𝐴𝐵_𝐴𝑡𝑡𝑒𝑚𝑝𝑡𝑠

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 14 of 93

3.4

KPI Formula

3.4.1

Huawei KPI Name E-RAB Setup SR

Formula (L.E-RAB.SuccEst/L.E-RAB.AttEst)*100

Counter Name L.E-RAB.SuccEst

Counter Description Total number of successful E-RAB setups initiated by UEs in a cell

L.E-RAB.AttEst

Total number of E-RAB setup attempts initiated by UEs in a cell

3.4.2

Nokia KPI Name Formula E-RAB Setup SR 100*(ERAB_INI_SETUP_SUCC_QCI1 + ERAB_ADD_SETUP_SUCC_QCI1 + ERAB_INI_SETUP_SUCC_QCI2 + ERAB_ADD_SETUP_SUCC_QCI2 + ERAB_INI_SETUP_SUCC_QCI3 + ERAB_ADD_SETUP_SUCC_QCI3 + ERAB_INI_SETUP_SUCC_QCI4 + ERAB_ADD_SETUP_SUCC_QCI4 + ERAB_INI_SETUP_SUCC_QCI5 + ERAB_ADD_SETUP_SUCC_QCI5 + ERAB_INI_SETUP_SUCC_QCI6 + ERAB_ADD_SETUP_SUCC_QCI6 + ERAB_INI_SETUP_SUCC_QCI7 + ERAB_ADD_SETUP_SUCC_QCI7 + ERAB_INI_SETUP_SUCC_QCI8 + ERAB_ADD_SETUP_SUCC_QCI8 + ERAB_INI_SETUP_SUCC_QCI9 + ERAB_ADD_SETUP_SUCC_QCI9) / (ERAB_INI_SETUP_ATT_QCI1 + ERAB_ADD_SETUP_ATT_QCI1 + ERAB_INI_SETUP_ATT_QCI2 + ERAB_ADD_SETUP_ATT_QCI2 + ERAB_INI_SETUP_ATT_QCI3 + ERAB_ADD_SETUP_ATT_QCI3 + ERAB_INI_SETUP_ATT_QCI4 + ERAB_ADD_SETUP_ATT_QCI4 + ERAB_INI_SETUP_ATT_QCI5 + ERAB_ADD_SETUP_ATT_QCI5 + ERAB_INI_SETUP_ATT_QCI6 + ERAB_ADD_SETUP_ATT_QCI6 + ERAB_INI_SETUP_ATT_QCI7 + ERAB_ADD_SETUP_ATT_QCI7 + ERAB_INI_SETUP_ATT_QCI8 + ERAB_ADD_SETUP_ATT_QCI8 + ERAB_INI_SETUP_ATT_QCI9 + ERAB_ADD_SETUP_ATT_QCI9)

Counter ID

Counter Name

Counter Description

M8006C188

ERAB_INI_SETUP_ATT_QCI1

This measurement provides the number of setup attempts for initial E-RABs of QCI1.

M8006C189

ERAB_INI_SETUP_ATT_QCI2

This measurement provides the number of setup attempts for initial E-RABs of QCI2.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 15 of 93

Counter ID

Counter Name

Counter Description

M8006C190

ERAB_INI_SETUP_ATT_QCI3

This measurement provides the number of setup attempts for initial E-RABs of QCI3.

M8006C191

ERAB_INI_SETUP_ATT_QCI4

This measurement provides the number of setup attempts for initial E-RABs of QCI4.

M8006C192

ERAB_INI_SETUP_ATT_QCI5

M8006C193

ERAB_INI_SETUP_ATT_QCI6

This measurement provides the number of setup attempts for initial E-RABs of QCI5. This measurement provides the number of setup attempts for initial E-RABs of QCI6.

M8006C194

ERAB_INI_SETUP_ATT_QCI7

This measurement provides the number of setup attempts for initial E-RABs of QCI7.

M8006C195

ERAB_INI_SETUP_ATT_QCI8

This measurement provides the number of setup attempts for initial E-RABs of QCI8.

M8006C196

ERAB_INI_SETUP_ATT_QCI9

This measurement provides the number of setup attempts for initial E-RABs of QCI9.

M8006C197

ERAB_ADD_SETUP_ATT_QCI1

This measurement provides the number of setup attempts for additional E-RABs of QCI1.

M8006C198

ERAB_ADD_SETUP_ATT_QCI2

This measurement provides the number of setup attempts for additional E-RABs of QCI2.

M8006C199

ERAB_ADD_SETUP_ATT_QCI3

This measurement provides the number of setup attempts for additional E-RABs of QCI3.

M8006C200

ERAB_ADD_SETUP_ATT_QCI4

This measurement provides the number of setup attempts for additional E-RABs of QCI4.

M8006C201

ERAB_ADD_SETUP_ATT_QCI5

This measurement provides the number of setup attempts for additional E-RABs of QCI5.

M8006C202

ERAB_ADD_SETUP_ATT_QCI6

This measurement provides the number of setup attempts for additional E-RABs of QCI6.

M8006C203

ERAB_ADD_SETUP_ATT_QCI7

This measurement provides the number of setup attempts for additional E-RABs of QCI7.

M8006C204

ERAB_ADD_SETUP_ATT_QCI8

This measurement provides the number of setup attempts for additional E-RABs of QCI8.

M8006C205

ERAB_ADD_SETUP_ATT_QCI9

This measurement provides the number of setup attempts for additional E-RABs of QCI9.

M8006C206

ERAB_INI_SETUP_SUCC_QCI1

This measurement provides the number of successfully established initial E-RABs of QCI1.

M8006C207

ERAB_INI_SETUP_SUCC_QCI2

This measurement provides the number of successfully established initial E-RABs of QCI2.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 16 of 93

Counter ID

Counter Name

Counter Description

M8006C208

ERAB_INI_SETUP_SUCC_QCI3

This measurement provides the number of successfully established initial E-RABs of QCI3.

M8006C209

ERAB_INI_SETUP_SUCC_QCI4

This measurement provides the number of successfully established initial E-RABs of QCI4.

M8006C210

ERAB_INI_SETUP_SUCC_QCI5

This measurement provides the number of successfully established initial E-RABs of QCI5.

M8006C211

ERAB_INI_SETUP_SUCC_QCI6

This measurement provides the number of successfully established initial E-RABs of QCI6.

M8006C212

ERAB_INI_SETUP_SUCC_QCI7

This measurement provides the number of successfully established initial E-RABs of QCI7.

M8006C213

ERAB_INI_SETUP_SUCC_QCI8

This measurement provides the number of successfully established initial E-RABs of QCI8.

M8006C214

ERAB_INI_SETUP_SUCC_QCI9

This measurement provides the number of successfully established initial E-RABs of QCI9.

M8006C215

ERAB_ADD_SETUP_SUCC_QCI1

This measurement provides the number of successfully established additional E-RABs of QCI1.

M8006C216

ERAB_ADD_SETUP_SUCC_QCI2

This measurement provides the number of successfully established additional E-RABs of QCI2.

M8006C217

ERAB_ADD_SETUP_SUCC_QCI3

This measurement provides the number of successfully established additional E-RABs of QCI3.

M8006C218

ERAB_ADD_SETUP_SUCC_QCI4

This measurement provides the number of successfully established additional E-RABs of QCI4.

M8006C219

ERAB_ADD_SETUP_SUCC_QCI5

This measurement provides the number of successfully established additional E-RABs of QCI5.

M8006C220

ERAB_ADD_SETUP_SUCC_QCI6

This measurement provides the number of successfully established additional E-RABs of QCI6.

M8006C221

ERAB_ADD_SETUP_SUCC_QCI7

This measurement provides the number of successfully established additional E-RABs of QCI7.

M8006C222

ERAB_ADD_SETUP_SUCC_QCI8

This measurement provides the number of successfully established additional E-RABs of QCI8.

M8006C223

ERAB_ADD_SETUP_SUCC_QCI9

This measurement provides the number of successfully established additional E-RABs of QCI9.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 17 of 93

3.4.3

ZTE KPI Name E-RAB Setup SR

Formula 100*(C373505473+C373505481) / (C373505472+C373505480) 100*(ERAB.EstabInitSuccNbr + ERAB.EstabAddSuccNbr) / (ERAB.EstabInitAttNbr + ERAB.EstabAddAttNbr)

Counter ID

Counter Name

C373505472

ERAB.EstabInitAttNbr

C373505473

ERAB.EstabInitSuccNbr

C373505480

ERAB.EstabAddAttNbr

C373505481

ERAB.EstabAddSuccNbr

3.4.4

Counter Description On receipt by the eNodeB of an INITIAL CONTEXT SETUP REQUEST message, each requested E-RAB in the message is added to the counter. On transmission by the eNodeB to MME of an INITIAL CONTEXT SETUP RESPONSE message, in which each ERAB successfully established is added to the counter. On receipt by the eNodeB of an E-RAB SETUP REQUEST message, each requested E-RAB in the message is added to the counter. On transmission by the eNodeB to MME of an E-RAB SETUP RESPONSE message, in which each E-RAB successfully established is added to the counter.

Ericsson

KPI Name E-RAB Setup SR

Counter Name pmErabEstabSuccInit

pmErabEstabSuccAdded pmErabEstabAttInit

pmErabEstabAttAdded

Formula 100 * (pmErabEstabSuccInit+pmErabEstabSuccAdded) /(pmErabEstabAttInit+pmErabEstabAttAdded) Description The total number of successful initial E-RAB Establishments. Initial ERABs are all E-RABs present in the S1 message Initial Context Setup Request. The total number of successfully added E-RABs. Added E-RABs are all E-RABs present in S1 message E-RAB Setup Request. The total number of initial E-RAB Establishment attempts. Initial ERABs are all E-RABs present in the S1 message Initial Context Setup Request. The total number of added E-RAB Establishment attempts. Added ERABs are all E-RABs present in S1 message E-RAB Setup Request.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 18 of 93

3.5

KPI Simulation

4.

CSSR (Call Setup Success Rate)

4.1

Definition

The Call Setup Success Rate (CCSR) or Session Setup Success Rate (SSSR) is defined as the ratio of successful session setups, divided by the total number of session setup attempts. Note: The CSSR KPI consists of three KPI: 1. RRC Setup Success Rate 2. E-RAB Init and Added Success Rate 3. S1 Signaling Success Rate

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 19 of 93

4.2

Generic Formula 𝐶𝑆𝑆𝑅[%] = 100% ×

4.3

Signaling Flow

#𝑆𝑢𝑐𝑐𝑒𝑠𝑠𝑓𝑢𝑙 𝑆𝑒𝑠𝑠𝑖𝑜𝑛 𝑆𝑒𝑡𝑢𝑝𝑠 #𝑆𝑒𝑠𝑠𝑖𝑜𝑛 𝐴𝑡𝑡𝑒𝑚𝑝𝑡𝑠

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 20 of 93

4.4 4.4.1

KPI Formula Huawei KPI Name

CSSR

Formula 100*(L.RRC.ConnReq.Succ.Emc + L.RRC.ConnReq.Succ.HighPri + L.RRC.ConnReq.Succ.Mt + L.RRC.ConnRe q.Succ.MoData + L.RRC.ConnReq.Succ.DelayTol + L.RRC.ConnReq.Succ.MoSig) / (L.RRC.ConnReq.Att.Emc + L.RRC.ConnReq.Att.HighPri + L.RRC.ConnRe q.Att.Mt + L.RRC.ConnReq.Att.MoData + L.RRC.ConnReq.Att.DelayTol + L.RRC.ConnReq.Att.MoSig) * (L.E- RAB.SuccEst/L.E-RAB.AttEst) * (L.S1Sig.ConnEst.Succ/ L.S1Sig.ConnEst.Att)

Counter Name L.RRC.ConnReq.Succ.Emc

Counter Description Number of RRC Connection Setup Complete messages with a cause value of emergency received from UEs in a cell

L.RRC.ConnReq.Succ.HighPri

Number of RRC Connection Setup Complete messages with a cause value of highPriorityAccess received from UEs in a cell

L.RRC.ConnReq.Succ.Mt

Number of RRC Connection Setup Complete messages with a cause value of mt-Access received from UEs in a cell Number of RRC Connection Setup Complete messages with a cause value of mo-Data received from UEs in a cell

L.RRC.ConnReq.Succ.MoData L.RRC.ConnReq.Succ.DelayTol

L.RRC.ConnReq.Succ.MoSig L.RRC.ConnReq.Att.Emc

L.RRC.ConnReq.Att.HighPri

Number of RRC Connection Setup Complete messages with a cause value of delayTolerantAccess-v1020 received from UEs in a cell Number of RRC Connection Setup Complete messages with a cause value of mo-signalling received from UEs in a cell Number of RRC connection setup attempts with a cause value of emergency performed by UEs in a cell (retransmission excluded) Number of RRC connection setup attempts with a cause value of highPriorityAccess performed by UEs in a cell (retransmission excluded)

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 21 of 93

Counter Name L.RRC.ConnReq.Att.Mt

L.RRC.ConnReq.Att.MoData

L.RRC.ConnReq.Att.DelayTol

L.RRC.ConnReq.Att.MoSig

L.E-RAB.SuccEst

Counter Description Number of RRC connection setup attempts with a cause value of mt-Access performed by UEs in a cell (retransmission excluded) Number of RRC connection setup attempts with a cause value of mo-Data performed by UEs in a cell (retransmission excluded) Number of RRC connection setup attempts with a cause value of delayTolerantAccess-v1020 performed by UEs in a cell (retransmission excluded) Number of RRC connection setup attempts with a cause value of mo-Signalling performed by UEs in a cell (retransmission excluded) Total number of successful E-RAB setups initiated by UEs in a cell

L.E-RAB.AttEst

Total number of E-RAB setup attempts initiated by UEs in a cell

L.S1Sig.ConnEst.Succ

Number of successful UE-related signaling connection setups over the S1 interface

L.S1Sig.ConnEst.Att

Number of UE-related signaling connection setup attempts over the S1 interface

4.4.2 CSSR

Nokia KPI Name

Formula 100*(SIGN_CONN_ESTAB_COMP) * (S1_SIGN_CONN_ESTAB_SUCC_UE) * (ERAB_INI_SETUP_SUCC_QCI1 + ERAB_ADD_SETUP_SUCC_QCI1 + ERAB_INI_SETUP_SUCC_QCI2 + ERAB_ADD_SETUP_SUCC_QCI2 + ERAB_INI_SETUP_SUCC_QCI3 + ERAB_ADD_SETUP_SUCC_QCI3 + ERAB_INI_SETUP_SUCC_QCI4 + ERAB_ADD_SETUP_SUCC_QCI4 + ERAB_INI_SETUP_SUCC_QCI5 + ERAB_ADD_SETUP_SUCC_QCI5 + ERAB_INI_SETUP_SUCC_QCI6 + ERAB_ADD_SETUP_SUCC_QCI6 + ERAB_INI_SETUP_SUCC_QCI7 + ERAB_ADD_SETUP_SUCC_QCI7 + ERAB_INI_SETUP_SUCC_QCI8 + ERAB_ADD_SETUP_SUCC_QCI8 + ERAB_INI_SETUP_SUCC_QCI9 + ERAB_ADD_SETUP_SUCC_QCI9) / ((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_SIGN_CONN_ESTAB_ATT_UE) *

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 22 of 93

KPI Name

Counter ID

Formula (ERAB_INI_SETUP_ATT_QCI1 + ERAB_ADD_SETUP_ATT_QCI1 + ERAB_INI_SETUP_ATT_QCI2 + ERAB_ADD_SETUP_ATT_QCI2 + ERAB_INI_SETUP_ATT_QCI3 + ERAB_ADD_SETUP_ATT_QCI3 + ERAB_INI_SETUP_ATT_QCI4 + ERAB_ADD_SETUP_ATT_QCI4 + ERAB_INI_SETUP_ATT_QCI5 + ERAB_ADD_SETUP_ATT_QCI5 + ERAB_INI_SETUP_ATT_QCI6 + ERAB_ADD_SETUP_ATT_QCI6 + ERAB_INI_SETUP_ATT_QCI7 + ERAB_ADD_SETUP_ATT_QCI7 + ERAB_INI_SETUP_ATT_QCI8 + ERAB_ADD_SETUP_ATT_QCI8 + ERAB_INI_SETUP_ATT_QCI9 + ERAB_ADD_SETUP_ATT_QCI9))

Counter Name

Counter Description

M8006C188

ERAB_INI_SETUP_ATT_QCI1

This measurement provides the number of setup attempts for initial E-RABs of QCI1.

M8006C189

ERAB_INI_SETUP_ATT_QCI2

This measurement provides the number of setup attempts for initial E-RABs of QCI2.

M8006C190

ERAB_INI_SETUP_ATT_QCI3

This measurement provides the number of setup attempts for initial E-RABs of QCI3.

M8006C191

ERAB_INI_SETUP_ATT_QCI4

This measurement provides the number of setup attempts for initial E-RABs of QCI4.

M8006C192

ERAB_INI_SETUP_ATT_QCI5

M8006C193

ERAB_INI_SETUP_ATT_QCI6

This measurement provides the number of setup attempts for initial E-RABs of QCI5. This measurement provides the number of setup attempts for initial E-RABs of QCI6.

M8006C194

ERAB_INI_SETUP_ATT_QCI7

This measurement provides the number of setup attempts for initial E-RABs of QCI7.

M8006C195

ERAB_INI_SETUP_ATT_QCI8

This measurement provides the number of setup attempts for initial E-RABs of QCI8.

M8006C196

ERAB_INI_SETUP_ATT_QCI9

This measurement provides the number of setup attempts for initial E-RABs of QCI9.

M8006C197

ERAB_ADD_SETUP_ATT_QCI1

This measurement provides the number of setup attempts for additional E-RABs of QCI1.

M8006C198

ERAB_ADD_SETUP_ATT_QCI2

This measurement provides the number of setup attempts for additional E-RABs of QCI2.

M8006C199

ERAB_ADD_SETUP_ATT_QCI3

This measurement provides the number of setup attempts for additional E-RABs of QCI3.

M8006C200

ERAB_ADD_SETUP_ATT_QCI4

This measurement provides the number of setup attempts for additional E-RABs of QCI4.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 23 of 93

Counter ID

Counter Name

Counter Description

M8006C201

ERAB_ADD_SETUP_ATT_QCI5

This measurement provides the number of setup attempts for additional E-RABs of QCI5.

M8006C202

ERAB_ADD_SETUP_ATT_QCI6

This measurement provides the number of setup attempts for additional E-RABs of QCI6.

M8006C203

ERAB_ADD_SETUP_ATT_QCI7

This measurement provides the number of setup attempts for additional E-RABs of QCI7.

M8006C204

ERAB_ADD_SETUP_ATT_QCI8

This measurement provides the number of setup attempts for additional E-RABs of QCI8.

M8006C205

ERAB_ADD_SETUP_ATT_QCI9

This measurement provides the number of setup attempts for additional E-RABs of QCI9.

M8006C206

ERAB_INI_SETUP_SUCC_QCI1

This measurement provides the number of successfully established initial E-RABs of QCI1.

M8006C207

ERAB_INI_SETUP_SUCC_QCI2

This measurement provides the number of successfully established initial E-RABs of QCI2.

M8006C208

ERAB_INI_SETUP_SUCC_QCI3

This measurement provides the number of successfully established initial E-RABs of QCI3.

M8006C209

ERAB_INI_SETUP_SUCC_QCI4

This measurement provides the number of successfully established initial E-RABs of QCI4.

M8006C210

ERAB_INI_SETUP_SUCC_QCI5

This measurement provides the number of successfully established initial E-RABs of QCI5.

M8006C211

ERAB_INI_SETUP_SUCC_QCI6

This measurement provides the number of successfully established initial E-RABs of QCI6.

M8006C212

ERAB_INI_SETUP_SUCC_QCI7

This measurement provides the number of successfully established initial E-RABs of QCI7.

M8006C213

ERAB_INI_SETUP_SUCC_QCI8

This measurement provides the number of successfully established initial E-RABs of QCI8.

M8006C214

ERAB_INI_SETUP_SUCC_QCI9

This measurement provides the number of successfully established initial E-RABs of QCI9.

M8006C215

ERAB_ADD_SETUP_SUCC_QCI1

This measurement provides the number of successfully established additional E-RABs of QCI1.

M8006C216

ERAB_ADD_SETUP_SUCC_QCI2

This measurement provides the number of successfully established additional E-RABs of QCI2.

M8006C217

ERAB_ADD_SETUP_SUCC_QCI3

This measurement provides the number of successfully established additional E-RABs of QCI3.

M8006C218

ERAB_ADD_SETUP_SUCC_QCI4

This measurement provides the number of successfully established additional E-RABs of QCI4.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 24 of 93

Counter ID

Counter Name

Counter Description

M8006C219

ERAB_ADD_SETUP_SUCC_QCI5

This measurement provides the number of successfully established additional E-RABs of QCI5.

M8006C220

ERAB_ADD_SETUP_SUCC_QCI6

This measurement provides the number of successfully established additional E-RABs of QCI6.

M8006C221

ERAB_ADD_SETUP_SUCC_QCI7

This measurement provides the number of successfully established additional E-RABs of QCI7.

M8006C222

ERAB_ADD_SETUP_SUCC_QCI8

This measurement provides the number of successfully established additional E-RABs of QCI8.

M8006C223

ERAB_ADD_SETUP_SUCC_QCI9

This measurement provides the number of successfully established additional E-RABs of QCI9.

M8013C17

SIGN_CONN_ESTAB_ATT_MO_S

M8013C18

SIGN_CONN_ESTAB_ATT_MT

M8013C19

SIGN_CONN_ESTAB_ATT_MO_D

M8013C21

SIGN_CONN_ESTAB_ATT_EMG

The number of Signaling Connection Establishment attempts for mobile originated signaling. From UE's point of view, the transition from ECM-IDLE to ECMCONNECTED has started. The number of Signaling Connection Establishment attempts for mobile terminated connections. From UE's point of view, the transition from ECM-IDLE to ECMCONNECTED is started. The number of Signaling Connection Establishment attempts for mobile originated data connections. From UE's point of view, the transition from ECM-IDLE to ECMCONNECTED is started. Number of Signaling Connection Establishment attempts for emergency calls.

M8013C31

SIGN_CONN_ESTAB_ATT_HIPRIO

M8013C34

SIGN_CONN_ESTAB_ATT_DEL_TO L

M8013C43

S1_SIGN_CONN_ESTAB_ATT_UE

M8013C44

S1_SIGN_CONN_ESTAB_SUCC_UE

M8013C5

SIGN_CONN_ESTAB_COMP

The number of Signaling Connection Establishment attempts for highPriorityAccess connections. From UE's point of view, the transition from ECM-IDLE to ECMCONNECTED is started. The number of Signaling Connection Establishment attempts for delayTolerantAccess connections. From UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED is started. This measurement provides the number of UE-specific logical S1 Signaling Connection Establishment attempts being used for subsequent UE-specific S1 signaling. This measurement provides the number of UE-specific logical S1 Signaling Connection Establishment completions being used for subsequent UE-specific S1 signaling. This measurement provides the number of successful RRC Connection Setups.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 25 of 93

4.4.3 CSSR

Counter ID

ZTE KPI Name

Formula 100*((C373200000+C373200004+C373200008 +C373200012+C373200016+C373200120) * (C373505473+C373505481) * (C373495201)) / ((C373200084+C373200085+C373200086 +C373200087+C373200088+C373200124) * (C373505472+C373505480) * (C373495200)) 100*(RRC.ConnEstabSucc.CauseMtAccess + RRC.ConnEstabSucc.CauseMoSignalling + RRC.ConnEstabSucc.CauseMoData + RRC.ConnEstabSucc.CauseHighPriorityAccess + RRC.ConnEstabSucc.CauseEmergency + RRC.ConnEstabSucc.CauseDelayTolerantAccess) * (ERAB.EstabInitSuccNbr + ERAB.EstabAddSuccNbr) *(S1SIG.conestabSucc) / (RRC.ConnEstabAtt.CauseMtAccess + RRC.ConnEstabAtt.CauseMoSignalling + RRC.ConnEstabAtt.CauseMoData + RRC.ConnEstabAtt.CauseHighPriorityAccess + RRC.ConnEstabAtt.CauseEmergency + RRC.ConnEstabAtt.CauseDelayTolerantAccess) * (ERAB.EstabInitAttNbr + ERAB.EstabAddAttNbr) * (S1SIG.conestabSucc)

Counter Name

C373200000

RRC.ConnEstabSucc.CauseMtAccess

C373200004

RRC.ConnEstabSucc.CauseMoSignalling

Counter Description The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment.The counter is used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is mt-Access. The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment.The counter is used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is mo-Signalling.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 26 of 93

Counter ID

Counter Name

C373200008

RRC.ConnEstabSucc.CauseMoData

C373200012

RRC.ConnEstabSucc.CauseHighPriorityAccess

C373200016

RRC.ConnEstabSucc.CauseEmergency

C373200084

RRC.ConnEstabAtt.CauseMtAccess

C373200085

RRC.ConnEstabAtt.CauseMoSignalling

C373200086

RRC.ConnEstabAtt.CauseMoData

C373200087

RRC.ConnEstabAtt.CauseHighPriorityAccess

C373200088

RRC.ConnEstabAtt.CauseEmergency

Counter Description The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment.The counter is used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is mo-Data. The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment.The counter is used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is highPriorityAccess. The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment.The counter is used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is emergency. The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is mt-access. Each RRCConnectionRequest message received is added to the counter. The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is mo-Signalling. Each RRCConnectionRequest message received is added to the counter. The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is mo-Data. Each RRCConnectionRequest message received is added to the counter. The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is highPriorityAccess. Each RRCConnectionRequest message received is added to the counter. The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is emergency. Each RRCConnectionRequest message received is added to the counter.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 27 of 93

Counter ID

Counter Name

Counter Description

C373200120

RRC.ConnEstabSucc.CauseDelayTolerantAccess

C373200124

RRC.ConnEstabAtt.CauseDelayTolerantAccess

C373505472

ERAB.EstabInitAttNbr

C373505473

ERAB.EstabInitSuccNbr

C373505480

ERAB.EstabAddAttNbr

C373505481

ERAB.EstabAddSuccNbr

C373495200

S1SIG.ConnEstabAtt

The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment.The counter is used to count the number of RRCConnectionSetupComplete message received by eNodeB from UE, and the RRC establishment cause is delayTolerantAccess. The eNodeB receives a RRCConnectionRequest message from the UE and the RRC Connection setup cause is delayTolerantAccess. Each RRCConnectionRequest message received is added to the counter. On receipt by the eNodeB of an INITIAL CONTEXT SETUP REQUEST message, each requested E-RAB in the message is added to the counter. On transmission by the eNodeB to MME of an INITIAL CONTEXT SETUP RESPONSE message, in which each E-RAB successfully established is added to the counter. On receipt by the eNodeB of an E-RAB SETUP REQUEST message, each requested E-RAB in the message is added to the counter. On transmission by the eNodeB to MME of an E-RAB SETUP RESPONSE message, in which each E-RAB successfully established is added to the counter. Transmission of an INITIAL UE MESSAGE by the eNodeB to the the MME.

C373495201

S1SIG.ConnEstabSucc

On receipt by The eNodeB of first message from MME which succeeds INITIAL UE MESSAGE message on an UE-associated logical S1-connection.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 28 of 93

4.4.4

Ericsson

KPI Name

Formula

CSSR

100 * (pmRrcConnEstabSucc/(pmRrcConnEstabAtt-pmRrcConnEstabAttReAtt)) * (pmS1SigConnEstabSucc/pmSigConnEstabAtt) * (pmErabEstabSuccInit+pmErabEstabSuccAdded)/(pmErabEstabAttInit+pmErabEs tabAttAdded)

Counter Name pmRrcConnEstabSucc pmRrcConnEstabAtt pmRrcConnEstabAttReAtt pmS1SigConnEstabSucc pmS1SigConnEstabAtt pmErabEstabSuccInit

pmErabEstabSuccAdded pmErabEstabAttInit

pmErabEstabAttAdded

Description The total number of successful RRC Connection Establishments. The total number of RRC Connection Request attempts. The total number of RRC Connection Request attempts that are considered as re-attempts. The total number of successful S1 signalling connection establishments. This measurement provides the number of S1 Signalling connection establishment attempts for any establishment cause. The total number of successful initial E-RAB Establishments. Initial E-RABs are all E-RABs present in the S1 message Initial Context Setup Request. The total number of successfully added E-RABs. Added E-RABs are all E-RABs present in S1 message E-RAB Setup Request. The total number of initial E-RAB Establishment attempts. Initial E-RABs are all E-RABs present in the S1 message Initial Context Setup Request. The total number of added E-RAB Establishment attempts. Added E-RABs are all E-RABs present in S1 message E-RAB Setup Request.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 29 of 93

4.5

KPI Simulation

5.

SDR – Service Drop Rate

5.1

Definition

The Service Drop Rate or Session Abnormal Release Rate is measures the ability of the network to maintain a radio access bearer independent of the user session on the bearer. It is defined as the ratio of abnormal session disconnections, divided by the total number of successful session setups.

Notes: -

The drop is measure for active connection only (there is data in the buffer)

-

The SDR KPI includes drop due to eNB, MME. Service Drop Rate also including drop due to handover, RRNA (Radio Resource Not Available) and Partial Handover. The KPI excluding drop due to inactivity.

5.2

Generic Formula

𝑆𝐷𝑅 [%] = 100% ×

#𝐴𝑏𝑛𝑜𝑟𝑚𝑎𝑙_𝑆𝑒𝑠𝑠𝑖𝑜𝑛_𝑅𝑒𝑙𝑒𝑎𝑠𝑒𝑠 #𝐴𝑙𝑙 𝑒𝑅𝐴𝐵 𝑅𝑒𝑙𝑒𝑎𝑠𝑒

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 30 of 93

5.3

Signaling Flow

RBS Initiated E-RAB Release

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 31 of 93

MME Initiated E-RAB Release

5.4

KPI Formula

5.4.1

Huawei KPI Name Service Drop Rate

Formula 100*(L.E-RAB.AbnormRel + L.E-RAB.AbnormRel.MME) / (L.E-RAB.AbnormRel + L.E-RAB.NormRel + L.E-RAB.AbnormRel.MME)

Counter Name L.E-RAB.NormRel

Counter Description Total number of normal E-RABreleases initiated by the eNodeB in a cell

L.E-RAB.AbnormRel.MME

Number of abnormal releases of E-RABs because of faults on the MME side

L.E-RAB.AbnormRel

Total number of abnormal releases of actived E-RABs initiated by the eNodeB

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 32 of 93

5.4.2 Nokia KPI Name Formula Service Drop Rate 100 * sum (ERAB_REL_ENB_ACT_QCI1 + ERAB_REL_ENB_ACT_QCI2 + ERAB_REL_ENB_ACT_QCI3 + ERAB_REL_ENB_ACT_QCI4 + ERAB_REL_ENB_ACT_NON_GBR + ERAB_REL_HO_PART + EPC_EPS_BEARER_REL_REQ_RNL + EPC_EPS_BEARER_REL_REQ_OTH + ERAB_REL_EPC_PATH_SWITCH) / sum (ERAB_REL_ENB + 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_EPC_PATH_SWITCH)

Counter ID

Counter Name

M8006C176

ERAB_REL_ENB_ACT_QCI1

M8006C177

ERAB_REL_ENB_ACT_QCI2

M8006C178

ERAB_REL_ENB_ACT_QCI3

M8006C179

ERAB_REL_ENB_ACT_QCI4

M8006C180

ERAB_REL_ENB_ACT_NON_GBR

Counter Description This measurement provides the number of released active E-RABs (that is when there was user data in the queue at the time of release) with QCI1 characteristics. The release is initiated by the eNB due to radio connectivity problems. This measurement provides the number of released active E-RABs (that is when there was user data in the queue at the time of release) with QCI2 characteristics. The release is initiated by the eNB due to radio connectivity problems. This measurement provides the number of released active E-RABs (that is when there was user data in the queue at the time of release) with QCI3 characteristics. The release is initiated by the eNB due to radio connectivity problems. This measurement provides the number of released active E-RABs (that is when there was user data in the queue at the time of release) with QCI4 characteristics. The release is initiated by the eNB due to radio connectivity problems. This measurement provides the number of released active E-RABs (that is when there was user data

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 33 of 93

Counter ID

Counter Name

M8006C261

ERAB_REL_HO_PART

M8006C8

EPC_EPS_BEARER_REL_REQ_RNL

M8006C9

EPC_EPS_BEARER_REL_REQ_OTH

M8006C277

ERAB_REL_EPC_PATH_SWITCH

M8006C254

ERAB_REL_ENB

Counter Description in the queue at the time of release) with non-GBR characteristics (QCI5...9). The release is initiated by the eNB due to radio connectivity problems. This measurement provides the number of E-RABs released due to a partial HO. The partial HO means that the HO for the admitted E-RABs was successfully completed, although not all E-RABs were admitted by the HO target during HO preparation. The counter is incremented with the number of E-RABs not admitted by the HO target. The counter is maintained in the source cell regardless of the bearers QCI. The number of EPC-initiated EPS Bearer Release requests due to the Radio Network Layer cause. Each bearer of the "E-RAB to be Released List" IE is counted. In case of a UE context release command, all established EPS Bearers are counted. The number of released DataRadio Bearers due to Other Reasons. Each bearer of the "ERAB To Be Released List" IE has to be counted. In case of a UE context release command, all established EPS Bearer are counted. This measurement provides the number of E-RABs abnormally released in case that EPC has failed to perform the UP path switch for at least one, but not for all, and at least for one non-GBR E-RAB the UP path switch was successful, of the E-RABs included in the preceding S1AP: PATH SWITCH REQUEST. This measurement provides the total number of eNB initiated ERAB releases regardless of the release cause and of the released bearers QCI.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 34 of 93

Counter ID

Counter Name

M8006C6

EPC_EPS_BEARER_REL_REQ_NORM

M8006C7

EPC_EPS_BEARER_REL_REQ_DETACH

ZTE KPI Name Service Drop Rate

Counter Description The number of released Data Radio Bearers due to "normal release per call". Each bearer of the "E-RAB To Be Released List" IE has to be counted. In case of a UE context release command, all established EPS bearers are counted. In case of S1AP: PATH SWITCH REQUEST ACKNOWLEDGE, the number of ERABs normally released in case that EPC has failed to perform the UP path switch for at least one, but not for all, and at least for one non-GBR E-RAB the UP path switch was successful, of the ERABs included in the preceding S1AP: PATH SWITCH REQUEST is counted. The number of EPC-initiated EPS Bearer Release requests due to the Detach procedure by the UE or MME (NAS cause). Each bearer of the "E-RAB To Be Released List" IE has to be counted. In case of a UE context release command, all established EPS Bearers are counted.

5.4.3

Formula 100* (C373505499+ C374067454+ C373505461) / (C373210371+C373210381+C373210391 +C373210421+C373210431+C373210441 +C373210451+C373210501+C373210511 +C373210521+C373210531+C373505354 +C373505364+C373505461+C373505471 +C373505499+C374067454) 100* (ERAB.RelActNbr + ERAB.Rel.ActMME + ERAB.RelEnbNbr.UEOff) /( ERAB.RelAttNbr.MmeReq +ERAB.RelEnbNbr.CauseOverLoadControl + ERAB.RelEnbNbr.Other + ERAB.RelEnbNbr.eNodebCellCongestion + ERAB.RelEnbNbr.CauseHOFail

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 35 of 93

KPI Name

Counter ID

Formula + ERAB.RelEnbNbr.CauseRadioLinkFail + ERAB.RelEnbNbr.ReestFail + ERAB.RelEnbNbr.UserInactive + ERAB.RelEnbNbr.CellBlockOrReset + ERAB.RelAttNbr.InterEnbReestabFail + ERAB.RelEnbNbr.Redirection + ERAB.RelEnbNbr.S1LinkError + ERAB.RelEnbNbr.CCO + ERAB.RelEnbNbr.UEOff + ERAB.RelMmeNbr.S1Reset)

Counter Name

C373210371

ERAB.RelAttNbr.MmeReq

C373210381

ERAB.RelEnbNbr.CauseOverLoadControl

C373210391

ERAB.RelEnbNbr.Other

C373210421

ERAB.RelEnbNbr.eNodebCellCongestion

C373210431

ERAB.RelEnbNbr.CauseHOFail

Counter Description The eNodeB receives the UEContextReleaseCommand or ERABReleaseCommand message from the MME, in which the Cause is “Normal Relase”, “Detach”,” Authentication failure” or” Interaction with other procedure”. Each above E-RABs release successful initiated by MME is added to the counter In the condition of opening "Load Control" switch,the eNodeB trigger the some appropriate traffics to release when detecting cell overloading.When a E-RAB is released for above reason, it is added to the counter. For other reason, the eNodeB sends the ERABReleaseIndication message to MME. Each above E-RABs initiated by eNodeB is added to the counter. In the condition of opening "Congestion Control" switch,the eNodeB trigger the some appropriate traffics to release when cell congestion.When QCI1 E-RAB is released for above reason,it is added to the counter. 1 A UE is realesed by the source eNodeB due to an expected UEContextReleaseCommand or UEContextRelease message indicating handover complete not received by the eNodeB. 2 The eNodeB receives the HANDOVER COMMAND message then release the partial E-RABs due to the target preparation failure. Each above two conditions E-RAB realeased is added to the counter.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 36 of 93

Counter ID

Counter Name

C373210441

ERAB.RelEnbNbr.CauseRadioLinkFail

C373210451

ERAB.RelEnbNbr.ReestFail

C373210501

ERAB.RelEnbNbr.UserInactive

C373210511

ERAB.RelEnbNbr.CellBlockOrReset

C373210521

ERAB.RelAttNbr.InterEnbReestabFail

C373210531

ERAB.RelEnbNbr.Redirection

C373505354

ERAB.RelEnbNbr.S1LinkError

Counter Description When a RLC PDU is transfered then exceeded the maximum number on the downlink, it is regarded as RLF.When eNodeB's timer expires that monitoring the message from the the UE to eNodeB, it is regarded as RLF. For example, the RRCConnectionReestablishmentComplete message, the RRCConnectionReconfigurationComplete message and so on.When a SR is transfered then exceeded the maximum number,it is regarded as RLF. Transmission of a UE CONTEXT RELEASE REQUEST message by the eNodeB to the MME when eNodeB occur RRC connection reestablishment failures then sends the RRCConnectionReestablishmentReject message to the UE. Each above E-RAB released is added to the counter. In the condition of opening "USER INACTIVITY" switch,the eNodeB detects user that have no DTCH data queued on the downlink and the uplink during configuration intervals. The user is regarded as "inactivity". Each above condition E-RAB released is added to the counter. 1 The eNodeB receives the Cell Block Command from the OMM for manual operation.2 The eNodeB occurs alarm about cell that trigger UE release.Each above two conditions E-RAB released is added to the counter. An E-RAB is released when the eNodeB receiving a UE context release message, which indicates that the cause is "Failure in the Radio Interface Procedure", from the MME. This counter counts the number of times that an E-RAB is released in this case. When the eNodeB concludes UE redirection to other cell, it sends the UeContextReleaseRequest message to MME after sending the RRCConnectionRelease message to UE. Each above E-RAB released is added to the counter. The S1 link fault refer to the following.1 The eNodeB detects the fibber warning.2 The eNodeB gtpu layer detects the path fault from the eNodeB to SGW.3 The eNodeB gtpu layer receives the ErrorIndication message from the SGW.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 37 of 93

Counter ID

Counter Name

C373505364

ERAB.RelEnbNbr.CCO

C373505461

ERAB.RelEnbNbr.UEOff

C373505471

ERAB.RelMmeNbr.S1Reset

C373505499

ERAB.RelActNbr

C374067454

Number of Abnormal Release Active ERAB Triggered by MME

5.4.4

Counter Description The E-RABs requested to be released by eNodeB due to CCO are added to the counter. The eNodeB judge UE's state according to HARQ feedback algorithm. If the UE's state is concluded as offline, the eNodeB will trigger UE release.Each above E-RAB released is added to the counter. When the eNodeB receives an S1 Reset message or Error Ind message from the MME, or receives a UE context release message from the core network (the cause carried in the message is not "Normal Release, Detach, Authentication failure, Successful Handover, Interaction with other procedure, Failure in the Radio Interface Procedure"), it sends an RRCConnectionRelease message to the UE. In this case, the counter starts counting. The abnormally released E-RABs that were active at the time of release. i.e.when there was user data in the queue in any of the directions. Each E-RAB is added to the counter. This counter counts the number of times that an MME triggers an E-RAB release because the MME is improper.

Ericsson

KPI Name

Formula

Service Drop Rate

100*(pmErabRelAbnormalEnbAct+pmErabRelAbnormalMmeAct)/(pmErabRelAb normalEnb+pmErabRelNormalEnb+pmErabRelMme)

Counter Name pmErabRelAbnormalEnbAct

pmErabRelAbnormalMmeAct pmErabRelAbnormalEnb pmErabRelNormalEnb

Description The total number of abnormal E-RAB Releases per cell initiated by the eNB and that there was data in either the UL or DL buffer (i.e. active). The total number of E-RAB Releases initiated by the MME considered as abnormal. The counter is stepped if if there was data in either the UL or DL buffer (i.e. active). The total number of abnormal E-RAB Releases triggered by eNB per cell. The total number of normal E-RAB Releases triggered by eNB per cell.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 38 of 93

Counter Name

Description The total number of E-RAB Releases per cell initiated by the MME excluding successful handover. The counter is stepped regardless of whether data was or was not lost in UL/DL buffers.

pmErabRelMme

5.5

KPI Simulation

6.

Intra Frequency Handover Success Rate

6.1

Definition

Intra LTE HO Success Rate (HOSR) is defined as the number of successful intra LTE handover attempts divided by the total number of intra LTE handover attempts. Note: -

The formula is measured Handover execution only

-

The formula includes intra/inter eNodeB and X2/S1 handover

6.2

Generic Formula

𝐻𝑂𝑆𝑅 = 100% 𝑥

#𝑆𝑢𝑐𝑐𝑒𝑠𝑠𝑓𝑢𝑙 𝐼𝑛𝑡𝑟𝑎 𝐿𝑇𝐸 𝐻𝑂𝑠 #𝐴𝑡𝑡𝑒𝑚𝑝𝑡𝑒𝑑 𝐼𝑛𝑡𝑟𝑎 𝐿𝑇𝐸 𝐻𝑂𝑠

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 39 of 93

6.3

Signaling Flow

X2 Handover

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 40 of 93

S1 Handover

6.4

KPI Formula

6.4.1

Huawei KPI Name Intra-Frequency Handover SR

Formula 100*(L.HHO.IntraeNB.IntraFreq.ExecSuccOut + L.HHO.IntereNB.IntraFreq.ExecSuccOut - L.HHO.IntraeNB.IntraFreq.Succ.ReEst2Src - L.HHO.IntereNB.IntraFreq.Succ.ReEst2Src) / (L.HHO.IntraeNB.IntraFreq.ExecAttOut + L.HHO.IntereNB.IntraFreq.ExecAttOut)

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 41 of 93

Counter Name L.HHO.IntraeNB.IntraFreq.ExecAttOut

Counter Description Number of intra-eNodeB intra-frequency outgoing handovers executions in a cell

L.HHO.IntraeNB.IntraFreq.ExecSuccOut

Number of successful intra-eNodeB intra-frequency outgoing handovers in a cell

L.HHO.IntereNB.IntraFreq.ExecAttOut

Number of inter-eNodeB intra-frequency outgoing handovers executions in a cell Number of successful inter-eNodeB intra-frequency outgoing handovers in a cell

L.HHO.IntereNB.IntraFreq.ExecSuccOut L.HHO.IntraeNB.IntraFreq.Succ.ReEst2Src

L.HHO.IntereNB.IntraFreq.Succ.ReEst2Src

Number of successful intra-eNodeB intra-frequency outgoing handovers where RRC connections are reestablished to the source cell for UEs in a cell Number of successful inter-eNodeB intra-frequency outgoing handovers where RRC connections are reestablished to the source cell for UEs in a cell

6.4.2

Nokia KPI Name Intra-Frequency 100*(SUCC_INTRA_ENB_HO Handover SR + SUCC_INTER_ENB_HO + INTER_ENB_S1_HO_SUCC - HO_INTFREQ_SUCC) / (ATT_INTRA_ENB_HO + ATT_INTER_ENB_HO + INTER_ENB_S1_HO_ATT - HO_INTFREQ_ATT)

Counter ID

Counter Name

Formula

Counter Description

M8009C6

ATT_INTRA_ENB_HO

The number of Intra-eNB Handover attempts.

M8009C7

SUCC_INTRA_ENB_HO

The number of successful Intra-eNB Handover completions.

M8014C18

INTER_ENB_S1_HO_ATT

The number of Inter eNB S1-based Handover attempts

M8014C19

INTER_ENB_S1_HO_SUCC

The number of successful Inter eNB S1-based Handover completions

M8014C6

ATT_INTER_ENB_HO

The number of Inter-eNB X2-based Handover attempts.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 42 of 93

Counter ID

Counter Name

Counter Description

M8014C7

SUCC_INTER_ENB_HO

The number of successful Inter-eNB X2-based Handover completions.

M8021C0

HO_INTFREQ_ATT

The number of intra LTE inter-frequency Handover attempts. It comprises the intra- and inter-eNB.

M8021C2

HO_INTFREQ_SUCC

The number of successful intra LTE inter-frequency Handover completions. It comprises the intra- and intereNB Handover scenario.

6.4.3

ZTE KPI Name Intra-Frequency Handover SR

Formula 100* (C373250980+ C373261280+ C373271580) / (C373250900+ C373261280+ C373271500) 100* ( HO.IntraEnbIntraFreqOutExeSucc + HO.InterEnbX2IntraFreqOutExeSucc + HO.InterEnbS1IntraFreqOutExeSucc) / (HO.IntraEnbIntraFreqOutPrepSucc + HO.InterEnbX2IntraFreqOutPrepSucc + HO.InterEnbS1IntraFreqOutPrepSucc)

Counter ID

Counter Name

C373250900

HO.IntraEnbIntraFreqOutPrepSucc

C373250980

HO.IntraEnbIntraFreqOutExeSucc

C373261200

HO.InterEnbX2IntraFreqOutPrepSucc

C373261280

HO.InterEnbX2IntraFreqOutExeSucc

C373271500

HO.InterEnbS1IntraFreqOutPrepSucc

Counter Description When the eNodeB sends an "RRC Connection Reconfiguration" message (RRCConnectionReconfiguration) carrying the mobilityControlInfo to the UE When the eNodeB receives the RRCConnectionReconfigurationComplete message from the UE, the switching type is the same frequency The source eNodeB receives the "HANDOVER REQUEST ACKNOWLEDGE" (TS36.423) message sent by the target eNodeB When eNodeB receives a X2AP message UE CONTEXT RELEASE sent from the target eNodeB to the source eNodeB, it indicates a successful handover over the X2. Each UE CONTEXT RELEASE message received is added to the counter. Transmission of the RRCConnectionReconfiguration message to UE triggering the handover over the S1 from

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 43 of 93

Counter ID

C373271580

6.4.4

Counter Name

HO.InterEnbS1IntraFreqOutExeSucc

Counter Description the source eNodeB to the target eNodeB,it indicates the successful preparation of an outgoing inter-eNB handover. Each RRCConnectionReconfiguration message transimtted is added to the counter. When eNodeB receives a S1AP message UE CONTEXT RELEASE COMMAND sent from the MME to the source eNodeB, it indicates a successful handover over the S1. Each UE CONTEXT RELEASE COMMAND message received is added to the counter.

Ericsson

KPI Name Intra-Frequency Handover SR

Formula 100*(pmHoExeSuccLteIntraF/pmHoExeAttLteIntraF)

Counter Name Description pmHoExeSuccLteIntraF The number of successful intra LTE intra frequency handovers. pmHoExeAttLteIntraF The number of intra LTE intra frequency handover execution attempts.

6.5

KPI Simulation

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 44 of 93

7.

CSFB Success Rate

7.1

Definition

This KPI shows the setup success ratio for the preparation procedure subject to a CS fallback, including both the setup of an initial UE context in MME (UE-associated logical S1connection) and UE context modifications for CS fallback Note: -

7.2

Ericsson can only measure number CSFB attempt, there is no CSFB success counter.

Generic Formula

𝐶𝑆𝐹𝐵 𝑆𝑅 [%] = 100% ×

7.3

# initial context setup and context modification successes for CS Fallback #initial context setup and context modification attempts for CS Fallback

Signaling Flow

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 45 of 93

7.4

KPI Formula

7.4.1

Huawei KPI Name CSFB Success Rate

Formula 100*L.CSFB.PrepSucc/L.CSFB.PrepAtt

Counter Name L.CSFB.PrepAtt

Counter Description Number of CSFB indicators received by the eNodeB

L.CSFB.PrepSucc

Number of successful CSFB responses from the eNodeB

7.4.2

Nokia KPI Name Formula CSFB Success Rate 100*(UE_CTX_SETUP_SUCC_CSFB + UE_CTX_MOD_SUCC_CSFB / (UE_CTX_SETUP_ATT_CSFB + UE_CTX_MOD_ATT_CSFB)

Counter ID

Counter Name

Counter Description

M8013C46

UE_CTX_SETUP_ATT_CSFB

M8013C48

UE_CTX_SETUP_SUCC_CSFB

M8013C51

UE_CTX_MOD_ATT_CSFB

M8013C53

UE_CTX_MOD_SUCC_CSFB

This measurement provides the number of UE Context Setup attempts. Only the UE Contexts that are subject to CS Fallback are counted. This measurement provides the number of successfully established UE Contexts. Only those UE Contexts that are subject to CS Fallback are counted. This measurement provides the number of attempted UE Context Modifications. Only those UE Contexts that are subject to CS Fallback are counted. This measurement provides the number of successful UE Context Modifications. Only those UE Contexts that are subject to CS Fallback are counted.

7.4.3 KPI Name CSFB Success Rate

ZTE Formula 100* (C373220645+ C373220648+ C373220651 + C373220654) / (C373220644+ C373220647+ C373220650 + C373220653)

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 46 of 93

KPI Name

Counter ID

Formula 100* (Number of Successful Mt-Access Initial Context Setup with CSFB + Number of Successful Mo-Signaling or Mo-Data Initial Context Setup with CSFB + Number of Successful Context Modification with CSFB + Number of Successful Other Initial Context Setup with CSFB) / ( Number of Attempted Mt-Access Initial Context Setup with CSFB + Number of Attempted Mo-Signaling or Mo-Data Initial Context Setup with CSFB + Number of Attempted Context Modification with CSFB + Number of Attempted Other Initial Context Setup with CSFB)

Counter Name

C373220644

Number of Attempted Mt-Access Initial Context Setup with CSFB

C373220645

Number of Successful Mt-Access Initial Context Setup with CSFB

C373220647

Number of Attempted Mo-Signalling or Mo-Data Initial Context Setup with CSFB

C373220648

Number of Successful Mo-Signalling or Mo-Data Initial Context Setup with CSFB

C373220650

Number of Attempted Context Modification with CSFB

C373220651

Number of Successful Context Modification with CSFB

Counter Description After the LTE user sends the service request message to MME for Mt-Access, the MME requires eNodeB to establish the UE Context which indicates CS service fallback to GERAN/UTRAN. The counter increase by 1. After the LTE user sends the service request message to MME for mt-signaling or mtdata ,the MME requires eNodeB to establish the UE Context which indicates CS service fallback to GERAN/UTRAN, after eNodeB response MME the UE Context established, The counter increase by 1 After the LTE user sends the service request message to MME for Mo-Access, the MME requires eNodeB to establish the UE Context which indicates CS service fallback to GERAN/UTRAN. The counter increase by 1. After the LTE user sends the service request message to MME for mo-signaling or modata ,the MME requires eNodeB to establish the UE Context which indicates CS service fallback to GERAN/UTRAN, after eNodeB response MME the UE Context established, The counter increase by 1 After the LTE user sends the service request message to MME for Modification, the MME requires eNodeB to establish the UE Context which indicates CS service fallback to GERAN/UTRAN. The counter increase by 1. After the LTE user sends the service request message to MME ,the MME requires eNodeB to establish the UE Context which indicates CS service fallback to GERAN/UTRAN, after eNodeB response

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 47 of 93

Counter ID

Counter Name

Counter Description MME the UE Context established, The counter increase by 1

C373220653

Number of Attempted Other Initial Context Setup with CSFB

C373220654

Number of Successful Other Initial Context Setup with CSFB

7.4.4

After the LTE user sends the service request message to MME for other, the MME requires eNodeB to establish the UE Context which indicates CS service fallback to GERAN/UTRAN. The counter increase by 1. After the LTE user sends the service request message to MME for other ,the MME requires eNodeB to establish the UE Context which indicates CS service fallback to GERAN/UTRAN, after eNodeB response MME the UE Context established, The counter increase by 1

Ericsson

Not Available. KPI not supported, Ericsson only has counter CSFB redirection attempt without success counter.

7.5

KPI Simulation

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 48 of 93

8.

3G CS Fallback Success Rate

8.1

Definition

3G CSFB Success Rate (CSFB SR) is defined as the fraction of Circuit Switched Fallback calls that can successfully setup a call on a target WCDMA 3G network layer. Notes: - The formula only measures in RRC Phase

8.2

Generic Formula 3𝐺 𝐶𝑆𝐹𝐵 𝑆𝑅 = 100% 𝑥

# 𝑆𝑢𝑐𝑐𝑒𝑠𝑓𝑢𝑙 𝐶𝑆𝐹𝐵 𝑐𝑎𝑙𝑙 𝑠𝑒𝑡𝑢𝑝𝑠 # 𝐶𝑆𝐹𝐵 𝐶𝑎𝑙𝑙 𝑎𝑡𝑡𝑒𝑚𝑝𝑡𝑠

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 49 of 93

8.3

Signaling Flow

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 50 of 93

8.4

KPI Formula

8.4.1

Huawei KPI Name 3G CSFB SR

Formula 100*VS.RRC.SuccConnEstab.CSFB/VS.RRC.AttConnEstab.CSFB

Counter Name VS.RRC.AttConnEstab.CSFB

Counter Description Number of RRC Connection Setup Requests for CSFB for Cell

VS.RRC.SuccConnEstab.CSFB

Number of Successful RRC Connection Setups for CSFB for Cell

8.4.2

Nokia KPI Name Formula 3G CSFB SR 100*(RRC_CONN_STP_ATT_CSFB - RRC_STP_ACC_FAIL_CSFB - RRC_ACC_REL_CSFB) / (RRC_CONN_STP_ATT_CSFB - RRC_ACC_REL_CSFB - RRC_ATT_REP_CSFB)

Counter ID

Counter Name

M1001C747

RRC_CONN_STP_ATT_CSFB

M1001C748

RRC_STP_ACC_FAIL_CSFB

M1001C749

RRC_ACC_REL_CSFB

M1001C750

RRC_ATT_REP_CSFB

Counter Description The number of RRC connection setup attempts for CS fallback. Updated when the RNC receives RRC: RRC CONNECTION REQUEST message with "CSFB Indication" IE from the UE, and the RNC starts to reserve resources for the RRC connection. The number of RRC connection setup/access failures for CS fallback. Updated when the RRC connection setup fails either in the resource reservation or access phase, and RRC: RRC CONNECTION REQUEST included "CSFB Indication" IE. The number of RRC access releases for CS fallback. Updated when the UE performing RRC connection setup with "CSFB Indication" IE in RRC: RRC CONNECTION REQUEST, and the UE sends a new RRC Connection Request to another cell and therefore the previous RRC connection setup procedure is interrupted. The number of RRC connection setup repetitions for CS fallback. Updated when a repeated RRC CONNECTION REQUEST is received from the same UE as the first RRC CONNECTION REQUEST with "CSFB Indication" IE during the time interval defined.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 51 of 93

8.4.3

ZTE KPI Name

Formula 100* C310083539/ C310083538

3G CSFB SR

100* CELL_UE_REDIREC_EUTRAN_TO_UTRAN_SUCC / CELL_UE_REDIREC_EUTRAN_TO_UTRAN_ATT

Counter ID

Counter Name

C310083539

CELL_UE_REDIREC_EUTRAN_TO_UTRAN_SUCC

C310083538

CELL_UE_REDIREC_EUTRAN_TO_UTRAN_ATT

8.4.4 KPI Name 3G CSFB SR

Counter Description The Number of successful RRC connection establishment when “Cause” is “CSFB Indication” in the RRC Connection Request message The Number of attempted RRC Connection establishment when “Cause” is “CSFB Indication”in the RRC Connection Request message. The Counter exclude the number of rejected RRC Connection request caused by Service-balanced Redirection.

Ericsson Formula 100*((UtranCell.pmTotNoRrcConnReqCsfbIndSucc/(UtranCell.pmTotNoRrcConnR eqCsfbInd-UtranCell.pmNoLoadSharingRrcConnCsfbInd))

Counter Name pmTotNoRrcConnReqCsfbIndSucc

Description Number of successful RRC Connection Requests for which the UE included the IE 'CSFB Indication'. Feature: CsFallbackLte Condition: Incremented by one when the RNC receives an RRC Connection Setup Complete message, indicating that the RRC connection has been successfully established, for a UE that included the IE 'CSFB Indication' at RRC establishment. Counter type: PEG Scanner: Not included in any predefined scanner Counter is reset after measurement period: Yes Context: SRNC

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 52 of 93

Counter Name pmTotNoRrcConnReqCsfbInd

pmNoLoadSharingRrcConnCsfbInd

Description Number of RRC CONNECTION REQUEST messages that were received during the ROP and included the IE 'CSFB Indication', not including retransmissions. Feature: CsFallbackLte Condition: Incremented by one per connection when the RNC receives an RRC CONNECTION REQUEST message from a UE with any Establishment Cause and that includes the IE 'CSFB Indication'. Subsequent retransmissions are not counted. Counter type: PEG Scanner: Not included in any predefined scanner Counter is reset after measurement period: Yes Context: SRNC Number of load sharing RRC connection attempts for UEs that included the IE 'CSFB Indication' in the RRC Connection Request message. Feature: CsFallbackLte Condition: Incremented by one per connection when the RNC sends an RRC Connection Reject message to a UE requesting CS service because another cell (frequency) has been selected by Load Sharing, if the UE included the IE 'CSFB Indication' in the RRC Connection Request message. Counter type: PEG Scanner: Not included in any predefined scanner Counter is reset after measurement period: Yes Context: SRNC

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 53 of 93

8.5

KPI Simulation

9.

User Downlink Throughput

9.1

Definition

DL User Throughput is the average user throughput on a downlink Radio Bearer. It includes user data but excluding retransmissions, padding bits, data PDU headers and RLC control PDU's. Note: -

9.2

The last data unit TTI should be removed

Generic Formula DL_User_Throughput =

9.3 n/a

DL_Data_Throughput_Volume_kbits [kbps] DL_Data_Throughput_Time_seconds

Signaling Flow

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 54 of 93

9.4

KPI Formula

9.4.1

Huawei KPI Name User DL Throughput (kbps)

Formula ([L.Thrp.bits.DL] - [L.Thrp.bits.DL.LastTTI]) / [L.Thrp.Time.DL.RmvLastTTI]

Counter Name L.Thrp.bits.DL

Counter Description Total downlink traffic volume for PDCP SDUs in a cell

L.Thrp.bits.DL.LastTTI

Downlink traffic volume sent in the last TTI for PDCP SDUs before the buffer is empty

L.Thrp.Time.DL.RmvLastTTI

Data transmit duration except the last TTI before the downlink buffer is empty

9.4.2

Nokia KPI Name Formula User DL (IP_TPUT_VOL_DL_QCI_1 + IP_TPUT_VOL_DL_QCI_2 + Throughput (kbps) IP_TPUT_VOL_DL_QCI_3 + IP_TPUT_VOL_DL_QCI_4 + IP_TPUT_VOL_DL_QCI_5 + IP_TPUT_VOL_DL_QCI_6 + IP_TPUT_VOL_DL_QCI_7 + IP_TPUT_VOL_DL_QCI_8 + IP_TPUT_VOL_DL_QCI_9) / (IP_TPUT_TIME_DL_QCI_1 + IP_TPUT_TIME_DL_QCI_2 + IP_TPUT_TIME_DL_QCI_3 + IP_TPUT_TIME_DL_QCI_4 + IP_TPUT_TIME_DL_QCI_5 + IP_TPUT_TIME_DL_QCI_6 + IP_TPUT_TIME_DL_QCI_7 + IP_TPUT_TIME_DL_QCI_8 + IP_TPUT_TIME_DL_QCI_9)

Counter ID

Counter Name

Counter Description

M8012C117

IP_TPUT_VOL_DL_QCI_1

This measurement provides IP throughput volume on QCI 1 bearers in downlink as experienced by the UE.

M8012C119

IP_TPUT_VOL_DL_QCI_2

This measurement provides IP throughput volume on QCI 2 bearers in downlink as experienced by the UE.

M8012C121

IP_TPUT_VOL_DL_QCI_3

This measurement provides IP throughput volume on QCI 3 bearers in downlink as experienced by the UE.

M8012C123

IP_TPUT_VOL_DL_QCI_4

This measurement provides IP throughput volume on QCI 4 bearers in downlink as experienced by the UE.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 55 of 93

Counter ID

Counter Name

Counter Description

M8012C125

IP_TPUT_VOL_DL_QCI_5

M8012C127

IP_TPUT_VOL_DL_QCI_6

M8012C129

IP_TPUT_VOL_DL_QCI_7

This measurement provides IP throughput volume on QCI 7 bearers in downlink as experienced by the UE.

M8012C131

IP_TPUT_VOL_DL_QCI_8

This measurement provides IP throughput volume on QCI 8 bearers in downlink as experienced by the UE.

M8012C133

IP_TPUT_VOL_DL_QCI_9

This measurement provides IP throughput volume on QCI 9 bearers in downlink as experienced by the UE.

M8012C118

IP_TPUT_TIME_DL_QCI_1

This measurement provides the IP throughput time on QCI 1 bearers in downlink.

M8012C120

IP_TPUT_TIME_DL_QCI_2

This measurement provides the IP throughput time on QCI 2 bearers in downlink.

M8012C122

IP_TPUT_TIME_DL_QCI_3

This measurement provides the IP throughput time on QCI 3 bearers in downlink.

M8012C124

IP_TPUT_TIME_DL_QCI_4

This measurement provides the IP throughput time on QCI 4 bearers in downlink.

M8012C126

IP_TPUT_TIME_DL_QCI_5

This measurement provides the IP throughput time on QCI 5 bearers in downlink.

M8012C128

IP_TPUT_TIME_DL_QCI_6

This measurement provides the IP throughput time on QCI 6 bearers in downlink.

M8012C130

IP_TPUT_TIME_DL_QCI_7

This measurement provides the IP throughput time on QCI 7 bearers in downlink.

M8012C132

IP_TPUT_TIME_DL_QCI_8

This measurement provides the IP throughput time on QCI 8 bearers in downlink.

M8012C134

IP_TPUT_TIME_DL_QCI_9

This measurement provides the IP throughput time on QCI 9 bearers in downlink.

ZTE KPI Name User DL Throughput (kbps)

This measurement provides IP throughput volume on QCI 5 bearers in downlink as experienced by the UE. This measurement provides IP throughput volume on QCI 6 bearers in downlink as experienced by the UE.

9.4.3

Formula (C374107514*1000+ C374107515)/ C374107516/1000 (DL Aggregated Volume High through Uu for IP Throughput *1000 + DL Aggregated Volume Low through Uu for IP Throughput) /

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 56 of 93

KPI Name

Counter ID

Formula DL Aggregated Time For IP Throughput / 1000

Counter Name

C374107514

DL Aggregated Volume High through Uu For IP Throughput

C374107515

DL Aggregated Volume Low through Uu For IP Throughput

C374107516

DL Aggregated Time For IP Throughput

9.4.4

Counter Description This counter counts the total downlink PDCP SDU dead load, not including packets lost at the Uu interface, tail packets, and data completed through one data scheduling. The counter value = the total data / 1000000. This counter counts the total downlink PDCP SDU dead load, not including packets lost at the Uu interface, tail packets, and data completed through one data scheduling. The counter value = the total data % 1000000. This counter counts the downlink service time during which the eNodeB buffer becomes empty from being not empty, not including the data transmission time for tail packets and data completed through one data scheduling.

Ericsson

KPI Name User DL Throughput (kbps)

Counter Name pmPdcpVolDlDrb

pmPdcpVolDlDrbLastTTI

Formula (pmPdcpVolDlDrbpmPdcpVolDlDrbLastTTI)/(pmUeThpTimeDl/1000)

Description The total volume (PDCP SDU) on Data Radio Bearers that has been transferred (UM and AM) in the downlink direction. When carrier aggregation is used, a PDCP SDU can be sent over multiple cells (PCell/SCell(s)). The total volume (PDCP SDU) on Data Radio Be The total volume (PDCP SDU) on Data Radio Bearers that has been transferred (acknowledged by the UE) in the downlink direction in the last TTI when a buffer is emptied. When carrier aggregation is used, a PDCP SDU can be sent over multiple cells (PCell/S

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 57 of 93

Counter Name pmUeThpTimeDl

Description The effective DL transport time comprises those periods from when the first part of the PDCP SDU of the DL buffer was transmitted on Uu until the buffer is emptied, excluding the TTI emptying the buffer. When carrier aggregation is used, a PDCP SDU can b

9.5

KPI Simulation

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 58 of 93

10.

Cell Downlink Throughput

10.1

Definition

This KPI measures the Cell Throughput in DL for DRB, when the DRB data was scheduled to be transmitted. It represents PDCP level. Note: -

10.2

time for denominator calculated also during no transmission while buffer not empty

Generic Formula

𝐶𝑒𝑙𝑙 𝐷𝐿 𝑇ℎ𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡 =

10.3

DL Data Throughput Volume #Time in which DRB data was required to be scheduled in the downlink

Signaling Flow

n/a

10.4

KPI Formula

10.4.1

Huawei KPI Name Cell DL Throughput (kbps)

Formula ([L.Thrp.bits.DL] / [L.Thrp.Time.Cell.DL.HighPrecision]

Counter Name L.Thrp.bits.DL

Counter Description Total downlink traffic volume for PDCP SDUs in a cell

L.Thrp.Time.Cell.DL.HighPrecision

Total duration of downlink data transmission in a cell (with the precision of 1 ms)

10.4.2 Nokia KPI Name Cell DL Throughput 8*(PDCP_SDU_VOL_DL) (kbps) /

Formula

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 59 of 93

KPI Name

Formula (ACTIVE_TTI_DL)

Counter ID

Counter Name

Counter Description

M8012C20

PDCP_SDU_VOL_DL

M8012C90

ACTIVE_TTI_DL

ZTE KPI Name Cell DL Throughput (kbps)

The measurement gives an indication of the eUu interface traffic load by reporting the total transmitted PDCP SDUrelated traffic volume. This counter provides the number of active TTIs in DL, that is those TTIs with at least one UE scheduled to receive user plane data.

10.4.3

Formula (C373343806* 1000+ C373343807)/C373343885/1000 (Drb.IpThrouDlVoH * 1000+ Drb.IpThrouDlVoL) / DL Traffic Transmission Time /1000

Counter ID

Counter Name

C373343806

Drb.IpThrouDlVoH

C373343807

Drb.IpThrouDlVoL

C373343885

DL Traffic Transmission Time

10.4.4 KPI Name

Ericsson Formula

Counter Description The counter provides the part volume of PDCP SDU transmitted by eNodeB to UE on the downlink.The total volume = volume High + Volume Low. When the eNodeB get the successful DL TB HARQ feedback and all frag of PDCP SDU related to TB have been transmitted to the air interface successfully,the counter is collected. The counter provides the other part volume of PDCP SDU transmitted by eNodeB to UE on the downlink. The total volume = volume High + Volume Low. When the eNodeB get the successful DL TB HARQ feedback and all frag of PDCP SDU related to TB have been transmitted to the air interface successfully,the counter is collected. This counter counts the duration from the time data appears in the downlink service buffer to the time the service buffer becomes empty in a measurement period of all eNodeBs. The overlapping time periods of multiple services are counted once.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 60 of 93

Cell DL Throughput (kbps)

Counter Name pmPdcpVolDlDrb

pmSchedActivityCellDl

10.5

pmPdcpVolDlDrb/(pmSchedActivityCellDl/1000)

Description The total volume (PDCP SDU) on Data Radio Bearers that has been transferred (UM and AM) in the downlink direction. When carrier aggregation is used, a PDCP SDU can be sent over multiple cells (PCell/SCell(s)). The total volume (PDCP SDU) on Data Radio Be The aggregated number of ms in which DRB data was required to be scheduled in the downlink. Condition: Each TTI, the counter shall be incremented when there was a need to schedule DRB data in the downlink. Counter type: PEG Sampling rate: Per ms Scanner: Not included in any predefined scanner Counter is reset after measurement period: Yes Unit: ms

KPI Simulation

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 61 of 93

11.

Cell Downlink Dimensioning Throughput

11.1

Definition

This KPI calculates total downlink traffic volume during the observation of one-hour period. The KPI is calculated on cell level. Unit in kbps.

11.2

Generic Formula Cell DL Dimensioning Throughput = (

11.3

Total Cell DL Traffic Volume [kbit] ) 3600 [s]

Signaling Flow

n/a

11.4

KPI Formula

11.4.1

Huawei KPI Name Cell DL Dimensioning Throughput (Kbps)

Counter Name L.Thrp.bits.DL

Formula L.Thrp.bits.DL / (1000 * 3600)

Counter Description Total downlink traffic volume for PDCP SDUs in a cell

11.4.2 Nokia KPI Name Cell DL (PDCP_SDU_VOL_DL) * 8 Dimensioning / Throughput (Kbps) (1000 * 3600)

Counter ID M8012C20

Counter Name PDCP_SDU_VOL_DL

Formula

Counter Description The measurement gives an indication of the eUu interface traffic load by reporting the total transmitted PDCP SDUrelated traffic volume.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 62 of 93

11.4.3

ZTE KPI Name Cell DL Dimensioning Throughput (Kbps)

Formula (C373343806*1000+ C373343807) / 3600 (Drb.IpThrouDlVoH*1000 + Drb.IpThrouDlVoL) / 3600

Counter ID

Counter Name

C373343806

Drb.IpThrouDlVoH

C373343807

Drb.IpThrouDlVoL

11.4.4

Counter Description The counter provides the part volume of PDCP SDU transmitted by eNodeB to UE on the downlink.The total volume = volume High + Volume Low. When the eNodeB get the successful DL TB HARQ feedback and all frag of PDCP SDU related to TB have been transmitted to the air interface successfully,the counter is collected. The counter provides the other part volume of PDCP SDU transmitted by eNodeB to UE on the downlink. The total volume = volume High + Volume Low. When the eNodeB get the successful DL TB HARQ feedback and all frag of PDCP SDU related to TB have been transmitted to the air interface successfully,the counter is collected.

Ericsson

KPI Name Cell DL Dimensioning Throughput (Kbps)

Counter Name pmPdcpVolDlDrb

Formula pmPdcpVolDlDrb / 3600

Description The total volume (PDCP SDU) on Data Radio Bearers that has been transferred (UM and AM) in the downlink direction. When carrier aggregation is used, a PDCP SDU can be sent over multiple cells (PCell/SCell(s)). The total volume (PDCP SDU) on Data Radio Be

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 63 of 93

12.

User Uplink Throughput

12.1

Definition

UL User Throughput is the average user throughput on an uplink Radio Bearer. It includes user data but excluding retransmissions, padding bits, data PDU headers and RLC control PDU's. PDSCH or PUSCH are usually used. Note: -

The last data unit TTI should be removed

12.2

Generic Formula

12.3

Signaling Flow

n/a

12.4

KPI Formula

12.4.1

Huawei KPI Name User UL Throughput (kbps)

Formula (L.Thrp.bits.UL - L.Thrp.bits.UE.UL.LastTTI) / (L.Thrp.Time.UE.UL.RMVLastTTI)

Counter Name L.Thrp.bits.UL

Counter Description Total uplink traffic volume for PDCP PDUs in a cell

L.Thrp.bits.UE.UL.LastTTI

Traffic volume of uplink PDCP PDUs sent in the last TTI before the UE buffer is empty

L.Thrp.Time.UE.UL.RMVLastTTI

Uplink data transmit duration except the last TTI before the UE buffer is empty

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 64 of 93

12.4.2 Nokia KPI Name Formula User UL (IP_TPUT_VOL_UL_QCI_1 + IP_TPUT_VOL_UL_QCI_2 + Throughput (kbps) IP_TPUT_VOL_UL_QCI_3 + IP_TPUT_VOL_UL_QCI_4 + IP_TPUT_VOL_UL_QCI_5 + IP_TPUT_VOL_UL_QCI_6 + IP_TPUT_VOL_UL_QCI_7 + IP_TPUT_VOL_UL_QCI_8 + IP_TPUT_VOL_UL_QCI_9) / (IP_TPUT_TIME_UL_QCI_1 + IP_TPUT_TIME_UL_QCI_2 + IP_TPUT_TIME_UL_QCI_3 + IP_TPUT_TIME_UL_QCI_4 + IP_TPUT_TIME_UL_QCI_5 + IP_TPUT_TIME_UL_QCI_6 + IP_TPUT_TIME_UL_QCI_7 + IP_TPUT_TIME_UL_QCI_8 + IP_TPUT_TIME_UL_QCI_9)

Counter ID

Counter Name

Counter Description

M8012C91

IP_TPUT_VOL_UL_QCI_1

This measurement provides IP throughput volume on QCI 1 bearers in uplink as experienced by the UE.

M8012C93

IP_TPUT_VOL_UL_QCI_2

This measurement provides IP throughput volume on QCI 2 bearers in uplink as experienced by the UE.

M8012C95

IP_TPUT_VOL_UL_QCI_3

This measurement provides IP throughput volume on QCI 3 bearers in uplink as experienced by the UE.

M8012C97

IP_TPUT_VOL_UL_QCI_4

This measurement provides IP throughput volume on QCI 4 bearers in uplink as experienced by the UE.

M8012C99

IP_TPUT_VOL_UL_QCI_5

M8012C101

IP_TPUT_VOL_UL_QCI_6

This measurement provides IP throughput volume on QCI 5 bearers in uplink as experienced by the UE. This measurement provides IP throughput volume on QCI 6 bearers in uplink as experienced by the UE.

M8012C103

IP_TPUT_VOL_UL_QCI_7

This measurement provides IP throughput volume on QCI 7 bearers in uplink as experienced by the UE.

M8012C105

IP_TPUT_VOL_UL_QCI_8

This measurement provides IP throughput volume on QCI 8 bearers in uplink as experienced by the UE.

M8012C107

IP_TPUT_VOL_UL_QCI_9

This measurement provides IP throughput volume on QCI 9 bearers in uplink as experienced by the UE.

M8012C92

IP_TPUT_TIME_UL_QCI_1

This measurement provides the IP throughput time on QCI 1 bearers in uplink.

M8012C94

IP_TPUT_TIME_UL_QCI_2

This measurement provides the IP throughput time on QCI 2 bearers in uplink.

M8012C96

IP_TPUT_TIME_UL_QCI_3

This measurement provides the IP throughput time on QCI 3 bearers in uplink.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 65 of 93

Counter ID

Counter Name

Counter Description

M8012C98

IP_TPUT_TIME_UL_QCI_4

This measurement provides the IP throughput time on QCI 4 bearers in uplink.

M8012C100

IP_TPUT_TIME_UL_QCI_5

This measurement provides the IP throughput time on QCI 5 bearers in uplink.

M8012C102

IP_TPUT_TIME_UL_QCI_6

This measurement provides the IP throughput time on QCI 6 bearers in uplink.

M8012C104

IP_TPUT_TIME_UL_QCI_7

This measurement provides the IP throughput time on QCI 7 bearers in uplink.

M8012C106

IP_TPUT_TIME_UL_QCI_8

This measurement provides the IP throughput time on QCI 8 bearers in uplink.

M8012C108

IP_TPUT_TIME_UL_QCI_9

This measurement provides the IP throughput time on QCI 9 bearers in uplink.

12.4.3

ZTE KPI Name User UL Throughput (kbps)

Formula (C374107517*1000+ C374107518)/ C374107519/1000 (UL Aggregated Volume High through Uu For IP Throughput*1000 + UL Aggregated Volume Low through Uu For IP Throughput) / UL Aggregated Time For IP Throughput/1000

Counter ID

Counter Name

C374107517

UL Aggregated Volume High through Uu For IP Throughput

C374107518

UL Aggregated Volume Low through Uu For IP Throughput

C374107519

UL Aggregated Time For IP Throughput

Counter Description This counter counts the total uplink PDCP SDU dead load, not including packets lost at the Uu interface, tail packets, and data completed through one data scheduling. The counter value = the total data / 1000000. This counter counts the total uplink PDCP SDU dead load, not including packets lost at the Uu interface, tail packets, and data completed through one data scheduling. The counter value = the total data % 1000000. This counter counts the uplink service time during which the eNodeB buffer becomes empty from being not empty, not including the data transmission time for tail packets and data completed through one data scheduling.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 66 of 93

12.4.4

Ericsson

KPI Name User UL Throughput (kbps)

Counter Name pmUeThpVolUl

pmUeThpTimeUl

12.5

Formula pmUeThpVolUl/(pmUeThpTimeUl/1000)

Description The UL DRB volume used for UL UE Throughput. It comprises of the MAC SDU volume received on Uu, excluding the volume received in the first 4 data receptions of an UL buffer transfer and the TTI emptying the UL buffer. The UL volume transfer time used for UL UE Throughput. It comprises of time periods from when the 5th MAC SDU data reception of an UL buffer transfer on Uu until the buffer is emptied, excluding the TTI emptying the buffer.

KPI Simulation

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 67 of 93

13.

Cell Uplink Throughput

13.1

Definition

This KPI measures the Cell Throughput in UL for DRB, when the DRB data was scheduled to be transmitted. It represents PDCP level. Note: -

13.2

time for denominator calculated also during no transmission while buffer not empty

Generic Formula

𝐶𝑒𝑙𝑙 𝑈𝐿 𝑇ℎ𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡 =

13.3

UL Data Throughput Volume #Time in which DRB data was required to be scheduled in the uplink

Signaling Flow

n/a

13.4

KPI Formula

13.4.1

Huawei KPI Name Cell UL Throughput (kbps)

Formula ([L.Thrp.bits.UL]/[L.Thrp.Time.Cell.UL.HighPrecision])

Counter Name

Counter Description

L.Thrp.bits.UL

Total uplink traffic volume for PDCP PDUs in a cell

L.Thrp.Time.Cell.UL.HighPrecision

Total duration of uplink data transmission in a cell (with the precision of 1 ms)

13.4.2 Nokia KPI Name Cell UL Throughput 8*(PDCP_SDU_VOL_UL) (kbps) / (ACTIVE_TTI_UL)

Formula

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 68 of 93

Counter ID

Counter Name

Counter Description

M8012C19

PDCP_SDU_VOL_UL

M8012C89

ACTIVE_TTI_UL

The measurement gives an indication of the eUu interface traffic load by reporting the total received PDCP SDU-related traffic volume. This counter provides the number of active TTIs in UL, that is those TTIs with at least one UE scheduled to transmit user plane data.

13.4.3

ZTE KPI Name Cell UL Throughput (kbps)

Formula (C373343804*1000+ C373343805)/ C373343875/1000 (Drb.IpThrouUlVoH*1000+ Drb.IpThrouUlVoL) / UL Traffic Transmission Time/1000

Counter ID

Counter Name

C373343804

Drb.IpThrouUlVoH

C373343805

Drb.IpThrouUlVoL

C373343875

UL Traffic Transmission Time

13.4.4 Ericsson KPI Name Cell UL Throughput (kbps)

Counter Name pmPdcpVolUlDrb pmSchedActivityCellUl

Counter Description The counter provides the part volume of PDCP SDU transmitted by eNodeB to UE on the uplink. The total volume = volume High + Volume Low. The counter provides the other part volume of PDCP SDU transmitted by eNodeB to UE on the uplink. The total volume = volume High + Volume Low. This counter counts the duration from the time data appears in the uplink service buffer to the time the service buffer becomes empty in a measurement period of all eNodeBs. The overlapping time periods of multiple services are counted once.

Formula pmPdcpVolUlDrb/(pmSchedActivityCellUl/1000)

Description The total volume (PDCP SDU) on Data Radio Bearers that has been received in the uplink direction and transmitted over the GTP-U. The aggregated number of ms in which DRB data was required to be scheduled in the uplink.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 69 of 93

13.5

KPI Simulation

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 70 of 93

14.

Cell Uplink Dimensioning Throughput

14.1

Definition

This KPI calculates total uplink traffic volume during the observation of one-hour period. The KPI is calculated on cell level. Unit in kbps.

14.2

Generic Formula Cell UL Dimensioning Throughput = (

14.3

Total Cell UL Traffic Volume [kbit] ) 3600 [s]

Signaling Flow

n/a

14.4

KPI Formula

14.4.1

Huawei KPI Name Cell UL Dimensioning Throughput (Kbps)

Counter Name L.Thrp.bits.UL

Formula L.Thrp.bits.UL / (1000 * 3600)

Counter Description Total uplink traffic volume for PDCP PDUs in a cell

14.4.2 Nokia KPI Name Cell UL (PDCP_SDU_VOL_UL) *8 Dimensioning / Throughput (Kbps) (1000 * 3600)

Formula

Counter ID

Counter Name

Counter Description

M8012C19

PDCP_SDU_VOL_UL

The measurement gives an indication of the eUu interface traffic load by reporting the total received PDCP SDU-related traffic volume.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 71 of 93

14.4.3

ZTE KPI Name Cell UL Dimensioning Throughput (Kbps)

Formula (C373343804*1000+ C373343805) / 3600 (Drb.IpThrouUlVoH*1000 + Drb.IpThrouUlVoL) / 3600

Counter ID

Counter Name

C373343804

Drb.IpThrouUlVoH

C373343805

Drb.IpThrouUlVoL

14.4.4

Counter Description The counter provides the part volume of PDCP SDU transmitted by eNodeB to UE on the uplink.The total volume = volume High + Volume Low. The counter provides the other part volume of PDCP SDU transmitted by eNodeB to UE on the uplink. The total volume = volume High + Volume Low.

Ericsson

KPI Name Cell UL Dimensioning Throughput (Kbps)

Counter Name pmPdcpVolUlDrb

Formula pmPdcpVolUlDrb / 3600

Description The total volume (PDCP SDU) on Data Radio Bearers that has been transferred (UM and AM) in the downlink direction. When carrier aggregation is used, a PDCP SDU can be sent over multiple cells (PCell/SCell(s)). The total volume (PDCP SDU) on Data Radio Be

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 72 of 93

15.

DL Traffic Volume

15.1

Definition

This KPI calculates the total volume (PDCP SDU) on Data Radio Bearers only. Unit in Mbyte.

15.2

Generic Formula

𝐷𝐿 𝑇𝑟𝑎𝑓𝑓𝑖𝑐 𝑉𝑜𝑙𝑢𝑚𝑒 = 𝑇𝑜𝑡𝑎𝑙 𝐷𝐿 𝑣𝑜𝑙𝑢𝑚𝑒 (𝑃𝐷𝐶𝑃 𝑆𝐷𝑈) 𝑜𝑛 𝐷𝑎𝑡𝑎 𝑅𝑎𝑑𝑖𝑜 𝐵𝑒𝑎𝑟𝑒𝑟𝑠 15.3

Signaling Flow

n/a

15.4

KPI Formula

15.4.1

Huawei KPI Name DL Traffic Volume (MByte)

Formula L.Thrp.bits.DL/ (8*1024*1024)

Counter Name L.Thrp.bits.DL

Counter Description Total downlink traffic volume for PDCP SDUs in a cell

15.4.2 Nokia KPI Name Formula DL Traffic Volume (PDCP_SDU_VOL_DL) / (1024 * 1024) (MByte)

Counter ID M8012C20

Counter Name PDCP_SDU_VOL_DL

Counter Description The measurement gives an indication of the eUu interface traffic load by reporting the total transmitted PDCP SDUrelated traffic volume.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 73 of 93

15.4.3

ZTE KPI Name DL Traffic Volume (MByte)

Formula (C373343806*1000000+ C373343807*1000) / (8*1024*1024) (Drb.IpThrouDlVoH*1000000 + Drb.IpThrouDlVoL*1000) / (8*1024*1024)

Counter ID

Counter Name

C373343806

Drb.IpThrouDlVoH

C373343807

Drb.IpThrouDlVoL

15.4.4

Counter Description The counter provides the part volume of PDCP SDU transmitted by eNodeB to UE on the downlink.The total volume = volume High + Volume Low. When the eNodeB get the successful DL TB HARQ feedback and all frag of PDCP SDU related to TB have been transmitted to the air interface successfully,the counter is collected. The counter provides the other part volume of PDCP SDU transmitted by eNodeB to UE on the downlink. The total volume = volume High + Volume Low. When the eNodeB get the successful DL TB HARQ feedback and all frag of PDCP SDU related to TB have been transmitted to the air interface successfully,the counter is collected.

Ericsson

KPI Name DL Traffic Volume (MByte)

Counter Name pmPdcpVolDlDrb

Formula pmPdcpVolDlDrb *1000 /(8*1024*1024)

Description The total volume (PDCP SDU) on Data Radio Bearers that has been transferred (UM and AM) in the downlink direction. When carrier aggregation is used, a PDCP SDU can be sent over multiple cells (PCell/SCell(s)). The total volume (PDCP SDU) on Data Radio Be

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 74 of 93

15.5

KPI Simulation

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 75 of 93

16.

UL Traffic Volume

16.1

Definition

This KPI calculates the total volume (PDCP SDU) on Data Radio Bearers only. Unit in Mbyte.

16.2

Generic Formula

𝑈𝐿 𝑇𝑟𝑎𝑓𝑓𝑖𝑐 𝑉𝑜𝑙𝑢𝑚𝑒 = 𝑇𝑜𝑡𝑎𝑙 𝑈𝐿 𝑣𝑜𝑙𝑢𝑚𝑒 (𝑃𝐷𝐶𝑃 𝑆𝐷𝑈) 𝑜𝑛 𝐷𝑎𝑡𝑎 𝑅𝑎𝑑𝑖𝑜 𝐵𝑒𝑎𝑟𝑒𝑟𝑠 16.3

Signaling Flow

n/a

16.4

KPI Formula

16.4.1

Huawei KPI Name UL Traffic Volume (MByte)

Formula L.Thrp.bits.UL/ (8*1024*1024)

Counter Name L.Thrp.bits.UL

Counter Description Total uplink traffic volume for PDCP PDUs in a cell

16.4.2 Nokia KPI Name Formula UL Traffic Volume (PDCP_SDU_VOL_UL) / (1024 * 1024) (MByte)

Counter ID

Counter Name

Counter Description

M8012C19

PDCP_SDU_VOL_UL

The measurement gives an indication of the eUu interface traffic load by reporting the total received PDCP SDU-related traffic volume.

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 76 of 93

16.4.3

ZTE KPI Name UL Traffic Volume (MByte)

Formula (C373343804*1000000+ C373343805*1000) / (8*1024*1024) (Drb.IpThrouUlVoH*1000000 + Drb.IpThrouUlVoL*1000) / (8*1024*1024)

Counter ID

Counter Name

C373343804

Drb.IpThrouUlVoH

C373343805

Drb.IpThrouUlVoL

16.4.4

Counter Description The counter provides the part volume of PDCP SDU transmitted by eNodeB to UE on the uplink.The total volume = volume High + Volume Low. The counter provides the other part volume of PDCP SDU transmitted by eNodeB to UE on the uplink. The total volume = volume High + Volume Low.

Ericsson

KPI Name Formula UL Traffic Volume (MByte) pmPdcpVolUlDrb *1000 /(8*1024*1024)

Counter Name pmPdcpVolUlDrb

Description The total volume (PDCP SDU) on Data Radio Bearers that has been transferred (UM and AM) in the downlink direction. When carrier aggregation is used, a PDCP SDU can be sent over multiple cells (PCell/SCell(s)). The total volume (PDCP SDU) on Data Radio Be

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 77 of 93

16.5

KPI Simulation

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 78 of 93

17.

DL PRB Utilization

17.1

Definition

This KPI DL PRB utilization is calculated the total number of used PRB pairs by available PRB pairs Note: -

Used DL PRB is using average counter

-

Ericsson only can calculate using weighted average (mid-range value) of PDF counter.

17.2

Generic Formula

𝐷𝐿 𝑃𝑅𝐵 𝑈𝑡𝑖𝑙𝑖𝑧𝑎𝑡𝑖𝑜𝑛 = 100% ∗

17.3

#𝑇𝑜𝑡𝑎𝑙 𝑛𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑢𝑠𝑒𝑑 𝐷𝐿 𝑃𝑅𝐵 𝐴𝑣𝑎𝑖𝑙𝑎𝑏𝑙𝑒 𝑃𝑅𝐵

Signaling Flow

n/a

17.4 17.4.1

KPI Formula Huawei KPI Name

PRB DL Util

Formula L.ChMeas.PRB.DL.Used.Avg/ L.ChMeas.PRB.DL.Avail

Counter Name L.ChMeas.PRB.DL.Used.Avg

Counter Description Average number of used PDSCH PRBs

L.ChMeas.PRB.DL.Avail

Number of available downlink PRBs

17.4.2 Nokia KPI Name Formula PRB DL Util (DL_PRB_UTIL_TTI_MEAN) / 10

Doc. No: NQM/RNQ/Standard/2

LTE RAN KPI Formula

Version: 1.0 Page 79 of 93

Counter ID

Counter Name

Counter Description

M8011C37

DL_PRB_UTIL_TTI_MEAN

The mean value of the DL Physical Resource Block (PRB) use per TTI. The use is defined by the rate of used PRB per TTI. The reported value is 10 times higher than the actual value (for example 5.4 is stored as 54).

17.4.3

ZTE KPI Name

Formula 100* C373424610/ C373424611

PRB DL Util

100* RRU.PrbTotUsedDl / RRU.PrbTotAvalDl

Counter ID

Counter Name

Counter Description

C373424610

RRU.PrbTotUsedDl

It is all available PRBs that eNodeB have assigned for downlink channel.

C373424611

RRU.PrbTotAvalDl

It is PRB number that eNodeB allocates for downlink channel, is equal to the PRB number for system banwidth on the downlink.

17.4.4

Ericsson

KPI Name PRB DL Util

Counter Name pmPrbUtilDl

Formula WeightedAverage(pmPrbUtilDl,[5,15,25,35,45,55,65,75,85,95])

Description A distribution that shows the downlink Physical Resource Block (PRB) pair utilization (total number of used PRB pairs by available PRB pairs) on the Physical Downlink Shared Channel (PDSCH). PDF ranges: [0]: 0 %