How does beam failure detection work in 5G NR?

The UE monitors beam failure detection reference signals (BFD-RS), which are SSB or CSI-RS resources configured by RRC. For each BFD-RS occasion, the UE estimates the hypothetical PDCCH block error rate (BLER). If the estimated BLER exceeds the Qout threshold (~10%), a beam failure instance (BFI) is counted. The Qout threshold corresponds approximately to SS-RSRP < -140 dBm or L1-SINR < -8 dB, though the exact mapping depends on the PDCCH configuration (aggregation level, DCI format). BFIs are accumulated: if beamFailureInstanceMaxCount BFIs occur within beamFailureDetectionTimer (configurable from 1 to 60 ms), beam failure is declared and recovery begins. If the beam quality recovers before reaching the count, the BFI counter resets.

What causes beam failure in mmWave 5G?

Common causes of beam failure at FR2 (mmWave) frequencies: 1) Human body blockage: a hand or head blocking the line-of-sight path causes 20-35 dB attenuation at 28 GHz. This is the most frequent cause, occurring every few seconds during normal phone use. 2) Vehicle/pedestrian blockage in outdoor deployments: moving objects crossing the beam path cause transient outages of 50-200 ms. 3) UE rotation: rotating the phone 90° can move the active antenna panel away from the serving beam direction. 4) Multipath fading: constructive/destructive interference from reflections can cause rapid signal fluctuations. 5) gNB handover boundary: moving between cell coverage areas where no single beam has sufficient gain. FR1 (sub-6 GHz) beam failures are rare because wider beams (30-120°) provide inherent robustness.

What are the key BFD configuration parameters?

RRC configures BFD through several parameters: 1) BFD-RS set: the reference signals to monitor (up to 64 SSB indices or CSI-RS resources). Multiple BFD-RS allows monitoring multiple serving beams simultaneously. 2) beamFailureInstanceMaxCount: number of consecutive BFIs before declaring failure (values: 1, 2, 3, 4, 5, 6, 8, 10). Lower values = faster detection but higher false alarm rate. 3) beamFailureDetectionTimer: time window for counting BFIs (values: 1-60 ms). BFIs outside this window are discarded. 4) Qout threshold: not directly configurable; defined by 3GPP as the PDCCH BLER corresponding to ~10% block error rate. The network optimizes these parameters based on deployment scenario: aggressive settings (maxCount=2, timer=10ms) for urban mmWave with frequent blockage, conservative settings (maxCount=6, timer=40ms) for sub-6 GHz macro cells.

5G NR Beam Management

Beam Failure Detection (BFD)

Q: What causes beam failure in mmWave 5G?

Common causes of beam failure at FR2 (mmWave) frequencies: 1) Human body blockage: a hand or head blocking the line-of-sight path causes 20-35 dB attenuation at 28 GHz. This is the most frequent cause, occurring every few seconds during normal phone use. 2) Vehicle/pedestrian blockage in outdoor deployments: moving objects crossing the beam path cause transient outages of 50-200 ms. 3) UE rotation: rotating the phone 90° can move the active antenna panel away from the serving beam direction. 4) Multipath fading: constructive/destructive interference from reflections can cause rapid signal fluctuations. 5) gNB handover boundary: moving between cell coverage areas where no single beam has sufficient gain. FR1 (sub-6 GHz) beam failures are rare because wider beams (30-120°) provide inherent robustness.

Q: What are the key BFD configuration parameters?

RRC configures BFD through several parameters: 1) BFD-RS set: the reference signals to monitor (up to 64 SSB indices or CSI-RS resources). Multiple BFD-RS allows monitoring multiple serving beams simultaneously. 2) beamFailureInstanceMaxCount: number of consecutive BFIs before declaring failure (values: 1, 2, 3, 4, 5, 6, 8, 10). Lower values = faster detection but higher false alarm rate. 3) beamFailureDetectionTimer: time window for counting BFIs (values: 1-60 ms). BFIs outside this window are discarded. 4) Qout threshold: not directly configurable; defined by 3GPP as the PDCCH BLER corresponding to ~10% block error rate. The network optimizes these parameters based on deployment scenario: aggressive settings (maxCount=2, timer=10ms) for urban mmWave with frequent blockage, conservative settings (maxCount=6, timer=40ms) for sub-6 GHz macro cells.

