name: TDD:
full_form: A duplex method whereby uplink and downlink transmissions are carried over same radio frequency by using synchronised time intervals. In the TDD, time slots in a physical channel are divided into transmission and reception part. Information on uplink and downlink are transmitted reciprocally.
context: (triggered by the RLF report). 2. Network based solution 2: a. A comparison between the cell the UE was connected at the moment the RLF report was retrieved and the re-establishment cell indicated in the RLF report is carried out. If these cells are matched, the re-establishment cell should be considered for MRO adjustments at the eNB where the failure has occurred. The comparison is performed at the eNB retrieving the RLF report and a new IE is added to the RLF indication to identify the matched and unmatched cases. b. A similar comparison to the one done in Network Solution 2a is carried out. The comparison is performed by the eNB where the RLF has occurred (the one receiving the RLF Indication) and no additional IE is needed. Instead the existing IE called Re-establishment cell ECGI in the RLF Indication can be used to signal the cell where the RLF report has been retrieved i.e. a cell where a successful RRC re-establishment/handover has occurred. 3. Network based solution 3: The
description: Time Division Duplexing (TDD) is a duplex method used in telecommunications where uplink and downlink transmissions are carried over the same radio frequency by using synchronized time intervals. In TDD, time slots in a physical channel are divided into transmission and reception parts, allowing for reciprocal transmission of information on uplink and downlink.
explanation: TDD is classified as a Technology because it describes a specific method used to transmit data over a shared radio frequency. This involves the precise allocation of time slots for both uplink and downlink communication, which are fundamental aspects of telecommunications technology.
section_title: 6.2	Downlink models
biotag_Context: O,O,O,B-Procedure,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Procedure,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,B-Procedure,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,O,O,B-Message,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Message,O,O,O,O,O,B-Message,O,O,O,B-Parameter,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Network,O,O,O,O
biotag_Description: B-Technology,I-Technology,I-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,O,O,O,O,O,O,O,O