Tuesday, March 3, 2015

eRAN Performance KPI Overview (Mobility KPIs)






Mobility KPIs

Intra/Inter-frequency Handover Out Success Rate 
 
 Note: In HW eNodeB, all the handover attempt statistic is calculated after admission control in target cell, which means HO failure statistic exclude admission failure

  •  This KPI can be used to evaluate the intra/inter-frequency Handover out success rate in a cell or a cluster. The intra-frequency handover (HO) includes both inter-eNodeB and intra-eNodeB.
  • The intra/inter-frequency handover (HO) includes both inter-eNodeB and intra-eNodeB scenarios.

Associated Counters (Intra eNB)
 

 
Note: In HW eNodeB, all the handover attempt statistic is calculated after admission determination in target cell,
 
During a handover where the source cell and target cell are controlled by the same eNodeB, as shown in point B, the corresponding counter is incremented by 1 each time the eNodeB sends an RRC Connection Reconfiguration message to the UE. The counters are measured as follows:
  • If the source cell and target cell work at the same frequency, the L.HHO.IntraeNB.IntraFreq.ExecAttOut counter is incremented by 1.
  • If the source cell and target cell work at different frequencies, the L.HHO.IntraeNB.InterFreq.ExecAttOut counter is incremented by 1.
As shown in point C , the corresponding counter is incremented each time the eNodeB receives an RRC Connection Reconfiguration Complete message from the UE and the subsequent operations are successful. The counters are measured as follows:
  • If the source cell and target cell are at the same frequency, the L.HHO.IntraeNB.IntraFreq.ExecSuccOut counter is incremented by 1.
  • If the source cell and target cell are at different frequencies, the L.HHO.IntraeNB.InterFreq.ExecSuccOut counter is incremented by 1.

Associated Counters (Inter eNB) X2 Based Handover



During such a handover where the source cell and target cell are controlled by different eNodeBs, as shown in point B in the figure above, the corresponding counter is incremented each time the source eNodeB sends an RRC Connection Reconfiguration message to the UE after receiving a HANDOVER REQUEST ACKNOWLEDGE from the target eNodeB or receiving a HANDOVER COMMAND message from the MME. The counters are measured as follows:
  • If the source cell and target cell work at the same frequency, the L.HHO.IntereNB.IntraFreq.ExecAttOut counter is incremented by 1.
  • If the source cell and target cell work at different frequencies, the L.HHO.IntereNB.InterFreq.ExecAttOut counter is incremented by 1.
As shown in point C , the corresponding counter is incremented each time the source eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB or a UE CONTEXT RELEASE COMMAND message from the MME. The counters are measured as follows:
  • If the source cell and target cell are at the same frequency, the L.HHO.IntereNB.IntraFreq.ExecSuccOut counter is incremented by 1.
  • If the source cell and target cell are at different frequencies, the L.HHO.IntereNB.InterFreq.ExecSuccOut counter is incremented by 1.

 Associated Counters (Inter eNB) S1 based Handover
 
 
During such a handover where the source cell and target cell are controlled by different eNodeBs, as shown in point B in the figure above, the corresponding counter is incremented each time the source eNodeB sends an RRC Connection Reconfiguration message to the UE after receiving a HANDOVER REQUEST ACKNOWLEDGE from the target eNodeB or receiving a HANDOVER COMMAND message from the MME. The counters are measured as follows:
  • If the source cell and target cell work at the same frequency, the L.HHO.IntereNB.IntraFreq.ExecAttOut counter is incremented by 1.
  • If the source cell and target cell work at different frequencies, the L.HHO.IntereNB.InterFreq.ExecAttOut counter is incremented by 1.
