Event-driven rule-based messaging system

Claim 3

The method of claim 1 wherein said translating step includes translating said completed rule into a byte-code stream forming said instruction stream.

Claim 4

Apparatus for connection to a network for sending messages from said apparatus and for receiving messages from at least one other network connected device, comprising: a processor processing messages received from said at least one other network connected device in accordance with at least one of a plurality of rules, said at least one of said plurality of rules comprising a plurality of fields including an event portion, a condition portion, and an action portion, said event portion specifying at least one of a plurality of types of occurrence that initiate evaluation of said condition portion, said condition portion specifying at least one condition which upon satisfaction initiates execution of an action specified in said action portion; at least one user interface in electrical communication with said processor and having at least one selectively alterable field that is altered by a selection made by a user, said selection providing information for at least one of said plurality of fields; a translation mechanism receiving said selection and incorporating said at least one of said plurality of fields to form at least one completed rule, said translation mechanism translating said at least one completed rule into a processor executable information stream; and an event mechanism operative to indicate the occurrence of at least one of said plurality of types of occurrence and processing event information upon occurrence of said plurality of types of occurrence, said event mechanism conveying said event information to said processor whereupon said processor executes said processor executable information stream to evaluate said condition portion and to initiate performance of said action upon satisfaction of said condition portion; wherein said event mechanism further comprises an event manager which further comprises at least one event queue, said event manager is operative to create event records in accordance with said plurality of events to store in said at least one event queue, and said event manager is operative to retrieve event records from said at least one event queue; and wherein said at least one event queue comprises a persistent event queue for storing events which persist across invocations of said rule processor and a non-persistent event queue for storing events that do not persist across invocations of said rule processor.

Claim 5

Apparatus for connection to a network for sending messages from said apparatus and for receiving messages from at least one other network connected device, comprising: a processor processing messages received from said at least one other network connected device in accordance with at least one of a plurality of rules, said at least one of said plurality of rules comprising a plurality of fields including an event portion, a condition portion, and an action portion, said event portion specifying at least one of a plurality of types of occurrence that initiate evaluation of said condition portion, said condition portion specifying at least one condition which upon satisfaction initiates execution of an action specified in said action portion; at least one user interface in electrical communication with said processor and having at least one selectively alterable field that is altered by a selection made by a user, said selection providing information for at least one of said plurality of fields; a translation mechanism receiving said selection and incorporating said at least one of said plurality of fields to form at least one completed rule, said translation mechanism translating said at least one completed rule into a processor executable information stream; and an event mechanism operative to indicate the occurrence of at least one of said plurality of types of occurrence and processing event information upon occurrence of said plurality of types of occurrence, said event mechanism conveying said event information to said processor whereupon said processor executes said processor executable information stream to evaluate said condition portion and to initiate performance of said action upon satisfaction of said condition portion; wherein said event mechanism further comprises an event manager which further comprises at least one event queue, said event manager is operative to create event records in accordance with said plurality of events to store in said at least one event queue, and said event manager is operative to retrieve event records from said at least one event queue; and wherein said at least one event queue comprises a persistent event queue for storing events which persist across invocations of said rule processor and a non-persistent event queue for storing events that do not persist across invocations of said rule processor.

Claim 6

The apparatus of claim 3 wherein said plurality of types of occurrence consists of: receiving said message at said apparatus, first time reading of said message received at said apparatus, filing of said message in a specified folder, recurring expiration of a specified period of time, occurrence of a specified date and time, starting up of said messaging system, shutting down of said messaging system, pushing of a button on said user input device, clicking of a mouse cursor on an icon of a display in said messaging system, initiation of communication between said messaging system and an external device, and dropping of an icon into a drop well on a display in said messaging system.

Claim 7

The apparatus of claim 3 wherein said at least one user interface includes a graphical user interface presenting a template to a rule editor operative to permit editing of at least one of said event portion, said condition portion and said action portion of said plurality of rules.

Claim 8

The apparatus of claim 5 wherein said rule editor permits editing of said condition and action portions of a rule having an event portion that specifies triggering upon occurrence of one of a specified date and time, receiving a message at said apparatus, recurring expiration of a period of time, starting up of said messaging system, and shutting down said messaging system.

Claim 9

The apparatus of claim 3 wherein said event mechanism comprises an event manager comprising an event kind filter operative as a mask to permit selectively of operation of said event manager.

Claim 10

The apparatus of claim 3 wherein said at least one event queue is a first in first out queue, subject to an event kind filter and prioritization of events stored thereon.

Claim 11

The apparatus of claim 3 wherein said persistent event queue is resident on a mass storage device.

Claim 12

The apparatus of claim 3 wherein said non-persistent event queue is resident in an apparatus resident memory.

Claim 13

The apparatus of claim 3 wherein said event manager synchronizes said persistent event queue and said non-persistent event queue to effect merger into a virtual single queue.

Claim 14

The apparatus of claim 3 wherein ones of said plurality of events stored in said persistent event queue are events selected from a group of occurrences consisting of: a new message, a read message, a filed message, a periodic event, and a timed event, and ones of said plurality of events stored in said non-persistent event queue are events selected from a group of occurrences consisting of: a manual event, a drag and drop event, an application startup, an application exiting, a button event, and an inter-application communication event.

Claim 15

The apparatus of claim 3 further comprising a first memory storing information for implementing said rule processor and further comprising at least one of a second memory and a disk and wherein said action invoked in accordance with said third portion of said respective rule is a launch action which swaps said information for implementing said rule processor out of said first memory and into said one of said second memory and said disk and swaps an application program into said first memory and upon completion of said application program said information for implementing said rule processor is swapped back into said first memory and said application program is swapped back to one of said second memory and said disk.

Claim 18

The method of claim 14, wherein said translating step includes translating said rule into a byte-code stream forming said instruction stream.

Claim 21

The method of claim 16 wherein said rule formulating step includes selecting for the event portion at least one of a plurality of occurrences within said apparatus and relating to said message.

Claim 22

The method of claim 17 wherein said selecting step includes selecting from a group of occurrences consisting of: receiving said message at said apparatus, first time reading of said message received at said apparatus, filing of said message in a specified folder, recurring expiration of a specified period of time, occurrence of a specified date and time, starting up of said messaging system, shutting down of said messaging system, pushing of a button on said user input device, clicking of a mouse cursor on an icon of a display in said messaging system, initiation of communication between said messaging system and an external device, and dropping of an icon into a drop well on a display in said messaging system.

Claim 23

The method of claim 16 wherein said rule formulating step includes specifying for the event portion at least one of a plurality of types of occurrence that initiate evaluation of said condition portion and specifying for the condition portion at least one condition which upon satisfaction initiates execution of an action specified in said action portion.

Claim 24

The method of claim 16 wherein said user input device comprises at least one graphical user interface presenting a template, and the step of inputting selected information includes filling in at least one blank in said template which provides said at least one data field and provides at least one of said event portion, said condition portion and said action portion of said at least one rule.

Claim 25

The method of claim 20 wherein said graphical user interface includes a customizable icon bar and said method further comprises triggering said at least one rule by interaction with said customizable icon bar.

Claim 26

The method of claim 20 wherein said inputting step includes interacting with said template and said formulating step includes constructing a rule including an event portion that specifies said rule for triggering upon occurrence of one of a specified date and time, receiving a message at said apparatus, recurring expiration of a period of time, starting up of said messaging system, and shutting down said messaging system.