SYSTEM AND METHOD FOR CONCURRENT SESSIONS IN A PEER-TO-PEER HYBRID COMMUNICATIONS NETWORK

• US 20120005723A1
• Filed: 09/15/2011
• Published: 01/05/2012
• Est. Priority Date: 06/29/2004
• Status: Active Grant

• Current Assignee: Damaka, Inc.
• Original Assignee: Damaka, Inc.
• Inventors: CHATURVEDI, SIVAKUMAR, GUNDABATHULA, SATISH
• Granted Patent: US 8,432,917 B2
• Time in Patent Office: Days
• US Class Current: 726/1
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks

Abstract

An improved system and method are disclosed for peer-to-peer communications. In one example, the method provides for concurrent sessions to be maintained by multiple endpoints.

Claims

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

performing, by the first endpoint, an authentication process with an access server to gain access to network information needed to communicate within the peer-to-peer hybrid network, wherein the authentication process presents unique user authentication information by the first endpoint to the access server and associates the first endpoint with the unique user authentication information within the network;

receiving, by the first endpoint, a profile and a routing table from the access server in response to the authentication process, wherein the profile is uniquely associated with the unique user authentication information by the access server, and wherein the profile identifies second and third endpoints as endpoints with which the first endpoint has permission to communicate and identifies a status of the second and third endpoints as online, and the routing table contains first address information needed for the first endpoint to communicate directly with the second endpoint and second address information needed for the first endpoint to communicate directly with the third endpoint;

determining, by the first endpoint, that the unique user authentication information is concurrently associated with the second endpoint, whereby the second endpoint previously presented the unique user authentication information to the access server in order to log in to the network;

identifying, by the first endpoint, the first endpoint as a master endpoint corresponding to the unique user authentication information and the second endpoint as a slave endpoint corresponding to the unique user authentication information;

sending, by the first endpoint, a first message directly to the second endpoint to notify the second endpoint that the first endpoint is logged into the network using the unique user authentication information and that the first endpoint is the master endpoint; and

sending, by the first endpoint, a second message directly to the third endpoint to notify the third endpoint that the first endpoint is logged into the network and that communications sent from the third endpoint to a user of the first and second endpoints should be sent to the first endpoint only.

2. The method of claim 1 wherein the profile further identifies a fourth endpoint and identifies a status of the fourth endpoint as offline, and wherein the routing table contains no address information for the fourth endpoint when received by the first endpoint.

3. The method of claim 2 further comprising:

receiving, by the first endpoint, a notification message directly from the fourth endpoint that the fourth endpoint is now online, wherein the notification message includes third address information needed for the first endpoint to communicate directly with the fourth endpoint; and

updating, by the first endpoint, the status of the third endpoint in the profile stored on the first endpoint from offline to online.

4. The method of claim 1 further comprising:

identifying, by the first endpoint, a status of the first endpoint as away, wherein the status of the first endpoint is available to both the second and third endpoints;

identifying, by the first endpoint, a status of the second endpoint as active, wherein the status of the second endpoint is available only to the first endpoint and not the third endpoint because the first endpoint shares the unique user authentication information of the second endpoint and the third endpoint does not; and

sending, by the first endpoint, a third message directly to the third endpoint, wherein the third message identifies a status of the first endpoint as online to the third endpoint based on the active status of the second endpoint even though the first endpoint has a status of away.

5. The method of claim 1 further comprising:

receiving, by the first endpoint, a third message from the third endpoint via the network;

identifying, by the first endpoint, source information from the third message, wherein the source information identifies the third endpoint as the source of the third message;

determining, by the first endpoint, whether to apply a first policy or a second policy to the third message based on the source information, wherein the first policy is a custom policy to be applied to messages received from the third endpoint and the second policy is a default policy to be applied to messages received from an endpoint not having a corresponding custom policy; and

determining, by the first endpoint, that the first policy is to be applied to the third message.

6. The method of claim 5 further comprising:

determining, by the first endpoint, that the first policy requires that the third message be forwarded to the second endpoint; and

forwarding, by the first endpoint, the third message to the second endpoint.

7. The method of claim 5 further comprising:

determining, by the first endpoint, that the third message indicates an incoming call session from the third endpoint;

