Related Features
MME.QCI.9
1.1.6.6 Number of Abnormal E-RAB Releases for Different Causes in a Cell
Counters
Counter ID Counter Name Counter
Description Network Element
1526728282
L.E-RAB.AbnormRel.Ra dio
Number of abnormal releases of activated E-RABs because of faults at the radio network layer
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE, BTS3900
1526728283
L.E-RAB.AbnormRel.T NL
Number of abnormal releases of activated E-RABs because of faults at the transport network layer
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE, BTS3900
1526728284
L.E-RAB.AbnormRel.C ong
Number of abnormal releases of activated E-RABs because of network congestion
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE, BTS3900
1526728291
L.E-RAB.AbnormRel.H OFailure
Number of abnormal releases of activated E-RABs because of handover failures
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE, BTS3900
Counter ID Counter Name Counter
Description Network Element
1526728292
L.E-RAB.AbnormRel.M ME
Number of abnormal releases of activated E-RABs due to faults on the MME side
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE, BTS3900
1526728940
L.E-RAB.AbnormRel.M METot
Total number of abnormal E-RAB releases due to faults on the MME side
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE, BTS3900
Description
The counters measure the number of abnormal E-RAB releases based on the release cause in a cell. An E-RAB is the access layer bearer for carrying service data of a UE. The E-RAB release is a process of releasing the access layer bearer resources of UEs.
Measurement Points
As shown at point A in Figure 1-54, in an E-RAB release procedure initiated by the MME, the L.RAB.AbnormRel.MMETot counter is incremented each time the eNodeB receives an E-RAB RELEASE COMMAND message from the MME and the release cause is not "Normal Release", "Detach, User Inactivity", "CS Fallback triggered", "UE Not Available for PS Service", "Inter-RAT Redirection", or "Successful Handover". In addition, the
L.E-RAB.AbnormRel.MME counter is incremented each time the preceding condition is met and the corresponding bearer carries data. If the E-RAB RELEASE COMMAND message requests to release multiple E-RABs at the same time, the RAB.AbnormRel.MMETot and L.E-RAB.AbnormRel.MME counters are incremented by the number of requested E-RAB releases in the message.
As shown at point A in Figure 1-55, in a UE context release procedure initiated by the MME, all E-RABs of the UE are released when the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME. In this case, the L.E-RAB.AbnormRel.MMETot counter is incremented by the number of requested E-RAB releases in the message each time the release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered", "UE Not Available for PS Service", "Inter-RAT Redirection", or "Successful Handover". In addition, the L.E-RAB.AbnormRel.MME counter is incremented each time the preceding condition is met and the corresponding bearer carries data.
As shown at point A in Figure 1-56, when the eNodeB sends an E-RAB RELEASE INDICATION message to the MME, the counters are measured as follows:
(1) The L.E-RAB.AbnormRel.Radio counter is incremented each time the E-RAB is abnormally released due to faults at the radio network layer and the eNodeB determines that the E-RAB to
(2) The L.E-RAB.AbnormRel.TNL counter is incremented each time the E-RAB is abnormally released due to faults at the transport network layer and the eNodeB determines that the E-RAB to be released carries data.
(3) The L.E-RAB.AbnormRel.Cong counter is incremented each time the E-RAB is abnormally released due to network congestion and the eNodeB determines that the E-RAB to be released carries data.
For details about faults at the radio network layer and the transport network layer as well as network congestion faults, see 3GPP TS 36.413. In addition, if the E-RAB RELEASE
INDICATION message requests to release multiple E-RABs at the same time, the corresponding counter is incremented by the number of requested E-RAB releases based on the release cause.
As shown at point A in Figure 1-57, when the eNodeB sends a UE CONTEXT RELEASE REQUEST message to the MME, all E-RABs of the UE are released. The counters are measured as follows:
(1) The L.E-RAB.AbnormRel.Radio counter is incremented each time the E-RABs are abnormally released due to faults at the radio network layer and the eNodeB determines that the E-RABs to be released carry data.
(2) The L.E-RAB.AbnormRel.TNL counter is incremented each time the E-RABs are
abnormally released due to faults at the transport network layer and the eNodeB determines that the E-RABs to be released carry data.
(3) The L.E-RAB.AbnormRel.Cong counter is incremented each time the E-RABs are
abnormally released due to network congestion (including preemption and resource insufficient) and the eNodeB determines that the E-RABs to be released carry data.
For details about faults at the radio network layer and the transport network layer as well as network congestion faults, see 3GPP TS 36.413.
(4) The L.E-RAB.AbnormRel.HOFailure counter is incremented each time the E-RABs are abnormally released due to handover failures and the eNodeB determines that the E-RABs to be released carry data.
The corresponding counters are incremented by the number of requested E-RAB releases based on the release cause. When the MME sends a UE CONTEXT RELEASE COMMAND message to the eNodeB, the corresponding counter is not incremented.
Figure 1-54
Figure 1-55
Figure 1-56
Figure 1-57
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
L.E-RAB.AbnormRel.Radio Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Radio Bearer Management
Counter Name Feature ID Feature Name L.E-RAB.AbnormRel.TNL Multi-mode: None
GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Radio Bearer Management L.E-RAB.AbnormRel.Cong Multi-mode: None
GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008 LBFD-002024 TDLBFD-002024 LOFD-00102901 TDLOFD-00102901
Radio Bearer Management Radio Bearer Management Congestion Control Congestion Control
Radio/transport resource pre-emption
Radio/transport resource pre-emption
L.E-RAB.AbnormRel.HO-Failure
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Radio Bearer Management L.E-RAB.AbnormRel.MME Multi-mode: None
GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Radio Bearer Management
L.E-RAB.AbnormRel.MMETot
Multi-mode: None GSM: None UMTS: None LTE: LBFD-002008 TDLBFD-002008
Radio Bearer Management Radio Bearer Management
Counters
Counter ID Counter Name Counter
Description Network Element
1526728436
L.E-RAB.Release.Unsyn
Number of released E-RABs of UEs in the uplink out-of-synchronization state
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE, BTS3900
Description
The counter measures the number of released E-RABs of UEs in the uplink out-of-synchronization state in a cell.
Measurement Points
As shown at point A in Figure 1-58, Figure 1-59, Figure 1-60, or Figure 1-61, when the UE is in the uplink out-of-synchronization state, the L.E-RAB.Release.Unsyn counter is
incremented by 1 in any of the following scenarios:
- The eNodeB sends an E-RAB RELEASE INDICATION message to the MME.
- The eNodeB receives an E-RAB RELEASE COMMAND message from the MME without sending the corresponding E-RAB RELEASE INDICATION message to the MME.
- The eNodeB sends a UE CONTEXT RELEASE REQUEST message to the MME.
- The eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME without sending the corresponding UE CONTEXT RELEASE REQUEST message to the MME.
In each scenario, if the message requests to release multiple E-RABs, the corresponding counter is incremented by the number of requested E-RAB releases in the message.