Lte Ericsson- Nsn Kpi Mapping_v2.0

Introduction

This document defines and describes the KPI and counter mapping between ericsson and nsn

Sheet: Description:KPI Mapping list for immediate referenceKPI Mapping list for immediate reference

Ericsson L14A FDD / L14A TDD Release KPI mapped with NSN Rl50 / RL 45TD Release

Counter triggering points with call flow diagrams provided for intra enb handover

Counter triggering points with call flow diagrams provided for inter enb handover via x2

Counter triggering points with call flow diagrams provided for inter enb handover via s1

Counter triggering points with call flow diagrams provided for LTE to wcdma handoverCounter triggering points with call flow diagrams provided for LTE to gsm srvcc handoverCounter triggering points with call flow diagrams provided for retainabilityCounter triggering points with call flow diagrams provided for accessibility

1.3 Revision history

v 1.0 First version of Ericsson L13B LTE KPIs mapped to NSN RL 40 Release KPI's

V 2.0 First version of Ericsson L13B LTE KPIs mapped to NSN RL 40 Release KPI's

1.1 Purpose

1.2 Sheet description

Executive Level ( FDD)Executive Level ( TDD)Ericsson -> NSN (FDD)

Ericsson L13B FDD / L13B TDD Release KPI mapped with NSN RL 40 / Rl25 Release ( RL 50 / RL35 Release KPI also provided for some special cases )

