name: BFD
full_form: Beam Failure Detection
context: When RRC (TS 38.331 [3]) configures a PC5 QoS flow to SL-DRB mapping rule for a PC5 QoS flow, the SDAP entity shall: - for unicast of NR sidelink communication, if the SDAP entity has already been established and there is no stored SL-DRB mapping rule for the PC5 QoS flow and a default SL-DRB is configured: - construct an end-marker control PDU, as specified in the clause 6.2.3, for the PC5 QoS flow; - map the end-marker control PDU to the default SL-DRB; - submit the end-marker control PDU to the lower layers; - for unicast of NR sidelink communication, if the stored PC5 QoS flow to SL-DRB mapping rule is different from the configured PC5 QoS flow to SL-DRB mapping rule for the PC5 QoS flow and the SL-DRB according to the stored PC5 QoS flow to SL-DRB mapping rule is configured by RRC (TS 38.331 [3]) with the presence of SL SDAP header: - construct an end-marker control PDU, as specified in the clause 6.2.3, for the PC5 QoS flow; - map the end-marker control PDU to the SL-DRB
description: Beam Failure Detection (BFD) is a procedure in the 5G New Radio (NR) system that allows the network to detect and respond to beam failures, which can occur when the UE's serving cell or secondary cell(s) experience poor radio conditions. The BFD relaxation procedure enables the network to configure the UE to perform beam failure detection on the Secondary Cell Group (SCG) while it is deactivated, allowing for more efficient use of radio resources.
explanation: The context describes a specific procedure in the NR system related to beam failure detection and relaxation. It outlines how the network can configure the UE to perform BFD on the SCG while it is deactivated, which indicates that BFD is a procedural step taken by the network to manage radio resources.
section_title: 7.14	RLM/BFD relaxation
biotag_Context: O,B-Protocol,O,O,O,O,O,O,B-Measurement,O,O,B-Connection,O,O,O,O,O,B-Measurement,O,O,B-Protocol,O,O,O,O,O,O,B-Network,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,B-Measurement,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,B-Measurement,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Measurement,O,O,B-Connection,O,O,O,O,O,B-Measurement,O,O,O,B-Connection,O,O,O,O,O,B-Measurement,O,O,B-Connection,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Technology,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,B-Connection,O,O,B-Connection
biotag_Description: B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,B-Technology,B-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,B-Procedure,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O