Description
The Single Network Slice Selection Assistance Information (S-NSSAI) is a fundamental construct in the 5G System (5GS) that uniquely identifies a network slice. A network slice is a logical, end-to-end network tailored to meet the specific requirements of a service or customer. The S-NSSAI is used by the User Equipment (UE) and the network to select and associate the UE with the appropriate network slice instance during registration and session establishment procedures. It is a critical parameter carried in Non-Access Stratum (NAS) signaling messages between the UE and the Access and Mobility Management Function (AMF).
An S-NSSAI is composed of two parts: a mandatory Slice/Service Type (SST) and an optional Slice Differentiator (SD). The SST is an 8-bit value that indicates the expected network slice behavior in terms of features and services. Standardized SST values include 1 for enhanced Mobile Broadband (eMBB), 2 for Ultra-Reliable Low Latency Communications (URLLC), and 3 for massive IoT (mIoT). The SD is a 24-bit optional identifier used to differentiate among multiple network slices of the same SST, allowing operators to create further specialized slices within a broad category (e.g., different eMBB slices for enterprise and consumer services). The combination of SST and SD allows for fine-grained slice selection.
During initial registration, the UE provides a Requested NSSAI, which is a list of S-NSSAIs corresponding to the slices it wishes to access. The network validates these requests against the subscriber's Subscribed S-NSSAIs stored in the Unified Data Management (UDM). The AMF, in coordination with the Network Slice Selection Function (NSSF), selects the appropriate network slice instances and returns an Allowed NSSAI to the UE for use in the current registration area. This Allowed NSSAI is then used for subsequent session establishment with the Session Management Function (SMF). The S-NSSAI influences the selection of all other core network functions (SMF, PCF, UPF) and can be used to apply specific network policies, quality of service (QoS) profiles, and charging rules, enabling true end-to-end logical network isolation and customization.
Purpose & Motivation
S-NSSAI was introduced in 3GPP Release 15 as a core enabler of 5G network slicing, a revolutionary concept that allows a single physical network infrastructure to be partitioned into multiple virtual, independent logical networks. Prior to 5G, networks provided largely monolithic services; customizing the network for different service types (e.g., video streaming, autonomous driving, sensor networks) was complex and inefficient. S-NSSAI solves this by providing a simple, standardized identifier that allows both the device and the network to dynamically select a pre-configured slice with specific characteristics.
The creation of S-NSSAI was motivated by the diverse and stringent requirements of 5G use cases, which range from high bandwidth and low latency to massive connection density. It addresses the problem of how to efficiently direct traffic and apply tailored resources without building separate physical networks. By including the S-NSSAI in signaling, the 5G system can instantiate the correct set of network functions and policies on a per-session basis. This enables operators to offer Network-as-a-Service (NaaS), support enterprise private networks, and optimize resource utilization, thereby unlocking new revenue streams and meeting the performance demands of modern applications.
What changed in its specifications
The latest release-to-release comparison of specifications that define S-NSSAI. Each summary describes the whole specification, not only this term.
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 →Rel-18 adds ECS authentication methods, ECS supported PLMNs information, and carriage return handling in Network Name. It adds URSP provisioning text for EPS support and removes an extended DRX restriction for RedCap UEs in RRC_INACTIVE state.
Full comparison in TS 24.008 →Architecture
Technology family
Network slicing · Core Network › 5G Core
- Rel-15 Network Slice, Network Slice Instance (NSI), Network Slice Subnet, Network Slice Subnet Instance (NSSI), NSI ID, NSSAI, NSSF, S-NSSAI
- Rel-16 ENSI, GST, NSSAA, NSSAAF
- Rel-17 NSAC, NSACF, NSAG, NSSRG
- Rel-18 Alternative S-NSSAI
Also in this family (introduction release not pinned to a single defining specification): Service Profile, Slice Profile
- S-NSSAI extended by NSSAI
“An NSSAI is a set of supported S-NSSAI(s)” TS 28.541
- S-NSSAI extended by Alternative S-NSSAI
“The Network Slice Replacement feature is used to temporarily replace an S-NSSAI with an Alternative S-NSSAI when an S-NSSAI becomes unavailable or congested in the 5GC.” TS 23.501
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 sourcesDocumented 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.
S-NSSAI is specified for the first time in Rel-15: a slice identifier made of SST and optional SD, used in NSSAI, registration, session management and congestion control.
- “Within a PLMN, a network slice is identified by an S-NSSAI, which is comprised of a slice/service type (SST) and a slice differentiator (SD).” TS 24.501 v15.7.0
- “An S-NSSAI with a non-standard value identifies a single Network Slice within the PLMN with which it is associated.” TS 23.501 v15.13.0
- Introducing the S-NSSAI definition TS 23.003CR0485
S-NSSAI handling was extended in Rel-16: rejected S-NSSAIs gain NSSAA-related cause values, S-NSSAI becomes an access category criteria type, and network slice identification now covers SNPNs.
- “Rejected NSSAI for the failed or revoked NSSAA: A set of S-NSSAI(s) which is sent by the AMF with the rejection cause” TS 24.501 v16.15.0
- “the access attempt matches access category criteria type S-NSSAI if the S-NSSAI requested by the UE during the PDU session establishment procedure” TS 24.501 v16.15.0
- “the AMF shall execute the Network-initiated Deregistration procedure described in clause 4.2.2.3.3 of TS 23.502 [3]” TS 23.501 v16.20.0
Rel-17 changed S-NSSAI handling: rejected S-NSSAIs now carry mapped HPLMN S-NSSAIs and back-off timers, the mapped S-NSSAI definition was extended, and UPF resource allocation can be based on S-NSSAI.
- “Each rejected S-NSSAI also includes the mapped HPLMN S-NSSAI if available.” TS 24.501 v17.18.1
- “UPF allocates resources based on the Network Instance and S-NSSAI and it is supported according to TS 29.244 [65].” TS 23.501 v17.15.0
- Excluding the S-NSSAI(s) in the pending NSSAI from the requested NSSAI TS 24.501CR2681
Rel-18 extends S-NSSAI handling with partially allowed/rejected NSSAI, Alternative S-NSSAI replacement, and S-NSSAI time and location validity information, along with LADN per DNN and S-NSSAI.
- “The AMF uses the Alternative S-NSSAI received in the notification from the NSSF, or from OAM or from the PCF.” TS 23.501 v18.12.0
- “When the S-NSSAI time validity information of an S-NSSAI indicates that the S-NSSAI becomes available again, the AMF shall update the allowed NSSAI” TS 24.501 v18.14.0
- Introduction of partially Allowed NSSAI and Partially Rejected S-NSSAI TS 23.501CR4035
Rel-19 extends mapped S-NSSAI handling to certain EHPLMNs, and adds network slice replacement, alternative S-NSSAI handling and S-NSSAI-related procedures for the S-NSSAI.
- “to which an S-NSSAI of the registered PLMN (in roaming scenarios and in certain EHPLMNs, as specified in clause 4.6.1)” TS 24.501 v19.8.0
- “the network need not provide any mapped S-NSSAIs. If the network provides mapped S-NSSAIs, it shall do this as specified for case a) above.” TS 24.501 v19.8.0
- Handling of mapped S-NSSAI in EHPLMN case TS 24.501CR6680
S-NSSAI handling was refined: the AMF must now provide S-NSSAI location validity information in Registration accept, and the UE includes alternative S-NSSAI in the UL NAS TRANSPORT message on PDU session re-establishment.
- “the UE includes the alternative S-NSSAI in the S-NSSAI IE of the UL NAS TRANSPORT message for PDU session re-establishment.” TS 24.501 v20.1.0
- Corrections for S-NSSAI location validity information description TS 24.501CR7194
- Processing of URSP rules in EPS when multiple S-NSSAI share a DNN TS 23.501CR6491
Defining Specifications
3GPP specifications that define or reference S-NSSAI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.435 vk00 | Network Slice Capability Enablement (NSCE) Architecture | Rel-20 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TR 23.745 vh00 | Study on App Layer Support for Factories of the Future in 5G | Rel-17 read |
| TR 23.758 vh00 | Study on Edge Application Architecture | Rel-17 read |
| TS 24.008 vk10 | NAS Call, Mobility and Session Procedures | 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.483 vk10 | Mission Critical Services Management Objects | Rel-20 read |
| TS 24.484 vk10 | Mission Critical Services Configuration Management | Rel-20 read |
| TS 24.501 vk10 | 5GS NAS Protocol Specification | Rel-20 read |
| TS 24.526 vk00 | 5GS UE Policies | Rel-20 read |
| TS 24.549 vj20 | SEAL Network Slice Capability Enablement Protocol | Rel-19 read |
| TS 24.575 vj00 | UE Pre-configuration for MBS | Rel-19 read |
| TS 24.890 vg00 | 5G NAS Protocol for 5GS Stage 3 | Rel-16 read |
| TS 28.202 vj00 | 5G Network Slice Management Charging | Rel-19 read |
| TS 28.203 vi10 | Charging management | Rel-18 read |
| TS 28.204 vi11 | Charging management | Rel-18 read |
| TS 28.535 vj00 | Closed Control Loop Assurance Management | Rel-19 read |
| TR 28.833 vi01 | Technical Report on 5G LAN-type Service Management | Rel-18 read |
| TR 28.836 vi00 | Technical Report on Intent Driven Management | Rel-18 read |
| TR 28.843 vi10 | Technical Report on Charging Aspects for Vertical Scenarios | Rel-18 read |
| TS 29.122 vk10 | T8 SCEF Service Exposure APIs | 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.512 vk10 | Session Management Policy Control Service Stage 3 | Rel-20 read |
| TS 29.513 vk10 | 5G PCC Signalling Flows | Rel-20 read |
| TS 29.514 vk10 | Policy Authorization Service | Rel-20 read |
| TS 29.518 vk10 | AMF Service Based Interface | Rel-20 read |
| TS 29.519 vk10 | 5G UDR Policy and Application Data Services | Rel-20 read |
| TS 29.520 vk10 | 5G NWDAF Services | Rel-20 read |
| TS 29.521 vk10 | Binding Support Management Service | Rel-20 read |
| TS 29.522 vk10 | NEF Northbound Interface | Rel-20 read |
| TS 29.523 vk10 | Policy Control Event Exposure Service | Rel-20 read |
| TS 29.532 vk00 | Nmbsmf Service Based Interface Specification | Rel-20 read |
| TS 29.543 vk10 | Data Transfer Policy Control Services | Rel-20 read |
| TS 29.554 vk10 | BDT Policy Control Service | Rel-20 read |
| TS 29.561 vk10 | 5G Network Interworking Procedures | Rel-20 read |
| TS 29.581 vk00 | Nmbstf Service Based Interface Stage 3 | Rel-20 read |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 read |
| TS 31.105 vj20 | Slice Subscriber Identity Module (SSIM) Application | Rel-19 read |
| TS 31.111 vj40 | 3GPP TS 31111 vj40: USIM Application Toolkit | Rel-19 read |
| TS 31.127 vj00 | UE Application Behavioural Tests for Non-Removable UICC | Rel-19 read |
| TR 31.826 vi00 | Technical Report | Rel-18 read |
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TR 32.847 vi00 | Technical Report | Rel-18 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 |
| TR 33.739 vi10 | Study on security enhancement of support for | Rel-18 read |
| TS 33.749 vj00 | Study on security aspects of edge computing enhancement | 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.300 vj40 | NR and NG-RAN Overall 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 |