ICN Routing Using Named-Data Metrics Instead of Node Addresses
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing routing protocols for Information Centric Networks (ICN) fail to operate effectively in native ICN environments, as they rely on node addresses rather than named-data, leading to inefficient network performance and poor routing.
Innovation Solution
Modifications to the IS-IS and OSPF protocols to enable them to operate in native ICN networks by using Type-Length-Value (TLV) formats for ICN name data and implementing multiple-source shortest path techniques, allowing routing based on content names rather than node addresses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing routing protocols (IS-IS, OSPF) are used in ICN environments, then routing expertise and infrastructure can be leveraged, but the protocols fail to operate effectively because they rely on node addresses rather than named-data
Solution Approach 1:
The patent modifies the routing protocols by changing the fundamental parameter they route on - from node addresses to named-data. This is achieved by altering the protocol's data structures (e.g., changing destination identifiers from IP addresses to data names) and routing decisions from address-based to content-based, allowing the same protocol framework to function effectively in ICN environments
2Ease of manufacture
If address-based routing is used, then existing network infrastructure can be utilized, but network performance becomes inefficient and routing is poor in ICN environments
Solution Approach 1:
The patent introduces dynamic adaptation to ICN requirements by enabling the routing protocol to dynamically switch from address-based to named-data routing. This is accomplished through dynamic data structure updates (e.g., FIB tables storing named-data entries instead of addresses) and dynamic routing decision-making based on content names, allowing the system to adapt its behavior to the specific needs of ICN while maintaining the underlying protocol framework
Data Source
AI summary
System and techniques for Information Centric Network (ICN) routing are described herein. An ICN node receives a routing packet—which is a link layer packet corresponding to a link of the ICN node—that includes an ICN name and a routing metric. An entry for the link and name is created or updated and then sorted into a local routing data store based on the routing metric. Then, an interest packet for the ICN name is routed via the link based on the entry having a highest rank in the local routing data store.