Peer-to-peer sharing in a content centric network

• US 9,602,596 B2
• Filed: 01/12/2015
• Issued: 03/21/2017
• Est. Priority Date: 01/12/2015
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Systems, Inc.
• Inventors: Mosko, Marc E.
• Primary Examiner(s): JEAN, FRANTZ B
• Application Number:
  US14/595,123
• Publication Number:
  US 20160205178A1
• Time in Patent Office: 799 Days
• Field of Search: 709/204, 709/217, 709/219
• US Class Current: 1/1
• CPC Class Codes: H04L 2101/35 containing special prefixes
• CPC Class Codes: H04L 45/021 Ensuring consistency of routing table updates, e.g. by using epoch numbers
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1063 Discovery through centralising entities
• CPC Class Codes: H04L 67/1074 for supporting data block transmission mechanisms file transfer H04L67/06
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

The system receives a list of one or more name prefixes associated with an original name, wherein the original name corresponds to an original root manifest that indicates a set of original content objects and includes a set of content object hash (COH) values for the indicated set of original content objects, and wherein the original root manifest is registered with a tracking service. Based on a name prefix from the list, the system receives the original root manifest and selects a peer node that stores one or more of the original content objects. The system determines which original content objects are stored at the selected peer node and generates an interest for an original content object, wherein the name for the interest includes the name prefix, and wherein the third interest includes a COH value for an original content object stored at the selected peer node.

Claims

1. A computer-implemented method, comprising:

receiving, by a content consuming device, in response to a first interest for a piece of content based on an original name, a first content object that includes a list of one or more name prefixes associated with the original name,

wherein a name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level,

wherein the original name corresponds to an original root manifest that indicates a set of original content objects and includes a set of content object hash (COH) values for the indicated set of original content objects, and

wherein the original root manifest is registered with a tracking service;

receiving, in response to a second interest based on a name prefix from the list, a second content object that is the original root manifest;

selecting a peer node based on the name prefix, wherein the peer node stores one or more of the original content objects;

determining which original content objects are stored at the selected peer node; and

generating a third interest for a respective content object of the original content objects, wherein the name for the third interest includes the name prefix used to select the peer node, and wherein the third interest includes a COH value for a determined original content object stored at the selected peer node.

2. The method of claim 1, wherein determining which original objects are stored at the selected peer node further comprises:

generating a request for an index value from the selected peer node, wherein the request includes a first current index value of a last known peer node; and

receiving, based on the request, a response that indicates a second current index value of the selected peer node, wherein the second current index value indicates which original content objects are stored at the selected peer node.

3. The method of claim 1, wherein the original root manifest includes metadata information for the content represented by the original manifest, wherein the metadata information can be used by a content consuming device to search for content in a CCN, and wherein the metadata information includes one or more of:

a title for the content represented by the original root manifest;

one or more key words for the content represented by the original root manifest; and

a description for the content represented by the original root manifest.

4. The method of claim 1, wherein in response to receiving the original root manifest, the method further comprises:

creating a new root manifest, wherein the new root manifest indicates the original root manifest and a new name associated with the original name; and

registering the new root manifest with the tracking service, wherein a new name prefix associated with the new name is added to the list.

5. The method of claim 4, wherein in response to receiving one or more of the original content objects, the method further comprises:

receiving a fourth interest for a respective content object of the original content objects, wherein the name for the fourth interest includes the new name prefix, and wherein the fourth interest includes a COH value for the respective content object.

6. The method of claim 4, wherein the original root manifest includes a signature of an original publisher of the content indicated by the original root manifest, and wherein the new root manifest includes a signature of a user of the content consuming device.

7. The method of claim 4, further comprising:

generating a request to remove the new name prefix from the list, wherein the request includes a signature of a user of the content consuming device and a COH value of a manifest for removal.

8. The method of claim 4, wherein the original root manifest includes an additional name to be used as a routable prefix for the content represented by the original root manifest, and wherein the new root manifest includes an additional name to be used as a routable prefix for the content represented by the new root manifest.

9. A computer-implemented method, comprising:

receiving, by a tracking device, an original root manifest for registration,

wherein the original root manifest indicates a set of original content objects and includes a set of content object hash (COH) values for the indicated set of original content objects,

wherein the original root manifest further indicates an original name, an original name prefix associated with the original name, and a signature of a publisher of the original root manifest, and

wherein a name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level;

verifying the signature of the publisher based on a public key of the publisher;

adding the original name prefix to a list that indicates one or more name prefixes associated with the original name;

generating a content object that indicates the list in response to a request for a content object indicating the one or more name prefixes associated with the original name.

10. The method of claim 9, further comprising:

receiving a new root manifest for registration, wherein the new root manifest indicates the original root manifest, a new name associated with the original name, and a signature of a publisher of the new root manifest;

verifying the signature of the publisher of the new root manifest based on a public key of the publisher of the new root manifest;

in response to verifying the signature of the publisher of the original root manifest indicated in the new root manifest, adding the new name prefix to the list that indicates the one or more name prefixes associated with the original name.

