# US 2025/0097064 A1 · System and Method for Improving Content Fetching by Selecting Tunnel Devices

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

- Number: US 2025/0097064 A1
- Document ID: US20250097064A1
- Status: Published application
- Kind: A1
- Application number: 18/959,844
- Filed: 2024-11-26
- Published: 2025-03-20
- Earliest claimed: 2017-08-28
- Assignees: Bright Data Ltd.
- Applicants: Bright Data Ltd.
- Inventors: Derry Shribman; Ofer Vilenski
- Web page: https://patentgrep.com/patent/US20250097064A1

## CPC

- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- G06F 7/58: Random or pseudo-random number generators
- G06F 7/588: {Random number generators, i.e. based on natural stochastic processes}
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 9/45545: {Guest-host, i.e. hypervisor is an application program itself, e.g. VirtualBox}
- G06F 9/4555: {Para-virtualisation, i.e. guest operating system has to be modified}
- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- G06F 16/955: using information identifiers, e.g. uniform resource locators [URL]
- H04L 12/2803: {Home automation networks}
- H04L 12/2856: {Access arrangements, e.g. Internet access (asynchronous transfer mode networks H04L12/5601; broadband local area networks H04L12/2801; optical access or distribution networks H04Q11/0067; access to open networks H04L12/5691; digital subscriber line end-user equipment and bit-level processing of data on a PSTN-based network H04M11/00; home network gateways H04L12/2834; wireless access networks H04W)}
- H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling}
- H04L 47/283: in response to processing delays, e.g. caused by jitter or round trip time [RTT]
- H04L 61/256: NAT traversal
- H04L 61/2575: using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
- H04L 61/2585: through application level gateway [ALG]
- H04L 61/2589: over a relay server, e.g. traversal using relay for network address translation [TURN]
- H04L 61/2592: using tunnelling or encapsulation
- H04L 61/4511: using domain name system [DNS]
- H04L 61/5007: Internet protocol [IP] addresses
- H04L 63/0272: {Virtual private networks}
- H04L 63/0281: {Proxies}
- H04L 63/029: {Firewall traversal, e.g. tunnelling or, creating pinholes}
- H04L 63/164: {at the network layer}
- H04L 67/01: Protocols
- H04L 67/025: for remote control or remote monitoring of applications
- H04L 67/1008: based on parameters of servers, e.g. available memory or workload (monitoring of computer activity G06F11/30)
- H04L 67/1021: based on client or server locations
- H04L 67/133: Protocols for remote procedure calls [RPC]
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L 67/142: Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
- H04L 67/288: Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
- H04L 67/2885: Hierarchically arranged intermediate devices, e.g. for hierarchical caching
- H04L 67/56: Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54)
- H04L 67/563: Data redirection of data network streams
- H04L 67/567: Integrating service provisioning from a plurality of service providers
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L 67/5681: Pre-fetching or pre-delivering data based on network characteristics
- H04L 67/63: Routing a service request depending on the request content or context
- H04L 69/16: Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L 69/162: {involving adaptations of sockets based mechanisms (secure socket layer H04L63/168)}
- H04L 69/167: Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6 (translation of Internet protocol [IP] addresses H04L61/2503)
- H04L 69/168: specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
- H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
- H04W 48/18: Selecting a network or a communication service
- H04W 84/10: Small scale networks; Flat hierarchical networks
- H04W 84/18: Self-organising networks, e.g. ad-hoc networks or sensor networks
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 2009/45591: {Monitoring or debugging support}
- G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances}
- H04L 61/2514: between local and global IP addresses
- H04L 61/2553: Binding renewal aspects, e.g. using keep-alive messages
- H04L 69/325: in the network layer [OSI layer 3], e.g. X.25 (H04L69/16 takes precedence)
- H04L 69/326: in the transport layer [OSI layer 4] (H04L69/16 takes precedence)
- H04L 69/329: in the application layer [OSI layer 7]
- H04L 2101/69: using geographic information, e.g. room number
- Y10S 30/01: Rechargeable battery operated
- Y10S 320/21: State of charge of battery
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## 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 tunnel device is selected based on an attribute, such as IP Geolocation. A tunnel bank server stores a list of available tunnels that may be used, associated with values of various attribute types. The tunnel devices initiate communication with the tunnel bank server, and stays connected to it, for allowing a communication session initiated by the tunnel bank server. Upon receiving a request from a client to a content and for specific attribute types and values, a tunnel is selected by the tunnel bank server, and is used as a tunnel for retrieving the required content from the web server, using standard protocol such as SOCKS, WebSocket or HTTP Proxy. The client only communicates with a super proxy server that manages the content fetching scheme.

