ICN over LISP Name-to-Locator Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing LISP solutions require establishing communication by requesting a location for an identifier of a particular endpoint, limiting the ability of ICN consumer endpoints to request content by name within a LISP network.
Innovation Solution
The method involves an ingress tunnel router receiving an ICN interest packet, resolving a target egress tunnel router based on the packet's name, encapsulating the packet in a LISP packet, and sending it to the target ETR, allowing ICN consumer endpoints to request content by name even when connected through a LISP network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Force
If LISP separates identifier from locator for routing scalability, then routing scalability is improved, but the ability to request content by name is lost
Solution Approach 1:
The patent introduces an intermediary mapping mechanism that translates ICN name-based requests into LISP locator-based routing. The system uses a name-to-locator mapping table and iterative resolution process with ETRs as intermediaries, allowing ICN endpoints to request content by name while LISP handles the locator translation in the background, thus preserving both routing scalability and name-based content request capability
Solution Approach 2:
The patent segments the communication process into distinct layers: the ICN layer handles name-based content requests, while the LISP layer handles locator-based routing. This segmentation allows each layer to operate independently with its own optimization goals, enabling ICN endpoints to use names for content identification while LISP routers use locators for efficient routing, resolving the contradiction between routing scalability and content request capability
2Speed
If LISP uses EID-to-RLOC mapping for routing, then routing efficiency is improved, but direct name-based content addressing is limited
Solution Approach 1:
The patent creates a mapping copy mechanism where name-to-locator mappings are stored in local tables at ICN endpoints and intermediate routers. Instead of performing complex name resolution for every packet, the system uses pre-established mapping copies that enable direct name-based addressing while maintaining efficient locator-based routing in the background, thus improving both routing efficiency and ease of content addressing
Solution Approach 2:
The patent performs preliminary name-to-locator mapping resolution before actual data transmission. The system establishes mapping relationships in advance through iterative ETR resolution and stores them in caching tables, so that subsequent content requests can use these pre-computed mappings for efficient direct addressing, eliminating the need for real-time name resolution and improving both routing efficiency and operational simplicity
Data Source
AI summary
A computer-implemented method of enabling information-centric networking (ICN) over a locator/identifier separation protocol (LISP) comprises receiving, by one or more processors of an ingress tunnel router (ITR), from an endpoint, an ICN interest packet that identifies an interest by name; resolving, by the one or more processors of the ITR, a target egress tunnel router (ETR) in accordance with the name; encapsulating, by the one or more processors of the ITR, the ICN interest packet in a LISP packet; and sending, by the one or more processors of the ITR, the LISP packet to the target ETR.