System and method for dynamic stability in a peer-to-peer hybrid communications network

• US 20070165629A1
• Filed: 12/29/2006
• Published: 07/19/2007
• Est. Priority Date: 06/29/2004
• Status: Active Grant

• Current Assignee: Damaka, Inc.
• Original Assignee: Damaka, Inc.
• Inventors: Gundabathula, Satish, Chaturvedi, Sivakumar
• Granted Patent: US 7,778,187 B2
• Time in Patent Office: Days
• US Class Current: 370/389
• CPC Class Codes: H04L 12/56 Packet switching systems
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/54 Organization of routing tables
• CPC Class Codes: H04L 51/23 Reliability checks, e.g. acknowledgments or fault reporting
• CPC Class Codes: H04L 51/48 Message addressing, e.g. address format or anonymous messages, aliases
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• CPC Class Codes: H04L 61/2567 for reachability, e.g. inquiring the address of a correspondent behind a NAT server
• CPC Class Codes: H04L 61/2575 using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
• CPC Class Codes: H04L 61/2578 without involvement of the NAT server
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/029 Firewall traversal, e.g. tunnelling or, creating pinholes
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

An improved system and method are disclosed for peer-to-peer communications. In one example, the method provides for dynamic stability.

Claims

1. A method for use in a peer-to-peer hybrid network comprising:

retrieving a profile and a routing table from an access server by a first endpoint during an authentication process, wherein the profile identifies a second endpoint as an endpoint with which the first endpoint has permission to communicate, and the routing table contains address information needed for the first endpoint to communicate directly with the second endpoint;

sending a notification message from the first endpoint directly to the second endpoint using the address information to inform the second endpoint that the first endpoint is online;

determining that a failure has occurred in communicating with the second endpoint, wherein the access server cannot communicate with the second endpoint using the address information; and

sending a failure message from the access server to the first endpoint, wherein the failure message notifies the first endpoint that the second endpoint cannot be communicated with using the address information.

2. The method of claim 1 further comprising:

performing a re-authentication process with the access server by the second endpoint, wherein the re-authentication process updates the routing table on the access server with new address information needed to communicate directly with the second endpoint; and

sending a notification message from the second endpoint directly to the first endpoint to inform the first endpoint that the second endpoint is online and to update the routing table on the first endpoint with the new address information.

3. The method of claim 2 further comprising:

sending a STUN request from the second endpoint to the access server;

determining whether the address information has changed based on a response to the STUN request; and

performing the re-authentication process by the second endpoint only if the address information has changed.

4. The method of claim 1 further comprising performing a check on a network driver of the second endpoint to determine whether the network driver is functioning properly.

5. The method of claim 4 further comprising determining a cause of malfunction if the network driver is not functioning properly.

6. The method of claim 5 further comprising attempting to rectify the malfunction by executing a predefined process associated with the cause of malfunction.

7. The method of claim 1 further comprising sending a message from the second endpoint to a gateway positioned between the second endpoint and the access server and first endpoint to determine whether a link between the second endpoint and the gateway is functioning properly.

8. The method of claim 7 wherein the message is an ICMP ping.

9. The method of claim 1 further comprising sending a message from the second endpoint to the access server.

10. The method of claim 9 wherein the message is an ICMP ping.

11. The method of claim 9 further comprising resetting, by the access server, a “

keep alive”

flag corresponding to the second endpoint after receiving the message.

12. The method of claim 11 further comprising, if another message is not received by the access server from the second endpoint within a predefined period of time after resetting the keep alive flag, sending the failure message from the access server to the first endpoint.

13. The method of claim 1 wherein the failure message identifies a status of each endpoint with which the first endpoint has permission to communicate as failed or functional.

14. A method comprising:

sending a first authentication request from a first endpoint in a peer-to-peer hybrid network to an access server, wherein the first authentication request identifies network address information needed for the access server to communicate directly with the first endpoint;

sending the network address information directly to a second endpoint after being authenticated by the access server, wherein the second endpoint can communicate directly with the first endpoint using the network address information;

determining that an event has occurred that prevents the first endpoint from communicating with the access server or the second endpoint; and

rectifying the event to re-establish communications with the access server and second endpoint.

15. The method of claim 14 wherein rectifying the event includes:

sending a second authentication request from the first endpoint to the access server, wherein the second authentication request identifies new network address information needed for the access server to communicate directly with the first endpoint; and

sending the new network address information directly to the second endpoint after being authenticated by the access server, wherein the second endpoint can communicate directly with the first endpoint using the new network address information.

16. The method of claim 14 wherein determining that the event has occurred includes:

sending a STUN request from the first endpoint to the access server; and

determining whether a STUN response contains information different from the address information identified in the first authentication request.

17. The method of claim 14 wherein determining that the event has occurred includes:

pinging a gateway positioned between the first endpoint and the access server and second endpoint to determine whether a link between the first endpoint and the gateway is functioning properly; and

not getting a response from the gateway.

18. The method of claim 14 wherein determining that the event has occurred includes checking status information of a network driver of the first endpoint.

19. The method of claim 14 wherein determining that the event has occurred includes:

pinging the access server; and

not getting a response from the access server.

20. A system comprising:

an access server for a peer-to-peer hybrid network;

first and second endpoints coupled to each other and the access server via the peer-to-peer hybrid network; and

a plurality of instructions for execution by at least one of the first and second endpoints and access server, the instructions including instructions for;

retrieving a profile and a routing table from the access server by the first endpoint during an authentication process, wherein the profile identifies the second endpoint as an endpoint with which the first endpoint has permission to communicate, and the routing table contains address information needed for the first endpoint to communicate directly with the second endpoint;

sending a notification message from the first endpoint directly to the second endpoint using the address information to inform the second endpoint that the first endpoint is online;

determining that a failure has occurred in communicating with the second endpoint, wherein the access server cannot communicate with the second endpoint using the address information; and

sending a failure message from the access server to the first endpoint, wherein the failure message notifies the first endpoint that the second endpoint cannot be communicated with using the address information.