Hierarchical Delegation and Reservation of Lookup Keys

• US 20130031255A1
• Filed: 07/28/2011
• Published: 01/31/2013
• Est. Priority Date: 07/28/2011
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Maloy, Jon, Andersson, Per, Lynam, Jonathan
• Granted Patent: US 9,009,315 B2
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: H04L 61/3015 Name registration, generation or assignment
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]

Abstract

A method of reserving lookup keys in a computer communication system including a hierarchy of key manager nodes includes receiving a first reservation request at a first key manager node at a first level of the hierarchy of key manager nodes. The first reservation request requests reservation of a lookup key. The methods include determining whether or not the first key manager node has authority to grant the reservation request, and, in response to determining that the first key manager node does not have authority to grant the reservation request, sending a second reservation request requesting reservation of the lookup key to a second key manager node that is at a second level of the hierarchy of key manager nodes.

Claims

1. A method of reserving lookup keys in a computer communication system including a hierarchy of key manager nodes, the method comprising:

receiving a first reservation request at a first key manager node at a first level of the hierarchy of key manager nodes, the first reservation request requesting reservation of a lookup key;

determining whether or not the first key manager node has authority to grant the reservation request; and

in response to determining that the first key manager node does not have authority to grant the reservation request, sending a second reservation request requesting reservation of the lookup key to a second key manager node that is at a second level of the hierarchy of key manager nodes.

2. The method of claim 1, further comprising:

receiving a delegation of authority to grant the reservation request from the second key manager node; and

in response to receiving the delegation of authority, granting the reservation request.

3. The method of claim 1, further comprising:

in response to determining that the first key manager node has authority to grant the reservation request, granting the reservation request and sending a response to the reservation request confirming reservation of the lookup key.

4. The method of claim 1, wherein the first reservation request specifies a first range of lookup keys, and wherein the second reservation request specifies a second range of lookup keys that is greater than the first range of lookup keys.

5. The method of claim 4, further comprising:

receiving a delegation of authority from the second key manager node to reserve the second range of lookup keys; and

in response to receiving the delegation of authority, reserving the first range of lookup keys and sending a response to the reservation request confirming reservation of the first range of lookup keys.

6. The method of claim 5, wherein the delegation of authority includes authority to reserve a third range of lookup keys that includes the second range of lookup keys.

7. The method of claim 2, further comprising:

reporting reservation of the lookup key to a reservation supervisor node.

8. The method of claim 4, wherein the second range of lookup keys is at least twice as large as the first range of lookup keys.

9. The method of claim 7, wherein the second range of lookup keys is at least ten times as large as the first range of lookup keys.

10. The method of claim 1, wherein the second key manager node comprises a root key manager node, the method further comprising creating the lookup key at the root manager key node.

11. A key manager node, comprising:

a processor configured to receive a first reservation request from an application, the first reservation request requesting reservation of a lookup key, configured to determine whether or not the key manager node has authority to grant the reservation request, and in response to determining that the key manager node does not have authority to grant the reservation request, configured to send a second reservation request requesting reservation of the lookup key to a second key manager node that is at a higher level of a hierarchy of key manager nodes than the key manager node.

12. The key manager node of claim 11, wherein the processor is further configured to receive a delegation of authority to grant the reservation request from the second key manager node, and in response to receiving the delegation of authority, to grant the reservation request.

13. The key manager node of claim 11, wherein the processor is further configured to grant the reservation request and send a response to the reservation request confirming reservation of the lookup key in response to determining that the key manager node has authority to grant the reservation request.

14. The key manager node of claim 11, wherein the first reservation request specifies a first range of lookup keys, and wherein the second reservation request specifies a second range of lookup keys that is greater than the first range of lookup keys.

15. The key manager node of claim 14, wherein the processor is further configured to receive a delegation of authority from the second key manager node to reserve the second range of lookup keys, and in response to receiving the delegation of authority, to reserve the first range of lookup keys and send a response to the reservation request confirming reservation of the first range of lookup keys.

16. The key manager node of claim 15, wherein the delegation of authority includes authority to reserve a third range of lookup keys that includes the second range of lookup keys.

17. The key manager node of claim 12, wherein the processor is further configured to report reservation of the lookup key to a reservation supervisor node.

18. The key manager node of claim 14, wherein the second range of lookup keys is at least twice as large as the first range of lookup keys.

19. The key manager node of claim 17, wherein the second range of lookup keys is at least ten times as large as the first range of lookup keys.

20. A hierarchical key management system, comprising:

a plurality of key manager nodes arranged in a hierarchy including a root key manager node and a plurality of intermediate key manager nodes;

wherein each of the intermediate nodes is configured to receive a first reservation request from an application or a lower level key manager node, the first reservation request requesting reservation of a lookup key, configured to determine whether or not the intermediate key manager node has authority to grant the reservation request, and in response to determining that the intermediate key manager node does not have authority to grant the reservation request, configured to send a second reservation request requesting reservation of the lookup key to a second key manager node that is at a higher level of the hierarchy than the intermediate key manager node.