## Claims

### Claim 1

A method for obtaining, by a client device, a first content that is stored in a first web server, that comprises a first web-page or a part thereof, and that is identified by a first content identifier, and for obtaining by the client device, a second content that is stored in a second web server, that comprises a second web-page or a part thereof, and that is identified by a second content identifier, by using a group of mobile devices, each of the mobile devices in the group is identified by a respective Internet Protocol (IP) address, for use with a database that associates a respective bandwidth (BW) value to each of the IP address of the mobile devices in the group, the method comprising:
establishing, via a first wireless network over the Internet, a first connection over to a first mobile device;
measuring, a first BW value of the first connection;
adding, the first mobile device to the group, by adding an IP of the first mobile device associated with the measured first BW to the database;
establishing, via a second wireless network over the Internet, a second connection to a second mobile device;
measuring, a second BW value of the second connection;
adding, the second mobile device to the group, by adding an IP of the second mobile associated with the measured second BW to the database;
receiving, by a first server from the client device over the Internet, a first request for the first content that comprises the first content identifier;
selecting, from the group, based on BW values in the database, in response to the receiving of the first request, a third mobile device from the group by selecting from the database a third IP address of the third mobile device;
sending, by the first server to the first web server via the third mobile device over the Internet, the first request, in response to the selecting of the third mobile device;
receiving, by the first server from the first web server via the third mobile device over the Internet, the first content, in response to the sending of the first request;
sending, by the first server to the client device over the Internet, the received first content;
receiving, by the first server from the client device over the Internet, a second request for the second content that comprises the second content identifier;
selecting, from the group, based on BW values in the database, in response to the receiving of the second request, a fourth mobile device from the group by selecting from the database a fourth IP address of the fourth mobile device;
sending, by the first server to the second web server via the fourth mobile device over the Internet, the second request, in response to the selecting of the fourth mobile device;
receiving, by the first server from the second web server via the fourth mobile device over the Internet, the second content, in response to the sending of the second request; and
sending, by the first server to the client device over the Internet, the received second content.

### Claim 2 (depends on 1)

The method according to claim 1, further comprising estimating or measuring, a Round-Trip delay Time (RTT) with the first or second mobile device; and storing the estimated or measured RTT.

### Claim 3 (depends on 1)

The method according to claim 1, further comprising:
establishing, over the Internet, a third connection to a fifth mobile device;
measuring, a third BW value of the third connection; and
adding, the fifth mobile device to the group, by adding an IP of the fifth mobile device associated with the measured third BW to the database.

### Claim 4 (depends on 1)

The method according to claim 1, further for obtaining a third content that is stored in the first web server, that comprises a third web-page or a part thereof, and that is identified by a third content identifier, the method further comprising:
receiving, by a first server from the client device over the Internet, a third request for the third content that comprises the third content identifier;
selecting, from the group, based on BW values in the database, in response to the receiving of the third request, a fifth mobile device from the group by selecting from the database a fifth IP address of the fifth mobile device;
sending, by the first server to the first web server via the fifth mobile device over the Internet, the third request, in response to the selecting of the fifth mobile device;
receiving, by the first server from the first web server via the fifth mobile device over the Internet, the third content, in response to the sending of the third request; and
sending, by the first server to the client device over the Internet, the received third content.

### Claim 5 (depends on 1)

The method according to claim 1, further for obtaining a third content that is stored in a third web server, that comprises a third web-page or a part thereof, and that is identified by a third content identifier, the method further comprising:
receiving, by a first server from the client device over the Internet, a third request for the third content that comprises the third content identifier;
selecting, from the group, based on BW values in the database, in response to the receiving of the third request, the first mobile device from the group by selecting from the database a first IP address of the first mobile device;
sending, by the first server to the third web server via the first mobile device over the Internet, the third request, in response to the selecting of the first mobile device;
receiving, by the first server from the third web server via the first mobile device over the Internet, the third content, in response to the sending of the third request; and
sending, by the first server to the client device over the Internet, the received third content.

### Claim 6 (depends on 1)

The method according to claim 1, further comprising storing or using a virtualized operating system, wherein the operating system is executed as a guest operating system as part of a Virtual Machine (VM).

### Claim 7 (depends on 6)

The method according to claim 6, for use with a host computer that implement the VM, wherein the method further comprising executing, by the host computer, a hypervisor or a Virtual Machine Monitor (VMM), and wherein the guest operating system uses or interfaces virtual hardware.

### Claim 8 (depends on 6)

The method according to claim 6, wherein the virtualization includes, is based on, or uses, full virtualization, para-virtualization, or hardware assisted virtualization.