/beem FAYL-yur dee-TEK-shun/

A 5G NR Layer 1 procedure where the UE monitors serving beam quality via BFD reference signals (SSB or CSI-RS). When the hypothetical PDCCH BLER exceeds Q_out (~10%, corresponding to SS-RSRP < −140 dBm or SINR < −8 dB), a beam failure instance (BFI) is counted. After beamFailureInstanceMaxCount BFIs within beamFailureDetectionTimer, beam failure is declared and recovery (BFR) initiates. Critical for FR2 (mmWave) where body/obstacle blockage causes 20 to 35 dB sudden attenuation.

Q_out: ~10% BLER

RSRP threshold: <−140 dBm

Spec: TS 38.321

Understanding Beam Failure Detection

Beam failure detection is the first stage of the 5G NR beam recovery mechanism. At mmWave frequencies, the narrow beams that provide necessary link budget gain are highly susceptible to blockage. A human hand blocking the line-of-sight path at 28 GHz introduces 20 to 35 dB of attenuation, enough to collapse the link instantly. BFD must detect this condition within milliseconds so that recovery can begin before the user experiences a noticeable service interruption.

The detection mechanism is based on monitoring reference signals that the gNB transmits on the serving beam. The UE estimates what the PDCCH decoding performance would be at the current signal quality. When the estimated block error rate exceeds Q_out (approximately 10%), the UE recognizes that reliable control channel reception is no longer possible on this beam.

BFD Threshold Mechanics

Q_out Threshold (Beam Failure):
Hypothetical PDCCH BLER > 10%
Corresponding SS-RSRP < −140 dBm
Corresponding L1-SINR < −8 dB

Q_in Threshold (Beam Recovery Candidate):
Hypothetical PDCCH BLER < 1%
Corresponding SS-RSRP > −128 dBm
Corresponding L1-SINR > −2 dB

Detection Timeline:
BFI count = beamFailureInstanceMaxCount
Window = beamFailureDetectionTimer
Typical: 2–4 BFIs in 10–20 ms
Total detection time: 10–40 ms

BFD Configuration Parameters

Parameter	Values	Aggressive	Conservative
BFI MaxCount	1,2,3,4,5,6,8,10	2	6
Detection Timer	1–60 ms	10 ms	40 ms
BFD-RS count	1–64	4–8	1–2
Best scenario	—	Urban FR2	Sub-6 macro
Detection latency	—	~10 ms	~40 ms

Common Questions

Frequently Asked Questions

How does BFD work?

UE monitors BFD-RS (SSB/CSI-RS). Estimates PDCCH BLER. If BLER > Q_out (10%), BFI counted. After MaxCount BFIs in DetectionTimer, beam failure declared. Counter resets if beam recovers before threshold.

What causes beam failure?

FR2: body blockage (20 to 35 dB at 28 GHz), vehicle/pedestrian obstruction (50 to 200 ms), UE rotation, multipath fading. FR1: rare due to wider beams (30 to 120°). Blockage is the dominant cause at mmWave.

Key configuration parameters?

BFD-RS set (up to 64), BFI MaxCount (1 to 10), DetectionTimer (1 to 60 ms), Q_out threshold (~10% BLER). Aggressive for urban FR2 (MaxCount=2, 10 ms), conservative for sub-6 GHz (MaxCount=6, 40 ms).

Related Terms

← Beam Correspondence Beam Failure Recovery →

5G NR Systems

Precision RF Components

RF Essentials provides precision terminations and custom waveguide assemblies for 5G NR beam management test systems and OTA measurement equipment.

Request a Quote