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.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (10 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-2, normative work from Rel-15.
In Release 15, the UAC (Unified Access Control) function was enhanced by introducing a new Elementary File (EF) to contain 5G UAC Access Identity information. This release also updated the USIM Service Table to provide support for PDU session call control. Furthermore, it removed and corrected a control plane-based Steering of Roaming (SoR) related EF, consolidating this functionality solely within the EF-UST.
- Introduce an EF that contains 5G UAC Access Identity Information TS 31.102CR0780
- USIM Service Table update for PDU session call control support TS 31.102CR0786
- Remove the control plane based SoR related EF and use only the EF-UST. TS 31.102CR0798
- Corrections to the control plane based SoR related EF TS 31.102CR0799
- Missing description of RRC Connection Re-establishment for the Control plane TS 36.300CR1094
- Introduction of support for MAC PDU containing UE contention resolution identity MAC control element without RRC response message in NB-IoT TS 36.300CR1102
In Release 16, the enhancement to the Unified Access Control (UAC) function specifically clarified the procedure for reading the UAC Access Identities Configuration Elementary File (EF) stored on the USIM. This update provided definitive guidance on how a User Equipment must retrieve this configuration data, ensuring consistent and reliable access control behavior across different implementations.
- Clarify reading procedure for UAC Access Identities Configuration EF in USIM TS 31.102CR0866
In Release 18, the UAC (Unified Access Control) function was enhanced by adding an EF (Elementary File) for Access Control to the GBA_U_APIs stored on the USIM. Additionally, corrections were made to fix issues related to the FID (File Identifier) for the Access Control files on the SIM card.
In Release 19, the Unified Access Control (UAC) function introduced new capabilities for operator-controlled network selection, specifically the "Operator-controlled-LSP-PLMN" parameter. This was complemented by the introduction of a "PeriodicSearchTimerNonLSP" timer mechanism to govern search behavior. These additions enhanced operator control over how user equipment prioritizes and periodically searches for available networks.
- Introducing Operator-controlled-LSP-PLMN and PeriodicSearchTimerNonLSP TS 31.102CR1081
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.
| Specification | Title | Release |
|---|---|---|
| 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 |