Network Identifier

Description

The Network Identifier (NID) is a critical component in 3GPP's architecture for Stand-alone Non-Public Networks (SNPNs), introduced to enable private cellular network deployments. An SNPN is a 5G network operated for private use (e.g., by an enterprise, factory, or utility) that does not rely on a Public Land Mobile Network (PLMN) for core network functions. To uniquely identify such a network globally, a two-part identifier is used: a PLMN ID (Public Land Mobile Network Identity) and a NID. The PLMN ID (MCC+MNC) in this context identifies the SNPN operator, which could be the enterprise itself or a third-party private network operator, and is not necessarily a traditional public operator code. The NID is a 20-bit to 32-bit value (typically represented as 5 to 8 hexadecimal digits) that uniquely identifies a specific network under that PLMN ID.

Architecturally, the NID is broadcast in the system information (SIB1) by the 5G radio cells (gNBs) belonging to the SNPN. A User Equipment (UE) configured to access an SNPN will have one or more SNPN subscription identifiers stored in its Universal Subscriber Identity Module (USIM) or in device configuration. This identifier is a combination of the PLMN ID and the NID. During initial cell selection and network registration, the UE reads the broadcast PLMN ID and NID and compares it with its configured list. If a match is found, the UE proceeds to attach to that SNPN. The NID is carried in key NAS (Non-Access Stratum) messages, such as the Registration Request, to inform the network core of the specific network the UE is attempting to access.

How it works involves several layers. At the physical and RRC layer, the NID is broadcast, allowing UE discovery. At the NAS layer, it is used for network selection and registration. Within the core network, the Network Function (NF) responsible for access management, the Access and Mobility Management Function (AMF), uses the received PLMN ID and NID to route the registration request to the correct network slice and authentication infrastructure specific to that SNPN. The Authentication Server Function (AUSF) will use the full SNPN identifier (PLMN ID + NID) to select the correct credentials and authentication method for that private network. This ensures complete logical isolation between different SNPNs, even if they share the same radio spectrum or are managed by the same infrastructure provider.

Key components include the NID value itself, the broadcast mechanism in system information, the UE's configuration storage for SNPN identifiers, and the core network's routing and subscription lookup based on the combined PLMN+NID. Its role is fundamental to the SNPN concept, providing the granularity needed to support multiple, independent private networks within a shared operator space. It enables features like closed access groups, where only pre-configured UEs can access the network, and forms the basis for secure, isolated private network operation as envisioned for Industry 4.0, campus networks, and critical infrastructure.

Purpose & Motivation

The NID was created to solve the fundamental problem of identifying and isolating private cellular networks in a standardized global framework. Prior to its introduction, private networks often used closed subscriber groups (CSG) within a public PLMN or operated as completely isolated islands with non-standard identifiers, leading to interoperability issues and management complexity. The rise of Industry 4.0, smart factories, and critical infrastructure demanded dedicated, secure, and reliable 5G networks that could operate independently of public MNOs. The SNPN concept, enabled by the NID, was the 3GPP-standardized answer to this demand.

It addresses the limitation of the PLMN ID alone, which is designed for public operators. An enterprise deploying a private network is not a public operator and should not need a globally unique MNC from the scarce ITU-administered pool just for its internal network. The NID provides the necessary additional namespace under a designated PLMN ID (which could be a dedicated range for private network use, e.g., using the MCC '999' as defined for test/private networks). This allows an infinite number of private networks to be created under a single PLMN ID, simplifying administration while ensuring global uniqueness through the combination.

Furthermore, the NID enables clear network selection for devices. A device can be configured with subscriptions to multiple different SNPNs (e.g., for different corporate campuses or roles). The broadcast NID allows the device to automatically identify and connect to the correct one. This is crucial for automated industrial equipment, drones, and sensors that must operate in specific, controlled network environments. The creation of the NID and the SNPN framework in 3GPP Release 16 was a direct response to strong market demand for standardized private 5G, moving beyond proprietary solutions and ensuring device and network interoperability across different vendors and vertical industries.