Flexible command and control in content centric networks

• US 10,075,402 B2
• Filed: 06/24/2015
• Issued: 09/11/2018
• Est. Priority Date: 06/24/2015
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Wood, Christopher A., Scott, Glenn C.
• Primary Examiner(s): Swearingen, Jeffrey R
• Application Number:
  US14/749,349
• Publication Number:
  US 20160380945A1
• Time in Patent Office: 1,175 Days
• Field of Search: None
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: H04L 51/18 Commands or executable codes
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/30 Definitions, standards or architectural aspects of layered protocol stacks

Abstract

One embodiment provides a transport-framework system that facilitates command messages to be communicated in a layer-agnostic manner. During operation, the system generates, by a component of a stack of communication modules, a first command message for a target entity. The first command message includes a name unique to the target entity, and the stack does not require a respective communication module to communicate only with a layer above or below thereof. The component sends the first command message to the target entity by inserting the first command message into a queue corresponding to the component. The component can also receive a second command message from a sending entity via a queue corresponding to the sending entity, and the second command message includes a name unique to the component. This facilitates command messages to be communicated in a layer-agnostic manner.

Claims

1. A method, comprising:

generating, by a module of a network stack of communication modules, a first command message for a target entity, the first command message including a name unique to the target entity, wherein the network stack enables a respective communication module to communicate with a layer that is not directly above or directly below the respective communication module;

sending the first command message, via a message delivery system, to the target entity by inserting the first command message into a queue corresponding to the module, wherein the message delivery system uses the name unique to the target entity and a value that represents content of the queue corresponding to the module; and

receiving a second command message from a sending entity via a queue corresponding to the sending entity, the second command message including a name unique to the component module.

2. The method of claim 1, wherein the target entity and the sending entity are one or more of:

another module of the network stack;

a module of another network stack;

an API instance associated with an application corresponding to the network stack;

an API instance associated with an application corresponding to another network stack;

a forwarder associated with the network stack; and

a forwarder associated with another network stack.

3. The method of claim 1, wherein sending the first command message further comprises:

sending the first command message via a message delivery system to the target entity.

4. The method of claim 1, wherein the method further comprises:

responsive to determining that the target entity is another module of the network stack, a module of another network stack, an API instance associated with an application corresponding to another network stack, or a forwarder associated with another network stack, setting an upward or downward output queue for the module as the queue corresponding to the module;

responsive to determining that the target entity is an API instance associated with an application corresponding to the network stack, setting the upward output queue for the module as the queue corresponding to the module; and

responsive to determining that the target entity is a forwarder associated with the network stack, setting the downward output queue for the module as the queue corresponding to the module.

5. The method of claim 1, wherein receiving the second command message further comprises:

receiving the second command message via a message delivery system from the sending entity.

6. The method of claim 1, wherein the second command message is received via an upward or downward input queue associated with the sending entity.

7. The method of claim 1, wherein the name for the first or second command message includes one or more of:

a name for the network stack;

a name for a forwarder associated with a corresponding portal instance;

a name for a module of the network stack; and

a command associated with a module of the network stack.

8. The method of claim 1, wherein a name for a module of the network stack is based on one or more of:

a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name module ordered from a most general level to a most specific level, wherein the HSVLI is applicable in a portal instance corresponding to the network stack;

a flat name that does not indicate any hierarchy;

a role of the module of the network stack; and

a unique identifier which is specific to the module of the network stack.

16. The storage medium of claim 1, wherein a name for a module of the network stack is based on one or more of:

a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name modules ordered from a most general level to a most specific level, wherein the HSVLI is applicable in a portal instance corresponding to the network stack;

a flat name that does not indicate any hierarchy;

a role of the module of the network stack; and

a unique identifier which is specific to the module of the network stack.

9. A non-transitory computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method, the method comprising:

generating, by a module of a network stack of communication modules, a first command message for a target entity, the first command message including a name unique to the target entity, wherein the network stack enables a respective communication module to communicate with a layer that is not directly above or directly below the respective communication module;

