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

Glossary term · Services

CAG

Closed Access Group

Services →

CAG is a 5G feature that provides restricted and secure network access exclusively to authorized users within a specific location, such as an enterprise campus.

Introduced
Rel-16
Where
Radio Access Network › NG-RAN (5G)
Specifications
22 specs
Also in
Security, Core Network, User Equipment, Management
CAG Description Purpose What changed Neighbours Detected Changes Specifications

Description

A Closed Access Group (CAG) is a 3GPP-defined mechanism in 5G systems that facilitates controlled and restricted network access for a defined group of User Equipment (UEs) within a specific geographical area, such as an enterprise campus, factory, or hospital. It operates by associating one or more CAG Identifiers (CAG IDs) with specific cells, known as CAG cells, which are part of a Public Land Mobile Network (PLMN). Only UEs that are subscribed to and explicitly authorized for a particular CAG ID are permitted to access the corresponding CAG cells. This creates a logical, access-controlled network slice within the public 5G infrastructure, ensuring that the radio resources and network services are dedicated to the authorized group, thereby preventing unauthorized public access.

The architecture involves several key network functions. The Access and Mobility Management Function (AMF) plays a central role in enforcing CAG access control during registration and service request procedures. The Unified Data Management (UDM) stores the subscriber's CAG subscription data, including the list of Allowed CAG IDs for each UE. This subscription data is provided to the AMF via the Authentication Server Function (AUSF) during authentication. The Radio Access Network (RAN), specifically the gNB, broadcasts the supported CAG IDs for a cell in System Information Block 1 (SIB1) using the `cag-IdentityList` parameter. A UE configured for CAG access scans for these broadcasts and only attempts to select or camp on a cell if its subscribed Allowed CAG list includes one of the IDs broadcast by that cell.

The operational flow begins with the UE, which must have a USIM containing a CAG-specific Access Control List. When the UE is powered on or enters the area, it reads the CAG ID list from the cell's SIB1. The UE compares this list with its stored Allowed CAG list. If a match is found, the UE proceeds with the initial registration procedure, indicating its selected CAG ID to the network. The AMF then verifies the UE's authorization by checking the subscription data received from the UDM. If the UE is not authorized for the requested CAG, the AMF rejects the registration with an appropriate cause code, such as "CAG not allowed." For mobility, a UE is generally not permitted to handover into a CAG cell unless it is authorized for that CAG, ensuring the closed nature of the group is maintained during movement.

CAG is closely integrated with other 5G features like Network Slicing. A CAG can be associated with one or more Network Slice Instances (NSIs), allowing the closed group of users to access specific, tailored services (e.g., ultra-reliable low-latency communication for factory automation) on a dedicated logical network. This combination provides both access control and service isolation. Management and exposure of CAG capabilities are handled by the Network Exposure Function (NEF) and the Service Capability Exposure Function (SCEF) for northbound APIs, enabling enterprise applications to manage their CAG memberships and policies.

Purpose & Motivation

CAG was introduced in 3GPP Release 16 to address the growing demand from vertical industries (e.g., manufacturing, energy, healthcare) and enterprises for private, secure, and controlled 5G network access. Prior to CAG, similar concepts existed like Closed Subscriber Groups (CSG) in 4G LTE, which were primarily designed for residential femtocells. However, CSG had limitations for large-scale enterprise deployments, including less flexible subscription management and limited integration with modern 5G core network principles like network slicing and service-based architecture. CAG was created to provide a more scalable, policy-driven, and network-slice-aware access control mechanism suitable for professional and industrial use cases.

The primary problem CAG solves is enabling a public network operator to offer a "virtual private network" experience on a shared public RAN and core infrastructure. Without CAG, an enterprise would require a physically separate, dedicated network (a true private network) to ensure only its devices can connect, which is costly and inefficient. CAG allows the operator to logically partition a portion of its public network, designating certain cells for exclusive use by a customer's authorized devices. This solves the problems of unauthorized access, radio resource contention with public users, and lack of service guarantees for critical enterprise applications.

