System and method for improving internet communication by using intermediate nodes

• US 10,440,146 B2
• Filed: 12/10/2018
• Issued: 10/08/2019
• Est. Priority Date: 08/28/2013
• 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): Scott, Randy A
• Application Number:
  US16/214,451
• Publication Number:
  US 20190116243A1
• Time in Patent Office: 302 Days
• Field of Search: 709218, 709226, 709227, 709228, 709231
• CPC Class Codes: H04L 43/0864 Round trip delays
• CPC Class Codes: H04L 63/029 Firewall traversal, e.g. tunnelling or, creating pinholes
• CPC Class Codes: H04L 63/0407 wherein the identity of one or more communicating identities is hidden cryptographic mechanisms or cryptographic arrangements for anonymous credentials or for identity based cryptographic systems H04L9/00
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers
• CPC Class Codes: H04L 67/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70
• CPC Class Codes: H04N 21/4622 Retrieving content or additional data from different sources, e.g. from a broadcast channel and the Internet web site content organization and management for information retrieval from the Internet G06F16/958; transmission by internet of broadcast information H04H60/82; stock exchange data over packet-switching network H04L12/1804; push services including data channel over packet-switching network H04L12/1859
• CPC Class Codes: H04W 4/029 Location-based management or tracking services

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

Claims

1. A method for fetching over the Internet a first content identified by a first content identifier and stored in a second server, by a first device identified in the Internet by a first identifier, for use with a second device identified in the Internet by a second identifier, for use with a third device identified in the Internet by a third identifier, for use with a second content identified by a second content identifier and stored in a third server, and for use with a first server, the method comprising the steps of:

sending, by the second device, the second identifier to the first server;

receiving and storing, by the first server, the second identifier;

sending, by the first device, the first content identifier to the first server;

receiving, by the first server, the first content identifier;

sending, by the second device, the first content identifier to the second server;

receiving, by the second device, the first content from the second server;

receiving, by the first device, the first content;

sending, by the third device, the third identifier to the first server;

receiving and storing, by the first server, the third identifier;

sending, by the first device, the second content identifier to the first server;

receiving, by the first server, the second content identifier;

sending, by the third device, the second content identifier to the third server;

receiving, by the third device, the second content from the third server; and

receiving, by the first device, the second content in response to the receiving, by the third device, of the second content from the third server,

wherein the second device is a portable device that stores, operates, or uses, a mobile operating system.

2. The method according to claim 1, wherein the steps are sequentially executed.

3. The method according to claim 1, wherein at least two steps are concurrently executed using multitasking or multiprocessing.

4. The method according to claim 1, wherein the sending, by the second device, of the first content identifier to the second server is in response to the receiving and storing, by the first server, of the second identifier and in response to the receiving, by the first server, of the first content identifier.

5. The method according to claim 1, wherein the receiving, by the first device, of the first content is in response to the receiving, by the second device, of the first content from the second server.

6. The method according to claim 1, wherein the receiving, by the first device, of the first content comprises receiving, by the first device, the first content from the second device.

7. The method according to claim 1, further comprising receiving the second identifier from the first server.

8. The method according to claim 7, wherein the receiving the second identifier from the first server is performed by the first device.

9. The method according to claim 1, further comprising sending, by the first device, the first identifier to the first server;

and receiving and storing, by the first server, the first identifier.

10. The method according to claim 1, wherein the second and third servers are the same server.

11. The method according to claim 1, for use with a group that includes a plurality of devices, each device in the group is identified in the Internet using a respective identifier, and for use with a second content identified by a second content identifier and stored in a third server, the method further comprising the steps of:

sending, by each of the devices in the group, the respective identifier to the first server;

receiving and storing, by the first server, the identifiers of the devices in the group;

sending, by the first device, the second content identifier to the first server;

receiving, by the first server, the first content identifier;

sending, by a third device selected from the group, the second content identifier to the third server;

receiving, by the third device, the second content from the third server; and

receiving, by the first device, the second content,

wherein each of the devices in the group is a portable device that stores, operates, or uses, a mobile operating system.

12. The method according to claim 11, wherein the receiving, by the first device, of the second content is in response to the receiving, by the third device, of the second content from the third server.

13. The method according to claim 11, further comprising the step of selecting the third device out of the devices in the group.

14. The method according to claim 13, wherein the third device is randomly selected out of the devices in the group.

15. The method according to claim 13, wherein the third device is selected based on an attribute or a characteristic of the third device.

16. The method according to claim 13, wherein the third device is selected based on a physical geographical location of the third device.

17. The method according to claim 16, wherein the third device is selected based on a physical geographical proximity to the third server.

18. The method according to claim 16, wherein the third device is selected based on the value of the third identifier, wherein the third device is selected based on past activities, or wherein the third device is selected based on a timing of an event.

19. The method according to claim 1, wherein each of the identifiers is an IP address that is in IPv4 or IPv6 form or a URL.

20. The method according to claim 1, wherein the first or second server a is a web server using HyperText Transfer Protocol (HTTP) that responds to HTTP requests via the Internet, and wherein the communication of the first or second device with the first or second server is based on, or using, HTTP persistent connection.

21. The method according to claim 1, wherein the communication over the Internet with the first device, the second device, the first server, or the second server, is based on, or according to, TCP/IP protocol or connection.

22. The method according to claim 1, further comprising establishing a connection with the first device or the second device using TCP, and wherein the connection is established by performing ‘

Active OPEN’

or ‘

Passive OPEN’

.

23. The method according to claim 1, wherein the first or second device is communicating over the Internet using a VPN.

24. The method according to claim 1, wherein the first content includes, consists of, or comprises, a part or whole of files, text, numbers, audio, voice, multimedia, video, images, music, or computer program, or wherein the first content includes, consists of, or comprises, a part of, or a whole of, a web-site page.

25. The method according to claim 1, wherein at least the first server or the second server is storing, operating, or using, a server operating system.

26. The method according to claim 25, wherein the server operating system consists or, comprises of, or based on, one out of Microsoft Windows Server®

, Linux, or UNIX.

27. The method according to claim 25, wherein the server operating system consists or, comprises of, or based on, one out of Microsoft Windows Server®

2003 R2, 2008, 2008 R2, 2012, or 2012 R2 variant, Linux™

or GNU/Linux based Debian GNU/Linux, Debian GNU/kFreeBSD, Debian GNU/Hurd, Fedora™

, Gentoo™

, Linspire™

, Mandriva, Red Hat®

Linux, SuSE, and Ubuntu®

, UNIX®

variant Solaris™

, AIX®

, Mac™

OS X, FreeBSD®

, OpenBSD, and NetBSD®

.

28. The method according to claim 1, wherein the second device is a cellular telephone device, and wherein the mobile operating system is one out of Android version 2.2 (Froyo), Android version 2.3 (Gingerbread), Android version 4.0 (Ice Cream Sandwich), Android Version 4.2 (Jelly Bean), Android version 4.4 (KitKat), Apple iOS version 3, Apple iOS version 4, Apple iOS version 5, Apple iOS version 6, Apple iOS version 7, Microsoft Windows®

Phone version 7, Microsoft Windows®

Phone version 8, Microsoft Windows®

Phone version 9, and Blackberry®

operating system.