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.
What changed in its specifications
The latest release-to-release comparison of specifications that define NSSI. Each summary describes the whole specification, not only this term.
Rel-16 adds Closed loop SLS Assurance, defining Service Level Specification and a monitoring, analysis, decision and execution control loop. It also adds tenant information to TS 28.530, covering tenant association with communication services and control of tenant access to management capabilities.
Full comparison in TS 28.530 →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
- Rel-15 Network Slice, Network Slice Instance (NSI), Network Slice Subnet, Network Slice Subnet Instance (NSSI), NSI ID, NSSAI, NSSF, S-NSSAI
- Rel-16 ENSI, GST, NSSAA, NSSAAF
- Rel-17 NSAC, NSACF, NSAG, NSSRG
- 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 sourcesDocumented changes in 5 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.
NSSI is specified for the first time in Rel-15, with NSSI lifecycle management, NSSI state handling, and NSSI performance and fault supervision services.
- “A NetworkSliceSubnet instance (NSSI) is a logical object in the management system that represents a complex grouping of resources” TS 28.541 v15.12.0
- “The fault supervision data report service for NSSI shall have the capability to provide alarm notifications of a network slice subnet instance” TS 28.545 v15.2.0
- “To enable the authorized consumer to create a measurement job for collecting the performance data of NSSI(s).” TS 28.550 v15.8.0
Rel-16 adds NSSI performance threshold monitoring use cases (create/terminate threshold monitoring, crossing notifications) and corrects NSSI allocation, deallocation and reuse procedures.
- “To enable the authorized consumer to request creation of threshold monitoring for NSSI performance measurements.” TS 28.550 v16.10.0
- “reports the threshold crossing event to NSSI performance threshold monitoring service producer, who then sends the threshold crossing notification to the consumer.” TS 28.550 v16.10.0
- Add use case for NSSI performance threshold monitoring TS 28.550CR0029
NSSI allocation, deallocation and modification procedures were revised, and fault supervision services for NSSI alarms (including alarm list rebuilt notification) were added.
- “request the provider to deallocate a slice profile in an NSSI. The provider may terminate the requested NSSI or modify the requested NSSI” TS 28.531 v17.10.0
- “The fault supervision data report service for NSSI shall have the capability to provide alarm list rebuilt notifications to its authorized consumer” TS 28.545 v17.0.0
- Updating NSSI allocation TS 28.531CR0080
NSSI allocation and deallocation procedures were updated in Rel-18, adding isolation profile association with NSI and NSSI and refining how existing NSSIs are matched, reused or created.
- “if applicable with the isolation profiles are associated with the NSI and NSSI(s), and triggers to establish the links between the service access points” TS 28.531 v18.8.0
- Update Procedure of Network Slice Subnet Instance Allocation to support asynchronous operations TS 28.531CR0176
- “Based on the network slice subnet related requirements received and if applicable the isolation profile is selected” TS 28.531 v18.8.0
Rel-20 updates the NSSI lifecycle management procedures in TS 28.531, including the condition text for NSSIs that contain virtualized parts.
- Rel-20 CR 28.531 Updated procedures for NSSI LCM TS 28.531CR0270
- “opt If the NSSI contains virtualized parts” TS 28.531 v20.1.0
Defining Specifications
3GPP specifications that define or reference NSSI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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 |
| TS 26.941 vk00 | 5GMS Network Slicing Study | Rel-20 read |
| TS 28.530 vj00 | Network Slicing Concepts & Requirements | Rel-19 read |
| TS 28.531 vk10 | 5G Network Slice Provisioning Management | Rel-20 read |
| TS 28.535 vj00 | Closed Control Loop Assurance Management | Rel-19 read |
| TS 28.536 vj20 | Management services for communication service assurance | Rel-19 read |
| TS 28.541 vk41 | 5G Network Resource Model Stage 2/3 | Rel-20 read |
| TS 28.545 vh00 | Fault Supervision for 5G Networks | Rel-17 read |
| TS 28.801 vf10 | Management and Orchestration of Network Slicing | Rel-15 read |
| TR 28.808 vh00 | 5G satellite integration management study | Rel-17 read |
| TR 28.841 vi01 | Technical Report on IoT NTN Enhancements | Rel-18 read |
| TS 28.861 vg00 | SON for 5G Networks Management | Rel-16 read |
| TS 33.811 vf00 | Security study for 5G network slicing management | Rel-15 read |