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

Glossary term · Network Slicing

Network Slice instance

Network Slice instance

Network Slicing →

Network Slice instance is a set of Network Function instances and the required compute, storage, and networking resources forming a deployed Network Slice that provides a complete logical network tailored to specific service characteristics.

Introduced
Rel-14
Where
Management
Specifications
5 specs
Network Slice instance Description Purpose What changed Neighbours Detected Changes Specifications

Description

A Network Slice instance (NSI) is the concrete, deployed realization of a Network Slice. It consists of a set of Network Function instances and the required resources—such as compute, storage, and networking resources—that together form a deployed Network Slice. The concept was introduced in 3GPP Release 14 and has been refined through subsequent releases, with the definition reworded in Release 16 to emphasize Network Function instances and required resources rather than abstract network functions.

A Network Slice instance provides a complete logical network with specific network characteristics, such as ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), or massive machine-type communication (mMTC). It is created from a Network Slice Template (NST) and may be composed of one or more Network Slice Subnet instances (NSSIs), each covering a domain such as the core network, radio access network, or transport network. The NSI is the top-level entity that operators instantiate, manage, and terminate over its lifecycle.

The lifecycle of a Network Slice instance includes preparation, instantiation/configuration, and operation. During preparation, the network slice template is designed and validated. During instantiation, the necessary network functions and resources are allocated and configured. During operation, the NSI is monitored, scaled, and modified as needed, and eventually decommissioned. Management of the NSI is specified in TS 28.530 (management and orchestration of network slicing) and TS 28.801 (network slice lifecycle management), which define the management services and procedures.

Architecturally, the Network Slice instance is described in TS 23.501, which defines the 5G System architecture and how network slicing is supported. The NSI may span multiple domains and may include network functions from the 5G Core (e.g., AMF, SMF, UPF) and the NG-RAN. Each NSI is identified by an S-NSSAI (Single Network Slice Selection Assistance Information), which is used by the UE and network to select the appropriate slice. Security aspects of network slicing, including isolation between slices, are addressed in TS 33.811.

The Network Slice instance is central to the network slicing paradigm because it is the unit of deployment and management. Operators create NSIs to serve specific vertical industries or service types, each with its own performance, isolation, and security requirements. The NSI abstraction allows operators to manage slices as complete logical networks rather than as collections of individual network functions, simplifying operations and enabling service-level agreements (SLAs) to be met. The reworded Release 16 definition, which explicitly mentions Network Function instances and required resources, reflects the maturation of the concept toward concrete, resource-aware deployment and orchestration.

Purpose & Motivation

The Network Slice instance exists to make network slicing operational and manageable. Network slicing as a concept allows a single physical network to be partitioned into multiple logical networks, each tailored to specific service requirements. However, the concept only becomes useful when slices can be instantiated, configured, monitored, and terminated as concrete entities. The NSI provides that concrete entity, serving as the unit of deployment and lifecycle management.

Before network slicing, operators typically built separate networks or used best-effort partitioning to serve different service types. This was costly and inflexible. The NSI addresses these limitations by allowing operators to create logical networks on demand, with the specific network functions and resources needed for each service. This enables efficient resource utilization, faster service rollout, and the ability to meet diverse requirements—from low-latency industrial control to high-throughput broadband—on a shared infrastructure.

The evolution of the definition from Release 14 to Release 16 reflects the maturation of the concept. The original definition focused on a set of network functions and resources forming a complete logical network. The Release 16 rewording explicitly references Network Function instances and required resources such as compute, storage, and networking, aligning the definition with the resource-aware orchestration and management frameworks defined in TS 28.530 and TS 28.801. This shift supports the practical needs of operators deploying and managing slices in cloud-native, virtualized environments.

What changed in its specifications

The latest release-to-release comparison of specifications that define Network Slice instance. 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 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 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-18 2 changes
  • Change of Network Slice instance for PDU sessions TS 23.501CR3867
  • Explicit subscription to NSSF for network slice instance replacement TS 23.501CR4354

Defining Specifications

3GPP specifications that define or reference Network Slice instance, 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 28.530 vj00 Network Slicing Concepts & Requirements Rel-19 read
TS 28.801 vf10 Management and Orchestration of Network Slicing Rel-15 read
TS 32.845 vg00 Charging Aspects of Network Slicing Study Rel-16 read
TS 33.811 vf00 Security study for 5G network slicing management Rel-15 read