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

Glossary term · Network Slicing

NSST

Network Slice Subnet Template

Network Slicing →

NSST is a reusable 3GPP template defining a network slice subnet’s characteristics and requirements, enabling automated, repeatable instantiation from a standardized blueprint.

Introduced
Rel-15
Where
Management
Specifications
2 specs
NSST Description Purpose Neighbours Specifications

Description

The Network Slice Subnet Template (NSST) is a foundational concept in 3GPP network slicing management, introduced in Release 15 within the network slicing study TS 28.801 and referenced in security specifications such as TS 33.811. A network slice subnet is a constituent part of an end-to-end network slice, typically covering a specific domain such as the radio access network, the core network, or the transport network. The NSST provides the blueprint from which such subnets are instantiated, capturing the topology, resource requirements, configuration parameters, and behavioral characteristics needed to create a functioning subnet.

Conceptually, the NSST plays a role analogous to a class in object-oriented design or a template in cloud orchestration. It is not a running network; it is a specification. When a Network Slice Subnet Management Function (NSSMF) receives a request to create a subnet — for example, from the Network Slice Management Function (NSMF) as part of end-to-end slice creation — it selects an appropriate NSST and instantiates a network slice subnet instance (NSSI) from it. The template defines what the subnet should look like: which network functions or nested subnets it comprises, what resources each requires, what configuration parameters apply, and what performance and assurance characteristics are expected.

The NSST is closely related to other 3GPP template concepts. The Network Slice Template (NST) describes an end-to-end slice, and it may reference one or more NSSTs that compose it. At a lower level, the NSST may reference network service descriptors (NSDs) and virtual network function descriptors (VNFDs) in NFV environments, bridging 3GPP slice management with ETSI NFV orchestration. This layered template hierarchy — NST at the top, NSST in the middle, and NFV descriptors at the bottom — allows reuse and composition: a single NSST can be used in many different end-to-end slices, and an NST can be assembled from a library of NSSTs.

TS 28.801, the Release 15 study on network slicing management and orchestration, introduced the NSST as part of its conceptual model, describing how templates support the automation of slice lifecycle management. The template-driven approach is essential for scalability: manually designing each slice instance would be error-prone and slow, whereas instantiating from validated templates enables rapid, consistent deployment. The NSST also carries attributes relevant to security and isolation, which is why TS 33.811, the security study for network slicing, references it when discussing how security requirements are associated with slice components.

In practice, an NSST includes information such as the subnet's constituent elements, resource and QoS requirements, supported service types, geographic or administrative scope, and management interfaces. It may also include policies for scaling, healing, and performance monitoring. Because the NSST is a management-plane artifact, its exact data model is refined across releases and aligned with the information models in TS 28.541 and related specifications. The template concept remains central to how 3GPP envisions automated slice deployment, even as the surrounding management architecture matures.

Purpose & Motivation

The NSST was created to make network slice deployment automated, repeatable, and scalable. In early 5G slicing discussions, it became clear that manually configuring each slice subnet would not support the vision of dynamic, on-demand slicing with potentially thousands of concurrent slices. A template-based approach allows operators to define validated blueprints once and instantiate them many times, reducing errors and operational cost.

The NSST also addresses composition and reuse. End-to-end slices are built from subnets, and different slices often share similar subnet requirements — for example, many slices need a standard core network subnet with mobility management and user plane functions. By standardizing subnet templates, operators can build libraries of reusable components, mix and match them per slice, and ensure consistency across deployments. This mirrors established practices in cloud computing and NFV, where templates and descriptors are the basis for orchestration.

Before the NSST concept, slice management lacked a standardized way to describe subnet blueprints, which hindered interoperability between management systems and vendors. TS 28.801 established the template model as part of the 3GPP slicing framework, providing the conceptual foundation that later normative specifications build upon.

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-15 Initial

Initial introduction of the NSST concept in TS 28.801, the network slicing management and orchestration study. Defined the template as the blueprint for network slice subnets, established its relationship to NST and NFV descriptors, and described how templates support automated slice lifecycle management. Also referenced in TS 33.811 for security aspects of slice components.

Defining Specifications

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

SpecificationTitleRelease
TS 28.801 vf10 Management and Orchestration of Network Slicing Rel-15 read
TS 33.811 vf00 Security study for 5G network slicing management Rel-15 read