KPI Description

NAME
_PS_Data_Call_Success_Rate
_RRC_setup_SR_ATT
_Initial_ERAB_Setup_SR_ATT
_S1_sig_estab_succ_rate_ATT
_ERAB_System_RET02
_PCT_IRAT_Redir_Excl_CSFB
_HO_Succ_Rate_ATT
_RRC_drop
VS_RRC_cnx_req
_INTRA_HO_FR
_E_Intra_eNB_HO_Success_Rate
DESCRIPTION
This indicator is designed to monitor the end-user service availability meaning that the service data (N
eUTRAN perspective. We consider that this service is ensured when the E-RAB needed to transport da
established successfully. 4 different steps are needed in order to achieve this: - RRC connection establ
connection establishment - UE Initial Context allocation - Dedicated E-RAB establishment.
RRC_setup_SR_ATT
This indicator provides the success rate of S1 dedicated connection establishment procedure. This con
used for dialog between the eNodeB and the MME as well as for NAS transport between the UE and th
This indicator provides the rate of system non-GBR E-RABs that are dropped (associated to dropped ca
not taken into account. The normal release counter is not incremented on source cell in case of hando
release counter is not incremented in case of drop on mobility failure (so HO failure +RRC reestab failu
will not reflect the real activity and at network level (from user point of view), it will not include the m
is to have a rate always coherent. So depending on handover activity, the rate is more or less correct.
PCT_IRAT_Redir_Excl_CSFB
HO_Succ_Rate_ATT
This indicator provides the number for RRC connection requests received from UE in the cell. TRIGGER
triggered on reception of RrcConnectionRequest message.
The intra-eNB handover success rate is the percentage of the successfully performed intra-eNB hando
FORMULA
VS_RRC_cnx_succ_rate*VS_S1AP_cnx_estab_succ_rate*VS_ERABs_NonG
RRC_ConnEstabSucc_Sum/
(RRC_ConnEstabAtt_EmergencyCallAttempts+RRC_ConnEstabAtt_HighPriorityAccessAttempts+RRC
ConnEstabAtt_MobileOriginatedSignalling+RRC_ConnEstabAtt_MobileOriginatedUserB
((SAEB_EstabInitSuccNbr_QCI2+SAEB_EstabInitSuccNbr_QCI3+SAEB_EstabInitSuccNbr_QCI4+SAE
Nbr_QCI7+SAEB_EstabInitSuccNbr_QCI8+SAEB_EstabInitSuccNbr_QCI9)+
(SAEB_EstabAddSuccNbr_QCI2+SAEB_EstabAddSuccNbr_QCI3+SAEB_EstabAddSuccNbr_QCI4+SA
ccNbr_QCI7+SAEB_EstabAddSuccNbr_QCI8+SAEB_EstabAddSuccNbr_QCI9))/
((SAEB_EstabInitAttNbr_QCI2+SAEB_EstabInitAttNbr_QCI3+SAEB_EstabInitAttNbr_QCI4+SAEB_Est
+SAEB_EstabInitAttNbr_QCI8+SAEB_EstabInitAttNbr_QCI9)+
(SAEB_EstabAddAttNbr_QCI2+SAEB_EstabAddAttNbr_QCI3+SAEB_EstabAddAttNbr_QCI4+SAEB_E
I7+SAEB_EstabAddAttNbr_QCI8+SAEB_EstabAddAttNbr_QCI9))
((VS_UE_NAS_first_DL+VS_UE_ctxt_setup_req_WithoutDLNAS)/S1SI
1-(VS_ERABs_NonGBR_rel_abnormal)/(VS_ERABs_NonGBR_rel_abnormal+VS_E
(VS_redirect_all_UtraFdd+VS_redirect_all_GERAN-VS_redirect_UtraFdd_
(VS_UE_ctxt_setup_succ_WithoutDLNAS+VS_UE_ctxt_setup_succ
(HO_IntraEnbOutSucc_Sum+VS_HO_IrC_X2_succ_src+VS_HO_IrC
(VS_HO_IrC_eNB_req_src+VS_HO_IrC_X2_req_src+VS_HO_IrC_
(VS_RRC_connected_RLF_UL_L1SyncLost+VS_RRC_connected_RLF_MaxRetrans
(VS_HO_IrC_eNB_fail_prep_CAC_tgt+VS_HO_IrC_eNB_fail_exec_integrity_tgt_OD+VS_HO_IrC_eNB_fa
ail_exec_ReestabOnOther_tgt_OD+VS_HO_IaF_IrC_eNB_all_fail_exec_ReestabOnSrc_tgt_OD+VS_HO
+VS_HO_IrC_eNB_fail_exec_TimeoutUE_tgt_OD)/VS_HO_IrC_eN
HO_IntraEnbOutSucc_Sum/VS_HO_IrC_eNB_req_src
NAME
_Data_acc_ACC02_wo_reptn
VS_RRC_cnx_WithoutRepetition_fail_rate
VS_RRC_cnx_WithoutRepetition_succ_rate
VS_RRC_cnx_WithoutRepetition_fail
VS_RRC_cnx_WithoutRepetition_req
RRC_ConnEstabFail_InterventionOAM
RRC_ConnEstabFail_S1FaultExternalFailure
RRC_ConnEstabFail_NoResponseFromUE
RRC_ConnEstabFail_TooLateEnbResponse
RRC_ConnEstabFail_OverloadConditionFailure
VS_RRC_connected_RLF_sum
VS_RRC_connected_RLF_MaxRetrans
VS_RRC_connected_RLF_UL_L1SyncLost
RRC_ConnEstabFail_CACFailure
VS_UE_RRC_connected_state_avg_PerCell
VS_UE_RRC_connected_state_min
VS_RRC_cnx_WithoutRepetition_fail_CAC_rate
VS_UE_ctxt_setup_fail_CAC
VS_UE_ctxt_setup_fail_CSFBNotPossible_OD
VS_UE_ctxt_setup_fail_ERABCtxtAllocation_OD
VS_UE_ctxt_setup_fail_InternalFail_OD
VS_UE_ctxt_setup_fail_SecurityActivationFailure_OD
VS_UE_ctxt_setup_fail_SecurityAlgoNotCompatible_OD
VS_UE_ctxt_setup_fail_TimeoutUE_OD
VS_UE_ctxt_setup_fail_integrity_OD
VS_ERABs_all_initial_setup_req
VS_ERABs_all_initial_setup_succ
_S1_sig_estab_succ_rate_ATT
S1SIG_ConnEstabAtt
VS_UE_NAS_first_DL
VS_UE_ctxt_setup_req_AfterDLNAS
VS_UE_ctxt_setup_req_WithoutDLNAS
VS_S1AP_cnx_estab_fail_timeout
VS_UE_ctxt_setup_req
VS_S1AP_cnx_estab_succ
VS_UE_ctxt_rel_by_eNB_S1ResetMME
VS_UE_ctxt_rel_by_eNB_S1ResetOAM
VS_UE_ctxt_rel_by_eNB_S1ResetENB
VS_UE_ctxt_rel_by_eNB_S1FaultExternalFailure
VS_UE_ctxt_rel_by_eNB_NoCtxtRelCmd
VS_UE_ctxt_rel_req_IrRATRedirection
VS_UE_ctxt_rel_req
VS_UE_ctxt_rel_req_RLF
VS_UE_ctxt_rel_req_UserInactivity
VS_UE_ctxt_rel_req_InternalFail
VS_UE_ctxt_rel_req_NoCtxtSetupReq
VS_UE_ctxt_rel_req_SecurityAlgoNotCompatible
VS_UE_ctxt_rel_req_RadioInterfaceFailure
VS_UE_ctxt_rel_req_TimeoutX2RelForX2HO
VS_UE_ctxt_rel_req_TimeoutS1RelForPSHOToUtra
VS_UE_ctxt_rel_req_IrFreqRedirection
VS_UE_ctxt_rel_req_integrity
VS_UE_ctxt_rel_cmd
VS_UE_ctxt_rel_cmd_CtxtRelReq
VS_UE_ctxt_rel_cmd_normal
VS_UE_ctxt_rel_cmd_auth_fail
VS_UE_ctxt_rel_cmd_detach
VS_UE_ctxt_rel_cmd_normal_OnHOsucc
VS_UE_ctxt_rel_by_eNB
VS_ERABs_all_rel_abnormal
_ERAB_Drops_incl_Mobility
_ERAB_Network_RET02
_HO_Success_Rate
_HO_Prep_Success_Rate
_HO_Exec_Success_Rate
VS_HO_IrC_X2_fail_sum_WithoutAbort_src
VS_HO_IaF_IrC_X2_all_fail_exec_ReestabOnSrc_src_OD
VS_HO_IrC_X2_fail_exec_TimeoutX2_src_OD
VS_HO_IrC_X2_fail_prep_HOPrepFailRcvd_src_OD
VS_HO_IrC_X2_fail_prep_TimeoutX2_src_OD
VS_HO_IrC_X2_abort_sum_src
VS_HO_IrC_X2_abort_CSFB_src_OD
VS_HO_IrC_X2_abort_EventA1_src_OD
VS_HO_IrC_X2_abort_S1APResetOrUECtxtRelCmd_src_OD
VS_HO_IrC_X2_abort_VoIPnonAdmission_src_OD
VS_HO_IrC_X2_abort_X2APReset_src_OD
VS_HO_IrC_X2_abort_prep_CascadeHO_src_OD
_Intra_Freq_HO_SR_tgt
VS_HO_IrC_X2_fail_sum_WithoutAbort_tgt
VS_HO_IrC_X2_fail_exec_PathSwitchFail_tgt_OD
VS_HO_IrC_X2_fail_exec_TimeoutS1PathSwitch_tgt_OD
VS_HO_IrC_X2_fail_exec_TimeoutX2orUE_tgt_OD
VS_HO_IrC_X2_fail_exec_integrity_tgt_OD
VS_HO_IrC_X2_abort_sum_tgt
VS_HO_IrC_X2_abort_X2APHOCancel_tgt_OD
VS_HO_IrC_X2_abort_X2APReset_tgt_OD
VS_HO_IrC_eNB_fail_sum_WithoutAbort_tgt
VS_HO_IrC_eNB_fail_InternalFail_tgt_OD
VS_HO_IrC_eNB_fail_exec_TimeoutUE_tgt_OD
VS_HO_IrF_IrC_eNB_all_fail_exec_TimeoutUE_tgt_OD
VS_HO_IrF_IrC_eNB_all_fail_prep_CAC_tgt
VS_cell_thpt_FDD_DL_avg_PerCell
VS_cell_thpt_FDD_DL_max
VS_cell_thpt_FDD_DL_min
_DL_RLC_Enhanced_Tput_kbps
VS_cell_thpt_DL_Hi
VS_cell_thpt_DL_HiLo
VS_cell_thpt_DL_HiMed
VS_cell_thpt_DL_Lo
VS_cell_thpt_DL_LoMed
VS_cell_thpt_DL_Hi_ratio
VS_noise_PRB_all_UL_Lo_OD
VS_noise_PRB_all_UL_LoMed_OD
VS_noise_PRB_all_UL_HiLo_OD
VS_noise_PRB_all_UL_HiMed_OD
VS_noise_PRB_all_UL_Hi_OD
VS_noise_PRB_all_UL_Hi_HiMed_HiLo_OD
VS_noise_PRB_all_UL_Lo_LoMed_OD
VS_noise_PRB_all_UL_Hi_HiMed_HiLo_OD_ratio
VS_noise_PRB_all_UL_Lo_LoMed_OD_ratio
VS_noise_PRB_group01_UL_Hi_OD
VS_noise_PRB_group01_UL_HiMed_OD
_Data_Acc_ACC02_wtrep
_VS_RRC_cnx_SuccRate_wtrep
_VS_RRC_cnx_WithoutRepet_req
_Initial_ERAB_SSR_ATT
_Initial_ERAB_Setup_Suc
_Initi_ERAB_Setup_Req
_VS_S1_cnx_estab_succ_rate
_VS_S1AP_cnx_estab_suc
_VS_S1AP_cnx_est_req
_ERAB_Network_Retainability02_BH
_VS_ERABs_NonGBR_rel_norm
_VS_ERABs_NonGBR_rel_Denom
_Intra_Frq_HO_SR_tgt
_Intra_Freq_tgt_HO_Suc
_VS_HO_IaF_IaLTE_req_tgt
_IRAT_Redirect_ToNonLTE_woCSFB
VS_UE_MIMO_DL_eligible_yes_ratio
_IRAT_Redirect_ToNonLTE_woCSFB
_Inter_Frequency_PS_Data_HHO_Success_Rate_LTE_LTE
VS_HO_IrF_IrC_X2_IaFDDorIaTDD_fail_src
VS_HO_IrF_IrC_X2_IaFDDorIaTDD_fail_src_WithoutAbort
VS_HO_IrF_IrC_X2_IaFDDorIaTDD_abort_sum_src
VS_HO_IrF_IrC_X2_IaFDDorIaTDD_fail_exec_src
VS_HO_IrF_IrC_X2_IaFDDorIaTDD_fail_tgt
VS_HO_IrF_IrC_X2_IaFDDorIaTDD_abort_sum_tgt
VS_HO_IrF_IrC_X2_IaFDDorIaTDD_fail_tgt_WithoutAbort
VS_HO_IrF_IrC_X2_all_fail_exec_integrity_tgt_OD
VS_HO_IrF_IrC_X2_all_fail_exec_TimeoutX2orUE_tgt_OD
_PCT_IRAT_Redirect_nonLTE
_LIMO_Mobility_IRAT_LTE_to_UTRAN_Succ_Rate
_LIMO_Mobility_IRAT_LTE_to_UTRAN_attempts
COUNTER DESCRIPTION
Data_acc_ACC02_wo_reptn
This indicator provides the failure rate of RRC Connection establishment procedure, exclud
This indicator provides the success rate of RRC Connection establishment procedure proce
repetitions.
This indicator provides the number of RRC Connection establishment failure, excluding the
This indicator provides the number for RRC connection requests received from UE in the ce
repetitions. TRIGGER EVENT: The counter is triggered when the first RrcConnectionReques
from UE in the cell. This is detected through InitialUE-Identity IE received in RrcConnection
EstablishmentCause of the concerned screening: - If s-TMSI is present, no UE in the cell con
value stored and same EstablishmentCause value - If randomValue is present, no UE conte
the same value stored and same EstablishmentCause value.
This indicator provides the number of RRC connection procedures that failed for some failu
cell service due to customer OAM intervention barring the cell or a UE is illicitly trying to a
operator use (When a cell is reserved for operator use, only RRC establishment requests u
'highPriorityAccess' are allowed). Based on 3GPP counter: RRC.ConnEstabFail.Intervention
Sending of RrcConnectionReject due to the problem in 'Description'. NOTES: The eNodeB fi
hysteresis timer" (interval T1) and, when it times out, raises an"eNodeB Cells Barred" alar
CNP (L97933 logic). In the worst case the eNodeB takes 40 sec (interval T2) to notify all th
point, that is during the entire interval (T1+T2), "unaware" UEs can still make calls and the
them with proper pegging/screenings. If DSIM is not enabled, the cell barred information c
UEs will continue to attempt to access the barred cell, resulting in pegging of this counter
one or more S1 link is locked and other S1 links experience problems described in Screenin
accesses are disabled and the cell is not barred. Based on 3GPP counter: RRC.ConnEstabFa
TRIGGER EVENT: Sending of RrcConnectionReject due to the problem in 'Description'. NOTE
starts a "cell-barring hysteresis timer" (interval T1) and, when it times out, raises an"eNod
which triggers DSIM/ CNP (L97933 logic). In the worst case the eNodeB takes 40 sec (inter
UEs. So prior to this point, that is during the entire interval (T1+T2), "unaware" UEs can st
eNodeB needs to reject them with proper pegging/screenings. If DSIM is not enabled, the c
cannot be broadcast, and UEs will continue to attempt to access the barred cell, resulting
for each failed attempt. If one or more S1 link is locked and other S1 links experience prob
Screening.
RrcConnectionSetupComplete supervision timer expiration (message not received from th
counter: RRC.ConnEstabFail.NoResponseFromUE TRIGGER EVENT: The counter is triggered
RrcConnectionSetupComplete supervision timer expiration.
Connection Request has been queued too long for it to be worth processing, as the UE is n
answer. Based on 3GPP counter: RRC.ConnEstabFail.TooLateEnbResponse TRIGGER EVENT:
on Discard of an RRC Connection Request.
Failure due to overload condition. Based on 3GPP counter: RRC.ConnEstabFail.OverloadCon

EVENT: Sending of RrcConnectionReject. NOTES: There is currently no cause provided in 3G
message. As far as the KPI for eNodeB reliability/ availability is concerned, Screening 3 is
Screening 2 may or may not be ALU contributable. In case of overlap screening 3 shall be p
screening 2. For screenings 2 - 3, the eNodeB first starts a "cell-barring hysteresis timer" (
times out, raises an"eNodeB Cells Barred" alarm, which triggers DSIM/ CNP (L97933 logic).
eNodeB 40 sec (interval T2) to notify all the UEs. So prior to this point -- that is, during the
"unaware" UEs can still make calls and the eNodeB needs to reject them with proper peggi
UEs are 'aware' that the cell is barred, they will not attempt a call on this cell and thus wil
on the cell. If DSIM is not enabled, the cell barred information cannot be broadcast, and UE
attempt to access the barred cell, resulting in pegging of this counter for each failed attem
is locked and other S1 links experience problems described in Screening 2 resulting in a lo
pegging is done against Screening 3, regardless of the order of S1 events.
This indicator provides the number of Radio Link failures detected by the eNodeB. Radio li
not counted in case RRCConnectionReconfiguration (HO command) or RRCMobilityFromEUT
previously transmitted. Based on 3GPP counter: VS.RadioLinkFailureSum TRIGGER EVENT:
when the Radio Link failure is detected by the eNodeB.
not counted in case RRC connection Reconfiguration or RrcMobilityFromEUTRACommand (H
previously transmitted. Maximum number of DL RLC retransmissions has been reached. Ba
VS.RadioLinkFailure.MaxNbRlcRetransReached TRIGGER EVENT: The counter is triggered w
is detected and no RRC connection Reconfiguration (HO command) has been previously tra
counter handling the number of RLC retransmissions for a given block has its value equal t
value.
not counted in case RRC connection Reconfiguration or RrcMobilityFromEUTRACommand (H
previously transmitted. Loss of UL L1 synchronization. Based on 3GPP counter:
VS.RadioLinkFailure.LossOfUlL1Synchro TRIGGER EVENT: The counter is triggered when: detected and no RRC connection Reconfiguration (HO command) has been previously trans
value computed by the eNodeB is below configurable threshold, indicating a loss of UL syn
the eUTRAN due to CAC failure (Maximum number of call of the eNodeB exceeded, Maximu
modem, ...). The granularity of CAC may be eNodeB, cell or PLMN. Based on 3GPP counter:
RRC.ConnEstabFail.CACFailure TRIGGER EVENT: The counter is triggered on sending of Rrc
This indicator provides the average number of UE in or transitioning into RRC_Connected s
This indicator provides the minimum number of UE that are in or transitioning into RRC CO
the cells. Based on 3GPP counter: RRC.Conn.Min TRIGGER EVENT: The pegging of this coun
procedures when CAC (Call Admission Control) is accepted on context setup (+1) and when
deleted (-1). Remark: "minimum" is when the spatial and temporal aggregation are set to
This indicator provides the CAC failure rate of RRC Connection establishment procedure, e
NOTES: CAC is Call Admission Control.
This indicator provides the number of Initial Context Setup procedures failed for some fail
multiple partial E-RABs setup failure, only the last cause is used to peg the counter. CAC fa
for all E-RABs. Based on 3GPP counter: VS.InitialContextSetupFailed.CACFailure TRIGGER E
triggered on sending of INITIAL CONTEXT SETUP FAILURE message due to CAC failure. NOT
Context Setup partial failure, the Initial Context Setup procedure is considered as success
triggered.
This indicator provides the number of Initial Context Setup procedures that have been fail
causes. In case of multiple partial E-RABs setup failure, only the last cause is used to trigg
Fallback can not be performed. Based on 3GPP counter: VS.InitialContextSetupFailed.CsFa
TRIGGER EVENT: The counter is triggered when the eNodeB receives an S1AP Initial Contex
containing the CSFallbackIndicator IE. CS Fallback is not possible either because the UE do
eligible RAT(s) for CS Fallback, because of RAT or PLMN restrictions for this UE (Handover
a forbidden RAT/ PLMN that is the CSFB target and the call is a non-emergnecy CSFB attem
Fallback features are not activated. NOTES: In case of Initial Context Setup partial failure,
procedure is considered as successful, this counter is not triggered.
This indicator provides the number of Initial Context Setup procedures that have been fail
causes. In case of multiple partial E-RABs setup failure, only the last cause is used to trigg
Context allocation failure. Based on 3GPP counter: VS.InitialContextSetupFailed.ERABCont
TRIGGER EVENT: The counter is triggered when INITIAL CONTEXT SETUP FAILURE message
Context allocation failure. NOTES: In case of Initial Context Setup partial failure, the Initia
is considered as successful, this counter is not triggered.
multiple partial E-RABs setup failure, only the last cause is used to peg the counter. Intern
on 3GPP counter: VS.InitialContextSetupFailed.InternalFailure TRIGGER EVENT: The counte
of INITIAL CONTEXT SETUP FAILURE message due to internal failure. NOTES: In case of Init
failure, the Initial Context Setup procedure is considered as successful, this counter is not
multiple partial E-RABs setup failure, only the last cause is used to peg the counter. UE fai
Based on 3GPP counter: VS.InitialContextSetupFailed.SecurityActivationFailure TRIGGER E
triggered on reception from the UE of RrcSecurityModeFailure or RrcSecurityModeComplet
verification failure. NOTES: In case of Initial Context Setup partial failure, the Initial Conte
considered as successful, this counter is not triggered.
multiple partial E-RABs setup failure, only the last cause is used to peg the counter. Secur
selected because none can match UE security capabilities. Based on 3GPP counter:
VS.InitialContextSetupFailed.SecurityAlgoNotCompatible TRIGGER EVENT: The counter is t
S1-AP INITIAL CONTEXT SETUP REQUEST message from the MME when security algorithms
not compatible with security algorithms supported by UE. NOTES: In case of Initial Context
Initial Context Setup procedure is considered as successful, this counter is not triggered.
multiple partial E-RABs setup failure, only the last cause is used to peg the counter. Timeo
UE). Based on 3GPP counter: VS.InitialContextSetupFailed.Timeout TRIGGER EVENT: The co
of INITIAL CONTEXT SETUP FAILURE message due to expiration of the timer supervising rec
the UE after reception of the S1AP Initial Context Setup Request (cases of UE capability En
Command procedures and no UE answer to the RrcConnectionReconfiguration). NOTES: In
Setup partial failure, the Initial Context Setup procedure is considered as successful, this c
multiple partial E-RABs setup failure, only the last cause is used to peg the counter. Integr
a received UL RRC message after AS security has been activated (reception of RRC Securit
successful integrity verification). Based on 3GPP counter: VS.InitialContextSetupFailed.Int
EVENT: The counter is triggered on detection of integrity failure on a received UL RRC mes
Initial Context Setup partial failure, the Initial Context Setup procedure is considered as su
not triggered.
Initial_ERAB_Setup_SR_ATT
This indicator provides the total number of initial E-RAB setup requ
This indicator provides the total number of initial E-RAB setup succe
This indicator provides the success rate of S1 dedicated connection establishment procedu
one that will be used for dialog between the eNodeB and the MME as well as for NAS trans
the MME.
This indicator indicates the number of 'UE INITIAL MESSAGE' sent to the MME. Based on 3G
S1SIG.ConnEstabAtt TRIGGER EVENT: The counter is triggered when the UE INITIAL MESSA
This indicator is providing the number of DL NAS TRANSPORT messages received just after
been sent (only the first received message is considered). Based on 3GPP counter: VS.Firs
EVENT: The counter is triggered when the first DL NAS TRANSPORT message is received.
This indicator is providing the number of INITIAL CONTEXT SETUP REQUEST messages rece
NAS TRANSPORT' message received before INITIAL CONTEXT SETUP REQUEST. Based on 3G
VS.UEContextSetupRequest.AfterDLNASTransport TRIGGER EVENT: The counter is triggere
CONTEXT SETUP REQUEST message is received.
This indicator is providing the number of INITIAL CONTEXT SETUP REQUEST messages rece
'DL NAS TRANSPORT' message received before INITIAL CONTEXT SETUP REQUEST. Based on
VS.UEContextSetupRequest.WithoutPreviousDLNASTransport TRIGGER EVENT: The counter
S1AP INITIAL CONTEXT SETUP REQUEST message is received.
This indicator is providing the number of S1 dedicated connection establishment failures f

Procedure failure due to timeout. Based on 3GPP counter: VS.S1ConnectionEstablishmentF
EVENT: The counter is triggered on expiration of the timer supervising reception of S1 mes
This indicator provides the number of UE Context Setup request
This indicator provides the number of S1 dedicated connection establishment success. Thi
that will be used for dialog between the eNodeB and the MME as well as for NAS transport
MME.
This indicator provides the number of local UE contexts releases for some causes. Release
RESET procedure MME initiated. Based on 3GPP counter: VS.LocalUEContextRelease.S1APR
EVENT: The counter is triggered when UE context is locally released on reception of S1 RES
WARNING: The counter has never been implemented so removed This indicator provides th
contexts releases for some causes. Release of UE context on S1 RESET procedure eUTRAN
eNodeB Lock. Based on 3GPP counter: VS.LocalUEContextRelease.S1APResetOAM TRIGGER
triggered when UE context is locally released on sending of S1 RESET message to MME. NO
because no way to distinguish the real trigger for cell lock.
This indicator provides the number of local UE contexts releases for some causes. Release
RESET procedure eUTRAN initiated (Modem failure). Based on 3GPP counter:
VS.LocalUEContextRelease.S1APResetENodeB TRIGGER EVENT: The counter is triggered w
released on sending of S1 RESET message to MME.
This indicator provides the number of local UE contexts releases for some causes. All MME
Based on 3GPP counter: VS.LocalUEContextRelease.S1FaultExternalFailure TRIGGER EVENT
when UE context is locally released because local release of the UE Context is called for th
'Description'.
This indicator provides the number of local UE contexts releases for some causes. S1AP UE
REQUEST has been sent (with cause different from User Inactivity) and expiration of the ti
of S1AP UE CONTEXT RELEASE COMMAND message. Based on 3GPP counter:
VS.LocalUEContextRelease.NoContextReleaseCommand TRIGGER EVENT: The counter is tri
is locally released on expiration of the timer supervising reception of S1AP UE CONTEXT R
message.
This indicator provides the number of UE CONTEXT RELEASE REQUEST messages sent. All t
Redirection (to HRPD, UTRA FDD, UTRA TDD, GERAN) whatever the trigger of this redirecti
Based on 3GPP counter: VS.UEContextReleaseRequest.InterRATRedirection TRIGGER EVEN
triggered when the UE CONTEXT RELEASE REQUEST message is sent.
This indicator provides the number of UE CONTEXT RELEASE REQUEST messages sent. Bas
VS.UEContextReleaseRequestSum TRIGGER EVENT: The counter is triggered when the UE C
REQUEST message is sent.
This indicator provides the number of UE CONTEXT RELEASE REQUEST messages sent. Rad
establishment timer expires (the radio connection with the UE was lost). Based on 3GPP co
VS.UEContextReleaseRequest.RadioLinkFailure TRIGGER EVENT: The counter is triggered w
RELEASE REQUEST message is sent.
This indicator provides the number of UE CONTEXT RELEASE REQUEST messages sent. Use
3GPP counter: VS.UEContextReleaseRequest.UserInactivity TRIGGER EVENT: The counter is
CONTEXT RELEASE REQUEST message is sent.
This indicator provides the number of UE CONTEXT RELEASE REQUEST messages sent. Inte
3GPP counter: VS.UEContextReleaseRequest.InternalFailure TRIGGER EVENT: The counter
CONTEXT RELEASE REQUEST message is sent. NOTES: On sending of UE context release re
with repetitions, if the UE context release command is not received, the UE context releas
generated reason" is sent and the counter is incremented.
This indicator provides the number of UE CONTEXT RELEASE REQUEST messages sent. Exp
supervising reception of INITIAL CONTEXT SETUP REQUEST message. Based on 3GPP count
VS.UEContextReleaseRequest.NoInitialContextSetupRequest TRIGGER EVENT: The counter
This indicator provides the number of UE CONTEXT RELEASE REQUEST messages sent. Sec
selected because none can match UE security capabilities: Reception of S1-AP INITIAL CON
message from the MME when security algorithms supported by eNodeB are not compatible
supported by UE. Based on 3GPP counter: VS.UEContextReleaseRequest.SecurityAlgoNotC
EVENT: The counter is triggered when the UE CONTEXT RELEASE REQUEST message is sent
This indicator provides the number of UE CONTEXT RELEASE REQUEST messages sent. Fail
(Security Mode Failure, Timeout or Integrity Failure). Based on 3GPP counter:
VS.UEContextReleaseRequest.RadioInterfaceFailure TRIGGER EVENT: The counter is trigge
This indicator provides the number of UE CONTEXT RELEASE REQUEST messages sent. X2R
Expiration of X2Release timer, supervising Handover execution procedure (that is no X2AP
answer from the target eNodeB). Based on 3GPP counter: VS.UEContextReleaseRequest.X
This indicator provides the number of UE CONTEXT RELEASE REQUEST messages sent.
TS1RelocOverallForPSHandoverToUtraFdd timeout: Expiration of TS1RelocOverall timer, su
execution procedure (that is no S1AP UE CONTEXT RELEASE COMMAND from the MME). Ba
VS.UEContextReleaseRequest.TS1RelocOveralForPSHOToUtraTimeout TRIGGER EVENT: The
when the UE CONTEXT RELEASE REQUEST message is sent.
Based on 3GPP counter: VS.UEContextReleaseRequest.InterFreqRedirection TRIGGER EVEN
triggered when the UE CONTEXT RELEASE REQUEST message is sent.
on a received UL RRC message after AS security has been activated (reception of RRC Secu
successful integrity verification). Based on 3GPP counter: VS.UEContextReleaseRequest.In
This indicator provides the number of UE CONTEXT RELEASE COMMAND messages received
VS.UEContextReleaseCommandSum TRIGGER EVENT: The counter is triggered when UE CO
COMMAND message is received.
COMMAND received following UE CONTEXT RELEASE REQUEST sent by the eNodeB. Based o
VS.UEContextReleaseCommand.ResponseToReleaseRequest TRIGGER EVENT: The counter
CONTEXT RELEASE COMMAND message is received.
CONTEXT RELEASE COMMAND = 'Normal release' and no UE CONTEXT RELEASE REQUEST h
Based on 3GPP counter: VS.UEContextReleaseCommand.NormalRelease TRIGGER EVENT: T
when UE CONTEXT RELEASE COMMAND message is received. NOTES: When screenings 5 or
1 or 3 are simultaneously pegged.
CONTEXT RELEASE COMMAND = 'Authentication Failure' and no UE CONTEXT RELEASE REQ
previously. Based on 3GPP counter: VS.UEContextReleaseCommand.AuthenticationFailure
counter is triggered when UE CONTEXT RELEASE COMMAND message is received.
CONTEXT RELEASE COMMAND = 'Detach' and no UE CONTEXT RELEASE REQUEST has been
3GPP counter: VS.UEContextReleaseCommand.Detach TRIGGER EVENT: The counter is trig
RELEASE COMMAND message is received. NOTES: When screenings 5 or 6 are pegged, scre
simultaneously pegged.
CONTEXT RELEASE COMMAND = 'Successful Handover' and no UE CONTEXT RELEASE REQU
previously. Based on 3GPP counter: VS.UEContextReleaseCommand.SuccessfulHandover T
counter is triggered when UE CONTEXT RELEASE COMMAND message is received.
This indicator provides the number of local UE contexts releases. Based on 3GPP counter:
VS.LocalUEContextReleaseSum TRIGGER EVENT: The counter is triggered when UE context
This indicator provides the number of E-RABs released after abnormal behavior. The E
interrupted for any abnormal reason.
ERAB_Drops_incl_Mobility
This indicator provides the rate of system non-GBR E-RABs that are dropped (associated to
The mobility is not taken into account. The normal release counter is not incremented on s
handover success. The abnormal release counter is not incremented in case of drop on mo
failure +RRC reestab failure). At cell level, this indicator will not reflect the real activity an
user point of view), it will not include the mobility failures. The advantage is to have a rate
depending on handover activity, the rate is more or less correct.
HO_Success_Rate
HO_Prep_Success_Rate
HO_Exec_Success_Rate
This indicator provides the number of times that an outgoing inter-eNodeB X2 handover p
failed. Based on 3GPP counter: VS.OutgoingInterENodeBX2HOFailureSum TRIGGER EVENT:
when there is any failure (abort are excluded), including protocol errors, that makes X2 ha
perform. NOTES: in case of Outgoing Inter-eNodeB X2 Handover resource allocation partia
Inter-eNodeB X2 Handover preparation procedure is considered as successful, this counter
stage.
failed for some failure causes. RRC connection re-establishment On the source cell. Based
VS.OutgoingInterENodeBX2HOFailure.RRCConnectionReestablishmentOnSourceCell TRIGG
triggered on reception of RrcConnectionReestablishmentRequest in the source cell. NOTES
failure is due to S1 faults or cell barring at the Target eNodeB, the target pegs HO failure a
screening (see counter 12713). As such this counter at Source eNodeB currently does not
in the Handover Preparation Failure message received. In case of Outgoing Inter-eNodeB X
allocation partial failure, the Outgoing Inter-eNodeB X2 Handover preparation procedure i
successful, this counter is not pegged at this stage.
failed for some failure causes. X2Release timeout. Based on 3GPP counter:
VS.OutgoingInterENodeBX2HOFailure.X2ReleaseTimeout TRIGGER EVENT: The counter is t
X2Release timer, supervising Handover execution procedure (that is no X2AP RELEASE RES
target eNodeB). NOTES: If an inter-eNodeB HO failure is due to S1 faults or cell barring at
target pegs HO failure against a specific screening (see counter 12713). As such this count
currently does not screen on the cause value in the Handover Preparation Failure message
Outgoing Inter-eNodeB X2 Handover resource allocation partial failure, the Outgoing Inter
preparation procedure is considered as successful, this counter is not pegged at this stage
failed for some failure causes. Handover preparation failure. Based on 3GPP counter:
VS.OutgoingInterENodeBX2HOFailure.HOPreparationFailureOther TRIGGER EVENT: The cou
HANDOVER PREPARATION FAILURE received from the target eNodeB. NOTES: If an inter-eN
S1 faults or cell barring at the Target eNodeB, the target pegs HO failure against a specific
12713). As such this counter at Source eNodeB currently does not screen on the cause val
Preparation Failure message received. In case of Outgoing Inter-eNodeB X2 Handover reso
failure, the Outgoing Inter-eNodeB X2 Handover preparation procedure is considered as su
not pegged at this stage.
failed for some failure causes. X2Preparation timeout. Based on 3GPP counter:
VS.OutgoingInterENodeBX2HOFailure.X2PreparationTimeout TRIGGER EVENT: The counter
of X2Preparation timer, supervising handover preparation procedure (that is no answer fro
NOTES: If an inter-eNodeB HO failure is due to S1 faults or cell barring at the Target eNode
failure against a specific screening (see counter 12713). As such this counter at Source eN
screen on the cause value in the Handover Preparation Failure message received. In case o
X2 Handover resource allocation partial failure, the Outgoing Inter-eNodeB X2 Handover p
considered as successful, this counter is not pegged at this stage.
has aborted. Based on 3GPP counter: VS.OutgoingInterENodeBX2HOAbortSum TRIGGER EV
triggered when there is any event that interrupts the handover.
This indicator provides the number of times an outgoing inter-eNodeB X2 handover proced
cell . Decision to perform a CS Fallback. Based on 3GPP counter: VS.OutgoingInterENodeBX
TRIGGER EVENT: The counter is triggered on decision to perform a CS Fallback. NOTES: Scr
not be pegged when X2 handover preparation concerns an off-loading
cell . Inter-frequency Handover preparation cancelled upon reception of A1 event (leaving
on 3GPP counter: VS.OutgoingInterENodeBX2HOAbort.EventA1 TRIGGER EVENT: The count
reception of A1 event (leaving alarm conditions). NOTES: Screening values 0 to 5 shall not
handover preparation concerns an off-loading
aborted. S1AP Reset received from the MME or S1AP Reset eNodeB initiated or S1AP UE Co
received from the MME (with cause other than Succeful Handover). Based on 3GPP counte
VS.OutgoingInterENodeBX2HOAbort.Other TRIGGER EVENT: The counter is triggered on S1
the MME or S1AP Reset eNodeB initiated or S1AP UE Context Release Command received f
other than successfull handover). NOTES: Screening values 0 to 5 shall not be pegged whe
preparation concerns an off-loading mobility.
cell. Inter-frequency or intra-frequency Handover preparation of a VoIP call cancelled upon
ACK with no VoIP bearer admission. Based on 3GPP counter:
VS.OutgoingInterENodeBX2HOAbort.VoIPBearerNonAdmission TRIGGER EVENT: The counte
reception of HO Request ACK. NOTES: Screening values 0 to 5 shall not be pegged when X
concerns an off-loading mobility.
cell . Reception of X2AP Reset before HO request ACK. Based on 3GPP counter:
VS.OutgoingInterENodeBX2HOAbort.X2APReset TRIGGER EVENT: The counter is triggered
Reset. NOTES: Screening values 0 to 5 shall not be pegged when X2 handover preparation
mobility.
aborted. Reception of RrcMeasurementReport (measId configured for mobility trigger) trig
handover during Inter-EnodeB outgoing X2 handover procedure. Based on 3GPP counter:
VS.OutgoingInterENodeBX2HOAbort.CascadedHandover TRIGGER EVENT: The counter is tr
RrcMeasurementReport (measId configured for HO mobility trigger). NOTES: Screening va
pegged when X2 handover preparation concerns an off-loading
This indicator provides the success rate of all inter-cell intra-LTE handover procedure on
serving cell and target cell are the same. INCLUDING RRC_ReEstablishments for
This indicator provides the number of times that an incoming inter-eNodeB X2 handover p
failed. Based on 3GPP counter: VS.IncomingInterENodeBX2HOFailureSum TRIGGER EVENT:
when there is any failure (abort are excluded), including protocol errors, that makes hando
perform. In case of incoming Inter-eNodeB X2 handover resource allocation partial failure,
eNodeB X2 handover preparation procedure is considered as successful, the counter is not
failed for some failure causes. Path switch failure. Based on 3GPP counter:
VS.IncomingInterENodeBX2HOFailure.PathSwitchFailure TRIGGER EVENT: The counter is tr
PATH SWITCH REQUEST FAILURE S1AP message from the MME. NOTES: Even if re-establish
performed in the target cell, handover procedure is considered as failed. If one or more S1
S1 links experience problems described in Screening 7 resulting in a loss of S1 service, the
Screening 0, regardless of the order of S1 events. When triggered for radio reason in case
X2 Handover partial failure, the Incoming Inter-eNodeB X2 Handover procedure is conside
counter is not pegged. Otherwise in case of off-loading, the partial failure induces a X2 Ha
failed for some failure causes. S1PathSwitch timeout. Based on 3GPP counter:
VS.IncomingInterENodeBX2HOFailure.S1PathSwitchTimeout TRIGGER EVENT: The counter
of S1PathSwitch timer, supervising User Plane path switch procedure (that is no answer to
received from the MME). NOTES: Even if re-establishment is successfully performed in the
procedure is considered as failed. If one or more S1 link is locked and other S1 links exper
in Screening 7 resulting in a loss of S1 service, the pegging is done against Screening 0, re
S1 events. When triggered for radio reason in case of Incoming Inter-eNodeB X2 Handover
Incoming Inter-eNodeB X2 Handover procedure is considered as successful, this counter is
case of off-loading, the partial failure induces a X2 Handover cancellation.
failed for some failure causes. InterENodeBHO timeout. Based on 3GPP counter:
VS.IncomingInterENodeBX2HOFailure.InterEnbHOTimeout TRIGGER EVENT: The counter is
InterEnbHo timer, supervising Handover execution procedure. This means: If PDCP SN stat
apply for any E-RAB, no RrcConnectionReconfigurationComplete message received from th
preservation does apply for at least one E-RAB, no reception of X2 SN STATUS TRANFER fro
RrcConnectionReconfigurationComplete from the UE. NOTES: Even if re-establishment is su
the target cell, handover procedure is considered as failed. If one or more S1 link is locked
experience problems described in Screening 7 resulting in a loss of S1 service, the peggin
for some failure causes. Integrity verification is failed on an UL RRC message received on S
Reconfiguration Complete) or SRB2. Based on 3GPP counter: VS.IncomingInterENodeBX2H
TRIGGER EVENT: The counter is triggered on detection of integrity failure on a received UL
Even if re-establishment is successfully performed in the target cell, handover procedure i
one or more S1 link is locked and other S1 links experience problems described in Screenin
S1 service, the pegging is done against Screening 0, regardless of the order of S1 events.
reason in case of Incoming Inter-eNodeB X2 Handover partial failure, the Incoming Inter-e
procedure is considered as successful, this counter is not pegged. Otherwise in case of off
failure induces a X2 Handover cancellation.
has aborted. Based on 3GPP counter: VS.IncomingInterENodeBX2HOAbortSum TRIGGER EV
triggered when there is any failure, including protocol errors, that makes handover imposs
aborted. Reception of X2AP Handover Cancel. Based on 3GPP counter:
VS.IncomingInterENodeBX2HOAbort.X2APHOCancel TRIGGER EVENT: The counter is trigge
Handover Cancel.
the cell . Reception of X2AP Reset. Based on 3GPP counter: VS.IncomingInterENodeBX2HO
TRIGGER EVENT: The counter is triggered on reception of X2AP Reset.
This indicator provides the number of times that an intra-eNodeB handover procedure tow
failed. Based on 3GPP counter: VS.IntraENodeBHOFailureSum TRIGGER EVENT: The counte
is any failure (abort are excluded), including protocol errors, that makes handover imposs
Currently the counter is not pegged for non-eligible cells. A barred cell is considered as no
Intra-eNodeB Handover partial failure, the Intra-eNodeB Handover procedure is considered
counter is not pegged.
for some failure causes. Internal eNodeB failure (during preparation or execution procedur
counter: VS.IntraENodeBHOFailure.InternalFailure TRIGGER EVENT: Handover procedure fa
eNodeB failure. NOTES: If there is an S1 fault, calls are released, for example see counter
intra-eNodeB HO is attempted.
for some failure causes. Timeout (no answer from the UE). Based on 3GPP counter:
VS.IntraENodeBHOFailure.Timeout TRIGGER EVENT: Expiration of the timer supervising the
RrcReconfigurationComplete message from the UE. NOTES: If there is an S1 fault, calls are
see counter 12508, and therefore no intra-eNodeB HO is attempted.
This indicator provides the number of times an intra-eNodeB handover procedure towards
failure causes. Timeout (no answer from the UE) during inter-frequency handover. Based o
VS.IntraENodeBHOFailure.InterFreqTimeout TRIGGER EVENT: The counter is triggered on e
supervising the reception of RrcReconfigurationComplete message from the UE. NOTES: If
are released, for example see counter 12508, and therefore no intra-eNodeB HO is attemp
This indicator provides the number of times an intra-eNodeB handover procedure towards
failure causes. CAC failure for all E-RABs during inter-frequency handover. The granularity
cell or PLMN. Based on 3GPP counter: VS.IntraENodeBHOFailure.InterFreqCACFailure TRIGG
triggered when the handover procedure failed due to a lack of resource in the target cell.
fault, calls are released, for example see counter 12508, and therefore no intra-eNodeB HO
Intra-eNodeB Handover partial failure, the Intra-eNodeB handover procedure is considered
counter is not pegged.
This indicator provides for FDD technology the "average" downlink throughput (including D
message 4, PDSCH and HARQ retransmissions) experienced on the L1 shared channels of t
broadcast data transmissions (SIBx, Paging) on PDSCH as well as SRB0 traffic. RACH respo
The throughput formula is the number of DL kbits over the number of TTIs used (containin
This indicator provides for FDD technology the "maximum" downlink throughput (including
includes broadcast data transmissions (SIBx, Paging) on PDSCH as well as SRB0 traffic. RA
included. The counter is sampled every 5 seconds and updated based on throughput value
every mobiles scheduled on the cell during this sampling period. Based on 3GPP counter:
VS.CellDLL1ThroughputLoad.Max TRIGGER EVENT: 1.Trigger: MAC entity sends a MAC PDU
(including HARQ retransmissions). Actions: L1DlPayload += TBS in bits 2.Trigger: Every TT
MAC PDU has been sent on L1 channel during this TTI then nbDlL1TTI++. 3.Trigger: At the
period (5 seconds). Actions: Add integer part of (L1DlPayload / 1024) to CUMULATED VALU
NUMBER OF EVENTS (not rounded down to integer). L1DlPayload = 0, nbDlL1TTI = 0. Rema
the spatial and temporal aggregation are set to MAX.
This indicator provides for FDD technology the "minimum" downlink throughput (including
includes broadcast data transmissions (SIBx, Paging) on PDSCH as well as SRB0 traffic. RA
included. The counter is sampled every 5 seconds and updated based on throughput value
every mobiles scheduled on the cell during this sampling period. Based on 3GPP counter:
VS.CellDLL1ThroughputLoad.Min TRIGGER EVENT: 1.Trigger: MAC entity sends a MAC PDU
(including HARQ retransmissions). Actions: L1DlPayload += TBS in bits 2.Trigger: Every TT
MAC PDU has been sent on L1 channel during this TTI then nbDlL1TTI++. 3.Trigger: At the
period (5 seconds). Actions: Add integer part of (L1DlPayload / 1024) to CUMULATED VALU
NUMBER OF EVENTS (not rounded down to integer). L1DlPayload = 0, nbDlL1TTI = 0. Rema
the spatial and temporal aggregation are set to MIN.
DL_RLC_Enhanced_Tput_kbps
This indicator provides the distribution of the downlink throughput (including HARQ retran
on the L1 shared channels of the cell. The counter includes broadcast data transmissions (
as well as SRB0 traffic. RACH responses are not included. Number of L1 downlink throughp
Range4. Based on 3GPP counter: VS.CellDLL1Throughput.GTRange4 NOTES: L1DlThroughp
used are hard coded . L1DlThroughputMinKb = 0 kbps, - For FDD: Range1=128 kbps, Rang
1000 kbps, Range4= 5000 kbps - For TDD: Range1=128 kbps*VS_TTIs_all_DL_ratio, Range2
kbps*VS_TTIs_all_DL_ratio, Range3= 1000 kbps*VS_TTIs_all_DL_ratio, Range4= 5000 kbps*V
counter is sampled every 5 seconds and updated based on throughput values computed gl
scheduled on the cell during this sampling period. In order to avoid pegging the counter w
values, the throughput is only taken into account if at least L1DlThroughputMinKb KiBytes
sent during this period.] This counter provides the distribution of the downlink throughpu
retransmissions) experienced on the L1 shared channels of the cell. The counter includes b
transmissions (SIBx, Paging) on PDSCH as well as SRB0 traffic. RACH responses are not inc
sampled every 5 seconds and updated based on throughput values computed globally for
on the cell during busy TTIs of this sampling period. In order to avoid pegging the counter
sent during this period. TRIGGER EVENT: 1.Trigger: MAC entity sends a MAC PDU on the L1
retransmissions). Actions: L1DlPayload += TBS (in kbits) . 2.Trigger: Every TTI. Actions: If
been sent on L1 channel during this TTI then nbDlL1TTI++ . 3.Trigger: At the end of the sa
seconds). Actions: If (L1DlPayload > L1DlThroughputMinKb) then L1DlThroughput = (L1DlP
ttiDuration)) L1DlThroughput is in kbits/s and ttiDuration = 0.001 s. The sub-counter that
L1DlThroughput is incremented by 1 else the counter is not pegged, L1DlPayload = 0, nbD
Range2 and lower or equal to Range3. Based on 3GPP counter: VS.CellDLL1Throughput.GT
L1DlThroughputMinKb and the 4 values used are hard coded . L1DlThroughputMinKb = 0 k
Range1=128 kbps, Range2= 512 kbps, Range3= 1000 kbps, Range4= 5000 kbps - For TDD
Range4= 5000 kbps*VS_TTIs_all_DL_ratio The counter is sampled every 5 seconds and upd
values computed globally for every mobiles scheduled on the cell during this sampling per
pegging the counter with non-representative values, the throughput is only taken into acc
L1DlThroughputMinKb KiBytes (1024 Bytes) have been sent during this period.] This count
distribution of the downlink throughput (including HARQ retransmissions) experienced on
the cell. The counter includes broadcast data transmissions (SIBx, Paging) on PDSCH as we
responses are not included. The counter is sampled every 5 seconds and updated based on
computed globally for every mobiles scheduled on the cell during busy TTIs of this samplin
avoid pegging the counter with non-representative values, the throughput is only taken in
L1DlThroughputMinKb KiBytes (1024 Bytes) have been sent during this period. TRIGGER E
entity sends a MAC PDU on the L1 channel (including HARQ retransmissions). Actions: L1D
. 2.Trigger: Every TTI. Actions: If at least one MAC PDU has been sent on L1 channel during
+ . 3.Trigger: At the end of the sampling period (5 seconds). Actions: If (L1DlPayload > L1D
L1DlThroughput = (L1DlPayload / (nbDlL1TTI * ttiDuration)) L1DlThroughput is in kbits/s an
The sub-counter that corresponds to the L1DlThroughput is incremented by 1 else the cou
L1DlPayload = 0, nbDlL1TTI = 0.
to Range1 Based on 3GPP counter: VS.CellDLL1Throughput.LeRange1 NOTES: L1DlThrough
values used are hard coded . L1DlThroughputMinKb = 0 kbps, - For FDD: Range1=128 kbps
Range3= 1000 kbps, Range4= 5000 kbps - For TDD: Range1=128 kbps*VS_TTIs_all_DL_rati
counter is sampled every 5 seconds and updated based on throughput values computed gl
scheduled on the cell during this sampling period. In order to avoid pegging the counter w
sent during this period.] This counter provides the distribution of the downlink throughpu
retransmissions) experienced on the L1 shared channels of the cell. The counter includes b
transmissions (SIBx, Paging) on PDSCH as well as SRB0 traffic. RACH responses are not inc
sampled every 5 seconds and updated based on throughput values computed globally for
on the cell during busy TTIs of this sampling period. In order to avoid pegging the counter
sent during this period. TRIGGER EVENT: 1.Trigger: MAC entity sends a MAC PDU on the L1
retransmissions). Actions: L1DlPayload += TBS (in kbits) . 2.Trigger: Every TTI. Actions: If
been sent on L1 channel during this TTI then nbDlL1TTI++ . 3.Trigger: At the end of the sa
seconds). Actions: If (L1DlPayload > L1DlThroughputMinKb) then L1DlThroughput = (L1DlP
ttiDuration)) L1DlThroughput is in kbits/s and ttiDuration = 0.001 s. The sub-counter that
L1DlThroughput is incremented by 1 else the counter is not pegged, L1DlPayload = 0, nbD
This indicator provides the high ratio distribution (for FDD above 5Mbit/s and for TDD abov
5Mbit/s*VS_TTIs_all_DL_ratio) of the downlink throughput (including HARQ retransmissions
shared channels of the cell.
This indicator provides the distribution for all the PRB of Uplink noise monitored on the ce
NOTES: Range1= -115 db, Range2= -112 db, Range3= -105 db, Range4= -90 db .
<= -112db . NOTES: Range1= -115 db, Range2= -112 db, Range3= -105 db, Range4= -90 d
<= -105db . NOTES: Range1= -115 db, Range2= -112 db, Range3= -105 db, Range4= -90 d
<= -90db . NOTES: Range1= -115 db, Range2= -112 db, Range3= -105 db, Range4= -90
NOTES: Range1= -115 db, Range2= -112 db, Range3= -105 db, Range4= -90 db .
This indicator provides the high+high_med+high_low distribution of Uplink Noise measure
This indicator provides the low+med_low distribution of Uplink Noise measured.

This indicator provides the high+high_med+high_low ratio distribution of Uplink Noise mea
This indicator provides the low+med_low ratio distribution of Uplink Noise measured.
This indicator provides the distribution per 4 PRBs group of Uplink noise monitored on the
each PRB of the group, the measure is done and the corresponding counter range is increm
noise values greater than Range4 for the 4 PRBs of group1 (PRB01 to PRB04). Based on 3G
VS.ULNoisePerPRBGroup.GtRg4PRBg1 NOTES: The 4 values used as screenings' criteria ar
-115 db, Range2= -112 db, Range3= -105 db, Range4= -90 db. This counter is a 'On deman
releases it will not be systematically reported to the EMS. TRIGGER EVENT: The counter is
term period (period duration configurable and set to P2 by default) averaged NoisePower
eNodeB for each PRB. The counter is updated every 1000 radio frames with the latest com
corresponding 4 PRBs group (the screening (sub-counter) that corresponds to the NoisePo
by 1).
by 1).
by 1).
by 1).
by 1).
by 1).
by 1).
by 1).
by 1).
noise values greater than Range4 for the 4 PRBs of group10 (PRB37 to PRB40). Based on 3
VS.ULNoisePerPRBGroup.GtRg4PRBg10 NOTES: The 4 values used as screenings' criteria a
by 1).
by 1).
by 1).
by 1).
noise values greater than Range3 and lower or equal to Range4 for the 4 PRBs of group1 (
on 3GPP counter: VS.ULNoisePerPRBGroup.GtRg3LeRg4PRBg1 NOTES: The 4 values used a
hard coded . Range1= -115 db, Range2= -112 db, Range3= -105 db, Range4= -90 db. This
counter. In the future releases it will not be systematically reported to the EMS. TRIGGER E
pegged based on the long term period (period duration configurable and set to P2 by defa
metric computed by the eNodeB for each PRB. The counter is updated every 1000 radio fra
computed noise value for the corresponding 4 PRBs group (the screening (sub-counter) th
NoisePower value is incremented by 1).
noise values greater than Range3 and lower or equal to Range4 for the 4 PRBs of group10
on 3GPP counter: VS.ULNoisePerPRBGroup.GtRg3LeRg4PRBg10 NOTES: The 4 values used
Based on 3GPP counter: VS.ULNoisePerPRBGroup.GtRg3LeRg4PRBg25 NOTES: The 4 value
criteria are hard coded . Range1= -115 db, Range2= -112 db, Range3= -105 db, Range4= 'On demand' counter. In the future releases it will not be systematically reported to the EM
counter is pegged based on the long term period (period duration configurable and set to
NoisePower metric computed by the eNodeB for each PRB. The counter is updated every 1
latest computed noise value for the corresponding 4 PRBs group (the screening (sub-coun
the NoisePower value is incremented by 1).
Data_acc_ACC02_wo_reptn
This indicator provides the success rate of RRC Connection establishment procedure proce
repetitions.
This indicator provides the number for RRC connection requests received from UE in the ce
repetitions. TRIGGER EVENT: The counter is triggered when the first RrcConnectionReques
from UE in the cell. This is detected through InitialUE-Identity IE received in RrcConnection
EstablishmentCause of the concerned screening: - If s-TMSI is present, no UE in the cell con
value stored and same EstablishmentCause value - If randomValue is present, no UE conte
the same value stored and same EstablishmentCause value.
This indicator provides the success rate of S1 dedicated connection establishment procedu
one that will be used for dialog between the eNodeB and the MME as well as for NAS trans
the MME.
This indicator provides the number of S1 dedicated connection establishment success. Thi
MME.
This indicator provides the number of S1 dedicated connection establishment attempt. Th

MME.
This indicator provides the rate of system non-GBR E-RABs that are dropped (associated to
The mobility is not taken into account. The normal release counter is not incremented on s
handover success. The abnormal release counter is not incremented in case of drop on mo
failure +RRC reestab failure). At cell level, this indicator will not reflect the real activity an
user point of view), it will not include the mobility failures. The advantage is to have a rate
depending on handover activity, the rate is more or less correct.
This indicator provides the number of system non-GBR E-RABs released after normal usage
normally ended excluding non-GBR ERAB HO but including Inter-RAT Redirection. Remark:
from eNodeb/MME point of view, the non-GBR ERAB is not released but transfered on anot
This indicator provides the number of system non-GBR E-RABs released after normal usage
normally ended excluding non-GBR ERAB HO but including Inter-RAT Redirection. Remark:
from eNodeb/MME point of view, the non-GBR ERAB is not released but transfered on anot
This indicator provides the success rate of all inter-cell intra-LTE handover procedure on ta
serving cell and target cell are the same. INCLUDING RRC_ReEstablishments for Intra_Freq
This indicator provides the success rate of all inter-cell intra-LTE handover procedure on ta
serving cell and target cell are the same. INCLUDING RRC_ReEstablishments for Intra_Freq
This indicator provides the number of all inter-cell intra-LTE handover request on target ce
cell and target cell are the same.
Percent_IRAT_Redir_Excl_CSFB
This indicator provides the ratio of number of times that UEs are eligible
Percent_IRAT_Redir_Excl_CSFB
This indicator provides the success rate of all Inter LTE inter-cell mobility procedu
This indicator provides the number of outgoing inter-eNodeB X2 handover procedure faile
Frequency of serving cell and target cell are different, but both are FDD frequency, or TDD
abort causes. Frequency of serving cell and target cell are different, but both are FDD freq
This indicator provides the number of times an outgoing inter-frequency inter-eNodeB X2

towards the cell is aborted. Frequency of serving cell and target cell are different, but bot
TDD frequency. Based on 3GPP counter:
VS.OutgoingInterENodeBX2HOAbortScreenedSum.InterFreqSameFrameStructure TRIGGER
This indicator provides the number of outgoing inter-eNodeB X2 handover execution proce
(execution is after preparation success and before handover success). Frequency of servin
different, but both are FDD frequency, or TDD frequency.
Frequency of serving cell and target cell are different, but both are FDD frequency, or TDD
This indicator provides the number of times that an incoming inter-frequency inter-eNodeB
towards the cell is aborted. Frequency of serving cell and target cell are different, but bot
TDD frequency. Based on 3GPP counter:
VS.IncomingInterENodeBX2HOAbortScreenedSum.InterFreqSameFrameStructure TRIGGER
abort causes. Frequency of serving cell and target cell are different, but both are FDD freq
for some failure causes. Integrity verification is failed on an UL RRC message received on S
Reconfiguration Complete) or SRB2 during inter-frequency handover. Based on 3GPP count
VS.IncomingInterENodeBX2HOFailure.InterFreqIntegrityFailure TRIGGER EVENT: The count
detection of integrity failure on a received UL RRC message. NOTES: Even if re-establishm
performed in the target cell, handover procedure is considered as failed. If one or more S1
S1 links experience problems described in Screening 7 resulting in a loss of S1 service, the
for some failure causes. InterENodeBHO timeout during inter-frequency handover. Based o
VS.IncomingInterENodeBX2HOFailure.InterFreqInterEnbHOTimeout TRIGGER EVENT: The co
expiration of InterEnbHo timer, supervising Handover execution procedure. This means: If
preservation does not apply for any E-RAB, no RrcConnectionReconfigurationComplete me
UE. If PDCP SN status preservation does apply for at least one E-RAB, no reception of X2 S
the source eNodeB or RrcConnectionReconfigurationComplete from the UE. NOTES: Even if
successfully performed in the target cell, handover procedure is considered as failed. If on
locked and other S1 links experience problems described in Screening 7 resulting in a loss
pegging is done against Screening 0, regardless of the order of S1 events. When triggered
of Incoming Inter-eNodeB X2 Handover partial failure, the Incoming Inter-eNodeB X2 Hand
considered as successful, this counter is not pegged. Otherwise in case of off-loading, the
X2 Handover cancellation.
PCT_IRAT_Redirect_nonLTE
HandoversuccessrateofallPSinter-cellprocedureonsourcecellforInterRATtoUTRAN
NumberofPSinter-cellHOproceduremeasuredonsourcecellforInterRATtoUTRAN(TD
FORMULA
(VS_RRC_cnx_WithoutRepetition_succ_rate)*(_S1_sig_estab_succ_rate_ATT)*(_Initial
_ERAB_Setup_SR_ATT)
VS_RRC_cnx_WithoutRepetition_fail/VS_RRC_cnx_WithoutRepetition_req
VS_RRC_cnx_succ/VS_RRC_cnx_WithoutRepetition_req
VS_RRC_cnx_WithoutRepetition_req-VS_RRC_cnx_succ
(VS_UE_RRC_connected_state_cum/VS_UE_RRC_connected_state_NbEvt)*VS_nb_PL
MNs_OnCell
((SAEB_EstabInitSuccNbr_QCI2+SAEB_EstabInitSuccNbr_QCI3+SAEB_EstabInitSucc
Nbr_QCI4+SAEB_EstabInitSuccNbr_QCI6+SAEB_EstabInitSuccNbr_QCI7+SAEB_Est
abInitSuccNbr_QCI8+SAEB_EstabInitSuccNbr_QCI9)+
(SAEB_EstabAddSuccNbr_QCI2+SAEB_EstabAddSuccNbr_QCI3+SAEB_EstabAddSuc
cNbr_QCI4+SAEB_EstabAddSuccNbr_QCI6+SAEB_EstabAddSuccNbr_QCI7+SAEB_E
stabAddSuccNbr_QCI8+SAEB_EstabAddSuccNbr_QCI9))/
((SAEB_EstabInitAttNbr_QCI2+SAEB_EstabInitAttNbr_QCI3+SAEB_EstabInitAttNbr_
QCI4+SAEB_EstabInitAttNbr_QCI6+SAEB_EstabInitAttNbr_QCI7+SAEB_EstabInitAtt
Nbr_QCI8+SAEB_EstabInitAttNbr_QCI9)+
(SAEB_EstabAddAttNbr_QCI2+SAEB_EstabAddAttNbr_QCI3+SAEB_EstabAddAttNbr_
QCI4+SAEB_EstabAddAttNbr_QCI6+SAEB_EstabAddAttNbr_QCI7+SAEB_EstabAddA
ttNbr_QCI8+SAEB_EstabAddAttNbr_QCI9))
VS_ERAB_QCI1_initial_setup_req+VS_ERAB_QCI2_initial_setup_req+VS_ERAB_QCI3_
initial_setup_req+VS_ERAB_QCI4_initial_setup_req+VS_ERAB_QCI5_initial_setup_req
+VS_ERAB_QCI6_initial_setup_req+VS_ERAB_QCI7_initial_setup_req+VS_ERAB_QCI
8_initial_setup_req+VS_ERAB_QCI9_initial_setup_req+VS_ERABs_CustomerQCIs_initi
al_setup_req
VS_ERAB_QCI1_initial_setup_succ+VS_ERAB_QCI2_initial_setup_succ+VS_ERAB_QCI
3_initial_setup_succ+VS_ERAB_QCI4_initial_setup_succ+VS_ERAB_QCI5_initial_setu
p_succ+VS_ERAB_QCI6_initial_setup_succ+VS_ERAB_QCI7_initial_setup_succ+VS_
ERAB_QCI8_initial_setup_succ+VS_ERAB_QCI9_initial_setup_succ+VS_ERABs_Custo
merQCIs_initial_setup_succ
((VS_UE_NAS_first_DL+VS_UE_ctxt_setup_req_WithoutDLNAS)/S1SIG_ConnEstabAtt
)
VS_UE_ctxt_setup_req_AfterDLNAS+VS_UE_ctxt_setup_req_WithoutDLNAS
VS_UE_NAS_first_DL+VS_UE_ctxt_setup_req_WithoutDLNAS+
(VS_UE_ctxt_rel_cmd_detach-VS_UE_ctxt_rel_cmd_detach_AfterCtxtEstablished)
VS_ERAB_QCI1_rel_abnormal+VS_ERAB_QCI2_rel_abnormal+VS_ERAB_QCI3_rel_ab
normal+VS_ERAB_QCI4_rel_abnormal+VS_ERAB_QCI5_rel_abnormal+VS_ERAB_QC
I6_rel_abnormal+VS_ERAB_QCI7_rel_abnormal+VS_ERAB_QCI8_rel_abnormal+VS_
ERAB_QCI9_rel_abnormal+VS_ERABs_CustomerQCIs_rel_abnormal
((VS_ERABs_NonGBR_IaLTE_setup_succ)+
(VS_HO_IrC_eNB_succ_tgt+VS_HO_IrC_X2_succ_tgt+VS_HO_IrC_S1_succ_tgt-HO_I
ntraEnbOutSucc_Sum-VS_HO_IrC_X2_succ_src-VS_HO_IrC_S1_succ_src)(VS_ERABs_NonGBR_rel_normal))
(VS_ERABs_NonGBR_rel_normal)/((VS_ERABs_NonGBR_IaLTE_setup_succ)+
ntraEnbOutSucc_Sum-VS_HO_IrC_X2_succ_src-VS_HO_IrC_S1_succ_src))
(HO_IntraEnbOutSucc_Sum+VS_HO_IrC_X2_succ_src+VS_HO_IrC_S1_succ_src)/
(VS_HO_IrC_eNB_req_src+VS_HO_IrC_X2_req_src+VS_HO_IrC_S1_req_src)
(HO_IntraEnbOutAtt_Sum+VS_HO_IrC_X2_succ_prep_src+VS_HO_IrC_S1_succ_prep
_src)/(VS_HO_IrC_eNB_req_src+VS_HO_IrC_X2_req_src+VS_HO_IrC_S1_req_src)
(HO_IntraEnbOutSucc_Sum+VS_HO_IrC_X2_succ_src+VS_HO_IrC_S1_succ_src)/
(HO_IntraEnbOutAtt_Sum+VS_HO_IrC_X2_succ_prep_src+VS_HO_IrC_S1_succ_prep
_src)
((((VS_HO_IrC_eNB_succ_tgt)+(VS_HO_IrC_X2_succ_tgt)+
(VS_HO_IrC_S1_succ_tgt))-((VS_HO_IrF_IrC_S1_IaFDDorIaTDD_succ_tgt)+
(VS_HO_IrF_IrC_X2_IaFDDorIaTDD_succ_tgt)+
(VS_HO_IrF_IrC_eNB_IaFDDorIaTDD_succ_tgt)))+
(((RRC_ConnReEstabSucc_OnTargetCellDuringIntraENodeBHO)(RRC_ConnReEstabSucc_OnTargetCellDuringIntraENodeBInterFreqSameFrameStructur
eHO)))+(((RRC_ConnReEstabSucc_OnTargetCellDuringInterENodeBS1HO)(RRC_ConnReEstabSucc_OnTargetCellDuringInterENodeBInterFreqSameFrameStructur
eS1HO)))+(((RRC_ConnReEstabSucc_OnTargetCellDuringInterENodeBX2HO)(RRC_ConnReEstabSucc_OnTargetCellDuringInterENodeBInterFreqSameFrameStructur
eX2HO))))/(((VS_HO_IrC_eNB_req_tgt)+(VS_HO_IrC_X2_req_tgt)+
(VS_HO_IrC_S1_req_tgt))-((VS_HO_IrF_IrC_S1_IaFDDorIaTDD_req_tgt)+
(VS_HO_IrF_IrC_X2_IaFDDorIaTDD_req_tgt)+
(VS_HO_IrF_IrC_eNB_IaFDDorIaTDD_req_tgt)))
(VS_cell_thpt_DL_cum/VS_cell_thpt_DL_NbEvt)*(1024/1000)
VS_cell_thpt_DL_Hi/VS_cell_thpt_DL_all_distribution
VS_noise_PRB_all_UL_Hi_OD+VS_noise_PRB_all_UL_HiMed_OD+VS_noise_PRB_all_U
L_HiLo_OD
VS_noise_PRB_all_UL_LoMed_OD+VS_noise_PRB_all_UL_Lo_OD
VS_noise_PRB_all_UL_Hi_HiMed_HiLo_OD/VS_noise_PRB_all_UL_OD
(VS_noise_PRB_all_UL_LoMed_OD+VS_noise_PRB_all_UL_Lo_OD)/VS_noise_PRB_all_
UL_OD
(_VS_RRC_cnx_SuccRate_wtrep_BH)*(_Initial_ERAB_SSR_ATT_BH)*(_VS_S1_cnx_esta
b_succ_rate_BH)
_VS_RRC_succ_BH/_VS_RRC_cnx_WithoutRepet_req_BH
VS_RRC_cnx_WithoutRepetition_req
_Initial_ERAB_Setup_Suc_BH/_Initi_ERAB_Setup_Req_BH
((SAEB_EstabInitSuccNbr_QCI2+SAEB_EstabInitSuccNbr_QCI3+SAEB_EstabInitSucc
Nbr_QCI4+SAEB_EstabInitSuccNbr_QCI6+SAEB_EstabInitSuccNbr_QCI7+SAEB_Est
abInitSuccNbr_QCI8+SAEB_EstabInitSuccNbr_QCI9)+
(SAEB_EstabAddSuccNbr_QCI2+SAEB_EstabAddSuccNbr_QCI3+SAEB_EstabAddSuc
cNbr_QCI4+SAEB_EstabAddSuccNbr_QCI6+SAEB_EstabAddSuccNbr_QCI7+SAEB_E
stabAddSuccNbr_QCI8+SAEB_EstabAddSuccNbr_QCI9))
((SAEB_EstabInitAttNbr_QCI2+SAEB_EstabInitAttNbr_QCI3+SAEB_EstabInitAttNbr_
QCI4+SAEB_EstabInitAttNbr_QCI6+SAEB_EstabInitAttNbr_QCI7+SAEB_EstabInitAtt
Nbr_QCI8+SAEB_EstabInitAttNbr_QCI9)+
(SAEB_EstabAddAttNbr_QCI2+SAEB_EstabAddAttNbr_QCI3+SAEB_EstabAddAttNbr_
QCI4+SAEB_EstabAddAttNbr_QCI6+SAEB_EstabAddAttNbr_QCI7+SAEB_EstabAddA
ttNbr_QCI8+SAEB_EstabAddAttNbr_QCI9))
_VS_S1AP_cnx_estab_suc_BH/_VS_S1AP_cnx_est_req_BH
VS_UE_NAS_first_DL+VS_UE_ctxt_setup_req_WithoutDLNAS
S1SIG_ConnEstabAtt
_VS_ERABs_NonGBR_rel_norm_BH/_VS_ERABs_NonGBR_rel_Denom_BH
VS_ERAB_QCI5_rel_normal+VS_ERAB_QCI6_rel_normal+VS_ERAB_QCI7_rel_normal
+VS_ERAB_QCI8_rel_normal+VS_ERAB_QCI9_rel_normal
((VS_ERABs_NonGBR_IaLTE_setup_succ)+
ntraEnbOutSucc_Sum-VS_HO_IrC_X2_succ_src-VS_HO_IrC_S1_succ_src))
_Intra_Freq_tgt_HO_Suc_BH1/_Intra_Freq_tgt_HO_Req_BH
(VS_HO_IaF_IrC_IaLTE_succ_tgt+_RRC_reestab_succHO_IaF_IrC+_RRC_reestab_succ
HO_IaF_S1+_RRC_reestab_succHO_IaF_X2)
VS_HO_IrC_IaLTE_req_tgt-VS_HO_IrF_IrC_IaLTE_IaFDDorIaTDD_req_tgt
(VS_redirect_all_UtraFdd+VS_redirect_all_GERAN-VS_redirect_UtraFdd_basic_ForCS
FB_all)/
(VS_UE_ctxt_setup_succ_WithoutDLNAS+VS_UE_ctxt_setup_succ_AfterDLNAS)
VS_UE_MIMO_DL_eligible_yes/
(VS_UE_MIMO_DL_eligible_no+VS_UE_MIMO_DL_eligible_yes)
(VS_redirect_all_UtraFdd+VS_redirect_all_GERAN-VS_redirect_UtraFdd_basic_ForCS
FB_all)/
(VS_HO_IrF_IrC_eNB_IaFDDorIaTDD_succ_tgt+RRC_ConnReEstabSucc_OnTargetCellD
uringIntraENodeBInterFreqSameFrameStructureHO+VS_HO_IrF_IrC_S1_IaFDDorIaTDD
_succ_tgt+RRC_ConnReEstabSucc_OnTargetCellDuringInterENodeBInterFreqSameFra
meStructureS1HO+VS_HO_IrF_IrC_X2_IaFDDorIaTDD_succ_tgt+RRC_ConnReEstabS
ucc_OnTargetCellDuringInterENodeBInterFreqSameFrameStructureX2HO)/
(VS_HO_IrF_IrC_eNB_IaFDDorIaTDD_req_tgt+VS_HO_IrF_IrC_S1_IaFDDorIaTDD_req_t
gt+VS_HO_IrF_IrC_X2_IaFDDorIaTDD_req_tgt)
VS_HO_IrF_IrC_X2_IaFDDorIaTDD_req_src-VS_HO_IrF_IrC_X2_IaFDDorIaTDD_succ_src
VS_HO_IrF_IrC_X2_IaFDDorIaTDD_fail_src-VS_HO_IrF_IrC_X2_IaFDDorIaTDD_abort_su
m_src
VS_HO_IrF_IrC_X2_IaFDDorIaTDD_succ_prep_src-VS_HO_IrF_IrC_X2_IaFDDorIaTDD_su
cc_src
VS_HO_IrF_IrC_X2_IaFDDorIaTDD_req_tgt-VS_HO_IrF_IrC_X2_IaFDDorIaTDD_succ_tgt
VS_HO_IrF_IrC_X2_IaFDDorIaTDD_fail_tgt-VS_HO_IrF_IrC_X2_IaFDDorIaTDD_abort_su
m_tgt
(VS_redirect_all_UtraFdd+VS_redirect_all_GERAN)/
VS_HO_LTE_to_UTRAN_PS_all_succ_src_rate
VS_HO_LTE_to_UTRAN_PS_all_req_src

KPI Description

Uploaded by

Copyright:

Available Formats

KPI Description

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

KPI Description

Uploaded by

Copyright:

Available Formats

NAME

Failure due to overload condition. Based on 3GPP counter: RRC.ConnEstabFail.OverloadCon

This indicator provides the average number of UE in or transitioning into RRC_Connected s

This indicator is providing the number of S1 dedicated connection establishment failures f

This indicator provides the number of UE Context Setup request

This indicator provides the high+high_med+high_low distribution of Uplink Noise measure

This indicator provides the low+med_low distribution of Uplink Noise measured.

This indicator provides the number of S1 dedicated connection establishment attempt. Th

This indicator provides the number of times an outgoing inter-frequency inter-eNodeB X2

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.