LATENCY VIRTUALIZATION DATA ACCELERATOR

• US 20150271009A1
• Filed: 08/16/2013
• Published: 09/24/2015
• Est. Priority Date: 08/16/2012
• Status: Abandoned Application

• Current Assignee: Data Accelerator Ltd.
• Original Assignee: Data Accelerator Ltd.
• Inventors: Clothier, Matthew P., Corbett, Sean P., Kirkby, Martin, A'Court, Robert, McNeil, Andrew, Elliott, Edward Philip Edwin
• Application Number:
  US14/435,427
• Publication Number:
  US 20150271009A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 43/045 for graphical visualisation of monitoring data
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal

Abstract

A technique involves placing a data acceleration engine between an end user device and a host device. The host device provides data associated with a client application to the data acceleration engine, which provides the data to the end user device. If the data acceleration engine is on the host device, content from a datastore is served to the data acceleration engine as if the data acceleration engine were a client running the client application locally; therefore, latency normally associated with a network between the content datastore and the client device is eliminated. If the data acceleration engine is on the end user device and has received at least some data in advance of a relevant query, responses to the query also do not have latency associated with a network. The data acceleration engine can be implemented as a series of data acceleration engines between end user and host devices.

Claims

1. A method comprising:

installing a data acceleration interface on an end-user device;

installing an instance of a latency virtualization data accelerator on a computer;

configuring the data accelerator interface to connect to the instance of the latency virtualization data accelerator;

configuring the latency virtualization data accelerator to connect to a host endpoint;

receiving a request on behalf of an application associated with the end-user device;

identifying at the data accelerator a target and action associated with the request;

responding to the request from a relatively nearby location.

2. The method of claim 1, further comprising configuring the instance of the latency virtualization data accelerator to connect to second one or more instances of the latency virtualization data accelerator until the host endpoint is a next connection of a last of the second one or more instances.

3. The method of claim 1, further comprising sending the request to a host server when the data accelerator cannot independently respond.

4. The method of claim 3, further comprising receiving a response to the request from the host server.

5. A system comprising:

a means for installing a data acceleration interface on an end-user device;

a means for installing an instance of a latency virtualization data accelerator on a computer;

a means for configuring the data accelerator interface to connect to the instance of the latency virtualization data accelerator;

a means for configuring the latency virtualization data accelerator to connect to a host endpoint;

a means for receiving a request on behalf of an application associated with the end-user device;

a means for identifying at the data accelerator a target and action associated with the request;

a means for responding to the request from a relatively nearby location.

6. The system of claim 5, further comprising a means for configuring the instance of the latency virtualization data accelerator to connect to second one or more instances of the latency virtualization data accelerator until the host endpoint is a next connection of a last of the second one or more instances.

7. The system of claim 5, further comprising a means for sending the request to a host server when the data accelerator cannot independently respond.

8. The system of claim 7, further comprising a means for receiving a response to the request from the host server.

9. A method comprising:

installing a data acceleration interface on an end-user device;

configuring the data accelerator interface to connect to an instance of a latency virtualization data accelerator;

sending a request on behalf of an application associated with the end-user device;

receiving a response to the request from a relatively nearby location.

10. The method of claim 9, further comprising installing an instance of a latency virtualization data accelerator on a computer.

11. The method of claim 9, further comprising configuring the instance of the latency virtualization data accelerator to connect to another instance of the latency virtualization data accelerator until a host endpoint is a next connection.

12. The method of claim 9, further comprising configuring the latency virtualization data accelerator to connect to a host endpoint.

13. The method of claim 9, further comprising receiving a request on behalf of an application associated with the end-user device.

14. The method of claim 9, further comprising identifying at the data accelerator a target and action associated with the request.

15. The method of claim 9, further comprising sending the request to a host server when the data accelerator cannot independently respond.

16. The method of claim 9, further comprising responding to the request from a relatively nearby location.