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

Glossary term · Network Slicing

NSSAI

Network Slice Selection Assistance Information

Network Slicing →

NSSAI is the 3GPP parameter that identifies the set of network slices a UE requests, consisting of one or more S-NSSAIs, which the network uses to route the connection to the appropriate slice-supporting functions.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
32 specs
Also in
Radio Access Network, Services, Management, Security
NSSAI Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

Network Slice Selection Assistance Information (NSSAI) is a fundamental concept and data structure in 5G System (5GS) architecture, introduced in 3GPP Release 15. It is the mechanism by which a User Equipment (UE) communicates its desired network slice(s) to the network during registration and session establishment procedures. An NSSAI is not a single identifier but a collection, typically containing one or more Single Network Slice Selection Assistance Information (S-NSSAI) elements. Each S-NSSAI is the unique identifier for a specific network slice instance or slice type that a UE is permitted to access.

An S-NSSAI itself is composed of two parts: a Slice/Service Type (SST) and an optional Slice Differentiator (SD). The SST is a mandatory 8-bit field that indicates the expected network slice behavior in terms of features and services (e.g., enhanced Mobile Broadband - eMBB, Ultra-Reliable Low Latency Communications - URLLC, Massive IoT - MIoT). The SD is an optional 24-bit field used to differentiate among multiple network slice instances of the same SST, allowing an operator to deploy several slices for the same service type but for different tenants or use cases. The UE obtains the S-NSSAIs it is allowed to use from its subscription profile, often configured via the home operator.

During the initial registration procedure, the UE includes a Requested NSSAI in the Registration Request message sent to the Access and Mobility Management Function (AMF) via the (R)AN. The Requested NSSAI contains the S-NSSAIs the UE wishes to register for in the current registration area. The AMF, in conjunction with the Network Slice Selection Function (NSSF) and subscription data from the Unified Data Management (UDM), validates these requests. The network then responds with an Allowed NSSAI, which is the set of S-NSSAIs the UE is permitted to use in the current registration area. The UE stores this Allowed NSSAI and includes a subset of it, called the Configured NSSAI for the serving Public Land Mobile Network (PLMN), in subsequent registration and PDU Session Establishment requests. This process ensures the UE is connected to the correct AMF and Session Management Function (SMF) instances that support the requested slices, enabling the tailored connectivity and resource allocation that defines network slicing.

Purpose & Motivation

NSSAI was created to solve the critical problem of slice selection and routing in a 5G network where multiple logical networks (slices) coexist on shared physical infrastructure. In pre-5G systems, a UE simply attached to "the network." With network slicing, a UE may need access to several distinct logical networks simultaneously—for example, one for regular internet browsing (eMBB), one for a corporate VPN, and one for a low-latency gaming service. The network needed a standardized way for the UE to signal which of these logical networks it required for a given communication context.

The NSSAI mechanism provides this signaling. It addresses the limitation of earlier networks which lacked a native, standardized identifier for service-specific network partitions. Without NSSAI, implementing slicing would require non-standard, proprietary signaling or inefficient over-the-top solutions. NSSAI enables efficient network resource utilization by allowing the (R)AN and core network to direct traffic to the specific set of network functions (AMF, SMF, UPF, etc.) instantiated for a slice. This is essential for meeting the diverse Key Performance Indicators (KPIs) of different services, as it ensures the UE's data plane and control plane are handled by functions configured with the appropriate policies (e.g., latency, bandwidth, security). Its introduction was a cornerstone in making the 5G vision of customized logical networks a practical reality.

What changed in its specifications

The latest release-to-release comparison of specifications that define NSSAI. 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.301Rel-18 → Rel-19

Rel-19 adds store-and-forward satellite operation for NTN, control plane CIoT data overhead reduction via EMM TRANSPORT and Data container IE, and RAT utilization control. It also adds disaster roaming indications and MINT-EPS support, plus MPS priority for messaging paging.

Full comparison in TS 24.301 →

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

  • NSSAI builds on S-NSSAI
    “An NSSAI is a set of supported S-NSSAI(s)” TS 28.541

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 6 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-15 introduced

NSSAI is specified for the first time as a collection of S-NSSAIs, in Configured, Requested and Allowed forms, used by the UE and network to select AMF and slices.

  • “The NSSAI is a collection of S-NSSAIs. An NSSAI may be a Configured NSSAI, a Requested NSSAI or an Allowed NSSAI.” TS 23.501 v15.13.0
  • “Requested NSSAI: NSSAI provided by the UE to the Serving PLMN during registration.” TS 23.501 v15.13.0
  • “Configured NSSAI: NSSAI provisioned in the UE applicable to one or more PLMNs.” TS 23.501 v15.13.0
Rel-16 1 CR

