Method of distributed hash table node ID collision detection

• US 20070233832A1
• Filed: 03/30/2006
• Published: 10/04/2007
• Est. Priority Date: 03/30/2006
• Status: Abandoned Application

• Current Assignee: Panasonic Corporation (Panasonic Holdings Corporation)
• Original Assignee: Matsushita Electric Industrial Company Limited (Panasonic Holdings Corporation)
• Inventors: Narayanan, Sathya, Shim, Eunsoo, Braun, David
• Application Number:
  US11/393,463
• Publication Number:
  US 20070233832A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1046 Joining mechanisms
• CPC Class Codes: H04L 67/1065 Discovery involving distributed pre-established resource-based relationships among peers, e.g. based on distributed hash tables [DHT] pre-configuration of logical or physical connections H04L67/1053

Abstract

A method for joining a network resource as a joining node to a peer-to-peer network includes establishing a node ID for the joining node to be joined to the peer-to-peer network, routing the join message to an assignment node that manages resources with resource IDs closest to the node ID of the joining node, determining whether or not the node ID established is identical to respective ones of the node IDs on the peer-to-peer network, and joining the joining node to the peer-to-peer network, when the node ID of the joining node is not identical to any one of the node IDs on the peer-to-peer network.

Claims

1. A method for joining a network resource, as a joining node, to a peer-to-peer network, comprising the steps of:

a) establishing a node ID for the joining node to be joined to the peer-to-peer network;

b) routing a message to an assignment node that manages resources with resource IDs closest to the node ID of the joining node;

c) determining whether the node ID established in step (a) is identical to one of the node IDs on the peer-to-peer network; and

d) joining the joining node to the peer-to-peer network when the node ID of the joining node is not identical to any one of the node IDs managed by the assignment node.

2. The method according to claim 1, wherein step (c) of determining whether or not the node ID for the joining node is identical to the one of the node IDs on the peer-to-peer network includes

comparing the node IDs managed by the assignment node to the node ID of the joining node, and

sending a join message from the assignment node to the joining node to enable joining of the joining node to the peer-to-peer network when none of the node IDs managed by the assignment node matches the node ID of the joining node.

3. The method according to claim 1, wherein step (c) of determining whether the node ID for the joining node is identical to the one of the node IDs on the peer-to-peer network includes comparing the node IDs managed by the assignment node to the node ID of the joining node, and the method further comprises the step of

e) sending an other message from the assignment node to the joining node indicating a node ID collision when one of the node IDs managed by the assignment node matches the node ID of the joining node.

4. The method according to claim 1, wherein step (c) of determining whether the node ID for the joining node is identical to the one of the node IDs on the peer-to-peer network includes

comparing the node IDs managed by the assignment node to the node ID of the joining node and identifying as a colliding node a node having a node ID managed by the assignment node that matches the node ID of the joining node;

routing the message from the assignment node to the colliding node; and

the method further comprising the step of

e) sending an other message to the joining node indicating a node ID collision when the colliding node responds to the message from the assignment node.

5. The method according to claim 4, wherein the message routed to the assignment node is a join message and the other message sent to the joining node is an error message indicating the node ID collision.

6. The method according to claim 4, wherein the message routed to the assignment node is a lookup message and the other message sent to the joining node is a lookup success message indicating that a node with a node ID identical to the node ID of the joining node has been identified.

7. The method according to claim 4, further comprising the step of:

f) responsive to reception of the other message, establishing a node ID for the joining node, which is different from any other node ID previously used to join the joining node to the peer-to-peer network by changing the one or more components of the node ID that are independent of the joining node; and

g) repeating steps (b) through (d) using the different node ID to join the joining node to the peer-to-peer network.

8. The method according to claim 4, further comprising the steps of:

g) determining a number of error messages indicating node ID collisions received by the joining node; and

h) preventing the joining node from joining the peer-to-peer network, when the number of error messages determined in step (g) is more than a predetermined threshold number.

