When should a network operator use B2 instead of B1?

B2 is the conservative choice for inter-frequency handover. Use B2 when you want the UE to stay on its current frequency as long as it is performing adequately, and only move to a different frequency when the current connection is genuinely degrading. This minimizes unnecessary handovers (ping-pong), reduces signaling load on the core network, and avoids measurement gaps that interrupt data throughput. B1, by contrast, triggers based only on the neighbor quality, which can cause premature handovers to a higher-capacity layer even when the current connection is perfectly good.

How does B2 relate to NR-to-LTE fallback?

B2 is the primary event used for inter-RAT fallback from 5G NR to LTE. In NSA (Non-Standalone) deployments, the network configures a B2 event where Thresh1 monitors the NR serving cell and Thresh2 monitors LTE neighbor cells. When the NR signal drops below Thresh1 and an LTE cell exceeds Thresh2, the UE reports the LTE cell, and the network redirects the UE to LTE. This is how operators handle NR coverage holes at cell edges, especially for mmWave deployments where coverage drops off sharply.

5G NR / Mobility

B2 Event

Q: How are the two B2 thresholds configured?

B2 uses two independent thresholds. Threshold1 applies to the serving cell (Ms + Hys Thresh2). A typical configuration might set Thresh1 to -110 dBm RSRP (serving is weak) and Thresh2 to -100 dBm RSRP (neighbor is good). Both conditions must be true simultaneously and sustained for the time-to-trigger duration before the UE sends a measurement report. The hysteresis value prevents rapid toggling near the threshold boundaries.

/bee-too ee-vent/

A B2 Event is a conditional inter-frequency measurement event in 5G NR (3GPP TS 38.331) that triggers when two conditions are met simultaneously: the serving cell's signal quality drops below a first configured threshold (Thresh1), AND a neighbor cell on a different frequency or RAT exceeds a second threshold (Thresh2). This dual-condition design prevents unnecessary handovers when the current connection is still adequate, making B2 the preferred event for conservative inter-frequency mobility and NR-to-LTE fallback.

Category: 5G NR Mobility

3GPP Spec: TS 38.331, TS 38.133

Type: Inter-frequency / Inter-RAT

Understanding the B2 Event

The B2 event is the inter-frequency counterpart of the A5 event (which operates intra-frequency). It solves a specific problem: how to move a UE to a different frequency band only when the current band is actually performing poorly. This prevents the "eager handover" behavior of B1, where the UE would report and potentially hand over to a new frequency even though the existing connection was perfectly functional.

In practice, B2 is the workhorse event for NR-to-LTE fallback in NSA (Non-Standalone) deployments. When a user walks away from a 5G cell, the NR signal weakens. If B2 is configured, the UE only reports the fallback LTE cell when the NR signal drops below Thresh1, ensuring the UE stays on the high-throughput NR carrier as long as possible.

B2 Trigger Conditions

B2 Event:
A B2 Event is a conditional inter-frequency measurement event in 5G NR (3GPP TS 38.331) that triggers when two conditions are met simultaneously: the serving...

Key specifications:
1 v | 0 dB | 1 mW | 30 dB | 1 W | 110 GHz

Power: P(dBm) = 10log(P_mW), 0dBm = 1mW

B1 vs. B2 Decision Matrix

Criterion	B1 Event	B2 Event
Trigger logic	Neighbor > Thresh	Serving < Thresh1 AND Neighbor > Thresh2
Conservatism	Aggressive (neighbor-only)	Conservative (dual-condition)
Ping-pong risk	Higher	Lower
NR-to-LTE fallback	Not typical	Primary use case
Load balancing	Good (steers to preferred layer)	Poor (only fires when serving is weak)
Data interruption	More frequent gaps	Fewer gaps (stays on current freq longer)

Key Equations

Decibel conversion:
Power: dB = 10log(P₂/P₁)
Voltage: dB = 20log(V₂/V₁)

dBm to watts:
P(W) = 10^{(dBm−30)/10}
0 dBm = 1 mW, +30 dBm = 1 W

Wavelength:
λ = c/f = 300/f(MHz) meters

Comparison

Aspect	B2 Event Spec	Typical Range	Impact	Design Note
Primary function	This dual-condition design prevents unne...	Application-dep.	Critical	Verify in sim
Operating range	Understanding the B2 Event The B2 event...	Application-dep.	Critical	Verify in sim
Performance	It solves a specific problem: how to mov...	Application-dep.	Critical	Verify in sim
Integration	This prevents the "eager handover" behav...	Application-dep.	Critical	Verify in sim
Trade-off	In practice, B2 is the workhorse event f...	Application-dep.	Critical	Verify in sim

Common Questions

Frequently Asked Questions

When should a network use B2 instead of B1?

B2 is the conservative choice. Use it when you want the UE to stay on its current frequency as long as it is adequate, and only move when the connection is genuinely degrading. This minimizes unnecessary handovers, reduces signaling load, and avoids measurement gaps that interrupt throughput. B1 triggers based only on neighbor quality, which can cause premature handovers even when the current connection is fine.

How are the two B2 thresholds configured?

Threshold1 applies to the serving cell (Ms + Hys < Thresh1). Threshold2 applies to the neighbor cell (Mn + Ofn + Ocn - Hys > Thresh2). A typical setup: Thresh1 = -110 dBm RSRP (serving is weak), Thresh2 = -100 dBm (neighbor is good). Both conditions must be true simultaneously and sustained for the time-to-trigger duration before the UE sends a report.

How does B2 handle NR-to-LTE fallback?

B2 is the primary event for inter-RAT fallback from 5G NR to LTE. In NSA deployments, the network configures B2 where Thresh1 monitors the NR serving cell and Thresh2 monitors LTE neighbors. When NR drops below Thresh1 and an LTE cell exceeds Thresh2, the UE reports the LTE cell and the network redirects. This handles NR coverage holes at cell edges, especially for mmWave deployments where coverage drops sharply.

Related Terms

← B1 Homogeneity B8ZS →