Description
PIN Elements with Gateway Capability (PEGC) is a concept introduced in 3GPP Release 18, defined across multiple specifications including TS 23.501 and TS 29.583. It involves enhancing traditional PIN-based authentication elements with gateway capabilities to facilitate secure and efficient access in advanced network architectures like 5G. The architecture integrates PEGC into the authentication and security framework, where it acts as an intermediary between user equipment (UE) and network functions, providing both identity verification and gateway services. This is particularly relevant in scenarios involving network slicing, edge computing, and non-public networks (NPNs), where trusted access is critical.
In operation, PEGC works by leveraging PIN elements—such as those used in SIM cards or embedded secure elements—to authenticate users or devices, while the gateway capability allows it to route traffic, enforce policies, and manage connectivity. For example, in a network slice for industrial IoT, a PEGC might authenticate a sensor using its PIN credentials and then gateway the sensor's data to a specific slice instance, ensuring isolation and security. Key components include the PIN management function, which handles PIN verification, and the gateway function, which provides routing, filtering, and protocol translation. PEGC interfaces with other network functions via service-based interfaces (e.g., Nudm for authentication) or reference points, as detailed in specs like TS 24.501 and TS 33.127.
The role of PEGC in the network is to enhance security and flexibility in access control. It enables fine-grained authentication, where PIN elements are used not just for initial access but for ongoing verification in dynamic environments. By combining gateway capabilities, PEGC can also support traffic steering, for instance, directing authenticated users to localized edge services. This is vital for use cases like mission-critical communications or private 5G networks, where low latency and high reliability are required. PEGC contributes to the overall security architecture by providing a trusted point for identity assertion, reducing the risk of unauthorized access, and enabling seamless mobility across different network domains.
Purpose & Motivation
PEGC was created to address the evolving security and access needs of 5G networks, especially with the proliferation of network slicing, edge computing, and diverse device types (e.g., IoT sensors, AR/VR headsets). Prior approaches relied on separate authentication and gateway functions, which could lead to complexity, latency, and security gaps in dynamic scenarios. Limitations included inefficient handling of PIN-based authentication in gateway contexts, lack of integration with network slicing, and limited support for edge access, making it hard to ensure trusted and efficient connectivity for specialized services.
The motivation for PEGC stems from 3GPP's efforts to enhance network flexibility and security in Release 18 and beyond. It solves problems such as how to securely authenticate devices in edge locations without centralized servers, how to gateway traffic for isolated network slices, and how to simplify access control for non-public networks. Historically, PIN elements were used primarily for subscriber identity in cellular networks, but with PEGC, they are extended to provide gateway services, enabling a more integrated and scalable solution. This addresses the need for lightweight, yet robust, authentication mechanisms in decentralized architectures.
PEGC also supports the trend towards network automation and service-based architectures. By embedding gateway capabilities into PIN elements, it reduces the dependency on external gateways for basic routing, lowering latency and improving efficiency. This is particularly important for time-sensitive applications in industrial IoT or vehicular communications. The inclusion in multiple specs, from core network (23.501) to security (33.127), indicates its cross-cutting role in 5G evolution. PEGC helps operators deploy secure, slice-aware networks while maintaining backward compatibility with existing PIN-based systems, ensuring a smooth transition to more advanced authentication and access paradigms.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (186 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the PIN Element with Gateway Capability (PEGC) function was newly introduced as a specific type of UE within a Personal IoT Network (PIN). This UE-based PEGC provides DN connectivity via the 5G network for other PIN Elements and can also provide relay functionality for communication between them. The introduction of this function enables PIN-DN communication and PIN indirect communication for grouped IoT devices.
- Registration procedure triggered by a change of UE Radio Capability TS 24.501CR0278
- UE Core Network Capability handling TS 23.501CR0107
- Correction on capability negotiation on "SMS over NAS" TS 23.501CR0305
- Correction to UE Radio Capability handling TS 23.501CR0353
- UE radio capability for paging information with NR and eLTE connected to the CN TS 23.501CR0690
- UE sending UE Integrity Protection Data Rate capability over any access TS 23.501CR0695
+ 16 more changes
In Release 16, the PEGC (PIN Element with Gateway Capability) function was newly defined as a specific UE role within a Personal IoT Network (PIN). This UE, acting as a PEGC, gained the explicit capability to provide Data Network connectivity via the 5G network for other PIN Elements and to provide relay functionality for communication between PIN Elements. The release formally established that only a UE can act as a PEGC and that a PIN must include at least one such device.
- UPF Selection influenced by the indication of the identity/identities of 5G AN N3 User Plane capability TS 23.501CR0862
- CIoT capability negotiation between UE and network TS 24.501CR0987
- 5GMM capability for SRVCC from NG-RAN to UTRAN TS 24.501CR1187
- V2X capability and V2X PC5 capability TS 24.501CR1280
- 5GMM capability update for eNS TS 24.501CR1316
- Addition of LCS indication in 5GMM capability and 5GS NW capability TS 24.501CR1335
+ 41 more changes
In Release 17, the PEGC (PIN Elements with Gateway Capability) function was introduced as a new UE capability to enable Personal IoT Networks (PINs). Specifically, a PEGC is a UE that acts as a gateway, providing Data Network (DN) connectivity via the 5G network for other PIN Elements (PINEs) and/or providing relay functionality for communication between PINEs. This allows for PIN-DN communication and PIN indirect communication, facilitating managed IoT group connectivity.
- Alignment of NWDAF discovery of data exposure capability in TS 23.501. TS 23.501CR2759
- Introduction of MUSIM capability exchange TS 23.501CR2927
- Add target QoS flow capability for access performance measurement TS 24.501CR3248
- UE ProSe capability negotiation with 5GC TS 24.501CR3159
- MUSIM capability negotiation in 5GCN TS 24.501CR3402
- Support NSAG in 5GMM capability TS 24.501CR4295
+ 23 more changes
In Release 18, the PEGC (PIN Element with Gateway Capability) function was enhanced to enable the UE acting as a PEGC to support QoS differentiation for connected devices in the non-3GPP network behind it. This builds upon the foundational definition of a PEGC as a UE providing DN connectivity and relay functionality for other PIN Elements. The release also clarified that a single UE may simultaneously act as both a PEGC and a PEMC (PIN Element with Management Capability) within a Personal IoT Network.
- TS 23.501 Enhancing External Exposure of Network Capability TS 23.501CR3715
- Considering ML model management capability during ADRF discovery and selection TS 23.501CR3929
- CN based MT communication capability indication TS 23.501CR4081
- Extension of NWDAF registration information to reflect new accuracy checking capability TS 23.501CR3764
- Considering capability of UPF event exposure during UPF discovery TS 23.501CR4378
- NEF capability for the new AIML service TS 23.501CR4408
+ 57 more changes
In Release 19, the PEGC (PIN Element with Gateway Capability) function was introduced as a new UE role within a Personal IoT Network (PIN). Specifically, a PEGC is defined as a UE with the ability to provide Data Network connectivity via the 5G network for other PIN Elements and/or to provide relay functionality for communication between PIN Elements. This establishes the foundational architecture for PIN-DN communication and PIN indirect communication via the 5G system.
- Handling of UE capability for MPQUIC-IP and MPQUIC-E steering functionalities TS 23.501CR5844
- Enhancement of 5G ProSe capability for multi-hop relays TS 24.501CR6552
- Update 5GMM capability for 5G ProSe multi-hop relays TS 24.501CR6692
- Update 5GMM capability for IM relay TS 24.501CR6937
- NW capability for multiple LCS-UPP connections per UE TS 24.501CR6953
- Support of QoS monitoring capability configuration and transfer within 5GC TS 23.501CR5402
+ 19 more changes
Explore further
Broader topics and technologies where PEGC plays a role.
Defining Specifications
3GPP specifications that define or reference PEGC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 23.542 vk10 | Application layer support for Personal IoT Network | Rel-20 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 24.583 vj00 | Application Layer Support for Personal IoT Network | Rel-19 |
| TR 26.806 vi00 | Technical Report on Smartly Tethering AR Glasses | Rel-18 |
| TS 29.583 vj00 | PINAPP Stage 3 Protocol for PIN-9 Interface | Rel-19 |
| TS 33.127 vj50 | Lawful Interception Architecture and Functions | Rel-19 |
| TR 33.882 vi01 | Technical Report on 5G Security for Personal IoT Networks | Rel-18 |