TRANSPORT STACK NAME SCHEME AND IDENTITY MANAGEMENT

• US 20160373390A1
• Filed: 06/22/2015
• Published: 12/22/2016
• Est. Priority Date: 06/22/2015
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Palo Alto Research Center, Inc. (Xerox Holdings Corp.)
• Inventors: Wood, Christopher A., Scott, Glenn C.
• Granted Patent: US 10,116,605 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/026 using e-messaging for transporting management information, e.g. email, instant messaging or chat
• CPC Class Codes: H04L 41/044 comprising hierarchical management structures
• CPC Class Codes: H04L 51/18 Commands or executable codes
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/321 Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
• CPC Class Codes: H04L 69/322 Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions

Abstract

An identity management and initialization scheme, along with a naming scheme for a transport stack and its components, facilitates directly addressing each component in the transport stack. During operation, the system receives, by a forwarder, a packet that corresponds to an interest, where the interest includes a name. In response to determining that the interest is destined for a component of a stack of communication modules, the forwarder sends the interest to the destined component based on the name for the interest, where the stack does not require a respective communication module to communicate only with a layer above or below thereof. In response to determining that the interest is not destined for a component of the stack, the forwarder sends the interest to a network element based on the name for the interest. This facilitates directly addressing individual components of the stack.

Claims

1. A computer-implemented method, comprising:

receiving, by a forwarder, a packet that corresponds to an interest, wherein the interest includes a name;

in response to determining that the interest is destined for a component of a stack of communication modules, sending the interest to the destined component based on the name for the interest, wherein the stack does not require a respective communication module to communicate only with a layer above or below thereof; and

in response to determining that the interest is not destined for a component of the stack, sending the interest to a network element based on the name for the interest,

thereby facilitating directly addressing individual components of the stack.

2. The method of claim 1, wherein the name for the interest includes one or more of:

a name for the stack;

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

a name for a component of the stack; and

a command associated with a component of the stack.

3. The method of claim 1, wherein a name for a component of the 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 stack;

a flat name that does not indicate any hierarchy;

a role of the component of the stack; and

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

4. The method of claim 1, wherein the interest includes a payload which includes a command associated with a component identified by the name for the interest.

5. The method of claim 1, wherein sending the interest to the destined component further comprises:

sending a message included in the interest to the destined component via a message delivery system based on the name for the interest.

6. The method of claim 1, further comprising:

receiving, from an application, a request to create a portal instance associated with the stack;

creating the portal instance based on application information included in the request; and

returning the portal instance to the application, wherein the portal instance indicates the stack, the forwarder associated with the stack, and each component of the stack.

7. The method of claim 6, wherein the application information includes one or more of:

a name for the portal instance; and

a nonce for the portal instance.

8. The method of claim 6, wherein creating the portal instance is further based on an identity and a private key of a creator of the portal instance, further comprising:

storing the private key of the creator in a verifier component of the 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:

receiving, by a forwarder, a packet that corresponds to an interest, wherein the interest includes a name;

in response to determining that the interest is destined for a component of a stack of communication modules, sending the interest to the destined component based on the name for the interest, wherein the stack does not require a respective communication module to communicate only with a layer above or below thereof; and

in response to determining that the interest is not destined for a component of the stack, sending the interest to a network element based on the name for the interest,

thereby facilitating directly addressing individual components of the stack.

10. The storage medium of claim 9, wherein the name for the interest includes one or more of:

a name for the stack;

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

a name for a component of the stack; and

a command associated with a component of the stack.

11. The storage medium of claim 9, wherein a name for a component of the 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 stack;

a flat name that does not indicate any hierarchy;

a role of the component of the stack; and

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

12. The storage medium of claim 9, wherein the interest includes a payload which includes a command associated with a component identified by the name for the interest.

13. The storage medium of claim 9, wherein sending the interest to the destined component further comprises:

sending a message included in the interest to the destined component via a message delivery system based on the name for the interest.

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

receiving, from an application, a request to create a portal instance associated with the stack;

creating the portal instance based on application information included in the request; and

returning the portal instance to the application, wherein the portal instance indicates the stack, the forwarder associated with the stack, and each component of the stack.

15. The storage medium of claim 14, wherein the application information includes one or more of:

a name for the portal instance; and

a nonce for the portal instance.

16. The storage medium of claim 14, wherein creating the portal instance is further based on an identity and a private key of a creator of the portal instance, and wherein the method further comprises:

storing the private key of the creator in a verifier component of the 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;

receiving, by a forwarder, a packet that corresponds to an interest, wherein the interest includes a name;

in response to determining that the interest is destined for a component of a stack of communication modules, sending the interest to the destined component based on the name for the interest, wherein the stack does not require a respective communication module to communicate only with a layer above or below thereof; and

in response to determining that the interest is not destined for a component of the stack, sending the interest to a network element based on the name for the interest,

thereby facilitating directly addressing individual components of the stack.

18. The computer system of claim 17, wherein the name for the interest includes one or more of:

a name for the stack;

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

a name for a component of the stack; and

a command associated with a component of the stack.

19. The computer system of claim 17, wherein a name for a component of the 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 stack;

a flat name that does not indicate any hierarchy;

a role of the component of the stack; and

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

20. The computer system of claim 17, wherein the interest includes a payload which includes a command associated with a component identified by the name for the interest.

21. The computer system of claim 17, wherein sending the interest to the destined component further comprises:

sending a message included in the interest to the destined component via a message delivery system based on the name for the interest.

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

receiving, from an application, a request to create a portal instance associated with the stack;

creating the portal instance based on application information included in the request; and

returning the portal instance to the application, wherein the portal instance indicates the stack, the forwarder associated with the stack, and each component of the stack.

23. The computer system of claim 22, wherein the application information includes one or more of:

a name for the portal instance; and

a nonce for the portal instance.

24. The computer system of claim 22, wherein creating the portal instance is further based on an identity and a private key of a creator of the portal instance, and wherein the method further comprises:

storing the private key of the creator in a verifier component of the stack.