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.
Key Features
- Uniquely identifies a network slice via SST and optional SD
- Carried in NAS signaling for slice selection during UE registration
- Enables network to select slice-specific AMF, SMF, PCF, and UPF instances
- Supports standardized Slice/Service Types (eMBB, URLLC, MIoT)
- Allows operators to define multiple differentiated slices per SST
- Integrates with subscriber data (UDM) for slice authorization
Evolution Across Releases
Introduced S-NSSAI as the fundamental identifier for network slicing in the first 5G system specification. Defined the structure with SST and SD, and specified its use in UE registration and PDU session establishment procedures to enable selection of slice-specific network functions and resources.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.435 | 3GPP TS 23.435 |
| TS 23.501 | 3GPP TS 23.501 |
| TS 23.700 | 3GPP TS 23.700 |
| TS 23.745 | 3GPP TS 23.745 |
| TS 23.758 | 3GPP TS 23.758 |
| TS 24.008 | 3GPP TS 24.008 |
| TS 24.301 | 3GPP TS 24.301 |
| TS 24.302 | 3GPP TS 24.302 |
| TS 24.483 | 3GPP TS 24.483 |
| TS 24.484 | 3GPP TS 24.484 |
| TS 24.501 | 3GPP TS 24.501 |
| TS 24.526 | 3GPP TS 24.526 |
| TS 24.549 | 3GPP TS 24.549 |
| TS 24.575 | 3GPP TS 24.575 |
| TS 24.890 | 3GPP TS 24.890 |
| TS 28.202 | 3GPP TS 28.202 |
| TS 28.203 | 3GPP TS 28.203 |
| TS 28.204 | 3GPP TS 28.204 |
| TS 28.535 | 3GPP TS 28.535 |
| TS 28.833 | 3GPP TS 28.833 |
| TS 28.836 | 3GPP TS 28.836 |
| TS 28.843 | 3GPP TS 28.843 |
| TS 29.122 | 3GPP TS 29.122 |
| TS 29.507 | 3GPP TS 29.507 |
| TS 29.508 | 3GPP TS 29.508 |
| TS 29.512 | 3GPP TS 29.512 |
| TS 29.513 | 3GPP TS 29.513 |
| TS 29.514 | 3GPP TS 29.514 |
| TS 29.518 | 3GPP TS 29.518 |
| TS 29.519 | 3GPP TS 29.519 |
| TS 29.520 | 3GPP TS 29.520 |
| TS 29.521 | 3GPP TS 29.521 |
| TS 29.522 | 3GPP TS 29.522 |
| TS 29.523 | 3GPP TS 29.523 |
| TS 29.532 | 3GPP TS 29.532 |
| TS 29.543 | 3GPP TS 29.543 |
| TS 29.554 | 3GPP TS 29.554 |
| TS 29.561 | 3GPP TS 29.561 |
| TS 29.581 | 3GPP TS 29.581 |
| TS 29.890 | 3GPP TS 29.890 |
| TS 31.105 | 3GPP TR 31.105 |
| TS 31.111 | 3GPP TR 31.111 |
| TS 31.127 | 3GPP TR 31.127 |
| TS 31.826 | 3GPP TR 31.826 |
| TS 32.240 | 3GPP TR 32.240 |
| TS 32.847 | 3GPP TR 32.847 |
| TS 32.899 | 3GPP TR 32.899 |
| TS 33.117 | 3GPP TR 33.117 |
| TS 33.739 | 3GPP TR 33.739 |
| TS 33.749 | 3GPP TR 33.749 |
| TS 37.473 | 3GPP TR 37.473 |
| TS 37.483 | 3GPP TR 37.483 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.413 | 3GPP TR 38.413 |
| TS 38.423 | 3GPP TR 38.423 |
| TS 38.463 | 3GPP TR 38.463 |
| TS 38.473 | 3GPP TR 38.473 |