Non-Public Network

In Release 15, the foundational concept of the Non-Public Network (NPN) was introduced to provide exclusive network access for specific sets of users and purposes, catering to vertical industry needs. The release established that 5G system requirements generally apply to both NPNs and PLMNs, and it specified mechanisms for an MNO to operate a hosted NPN and coordinate its services with slices in a public PLMN. Furthermore, it defined support for secure, remote credential provisioning for IoT devices specifically within an NPN.

• Storing Configured NSSAI when the PLMN is changed TS 24.501CR0203
• Network sharing prioritised PLMN handling TS 23.501CR0056
• Inter-PLMN mobility when N26 is not used TS 23.501CR0070
• Non-Allowed Area as criterion for Cell Reselection or trigger for PLMN Selection TS 23.501CR0076
• 5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI TS 23.501CR0087
• Clarification on usage of PLMN ID received via PCO during PDN connection establishment TS 23.501CR0383

+ 22 more changes

In Release 16, the NPN function was formally introduced, defining non-public networks intended for exclusive use by a specific set of users. It specifically added support for Stand-alone Non-Public Networks (SNPNs) and detailed mechanisms for a UE to access an NPN via encrypted connection, including the ability for an MNO to update a UE's subscription to allow on-demand connectivity to a desired NPN. The release also addressed security requirements for non-public networks and support for emergency services in public network integrated NPNs.

• TS 23.501: Introducing Non-public network TS 23.501CR0734
• Introducing support for Non-Public Networks TS 23.501CR0757
• New clause for URLLC supporting TS 23.501CR0810
• Introducing Non-public network TS 23.501CR0734
• FQDN format of N3IWF in a standalone non-public network TS 23.501CR0841
• Support of emergency services in public network integrated NPNs TS 23.501CR1073

+ 137 more changes

In Release 17, key NPN enhancements included support for IMS emergency services within SNPNs and mobility between SNPNs and between SNPNs and PLMNs. It also introduced mechanisms for updating subscription credentials for SNPN access and provided support for Disaster Roaming, allowing users from a failed PLMN to register on other networks. Furthermore, the release added support for Public Warning System (PWS) messages in SNPNs.

• Supporting IMS emergency for NPN TS 22.261CR0425
• Informative guideline on supporting session/service continuity between SNPN and PLMN when using N3IWF TS 23.501CR2563
• Adding the usage of Redundant Transmission Experience analytics for URLLC service TS 23.501CR2581
• User Plane Remote Provisioning of UEs if PLMN as ON TS 23.501CR2802
• Mobility support between SNPNs and between SNPN and PLMN TS 23.501CR2826
• PLMN with disaster condition TS 24.501CR3585

+ 75 more changes

In Release 18, enhancements for Non-Public Networks (NPN) introduced support for a UE to access multiple NPNs simultaneously and expanded management capabilities. Specifically, the release added solutions for NPN fault management, SLA monitoring and assurance, and the management of NPN service customers and their shared or dedicated resource demands. Furthermore, it introduced charging architecture considerations for NPNs and enhanced Management Data Collection (MDT) to operate with an NPN area scope.

• Support multiple non-public networks access and corresponding simultaneous services for a UE TS 22.261CR0564
• Edge Relocation within the same hosting PLMN's EHEs TS 23.501CR3820
• KI#4: Support for Centralized NSACF in a PLMN with multi-service areas TS 23.501CR3822
• 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

+ 68 more changes

In Release 19, key enhancements for Non-Public Networks (NPN) included the introduction of ProSe (Proximity Services) support within NPNs, enabling direct device-to-device communication and relaying for scenarios like Public Safety. The release also added specific security considerations for PLMNs hosting an NPN and introduced token-based authorization mechanisms for secure indirect communication when a Network Function is selected at a target PLMN. Furthermore, requirements were defined for a PLMN operator to provide location reporting information to an NPN and for the system to support mechanisms for an MNO to update a UE's subscription to allow on-demand connectivity to a desired NPN.

• Add requirements on NPN security considerations TS 22.261CR0688
• Location reporting information obtained from the PLMN operator (5G) TS 23.289CR0126
• NF discovery and selection by target PLMN TS 23.501CR5399
• Enhancement of getting public UE IP address and port number TS 23.501CR5445
• ProSe and NPN TS 24.501CR6392
• Storage and replacement of RAT utilization control information associated to the current PLMN TS 24.501CR6460

+ 18 more changes

In Release 20, the NPN function introduced a specific correction for roaming scenarios by replacing appended PLMN ID access token claims with PLMN ID specific claims to resolve a misalignment with the technical specification for the network function repository. This update refined the credential mechanism for authorizing UE access to non-public networks, ensuring proper interoperability when extending services through a PLMN as required by the 5G system architecture.

• MCC Editorial update for publication after TSG SA approval (SA#109) TS 23.700
• Correction of misalignment with TS 29.510: Replace appended PLMN ID access token claims with PLMN ID specific claims in roaming TS 33.501CR2214