Method and system for collecting historical network information in a content centric network

• US 10,051,071 B2
• Filed: 03/04/2016
• Issued: 08/14/2018
• Est. Priority Date: 03/04/2016
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Wood, Christopher A., Solis, Ignacio, Ioannou, Andriana, Scott, Glenn C.
• Primary Examiner(s): Nguyen, Quang N
• Application Number:
  US15/061,817
• Publication Number:
  US 20170257444A1
• Time in Patent Office: 893 Days
• Field of Search: 709203, 709206, 709217, 709219, 709223, 709224, 709226, 709228, 709231, 709232, 709238
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 69/02 Protocol performance

Abstract

One embodiment provides a system that facilitates collection of historical network information. During operation, the system monitors a plurality of packets which include outgoing interests and corresponding incoming content objects, wherein a name for an interest is a hierarchically structured variable length identifier that includes contiguous name components ordered from a most general level to a most specific level. The system collects historical information associated with the packets based on name prefixes of the packets, wherein a name prefix includes one or more contiguous name components. In response to receiving a query from a requesting entity for the historical information, the system transmits the historical information, thereby facilitating the requesting entity to use the historical information to increase network efficiency.

Claims

1. A computer system for facilitating collection of historical network information, the system comprising:

a processor; and

a storage device storing instructions that when executed by the processor cause the processor to perform a method, the method comprising;

monitoring a plurality of packets which include outgoing interests and corresponding incoming content objects, wherein a name for an interest is a hierarchically structured variable length identifier that includes contiguous name components ordered from a most general level to a most specific level;

collecting historical information associated with the packets based on name prefixes of the packets, wherein a name prefix includes one or more contiguous name components;

storing the collected historical information;

receiving a query from a requesting entity for the historical information;

transmitting the historical information to the requesting entity; and

facilitating the requesting entity to use the historical information to increase network efficiency;

wherein the monitored plurality of packets further includes incoming interests and corresponding outgoing content objects.

2. The computer system of claim 1, wherein the method is performed by a collector component in the system, wherein the collector component resides in one or more of:

an application;

a single stack;

a shared stack;

a single forwarder;

a shared forwarder; and

any node in a network.

3. The computer system of claim 2, wherein the requesting entity is one or more of:

an application associated with a first stack, wherein the collector component resides in the first stack;

an application associated with a second stack that is different from the first stack;

a stack component of the first stack, wherein the stack component is different from the collector component;

a stack component of the second stack; and

any other element or node in the network.

4. The computer system of claim 1, wherein the historical information associated with the packets is one or more of:

a round trip time that begins when an outgoing interest is transmitted and ends when a corresponding incoming content object is received;

a number of outgoing interests for which a corresponding incoming content object has not been received;

a number of outgoing interests for which a corresponding incoming content object is received based on a predetermined amount of time or the round trip time;

a number of bytes correctly retrieved based on the predetermined amount of time or the round trip time;

a number of outgoing interests that time out based on the predetermined amount of time or the round trip time;

a number of outgoing interests which are retransmitted based on the predetermined amount of time or the round trip time;

a number of re-transmitted outgoing interests that time out based on the predetermined amount of time or the round trip time;

a number of interest return messages received based on the predetermined amount of time or the round trip time, wherein an interest return message is received in response to an outgoing interest and is identified based on a code indicated in the message; and

a number of outgoing interests aggregated based on the predetermined amount of time or the round trip time.

5. The computer system of claim 1, wherein the historical information associated with the packets is one or more of:

a number of active upstream paths identified for a given time;

a strategy for forwarding packets;

a first number of transmitted original interests, wherein an original interest is not a re-transmitted interest, and wherein the first number of original interests include names that share one or more name prefixes;

a second number of transmitted original interests, wherein the second number of original interests include names that do not share any name prefixes;

a first number of active entries in a forwarding information base, wherein the first number of entries include names that share one or more name prefixes; and

a second number of active entries in a forwarding information base, wherein the second number of entries include names that do not share any name prefixes.

