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

Glossary term · Network Slicing

NSC

Network Slice Customer

Network Slicing →

NSC is a customer entity, such as an enterprise or service provider, that requests and uses a tailored network slice instance from an operator, defining its requirements and being the beneficiary of its isolated connectivity.

Introduced
Rel-15
Where
Management
Specifications
7 specs
Also in
Services
NSC Description Purpose What changed Neighbours Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define NSC. Each summary describes the whole specification, not only this term.

TS 28.530Rel-15 → Rel-16

Rel-16 adds Closed loop SLS Assurance, defining Service Level Specification and a monitoring, analysis, decision and execution control loop. It also adds tenant information to TS 28.530, covering tenant association with communication services and control of tenant access to management capabilities.

Full comparison in TS 28.530 →
TS 28.531Rel-18 → Rel-19

Rel-19 adds management of IAB nodes to TS 28.531. The new clauses cover IAB-node configuration, location information, configuration via notifications, and a procedure with a sequence diagram.

Full comparison in TS 28.531 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-15 Initial

Introduced as part of the initial 5G network slicing architecture. Defined the NSC role in slice requirement specification and lifecycle management, establishing the framework for customer-driven slice provisioning and the interaction between NSC and network slice management systems.

Defining Specifications

3GPP specifications that define or reference NSC, 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.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 26.941 vk00 5GMS Network Slicing Study Rel-20 read
TS 28.530 vj00 Network Slicing Concepts & Requirements Rel-19 read
TS 28.531 vk10 5G Network Slice Provisioning Management Rel-20 read
TR 28.836 vi00 Technical Report on Intent Driven Management Rel-18 read
TR 32.847 vi00 Technical Report Rel-18 read