Description
A Non-Public Network (NPN) is a 5G network system intended for the private use of an entity such as an enterprise, utility, government, or industrial facility. It is defined by 3GPP as a network that is not offered to the general public. NPNs can be deployed as fully standalone systems or can be integrated with a public land mobile network (PLMN) for certain services. The architecture is built upon the standard 3GPP 5G System (5GS) but is tailored for private operation, offering dedicated and predictable performance, ultra-reliable low-latency communication (URLLC), and enhanced data privacy and security within a defined geographical area like a factory floor, port, mine, or campus.
NPNs operate using the core 5G network functions (NFs) such as the Access and Mobility Management Function (AMF), Session Management Function (SMF), and User Plane Function (UPF), which can be deployed on-premises or in a dedicated cloud. They utilize 5G New Radio (NR) for wireless access, potentially operating in licensed, shared, or unlicensed spectrum (e.g., 5G NR-U). A key architectural concept is the Network Identifier (NID), which, used in conjunction with a PLMN ID, uniquely identifies an NPN. Standalone NPNs (SNPNs) operate completely independently with their own credentials and identity, while Public Network Integrated NPNs (PNI-NPNs) leverage network slices or dedicated resources from a public PLMN operator to provide NPN services.
How it works: Devices (UEs) configured for the NPN discover and select the network based on broadcast identifiers. For SNPNs, authentication and authorization are performed using credentials managed by the private entity, not a public MNO. Network policies, such as access control, QoS prioritization for critical machinery, and local breakout of data traffic, are enforced by the locally deployed 5G core functions. This allows sensitive data to remain on-site, ensures low latency for industrial control loops, and provides the enterprise with full administrative control over their network resources, user devices, and services.
Purpose & Motivation
NPNs were created to meet the demanding connectivity requirements of vertical industries (e.g., manufacturing, logistics, energy) that cannot be fully satisfied by best-effort public mobile networks. Public networks are designed for broad coverage and high capacity but offer limited guarantees on latency, reliability, data locality, and administrative control. Industries undergoing digital transformation (Industry 4.0) require deterministic performance for applications like automated guided vehicles, real-time process control, augmented reality for maintenance, and massive sensor networks.
The motivation for standardizing NPNs in 3GPP (starting in Release 16) was to provide a unified, interoperable framework for private 5G, moving away from proprietary solutions. It addresses the limitations of previous approaches like Wi-Fi (which lacks seamless mobility, ultra-reliability, and native support for network slicing) and early non-standardized private LTE systems. NPNs leverage the full capabilities of 5G—including network slicing, edge computing, and precise QoS—in a dedicated environment. They solve problems of data sovereignty, mission-critical communication reliability, and integration with industrial operational technology (OT) systems, enabling enterprises to build a secure, high-performance wireless infrastructure tailored to their specific operational needs.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (85 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 16, the Non-Public Network (NPN) function was formally introduced, defining both standalone operation (SNPN) and integration with a Public Land Mobile Network (PLMN). The release specified mechanisms for UE identification and selection of an NPN, including access control for PLMN-integrated NPNs, and introduced requirements for supporting SNPN cellular hotspots. It also enabled features like unified access control, network slicing coordination between NPNs and PLMNs, and the ability for an MNO to host and manage a non-public network.
- TS 23.501: Introducing Non-public network TS 23.501CR0734
- Introducing Non-public network TS 23.501CR0734
- FQDN format of N3IWF in a standalone non-public network TS 23.501CR0841
- Introduction of non-public network TS 24.501CR1054
- Corrections to 38.304 for supporting IAB in NPN TS 38.304CR0157
- Corrections to 38.331 for supporting IAB in NPN TS 38.331CR1590
+ 38 more changes
In Release 17, NPN enhancements introduced support for IMS emergency services and Public Warning System (PWS) in Standalone Non-Public Networks (SNPNs). The release also added mechanisms for secure remote credential provisioning for IoT devices and for an MNO to update a UE's subscription to allow on-demand connectivity to a desired NPN. Furthermore, it clarified support for simultaneous data services from both a PNI-NPN and a PLMN.
- Supporting IMS emergency for NPN TS 22.261CR0425
- Introducing NPN enhancements: Credential Holders, Onboarding, IMS emergency, and PWS support in SNPNs TS 38.300CR0414
- Introducing NPN enhancements: Credentials Holder, UE Onboarding, and IMS emergency support in SNPNs TS 38.331CR2925
- Simultaneous data service from PNI-NPN and PLMN TS 23.501CR2902
- Clarification of ProSe support in NPN TS 24.501CR4203
- Removing Editor's Note on PNi-NPN security aspects TS 33.501CR1304
+ 1 more changes
In Release 18, the NPN (Non-Public Network) function was enhanced with new management and monitoring capabilities. Specifically, the release introduced solutions for NPN fault management, the management of NPN service customers, and SLA monitoring and assurance. It also added architectural considerations for NPN charging and expanded support for managing shared and dedicated resources within an NPN.
- Add use case and requirements for NPN fault management TS 28.557CR0002
- Add use case and requirements for management of NPN service customer TS 28.557CR0003
- Add solution for NPN fault management TS 28.557CR004
- Add solution for management of NPN service customer TS 28.557CR005
- Rel-18 CR TS 28.557 Add solution for SLA monitoring and assurance in NPN TS 28.557CR0011
- Rel-18 CR TS 28.557 Add solution for shared and dedicated resources in NPN TS 28.557CR0012
+ 22 more changes
In Release 19, the NPN function was enhanced with new requirements for security considerations and the support for Proximity Services (ProSe) within NPNs. It also introduced specific security mechanisms for a PLMN hosting an NPN and updated the area scope definition for NPN support in management specifications. Furthermore, the release expanded on the combined operation and management of hosted non-public networks with private PLMN slices through defined APIs.
- Add requirements on NPN security considerations TS 22.261CR0688
- ProSe and NPN TS 24.501CR6392
- Security for PLMN hosting a NPN TS 33.501CR2137
- ProSe support in NPN [ProSe_NPN] TS 38.300CR0957
- ProSe support in NPN [ProSe_NPN] TS 38.331CR5209
- Rel-19 CR TS 28.622 Update area scope definition for NPN support (stage 2) TS 28.622CR0584
Explore further
Broader topics and technologies where NPN plays a role.
Defining Specifications
3GPP specifications that define or reference NPN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.261 vk30 | 5G System Service Requirements | Rel-20 |
| TR 22.832 vh40 | Study on cyber-physical control in vertical domains | Rel-17 |
| TS 23.289 vk10 | Mission Critical services over 5G System | Rel-20 |
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TR 26.805 vh01 | Study on Media Production over 5G NPN Systems | Rel-17 |
| TR 26.942 vj00 | Study on Media Energy Consumption Exposure & Evaluation | Rel-19 |
| TS 28.557 vj00 | Management of Non-Public Networks (NPN) | Rel-19 |
| TS 28.622 vk20 | Telecommunication Management; Generic NRM Information Service | Rel-20 |
| TR 28.807 vh00 | Study on NPN Management | Rel-17 |
| TR 28.843 vi10 | Technical Report on Charging Aspects for Vertical Scenarios | Rel-18 |
| TR 28.907 vj00 | Enhanced Management of Non-Public Networks | Rel-19 |
| TS 29.244 vj40 | PFCP Specification for Control/User Plane Separation | Rel-19 |
| TS 32.255 vk10 | Telecom Management; Charging for 5G Data Connectivity | Rel-20 |
| TS 33.501 vk00 | 5G Security Architecture and Procedures | Rel-20 |
| TS 33.776 vj00 | Study of ACME for 5G SBA | Rel-19 |
| TS 33.819 vg10 | 5GS Security for Vertical & LAN Services | Rel-16 |
| TS 37.320 vj00 | Minimization of Drive Tests (MDT) Overview | Rel-19 |
| TS 37.483 vj10 | E1 Application Protocol (E1AP) | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TS 38.304 vj00 | UE RRC_IDLE and RRC_INACTIVE Procedures | Rel-19 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |
| TS 38.401 vj10 | NG-RAN Architecture Specification | Rel-19 |
| TS 38.413 vj10 | NG Application Protocol (NGAP) | Rel-19 |
| TS 38.423 vj10 | Xn Application Protocol (XnAP) specification | Rel-19 |
| TS 38.463 vj00 | E1 Application Protocol (E1AP) | Rel-19 |
| TS 38.473 vj10 | 5G F1 Application Protocol (F1AP) | Rel-19 |
