NSI

Network Slice Instance Identifier

Network Slicing →
Introduced in Rel-14 Also in: Core Network, Services, Security

NSI is a unique identifier for a deployed set of network functions and resources that provides a complete logical network for a specific service type or tenant in 5G systems.

Category
Network Slicing
Introduced
Rel-14
Where
Management
Also touches
3 segments
Specifications
26 specs
NSI Description Purpose Related Classification Detected Changes Specifications

Description

The Network Slice Instance Identifier (NSI ID) is a critical component of the 5G network slicing architecture, defined in the 5G System specifications. A Network Slice Instance is a real, instantiated logical network that provides specific network capabilities and characteristics. The NSI ID is the unique key used by management systems (specifically, the Network Slice Management Function (NSMF) and Communication Service Management Function (CSMF)) to identify, manage, and orchestrate a specific slice instance throughout its lifecycle—from creation and activation to modification, supervision, and decommissioning. The identifier is used within the management and orchestration (MANO) plane, as defined by 3GPP and often integrated with ETSI NFV MANO. It is referenced in network slice selection and subscription data, allowing the network to associate a UE with the correct slice. The NSI ID is distinct from the S-NSSAI (Single Network Slice Selection Assistance Information), which is used by the UE and the access network for slice selection during registration and session establishment. The S-NSSAI points to a Network Slice Type, and the network maps that request to a specific NSI using the NSI ID internally. The NSI ID binds together all the virtualized and physical resources—including core network functions (like AMF, SMF, UPF), RAN components, and transport network segments—that collectively realize the slice. Its uniqueness is paramount for ensuring strict isolation between slices, accurate charging, fault management, and performance monitoring per slice.

Purpose & Motivation

The NSI ID was introduced with 5G network slicing to solve the problem of managing multiple, isolated, logical networks running on a shared physical infrastructure. Pre-5G networks were largely monolithic, designed for a one-size-fits-all service model (primarily mobile broadband). The advent of diverse use cases—such as massive IoT, ultra-reliable low-latency communications (URLLC), and enhanced mobile broadband (eMBB)—required the ability to create tailored networks with specific performance, security, and functional characteristics. Network slicing is the architectural answer, but it necessitates a robust identification and management system. The NSI ID provides the fundamental handle for orchestration and lifecycle management. It addresses the limitation of not having a standardized, network-wide identifier to track a specific slice instance across all management domains (RAN, Transport, Core). This enables automated slice provisioning, granular resource allocation, independent operation and scaling of slices, and tenant-specific management, which are essential for 5G's vision of supporting vertical industries and new business models.

Classification

Part ofS-NSSAI
Related approachesNSMFNSSF

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (12 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 3 changes

In Release 15, the NSI function was introduced with the definition of the Network Slice Instance Identifier (NSI ID) as an operator-specific string to uniquely identify a Network Slice Instance within a PLMN. The release also introduced the 5G NSI Exposure Function (EF) and its associated procedures, alongside updates to operation names within NSI provisioning procedures. Furthermore, corrections were made regarding the defined length of the EF NSI identifier.

  • Update operation names in the procedures of NSI provisioning TS 28.531CR0002
  • Introduce 5G NSI EF and procedure. TS 31.102CR0828
  • Correction of EF NSI length TS 31.102CR0846
Rel-16 5 changes

In Release 16, the specification introduced the Network Specific Identifier (NSI) as a new type of SUPI, distinct from an IMSI, and defined its format using a domain name as the Home Network Identifier. This release also addressed operational corrections for NSI activation and deactivation, and clarified performance measurement terms for NSI and NSSI. Furthermore, it resolved reporting scenarios to properly distinguish between the use of an IMSI or an NSI as the subscriber identifier.

  • SUCI value with SUPI format NSI TS 31.102CR0879
  • Fix NSI activation and deactivation use cases TS 28.531CR0045
  • Correction of NSI and NSSI Operations TS 28.531CR0061
  • PM terms for NSI and NSSI TS 28.552CR0016
  • Either IMSI or NSI - Report of SA3 S3-194455 Tdocs recommendation (in Rel16) TS 31.102CR0884
Rel-17 1 change

In Release 17, a specific correction was made to the state management procedures for the Network Slice Instance (NSI) and the Network Slice Subnet Instance (NSSI). This update refined the operational handling of these entities but did not alter the fundamental definition of the NSI Identifier itself, which remains an operator-specific string used to uniquely identify a Network Slice Instance within a PLMN or SNPN.

  • Correction to NSI and NSSI state management TS 28.541CR0467
Rel-18 3 changes

In Release 18, the standardization introduced a formal definition for the Network Slice Instance Identifier (NSI ID) as an operator-specific string to uniquely differentiate between multiple instances of the same network slice within a PLMN or SNPN. The release also updated procedures for the feasibility check and reservation of NSI and NSSI to align with a new FeasibilityCheckAndReservationJob. Furthermore, it provided clarifications on the semantics of the S-NSSAI and the NSI within the AmfEventArea data type.

  • NSI Identifier definition TS 23.003CR0678
  • Update procedure of feasibility check and reservation of NSI and NSSI to align with FeasibilityCheckAndReservationJob TS 28.531CR0218
  • Clarify the semantics of the S-NSSAI and the NSI in the AmfEventArea datatype TS 29.518CR1056

Explore further

Broader topics and technologies where NSI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.003 vj50 Numbering, addressing and identification in 3GPP Rel-19
TS 23.435 vj30 Network Slice Capability Exposure Procedures Rel-19
TS 23.501 vk00 5G System Architecture Stage 2 Rel-20
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TR 23.799 ve00 Study on Next Generation System Architecture Rel-14
TR 26.941 vj01 5G Media Slicing Extensions Rel-19
TS 28.202 vj00 5G Network Slice Management Charging Rel-19
TS 28.530 vj00 Network Slicing Concepts & Requirements Rel-19
TS 28.531 vk00 Management and Orchestration Rel-20
TS 28.535 vj00 Closed Control Loop Assurance Management Rel-19
TS 28.541 vk00 5G Network Resource Model (NRM) Stage 2/3 Rel-20
TS 28.545 vh00 Fault Supervision for 5G Networks Rel-17
TS 28.552 vk10 5G Performance Management Measurements Rel-20
TS 28.801 vf10 Management and Orchestration of Network Slicing Rel-15
TS 28.805 vg10 Management of Communication Services in 5G Rel-16
TR 28.808 vh00 5G satellite integration management study Rel-17
TR 28.812 vh10 Study on Intent Driven Management Services Rel-17
TR 28.841 vi01 Technical Report on IoT NTN Enhancements Rel-18
TS 28.861 vg00 SON for 5G Networks Management Rel-16
TS 29.518 vj50 AMF Service Based Interface Protocol Rel-19
TS 31.102 vj40 USIM Application Specification Rel-19
TR 32.847 vi00 Technical Report Rel-18
TS 32.899 vf10 5G Charging Architecture Study Rel-15
TS 33.117 vk00 Catalogue of General Security Assurance Requirements Rel-20
TS 33.757 vj00 Security for PLMN Hosting Non-Public Network Rel-19
TS 33.811 vf00 Security study for 5G network slicing management Rel-15
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.