Glossary term · Network Slicing

Network Slice

Network Slice

Network Slicing →

Network Slice is a logical network customized for specific service requirements, enabling operators to create multiple virtual networks on shared infrastructure.

Introduced
Rel-14
Where
Core Network › 5G Core
Specifications
6 specs
Also in
Management

3GPP QuarterlyThe next issue by email, at most eight a year.

Category
Network Slicing
Introduced
Rel-14
Where
Core Network › 5G Core
Also touches
1 segments
Specifications
6 specs
Network Slice Description Purpose Related Detected Changes Specifications

Description

A Network Slice is a fundamental concept in 5G and beyond that enables the creation of multiple logical networks on top of a shared physical infrastructure. Each network slice is customized to provide an optimized solution for a specific market scenario demanding particular requirements with end-to-end scope. This concept, extensively documented in specifications such as 22.261, 23.501, 23.799, 28.530, 33.811, and 38.801, represents a paradigm shift from traditional one-size-fits-all network architectures to flexible, service-specific network deployments.

Architecturally, a network slice comprises a set of network functions and corresponding resources necessary to provide required telecommunication services and network capabilities. These network functions can be deployed across multiple technical domains: the device, the radio access network, the transport network, and the core network. The slice definition includes both physical and virtual resources, with the ability to instantiate, scale, and terminate slices dynamically based on demand. The 3GPP management framework, particularly in TS 28.530, defines how slices are managed through their lifecycle, including preparation, commissioning, operation, and decommissioning phases.

The implementation of network slicing relies on several key technologies. Network Function Virtualization (NFV) and Software-Defined Networking (SDN) provide the foundational infrastructure flexibility. Service-Based Architecture (SBA) in the 5G core enables modular network function deployment and interconnection. The concept of Network Slice Selection Assistance Information (NSSAI) allows user equipment to request and connect to specific slices. Each slice is identified by an S-NSSAI (Single Network Slice Selection Assistance Information), which comprises a Slice/Service Type (SST) and optionally a Slice Differentiator (SD).

Network slices can be categorized based on their service characteristics. Enhanced Mobile Broadband (eMBB) slices prioritize high data rates and capacity. Ultra-Reliable Low-Latency Communication (URLLC) slices focus on extremely low latency and high reliability. Massive Machine-Type Communication (mMTC) slices optimize for high connection density and energy efficiency. Beyond these standardized types, operators can define custom slices for specific enterprise customers or vertical industries, each with tailored performance characteristics, security policies, and network functions.

The isolation between slices is a critical design consideration. Different slices may share some network functions while maintaining separate instances of others. The level of isolation can vary from complete physical separation to logical separation with shared resources. This flexibility allows operators to balance cost efficiency against the specific isolation requirements of different services. For example, a slice serving critical infrastructure might require strict isolation, while a slice for general consumer services might share more resources.

Network slicing also introduces new challenges in terms of management, orchestration, and assurance. The operator must be able to monitor each slice's performance independently, ensure that slices do not adversely affect each other, and dynamically adjust resources as demand changes. The 3GPP management architecture provides mechanisms for slice performance monitoring, fault management, and SLA assurance. These capabilities are essential for operators to offer slice-based services with guaranteed quality of service to enterprise customers.

Purpose & Motivation

Network slicing was created to address the diverse and often conflicting requirements of different 5G use cases and vertical industries. Traditional mobile networks were designed to serve a single primary service type, typically voice or mobile broadband, with uniform network characteristics across all users. However, 5G envisioned a much broader range of applications, from autonomous vehicles requiring ultra-low latency to massive IoT deployments needing extreme energy efficiency and connection density. A single network architecture optimized for one use case would be suboptimal for others.

The concept emerged from the recognition that operators needed a way to partition their physical network resources into multiple virtual networks, each tailored to specific service requirements. This approach allows a single operator to simultaneously serve an autonomous driving company needing 1ms latency, a utility company deploying millions of smart meters, and consumers streaming 4K video, all on the same physical infrastructure. Each customer or service type receives a network experience optimized for their needs without requiring separate physical deployments.

Before network slicing, operators had limited options for service differentiation. They could implement separate physical networks for different services, which was prohibitively expensive, or they could use QoS mechanisms within a single network, which provided limited isolation and customization. Network slicing provides a standardized, scalable approach to service differentiation that leverages cloud-native technologies and automation to make multi-service networks economically viable. This capability is considered a key enabler for 5G's promise of supporting diverse vertical industries and new business models.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 5 changes
  • Clarification note on Network Slice limitation TS 23.501CR0446
  • Merging Network Slice with regular EPS Interworking TS 23.501CR0518
  • TS 23.501 Update to Network Slice availability TS 23.501CR0808
  • Clarification on Establishing a PDU Session in a Network Slice TS 23.501CR0833
  • Clarify on Network Slice availability change TS 23.501CR0968
Rel-16 12 changes
  • Enhanced network slice requirements based on business role models TS 22.261CR0310
  • Clarification of geographic constraint on a network slice TS 22.261CR0368
  • Corrections to Network Slice Registration TS 23.501CR1257
  • CAG and Network Slice Selection TS 23.501CR1297
  • Alignment of Network Slice selection logic TS 23.501CR1303
  • Correction of Network Slice selection with NSSF TS 23.501CR1483

+ 6 more changes

Rel-17 11 changes
  • Network Slice restriction based on NWDAF analytics TS 23.501CR2567
  • TS23.501 KI#1 Network Slice Admission Control Function (NSACF) definition TS 23.501CR2679
  • TS23.501 KI#2 Network Slice Admission Control Function (NSACF) definition TS 23.501CR2680
  • Support of 5GC assisted cell selection to access network slice TS 23.501CR2719
  • Introduction of support of NG.116 attribute Simultaneous Use of a Network Slice TS 23.501CR2813
  • Support of Emergency and Priority Services in Network Slice Admission Control TS 23.501CR2837

+ 5 more changes

Rel-18 21 changes
  • Change of Network Slice instance for PDU sessions TS 23.501CR3867
  • Improved network control of the UE beahviour for a network slice TS 23.501CR3939
  • Optimizations for the support of time vality policies for a network slice and graceful network slice PDU sessions release. TS 23.501CR4004
  • Support of reduced network slice availability TS 23.501CR4077
  • Support of graceful/gradual termination of PDU sessions during network slice decommissioning TS 23.501CR4078
  • Support of network slice replacement TS 23.501CR4083

+ 15 more changes

Rel-19 6 changes
  • Clarification on network slice handling for Indirect Network Sharing TS 23.501CR5560
  • Clarification on network slice in the case of Indirect Network Sharing TS 23.501CR5926
  • Resolution of EN in AF Requested modification of the Set of Network Slice(s) for a UE TS 23.501CR6020
  • Clarification on Configured NSSAI in AF Requested modification of the Set of Network Slice(s) for a UE TS 23.501CR6114
  • Clarification on network slice handling for EHPLMN TS 23.501CR5683
  • Partially Allowed NSSAI handling for network slice replacement TS 23.501CR6455

Defining Specifications

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

SpecificationTitleRelease
TS 22.261 vk70 5G System Service Requirements Rel-20 read
TS 23.501 vk30 5G System Architecture Rel-20 read
TR 23.799 ve00 Study on Next Generation System Architecture Rel-14 read
TS 28.530 vj00 Network Slicing Concepts & Requirements Rel-19 read
TS 33.811 vf00 Security study for 5G network slicing management Rel-15 read
TR 38.801 ve00 Study on new radio access technology: Radio access architecture and interfaces Rel-14 read