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.
Technology family
Network slicing · Core Network › 5G Core
- Rel-15 Network Slice, Network Slice Instance (NSI), Network Slice Subnet, Network Slice Subnet Instance (NSSI), NSI ID, NSSAI, NSSF, S-NSSAI
- Rel-16 ENSI, GST, NSSAA, NSSAAF
- Rel-17 NSAC, NSACF, NSAG, NSSRG
- Rel-18 Alternative S-NSSAI
Also in this family (introduction release not pinned to a single defining specification): Service Profile, Slice Profile
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 6 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
Network Slice is defined for the first time in the 5G system specs as a logical network providing specific network capabilities and characteristics, with Network Slice instances, NSSAI-based selection and NSSF.
- “Network Slice: A logical network that provides specific network capabilities and network characteristics.” TS 23.501 v15.13.0
- “A set of Network Function instances and the required resources (e.g. compute, storage and networking resources) which form a deployed Network Slice.” TS 23.501 v15.13.0
- “A Network Slice may be available in the whole PLMN or in one or more Tracking Areas of the PLMN.” TS 23.501 v15.13.0
Network Slice handling changed in Rel-16: Network Slice Specific Authentication and Authorization (NSSAAF) was added, and Allowed NSSAI determination and slice selection and registration behaviour were revised.
- “Network Slice Specific Authentication and Authorization Function (NSSAAF).” TS 23.501 v16.20.0
- “This procedure is triggered by the AMF during a Registration procedure when some Network Slices require Slice-Specific Authentication and Authorization” TS 23.502 v16.19.0
- Correction of Network Slice selection with NSSF TS 23.501CR1483
Rel-17 extended Network Slice with Network Slice Admission Control (NSACF), NSAG-based cell reselection and Random Access, slice-specific frequency band redirection, and SNPN support for network slice instances.
- “Network Slice Admission Control (NSAC) controls the number of registered UEs per network slice and the number of PDU Sessions per network slice” TS 23.501 v17.15.0
- “the UE may perform Network Slice based cell reselection and Random Access as described in TS 38.300” TS 23.501 v17.15.0
- TS23.501 KI#1 Network Slice Admission Control Function (NSACF) definition TS 23.501CR2679
Rel-18 adds Partial Network Slice support in a Registration Area, network slice areas of service not matching deployed TAs, Network Slice Replacement, and asynchronous slice management procedures.
- “The Partial Network Slice support in a Registration Area for a UE includes configuring the UE with a Partially Allowed NSSAI” TS 23.501 v18.12.0
- “one or more cells when the NS-AoS does not match deployed TAs as defined in clause 5.15.18.” TS 23.501 v18.12.0
- Clarification on Network Slice Replacement TS 23.501CR5156
Rel-19 adds AF-requested modification of the set of Network Slices for a UE, letting an AF ask the PCF to replace an S-NSSAI with an Alternative S-NSSAI, with PCF/AMF handling and notifications.
- “an authorized AF or an AF subject to authorization via the NEF, may request to replace a certain S-NSSAI (Replaced S-NSSAI) for a UE with another S-NSSAI” TS 23.501 v19.9.0
- “5.15.5.2.2a AF Requested modification of the Set of Network Slice(s) for a UE” TS 23.501 v19.9.0
- Correction of PDU Session Establishment procedure for Network Slice Replacement support TS 23.502CR5602
Network slice behaviour was extended: NSSAA for a network slice over 3GPP access to EPC was added, plus energy-based slice adaptation and slice replacement information in AM policy.
- “Network Slice Specific Authentication and Authorization (NSSAA) by a AAA Server for a network slice over 3GPP access to EPC, is supported” TS 23.502 v20.3.0
- Network Slice replacement Information in AM Policy Association Establishment Response TS 29.507CR0383
- Enhance Network Slice Adaptation Considering Energy Information for VAL Application TS 23.435CR0032
Defining Specifications
3GPP specifications that define or reference Network Slice, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.261 vk81 | 5G Service and Operational 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 |