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

Glossary term · Network Slicing

NSACF

Network Slice Admission Control Function

Network Slicing →

NSACF is the network function that enforces Network Slice Admission Control policy by tracking registered UEs per slice and providing admission decisions to the AMF to enforce slice capacity limits.

Introduced
Rel-17
Where
Core Network › 5G Core
Specifications
17 specs
Also in
Services, Management
NSACF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Network Slice Admission Control Function (NSACF) is a critical control plane network function introduced in 3GPP Release 17 as the central entity responsible for executing Network Slice Admission Control (NSAC) policies. It is a logical function that can be deployed as a standalone network element or collocated with other control plane functions. The primary role of the NSACF is to manage and enforce the maximum allowed number of User Equipments (UEs) registered to each network slice instance (NSI). It does this by maintaining accurate, real-time counters for UE registrations and deregistrations on a per-slice basis. The AMF, which handles UE registration requests, interacts with the NSACF to determine if a UE can be admitted to a requested slice.

The NSACF operates through a set of service-based interfaces, primarily exposing services to the AMF. When a UE initiates a registration procedure including a Network Slice Selection Assistance Information (NSSAI), the AMF invokes a service operation on the NSACF (e.g., Nnsacf_NSAC_Control service) to request an admission check. The NSACF receives this request, which includes the slice identifier (S-NSSAI), and checks its internal database or policy repository for the configured maximum UE limit and the current registration count for that slice. Based on this check, it returns an admission control decision (allow or reject) to the AMF. If allowed, the NSACF increments its internal counter. Conversely, when a UE deregisters or its registration context is released, the AMF notifies the NSACF, which then decrements the corresponding counter.

Architecturally, the NSACF is a stateful function that must ensure data consistency and reliability. It may interact with a Unified Data Repository (UDR) to persistently store slice admission control policy data and potentially the registration counts for recovery purposes. The NSACF's design also considers scalability and high availability, as it becomes a central point for slice admission control across the entire network. Its functionality is tightly integrated with the overall network slicing management system, including the Network Slice Selection Function (NSSF) and the Policy Control Function (PCF), to ensure a cohesive slice management and policy enforcement framework.

Purpose & Motivation

The NSACF was created to provide a dedicated, scalable, and centralized point for enforcing Network Slice Admission Control policies. Prior to its introduction, there was no standardized function to manage the scale of network slices in terms of connected devices. Relying on individual network functions like the AMF to locally enforce such limits would be inefficient, inconsistent, and difficult to manage network-wide. The NSACF solves this by centralizing the logic and state for slice admission, ensuring a single source of truth for slice registration counts across all AMFs in the network.

This centralization is crucial for several reasons. First, it guarantees consistent policy enforcement regardless of which AMF a UE attaches to, which is essential in a cloud-native, distributed core network. Second, it simplifies operations and policy management for network operators, as they can configure and update slice capacity limits in one logical function. Third, it enables advanced features like dynamic capacity adjustments and integration with network analytics. The NSACF's creation was a direct response to operator requirements for robust commercial slicing, where guaranteeing a slice is not oversubscribed is as important as guaranteeing its performance, making it a cornerstone for slice-as-a-service business models.

What changed in its specifications

The latest release-to-release comparison of specifications that define NSACF. 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-17 introduced

Rel-17 defines NSACF for the first time, with its role in tracking registered UEs and PDU Sessions per slice and returning admission decisions to AMF/SMF, plus its services and discovery.

  • “The NSACF keeps track of the current number of UEs registered for a network slice so that it can ensure it does not exceed” TS 23.501 v17.15.0
  • “The NSACF supports the following services.” TS 29.536 v17.6.0
  • TS23.501 KI#1 Network Slice Admission Control Function (NSACF) definition TS 23.501CR2679
Rel-18 1 CR

Rel-18 adds hierarchical NSACF architecture: NSACFs delegate admission requests to a Primary NSACF, which can adjust local maximums, with roles configured per S-NSSAI and registered in the NF profile.

  • “If the local maximum number of UEs is reached, the NSACF sends a delegation request to the Primary NSACF.” TS 23.502 v18.14.0
  • “the NSACF role (i.e. primary NSACF or distributed NSACF) is configured in the NSACF per S-NSSAI” TS 29.536 v18.8.0
  • Hierarchical NSACF architecture procedures TS 23.502CR3930
Rel-19 specification text

Rel-19 extends NSACF: it can be a monitoring-event source via NEF, supports event subscription filters, access-type-specific reports, multiple event reports (MERN), and primary-NSACF delegation of thresholds.

  • “If event filter(s) was provided for the subscription, the NSACF shall genereate the event reports accordingly.” TS 29.536 v19.4.0
  • “If both the NSACF and the NF consumer supports the "MERN" feature, the notification may contain multiple SAC Event reports.” TS 29.536 v19.4.0
  • “The primary NSACF may update UE admission threshold per S-NSSAI.” TS 29.536 v19.4.0
Rel-20 1 CR

NSACF gains new quota retrieval behaviour in hierarchical NSAC, where a serving NSACF queries the primary NSACF for allocated quota per PLMN and S-NSSAI.

  • “The serving NSACF shall send a POST request to the resource representing quota retrieval (i.e …/slices/quota‑allocs/query) in the primary NSACF.” TS 29.536 v20.1.0
  • Quota retrieval by serving NSACF from primary NSACF in hierarchical NSAC deployment TS 29.536CR0162
  • “if the local maximum number of UEs with at least one PDU session/PDN connection or local threshold is reached, the NSACF may interact with the Primary NSACF” TS 29.536 v20.1.0

Defining Specifications

3GPP specifications that define or reference NSACF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
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
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TS 26.942 vk00 Sustainable Media Metrics and Architectural Impacts for 5G Rel-20 read
TS 28.203 vi10 Charging management Rel-18 read
TR 28.843 vi10 Technical Report on Charging Aspects for Vertical Scenarios Rel-18 read
TS 28.879 vj10 OAM for Service Management Exposure Study Rel-19 read
TS 29.522 vk10 NEF Northbound Interface Rel-20 read
TS 29.536 vk10 Nnsacf Network Slice Admission Control 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.575 vk10 ADRF Service Based Interface 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
TS 32.291 vk10 5G Charging Service-Based Interface Rel-20 read