Virtual channel joining

• US 9,705,957 B2
• Filed: 07/17/2013
• Issued: 07/11/2017
• Est. Priority Date: 03/04/2013
• Status: Expired due to Fees

• Current Assignee: Open Garden Incorporated
• Original Assignee: Open Garden Incorporated
• Inventors: Shalunov, Stanislav, Hazel, Gregory, Benoliel, Micha
• Primary Examiner(s): Mundur, Padma
• Application Number:
  US13/944,756
• Publication Number:
  US 20140250204A1
• Time in Patent Office: 1,455 Days
• Field of Search: None
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: H04W 74/02 Hybrid access
• CPC Class Codes: H04W 76/15 Setup of multiple wireless link connections
• CPC Class Codes: H04W 88/06 adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Abstract

Methods for establishing connection to the Internet using multiple channels. A device takes advantage of several channels available to it internally and/or from neighboring devices to request the various resources of the webpage, and assembles the webpage using the resources arriving from the different channels. When a device has the ability to connect to the Internet using multiple internal channels, the device uses internal heuristics to request the webpage resources using these channels. A cloud exit server may be used to enhance security and to handle requests that may not be handled using multiple channels.

Claims

1. A method for enabling multi-channel communication with a mobile device, the mobile device having a processor and a memory, executing a user application, the method comprising:

providing a main application residing on a network-connected server;

causing the mobile device, using a client application, to perform a process comprising;

(a) intercepting a request generated by the user application;

(b) analyzing the request to determine whether the request is decipherable and can be processed by the client application;

(c) when the request is not decipherable and cannot be processed by the client application, encapsulating the request as a first encapsulated partial request inside a first encapsulation packet and a second encapsulated partial request inside a second encapsulation packet, wherein the first encapsulated partial request contains a target address, the first encapsulation packet contains an address of the network-connected server as its destination, the second encapsulated partial request contains the target address, and the second encapsulation packet contains the address of the network-connected server as its destination;

(d) sending the first encapsulated partial request to the network-connected server via a first intermediary device; and

(e) sending the second encapsulated partial request to the network-connected server via a second intermediary device;

receiving, by the main application, the first encapsulated partial request from the first intermediary device, the first encapsulated partial request being originated and sent from the mobile device and containing an originating address of the request;

receiving, by the main application, the second encapsulated partial request from the second intermediary device, the second encapsulated partial request being originated and sent from the mobile device and containing the originating address of the request;

decapsulating, by the main application, the first encapsulated partial request to obtain a first decapsulated partial request and determining the originating address and the target address from the first decapsulated partial request;

decapsulating, by the main application, the second encapsulated partial request to obtain a second decapsulated partial request;

assembling the first decapsulated partial request and the second decapsulated partial request into an assembled decapsulated request corresponding to the original request generated by the user application on the mobile device;

sending the assembled decapsulated request to the target using the target address and including the network-connected server as a request originator;

receiving a response to the assembled decapsulated request from the target; and

forwarding the response to the mobile device using the originating address of the request.

2. The method of claim 1, further comprising sending the request from the client application to the target address when the request is decipherable.

3. The method of claim 1, further comprising sending the request from the client application to the target address a plurality of times using a plurality of channels when the request is decipherable and the request is an idempotent request.

4. The method of claim 1, further comprising:

when the request is decipherable, splitting the request into a plurality of sub-requests; and

sending the plurality of sub-requests from the client application to the target address using a plurality of channels.

5. The method of claim 1, further comprising:

when the request is decipherable, sending the request from the client application to the target address; and

following receipt of a reply to the request, storing at least part of the reply in a cache memory.

6. The method of claim 5, further comprising:

receiving a forward request from a second mobile device;

determining whether a forward reply to the forward request is stored in the cache memory as a cached reply; and

if the cached reply is stored in the cache memory, sending the cached reply to the second mobile device without sending the forward request to the target address.

7. The method of claim 1, further comprising:

sending the request from the client application to the target address via a second mobile device when the request is decipherable; and

following receipt of a reply to the request at the second mobile device, storing at least part of the reply in a cache memory of the second mobile device.

8. The method of claim 1, further comprising:

sending the request from the client application to the target address via a second mobile device when the request is decipherable; and

following receipt of the request by the second mobile device, determining whether a reply to the request is stored in a cache memory of the second mobile device as a cached reply; and

if the cached reply is stored in the cache memory, fetching the cached reply from the cache memory of the second mobile device and sending the cached reply to the mobile device.

9. The method of claim 1, further comprising:

determining if the request is decipherable to contain a plurality of sub-requests;

determining whether a reply to at least one sub-request of the plurality of sub-requests is stored in a cache memory as a cached reply; and

if the cached reply is stored in the cache memory, providing the cached reply to the user application and sending remaining sub-requests other than the at least one sub-request to the target address.

10. The method of claim 9, wherein the plurality of sub-requests are sent via a plurality of communications channels and wherein at least one of the communication channels comprises an ad-hoc connection to a second mobile device.