AUTO-CONFIGURABLE TRANSPORT STACK

• US 20180020084A1
• Filed: 09/28/2017
• Published: 01/18/2018
• Est. Priority Date: 01/12/2015
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Solis, Ignacio, Scott, Glenn C.
• Granted Patent: US 10,440,161 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence

Abstract

A computer-implemented method includes: receiving an interest of an object in a network; obtaining a stack requirement for a protocol stack, wherein the stack requirement specifies at least a functionality for a stack component; selecting the stack component, based on the functionality and at least a name prefix of the interest or the object; and instantiating the stack component in the protocol stack.

Claims

1. A computer-implemented method, comprising:

receiving an interest of an object in a network;

obtaining a stack requirement for a protocol stack, wherein the stack requirement specifies at least a functionality for a stack component;

selecting the stack component, based on the functionality and at least a name prefix of the interest or the object; and

instantiating the stack component in the protocol stack.

2. The method of claim 1, wherein the stack component is selected based on a name of the interest or the object.

3. The method of claim 1, wherein the selecting includes:

determining, from the stack requirement, a component requirement;

determining, from a component repository, a set of components that satisfies the component requirement; and

selecting, from the set of components, the stack component, which is compatible with other components in the protocol stack.

4. The method of claim 1, further comprising:

searching for the stack component in a local repository; and

responsive to determining that the stack component is not available in the local repository, obtaining the stack component from a remote repository.

5. The method of claim 4, wherein the remote repository includes one or more of:

a component cache;

a component storage server;

or

a component marketplace.

6. The method of claim 1, further comprising:

determining that an updated version of the stack component exists;

determining a protocol stack in which the stack component is instantiated; and

replacing an instantiation of the stack component with an instantiation of the updated version of the stack component.

7. The method of claim 6, further comprising:

analyzing the updated version of the stack component to obtain a stack requirement; and

responsive to determining that the stack requirement of the stack component has changed, updating an implementation of the protocol stack to satisfy a new stack requirement.

8. 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:

receiving an interest of an object in a network;

obtaining a stack requirement for a protocol stack, wherein the stack requirement specifies at least a functionality for a stack component;

selecting the stack component, based on the functionality and at least a name prefix of the interest or the object; and

instantiating the stack component in the protocol stack.

9. The non-transitory computer-readable storage medium of claim 8, wherein the stack component is selected, based on a name of the interest or the object.

10. The non-transitory computer-readable storage medium of claim 8, wherein the selecting involves:

determining, from the stack requirement, a component requirement;

determining, from a component repository, a set of components that satisfies the component requirement; and

selecting, from the set of components, the stack component, which is compatible with other components in the protocol stack.

11. The non-transitory computer-readable storage medium of claim 8, further comprising:

searching for the stack component in a local repository; and

responsive to determining that the stack component is not available in the local repository, obtaining the stack component from a remote repository.

12. The non-transitory computer-readable storage medium of claim 11, wherein the remote repository includes one or more of:

a component cache;

a component storage server;

or

a component marketplace.

13. The non-transitory computer-readable storage medium of claim 8, further comprising:

determining that an updated version of the stack component exists;

determining a protocol stack in which the stack component is instantiated; and

replacing an instantiation of the stack component with an instantiation of the updated version of the stack component.

14. The non-transitory computer-readable storage medium of claim 13, further comprising:

analyzing the updated version of the stack component to obtain a stack requirement; and

responsive to determining that the stack requirement of the stack component has changed, updating an implementation of the protocol stack to satisfy a new stack requirement.

15. An apparatus comprising:

a communication interface;

a processor; and

a memory configured to store instructions executable by the processor,

wherein the processor is configured to;

receive an interest of an object in a network;

obtaining a stack requirement for a protocol stack, wherein the stack requirement specifies at least a functionality for a stack component;

select the stack component, based on the functionality and at least a name prefix of the interest or the object; and

instantiate the stack component in the protocol stack.

16. The apparatus of claim 15, wherein the processor is further configured to:

determine, from the stack requirement, a component requirement;

determine, from a component repository, a set of components that satisfies the component requirement; and

select, from the set of components, the stack component, which is compatible with other components in the protocol stack.

17. The apparatus of claim 15, wherein the processor is further configured to:

search for the stack component in a local repository; and

responsive to determining that the stack component is not available in the local repository, obtain the stack component from a remote repository.

18. The apparatus of claim 17, wherein the remote repository includes one or more of:

a component cache;

a component storage server;

or

a component marketplace.

19. The apparatus of claim 15, the processor is further configured to:

determine that an updated version of the stack component exists;

determine a protocol stack in which the stack component is instantiated; and

replace an instantiation of the stack component with an instantiation of the updated version of the stack component.

20. The apparatus of claim 19, the processor is further configured to:

analyze the updated version of the stack component to obtain a stack requirement; and

responsive to determining that the stack requirement of the stack component has changed, update an implementation of the protocol stack to satisfy a new stack requirement.