System providing faster and more efficient data communication

• US 10,805,429 B1
• Filed: 06/24/2020
• Issued: 10/13/2020
• Est. Priority Date: 10/08/2009
• Status: Active Grant

• Current Assignee: Bright Data, Ltd. (f/k/a Luminati Networks)
• Original Assignee: Bright Data, Ltd. (f/k/a Luminati Networks)
• Inventors: Shribman, Derry, Vilenski, Ofer
• Primary Examiner(s): Nguyen, Minh Chau
• Application Number:
  US16/910,863
• Publication Number:
  US 20200322457A1
• Time in Patent Office: 111 Days
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/1063 Discovery through centralising entities
• CPC Class Codes: H04L 67/108 characterised by resources being split in blocks or fragments
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

Claims

1. A method for fetching a content by a requesting client device from a web server, the content comprises multiple parts where each part is identified by a distinct Uniform Resource Locator (URL), for use with a plurality of client devices each identified by a distinct IP address and associated with the geographical location, and for use with a first server that is distinct from the web server, the method comprising:

Identifying, by the requesting client device, the multiple parts;

sending, by the requesting client device, to the first server over the Internet, the URLs of the multiple parts and a geographical location;

sending, for each one of the multiple parts, by the first server, the respective URL of the part to a distinct client device from the plurality of client devices;

fetching, by the first server, the multiple parts from the web server in response to the receiving of the sent URLs;

sending, by the first server, the content to the requesting client device in response to the receiving of the multiple parts; and

receiving, by the requesting client device, over the Internet in response to the sending and the geographical location, from the first server, the content.

2. The method according to claim 1, for use with a group of client devices that includes the plurality of client devices, the method further comprising selecting the plurality of client devices from the group based on being associated with, or being located in, the geographical location.

3. The method according to claim 2, wherein the selecting is based on a response time.

4. The method according to claim 3, wherein the selecting is based on being the quickest to respond to queries.

5. The method according to claim 2, wherein the selecting is by the first server.

6. The method according to claim 2, wherein the selecting is by the requesting client device.

7. The method according to claim 2, for use with a list of IP addresses of the devices in the group, and wherein the selecting comprises selecting the IP addresses of the multiple device from the list.

8. The method according to claim 1, wherein the requesting client device is identified by an Internet Protocol (IP) address, Media Access Control (MAC) address, or a hostname, and wherein the method further comprising sending, by the requesting client device, during, as part of, or in response to, a start-up of the requesting client device, a message to the first server that comprises the IP address, the MAC address, or the hostname.

9. The method according to claim 8, for use with a first application stored in the requesting client device and associated with a first version number, wherein the sending comprises sending the first version number.

10. The method according to claim 9, for use with a second application that is a version of the first application and is stored in the first server and associated with a second version number, wherein the method further comprising receiving, by the requesting client device from the first server, in response to the message, the second version number.

11. The method according to claim 1, further comprising, for each one of the multiple parts, receiving, by the first server, the multiple parts from the plurality of client devices.

12. The method according to claim 11, further comprising, by the first server, forming the content from the received multiple parts.

13. The method according to claim 1, further comprising periodically communicating between the first server and the requesting client device.

14. The method according to claim 13, wherein the periodically communicating comprises exchanging ‘

keep alive’

messages.

15. The method according to claim 1, wherein each of the multiple parts consists of, or comprises, a web-page or a portion thereof.

16. The method according to claim 15, wherein each of the multiple parts consists of, or comprises, an HTML object of a web-page.

17. The method according to claim 1, further comprising executing, by the requesting client device, an application.

18. The method according to claim 17, wherein the identifying comprises intercepting, by a driver in the requesting client device, the request for the content respectively from the application.

19. The method according to claim 1, wherein the web server is a publicly-accessed Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS) server that respectively responds to HTTP or HTTPS requests.

20. The method according to claim 1, wherein the sending comprises sending of a HTTP or HTTPS requests for the multiple parts.

21. The method according to claim 1, further comprising establishing, by the requesting client device, a Transmission Control Protocol (TCP) connection with the first server using TCP/IP protocol.

22. The method according to claim 1, wherein the requesting client device comprises a wireless modem for Radio-Frequency (RF) communication, and wherein the sending and the receiving is using the RF communication.

23. The method according to claim 1, wherein the requesting client device communicates over the Internet based on, or according to, one out of UDP, DNS, FTP, POP #, SMTP, or SQL standards.

24. The method according to claim 1, wherein the content comprises a web-page, a web-site, audio data, or video data.

25. The method according to claim 1, wherein the content is identified over the Internet using a distinct URL.

26. The method according to claim 1, wherein the application comprises a web/Internet browser application or an email application.

27. The method according to claim 1, further comprising storing, by the requesting client device, the received content;

and sending a communication port number to the first server, wherein the communication with the first server is using the communication port number.

28. The method according to claim 1, further comprising determining that the received content, or part thereof, is valid, and wherein the determining is based on a received HTTP header that is according to, or based on, IETF RFC 2616.