Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Radio Access Network

BFR

Beam Failure Recovery

Radio Access Network →

BFR is a 5G NR mechanism where a UE detects its serving beam has failed and rapidly re-establishes a reliable connection using a new beam, ensuring continuous mobility and high data rates.

Introduced
Rel-15
Where
Radio Access Network › NG-RAN (5G)
Specifications
3 specs
BFR Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

Beam Failure Recovery (BFR) is a critical physical layer and MAC layer procedure defined for 5G New Radio (NR), particularly for operation in Frequency Range 2 (FR2), which includes millimeter-wave (mmWave) bands. In these high-frequency spectrums, communication relies on highly directional beamformed transmissions between the gNodeB (gNB) and the User Equipment (UE) to overcome high path loss. However, these narrow beams are vulnerable to sudden blockages (e.g., by a person, vehicle, or building), leading to a rapid degradation of signal quality, termed a beam failure. The BFR procedure is the UE-initiated mechanism to detect this failure and recover the connection without resorting to a full radio link failure (RLF) and subsequent RRC re-establishment, which is a much slower and more disruptive process.

The architecture of BFR involves monitoring, detection, and recovery phases, coordinated between the UE's physical layer (PHY), Medium Access Control (MAC) layer, and the gNB. The gNB configures the UE with a set of reference signals for beam management, primarily Channel State Information Reference Signals (CSI-RS) and/or Synchronization Signal Blocks (SSBs). The UE continuously monitors the quality of its currently active serving beam using these reference signals. The procedure is triggered when the beam quality, measured as a Reference Signal Received Power (RSRP) or similar metric, falls below a configured threshold for a certain number of consecutive measurement instances. This constitutes the beam failure detection.

Upon detecting a failure, the UE initiates the recovery request phase. The gNB pre-configures the UE with a set of candidate beams, which are alternative beams (identified by specific CSI-RS resources or SSBs) that the UE can measure. The UE selects a suitable new beam from these candidates and transmits a Beam Failure Recovery Request (BFRQ) to the gNB. This request is sent using a dedicated Physical Random Access Channel (PRACH) preamble, known as a Contention-Free Random Access (CFRA) resource, which is uniquely associated with the selected candidate beam. This association allows the gNB to identify which new beam the UE is proposing for recovery upon receiving the preamble.

The final phase is the gNB's response and recovery completion. After receiving the BFRQ preamble, the gNB acknowledges it with a Random Access Response (RAR) message on the Physical Downlink Control Channel (PDCCH). Crucially, this response is transmitted using the new beam identified by the UE's request, confirming the gNB's acceptance of the beam switch. Following this, normal communication resumes on the new beam. The entire BFR procedure is designed to be executed within tens of milliseconds, ensuring minimal impact on user experience and maintaining the high reliability and low latency required for 5G services.

Purpose & Motivation

BFR was introduced to address a fundamental challenge in 5G NR's utilization of mmWave and high-frequency spectrum: the inherent fragility of directional communication links. Prior to 5G, cellular systems primarily operated in sub-6 GHz bands where signals are more omnidirectional and less prone to complete, instantaneous blockage. In these systems, link failure recovery was handled at a higher layer through Radio Link Failure (RLF) procedures, which involve complex RRC re-establishment, cell reselection, or handovers—processes that can take hundreds of milliseconds to seconds. This latency is unacceptable for the ultra-reliable low-latency communication (URLLC) and enhanced mobile broadband (eMBB) use cases envisioned for 5G.

The motivation for creating BFR stemmed from the realization that in beam-centric mmWave deployments, a link disruption is often a local beam problem, not a complete cell failure. The serving cell (gNB) likely has other viable beams to serve the UE. The purpose of BFR is to provide a fast, lower-layer recovery mechanism that treats beam failure as a localized event. It solves the problem of service interruption due to temporary blockages by enabling a swift beam switch, analogous to a 'beam-level handover,' without involving the core network or complex upper-layer protocols. This directly enhances mobility robustness, user throughput, and overall network reliability in dense urban and indoor environments where blockages are frequent.

Historically, 4G LTE did not have an equivalent procedure because it did not employ beamforming as intensively as 5G NR in mmWave. LTE's beam management, where it existed, was less dynamic. BFR represents a paradigm shift to a more agile and resilient Radio Access Network (RAN) architecture, acknowledging the physical layer realities of high-frequency communication. It addresses the limitations of previous all-or-nothing RLF recovery by introducing a granular, beam-specific recovery process, which is essential for fulfilling 5G's performance promises.

