# US 2022/0286530 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 2022/0286530 A1
- Document ID: US20220286530A1
- Status: Published application
- Kind: A1
- Application number: 17/681,758
- Filed: 2022-02-26
- Published: 2022-09-08
- Earliest claimed: 2013-08-28
- Assignees: Bright Data Ltd.
- Applicants: Bright Data Ltd.
- Inventors: Derry Shribman; Ofer Vilenski
- Web page: https://patentgrep.com/patent/US20220286530A1

## 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 use with a first content identified by a first Uniform Resource Locator (URL) and stored in a first web server, for use with a second content identified by a second URL and stored in a second web server, and for use with a third server, the method comprising:
sending, by a first device to the third server, a first Hypertext Transfer Protocol (HTTP) or HTTP Secure (HTTPS) request that comprises the first URL;
receiving, by a second device from the third server, the first URL;
sending, by the second device to the first web server, the first URL;
receiving, by the second device from the first web server, the first content;
sending, by the second device to the third server, the first content;
receiving, by the first device from the third server, the first content;
sending, by the first device to the third server, a second HTTP or HTTPS request that comprises the second URL;
receiving, by the second device from the third server, the second URL;
sending, by the second device to the second web server, the second URL;
receiving, by the second device from the second web server, the second content;
sending, by the second device to the third server, the second content; and
receiving, by the first device from the third server, the second content,
wherein the first content includes, consists of, or comprises, a part of, or a whole of, a first web-site page, and
wherein the first content includes, consists of, or comprises, a part of, or a whole of, a second web-site page.

### Claim 2 (depends on 1)

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

### Claim 3 (depends on 1)

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

### Claim 4 (depends on 1)

The method according to claim 1, further comprising receiving, by the third server from the first device, the first URL; and in response sending, by the third server to the second device, the first URL.

### Claim 5 (depends on 4)

The method according to claim 4, for use with a group of devices that includes the second device, each device in the group is identified in the Internet using a respective address that is an Internet Protocol (IP) address in IPv4 or IPv6 form, wherein the addresses of the devices in the group are stored in the third server.

### Claim 6 (depends on 5)

The method according to claim 5, further comprising selecting, by the third server, the second device from the group, in response to the receiving of the first URL from the first device.

### Claim 7 (depends on 6)

The method according to claim 6, wherein the selecting comprises randomly selecting.

### Claim 8 (depends on 6)

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

### Claim 9 (depends on 6)

The method according to claim 6, wherein the selecting is based on a physical geographical location of the selected device.

### Claim 10 (depends on 9)

The method according to claim 9, wherein the selecting is based on a physical geographical proximity to the first web server.

### Claim 11 (depends on 9)

The method according to claim 9, wherein the selecting is based on the value of the selected device address.

### Claim 12 (depends on 9)

The method according to claim 9, wherein the selecting is based on past activities.

### Claim 13 (depends on 12)

The method according to claim 12, wherein the selecting is based on a timing of an event.

### Claim 14 (depends on 1)

The method according to claim 1, further comprising receiving, by the third server from the second device, the first content; and in response sending, by the third server to the first device, the first content.

### Claim 15 (depends on 1)

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.

### Claim 16 (depends on 1)

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

### Claim 17 (depends on 1)

The method according to claim 1, wherein the first device comprises a client device.

### Claim 18 (depends on 1)

The method according to claim 1, wherein the second device comprises a client device.

### Claim 19 (depends on 1)

The method according to claim 1, wherein the first or second web server responds to HTTP requests via the Internet, and wherein the communication with the first or second device is based on, or using, HTTP persistent connection.

### Claim 20 (depends on 1)

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

### Claim 21 (depends on 1)

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’.

### Claim 22 (depends on 1)

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

### Claim 23 (depends on 1)

The method according to claim 1, wherein the third server is storing, operating, or using, a server operating system.

### Claim 24 (depends on 23)

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

### Claim 25 (depends on 23)

The method according to claim 23, 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 26 (depends on 1)

The method according to claim 1, wherein at least one of the first device and the second device comprises a portable device.

### Claim 27 (depends on 26)

The method according to claim 26, wherein the portable device is a cellular telephone device.

### Claim 28 (depends on 1)

