name: RCEF
full_form: RRC Connection Establisment Failure
context: RCEF reporting is activated to the eNB as a special Trace Session where the Job Type indicates RCEF reporting only. The detailed procedure is shown in figure 4.8.1.1 where a UE experiences an RCEF event and the RRC establishment is successful to the same eNB. Figure 4.8.1.1 Example scenario for RCEF reporting when UE RRC establishment is successful to the same eNB. When the eNB receives the Trace Session activation indicating RCEF reporting only, the eNB shall start a Trace Session. This Trace Session shall collect only RCEF reports received from the UE. The Trace Session activation message received from the shall contain the following information: - Trace Reference - Job Type = RCEF reporting only - TCE IP Address Figure 4.8.1.2 shows another example where the UE RRC Establishment is failed to one eNB, but successful to another eNB. Figure 4.8.1.2 Example scenario for RCEF reporting when the UE RRC establishment is successful to a different eNB If the UE establishes the RRC connection
description: RRC Connection Establishment Failure (RCEF) is a procedure in E-UTRAN that involves the activation of a special Trace Session for reporting RCEF events. This procedure includes the eNB receiving a Trace Session activation message indicating RCEF reporting only, starting a Trace Session to collect RCEF reports from the UE, and collecting specific information such as Trace Reference, Job Type, and TCE IP Address.
explanation: The context describes a specific sequence of network operations involving RRC connection establishment failure, Trace Session activation, and report collection. This matches the definition of a Procedure in the predefined categories.
section_title: 4.8.1Trace session activation for RCEF reporting in E-UTRAN
biotag_Context: B-Procedure,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Procedure,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,B-Device,B-Protocol,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Procedure,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Network Function,B-Protocol,O,O,O,O,O,O,O,O,B-Device,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Device,B-Protocol,O,O,O,O,O,O,B-Network Function,O,O,B-Device,O,O,B-Protocol,O
biotag_Description: B-Protocol,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,B-Protocol,O