determining, by the first endpoint, that the first policy requires that the incoming call session be connected to a telephone number defined in the first policy; and

connecting, by the first endpoint, the incoming call session with the telephone number, wherein the first endpoint bridges the call session between the third endpoint and the telephone number.

8. The method of claim 5 wherein a plurality of endpoints including the first and second endpoints are logged into the network using the same unique user authentication as the first endpoint, the method further comprising:

identifying, by the first endpoint, an active endpoint of the plurality of endpoints; and

forwarding, by the first endpoint, the third message to the active endpoint.

9. The method of claim 8 wherein identifying the active endpoint occurs only when there is no forwarding destination defined in the first policy.

10. The method of claim 8 wherein identifying the active endpoint includes identifying an endpoint of the plurality of endpoints that exhibits the most recent activity.

11. The method of claim 8 wherein identifying the active endpoint includes simultaneously requesting a call session with each of the plurality of endpoints, the method further comprising instructing all simultaneously contacted endpoints except the active endpoint to disconnect once the active endpoint responds to the call session request.

12. The method of claim 8 wherein identifying the active endpoint includes attempting to contact each of the plurality of endpoints in turn until a response is received.

13. The method of claim 1 further comprising:

receiving, by the first endpoint, a notification message directly from a fourth endpoint that the fourth endpoint is now online, wherein the notification message includes third address information needed for the first endpoint to communicate directly with the fourth endpoint, and wherein the profile received from the access server in response to the authentication process identified the fourth endpoint and identified a status of the fourth endpoint as offline, and wherein the routing table contained no address information for the fourth endpoint when received by the first endpoint;

updating, by the first endpoint, the status of the fourth endpoint in the profile stored on the first endpoint from offline to online; and

determining, by the first endpoint, that the unique user authentication information is concurrently associated with the fourth endpoint.

14. The method of claim 13 further comprising identifying, by the first endpoint, the first endpoint as a slave endpoint corresponding to the unique user authentication information and the fourth endpoint as a master endpoint corresponding to the unique user authentication information.

15. The method of claim 13 further comprising identifying, by the first endpoint, the first endpoint as the master endpoint corresponding to the unique user authentication information and the fourth endpoint as a slave endpoint corresponding to the unique user authentication information.

16. The method of claim 15 further comprising notifying, by the first endpoint, the second endpoint that the fourth endpoint has logged onto the network.

17. A method for applying a policy in a hybrid peer-to-peer network comprising:

logging, by a first endpoint, into the network by presenting unique user authentication information by the first endpoint to the network, wherein the login associates the first endpoint with the unique user authentication information required for authentication with the network;

determining, by the first endpoint, that a second endpoint is not currently logged into the network and a third endpoint is logged into the network using unique user authentication information different from the unique user authentication information of the first endpoint;

sending, by the first endpoint, a first message directly from the first endpoint to the third endpoint to notify the third endpoint that the first endpoint is logged into the network;

receiving, by the first endpoint, a second message directly from the second endpoint that the second endpoint has logged into the network using the same unique user authentication information as the first endpoint, wherein the first and second endpoints represent a single user in the network;

receiving, by the first endpoint, a third message directly from one of the second and third endpoints;

determining, by the first endpoint, whether the third message is received from the second endpoint that has been authenticated with the network by presenting the unique user authentication information of the first endpoint to the network or from the third endpoint that is authenticated with the network using unique user authentication information different from the unique user authentication information of the first endpoint; and

applying a policy based on whether the third message is from the second endpoint or the third endpoint.

18. The method of claim 17 further comprising:

determining, by the first endpoint, whether the second endpoint has logged into the network as a slave endpoint or a master endpoint; and

setting, by the first endpoint, a status of the first endpoint as a slave endpoint if the second endpoint has logged into the network as a master endpoint.

19. The method of claim 17 further comprising determining whether a custom policy is associated with the third endpoint if the third message is from the third endpoint, wherein the custom policy defines a behavior of the first endpoint with respect to messages received from the third endpoint.

20. The method of claim 19 wherein the custom policy defines a forwarding destination for the third message, and wherein the forwarding destination is defined in the custom policy as a most recently active endpoint of the first and second endpoints.