Packet Data Network

Description

In 3GPP architecture, a Packet Data Network (PDN) is an external network that provides packet-switched data services to a User Equipment (UE). It is essentially an IP network that resides outside the 3GPP operator's domain. Common examples include the public Internet, an Internet Multimedia Subsystem (IMS) network for VoIP and VoLTE, or a private enterprise intranet. The primary function of the 3GPP core network—whether GPRS, EPS (4G), or 5GS (5G)—is to provide secure, policy-controlled connectivity between the UE and one or more PDNs.

The connection to a PDN is established through a Packet Data Protocol (PDP) Context in 3G/4G or a Protocol Data Unit (PDU) Session in 5G. This logical connection is anchored at a gateway node: the Gateway GPRS Support Node (GGSN) in 3G, the Packet Data Network Gateway (PDN-GW or PGW) in 4G EPS, and the User Plane Function (UPF) in 5G. This gateway acts as the point of entry and exit for all user plane traffic between the 3GPP network and the external PDN. It performs critical functions like IP address allocation to the UE (often from the PDN's address space), packet routing and forwarding, policy enforcement, charging, and traffic screening.

Each PDN is identified by an Access Point Name (APN), a textual label that the UE includes in its connection request. The APN is used by the network to determine the correct gateway and the specific external network to connect to. A single UE can have multiple simultaneous connections to different PDNs (e.g., one for internet, one for IMS), each with its own IP address and set of QoS characteristics. The PDN concept abstracts the details of the external network, allowing the 3GPP core to provide a consistent set of mobility, security, and policy functions regardless of whether the destination is the public internet or a specialized service network.

The role of the PDN has evolved with network generations. In 5G, the concept is generalized, but the principle remains. The 5G core network provides 'PDU Connectivity Services' to 'Data Networks' (DNs), which are the 5G equivalent of PDNs. The Service Continuity between EPS and 5GS relies heavily on maintaining PDN connectivity/PDU Sessions during inter-system handovers. The security boundary between the operator's trusted core and the external PDN is rigorously enforced at the gateway, using firewalling, Network Address Translation (NAT), and tunneling protocols like GTP or IPsec.

Purpose & Motivation

The concept of a Packet Data Network (PDN) was introduced to formalize and standardize how mobile networks provide access to external IP-based data services. In early cellular networks, data services were circuit-switched and limited. The shift to packet-switched data required a model where the mobile network acted as an access network to the broader internet and other IP networks. The PDN concept created a clear architectural separation between the operator's mobility management domain and the vast array of external service networks.

It solved the problem of how to route IP packets to and from a mobile subscriber whose point of attachment to the radio network changes constantly. The PDN Gateway (like GGSN/PGW) serves as a fixed anchor point in the IP topology, hiding the subscriber's mobility from the external PDN. This allows the UE to maintain a stable IP address and ongoing sessions even while moving across base stations. Without this anchor-and-tunnel model to a defined PDN, mobile IP data services would be impractical.

Historically, the PDN model enabled the commercial success of mobile internet. It provided the framework for billing (different rates for different PDNs via APNs), service differentiation (prioritizing IMS traffic over best-effort internet), and secure enterprise access (via private APNs). The evolution from 3G to 5G has seen the PDN concept become more flexible (supporting non-IP traffic in 5G) and integrated with network slicing, where a slice may provide dedicated connectivity to a specific type of PDN (e.g., an industrial IoT network). It remains a foundational abstraction for all mobile data services.

Key Features

• Represents any external IP network (Internet, IMS, enterprise) accessible via the mobile core
• Identified by an Access Point Name (APN) used for routing and policy
• Connectivity is anchored at a gateway node (GGSN, PGW, UPF)
• Supports simultaneous UE connections to multiple PDNs
• Enables IP address allocation from the PDN's address space
• Forms the security and policy enforcement boundary between operator and external networks

Evolution Across Releases

Defining Specifications