Methods and systems for determining ICN capability of a node/server

Patent metadata

Field	Value
Publication number	US-11368365-B2
Application number	US-202017079292-A
Country	US
Kind code	B2
Filing date	Oct 23, 2020
Priority date	Oct 25, 2019
Publication date	Jun 21, 2022
Grant date	Jun 21, 2022

Abstract

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.

First claim

What is claimed is:

1. A method for determining information centric networking (ICN) capability of a server in a communication network, the method comprising:
sending, by a client device, at least one domain name server (DNS) query comprising at least one ICN-resolution and path discovery (IRP) resource record, to a DNS server;
receiving, by the client device, from the DNS server, at least one DNS response corresponding to the at least one DNS query; and
determining, by the client device, that the server is capable of providing at least one service using ICN if the at least one DNS response includes the at least one IRP resource record.

2. The method of claim 1 , wherein the at least one DNS query is sent by one of: at least one application in the client device or an application abstraction framework in the client device, wherein at least one change is introduced at an application level if the at least one application sends the at least one DNS query, wherein the at least one DNS query is sent in response to the at least one application being launched.

3. The method of claim 2 , wherein the application abstraction framework determines whether the at least one application in the client device supports ICN, and
connects the client device and the server.

4. The method of claim 2 , wherein the at least one change introduced at the application level is a change in a socket call Application Programming Interface (API).

5. The method of claim 1 , wherein the method further comprises:
establishing, by the client device, a non-ICN link with the server, for data transfer between the client device and the server, if the at least one DNS response does not include the at least one IRP resource record.

6. The method of claim 1 , wherein the method further comprises
establishing, by the client device, an ICN link with the server, for data transfer between the client device and the server, if the at least one DNS response includes the at least one IRP resource record.

7. A client device, in a communication network, for determining information centric networking (ICN) capability of a server, the client device comprising:
a memory; and
at least one processor coupled to the memory, wherein the at least one processor is configured to:
send at least one domain name server (DNS) query comprising at least one ICN-resolution and path discovery (IRP) resource record, to a DNS server;
receive, from the DNS server, at least one DNS response corresponding to the at least one DNS query; and
determine that the server is capable of providing at least one service using ICN, if the at least one DNS response includes the at least one IRP resource record.

8. The client device of claim 7 , wherein the at least one DNS query is sent by one of: at least one application in the client device or an application abstraction framework in the client device, wherein at least one change is introduced at an application level if the at least one application sends the at least one DNS query, wherein the at least one DNS query is sent in response to the at least one application being launched.

9. The client device of claim 8 , wherein the application abstraction framework:
determines whether the at least one application in the client device supports ICN, and connects the client device and the server.

10. The client device of claim 8 , wherein the at least one change introduced at the application level is a change in a socket call Application Programming Interface (API).

11. The client device of claim 7 , wherein the at least one processor is further configured to establish a non-ICN link with the server, for data transfer between the client device and the server, if the at least one DNS response does not include the at least one IRP resource record.

12. The client device of claim 7 , wherein the at least one processor is further configured to establish an ICN link with the server, for data transfer between the client device and the server, if the at least one DNS response includes the at least one IRP resource record.

13. A non-transitory computer readable medium for determining information centric networking (ICN) capability of a server, storing instructions, when executed by at least one processor of a client device, causing the client device to:
send at least one domain name server (DNS) query comprising at least one ICN-resolution and path discovery (IRP) resource record, to a DNS server;
receive from the DNS server, at least one DNS response corresponding to the at least one DNS query; and
determine that the server is capable of providing at least one service using ICN if the at least one DNS response includes the at least one IRP resource record.

14. The non-transitory computer readable medium of claim 13 , wherein the at least one DNS query is sent by one of: at least one application in the client device or an application abstraction framework in the client device, wherein at least one change is introduced at an application level if the at least one application sends the at least one DNS query, wherein the at least one DNS query is sent in response to the at least one application being launched.

15. The non-transitory computer readable medium of claim 14 , wherein the application abstraction framework determines whether the at least one application in the client device supports ICN, and
connects the client device and the server.

16. The non-transitory computer readable medium of claim 14 , wherein the at least one change introduced at the application level is a change in a socket call Application Programming Interface (API).

17. The non-transitory computer readable medium of claim 13 , further storing instructions, when executed by the at least one processor of the client device, causing the client device to:
establish a non-ICN link with the server, for data transfer between the client device and the server, if the at least one DNS response does not include the at least one IRP resource record.

18. The non-transitory computer readable medium of claim 13 , further storing instructions, when executed by the at least one processor of the client device, causing the client device to:
establish an ICN link with the server, for data transfer between the client device and the server, if the at least one DNS response includes the at least one IRP resource record.

Assignees

• Samsung Electronics Co Ltd

Inventors

• Kanagarathinam Madhan Raj
• Gantha Shiva Souhith
• Nigam Anshuman
• Arunachalam Karthikeyan
• Lee Sunghee
• Jayaseelan Sujith Rengan

Classifications

• H04L41/12

  Discovery or management of network topologies · CPC title

• H04L41/0866 Primary

  Checking the configuration · CPC title

• H04L61/4511 Primary

  using domain name system [DNS] · CPC title

• H04L61/1511

  Electricity · mapped topic