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

Glossary term · Network Slicing

GST

Generic Network Slice Template

Network Slicing →

GST is a standardized data model that defines a network slice's characteristics and requirements to enable automated, vendor-agnostic lifecycle management.

Introduced
Rel-16
Where
Services › Codecs
Specifications
7 specs
Also in
Management
GST Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

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

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 →

Technology family

Network slicing · Core Network › 5G Core

  1. Rel-15 Network Slice, Network Slice Instance (NSI), Network Slice Subnet, Network Slice Subnet Instance (NSSI), NSI ID, NSSAI, NSSF, S-NSSAI
  2. Rel-16 ENSI, GST, NSSAA, NSSAAF
  3. Rel-17 NSAC, NSACF, NSAG, NSSRG
  4. 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 sources

Documented changes in 4 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.

Rel-16 introduced

Rel-16 first specifies GST in 3GPP management specs: NRM requirement to support GSMA GST attributes, GST-related attributes, and an annex relating GST to ServiceProfile and SliceProfile.

  • “The NRM definitions shall support the attributes of the Generic network Slice Template (GST) defined by GSMA [8].” TS 28.540 v16.2.1
  • “the GST [50] is translated and used as input to NRM ServiceProfile” TS 28.541 v16.25.0
  • Add relation of GST and profiles TS 28.541CR0178
Rel-17 2 CRs

TS 28.541 revised how the GSMA GST relates to ServiceProfile and SliceProfile: GST parameters now feed ServiceProfile, which is translated to TopSliceSubnetProfile, with corrected GST attribute mappings and translation tables.

  • “the GST parameters [50] are used as input to ServiceProfile.” TS 28.541 v17.20.0
  • Correction on mapping GST attributes TS 28.541CR0508
  • Update relationship between GST and Network Slice NRM fragment TS 28.541CR0587
Rel-18 specification text

TS 28.541 gained an 'Access specific GST configuration' addition (CR0711) and its GST-to-ServiceProfile mapping annex was renumbered and kept, while GST references were updated in 28.531.

Rel-19 1 CR

TS 28.541 configuration parameters were updated for GST translation, changing how GST attributes map to network slice configuration in Rel-19.

  • Update configuration parameters for GST translation TS 28.541CR1415

Defining Specifications

3GPP specifications that define or reference GST, 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
TR 23.745 vh00 Study on App Layer Support for Factories of the Future in 5G Rel-17 read
TS 26.941 vk00 5GMS Network Slicing Study Rel-20 read
TS 28.531 vk10 5G Network Slice Provisioning Management Rel-20 read
TS 28.880 vj00 Study on 5G Energy Efficiency & Saving Rel-19 read
TR 32.847 vi00 Technical Report Rel-18 read