UAC

Unified Access Control

Mobility →
Introduced in Rel-2 Also in: Services, User Equipment

UAC is a mechanism that manages UE access attempts during congestion or emergencies, using Access Class Barring, Service Specific Access Control, and Extended Access Barring to prioritize specific users or services for network stability.

Category
Mobility
Introduced
Rel-2
Where
Core Network › 5G Core
Also touches
2 segments
Specifications
11 specs
UAC Description Purpose Detected Changes Specifications

Description

Unified Access Control (UAC) is a comprehensive framework in 3GPP that governs how User Equipment (UE) is allowed or barred from initiating access to the radio network (e.g., for making a call, sending data, or signaling). It is a critical Radio Resource Management (RRM) function executed by the Radio Access Network (RAN) in coordination with the core network. UAC employs a set of barring parameters broadcast in system information blocks (SIBs) that the UE must evaluate before attempting any access procedure, such as RRC connection establishment. The UE applies these rules locally, preventing a flood of access attempts that could collapse a congested or recovering network.

The framework unifies several previously separate barring mechanisms. The core components are Access Class Barring (ACB), which bars UEs based on a randomly assigned Access Class (0-9, with 10-15 for higher priority); Service Specific Access Control (SSAC), which applies specific barring factors for Multimedia Telephony Service (MTSI) voice and video sessions; and Extended Access Barring (EAB), which targets UEs configured for low access priority (e.g., machine-type devices). For 5G NR, this was enhanced with Unified Access Control for NR (UAC-NR), which introduced Access Identity and Access Category based control, providing more granularity. The UE determines its applicable Access Identity (e.g., as a multimedia priority service user) and the Access Category of the intended service (e.g., emergency, delay-tolerant, mobile originated signaling), then checks the corresponding barring information broadcast by the network.

When the network experiences high load, a disaster, or a failure, the network operator can dynamically update the UAC parameters broadcast in SIBs. For instance, it can bar all regular users (Access Class 0-9) while allowing emergency services (Access Class 14) and network staff (Access Class 15) to access the network. The UE performs a probabilistic check using a broadcast barring factor and barring time; if barred, it must wait before retrying. This decentralized control mechanism is highly efficient as it prevents the access network from being overwhelmed by rejected requests, conserving signaling resources for allowed accesses. UAC is therefore essential for maintaining network availability, implementing service differentiation, and ensuring priority access for public safety and emergency communications.

Purpose & Motivation

UAC was created to solve the critical problem of radio access network congestion collapse, particularly during mass events, emergencies, or network failures. Prior to unified mechanisms, barring controls were more fragmented and less granular. UAC provides a standardized, unified framework that allows network operators to dynamically control the influx of access attempts based on user priority, service type, and device characteristics, thereby protecting network stability and ensuring resources are available for the most important communications.

The evolution towards UAC was motivated by the need for more sophisticated traffic management with the rise of always-connected smartphones and massive IoT deployments. Simple access class barring from 2G/3G was insufficient. SSAC addressed the specific need to protect voice over LTE (VoLTE) services during congestion. EAB was introduced to manage the potential signaling storm from millions of low-priority MTC devices. UAC unified these under a single conceptual framework, simplifying network management and UE implementation. It addresses the limitation of reactive congestion management by providing proactive, broadcast-based controls that are applied at the source (the UE).

In 5G, the purpose expanded to support a wider range of service-defined categories, aligning with network slicing and diverse QoS requirements. The new model based on Access Identities and Categories allows the network to implement very precise policies, such as allowing access for a specific network slice while barring others, or prioritizing factory automation traffic over sensor updates. This ensures that 5G can reliably support both mission-critical and massive IoT services on a shared infrastructure.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 1 change

In Release 15, a key introduction for the Unified Access Control (UAC) function was a new Elementary File (EF) to store 5G UAC Access Identity information. This provided the UE with a standardized method to hold the access identities used for access control and barring mechanisms in 5G. The change specifically involved adding this new data structure to the USIM.

  • Introduce an EF that contains 5G UAC Access Identity Information TS 31.102CR0780
Rel-16 1 change

In Release 16, the primary update for the Unified Access Control (UAC) function was a clarification of the procedure for reading the UAC Access Identities configuration from the EF (Elementary File) on the USIM. This enhancement specifically addressed the reading procedure for the "UAC Access Identities Configuration EF," ensuring more reliable and standardized access to these critical subscription parameters.

  • Clarify reading procedure for UAC Access Identities Configuration EF in USIM TS 31.102CR0866

Explore further

Broader topics and technologies where UAC plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 24.228 v1500 IP Multimedia Call Control Signaling Flows Rel-5
TS 24.229 vj50 IMS call control protocol based on SIP and SDP Rel-19
TS 29.162 vj00 IMS-IP Network Interworking Rel-19
TS 29.163 vj00 Interworking between 3GPP IM CN and CS networks Rel-19
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures Rel-19
TS 31.102 vj40 USIM Application Specification Rel-19
TS 32.808 v1800 Common User Profile Storage Framework Rel-8
TS 32.850 ve00 IMS Charging Correlation Methods Study Rel-14
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.304 vj00 UE Idle Mode Procedures in E-UTRA Rel-19
TS 38.304 vj00 UE RRC_IDLE and RRC_INACTIVE Procedures Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.