Named content for end-to-end information-centric ip internet

A content producer method executed on a processor serving as a local node in a digital communications network, the method comprising, in response to receiving content from a server process on the local node, wherein the content comprises a plurality of chunks:

• storing the content on the local node;
• generating a content name server (CNS) compatible name for the content and generating a plurality of chunk names for the plurality of chunks;
• generating a manifest field that holds data that indicates the chunk names and a coding method of encoding of the chunks;
• and
• causing the manifest field and the CNS-compatible name to be stored by a CNS node and a data packet that includes the manifest field and a node identifier for the node that stores the content to be sent by the CNS node in a first reliable protocol payload in reply to a request for the manifest for the CNS-compatible name.

A CNS method executed on a processor serving as a local content name server (CNS) node in a digital communications network, the method comprising:

• receiving, from a first remote node, a manifest registration packet that includes a first reliable protocol payload that includes a manifest field for content that comprises a plurality of chunks, wherein the manifest field holds data that indicates a list of chunk names for the plurality of chunks and a coding method to decode the content after the content is delivered in coded form;
• and
• storing locally in a named content delivery data structure
• a CNS-compatible name in a content name field,
• the manifest field, and
• a node identifier of the first remote node in an address field.

A proxy method executed on a processor serving as a local node in a digital communications network, the method comprising:

• receiving, from a client process on a first remote node, an interest packet that includes an Internet Protocol (IP) header that indicates a different second remote node and a first reliable protocol payload that indicates a name for content, wherein the content comprises a plurality of chunks, and a transport cookie that indicates one or more missing chunks of the plurality of chunks, wherein a missing chunk has not been successfully received by the client process;
• determining whether the missing chunk associated with the name for the content is stored locally;
• when the missing chunk associated with the name for the content is not stored locally, then forwarding the interest packet to the second remote node;
• and
• when the missing chunk associated with the name for the content is stored locally, then, instead of forwarding the interest packet to the second remote node, sending to the first remote node a data delivery packet that includes a second reliable protocol payload that indicates the name for the content and the missing chunk.

A non-transitory computer-readable medium carrying a data structure that includes:

• a first field that holds data that indicates a content name for content that comprises a plurality of data chunks;
• a second field that holds data that indicates a plurality of names for the plurality of data chunks;
• and
• a third field that holds data that indicates a method for decoding the plurality of chunks.

A non-transitory computer-readable medium carrying one or more sequences of instructions for a content consumer, wherein execution of the one or more sequences of instructions by one or more processors serving as a local node in a digital communications network causes the one or more processors to:

• send a request packet from a client process on the local node to a server process on a remote node for content, wherein the content comprises a plurality of chunks,
• receive from the remote node a manifest packet that includes a first reliable protocol payload that indicates a name for the content, a method to decode the content after the content is delivered in coded form, and a list of chunk names and corresponding sizes of the plurality of chunks;
• and
• send, to the server process, an interest packet that includes a second reliable protocol payload that indicates the name for the content and chunk names for one or more missing chunks of the plurality of chunks, wherein a missing chunk has not been successfully received by the client process.

A non-transitory computer-readable medium carrying one or more sequences of instructions for a content producer, wherein execution of the one or more sequences of instructions by one or more processors serving as a local node in a digital communications network causes the one or more processors, in response to receiving content from a server process on the local node, wherein the content comprises a plurality of chunks, to:

• store the content on the local node;
• generate a content name server (CNS) compatible name for the content and generating a plurality of chunk names for the plurality of chunks;
• generate a manifest field that holds data that indicates the chunk names and a method of encoding of the chunks;
• and
• send the manifest in a first reliable protocol payload to a CNS node configured to store the manifest field and store the CNS-compatible name in a content name field, and configured to reply to a request for the manifest for the CNS-compatible name with a data packet that includes the manifest field in a second reliable protocol payload and an node identifier for a node that stores the content.

A non-transitory computer-readable medium carrying one or more sequences of instructions for a name server, wherein execution of the one or more sequences of instructions by one or more processors serving as a local content name server (CNS) node in a digital communications network causes the one or more processors to:

• receive, from a first remote node, a manifest registration packet that includes a first reliable protocol payload that indicates a CNS-compatible name for content and a manifest field, wherein the content comprises a plurality of chunks, and wherein the manifest field holds data that indicates chunk names and metadata that indicates encoding of the chunks;
• and
• store locally in a named content delivery data structure
• the CNS-compatible name in a content name field,
• the manifest field in a manifest field, and
• a node identifier of the first remote node in an address field.

A non-transitory computer-readable medium carrying one or more sequences of instructions for a content proxy, wherein execution of the one or more sequences of instructions by one or more processors serving as a local node in a digital communications network causes the one or more processors to:

• receive, from a client process on a first remote node, an interest packet that includes an Internet Protocol (IP) header that indicates a different second remote node and a first reliable protocol payload that indicates a name for content, wherein the content comprises a plurality of chunks, and a transport cookie that indicates one or more missing chunks of the plurality of chunks, wherein a missing chunk has not been successfully received by the client process;
• determine whether the missing chunk associated with the name for the content is stored locally;
• when the missing chunk associated with the name for the content is not stored locally, then forward the interest packet to the second remote node;
• and
• when the missing chunk associated with the name for the content is stored locally, then, instead of forwarding the interest packet to the second remote node, send to the first remote node a data delivery packet that includes a second reliable protocol payload that indicates the name for the content and the missing chunk.

An apparatus comprising:

• at least one processor serving as a local node in a digital communications network;
• and
• at least one memory including one or more sequences of instructions for a content consumer,
• the at least one memory and the one or more sequences of instructions configured to, with the at least one processor, cause the apparatus to:
• send a request packet from a client process on the local node to a server process on a remote node for content, wherein the content comprises a plurality of chunks,
• receive from the remote node a manifest packet that includes a first reliable protocol payload that indicates a name for the content, a method to decode the content after the content is delivered in coded form, and a list of chunk names and corresponding sizes of the plurality of chunks;
• and
• send, to the server process, an interest packet that includes a second reliable protocol payload that indicates the name for the content and chunk names for one or more missing chunks of the plurality of chunks, wherein a missing chunk has not been successfully received by the client process.

An apparatus comprising:

• at least one processor serving as a local node in a digital communications network;
• and
• at least one memory including one or more sequences of instructions for a content producer,
• the at least one memory and the one or more sequences of instructions configured to, with the at least one processor, cause the apparatus, in response to receiving content from a server process on the local node, wherein the content comprises a plurality of chunks, to:
• store the content on the local node;
• generate a content name server (CNS) compatible name for the content and generating a plurality of chunk names for the plurality of chunks;
• generate a manifest field that holds data that indicates the chunk names and a method of encoding of the chunks;
• and
• send the manifest in a first reliable protocol payload to a CNS node configured to store the manifest field and store the CNS-compatible name in a content name field, and configured to reply to a request for the manifest for the CNS-compatible name with a data packet that includes the manifest field in a second reliable protocol payload and an node identifier for a node that stores the content.

An apparatus comprising:

• at least one processor serving as a local content name server (CNS) node in a digital communications network;
• and
• at least one memory including one or more sequences of instructions for content name server,
• the at least one memory and the one or more sequences of instructions configured to, with the at least one processor, cause the apparatus to:
• receive, from a first remote node, a manifest registration packet that includes a first reliable protocol payload that indicates a CNS-compatible name for content and a manifest field, wherein the content comprises a plurality of chunks, and wherein the manifest field holds data that indicates chunk names and metadata that indicates encoding of the chunks;
• and
• store locally in a named content delivery data structure
• the CNS-compatible name in a content name field,
• the manifest field in a manifest field, and
• a node identifier of the first remote node in an address field.

An apparatus comprising:

• at least one processor serving as a local node in a digital communications network;
• and
• at least one memory including one or more sequences of instructions for a content proxy,
• the at least one memory and the one or more sequences of instructions configured to, with the at least one processor, cause the apparatus to:
• receive, from a client process on a first remote node, an interest packet that includes an Internet Protocol (IP) header that indicates a different second remote node and a first reliable protocol payload that indicates a name for content, wherein the content comprises a plurality of chunks, and a transport cookie that indicates one or more missing chunks of the plurality of chunks, wherein a missing chunk has not been successfully received by the client process;
• determine whether the missing chunk associated with the name for the content is stored locally;
• when the missing chunk associated with the name for the content is not stored locally, then forward the interest packet to the second remote node;
• and
• when the missing chunk associated with the name for the content is stored locally, then, instead of forwarding the interest packet to the second remote node, send to the first remote node a data delivery packet that includes a second reliable protocol payload that indicates the name for the content and the missing chunk.

A system comprising:

• a consumer process executing on a first node in a digital communications network and configured to
• send a request packet for content from a client process on the first node to a server process on a different second node in the digital communications network, wherein the content comprises a plurality of chunks,
• in response to sending the request packet, receive a manifest packet that includes a first reliable protocol payload that indicates a name for the content, a node identifier for a node that stores the content, a method to decode the content after the content is delivered in coded form, and a list of chunk names of the plurality of chunks;
• and
• send, to the node that stores the content, an interest packet that includes a second reliable protocol payload that indicates the name for the content and a chunk name for each of one or more missing chunks of the plurality of chunks, wherein a missing chunk has not been successfully received by the consumer process;
• and
• a producer process executing on the second node and configured, in response to receiving content from the server process on the second node, to
• store the content on the second node,
• generate a content name server (CNS) compatible name for the content and generating a plurality of chunk names for the plurality of chunks,
• generate a manifest field that holds data that indicates the plurality of chunk names and a method of encoding of the chunks, and
• cause the manifest field and the CNS-compatible name to be stored and a data packet that includes the manifest field and a node identifier for the node that stores the content to be sent in the first reliable protocol payload in reply to a request for the manifest for the CNS-compatible name.