Rel-16 extends NSSAI handling: a new Pending NSSAI for NSSAA, rejected NSSAI for failed/revoked NSSAA, SNPN-scoped configured/allowed NSSAI, and revised rules for building the requested NSSAI.

  • “Pending NSSAI: NSSAI provided by the Serving PLMN during a Registration procedure, indicating the S-NSSAI(s) for which the network slice-specific authentication and authorization procedure is pending.” TS 23.501 v16.20.0
  • “The UE does not include in the requested NSSAI any of the S-NSSAIs from the pending NSSAI that the UE stores, regardless of the access type.” TS 24.501 v16.15.0
  • Handling of pending NSSAI TS 23.501CR2268
Rel-17 specification text

Rel-17 changed NSSAI handling: a Target NSSAI is introduced for NG-RAN steering, NSSRG constraints apply to allowed, requested and configured NSSAI, and rejected NSSAI can use an extended IE.

  • “Target NSSAI: NSSAI provided by the Serving PLMN to the NG-RAN to cause the NG-RAN to attempt to steer the UE” TS 23.501 v17.15.0
  • “When S-NSSAIs have associated NSSRG information, then the S-NSSAIs in the Allowed NSSAI shall share at least one NSSRG.” TS 23.501 v17.15.0
  • “the rejected NSSAI shall be included in the Extended rejected NSSAI IE in the REGISTRATION ACCEPT message” TS 24.501 v17.18.1
Rel-18 1 CR

Rel-18 extends NSSAI handling with Partially Allowed and Partially Rejected NSSAI, Alternative NSSAI and on-demand NSSAI, plus new UE storage and AMF handling rules, and a revised Target NSSAI.

  • “There can be at most seven S-NSSAIs in the Partially Allowed NSSAI and at most seven S-NSSAIs rejected partially in the RA” TS 23.501 v18.12.0
  • Introduction of partially Allowed NSSAI and Partially Rejected S-NSSAI TS 23.501CR4035
  • “The allowed NSSAI, the partially allowed NSSAI and the rejected NSSAI shall be included in the CONFIGURATION UPDATE COMMAND message” TS 24.501 v18.14.0
Rel-19 1 CR

NSSAI handling changed in Rel-19: mapped S-NSSAIs are now provided for requested, allowed and configured NSSAIs, not only when roaming, and the UE locally sets a missing mapped S-NSSAI equal to the received S-NSSAI.

  • “the UE shall locally set the mapped S-NSSAI to the same value as the received S-NSSAI” TS 24.501 v19.8.0
  • “if the mapped S-NSSAI(s) associated to requested NSSAI are missing, the AMF shall locally set the mapped S-NSSAI to the same value as the received S-NSSAI” TS 24.501 v19.8.0
  • Requested NSSAI includeds S-NSSAI from partially allowed NSSAI TS 24.501CR6906
Rel-20 2 CRs

Rel-20 adds requirements on how the UE builds the Requested NSSAI (common NSSRG with PDN connections in EPS) and changes how NSSAI-related information is handled in configuration update.

  • “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
  • NSSRG handling for requested NSSAI considering PDN connection(s) in EPS TS 24.501CR7190
  • Update in rejected NSSAI upon a failed or revoked NSSAA TS 24.301CR4710

Defining Specifications

3GPP specifications that define or reference NSSAI, 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 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 24.301 vk10 EPS NAS Mobility and Session Management Rel-20 read
TS 24.302 vj00 Access to EPC via non-3GPP networks; Stage 3 Rel-19 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 24.890 vg00 5G NAS Protocol for 5GS Stage 3 Rel-16 read
TS 26.501 vk00 5G Media Streaming Architecture Rel-20 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TS 26.891 vg00 Media Distribution Services in 5G System Rel-16 read
TS 28.202 vj00 5G Network Slice Management Charging Rel-19 read
TS 28.541 vk41 5G Network Resource Model Stage 2/3 Rel-20 read
TS 28.801 vf10 Management and Orchestration of Network Slicing Rel-15 read
TS 29.503 vk10 UDM Service Based Interface Rel-20 read
TS 29.507 vk10 Access and Mobility Policy Control Rel-20 read
TS 29.508 vk10 Session Management Event Exposure Service Rel-20 read
TS 29.513 vk10 5G PCC Signalling Flows Rel-20 read
TS 29.518 vk10 AMF Service Based Interface Rel-20 read
TS 29.541 vk00 NEF South-Bound Interfaces for NIDD and SMS Rel-20 read
TS 29.562 vk10 HSS Nhss Services for IMS and GBA Rel-20 read
TS 29.890 vg00 CT3 5G System Technical Report Rel-16 read
TS 31.111 vj40 3GPP TS 31111 vj40: USIM Application Toolkit Rel-19 read
TS 32.899 vf10 5G Charging Architecture Study Rel-15 read
TS 33.117 vk20 Catalogue of Security Requirements and Tests Rel-20 read
TS 33.501 vk30 5G Security Architecture Rel-20 read
TS 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TS 37.473 vj00 W1 Application Protocol (W1AP) Specification Rel-19 read
TS 37.483 vj40 E1 Application Protocol (E1AP) 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
TS 38.509 vj00 5GS UE Special Conformance Test Functions Rel-19 read