Counter Mapping FDDEricsson L13B FDD / L13B TDD Release Counters mapped with NSN RL 40 / Rl25 Release ( RL 50 / RL35 Release Counters which are related with Mapped KPI's

Ericsson -> NSN (TDD)

Counter Mapping TDDEricsson L14A FDD / L14A TDD Release Counters mapped with NSN Rl50 / RL 45TD Release Counters which are related with Mapped KPI's

Intra eNB Handover

Inter eNB Handover via x2

Inter eNB Handover via s1

LTE - WCDMA HOLTE - GSM SRVCCretainabilityaccessibility

This document defines and describes the KPI and counter mapping between ericsson and nsn

KPI Mapping list for immediate referenceKPI Mapping list for immediate reference

Ericsson L14A FDD / L14A TDD Release KPI mapped with NSN Rl50 / RL 45TD Release

Counter triggering points with call flow diagrams provided for intra enb handover

Counter triggering points with call flow diagrams provided for inter enb handover via x2

Counter triggering points with call flow diagrams provided for inter enb handover via s1

Counter triggering points with call flow diagrams provided for LTE to wcdma handoverCounter triggering points with call flow diagrams provided for LTE to gsm srvcc handoverCounter triggering points with call flow diagrams provided for retainabilityCounter triggering points with call flow diagrams provided for accessibility

Comments Rev. date:

January 9, 2014

March 24,2014

Ericsson L13B FDD / L13B TDD Release KPI mapped with NSN RL 40 / Rl25 Release ( RL 50 / RL35 Release KPI also

Ericsson L13B FDD / L13B TDD Release Counters mapped with NSN RL 40 / Rl25 Release ( RL 50 / RL35 Release

Ericsson L14A FDD / L14A TDD Release Counters mapped with NSN Rl50 / RL 45TD Release Counters which are related

Counter mapping revised.Tuning completed for Mobility success rate with added new features Load balancing and MBMS

Author

M.Mayilvaganan([email protected])

KPI Class KPI Name

Availability

Availability

Partial Cell Availability ( Manual Blocking time excluded )

Partial Cell Availability ( Node restart excluded . Manual blocking time included)

Mobility

Mobility

Accessibility

Mobility Success Rate ( Considering LTE to WCDMA HO alone in non-LTE system )

Mobility Success Rate ( Considering LTE to GSM SRVCC alone in non-LTE system )

Initial E-RAB Establishment Success Rate

Accessibility

Accessibility

Accessibility

Initial E-RAB Establishment Success Rate Per QCI

Initial E-RAB Establishment Success Rate for Emergency Calls

eMBMS Establishment Success Rate

Accessibility

Accessibility

Accessibility

Added E-RAB Establishment Success Rate

Added E-RAB Establishment Success Rate per QCI

Added E-RAB Establishment Success Rate for Emegency Calls

Accessibility

Accessibility

Integrity Downlink Latency ( ms)

A ) Avg.Number of RRC connected Users

B ) Avg.Number of RRC connected Users

Integrity Downlink Latency Per QCI

Integrity Avg. Downlink UE Throughput

Integrity Avg. Downlink Cell Throughput

Integrity Downlink Throughput Per QCI

Integrity Avg. Uplink UE Throughput

Integrity Avg. Uplink Cell Throughput

Integrity Uplink Throughput ,LCG

Integrity

Integrity

Downlink Packet Error loss Rate , Cell ( % )

Uplink Packet Error loss Rate , Cell ( % )

Retainability E-RAB Retainability ( drops /s )

RetainabilityE-RAB Retainability per QCI ( drops /s )

RetainabilityE-RAB Retainability _Cell Level ( % )

KPI Formula Unit O - O Comparision

%

%

Cell Availability ( % ) = 100* [ ( N * L * 900 ) - ∑ pmCellDownTimeAuto ] / [ ( N * L * 900 ) - ∑ pmCellDownTimeMan ]

E/// Sampling Interval : 1sNSN Sampling Interval : 10s

Cell Availability ( % ) = 100*( ( N * L * 900 ) - ∑( pmCellDownTimeAuto + pmCellDownTimeMan ) / ( N * L * 900 ) )


%

%

%

Mobility Success Rate ( % ) = 100* [ ( pmHoPrepSuccLteIntraF + pmHoPrepSuccLteInterF + pmHoPrepSuccWcdma ) / ( pmHoPrepAttLteIntraF + pmHoPrepAttLteInterF + pmHoPrepAttWcdma ) ] * [ ( pmHoExeSuccLteIntraF + pmHoExeSuccLteInterF + pmHoExeSuccWcdma ) / ( pmHoExeAttLteIntraF + pmHoExeAttLteInterF + pmHoExeAttWcdma) ]

1. No Preparation Phase counters for InterFrequency HO type in NSN

2. Intra Frequency ( Intra eNB ,Inter eNB via X2 ,Inter eNB via S1 ) ,Inter Frequency ( Intra eNB ,Inter eNB via X2 ,Inter eNB via S1 ) ,IRAT HO Type Preparation Phase Successes taken as input for Execution Phase Attempts in NSN ( Causes difference in HO time as compared with E/// )

3. Deviations observed in Counter Triggering Points as compared with NSN ( Refer : Counter Mapping )

Mobility Success Rate ( % ) = 100* [ ( pmHoPrepSuccLteIntraF + pmHoPrepSuccLteInterF + pmHoPrepSucc ) / ( pmHoPrepAttLteIntraF + pmHoPrepAttLteInterF + pmHoPrepAtt ) ] * [ ( pmHoExeSuccLteIntraF + pmHoExeSuccLteInterF + pmHoExeSucc ) / ( pmHoExeAttLteIntraF + pmHoExeAttLteInterF + pmHoExeAtt) ]

1. No Preparation Phase counters for InterFrequency HO & LTE to GSM SRVCC HO type in NSN

2. Intra Frequency ( Intra eNB ,Inter eNB via X2 ,Inter eNB via S1 ) ,Inter Frequency ( Intra eNB ,Inter eNB via X2 ,Inter eNB via S1 ) ,SRVCC HO Type Preparation Phase Successes taken as input for Execution Phase Attempts in NSN ( Causes difference in HO time as compared with E/// )

3. Deviations observed in Counter Triggering Points as compared with NSN ( Refer : Counter Mapping )

Initial E-RAB Establishment Success Rate ( %) = 100 * [ pmRrcConnEstabSucc / ( pmRrcConnEstabAtt - pmRrcConnEstabAttReatt ) ] * [ pmS1SigConnEstabSucc / pmS1SigConnEstabAtt ] * [ pmErabEstabSuccInit / pmErabEstabAttInit ]

1 . Ericsson subtract repetitive RRC attempts from the same UE in denominator .

2.In NSN , If a UE (erroneously) sends RRC Connection message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted ( Signalling connection attempt counters will not update repetetive attempts from Same UE final message as reference) 3.NSN's own Initial E-RAB setup success Ratio LTE_5112b describes the setup success ratio of the elementaryinitial E-RAB setup procedure.It indicates the E-UTRAN contribution to network accessibilityfor the end-user, not the whole end-to-end service accessibility

%

%

%

Initial E-RAB Establishment Success Rate Per QCI ( %) = 100 * [ ( pmRrcConnEstabSuccMod + pmRrcConnEstabSuccMta ) / ( pmRrcConnEstabAttMod + pmRrcConnEstabAttMta - pmRrcConnEstabAttReattMod -pmRrcConnEstabAttReattMta ) ] * [ ( pmS1SigConnEstabSuccMod + pmS1SigConnEstabSuccMta ) / ( pmS1SigConnEstabAttMod + pmS1SigConnEstabAttMta ) ] * [ ( pmErabEstabSuccInitQci / pmErabEstabAttInitQci ) ]

1. Direct Mapping not possible due to non availability of equivalent counter2. In NSN Counters NOT available for RRC connection establishments under different causes .

3. In NSN Counters NOT available for Initial signalling connection establishments under different causes.

4. In NSN Initial EPS bearer setup counters Mapping available for all QCI's ( GBR & NON- GBR )(Refer : Counter Mapping )

Initial E-RAB Establishment Success Rate for Emergency Calls ( % ) = 100 *[ ( pmRrcConnEstabSuccEm / ( pmRrcConnEstabAttEm -pmRrcConnEstabAttReattEm ) ] * [ ( pmS1SigConnEstabSuccEm / ( pmS1SigConnEstabAttEm ) ] * [ ( pmErabEstabSuccInitArp / pmErabEstabAttInitArp) ]

1. Direct Mapping not possible due to non availability of equivalent counter2.In NSN ,Counters NOT available for Initial signalling connection establishments under cause Emergency4. In NSN ,Counters not avaible for different APR priority level(Refer : Counter Mapping )

MBMS Establishment Success Rate = 100 * ( pmMBMSSessionEstabSucc / pmMBMSSessionEstabAtt )

Equivalent KPI & Counters NOT available in NSN

%

%

%

Added E-RAB Establishment Success Rate = 100 * ( pmErabEstabSuccAdded / pmErabEstabAttAdded )

In NSN , all initial E-RAB setup attemps & establishments subtracted from total EPS bearer attemps for 1 to 1 mapping

Added E-RAB Establishment Success Rate Per QCI = 100 * ( pmErabEstabSuccAddedQci / pmErabEstabAttAddedQci )

Equivalent counters NOT available for Non GBR QCI 's .

Added E-RAB Establishment Success Rate Per QCI = 100 * ( pmErabEstabSuccAddedArp / pmErabEstabAttAddedArp )


#

#

ms

Avg.Number of RRC connected Users =[ pmRrcConnLevSum / pmRrcConnLevSamp ] / L

1. Equivalent KPI available from NSN RL 50 release 2. Sampling Interval :E/// - 5 sNSN - 1s


1 . In RL 40 Release euivalent counter is available for direct mapping2. Sampling Interval :E/// - 5 sNSN - 4s

DL Latency ( ms) = [ pmPdcpLatTimeDl / pmPdcpLatPktTransDl ]

1 ) E/// dividing latency counter from number of packets transmitted where as in NSN direct average latency KPI available .2 ) In NSN , Latency KPI can be fetched in Network & eNB level . Cell Level latency NOT possible.

ms

Kbps

Kbps

DL Latency Per QCI ( ms) = [ pmPdcpLatTimeDlQci / pmPdcpLatPktTransDlQci ]

1 ) In NSN , Latency KPI available for individual QCI's2 ) In NSN , Latency KPI can be fetched in Network & eNB level . Cell Level latency NOT possible.

Avg. DL UE Throughput ( kbps ) = ( pmPdcpVolDlDrb - pmPdcpVolDlDrbLastTTI ) / ( pmUeThpTimeDl / 1000 )

Direct Mapping NOT possible. NSN only supporting Cell level throughput

Avg. DL Cell Throughput ( kbps ) = ( pmPdcpVolDlDrb ) / ( pmSchedActivityCellDl / 1000 )

RL 50 Release KPI ( LTE_5292d) more suitable for mapping .

Kbps

Kbps

Kbps

Avg. DL Throughput per QCI ( kbps ) = ( pmPdcpVolDlDrbQci - pmPdcpVolDlDrbLastTTIQci ) / ( pmDrbThpTimeDlQci / 1000 )

In NSN , only QCI 1 GBR DRB throughput available

Avg.UL UE Throughput ( kbps ) = ( pmPdcpVolUlDrb - pmPdcpVolUlDrbLastTTI ) / ( pmUeThpTimeUl / 1000 )


Avg. UL Cell Throughput ( kbps ) = ( pmPdcpVolUlDrb ) / ( pmSchedActivityCellUl / 1000 )


Kbps

%

%

Uplink Throughput ,LCG ( Kbps ) = ( pmLcgThpVolUlLcg / ( pmLcgThpTimeUlLcg /1000 )


Downlink Packet Error loss Rate , Cell ( % ) =100* [ ( pmPdcpPktDiscDlPelr +pmPdcpPktDiscDlPelrUu +pmPdcpPktDiscDlHo ) / ( pmPdcpPktReceivedDl -pmPdcpPktFwdDl ) ]

Downlink Packet Error loss Rate , Cell ( % ) =100* [ ( pmPdcpPktLostUl ) / ( pmPdcpPktLostUl +pmPdcpPktReceivedUl ) ]

drops/s

drops/s

E-RAB Retainability ( drops /s ) = ( pmErabRelAbnormalEnbAct +pmErabRelAbnormalMmeAct ) /pmSessionTimeUe

1. Actual NSN formula LTE_5581a & LTE_5581b configured with UNIT #/min & # /h .For Exact mapping remove the 60 & 3600 from denominator of both the formulas .

2. NSN formula only deals with abnormal drops with release cause "Radio connection with UE lost " whereas in E/// formula includes all abnormal (Radio Connection with UE is lost; Handover failure for the UE; Non admitted E-RABs by target cell at successful handover for the UE; ) drops.

3. Equivalent MME initiated drops NOT available in NSN

E-RAB Retainability ( drops /s ) = ( pmErabRelAbnormalEnbActQci +pmErabRelAbnormalMmeActQci ) /pmSessionTimeDrbQci

1. Actual NSN formula configured with UNIT #/min & # /h .For Exact mapping remove the 60 & 3600 from denominator of both the formulas .



%

E-RAB Retainability ( %) = ( pmErabRelAbnormalEnbAct +pmErabRelAbnormalMmeAct ) / ( pmErabRelAbnormalEnb + pmErabRelNormalEnb + pmErabRelMme )

1. NSN eNB initiated Abnormal E-RAB releases having the cause split up of RNL / TNL / OTH reasons.


3. Closest Match

KPI ID KPI Name

LTE_5001a

LTE_5002a

Cell Availability

Cell Availability excluding BLU

Custom KPI Mobility Success Rate


Custom KPIInitial E-RAB Establishment Success Rate

Custom KPI

Custom KPI



Custom KPI

Custom KPI



LTE_5242a

M8001C199 RRC Connected UEs Avg

LTE_5134a

E-UTRAN Average RRC Connected Ues

E-UTRAN Average Latency Downlink

LTE_5138a ( QCI 1 ) ,LTE_5556a ( QCI 2),LTE_5557a ( QCI 3) ,LTE_5558a ( QCI 4) ,LTE_5139a ( non - GBR QCI's

E-UTRAN Average Latency Downlink for non GBR DRBs & GBR DRB's

LTE_5292c ( RL 40 ) -----------------------------------------LTE_5292d ( RL 50 )

E-UTRAN Average PDCP Layer Active Cell Throughput DL

LTE_5293c

E-UTRAN average PDCP Layer Active Cell Throughput DL for QCI1 DRBs

LTE_5289c ( RL 40 ) -----------------------------------------LTE_5289d ( RL 50 )

E-UTRAN Average PDCP Layer Active Cell Throughput UL

LTE_5304a

LTE_5310a

E-UTRAN PDCP SDU Loss Ratio in the DL

E-UTRAN PDCP SDU Loss Ratio in the UL

( LTE_5581a / 60 )

E-UTRAN E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost

( LTE_5582a / 60 ) & ( LTE_5583a / 60 ) &( LTE_5584a / 60 ) &( LTE_5585a / 60 ) &( LTE_5586a / 60 ) &

E-UTRAN E-RAB Retainability Rate per QCI , RAN View, RNL Failure with UE Lost

Custom KPIE-RAB Retainability _Cell Level ( % )

KPI formula Unit

%

%

100*sum([SAMPLES_CELL_AVAIL{71488, 7, 1}])/sum([DENOM_CELL_AVAIL{71487, 7, 1}]-[SAMPLES_CELL_PLAN_UNAVAIL{71489, 7, 1}])

100*sum([SAMPLES_CELL_AVAIL{71488, 7, 1}])/sum([DENOM_CELL_AVAIL{71487, 7, 1}])

%

%

%

100 * [ ( ATT_INTRA_ENB_HO +ATT_INTER_ENB_HO +INTER_ENB_S1_HO_ATT + ISYS_HO_ATT ) / ( INTRA_ENB_HO_PREP +INTER_ENB_HO_PREP +INTER_ENB_S1_HO_PREP + ISYS_HO_PREP) ] * [ (SUCC_INTRA_ENB_HO +SUCC_INTER_ENB_HO +INTER_ENB_S1_HO_SUCC +HO_INTFREQ_SUCC +ISYS_HO_SUCC ) / ( ATT_INTRA_ENB_HO +ATT_INTER_ENB_HO +INTER_ENB_S1_HO_ATT +ISYS_HO_ATT +HO_INTFREQ_ATT) ]

100 * [ ( ATT_INTRA_ENB_HO +ATT_INTER_ENB_HO +INTER_ENB_S1_HO_ATT ) / ( INTRA_ENB_HO_PREP +INTER_ENB_HO_PREP +INTER_ENB_S1_HO_PREP ) ] * [ (SUCC_INTRA_ENB_HO +SUCC_INTER_ENB_HO +INTER_ENB_S1_HO_SUCC +HO_INTFREQ_SUCC +ISYS_HO_GERAN_SRVCC_SUCC) / ( ATT_INTRA_ENB_HO +ATT_INTER_ENB_HO +INTER_ENB_S1_HO_ATT +ISYS_HO_GERAN_SRVCC_ATT +HO_INTFREQ_ATT) ]

100 * [ ( SIGN_CONN_ESTAB_COMP ) / ( SIGN_CONN_ESTAB_ATT_MO_S +SIGN_CONN_ESTAB_ATT_MT +SIGN_CONN_ESTAB_ATT_MO_D +SIGN_CONN_ESTAB_ATT_OTHERS + SIGN_CONN_ESTAB_ATT_EMG ) ] * [ S1AP_NAS_DOWNLINK / UE_LOG_S1_SETUP ] * [ INI_CONT_STP_COMP / INI_CONT_STP_REQ ]

%

%

100 * [ ( X ) / ( SIGN_CONN_ESTAB_ATT_MT +SIGN_CONN_ESTAB_ATT_MO_D + ) ] * [ X / X ] * [ ( EPS_BEARER_STP_COM_INI_QCI1+ EPS_BEARER_STP_COM_INI_QCI_2+ EPS_BEARER_STP_COM_INI_QCI_3+ EPS_BEARER_STP_COM_INI_QCI_4+

EPS_BEAR_STP_COM_INI_NON_GBR ) / ( EPS_BEARER_STP_ATT_INI_QCI1 + EPS_BEARER_STP_ATT_INI_QCI_2 + EPS_BEARER_STP_ATT_INI_QCI_3 + EPS_BEARER_STP_ATT_INI_QCI_4+ EPS_BEAR_STP_ATT_INI_NON_GBR ) ]

100 * [ ( SIGN_CONN_ESTAB_COMP_EMG ) / ( SIGN_CONN_ESTAB_ATT_EMG ) ] * [ X / X ] * [ X / X ]

%

%

Added E-RAB Establishment Success Rate = 100 * [ EPS_BEARER_SETUP_COMPLETIONS - ( EPS_BEARER_STP_COM_INI_QCI1+ EPS_BEARER_STP_COM_INI_QCI_2 + EPS_BEARER_STP_COM_INI_QCI_3 + EPS_BEARER_STP_COM_INI_QCI_4 + EPS_BEAR_STP_COM_INI_NON_GBR ) ] / [ EPS_BEARER_SETUP_ATTEMPTS - ( EPS_BEARER_STP_ATT_INI_QCI1 + EPS_BEARER_STP_ATT_INI_QCI_2+ EPS_BEARER_STP_ATT_INI_QCI_3+ EPS_BEARER_STP_ATT_INI_QCI_4 + EPS_BEAR_STP_ATT_INI_NON_GBR ) ]

Added E-RAB Establishment Success Rate = 100 * [ EPS_BEAR_SET_COM_ADDIT_QCI1+ EPS_BEARER_STP_COM_ADD_QCI_2+ EPS_BEARER_STP_COM_ADD_QCI_3 +EPS_BEARER_STP_COM_ADD_QCI_4 ] / [ EPS_BEAR_SET_ATT_ADD_QCI_1+ EPS_BEARER_STP_ATT_ADD_QCI_2+ EPS_BEARER_STP_ATT_ADD_QCI_3+EPS_BEARER_STP_ATT_ADD_QCI_4 ]

#

sum( RRC_CONN_UE_AVG ) #

avg( PDCP_SDU_DELAY_DL_DTCH_MEAN ) ms

sum(SUM_RRC_CONN_UE )/sum(DENOM_RRC_CONN_UE)

ms

Kbps

Avg ( PDCP_RET_DL_DEL_MEAN_QCI_1 , PDCP_RET_DL_DEL_MEAN_QCI_2, PDCP_RET_DL_DEL_MEAN_QCI_3,PDCP_RET_DL_DEL_MEAN_QCI_4,PDCP_RET_DL_DEL_MEAN_NON_GBR )

avg( PDCP_DATA_RATE_MEAN_DL ) [ RL 40 ]

------------------------------------------------------------8 * sum( PDCP_SDU_VOL_DL ) /sum( ACTIVE_TTI_DL ) [ RL 50 ]

avg (PDCP_DATA_RATE_MEAN_DL_QCI_1 ) Kbps

Kbps

avg( PDCP_DATA_RATE_MEAN_UL ) [ RL 40 ]

------------------------------------------------------------8 * sum( PDCP_SDU_VOL_UL ) /sum( ACTIVE_TTI_UL ) [ RL 50 ]

%

%

100 * sum( PDCP_SDU_LOSS_DL ) / sum( PDCP_SDU_DL + PDCP_SDU_LOSS_DL )

100 * sum(PDCP_SDU_LOSS_UL ) / sum( PDCP_SDU_UL + PDCP_SDU_LOSS_UL)

# / s

# / s

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 )/ sum(ERAB_IN_SESSION_TIME_QCI1 + ERAB_IN_SESSION_TIME_QCI2 + ERAB_IN_SESSION_TIME_QCI3 + ERAB_IN_SESSION_TIME_QCI4 + ERAB_IN_SESSION_TIME_NON_GBR )

( ERAB_REL_ENB_ACT_QCI1 / ERAB_IN_SESSION_TIME_QCI1 ) & ( ERAB_REL_ENB_ACT_QCI2 / ERAB_IN_SESSION_TIME_QCI2 ) & ( ERAB_REL_ENB_ACT_QCI3 / ERAB_IN_SESSION_TIME_QCI3 ) & (ERAB_REL_ENB_ACT_QCI4 / ERAB_IN_SESSION_TIME_QCI4 ) & ( ERAB_REL_ENB_ACT_NON_GBR / ERAB_IN_SESSION_TIME_NON_GBR )

%

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 )/ sum(ENB_EPS_BEARER_REL_REQ_RNL + ENB_EPS_BEARER_REL_REQ_OTH + ENB_EPS_BEARER_REL_REQ_TNL + ENB_EPS_BEARER_REL_REQ_NORM + ENB_EPSBEAR_REL_REQ_RNL_REDIR + EPC_EPS_BEARER_REL_REQ_NORM +EPC_EPS_BEARER_REL_REQ_DETACH )

KPI Class KPI Name

Availability

Availability

Mobility



Mobility Success Rate ( Considering LTE to WCDMA HO alone in non-LTE system )

Mobility

Accessibility

Mobility Success Rate ( Considering LTE to GSM SRVCC alone in non-LTE system )


Accessibility

Accessibility

Accessibility

Accessibility





Accessibility

Accessibility

Accessibility

Accessibility













Integrity

Integrity




Retainability

Retainability

E-RAB Retainability per QCI ( drops /s )

E-RAB Retainability _Cell Level ( % )

Counters used in KPI KPI Formula

pmCellDownTimeAuto ;pmCellDownTimeMan




pmHoPrepSuccLteIntraF ;pmHoPrepSuccLteInterF ;pmHoPrepSuccWcdma (MO Class : UtranCellRelation );pmHoPrepAttLteIntraF ;pmHoPrepAttLteInterF ;pmHoPrepAttWcdma (MO Class : UtranCellRelation );pmHoExeSuccLteIntraF ;pmHoExeSuccLteInterF ;pmHoExeSuccWcdma (MO Class : UtranCellRelation );pmHoExeAttLteIntraF ;pmHoExeAttLteInterF ;pmHoExeAttWcdma (MO Class : UtranCellRelation ) ;

Mobility Success Rate ( % ) = 100* [ ( pmHoPrepSuccLteIntraF + pmHoPrepSuccLteInterF + pmHoPrepSuccWcdma ) / ( pmHoPrepAttLteIntraF + pmHoPrepAttLteInterF + pmHoPrepAttWcdma ) ] * [ ( pmHoExeSuccLteIntraF + pmHoExeSuccLteInterF + pmHoExeSuccWcdma ) / ( pmHoExeAttLteIntraF + pmHoExeAttLteInterF + pmHoExeAttWcdma) ]

pmHoPrepSuccLteIntraF ;pmHoPrepSuccLteInterF ;pmHoPrepSucc (MO Class : UtranCellRelation , GeranCellRelation ) ;pmHoPrepAttLteIntraF ;pmHoPrepAttLteInterF ;pmHoPrepAtt (MO Class : UtranCellRelation , GeranCellRelation ) ;pmHoExeSuccLteIntraF ;pmHoExeSuccLteInterF ;pmHoExeSucc (MO Class : UtranCellRelation , GeranCellRelation ) ;pmHoExeAttLteIntraF ;pmHoExeAttLteInterF ;pmHoExeAtt (MO Class : UtranCellRelation , GeranCellRelation ) ;

Mobility Success Rate ( % ) = 100* [ ( pmHoPrepSuccLteIntraF + pmHoPrepSuccLteInterF + pmHoPrepSucc ) / ( pmHoPrepAttLteIntraF + pmHoPrepAttLteInterF + pmHoPrepAtt ) ] * [ ( pmHoExeSuccLteIntraF + pmHoExeSuccLteInterF + pmHoExeSucc ) / ( pmHoExeAttLteIntraF + pmHoExeAttLteInterF + pmHoExeAtt) ]

pmRrcConnEstabSucc ;pmRrcConnEstabAtt ;pmRrcConnEstabAttReatt ;pmS1SigConnEstabSucc ;pmS1SigConnEstabAtt ;pmErabEstabSuccInit ;pmErabEstabAttInit ;


pmRrcConnEstabSuccMod ;pmRrcConnEstabSuccMta ;pmRrcConnEstabAttMod ;pmRrcConnEstabAttMta ;pmRrcConnEstabAttReattMod ;pmRrcConnEstabAttReattMta ;pmS1SigConnEstabSuccMod ;pmS1SigConnEstabSuccMta ;pmS1SigConnEstabAttMod ;pmS1SigConnEstabAttMta ;pmErabEstabSuccInitQci ;pmErabEstabAttInitQci ;


pmRrcConnEstabSuccEm pmRrcConnEstabAttEmpmRrcConnEstabAttReattEmpmS1SigConnEstabSuccEmpmS1SigConnEstabAttEm pmErabEstabSuccInitArppmErabEstabAttInitArp


pmMBMSSessionEstabSucc ;pmMBMSSessionEstabAtt ;


pmErabEstabSuccAdded ;pmErabEstabAttAdded ;


pmErabEstabSuccAddedQci ;pmErabEstabAttAddedQci ;


pmErabEstabSuccAddedArp ; pmErabEstabAttAddedArp ;


pmRrcConnLevSum ;pmRrcConnLevSamp ;L = Number of Cells




pmPdcpLatTimeDl ;pmPdcpLatPktTransDl ;


pmPdcpLatTimeDlQci ;pmPdcpLatPktTransDlQci ;


pmPdcpVolDlDrb ;pmPdcpVolDlDrbLastTTI ;pmUeThpTimeDl ;


pmPdcpVolDlDrb ;pmSchedActivityCellDl ;


pmPdcpVolDlDrbQci ;pmPdcpVolDlDrbLastTTIQci ;pmDrbThpTimeDlQci ;


pmPdcpVolUlDrb ;pmPdcpVolUlDrbLastTTI ;pmUeThpTimeUl ;


pmPdcpVolDUlDrb ;pmSchedActivityCellUl ;


pmLcgThpVolUlLcg ;pmLcgThpTimeUlLcg ;


pmPdcpPktDiscDlPelr ;pmPdcpPktDiscDlPelrUu ;pmPdcpPktDiscDlHo ;pmPdcpPktReceivedDl ;pmPdcpPktFwdDl ;


pmPdcpPktLostUl ;pmPdcpPktReceivedUl ;


pmErabRelAbnormalEnbAct ;pmErabRelAbnormalMmeAct ;pmSessionTimeUe ;


pmErabRelAbnormalEnbActQci ;pmErabRelAbnormalMmeActQci ;pmSessionTimeDrbQci ;


pmErabRelAbnormalEnbAct ;pmErabRelAbnormalMmeAct ;pmErabRelAbnormalEnb ;pmErabRelNormalEnb ;pmErabRelMme ;


Comments_E/// Unit

%

%

%

1) Used counters Incremented by one each second ( 1 s)

2 ) Counters will be incremented when the RBS is operational.



1. Counters pmHoPrepSuccWcdma, pmHoPrepAttWcdma, pmHoExeSuccWcdma & pmHoExeAttWcdma refer to LTE to WCDMA HO and are NOT parents of the Corresponding LTE handover counters.

%

%

Counters pmHoPrepSucc, pmHoPrepAtt, pmHoExeSucc & pmHoExeAtt refer to LTE to GSM SRVCC and are NOT parents of the Corresponding LTE handover counters.

%

%

Accessibility success rate for end-user eMBMS %

%

The impact of multiple E-RABs in the Initial context setup procedureis not considered in the RRC and S1 signalling part contribution.

The accessibility success rate for emergency callsthat are carried by E-RABs included in the Initial UE Context setup procedure.The counters are on cell level and per ARP (hence only include the ARP rangethat defines Emergency)

Accessibility success rate for end-user services which is carried by E-RABsincluded in the E-RAB setup procedure

%

%

#

#

ms

ms

Accessibility success rate for end-user services which is carried by E-RABsincluded in the E-RAB setup procedure per QCI

Accessibility success rate for emergency calls which is carried by E-RABsincluded in the E-RAB setup procedure

This KPI measures the impact on the end user. NOTE that the latency willincrease with more instantaneously active UEs and will also depend on thescheduling algorithm(s) being used.

This KPI measures the impact on the end user. NOTE that the latency willincrease with more instantaneously active UEs and will also depend on thescheduling algorithm(s) being used, especially for the specific QCI.

Kbps

Kbps

Kbps

Kbps

1 . For traffic, which uses small SDU (e.g. VoLTE), the throughputmay not be a good measurement to evaluate performance, sincemost of the traffic may only use a single TTI and may be countedin pmPdcpVolDlDrbLastTti leaving minimal net volume if any, on thenumerator.2. For cases where pmUeThpTimeDl is small and / or wherepmPdcpVolDlDrb is similar magnitude to pmPdcpVolDlDrbLastTti(causing a small numerator from two large values), caution should beused in using the metric as the result may be ill-conditioned.

1. In many early deployments with a small number of simultaneous users (at TTI granularity), it is likely that per-UE throughput will be greater than cell throughput. However as the market matures and there are consequently moresimultaneous users (at TTI granularity), then it is likely that per-UE throughput will reduce, while cell throughput will show minimal change (or possibly slight increase) and thus cell throughput will exceed the per-UE throughput.

2.If DL Carrier Aggregation is active, the PDCP counters (volume & time) for a cell will reflect both its own Pcell traffic and also its own traffic carried on a different Scell. It will NOT show any traffic which this cell supports as an Scell

1. This KPI measures the impact on the end user. DL Throughput for both AM and UM for end-user services (defined by QCI)

2.Usually Throughput may not be a good measurement to evaluateperformance on services that uses RLC unacknowledged mode (since they are usually of the delay sensitive type).For QCI, which use small SDU (e.g. VoLTE), the throughput may not be a good measurement to evaluate performance, since most of the traffic may only use a single TTI and may be counted in pmPdcpVolDlDrbLastTtiQci leaving minimal net volume if any, on the numerator.

1. This KPI measures the impact on the end user. For traffic which use small SDU(e.g. VoLTE), the throughput may not be a good measurement to evaluate performance, since most of the traffic may only use a single TTI and may be excluded from the counters.2.For traffic, which uses small SDU (e.g. VoLTE), the throughput may not be a good measurement to evaluate performance, since most of the traffic may only use a single TTI and may be counted in the "LastTti" leaving minimal net volume if any, on the numerator.

Kbps

Kbps

%

%

drops/s

DL packet error loss rate for the UE is given by the following equation.The counters are all on cell level,

Since the KPI measures the impact of the network on the enduser, it also includes releases initiated by the MME. To observe theimpact of the RBS only, remove the pmErabRelAbnormalMmeActfrom the formula. The contribution of several components includingpmErabRelAbnormalEnbActTnFail and pmErabRelAbnormalEnbActCdtare not part of the 3GPP 32.450 definition of the KPI. However,Ericsson thinks it is important to include these cases even if there is no S1AP messages for these cases (the 32.425 have its triggers built on S1AP triggers).To achieve the number of minutes per drop, the multiplicative inverse of the E-RAB Retainability together with unit transformation from seconds to minutes can be used.

drops/s

%

To achieve the number of minutes per drop, the multiplicative inverse of the E-RAB Retainability together with unit transformation from seconds to minutes can be used

O - O Comparision KPI ID KPI Name

LTE_5001a

LTE_5002a

Cell Availability





1. No Preparation Phase counters for InterFrequency HO type in NSN

2. Intra Frequency ( Intra eNB ,Inter eNB via X2 ,Inter eNB via S1 ) ,Inter Frequency ( Intra eNB ,Inter eNB via X2 ,Inter eNB via S1 ) ,IRAT HO Type Preparation Phase Successes taken as input for Execution Phase Attempts in NSN ( Causes difference in HO time as compared with E/// )


Custom KPI

1. No Preparation Phase counters for InterFrequency HO & LTE to GSM SRVCC HO type in NSN

2. Intra Frequency ( Intra eNB ,Inter eNB via X2 ,Inter eNB via S1 ) ,Inter Frequency ( Intra eNB ,Inter eNB via X2 ,Inter eNB via S1 ) ,SRVCC HO Type Preparation Phase Successes taken as input for Execution Phase Attempts in NSN ( Causes difference in HO time as compared with E/// )




Custom KPI

Custom KPI

Custom KPI










Custom KPI

LTE_5242a


LTE_5134a




1. Equivalent KPI available from NSN RL 50 release 2. Sampling Interval :E/// - 5 sNSN - 1s


1 . In RL 40 Release euivalent counter is available for direct mapping2. Sampling Interval :E/// - 5 sNSN - 4s






LTE_5293c



LTE_5292c ( RL 40 ) -----------------------------------------LTE_5292d ( RL 50 )





LTE_5304a

LTE_5310a

( LTE_5581a / 60 )


LTE_5289c ( RL 40 ) -----------------------------------------LTE_5289d ( RL 50 )









Custom KPI








3. Closest Match


Counters used in KPI

M8020C3:SAMPLES_CELL_AVAILM8020C4:SAMPLES_CELL_PLAN_UNAVAILM8020C6:DENOM_CELL_AVAIL

M8020C3:SAMPLES_CELL_AVAILM8020C6:DENOM_CELL_AVAIL

INTRA_ENB_HO_PREP ( M8009C2 ) ;INTER_ENB_HO_PREP ( M8014C0 ) ;INTER_ENB_S1_HO_PREP (M8014C14 ) ;ATT_INTRA_ENB_HO ( M8009C6 ) ;ATT_INTER_ENB_HO ( M8014C6 ) ;INTER_ENB_S1_HO_ATT (M8014C18) ;SUCC_INTRA_ENB_HO ( M8009C7) ;SUCC_INTER_ENB_HO ( M8014C7 ) ;INTER_ENB_S1_HO_SUCC (M8014C19) ;HO_INTFREQ_ATT ( M8021C0 ) ;HO_INTFREQ_SUCC ( M8021C2 ) ;ISYS_HO_PREP ( M8016C14 ) ;ISYS_HO_ATT ( M8016C21 ) ;ISYS_HO_SUCC ( M8016C23 ) ;ISYS_HO_GERAN_SRVCC_ATT ( M8016C33 ) ;ISYS_HO_GERAN_SRVCC_SUCC ( M8016C34 ) ;

INTRA_ENB_HO_PREP ( M8009C2 ) ;INTER_ENB_HO_PREP ( M8014C0 ) ;INTER_ENB_S1_HO_PREP (M8014C14 ) ;ATT_INTRA_ENB_HO ( M8009C6 ) ;ATT_INTER_ENB_HO ( M8014C6 ) ;INTER_ENB_S1_HO_ATT (M8014C18) ;SUCC_INTRA_ENB_HO ( M8009C7) ;SUCC_INTER_ENB_HO ( M8014C7 ) ;INTER_ENB_S1_HO_SUCC (M8014C19) ;HO_INTFREQ_ATT ( M8021C0 ) ;HO_INTFREQ_SUCC ( M8021C2 ) ;ISYS_HO_PREP ( M8016C14 ) ;ISYS_HO_ATT ( M8016C21 ) ;ISYS_HO_SUCC ( M8016C23 ) ;ISYS_HO_GERAN_SRVCC_ATT ( M8016C33 ) ;ISYS_HO_GERAN_SRVCC_SUCC ( M8016C34 ) ;

M8013C5:SIGN_CONN_ESTAB_COMP ;M8013C17:SIGN_CONN_ESTAB_ATT_MO_S ;M8013C18:SIGN_CONN_ESTAB_ATT_MT ;M8013C19:SIGN_CONN_ESTAB_ATT_MO_D; M8013C20:SIGN_CONN_ESTAB_ATT_OTHERS; M8013C21:SIGN_CONN_ESTAB_ATT_EMG;M8000C30 : S1AP_NAS_DOWNLINK ;M8000C12 : UE_LOG_S1_SETUP ; M8000C1 :INI_CONT_STP_COMP ; M8000C0 :INI_CONT_STP_REQ ;

M8013C18:SIGN_CONN_ESTAB_ATT_MT ;M8013C19:SIGN_CONN_ESTAB_ATT_MO_D; EPS_BEARER_STP_COM_INI_QCI1 ( M8006C35 ) , EPS_BEARER_STP_COM_INI_QCI_2 ( M8006C168 ) , EPS_BEARER_STP_COM_INI_QCI_3 ( M8006C169 ) ,EPS_BEARER_STP_COM_INI_QCI_4 ( M8006C170 ),EPS_BEAR_STP_COM_INI_NON_GBR ( M8006C36 ) ,EPS_BEARER_STP_ATT_INI_QCI1 ( M8006C17) , EPS_BEARER_STP_ATT_INI_QCI_2 ( M8006C162 ) , EPS_BEARER_STP_ATT_INI_QCI_3 ( M8006C163 ) ,EPS_BEARER_STP_ATT_INI_QCI_4 ( M8006C164 ),EPS_BEAR_STP_ATT_INI_NON_GBR ( M8006C18 )

EPS_BEARER_SETUP_COMPLETIONS (M8006C1) ; EPS_BEARER_STP_COM_INI_QCI1 ( M8006C35 );EPS_BEARER_STP_COM_INI_QCI_2 ( M8006C168 ) ; EPS_BEARER_STP_COM_INI_QCI_3 ( M8006C169 ) ; EPS_BEARER_STP_COM_INI_QCI_4 ( M8006C170 ) ;EPS_BEAR_STP_COM_INI_NON_GBR ( M8006C36 ) ; EPS_BEARER_SETUP_ATTEMPTS ( M8006C0) ; EPS_BEARER_STP_ATT_INI_QCI1 ( M8006C17) ; EPS_BEARER_STP_ATT_INI_QCI_2 ( M8006C162 ) ; EPS_BEARER_STP_ATT_INI_QCI_3 ( M8006C163 ) ; EPS_BEARER_STP_ATT_INI_QCI_4 ( M8006C164 ) ; EPS_BEAR_STP_ATT_INI_NON_GBR ( M8006C18 )

RRC_CONN_UE_AVG ( M8001C199 )

PDCP_SDU_DELAY_DL_DTCH_MEAN ( M8001C2 )

EPS_BEAR_SET_COM_ADDIT_QCI1 ( M8006C44 ) ;EPS_BEARER_STP_COM_ADD_QCI_2 ( M8006C171 ) ;EPS_BEARER_STP_COM_ADD_QCI_3 ( M8006C172 );EPS_BEARER_STP_COM_ADD_QCI_4 ( M8006C173 ) ;EPS_BEAR_SET_ATT_ADD_QCI_1 ( M8006C26) ;EPS_BEARER_STP_ATT_ADD_QCI_2 ( M8006C165 ) ;EPS_BEARER_STP_ATT_ADD_QCI_3 ( M8006C166 );EPS_BEARER_STP_ATT_ADD_QCI_4 ( M8006C167 )

SUM_RRC_CONN_UE ( M8001C318 ) ;DENOM_RRC_CONN_UE ( M8001C319 )

PDCP_RET_DL_DEL_MEAN_QCI_1 ( M8001C269) , PDCP_RET_DL_DEL_MEAN_QCI_2 ( M8001C270 ) , PDCP_RET_DL_DEL_MEAN_QCI_3 ( M8001C271 ),PDCP_RET_DL_DEL_MEAN_QCI_4 ( M8001C272 ),PDCP_RET_DL_DEL_MEAN_NON_GBR (M8001C270 )

M8012C143:PDCP_DATA_RATE_MEAN_DL_QCI_1

M8012C26:PDCP_DATA_RATE_MEAN_DL ;M8012C20:PDCP_SDU_VOL_DL ;M8012C90:ACTIVE_TTI_DL ;

M8012C19:PDCP_SDU_VOL_UL ;M8012C89:ACTIVE_TTI_UL ;M8012C23:PDCP_DATA_RATE_MEAN_UL ;

M8001C154:PDCP_SDU_DL ;M8001C259:PDCP_SDU_LOSS_DL ;

M8001C153:PDCP_SDU_UL ;M8001C254:PDCP_SDU_LOSS_UL ;

M8006C176:ERAB_REL_ENB_ACT_QCI1:2.4u:Integer numberM8006C177:ERAB_REL_ENB_ACT_QCI2:2.4u:Integer numberM8006C178:ERAB_REL_ENB_ACT_QCI3:2.4u:Integer numberM8006C179:ERAB_REL_ENB_ACT_QCI4:2.4u:Integer numberM8006C180:ERAB_REL_ENB_ACT_NON_GBR:2.4u:Integer numberM8006C181:ERAB_IN_SESSION_TIME_QCI1:2.4u:sM8006C182:ERAB_IN_SESSION_TIME_QCI2:2.4u:sM8006C183:ERAB_IN_SESSION_TIME_QCI3:2.4u:sM8006C184:ERAB_IN_SESSION_TIME_QCI4:2.4u:sM8006C185:ERAB_IN_SESSION_TIME_NON_GBR:2.4u:s


M8006C176:ERAB_REL_ENB_ACT_QCI1M8006C177:ERAB_REL_ENB_ACT_QCI2M8006C178:ERAB_REL_ENB_ACT_QCI3M8006C179:ERAB_REL_ENB_ACT_QCI4M8006C180:ERAB_REL_ENB_ACT_NON_GBRM8006C181:ERAB_IN_SESSION_TIME_QCI1M8006C182:ERAB_IN_SESSION_TIME_QCI2M8006C183:ERAB_IN_SESSION_TIME_QCI3M8006C184:ERAB_IN_SESSION_TIME_QCI4M8006C185:ERAB_IN_SESSION_TIME_NON_GBRM8006C12:ENB_EPS_BEARER_REL_REQ_RNL M8006C13:ENB_EPS_BEARER_REL_REQ_OTH M8006C14:ENB_EPS_BEARER_REL_REQ_TNLM8006C10:ENB_EPS_BEARER_REL_REQ_NORMM8006C15:ENB_EPSBEAR_REL_REQ_RNL_REDIRM8006C6:EPC_EPS_BEARER_REL_REQ_NORM M8006C7:EPC_EPS_BEARER_REL_REQ_DETACH

Logical formula

Cell Avail excl BLU=(cell avail)/(all cells-cells plan unavail)*100%

Cell Avail=(Samples Cell Avail/Samples Cells)*100%

100 * [ ( Intra Freq HO preparation Success + Inter Freq HO preparation Success + IRAT ( WCDMA ) Ho Preparation Success ) / ( Intra Freq HO preparation Attempts + Inter Freq HO preparation Attempts + IRAT ( WCDMA ) Ho Preparation Attempts ) ] * [ (Intra Freq HO Execution Success + Inter Freq HO Execution Success + IRAT ( WCDMA ) Ho Execution Success) / ( Intra Freq HO Execution Attempts + Inter Freq HO Execution Attempts + IRAT ( WCDMA ) Ho Execution Attempts ) ]

100 * [ ( Intra Freq HO preparation Success + Inter Freq HO preparation Success + SRVCC Ho Preparation Success ) / ( Intra Freq HO preparation Attempts + Inter Freq HO preparation Attempts + SRVCC Ho Preparation Attempts ) ] * [ (Intra Freq HO Execution Success + Inter Freq HO Execution Success + SRVCC Ho Execution Success) / ( Intra Freq HO Execution Attempts + Inter Freq HO Execution Attempts +SRVCC Ho Execution Attempts ) ]

100 * [ ( Number of Signaling Connection Establishment completions) / ( Number of RRC signalling connection attempts due to MO-Signalling +Number of RRC signalling connection attempts due to MT-Access +Number of RRC signalling connection attempts due to MO-Data +Number of RRC signalling connection attempts due to others + Number of RRC signalling connection attempts due to emergency calls ) ] * [ Number of Downlink NAS Transport messages / Number of UE-associated logical S1-connection establishments ] * [ initial context setup successes / initialcontext setup attempts ]

( or) 100 * [ RRC Connection Setup Success Ratio ( LTE_5218c ) ] * [ Number of Downlink NAS Transport messages / Number of UE-associated logical S1-connection establishments ] * [ S1 Initial Context setup Success Ratio ( LTE_5009a ) ]

100 * [ Total EPS bearer Completions - ( Initial EPS Bearer setup Completions for GBR DRB's & Non - GBR's ) ] / [ Total EPS bearer Attempts - ( Initial EPS Bearer setup Attempts for GBR DRB's & Non - GBR's ) ]

ACT UE Area=( average number of RRC connected UEs)

LatencyAvgDL=PDCP SDU delay on DL DTCH Mean

100 * [ EPS Bearer setup Completions for GBR DRB's ] / [ EPS Bearer setup Attempts for GBR DRB's ]

LatencyAvgDL=PDCP SDU delay on DL DTCH Mean for GBR DRBs & Non-GBR DRBs

AVG DL PDCP CELL THP= average PDCP cell throughput DL

AVG DL PDCP CELL THP QCI1= average PDCP cell throughput DL for QCI1 DRBs

AVG UL PDCP CELL THP= average PDCP cell throughput UL

PDCPSDULossRDL = (number of lost PDCP SDUs DL / number of transmitted PDCP SDUs DL) x 100

PDCPSDULossRUL = (number of lost PDCP SDUs UL / number of transmitted PDCP SDUs UL) x 100

E-RAB RetainR (RNL UE Los)= (Active ERAB Rel QCI1 + Active ERAB Rel QCI2+ Active ERAB Rel QCI3 + Active ERAB Rel QCI4 + Active ERAB Rel non GBR )/(ERABActive Time QCI1 + ERAB Active Time QCI2 + ERAB Active Time QCI3 + ERABActive Time QCI4 + ERAB Active Time nonGBR)

E-RAB RetainR (RNL UE Los)= (Active ERAB Rel QCI1 / ERABActive Time QCI1 ) & ( Active ERAB Rel QCI2 / ERAB Active Time QCI2 ) & ( Active ERAB Rel QCI3 / ERAB Active Time QCI3 ) &( Active ERAB Rel QCI4 / ERABActive Time QCI4 ) ( Active ERAB Rel non GBR / ERAB Active Time nonGBR )

E-RAB RetainRate (%)= (Active ERAB Rel QCI1 + Active ERAB Rel QCI2+ Active ERAB Rel QCI3 + Active ERAB Rel QCI4 + Active ERAB Rel non GBR ) / ( eNB initiated Abnormal Releases + eNB initiated Normal Releases + EPC initiated Normal Releases )

KPI Formula Unit Comments_NSN

%

%

%


1) Sampling Interval : 10 s 2) Counter M8020C4 ( SAMPLES_CELL_PLAN_UNAVAIL )will be incremented when cell operational state in locked


1) Sampling Interval : 10 s 2) Counters will be incremented when cell operational state in enabled

