Data-driven and plug-in defined event engine

• US 20070073739A1
• Filed: 09/29/2005
• Published: 03/29/2007
• Est. Priority Date: 09/29/2005
• Status: Active Grant

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Technology Corporation Miami Lakes FLA US
• Inventors: Jennings, Terry, Youngkin, Richard
• Granted Patent: US 7,509,654 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/4494 data driven
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

An event engine enables application developers to define finite state machines (FSMs) that they want to implement, via a data-driven approach as opposed to having to hardcode the FSMs. The event engine has three notable characteristics: computations may be associated with FSM state transitions, the set of computations that is associated with each transition is specified by data (illustratively an XML document), and the particulars of the computations are defined and handled by plug-ins, each with the same interface.

Claims

1. An apparatus comprising:

computer storage storing

an event engine that implements at least one finite state machine (FSM) comprising states and event-driven transitions between the states,

a specification expressed in a computer language, that specifies for each one of a plurality of the transitions a set of one or more actions to be performed upon occurrence of that transition, and

executable plug-ins whose execution implements the actions specified by the sets; and

a processor, coupled to the computer storage, that executes the stored event engine, and responds to occurrence of an event by causing the event engine to undergo one of the transitions that is driven by the event, and responds to occurrence of the undergone transition by executing those plug-ins that implement the actions of the set that corresponds to the undergone transition.

2. The apparatus of claim 1 wherein:

the specification is expressed in extensible markup language (XML).

3. The apparatus of claim 1 wherein:

the computer storage further stores a schema expressed in a computer language, that defines the specification; and

the processor uses the specification and the schema to construct the event engine.

4. The apparatus of claim 3 wherein:

the schema is expressed in either XSCHEMA or a DTD.

5. The apparatus of claim 1 wherein:

the processor executes a portion of the stored event engine to parse the specification to identify the transitions and the sets of actions for the transitions, the processor executes a corresponding plug-in for each action specified in each set to create a corresponding executable processing element, and associates the processing elements corresponding to each set with the corresponding transition; and

the processor executes another portion of the stored event engine to respond to occurrence of an event by causing the FSM to undergo the transition driven by the event and to execute the processing elements that are associated with the transition.

6. The apparatus of claim 5 wherein:

the specification is expressed in extensible markup language (XML);

the event engine comprises executable objects;

each plug-in comprises an executable object; and

each processing element comprises an executable object.

7. The apparatus of claim 6 wherein:

each executable object is an instance of a Java class.

8. The apparatus of claim 5 wherein:

a new processing element is added by adding a corresponding plug-in and referencing the plug-in in the specification.

9. The apparatus of claim 1 wherein:

each syntax element in the specification corresponds to a name of a corresponding one of the plug-ins.

10. The apparatus of claim 1 wherein:

each plug-in has a name that corresponds to a syntax element in the specification.

11. The apparatus of claim 1 wherein:

all of the plug-ins have a same interface.

12. A method comprising:

using a specification expressed in a computer language to initialize by a processor an executable event engine that implements at least one finite state machine (FSM) comprising states and event-driven transitions between the states, including specifying, for each one of a plurality of the transitions, a set of one or more actions to be performed upon occurrence of that transition;

providing executable plug-ins whose execution implements the actions;

in response to occurrence of an event, executing the event engine by the processor to cause the event engine to undergo one of the transitions that is driven by the event, and

in response to the undergone transition, executing by the processor those plug-ins that implement the actions of the set that corresponds to the undergone transition.

13. The method of claim 12 wherein:

the specification is expressed in extensible markup language (XML).

14. The method of claim 12 further comprising:

using a schema expressed in a computer language to define the specification; and

using the schema and the specification to construct the event engine by the processor.

15. The method of claim 14 wherein:

the schema is expressed in either XSCHEMA or a DTD.

16. The method of claim 12 wherein:

using comprises

parsing the specification by executing the event engine to identify the transitions and the sets of actions for the transitions

for each action specified in each set, executing the corresponding plug-in to create a corresponding executable processing element,

associating the processing elements corresponding to each set with the corresponding transition; and

executing plug-ins comprises

in response to the undergone transition, the event engine effecting execution of the processing elements that are associated with the transition.

17. The method of claim 15 wherein:

the specification is expressed in extensible markup language (XML); and

the event engine, the plug-ins, and the processing elements are implemented as executable objects.

18. The method of claim 17 wherein:

each executable object is an instance of a Java class.

19. The method of claim 15 further comprising:

adding a new processing element by adding a corresponding plug-in and referencing the plug-in in the specification.

20. The method of claim 12 wherein:

providing comprises

naming each plug-in with a name that corresponds to a syntax element in the specification.

21. The method of claim 12 wherein:

providing comprises

naming each syntax element in the specification with a name of a corresponding plug-in.

22. The method of claim 12 wherein:

providing comprises

defining all of the plug-ins to have a same interface.