Description
The Packet Data Gateway (PDG) is a critical network element within the 3GPP architecture, specifically defined for the core network domain. It functions as an access-agnostic gateway, providing connectivity between the user's device (User Equipment, UE) and external IP networks, known as Packet Data Networks (PDNs). The PDG is a central anchor point for the user's IP session. It performs several key roles: it establishes and manages IPsec tunnels (using IKEv2) with the UE to ensure secure data transmission, it acts as a policy enforcement point for applying Quality of Service (QoS) and charging rules, and it performs network address translation and IP address allocation for the UE.
Architecturally, the PDG resides in the home network of the subscriber. It interfaces with the 3GPP AAA (Authentication, Authorization, and Accounting) server for user authentication and authorization. It also connects to the Online Charging System (OCS) and Offline Charging System (OFCS) for billing. The PDG's operation involves several protocols. It uses the Wm reference point to communicate with the 3GPP AAA server for authentication. The user data plane traffic flows through the PDG via the established IPsec tunnel (over the Wn reference point from the access network) and is then routed to the external PDN (via the Wi reference point). The PDG also supports the Gateway GPRS Support Node (GGSN)-like functionality for specific access types, acting as the topological anchor for the user's IP address.
In the broader network evolution, the PDG was a foundational element for enabling secure, non-3GPP access (like WLAN) to 3GPP core network services, a concept formalized as Interworking WLAN (I-WLAN). It ensured that users could access operator services securely from any IP-based access network, with consistent authentication, authorization, and policy application. The PDG's design principles of secure tunneling, policy enforcement, and session anchoring were later evolved and incorporated into more advanced gateways like the evolved Packet Data Gateway (ePDG) for untrusted non-3GPP access in EPS, and the Non-3GPP InterWorking Function (N3IWF) in 5G systems.
Purpose & Motivation
The PDG was created to solve the problem of secure and seamless integration of non-3GPP IP access networks (primarily Wireless Local Area Networks - WLANs) with the 3GPP mobile core network. In the early 2000s, WLAN technology became widespread, but it lacked the integrated security, mobility management, and billing frameworks of cellular networks. The 3GPP standards body needed a way to allow mobile operators to extend their services over WLAN, creating a unified user experience.
The PDG addressed this by providing a standardized gateway in the operator's core network that could terminate secure tunnels from devices on untrusted IP networks. This solved several key issues: it provided strong authentication using SIM credentials (via the AAA server), it encrypted all user traffic from the device to the operator's network, and it allowed the operator to apply the same service policies and charging mechanisms as used for cellular data. This enabled new business models like 'Operator WiFi' and was a crucial step in the convergence of cellular and IP networks. It laid the groundwork for the future vision of access-agnostic service delivery, which is a cornerstone of 4G and 5G architectures.
Classification
Evolution Across Releases
Initial introduction of the PDG concept as part of the 3GPP system architecture for packet-switched services. Established its role as a gateway for GPRS, defining basic connectivity and routing functions between the core network and external data networks.
Explore further
Broader topics and technologies where PDG plays a role.
Defining Specifications
3GPP specifications that define or reference PDG, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.234 vd10 | 3GPP-WLAN Interworking Index Specification | Rel-13 |
| TR 22.980 vj00 | Network Composition Feasibility Study | Rel-19 |
| TS 23.125 v1700 | Flow Based Charging Architecture | Rel-7 |
| TS 23.141 vj00 | Presence Service Stage 2 Architecture | Rel-19 |
| TS 23.234 vd10 | 3GPP-WLAN Interworking Index | Rel-13 |
| TS 24.229 vj50 | IMS call control protocol based on SIP and SDP | Rel-19 |
| TS 24.234 vc20 | 3GPP-WLAN Interworking Network Selection | Rel-12 |
| TS 24.327 vc00 | Mobility between I-WLAN and GPRS | Rel-12 |
| TS 28.601 vc00 | Telecom management; CN and non-3GPP access NRM IRP Requirements | Rel-12 |
| TS 28.602 vc00 | CN & non-3GPP NRM IRP Information Service | Rel-12 |
| TS 29.161 vc00 | 3GPP-WLAN Interworking Requirements | Rel-12 |
| TS 29.234 vb20 | WLAN-3GPP Interworking Stage-3 Protocol | Rel-11 |
| TS 32.240 vj40 | Charging Management Architecture & Principles | Rel-19 |
| TS 32.252 vc00 | 3GPP WLAN Interworking Charging | Rel-12 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 33.107 vj00 | Lawful Interception Architecture & Functions | Rel-19 |
| TS 33.108 vj00 | LI Handover Interface Specification | Rel-19 |
| TS 33.234 vj00 | 3GPP-WLAN Interworking Security | Rel-19 |
| TS 33.822 v1800 | Security Architecture for Inter-Access Mobility | Rel-8 |