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

Glossary term · Network Slicing

NSSF

Network Slice Selection Function

Network Slicing →

NSSF is the 5G core network function that selects the appropriate network slice instance for a user based on subscription, requested service, and network conditions.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
9 specs
NSSF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Network Slice Selection Function (NSSF) is a critical component within the 5G Core (5GC) network architecture, specifically part of the control plane. Its primary role is to assist in the selection of a suitable Network Slice Instance (NSI) for a User Equipment (UE) during registration and session establishment procedures. The NSSF operates by evaluating slice selection information, which includes the Subscribed Network Slice Selection Assistance Information (S-NSSAI) requested by the UE, the Allowed NSSAI provided by the network, and the UE's subscription profile stored in the Unified Data Management (UDM) function. Based on this information, local operator policies, and the availability of network slice instances, the NSSF determines the specific NSI to serve the UE's session.

Architecturally, the NSSF interacts with other core network functions through service-based interfaces (SBIs), primarily using the Nnssf service. Key interactions include communication with the Access and Mobility Management Function (AMF) during the UE registration procedure. When an AMF receives a registration request containing a Requested NSSAI, it may query the NSSF to determine the Allowed NSSAI for the UE and to identify the set of Network Slice and AMF Set(s) or the specific AMF that can serve the requested slices. The NSSF's decision-making process considers the mapping between S-NSSAIs and the actual deployed NSIs, which are composed of managed Network Slice Subnet Instances (NSSIs).

The NSSF's functionality is vital for the practical realization of network slicing, a foundational 5G concept. It ensures that a UE is connected to a network slice that aligns with its service requirements, whether for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), or massive Machine-Type Communications (mMTC). By performing this selection, the NSSF enables efficient resource utilization, isolation between slices, and the delivery of tailored Quality of Service (QoS). Its operations are defined in 3GPP specifications such as TS 23.501 for the overall system architecture and TS 29.520 for its service-based interface definition.

Purpose & Motivation

The NSSF was introduced with 5G in 3GPP Release 15 to address the fundamental challenge of efficiently mapping diverse user service requests to logically isolated network slices. Pre-5G networks offered a largely monolithic architecture where all services were delivered over a single, uniform network infrastructure. This approach was insufficient for supporting the wide range of 5G use cases, which have drastically different technical requirements—from gigabit speeds for video streaming to millisecond latency for industrial automation and high connection density for IoT sensors.

The creation of the NSSF was motivated by the need for a dedicated, intelligent function to manage slice selection as a first-class procedure in the core network. Without it, the AMF or other functions would need embedded, complex logic to understand slice deployment topologies and subscriber entitlements, leading to scalability and management issues. The NSSF centralizes this intelligence, allowing for dynamic, policy-driven slice selection that can adapt to network load, slice availability, and commercial agreements. It solves the problem of how to automatically and accurately connect a device to the correct virtualized network segment out of many possible options, which is a prerequisite for delivering network slicing as a service.

What changed in its specifications

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

Rel-19 adds Vertical Federated Learning training and inference APIs to TS 29.520, along with signalling storm, QoS/policy, and roaming analytics subscriptions. It also extends NWDAF ML model provisioning, event subscription fields, and 308 Permanent Redirect responses.

Full comparison in TS 29.520 →

Architecture

Where it sits in the network

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 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

The NSSF is specified for the first time in Rel-15: it selects network slice instances and returns the Allowed NSSAI, AMF Set and NRF, and it offers the Nnssf_NSSelection and Nnssf_NSSAIAvailability services.

Rel-16 1 CR

NSSF behaviour was extended in Rel-16: it returns 403 SNSSAI_NOT_SUPPORTED when no slice instance matches, omits AuthorizedNssaiAvailabilityData for TAs with no authorized S-NSSAIs, and gains NRF-based discovery.

  • “If no slice instances can be found for the requested slice selection information or the requested slice mapping information, then the NSSF shall return a 403 Forbidden” TS 29.531 v16.11.0
  • “If there is no supported S-NSSAIs authorized by the NSSF for the TA, the NSSF shall not return the AuthorizedNssaiAvailabilityData” TS 29.531 v16.11.0
  • Correction of Network Slice selection with NSSF TS 23.501CR1483
Rel-17 specification text

NSSF behaviour was extended in Rel-17: it handles NSSRG restrictions, provides NSAG information and Target NSSAI, serves NWDAF consumers, and may use NWDAF analytics for slice selection.

  • “If subscribed NSSRG list is provided, the NSSF shall provide the compatible S-NSSAIs in the Allowed NSSAI” TS 29.531 v17.12.0
  • “If the AMF has indicated the support of NSAG by the UE, the NSSF shall include the "nsagInfoList" attribute” TS 29.531 v17.12.0
  • “The NSSF may provide support for Network Slice restriction and Network Slice instance restriction based on NWDAF analytics.” TS 23.501 v17.15.0
Rel-18 1 CR

NSSF gained Network Slice Replacement and Network Slice Instance Replacement: it detects unavailable or congested S-NSSAIs or NSIs, notifies subscribed consumers with an alternative S-NSSAI, and supports new notification features.

  • “the NSSF shall send Network Slice Replacement for the S-NSSAI to the NF service consumer if the NF service consumer has subscribed to this event” TS 29.531 v18.10.0
  • “the NSSF sends network slice availability notification for the S-NSSAI to the AMF” TS 23.501 v18.12.0
  • Introduction of Alternative S-NSSAI replacement determined by NSSF TS 23.501CR4036
Rel-19 specification text

NSSF discovery changed from local configuration only to optional NRF-based discovery with a new clause 6.3.28, and NSSF services gained NSAG info, Indirect Network Sharing slice mapping, and supported-events signalling.

  • “NF consumer (i.e. AMF) or SCP may utilise the NRF discovery service to discover the NSSF(s) and get the NF profile(s) of the NSSF(s).” TS 23.501 v19.9.0
  • “It also enables the NSSF to provide to the AMF the slice mapping information in the case of Indirect Network Sharing.” TS 29.531 v19.7.0
  • “When present, this IE shall indicate the supported NSSF events by the NSSF instance.” TS 29.510 v19.8.0
Rel-20 1 CR

A correction was made to the NSSF's NSSAI Availability Notification behaviour in TS 23.502 for Rel-20.

  • Correction for NSSF NSSAI Availability Notification TS 23.502CR5773

Defining Specifications

3GPP specifications that define or reference NSSF, 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 26.891 vg00 Media Distribution Services in 5G System Rel-16 read
TS 29.520 vk10 5G NWDAF Services Rel-20 read
TS 29.524 vk00 5GC to NAS Cause Mapping Specification Rel-20 read
TS 29.552 vk10 5G Network Data Analytics Procedures Rel-20 read
TS 29.574 vk10 DCCF Service Based Interface Rel-20 read
TS 29.576 vk10 MFAF Service Based Interface Rel-20 read
TS 32.255 vk30 5G Data Connectivity Converged Charging Rel-20 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read