PNI-NPN

Public Network Integrated Non-Public Network

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

PNI-NPN is a 3GPP architecture that enables Non-Public Networks using a public operator's infrastructure, providing dedicated, isolated network slices for enterprises while leveraging the operator's existing radio and core network assets.

Category
Network Slicing
Introduced
Rel-16
Where
Radio Access Network › NG-RAN (5G)
Also touches
4 segments
Specifications
24 specs
PNI-NPN Description Purpose Detected Changes Specifications

Description

Public Network Integrated Non-Public Network (PNI-NPN) is a 3GPP standardized model for deploying Non-Public Networks (private networks) by utilizing the physical infrastructure and spectrum resources of a public mobile network operator. Introduced in Release 16 as part of the 5G system enhancement for vertical industries, it is defined across a comprehensive set of specifications covering architecture, procedures, and management. The core concept is to create logically isolated network slices within the public network's infrastructure to serve specific enterprise customers or verticals, providing them with the dedicated performance, security, and control characteristics of a private network.

Architecturally, a PNI-NPN is realized through the 5G network slicing framework. The public network operator's 5G Core (5GC) and Radio Access Network (RAN) are partitioned to create dedicated network slices for the NPN. These slices include dedicated core network functions (e.g., SMF, UPF) and may involve dedicated radio resources or shared resources with quality-of-service (QoS) isolation. Key components include the Network Slice Selection Assistance Information (NSSAI) to identify the slice, enhanced access control mechanisms to restrict NPN access to authorized User Equipment (UE), and potentially a dedicated Network Identifier (PNI-NPN ID) for discovery. The architecture supports both Standalone Non-Public Networks (SNPN) and PNI-NPN models, with PNI-NPN specifically relying on the public network's PLMN ID.

From an operational perspective, a UE accesses the PNI-NPN by connecting to the public network's cells and then being routed to the dedicated slice based on subscription and network policies. The 5GC ensures traffic isolation between the PNI-NPN slice and other public network traffic. Management and orchestration of the PNI-NPN slice are handled by the public network operator, often using service management interfaces exposed to the enterprise customer. This allows the enterprise to monitor and control aspects of their dedicated slice, such as QoS policies or connected device lists, without managing the underlying physical infrastructure.

The PNI-NPN model works in conjunction with features like Closed Access Group (CAG) to control access at the cell level, ensuring that only UEs belonging to a specific enterprise can utilize certain radio resources. It also integrates with mechanisms for network discovery and selection, where a UE can identify available PNI-NPNs. The role of PNI-NPN in the network is to bridge the gap between fully private, standalone deployments and public mobile broadband, offering a cost-effective and scalable solution for enterprise 5G adoption by leveraging existing operator investments and spectrum licenses.

Purpose & Motivation

PNI-NPN was created to address the growing demand from industries for private 5G networks without requiring them to acquire and manage their own licensed spectrum and full network infrastructure. Prior to its standardization, enterprises seeking dedicated wireless performance had limited options: deploy a Wi-Fi network with its limitations in mobility, reliability, and determinism, or invest in a costly standalone private mobile network. PNI-NPN solves this by allowing public network operators to offer 'private network as a service' using their existing assets.

The primary problem it solves is providing enterprises with the tailored performance (ultra-reliable low latency, high bandwidth, device density), security, and data privacy of a private network, but with the operational simplicity and economic benefits of a service model. It addresses the limitations of previous approaches by leveraging the advanced network slicing and QoS capabilities of 5G Standalone (SA) architecture. This enables multiple, isolated logical networks to run on shared physical infrastructure, making private network features accessible to a wider range of small and medium-sized enterprises.

Historically, Release 16's focus on verticals and industrial IoT created the impetus for this model. It was motivated by the need to unlock the 5G market for manufacturing, logistics, healthcare, and other sectors. PNI-NPN allows operators to monetize their 5G investments beyond consumer broadband, while enterprises gain a future-proof, standardized, and carrier-grade solution for their critical communications, accelerating digital transformation across industries.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 5 changes

In Release 16, the PNI-NPN function was enhanced to specify mechanisms for authentication, mobility, and dual connectivity in mixed cell scenarios with a public PLMN. It introduced procedures for reusing NSSAI for AMF selection when network isolation is required and defined the CAG (Closed Access Group) configuration update process. The release also provided clarifications on the consistent use of the PNI-NPN term across RAN specifications.

  • PNI-NPN - Reusing NSSAI for AMF selection when NPN isolation is needed TS 23.501CR1997
  • 23.501: Revision on PNI-NPN CAG Configuration Update TS 23.501CR2430
  • Authentication in PNI-NPN TS 33.501CR0747
  • Clarifying the use of PNI-NPN term in RAN specifications TS 38.300CR0324
  • Handling of mobility and dual connectivity in mixed PNI-NPN/PLMN cell scenarios TS 38.300CR0398
Rel-17 2 changes

In Release 17, the PNI-NPN function was enhanced to enable a UE to simultaneously receive data services from both the PNI-NPN and a public PLMN. Additionally, editorial clarifications were made by removing an Editor's Note concerning the security aspects of PNI-NPNs.

  • Simultaneous data service from PNI-NPN and PLMN TS 23.501CR2902
  • Removing Editor's Note on PNi-NPN security aspects TS 33.501CR1304
Rel-18 4 changes

In Release 18, the PNI-NPN function saw the introduction of a new charging principle to govern its operation. Furthermore, the release included several corrections to refine the Minimization of Drive Tests (MDT) functionality specifically for use within PNI-NPN deployments.

  • Addition of charging principle for PNI-NPN TS 32.255CR0499
  • Correction on MDT for PNI-NPN TS 37.320CR0133
  • Corrections on MDT for PNI-NPN TS 38.413CR1174
  • Corrections on MDT for PNI-NPN TS 38.423CR1288

Explore further

Broader topics and technologies where PNI-NPN plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.289 vk10 Mission Critical services over 5G System Rel-20
TS 23.501 vk00 5G System Architecture Stage 2 Rel-20
TS 24.501 vj50 5G NAS Protocols Specification Rel-19
TS 24.554 vj40 5G Proximity Services (ProSe) Protocols Rel-19
TS 28.203 vi10 Charging management Rel-18
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.828 vi00 Charging Aspects for Non-Public Networks Rel-18
TR 28.907 vj00 Enhanced Management of Non-Public Networks Rel-19
TS 31.111 vj30 USIM Application Toolkit (USAT) Specification Rel-19
TS 32.255 vk10 Telecom Management; Charging for 5G Data Connectivity Rel-20
TS 32.422 vk00 Telecom Management: Trace Control & Configuration Rel-20
TS 33.501 vk00 5G Security Architecture and Procedures Rel-20
TS 33.757 vj00 Security for PLMN Hosting Non-Public Network Rel-19
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.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
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.