name: CHO
full_form: Conditional Handover
context: The potential gains of mitigating the CQI mismatch can be obtained by comparing the performance of the following two cases. - ICS performance with CQI mismatch: the legacy ICS UE is considered, which does the CQI evaluation and filering normally regardless the interferer structures. When the serving NodeB schedules the ICS UE, the reported CQI is used. - ICS performance with CQI mismatch mitigation: When the serving Node B choose the TB size for the ICS UE, the scheduled CQI is obtained by compensating the CQI mismatch caused by the interferer structure difference. Regarding the normal ICS performance with CQI Mismatch, the CQI measurement and the TBS selection/scheduling are the same as the normal operation in legacy system. If the interferer structure used in the moment CQI measured is different from the interferer structure used in the moment CQI used, there exists CQI Mismatch between the current interferer structure and the used CQI values. Regarding the ICS performance with CQI
description: Conditional Handover (CHO) is a procedure in mobile networks that allows for the handover of a user equipment's (UE) connection from one cell to another based on specific conditions. It involves the UE selecting a target cell for connection re-establishment and executing the CHO procedure towards that cell upon fulfilling the configured condition. The CHO procedure is used to handle scenarios where the UE experiences a Handover (HO) failure, such as when it fails to re-establish a connection with the selected candidate cell.
explanation: The context describes a specific set of actions (selecting a target cell, executing the CHO procedure) performed by the UE in response to handover failures. This sequence of actions defines a defined process, classifying it as a Procedure.
section_title: 5.4.1.2	Radio Link Failure report
biotag_Context: O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,B-Parameter,O,O,O,B-Specification,B-Device,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Specification,O,O,O,B-Parameter,O,O,O,B-Specification,O,O,B-Parameter,O,O,O,O,O,B-Network Function,I-Network Function,O,O,B-Parameter,O,O,O,B-Specification,O,O,O,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,B-Parameter,O,O,B-Parameter,O,O,O,B-Technology,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,B-Parameter,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Specification,O,O,B-Parameter
biotag_Description: B-Procedure,I-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,O,O,O,O,O,B-Device,O,O,O,O,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,B-Device,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O