System and method for data transfer in a peer-to-peer hybrid communication network

• US 9,106,509 B2
• Filed: 07/03/2012
• Issued: 08/11/2015
• Est. Priority Date: 06/29/2004
• Status: Active Grant

• Current Assignee: Damaka, Inc.
• Original Assignee: Damaka, Inc.
• Inventors: Chaturvedi, Sivakumar, Gundabathula, Satish
• Primary Examiner(s): Shah, Chirag
• Assistant Examiner(s): SMITH, JOSHUA Y
• Application Number:
  US13/541,338
• Publication Number:
  US 20120269063A1
• Time in Patent Office: 1,134 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 1/08 by repeating transmission, e.g. Verdan system H04L1/1858 and H04L1/189 take precedence
• CPC Class Codes: H04L 1/1607 Details of the supervisory signal
• 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 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 63/102 Entity profiles
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1094 Inter-user-equipment sessions transfer or sharing
• CPC Class Codes: H04L 67/306 User profiles

Abstract

An improved system and method are disclosed for peer-to-peer communications. In one example, the method enables an endpoint to transfer data directly to another endpoint.

Claims

1. A method for transferring data from a first endpoint to a second endpoint, the method comprising:

sending, by the first endpoint, a plurality of packets to the second endpoint, wherein the sending includes, for each packet,

placing the packet on an unacknowledged (UNACK) list upon sending the packet to the second endpoint;

removing the packet from the UNACK list only if an acknowledgment (ACK) response from the second endpoint indicates that the packet was correctly received by the second endpoint; and

resending the packet without waiting for each of the plurality of packets to be sent if an UNACK response from the second endpoint indicates that the packet was not correctly received by the second endpoint;

and wherein the sending includes, for each packet on the UNACK list after each of the plurality of packets is sent a first time, resending all packets that appear on the UNACK list after sending each of the plurality of packets a first time, wherein the packets that appear on the UNACK list are resent even if no response is received for each of the packets that appear on the UNACK list from the second endpoint, and wherein a packet is removed from the UNACK list only if an ACK response is received for that packet, and wherein the step of resending all packets that appear on the UNACK list is repeated by the first endpoint until either the UNACK list is empty or a timeout occurs;

receiving, by the first endpoint, a plurality of out of sequence notifications that at least some of the plurality of packets were received out of sequence by the second endpoint, wherein the out of sequence notifications are not an ACK or an UNACK;

determining, by the first endpoint, that each of the out of sequence notifications was received within a certain period of time after sending the respective packet for which the out of sequence notification was received; and

recalculating, by the first endpoint, an inter-packet delay based on the plurality of out of sequence notifications only if a certain number of out of sequence notifications have been received from the second endpoint.

2. The method of claim 1 wherein the inter-packet delay is recalculated using a round trip time representing an amount of time that elapses between sending the packet for which the out of sequence notification was received and receiving the out of sequence notification for that packet.

3. The method of claim 1 further comprising receiving, by the first endpoint, a packet from the second endpoint indicating that the first endpoint should increase the rate at which the first endpoint is sending the plurality of packets to the second endpoint.

4. The method of claim 1 further comprising receiving, by the first endpoint, a packet from the second endpoint indicating that the first endpoint should decrease the rate at which the first endpoint is sending the plurality of packets to the second endpoint.

5. A first endpoint device comprising:

a hardware platform; and

an architecture having a graphical user interface (GUI) configured to provide user access to an endpoint engine, an operating system configured to provide access to the hardware platform, and the endpoint engine coupled to the GUI and the operating system, the endpoint engine having a plurality of functional components configured for;

sending a plurality of packets to a second endpoint device, wherein the sending includes, for each packet,

placing the packet on an unacknowledged (UNACK) list upon sending the packet to the second endpoint device;

removing the packet from the UNACK list only if an acknowledgment (ACK) response from the second endpoint device indicates that the packet was correctly received by the second endpoint device; and

