Proxy Binding Update

Description

The Proxy Binding Update (PBU) is a control plane message defined within the Proxy Mobile IPv6 (PMIPv6) protocol, specified in IETF RFC 5213 and adopted by 3GPP for network-based mobility management. It is a fundamental message sent from the Mobile Access Gateway (MAG), which is the network entity serving the mobile node (MN), to the Local Mobility Anchor (LMA), which is the home agent for the MN's mobility session. The PBU message is used to register the MN's current point of attachment and request the establishment or update of a binding cache entry at the LMA.

Architecturally, when a mobile node attaches to a PMIPv6 domain (e.g., connects to an LTE or 5G network), the MAG detects the attachment. The MAG, acting as a proxy for the MN, formulates and sends a PBU message to the LMA. This message contains critical information such as the MN's identifier (e.g., its Network Access Identifier or NAI), the home network prefix(es) assigned to the MN, the MAG's own IP address (Proxy-CoA), and requested lifetime for the binding. The MAG derives this information from local policy and authentication exchanges with the AAA infrastructure.

Upon receiving a valid PBU, the LMA processes it to create or update a binding cache entry. This entry maps the MN's home network prefix to the Proxy-CoA (the MAG's address). The LMA then responds with a Proxy Binding Acknowledgement (PBA) message. If successful, the LMA also sets up a bidirectional tunnel with the MAG. All packets destined for the MN's home address are routed to the LMA, which encapsulates them and forwards them through the tunnel to the MAG. The MAG decapsulates the packets and delivers them to the MN. Similarly, upstream packets from the MN are sent to the MAG, which encapsulates them and sends them to the LMA for routing to the external network.

The PBU message is triggered not only at initial attachment but also during handovers between MAGs. When an MN moves to a new MAG, the new MAG sends a PBU, causing the LMA to update the binding to the new Proxy-CoA. The old binding is eventually cleaned up. This process enables seamless IP mobility without requiring the MN itself to participate in any mobility signaling—hence the term 'network-based' mobility. PBU messages are secured using IPsec security associations established between the MAG and LMA.

Purpose & Motivation

The PBU message and the PMIPv6 protocol were created to provide a scalable, network-based mobility solution, addressing the limitations of host-based mobility protocols like Mobile IPv6 (MIPv6). In MIPv6, the mobile node itself is responsible for sending binding updates to its home agent, which can be inefficient for resource-constrained devices (like IoT sensors) and adds complexity to device software. PMIPv6, and by extension the PBU, shifts this responsibility to the network infrastructure.

It solves the problem of providing seamless IP mobility for a large number of devices without requiring modifications to their IP stacks. This is particularly crucial for 3GPP networks serving diverse devices, from smartphones to simple M2M modules. The network (the MAG) detects movement and manages the mobility signaling transparently. This enables operators to manage mobility as a network service.

The historical motivation stems from the need for efficient mobility management in evolved packet core (EPC) networks for LTE and later in 5G Core. In 3GPP architectures, the MAG function is often co-located with the access node (e.g., the Serving Gateway in EPC), and the LMA is co-located with the Packet Data Network Gateway (PGW) or its equivalent. The PBU/PBA exchange is the core mechanism that allows the PGW to track the UE's serving gateway, enabling session continuity during handovers. It supports various access technologies (3GPP and non-3GPP) under a common IP anchor point, simplifying core network design and enabling fixed-mobile convergence.

Key Features

• Initiated by the network (MAG) on behalf of the mobile node
• Establishes or updates a binding between home prefix and Proxy-CoA at the LMA
• Triggers the setup of a bidirectional tunnel between LMA and MAG
• Supports handover by allowing binding updates from new MAGs
• Carries mobility session parameters like lifetime and home network prefix
• Secured using IPsec between MAG and LMA

Evolution Across Releases

Defining Specifications