PMIP

Proxy Mobile Internet Protocol version 6

Mobility →
Introduced in Rel-8

PMIP is a network-based mobility protocol where the network handles all mobility signaling on behalf of a mobile node, enabling IP mobility without requiring the device's direct involvement.

Category
Mobility
Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Specifications
8 specs
PMIP Description Purpose Related Classification Detected Changes Specifications

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.

Classification

Part ofGTP
Specific typesDSMIPMAGPBURRP
Related approachesMAGLMA

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (14 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-8, normative work from Rel-15.

Rel-15 2 changes

In Release 15, the PMIP function was enhanced to support IMS restoration procedures, specifically introducing the use of the PMIP Update Notification (UPN/UPA) procedure to inform UEs of a P-CSCF failure and provide new P-CSCF addresses. This mechanism is defined for the PMIP-based S5, S2a, and S2b interfaces, enabling the PGW to trigger a bearer modification to update the Protocol Configuration Options (PCO) when a serving P-CSCF becomes unavailable.

Rel-16 4 changes

In Release 16, the primary enhancement for PMIP was the introduction of a standardized procedure for IMS restoration following a P-CSCF failure when using a PMIP-based S5, S2a, or S2b interface. This involves the PDN-GW initiating a PMIP Update Notification (UPN) message to inform the SGW, TWAN, or ePDG of the failure, triggering a bearer update to provide the UE with new P-CSCF addresses. The update also clarified the use of this LMA Initiated Update Notification procedure, as specified in RFC 7077, to restore service without requiring the UE to reactivate the PDN connection.

  • Inclusion of Version Identifier in PLMN assigned ID TS 23.401CR3561
  • Clarification on Version ID TS 23.401CR3598
  • Update to Rel-16 version (MCC) TS 24.161
  • Update to Rel-16 version (MCC) TS 29.276
Rel-17 2 changes

In Release 17, the PMIPv6 function was enhanced to support IMS restoration procedures specifically for P-CSCF failure scenarios over PMIP-based interfaces (S5, S2a, and S2b). This introduced the standardized use of the PMIP Update Notification (UPN/UPA) procedure, as defined in RFC 7077, to dynamically inform the UE about available P-CSCF addresses via the SGW, TWAN, or ePDG. The update enabled the PDN-GW to trigger a bearer modification without QoS update to deliver new P-CSCF information to the UE upon a failure, improving service continuity.

Rel-18 4 changes

In Release 18, the PMIP function was enhanced to support standardized restoration procedures following a P-CSCF failure. Specifically, it defined the use of the PMIPv6 Update Notification (UPN) procedure over the S5, S2a, and S2b interfaces to notify gateways and, subsequently, UEs of the failure and to provide new P-CSCF addresses. This allows for automatic service recovery without requiring the UE to re-establish the PDN connection.

Rel-19 2 changes

In Release 19, the PMIP function was enhanced to support IMS restoration procedures specifically for P-CSCF failure scenarios over PMIP-based interfaces (S5, S2a, and S2b). This introduced the standardized use of the PMIPv6 Update Notification (UPN) procedure, as defined in IETF RFC 7077, to notify the SGW, TWAN, or ePDG of P-CSCF failure and to deliver new P-CSCF addresses to the UE. These mechanisms enable the PGW to trigger a network-initiated bearer modification to update the UE without requiring a full PDN connection reactivation.

Explore further

Broader topics and technologies where PMIP plays a role.

Defining Specifications

3GPP specifications that define or reference PMIP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.380 vj10 IMS Restoration Procedures Rel-19
TS 23.401 vj50 Evolved Packet System (EPS) Stage 2 Description Rel-19
TS 24.161 vj00 Network-Based IP Flow Mobility (NBIFOM) Rel-19
TS 29.276 vj00 EPS S101/S121/S103 Interfaces Stage 3 Rel-19
TS 29.826 vd10 P-CSCF Restoration Enhancements for WLAN Rel-13
TS 32.251 vj00 PS Domain Charging Management Rel-19
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19
TS 33.108 vj00 LI Handover Interface Specification Rel-19