Intelligent network streaming and execution system for conventionally coded applications

• US 9,130,953 B2
• Filed: 11/18/2014
• Issued: 09/08/2015
• Est. Priority Date: 11/06/2000
• Status: Expired due to Fees

• Current Assignee: Numecent Holdings Incorporated
• Original Assignee: Numecent Holdings Incorporated
• Inventors: Arai, Daniel T., Panwar, Sameer, Benitez, Manuel E., Holler, Anne Marie, Shah, Lacky Vasant
• Primary Examiner(s): SHAW, PETER C
• Application Number:
  US14/547,052
• Publication Number:
  US 20150142880A1
• Time in Patent Office: 294 Days
• Field of Search: 726/9
• US Class Current: 1/1
• CPC Class Codes: G06F 21/1083 Partial license transfers
• CPC Class Codes: G06F 21/34 involving the use of external additional devices, e.g. dongles or smart cards
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 2463/101 applying security measures for digital rights management data processing systems or methods, specially adapted for commerce, e.g. marketing, shopping, billing, auctions or e-commerce G06Q30/00
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data

Abstract

An intelligent network streaming and execution system for conventionally coded applications provides a system that partitions an application program into page segments by observing the manner in which the application program is conventionally installed. A minimal portion of the application program is installed on a client system and the user launches the application in the same ways that applications on other client file systems are started. An application program server streams the page segments to the client as the application program executes on the client and the client stores the page segments in a cache. Page segments are requested by the client from the application server whenever a page fault occurs from the cache for the application program. The client prefetches page segments from the application server or the application server pushes additional page segments to the client based on the pattern of page segment requests for that particular application. The user subscribes and unsubscribes to application programs, whenever the user accesses an application program a securely encrypted access token is obtained from a license server if the user has a valid subscription to the application program. The application server begins streaming the requested page segments to the client when it receives a valid access token from the client. The client performs server load balancing across a plurality of application servers. If the client observes a non-response or slow response condition from an application server or license server, it switches to another application or license server.

Claims

1. A method comprising:

receiving, at a client device, a streaming application install block from a streaming application server for a streaming application executed at the client device;

generating file spoof data at the client device according to the streaming application install block;

beginning execution of the streaming application at the client device using the streaming application install block;

intercepting a request for a file used in continuing execution of the streaming application at the client device using the file spoof data;

determining if the file is located at the client device in a client stream cache;

if it is determined that the file is located in the client stream cache, satisfying the request for the file by;

retrieving the file from the client stream cache;

providing the file for continued execution of the streaming application at the client device;

if it is determined that the file is absent from the client stream cache, satisfying the request for the file by;

sending a request for the file to the streaming application server;

receiving at least one application file page including the file from the streaming application server;

providing the file from the at least one application file page for continued execution of the streaming application at the client device;

generating a prefetch history based on requests for application file pages made by the client device to the streaming application server;

sending the prefetch history to the streaming application server;

receiving from the streaming application server an additional application file page based on the prefetch history.

2. The method of claim 1, wherein the streaming application install block includes initial client stream cache content, the initial client stream cache content including at least one initial application file page used for beginning execution of the streaming application at the client device.

3. The method of claim 1, further comprising:

generating registry spoof data at the client device according to the streaming application install block;

spoofing a registry of the client device using the registry spoof data by returning a value of a registry entry called for in the execution of the streaming application at the client device.

4. The method of claim 1, further comprising:

receiving, at the client device, an access token unique to a particular user of the client device and the streaming application;

sending the access token to the streaming application server;

receiving the streaming application install block from the streaming application server if the access token is valid.

5. The method of claim 4, wherein the access token includes an expiration time, the method further comprising using the expiration time to determine when to request a new access token.

6. The method of claim 1, further comprising storing the at least one application file page in the client stream cache, the at least one application file page used to retrieve the file from the client stream cache for satisfying future requests for the file.

7. The method of claim 1, further comprising managing the client stream cache by purging application file pages stored in the client stream cache.

8. The method of claim 1, further comprising:

modifying the at least one application file page in the client stream cache;

marking the at least one application file page as dirty;

marking a plurality of application file pages in the client stream cache as clean if they remain unmodified as received from the streaming application server;