As shown in point C , the corresponding counter is incremented each time the source eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB or a UE CONTEXT RELEASE COMMAND message from the MME. The counters are measured as follows:
  • If the source cell and target cell are at the same frequency, the L.HHO.IntereNB.IntraFreq.ExecSuccOut counter is incremented by 1.
  • If the source cell and target cell are at different frequencies, the L.HHO.IntereNB.InterFreq.ExecSuccOut counter is incremented by 1.
 Handover In Success Rate
 
  •  This KPI can be used to evaluate the handover in success rate in a cell or a cluster. 
  • The HO includes both inter-eNodeB and intra-eNodeB scenarios.

Associated Counters (Intra eNB)


Number of Intra-eNB incoming handover attempts
During a handover where the source cell and target cell are controlled by the same eNodeB, as shown in point B, the counter is incremented by 1 in the target cell each time the eNodeB sends an RRC Connection Reconfiguration message to the UE.
Number of successful intra-eNB incoming handovers
As shown in point C , the counter is incremented by 1 in the target cell each time the eNodeB receives an RRC Connection Reconfiguration Complete message from the UE and the subsequent operations are successful

Related Counters (Inter eNB)X2 Handover


Number of Inter-eNB incoming handover attempts
The source cell and target cell of a handover are controlled by different eNodeBs. As shown in point B, the counter is incremented by 1 in the target cell each time the target eNodeB sends a HANDOVER REQUEST ACKNOWLEDGE message to the source eNodeB over the X2 interface or to the MME over the S1 interface.
Number of successful Inter-eNB incoming handovers
As shown in point C , the counter is incremented by 1 in the target cell each time the target eNodeB sends a UE CONTEXT RELEASE to the source eNodeB over the X2 interface after receiving a PATH SWITCH ACK message from the MME or the target eNodeB sends a HANDOVER NOTIFY message to the MME over the S1 interface.

Related Counters (Inter eNB) S1 Handover


Number of Inter-eNB incoming handover attempts
The source cell and target cell of a handover are controlled by different eNodeBs. As shown in point B, the counter is incremented by 1 in the target cell each time the target eNodeB sends a HANDOVER REQUEST ACKNOWLEDGE message to the source eNodeB over the X2 interface or to the MME over the S1 interface.
Number of successful Inter-eNB incoming handovers
As shown in point C , the counter is incremented by 1 in the target cell each time the target eNodeB sends a UE CONTEXT RELEASE to the source eNodeB over the X2 interface after receiving a PATH SWITCH ACK message from the MME or the target eNodeB sends a HANDOVER NOTIFY message to the MME over the S1 interface.

Inter_RAT Handover Out Success Rate (LTE to WCDMA)


This KPI can be used to evaluate the inter-RAT handover out success rate in a cell or a cluster. As suggested by the name, this KPI measures the performance of the inter-RAT handover from LTE to WCDMA.


Associated Counters


Number of Performed Outgoing Handovers from E-UTRAN to UTRAN
As shown in point B, the counter is incremented by 1 each time the eNodeB sends a Mobility from EUTRA Command message to the UE during a handover from E-UTRAN to UTRAN. Number of Successful Outgoing Handovers from E-UTRAN to UTRAN
Number of Successful Outgoing Handovers from E-UTRAN to UTRAN
As shown in point C, the counter is incremented by 1 each time the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME after the UE is handed over from E-UTRAN to UTRAN.

Inter_RAT Handover Out Success Rate (LTE to GSM)


This KPI can be used to evaluate the inter-RAT handover out success rate in a cell or a cluster. As suggested by the name, this KPI measures the performance of the inter-RAT handover from LTE to GSM.

Associated Counters


Number of Performed Outgoing Handovers from E-UTRAN to GERAN
As shown in point B, the counter is incremented by 1 each time the eNodeB sends a Mobility from EUTRA Command message to the UE during a handover from E-UTRAN to UTRAN. Number of Successful Outgoing Handovers from E-UTRAN to GERAN
Number of Successful Outgoing Handovers from E-UTRAN to GERAN
As shown in point C, the counter is incremented by 1 each time the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME after the UE is handed over from E-UTRAN to GERAN









No comments:

Post a Comment