ICN Capability Detection via DNS Queries and TCP Options
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Information Centric Networking (ICN) systems face challenges in determining the ICN capability of nodes/servers, leading to discarded packets and bandwidth loss when ICN is not supported, resulting in increased latency and resource wastage.
Innovation Solution
The method involves using Domain Name Server (DNS) resource records and Transfer Control Protocol (TCP) options to determine ICN capability by sending specific queries and analyzing responses, allowing for the selection of suitable servers based on location and priority for efficient data transfer using ICN or IP protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the source device sends ICN packets to retrieve data, then the data retrieval flexibility is improved, but the packet will be discarded by non-ICN nodes causing bandwidth loss
Solution Approach 1:
The source device performs a preliminary DNS query to determine the ICN capability of the destination server before sending data packets. This advance checking prevents sending ICN packets to non-ICN nodes, thereby avoiding bandwidth loss while maintaining the ability to use ICN when appropriate
Solution Approach 2:
The system uses DNS response feedback indicating server ICN capability to adjust the data transmission approach. Based on the feedback about whether the destination server supports ICN, the source device dynamically selects between sending ICN packets or standard packets, preventing bandwidth waste from discarded packets
2Adaptability or versatility
If the source device computes ICN headers to generate ICN packets, then the data retrieval capability is improved, but the bandwidth, throughput, and power consumption increase
Solution Approach 1:
The source device performs a preliminary DNS query to determine the ICN capability of the destination server before computing ICN headers. This advance checking prevents unnecessary ICN header computation when the destination does not support ICN, thereby conserving bandwidth and throughput while maintaining full ICN capability when needed
3Adaptability or versatility
If the source device sends ICN packets to non-ICN servers, then the data retrieval attempt is made, but the packets are discarded causing increased latency
Solution Approach 1:
The source device performs a preliminary DNS query to determine the ICN capability of the destination server before sending data packets. This advance checking prevents sending ICN packets to non-ICN nodes, thereby avoiding the latency caused by packet discarding while maintaining the ability to use ICN when appropriate
Solution Approach 2:
The system takes preliminary action by checking server ICN capability through DNS queries before attempting to send ICN packets. This prevents the harmful action of sending incompatible packets that would be discarded, thereby avoiding the latency penalty of failed transmission attempts
Data Source
AI summary
Methods and systems for determining ICN capability of a node/server. The ICN capability is determined based on DNS resource records or TCP options. The DNS resource records are DNS queries that are sent to a DNS server, for determining the ICN capability of the server. The DNS query includes a content to indicate the intent to determine the ICN capability. If the server is having ICN capability, a DNS response is received from the DNS server, which includes the content that is identical to the content in the DNS query. A server is selected, amongst multiple servers, for transferring ICN packets, based on locations and priorities of the multiple servers, indicated in DNS responses, and an order of issuance of DNS queries to the DNS server. TCP options in the header of TCP packets are used for determining ICN capability of the nodes/servers and parameters pertaining to the ICN capability.