Non-Public Network

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.

Key Features

• Dedicated network operation for a single organization (enterprise, factory)
• Support for both Standalone NPN (SNPN) and Public Network Integrated NPN (PNI-NPN) models
• Use of Network Identifier (NID) for unique identification
• On-premises or localized deployment of 5G core network functions
• Enhanced control over security, authentication, and data privacy
• Support for critical 5G capabilities like URLLC, mMTC, and network slicing within the private domain

Evolution Across Releases

Defining Specifications