System and method for transferring a call between endpoints in a hybrid peer-to-peer network

• US 8,446,900 B2
• Filed: 06/18/2010
• Issued: 05/21/2013
• Est. Priority Date: 06/18/2010
• Status: Active Grant

• Current Assignee: Damaka, Inc.
• Original Assignee: Damaka, Inc.
• Inventors: Chaturvedi, Sivakumar R., Gundabathula, Satish
• Primary Examiner(s): Nawaz, Asad
• Assistant Examiner(s): Jensen, Nicholas A
• Application Number:
  US12/818,931
• Publication Number:
  US 20110310886A1
• Time in Patent Office: 1,068 Days
• Field of Search: 370/352, 379/208.01, 379/212.01, 379/218.02
• US Class Current: 370/352
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions

Abstract

An improved system and method are disclosed for peer-to-peer communications. In one example, the method enables an endpoint to move (e.g., transfer or forward) a call to another endpoint in a peer-to-peer environment.

Claims

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

receiving, by a peer-to-peer first endpoint, an instruction to transfer a call to a peer-to-peer second endpoint, wherein the first endpoint is engaged in the call with a peer-to-peer third endpoint when the instruction is received;

determining, by the first endpoint, whether the first endpoint has a buddy relationship with the second endpoint based on a profile obtained by the first endpoint from an access server when authenticating with the hybrid peer-to-peer network, wherein the first endpoint cannot transfer the call to the second endpoint unless the first and second endpoints have a buddy relationship because the buddy relationship is needed to provide permission by the second endpoint for the first endpoint to communicate with the second endpoint, and wherein the profile contains all information needed to communicate with the second endpoint if the first and second endpoints have a buddy relationship;

establishing, by the first endpoint, a buddy relationship with the second endpoint if the first and second endpoints are not in a buddy relationship, wherein establishing the buddy relationship includes;

communicating, by the first endpoint, with the access server in the hybrid peer-to-peer network to obtain address information for the second endpoint; and

sending, by the first endpoint, a request message for the buddy relationship to the second endpoint based on the address information obtained from the access server, wherein the request message identifies that the buddy relationship is to be temporary;

sending, by the first endpoint, at least one transfer message to the second endpoint to transfer the call, wherein the at least one transfer message indicates that the first endpoint wants to transfer the call to the second endpoint and identifies the third endpoint as being involved in the call, and wherein the transfer message contains all information needed by the second endpoint to accept the transfer from the first endpoint because the hybrid peer-to-peer network does not contain a central switching mechanism;

ending, by the first endpoint, the first endpoint'"'"'s involvement in the call after the call is transferred; and

sending, by the first endpoint, a message to the second endpoint to end the buddy relationship if the buddy relationship was established in order to transfer the call.

2. The method of claim 1 further comprising answering, by the first endpoint, the call before receiving the instruction to transfer the call.

3. The method of claim 1 wherein the call is not answered by the first endpoint before receiving the instruction to transfer the call.

4. The method of claim 1 further comprising determining, by the first endpoint, whether the second endpoint is online before sending the at least one transfer message to the second endpoint.

5. The method of claim 1 further comprising establishing, by the first endpoint, at least one communication route with the second endpoint, wherein the at least one communication route is established before sending the at least one transfer message.

6. A method for receiving a call transfer in a hybrid peer-to-peer network comprising:

receiving, by a peer-to-peer first endpoint, a request for a buddy relationship from a peer-to-peer second endpoint before receiving a transfer message from the second endpoint, wherein the transfer message cannot be received from the second endpoint unless the first and second endpoints have a buddy relationship;

receiving, by the first endpoint, the transfer message from the second endpoint requesting that the first endpoint accept a call transfer for a call in which the second endpoint is engaged with a peer-to-peer third endpoint, wherein the call transfer will engage the first endpoint in the call with the third endpoint;

accepting, by the first endpoint, the call transfer from the second endpoint;

determining, by the first endpoint, whether the first endpoint has a buddy relationship with the third endpoint based on a profile obtained by the first endpoint from an access server while authenticating with the hybrid peer-to-peer network, wherein the first endpoint cannot communicate with the third endpoint to aid in transferring the call unless the first endpoint and third endpoint have a buddy relationship because the buddy relationship is needed to provide permission by the third endpoint for the first endpoint to communicate with the third endpoint, and wherein the profile contains all information needed to communicate with the third endpoint if the first and third endpoints have a buddy relationship;

establishing, by the first endpoint, a buddy relationship with the third endpoint if the first and third endpoints are not in a buddy relationship, wherein establishing the buddy relationship includes;

communicating, by the first endpoint, with the access server in the hybrid peer-to-peer network to obtain address information for the third endpoint; and

sending, by the first endpoint, a request message for the buddy relationship to the third endpoint based on the address information obtained from the access server, wherein the request message identifies that the buddy relationship is to be temporary;

sending, by the first endpoint, at least one update message to the third endpoint to aid in transferring the call, wherein the at least one update message indicates that the third endpoint is to update its call information to include the first endpoint in the call;

ending, by the first endpoint, the buddy relationship with the second endpoint if the buddy relationship was established in order to transfer the call; and

engaging, by the first endpoint, in the call with the third endpoint.

7. The method of claim 6 further comprising determining, by the first endpoint, whether the third endpoint is online before sending the at least one update message to the third endpoint.

8. The method of claim 7 further comprising ending the call if the third endpoint is not online.

9. The method of claim 6 further comprising establishing, by the first endpoint, at least one communication route with the third endpoint, wherein the at least one communication route is established before sending the at least one update message.

10. A system comprising:

a network interface;

a processor coupled to the network interface; and

a memory coupled to the processor and containing a plurality of instructions for execution by the processor, the instructions including instructions for configuring a peer-to-peer first endpoint stored at least partially in the memory to transfer a call between the first endpoint and a peer-to-peer third endpoint from the first endpoint to a peer-to-peer second endpoint by;

receiving an instruction to transfer the call to the second endpoint;

determining whether the first endpoint has a buddy relationship with the second endpoint based on a profile obtained by the first endpoint from an access server when authenticating with the hybrid peer-to-peer network, wherein the first endpoint cannot transfer the call to the second endpoint unless the first and second endpoints have a buddy relationship because the buddy relationship is needed to provide permission by the second endpoint for the first endpoint to communicate with the second endpoint, and wherein the profile contains all information needed to communicate with the second endpoint if the first and second endpoints have a buddy relationship;

establishing a buddy relationship with the second endpoint if the first and second endpoints are not in a buddy relationship, wherein establishing the buddy relationship includes;

communicating, by the first endpoint, with the access server in the hybrid peer-to-peer network to obtain address information for the second endpoint; and

sending, by the first endpoint, a request message for the buddy relationship to the second endpoint based on the address information obtained from the access server, wherein the request message identifies that the buddy relationship is to be temporary;

sending at least one transfer message to the second endpoint to transfer the call, wherein the at least one transfer message indicates that the first endpoint wants to transfer the call to the second endpoint and identifies the third endpoint as being involved in the call, and wherein the transfer message contains all information needed by the second endpoint to accept the transfer from the first endpoint because the hybrid peer-to-peer network does not contain a central switching mechanism;

ending the first endpoint'"'"'s involvement in the call after the call is transferred; and

ending the buddy relationship with the second endpoint if the buddy relationship was established in order to transfer the call.

11. The system of claim 10 further comprising instructions for answering the call before receiving the instruction to transfer the call.