# US 2020/0351378 A1 · System and Method for Improving Internet Communication by Using Intermediate Nodes

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0351378 A1
- Document ID: US20200351378A1
- Status: Published application
- Kind: A1
- Application number: 16/932,764
- Filed: 2020-07-19
- Published: 2020-11-05
- Earliest claimed: 2013-08-28
- Assignees: Luminati Networks Ltd.
- Applicants: Luminati Networks Ltd.
- Inventors: Derry Shribman; Ofer Vilenski
- Web page: https://patentgrep.com/patent/US20200351378A1

## CPC

- 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)
- G06Q 40/08: Insurance
- G06Q 50/16: Real estate
- H04L 43/0864: Round trip delays
- H04L 51/02: using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages
- H04L 61/5007: Internet protocol [IP] addresses
- H04L 63/029: {Firewall traversal, e.g. tunnelling or, creating pinholes}
- 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)}
- H04L 65/612: for unicast
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L 67/567: Integrating service provisioning from a plurality of service providers
- H04L 67/59: Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
- G05B 2219/2642: Domotique, domestic, home control, automation, smart house
- G08B 21/043: {detecting an emergency event, e.g. a fall}
- H04L 12/2803: {Home automation networks}
- H04L 67/52: specially adapted for the location of the user terminal
- H04L 2101/659: Internet protocol version 6 [IPv6] addresses
- 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)}
- H04W 4/029: Location-based management or tracking services
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G05B: CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS (systems for controlling or regulating non-electric variables G05D; systems for regulating electric or magnetic variables G05F; control devices or systems insofar as characterised by mechanical features only G05G)
- G08B: SIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## 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

### Claim 1

A method for anonymously fetching by a first device a content from a web server that stores a publicly-accessed web-site that includes at least first and second web-pages that are respectively identified by first and second Uniform Resource Locators (URLs), for use with a group of client devices that includes distinct first and second client devices that are identified in the Internet by a respective first and second Internet-Protocol (IP) addresses, the method comprising:
receiving, by a first server from the first device, the first and second URLs;
selecting, by the first server in response to the receiving, the first and second client devices;
sending, by the first server to the first client device, using the IP address of the first client device, a first HyperText Transfer Protocol (HTTP) request for the first URL;
sending, by the first server to the second client device, using the IP address of the second client device, a second HyperText Transfer Protocol (HTTP) request for the second URL;
receiving, by the first server from the first client device, in response to the sent first HTTP request, at least part of the first web page;
receiving, by the first server from the second client device, in response to the sent second HTTP request, at least part of the second web page; and
constructing at least part of the web-site from the received parts of the first and second web-pages,
so that the web server is prevented from identifying the first device and the first server.

### Claim 2 (depends on 1)

The method according to claim 1, wherein each of the client devices in the group comprises, or consists of, a portable or mobile device that stores or operates a mobile operating system.

### Claim 3 (depends on 2)

The method according to claim 2, wherein each of the client devices in the group comprises, or consists of a cellular telephone device.

### Claim 4 (depends on 2)

The method according to claim 2, 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.

### Claim 5 (depends on 1)

The method according to claim 1, wherein the constructing is performed by the first server.

### Claim 6 (depends on 5)

The method according to claim 5, further comprising sending, by the first server to the first device, the constructed at least part of the web-site in response to the receiving of the first and second URLs.

### Claim 7 (depends on 1)

The method according to claim 1, further comprising sending, by the first server to the first device, the at least part of the first and second web-pages.

### Claim 8 (depends on 7)

The method according to claim 7, wherein the constructing is performed by the first device.

### Claim 9 (depends on 1)

The method according to claim 1, wherein the selecting of the respective client device comprises randomly selecting a device from the group.

### Claim 10 (depends on 1)

The method according to claim 1, wherein the first device is a client device in a client-server architecture with the first server.

### Claim 11 (depends on 1)

The method according to claim 1, wherein the receiving by the first server from the first client device, in response to the sent first HTTP request, comprises receiving the whole first web-page.

### Claim 12 (depends on 11)

The method according to claim 11, wherein the receiving by the first server from the second client device, in response to the sent second HTTP request, comprises receiving the whole second web-page.

### Claim 13 (depends on 1)

The method according to claim 1, wherein the constructing comprises constructing the whole web-site.

### Claim 14 (depends on 1)