100 * [ ( ATT_INTRA_ENB_HO +ATT_INTER_ENB_HO +INTER_ENB_S1_HO_ATT + ISYS_HO_ATT ) / ( INTRA_ENB_HO_PREP +INTER_ENB_HO_PREP +INTER_ENB_S1_HO_PREP + ISYS_HO_PREP) ] * [ (SUCC_INTRA_ENB_HO +SUCC_INTER_ENB_HO +INTER_ENB_S1_HO_SUCC +HO_INTFREQ_SUCC +ISYS_HO_SUCC ) / ( ATT_INTRA_ENB_HO +ATT_INTER_ENB_HO +INTER_ENB_S1_HO_ATT +ISYS_HO_ATT +HO_INTFREQ_ATT) ]

Sepearte KPI's available for all types of HO's

%

%

100 * [ ( ATT_INTRA_ENB_HO +ATT_INTER_ENB_HO +INTER_ENB_S1_HO_ATT ) / ( INTRA_ENB_HO_PREP +INTER_ENB_HO_PREP +INTER_ENB_S1_HO_PREP ) ] * [ (SUCC_INTRA_ENB_HO +SUCC_INTER_ENB_HO +INTER_ENB_S1_HO_SUCC +HO_INTFREQ_SUCC +ISYS_HO_GERAN_SRVCC_SUCC) / ( ATT_INTRA_ENB_HO +ATT_INTER_ENB_HO +INTER_ENB_S1_HO_ATT +ISYS_HO_GERAN_SRVCC_ATT +HO_INTFREQ_ATT) ]



NSN's own Initial E-RAB setup success Ratio LTE_5112b describes the setup success ratio of the elementaryinitial E-RAB setup procedure.It indicates the E-UTRAN contribution to network accessibilityfor the end-user, not the whole end-to-end service accessibility.

%

%

%



1. Counters NOT available for RRC connection establishments under different causes .

2. Counters NOT available for Initial signalling connection establishments under different causes.

3. Initial EPS bearer setup counters Mapping available for all QCI's ( GBR & NON- GBR )



All initial E-RAB setup attemps & establishments subtracted from total EPS bearer attemps for 1 to 1 mapping

%

#

Available from RL50 Release

sum( RRC_CONN_UE_AVG ) # Sampling Interval : 4 s


ms


Deviation Observed . Counters for Additional E-RAB Setup Attempts not available for Non-GBR QCI's


This KPI shows the retention period (delay) of a PDCP SDU (DL) inside eNB. Time from reception of IP packet to transmission of first packet over the Uu interface.


This KPI shows the retention period (delay) of a PDCP SDU (DL) inside eNB for QCI1 / QCI 2/QCI3/QCI4/non-GBR ( QCI5…9) DRBs. Time from reception of IP packet to transmission of first packet over the Uu interface.

Kbps


avg( PDCP_DATA_RATE_MEAN_DL ) [ RL 40 ]

------------------------------------------------------------8 * sum( PDCP_SDU_VOL_DL ) /sum( ACTIVE_TTI_DL ) [ RL 50 ]

Kbps

%

%

# / s

avg( PDCP_DATA_RATE_MEAN_UL ) [ RL 40 ]

------------------------------------------------------------8 * sum( PDCP_SDU_VOL_UL ) /sum( ACTIVE_TTI_UL ) [ RL 50 ]




This KPI provides how often an end-user abnormally looses due to RNL failurewith UE lost cause an E-RAB during the time the E-RAB is active.

# / s

%




MO Class Counter _ Ericsson Description_Ericsson

Availability pmCellDownTimeAuto

Availability pmCellDownTimeMan

Mobility pmHoPrepAttLteIntraF A better LTE cell is reported by the UE.

Mobility pmHoPrepSuccLteIntraF

Length of time the cell has been disabled due to a fault (system has set cell MO OperationalState to Disabled). The counter is only incremented when the RBS is operational.Length of time the cell has been disabled due to:- AdministrativeState of the cell MO or another MO the cell depends on has been set to Locked by the operatoror- the operator has performed a reconfiguration request on an Unlocked cell which requires the cell to be taken down temporarily.The counter is only incremented when the RBS is operational.

HANDOVER COMMAND message is received by the source eNodeB from the MME (S1 handover)orHANDOVER REQUEST ACKNOWLEDGE message is received by the source eNodeB from the target eNodeB (X2 handover)orInternal eNodeB trigger (corresponding to HANDOVER REQUEST ACKNOWLEDGE) received when target cell informs source cell that UE resources has been reserved (intra eNodeB handover)

Mobility pmHoExeAttLteIntraF

Mobility pmHoExeSuccLteIntraF

Mobility pmHoPrepAttLteInterF

Mobility pmHoPrepSuccLteInterF

RRC CONNCECTION RECONFIGURATION including the " mobilityControlInformation " is sent to the UE from the source cell.

UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered (S1 handover)orUE CONTEXT RELEASE received in the source eNodeB from the target eNodeB (X2 handover)orInternal eNodeB trigger (corresponding to UE CONTEXT RELEASE) received when the UE has changed cell during a intra eNodeB handover

The number of attempts to start outgoing intra LTE inter frequency handover preparation.


Mobility pmHoExeAttLteInterF

Mobility pmHoExeSuccLteInterF

Mobility pmHoPrepAttWcdma

Mobility pmHoPrepSuccWcdma



Number of handover to UTRAN or TD-SCDMA preparation attempts. A better UTRAN or TD-SCDMA cell is reported by the UE.

Number of successful handover to UTRAN or TD-SCDMA preparations. HANDOVER COMMAND received in the source eNodeB from the MME (S1 handover).

Mobility pmHoExeAttWcdma

Mobility pmHoExeSuccWcdma

Mobility pmHoPrepAtt

Mobility pmHoPrepSucc

Mobility pmHoExeAtt

Mobility pmHoExeSucc

pmRrcConnEstabSucc

Number of handover to UTRAN or TD-SCDMA execution attempts.MobilityFromEUTRACommand towards the UTRAN or TD-SCDMA cell is sent to the UE.

Number of successful handovers to UTRAN or TD-SCDMA.UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered (S1 handover) .

The number of attempts to start Single Radio Voice Call Continuity (SRVCC) handover preparation from LTE to GSM/EDGE Radio Access Network (GERAN). A better GERAN cell is reported by the UE and a VoIP bearer is established.

The number of successful Single Radio Voice Call Continuity (SRVCC) handover preparations from LTE to GSM/EDGE Radio Access Network (GERAN).HANDOVER COMMAND message is received by the source eNodeB from the MME (S1 handover), including a VoIP bearer.

The number of attempts to start Single Radio Voice Call Continuity (SRVCC) handover execution from LTE to GSM/EDGE Radio Access Network (GERAN).MobilityFromEUtraCommand including the Information on target RAT and cell is sent to the UE from the source cell, including a VoIP bearer.

The number of successful Single Radio Voice Call Continuity (SRVCC) handover executions from LTE to GSM/EDGE Radio Access Network (GERAN).UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered (S1 handover) and the UE has a VoIP bearer.

Accessibility

Stepped at reception of RRC message RRC Connection Setup Complete at eNB end.

pmRrcConnEstabAtt

pmRrcConnEstabAttReatt

pmS1SigConnEstabSucc

pmS1SigConnEstabAtt

pmErabEstabSuccInit

pmErabEstabAttInit

pmRrcConnEstabSuccMod

pmRrcConnEstabSuccMta

pmRrcConnEstabAttMod

Accessibility

Stepped at reception of RRC message RRC Connection Request.

Accessibility

Stepped at reception of RRC message RRC Connection Request while an RRC Connection Setup is already ongoing for that S-TMSI. ( Repetetive Attempts from Same UE )

Accessibility

The total number of successful S1 signalling connection establishments.

Accessibility

This measurement provides the number of S1 Signalling connection establishment attempts for any establishment cause.

Accessibility

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.

Accessibility

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.

Accessibility

The total number of successful RRC Connection Establishments for Establishment cause Mobile Originating Data.

Accessibility

The total number of successful RRC Connection Establishments for Establishment cause Mobile Terminating Access.

Accessibility

The total number of RRC Connection Request attempts with Establishment cause Mobile Originating Data.

pmRrcConnEstabAttMta

pmRrcConnEstabAttReattMod

pmRrcConnEstabAttReattMta

pmS1SigConnEstabSuccMod

pmS1SigConnEstabSuccMta

pmS1SigConnEstabAttMod

pmS1SigConnEstabAttMta

pmErabEstabSuccInitQci

pmErabEstabAttInitQci

Accessibility

The total number of RRC Connection Request attempts with Establishment cause Mobile Terminating Access.

Accessibility

The total number of RRC Connection Request attempts that are considered as re-attempts for Establishment cause Mobile Originating Data.

Accessibility

The total number of RRC Connection Request attempts that are considered as re-attempts for Establishment cause Mobile Terminating Access.

Accessibility

The total number of successful S1 signalling connection establishments with Establishment cause Mobile Originating Data.

Accessibility

The total number of successful S1 signalling connection establishments with Establishment cause Mobile Terminating Access.

Accessibility

This measurement provides the number of S1 Signalling connection establishment attempts with RRC Connection Request Establishment cause Mobile Originating Data.

Accessibility

This measurement provides the number of S1 Signalling connection establishment attempts with RRC Connection Request Establishment cause Mobile Terminating Access.

Accessibility

The total number of successful initial E-RAB setup per QCI.Compressed: True

Accessibility

The total number of initial E-RAB setup attempts per QCI.Compressed: True

pmRrcConnEstabSuccEm

pmRrcConnEstabAttEm

pmRrcConnEstabAttReattEm

pmS1SigConnEstabSuccEm

pmS1SigConnEstabAttEm

pmErabEstabSuccInitArp

pmErabEstabAttInitArp

pmMBMSSessionEstabSucc

pmMBMSSessionEstabAtt

Accessibility

The total number of successful RRC Connection Establishments for Establishment cause Emergency.

Accessibility

The total number of RRC Connection Request attempts with establishment cause emergency.

Accessibility

The total number of RRC Connection Request attempts that are considered as re-attempts for Establishment cause Emergency.

Accessibility

The total number of successful S1 signalling connection establishments with Establishment cause Emergency.

Accessibility

This measurement provides the number of S1 Signalling connection establishment attempts with RRC Connection Request Establishment cause Emergency.

Accessibility

The total number of successful initial E-RAB Establishments per ARP value.

[0]: N/A (unallowed ARP value)[1]: Sum of successful initial E-RAB Establishment with ARP priority value 1...[15]: Sum of successful initial E-RAB Establishment with ARP priority value 15

Accessibility

The total number of initial E-RAB Establishment attempts per ARP value. Initial E-RABs are all E-RABs present in the S1 message Initial Context Setup Request.

[0]: N/A (unallowed ARP value)[1]: Sum of initial E-RAB Establish Attempts with ARP priority value 1...[15]: Sum of initial E-RAB Establish Attempts with ARP priority value 15

Accessibility

The total number of MBMS sessions successfully established in eNB is incremented each time when the MBMS SESSON START RESPONSE is sent.

Accessibility

The total number of MBMS session establishment attempts is incremented each time when the MBMS SESSON START REQUEST is received.

pmErabEstabSuccAdded

pmErabEstabAttAdded

pmErabEstabSuccAddedQci

pmErabEstabAttAddedQci

pmErabEstabSuccAddedArp

pmErabEstabAttAddedArp

Accessibility

The total number of successfully added E-RABs. Added E-RABs are all E-RABs present in S1 message E-RAB Setup Request.

Accessibility

The total number of added E-RAB Establishment attempts. Added E-RABs are all E-RABs present in S1 message E-RAB Setup Request.

Accessibility

The total number of successful additional E-RAB setup per QCI.

Compressed: True

Accessibility

The total number of additional E-RAB setup attempts per QCI.Compressed: True

Accessibility

The total number of successfully added E-RABs per ARP value. Added E-RABs are all E-RABs present in S1 message E-RAB Setup Request.

[0]: N/A (unallowed ARP value)[1]: Sum of successful added E-RABs established with ARP priority value 1...[15]: Sum of successful added E-RABs established with ARP priority value 15

Accessibility

The total number of added E-RAB Establishment attempts per ARP value. Added E-RABs are all E-RABs present in S1 message E-RAB Setup Request.

[0]: N/A (unallowed ARP value)[1]: Sum of added E-RAB Establish Attempts with ARP priority value 1...[15]: Sum of added E-RAB Establish Attempts with ARP priority value 15

pmRrcConnLevSum

pmRrcConnLevSamp

pmRrcConnMax Peak Number of RRC Connected Users

Integrity pmPdcpLatTimeDl

Integrity pmPdcpLatPktTransDl

Integrity pmPdcpVolDlDrb

Accessibility

Sum of all sample values recorded for "number of UEs in RRC_CONNECTED mode".

Accessibility

Number of times the corresponding Sum counter has accumulated a new sample. Associated ACC pmCounter pmRrcConnLevSum.

Accessibility

Aggregated DL Latency for a measurement period. The effective DL Latency time comprises the time from PDCP DRB SDU entering the buffer until the first data has been transmitted to the UE.

When carrier aggregation is used, the DL Latency for all component carriers is registered on the UE's primary component carrier (PCell).

Number of DRB packets for downlink Latency measurements.


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 Bearers that has been transferred (UM and AM) in the downlink direction is measured on PCell.

Integrity pmPdcpVolDlDrbLastTTI

Integrity pmUeThpTimeDl

Integrity pmSchedActivityCellDl

Integrity pmDrbThpTimeDlQci

pmErabRelAbnormalEnbAct

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/SCell(s)). 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 is measured on PCell.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 be sent over multiple cells (PCell/SCell(s)). The effective DL transport time, comprising 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, is registered on PCell.The aggregated number of ms in which DRB data was required to be scheduled in the downlink.

The DL transmission time used for DL DRB Throughput per QCI. It comprises of time periods from when the first piece of data in a data burst is transmitted until the second last piece of data in the data burst is transmitted.

Retainability

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).

pmErabRelAbnormalMmeAct

pmSessionTimeUe

pmSessionTimeDrbQci

Retainability

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).

Retainability

This counters shows the accumulated active session time for all UEs in a cell. ( Unit : s )

Retainability

The session time aggregated for DRBs mapping to a QCI. Compressed: True

Retainability

pmErabRelAbnormalEnbActQci

The total number of active E-RABs released abnormally per cell per QCI for requests initiated by eNB (per cell per QCI). , except active E-RABs released due to successful HO. An E-RAB is considered to be active when there are data in the DL or UL queues for the E-RAB.

Compressed: True

Retainability

pmErabRelAbnormalMmeActQci

The total number of E-RAB Releases (per cell per QCI) initiated by the MME considered as abnormal. The counter is stepped if data was lost in either the UL or DL buffers. Type:Compressed PDF[0]: N/A[1]: Abnormal active E-RAB releases for E-RABs with QCI 1�.[255]: Abnormal active E-RAB releases for E-RABs with QCI 255

Compressed: True

pmErabRelAbnormalEnb

pmErabRelNormalEnb

pmErabRelMme

Retainability

The total number of abnormal E-RAB Releases triggered by eNB per cell.

Retainability

The total number of normal E-RAB Releases triggered by eNB per cell.

Retainability

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.

Triggering point O - O Comparision

Sampling Interval :E/// - 1 sNSN - 10 s

Intra eNB E/// - Updated in Source Cell after reception of Measurement report from UENSN - Updated in source cell after completion of admission control procedure in eNB on Target side.Inter eNB via X2E/// - Updated in Source Cell after reception of Measurement report from UENSN - Updated in source cell when HO decision made by source eNB after measurements reported by UE .Inter eNB via S1E/// - Updated in Source Cell after reception of Measurement report from UENSN - HANDOVER REQUIRED message from the source eNB to the MME if this message prepares an Inter eNB Handover.

Intra : Closest MatchInter via X2 : Closest MatchInter via S1 : Closest Match

Intra eNB E/// - Counter is incremented when the target cell informs the source cell that UE resources has been reserved for handover using internal RBS trigger .NSN - Updated in source cell after after sending HO command message to eNB .Inter eNB via X2E/// - On Reception of Handover Request acknowledge message the source eNB will increment this counterNSN - The reception of an X2AP: Handover Request Acknowledge message from the target eNB.Inter eNB via S1E/// - HANDOVER COMMAND message is received by the source eNodeB from the MMENSN - This counter is updated following the reception of an S1AP: HANDOVER COMMAND message from the MME to the source eNB


No Match

No Match

No Match

Intra eNB E/// - On Transmission of RRC CONNECTION RECONFIGURATION including "mobility Controlinformation " to UE from eNBNSN - NA Inter eNB via X2E/// - On Transmission of RRC CONNECTION RECONFIGURATION including "mobility Controlinformation " to UE from Source eNBNSN - NAInter eNB via S1E/// - On Transmission of RRC CONNECTION RECONFIGURATION including "mobility Controlinformation " to UE from source eNBIntra eNB E/// - Internal eNodeB trigger (corresponding to UE CONTEXT RELEASE) received when the UE has changed cell during a intra eNodeB handoverNSN - The reception of an internal UE Context Release Request for the handover on the source side. Updated to the source cell.Inter eNB via X2E/// - UE CONTEXT RELEASE received in the source eNodeB from the target eNodeB (X2 handover)NSN - The reception of a X2AP: Release Resource message sent by the target eNB.Inter eNB via S1E/// - UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered (S1 handover)NSN -This counter is updated following the reception of an S1AP: UE CONTEXT RELEASE COMMAND message from the MME to the source eNB


Intra eNB E/// - Updated in Source Cell after reception of Measurement report from UENSN - NAInter eNB via X2E/// - Updated in Source Cell after reception of Measurement report from UENSN - NAInter eNB via S1E/// - Updated in Source Cell after reception of Measurement report from UENSN - NA

Intra eNB E/// - Counter is incremented when the target cell informs the source cell that UE resources has been reserved for handover using internal RBS trigger .NSN - NAInter eNB via X2E/// - On Reception of Handover Request acknowledge message the source eNB will increment this counterNSN - NAInter eNB via S1E/// - HANDOVER COMMAND message is received by the source eNodeB from the MMENSN - NA

Closest Match

100 % Mapping

