NSSI

Network Slice Subnet Instance

Network Slicing
Introduced in Rel-15
An NSSI is a managed instance of a subset of resources (e.g., a group of network functions) that forms part of a complete end-to-end Network Slice Instance (NSI). It represents a deployable, manageable segment of a network slice, allowing for modular construction and independent lifecycle management of slice components.

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.

Key Features

  • Represents an instantiated, managed subset of an end-to-end Network Slice Instance (NSI)
  • Defined by a Network Slice Subnet Descriptor (NSSD) template
  • Independently managed lifecycle (creation, scaling, termination) via MANO systems
  • Can be shared across multiple NSIs as a common resource subnet
  • Composed of physical/virtual network functions and their interconnections
  • Enables modular construction of complex slices from reusable components

Evolution Across Releases

Rel-15 Initial

Introduced as a core concept for the decomposition and management of network slices. Defined the NSSI as a managed instance of a network slice subnet, its relationship to the NSI and NSSD, and the foundational principles for its lifecycle management within the 5G architecture.

Enhanced management capabilities for NSSIs, including more detailed performance assurance and fault supervision procedures. Introduced further details on the sharing of NSSIs across multiple NSIs and the associated management aspects.

Strengthened support for advanced slicing scenarios, including integration with non-public networks (NPNs) and enhanced isolation requirements. Refined models for capability exposure and service assurance related to NSSI performance.

Part of 5G-Advanced enhancements focusing on automation and intelligence in slice management. Worked on more dynamic optimization of NSSI resources and improved coordination between NSSI and NSI lifecycle management.

Continued evolution in 5G-Advanced, exploring intent-based management and orchestration of NSSIs, deeper integration with cloud-native principles, and support for more complex, multi-domain slice compositions.

Contributions to 6G exploratory studies, investigating future concepts for network decomposition and resource abstraction that may evolve or extend the NSSI paradigm for more extreme and diverse service environments.

Defining Specifications

SpecificationTitle
TS 23.435 3GPP TS 23.435
TS 23.700 3GPP TS 23.700
TS 26.941 3GPP TS 26.941
TS 28.530 3GPP TS 28.530
TS 28.531 3GPP TS 28.531
TS 28.535 3GPP TS 28.535
TS 28.536 3GPP TS 28.536
TS 28.541 3GPP TS 28.541
TS 28.545 3GPP TS 28.545
TS 28.801 3GPP TS 28.801
TS 28.808 3GPP TS 28.808
TS 28.841 3GPP TS 28.841
TS 28.861 3GPP TS 28.861
TS 33.811 3GPP TR 33.811