PMIP Protocol Stack Selection for IPv4 Network Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The PMIPv6 protocol faces backward incompatibility issues between the RFC and draft versions, particularly when used over an IPv4 transport network, leading to communication problems between nodes supporting different protocol stacks, and there is a need for a mechanism to determine the correct protocol stack for communication.
Innovation Solution
A mechanism is introduced where a MAG or LMA node sends communication messages in both PMIP draft and RFC formats initially to determine which protocol stack a peer node supports, allowing the selection of the appropriate protocol stack for subsequent communications, enabling dual protocol stack support in new nodes during migration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If nodes support both PMIP draft and RFC protocol stacks during migration, then compatibility with existing networks is maintained and seamless communication is enabled, but device complexity increases due to dual protocol stack support
Solution Approach 1:
The system dynamically selects which PMIP protocol stack (draft or RFC) to use based on the peer node's capabilities. The MAG node can switch between draft and RFC protocol stacks depending on whether the peer node is an old or new node, making the protocol selection adaptive rather than static. This resolves the contradiction by enabling protocol flexibility without permanently maintaining both stacks active simultaneously.
Solution Approach 2:
The system uses feedback from protocol version detection to determine which PMIP protocol stack to employ. When a MAG node detects that a peer node supports RFC 5844 (new node), it switches to RFC protocol; when detecting draft version support (old node), it uses draft protocol. This feedback mechanism enables automatic protocol selection, maintaining compatibility while managing complexity through intelligent decision-making rather than brute-force dual-stack support.
2Reliability
If immediate upgrade to RFC protocol stack is required, then communication standardization is improved, but system downtime increases and compatibility with existing networks is lost
Solution Approach 1:
The system performs preliminary detection of the peer node's PMIP protocol capabilities before establishing communication. By detecting whether the peer node supports RFC 5844 or draft version in advance, the MAG node can proactively select the appropriate protocol stack, preventing communication failures and avoiding the need for immediate system-wide upgrades. This preliminary action enables gradual migration without forcing immediate standardization.
Solution Approach 2:
The system changes the protocol version parameter dynamically based on peer node characteristics. Instead of fixing the protocol version at deployment, the MAG node adjusts the PMIP protocol version parameter (draft or RFC) according to the peer node's capabilities. This parameter flexibility allows the network to maintain communication with both old and new nodes, enabling gradual migration without system downtime.
3Ease of operation
If protocol version detection mechanism is implemented, then correct protocol stack selection is enabled, but communication overhead increases due to additional detection messages
Solution Approach 1:
The system merges the protocol version detection function with the existing PMIP protocol exchange. Instead of adding separate detection messages, the protocol capability detection is integrated into the normal PMIP signaling traffic. The MAG node determines peer node type (old or new) through existing protocol interactions, combining multiple functions into a single communication flow. This eliminates the need for additional dedicated detection messages while still enabling accurate protocol stack selection.
Data Source
AI summary
Example embodiments presented herein are directed towards determining a Proxy Mobile Internet Protocol version 6 (PMIPv6) control plane used by a network node peer in an Internet Protocol version 4 (IPv4) transport network. The example embodiments provide a mechanism in PMIP protocol stack, to allow a Mobility Access Gateway/Local Mobility Anchor (MAG/LMA) node such as SGW (which may be supporting both PMIP draft and PMIP RFC) to decide which PMIP protocol stack shall be used to communicate to the peer node, i.e. LMA/MAG.