Abstract execution model for a continuation-based meta-runtime

• US 20070239505A1
• Filed: 03/30/2006
• Published: 10/11/2007
• Est. Priority Date: 03/30/2006
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Schmidt, Robert, Sagar, Akash, Shukla, Dharma, Mehta, Mayank
• Application Number:
  US11/393,345
• Publication Number:
  US 20070239505A1
• Time in Patent Office: Days
• US Class Current: 705/8
• CPC Class Codes: G06F 2209/482 Application
• CPC Class Codes: G06F 9/485 Task life-cycle, e.g. stopping, restarting, resuming execution G06F9/4881 takes precedence
• CPC Class Codes: G06Q 10/0633 Workflow analysis

Abstract

Providing a workflow engine for virtualizing a managed execution environment. The workflow engine executes a workflow based on an automaton and methods associated therewith. The workflow engine captures continuations associated with the executing workflow to enable modeling of real-world processes.

Claims

1. A method for modeling real-world processes in a workflow, said method comprising:

defining an automaton for association with an activity in a workflow, said defined automaton having a set of states associated therewith;

defining one or more methods corresponding to each of the states in the automaton, said defined methods being associated with a data structure representing the activity;

executing, by a meta-runtime engine virtualizing a managed execution environment having a fixed functionality, a program fragment including the activity based on the defined automaton and the defined methods;

receiving a suspension signal directed to the executing program fragment;

determining continuation data associated with the program fragment responsive to the received suspension signal, said continuation data representing a continuation of the program fragment;

storing the determined continuation data in a memory area;

identifying one or more resources associated with the program fragment; and

releasing the identified resources.

2. The method of claim 1, further comprising:

receiving a resumption signal directed to the program fragment;

accessing the continuation data stored in the memory area;

loading the accessed continuation data into an execution memory associated with the execution machine; and

resuming execution of the program fragment based on the loaded continuation data.

3. The method of claim 1, wherein the execution machine operates to virtualize one or more of the following aspects of the managed execution environment:

a domain-specific op-code, a thread, a synchronization primitive, an execution machine, an object lifetime, a source format, an exception, a fault, fault propagation, and fault handling.

4. The method of claim 1, wherein defining the one or more methods comprises receiving, from a user, the methods for association with at least one of the states in the automaton associated with the activity.

5. The method of claim 1, wherein the automaton comprises one or more transition conditions defining transition of the activity through the set of states, and further comprising verifying the transition conditions prior to enabling the activity to transition through the states.

6. The method of claim 1, wherein one or more computer-readable media have computer-executable instructions for performing the method of claim 1.

7. A system for modeling real-world processes in a workflow, said system comprising:

a memory area for storing continuation data representing a continuation of a program fragment, said program fragment being associated with an activity in a workflow, said memory area further storing a meta-runtime engine for virtualizing a managed execution environment having fixed functionality, said meta-runtime engine having an execution machine representing an automaton having a set of states associated therewith, wherein one or more methods correspond to each of the states, wherein the methods are associated with a data structure representing the activity, said meta-runtime engine executing the program fragment based on the execution machine; and

a processor configured to execute computer-executable instructions for;

capturing the continuation data associated with the executing program fragment,

storing the captured continuation data in the memory area; and

releasing one or more resources associated with the program fragment.

8. The system of claim 7, wherein said capturing and said storing correspond to one or more of the following:

pickling the program fragment, evicting the program fragment, dehydrating the program fragment, and unloading the program fragment.

9. The system of claim 7, wherein the meta-runtime engine uses one or more of the following from the managed execution environment:

a thread, a stack, and a heap.

10. The system of claim 7, wherein the continuation data includes a program counter, said program counter identifying an exception handler next scheduled for execution.

11. The system of claim 7, wherein the memory area stores continuation data including an application state and a runtime state.

12. The system of claim 11, wherein the application state includes a list of activity objects.

13. The system of claim 11, wherein the runtime state includes a program counter

14. The system of claim 7, wherein the processor is further configured to execute computer-executable instructions for:

accessing the continuation data stored in the memory area;

loading the accessed continuation data into an execution memory associated with the meta-runtime; and

resuming execution of the program fragment based on the loaded continuation data.

15. The system of claim 14, wherein said loading and said resuming correspond to one or more of the following:

reactivation and restarting.

16. The system of claim 7, further comprising means for providing the meta-runtime and means for capturing a continuation associated with the program fragment.

17. The system of claim 7, further comprising an automaton received from a user, wherein the meta-runtime engine executes the program fragment based on the received automaton.

18. The system of claim 7, wherein the automaton comprises one or more transition conditions defining transition of the activity through the set of states, further comprising a first automaton associated with a first activity and a second automaton associated with a second activity, wherein a transition condition of the first automaton of the first activity is dependent on a current state of the second automaton of the second activity.

19. One or more computer-readable media having computer-executable modules for modeling workflow passivation, said modules comprising:

an automata module for defining an automaton for association with an activity in a workflow, said defined automaton having a set of states associated therewith and one or more methods corresponding to each of the states;

an execution machine module for executing a program fragment including the activity based on the automaton defined by the automata module; and

a continuation module for capturing, responsive to receipt of a suspension signal directed to the program fragment being executed by the execution machine module, continuation data of the program fragment and releasing a resource associated with the program fragment, said continuation data representing a continuation of the program fragment.

20. The computer-readable media of claim 19, further comprising a resumption module for restoring, responsive to receipt of a resumption signal directed to the program fragment being executed by the execution machine module, the continuation data for the program fragment captured by the continuation module, wherein the execution machine module resumes execution of the program fragment based on the restored continuation data.