resending the packet without waiting for each of the plurality of packets to be sent if an UNACK response from the second endpoint device indicates that the packet was not correctly received by the second endpoint device;

and wherein the sending includes, for each packet on the UNACK list after each of the plurality of packets is sent a first time, resending all packets that appear on the UNACK list after sending each of the plurality of packets a first time, wherein the packets that appear on the UNACK list are resent even if no response is received for each of the packets that appear on the UNACK list from the second endpoint device, and wherein a packet is removed from the UNACK list only if an ACK response is received for that packet, and wherein the step of resending all packets that appear on the UNACK list is repeated until either the UNACK list is empty or a timeout occurs;

receiving a plurality of notifications that at least some of the plurality of packets were received out of sequence by the second endpoint device, wherein the out of sequence notifications are not an ACK or an UNACK;

determining that each of the out of sequence notifications was received within a certain period of time after sending the respective packet for which the out of sequence notification was received; and

recalculating an inter-packet delay based on the plurality of out of sequence notifications only if a certain number of out of sequence notifications have been received from the second endpoint device.

6. The first endpoint device of claim 5 wherein the inter-packet delay is recalculated using a round trip time representing an amount of time that elapses between sending the packet for which the out of sequence notification was received and receiving the out of sequence notification for that packet.

7. The first endpoint device of claim 5 wherein the plurality of functional components are further configured for receiving a packet from the second endpoint device indicating that the first endpoint device should increase the rate at which the first endpoint device is sending the plurality of packets to the second endpoint device.

8. The first endpoint device of claim 5 wherein the plurality of functional components are further configured for receiving a packet from the second endpoint device indicating that the first endpoint device should decrease the rate at which the first endpoint device is sending the plurality of packets to the second endpoint device.

9. A method for transferring data from a first endpoint to a second endpoint in a peer-to-peer network, the method comprising:

retrieving, by the first endpoint, a profile and a routing table from an access server following an authentication process, wherein the profile indicates that the second endpoint is not available;

receiving, by the first endpoint, an online notification message directly from the second endpoint that the second endpoint is available, wherein the online notification message includes address information of the second endpoint needed by first endpoint to communicate directly with the second endpoint;

sending, by the first endpoint, a plurality of packets corresponding to a file to the second endpoint, wherein the sending includes, for each packet,

placing the packet on an unacknowledged (UNACK) list upon sending the packet to the second endpoint;

removing the packet from the UNACK list only if an acknowledgment (ACK) response from the second endpoint indicates that the packet was correctly received by the second endpoint; and

resending the packet without waiting for each of the plurality of packets to be sent if an UNACK response from the second endpoint indicates that the packet was not correctly received by the second endpoint;

and wherein the sending includes, for each packet on the UNACK list after each of the plurality of packets is sent a first time, resending all packets that appear on the UNACK list after sending each of the plurality of packets a first time, wherein the packets that appear on the UNACK list are resent even if no response is received for each of the packets that appear on the UNACK list from the second endpoint, and wherein a packet is removed from the UNACK list only if an ACK response is received for that packet, and wherein the step of resending all packets that appear on the UNACK list is repeated by the first endpoint until either the UNACK list is empty or a timeout occurs; and

determining, by the first endpoint, whether to recalculate an inter-packet delay based on a plurality of out of sequence notifications received from the second endpoint, wherein the first endpoint determines that each of the out of sequence notifications was received within a certain period of time after sending the respective packet for which the out of sequence notification was received; and

wherein the step of recalculating occurs only if a certain number of out of sequence notifications have been received from the second endpoint, and wherein the out of sequence notifications are not an ACK or an UNACK.

10. The method of claim 9 further comprising sending, from the first endpoint, a data transfer request message directly to the second endpoint.

11. The method of claim 9 further comprising establishing, by the first endpoint, a data transfer link directly with the second endpoint in order to send the plurality of packets corresponding to the file to the second endpoint.