Network Slice Template

Description

The Network Slice Template (NEST) is a fundamental concept within the 3GPP management framework for network slicing. It is defined as a formal, structured data model that describes all the necessary information to create and manage a network slice instance. This template is not a static document but a machine-interpretable specification, typically expressed using YANG data modeling language or similar, which can be processed by management and orchestration systems like the Network Slice Management Function (NSMF) and the Communication Service Management Function (CSMF). The template encompasses a comprehensive set of slice characteristics, including performance requirements (e.g., latency, bandwidth, reliability), service-level agreements (SLAs), resource requirements, topological constraints, and the constituent network functions and sub-network slices required.

Architecturally, the NEST acts as the input for the slice design and onboarding phase. It defines the 'what' of a network slice. When a communication service request is received, the CSMF maps the service requirements to a suitable NEST. The NSMF then consumes this template to decompose the slice requirements into resource-level requirements for the underlying network domains (e.g., RAN, Transport, Core), managed by Domain Management Systems (DMS) or the Network Slice Subnet Management Function (NSSMF). The template includes both service-facing and resource-facing parameters, bridging the gap between business intent and technical implementation.

Key components described within a NEST include the Slice Service Type (eSST), Slice Differentiator (SD), and a detailed list of slice profiles. The slice profile is a core element, specifying the network slice subnet (NSS) requirements, which detail the specific behaviors and capabilities needed from the RAN and Core Network parts. This includes the selection of network functions (NFs), their connectivity via service-based interfaces (SBIs), and specific configurations for features like network slicing selection policy (NSSP). The template also includes lifecycle management policies, monitoring descriptors for slice assurance, and security and isolation requirements.

Its role in the network is pivotal for automation and agility. By standardizing the slice definition, NEST enables multi-vendor interoperability and allows operators to offer slices as a service (Slice-as-a-Service) efficiently. It ensures that every instantiated slice instance conforms to a pre-validated design, reducing configuration errors and enabling predictable performance. The template is stored in a catalog or repository, allowing for reuse, versioning, and efficient management of the slice portfolio across its entire lifecycle from preparation to commissioning, operation, and decommissioning.

Purpose & Motivation

NEST was created to address the fundamental challenge of efficiently managing the complexity and diversity of network slices in 5G and beyond. Prior to its standardization, defining a network slice was an ad-hoc, manual process involving lengthy design documents and bespoke configurations for each use case, such as enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communication (URLLC), and massive Machine-Type Communication (mMTC). This approach was not scalable, error-prone, and hindered rapid service deployment and dynamic resource allocation.

The primary problem NEST solves is the lack of a common, machine-readable language to describe a network slice. Without it, automation of slice lifecycle management—instantiation, modification, monitoring, and termination—was impossible. The template provides this common language, enabling closed-loop automation where management systems can interpret service requirements, translate them into technical configurations, and orchestrate the necessary resources across multiple administrative and technological domains. This is essential for realizing the 5G vision of supporting millions of simultaneous connections with diverse and stringent requirements on a shared physical infrastructure.

Historically, network services were monolithic and rigid. The shift to cloud-native, software-defined networks demanded a new paradigm for service creation. NEST, introduced in 3GPP Release 16 as part of the enhanced management and orchestration framework, provides this paradigm. It addresses the limitations of previous network service descriptors by being specifically tailored for the end-to-end logical network concept of a slice, incorporating not just virtual network function (VNF) connectivity but also specific RAN behaviors, transport characteristics, and stringent SLA parameters. It is the cornerstone for commercializing network slicing, allowing operators to productize and offer standardized slice blueprints to enterprise customers.

Key Features

• Machine-readable data model (e.g., YANG) for automated processing
• Comprehensive definition of slice service and resource requirements
• Includes performance targets (latency, throughput, availability)
• Specifies constituent network functions and sub-network topologies
• Defines lifecycle management and monitoring policies
• Enables version control and template cataloging for reuse

Evolution Across Releases

Defining Specifications