Identifier Locator Separation for Scalable Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The traditional Internet routing and addressing architectures, which rely solely on IP address space, limit scalability and complicate mobility management, as they do not distinguish between identifiers and locators, leading to inefficient routing table expansion and management.
Innovation Solution
A system for data communications that separates identifiers (IDs) and locators (LLs and GLs) within a network, using access routers (ARs) and area border routers (ABRs) to establish and manage communications links, allowing for efficient data transmission across areas without altering the terminal or routing protocol stack, by querying local and global mapping information bases to determine transmission routes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional IP address space-based routing architecture is used, then data transmission can be achieved, but scalability is limited and routing tables become overly complex
Solution Approach 1:
The patent segments the addressing architecture into two independent parts: Identifier (ID) and Locator (LL). The ID identifies the terminal device, while the LL indicates the routing location. This segmentation allows routing tables to store only locator information rather than complete addressing information, significantly reducing routing table complexity and enabling better scalability.
Solution Approach 2:
The patent introduces a mapping relationship between IDs and Locators as an intermediary mechanism. Instead of directly using IP addresses for both identification and routing, the system uses IDs for identification and LLs for routing, with a mapping database connecting the two. This intermediary approach decouples the identification and routing functions, reducing routing table complexity.
2Ease of operation
If ID and locator are not separated, then routing can be simplified, but mobility management becomes complicated and scalability is limited
Solution Approach 1:
The patent segments the addressing function into ID (identification) and LL (location) components. The ID remains stable for mobility management, while the LL changes with location. This segmentation simplifies mobility management by allowing terminals to move between networks without changing their ID, while routing remains simple through direct LL-based forwarding.
Solution Approach 2:
The patent introduces dynamic mapping between IDs and Locators. The mapping relationship can change dynamically as terminals move between different networks, allowing the system to adapt to mobility without complicating the routing mechanism. The mapping database is updated dynamically to reflect current terminal locations.
3Adaptability or versatility
If multiple existing solutions separate ID and locator, then scalability improves, but implementation complexity varies significantly and none are accepted as practical
Solution Approach 1:
The patent designs a universal mapping mechanism that can be implemented across different network types and scenarios. The mapping database and routing protocol work universally whether terminals are moving within a single network or across multiple networks, making the solution adaptable to various implementation contexts and more feasible for practical deployment.
Solution Approach 2:
The patent changes the key parameter from using IP addresses for both identification and routing to using separate ID and LL parameters. This parameter change enables scalability while maintaining implementation feasibility by building upon existing IP-based infrastructure rather than requiring complete replacement.
Data Source
AI summary
The embodiments of the present invention disclose a system for data communications, a router, and a method for data transmission and mobility management. The method for data transmission includes: receiving, by a first AR, data; identifying the transmission route based on the results of querying the local mapping information base; and transmitting data, where the local mapping information base stores the mappings between IDs and LLs. The embodiments of the present invention completely separate the ID, LL, and GL of the terminal, and thus solve the problems with the routing table expansion and scalability faced by the Internet. In this way, the terminal data can be transmitted without changing the terminal or the routing protocol stack; in addition, the hierarchical mapping helps reduces the amount of locally and globally stored information, and thus accelerating the query.