6. The computer system of claim 1, wherein the system is a client computing device, an intermediate node, or a content producing device.

7. The computer system of claim 1, wherein collecting the historical information is further based on one or more of:

one or more name prefixes;

a routable name prefix which includes one or more contiguous name components beginning from the most general level;

a time of day;

a day of the week;

a number of upstream peers that are retrieving data; and

a feature based on time or space.

8. The computer system of claim 1, wherein the historical information associated with the packets is one or more of:

a round trip time that begins when an incoming interest is received and ends when a corresponding incoming content object is transmitted;

a number of incoming interests for which a corresponding outgoing content object has not been transmitted;

a number of incoming interests for which a corresponding outgoing content object is transmitted based on a predetermined amount of time or the round trip time;

a number of bytes correctly retrieved based on the predetermined amount of time or the round trip time;

a number of incoming interests that time out based on the predetermined amount of time or the round trip time;

a number of re-transmitted incoming interests based on the predetermined amount of time or the round trip time;

a number of re-transmitted incoming interests that time out based on the predetermined amount of time or the round trip time;

a number of interest return messages transmitted based on the predetermined amount of time or the round trip time, wherein an interest return message is transmitted in response to an incoming interest and is identified based on a code indicated in the message; and

a number of incoming interests aggregated based on a predetermined amount of time or a round trip time.

9. A computer-implemented method for facilitating collection of historical network information, the method comprising:

monitoring a plurality of packets which include outgoing interests and corresponding incoming content objects, wherein a name for an interest is a hierarchically structured variable length identifier that includes contiguous name components ordered from a most general level to a most specific level;

collecting historical information associated with the packets based on name prefixes of the packets, wherein a name prefix includes one or more contiguous name components;

storing the collected historical information;

receiving a query from a requesting entity for the historical information;

transmitting the historical information to the requesting entity; and

facilitating the requesting entity to use the historical information to increase network efficiency;

wherein the monitored plurality of packets further includes incoming interests and corresponding outgoing content objects.

10. The method of claim 9, wherein the method is performed by a collector component in a system, wherein the collector component resides in one or more of:

an application;

a single stack;

a shared stack;

a single forwarder;

a shared forwarder; and

any node in a network.

11. The method of claim 10, wherein the requesting entity is one or more of:

an application associated with a first stack, wherein the collector component resides in the first stack;

an application associated with a second stack that is different from the first stack;

a stack component of the first stack, wherein the stack component is different from the collector component;

a stack component of the second stack; and

any other element or node in the network.

12. The method of claim 9, wherein the historical information associated with the packets is one or more of:

a round trip time that begins when an outgoing interest is transmitted and ends when a corresponding incoming content object is received;

a number of outgoing interests for which a corresponding incoming content object has not been received;

a number of outgoing interests for which a corresponding incoming content object is received based on a predetermined amount of time or the round trip time;

a number of bytes correctly retrieved based on the predetermined amount of time or the round trip time;

a number of outgoing interests that time out based on the predetermined amount of time or the round trip time;

a number of outgoing interests which are retransmitted based on the predetermined amount of time or the round trip time;

a number of re-transmitted outgoing interests that time out based on the predetermined amount of time or the round trip time;

a number of interest return messages received based on the predetermined amount of time or the round trip time, wherein an interest return message is received in response to an outgoing interest and is identified based on a code indicated in the message; and

a number of outgoing interests aggregated based on the predetermined amount of time or the round trip time.

13. The method of claim 9, wherein the historical information associated with the packets is one or more of:

a number of active upstream paths identified for a given time;

a strategy for forwarding packets;

a first number of transmitted original interests, wherein an original interest is not a re-transmitted interest, and wherein the first number of original interests include names that share one or more name prefixes;

a second number of transmitted original interests, wherein the second number of original interests include names that do not share any name prefixes;

a first number of active entries in a forwarding information base, wherein the first number of entries include names that share one or more name prefixes; and

a second number of active entries in a forwarding information base, wherein the second number of entries include names that do not share any name prefixes.