Intra eNB E/// - On Transmission of RRC CONNECTION RECONFIGURATION including "mobility Controlinformation " to UE from eNBNSN - Updated in source cell after after sending HO command message to eNB . Inter eNB via X2E/// - On Transmission of RRC CONNECTION RECONFIGURATION including "mobility Controlinformation " to UE from Source eNBNSN - The reception of an X2AP: Handover Request Acknowledge message from the target eNB.Inter eNB via S1E/// - On Transmission of RRC CONNECTION RECONFIGURATION including "mobility Controlinformation " to UE from Source eNBNSN - This counter is updated following the reception of an S1AP: HANDOVER COMMAND message from the MME to the source eNB


Intra eNB E/// - Internal eNodeB trigger (corresponding to UE CONTEXT RELEASE) received when the UE has changed cell during a intra eNodeB handoverNSN - The reception of an internal UE Context Release Request for the handover on the source side. Updated to the source cell.Inter eNB via X2E/// - UE CONTEXT RELEASE received in the source eNodeB from the target eNodeB (X2 handover)NSN - The reception of a X2AP: Release Resource message sent by the target eNB.Inter eNB via S1E/// - UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered (S1 handover)NSN -This counter is updated following the reception of an S1AP: UE CONTEXT RELEASE COMMAND message from the MME to the source eNB


HO To WCDMA E/// - Updated in Source Cell after reception of Measurement report from UENSN - Transmission of a S1AP: HANDOVER REQUIRED message to source MME

HO To WCDMA E/// - Updated when HANDOVER COMMAND received in the source eNodeB from the MME NSN - Transmission of a S1AP: HANDOVER REQUIRED message to source MME

No Match

Closest Match

No Match

100 % Mapping

Closest Match

Closest Match

HO To WCDMA E/// - Updated when MobilityFromEUTRACommand towards the UTRANNSN - NA

HO To WCDMA E/// - Updated when UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered

NSN - Updated when UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover TriggeredLTE To GSM SRVCC E/// - Updated in Source Cell after reception of Measurement report from UENSN - NA

LTE To GSM SRVCC E/// - Updated when HANDOVER COMMAND received in the source eNodeB from the MME NSN - Updated when HANDOVER COMMAND received in the source eNodeB from the MM

LTE To GSM SRVCC E/// - Updated when MobilityFromEUTRACommand towards the UTRANNSN - NA

Delayed HO time possible in E/// - NSN mapping due to NSN counter's advanced triggering

LTE To GSM SRVCC E/// - Updated when UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered

NSN - Updated when UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered

E/// - Updated when reception of RRC message RRC Connection Setup Complete at eNB end.

NSN - Updated when reception of RRC message RRC Connection Setup Complete at eNB end.

Closest Match

No Match

Closest Match

Closest Match

Closest Match

Closest Match

No Match

No Match

Closest Match

E/// - Updated when reception of RRC message RRC Connection Request at eNB .

NSN - Updated when reception of RRC message RRC Connection Request at eNB .

E/// - Stepped at reception of RRC message RRC Connection Request while an RRC Connection Setup is already ongoing for that S-TMSI.

NSN- NAE/// - When setting up the E-RAB the ‘RRC CONNECTION SETUP COMPLETE’message contains a piggybacked NAS ‘Attach Request’ message. The RBS willsend this message to the MME in the S1AP ‘INITIAL UE MESSAGE’ andincrement the ‘pmS1SigConnEstabAtt’ counter

NSN- This counter is updated following the reception of an S1AP: DOWNLINK NAS TRANSPORT message sent by the MME to the eNB.E/// - Stepped at transmission of Initial UE message.

NSN- Transmission of the S1AP message INITIAL UE MESSAGE containing the first NAS signaling message to the MME.E/// - Stepped for each initial E-RAB that is successfully established.

NSN- The transmission of an S1AP:Initial Context Setup Response message sent by the eNB to MME for the successful Initial Context Setup completion.E/// - Stepped for each E-RAB received in the S1 message Initial Context Setup Request.

NSN- The reception of an S1AP:Initial Context Setup Request message sent by the MME to eNB

E/// - Stepped at reception of RRC message RRC Connection Setup Complete if the corresponding RRC Connection Request had Establishment cause Mobile Originating Data.NSN - NAE/// - Stepped at reception of RRC message RRC Connection Setup Complete if the corresponding RRC Connection Request had Establishment cause Mobile Terminating Access.NSN - NAE/// - Stepped at reception of RRC message RRC Connection Request with Establishment cause Mobile Originating Data.

NSN - Stepped at reception of RRC message RRC Connection Request with Establishment cause Mobile Originating Data.

Closest Match

No Match

No Match

No Match

No Match

No Match

No Match

100 % Mapping

100 % Mapping

E/// - Stepped at reception of RRC message RRC Connection Request with Establishment cause Mobile Terminating Access.NSN - Stepped at reception of RRC message RRC Connection Request with Establishment cause Mobile Terminating Access

Stepped at reception of RRC message RRC Connection Setup Complete if the corresponding RRC Connection Request had Establishment cause Mobile Originating Data AND while an RRC Connection Setup is already ongoing for that S-TMSI.

Stepped at reception of RRC message RRC Connection Setup Complete if the corresponding RRC Connection Request had Establishment cause Mobile Terminating Access AND while an RRC Connection Setup is already ongoing for that S-TMSI.

Stepped at the first occurrence of reception of any message on this S1 logical connection, if the RRC Connection Request Establishment cause was Establishment cause Mobile Originating Data.Stepped at the first occurrence of reception of any message on this S1 logical connection, if the RRC Connection Request Establishment cause was Establishment cause Mobile Terminating Access.

Stepped at transmission of Initial UE message with RRC Connection Request Establishment cause Mobile Originating Data.

Stepped at transmission of Initial UE message with RRC Connection Request Establishment cause Mobile Terminating Access.

E /// - Shall be stepped for each successful E-RAB Establishment attempt per QCI at transmission of S1-AP message Initial Context Setup Response.

NSN - The transmission of an S1AP:Initial Context Setup Response message sent by the eNB to MME

E/// - Shall be stepped for each E-RAB Establishment attempt per QCI at reception of S1-AP message Initial Context Setup Request.NSN - Receipt of a S1AP:Initial Context Setup Request sent by MME to the eNB for each QCI1 bearer contained in the "E-RAB to Be Setup List" IE.

100 % Mapping

Closest Match

No Match

No Match

No Match

No Match

No Match

No Match

No Match

E/// -Stepped at reception of RRC message RRC Connection Setup Complete if the corresponding RRC Connection Request had Establishment cause Emergency

NSN -Reception of the RRC: RRCConnectionSetupComplete message (eNB <- UE) in case that this message was received from the UE after the reception of the RRC: RRCConnectionRequest message (eNB <-UE) with EstablishmentCause set to emergencyE/// - Stepped at reception of RRC message RRC Connection Request with establishment cause emergency.NSN - Reception of the RRC: RRCConnectionRequest message (eNB <- UE) in case that this message contains the EstablishmentCause set to emergency

Stepped at reception of RRC message RRC Connection Setup Complete if the corresponding RRC Connection Request had Establishment cause Emergency AND while an RRC Connection Setup is already ongoing for that S-TMSI.

Stepped at the first occurrence of reception of any message on this S1 logical connection, if the RRC Connection Request Establishment cause was Establishment cause Emergency.

Stepped at transmission of Initial UE message with RRC Connection Request Establishment cause Emergency.

Stepped at sending of Initial Context Setup Response for each successfully setup E-RAB that have the given ARP Priority Level.

Stepped at reception of Initial Context Setup Request for each E-RAB that has the given ARP Priority Level.

Stepped for each MBMS session when eNB sends M3 message: MBMS SESSION RESPONSE back to MME.

Stepped for each MBMS session in the M3 message: MBMS SESSION START REQUEST.

Closest Match

Closest Match

No Match

No Match

E/// - Stepped for each added bearer that is successfully established.

NSN - The transmission of an S1AP:S1AP:E-RAB SETUP RESPONSE message sent by the eNB to MME.

E/// - Stepped for each bearer received in the S1 message E-RAB Setup Request.NSN - The receipt of an S1AP:E-RAB SETUP REQUEST message sent by MME to the eNB

E/// - Shall be stepped for each successful E-RAB Establishment attempt per QCI at transmission of S1-AP message E-RAB Setup Response.

NSN - Transmission of a S1AP:INITIAL CONTEXT SETUP RESPONSE message sent by eNB to the MME. The counter is updated with the number of QCI 1 / QCI 2 / QCI 3 / QCI 4 bearers contained in the "E-RAB Setup List" IE

Closest Match . Counters for Additional E-RAB Setup Completions not available for Non-GBR QCI's

E/// -Shall be stepped for each E-RAB Establishment attempt per QCI at reception of S1-AP message E-RAB Setup Request.

NSN - Receipt of a S1AP:E-RAB SETUP REQUEST message sent by MME to the eNB. The counter is updated with the number of QCI 1 / QCI 2 / QCI 3 / QCI 4 bearers contained in the "E-RAB to Be Setup List" IE

Closest Match . Counters for Additional E-RAB Setup Attempts not available for Non-GBR QCI's


Stepped at reception of E-RAB Setup Request for each E-RAB that has the given ARP Priority Level.

No Match

No Match

Closest Match

E/// - This counter is based on an internal level counter maintaining the current number of UEs in RRC_CONNECTED mode. Values are read periodically and accumulated.NSN - This Counter is updated after each sampling interval with the sample taken from the number of UE's in RRC_Connected state

Sampling Interval :E/// - 5 sNSN - 1s

E/// - The counter is increased at every occasion when the corresponding sum counter has accumulated a new sample.NSN - This counter is updated by value 1 when the number of RRC connected UE's is summed to counter SUM_RRC_CONN_UE


E/// - This counter is based on an internal level counter maintained by eNB. The internal level counter maintains the current number of UEs in RRC_CONNECTED mode. pmRrcConnMax is updated at end of ROP with the max value during the ROP period. NSN - This counter is updated after each sampling interval with the peak number of UEs in RRC_CONNECTED state during the measurement period.E/// - Measurement for UEs aggregated to cell level. Only PDCP SDUs that enters an empty buffer are measured. Samples during handover are excluded since they can distort the interpretation of the result (due to packet forwarding, the target cell might have to buffer data before it is possible to schedule the UE in the target cell, hence it would be an increased Latency measurement if it would be included. It would however not lead to a degraded performance for the end-user, due to packet forwarding).

NSN - NA

E///- Measurement for UEs aggregated to cell level. Only PDCP SDUs that enters an empty buffer are measured. Samples during handover are excluded since they can distort the interpretation of the result (due to packet forwarding, the target cell might have to buffer data before it is possible to schedule the UE in the target cell, hence it would be an increased Latency measurement if it would be included. It would however not lead to a degraded performance for the end-user, due to packet forwarding).

NSN - NA

E/// - Continuous measurement for DRBs aggregated to cell level. ( Unit : Kilobits / 1000 Bits )

NSN - This counter is updated when a PDCP SDU is transmitted towards the UE

No Match

No Match

Closest Match

No Match

E/// - Continuous measurement for UEs aggregated to cell level. ( Unit : Kilobits / 1000 Bits )

E/// - Continuous measurement for UEs aggregated to cell level. ( ms )

NSN -

E/// - Each TTI, the counter shall be incremented when there was a need to schedule DRB data in the downlink.NSN - This counter is incremented with every TTI ,in which at least one UE is scheduld to receive user plane data.

E/// - The bin accumulates the DL transmission time per QCI for each large data burst that needs to be transmitted across multiple TTIs.

E///- If there was data in the buffer at the time of release, then stepped at reception of S1 message E-RAB Release Command or UE Context Release Command when internal cause codes considered abnormal (Radio Connection with UE is lost; Handover failure for the UE; Non admitted E-RABs by target cell at successful handover for the UE; UE pre-emption) when the RBS initiated the release. It can also be stepped at transmission of E-RAB Release Indication, UE Context Release Request or Reset message by the RBS, or when a cell owned by that RBS is disabled (and that leads to internal RBS UE Context Release). In the UL case when a UE has multiple bearers co-existing and sharing the same LCG, the bearers share a single packet queue. If one of the bearers is released and there is data in the queue, the bearer's associated counter is incremented, regardless of whether or not the data belongs to the released bearer.

NSN - The counters shall be updated in case that user data are buffered (UL/DL) for an E-RAB with QCI1 / QCI2/QCI3/QCI4/Non-GBR QCI characteristics and the "S1AP UE Context Release Request" message is sent by eNB to the MME with the release cause "RNL Radio Connection with UE lost"

NSN Counter will be triggered only with release Cause ( RNL Radio Connection with UE lost ) & for Pre-Empted Bearers

Closest Match

No Match

Match

Match

E/// - Stepped at reception of S1 message E-RAB Release Command or UE Context Release with none of the causes Normal Release, Handover Successful, User Inactivity, Detach, CS Fallback Triggered, Inter-RAT Redirection, UE Not available for PS Service or Redirection towards 1xRTT and there was data in either the UL or DL buffer (i.e. active). The release must also have been MME initiated. In the UL case when a UE has multiple bearers co-existing and sharing the same LCG, the bearers share a single packet queue. If one of the bearers is released and there is data in the queue, the bearer's associated counter is incremented, regardless of whether or not the data belongs to the released bearer.

E/// - Number of session seconds aggregated for all UEs in a cell. A UE is said to be ´in session´ if any data on a DRB (UL or DL) has been transferred during the last 100 ms

NSN - This measurement provides the aggregated in-session activity time in seconds for all E-RABs with QCI1 / QCI2/QCI3/QCI4/Non-GBR QCI characteristics. The E-RAB is said to be "in session" if any user data has been transferred in UL or DL direction within the last 100msec

The bin accumulates session seconds aggregated for DRBs with a certain QCI. The DRBs for a UE is said to be "in session" if any data on any DRB (UL or DL) has been transferred during the last 100 ms for that QCI.

E/// - The bin is steped for each released active E-RAB that maps to a certain QCI when the release is triggered by an E-RAB Release Indication, UE Context Release Request or Reset message and has a internal abnormal cause code, except active E-RABs released due to a successful HO. In the UL case when a UE has multiple bearers co-existing and sharing the same LCG, the bearers share a single packet queue. If one of the bearers is released and there is data in the queue, the bearer's associated counter is incremented, regardless of whether or not the data belongs to the released bearer.



Closest Match

The bin corresponding to the QCI of the E-RAB is stepped at reception of S1 message E-RAB Release Command or UE Context Release with none of the causes Normal Release, Handover Successful, User Inactivity, Detach, CS Fallback Triggered, Inter-RAT Redirection, UE Not available for PS Service or Redirection towards 1xRTT and there was data in either the UL or DL buffer (i.e. active). The release must also have been MME initiated. In the UL case when a UE has multiple bearers co-existing and sharing the same LCG, the bearers share a single packet queue. If one of the bearers is released and there is data in the queue, the bearer's associated counter is incremented, regardless of whether or not the data belongs to the released bearer.

> NSN Counter will be triggered only with release Cause ( RNL Radio Connection with UE lost ) & for Pre-Empted Bearers

> Closest Match

Match

Match

E/// - Stepped at reception of S1 message E-RAB Release Command or UE Context Release Command where the cause value indicates system (abnormal) release with the pre-condition that the Initial Context Establishment procedure must first have been successfully completed. The release must also have been eNB initiated.

NSN - The transmission of an S1AP:E-RAB RELEASE INDICATION or an S1AP: UE Context Release Request from the eNB to the MME

> NSN eNB initiated Abnormal E-RAB releases having the cause split up of RNL / TNL / OTH reasons.

> Match

E/// - Stepped at reception of S1 message E-RAB Release Command or UE Context Release Command where the cause value indicates normal release with the pre-condition that the Initial Context Establishment procedure must first have been successfully completed. The release must also have been eNB initiated.

NSN - The transmission of an S1AP:E-RAB RELEASE INDICATION or an S1AP: UE Context Release Request from the eNB to MME.

E/// - The counter is stepped for each released E-RAB at reception of S1 message E-RAB Release Command or UE Context Release Command (except if the cause was successful handover) and with the pre-condition that the Initial Context Establishment procedure must first have been successfully completed. The release must also have been MME initiated.

NSN - Reception of an S1AP:E-RAB RELEASE COMMAND or an S1AP:UE CONTEXT RELEASE COMMAND message sent by MME to the eNB. The counter is not incremented in case that the S1AP:UE CONTEXT RELEASE COMMAND is received as a response to a previously sent S1AP:UE CONTEXT RELEASE REQUEST

Counter_NSN Description

M8020C4:SAMPLES_CELL_PLAN_UNAVAIL

The number of samples when the cell is planned unavailable . The counter is updated with value 1 approximately every 10 seconds when cell Administrative State is locked.

INTRA_ENB_HO_PREP ( M8009C2 ) + INTER_ENB_HO_PREP ( M8014C0 ) +INTER_ENB_S1_HO_PREP (M8014C14 )

Intra eNBAn internal eNB trigger. The eNB MM receives a list with the target cells from RRM and decides on an Intra-eNB Handover. Updated to the source cell.Inter eNB via X2The number of Inter-eNB X2-based Handover preparations. The Mobility management (MM) receives a list with target cells from the RRM and decides to start an Inter-eNB X2-based Handover.Inter eNB via S1This counter is updated following the transmission of an S1AP: HANDOVER REQUIRED message from the source eNB to the MME if this message prepares an Inter eNB Handover.

ATT_INTRA_ENB_HO ( M8009C6 ) +ATT_INTER_ENB_HO ( M8014C6 ) +INTER_ENB_S1_HO_ATT (M8014C18)

Intra eNBThe transmission of a RRC Connection Reconfiguration message sent by the eNB to UE, which indicates a Handover Command to the UE. Updated to the source cell.Inter eNB via X2The reception of an X2AP: Handover Request Acknowledge message from the target eNB.Inter eNB via S1This counter is updated following the reception of an S1AP: HANDOVER COMMAND message from the MME to the source eNB in case that this message is received in response to the preparation of an Inter eNB Handover.

No Separate Counters for HO execution attempts . NSN considering All HO preparation success's eligible for HO execution phase .

SUCC_INTRA_ENB_HO ( M8009C7) +SUCC_INTER_ENB_HO ( M8014C7 ) +INTER_ENB_S1_HO_SUCC (M8014C19)

Intra eNBThe reception of an internal UE Context Release Request for the handover on the source side. Updated to the source cell.Inter eNB via X2The reception of a X2AP: Release Resource message sent by the target eNB.Inter eNB via S1This counter is updated following the reception of an S1AP: UE CONTEXT RELEASE COMMAND message from the MME to the source eNB with the cause value Radio Network Layer (Successful Handover) in case that this message is received for an Inter eNB Handover.

No Separate Counters for inter Frequency HO preparation Phase . Total Interfrequency HO attempts Used for Success Rate calculation.


HO_INTFREQ_ATT ( M8021C0 )

Intra eNBThis counter is updated following the transmission of an RRC Connection Reconfiguration message sent by the eNB to the UE, which indicates a Handover Command to the UE in case that this message is sent in response to the preparation of an inter-frequency Intra eNB Handover. Inter eNB via X2This counter is updated following the receipt of an X2AP: HANDOVER REQUEST ACKNOWLEDGE message from the target eNB in case that this message is received in response to the preparation of an inter-frequency Inter eNB Handover. Inter eNB via S1This counter is updated following the receipt of an S1AP: HANDOVER COMMAND message from the MME in case that this message is received in response to the preparation of an inter-frequency Inter eNB Handover.

HO_INTFREQ_SUCC ( M8021C2 )

Intra eNBThe reception of an internal UE Context Release Request for the handover on the source side. Updated to the source cell.Inter eNB via X2This counter is updated following the receipt of an X2AP: UE CONTEXT RELEASE message from the target eNB for an inter-frequency Inter eNB HandoverInter eNB via S1This counter is updated following the receipt of an S1AP: UE CONTEXT RELEASE COMMAND message from the MME with the cause value Radio Network Layer (Successful Handover) in case that this message is received for an inter-frequency Inter eNB Handover.

ISYS_HO_PREP ( M8016C14 )

HO to WCDMA :Transmission of a S1AP: HANDOVER REQUIRED message to source MME for an Inter System Handover. This counter is updated for the source cell of the handover.

ISYS_HO_ATT ( M8016C21 )

HO to WCDMA :Updated when a S1AP: HANDOVER COMMAND message is received from MME for an Inter System Handover. This counter is updated for the source cell of the handover

ISYS_HO_SUCC ( M8016C23 )

M8013C5:SIGN_CONN_ESTAB_COMP


Updated when a S1AP: UE CONTEXT RELEASE COMMAND message is received from MME with Cause value "Radio Network Layer" (Successful Handover) for an Inter System Handover. This counter is updated for the source cell of the handover.

Preparation phase counters not available .

ISYS_HO_GERAN_SRVCC_ATT ( M8016C33 )

LTE To GSM SRVCC :Reception of a S1AP: HANDOVER COMMAND message (source eNB <- MME; 3GPP TS 36.413) in case this message is received in response to the preparation of an Inter System Handover to GERAN with SRVCC (Single Radio Voice Call Continuity, 3GPP TS 23.216).

Can Use all preparation phase Successes to Execution attempts . ISYS_HO_GERAN_SRVCC_ATT ( M8016C33 )

ISYS_HO_GERAN_SRVCC_SUCC ( M8016C34 )

Reception of a S1AP: UE CONTEXT RELEASE COMMAND message (source eNB <- MME; 3GPP TS 36.413) with Cause value "Radio Network Layer (Successful Handover)" in case this message is received for an Inter System Handover to GERAN with SRVCC (Single Radio Voice Call Continuity, 3GPP TS 23.216).

Stepped at reception of RRC message RRC Connection Setup Complete at eNB end.The reception of the first message from MME which succeeds the S1AP:INITIAL UE message on a UE-associated logical S1-connection

S1AP_NAS_DOWNLINK ( M8000C30 )

UE_LOG_S1_SETUP ( M8000C12 )

INI_CONT_STP_COMP ( M8000C1 )

INI_CONT_STP_REQ ( M8000C0 )

M8013C17:SIGN_CONN_ESTAB_ATT_MO_S +M8013C18:SIGN_CONN_ESTAB_ATT_MT +M8013C19:SIGN_CONN_ESTAB_ATT_MO_D +M8013C20:SIGN_CONN_ESTAB_ATT_OTHERS +M8013C21:SIGN_CONN_ESTAB_ATT_EMG

Signaling Connection Establishment attempts due to MO-Signaling / MO-Data / MT - Access / Others / Emergency Calls .

The receipt of an RRC Connection Request message sent by the UE to eNB. Note: If a UE (erroneously) sends this message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.No Separate Counters for RRC

Connection re-attempt . If a UE (erroneously) sends RRC Connection message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.

The number of Downlink NAS Transport messages received by the eNB.

The establishment of UE-associated logical S1-connection is initiated by the reception of the first NAS signaling message within the RRC Connection Establishment.

The number of successful Initial Context Setup completions.