The method according to claim 1, for use with a web site that further includes a third web-page that is identified by a third URL, wherein the group of client devices further comprises a third client device distinct from the first and second client devices and identified by a third IP address, and the method further comprising:
receiving, by a first server from the first device, a third URL;
selecting, by the first server in response to the receiving, the third client device;
sending, by the first server to the third client device, using the IP address of the third client device, a third HyperText Transfer Protocol (HTTP) request for the third URL; and
receiving, by the first server from the third client device, in response to the sent third HTTP request, at least part of the third web page,
wherein the constructing comprises constructing at least part of the web-site from the received parts of the first, second, and third web-pages.

### Claim 15 (depends on 1)

The method according to claim 1, wherein each of the first and second web-pages comprises multiple objects, wherein the received at least part of the first web page comprises a first object of the first web page, and wherein the received at least part of the second web page comprises a second object of the second web page.

### Claim 16 (depends on 15)

The method according to claim 15, wherein the constructing further comprises forming a message that includes at least the first and second objects.

### Claim 17 (depends on 16)

The method according to claim 16, wherein each of the first and second objects is a Hypertext Markup Language (HTML) object.

### Claim 18 (depends on 16)

The method according to claim 16, wherein at least one of the first and second objects comprises, or consists of, a file or program.

### Claim 19 (depends on 16)

The method according to claim 16, wherein each of the first and second objects comprises, or consists of, an HTTP addressed object.

### Claim 20 (depends on 1)

The method according to claim 1, wherein the web server that uses HyperText Transfer Protocol (HTTP) and responds to HTTP requests via the Internet.

### Claim 21 (depends on 1)

The method according to claim 1, wherein the communication with each of the first and second client devices is based on, or using, HTTP persistent connection.

### Claim 22 (depends on 1)

The method according to claim 1, wherein each of the IP addresses is in IPv4 or IPv6 form.

### Claim 23 (depends on 1)

The method according to claim 1, wherein the selecting of the device comprises selecting based on an attribute or a characteristic of the selected client device.

### Claim 24 (depends on 1)

The method according to claim 1, wherein the selecting of the first or second client device comprises selecting based on a physical geographical location of the selected device.

### Claim 25 (depends on 24)

The method according to claim 24, wherein the physical geographical location consists of, or comprises, one out of a continent, a country, a region, a city, a street, a ZIP code, or a timezone.

### Claim 26 (depends on 24)

The method according to claim 24, wherein the geographical location is based on a geolocation.

### Claim 27 (depends on 26)

The method according to claim 26, wherein the geolocation is based on W3C Geolocation API.

### Claim 28 (depends on 24)

The method according to claim 24, for use with a database associating IP addresses to geographical locations, wherein the geographical location is based on using the respective selected client device IP address in the database.

### Claim 29 (depends on 1)

The method according to claim 1, further comprising establishing a connection with the selected client device using TCP, and wherein the connection is established by performing ‘Active OPEN’ or ‘Passive OPEN’.

### Claim 30 (depends on 1)

The method according to claim 1, wherein at least one of the web-pages includes, consists of, or comprises, a part or whole of files, text, numbers, audio, voice, multimedia, video, images, music, or computer program.

### Claim 31 (depends on 1)

The method according to claim 1, wherein the first and second web-pages are of the same size.

### Claim 32 (depends on 1)

The method according to claim 1, wherein the web-site includes three or more web-pages.

### Claim 33 (depends on 1)

The method according to claim 1, further comprising, storing, by the first device, the constructed at least part of the web-site.

### Claim 34 (depends on 1)

The method according to claim 1, further comprising storing, operating, or using, by each of the first and second client devices, a client operating system.

### Claim 35 (depends on 1)

The method according to claim 1, further comprising storing, operating, or using, by the first device, a client operating system.

### Claim 36 (depends on 35)

The method according to claim 35, wherein the client operating system consists or, comprises of, or is based on, one out of Microsoft Windows 7, Microsoft Windows XP, Microsoft Windows 8, Microsoft Windows 8.1, Linux, and Google Chrome OS.

### Claim 37 (depends on 35)

The method according to claim 35, further comprising executing an application by the first device, and wherein the method further comprising sending, by the first device, the first and second URLs in response to the executing of the application.

### Claim 38 (depends on 37)

The method according to claim 37, wherein the application consists of, or comprises, a web browser.

### Claim 39 (depends on 38)

The method according to claim 38, wherein the web browser consists of, comprises of, or is based on, Microsoft Internet Explorer, Google Chrome, Opera™, Mozilla Firefox®, Safari, Opera Mini™, or Android web browser.

### Claim 40 (depends on 1)

The method according to claim 1, further comprising periodically sending, by each of the first and second client devices to the first server, a message that comprises a status of the respective client device.

### Claim 41 (depends on 40)

The method according to claim 40, wherein the sending of the message is in response to the status or a status change of the respective client device.

