Network Slice Subnet Instance

Description

A Network Slice Subnet Instance (NSSI) is a fundamental concept in the 3GPP network slicing architecture, representing an instantiated, managed, and operational segment of a network slice. While a Network Slice Instance (NSI) provides a complete, end-to-end logical network serving a particular business case, an NSSI constitutes a functional subset of that whole. An NSSI is a composition of managed physical and/or virtual resources, including Network Functions (NFs) and the necessary connectivity between them, that delivers a well-defined set of capabilities. Multiple NSSIs can be combined and interconnected to form a complete NSI. For example, an NSI for a factory automation service might be composed of separate NSSIs for the Radio Access Network (RAN) part, the Transport Network part, and the Core Network part, each with specific performance characteristics.

The management and orchestration of NSSIs are the responsibility of the Management and Orchestration (MANO) system, as defined in frameworks like ETSI NFV. The 3GPP Management System (3GPP MS) interacts with the MANO system to request the creation, modification, termination, and monitoring of NSSIs. Each NSSI has its own lifecycle, which is managed independently but coordinated to support the lifecycle of the parent NSI. An NSSI is described by a Network Slice Subnet Descriptor (NSSD), a template that defines the requirements and characteristics (e.g., capacity, latency, geographic area) of the subnet. The NSSD is used by the orchestrator to instantiate the corresponding NSSI with the appropriate resources.

From an operational perspective, NSSIs enable modularity, reuse, and efficient resource utilization in a sliced network. A single, high-performance transport NSSI might be shared as a common subnet across multiple different NSIs (e.g., one for eMBB and one for URLLC), provided the isolation and performance guarantees are met. This sharing is managed through the concept of nested slicing. The ability to manage subnets independently allows operators to scale, upgrade, or repair parts of a network slice without necessarily affecting the entire end-to-end service. Specifications such as TS 28.530 and TS 28.541 detail the management procedures and interfaces for NSSIs.

Purpose & Motivation

The concept of the NSSI was developed to address the practical complexity of deploying and managing end-to-end network slices. Creating a monolithic NSI from scratch for every new service would be highly inefficient and inflexible. The NSSI introduces a crucial layer of decomposition, allowing operators to build complex NSIs from smaller, reusable, and independently manageable building blocks.

This approach solves several key problems. First, it enables resource sharing and optimization across different slices. Instead of dedicating isolated resources for every function in every slice, common subnets (like a shared transport layer) can be created once and used by many slices, improving infrastructure efficiency. Second, it simplifies lifecycle management. Upgrading a core network function across dozens of slices can be achieved by updating a single, shared Core NSSI, rather than individually modifying each NSI. Third, it allows for different domains (RAN, Transport, Core) to be managed by different organizational units or even different vendors, with clear interfaces defined by the NSSI boundaries. The NSSI concept, therefore, is what makes large-scale, commercial network slicing operationally feasible and economically viable.