Network Address Translation

Description

Network Address Translation (NAT) in 3GPP networks is a function typically implemented in the Packet Data Network Gateway (PGW) in 4G or the User Plane Function (UPF) in 5G. It operates at the IP layer, modifying the source and/or destination IP addresses (and often port numbers) in packet headers as they traverse between the mobile user equipment (UE) and external packet data networks (PDNs) like the internet. The core mechanism involves maintaining a NAT binding table that maps each UE's private IP address (assigned from the mobile operator's pool, e.g., 10.0.0.0/8) and source port to a unique public IP address and port on the external interface. For outgoing packets from the UE, the NAT function replaces the private source IP and port with the mapped public ones; for incoming packets destined for the UE, it performs the reverse translation based on the destination port and IP in the packet.

The architecture integrates NAT within the data path of the user plane. In EPS (4G), the PGW acts as the anchor point and performs NAT for PDN connections that require it, often configured as part of the Packet Data Protocol (PDP) context or PDN connection establishment. In 5GC, the UPF performs the equivalent N6 point-of-presence function. Key components include the NAT mapping table (state), timers to manage the lifetime of inactive mappings, and algorithms for port allocation (e.g., Port Address Translation - PAT). Advanced forms like Carrier-Grade NAT (CGN) or Large Scale NAT (LSN) are employed to map thousands of UEs onto a single or a small pool of public IPv4 addresses, using port ranges to distinguish flows.

NAT's role is multifaceted: it conserves the globally scarce IPv4 address space by allowing many UEs to share few public addresses; it adds a layer of privacy and basic security by hiding internal network topology; and it simplifies network management for operators. However, it also introduces complexities, breaking the end-to-end principle of the internet. It can interfere with protocols that embed IP addresses in payloads (e.g., SIP, FTP) unless accompanied by Application Layer Gateways (ALGs) or techniques like NAT Traversal (NAT-T). Within 3GPP, NAT behavior and configuration are specified to ensure interoperability and predictable service delivery across different vendor equipment and network deployments.

Purpose & Motivation

NAT was adopted in 3GPP networks primarily to mitigate the exhaustion of public IPv4 addresses, a critical issue that emerged with the explosive growth of mobile internet devices. Without NAT, each UE requiring internet access would need a unique public IPv4 address, a requirement unsustainable given the limited address space. NAT solves this by allowing operators to use large private address spaces internally (RFC 1918) and map them to a much smaller pool of public addresses. This enabled the cost-effective scaling of mobile broadband services from 3G (R99) onwards.

Historically, early mobile data services had limited scale and sometimes used public addressing. As services expanded, NAT became a necessary network function. Its integration into 3GPP standards ensured a consistent, vendor-interoperable approach to address conservation. Furthermore, NAT provided incidental benefits like a basic firewall effect, as unsolicited inbound traffic without an existing mapping is typically dropped, enhancing network security. The technology addressed the limitations of simply deploying IPv6 (which has abundant addresses) by providing an immediate, backward-compatible solution while the transition to IPv6 progressed slowly. NAT's purpose evolved to also support network architectures like fixed-mobile convergence and multi-homing, where traffic from different access types is aggregated through a common gateway performing NAT.

Key Features

• Translates private IPv4 addresses to public IPv4 addresses (and vice versa)
• Implements Port Address Translation (PAT) to multiplex many users on a single IP
• Maintains stateful mapping tables with configurable timeout policies
• Integrated into core network gateways (GGSN/PGW/UPF) for mobile traffic
• Can be deployed as Carrier-Grade NAT (CGN) for large-scale subscriber aggregation
• Supports various NAT flavors like full-cone, restricted-cone, port-restricted, and symmetric

Evolution Across Releases

Defining Specifications