name: RLM
full_form: Radio Link Monitoring
context: Similar procedures as defined under clause 10.1.2.8 (Dual Connectivity operation) in TS 36.300 [2] apply for MR-DC. Similar CHO principles as defined in TS 36.300 [2] and TS 38.300 [3] apply for the Conditional PSCell Change and Conditional PSCell Addition in MR-DC. Similar LTM principles as defined in TS 38.300 [3] apply for MCG LTM and SCG LTM in NR-DC. MCG LTM with SCG release and MCG LTM without SCG change are supported. LTM for simultaneous PCell and PSCell change is not supported. Conditional PSCell Change and conditional PSCell addition are not supported for the MR-DC options NE-DC and NGEN-DC. Subsequent CPAC is only supported for NR-DC. Configuration of a deactivated SCG in a conditional configuration, configuration of CPC (or subsequent CPAC) while the SCG is deactivated and SCG deactivation while CPC (or subsequent CPAC) is configured are not supported. In MR-DC, CHO is supported in Master Node to eNB/gNB Change procedure and Conditional Handover with Secondary Node
description: Radio Link Monitoring (RLM) is a procedure used in the context of handovers to monitor and report on the radio link quality. It involves collecting various types of information such as RLM related timers, measurements of reference signals, RLC retransmission counter, beam failure detection related information, and handover related information. This information is then included in a successful handover report which may be forwarded from the target NG-RAN node to the source NR-RAN node.
explanation: RLM is classified as a procedure because it involves a series of steps or operations (e.g., collecting measurements, reporting) that are performed during a specific event (i.e., successful handover). The context highlights the various types of information collected and reported during RLM, indicating its procedural nature.
section_title: 5.3.2.5	Successful HO Report
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Specification,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,B-Procedure,O,O,O,O,B-Specification,O,O,O,O,B-Network,B-Procedure,O,B-Network Function,B-Procedure,O,O,B-Network,B-Procedure,O,B-Network Function,O,O,B-Network,B-Procedure,O,B-Network Function,O,O,O,B-Procedure,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,B-Technology,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Technology,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,B-Procedure,I-Procedure,O,B-Network Function,I-Network Function
biotag_Description: B-Procedure,I-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,B-Procedure,O,O,O,O,O,O,B-Protocol,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-Network Function,O,O,O,O,O,O