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

Glossary term · Network Slicing

NSSRG

Network Slice Simultaneous Registration Group

Network Slicing →

NSSRG is a group of network slices for which a single UE can maintain simultaneous active registrations, enabling it to support diverse service requirements concurrently without re-registering when switching services.

Introduced
Rel-17
Where
Core Network › 5G Core
Specifications
2 specs
NSSRG Description Purpose What changed Family Detected Changes Specifications

Description

The Network Slice Simultaneous Registration Group (NSSRG) is a 3GPP concept that defines a set of one or more Network Slice Instances (NSIs) for which a User Equipment (UE) can maintain simultaneous registration states. This mechanism is crucial for enabling a single UE to concurrently access services from different network slices, each potentially tailored for distinct service types such as enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), or massive IoT. The NSSRG is managed by the Access and Mobility Management Function (AMF) in the 5G Core Network (5GC). When a UE initiates a registration procedure, it can indicate its requested Network Slice Selection Assistance Information (NSSAI). The AMF, in conjunction with the Network Slice Selection Function (NSSF), determines the allowed NSSAI and, based on network policies and subscription data, can assign the UE to a specific NSSRG. The AMF maintains the UE's registration context for all slices within the assigned NSSRG.

Architecturally, the NSSRG concept is tightly integrated with the 5G registration and session management procedures. A UE registered to an NSSRG does not need to perform a new registration procedure when establishing a Protocol Data Unit (PDU) session on a different network slice within the same group. This reduces signaling overhead and latency for service access. The AMF holds the common registration context for the UE across the slices in the group, while individual User Plane Functions (UPFs) and Session Management Functions (SMFs) are selected per PDU session based on the specific slice. The NSSRG identifier is part of the UE's context in the AMF and the Unified Data Management (UDM).

The operation hinges on the AMF's ability to support multiple Network Slice Identifiers (S-NSSAIs) under a single registration context. During the initial registration or a registration update, if the UE's requested S-NSSAIs belong to the same NSSRG as per network configuration, the AMF can accept them under one Registration Area and one 5G-Globally Unique Temporary Identifier (5G-GUTI). For mobility, if a UE moves to an area where not all slices in its NSSRG are available, the AMF may need to modify the allowed NSSAI, but the registration for the group remains intact for the available slices. This provides a balance between service continuity and network resource optimization. The NSSRG is a key enabler for efficient multi-slice device operation, which is fundamental to realizing the 5G vision of a single physical network infrastructure supporting a multitude of virtualized networks with different characteristics.

Purpose & Motivation

The NSSRG was introduced to solve the problem of signaling inefficiency and service interruption when a UE needs to access multiple network slices. Prior to its introduction, a UE typically maintained a registration state per network slice. Switching between services on different slices could require explicit registration procedures for each slice, leading to increased signaling load on the network and latency for the user. This was particularly problematic for devices requiring simultaneous access to slices, such as a smartphone running a high-bandwidth video stream (eMBB slice) while also controlling a low-latency industrial sensor (URLLC slice).

The creation of NSSRG was motivated by the need for a more scalable and efficient registration model in a sliced network. It addresses the limitation of a one-to-one mapping between UE registration and a network slice, which does not scale well as the number of slices and UEs increases. By grouping slices that a device is likely to use together, the network can maintain a unified mobility and connection management state, drastically reducing the control plane signaling associated with registration, deregistration, and periodic registration updates. This is essential for network performance and battery life of devices.

Historically, this concept evolved from the single registration model used in earlier mobile generations and the initial 5G slice-aware registration. NSSRG provides a middle ground, offering the simultaneous access benefits of multiple registrations with the signaling efficiency of a single registration. It is a foundational capability for advanced use cases like network slicing for enterprise services, where a device may need seamless access to both a corporate slice and a public internet slice. Its introduction in Release 17 reflects the maturing of network slicing implementations towards more complex and realistic deployment scenarios.

What changed in its specifications

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

NSSRG is specified for the first time: subscription-based NSSRG information restricts which S-NSSAIs a UE may register simultaneously, with UE capability signalling and configuration via Configured NSSAI and NSSF.

  • “Support of subscription-based restrictions to simultaneous registration of network slices uses Network Slice Simultaneous Registration Group (NSSRG) information” TS 23.501 v17.15.0
  • “if NSSRG information is present in the subscription information, at least one NSSRG shall be associated with each of the S-NSSAIs in the subscription information.” TS 23.501 v17.15.0
  • “The AMF shall provide the UE with NSSRG information alongside the Configured NSSAI if NSSRG information is included in the subscription information” TS 23.501 v17.15.0
Rel-18 1 CR

Rel-18 changes NSSRG handling: UE requested NSSAI must share a common NSSRG across accesses, NSSRG info is provided to lower layers, and NSSRG updates and deletion procedures were refined.

  • “if the NSSRG information is available, the subset of configured NSSAI provided in the requested NSSAI shall be associated with at least one common NSSRG value.” TS 24.501 v18.14.0
  • “the S-NSSAIs of the requested NSSAI in the REGISTRATION REQUEST message over the current access and the allowed NSSAI over the other access are not associated with any common NSSRG value.” TS 24.501 v18.14.0
  • NSSRG restriction applicability for the other access type TS 24.501CR4708
Rel-19 1 CR

NSSRG handling was changed in NAS signalling: mapped S-NSSAIs are now provided for NSSRG information in more scenarios, and the UE sets the NSSRG supported bit in the 5GMM capability IE.

  • “If the UE supports the NSSRG, then the UE shall set the NSSRG bit to "NSSRG supported" in the 5GMM capability IE” TS 24.501 v19.8.0
  • “the AMF provides mapped S-NSSAI(s) for the configured NSSAI, the allowed NSSAI, the partially allowed NSSAI” TS 24.501 v19.8.0
  • Correction to NSSRG test case 9.1.13.1 TS 38.523-1CR5532
Rel-20 1 CR

NSSRG handling was extended to EPS: UEs must ensure requested NSSAI S-NSSAIs and PDN connections in EPS share a common NSSRG value, with matching NAS requested NSSAI rules.

  • “the S-NSSAIs in the Requested NSSAI share a common NSSRG with the S-NSSAIs of already established PDN connections” TS 23.501 v20.3.0
  • “PDN connections established in EPS shall share a common NSSRG value.” TS 23.501 v20.3.0
  • NSSRG handling for requested NSSAI considering PDN connection(s) in EPS TS 24.501CR7190

Defining Specifications

3GPP specifications that define or reference NSSRG, 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