Registered SNPN

Description

RSNPN, or Registered SNPN, is a critical identifier within the 5G system architecture for Standalone Non-Public Networks (SNPNs). An SNPN is a network deployed for private use, such as by an enterprise or factory, which operates independently of public network operator credentials (like PLMNs). The RSNPN specifically denotes the particular SNPN where a User Equipment (UE) has successfully completed registration and authentication procedures. This registration process is defined in 3GPP TS 24.501, which specifies the Non-Access Stratum (NAS) protocol for 5G systems. Upon successful registration, the UE and the network mutually acknowledge the RSNPN identity, establishing a secure context for subsequent communication.

The architecture supporting RSNPN involves core network functions like the Access and Mobility Management Function (AMF) and the Authentication Server Function (AUSF). When a UE attempts to access an SNPN, it provides a Network Identifier (NID) combined with a PLMN ID (which for an SNPN is a dedicated, standardized value). The AMF, in coordination with the AUSF, authenticates the UE based on credentials specific to that private network, such as credentials from the SNPN operator or a credential holder. Successful authentication and registration lead to the establishment of an RSNPN context. This context is used for session management, mobility management, and policy enforcement within the confines of that specific private network.

The role of RSNPN is fundamental for network selection, access control, and service continuity within private 5G deployments. It ensures that a UE only accesses services and resources authorized for that specific SNPN. The identifier is used in NAS signaling messages to maintain the registration state and is crucial during mobility events, such as handovers between cells belonging to the same SNPN. It enables the network to apply specific network slices, QoS policies, and security settings configured for that private network. For network operators and enterprises, RSNPN provides a clear demarcation, allowing multiple isolated private networks to coexist without interference, even if they share underlying physical infrastructure.

Purpose & Motivation

RSNPN was introduced in 3GPP Release 16 to address the growing demand for private, standalone 5G networks. Prior to SNPNs, private network deployments often relied on public network slices or isolated PLMNs, which could involve dependencies on public mobile network operators. The motivation was to enable industries like manufacturing, logistics, and utilities to deploy and operate their own 5G networks completely independently, with full control over security, performance, and user management. RSNPN as a concept solves the problem of unambiguous identification and access control for UEs within these autonomous networks.

It addresses limitations where earlier solutions for private access, such as Closed Access Groups (CAGs) for Non-Public Networks (NPNs) deployed with public network support, still required public network infrastructure. RSNPN facilitates a pure private network model, eliminating any reliance on a public PLMN for core network functions. This is essential for use cases requiring maximum isolation, data sovereignty, and tailored network characteristics. The creation of the RSNPN identifier formalizes the registration state, ensuring that mobility and session management procedures are correctly anchored to the private network's context, enabling reliable and secure industrial IoT and mission-critical communications.