LISP EID-NOTIFY for Network Device Mobility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network addressing methods, such as using a single IP address for identification and topology, lead to routing conflicts and inefficiencies, particularly in managing device mobility across different locations without the need for rerouting.
Innovation Solution
The proposed solution involves a modification to the Location/Identifier Separation Protocol (LISP) where first-hop routers perform EID detection independently of LISP encapsulation and decapsulation, and site gateway routers handle LISP encapsulation and decapsulation, using EID-NOTIFY messages to inform the mapping system of endpoint identifier changes, allowing for dynamic endpoint mobility without requiring routers to perform both functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a single IP address is used for both device identification and topological location, then routing efficiency is improved, but device mobility management deteriorates
Solution Approach 1:
The patent segments the traditional single IP address function into two separate components: EID (Endpoint Identifier) for device identification and RLOC (Routing Locator) for topological location. This segmentation allows independent optimization of identification and routing functions, enabling devices to maintain their EID while changing RLOCs during mobility events without disrupting routing efficiency.
Solution Approach 2:
The patent introduces a mapping system as an intermediary between EIDs and RLOCs. This mapping system stores and manages the correspondence between endpoint identifiers and routing locators, allowing routers to efficiently forward packets to current device locations while devices maintain stable identification. The mapping system resolves the conflict by decoupling identification from location through this mediating layer.
2Productivity
If IP addresses are assigned topologically for efficient routing, then routing efficiency is improved, but addressing management complexity increases
Solution Approach 1:
The mapping system acts as an intermediary that manages the complexity of topological addressing. Routers only need to know RLOCs for efficient routing, while the mapping system handles the complex task of tracking EID-RLOC correspondences. This intermediary absorbs the management complexity, allowing routing to remain simple and efficient while supporting mobile devices.
Solution Approach 2:
The patent extracts the addressing management complexity from the routing function and places it in the mapping system. Routers are relieved of the burden of managing dynamic address assignments and can focus solely on efficient packet forwarding based on RLOCs. The complex task of tracking device locations and updating mappings is extracted and handled separately by the mapping system.
3Adaptability or versatility
If routers perform both EID detection and LISP encapsulation/decapsulation, then functionality is improved, but device complexity increases
Solution Approach 1:
The patent segments router functionality into two distinct roles: first-hop routers that perform EID detection, and site gateway routers that perform LISP encapsulation and decapsulation. This segmentation allows each router type to be optimized for its specific function, reducing configuration complexity while maintaining comprehensive functionality across the network.
Solution Approach 2:
While the patent segments functions, it maintains versatility by allowing different router types to coexist in the same network. First-hop routers and site gateway routers work together as a unified system, with each performing its specialized function. This multi-functionality at the system level achieves comprehensive capability without requiring every individual router to perform all functions.
Data Source
AI summary
According to one example embodiment, an EID-NOTIFY packet is defined for use with the Location/Identifier Separation Protocol (LISP). A first-hop network element may send EID-NOTIFY responsive to decoding a data packet from a previously undetected host on its subnetwork. A site network element may receive EID-NOTIFY, and send a MAP-REGISTER message to a mapping system. EID-NOTIFY may have substantially the same format as MAP-NOTIFY. This may enable the site network element to be removed more than one hop from the subnetwork.