The number of Initial Context Setup Requests

No Separate Counters for RRC Connection establishment due to MO-DATA

No Separate Counters for RRC Connection establishment due to MT-ACCESS

SIGN_CONN_ESTAB_ATT_MO_D ( M8013C19)

The number of Signaling Connection Establishment attempts for mobile originated data connections. From UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED is started.

SIGN_CONN_ESTAB_ATT_MT ( M8013C18 )

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.No Separate Counters for RRC

Connection re-attempt . If a UE (erroneously) sends RRC Connection message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.No Separate Counters for RRC Connection re-attempt . If a UE (erroneously) sends RRC Connection message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.No Separate Counters for S1 signalling connection establishments with Establishment cause Mobile Originating Data.No Separate Counters for S1 signalling connection establishments with Establishment cause Mobile Terminating Access.

No Separate Counters for S1 signalling connection attempts with Establishment cause Mobile Originating Data.

No Separate Counters for S1 signalling connection attempts with Establishment cause Mobile terminating Access.

EPS_BEARER_STP_COM_INI_QCI1 ( M8006C35 )+ EPS_BEARER_STP_COM_INI_QCI_2 ( M8006C168 )+ EPS_BEARER_STP_COM_INI_QCI_3 ( M8006C169 ) + EPS_BEARER_STP_COM_INI_QCI_4 ( M8006C170 )+ EPS_BEAR_STP_COM_INI_NON_GBR ( M8006C36 )

The number of initial EPS bearer setup completions per QCI. Each bearer of the E-RAB Setup List IE is counted.

EPS_BEARER_STP_ATT_INI_QCI1 ( M8006C17) + EPS_BEARER_STP_ATT_INI_QCI_2 ( M8006C162 ) + EPS_BEARER_STP_ATT_INI_QCI_3 ( M8006C163 ) + EPS_BEARER_STP_ATT_INI_QCI_4 ( M8006C164 )+ EPS_BEAR_STP_ATT_INI_NON_GBR ( M8006C18 )

The number of initial EPS bearer setup attempts per QCI1. Each bearer of the E-RAB to Be Setup List IE is counted

SIGN_CONN_ESTAB_COMP_EMG

Equivalent Counters not available




The number of Signalling Connection Establishment completions for emergency calls

SIGN_CONN_ESTAB_ATT_EMG ( M8013C21 )

Number of Signaling Connection Establishment attempts for emergency calls

No Separate Counters for RRC Connection re-attempt . If a UE (erroneously) sends RRC Connection message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.No Separate Counters for S1 signalling connection establishments with Establishment cause Emergency Calls

No Separate Counters for S1 signalling connection attempts with Establishment cause Emergency Calls



EPS_BEARER_SETUP_COMPLETIONS (M8006C1) - [ EPS_BEARER_STP_COM_INI_QCI1 ( M8006C35 )+ EPS_BEARER_STP_COM_INI_QCI_2 ( M8006C168 )+ EPS_BEARER_STP_COM_INI_QCI_3 ( M8006C169 ) + EPS_BEARER_STP_COM_INI_QCI_4 ( M8006C170 )+ EPS_BEAR_STP_COM_INI_NON_GBR ( M8006C36 ) ]

The number of EPS bearer setup completions. Each bearer of the "E-RAB Setup List" IE is counted. ( All intial context setup counters are subtracted from Parent )

EPS_BEARER_SETUP_ATTEMPTS ( M8006C0) - [ EPS_BEARER_STP_ATT_INI_QCI1 ( M8006C17) + EPS_BEARER_STP_ATT_INI_QCI_2 ( M8006C162 ) + EPS_BEARER_STP_ATT_INI_QCI_3 ( M8006C163 ) + EPS_BEARER_STP_ATT_INI_QCI_4 ( M8006C164 )+ EPS_BEAR_STP_ATT_INI_NON_GBR ( M8006C18 ) ]

The number of EPS bearer setup attempts. Each bearer of the "E-RAB to Be Setup List" IE is counted.

EPS_BEAR_SET_COM_ADDIT_QCI1 ( M8006C44 ) ;EPS_BEARER_STP_COM_ADD_QCI_2 ( M8006C171 ) ;EPS_BEARER_STP_COM_ADD_QCI_3 ( M8006C172 );EPS_BEARER_STP_COM_ADD_QCI_4 ( M8006C173 )

This measurement provides the number of additional EPS bearer setup completions for GBR DRBs of QCI 1 / QCI 2 / QCI 3 / QCI 4 characteristics

EPS_BEAR_SET_ATT_ADD_QCI_1 ( M8006C26) ;EPS_BEARER_STP_ATT_ADD_QCI_2 ( M8006C165 ) ;EPS_BEARER_STP_ATT_ADD_QCI_3 ( M8006C166 );EPS_BEARER_STP_ATT_ADD_QCI_4 ( M8006C167 )

This measurement provides the number of additional EPS bearer setup attempts for GBR DRBs of QCI 1 / QCI 2 / QCI 3 / QCI 4 characteristics

DENOM_RRC_CONN_UE ( M8001C319 )

RRC Connected UEs Max ( M8001C200)



PDCP_SDU_VOL_DL ( M8012C20 )

SUM_RRC_CONN_UE ( M8001C318 )

This Measurement provides the sum of sampled values for measuring the number of simultaneously RRC connected UE's .This counter divided by the denominator DENOM_RRC_CONN_UE provides the average number of RRC connected Ues per cell .

The number of sample taken for counter SUM_RRC_CONN_UE used as a denominator for average calculation

The highest value for number of UEs in RRC_CONNECTED state over the measurement period.

The measurement gives indication of the eUu interface traffic load by reporting the sum of transmitted PDCP SDU's related traffic volumes.



ACTIVE_TTI_DL ( M8012C90 )


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

Active ERAB Rel QCI1 + Active ERAB Rel QCI2 + Active ERAB Rel QCI3 + Active ERAB Rel QCI4 + Active ERAB Rel non GBR ( M8006C176 +M8006C177+ M8006C178+M8006C179+M8006C180 )

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



ERAB Active Time QCI1 + ERAB Active Time QCI2 + ERAB Active Time QCI3 + ERAB Active Time QCI4 + ERAB Active Time nonGBR ( M8006C181+M8006C182+M8006C183+M8006C184+M8006C185 )

When user data are transferred the in-session activity time is aggregated during the E-RAB lifetime. At the end of the measurement period and when E-RAB is released the sum counter for all E-RABs with QCI1 / QCI2/QCI3/QCI4/Non-GBR QCI characteristics shall be updated.

ERAB Active Time QCI1 / ERAB Active Time QCI2 / ERAB Active Time QCI3 / ERAB Active Time QCI4 / ERAB Active Time nonGBR ( M8006C181/M8006C182/M8006C183/M8006C184/M8006C185 )


Active ERAB Rel QCI1 / Active ERAB Rel QCI2 / Active ERAB Rel QCI3 / Active ERAB Rel QCI4 / Active ERAB Rel non GBR ( M8006C176/M8006C177/M8006C178/M8006C179/M8006C180 )


M8006C12:ENB_EPS_BEARER_REL_REQ_RNL +M8006C13:ENB_EPS_BEARER_REL_REQ_OTH +M8006C14:ENB_EPS_BEARER_REL_REQ_TNL

The number of E-RABs requested to be released in case a Radio Link Failure / Other causes / Transport Layer Cause is detected by eNB.

M8006C10:ENB_EPS_BEARER_REL_REQ_NORM+M8006C15:ENB_EPSBEAR_REL_REQ_RNL_REDIR

The number of eNB-initiated EPS Bearer Release requests due to the UE inactivity. In case of the UE context release request, all the established EPS Bearers are counted.

The number of eNB-initiated EPS Bearer Release requests due Redirect (release due to RNL E-UTRAN generated reason or RNL Inter-RAT Redirection)

M8006C6:EPC_EPS_BEARER_REL_REQ_NORM +M8006C7:EPC_EPS_BEARER_REL_REQ_DETACH

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.

KPI Class KPI Name

Availability

Availability

Mobility



Mobility Success Rate ( Considering LTE to WCDMA HO alone in non-LTE system & Load Balancing between LTE InterFreq & WCDMA Target )

Mobility

Accessibility

Mobility Success Rate ( Considering LTE to GSM SRVCC alone in non-LTE system & Load Balancing between LTE InterFreq & WCDMA Target )


Accessibility

Accessibility

Accessibility

Accessibility

Accessibility

Accessibility

Accessibility

Accessibility

















Integrity

Integrity




Retainability

Retainability



KPI Formula Unit O - O Comparision

%

%

%





Mobility Success Rate ( % ) = 100* [ ( pmHoPrepSuccLteIntraF + pmHoPrepSuccLteInterF + pmHoPrepSucc - pmHoPrepSuccLb -pmHoPrepSuccLteInterFLb - pmHoPrepSuccLteInterFMbms) / ( pmHoPrepAttLteIntraF + pmHoPrepAttLteInterF + pmHoPrepAtt- pmHoPrepAttLb -pmHoPrepAttLteInterFLb - pmHoPrepAttLteInterFMbms ) ] * [ ( pmHoExeSuccLteIntraF + pmHoExeSuccLteInterF + pmHoExeSucc - pmHoExeSuccLb -pmHoExeSuccLteInterFLb - pmHoExeSuccLteInterFMbms) / ( pmHoExeAttLteIntraF + pmHoExeAttLteInterF + pmHoExeAtt - pmHoExeAttLb -pmHoExeAttLteInterFLb - pmHoExeAttLteInterFMbms) ]

1. No Preparation Phase counters for InterFrequency HO, Load Balancing HO in NSN