The method according to claim 1, wherein at least one of the first device and the second device comprises stores, operates, or uses, a mobile operating system.

### Claim 29 (depends on 28)

The method according to claim 28, 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 30

A method for use with a first content identified by a first Uniform Resource Locator (URL) and stored in a first web server, for use with a second content identified by a second URL and stored in the first web server, and for use with a second server, the method comprising:
sending, by a first device to the second server, a first Hypertext Transfer Protocol (HTTP) or HTTP Secure (HTTPS) request that comprises the first URL;
receiving, by a second device from the second server, the first URL;
sending, by the second device to the first web server, the first URL;
receiving, by the second device from the first web server, the first content;
sending, by the second device to the second server, the first content;
receiving, by the first device from the second server, the first content;
sending, by the first device to the second server, a second HTTP or HTTPS request that comprises the second URL;
receiving, by the second device from the second server, the second URL;
sending, by the second device to the first web server, the second URL;
receiving, by the second device from the first web server, the second content;
sending, by the second device to the second server, the second content; and
receiving, by the first device from the second server, the second content,
wherein the first content includes, consists of, or comprises, a part of, or a whole of, a first web-site page, and
wherein the first content includes, consists of, or comprises, a part of, or a whole of, a second web-site page.

### Claim 31 (depends on 30)

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

### Claim 32 (depends on 30)

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

### Claim 33 (depends on 30)

The method according to claim 30, further comprising receiving, by the second server from the first device, the first URL; and in response sending, by the second server to the second device, the first URL.

### Claim 34 (depends on 33)

The method according to claim 33, for use with a group of devices that includes the second device, each device in the group is identified in the Internet using a respective address that is an Internet Protocol (IP) address in IPv4 or IPv6 form, wherein the addresses of the devices in the group are stored in the second server.

### Claim 35 (depends on 34)

The method according to claim 34, further comprising selecting, by the second server, the second device from the group, in response to the receiving of the first URL from the first device.

### Claim 36 (depends on 35)

The method according to claim 35, wherein the selecting comprises randomly selecting.

### Claim 37 (depends on 35)

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

### Claim 38 (depends on 35)

The method according to claim 35, wherein the selecting is based on a physical geographical location of the selected device.

### Claim 39 (depends on 38)

The method according to claim 38, wherein the selecting is based on a physical geographical proximity to the first web server.

### Claim 40 (depends on 38)

The method according to claim 38, wherein the selecting is based on the value of the selected device address.

### Claim 41 (depends on 38)

The method according to claim 38, wherein the selecting is based on past activities.

### Claim 42 (depends on 41)

The method according to claim 41, wherein the selecting is based on a timing of an event.

### Claim 43 (depends on 30)

The method according to claim 30, further comprising receiving, by the second server from the second device, the first content; and in response sending, by the second server to the first device, the first content.

### Claim 44 (depends on 30)

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

### Claim 45 (depends on 30)

The method according to claim 30, wherein the second content includes, consists of, or comprises, a part or whole of files, text, numbers, audio, voice, multimedia, video, images, music, or computer program.

### Claim 46 (depends on 30)

The method according to claim 30, wherein the first device comprises a client device.

### Claim 47 (depends on 30)

The method according to claim 30, wherein the second device comprises a client device.

### Claim 48 (depends on 30)

The method according to claim 30, wherein the web server responds to HTTP requests via the Internet, and wherein the communication with the first or second device is based on, or using, HTTP persistent connection.

### Claim 49 (depends on 30)

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

### Claim 50 (depends on 30)

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

### Claim 51 (depends on 30)

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

### Claim 52 (depends on 30)

The method according to claim 30, wherein the second server is storing, operating, or using, a server operating system.

### Claim 53 (depends on 52)

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

### Claim 54 (depends on 52)

The method according to claim 52, 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 55 (depends on 30)

The method according to claim 30, wherein at least one of the first device and the second device comprises a portable device.

### Claim 56 (depends on 55)

The method according to claim 55, wherein the portable device is a cellular telephone device.

### Claim 57 (depends on 30)

The method according to claim 30, wherein at least one of the first device and the second device comprises stores, operates, or uses, a mobile operating system.

### Claim 58 (depends on 57)

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