name: RLF
full_form: Radio Link Failure
context: In this case, there are two bursts, one is MBSFN Traffic burst (MT burst) for 7 normal timeslots, and the other is MBSFN Special burst (MS burst) for 1 short timeslot. Both of them consist of a preamble and a data symbol field, the lengths of which are different for the individual bursts. Thus, the number of data symbols in a burst depends on the SF and the burst type, as depicted in table 8A.a. Table 8A.a: number of symbols per data field in a MBSFN burst Note: MS burst only supports SF=16. The support of both bursts is mandatory and only used in dedicated carrier MBSFN. The both different bursts defined here are well suited for this application, as described in the following paragraphs. The MT burst can be used for the regular timeslots, the duration of which is 0.675ms. The data fields of the MT burst are 768 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 8A.a above. The preamble of MT burst has a length of 96 chips. The MT
description: Radio Link Failure (RLF) is an event that occurs when the radio link between the User Equipment (UE) and the eNodeB (eNB) fails, triggering a report to be sent to the network. This event is crucial for the network to take corrective actions, such as adjusting the handover parameters or re-establishing the connection.
explanation: RLF is classified as an Event because it describes a specific occurrence within the telecommunications system that has a defined impact. The text highlights that RLF triggers a report and leads to network actions, indicating its role as a significant event requiring response.
section_title: 4.3.1	Taking the outcome of the RRC re-establishment into account for MRO
biotag_Context: O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,B-Parameter,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,O,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,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,B-Procedure,O,O,O,O,O,O,O,O,B-Procedure
biotag_Description: B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,B-Network Function,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,O,O,O,O,O,O,O