sending the first command message, via a message delivery system, to the target entity by inserting the first command message into a queue corresponding to the module, wherein the message delivery system uses the name unique to the target entity and a value that represents content of the queue corresponding to the module; and

receiving a second command message from a sending entity via a queue corresponding to the sending entity, the second command message including a name unique to the module.

10. The storage medium of claim 9, wherein the target entity and the sending entity are one or more of:

another module of the network stack;

a module of another network stack;

an API instance associated with an application corresponding to the network stack;

an API instance associated with an application corresponding to another network stack;

a forwarder associated with the network stack; and

a forwarder associated with another network stack.

11. The storage medium of claim 9, wherein sending the first command message further comprises:

sending the first command message via a message delivery system to the target entity.

12. The storage medium of claim 9, wherein the method further comprises:

responsive to determining that the target entity is another module of the network stack, a module of another network stack, an API instance associated with an application corresponding to another network stack, or a forwarder associated with another network stack, setting an upward or downward output queue for the module as the queue corresponding to the module;

responsive to determining that the target entity is an API instance associated with an application corresponding to the network stack, setting the upward output queue for the module as the queue corresponding to the module; and

responsive to determining that the target entity is a forwarder associated with the network stack, setting the downward output queue for the module as the queue corresponding to the module.

13. The storage medium of claim 9, wherein receiving the second command message further comprises:

receiving the second command message via a message delivery system from the sending entity.

14. The storage medium of claim 9, wherein the second command message is received via an upward or downward input queue associated with the sending entity.

15. The storage medium of claim 9, wherein the name for the first or second command message includes one or more of:

a name for the network stack;

a name for a forwarder associated with a corresponding portal instance;

a name for a module of the network stack; and

a command associated with a module of the network stack.

17. A computer system for facilitating forwarding of packets, 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;

generating, by a module of a network stack of communication modules, a first command message for a target entity, the first command message including a name unique to the target entity, wherein the network stack enables a respective communication module to communicate with a layer that is not directly above or directly below the respective communication module;

sending the first command, via a message delivery system, message to the target entity by inserting the first command message into a queue corresponding to the module, wherein the message delivery system uses the name unique to the target entity and a value that represents content of the queue corresponding to the module; and

receiving a second command message from a sending entity via a queue corresponding to the sending entity, the second command message including a name unique to the module.

18. The computer system of claim 17, wherein the target entity and the sending entity are one or more of:

another module of the network stack;

a module of another network stack;

an API instance associated with an application corresponding to the network stack;

an API instance associated with an application corresponding to another network stack;

a forwarder associated with the network stack; and

a forwarder associated with another network stack.

19. The computer system of claim 17, wherein sending the first command message further comprises:

sending the first command message via a message delivery system to the target entity.

20. The computer system of claim 17, wherein the method further comprises:

responsive to determining that the target entity is another module of the network stack, a module of another network stack, an API instance associated with an application corresponding to another network stack, or a forwarder associated with another network stack, setting an upward or downward output queue for the module as the queue corresponding to the module;

responsive to determining that the target entity is an API instance associated with an application corresponding to the network stack, setting the upward output queue for the module as the queue corresponding to the module; and

responsive to determining that the target entity is a forwarder associated with the network stack, setting the downward output queue for the module as the queue corresponding to the module.

21. The computer system of claim 17, wherein receiving the second command message further comprises:

receiving the second command message via a message delivery system from the sending entity.

22. The computer system of claim 17, wherein the second command message is received via an upward or downward input queue associated with the sending entity.

23. The computer system of claim 17, wherein the name for the first or second command message includes one or more of:

a name for the network stack;

a name for a forwarder associated with a corresponding portal instance;

a name for a module of the network stack; and

a command associated with a module of the network stack.

24. The computer system of claim 17, wherein a name for a module of the network stack is based on one or more of:

a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name modules ordered from a most general level to a most specific level, wherein the HSVLI is applicable in a portal instance corresponding to the network stack;

a flat name that does not indicate any hierarchy;

a role of the module of the network stack; and

a unique identifier which is specific to the module of the network stack.