What changed in its specifications

The latest release-to-release comparison of specifications that define BFR. Each summary describes the whole specification, not only this term.

TS 38.321Rel-18 → Rel-19

Rel-19 adds sub-band full duplex handling to the NR Random Access procedure. It covers new second-PRACH-occasion RO type selection, power settings, Msg1 repetition, and RSRP threshold settings.

Full comparison in TS 38.321 →

Technology family

MIMO and beam management · Radio Access Network › NG-RAN (5G)

  1. R99 Transmit diversity, TSTD
  2. Rel-7 MIMO
  3. Rel-8 CSI, DM-RS, MU-MIMO, PMI, RI, SDMA, SRS, SU-MIMO, TPMI
  4. Rel-10 CSI-RS, NZP CSI-RS
  5. Rel-11 CoMP, CSI-IM, QCL, UL CLTD, UL MIMO
  6. Rel-13 CRI, FD-MIMO
  7. Rel-15 Beam Level Mobility, Beam management, BFD, BFD-RS, BFR, PT-RS, TCI, ZP CSI-RS
  8. Rel-18 CJT

Also in this family (introduction release not pinned to a single defining specification): Beamforming

  • BFR used together with BFD
    “For beam failure detection, the gNB configures the UE with beam failure detection reference signals (SSB or CSI-RS) and the UE declares beam failure when the number of beam failure instance indications from the physical layer reaches a configured threshold before a configured timer expires.” TS 38.300

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 5 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-15 introduced

The Beam Failure Recovery procedure is specified for the first time in the MAC specification TS 38.321, including its completion conditions, PDCCH-based termination and BWP operation for BFR random access.

Rel-16 specification text

Rel-16 adds SCell beam failure recovery in MAC: BFR MAC CE and Truncated BFR MAC CE, SR triggered for BFR, BFR triggering, cancellation and completion rules, and LCP prioritization.

  • “indicate to the Multiplexing and assembly entity to include a BFR MAC CE or a Truncated BFR MAC CE in the subsequent uplink transmission.” TS 38.321 v16.22.0
  • “consider the Beam Failure Recovery procedure successfully completed and cancel all the triggered BFRs for this Serving Cell.” TS 38.321 v16.22.0
  • “if this SR was triggered by beam failure recovery (see clause 5.17) of an SCell” TS 38.321 v16.22.0
Rel-17 1 CR

BFR was extended per BFD-RS set with new Enhanced and Truncated Enhanced BFR MAC CEs, per-set triggering, SR handling and completion/cancellation rules, plus unified TCI corrections.

  • “if this SR was triggered by beam failure recovery (see clause 5.17) for a BFD-RS set of a Serving Cell” TS 38.321 v17.15.0
  • “4> trigger a BFR for this BFD-RS set of the Serving Cell;” TS 38.321 v17.15.0
  • Corrections for Beam Failure Recovery related to unified TCI state framework TS 38.213CR0450
Rel-18 2 CRs

BFR behaviour was corrected in Rel-18: SDT BFR timer handling when not configured, BFR MAC CE candidate beam list field name, SR for mTRP BFR, and TCI state handling after BFR MAC CE in Msg3/MsgA.

  • Correction on SR for mTRP BFR TS 38.321CR2083
  • Correction on the field name of candidate beam list in BFR MAC CE TS 38.321CR1981
  • “SDT BFR timer being not configured [RA-SDT_BeamFailure]” TS 38.321 v18.10.0
Rel-19 specification text

F1AP now lets the gNB-DU receive a BFR SSB Index within MRO for LTM information, treating it as beam failure recovery after LTM cell switch for target beam selection optimisation.

  • “the gNB-DU shall, if supported, consider that a Beam Failure Recovery after successful LTM Cell Switch has occurred in the target DU” TS 38.473 v19.4.0
  • “SSB Index of the recovery beam or SSB Index of the beam which is QCLed with CSI-RS resources used at successful Beam Failure Recovery.” TS 38.473 v19.4.0

Defining Specifications

3GPP specifications that define or reference BFR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 37.816 vg00 RAN-centric Data Collection & Utilization Study Rel-16 read
TS 38.321 vj40 NR MAC Protocol Specification Rel-19 read
TR 38.808 vh00 Study on NR above 52.6 GHz to 71 GHz Rel-17 read