2. Intra Frequency ( Intra eNB ,Inter eNB via X2 ,Inter eNB via S1 ) ,Inter Frequency ( Intra eNB ,Inter eNB via X2 ,Inter eNB via S1 ) ,IRAT HO & Load Balancing HO Type Preparation Phase Successes taken as input for Execution Phase Attempts in NSN ( Causes difference in HO time as compared with E/// )

3.In NSN , there is no counters available for MBMS Handover and Load Based HO towards UTRAN Target

%

%








%

%

%

%

%

%

#

#
















1. Equivalent KPI available from NSN RL 50 / RL 35 release 2. Sampling Interval :E/// - 5 sNSN - 1s


1 . In RL 40 / RL 25 Release euivalent counter is available for direct mapping2. Sampling Interval :E/// - 5 sNSN - 4s

ms

ms

Kbps

Kbps

Kbps

Kbps

Kbps

Kbps

%

%








RL 50 / RL 35 Release KPI ( LTE_5292d) more suitable for mapping .











drops/s

drops/s

%












3. Closest Match

KPI ID KPI Name

LTE_5001a

LTE_5002a

Cell Availability




Custom KPIInitial E-RAB Establishment Success Rate

Custom KPI

Custom KPI

Custom KPI

Custom KPI

LTE_5242a







LTE_5134a

LTE_5293c

LTE_5304a

LTE_5310a




LTE_5292c ( RL 40 / RL 25) -----------------------------------------LTE_5292d ( RL 50 / RL35 )



LTE_5289c ( RL 40 / RL 25 ) -----------------------------------------LTE_5289d ( RL 50 / RL 35)




( LTE_5581a / 60 )

Custom KPI





KPI formula Unit

%

Cell Avail=(Samples Cell Avail/Samples Cells)*100% %

%


100 * [ ( Intra Freq HO preparation Success + Inter Freq HO preparation Success + IRAT ( WCDMA ) Ho Preparation Success - UTRAN LB Preparation Success - InterFreq LB Preparation Success -InterFreq LB Preparation Success due to MBMS ) / ( Intra Freq HO preparation Attempts + Inter Freq HO preparation Attempts + IRAT ( WCDMA ) Ho Preparation Attempts - UTRAN LB Preparation Attempts - InterFreq LB Preparation Attempts -InterFreq LB Preparation Attempts due to MBMS ) ] * [ (Intra Freq HO Execution Success + Inter Freq HO Execution Success + IRAT ( WCDMA ) Ho Execution Success - UTRAN LB Execution Success - InterFreq LB Execution Success - InterFreq LB Execution Success due to MBMS ) / ( Intra Freq HO Execution Attempts + Inter Freq HO Execution Attempts + IRAT ( WCDMA ) Ho Execution Attempts - UTRAN LB Execution Attempts - InterFreq LB Execution Attempts - InterFreq LB Execution Attempts due to MBMS ) ]

%

%

100 * [ ( Intra Freq HO preparation Success + Inter Freq HO preparation Success + SRVCC Ho Preparation Success - UTRAN LB Preparation Success - InterFreq LB Preparation Success -InterFreq LB Preparation Success due to MBMS ) / ( Intra Freq HO preparation Attempts + Inter Freq HO preparation Attempts + SRVCC Ho Preparation Attempts - UTRAN LB Preparation Attempts - InterFreq LB Preparation Attempts -InterFreq LB Preparation Attempts due to MBMS ) ] * [ (Intra Freq HO Execution Success + Inter Freq HO Execution Success + SRVCC Ho Execution Success - UTRAN LB Execution Success - InterFreq LB Execution Success - InterFreq LB Execution Success due to MBMS ) / ( Intra Freq HO Execution Attempts + Inter Freq HO Execution Attempts + SRVCC Ho Execution Attempts - UTRAN LB Execution Attempts - InterFreq LB Execution Attempts - InterFreq LB Execution Attempts due to MBMS ) ]



%

%

%

%

#

#




LatencyAvgDL=PDCP SDU delay on DL DTCH Mean ms

ms

Kbps

Kbps

Kbps

%

%







# / s

# / s

%




KPI Class KPI Name

Availability

Availability

Mobility



Mobility Success Rate ( Considering LTE to WCDMA HO alone in non-LTE system & Load Balancing between LTE InterFreq & WCDMA Target )

Mobility

Accessibility

Mobility Success Rate ( Considering LTE to GSM SRVCC alone in non-LTE system & Load Balancing between LTE InterFreq & WCDMA Target )


Accessibility

Accessibility

Accessibility

Accessibility





Accessibility

Accessibility

Accessibility

Accessibility













Integrity

Integrity




Retainability

Retainability



Counters used in KPI KPI Formula





pmHoPrepSuccLteIntraF ;pmHoPrepSuccLteInterF ;pmHoPrepSucc (MO Class : UtranCellRelation );pmHoPrepSuccLb (MO Class : UtranCellRelation ) ;pmHoPrepSuccLteInterFLb ;pmHoPrepSuccLteInterFMbms ;pmHoPrepAttLteIntraF ;pmHoPrepAttLteInterF ;pmHoPrepAtt (MO Class : UtranCellRelation );pmHoPrepAttLb (MO Class : UtranCellRelation ) ;pmHoPrepAttLteInterFLb ;pmHoPrepAttLteInterFMbms;pmHoExeSuccLteIntraF ;pmHoExeSuccLteInterF ;pmHoExeSucc (MO Class : UtranCellRelation );pmHoExeSuccLb (MO Class : UtranCellRelation ) ;pmHoExeSuccLteInterFLb ;pmHoExeSuccLteInterFMbms ;pmHoExeAttLteIntraF ;pmHoExeAttLteInterF ;pmHoExeAtt (MO Class : UtranCellRelation ) ;pmHoExeAttLb (MO Class : UtranCellRelation ) ;pmHoExeAttLteInterFLb ;pmHoExeAttLteInterFMbms ;


pmHoPrepSuccLteIntraF ;pmHoPrepSuccLteInterF ;pmHoPrepSucc (MO Class : UtranCellRelation );pmHoPrepSuccLb (MO Class : UtranCellRelation ) ;pmHoPrepSuccLteInterFLb ;pmHoPrepSuccLteInterFMbms ;pmHoPrepAttLteIntraF ;pmHoPrepAttLteInterF ;pmHoPrepAtt (MO Class : UtranCellRelation );pmHoPrepAttLb (MO Class : UtranCellRelation ) ;pmHoPrepAttLteInterFLb ;pmHoPrepAttLteInterFMbms;pmHoExeSuccLteIntraF ;pmHoExeSuccLteInterF ;pmHoExeSucc (MO Class : UtranCellRelation );pmHoExeSuccLb (MO Class : UtranCellRelation ) ;pmHoExeSuccLteInterFLb ;pmHoExeSuccLteInterFMbms ;pmHoExeAttLteIntraF ;pmHoExeAttLteInterF ;pmHoExeAtt (MO Class : UtranCellRelation ) ;pmHoExeAttLb (MO Class : UtranCellRelation ) ;pmHoExeAttLteInterFLb ;pmHoExeAttLteInterFMbms ;


pmRrcConnEstabSucc ;pmRrcConnEstabAtt ;pmRrcConnEstabAttReatt ;pmS1SigConnEstabSucc ;pmS1SigConnEstabAtt ;pmErabEstabSuccInit ;pmErabEstabAttInit ;


pmRrcConnEstabSuccMod ;pmRrcConnEstabSuccMta ;pmRrcConnEstabAttMod ;pmRrcConnEstabAttMta ;pmRrcConnEstabAttReattMod ;pmRrcConnEstabAttReattMta ;pmS1SigConnEstabSuccMod ;pmS1SigConnEstabSuccMta ;pmS1SigConnEstabAttMod ;pmS1SigConnEstabAttMta ;pmErabEstabSuccInitQci ;pmErabEstabAttInitQci ;


pmRrcConnEstabSuccEm pmRrcConnEstabAttEmpmRrcConnEstabAttReattEmpmS1SigConnEstabSuccEmpmS1SigConnEstabAttEm pmErabEstabSuccInitArppmErabEstabAttInitArp


pmMBMSSessionEstabSucc ;pmMBMSSessionEstabAtt ;


pmErabEstabSuccAdded ;pmErabEstabAttAdded ;


pmErabEstabSuccAddedQci ;pmErabEstabAttAddedQci ;


pmErabEstabSuccAddedArp ; pmErabEstabAttAddedArp ;






pmPdcpLatTimeDl ;pmPdcpLatPktTransDl ;


pmPdcpLatTimeDlQci ;pmPdcpLatPktTransDlQci ;


pmPdcpVolDlDrb ;pmPdcpVolDlDrbLastTTI ;pmUeThpTimeDl ;


pmPdcpVolDlDrb ;pmSchedActivityCellDl ;


pmPdcpVolDlDrbQci ;pmPdcpVolDlDrbLastTTIQci ;pmDrbThpTimeDlQci ;


pmPdcpVolUlDrb ;pmPdcpVolUlDrbLastTTI ;pmUeThpTimeUl ;


pmPdcpVolDUlDrb ;pmSchedActivityCellUl ;


pmLcgThpVolUlLcg ;pmLcgThpTimeUlLcg ;


pmPdcpPktDiscDlPelr ;pmPdcpPktDiscDlPelrUu ;pmPdcpPktDiscDlHo ;pmPdcpPktReceivedDl ;pmPdcpPktFwdDl ;


pmPdcpPktLostUl ;pmPdcpPktReceivedUl ;


pmErabRelAbnormalEnbAct ;pmErabRelAbnormalMmeAct ;pmSessionTimeUe ;


pmErabRelAbnormalEnbActQci ;pmErabRelAbnormalMmeActQci ;pmSessionTimeDrbQci ;


pmErabRelAbnormalEnbAct ;pmErabRelAbnormalMmeAct ;pmErabRelAbnormalEnb ;pmErabRelNormalEnb ;pmErabRelMme ;


Comments_E/// Unit

%

%

%





1. Counters pmHoPrepSucc, pmHoPrepSuccLb, pmHoPrepAtt,pmHoPrepAttLb, pmHoExeSucc, pmHoExeSuccLb, pmHoExeAtt& pmHoExeAttLb refer to handovers to non-LTE systems andare NOT parents of the corresponding LTE handover counters.These counters exist in class UtranCellRelation for WCDMA andTDScdma handovers

2.Load balancing and eMBMS features can trigger handover withoutany mobility. Thus counters with "Lb" suffix (pmHoPrepSuccLb,pmHoPrepSuccLteInterFLb, pmHoPrepAttLb, pmHoPrepAttLteInterFLb, pmHoExeSuccLb, pmHoExeSuccLteInterFLb,pmHoExeAttLb & pmHoExeAttLteInterFLb) remove handoversthat occur due to load-balancing rather than mobility. CounterspmHoExeAttLteInterFMbms, pmHoExeSuccLteInterFMbms,pmHoPrepAttLteInterFMbms & pmHoPrepSuccLteInterFMbmsremove inter-frequency handovers that occur due to eMBMS rather than mobility.

%

%

1.Counters pmHoPrepSucc, pmHoPrepAtt, pmHoExeSucc & pmHoExeAtt refer to LTE to GSM SRVCC and are NOT parents of the Corresponding LTE handover counters.

2.Load balancing and eMBMS features can trigger handover withoutany mobility. Thus counters with "Lb" suffix (pmHoPrepSuccLb,pmHoPrepSuccLteInterFLb, pmHoPrepAttLb, pmHoPrepAttLteInterFLb, pmHoExeSuccLb, pmHoExeSuccLteInterFLb,pmHoExeAttLb & pmHoExeAttLteInterFLb) remove handoversthat occur due to load-balancing rather than mobility. CounterspmHoExeAttLteInterFMbms, pmHoExeSuccLteInterFMbms,pmHoPrepAttLteInterFMbms & pmHoPrepSuccLteInterFMbmsremove inter-frequency handovers that occur due to eMBMS rather than mobility.

%

%

Accessibility success rate for end-user eMBMS %

%

The impact of multiple E-RABs in the Initial context setup procedureis not considered in the RRC and S1 signalling part contribution.

The accessibility success rate for emergency callsthat are carried by E-RABs included in the Initial UE Context setup procedure.The counters are on cell level and per ARP (hence only include the ARP rangethat defines Emergency)

Accessibility success rate for end-user services which is carried by E-RABsincluded in the E-RAB setup procedure

%

%

#

#

ms

ms

Accessibility success rate for end-user services which is carried by E-RABsincluded in the E-RAB setup procedure per QCI

Accessibility success rate for emergency calls which is carried by E-RABsincluded in the E-RAB setup procedure

This KPI measures the impact on the end user. NOTE that the latency willincrease with more instantaneously active UEs and will also depend on thescheduling algorithm(s) being used.

This KPI measures the impact on the end user. NOTE that the latency willincrease with more instantaneously active UEs and will also depend on thescheduling algorithm(s) being used, especially for the specific QCI.

Kbps

Kbps

Kbps

Kbps

1 . For traffic, which uses small SDU (e.g. VoLTE), the throughputmay not be a good measurement to evaluate performance, sincemost of the traffic may only use a single TTI and may be countedin pmPdcpVolDlDrbLastTti leaving minimal net volume if any, on thenumerator.2. For cases where pmUeThpTimeDl is small and / or wherepmPdcpVolDlDrb is similar magnitude to pmPdcpVolDlDrbLastTti(causing a small numerator from two large values), caution should beused in using the metric as the result may be ill-conditioned.

1. In many early deployments with a small number of simultaneous users (at TTI granularity), it is likely that per-UE throughput will be greater than cell throughput. However as the market matures and there are consequently moresimultaneous users (at TTI granularity), then it is likely that per-UE throughput will reduce, while cell throughput will show minimal change (or possibly slight increase) and thus cell throughput will exceed the per-UE throughput.

2.If DL Carrier Aggregation is active, the PDCP counters (volume & time) for a cell will reflect both its own Pcell traffic and also its own traffic carried on a different Scell. It will NOT show any traffic which this cell supports as an Scell

1. This KPI measures the impact on the end user. DL Throughput for both AM and UM for end-user services (defined by QCI)

2.Usually Throughput may not be a good measurement to evaluateperformance on services that uses RLC unacknowledged mode (since they are usually of the delay sensitive type).For QCI, which use small SDU (e.g. VoLTE), the throughput may not be a good measurement to evaluate performance, since most of the traffic may only use a single TTI and may be counted in pmPdcpVolDlDrbLastTtiQci leaving minimal net volume if any, on the numerator.

1. This KPI measures the impact on the end user. For traffic which use small SDU(e.g. VoLTE), the throughput may not be a good measurement to evaluate performance, since most of the traffic may only use a single TTI and may be excluded from the counters.2.For traffic, which uses small SDU (e.g. VoLTE), the throughput may not be a good measurement to evaluate performance, since most of the traffic may only use a single TTI and may be counted in the "LastTti" leaving minimal net volume if any, on the numerator.

Kbps

Kbps

%

%

drops/s

DL packet error loss rate for the UE is given by the following equation.The counters are all on cell level,

Since the KPI measures the impact of the network on the enduser, it also includes releases initiated by the MME. To observe theimpact of the RBS only, remove the pmErabRelAbnormalMmeActfrom the formula. The contribution of several components includingpmErabRelAbnormalEnbActTnFail and pmErabRelAbnormalEnbActCdtare not part of the 3GPP 32.450 definition of the KPI. However,Ericsson thinks it is important to include these cases even if there is no S1AP messages for these cases (the 32.425 have its triggers built on S1AP triggers).To achieve the number of minutes per drop, the multiplicative inverse of the E-RAB Retainability together with unit transformation from seconds to minutes can be used.

drops/s

%

To achieve the number of minutes per drop, the multiplicative inverse of the E-RAB Retainability together with unit transformation from seconds to minutes can be used

O - O Comparision KPI ID KPI Name

LTE_5001a

LTE_5002a

Cell Availability









Custom KPI







Custom KPI

Custom KPI

Custom KPI










Custom KPI

LTE_5242a


LTE_5134a




1. Equivalent KPI available from NSN RL 50 / RL 35 release 2. Sampling Interval :E/// - 5 sNSN - 1s


1 . In RL 40 / RL 25 Release euivalent counter is available for direct mapping2. Sampling Interval :E/// - 5 sNSN - 4s






LTE_5293c



LTE_5292c ( RL 40 / RL 25) -----------------------------------------LTE_5292d ( RL 50 / RL35 )





LTE_5304a

LTE_5310a

( LTE_5581a / 60 )


LTE_5289c ( RL 40 / RL 25 ) -----------------------------------------LTE_5289d ( RL 50 / RL 35)









Custom KPI








3. Closest Match


Counters used in KPI

M8020C3:SAMPLES_CELL_AVAILM8020C4:SAMPLES_CELL_PLAN_UNAVAILM8020C6:DENOM_CELL_AVAIL

M8020C3:SAMPLES_CELL_AVAILM8020C6:DENOM_CELL_AVAIL

INTRA_ENB_HO_PREP ( M8009C2 ) ;INTER_ENB_HO_PREP ( M8014C0 ) ;INTER_ENB_S1_HO_PREP (M8014C14 ) ;ATT_INTRA_ENB_HO ( M8009C6 ) ;ATT_INTER_ENB_HO ( M8014C6 ) ;INTER_ENB_S1_HO_ATT (M8014C18) ;SUCC_INTRA_ENB_HO ( M8009C7) ;SUCC_INTER_ENB_HO ( M8014C7 ) ;INTER_ENB_S1_HO_SUCC (M8014C19) ;HO_INTFREQ_ATT ( M8021C0 ) ;HO_INTFREQ_SUCC ( M8021C2 ) ;ISYS_HO_PREP ( M8016C14 ) ;ISYS_HO_ATT ( M8016C21 ) ;ISYS_HO_SUCC ( M8016C23 ) ;HO_LB_SUCC (M8021C24);HO_LB_ATT (M8021C23);

INTRA_ENB_HO_PREP ( M8009C2 ) ;INTER_ENB_HO_PREP ( M8014C0 ) ;INTER_ENB_S1_HO_PREP (M8014C14 ) ;ATT_INTRA_ENB_HO ( M8009C6 ) ;ATT_INTER_ENB_HO ( M8014C6 ) ;INTER_ENB_S1_HO_ATT (M8014C18) ;SUCC_INTRA_ENB_HO ( M8009C7) ;SUCC_INTER_ENB_HO ( M8014C7 ) ;INTER_ENB_S1_HO_SUCC (M8014C19) ;HO_INTFREQ_ATT ( M8021C0 ) ;HO_INTFREQ_SUCC ( M8021C2 ) ;ISYS_HO_GERAN_SRVCC_ATT ( M8016C33 ) ;ISYS_HO_GERAN_SRVCC_SUCC ( M8016C34 ) ;HO_LB_SUCC (M8021C24);HO_LB_ATT (M8021C23);

M8013C5:SIGN_CONN_ESTAB_COMP ;M8013C17:SIGN_CONN_ESTAB_ATT_MO_S ;M8013C18:SIGN_CONN_ESTAB_ATT_MT ;M8013C19:SIGN_CONN_ESTAB_ATT_MO_D; M8013C20:SIGN_CONN_ESTAB_ATT_OTHERS; M8013C21:SIGN_CONN_ESTAB_ATT_EMG;M8000C30 : S1AP_NAS_DOWNLINK ;M8000C12 : UE_LOG_S1_SETUP ; M8000C1 :INI_CONT_STP_COMP ; M8000C0 :INI_CONT_STP_REQ ;

M8013C18:SIGN_CONN_ESTAB_ATT_MT ;M8013C19:SIGN_CONN_ESTAB_ATT_MO_D; EPS_BEARER_STP_COM_INI_QCI1 ( M8006C35 ) , EPS_BEARER_STP_COM_INI_QCI_2 ( M8006C168 ) , EPS_BEARER_STP_COM_INI_QCI_3 ( M8006C169 ) ,EPS_BEARER_STP_COM_INI_QCI_4 ( M8006C170 ),EPS_BEAR_STP_COM_INI_NON_GBR ( M8006C36 ) ,EPS_BEARER_STP_ATT_INI_QCI1 ( M8006C17) , EPS_BEARER_STP_ATT_INI_QCI_2 ( M8006C162 ) , EPS_BEARER_STP_ATT_INI_QCI_3 ( M8006C163 ) ,EPS_BEARER_STP_ATT_INI_QCI_4 ( M8006C164 ),EPS_BEAR_STP_ATT_INI_NON_GBR ( M8006C18 )

EPS_BEARER_SETUP_COMPLETIONS (M8006C1) ; EPS_BEARER_STP_COM_INI_QCI1 ( M8006C35 );EPS_BEARER_STP_COM_INI_QCI_2 ( M8006C168 ) ; EPS_BEARER_STP_COM_INI_QCI_3 ( M8006C169 ) ; EPS_BEARER_STP_COM_INI_QCI_4 ( M8006C170 ) ;EPS_BEAR_STP_COM_INI_NON_GBR ( M8006C36 ) ; EPS_BEARER_SETUP_ATTEMPTS ( M8006C0) ; EPS_BEARER_STP_ATT_INI_QCI1 ( M8006C17) ; EPS_BEARER_STP_ATT_INI_QCI_2 ( M8006C162 ) ; EPS_BEARER_STP_ATT_INI_QCI_3 ( M8006C163 ) ; EPS_BEARER_STP_ATT_INI_QCI_4 ( M8006C164 ) ; EPS_BEAR_STP_ATT_INI_NON_GBR ( M8006C18 )

RRC_CONN_UE_AVG ( M8001C199 )

PDCP_SDU_DELAY_DL_DTCH_MEAN ( M8001C2 )

EPS_BEAR_SET_COM_ADDIT_QCI1 ( M8006C44 ) ;EPS_BEARER_STP_COM_ADD_QCI_2 ( M8006C171 ) ;EPS_BEARER_STP_COM_ADD_QCI_3 ( M8006C172 );EPS_BEARER_STP_COM_ADD_QCI_4 ( M8006C173 ) ;EPS_BEAR_SET_ATT_ADD_QCI_1 ( M8006C26) ;EPS_BEARER_STP_ATT_ADD_QCI_2 ( M8006C165 ) ;EPS_BEARER_STP_ATT_ADD_QCI_3 ( M8006C166 );EPS_BEARER_STP_ATT_ADD_QCI_4 ( M8006C167 )

SUM_RRC_CONN_UE ( M8001C318 ) ;DENOM_RRC_CONN_UE ( M8001C319 )

PDCP_RET_DL_DEL_MEAN_QCI_1 ( M8001C269) , PDCP_RET_DL_DEL_MEAN_QCI_2 ( M8001C270 ) , PDCP_RET_DL_DEL_MEAN_QCI_3 ( M8001C271 ),PDCP_RET_DL_DEL_MEAN_QCI_4 ( M8001C272 ),PDCP_RET_DL_DEL_MEAN_NON_GBR (M8001C270 )

M8012C143:PDCP_DATA_RATE_MEAN_DL_QCI_1

M8012C26:PDCP_DATA_RATE_MEAN_DL ;M8012C20:PDCP_SDU_VOL_DL ;M8012C90:ACTIVE_TTI_DL ;

M8012C19:PDCP_SDU_VOL_UL ;M8012C89:ACTIVE_TTI_UL ;M8012C23:PDCP_DATA_RATE_MEAN_UL ;

M8001C154:PDCP_SDU_DL ;M8001C259:PDCP_SDU_LOSS_DL ;

M8001C153:PDCP_SDU_UL ;M8001C254:PDCP_SDU_LOSS_UL ;



M8006C176:ERAB_REL_ENB_ACT_QCI1M8006C177:ERAB_REL_ENB_ACT_QCI2M8006C178:ERAB_REL_ENB_ACT_QCI3M8006C179:ERAB_REL_ENB_ACT_QCI4M8006C180:ERAB_REL_ENB_ACT_NON_GBRM8006C181:ERAB_IN_SESSION_TIME_QCI1M8006C182:ERAB_IN_SESSION_TIME_QCI2M8006C183:ERAB_IN_SESSION_TIME_QCI3M8006C184:ERAB_IN_SESSION_TIME_QCI4M8006C185:ERAB_IN_SESSION_TIME_NON_GBRM8006C12:ENB_EPS_BEARER_REL_REQ_RNL M8006C13:ENB_EPS_BEARER_REL_REQ_OTH M8006C14:ENB_EPS_BEARER_REL_REQ_TNLM8006C10:ENB_EPS_BEARER_REL_REQ_NORMM8006C15:ENB_EPSBEAR_REL_REQ_RNL_REDIRM8006C6:EPC_EPS_BEARER_REL_REQ_NORM M8006C7:EPC_EPS_BEARER_REL_REQ_DETACH

Logical formula


Cell Avail=(Samples Cell Avail/Samples Cells)*100%

100 * [ ( Intra Freq HO preparation Success + Inter Freq HO preparation Success + IRAT ( WCDMA ) Ho Preparation Success - UTRAN LB Preparation Success - InterFreq LB Preparation Success -InterFreq LB Preparation Success due to MBMS ) / ( Intra Freq HO preparation Attempts + Inter Freq HO preparation Attempts + IRAT ( WCDMA ) Ho Preparation Attempts - UTRAN LB Preparation Attempts - InterFreq LB Preparation Attempts -InterFreq LB Preparation Attempts due to MBMS ) ] * [ (Intra Freq HO Execution Success + Inter Freq HO Execution Success + IRAT ( WCDMA ) Ho Execution Success - UTRAN LB Execution Success - InterFreq LB Execution Success - InterFreq LB Execution Success due to MBMS ) / ( Intra Freq HO Execution Attempts + Inter Freq HO Execution Attempts + IRAT ( WCDMA ) Ho Execution Attempts - UTRAN LB Execution Attempts - InterFreq LB Execution Attempts - InterFreq LB Execution Attempts due to MBMS ) ]

100 * [ ( Intra Freq HO preparation Success + Inter Freq HO preparation Success + SRVCC Ho Preparation Success - UTRAN LB Preparation Success - InterFreq LB Preparation Success -InterFreq LB Preparation Success due to MBMS ) / ( Intra Freq HO preparation Attempts + Inter Freq HO preparation Attempts + SRVCC Ho Preparation Attempts - UTRAN LB Preparation Attempts - InterFreq LB Preparation Attempts -InterFreq LB Preparation Attempts due to MBMS ) ] * [ (Intra Freq HO Execution Success + Inter Freq HO Execution Success + SRVCC Ho Execution Success - UTRAN LB Execution Success - InterFreq LB Execution Success - InterFreq LB Execution Success due to MBMS ) / ( Intra Freq HO Execution Attempts + Inter Freq HO Execution Attempts + SRVCC Ho Execution Attempts - UTRAN LB Execution Attempts - InterFreq LB Execution Attempts - InterFreq LB Execution Attempts due to MBMS ) ]





LatencyAvgDL=PDCP SDU delay on DL DTCH Mean











KPI Formula Unit Comments_NSN

%

%

%


1) Sampling Interval : 10 s 2) Counter M8020C4 ( SAMPLES_CELL_PLAN_UNAVAIL )will be incremented when cell operational state in locked


1) Sampling Interval : 10 s 2) Counters will be incremented when cell operational state in enabled

100 * [ ( ATT_INTRA_ENB_HO +ATT_INTER_ENB_HO +INTER_ENB_S1_HO_ATT + ISYS_HO_ATT ) / ( INTRA_ENB_HO_PREP +INTER_ENB_HO_PREP +INTER_ENB_S1_HO_PREP + ISYS_HO_PREP) ] * [ (SUCC_INTRA_ENB_HO +SUCC_INTER_ENB_HO +INTER_ENB_S1_HO_SUCC +HO_INTFREQ_SUCC +ISYS_HO_SUCC - HO_LB_SUCC ) / ( ATT_INTRA_ENB_HO +ATT_INTER_ENB_HO +INTER_ENB_S1_HO_ATT +ISYS_HO_ATT +HO_INTFREQ_ATT - HO_LB_ATT) ]


%

%

100 * [ ( ATT_INTRA_ENB_HO +ATT_INTER_ENB_HO +INTER_ENB_S1_HO_ATT ) / ( INTRA_ENB_HO_PREP +INTER_ENB_HO_PREP +INTER_ENB_S1_HO_PREP ) ] * [ (SUCC_INTRA_ENB_HO +SUCC_INTER_ENB_HO +INTER_ENB_S1_HO_SUCC +HO_INTFREQ_SUCC +ISYS_HO_GERAN_SRVCC_SUCC - HO_LB_SUCC ) / ( ATT_INTRA_ENB_HO +ATT_INTER_ENB_HO +INTER_ENB_S1_HO_ATT +ISYS_HO_GERAN_SRVCC_ATT +HO_INTFREQ_ATT - HO_LB_ATT ) ]



NSN's own Initial E-RAB setup success Ratio LTE_5112b describes the setup success ratio of the elementaryinitial E-RAB setup procedure.It indicates the E-UTRAN contribution to network accessibilityfor the end-user, not the whole end-to-end service accessibility.

%

%

%



1. Counters NOT available for RRC connection establishments under different causes .

2. Counters NOT available for Initial signalling connection establishments under different causes.

3. Initial EPS bearer setup counters Mapping available for all QCI's ( GBR & NON- GBR )



All initial E-RAB setup attemps & establishments subtracted from total EPS bearer attemps for 1 to 1 mapping

%

#

Available from RL50 Release

sum( RRC_CONN_UE_AVG ) # Sampling Interval : 4 s


ms


Deviation Observed . Counters for Additional E-RAB Setup Attempts not available for Non-GBR QCI's


This KPI shows the retention period (delay) of a PDCP SDU (DL) inside eNB. Time from reception of IP packet to transmission of first packet over the Uu interface.


This KPI shows the retention period (delay) of a PDCP SDU (DL) inside eNB for QCI1 / QCI 2/QCI3/QCI4/non-GBR ( QCI5…9) DRBs. Time from reception of IP packet to transmission of first packet over the Uu interface.

Kbps


avg( PDCP_DATA_RATE_MEAN_DL ) [ RL 40 / RL 25 ]

------------------------------------------------------------8 * sum( PDCP_SDU_VOL_DL ) /sum( ACTIVE_TTI_DL ) [ RL 50 / RL 35 ]

Kbps

%

%

# / s

avg( PDCP_DATA_RATE_MEAN_UL ) [ RL 40 / RL 25 ]

------------------------------------------------------------8 * sum( PDCP_SDU_VOL_UL ) /sum( ACTIVE_TTI_UL ) [ RL 50 / RL 35]





# / s

%




MO Class Counter _ Ericsson Description_Ericsson

Availability pmCellDownTimeAuto

Availability pmCellDownTimeMan

Mobility pmHoPrepAttLteIntraF A better LTE cell is reported by the UE.

Mobility pmHoPrepSuccLteIntraF

Length of time the cell has been disabled due to a fault (system has set cell MO OperationalState to Disabled). The counter is only incremented when the RBS is operational.Length of time the cell has been disabled due to:- AdministrativeState of the cell MO or another MO the cell depends on has been set to Locked by the operatoror- the operator has performed a reconfiguration request on an Unlocked cell which requires the cell to be taken down temporarily.The counter is only incremented when the RBS is operational.


Mobility pmHoExeAttLteIntraF

Mobility pmHoExeSuccLteIntraF

Mobility pmHoPrepAttLteInterF

Mobility pmHoPrepSuccLteInterF



The number of attempts to start outgoing intra LTE inter frequency handover preparation.


Mobility pmHoExeAttLteInterF

Mobility pmHoExeSuccLteInterF





Number of handover to UTRAN or TD-SCDMA preparation attempts. A better UTRAN or TD-SCDMA cell is reported by the UE.

Number of successful handover to UTRAN or TD-SCDMA preparations. HANDOVER COMMAND received in the source eNodeB from the MME (S1 handover).

Mobility pmHoExeAtt




Mobility pmHoExeAtt


Mobility pmHoPrepSuccLb

Number of handover to UTRAN or TD-SCDMA execution attempts.MobilityFromEUTRACommand towards the UTRAN or TD-SCDMA cell is sent to the UE.

Number of successful handovers to UTRAN or TD-SCDMA.UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered (S1 handover) .

The number of attempts to start Single Radio Voice Call Continuity (SRVCC) handover preparation from LTE to GSM/EDGE Radio Access Network (GERAN). A better GERAN cell is reported by the UE and a VoIP bearer is established.

The number of successful Single Radio Voice Call Continuity (SRVCC) handover preparations from LTE to GSM/EDGE Radio Access Network (GERAN).HANDOVER COMMAND message is received by the source eNodeB from the MME (S1 handover), including a VoIP bearer.

The number of attempts to start Single Radio Voice Call Continuity (SRVCC) handover execution from LTE to GSM/EDGE Radio Access Network (GERAN).MobilityFromEUtraCommand including the Information on target RAT and cell is sent to the UE from the source cell, including a VoIP bearer.

The number of successful Single Radio Voice Call Continuity (SRVCC) handover executions from LTE to GSM/EDGE Radio Access Network (GERAN).UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered (S1 handover) and the UE has a VoIP bearer.

Number of successful handover to UTRAN preparations due to load balancing action

Mobility pmHoPrepSuccLteInterFLb

Mobility

Mobility pmHoPrepAttLb

Mobility pmHoPrepAttLteInterFLb

Mobility pmHoPrepAttLteInterFMbms

Mobility pmHoExeSuccLb

The number of successful outgoing intra LTE inter frequency handover preparations that was performed for load balancing reasons.

pmHoPrepSuccLteInterFMbms

The number of successful outgoing intra LTE inter frequency handover preparations that was performed due to MBMS Interest.

Number of handover to UTRAN preparation attempts due to load balancing actionThe number of attempts to start outgoing intra LTE inter frequency handover preparation due to load balancing.

The number of attempts to start outgoing intra LTE inter frequency handover preparation due to MBMS Interest.

Number of successful handovers to UTRAN due to load balancing action

Mobility pmHoExeSuccLteInterFLb

Mobility pmHoExeSuccLteInterFMbms

Mobility pmHoExeAttLb

The number of successful outgoing intra LTE inter frequency handovers that was performed for load balancing reasons.

The number of successful outgoing intra LTE inter frequency handovers that was performed due to MBMS Interest.

Number of handover to UTRAN execution attempts due to load balancing action

Mobility pmHoExeAttLteInterFLb

Mobility pmHoExeAttLteInterFMbms

pmRrcConnEstabSucc

pmRrcConnEstabAtt

pmRrcConnEstabAttReatt

pmS1SigConnEstabSucc

pmS1SigConnEstabAtt

pmErabEstabSuccInit

The number of outgoing intra LTE inter frequency handover execution attempts due to load balancing.

The number of outgoing intra LTE inter frequency handover execution attempts due to MBMS Interest.

Accessibility

Stepped at reception of RRC message RRC Connection Setup Complete at eNB end.

Accessibility

Stepped at reception of RRC message RRC Connection Request.

Accessibility

Stepped at reception of RRC message RRC Connection Request while an RRC Connection Setup is already ongoing for that S-TMSI. ( Repetetive Attempts from Same UE )

Accessibility

The total number of successful S1 signalling connection establishments.

Accessibility

This measurement provides the number of S1 Signalling connection establishment attempts for any establishment cause.

Accessibility

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.

pmErabEstabAttInit

pmRrcConnEstabSuccMod

pmRrcConnEstabSuccMta

pmRrcConnEstabAttMod

pmRrcConnEstabAttMta

pmRrcConnEstabAttReattMod

pmRrcConnEstabAttReattMta

pmS1SigConnEstabSuccMod

pmS1SigConnEstabSuccMta

pmS1SigConnEstabAttMod

pmS1SigConnEstabAttMta

Accessibility

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.

Accessibility

The total number of successful RRC Connection Establishments for Establishment cause Mobile Originating Data.

Accessibility

The total number of successful RRC Connection Establishments for Establishment cause Mobile Terminating Access.

Accessibility

The total number of RRC Connection Request attempts with Establishment cause Mobile Originating Data.

Accessibility

The total number of RRC Connection Request attempts with Establishment cause Mobile Terminating Access.

