Proxy Mobile Internet Protocol version 6

Description

Proxy Mobile IPv6 (PMIPv6) is a network-based mobility management protocol that provides IP mobility support for a mobile node without requiring the node to participate in any IP mobility-related signaling. The protocol is defined by the IETF in RFC 5213 and subsequent documents, and it has been adopted and profiled by 3GPP for use within the Evolved Packet Core (EPC) and later the 5G Core (5GC). In a PMIPv6 domain, the network entities are responsible for managing the mobility of a mobile node. The two key functional entities are the Mobile Access Gateway (MAG) and the Local Mobility Anchor (LMA). The MAG is a function typically co-located with the access router (e.g., the Serving Gateway (SGW) in EPC or the User Plane Function (UPF) in 5GC). It detects the mobile node's attachment to the network, initiates the mobility signaling with the LMA on the node's behalf, and establishes the bidirectional tunnel. The LMA is the topological anchor point for the mobile node's home network prefix(es). It maintains a binding cache entry that associates the mobile node's identity (e.g., its Network Access Identifier) with the care-of address of the MAG currently serving it. All traffic destined for the mobile node is routed through the LMA, which tunnels it to the appropriate MAG. The MAG then de-tunnels the packets and delivers them to the mobile node. Conversely, traffic from the mobile node is tunneled by the MAG to the LMA. This tunnel-based forwarding ensures session continuity as the mobile node moves between MAGs, as the LMA remains the constant anchor point. The protocol uses Proxy Binding Update (PBU) and Proxy Binding Acknowledgment (PBA) messages between the MAG and LMA to establish, update, and delete the binding state. PMIPv6 supports both IPv4 and IPv6 transport and addressing, with mechanisms like dual-stack operation and IPv4 home address mobility. Within 3GPP architectures, PMIPv6 is specified as one of the control plane protocols for the S5/S8 interface between the SGW and the Packet Data Network Gateway (PGW) in EPC, providing an alternative to the GPRS Tunneling Protocol (GTP).

Purpose & Motivation

PMIPv6 was developed to address the limitations of host-based mobility protocols like Mobile IPv6 (MIPv6), which require a mobility stack and active participation from the mobile node itself. This requirement posed challenges for simple, battery-constrained devices and complicated network operator control. The primary purpose of PMIPv6 is to provide seamless IP mobility as a network service, transparently to the end-user device. By moving the mobility management functionality into the network infrastructure, PMIPv6 simplifies device design, conserves device battery life, and gives operators greater control over mobility policies and resource management. Its adoption in 3GPP, starting with Release 8 for the EPC, was driven by the need for a standardized, IP-based mobility protocol that could interoperate with non-3GPP access networks (like Wi-Fi) and support network-based traffic steering and policy enforcement. It provided an alternative to GTP, fostering competition and enabling deployments in networks where GTP was not desirable. PMIPv6 solved the problem of maintaining ongoing data sessions while a device moves between different points of attachment, which is fundamental for always-on connectivity in mobile broadband services.

Key Features

• Network-based mobility management, requiring no client software on the mobile node
• Uses Proxy Binding Update/Acknowledgment messages between MAG and LMA
• Establishes a bidirectional IP-in-IP tunnel between MAG and LMA for data forwarding
• Supports both IPv4 and IPv6 addressing and transport (dual-stack operation)
• Enables inter-technology handovers (e.g., between 3GPP and trusted non-3GPP access)
• Provides a stable home network prefix for the mobile node, ensuring session continuity

Evolution Across Releases

Defining Specifications