Method and system for predictive loading of software resources
A method for predictive loading of software resources in a web application includes predicting a future state of the web application, determining the software resources required by the first predicted future state, and loading the software resources required by the first predicted future state. Determining that future predicated state further includes determining an associated probability for each possible future state in the first set of possible future states, identifying, from the first set of possible future states, a first predicted future state with the highest associated probability, and predicting a first set of possible future states based on a current state, run-time application context, and either use case data or historical application usage data.
1. A method for predictive loading of software resources in a web application, comprising:
determining at least one predicted future state of the web application, wherein determining the at least one predicted future state comprises:
predicting a first set of possible future states based on:
a current state;
run-time application context, wherein the run-time application context comprises user privilege information; and
use case data, wherein use case data comprises state transition information associated with a pre-defined use case;
determining an associated probability for each possible future state in the first set of possible future states;
identifying, based on the user privilege information, that a first possible future state is not accessible;
removing the first possible future state from the first set of possible future states; and
identifying, from the first set of possible future states, a first predicted future state with the highest associated probability;
determining a software resource required by the first predicted future state; and
loading the software resource required by the first predicted future state.
2. The method of claim 1 , wherein the software resource is at least one selected from the group consisting of:
code comprising executable instructions,
content, and
services.
3. The method of claim 1 , wherein after loading the software resources required by the first predicted future state, the method further comprises:
predicting a second set of possible future states based on historical usage analytics data;
determining an associated probability for each possible future state in the second set of possible future states;
identifying, from the second set of possible future states, a second predicted future state, wherein the second predicted future state is the possible future state in the second set of possible future states with the highest associated probability;
determining software resource required by the second predicted future state; and
loading the software resource required by the second predicted future state.
4. The method of claim 3 , wherein determining the associated probability for each possible future state in the second set of possible future states comprises:
identifying, in the historical usage analytics data, occurrences of the current state of the web application;
determining, from the occurrences of the current state in historical usage analytics data, the second set of possible future states; and
determining, for each possible future state in the second set of possible future states, the associated probability.
5. The method of claim 4 , wherein determining, for each possible future state in the second set of possible future states, the associated probability comprises:
for a possible future state in the second set of possible future states, determining a ratio between a cardinality of state transitions from the current state of the web application to the possible future state and a cardinality of all state transitions originating from the current state.
6. The method of claim 1 , wherein the use case data comprises state transition information including a plurality of pre-defined use cases for the web application.
7. The method of claim 1 , wherein determining the associated probability comprises determining a cardinality of matching states between the use case data and a current session of the web application.
8. A non-transitory computer readable medium (CRM) storing instructions for predictive loading of software resources in web applications, comprising:
determining at least one predicted future state of a web application, wherein determining the at least one predicted future state comprises:
predicting a first set of possible future states based on:
a current state;
run-time application context, wherein the run-time application context comprises user privilege information; and
use case data, wherein use case data comprises state transition information associated with a pre-defined use case;
determining an associated probability for each possible future state in the first set of possible future states;
identifying, based on the user privilege information, that a first possible future state is not accessible;
removing the first possible future state from the first set of possible future states; and
identifying, from the first set of possible future states, a first predicted future state with the highest associated probability;
determining a software resource required by the first predicted future state; and
loading the software resource required by the first predicted future state.
9. The non-transitory CRM of claim 8 , wherein the software resource is at least one selected from the group consisting of:
code comprising executable instructions,
content, and
services.
10. The non-transitory CRM of claim 8 , wherein after loading the software resources required by the first predicted future state, the instructions further comprise:
predicting a second set of possible future states based on historical usage analytics data;
determining an associated probability for each possible future state in the second set of possible future states;
identifying, from the second set of possible future states, a second predicted future state, wherein the second predicted future state is the possible future state in the second set of possible future states with the highest associated probability;
determining a software resource required by the second predicted future state; and
loading the software resource required by the second predicted future state.
11. The non-transitory CRM of claim 10 , wherein determining the associated probability for each possible future state in the second set of possible future states comprises:
identifying, in the historical usage analytics data, occurrences of the current state of the web application;
determining, from the occurrences of the current state in historical usage analytics data, the second set of possible future states; and
determining, for each possible future state in the second set of possible future states, the associated probability.
12. A system for predictive loading of software resources in web applications, comprising:
a computer processor;
a web application executing on the computer processor; and
a state transition prediction module of the web application, configured to:
determine at least one predicted future state of the web application, wherein determining the at least one predicted future state comprises:
predicting a first set of possible future states based on:
a current state;
run-time application context, wherein the run-time application context comprises user privilege information; and
use case data, wherein use case data comprises state transition information associated with a pre-defined use case;
determining an associated probability for each possible future state in the first set of possible future states;
identifying, based on the user privilege information, that a first possible future state is not accessible;
removing the first possible future state from the first set of possible future states; and
identifying, from the first set of possible future states, a first predicted future state with the highest associated probability;
determine a software resource required by the first predicted future state; and
load the software resource required by the first predicted future state.
13. The system of claim 12 , wherein the software resource is at least one selected from the group consisting of:
code comprising executable instructions,
content, and
services.
14. The system of claim 12 , wherein after loading the software resources required by the first predicted future state, the state transition prediction module of the web application is further configured to:
predict a second set of possible future states based on historical usage analytics data;
determine an associated probability for each possible future state in the second set of possible future states;
identify, from the second set of possible future states, a second predicted future state, wherein the second predicted future state is the possible future state in the second set of possible future states with the highest associated probability;
determine a software resource required by the second predicted future state; and
load the software resource required by the second predicted future state.
15. The system of claim 14 , wherein determining the associated probability for each possible future state in the second set of possible future states comprises:
identifying, in the historical usage analytics data, occurrences of the current state of the web application;
determining, from the occurrences of the current state in historical usage analytics data, the second set of possible future states; and
determining, for each possible future state in the second set of possible future states, the associated probability.