Network node, endpoint node and method of receiving an interest message

Patent metadata

Field	Value
Publication number	US-10715592-B2
Application number	US-201716099679-A
Country	US
Kind code	B2
Filing date	May 12, 2017
Priority date	May 13, 2016
Publication date	Jul 14, 2020
Grant date	Jul 14, 2020

Abstract

The invention relates to a network node ( 15 ) comprising at least one communication interface, at least one memory, and at least one processor. The at least one processor is configured to receive an interest message on the at least one communication interface from a downstream node ( 14 ), the interest message comprising a name of a requested data object, to determine whether to bid for storing the requested data object in the at least one memory, to calculate a bid value, to forward the interest message to an upstream node ( 16 ) on the at least one communication interface, the interest message including the calculated bid value in dependence on at least the determination whether to bid, to receive a data message comprising the requested data object from the upstream node on the at least one communication interface, to determine from at least the data message whether the network node won the bid, to store the data object in the at least one memory if the network node won the bid, and to forward the data message to the downstream node on the at least one communication interface.

First claim

The invention claimed is:

1. A network node, comprising:
at least one communication interface;
at least one memory; and
at least one processor, configured to:
receive an interest message on said at least one communication interface from a downstream node, said interest message comprising a name of a requested data object;
determine whether to bid for storing said requested data object in said at least one memory;
calculate a bid value;
forward said interest message to an upstream node on said at least one communication interface, said interest message including said calculated bid value in dependence on at least said determination whether to bid;
receive a data message comprising said requested data object from said upstream node on said at least one communication interface;
determine from at least said data message whether said network node won said bid;
store said data object in said at least one memory if said network node won said bid; and
forward said data message to said downstream node on said at least one communication interface.

2. The network node of claim 1 , wherein said received interest message further comprises a received bid value and said at least one processor is further configured to:
include said calculated bid value in said interest message if said determination whether to bid was positive and said calculated bid value represents a higher bid than said received bid value.

3. The network node of claim 1 , wherein said at least one processor is further configured to:
record bidding information in said at least one memory, said bidding information representing whether said network node included said calculated bid value in said interest message.

4. The network node of claim 3 , wherein said at least one processor is further configured to:
determine from at least said data message and said bidding information whether said network node won said bid.

5. The network node of claim 4 , wherein said received data message comprises an ignore counter, said ignore counter representing an amount of downstream nodes that lost said bid as determined by said upstream node or a further upstream node, and wherein said at least one processor is further configured to:
determine from at least said ignore counter and said bidding information whether said network node won said bid.

6. The network node of claim 5 , wherein said at least one processor is further configured to:
increment a node counter in said interest message before forwarding said interest message to said upstream node, said node counter representing an amount of downstream nodes.

7. The network node of claim 6 , wherein said at least one processor is further configured to:
record a losing bidder count in said at least one memory if said network node included said calculated bid value in said interest message, said losing bidder count being based on said node counter included in said received interest message and representing an amount of downstream nodes that lost said bid as determined by said network node.

8. The network node of claim 7 , wherein said at least one processor is further configured to:
set said ignore counter in said data message based on said losing bidder count before forwarding said data message to said downstream node if said network node won said bid.

9. The network node of claim 1 , wherein said at least one processor is further configured to:
determine whether to bid for storing said requested data object in said at least one memory by checking whether at least one empty slot is available on said at least one memory and/or whether a least recently cached item is older than a certain age threshold.

10. The network node of claim 1 , wherein said at least one processor is further configured to:
determine whether to bid for storing said requested data object in said at least one memory by checking whether said calculated bid value represents a bid which exceeds a certain auction threshold.

11. An endpoint node, comprising:
at least one communication interface; and
at least one processor configured to:
determine a name of a requested data object;
create an interest message comprising said name of said requested data object and a bid field for inserting a bid value, said bid value being left undefined so as to indicate that an auction of a right to cache said requested data object should start; and
transmit said interest message to an upstream node on said at least one communication interface.

12. A method of receiving an interest message, the method comprising:
receiving an interest message on at least one communication interface from a downstream node, said interest message comprising a name of a requested data object;
determining whether to bid for storing said requested data object in at least one memory;
calculating a bid value;
forwarding said interest message to an upstream node on said at least one communication interface, said interest message including said calculated bid value in dependence on at least said determination whether to bid;
receiving a data message comprising said requested data object from said upstream node on said at least one communication interface;
determining from at least said data message whether a network node won said bid;
storing said data object in said at least one memory if said network node won said bid; and
forwarding said data message to said downstream node on said at least one communication interface.

13. A non-transitory computer medium having stored thereon one or more computer programs comprising at least one software code portion that, when run on a computer system, causes the computer system to perform the method of claim 12 .

14. A network node, comprising:
at least one communication interface;
at least one memory; and
at least one processor configured to:
receive an HTTP request for a data object on said at least one communication interface from a downstream node;
determine whether to bid for storing said requested data object in said at least one memory;
calculate a bid value;
forward said HTTP request to an upstream node on said at least one communication interface, said HTTP request including said calculated bid value in dependence on at least said determination whether to bid;
receive a response message comprising said requested data object from said upstream node on said at least one communication interface
determine from at least said response message whether said network node won said bid;
store said data object in said at least one memory if said network node won said bid; and
forward said response message to said downstream node on said at least one communication interface.

15. A method of receiving an HTTP request, the method comprising:
receiving said HTTP request for a data object on at least one communication interface from a downstream node;
determining whether to bid for storing said requested data object in at least one memory;
calculating a bid value;
forwarding said HTTP request to an upstream node on said at least one communication interface, said HTTP request including said calculated bid value in dependence on at least said determination whether to bid;
receiving a response message comprising said requested data object from said upstream node on said at least one communication interface;
determining from at least said response message whether a network node won said bid;
storing said data object in said at least one memory if said network node won said bid; and
forwarding said response message to said downstream node on said at least one communication interface.

Assignees

• Koninklijke Kpn Nv
• Nederlandse Organisatie Voor Toegepast Natuurweten Schappelijk Onderzoek Tno
• TNO

Inventors

• Gill Amritpal Singh
• D'Acunto Lucia
• Trichias Konstantinos
• Van Brandenburg Ray
• Cramer Eelco

Classifications

• H04L67/63

  Routing a service request depending on the request content or context · CPC title

• H04L67/5682 Primary

  Policies or rules for updating, deleting or replacing the stored data · CPC title

• H04L67/02 Primary

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L67/568

  Storing data temporarily at an intermediate stage, e.g. caching · CPC title

• H04L67/1097

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title