14. The method of claim 9, wherein the method is performed by a client computing device, an intermediate node, or a content producing device.

15. The method of claim 9, wherein collecting the historical information is further based on one or more of:

one or more name prefixes;

a routable name prefix which includes one or more contiguous name components beginning from the most general level;

a time of day;

a day of the week;

a number of upstream peers that are retrieving data; and

a feature based on time or space.

16. The method of claim 9, wherein the historical information associated with the packets is one or more of:

a round trip time that begins when an incoming interest is received and ends when a corresponding incoming content object is transmitted;

a number of incoming interests for which a corresponding outgoing content object has not been transmitted;

a number of incoming interests for which a corresponding outgoing content object is transmitted based on a predetermined amount of time or the round trip time;

a number of bytes correctly retrieved based on the predetermined amount of time or the round trip time;

a number of incoming interests that time out based on the predetermined amount of time or the round trip time;

a number of re-transmitted incoming interests based on the predetermined amount of time or the round trip time;

a number of re-transmitted incoming interests that time out based on the predetermined amount of time or the round trip time;

a number of interest return messages transmitted based on the predetermined amount of time or the round trip time, wherein an interest return message is transmitted in response to an incoming interest and is identified based on a code indicated in the message; and

a number of incoming interests aggregated based on a predetermined amount of time or a round trip time.

17. A non-transitory computer readable storage media encoded with instructions, that when executed by processor, cause the processor to perform operations for facilitating collection of history network comprising:

monitoring a plurality of packets which include outgoing interests and corresponding incoming content objects, wherein a name for an interest is a hierarchically structured variable length identifier that includes contiguous name components ordered from a most general level to a most specific level;

collecting historical information associated with the packets based on name prefixes of the packets, wherein a name prefix includes one or more contiguous name components;

storing the collected historical information; and

in response to receiving a query from a requesting entity for the historical information, transmitting the historical information, thereby facilitating the requesting entity to use the historical information to increase network efficiency;

wherein the monitored plurality of packets further includes incoming interests and corresponding outgoing content objects.

18. The non-transitory computer readable storage media of claim 17, wherein the historical information associated with the packets is one or more of:

a round trip time that begins when an outgoing interest is transmitted and ends when a corresponding incoming content object is received;

a number of outgoing interests for which a corresponding incoming content object has not been received;

a number of outgoing interests for which a corresponding incoming content object is received based on a predetermined amount of time or the round trip time;

a number of bytes correctly retrieved based on the predetermined amount of time or the round trip time;

a number of outgoing interests that time out based on the predetermined amount of time or the round trip time;

a number of outgoing interests which are retransmitted based on the predetermined amount of time or the round trip time;

a number of re-transmitted outgoing interests that time out based on the predetermined amount of time or the round trip time;

a number of interest return messages received based on the predetermined amount of time or the round trip time, wherein an interest return message is received in response to an outgoing interest and is identified based on a code indicated in the message; and

a number of outgoing interests aggregated based on the predetermined amount of time or the round trip time.

19. The non-transitory computer readable storage media of claim 17, wherein the historical information associated with the packets is one or more of:

a number of active upstream paths identified for a given time;

a strategy for forwarding packets;

a first number of transmitted original interests, wherein an original interest is not a re-transmitted interest, and wherein the first number of original interests include names that share one or more name prefixes;

a second number of transmitted original interests, wherein the second number of original interests include names that do not share any name prefixes;

a first number of active entries in a forwarding information base, wherein the first number of entries include names that share one or more name prefixes; and

a second number of active entries in a forwarding information base, wherein the second number of entries include names that do not share any name prefixes.

20. The non-transitory computer readable storage media of claim 17, wherein the instructions that cause the processor to perform the collecting the historical information comprise instructions that cause the processor to perform the collector further based on one or more of:

one or more name prefixes;

a routable name prefix which includes one or more contiguous name components beginning from the most general level;

a time of day;

a day of the week;

a number of upstream peers that are retrieving data; and

a feature based on time or space.