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

Glossary term · Radio Access Network

ACB

Access Class Barring

Radio Access Network →

ACB is a congestion control mechanism that lets the network restrict which UE access classes may attempt random access, protecting RAN resources during overload by probabilistically or deterministically blocking low-priority access attempts.

Introduced
Rel-12
Where
Radio Access Network › UTRAN (3G)
Specifications
4 specs
ACB Description Purpose Neighbours Specifications

Description

Access Class Barring (ACB) is a radio access network congestion control mechanism defined by 3GPP to regulate the load on the random access channel (RACH) and the broader control plane during periods of high demand. Every UE is a member of one or more Access Classes (ACs): classes 0–9 are normal user classes assigned randomly and stored in the USIM, class 10 indicates an emergency call, class 11 is for PLMN use, class 12 for security services, class 13 for public utilities, class 14 for emergency services, and class 15 for PLMN staff. The network broadcasts barring parameters within System Information (SIB2 in LTE, SIB1/SIB2 in NR) that tell each UE whether its class is barred and, if so, with what probability it may still attempt access.

The core mechanism is probabilistic. The network broadcasts an ac-BarringFactor (a value between 0 and 1) and an ac-BarringTime. When a UE in a barred class wants to initiate an access, it draws a uniform random number; if the number is below the barring factor, access is permitted, otherwise the UE is barred and must wait for a duration derived from ac-BarringTime before retrying. By lowering the barring factor, the operator can throttle the fraction of UEs allowed to attempt access, effectively shaping the RACH arrival rate. Special handling exists for emergency calls and for high-priority classes (11–15), which can be configured with separate barring parameters or exempted entirely, ensuring that critical users retain access during congestion.

In LTE, ACB is complemented by mechanisms such as Service Specific Access Control (SSAC) for IMS voice/video, Extended Access Barring (EAB) for delay-tolerant MTC devices, and later Unified Access Control (UAC) in 5G NR. ACB itself operates at the RRC connection establishment stage: when a UE in RRC_IDLE wishes to transition to RRC_CONNECTED, it evaluates the barring parameters before sending an RRCConnectionRequest. If barred, the UE does not transmit, avoiding RACH collisions and signalling load on the eNodeB. The eNodeB controls the broadcast parameters dynamically based on observed load, typically via OAM or self-organising network (SON) functions.

ACB is closely tied to the RACH procedure. The PRACH is a contention-based channel; if too many UEs transmit preambles simultaneously, collisions rise, retransmissions increase, and access latency grows. ACB reduces the offered load so that the RACH operates within its capacity. The mechanism is specified across 22.806 (feasibility study on access class barring), 25.700/25.704 (UE and RAN procedures), and 36.848 (study on RAN overload control), reflecting its cross-layer nature spanning UE behaviour, RAN broadcast signalling, and OAM control.

Operationally, ACB is one of the primary tools an operator uses during mass events, disasters, or network outages. It is simple, standards-based, and requires no per-UE signalling—the parameters are broadcast, so all UEs receive them simultaneously. Its limitations include coarse granularity (only 10 normal classes) and the fact that it does not distinguish application types; these gaps motivated later mechanisms like EAB, SSAC, and UAC.

Purpose & Motivation

ACB exists to protect the radio access network from overload caused by simultaneous access attempts from many UEs. Without it, a sudden surge—such as after a disaster, during a large public event, or when a cell recovers from an outage—could saturate the PRACH and the control plane, causing widespread access failures and potentially cascading instability. Earlier networks had no standardised, broadcast-based way to throttle access attempts at the UE before they consumed RACH resources.

By defining access classes and broadcasting barring factors, 3GPP gave operators a lightweight, scalable control knob that requires no dedicated signalling per device. The mechanism was designed to be evaluated autonomously by the UE, so the network does not need to track individual devices. This makes ACB effective even when millions of devices attempt access at once.

The introduction in Rel-12 and refinement through Rel-13 reflected growing concern about machine-type communications and emergency scenarios, where prioritisation between normal users, emergency callers, and delay-tolerant devices became essential. ACB laid the conceptual groundwork for the more granular barring frameworks that followed in LTE-Advanced Pro and 5G.

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-12 Initial

Initial standardisation of Access Class Barring as a RAN overload control mechanism, defining access classes, broadcast barring parameters, and UE evaluation procedures in 22.806, 25.700, 25.704, and 36.848.

The term carried over unchanged in definition; Rel-13 work focused on complementary mechanisms such as Extended Access Barring for MTC, while ACB itself retained its Rel-12 semantics.

Defining Specifications

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

SpecificationTitleRelease
TS 22.806 vd10 Application Specific Congestion Control for Data Rel-13 read
TS 25.700 vc00 Further Enhanced Uplink (EUL) Study Rel-12 read
TS 25.704 vc00 Study on Enhanced Broadcast of System Information Rel-12 read
TS 36.848 vc00 Study on Smart Congestion Mitigation in E-UTRAN Rel-12 read