Description
The Alternative S-NSSAI is a Rel-19 concept introduced in 3GPP TS 23.501 and referenced in TS 29.502 for the NSSF/NRF service-based interfaces. In 5G System (5GS) network slicing, a UE registers with the network and receives an Allowed NSSAI — a list of S-NSSAIs (each composed of an SST and optional SD) that the UE is permitted to use in the current Registration Area. Each S-NSSAI identifies a network slice instance (NSI) or a set of NSIs providing specific service characteristics. When a slice identified by an S-NSSAI in the Allowed NSSAI becomes temporarily unavailable — for example due to slice congestion, NSI failure, or resource constraints — the AMF needs a mechanism to redirect the UE's PDU session or service request to a functionally compatible slice rather than rejecting the request outright.
The Alternative S-NSSAI provides exactly this mechanism. For a given S-NSSAI in the Allowed NSSAI, the network (typically the NSSF or the AMF itself, based on operator policy and slice availability information) can associate one or more Alternative S-NSSAIs that are considered compatible — meaning they satisfy the same or overlapping service requirements (e.g., same slice/service type, comparable QoS, similar feature set). When the AMF detects that the original S-NSSAI is unavailable or congested, it replaces that S-NSSAI with the Alternative S-NSSAI in the Allowed NSSAI communicated to the UE, so that subsequent UE requests referencing the original slice are transparently mapped to the alternative one.
Architecturally, this involves several network functions. The NSSF (Network Slice Selection Function) determines the Allowed NSSAI and can provide alternative slice mappings based on slice availability and load. The AMF enforces the substitution and maintains the mapping for the duration of the UE's registration. The UDM stores subscription data including subscribed S-NSSAIs, which constrain which alternatives are permissible. The PCF may provide policy information that influences slice selection. TS 29.502 defines the service-based interface (Nnssf) messages used to request and return slice selection information, which in Rel-19 can carry alternative S-NSSAI information.
The mechanism operates at registration and at service request time. During registration, the AMF obtains the Allowed NSSAI; if some S-NSSAIs are unavailable, the AMF may include Alternative S-NSSAIs. When the UE later requests a PDU session for a slice that has been substituted, the AMF (and SMF) use the alternative to establish the session on a compatible NSI. This avoids session establishment failures and improves user experience during partial slice outages.
Key considerations include: compatibility criteria (the alternative must meet the UE's service requirements), operator policy (which alternatives are allowed), and consistency (the UE must be informed of the substitution so it uses the correct S-NSSAI in subsequent requests). The Alternative S-NSSAI is distinct from the concept of a mapped S-NSSAI used in roaming (which maps a visited-network S-NSSAI to a home-network S-NSSAI); the alternative is about availability-driven substitution within the same network.
Purpose & Motivation
Network slicing allows operators to run multiple logical networks on shared infrastructure, but slices are not always available — an NSI may be congested, undergoing maintenance, or partially failed. Before Rel-19, when an S-NSSAI in the Allowed NSSAI became unavailable, the network had limited options: it could reject the UE's PDU session establishment request, or the UE could be forced to re-register and obtain a new Allowed NSSAI. Both outcomes degrade service continuity and user experience, and re-registration is costly in terms of signaling and latency.
The Alternative S-NSSAI solves this by giving the network a graceful degradation path. Instead of failing a request, the AMF can substitute a compatible slice that is available, allowing the service to continue with equivalent or acceptable characteristics. This is particularly valuable for mission-critical services, massive IoT deployments, and scenarios where slice availability fluctuates due to dynamic resource allocation or failures.
The concept also supports operator flexibility: operators can define compatibility relationships between slices (e.g., an enhanced mobile broadband slice and a general-purpose slice) and let the network automatically fall back when the preferred slice is unavailable. This reduces manual intervention, improves resilience, and aligns with the broader 5G goal of dynamic, software-defined network management. Introduced in Rel-19, it reflects the maturation of network slicing from static provisioning toward adaptive, availability-aware slice management.
What changed in its specifications
The latest release-to-release comparison of specifications that define Alternative 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-19 added QoS monitoring enhancement for delay, congestion, and bitrate. It also added local offloading management for I-SMF, Indirect Network Sharing mappings, HPLMN session breakout roaming, and Edge Computing offload indicators.
Full comparison in TS 29.502 →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
- Alternative S-NSSAI builds on 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 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-18 introduces Alternative S-NSSAI: a compatible S-NSSAI the AMF uses to replace an unavailable or congested S-NSSAI (Network Slice Replacement), with NSSF/PCF/OAM provisioning, UE mapping and SM signalling.
- “Indicating a compatible S-NSSAI for an S-NSSAI in the Allowed NSSAI that the AMF uses to replace an S-NSSAI when the S-NSSAI is not available or congested” TS 23.501 v18.12.0
- “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 v18.12.0
- Introduction of Alternative S-NSSAI replacement determined by NSSF TS 23.501CR4036
Rel-19 adds AF-requested network slice replacement with Alternative S-NSSAI, including PCF/AMF handling, outcome reporting, and Alternative S-NSSAI deletion when S-NSSAI time validity indicates unavailability.
- “may request to replace a certain S-NSSAI (Replaced S-NSSAI) for a UE with another S-NSSAI (Alternative S-NSSAI) which is part of the UE subscription” TS 23.501 v19.9.0
- “If the Alternative S-NSSAI is not within the UE subscription, or is not supported in the UE Registration Area, the AMF shall notify the PCF” TS 23.501 v19.9.0
- Alternative S-NSSAI deletion upon S-NSSAI time validity information indicates that the S-NSSAI is not available TS 24.501CR6508
Alternative S-NSSAI handling extended: it is now an optional input in SMF/AMF service operations, and the PCF provides S-NSSAI availability information to the AMF via Npcf_AMPolicyControl_Update Notify or Create response.
- “Input, Optional: S-NSSAI, Alternative S-NSSAI, PCO, Requested PDU Session Type, 5GSM Core Network Capability” TS 23.502 v20.3.0
- “Input, Optional: PEI, S-NSSAI(s), Alternative S-NSSAI, Slice Area Restriction indication, PDU Session ID, N1 SM container” TS 23.502 v20.3.0
- “the PCF provides the S-NSSAI availability information (see clause 6.5) to AMF via Npcf_AMPolicyControl_Update Notify based on the implicit subscription from the AMF” TS 23.503 v20.3.0
Defining Specifications
3GPP specifications that define or reference Alternative S-NSSAI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 29.502 vk10 | 5G SMF Service Based Interface Stage 3 | Rel-20 read |