24. A computer readable medium including software that is configured to control joining of the joining node to the peer-to-peer network by implementing a method according to claim 1.

25. A computer readable medium including software that is configured to control joining of the joining node to the peer-to-peer network by implementing a method according to claim 8.

9. A method for joining a network resource as a joining node to a peer-to-peer network, comprising the steps of:

a) establishing a node ID for the joining node to be joined to the peer-to-peer network based on one or more components related to the joining node and one or more components independent of the joining node;

b) routing the join message to a node that manages resources with resource IDs closest to the node ID of the joining node; and

c) joining the joining node to the peer-to-peer network when the node ID of the joining node is not identical to any one of the node IDs managed by the node that manages the resources with the resource IDs closest to the node ID of the joining node.

10. The method according to claim 9, wherein step (a) of the establishing the node ID includes the steps of:

determining an IP address of the joining node; and

using the IP address of the joining node to derive the component related to the joining node.

11. The method according to claim 9, wherein step (a) of the establishing the node ID includes the steps of:

determining a port number of the joining node; and

using the IP address and the port number of the joining node to derive the component related to the joining node.

12. The method according to claim 9, wherein step (a) of the establishing the node ID includes the steps of:

generating a random bit stream; and

using the random bit stream to derive the component independent of the joining node.

13. The method according to claim 12, wherein step (a) of the establishing the node ID includes the steps of:

applying a hash function to a value that is a combination of an IP address of the joining node, a port number of the joining node and the random bit stream to generate the node ID.

14. The method according to claim 12, wherein the step of generating the random bit stream includes

providing the random bit stream having a sufficient length based on an overall number of node IDs on the peer-to-peer network to ensure a unique node ID with a probability of 99% or greater.

15. A method for joining a network resource as a joining node to a peer-to-peer network, comprising the steps of:

a) establishing a node ID for the joining node based on one or more components which are related to the joining node and one or more components which are independent of the joining node;

b) sending a message including the node ID from the joining node to one or more other nodes;

c) routing the join message to an assignment node that manages resources with resource IDs closest to the node ID of the joining node;

d) determining whether or not the node ID established in step (a) is identical to one node ID managed by the assignment node; and

e) joining the joining node to the peer-to-peer network, when the node ID of the joining node is not identical to any of the node IDs managed by the assignment node.

16. The method according to claim 15, wherein the components which are related to the joining node include at least an IP address and a port number of the joining node.

17. The method according to claim 16, wherein the components independent of the joining node include a random bit stream.

18. The method according to claim 17, wherein the node ID of the joining node is a hash value of a concatenation of the IP address of the joining node, the port number of the joining node and the random bit stream.

19. The method according to claim 15, further comprising the step of:

f) sending an other message to the joining node indicating a node ID collision when one of the node IDs managed by the assignment node matches the node ID of the joining node.

20. The method according to claim 19, further comprising the steps of:

g) responsive to reception of the other message by the joining node in step (f), establishing a node ID for the joining node, which is different from other node IDs previously used to join the joining node to the peer-to-peer network by changing the one or more components that are independent of the joining node; and

h) repeating steps (b) through (g) using the different node ID to join the joining node to the peer-to-peer network.

21. The method according to claim 19, wherein:

step (d) of determining whether or not the node ID of the joining node is identical to one of node ID managed by the assignment node includes the step of routing the join message from the assignment node to a colliding node having a node ID that matches the node ID of the joining node, and

step (f) of sending the other message to the joining node indicating the node ID collision includes the step of sending the other message from the colliding node to the joining node indicating the node ID collision.

22. The method according to claim 20, wherein the other message sent to the joining node is one of an error message indicating the node ID collision or a lookup success message indicating that a node with an identical node ID to that of the joining node has been identified.

23. The method according to claim 22, further comprising the steps of:

g) determining a number of the error messages or the lookup success messages indicating node ID collisions that have been received by the joining node; and

h) preventing the joining node from joining the peer-to-peer network, when the number of the error messages or the lookup success messages determined in step (g) is more than a predetermined threshold number.