### Claim 9 (depends on 1)

The method according to claim 1, wherein the selecting of the third or fourth mobile device further comprises randomly selecting using a random number generated by a random number generator.

### Claim 10 (depends on 9)

The method according to claim 9, wherein the random number generator uses a thermal noise, shot noise, nuclear decaying radiation, photoelectric effect, or quantum phenomena.

### Claim 11 (depends on 9)

The method according to claim 9, wherein the random number generator is based on executing an algorithm for generating pseudo-random numbers.

### Claim 12 (depends on 1)

The method according to claim 1, wherein the database comprises at least 10,000, 20,000, 50,000, 100,000, 200,000, 500,000, 1,000,000, 2,000,000, 5,000,000, or 10,000,000 IP addresses.

### Claim 13 (depends on 1)

A non-transitory computer readable medium containing computer instructions that, when executed by a computer processor, cause the processor to perform at least part of the steps of claim 1.

### Claim 14 (depends on 1)

The method according to claim 1, wherein at least part steps of claim 1 are included in a Software Development Kit (SDK) that is provided as a non-transitory computer readable medium that contains computer instructions, and wherein the method further comprising installing the Software Development Kit (SDK).

### Claim 15 (depends on 1)

The method according to claim 1, wherein the first or second wireless network uses a Wireless Wide Area Network (WWAN).

### Claim 16 (depends on 15)

The method according to claim 15, wherein the WWAN uses a WiMAX network, that is compatible with IEEE 802.16-2009 standard.

### Claim 17 (depends on 15)

The method according to claim 15, wherein the wireless network implements a cellular telephone network.

### Claim 18 (depends on 17)

The method according to claim 17, wherein the cellular telephone network is a Third Generation (3G) network that uses a protocol selected from the group consisting of UMTS WCDMA, UMTS HSPA, UMTS TDD, CDMA2000 1×RTT, CDMA2000 EV-DO, and GSM EDGE-Evolution, or wherein the cellular telephone network uses a protocol selected from the group consisting of a Fourth Generation (4G) network that uses HSPA+, Mobile WiMAX, LTE, LTE-Advanced, MBWA, or is based on IEEE 802.20-2008.

### Claim 19 (depends on 15)

The method according to claim 15, wherein the first or second wireless network uses a Wireless Personal Area Network (WPAN).

### Claim 20 (depends on 19)

The method according to claim 19, wherein the WPAN is compatible with IEEE 802.15.1-2005 standard, or wherein the WPAN is a wireless control network that is compatible with IEEE 802.15.4-2003 standard.

### Claim 21 (depends on 15)

The method according to claim 15, wherein the first or second wireless network implements a Wireless Local Area Network (WLAN).

### Claim 22 (depends on 21)

The method according to claim 21, wherein the WLAN is according to, compatible with, or is based on, a standard selected from the group consisting of IEEE 802.11-2012, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and IEEE 802.11ac.

### Claim 23 (depends on 1)

The method according to claim 1, wherein at least one of the mobile devices in the group is housed in a single hand-held enclosure.

### Claim 24 (depends on 1)

The method according to claim 1, wherein the first or second content identifier is Uniform Resource Identifier (URI) or Uniform Resource Locator (URL).

### Claim 25 (depends on 1)

The method according to claim 1, further comprising executing, by at least one of the mobile devices in the group, an operating system.

### Claim 26 (depends on 25)

The method according to claim 25, wherein the operating system is a mobile operating system.

### Claim 27 (depends on 1)

The method according to claim 1, further comprising storing, operating, or using, by at least one of the mobile devices in the group, a web browser.

### Claim 28 (depends on 27)

The method according to claim 27, wherein the web browser comprises a mobile web browser.

### Claim 29 (depends on 1)

The method according to claim 1, wherein at least one of the mobile devices in the group, or the first or second mobile device, is integrated in part or entirely in an appliance.

### Claim 30 (depends on 1)

The method according to claim 1, wherein a communication over the Internet between the client device and the first server, or between the first server and the first or second mobile device, is compatible with WebSocket (ws) or WebSocket Secure (wss) protocol or connection, wherein one of nodes serves as an WebSocket (ws) or WebSocket Secure (wss) server respectively and the other node serves as an WebSocket (ws) or WebSocket Secure (wss) client respectively.

### Claim 31 (depends on 30)

The method according to claim 30, wherein the communication over the Internet between the client device and the first server is compatible with WebSocket (ws) or WebSocket Secure (wss) protocol or connection.

### Claim 32 (depends on 31)

The method according to claim 31, wherein the WebSocket (ws) or WebSocket Secure (wss) protocol or connection is compatible with IETF RFC 6455.
