Maintaining named data networking (NDN) flow balance with highly variable data object sizes

Patent metadata

Field	Value
Publication number	US-10200300-B2
Application number	US-201715398293-A
Country	US
Kind code	B2
Filing date	Jan 4, 2017
Priority date	Aug 11, 2014
Publication date	Feb 5, 2019
Grant date	Feb 5, 2019

Abstract

A network device in a Named Data Networking (NDN) network receives an Interest from a consumer including a name and an Expected Data Size of data requested through the Interest. The network device forwards the Interest along a path to a producer of the data based on the name. As a result, the network device receives data that has traversed the path in reverse and satisfies the forwarded Interest. The network device determines an actual data size of the received data. The network device compares the actual data size to the Expected Data Size. If the actual data size is greater than the expected data size, and if a level of traffic congestion associated with forwarding the received data to the consumer is below a threshold, forwarding the received data to the consumer along a path based on the name of the data.

First claim

What is claimed is:

1. A method comprising:
at a network device among network devices configured to perform named data networking (NDN) in an NDN network:
receiving an Interest from a consumer, the Interest requesting data by name and including an expected data size of the requested data;
responsive to receiving the Interest, allocating network device resources to handle the data expected to satisfy the Interest based on the expected data size;
forwarding the Interest along a path to a producer of the data based on the name;
obtaining received data that has traversed the path in reverse and satisfies the forwarded Interest;
determining an actual data size of the received data;
comparing the actual data size to the expected data size;
if the comparing indicates the actual data size is greater than the expected data size, and if a level of traffic congestion associated with forwarding the received data to the consumer is below a threshold, forwarding the received data to the consumer along a path based on the name of the data; and
if the comparing indicates the actual data size is less than the expected data size, responsive to receiving one or more additional Interests that name the data, allocating less network device resources to handle the data expected to satisfy the one or more additional Interests than were previously allocated to handle the data expected to satisfy the Interest.

2. The method of claim 1 , further comprising:
storing state information that associates incoming and outgoing faces of the network device traversed by the Interest with the name of the data to enable forwarding of the Interest along the path to the producer and the forwarding of the received data along the path in reverse to the consumer; and
storing the expected data size in association with the state information.

3. The method of claim 1 , further comprising, if the comparing indicates the actual data size is greater than the expected data size:
determining whether the level of traffic congestion associated with forwarding the received data to the consumer is below the threshold; and
if it is determined that level of traffic congestion is below the threshold, performing the forwarding the received data to the consumer along the path based on the name of the data.

4. The method of claim 3 , further comprising: if it is determined that the level of traffic congestion is above the threshold, dropping the received data and forwarding a message indicating that the actual data size is greater than the expected data size along a reverse path to the consumer.

5. The method of claim 1 , further comprising:
receiving multiple Interests at a face of the network device;
determining whether the multiple Interests received at the face include a same name but different expected data sizes for the data; and
if it is determined that the multiple Interests received at the face include the same name but different expected data sizes for the data, reducing a data rate at which the face operates.

6. The method of claim 1 , further comprising:
receiving multiple Interests including a same name but different expected data sizes;
forwarding one of the multiple Interests;
storing a maximum one of the different expected data sizes;
responsive to the forwarded one of the multiple Interests, receiving an error message, instead of receiving data satisfying that Interest, the error message indicating that the actual data size is less than the expected data size; and
responsive to the error message, re-forwarding the one of the multiple Interests modified to include the maximum expected data size.

7. An apparatus comprising:
multiple network faces to send and receive named data networking (NDN) packets to and from an NDN network; and
a processor coupled to the multiple network faces and configured to:
receive multiple Interests at a face among the multiple faces, each Interest requesting data by name and including an expected data size of the requested data;
determine whether the multiple Interests include the same name but different expected data sizes for the data; and
if the multiple Interests include the same name but different expected data sizes for the data:
forward one of the multiple Interests;
store a maximum one of the different expected data sizes;
responsive to the forwarded one of the multiple Interests, receive an error message, instead of receiving data satisfying the one of the multiple Interests, the error message indicating that the actual data size is less than the expected data size; and
responsive to the error message, re-forward the one of the multiple Interests modified to include the maximum expected data size.

8. The apparatus of claim 7 , wherein the processor is further configured to:
store state information that associates incoming and outgoing ones of the multiple faces traversed by at least one Interest among the multiple Interests with the name of the data in the at least one Interest to enable forwarding of the at least one Interest along a path to a producer of the data and then forwarding of the data, when received from the producer, along the path in reverse to a consumer that originated the at least one Interest; and
store the expected data size in association with the state information.

9. The apparatus of claim 7 , wherein the processor is further configured to, if the multiple Interests include the same name but different expected data sizes for the data, reduce a data rate at which the face operates.

10. The apparatus of claim 7 , wherein the processor is further configured to:
forward at least one Interest among the multiple Interests along a path to a producer of the data requested by the name in the at least one Interest based on the name;
obtain received data that has traversed the path in reverse and satisfies the forwarded at least one Interest;
determine an actual data size of the received data;
compare the actual data size to the expected data size; and
perform an action with respect to the received data based on the compare.

11. The apparatus of claim 10 , wherein the processor is further configured to:
store state information that associates incoming and outgoing ones of the multiple faces traversed by the at least one Interest with the name of the data to enable forwarding of the at least one Interest along the path to the producer and the forwarding of the received data along the path in reverse to a consumer that originated the at least one Interest; and
store the expected data size in association with the state information.

12. The apparatus of claim 10 , wherein, if the compare indicates the actual data size is greater than the expected data size, the processor performs the action with respect to the received data by:
determining whether a level of traffic congestion associated with forwarding the received data to a consumer that originated the at least one Interest is below a threshold; and
if the level of traffic congestion is below the threshold, forwarding the received data to the consumer along a path based on the name of the data.

13. The apparatus of claim 10 , wherein the processor is further configured to:
responsive to receiving the at least one Interest among the multiple Interests, allocate network device resources to handle the data expected to satisfy the at least one Interest based on the expected data size; and
if the compare indicates the actual data size is less than the expected data size, responsive to receiving one or more additional Interests that name the data, allocate less network device resources to handle the data expected to satisfy the one or more addition

Assignees

• Cisco Tech Inc

Inventors

• Oran Dave

Classifications

• H04L43/0876

  Network utilisation, e.g. volume of load or congestion level · CPC title

• H04L47/32

  by discarding or delaying data units, e.g. packets or frames · CPC title

• H04L47/722 Primary

  at the destination endpoint, e.g. reservation of terminal resources or buffer space · CPC title

• H04L67/327

  Electricity · mapped topic

• H04L47/74

  measures in reaction to resource unavailability · CPC title