### Claim 42 (depends on 40)

The method according to claim 40, wherein the message comprises, or is based on, an ‘heartbeat’ message, and wherein the time period between two or more sent messages is at least milliseconds, 20 milliseconds, 30 milliseconds, 50 milliseconds, 100 milliseconds, 1 second, 2 seconds, 3 seconds, 5 seconds, 10 seconds, 20 seconds, 30 seconds, 50 seconds, or 100 seconds, 1 minute, 2 minutes, 3 minutes, minutes 5, or 10 minutes.

### Claim 43 (depends on 1)

The method according to claim 1, further comprising, storing, operating, or using, by the first server, an operating system that consists or, comprises of, or based on, one out of Microsoft Windows Server®, Linux, or UNIX.

### Claim 44 (depends on 43)

The method according to claim 43, 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®.

### Claim 45 (depends on 1)

The method according to claim 1, for use with a resource associated with a criterion in each of the client devices in the group, and wherein each one of the client device in the group is associated with first and second states according to a utilization of the resource.

### Claim 46 (depends on 45)

The method according to claim 45, further comprising, periodically or continuously determining, by each one of the client devices in the group, whether the resource utilization satisfies the criterion.

### Claim 47 (depends on 46)

The method according to claim 46, further comprising, responsive to the determining that the utilization of the resource satisfies the criterion, shifting, by the respective one of the client devices in the group, to the first state or staying in the first state; and responsive to the determining that the utilization of the resource does not satisfy the criterion, shifting, by the respective one of the client devices in the group, to the second state or staying in the second state.

### Claim 48 (depends on 47)

The method according to claim 47, further comprising, performing a task, by the respective one of the client devices in the group, upon a request from the first server, when in the first state.

### Claim 49 (depends on 47)

The method according to claim 47, further comprising periodically or continuously sending, by the respective one of the client devices in the group, the resource utilization to the first server.

### Claim 50 (depends on 49)

The method according to claim 49, wherein the determining is performed by the first server in response to a receiving, by the first server, the resource utilization from the respective client device.

### Claim 51 (depends on 45)

The method according to claim 45, for use with a set threshold value, and wherein the criterion is satisfied when the resource utilization is above or below the threshold.

### Claim 52 (depends on 45)

The method according to claim 45, wherein the resource comprises, or consists of, a hardware component in the respective client device.

### Claim 53 (depends on 52)

The method according to claim 52, wherein the hardware component comprises, or consists of, a processor or Central Processing Unit (CPU) operation in the client device.

### Claim 54 (depends on 53)

The method according to claim 53, wherein the resource utilization is based on, or comprises, the processor or CPU time of executing one or more threads or processes, wherein the resource utilization is based on, or comprises, the processor or CPU idling time, or wherein the resource utilization is based on, or comprises, the processor or CPU executing a system idle process.

### Claim 55 (depends on 52)

The method according to claim 52, wherein the hardware component comprises, or consists of, a memory in the client device, and wherein the resource utilization is based on, or comprises, an amount of used or unused location or space of the memory.

### Claim 56 (depends on 45)

The method according to claim 45, wherein the resource comprises, or consists of, input or output capability.

### Claim 57 (depends on 56)

The method according to claim 56, wherein the resource comprises, or consists of, communication bandwidth of communication with another device over the Internet.

### Claim 58 (depends on 57)

The method according to claim 57, wherein the resource comprises, or consists of, communication bandwidth of communication with the server over the Internet, or wherein the resource utilization is based on, or according to, IETF RFC 2914.

### Claim 59 (depends on 1)

The method according to claim 1, wherein the selecting of the respective client device comprises selecting based on a physical geographical proximity to the first server.

### Claim 60 (depends on 1)

The method according to claim 1, wherein the selecting of the respective client device comprises selecting based on past activities or on a timing of an event.

### Claim 61 (depends on 1)

The method according to claim 1, further comprising:
receiving, by the first client device from the first server, the first URL;
sending, by the first client device to the web server, in response to the receiving of the first URL, a third HTTP request for the first URL;
receiving, by the first client device from the web server, in response to the sending of the third HTTP request, the at least part of the first web page;
sending, by the first client device to the first server, in response to the receiving of the at least part of the first web page, the at least part of the first web page;
receiving, by the second client device from the first server, the second URL;
sending, by the second client device to the web server, in response to the receiving of the second URL, a fourth HTTP request for the second URL;
receiving, by the second client device from the web server, in response to the sending of the fourth HTTP request, the at least part of the second web page; and
sending, by the second client device to the first server, in response to the receiving of the at least part of the second web page, the at least part of the second web page.