managing the client stream cache by purging the plurality of application file pages marked as clean from the client stream cache.

9. The method of claim 1, further comprising:

examining, at the client device, patterns of requests for application file pages made to the streaming application server;

prefetching application file pages from the streaming application server based on the patterns of requests for application file pages.

10. A system comprising:

a client device configured to receive a streaming application install block from a streaming application server for a streaming application executed at the client device;

a client application installer configured to begin execution of the streaming application at the client device using the streaming application install block;

a client file spoofer configured to;

generate file spoof data at the client device according to the streaming application install block;

intercept a request for a file used in continuing execution of the streaming application at the client device using the file spoof data;

a client cache manager configured to;

determine if the file is located at the client device in a client stream cache;

retrieve the file from the client stream cache, if it is determined that the file is located in the client stream cache;

provide the file from the client stream cache to the client application installer for continued execution of the streaming application at the client device, if it is determined that the file is located in the client stream cache;

send a request for the file to the streaming application server, if it is determined that the file is absent from the client stream cache;

receive at least one application file page including the file from the streaming application server, if it is determined that the file is absent from the client stream cache;

provide the file from the at least one application file page to the client application installer for continued execution of the streaming application at the client device, if it is determined that the file is absent from the client stream cache;

generate a prefetch history based on requests for application file pages made by the client device to the streaming application server;

send the prefetch history to the streaming application server;

receive from the streaming application server an additional application file page based on the prefetch history.

11. The system of claim 10, wherein the streaming application install block includes initial client stream cache content, the initial client stream cache content including at least one initial application file page used for beginning execution of the streaming application at the client device.

12. The system of claim 10, further comprising a client registry spoofer configured to:

generate registry spoof data at the client device according to the streaming application install block;

spoof a registry of the client device using the registry spoof data by returning a value of a registry entry called for in the execution of the streaming application at the client device.

13. The system of claim 10, further comprising a client license manager configured to:

receive an access token unique to a particular user of the client device and the streaming application;

send the access token to the streaming application server, the access token used to determine whether to send the streaming application install bock to the client device.

14. The system of claim 13, wherein the access token includes an expiration time, the client manager further configured to use the expiration time to determine when to request a new access token.

15. The system of claim 10, wherein the client cache manager is further configured to store the at least one application file page in the client stream cache, the at least one application file page used to retrieve the file from the client stream cache for satisfying future requests for the file.

16. The system of claim 10, further comprising a local copy-on-write file system configured to:

modify the at least one application file page in the client stream cache;

mark the at least one application file page as dirty;

mark a plurality of application file pages in the client stream cache as clean if they remain unmodified as received from the streaming application server;

manage the client stream cache by purging the plurality of application file pages marked as clean from the client stream cache.

17. The system of claim 10, wherein the client cache manager is further configured to:

examine patterns of requests for application file pages made to the streaming application server;

prefetch application file pages from the streaming application server based on the patterns of requests for application file pages.

18. A system comprising:

a means for receiving at a client device a streaming application install block from a streaming application server for a streaming application executed at the client device;

a means for beginning execution of the streaming application at the client device using the streaming application install block;

a means for generating file spoof data at the client device according to the streaming application install block;

a means for intercepting a request for a file used in continuing execution of the streaming application at the client device using the file spoof data;

a means for determining if the file is located at the client device in a client stream cache;

a means for retrieving the file from the client stream cache, if it is determined that the file is located in the client stream cache;

a means for providing the file from the client stream cache to a client application installer for continued execution of the streaming application at the client device, if it is determined that the file is located in the client stream cache;

a means for sending a request for the file to the streaming application server, if it is determined that the file is absent from the client stream cache;

a means for receiving at least one application file page including the file from the streaming application server, if it is determined that the file is absent from the client stream cache;

a means for providing the file from the at least one application file page to the client application installer for continued execution of the streaming application at the client device, if it is determined that the file is absent from the client stream cache;

a means for generating a prefetch history based on requests for application file pages made by the client device to the streaming application server;

a means for sending the prefetch history to the streaming application server;

a means for receiving from the streaming application server an additional application file page based on the prefetch history.