Furthermore, CAG supports the 5G vision of network-as-a-service and network slicing by providing the foundational access control layer. It allows enterprises to have guaranteed connectivity for their mission-critical IoT devices, autonomous guided vehicles, and AR/VR tools without interference from public traffic. The motivation stems from industry digitization trends (Industry 4.0) where reliable, low-latency, and secure wireless connectivity is a prerequisite. CAG, combined with network slicing, enables operators to meet stringent Service Level Agreements (SLAs) for these vertical customers on a shared infrastructure, unlocking new revenue streams and use cases beyond traditional consumer mobile broadband.

What changed in its specifications

The latest release-to-release comparison of specifications that define CAG. Each summary describes the whole specification, not only this term.

TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →
TS 24.501Rel-18 → Rel-19

Rel-19 adds satellite NG-RAN access text, LP-WUS/WUR assistance and disabling, ATUC RAT utilization control, and network-controlled slice selection with S-NSSAI time validity to TS 24.501. It also adds ATSSS Phase 4 multi-access and 5G ProSe multi-hop relay support.

Full comparison in TS 24.501 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 60 changes
  • Providing CAG ID to the lower layer TS 24.501CR0997
  • Provisioning of an allowed CAG list and a CAG access only indication TS 24.501CR1056
  • 5GMM cause value for CAG TS 24.501CR1057
  • Storage for CAG information TS 24.501CR1236
  • Transmission of the UE CAG capability to the network TS 24.501CR1431
  • CAG information towards the lower layers for paging TS 24.501CR1567

+ 54 more changes

Rel-17 45 changes
  • Usage of initial CAG information list TS 24.501CR2774
  • Introduce a USIM file to store pre-configured CAG information list TS 31.102CR0904
  • Toolkit support of CAG Cell Selection TS 31.111CR0772
  • The solution to CAG IDs of a PLMN beyond the limit of one Entry-IE part TS 24.501CR4124
  • The solution to CAG IDs of a PLMN beyond the limit of one Entry-Procedure part TS 24.501CR4125
  • The requirement of AMF to provide CAG information list for the current PLMN TS 24.501CR2452

+ 39 more changes

Rel-18 25 changes
  • Support of allowed CAG list with validity condition TS 23.501CR4119
  • Enhanced CAG selection - enforcement in successful cases TS 24.501CR4977
  • Enhanced CAG selection - enforcement in unsuccessful cases TS 24.501CR4978
  • Enhanced CAG selection - providing additional information TS 24.501CR4976
  • UE handling upon CAG validity state change TS 24.501CR5301
  • Clarify the allowed CAG list with validity condition TS 23.501CR4202

+ 19 more changes

Rel-19 11 changes
  • CAG information provisioning TS 23.501CR5808
  • CAG information Provisioning clarification of roaming support TS 23.501CR5856
  • 5G Femto Hosting Party acting as a CAG owner TS 23.501CR5667
  • Clarification on CAG information provisioning TS 23.501CR6080
  • CAG Information provisioning functionality TS 23.501CR6155
  • UDM functional description update for CAG information provisioning TS 23.501CR6214

+ 5 more changes

Defining Specifications

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

SpecificationTitleRelease
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 27.007 vk00 AT Command Interface for Mobile Terminals Rel-20 read
TS 28.622 vk40 Generic Network Resource Information Service Rel-20 read
TR 28.828 vi00 Charging Aspects for Non-Public Networks Rel-18 read
TS 31.102 vk00 USIM Application Specification Rel-20 read
TS 31.111 vj40 3GPP TS 31111 vj40: USIM Application Toolkit Rel-19 read
TS 32.255 vk30 5G Data Connectivity Converged Charging Rel-20 read
TS 32.422 vk30 Trace, MDT and UE Measurement Control Rel-20 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.545 vk10 NR Femto Security Architecture Rel-20 read
TS 33.745 vj10 Security Study for 5G NR Femto Rel-19 read
TS 33.819 vg10 5GS Security for Vertical & LAN Services Rel-16 read
TS 37.483 vj40 E1 Application Protocol (E1AP) Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.304 vj30 NR UE Idle and Inactive State Procedures Rel-19 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read
TS 38.413 vj40 NG Application Protocol (NGAP) Specification Rel-19 read
TS 38.423 vj40 NG-RAN Xn Application Protocol Rel-19 read
TS 38.463 vj00 E1 Application Protocol (E1AP) Rel-19 read
TS 38.473 vj40 F1 Application Protocol (F1AP) Rel-19 read