IP Library Granted Patent US 12,069,150
Granted Patent B2
US 12,069,150 · App. 18/073,137 · Granted Aug 20, 2024

System and method for improving internet communication by using intermediate nodes

Inventors: Derry Shribman (Tel Aviv, IL); Ofer Vilenski (Moshav Hadar Am, IL)
Assignee: BRIGHT DATA LTD.
H04L67/60H04L43/0864H04L63/029H04L63/0407H04L65/612H04L67/02H04L67/06H04L67/141H04L67/567H04L67/59H04N21/4622H04W4/029
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,069,150
App. No.
18/073,137
Granted
Aug 20, 2024
Kind
B2
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 (53)

1. A method for an anonymous communication using a group of client devices, the method comprising:

receiving, by a first server from each of the client devices in the group over the Internet, a respective message, in response to a sending of the respective message initiated by each of the client devices in the group;

storing, in the first server, in response to the receiving of the messages, a respective IP address of each of the client devices in the group;

receiving, by the first server from a first device over the Internet, a first URL that identifies a first content;

selecting, by the first server, in response to the receiving of the first URL, a first client device from the group;

sending, by the first server to the first client device over the Internet, the first URL;

receiving, by the first server from a second server via the first client device over the Internet, the first content;

sending, by the first server to the first device over the Internet, the received first content;

receiving, by the first server from the first device over the Internet, a second URL that identifies a second content;

selecting, by the first server, in response to the receiving of the second URL, a second client device from the group;

sending, by the first server to the second client device over the Internet, the second URL;

receiving, by the first server from a third server via the second client device over the Internet, the second content;

sending, by the first server to the first device over the Internet, the received second content;

receiving, by the first server from the first device over the Internet, a third URL that identifies a third content;

selecting, by the first server, in response to the receiving of the third URL, a third client device from the group;

sending, by the first server to the third client device over the Internet, the third URL;

receiving, by the first server from a fourth server via the third client device over the Internet, the third content; and

sending, by the first server to the first device over the Internet, the received third content,

so that the first device is not identified by the second, third, and fourth servers, and

wherein the first server is not a client device.

2. The method according to claim 1 , wherein the third server is distinct from the second server, wherein the third server is distinct from the fourth server, and wherein the second server is distinct from the fourth server.

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

4. The method according to claim 1 , wherein the first content is distinct from the second content and from the third content.

5. The method according to claim 1 , wherein the first content and the second content are the same content.

6. The method according to claim 1 , wherein each of the first content and the second content is a public content that is available from a respective web server for any requesting client device over the Internet.

7. The method according to claim 1 , wherein the first device consists of, or comprises, a host device having a processor and a computer-readable medium storing a software that is executed by the processor.

8. The method according to claim 1 , further comprising sending, by the first server to the first device over the Internet, at least a part of the stored IP addresses.

9. The method according to claim 1 , further comprising sending, by the first server to the first device over the Internet, the IP addresses of the selected devices to the first device.

10. The method according to claim 1 , wherein the selecting of the first, second, or third client device comprises randomly selecting out of the client devices in the group.

11. The method according to claim 1 , wherein the selecting of the first, second, or third client device comprises selecting based on attributes or characteristics of the devices in the group.

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

13. The method according to claim 12 , wherein the physical geographical location associated with each of the client devices in the group is based on, uses, or responsive to, the actual physical geographical location of the respective client device of the group.

14. The method according to claim 12 , further comprising receiving, by the first server from each of the client devices of the group over the Internet, the respective physical geographical location.

15. The method according to claim 12 , wherein the physical geographical location includes at least a country, a state or province, a city, a street, a ZIP code, longitude and latitude, or any combination thereof.

16. The method according to claim 12 , wherein the physical geographical location of each of the devices of the group is estimated based on a geolocation.

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

18. The method according to claim 1 , wherein the selecting of the first client device comprises selecting based on a value of the IP addresses of the devices in the group.

19. The method according to claim 1 , wherein the selecting of the first, second, or third client device comprises selecting based on past activities of the devices in the group.

20. The method according to claim 19 , wherein the selecting of the first, second, or third client device comprises selecting based on timing of an event.

21. The method according to claim 20 , wherein the selecting of the first, second, or third client device comprises selecting based on timing of a last communication with the devices in the group.

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

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

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

25. The method according to claim 1 , wherein the first content includes, consists of, or comprises, a part or whole of a file, text data, audio data, voice data, multimedia data, video data, an image, music data, or any combination thereof.

26. The method according to claim 1 , wherein the first, second, or third content includes, consists of, or comprises, a part or whole of a web-site page.

27. The method according to claim 1 , wherein the first URL is distinct from the second URL.

28. The method according to claim 1 , wherein the first URL and the second URL are the same URL.

29. The method according to claim 1 , wherein the first client device is distinct from the second client device.

30. The method according to claim 1 , wherein the first client device and the second client device are the same client device.

31. The method according to claim 1 , wherein the first device comprises, or consists of, a consumer mobile device.

32. The method according to claim 1 , wherein at least one of the devices in the group comprises, or consists of, a consumer mobile device.

33. The method according to claim 1 , wherein each of the devices in the group comprises, or consists of, a respective consumer mobile device.

34. The method according to claim 1 , wherein the first device is not included in the client devices in the group.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 1, 2022
From: SHRIBMAN, DERRY; VILENSKI, OFER
To: LUMINATI NETWORKS LTD.
Reel/Frame 061945/0204 →
CHANGE OF NAME Recorded Dec 1, 2022
From: LUMINATI NETWORKS LTD.
To: BRIGHT DATA LTD.
Reel/Frame 062038/0808 →
Continuity (7)
Continuation 16593999 · Oct 5, 2019
Continuation 16292363 · Mar 5, 2019
Continuation 15663762 · Jul 30, 2017
Continuation 14930894 · Nov 3, 2015
Division 14468836 · Aug 26, 2014
Provisional Application 61870815 · Aug 28, 2013
Related Publication 20230111675A1 · Apr 13, 2023