Packet Data Network Gateway

Description

The Packet Data Network Gateway (P-GW) is a fundamental component of the Evolved Packet Core (EPC) architecture defined in 3GPP Release 8 and beyond. It functions as the primary gateway between the mobile operator's network and external Packet Data Networks (PDNs), such as the public internet, IMS, or private corporate networks. The P-GW is the point of entry and exit for all user plane IP traffic for a UE. It is responsible for assigning the UE an IP address (via DHCP or other mechanisms) and managing the IP bearer context for each data session. The P-GW enforces policy and charging rules received from the Policy and Charging Rules Function (PCRF), applying gating, filtering, and quality-of-service (QoS) marking to packets. It also performs deep packet inspection (DPI) for service-aware charging and policy enforcement.

Architecturally, the P-GW interfaces with several key network elements. On the mobile network side, it connects to the Serving Gateway (S-GW) via the S5/S8 interface (GTP-based or PMIP-based) for user plane traffic and control signaling. The S5 interface is used when the S-GW and P-GW are within the same PLMN, while S8 is used for roaming scenarios between PLMNs. On the external network side, the P-GW connects to PDNs via the SGi interface, which is a standard IP interface. For control plane functions, the P-GW communicates with the PCRF over the Gx interface to receive dynamic policy and charging control (PCC) rules. It also interfaces with Online Charging Systems (OCS) via the Gy interface and Offline Charging Systems (OFCS) via the Gz interface.

A critical role of the P-GW is as an anchor for mobility. When a UE moves between different eNodeBs or even between 3GPP and non-3GPP access networks (like Wi-Fi), the P-GW remains the stable IP point of attachment. This ensures session continuity as the UE's IP address is preserved. The P-GW also supports advanced features like Traffic Detection Function (TDF) for application detection and reporting, and Bearer Binding and Event Reporting Function (BBERF) for non-3GPP accesses. In later 3GPP releases, with the introduction of 5G Core (5GC), many P-GW functions were integrated into the new User Plane Function (UPF), but the P-GW remains central to 4G EPS deployments and is a key element in interworking between 4G and 5G networks.

Purpose & Motivation

The P-GW was created as part of the System Architecture Evolution (SAE) in 3GPP Release 8 to address the limitations of previous 3G packet core architectures, specifically the Gateway GPRS Support Node (GGSN). The GGSN in 2G/3G networks handled similar gateway functions but was part of a less flexible, more monolithic architecture. The EPC, with the P-GW as a distinct entity, introduced a flatter, all-IP architecture designed for higher data throughput, lower latency, and more efficient packet routing. This was essential to support the burgeoning demand for mobile broadband services driven by smartphones and new applications.

The P-GW solves several key problems. It centralizes the policy enforcement and charging functions, allowing operators to implement sophisticated service plans and monetization strategies based on user, application, or network conditions. By acting as the single IP anchor point, it simplifies mobility management and enables seamless handovers between different radio access technologies. Furthermore, its design supports deep packet inspection and service-aware capabilities, which are crucial for implementing parental controls, enterprise VPNs, and optimized traffic management. The separation of the S-GW and P-GW also allowed for more flexible network deployments, where the S-GW could be distributed for latency optimization while the P-GW could be centralized for policy consistency.

Key Features

• IP address allocation and management for UEs (IPv4, IPv6, dual-stack)
• Policy and Charging Enforcement Function (PCEF) for applying QoS, gating, and bandwidth limits
• Anchor point for user plane mobility between 3GPP and non-3GPP accesses
• Packet filtering, inspection (DPI), and routing between SGi and S5/S8 interfaces
• Interaction with PCRF (Gx), OCS (Gy), and OFCS (Gz) for dynamic policy and charging
• Support for multiple PDN connections per UE and dedicated bearers

Evolution Across Releases

Defining Specifications