11. The method of claim 9, further comprising:

maintaining a synchronization protocol with one or more other tracking devices, wherein the tracking device and the one or more other tracking devices share a same anycast address, and wherein any of the synchronized tracking devices can fulfill a request for a content object that indicates the list.

12. The method of claim 9, wherein the tracking device receives the registration request from a content hosting device, further comprising:

receiving, from the content hosting device, a request to remove a name prefix from the list, wherein the request includes a signature of the content hosting device and a COH value of a manifest for removal;

in response to verifying the signature of the content hosting device and in response to determining that the COH value matches a manifest registered with the tracking device, removing the name prefix associated with the request from the list.

13. A computer system for accessing content, the system comprising:

a processor;

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

receiving, by a content consuming device, in response to a first interest for a piece of content based on an original name, a first content object that includes a list of one or more name prefixes associated with the original name,

wherein a name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level,

wherein the original name corresponds to an original root manifest that indicates a set of original content objects and includes a set of content object hash (COH) values for the indicated set of original content objects, and

wherein the original root manifest is registered with a tracking service;

receiving, in response to a second interest based on a name prefix from the list, a second content object that is the original root manifest;

selecting a peer node based on the name prefix, wherein the peer node stores one or more of the original content objects;

determining which original content objects are stored at the selected peer node; and

generating a third interest for a respective content object of the original content objects, wherein the name for the third interest includes the name prefix used to select the peer node, and wherein the third interest includes a COH value for a determined original content object stored at the selected peer node.

14. The computer system of claim 13, wherein determining which original objects are stored at the selected peer node further comprises:

generating a request for an index value from the selected peer node, wherein the request includes a first current index value of a last known peer node; and

receiving, based on the request, a response that indicates a second current index value of the selected peer node, wherein the second current index value indicates which original content objects are stored at the selected peer node.

15. The computer system of claim 13, wherein the original root manifest includes metadata information for the content represented by the original manifest, wherein the metadata information can be used by a content consuming device to search for content in a CCN, and wherein the metadata information includes one or more of:

a title for the content represented by the original root manifest;

one or more key words for the content represented by the original root manifest; and

a description for the content represented by the original root manifest.

16. The computer system of claim 13, wherein in response to receiving the original root manifest, the method further comprises:

creating a new root manifest, wherein the new root manifest indicates the original root manifest and a new name associated with the original name; and

registering the new root manifest with the tracking service, wherein a new name prefix associated with the new name is added to the list.

17. The computer system of claim 16, wherein in response to receiving one or more of the original content objects, the method further comprises:

receiving a fourth interest for a respective content object of the original content objects, wherein the name for the fourth interest includes the new name prefix, and wherein the fourth interest includes a COH value for the respective content object.

18. The computer system of claim 16, wherein the original root manifest includes a signature of an original publisher of the content indicated by the original root manifest, and wherein the new root manifest includes a signature of a user of the content consuming device.

19. The computer system of claim 16, wherein the method further comprises:

generating a request to remove the new name prefix from the list, wherein the request includes a signature of a user of the content consuming device and a COH value of a manifest for removal.

20. The computer system of claim 16, wherein the original root manifest includes an additional name to be used as a routable prefix for the content represented by the original root manifest, and wherein the new root manifest includes an additional name to be used as a routable prefix for the content represented by the new root manifest.

21. A computer system for accessing content, the system comprising:

a processor;

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

receiving, by a tracking device, an original root manifest for registration,

wherein the original root manifest indicates a set of original content objects and includes a set of content object hash (COH) values for the indicated set of original content objects,

wherein the original root manifest further indicates an original name, an original name prefix associated with the original name, and a signature of a publisher of the original root manifest, and

wherein a name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level;

verifying the signature of the publisher based on a public key of the publisher;

adding the original name prefix to a list that indicates one or more name prefixes associated with the original name;

generating a content object that indicates the list in response to a request for a content object indicating the one or more name prefixes associated with the original name.

22. The computer system of claim 21, wherein the method further comprises:

receiving a new root manifest for registration, wherein the new root manifest indicates the original root manifest, a new name associated with the original name, and a signature of a publisher of the new root manifest;

verifying the signature of the publisher of the new root manifest based on a public key of the publisher of the new root manifest;

in response to verifying the signature of the publisher of the original root manifest indicated in the new root manifest, adding the new name prefix to the list that indicates the one or more name prefixes associated with the original name.

23. The computer system of claim 21, wherein the method further comprises:

maintaining a synchronization protocol with one or more other tracking devices, wherein the tracking device and the one or more other tracking devices share a same anycast address, and wherein any of the synchronized tracking devices can fulfill a request for a content object that indicates the list.

24. The computer system of claim 21, wherein the tracking device receives the registration request from a content hosting device, and wherein the method further comprises:

receiving, from the content hosting device, a request to remove a name prefix from the list, wherein the request includes a signature of the content hosting device and a COH value of a manifest for removal;

in response to verifying the signature of the content hosting device and in response to determining that the COH value matches a manifest registered with the tracking device, removing the name prefix associated with the request from the list.