NSCE

Network Slice Capability Enablement

Network Slicing →
Introduced in Rel-17 Also in: Core Network

NSCE is a framework for enabling and exposing network slice capabilities to applications, allowing them to discover, request, and utilize specific slice features.

Category
Network Slicing
Introduced
Rel-17
Where
Services › Codecs
Also touches
1 segments
Specifications
10 specs
NSCE Description Purpose Detected Changes Specifications

Description

Network Slice Capability Enablement (NSCE) is a comprehensive framework introduced in 3GPP Release 17 to facilitate the interaction between applications (or vertical industry systems) and the underlying 5G network slicing capabilities. It operates as an intermediary layer, translating high-level application requirements into specific network slice selection and configuration parameters that the 5G core network can understand and provision. The architecture involves several key functional components, primarily the NSCE Capability Exposure Function (NSCE-CEF) and the NSCE Application Function (NSCE-AF). The NSCE-CEF is responsible for exposing the network's slice capabilities, such as available slice types, performance characteristics (latency, bandwidth), and service area coverage, to authorized external entities. The NSCE-AF, residing in the application domain, formulates service requests based on application needs and communicates with the NSCE-CEF via standardized APIs, such as those defined in TS 29.549.

The workflow begins with capability discovery, where an application queries the NSCE-CEF to understand what slice capabilities are available in a given geographical area. Based on this information, the application can then request the enablement of a specific network slice instance or the utilization of an existing one that matches its requirements. The NSCE framework handles the mapping of application-level parameters (e.g., 'ultra-reliable low-latency communication for factory automation') to technical network slice selection assistance information (NSSAI) and potentially interacts with the Network Slice Selection Function (NSSF) and Policy Control Function (PCF) within the 5G core to ensure the appropriate slice is selected and policies are applied for the user equipment (UE). This process includes lifecycle management aspects, allowing for modification or termination of slice usage as application sessions evolve.

NSCE's role is pivotal in realizing the full economic potential of 5G network slicing for vertical industries. It moves beyond simple slice provisioning by the operator, enabling a dynamic, demand-driven model where applications can actively participate in the slice selection and configuration process. This requires robust authentication, authorization, and accounting (AAA) mechanisms, as defined in the relevant security specifications, to ensure that only authorized applications can access and control network resources. By providing a standardized interface for slice capability exposure, NSCE reduces integration complexity for application developers and enables new business models, such as slice-as-a-service, where verticals can on-demand access tailored network performance guarantees.

Purpose & Motivation

NSCE was created to address a critical gap in the initial 5G network slicing architecture defined in Releases 15 and 16. While those releases standardized the core mechanisms for creating and managing network slices within the operator's domain, they provided limited, non-standardized means for external applications and vertical industry customers to interact with these slices. The lack of a standardized exposure interface meant each operator had to develop custom APIs, leading to fragmentation, high integration costs for application providers, and an inability to create portable applications across different operator networks. This hindered the commercialization of network slicing, particularly for enterprise and IoT use cases which require programmatic access to network resources.

The primary problem NSCE solves is the disconnection between the technical implementation of network slices and the business or service logic of applications. Before NSCE, an enterprise might have to engage in lengthy manual processes with an operator to procure a slice with specific characteristics. NSCE automates and standardizes this interaction, enabling applications to dynamically discover and request network capabilities that match their real-time needs. This is essential for use cases like automated guided vehicles (AGVs) in a smart factory, where the application software needs to guarantee a certain level of network performance before initiating a critical operation. The motivation was to unlock the revenue potential of 5G for operators by making slicing easily consumable, fostering an ecosystem of slice-aware applications, and accelerating the adoption of 5G in vertical markets such as manufacturing, healthcare, and transportation.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (36 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-17 3 changes

In Release 17, the Network Slice Capability Enablement (NSCE) function was formally introduced, replacing the previous NSCM terminology. The release specified the architecture and procedures for the NSCE service, including its API, and defined key capabilities such as policy harmonization, slice API configuration, performance monitoring, and predictive slice modification for edge deployments.

  • Terminology replacement of NSCM with NSCE TS 29.549CR0059
  • Resolution of the Editor’s note for Network slice capability Enablement API. TS 29.549CR0084
  • Modification of data type for Network slice capability Enablement API TS 29.549CR0094
Rel-18 32 changes

In Release 18, the NSCE function introduced new capabilities including predictive slice modification for edge deployments to proactively trigger changes and avoid service degradation, and the formal definition of the NSCE_ServiceContinuity API. The release also expanded existing services with updates to lifecycle management and discovery APIs, while providing corrections and clarifications across numerous other NSCE service APIs such as those for fault diagnosis and policy management.

  • Retrieve data and information from NSCE client TS 24.549CR0019
  • Notify slice modification in edge based NSCE deployments TS 24.549CR0025
  • Definition of service operation clause of the NSCE_ServiceContinuity API TS 29.435CR0017
  • Definition of the API clause of the NSCE_ServiceContinuity API TS 29.435CR0018
  • Update on NSCE_NetSliceLifeCycleMngt API TS 29.435CR0040
  • Update on NSCE_ManagementServiceDiscovery API TS 29.435CR0041

+ 26 more changes

Rel-19 1 change

In Release 19, the specific new feature for the Network Slice Capability Enablement (NSCE) function is "Network Slice Information delivery," which sends Network Slice information to the VAL server and NSCE client. This addition formalizes a dedicated procedure for delivering slice-related information as part of the NSCE service's capabilities. The release also included a minor editorial correction to a related YAML file's external documentation reference.

  • TS version corrected in the externalDocs field of the TS29435_NSCE_NSInfoDelivery.yaml file. TS 29.435

Explore further

Broader topics and technologies where NSCE plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.435 vj30 Network Slice Capability Exposure Procedures Rel-19
TS 23.436 vk00 ADAEnabler Functional Architecture and Information Flows Rel-20
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 24.549 vj10 SEAL Network Slice Capability Enablement Protocol Rel-19
TR 26.941 vj01 5G Media Slicing Extensions Rel-19
TS 28.879 vj10 OAM for Service Management Exposure Study Rel-19
TS 29.435 vj20 SEAL NSCE Server Services Stage 3 Rel-19
TS 29.536 vj30 NSACF Service Based Interface Protocol Rel-19
TS 29.548 vj40 SEAL Data Delivery Server Services Stage 3 Rel-19
TS 29.549 vj40 SEAL API Specification for Vertical Applications Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.