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

Glossary term · Network Slicing

NSAG

Network Slice Access Group

Network Slicing →

NSAG is a group identifier used in the RAN to associate a UE with a specific set of network slices, enabling common policies and optimizations for all UEs in that slice group.

Introduced
Rel-17
Where
Radio Access Network › NG-RAN (5G)
Specifications
12 specs
Also in
Core Network
NSAG Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Network Slice Access Group (NSAG) is a RAN-level concept introduced in 3GPP Release 17 to optimize Radio Access Network (RAN) procedures for network slicing. It is an identifier that groups together one or more Network Slice Selection Assistance Information (S-NSSAI) values. The core idea is that from the RAN's perspective, UEs that are allowed to access the same set of slices (i.e., the same NSAG) can be treated similarly for certain RAN procedures, allowing for more efficient resource management and signaling. The NSAG is configured in the RAN by the management system (OAM) and is communicated to the UE and the core network.

Operationally, the NSAG is used in several key RAN procedures. During the initial access, a UE may indicate its supported NSAG to the gNB in the RRC message, helping the RAN understand the slice grouping context early. More importantly, NSAG is utilized in paging optimization. When the core network (AMF) needs to page a UE in RRC_IDLE or RRC_INACTIVE state, it includes the UE's NSAG in the paging message sent to the RAN. The RAN can then broadcast the paging message only in cells that support the slices associated with that NSAG, rather than in all cells. This significantly reduces unnecessary paging overhead and improves battery life for UEs not in the target slice group. Furthermore, the RAN can use NSAG for radio resource allocation policies, connection establishment prioritization, and mobility settings that are common to all slices within the group.

The NSAG identifier is part of the UE context in both the core network and the RAN. The AMF determines the NSAG for a UE based on the subscribed and allowed S-NSSAIs and includes it in the UE context established with the gNB (e.g., via the NGAP interface). This allows the RAN to maintain a mapping between the UE, its allowed slices, and the corresponding NSAG. The use of NSAG effectively abstracts the potentially large and dynamic set of S-NSSAIs into a smaller number of stable groups, simplifying RAN implementations and reducing the signaling burden of handling individual slice identifiers in every RAN procedure.

Purpose & Motivation

NSAG was introduced to address RAN scalability and efficiency challenges posed by a large number of fine-grained network slices. In early 5G releases, the RAN had to handle individual S-NSSAIs for each UE, which could lead to signaling overhead and complex processing, especially for procedures like paging and mobility that are agnostic to the specific service but related to the slice group a UE belongs to. The RAN needed a way to aggregate slice-specific information to apply common policies without processing each slice individually.

The primary problem NSAG solves is inefficient paging. Without NSAG, when paging a UE, the RAN might have to broadcast the page in all cells, wasting radio resources and causing interference, because it doesn't know which cells support the UE's specific slices. NSAG allows the RAN to perform 'slice-aware paging,' targeting only relevant cells. This is crucial for network slicing to be efficient in the RAN. Furthermore, NSAG simplifies RAN implementation for slice-based radio resource management, allowing the gNB to configure common parameters (like dedicated random access resources or scheduling policies) per NSAG rather than per S-NSSAI, which is more scalable and manageable.

What changed in its specifications

The latest release-to-release comparison of specifications that define NSAG. 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 →

Technology family

Network slicing · Core Network › 5G Core

  1. Rel-15 Network Slice, Network Slice Instance (NSI), Network Slice Subnet, Network Slice Subnet Instance (NSSI), NSI ID, NSSAI, NSSF, S-NSSAI
  2. Rel-16 ENSI, GST, NSSAA, NSSAAF
  3. Rel-17 NSAC, NSACF, NSAG, NSSRG
  4. Rel-18 Alternative S-NSSAI

Also in this family (introduction release not pinned to a single defining specification): Service Profile, Slice Profile

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 3 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-17 introduced

Rel-17 first specifies NSAG: UE storage, handling and provision of NSAG information to lower layers, AMF-provided NSAG priority, and use in slice-based cell reselection and Random Access.

  • “A Network Slice AS Group is an identifier of a group of network slices which are associated with it.” TS 23.501 v17.15.0
  • “When providing NSAG Information to the UE, the AMF shall also provide the NSAG priority information for the NSAGs provided in the NSAG Information.” TS 23.501 v17.15.0
  • “the UE shall replace any stored NSAG information for the registered PLMN and its equivalent PLMN(s) or the registered SNPN with the new NSAG information” TS 24.501 v17.18.1
Rel-18 1 CR

NSAG information handling changed: the UE removes S-NSSAIs not in the configured NSSAI from it, stores it for equivalent PLMNs/SNPNs, and receives updated NSAG information containing the alternative S-NSSAI.

  • “The UE shall remove any S-NSSAI from the NSAG information which is not part of the configured NSSAI, if any.” TS 24.501 v18.14.0
  • “then the AMF provides updated NSAG information also including the Alternative S-NSSAI to the UE” TS 23.501 v18.12.0
  • Remove S-NSSAI from NSAG if S-NNSAI is not in configured NSSAI (Rel-18) TS 24.501CR4929
Rel-19 1 CR

NSAG handling was corrected in Rel-19: the NSAG capability bit number in the 5GMM capability IE was fixed, the NSSF attribute was renamed to "nsagInfos", and NSAG information comparison and storage text was revised.

  • Correction of faulty bit number for NSAG TS 24.501CR6617
  • “the NSSF shall include the "nsagInfos" attribute with NSAG information if available.” TS 29.531 v19.7.0
  • “If the UE supports NSAG, the UE shall set the NSAG bit to "NSAG supported" in the 5GMM capability IE” TS 24.501 v19.8.0

Defining Specifications

3GPP specifications that define or reference NSAG, 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 29.531 vk00 Nnssf Service Based Interface Stage 3 Rel-20 read
TS 37.320 vj40 MDT Overall Description (Stage 2) 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.321 vj40 NR MAC Protocol Specification Rel-19 read
TS 38.331 vj40 NR Radio Resource Control (RRC) 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.470 vj20 F1 Interface Specification for NG-RAN Rel-19 read
TS 38.473 vj40 F1 Application Protocol (F1AP) Rel-19 read