System and method for improving internet communication by using intermediate nodes
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.
1. A method for use by a client device that utilizes a resource, the method comprising:
initiating, by the client device over the Internet, a communication with a first server;
measuring, by the client device, a utilization level of the resource;
sending, by the client device to the first server, a message that is indicative of the measured utilization level;
receiving, by the client device over the Internet, a first request from the first server;
obtaining, by the client device, a first content in response to the received first request, by utilizing the resource; and
sending, by the client device to the first server over the Internet, the obtained first content, wherein the first content comprises a part or whole of audio data, voice data, multimedia data, video data, an image, or any combination thereof, and wherein the resource comprises, or consists of, a processor or Central Processing Unit (CPU) operation in the client device, an amount of used or unused location or space of a memory, or any combination thereof;
wherein the client device is configured to be in distinct first and second states, the method further comprising:
responsive to a determining that the utilization level of the resource is above or below a threshold level, shifting to, or staying in, the first state; and
responsive to the determining that the utilization level of the resource is respectively not above or below the threshold level, shifting to, or staying in, the second state;
wherein the sending of the message is in response to being in, or shifting to, the first or second state.
2. The method according to claim 1 , wherein the message comprises the measured utilization level.
3. The method according to claim 1 , for use with a threshold level, wherein the sending of the message is in response to the measured utilization level being below the threshold level.
4. The method according to claim 1 , wherein the first content is publicly-accessed, is identified in the Internet by a first identifier, and is stored in a web server, and wherein the first request comprises the first identifier.
5. The method according to claim 4 , wherein the first identifier comprises, or consists of, an Internet Protocol (IP) address in IPv4 or IPv6 form or a Uniform Resource Locator (URL), and wherein the first content comprises a part of, or a whole of, a web-site page.
6. The method according to claim 4 , wherein the obtaining of the first content comprises sending, by the client device to the web server over the Internet, the first identifier, and receiving, by the client device from the web server over the Internet, the first content, in response to the sending of the first identifier.
7. The method according to claim 6 , wherein the first request comprises a HyperText Transfer Protocol (HTTP) or a HyperText Transfer Protocol Secure (HTTPS) request, or wherein the sending of the first identifier comprises sending of a HyperText Transfer Protocol (HTTP) or a HyperText Transfer Protocol Secure (HTTPS) request.
8. The method according to claim 1 , wherein the receiving of the first request is in response to the sending of the message.
9. The method according to claim 1 , wherein the measuring of the utilization level comprises periodically measuring of the utilization level.
10. The method according to claim 9 , wherein the sending of the message comprises periodically sending of the message.
11. The method according to claim 10 , wherein the sending of the message is performed at least every 10, 20, 30, 50, or 100 milliseconds, every 1, 2, 3, 5, or 10 seconds, or every 1, 2, 3, 5, or 10 minutes.
12. The method according to claim 1 , wherein the measuring of the utilization level comprises continuously measuring of the utilization level.
13. The method according to claim 1 , further comprising determining, by the client device, whether the measured utilization level is above or below a threshold level.
14. The method according to claim 13 , wherein the sending of the message is in response to determining that the measured utilization level is above or below the threshold level.
15. The method according to claim 1 , 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.
16. The method according to claim 1 , wherein the resource further comprises a hardware component in the client device.
17. The method according to claim 1 , wherein the resource further comprises an input or output capability.
18. The method according to claim 17 , wherein the resource comprises, or consists of, communication bandwidth for communication with another device over the Internet.
19. The method according to claim 18 , wherein the resource comprises, or consists of, communication bandwidth of communication with the first server over the Internet, or wherein the resource utilization is based on, or according to, IETF RFC 2914.
20. The method according to claim 1 , wherein the receiving of the first request comprises receiving of the first request from a second server that is distinct from the first server, and wherein the sending of the received first content comprises sending of the first received content to the second server.
21. The method according to claim 1 , further comprising:
receiving, by the client device over the Internet, a second request;
obtaining, by the client device, a second content in response to the received second request, by utilizing the resource; and
sending, by the client device over the Internet, the obtained second content.
22. The method according to claim 21 , wherein the second content is publicly-accessed, is identified in the Internet by a first identifier, and is stored in a web server, wherein the second request comprises the first identifier, and wherein the obtaining of the second content comprises sending, by the client device to the web server over the Internet, the first identifier, and receiving, by the client device from the web server over the Internet, the second content, in response to the sending of the first identifier.
23. The method according to claim 1 , further comprising establishing a connection between the client device and the first server, and wherein any communication with the first server and the client device is over the established connection.
24. The method according to claim 23 , wherein the established connection is a Transmission Control Protocol (TCP) connection that is established by performing ‘Active OPEN’ or ‘Passive OPEN’, wherein the communication between the client device with the first server is based on, or is according to, Transmission Control Protocol over Internet Protocol (TCP/IP) protocol or connection, wherein the established connection uses a tunneling protocol or a Virtual Private Network (VPN), or wherein the established connection uses HTTP or HTTPS persistent connection.
25. The method according to claim 1 , further comprising:
receiving, by the first server from the client device, the message; and
sending, by the first server to the client device over the Internet, the first request in response to the received message.
26. The method according to claim 1 , wherein the client device comprises a vehicular device configured to be used or installable in a vehicle.
27. The method according to claim 1 , wherein the client device is further storing, operating, or using, a client operating system.
28. The method according to claim 27 , wherein the client operating system comprises Microsoft Windows 7, Microsoft Windows XP, Microsoft Windows 8, Microsoft Windows 8.1, Linux, or Google Chrome OS.
29. The method according to claim 27 , wherein the client operating system comprises 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, or Blackberry® operating system.
30. The method according to claim 27 , wherein the client operating system consists of, comprise, or is based on, Android TV, Android Auto, or Android Wear.
31. The method according to claim 27 , wherein the client operating system comprises a mobile operating system.
32. The method according to claim 31 , wherein the mobile operating system comprises 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, or Blackberry® operating system.
33. The method according to claim 1 , further comprising executing, by the client device, a web browser.
34. The method according to claim 33 , wherein the web browser comprises of Microsoft Internet Explorer, Google Chrome, Opera™, or Mozilla Firefox®.
35. The method according to claim 33 , wherein the web browser comprises a mobile web browser.
36. The method according to claim 35 , wherein the mobile web browser comprises Safari, Opera Mini™, or Android web browser.
37. The method according to claim 1 , further comprising periodically sending, by the client device to the first server over the Internet, an ‘heartbeat’ message that comprises a status of the client device, or is in response to the status of the client device.
38. The method according to claim 37 , wherein the status is based on the measured utilization level.
39. The method according to claim 37 , wherein a time period between sent multiple ‘heartbeat’ messages is at least 10 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.
40. The method according to claim 1 , wherein the client device comprises, or consists of, a portable or mobile device.
41. The method according to claim 40 , wherein the mobile device comprises a smartphone.
42. The method according to claim 1 , wherein the client device comprises, or is part of, a household appliance.
43. The method according to claim 42 , wherein the appliance comprises, or is part of, a major appliance that is an air conditioner, a dishwasher, a clothes dryer, a drying cabinet, a kitchen stove, a water heater, a washing machine, a trash compactor, a microwave oven, or an induction cooker.
44. The method according to claim 43 , wherein the appliance comprises, or is part of, a major appliance that is a freezer or a refrigerator.
45. The method according to claim 43 , wherein the appliance comprises, or is part of, a small appliance that is a television (TV) set.
46. The method according to claim 42 , wherein the appliance comprises, or is part of, a small appliance that is a CD or DVD player, a camcorder, a still camera, a clock, an alarm clock, a video game console, a HiFi or home cinema, a telephone, or an answering machine.
47. The method according to claim 1 , further comprising sending, by the client device to the first server over the Internet, a physical geographical location.
48. The method according to claim 47 , wherein the physical geographical location corresponds to the actual physical geographical location of the client device.
49. The method according to claim 47 , wherein the physical geographical location comprises a country, a state or province, a city, a street, a ZIP code, a longitude, a latitude, or any combination thereof.