name: BFR
full_form: Beam Failure Report
context: The MAC CEs for BFR consists of either: - BFR MAC CE; or - Truncated BFR MAC CE. The BFR MAC CE and Truncated BFR MAC CE are identified by a MAC subheader with LCID/eLCID as specified in Table 6.2.1-2 and Table 6.2.1-2b. The BFR MAC CE and Truncated BFR MAC CE have a variable size. They include a bitmap and in ascending order based on the ServCellIndex, beam failure recovery information i.e. octets containing candidate beam availability indication (AC) for SCells indicated in the bitmap. For BFR MAC CE, a single octet bitmap is used when the highest ServCellIndex of this MAC entity's SCell for which beam failure is detected and the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed is less than 8, otherwise four octets are used. A MAC PDU shall contain at most one BFR MAC CE. For Truncated BFR MAC CE, a single octet bitmap is used for the following cases, otherwise four octets are used: - the highest ServCellIndex of this
description: The Beam Failure Report (BFR) is a type of message exchanged between network components in the context of beam failure recovery. It contains information about candidate beam availability for secondary cells indicated in a bitmap.
explanation: Based on the provided context from 3GPP TS 38.321, BFR is classified as a Message because it refers to a specific type of signaling data exchanged between network components, containing beam failure recovery information.
section_title: 6.1.3.23BFR MAC CEs
biotag_Context: O,B-Protocol,O,O,B-Message,O,O,O,O,B-Message,B-Protocol,O,O,O,O,B-Message,B-Protocol,O,O,B-Message,B-Protocol,B-Message,O,O,B-Message,B-Protocol,B-Message,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,B-Protocol,B-Message,O,O,B-Message,B-Protocol,B-Message,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-Message,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Connection,O,O,O,O,O,B-Message,B-Protocol,O,O,O,B-Message,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Message,I-Message,I-Message,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