Accessibility

The total number of RRC Connection Request attempts that are considered as re-attempts for Establishment cause Mobile Originating Data.

Accessibility

The total number of RRC Connection Request attempts that are considered as re-attempts for Establishment cause Mobile Terminating Access.

Accessibility

The total number of successful S1 signalling connection establishments with Establishment cause Mobile Originating Data.

Accessibility

The total number of successful S1 signalling connection establishments with Establishment cause Mobile Terminating Access.

Accessibility

This measurement provides the number of S1 Signalling connection establishment attempts with RRC Connection Request Establishment cause Mobile Originating Data.

Accessibility

This measurement provides the number of S1 Signalling connection establishment attempts with RRC Connection Request Establishment cause Mobile Terminating Access.

pmErabEstabSuccInitQci

pmErabEstabAttInitQci

pmRrcConnEstabSuccEm

pmRrcConnEstabAttEm

pmRrcConnEstabAttReattEm

pmS1SigConnEstabSuccEm

pmS1SigConnEstabAttEm

pmErabEstabSuccInitArp

Accessibility

The total number of successful initial E-RAB setup per QCI.Compressed: True

Accessibility

The total number of initial E-RAB setup attempts per QCI.Compressed: True

Accessibility

The total number of successful RRC Connection Establishments for Establishment cause Emergency.

Accessibility

The total number of RRC Connection Request attempts with establishment cause emergency.

Accessibility

The total number of RRC Connection Request attempts that are considered as re-attempts for Establishment cause Emergency.

Accessibility

The total number of successful S1 signalling connection establishments with Establishment cause Emergency.

Accessibility

This measurement provides the number of S1 Signalling connection establishment attempts with RRC Connection Request Establishment cause Emergency.

Accessibility

The total number of successful initial E-RAB Establishments per ARP value.

[0]: N/A (unallowed ARP value)[1]: Sum of successful initial E-RAB Establishment with ARP priority value 1...[15]: Sum of successful initial E-RAB Establishment with ARP priority value 15

pmErabEstabAttInitArp

pmMBMSSessionEstabSucc

pmMBMSSessionEstabAtt

pmErabEstabSuccAdded

pmErabEstabAttAdded

pmErabEstabSuccAddedQci

pmErabEstabAttAddedQci

Accessibility

The total number of initial E-RAB Establishment attempts per ARP value. Initial E-RABs are all E-RABs present in the S1 message Initial Context Setup Request.

[0]: N/A (unallowed ARP value)[1]: Sum of initial E-RAB Establish Attempts with ARP priority value 1...[15]: Sum of initial E-RAB Establish Attempts with ARP priority value 15

Accessibility

The total number of MBMS sessions successfully established in eNB is incremented each time when the MBMS SESSON START RESPONSE is sent.

Accessibility

The total number of MBMS session establishment attempts is incremented each time when the MBMS SESSON START REQUEST is received.

Accessibility

The total number of successfully added E-RABs. Added E-RABs are all E-RABs present in S1 message E-RAB Setup Request.

Accessibility

The total number of added E-RAB Establishment attempts. Added E-RABs are all E-RABs present in S1 message E-RAB Setup Request.

Accessibility

The total number of successful additional E-RAB setup per QCI.

Compressed: True

Accessibility

The total number of additional E-RAB setup attempts per QCI.Compressed: True

pmErabEstabSuccAddedArp

pmErabEstabAttAddedArp

pmRrcConnLevSum

pmRrcConnLevSamp

pmRrcConnMax Peak Number of RRC Connected Users

Integrity pmPdcpLatTimeDl

Accessibility

The total number of successfully added E-RABs per ARP value. Added E-RABs are all E-RABs present in S1 message E-RAB Setup Request.

[0]: N/A (unallowed ARP value)[1]: Sum of successful added E-RABs established with ARP priority value 1...[15]: Sum of successful added E-RABs established with ARP priority value 15

Accessibility

The total number of added E-RAB Establishment attempts per ARP value. Added E-RABs are all E-RABs present in S1 message E-RAB Setup Request.

[0]: N/A (unallowed ARP value)[1]: Sum of added E-RAB Establish Attempts with ARP priority value 1...[15]: Sum of added E-RAB Establish Attempts with ARP priority value 15

Accessibility

Sum of all sample values recorded for "number of UEs in RRC_CONNECTED mode".

Accessibility

Number of times the corresponding Sum counter has accumulated a new sample. Associated ACC pmCounter pmRrcConnLevSum.

Accessibility

Aggregated DL Latency for a measurement period. The effective DL Latency time comprises the time from PDCP DRB SDU entering the buffer until the first data has been transmitted to the UE.


Integrity pmPdcpLatPktTransDl

Integrity pmPdcpVolDlDrb

Integrity pmPdcpVolDlDrbLastTTI

Integrity pmUeThpTimeDl

Integrity pmSchedActivityCellDl

Integrity pmDrbThpTimeDlQci

Number of DRB packets for downlink Latency measurements.


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 Bearers that has been transferred (UM and AM) in the downlink direction is measured on PCell.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/SCell(s)). 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 is measured on PCell.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 be sent over multiple cells (PCell/SCell(s)). The effective DL transport time, comprising 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, is registered on PCell.The aggregated number of ms in which DRB data was required to be scheduled in the downlink.

The DL transmission time used for DL DRB Throughput per QCI. It comprises of time periods from when the first piece of data in a data burst is transmitted until the second last piece of data in the data burst is transmitted.

pmErabRelAbnormalEnbAct

pmErabRelAbnormalMmeAct

pmSessionTimeUe

pmSessionTimeDrbQci

Retainability

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).

Retainability

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).

Retainability

This counters shows the accumulated active session time for all UEs in a cell. ( Unit : s )

Retainability

The session time aggregated for DRBs mapping to a QCI. Compressed: True

pmErabRelAbnormalEnb

pmErabRelNormalEnb

Retainability

pmErabRelAbnormalEnbActQci

The total number of active E-RABs released abnormally per cell per QCI for requests initiated by eNB (per cell per QCI). , except active E-RABs released due to successful HO. An E-RAB is considered to be active when there are data in the DL or UL queues for the E-RAB.

Compressed: True

Retainability

pmErabRelAbnormalMmeActQci

The total number of E-RAB Releases (per cell per QCI) initiated by the MME considered as abnormal. The counter is stepped if data was lost in either the UL or DL buffers. Type:Compressed PDF[0]: N/A[1]: Abnormal active E-RAB releases for E-RABs with QCI 1�.[255]: Abnormal active E-RAB releases for E-RABs with QCI 255

Compressed: True

Retainability

The total number of abnormal E-RAB Releases triggered by eNB per cell.

Retainability

The total number of normal E-RAB Releases triggered by eNB per cell.

pmErabRelMme

Retainability

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.

Triggering point O - O Comparision

Sampling Interval :E/// - 1 sNSN - 10 s

Intra eNB E/// - Updated in Source Cell after reception of Measurement report from UENSN - Updated in source cell after completion of admission control procedure in eNB on Target side.Inter eNB via X2E/// - Updated in Source Cell after reception of Measurement report from UENSN - Updated in source cell when HO decision made by source eNB after measurements reported by UE .Inter eNB via S1E/// - Updated in Source Cell after reception of Measurement report from UENSN - HANDOVER REQUIRED message from the source eNB to the MME if this message prepares an Inter eNB Handover.


Intra eNB E/// - Counter is incremented when the target cell informs the source cell that UE resources has been reserved for handover using internal RBS trigger .NSN - Updated in source cell after after sending HO command message to eNB .Inter eNB via X2E/// - On Reception of Handover Request acknowledge message the source eNB will increment this counterNSN - The reception of an X2AP: Handover Request Acknowledge message from the target eNB.Inter eNB via S1E/// - HANDOVER COMMAND message is received by the source eNodeB from the MMENSN - This counter is updated following the reception of an S1AP: HANDOVER COMMAND message from the MME to the source eNB


No Match

No Match

No Match

Intra eNB E/// - On Transmission of RRC CONNECTION RECONFIGURATION including "mobility Controlinformation " to UE from eNBNSN - NA Inter eNB via X2E/// - On Transmission of RRC CONNECTION RECONFIGURATION including "mobility Controlinformation " to UE from Source eNBNSN - NAInter eNB via S1E/// - On Transmission of RRC CONNECTION RECONFIGURATION including "mobility Controlinformation " to UE from source eNBIntra eNB E/// - Internal eNodeB trigger (corresponding to UE CONTEXT RELEASE) received when the UE has changed cell during a intra eNodeB handoverNSN - The reception of an internal UE Context Release Request for the handover on the source side. Updated to the source cell.Inter eNB via X2E/// - UE CONTEXT RELEASE received in the source eNodeB from the target eNodeB (X2 handover)NSN - The reception of a X2AP: Release Resource message sent by the target eNB.Inter eNB via S1E/// - UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered (S1 handover)NSN -This counter is updated following the reception of an S1AP: UE CONTEXT RELEASE COMMAND message from the MME to the source eNB


Intra eNB E/// - Updated in Source Cell after reception of Measurement report from UENSN - NAInter eNB via X2E/// - Updated in Source Cell after reception of Measurement report from UENSN - NAInter eNB via S1E/// - Updated in Source Cell after reception of Measurement report from UENSN - NA

Intra eNB E/// - Counter is incremented when the target cell informs the source cell that UE resources has been reserved for handover using internal RBS trigger .NSN - NAInter eNB via X2E/// - On Reception of Handover Request acknowledge message the source eNB will increment this counterNSN - NAInter eNB via S1E/// - HANDOVER COMMAND message is received by the source eNodeB from the MMENSN - NA

Closest Match

100 % Mapping

Intra eNB E/// - On Transmission of RRC CONNECTION RECONFIGURATION including "mobility Controlinformation " to UE from eNBNSN - Updated in source cell after after sending HO command message to eNB . Inter eNB via X2E/// - On Transmission of RRC CONNECTION RECONFIGURATION including "mobility Controlinformation " to UE from Source eNBNSN - The reception of an X2AP: Handover Request Acknowledge message from the target eNB.Inter eNB via S1E/// - On Transmission of RRC CONNECTION RECONFIGURATION including "mobility Controlinformation " to UE from Source eNBNSN - This counter is updated following the reception of an S1AP: HANDOVER COMMAND message from the MME to the source eNB


Intra eNB E/// - Internal eNodeB trigger (corresponding to UE CONTEXT RELEASE) received when the UE has changed cell during a intra eNodeB handoverNSN - The reception of an internal UE Context Release Request for the handover on the source side. Updated to the source cell.Inter eNB via X2E/// - UE CONTEXT RELEASE received in the source eNodeB from the target eNodeB (X2 handover)NSN - The reception of a X2AP: Release Resource message sent by the target eNB.Inter eNB via S1E/// - UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered (S1 handover)NSN -This counter is updated following the reception of an S1AP: UE CONTEXT RELEASE COMMAND message from the MME to the source eNB


HO To WCDMA E/// - Updated in Source Cell after reception of Measurement report from UENSN - Transmission of a S1AP: HANDOVER REQUIRED message to source MME

HO To WCDMA E/// - Updated when HANDOVER COMMAND received in the source eNodeB from the MME NSN - Transmission of a S1AP: HANDOVER REQUIRED message to source MME

No Match

Closest Match

No Match

100 % Match

Closest Match

No Match

HO To WCDMA E/// - Updated when MobilityFromEUTRACommand towards the UTRANNSN - NA

HO To WCDMA E/// - Updated when UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered

NSN - Updated when UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover TriggeredLTE To GSM SRVCC E/// - Updated in Source Cell after reception of Measurement report from UENSN - NA

LTE To GSM SRVCC E/// - Updated when HANDOVER COMMAND received in the source eNodeB from the MME NSN - Updated when HANDOVER COMMAND received in the source eNodeB from the MM

LTE To GSM SRVCC E/// - Updated when MobilityFromEUTRACommand towards the UTRANNSN - NA

Delayed HO time possible in E/// - NSN mapping due to NSN counter's advanced triggering

LTE To GSM SRVCC E/// - Updated when UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered

NSN - Updated when UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered

E/// - The HANDOVER COMMAND message is received from the MME (S1 handover) and the eNodeB initiated the handover due to load balancing action.

No Match

No Match

No Match

No Match

No Match

No Match

Intra eNB E/// - Internal eNodeB trigger (corresponding to HANDOVER REQUEST ACKNOWLEDGE) received when target cell informs source cell that UE resources has been reserved (intra eNodeB handover) and the source cell initiated the handover due to load balancing..NSN - NAInter eNB via X2E/// - HANDOVER REQUEST ACKNOWLEDGE message is received by the source eNodeB from the target eNodeB (X2 handover) and the source eNB initiated the handover due to load balancingNSN - NAInter eNB via S1E/// - HANDOVER COMMAND message is received by the source eNodeB from the MME (S1 handover) and the source eNB initiated the handover due to load balancingNSN - NAIntra eNB E/// - Internal eNodeB trigger (corresponding to HANDOVER REQUEST ACKNOWLEDGE) received when target cell informs source cell that UE resources has been reserved (intra eNodeB handover) and the source cell initiated the handover due to MBMS Interest..NSN - NAInter eNB via X2E///- HANDOVER REQUEST ACKNOWLEDGE message is received by the source eNodeB from the target eNodeB (X2 handover) and the source eNB initiated the handoverdue to MBMS Interest.NSN - NAInter eNB via S1E///- HANDOVER COMMAND message is received by the source eNodeB from the MME (S1 handover) and the source eNB initiated the handover due to MBMS InterestNSN - NAE/// - The eNodeB performs a load balancing action

E/// - The source cell performs a load balancing action.

E/// - The UE sends an RRC MBMS INTEREST INDICATION with an interested frequency that differs from the cell's frequency.

LB To WCDMA E/// - The UE CONTEXT RELEASE COMMAND message is received from the MME with the cause Handover Triggered (S1 handover) and the eNodeB initiated the handover due to load balancing action.

NSN -

100% Match

No Match

No Match

Intra eNB E///- Internal eNodeB trigger (corresponding to UE CONTEXT RELEASE) received when the UE has changed cell during a intra eNodeB handover and the source cell initiated the handover due to load balancing.

NSN - This counter is updated following the reception of an eNB-internal message in case that this message is received for a successful load balancing intra-eNB Handover.Inter eNB via X2E///-UE CONTEXT RELEASE received in the source eNodeB from the target eNodeB (X2 handover) and the source eNB initiated the handover due to load balancing.NSN - This counter is updated following the reception of an X2AP: UE CONTEXT RELEASE message from the target eNB in case that this message is received for a successful load balancing inter-eNB HandoverInter eNB via S1UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered (S1 handover) and the source eNB initiated the handover due to load balancing.NSN - This counter is updated following the reception of an S1AP: UE CONTEXT RELEASE COMMAND message from the MME with cause value Radio Network Layer (Successful Handover) in case that this message is received for a successful load balancing inter-eNB Handover

Intra eNB E///- Internal eNodeB trigger (corresponding to UE CONTEXT RELEASE) received when the UE has changed cell during a intra eNodeB handover and the source cell initiated the handover due MBMS Interest.NSN - NAInter eNB via X2E///- UE CONTEXT RELEASE received in the source eNodeB from the target eNodeB (X2 handover) and the source eNB initiated the handover due MBMS InterestNSN - NAInter eNB via S1E/// - UE CONTEXT RELEASE COMMAND received in the source eNodeB from the MME with the cause Handover Triggered (S1 handover) and the source eNB initiated the handover due MBMS InterestNSN - NA

LB To WCDMA E/// - The MobilityFromEUTRACommand message is sent to the UE and the eNodeB initiated the handover due to load balancing action.

NSN - NA

100 % Match

No Match

Closest Match

Closest Match

No Match

Closest Match

Closest Match

Closest Match

E/// - RRC CONNECTION RECONFIGURATION including the mobilityControlInformation is sent to the UE from the source cell and the reason for the handover is load balancing

NSN- This counter is updated following the transmission of an RRC Connection Reconfiguration message (sent by the eNB to the UE) which indicates a Handover Command to the UE in case this message is sent because of a load balancing handover.E/// - RRC CONNECTION RECONFIGURATION including the mobilityControlInformation is sent to the UE from the source cell and the reason for the handover is MBMS Interest.

NSN- NA

E/// - Updated when reception of RRC message RRC Connection Setup Complete at eNB end.

NSN - Updated when reception of RRC message RRC Connection Setup Complete at eNB end.

E/// - Updated when reception of RRC message RRC Connection Request at eNB .

NSN - Updated when reception of RRC message RRC Connection Request at eNB .

E/// - Stepped at reception of RRC message RRC Connection Request while an RRC Connection Setup is already ongoing for that S-TMSI.

NSN- NAE/// - When setting up the E-RAB the ‘RRC CONNECTION SETUP COMPLETE’message contains a piggybacked NAS ‘Attach Request’ message. The RBS willsend this message to the MME in the S1AP ‘INITIAL UE MESSAGE’ andincrement the ‘pmS1SigConnEstabAtt’ counter

NSN- This counter is updated following the reception of an S1AP: DOWNLINK NAS TRANSPORT message sent by the MME to the eNB.E/// - Stepped at transmission of Initial UE message.

NSN- Transmission of the S1AP message INITIAL UE MESSAGE containing the first NAS signaling message to the MME.E/// - Stepped for each initial E-RAB that is successfully established.

NSN- The transmission of an S1AP:Initial Context Setup Response message sent by the eNB to MME for the successful Initial Context Setup completion.

Closest Match

No Match

No Match

Closest Match

Closest Match

No Match

No Match

No Match

No Match

No Match

No Match

E/// - Stepped for each E-RAB received in the S1 message Initial Context Setup Request.

NSN- The reception of an S1AP:Initial Context Setup Request message sent by the MME to eNB

E/// - Stepped at reception of RRC message RRC Connection Setup Complete if the corresponding RRC Connection Request had Establishment cause Mobile Originating Data.NSN - NAE/// - Stepped at reception of RRC message RRC Connection Setup Complete if the corresponding RRC Connection Request had Establishment cause Mobile Terminating Access.NSN - NAE/// - Stepped at reception of RRC message RRC Connection Request with Establishment cause Mobile Originating Data.

NSN - Stepped at reception of RRC message RRC Connection Request with Establishment cause Mobile Originating Data.

E/// - Stepped at reception of RRC message RRC Connection Request with Establishment cause Mobile Terminating Access.NSN - Stepped at reception of RRC message RRC Connection Request with Establishment cause Mobile Terminating Access

Stepped at reception of RRC message RRC Connection Setup Complete if the corresponding RRC Connection Request had Establishment cause Mobile Originating Data AND while an RRC Connection Setup is already ongoing for that S-TMSI.

Stepped at reception of RRC message RRC Connection Setup Complete if the corresponding RRC Connection Request had Establishment cause Mobile Terminating Access AND while an RRC Connection Setup is already ongoing for that S-TMSI.

Stepped at the first occurrence of reception of any message on this S1 logical connection, if the RRC Connection Request Establishment cause was Establishment cause Mobile Originating Data.Stepped at the first occurrence of reception of any message on this S1 logical connection, if the RRC Connection Request Establishment cause was Establishment cause Mobile Terminating Access.

Stepped at transmission of Initial UE message with RRC Connection Request Establishment cause Mobile Originating Data.

Stepped at transmission of Initial UE message with RRC Connection Request Establishment cause Mobile Terminating Access.

100 % Mapping

100 % Mapping

100 % Mapping

Closest Match

No Match

No Match

No Match

No Match

E /// - Shall be stepped for each successful E-RAB Establishment attempt per QCI at transmission of S1-AP message Initial Context Setup Response.

NSN - The transmission of an S1AP:Initial Context Setup Response message sent by the eNB to MME

E/// - Shall be stepped for each E-RAB Establishment attempt per QCI at reception of S1-AP message Initial Context Setup Request.NSN - Receipt of a S1AP:Initial Context Setup Request sent by MME to the eNB for each QCI1 bearer contained in the "E-RAB to Be Setup List" IE.

E/// -Stepped at reception of RRC message RRC Connection Setup Complete if the corresponding RRC Connection Request had Establishment cause Emergency

NSN -Reception of the RRC: RRCConnectionSetupComplete message (eNB <- UE) in case that this message was received from the UE after the reception of the RRC: RRCConnectionRequest message (eNB <-UE) with EstablishmentCause set to emergencyE/// - Stepped at reception of RRC message RRC Connection Request with establishment cause emergency.NSN - Reception of the RRC: RRCConnectionRequest message (eNB <- UE) in case that this message contains the EstablishmentCause set to emergency

Stepped at reception of RRC message RRC Connection Setup Complete if the corresponding RRC Connection Request had Establishment cause Emergency AND while an RRC Connection Setup is already ongoing for that S-TMSI.

Stepped at the first occurrence of reception of any message on this S1 logical connection, if the RRC Connection Request Establishment cause was Establishment cause Emergency.

Stepped at transmission of Initial UE message with RRC Connection Request Establishment cause Emergency.


No Match

No Match

No Match

Closest Match

Closest Match

Stepped at reception of Initial Context Setup Request for each E-RAB that has the given ARP Priority Level.

Stepped for each MBMS session when eNB sends M3 message: MBMS SESSION RESPONSE back to MME.

Stepped for each MBMS session in the M3 message: MBMS SESSION START REQUEST.

E/// - Stepped for each added bearer that is successfully established.

NSN - The transmission of an S1AP:S1AP:E-RAB SETUP RESPONSE message sent by the eNB to MME.

E/// - Stepped for each bearer received in the S1 message E-RAB Setup Request.NSN - The receipt of an S1AP:E-RAB SETUP REQUEST message sent by MME to the eNB

E/// - Shall be stepped for each successful E-RAB Establishment attempt per QCI at transmission of S1-AP message E-RAB Setup Response.

NSN - Transmission of a S1AP:INITIAL CONTEXT SETUP RESPONSE message sent by eNB to the MME. The counter is updated with the number of QCI 1 / QCI 2 / QCI 3 / QCI 4 bearers contained in the "E-RAB Setup List" IE

Closest Match . Counters for Additional E-RAB Setup Completions not available for Non-GBR QCI's

E/// -Shall be stepped for each E-RAB Establishment attempt per QCI at reception of S1-AP message E-RAB Setup Request.

NSN - Receipt of a S1AP:E-RAB SETUP REQUEST message sent by MME to the eNB. The counter is updated with the number of QCI 1 / QCI 2 / QCI 3 / QCI 4 bearers contained in the "E-RAB to Be Setup List" IE

Closest Match . Counters for Additional E-RAB Setup Attempts not available for Non-GBR QCI's

No Match

No Match

No Match


Stepped at reception of E-RAB Setup Request for each E-RAB that has the given ARP Priority Level.

