Updating a transport stack in a content centric network

• US 10,063,414 B2
• Filed: 05/13/2016
• Issued: 08/28/2018
• Est. Priority Date: 05/13/2016
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Fox, Kevin C., Scott, Glenn C.
• Primary Examiner(s): Shin, Kyung H
• Application Number:
  US15/154,837
• Publication Number:
  US 20170331685A1
• Time in Patent Office: 837 Days
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 65/1083 In-session procedures
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/26 Special purpose or proprietary protocols or architectures network applications for proprietary or special purpose networking environments H04L67/12
• CPC Class Codes: H04L 69/321 Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers

Abstract

One embodiment provides a transport stack updating system that facilitates updating a component of a transport stack of a computer system. During operation, the system sets, by a component of the transport stack, a state of the component as quiesced in response to receiving a pause message. A component in the quiesced state is precluded from processing an interest or a content object. The system determines whether the pause message triggers a rejection passes an acknowledgment message of the pause message up the transport stack. The acknowledgment message indicates that the pause message has been successfully processed by a respective component of the transport stack.

Claims

1. A method, comprising:

at a particular component of a plurality of components of a transport stack of a content centric network node;

receiving a pause message while the particular component is processing interests and/or content objects;

determining whether the pause message triggers a rejection; and

if it is determined that the pause message does not trigger a rejection;

setting a state of the particular component as quiesced such that the particular component is precluded from processing the interests and/or the content objects;

receiving an update message configured to provide an update for the particular component;

updating the particular component based on the update message while the state of the particular component is quiesced; and

setting the state of the particular component as active such that the particular component resumes processing the interests and/or the content objects in accordance with the update.

2. The method of claim 1, wherein the particular component is a final component of the transport stack, the method further comprising:

if it is determined that the pause message does not trigger the rejection;

generating an acknowledgment message in response to receiving the pause message, wherein the acknowledgment message indicates that the pause message has been successfully processed by the plurality of components; and

sending the acknowledgement message up the transport stack.

3. The method of claim 1, further comprising:

if it is determined that the pause message triggers the rejection;

sending a pause failure message up the transport stack, wherein the pause failure message indicates that the pause message has not been successfully processed by the plurality of components.

4. The method of claim 3, wherein determining that the pause message triggers the rejection includes one or more of:

detecting a timeout event, processing a back flow, and identifying inter-dependent messages.

5. The method of claim 1, wherein the pause message is an interest message, the method further comprising:

if it is determined that the pause message does not trigger the rejection;

sending a control message to an administrator agent, wherein the control message transfers control to the administrator agent for updating the particular component.

6. The method of claim 1, wherein a name for the particular component of the transport stack is based on one or more of:

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 HSVLI is applicable in a portal instance corresponding to the transport stack;

a flat name that does not indicate any hierarchy;

a role of the particular component of the transport stack; and

a unique identifier which is specific to the particular component of the transport stack.

7. The method of claim 1, further comprising:

if it is determined that the pause message does not trigger the rejection;

flushing a local buffer of the particular component.

8. The method of claim 1, further comprising:

if it is determined that the pause message does not trigger the rejection;

receiving a resume message configured to instruct the particular component to set the state of the particular component as active.

9. A computer system for updating a transport stack, the system comprising:

a processor; and

a storage device storing instructions that when executed by the processor cause the processor to perform a method at a particular component of a plurality of components of the transport stack of a content centric network node, the method comprising;

receiving a pause message while the particular component is processing interests and/or content objects;

determining whether the pause message triggers a rejection; and

if it is determined that the pause message does not trigger a rejection;

setting a state of the particular component as quiesced such that the particular component is precluded from processing the interests and/or the content objects;

receiving an update message configured to provide an update for the particular component;

updating the particular component based on the update message while the state of the particular component is quiesced; and

setting the state of the particular component as active such that the particular component resumes processing the interests and/or the content objects in accordance with the update.

10. The computer system of claim 9, wherein the particular component is a final component of the transport stack, the method further comprising:

if it is determined that the pause message does not trigger the rejection;

generating an acknowledgment message in response to receiving the pause message, wherein the acknowledgment message indicates that the pause message has been successfully processed by the plurality of components; and

sending the acknowledgement message up the transport stack.

11. The computer system of claim 9, wherein the method further comprises:

if it is determined that the pause message triggers the rejection;

sending a pause failure message up the transport stack, wherein the pause failure message indicates that the pause message has not been successfully processed by the plurality of components.

12. The computer system of claim 11, wherein determining that the pause message triggers the rejection includes one or more of:

detecting a timeout event, processing a back flow, and identifying inter-dependent messages.

13. The computer system of claim 9, wherein the pause message is an interest message, the method further comprising:

if it is determined that the pause message does not trigger the rejection;

sending a control message to an administrator agent, wherein the control message transfers control to the administrator agent for updating the particular component.

14. The computer system of claim 9, wherein a name for the particular component of the transport stack is based on one or more of:

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 HSVLI is applicable in a portal instance corresponding to the transport stack;

a flat name that does not indicate any hierarchy;

a role of the particular component of the transport stack; and

a unique identifier which is specific to the particular component of the transport stack.

15. A non-transitory computer-readable storage medium storing instructions that when executed by a processor cause the processor to perform a method at a particular component of a plurality of components of a transport stack of a content centric network node, the method comprising:

receiving a pause message while the particular component is processing interests and/or content objects;

determining whether the pause message triggers a rejection; and

if it is determined that the pause message does not trigger a rejection;

setting a state of the particular component as quiesced such that the particular component is precluded from processing the interests and/or the content objects;

receiving an update message configured to provide an update for the particular component;

updating the particular component based on the update message while the state of the particular component is quiesced; and

setting the state of the particular component as active such that the particular component resumes processing the interests and/or the content objects in accordance with the update.

16. The storage medium of claim 15, wherein the particular component is a final component of the transport stack, the method further comprising:

generating an acknowledgment message in response to receiving the pause message, wherein the acknowledgment message indicates that the pause message has been successfully processed by the plurality of components; and

sending the acknowledgement message up the transport stack.

17. The storage medium of claim 15, the method further comprising:

if it is determined that the pause message triggers the rejection;

sending a pause failure message up the transport stack, wherein the pause failure message indicates that the pause message has not been successfully processed by the plurality of components.

18. The storage medium of claim 17, wherein determining that the pause message triggers the rejection includes one or more of:

detecting a timeout event, processing a back flow, and identifying inter-dependent messages.

19. The storage medium of claim 15, wherein the pause message is an interest message, the method further comprising:

if it is determined that the pause message does not trigger the rejection;

sending a control message to an administrator agent, wherein the control message transfers control to the administrator agent for updating the particular component.

20. The storage medium of claim 15, wherein a name for the particular component of the transport stack is based on one or more of:

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 HSVLI is applicable in a portal instance corresponding to the transport stack;

a flat name that does not indicate any hierarchy;

a role of the particular component of the transport stack; and

a unique identifier which is specific to the particular component of the transport stack.