Description
The Network Slice Customer (NSC) is a pivotal concept in 3GPP's network slicing framework, introduced in Release 15 as part of the 5G system. An NSC is typically an organization or entity that subscribes to and utilizes one or more network slice instances provided by a Mobile Network Operator (MNO) or a network slice provider. The NSC is not necessarily the end-user but rather the customer of the slicing service—examples include enterprises (e.g., a factory requiring ultra-reliable low-latency communications), Mobile Virtual Network Operators (MVNOs), or even internal departments of the MNO itself. The NSC specifies the requirements for the network slice through a Service Level Agreement (SLA) or a network slice template, which details the expected performance, functionality, and isolation levels.
Architecturally, the NSC interacts with the network slice management system, which includes the Communication Service Management Function (CSMF) and Network Slice Management Function (NSMF). The NSC provides the service requirements to the CSMF, which translates them into network slice requirements. These requirements are then used by the NSMF to design and instantiate the network slice across the underlying network resources, involving the RAN and Core Network segments. The NSC may have visibility and some control over their slice instance through management interfaces, allowing them to monitor performance and request modifications. The slice itself is a logical network that provides specific capabilities (e.g., enhanced mobile broadband, massive IoT, critical communications) tailored to the NSC's needs, often with dedicated or shared resources.
The role of the NSC is formalized in 3GPP specifications such as 23.435 and 28.530, which define the lifecycle management of network slices. The NSC is involved in phases like preparation, commissioning, operation, and decommissioning of slices. For instance, an automotive company acting as an NSC might request a slice for connected vehicle services, specifying low latency and high reliability. The MNO then provisions a slice with appropriate network functions (e.g., specialized UPF, edge computing) to meet those demands. The NSC concept enables new business models, allowing MNOs to offer customized network-as-a-service offerings, moving beyond one-size-fits-all connectivity to differentiated services that drive 5G monetization.
Purpose & Motivation
The NSC concept was created to address the need for customizable and tenant-specific network services in the 5G era. Traditional mobile networks offered uniform connectivity to all users, which was insufficient for diverse vertical industry requirements (e.g., industrial automation, healthcare, media). Network slicing allows the creation of virtual networks with tailored characteristics, and the NSC defines who requests and benefits from these slices. It solves the problem of how to formally capture and fulfill the unique demands of different customers within a shared physical infrastructure.
Historically, enterprises had to build private networks or use generic public mobile services, which were either costly or inadequate. The NSC model enables MNOs to serve multiple customers with specific SLAs on a single infrastructure, increasing efficiency and opening new revenue streams. It addresses limitations of previous approaches by providing a standardized framework for customer engagement in slice management, ensuring that slices meet precise technical and business needs. The NSC's role motivates the development of advanced management and orchestration systems in 5G, supporting dynamic slice lifecycle operations and multi-tenancy.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (56 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the foundational role of the Network Slice Customer (NSC) was introduced, specifically through new management interactions with NFV MANO for network service priority. This enabled use cases for network slice subnet management with an assigned priority, establishing initial mechanisms for the NSC to influence slice resource management. These introductions provided the basis for the NSC to express service-level requirements and priorities within the network slice lifecycle.
In Release 16, the NSC (Network Slice Customer) function was enhanced through the introduction of the Network Slice Capability Enablement (NSCE) service, which decouples the communication service from the network slice. This service provides the VAL server with functionalities like slice API configuration and translation, application-layer network slice lifecycle management, and network slice optimization based on VAL server policy. Additionally, it enables network slice performance and analytics monitoring, as well as network slice adaptation for the VAL application by guiding updates to URSP rules in the 5GS.
- Add informative annex to describe a network slice journey TS 28.531CR0024
- Cleanup Network Slice related definitions in OAM space TS 28.530CR0025
- update slice NRM to align with refined slice definitions TS 28.530CR0027
- Decouple communication service and network slice TS 28.530CR0033
- Correction of missing Figure 4.1.7.1 Examples of network slice as NOP internals TS 28.530CR0035
- Clarification on network slice related identifiers TS 28.531CR0047
+ 3 more changes
In Release 17, the new NSC (Network Slice Customer) function, termed Network Slice Capability Enablement (NSCE), introduced key service enhancements including slice API configuration and translation, application-layer network slice lifecycle management, and network slice optimization based on VAL server policy. It also added capabilities for predictive slice modification in edge deployments and coordinated resource optimization across multiple slices for a PNI-NPN owner. These features provide verticals (VAL) with greater autonomy in slice management and adaptation without requiring frequent direct interaction with the 5G system.
- Modification of network slice related requirements TS 28.531CR0098
- Update procedure of reservation and checking feasibility of network slice subnet TS 28.531CR0106
- Update procedure of reservation and checking feasibility of network slice TS 28.531CR0107
- Update procedure of reservation and checking feasibility of network slice subnet TS 28.531CR0114
- Handling of slice input data TS 28.530CR0044
- Network slice subnet capabilities TS 28.531CR0110
+ 11 more changes
In Release 18, key enhancements for the Network Slice Customer (NSC) function introduced a new provisioning procedure for slice activation and deactivation using administrative state and updated core lifecycle management procedures—including allocation, deallocation, and modification for both Network Slice Instances and Network Slice Subnet Instances—to support asynchronous operations. The release also provided clarifications on procedure initiation, fixes to Management Service (MnS) provisioning information, and the addition of UML source code for these lifecycle management processes.
- Add provisioning procedure for slice activation and deactivation using adminsitrative state TS 28.531CR0121
- Update Procedure of Network Slice Instance Allocation to support asynchronous operations TS 28.531CR0173
- Update Procedure of Network Slice Instance Deallocation to support asynchronous operations TS 28.531CR0174
- Update Procedure of Network Slice Instance Modification to support asynchronous operations TS 28.531CR0175
- Update Procedure of Network Slice Subnet Instance Allocation to support asynchronous operations TS 28.531CR0176
- Update Procedure of network slice subnet instance deallocation to support asynchronous operations TS 28.531CR0177
+ 15 more changes
In Release 19, the NSC function introduced enhancements for the Network Slice as a Service (NSaaS) model, specifically improving the network slice allocation procedure. It added new capabilities for slice requirement verification and alignment, and introduced a late notification mechanism to the network slice adaptation procedures. Furthermore, the release extended predictive slice modification to support Inter-PLMN based slice service continuity scenarios.
- Enhancements to Network slice allocation procedure in NSaaS model TS 23.435CR0004
- Enhancements to Slice requirement verification and alignment capability TS 23.435CR0005
- Enhancements to Slice requirement verification and alignment capability TS 23.435CR0017
- Enhancements to Slice requirement verification and alignment capability TS 23.435CR0022
- Add late notification to the network slice adaptation procedures TS 23.435CR0011
- Update on predictive slice modification in Inter-PLMN based slice service continuity TS 23.435CR0024
+ 1 more changes
Explore further
Broader topics and technologies where NSC plays a role.
Defining Specifications
3GPP specifications that define or reference NSC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.435 vj30 | Network Slice Capability Exposure Procedures | Rel-19 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TR 26.941 vj01 | 5G Media Slicing Extensions | Rel-19 |
| TS 28.530 vj00 | Network Slicing Concepts & Requirements | Rel-19 |
| TS 28.531 vk00 | Management and Orchestration | Rel-20 |
| TR 28.836 vi00 | Technical Report on Intent Driven Management | Rel-18 |
| TR 32.847 vi00 | Technical Report | Rel-18 |