Description
The Generic Network Slice Template (GST) is a pivotal data model within the 3GPP standards, specifically designed for the management and orchestration of network slices. It serves as a standardized, machine-readable blueprint that describes the complete set of attributes, requirements, and constraints of a network slice instance (NSI). The GST is defined using YANG data modeling language, ensuring it is structured, hierarchical, and suitable for automated processing by management systems like the Communication Service Management Function (CSMF), Network Slice Management Function (NSMF), and Network Slice Subnet Management Function (NSSMF). Its primary role is to act as an information object that is passed between these management functions during the slice provisioning, modification, and assurance processes.
Architecturally, the GST is a core component of the 3GPP management framework for network slicing, detailed in specifications such as TS 28.531 and TS 28.541. It abstracts the complex, multi-domain nature of a slice into a manageable template. The template encompasses several key areas: the service profile (defining the slice's intended service type, e.g., eMBB, URLLC, MIoT), the network slice subnet requirements (detailing the needed resources and performance across the RAN, Transport, and Core Network domains), and the slice performance and policy requirements (including latency, reliability, throughput, and isolation levels). This structured approach allows the management system to decompose the high-level service request into specific, actionable configuration commands for the underlying network functions and infrastructure.
In operation, the GST enables closed-loop, intent-based management. A communication service provider (CSP) or enterprise customer submits a service request, often via a portal or northbound API, which is translated into a GST instance. This GST is then consumed by the NSMF, which interprets the requirements and orchestrates the necessary resources across different administrative and technological domains by generating domain-specific sub-templates for the NSSMFs. The GST ensures consistency and prevents misinterpretation by providing a single source of truth for the slice's intended behavior. It is integral to achieving the promised benefits of network slicing: customized logical networks on a shared physical infrastructure, each with guaranteed performance and isolation.
Purpose & Motivation
The GST was introduced to solve a critical challenge in the practical deployment of network slicing: the lack of a standardized, interoperable method for describing slice requirements. Prior to its definition, each vendor or operator might use proprietary templates or manual processes to define slices, leading to fragmentation, high integration costs, and an inability to automate lifecycle management across multi-vendor environments. The creation of the GST was motivated by the 5G vision of supporting diverse vertical industries (like automotive, manufacturing, and healthcare) with vastly different service requirements. These industries needed a clear, unambiguous way to communicate their network needs to the mobile operator.
Historically, network services were relatively monolithic, and service creation was a slow, manual process involving significant human intervention. The shift towards softwarization and cloud-native networks in 5G demanded a more agile, software-driven approach. The GST provides this by acting as a common 'contract' or 'recipe' that decouples the service intent from the vendor-specific implementation. It addresses the limitations of previous ad-hoc approaches by enabling automated translation of business-level service requirements into technical network configurations. This is essential for scaling network slicing to support a massive number of diverse slices efficiently and reliably.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (50 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the foundational GST (Generic Network Slice Template) function was introduced, specifically adding the network slice subnet management use case with an assigned priority. This release also defined the initial management interactions between network slice management and NFV MANO (Management and Orchestration) to handle network service priority.
In Release 16, the enhancements to the Generic Network Slice Template (GST) function focused on clarifying and correcting foundational slice management procedures and identifiers. Specifically, the release provided corrections to the Network Slice Subnet Instance Deallocation procedure and refined use cases for Network Slice Subnet termination. Furthermore, it introduced an informative annex to describe a network slice journey and delivered fixes and clarifications for general information related to network slice identifiers.
- Add informative annex to describe a network slice journey TS 28.531CR0024
- Clarification on network slice related identifiers TS 28.531CR0047
- Fix general information of network slice related identifiers TS 28.531CR0057
- Correction on procedure of Network Slice Subnet Instance Deallocation TS 28.531CR0015
- Fix Network Slice subnet termination use case TS 28.531CR0044
In Release 17, the GST function was enhanced within the new Network Slice Capability Enablement (NSCE) service, introducing specific procedures for policy harmonization, requirement alignment, and slice API configuration and translation. Key new functionalities included predictive slice modification for edge deployments and coordinated resource optimization across multiple slices, such as between PLMN and PNI-NPN slices. Furthermore, procedures for application layer network slice lifecycle management and network slice adaptation for VAL applications were formally specified.
- 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
- Network slice subnet capabilities TS 28.531CR0110
- Update procedure of network slice subnet instance allocation TS 28.531CR0099
+ 9 more changes
In Release 18, the GST function introduced a new administrative state for slice activation and deactivation provisioning and enhanced key Lifecycle Management (LCM) procedures—including allocation, deallocation, and modification for both Network Slice Instances and Subnet Instances—to support asynchronous operations. The release also focused on correcting and clarifying the initiation and description of these core procedures while updating references and fixing the Management Service (MnS) for slice provisioning information.
- 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 GST function introduced enhancements for slice requirement verification and alignment, along with a new late notification capability for network slice adaptation procedures. It also updated the predictive slice modification feature to support Inter-PLMN based slice service continuity. These additions build upon the existing NSCE services for policy harmonization, requirement alignment, and predictive modification in edge deployments.
- 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 GST plays a role.
Defining Specifications
3GPP specifications that define or reference GST, 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 23.745 vh00 | Study on App Layer Support for Factories of the Future in 5G | Rel-17 |
| TR 26.941 vj01 | 5G Media Slicing Extensions | Rel-19 |
| TS 28.531 vk00 | Management and Orchestration | Rel-20 |
| TS 28.880 vj00 | Study on 5G Energy Efficiency & Saving | Rel-19 |
| TR 32.847 vi00 | Technical Report | Rel-18 |