Proxy Mobile IPv6 Multihoming via Binding Cache Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Proxy Mobile IPv6 (PMIPv6) does not currently support multi-homing mechanisms, leading to inefficient handling of flow mobility as each active interface is managed separately, making it difficult to redirect incoming packets without changing the source address of a mobile node (MN), especially during handovers between different wireless technologies.
Innovation Solution
The Local Mobility Anchor (LMA) maintains binding cache entries (BCEs) for multiple active interfaces of a MN, using home and secondary interface flags to direct incoming traffic over one of the active interfaces using the same home address (HoA), and communicates these flags and home network prefixes (HNPs) to corresponding Mobile Access Gateways (MAGs) via Proxy Binding Update (PBU) and Proxy Binding Acknowledgement (PBA) messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If PMIPv6 manages each active interface separately, then the protocol implementation is simple, but flow mobility cannot be efficiently handled and packet redirection is difficult
Solution Approach 1:
The patent segments the binding cache into multiple interface-specific binding cache entries (BCEs), each associated with a specific interface of the mobile node. This allows separate management of each interface while maintaining overall flow mobility capability, resolving the contradiction by enabling complex functionality through structured organization.
Solution Approach 2:
The patent introduces a flow mobility anchor (FMA) as an intermediary component that coordinates between multiple access routers and the mobile node. The FMA maintains the segmented binding cache and manages flow redirection, enabling efficient flow mobility without requiring complex multi-homing mechanisms at every network component.
2Reliability
If the MN changes source address during handover, then interface switching is straightforward, but session continuity is disrupted
Solution Approach 1:
The patent performs preliminary actions by pre-establishing binding cache entries for multiple interfaces before handover occurs. The source address translation mappings are prepared in advance at the FMA, allowing seamless session continuity during handover without requiring complex real-time address changes at the mobile node.
Solution Approach 2:
The patent creates a copy of the binding state at the flow mobility anchor, maintaining a mapping between the mobile node's home address and current care-of-address. This copy allows the network to redirect packets to the new interface without the mobile node needing to change its source address or perform complex handover operations.
3Productivity
If multiple BCEs are maintained for multiple interfaces, then flow mobility is improved, but binding cache management complexity increases
Solution Approach 1:
The patent makes the binding cache structure universal by designing it to handle both single-interface and multi-interface scenarios through a standardized segmented format. Each binding cache entry follows the same structure regardless of which interface it represents, allowing efficient packet forwarding while simplifying management through consistency.
Solution Approach 2:
The patent implements feedback mechanisms where access routers report interface status and mobile node movements to the flow mobility anchor. This feedback allows the FMA to dynamically update the segmented binding cache entries, maintaining high packet forwarding efficiency while automatically managing the complexity of multiple binding cache entries without manual intervention.
Data Source
AI summary
An apparatus comprising: a local mobility anchor (LMA) configured to maintain a plurality of binding cache entries (BCEs) for two or more active interfaces between a mobile node (MN) and a plurality of mobile access gateways (MAGs) comprising a first MAG and a second MAG, wherein the BCEs comprise a first BCE that corresponds to a home interface between the MN and the first MAG and that comprises a first list of home network prefixes (HNPs), and wherein the BCEs further comprise a second BCE that is linked to the first BCE, that corresponds to a secondary interface between the MN and the second MAG, and that comprises a second list of HNPs.