Section: 4.2.2.6 Number of released active E-RABs
Content: a) This measurement provides the number of released E-RABs that were active at the time of release. E-RABs with bursty flow are seen as being active when there is user data in the queue in any of the directions. E-RABs with continuous flow are always seen as active E-RABs in the context of this measurement. The measurement is split into subcounters per E-RAB QoS level (QCI). b) CC c) On transmission by the eNodeB/RN of an E-RAB RELEASE INDICATION message; or on transmission by the eNB/RN of an E-RAB RELEASE RESPONSE message for the E-RAB release initiated by the MME/DeNB with the exception of corresponding E-RAB RELEASE COMMAND message with “Cause” equal to “Normal Release” or on transmission by the eNodeB/RN of UE CONTEXT RELEASE COMPLETE for the UE context release initiated by the eNB/RN with the exception of the corresponding UE CONTEXT RELEASE REQUEST message with cause “User inactivity”, “CSG Subscription Expiry”, or any “cause” indicating a successful CS fallback (e.g., cause “CS Fallback triggered”, “UE Not Available for PS Service”, or “Redirection towards 1xRTT”) or a succesful mobility activity (e.g., cause “Inter-RAT Redirection”); or on transmission by the eNodeB/RN of UE CONTEXT RELEASE COMPLETE message for the UE context release initiated by the MME/DeNB with the exception of the corresponding UE CONTEXT RELEASE COMMAND message with "Cause" equal to “Normal Release” ", “detach”, “Handover Cancelled” or any “cause” indicating a successful CS fallback (e.g., cause “Redirection towards 1xRTT”) or a succesful mobility activity (e.g., cause “Successful Handover”, “Inter-RAT Redirection” or “S1 Intra system Handover triggered”) or on receipt by the eNB of a PATH SWITCH REQUEST ACKNOWLEDGE or PATH SWITCH REQUEST FAILED message by which some or all E-RABs in the corresponding PATH SWITCH REQUEST need to be released , or on transmission of a RESET ACKNOWLEDGE message to MME/DeNB; or on receipt of a RESET ACKNOWLEDGE message from MME/DeNB, if any of the UL or DL are considered active according to the definition used for "Number of active UEs" in TS 36.314[ Evolved Universal Terrestrial Radio Access  (E-UTRA); Layer 2 - Measurements ] . E-RABs with bursty flow are considered active when there is still data in the DL or UL buffer. E-RABs with continuous flow are always seen as active E-RABs in the context of this measurement.Each corresponding E-RAB to release is added to the relevant measurement per QCI. The possible QCIs are described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ]  [9]. The sum of all supported per QCI measurements shall equal the total number of E-RABs attempted to release when the E-RAB is active according to the definition of bursty flow/continuous flow. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. How to define for a particular QCI if the E-RAB is of type bursty flow or continuous flow is outside the scope of this document. d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB.RelActNbr.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) This measurement is to support the Retainability KPI “E-RAB Retainability” defined in [13].