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

Glossary term · Network Slicing

NSSAAF

Network Slice-specific Authentication and Authorization Function

Network Slicing →

NSSAAF is the 5G Core Network function that acts as a proxy between the AMF and external AAA servers to manage authentication and authorization for a specific network slice.

Introduced
Rel-16
Where
Management
Specifications
9 specs
Also in
Core Network
NSSAAF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Network Slice-specific Authentication and Authorization Function (NSSAAF) is a dedicated logical function within the 5G Core Network (5GC) specified from 3GPP Release 16. Its primary role is to facilitate the Network Slice-Specific Authentication and Authorization (NSSAA) procedure. The NSSAAF does not perform the authentication itself but acts as a relay and orchestrator between the Access and Mobility Management Function (AMF) within the operator's trust domain and external Authentication, Authorization, and Accounting (AAA) servers that belong to the tenant or provider of a specific network slice. This architecture is fundamental to enabling multi-party and multi-domain network slicing scenarios.

Operationally, the NSSAAF receives NSSAA requests from the AMF via the service-based interface Nnssaaf_NSSAA. This request includes the UE's identity and the identifier of the requested network slice (S-NSSAI). The NSSAAF then initiates a dialogue with the appropriate external AAA server, which is identified based on the S-NSSAI. The communication with the external AAA server occurs over the N33 reference point. The NSSAAF transparently relays Extensible Authentication Protocol (EAP) packets between the UE (which is the EAP peer) and the external AAA server (which is the EAP server). The UE and the external AAA server conduct a full EAP authentication method (e.g., EAP-AKA', EAP-TLS), with the NSSAAF and AMF simply passing the packets. The NSSAAF is responsible for mapping the EAP session to the correct UE and AMF context.

The NSSAAF's key responsibilities include managing the state of the NSSAA procedure, enforcing timeouts, and translating the final result from the external AAA server (EAP Success/Failure) into a 3GPP-defined NSSAA result sent to the AMF. It also handles potential error conditions from the external AAA server. The function can be implemented as a standalone Network Function (NF) or can be combined with another NF, such as the Authentication Server Function (AUSF), depending on vendor implementation and network deployment choices. Its design emphasizes neutrality to the specific EAP method used, allowing slice tenants to employ the authentication mechanism that best suits their security requirements.

Purpose & Motivation

The NSSAAF was created to operationalize the concept of slice-specific authentication introduced with NSSAA. Without a dedicated function to manage the interaction with external AAA systems, the AMF would need to directly interface with a potentially unlimited number of tenant-specific AAA servers, each with different protocols and security requirements. This would create immense complexity, scalability issues, and security risks for the core network operator.

The NSSAAF solves this by providing a standardized, secure, and controlled intermediary point. It abstracts the complexity of external AAA interactions from the AMF, allowing the AMF to handle mobility and session management while delegating slice-specific security decisions. This separation of concerns is a classic architectural principle that enhances modularity and security. Furthermore, the NSSAAF provides a single point in the operator's network where policies regarding external connectivity (e.g., firewall rules, traffic policing for AAA messages) can be enforced. Its creation was motivated by the need to make network slicing practically deployable for enterprise and vertical use cases, where the slice tenant demands control over access authentication without requiring deep integration of their AAA systems into the MNO's core.

What changed in its specifications

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

Rel-19 adds satellite NG-RAN access text, LP-WUS/WUR assistance and disabling, ATUC RAT utilization control, and network-controlled slice selection with S-NSSAI time validity to TS 24.501. It also adds ATSSS Phase 4 multi-access and 5G ProSe multi-hop relay support.

Full comparison in TS 24.501 →

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 4 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-16 introduced

NSSAAF is introduced as a new 5G core function that relays EAP messages between the AMF and AAA-S/AAA-P for slice-specific authentication, with Nnssaaf services, N58/N59 reference points, selection and re-authentication/revocation notifications.

  • “The NSSAAF provides NSSAA service to the requester NF by relaying EAP messages towards a AAA-S or AAA-P and performing related protocol conversion as needed.” TS 23.501 v16.20.0
  • “The Network slice specific authentication and authorization function (NSSAAF) shall handle the Network Slice Specific Authentication requests from the serving AMF.” TS 33.501 v16.20.0
  • Introduce NSSAAF TS 29.510CR0343
Rel-17 specification text

In Rel-17 NSSAAF was extended to also serve the AUSF for primary authentication in SNPN (AIW service, N83 reference point), renamed to include SNPN, with updated notification and AAA handling.

  • “Within the 5GC, the NSSAAF offers services to the AMF and the AUSF via the Nnssaaf service-based interface.” TS 29.526 v17.9.0
  • “The NSSAAF provides AIW (AAA interworking) service to the requester NF by relaying EAP messages towards a AAA-S or AAA-P” TS 23.501 v17.15.0
  • “N83: Reference point between AUSF and NSSAAF.” TS 23.501 v17.15.0
Rel-18 1 CR

NSSAAF gained converged charging support toward CHF per S-NSSAI per UE, and its NSSAF selection rules for SNPN were corrected in this release.

  • “The NSSAAF shall support converged charging for Network Slice-Specific Authentication and Authorization procedure per S-NSSAI per UE.” TS 28.204 v18.1.1
  • “In the case of SNPN, NSSAAF selection is only applicable to 3GPP access.” TS 23.501 v18.12.0
  • Correction on NSSAAF Selection in case of SNPN TS 23.501CR5253
Rel-20 specification text

NSSAAF now also serves the SMF+PGW-C (EPC, Nnssaaf, N115) for slice-specific authentication, re-authentication and revocation notifications, extending its consumers beyond the AMF.

  • “Within the EPC, the NSSAAF offers services to the SMF+PGW-C via the Nnssaaf service-based interface.” TS 29.526 v20.1.0
  • “the NSSAAF shall notify the NF Service Consumer (i.e. the AMF or the SMF+PGW-C) by using the HTTP POST method” TS 29.526 v20.1.0
  • “N115: Reference point between SMF+PGW-C and the NSSAAF.” TS 23.501 v20.3.0

Defining Specifications

3GPP specifications that define or reference NSSAAF, 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 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 28.204 vi11 Charging management Rel-18 read
TR 28.843 vi10 Technical Report on Charging Aspects for Vertical Scenarios Rel-18 read
TS 29.526 vk10 Nnssaaf Service Interface Rel-20 read
TS 29.561 vk10 5G Network Interworking Procedures Rel-20 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.290 vk00 5G Charging Service-Based Architecture Rel-20 read
TR 32.847 vi00 Technical Report Rel-18 read