System And Method For Loading Assets During Remote Execution

• US 20150350295A1
• Filed: 05/28/2014
• Published: 12/03/2015
• Est. Priority Date: 05/28/2014
• Status: Abandoned Application

• Current Assignee: Joel Solomon Isaacson
• Original Assignee: Joel Solomon Isaacson
• Inventors: Isaacson, Joel Solomon
• Application Number:
  US14/288,764
• Publication Number:
  US 20150350295A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 3/1454 involving copying of the display data of a local workstation or window to a remote workstation or window so that an actual copy of the data is displayed simultaneously on two or more displays, e.g. teledisplay
• CPC Class Codes: G09G 2360/06 Use of more than one graphics processor to process data before displaying to one or more screens
• CPC Class Codes: G09G 2370/022 Centralised management of display operation, e.g. in a server instead of locally
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/08 specially adapted for terminal emulation, e.g. Telnet
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

This invention generally relates to remote execution of computer applications. More specifically to a system and method of managing the transmission of assets needed for remote execution. The techniques described are particularly suited to graphical programs but have a wider domain of application.

Claims

1. A system for loading assets for the local thin client of a remote application determined by an analysis of previous application executions to reduce asset induced stalls and latency, comprising:

an executable program image designed to run a program on a local computing device;

an asset usage data base of previous executions;

a first computing device, comprising a first processor and running a first operating system, further comprising;

an application, running on the first processor, taken with modifications from said executable program image, said modifications comprising;

an extension stub for assembling the execution commands into a first data stream; and

a first transmitter for transmitting said first data stream assembled by said extension stub;

an asset loader, running on the first processor, for assembling a second data stream of predicted asset usage determined by the asset usage of previous executions in conjunction with the current asset usage of said running application; and

a second transmitter for transmitting said second data stream;

a second computing device, comprising a second processor and running a second operating system, further comprising;

a receiver for receiving the first and second data streams from said first computing device; and

a thin client, running on the second processor, for disassembling the two data streams, executing the disassembled commands and caching the loaded assets;

a communications channel for coupling said first and second transmitters of said first computing device to said receiver of said second computing device.

2. The system of claim 1 wherein said asset loader, loads all assets before said thin client begins execution of the disassembled commands.

3. The system of claim 1 wherein said asset loader, determines the predicted asset usage by the asset usage of one execution of the application in conjunction with the current asset usage of said running application.

4. The system of claim 1 wherein said asset loader, determines the predicted asset usage by the asset usage of the most recent completed execution of the application in conjunction with the current asset usage of said running application.

5. The system of claim 1 wherein said asset loader, determines the predicted asset usage by the conditional probabilities of asset usage computed from the asset usage of previous executions in conjunction with the current asset usage of said running application.

6. The system of claim 1 wherein:

said executable program image is an executable program image designed to run a graphical program on a local computing device;

said extension stub assembles graphical rendering commands into a first data stream; and

said thin client executes the disassembled graphical rendering commands.

7. The system of claim 6 wherein the graphical rendering commands are SKIA rendering commands.

8. The system of claim 6 wherein the graphical rendering commands are OpenGL rendering commands.

9. The system of claim 6 wherein the graphical rendering commands are Android Canvas.cpp rendering commands.

10. The system of claim 6 wherein the graphical rendering commands are Android OpenGLRenderer.cpp rendering commands.

11. A method for loading assets for the local thin client of a remote application determined by an analysis of previous application executions to reduce asset induced stalls and latency, comprising:

providing an executable program image of an application designed to run on a local computing device;

supplying an asset usage data base of previous executions;

modifying the executable program image of the application, to obtain a modified executable image of the application with the additional capabilities of;

assembling the execution commands into a data stream; and

transmitting the data stream to a separate distinct computing device;

running, on a first computing device, the modified executable program image of the application;

assembling, on the first computing device, by the modified executable program image of the program image, the execution commands into a first data stream;

transmitting, on the first computing device, by the modified executable program image of the application, the first data stream to a second computing device;

running, on the first computing device, an asset loader to generate a second data stream of predicted asset usage determined by the asset usage of previous executions in conjunction with the current asset usage of said running application;

transmitting, on the first computing device, by the asset loader, the second data stream to a second computing device;

receiving, on the second computer device, the first and second data streams;

disassembling, on the second computing device, the received data streams into a plurality of executing commands and assets;

caching, on the second computing device, the received assets; and

executing, on the second computing device, the disassembled execution commands.