Hybrid ICN System Maps Content Names to IP Addresses
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrating Information-Centric Networking (ICN) into existing Internet Protocol (IP) networks poses challenges due to the need for new packet formats and protocols, which complicates network deployment and requires significant modifications to IP infrastructure.
Innovation Solution
The hybrid ICN (hICN) communication system maps content names into IP addresses, allowing ICN features to be preserved while using standard IP packet formats, enabling transparent integration into IP networks without modifying Layer 7 applications or re-designing router architecture, and allowing selective use of ICN or IP semantics for routing and forwarding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If overlay approaches (CCN, NDN) are used to deploy ICN over IP, then ICN functionality can be provided, but new packet formats and protocols must be defined and standardized, increasing device complexity and deployment difficulty
Solution Approach 1:
The patent uses IP addresses as an intermediary to bridge ICN content names and IP network routing. Instead of requiring new packet formats, the system maps content names to IP addresses through a naming service, allowing ICN functionality to operate over standard IP infrastructure without modifying packet structures or router architecture.
Solution Approach 2:
The patent enables existing IP network infrastructure to serve dual purposes: traditional IP addressing and routing, plus ICN content name resolution and forwarding. By mapping content names to IP addresses, the same IP packets and routers can handle both conventional Internet traffic and ICN content delivery without requiring separate specialized infrastructure.
2Adaptability or versatility
If overlay approaches are used for ICN deployment, then ICN features can be implemented, but significant modifications to IP infrastructure are required, worsening ease of operation
Solution Approach 1:
The patent introduces a naming service as an intermediary layer that translates ICN content names into IP addresses without requiring modifications to the underlying IP infrastructure. This intermediary handles the complexity of name-to-address mapping, leaving existing IP networks to operate unchanged, thereby maintaining ease of operation while enabling ICN deployment.
Solution Approach 2:
The patent implements ICN functionality partially by mapping only the necessary content names to IP addresses through a naming service, rather than requiring complete redesign of IP infrastructure. This partial approach allows ICN features to be deployed selectively without the excessive action of modifying entire network architectures, thus preserving operational simplicity.
3Device complexity
If content names are mapped into IP addresses, then standard IP packet formats can be used, but ICN semantics must be preserved through the mapping process
Solution Approach 1:
The patent creates a mapping copy of content names in the IP address space through a naming service. Instead of directly modifying IP packets to carry ICN semantics, the system creates an equivalent representation by mapping content names to IP addresses, allowing standard IP packets to convey ICN information indirectly without losing essential routing and forwarding semantics.
Solution Approach 2:
The naming service acts as an intermediary that preserves ICN semantics during the translation from content names to IP addresses. It maintains the semantic meaning of content names by providing consistent mappings, ensuring that ICN routing and forwarding logic remains intact even though standard IP packet formats are used in the underlying network.
Data Source
Figure 1A
Figure 1B
Figure 2
AI summary
A method is provided in one example embodiment and may include receiving an Internet Protocol (IP) packet at a node; identifying a content semantic for the IP packet; determining whether the IP packet is an IP interest packet or an IP data packet; determining whether content identified in the IP packet is stored at the node based on a determination that the IP packet is an IP interest packet; forwarding the IP packet toward at least one other node based on a determination that the content is not stored at the node; and transmitting an IP data packet containing the content based on a determination that the content is stored at the node.