ICN Based Distributed Resource Directory for IoT Resource Discovery and Routing

• US 20170126542A1
• Filed: 10/28/2015
• Published: 05/04/2017
• Est. Priority Date: 10/28/2015
• Status: Abandoned Application

• Current Assignee: Futurewei Technologies Incorporated (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Futurewei Technologies Incorporated (Huawei Investment & Holding Co., Ltd.)
• Inventors: Dong, Lijun
• Application Number:
  US14/925,525
• Publication Number:
  US 20170126542A1
• Time in Patent Office: Days
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/12 Shortest path evaluation
• CPC Class Codes: H04L 45/20 Hop count for routing purposes, e.g. TTL
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

A method implemented in a network element (NE) configured to operate in an information centric network (ICN), the method comprising receiving, from a client via a receiver, a Resource Directory (RD) lookup message directed to a distributed RD database and comprising a lookupType field and an attribute value pair; converting the RD lookup message into an RD Lookup Forward (RDLF) comprising an RDLF lookupType field set to the lookupType field of the RD lookup message, an RDLF Time-To-Live (TTL) set to a largest number of hops that can be traversed in the ICN, and an RDLF attribute value pair set to the attribute value pair of the RD lookup message; and determining a forwarding interface list based on matching, to the attribute value pair, a routing entry from a Routing Table corresponding to the attribute value pair, wherein the Routing Table comprises routing information through the ICN to content mapped to a plurality of attribute value pairs.

Claims

1. A network element (NE) configured to operate in an information centric network (ICN), the NE comprising:

a receiver configured to receive, from an endpoint, an Internet of Things (IoT) resource registration comprising a Resource Directory (RD) entry comprising an attribute value pair;

a memory comprising a local portion of a distributed RD database and a candidate-to-be-published list;

a processor coupled to the receiver and the memory, wherein the processor is configured to;

insert the attribute and value pair in the candidate-to-be-published list; and

store the RD entry in the local portion of the distributed RD database; and

a transmitter coupled to the processor and configured to transmit an RD Entry Advertisement (RDEA) message comprising attribute value pairs copied from the candidate-to-be-published list to a plurality of neighboring NEs within the ICN for storage in a remote portion of the distributed RD database when a number of the attribute value pairs in the candidate-to-be-published list reaches a threshold.

2. The NE of claim 1, wherein stored RD entry comprises a time-to-live (TTL) attribute.

3. The NE of claim 1, wherein the transmitter is further configured to send an Attribute-Value Advertisement Cancellation (AVAC) message comprising the attribute value pair to the neighboring NEs within the ICN to remove the RD entry from the remote portion of the distributed RD database when the RD entry has expired based on the TTL attribute.

4. The NE of claim 1, wherein the receiver is further configured to receive, from the endpoint, a deletion request comprising a second RD entry comprising a second attribute value pair, wherein the processor is further configured to remove the second RD entry from the local portion of the distributed RD database, and wherein the transmitter is further configured to send an Attribute-Value Advertisement Cancellation (AVAC) message to the neighboring NEs within the ICN comprising the second attribute value pair to remove the second RD entry from the remote portion of the distributed RD database.

5. The NE of claim 1, wherein the receiver is further configured to receive, on an incoming interface, a message comprising a routing entry, and wherein the processor is further configured to:

calculate a metric based on a network path from the NE to an originator of the message;

update a Routing Table with the routing entry and the metric; and

assign the incoming interface as a forwarding interface for the routing entry in the Routing Table.

6. The NE of claim 1, wherein the receiver is further configured to receive, on an incoming interface, a message comprising a second attribute value pair, and wherein the processor is further configured to:

calculate a path metric based on a network path from the NE to an originator of the RDEA message;

update a Routing Table with the second attribute value pair and the metric; and

assign the incoming interface as a forwarding interface for the second attribute value pair in the Routing Table.

7. The NE of claim 1, wherein the receiver is further configured to receive, on an incoming interface, a message comprising a second attribute value pair and a path metric, and wherein the processor is further configured to remove the path metric from a forwarding interface list associated with the second attribute value pair when other path metrics are included in the forwarding interface list.

8. The NE of claim 1, wherein the NE is configured as a host RD for the endpoint.

9. The NE of claim 1, wherein the NE is configured as a repository for links to resources hosted by a plurality of endpoints including the endpoint from which the IoT resource registration is received.

10. A method implemented in a network element (NE) configured to operate in an information centric network (ICN), the method comprising:

receiving, from a client via a receiver, a Resource Directory (RD) lookup message directed to a distributed RD database and comprising a lookupType field and an attribute value pair;

converting the RD lookup message into an RD Lookup Forward (RDLF) comprising an RDLF lookupType field set to the lookupType field of the RD lookup message, an RDLF Time-To-Live (TTL) set to a largest number of hops that can be traversed in the ICN, and an RDLF attribute value pair set to the attribute value pair of the RD lookup message; and

determining a forwarding interface list based on matching, to the attribute value pair, a routing entry from a Routing Table corresponding to the attribute value pair, wherein the Routing Table comprises routing information through the ICN to content mapped to a plurality of attribute value pairs.

11. The method of claim 10 further comprising:

receiving, from the client via the receiver, a second Resource Directory (RD) lookup message comprising a second lookupType field and a second attribute value pair;

determining whether a matching RD entry is contained in a local portion of the distributed RD database stored in a memory based on the second attribute value pair; and

returning, through a transmitter, the matching RD entry to the client when the matching RD entry is contained in the local portion of the distributed RD database.

12. The method of claim 10 further comprising:

selecting, from the forwarding interface list, a forwarding interface for forwarding the RDLF message by determining the forwarding interface that most closely satisfies a pathing metric; and

forwarding the RDLF message through the forwarding interface.

13. The method of claim 10 further comprising:

setting the RDLF TTL field to one;

determining a number of forwarding interfaces from the forwarding interface list, wherein the number of forwarding interfaces is based on a random number; and

forwarding the RDLF message through the forwarding interfaces.

14. The method of claim 10 further comprising:

determining a plurality of forwarding interfaces from the forwarding interface list based on the plurality of forwarding interfaces most closely matching a pathing metric; and

forwarding the RDLF message through the forwarding interfaces.

15. The method of claim 10 further comprising forwarding the RDLF message through all of the forwarding interfaces contained in the forwarding interface list.

16. The method of claim 10, wherein the NE is configured as a host RD for the client.

17. A method implemented in a network element (NE) configured to operate in an information centric network (ICN), the method comprising:

receiving, via a receiver, an Resource Database (RD) Lookup Forward (RDLF) message comprising at least one attribute value pair;

determining whether a matching RD entry is contained in a local RD database based on the at least one attribute value pair;

retrieving a resource from an endpoint for the matching RD entry from a local portion of a distributed RD database; and

sending, through a transmitter, the resource to a client that requested the resource.

18. The method of claim 17 further comprising caching the resource in a memory.

19. The method of claim 17 further comprising sending the RD entry to the client through the transmitter.

20. The method of claim 17, wherein the NE is configured as a host RD for the client.