3GPP Non-Public Network standards and deployment models (SNPN, PNI-NPN) for private 5G media production and contribution.
Overview
5G-MAG tracks 3GPP Non-Public Network (NPN) standards for private 5G media production and contribution. For the technical analysis of NPN deployment models, identity/onboarding and QoS considerations, see the Tech page linked below. For acronyms used here, see the Glossary.
Technology & Analysis
Analysis documents and reference material on the developer/technical side.
NPN Deployment Models
Both deployment models are defined in the NPN clause of TS 23.501 (SNPN and PNI-NPN are described in the two sub-clauses of that clause).
- Standalone NPN (SNPN): Independent 5G network with its own core, not relying on a public land mobile network (PLMN). Identified by the combination of a PLMN ID and a Network Identifier (NID).
- Public Network Integrated NPN (PNI-NPN): NPN made available through a PLMN, for example by means of a dedicated Data Network Name (DNN) or one or more network slice instances allocated for the NPN, using a Closed Access Group (CAG) to control which subscribers may access the relevant cells.
Specifications by Release
The NPN feature set has grown across releases. The following is an orientation, not a substitute for the 3GPP work plan.
- Release 16: Baseline NPN. Introduced the SNPN and PNI-NPN models, the NID for SNPN, and the CAG mechanism for PNI-NPN. Architecture in the NPN clause of TS 23.501.
- Release 17: SNPN enhancements. Credentials Holder support (credentials owned by a separate 3GPP or non-3GPP entity such as an AAA server), UE onboarding and remote provisioning, and equivalent-SNPN handling. Related VIAPA requirements work continued in TS 22.263.
- Release 18 and later: Continued refinements to NPN mobility, service continuity between SNPN and PLMN, and localised services. Confirm the specific enhancements and their release placement against the current 3GPP work plan.
Key 3GPP Specifications
The specifications in scope of Non-Public Networks, grouped by the layer they define: the stage 1 requirements, the system architecture, the stage 3 access and authentication procedures, and the study that fed them.
| Specification | Title | Layer |
|---|---|---|
| TS 22.263 | Service requirements for Video, Imaging and Audio for Professional Applications (VIAPA)the stage 1 requirements anchor most often cited when NPNs are discussed for broadcast use | Service requirements |
| TS 23.501 | System Architecture for the 5G SystemNon-Public Network aspects, clause 5.30 | System architecture |
| TS 23.502 | Procedures for the 5G SystemNPN procedures | System architecture |
| TS 24.501 | Non-Access-Stratum (NAS) protocol for 5GS; Stage 3carries the SNPN-specific registration and authentication procedures (credential-owner vs. separate credential-holder models, SUCI handling) | Access and authentication |
| TS 24.502 | Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks; Stage 3 | Access and authentication |
| TS 33.501 | Security architecture for 5GSNPN security aspects | Access and authentication |
| TR 23.700-07 | Study on enhanced support of Non-Public Networks | Studies |
5G-MAG tracking and contribution focus
5G-MAG tracks NPN standardisation as it applies to media production and contribution, in particular the VIAPA requirements, the SNPN and PNI-NPN deployment models, device onboarding at scale, and the combination of NPN with TSC for deterministic essence transport and with RTC for interactive contribution. See the Tech: Non-Public Networks page for the detailed analysis.
Related Standards Work
- Standards: Connectivity Quality with Network APIs
- Standards: Time Sensitive Communications: TSC for professional media production is typically deployed over an NPN
- Standards: Real-Time Communications (RTC): interactive, uplink-heavy contribution over an NPN
- Tech: Non-Public Networks: analysis documents and reference material on the developer/technical side
- Feedback and Requirements: how 5G-MAG submits feedback and requirements to SDOs
Refer to the Standards repository to contribute to this documentation.