E/// - This counter is based on an internal level counter maintaining the current number of UEs in RRC_CONNECTED mode. Values are read periodically and accumulated.NSN - This Counter is updated after each sampling interval with the sample taken from the number of UE's in RRC_Connected state


E/// - The counter is increased at every occasion when the corresponding sum counter has accumulated a new sample.NSN - This counter is updated by value 1 when the number of RRC connected UE's is summed to counter SUM_RRC_CONN_UE


E/// - This counter is based on an internal level counter maintained by eNB. The internal level counter maintains the current number of UEs in RRC_CONNECTED mode. pmRrcConnMax is updated at end of ROP with the max value during the ROP period. NSN - This counter is updated after each sampling interval with the peak number of UEs in RRC_CONNECTED state during the measurement period.E/// - Measurement for UEs aggregated to cell level. Only PDCP SDUs that enters an empty buffer are measured. Samples during handover are excluded since they can distort the interpretation of the result (due to packet forwarding, the target cell might have to buffer data before it is possible to schedule the UE in the target cell, hence it would be an increased Latency measurement if it would be included. It would however not lead to a degraded performance for the end-user, due to packet forwarding).

NSN - NA

No Match

Closest Match

No Match

No Match

Closest Match

No Match

E///- Measurement for UEs aggregated to cell level. Only PDCP SDUs that enters an empty buffer are measured. Samples during handover are excluded since they can distort the interpretation of the result (due to packet forwarding, the target cell might have to buffer data before it is possible to schedule the UE in the target cell, hence it would be an increased Latency measurement if it would be included. It would however not lead to a degraded performance for the end-user, due to packet forwarding).

NSN - NA

E/// - Continuous measurement for DRBs aggregated to cell level. ( Unit : Kilobits / 1000 Bits )

NSN - This counter is updated when a PDCP SDU is transmitted towards the UE

E/// - Continuous measurement for UEs aggregated to cell level. ( Unit : Kilobits / 1000 Bits )

E/// - Continuous measurement for UEs aggregated to cell level. ( ms )

NSN -

E/// - Each TTI, the counter shall be incremented when there was a need to schedule DRB data in the downlink.NSN - This counter is incremented with every TTI ,in which at least one UE is scheduld to receive user plane data.

E/// - The bin accumulates the DL transmission time per QCI for each large data burst that needs to be transmitted across multiple TTIs.

No Match

Match

Match

E///- If there was data in the buffer at the time of release, then stepped at reception of S1 message E-RAB Release Command or UE Context Release Command when internal cause codes considered abnormal (Radio Connection with UE is lost; Handover failure for the UE; Non admitted E-RABs by target cell at successful handover for the UE; UE pre-emption) when the RBS initiated the release. It can also be stepped at transmission of E-RAB Release Indication, UE Context Release Request or Reset message by the RBS, or when a cell owned by that RBS is disabled (and that leads to internal RBS UE Context Release). In the UL case when a UE has multiple bearers co-existing and sharing the same LCG, the bearers share a single packet queue. If one of the bearers is released and there is data in the queue, the bearer's associated counter is incremented, regardless of whether or not the data belongs to the released bearer.



Closest Match

E/// - Stepped at reception of S1 message E-RAB Release Command or UE Context Release with none of the causes Normal Release, Handover Successful, User Inactivity, Detach, CS Fallback Triggered, Inter-RAT Redirection, UE Not available for PS Service or Redirection towards 1xRTT and there was data in either the UL or DL buffer (i.e. active). The release must also have been MME initiated. In the UL case when a UE has multiple bearers co-existing and sharing the same LCG, the bearers share a single packet queue. If one of the bearers is released and there is data in the queue, the bearer's associated counter is incremented, regardless of whether or not the data belongs to the released bearer.

E/// - Number of session seconds aggregated for all UEs in a cell. A UE is said to be ´in session´ if any data on a DRB (UL or DL) has been transferred during the last 100 ms

NSN - This measurement provides the aggregated in-session activity time in seconds for all E-RABs with QCI1 / QCI2/QCI3/QCI4/Non-GBR QCI characteristics. The E-RAB is said to be "in session" if any user data has been transferred in UL or DL direction within the last 100msec

The bin accumulates session seconds aggregated for DRBs with a certain QCI. The DRBs for a UE is said to be "in session" if any data on any DRB (UL or DL) has been transferred during the last 100 ms for that QCI.

Match

E/// - The bin is steped for each released active E-RAB that maps to a certain QCI when the release is triggered by an E-RAB Release Indication, UE Context Release Request or Reset message and has a internal abnormal cause code, except active E-RABs released due to a successful HO. In the UL case when a UE has multiple bearers co-existing and sharing the same LCG, the bearers share a single packet queue. If one of the bearers is released and there is data in the queue, the bearer's associated counter is incremented, regardless of whether or not the data belongs to the released bearer.



Closest Match

The bin corresponding to the QCI of the E-RAB is stepped at reception of S1 message E-RAB Release Command or UE Context Release with none of the causes Normal Release, Handover Successful, User Inactivity, Detach, CS Fallback Triggered, Inter-RAT Redirection, UE Not available for PS Service or Redirection towards 1xRTT and there was data in either the UL or DL buffer (i.e. active). The release must also have been MME initiated. In the UL case when a UE has multiple bearers co-existing and sharing the same LCG, the bearers share a single packet queue. If one of the bearers is released and there is data in the queue, the bearer's associated counter is incremented, regardless of whether or not the data belongs to the released bearer.

> NSN Counter will be triggered only with release Cause ( RNL Radio Connection with UE lost ) & for Pre-Empted Bearers

> Closest Match

E/// - Stepped at reception of S1 message E-RAB Release Command or UE Context Release Command where the cause value indicates system (abnormal) release with the pre-condition that the Initial Context Establishment procedure must first have been successfully completed. The release must also have been eNB initiated.

NSN - The transmission of an S1AP:E-RAB RELEASE INDICATION or an S1AP: UE Context Release Request from the eNB to the MME

> NSN eNB initiated Abnormal E-RAB releases having the cause split up of RNL / TNL / OTH reasons.

> Match

E/// - Stepped at reception of S1 message E-RAB Release Command or UE Context Release Command where the cause value indicates normal release with the pre-condition that the Initial Context Establishment procedure must first have been successfully completed. The release must also have been eNB initiated.

NSN - The transmission of an S1AP:E-RAB RELEASE INDICATION or an S1AP: UE Context Release Request from the eNB to MME.

Match

E/// - The counter is stepped for each released E-RAB at reception of S1 message E-RAB Release Command or UE Context Release Command (except if the cause was successful handover) and with the pre-condition that the Initial Context Establishment procedure must first have been successfully completed. The release must also have been MME initiated.

NSN - Reception of an S1AP:E-RAB RELEASE COMMAND or an S1AP:UE CONTEXT RELEASE COMMAND message sent by MME to the eNB. The counter is not incremented in case that the S1AP:UE CONTEXT RELEASE COMMAND is received as a response to a previously sent S1AP:UE CONTEXT RELEASE REQUEST

Counter_NSN Description

M8020C4:SAMPLES_CELL_PLAN_UNAVAIL

The number of samples when the cell is planned unavailable . The counter is updated with value 1 approximately every 10 seconds when cell Administrative State is locked.

INTRA_ENB_HO_PREP ( M8009C2 ) + INTER_ENB_HO_PREP ( M8014C0 ) +INTER_ENB_S1_HO_PREP (M8014C14 )

Intra eNBAn internal eNB trigger. The eNB MM receives a list with the target cells from RRM and decides on an Intra-eNB Handover. Updated to the source cell.Inter eNB via X2The number of Inter-eNB X2-based Handover preparations. The Mobility management (MM) receives a list with target cells from the RRM and decides to start an Inter-eNB X2-based Handover.Inter eNB via S1This counter is updated following the transmission of an S1AP: HANDOVER REQUIRED message from the source eNB to the MME if this message prepares an Inter eNB Handover.

ATT_INTRA_ENB_HO ( M8009C6 ) +ATT_INTER_ENB_HO ( M8014C6 ) +INTER_ENB_S1_HO_ATT (M8014C18)

Intra eNBThe transmission of a RRC Connection Reconfiguration message sent by the eNB to UE, which indicates a Handover Command to the UE. Updated to the source cell.Inter eNB via X2The reception of an X2AP: Handover Request Acknowledge message from the target eNB.Inter eNB via S1This counter is updated following the reception of an S1AP: HANDOVER COMMAND message from the MME to the source eNB in case that this message is received in response to the preparation of an Inter eNB Handover.


SUCC_INTRA_ENB_HO ( M8009C7) +SUCC_INTER_ENB_HO ( M8014C7 ) +INTER_ENB_S1_HO_SUCC (M8014C19)

Intra eNBThe reception of an internal UE Context Release Request for the handover on the source side. Updated to the source cell.Inter eNB via X2The reception of a X2AP: Release Resource message sent by the target eNB.Inter eNB via S1This counter is updated following the reception of an S1AP: UE CONTEXT RELEASE COMMAND message from the MME to the source eNB with the cause value Radio Network Layer (Successful Handover) in case that this message is received for an Inter eNB Handover.



HO_INTFREQ_ATT ( M8021C0 )

Intra eNBThis counter is updated following the transmission of an RRC Connection Reconfiguration message sent by the eNB to the UE, which indicates a Handover Command to the UE in case that this message is sent in response to the preparation of an inter-frequency Intra eNB Handover. Inter eNB via X2This counter is updated following the receipt of an X2AP: HANDOVER REQUEST ACKNOWLEDGE message from the target eNB in case that this message is received in response to the preparation of an inter-frequency Inter eNB Handover. Inter eNB via S1This counter is updated following the receipt of an S1AP: HANDOVER COMMAND message from the MME in case that this message is received in response to the preparation of an inter-frequency Inter eNB Handover.

HO_INTFREQ_SUCC ( M8021C2 )

Intra eNBThe reception of an internal UE Context Release Request for the handover on the source side. Updated to the source cell.Inter eNB via X2This counter is updated following the receipt of an X2AP: UE CONTEXT RELEASE message from the target eNB for an inter-frequency Inter eNB HandoverInter eNB via S1This counter is updated following the receipt of an S1AP: UE CONTEXT RELEASE COMMAND message from the MME with the cause value Radio Network Layer (Successful Handover) in case that this message is received for an inter-frequency Inter eNB Handover.

ISYS_HO_PREP ( M8016C14 )

HO to WCDMA :Transmission of a S1AP: HANDOVER REQUIRED message to source MME for an Inter System Handover. This counter is updated for the source cell of the handover.

ISYS_HO_ATT ( M8016C21 )

HO to WCDMA :Updated when a S1AP: HANDOVER COMMAND message is received from MME for an Inter System Handover. This counter is updated for the source cell of the handover

ISYS_HO_SUCC ( M8016C23 )


Updated when a S1AP: UE CONTEXT RELEASE COMMAND message is received from MME with Cause value "Radio Network Layer" (Successful Handover) for an Inter System Handover. This counter is updated for the source cell of the handover.

Preparation phase counters not available .

ISYS_HO_GERAN_SRVCC_ATT ( M8016C33 )

LTE To GSM SRVCC :Reception of a S1AP: HANDOVER COMMAND message (source eNB <- MME; 3GPP TS 36.413) in case this message is received in response to the preparation of an Inter System Handover to GERAN with SRVCC (Single Radio Voice Call Continuity, 3GPP TS 23.216).

Can Use all preparation phase Successes to Execution attempts . ISYS_HO_GERAN_SRVCC_ATT ( M8016C33 )

ISYS_HO_GERAN_SRVCC_SUCC ( M8016C34 )

Reception of a S1AP: UE CONTEXT RELEASE COMMAND message (source eNB <- MME; 3GPP TS 36.413) with Cause value "Radio Network Layer (Successful Handover)" in case this message is received for an Inter System Handover to GERAN with SRVCC (Single Radio Voice Call Continuity, 3GPP TS 23.216).

HO_LB_SUCC

This measurement provides the number of successful load balancing Handover completions. It comprises the intra- and inter-eNB Handover scenario. Load balancing handovers are used to shift cell traffic from a high loaded serving cell to neighbor cells.

HO_LB_ATT

M8013C5:SIGN_CONN_ESTAB_COMP

S1AP_NAS_DOWNLINK ( M8000C30 )

UE_LOG_S1_SETUP ( M8000C12 )

INI_CONT_STP_COMP ( M8000C1 )

This measurement provides the number of load balancing Handover attempts. It comprises the intra- and inter-eNB Handover scenario. Load balancing handovers are used to shift cell traffic from a high loaded serving cell to neighbor cells.

Stepped at reception of RRC message RRC Connection Setup Complete at eNB end.The reception of the first message from MME which succeeds the S1AP:INITIAL UE message on a UE-associated logical S1-connection

M8013C17:SIGN_CONN_ESTAB_ATT_MO_S +M8013C18:SIGN_CONN_ESTAB_ATT_MT +M8013C19:SIGN_CONN_ESTAB_ATT_MO_D +M8013C20:SIGN_CONN_ESTAB_ATT_OTHERS +M8013C21:SIGN_CONN_ESTAB_ATT_EMG

Signaling Connection Establishment attempts due to MO-Signaling / MO-Data / MT - Access / Others / Emergency Calls .

The receipt of an RRC Connection Request message sent by the UE to eNB. Note: If a UE (erroneously) sends this message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.No Separate Counters for RRC

Connection re-attempt . If a UE (erroneously) sends RRC Connection message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.

The number of Downlink NAS Transport messages received by the eNB.

The establishment of UE-associated logical S1-connection is initiated by the reception of the first NAS signaling message within the RRC Connection Establishment.

The number of successful Initial Context Setup completions.

INI_CONT_STP_REQ ( M8000C0 ) The number of Initial Context Setup Requests

No Separate Counters for RRC Connection establishment due to MO-DATA

No Separate Counters for RRC Connection establishment due to MT-ACCESS

SIGN_CONN_ESTAB_ATT_MO_D ( M8013C19)

The number of Signaling Connection Establishment attempts for mobile originated data connections. From UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED is started.

SIGN_CONN_ESTAB_ATT_MT ( M8013C18 )

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.No Separate Counters for RRC

Connection re-attempt . If a UE (erroneously) sends RRC Connection message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.No Separate Counters for RRC Connection re-attempt . If a UE (erroneously) sends RRC Connection message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.No Separate Counters for S1 signalling connection establishments with Establishment cause Mobile Originating Data.No Separate Counters for S1 signalling connection establishments with Establishment cause Mobile Terminating Access.

No Separate Counters for S1 signalling connection attempts with Establishment cause Mobile Originating Data.

No Separate Counters for S1 signalling connection attempts with Establishment cause Mobile terminating Access.

SIGN_CONN_ESTAB_COMP_EMG


EPS_BEARER_STP_COM_INI_QCI1 ( M8006C35 )+ EPS_BEARER_STP_COM_INI_QCI_2 ( M8006C168 )+ EPS_BEARER_STP_COM_INI_QCI_3 ( M8006C169 ) + EPS_BEARER_STP_COM_INI_QCI_4 ( M8006C170 )+ EPS_BEAR_STP_COM_INI_NON_GBR ( M8006C36 )

The number of initial EPS bearer setup completions per QCI. Each bearer of the E-RAB Setup List IE is counted.

EPS_BEARER_STP_ATT_INI_QCI1 ( M8006C17) + EPS_BEARER_STP_ATT_INI_QCI_2 ( M8006C162 ) + EPS_BEARER_STP_ATT_INI_QCI_3 ( M8006C163 ) + EPS_BEARER_STP_ATT_INI_QCI_4 ( M8006C164 )+ EPS_BEAR_STP_ATT_INI_NON_GBR ( M8006C18 )

The number of initial EPS bearer setup attempts per QCI1. Each bearer of the E-RAB to Be Setup List IE is counted

The number of Signalling Connection Establishment completions for emergency calls

SIGN_CONN_ESTAB_ATT_EMG ( M8013C21 )

Number of Signaling Connection Establishment attempts for emergency calls

No Separate Counters for RRC Connection re-attempt . If a UE (erroneously) sends RRC Connection message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.No Separate Counters for S1 signalling connection establishments with Establishment cause Emergency Calls

No Separate Counters for S1 signalling connection attempts with Establishment cause Emergency Calls




EPS_BEARER_SETUP_COMPLETIONS (M8006C1) - [ EPS_BEARER_STP_COM_INI_QCI1 ( M8006C35 )+ EPS_BEARER_STP_COM_INI_QCI_2 ( M8006C168 )+ EPS_BEARER_STP_COM_INI_QCI_3 ( M8006C169 ) + EPS_BEARER_STP_COM_INI_QCI_4 ( M8006C170 )+ EPS_BEAR_STP_COM_INI_NON_GBR ( M8006C36 ) ]

The number of EPS bearer setup completions. Each bearer of the "E-RAB Setup List" IE is counted. ( All intial context setup counters are subtracted from Parent )

EPS_BEARER_SETUP_ATTEMPTS ( M8006C0) - [ EPS_BEARER_STP_ATT_INI_QCI1 ( M8006C17) + EPS_BEARER_STP_ATT_INI_QCI_2 ( M8006C162 ) + EPS_BEARER_STP_ATT_INI_QCI_3 ( M8006C163 ) + EPS_BEARER_STP_ATT_INI_QCI_4 ( M8006C164 )+ EPS_BEAR_STP_ATT_INI_NON_GBR ( M8006C18 ) ]

The number of EPS bearer setup attempts. Each bearer of the "E-RAB to Be Setup List" IE is counted.

EPS_BEAR_SET_COM_ADDIT_QCI1 ( M8006C44 ) ;EPS_BEARER_STP_COM_ADD_QCI_2 ( M8006C171 ) ;EPS_BEARER_STP_COM_ADD_QCI_3 ( M8006C172 );EPS_BEARER_STP_COM_ADD_QCI_4 ( M8006C173 )

This measurement provides the number of additional EPS bearer setup completions for GBR DRBs of QCI 1 / QCI 2 / QCI 3 / QCI 4 characteristics

EPS_BEAR_SET_ATT_ADD_QCI_1 ( M8006C26) ;EPS_BEARER_STP_ATT_ADD_QCI_2 ( M8006C165 ) ;EPS_BEARER_STP_ATT_ADD_QCI_3 ( M8006C166 );EPS_BEARER_STP_ATT_ADD_QCI_4 ( M8006C167 )

This measurement provides the number of additional EPS bearer setup attempts for GBR DRBs of QCI 1 / QCI 2 / QCI 3 / QCI 4 characteristics



DENOM_RRC_CONN_UE ( M8001C319 )

RRC Connected UEs Max ( M8001C200)


SUM_RRC_CONN_UE ( M8001C318 )

This Measurement provides the sum of sampled values for measuring the number of simultaneously RRC connected UE's .This counter divided by the denominator DENOM_RRC_CONN_UE provides the average number of RRC connected Ues per cell .

The number of sample taken for counter SUM_RRC_CONN_UE used as a denominator for average calculation

The highest value for number of UEs in RRC_CONNECTED state over the measurement period.


PDCP_SDU_VOL_DL ( M8012C20 )



ACTIVE_TTI_DL ( M8012C90 )


The measurement gives indication of the eUu interface traffic load by reporting the sum of transmitted PDCP SDU's related traffic volumes.

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


Active ERAB Rel QCI1 + Active ERAB Rel QCI2 + Active ERAB Rel QCI3 + Active ERAB Rel QCI4 + Active ERAB Rel non GBR ( M8006C176 +M8006C177+ M8006C178+M8006C179+M8006C180 )


ERAB Active Time QCI1 + ERAB Active Time QCI2 + ERAB Active Time QCI3 + ERAB Active Time QCI4 + ERAB Active Time nonGBR ( M8006C181+M8006C182+M8006C183+M8006C184+M8006C185 )


ERAB Active Time QCI1 / ERAB Active Time QCI2 / ERAB Active Time QCI3 / ERAB Active Time QCI4 / ERAB Active Time nonGBR ( M8006C181/M8006C182/M8006C183/M8006C184/M8006C185 )



Active ERAB Rel QCI1 / Active ERAB Rel QCI2 / Active ERAB Rel QCI3 / Active ERAB Rel QCI4 / Active ERAB Rel non GBR ( M8006C176/M8006C177/M8006C178/M8006C179/M8006C180 )


M8006C12:ENB_EPS_BEARER_REL_REQ_RNL +M8006C13:ENB_EPS_BEARER_REL_REQ_OTH +M8006C14:ENB_EPS_BEARER_REL_REQ_TNL

The number of E-RABs requested to be released in case a Radio Link Failure / Other causes / Transport Layer Cause is detected by eNB.

M8006C10:ENB_EPS_BEARER_REL_REQ_NORM+M8006C15:ENB_EPSBEAR_REL_REQ_RNL_REDIR

The number of eNB-initiated EPS Bearer Release requests due to the UE inactivity. In case of the UE context release request, all the established EPS Bearers are counted.

The number of eNB-initiated EPS Bearer Release requests due Redirect (release due to RNL E-UTRAN generated reason or RNL Inter-RAT Redirection)

M8006C6:EPC_EPS_BEARER_REL_REQ_NORM +M8006C7:EPC_EPS_BEARER_REL_REQ_DETACH

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.

Partial Cell Availability ( node Restart excluded )

Majority of the data is fundamentally measured on the cell level and with a 15-minute ROP granularity.

Cell Availability ( % ) = 100*( ( N * L * 900 ) - ∑( pmCellDownTimeAuto + pmCellDownTimeMan ) / ( N * L * 900 )

Where L = Number of Cells ; N = Reporting Period ( For Ex: 1 hour will contain 4 ROP's ( 15 min) )

( N * L * 900 ) )

HO_INTFREQ_ATT

HO_INTFREQ_SUCC

HO_INTFREQ_ATT

HO_INTFREQ_SUCC

HO_INTFREQ_ATT

HO_INTFREQ_ATT

HO_INTFREQ_ATT

ISYS_HO_PREP

ISYS_HO_ATT

ISYS_HO_SUCC

ISYS_HO_GERAN_SRVCC_ATT

ISYS_HO_GERAN_SRVCC_SUCC

Measurement Report

pmHOPrepAtt

pmHOPrepSucc

pmHOExeAtt

pmHOExeSucc

EPC_EPS_BEARER_REL_REQ_NORM +EPC_EPS_BEARER_REL_REQ_DETACH

ENB_EPS_BEARER_REL_REQ_RNL +ENB_EPS_BEARER_REL_REQ_OTH +ENB_EPS_BEARER_REL_REQ_TNL

ENB_EPS_BEARER_REL_REQ_NORM+ENB_EPSBEAR_REL_REQ_RNL_REDIR

Active ERAB Rel QCI1 + Active ERAB Rel QCI2 + Active ERAB Rel QCI3 + Active ERAB Rel QCI4 + Active ERAB Rel non GBR

Documents

Lte Ericsson- Nsn Kpi Mapping_v2.0