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

Glossary term · Network Slicing

NSAC

Network Slice Admission Control

Network Slicing →

NSAC is a control mechanism that ensures the number of user devices registered to a specific network slice does not exceed a configured maximum limit to maintain performance and prevent congestion.

Introduced
Rel-17
Where
Core Network › 5G Core
Specifications
6 specs
NSAC Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

Network Slice Admission Control (NSAC) is a fundamental control plane function introduced in 3GPP Release 17 to manage the scale and capacity of network slices. It operates by enforcing a maximum allowed number of User Equipments (UEs) that can be simultaneously registered to a given network slice instance (NSI). This is not a resource admission control for data traffic, but rather a registration-level admission control. The primary goal is to prevent a slice from becoming overloaded with registered UEs, which could degrade the quality of service for all users of that slice and potentially impact other slices sharing the same underlying infrastructure. NSAC is a policy-based mechanism, where the maximum number of UEs per slice is a key policy parameter defined by the network operator, often aligned with commercial or technical service level agreements (SLAs).

The NSAC function is typically implemented within the core network's control plane, interacting with key network functions like the Access and Mobility Management Function (AMF) and the Network Slice Admission Control Function (NSACF). When a UE initiates a registration procedure and requests a network slice, the AMF consults the NSAC mechanism to check if the UE can be admitted to the requested slice. This check involves verifying whether the current registration count for that slice is below the configured maximum limit. If the limit has not been reached, the registration is allowed, and the counter is incremented. If the limit is reached, the registration request for that specific slice may be rejected, or the UE may be directed to an alternative slice, depending on network policies and UE capabilities.

NSAC works in conjunction with the Network Slice Admission Control Function (NSACF), which is the entity responsible for maintaining the registration counts and enforcing the admission policies. The AMF communicates with the NSACF via service-based interfaces (e.g., Namf_Communication) to report registration and deregistration events. The NSACF maintains per-slice counters, updates them based on these events, and provides admission decisions to the AMF. This architecture centralizes the admission control logic, allowing for consistent policy enforcement across the network. NSAC also supports monitoring and reporting capabilities, enabling operators to track slice usage and make informed decisions about capacity planning and slice lifecycle management.

Purpose & Motivation

NSAC was created to address a critical gap in the initial 3GPP network slicing architecture defined in Release 15. While early releases provided the mechanisms to create and manage slices, they lacked robust controls to limit the scale of a slice in terms of connected users. Without such control, a popular slice (e.g., for a massive IoT service or a popular enterprise application) could experience an uncontrolled influx of UEs, leading to signaling storms, resource exhaustion, and performance degradation for all users on that slice and potentially on shared network functions. This posed a significant risk to network stability and the ability to guarantee isolated performance as promised by slicing.

The introduction of NSAC in Release 17 was motivated by the need for operators to offer reliable and predictable slice-based services with enforceable SLAs. It allows operators to define a 'capacity' for a slice not just in bandwidth, but in terms of supported devices, which is essential for commercial models (e.g., selling a slice to an enterprise for up to 10,000 devices). It solves the problem of slice overload by providing a hard limit, protecting the slice from being overwhelmed. Furthermore, it enables more efficient resource planning and prevents one slice from monopolizing common control plane resources, thereby upholding the principle of resource isolation that is foundational to network slicing.

What changed in its specifications

The latest release-to-release comparison of specifications that define NSAC. 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 first specifies Network Slice Admission Control, with an NSACF that is configured with a maximum number of UEs per S-NSSAI and checks and updates registered UE counts, plus roaming and EPC interworking support.

  • “The NSACF is configured with the maximum number of UEs and/or the maximum number of PDU Sessions allowed to be served per S-NSSAI subject to NSAC.” TS 23.501 v17.15.0
  • “The number of UEs per network slice availability check and update procedure is to update (i.e. increase or decrease) the number of UEs registered with an S-NSSAI” TS 23.502 v17.15.0
  • “Introducion of Network Slice Admission Control” TS 24.501 v17.18.1
Rel-18 specification text

Rel-18 extends NSAC with hierarchical, centralized and non-hierarchical architecture options, a Primary NSACF with quota/threshold-based UE admission and delegation, and NSAC service areas.

  • “Depending on the NSAC architecture deployed in the network, three options of NSAC procedures are defined:” TS 23.502 v18.14.0
  • “the Primary NSACF rejects the NSAC request. If the UE already Registered indication is included and if the Primary NSACF decided to store the UE entry” TS 23.502 v18.14.0
  • “There are two types of UE admission control: quota-based control or threshold-based control.” TS 23.501 v18.12.0
Rel-19 1 CR

NSAC gained support for Indirect Network Sharing and new hierarchical NSACF handling, including delegation of NSAC handling, VPLMN admission modes, and updated NSAC indications between NSACF and Primary NSACF.

  • “In the case of Indirect Network Sharing, the NSAC of the number of UEs for roaming UEs as specified in clause 4.2 also applies.” TS 29.536 v19.4.0
  • NSAC handling in Hierarchical architecture TS 23.502CR5104
  • “it indicates a list of S-NSSAI to delegate the NSAC handling to the NSACF” TS 29.536 v19.4.0
Rel-20 1 CR

TS 29.536 NSAC specification changed for hierarchical NSAC: primary/distributed NSACF roles, quota retrieval from primary NSACF, local maximum updates, and roaming admission modes were specified.

  • Quota retrieval by serving NSACF from primary NSACF in hierarchical NSAC deployment TS 29.536CR0162
  • “in hierarchical NSAC architecture, a distributed NSACF may interact with the primary NSACF to fetch the quota for number of UEs or number of PDU sessions” TS 29.536 v20.1.0

Defining Specifications

3GPP specifications that define or reference NSAC, 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.203 vi10 Charging management Rel-18 read
TS 29.122 vk10 T8 SCEF Service Exposure APIs Rel-20 read
TS 29.522 vk10 NEF Northbound Interface Rel-20 read
TS 29.536 vk10 Nnsacf Network Slice Admission Control Rel-20 read