Event-driven rule-based messaging system

• US 5,802,253 A
• Filed: 02/26/1996
• Issued: 09/01/1998
• Est. Priority Date: 10/04/1991
• Status: Expired due to Term

• Current Assignee: Unisys Corporation
• Original Assignee: Banyan Systems, Inc. (Banyan Corp.)
• Inventors: Digate, Charles J., Gross, Kevin C., Lee, Eugene H.
• Primary Examiner(s): Downs, Robert W.
• Application Number:
  US08/606,698
• Time in Patent Office: 918 Days
• Field of Search: 395/53, 395/51
• US Class Current: 706/47
• CPC Class Codes: G06N 5/022 Knowledge engineering; Knowledge acquisition
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: Y10S 706/925 Business

Abstract

A flexible, event driven and conditional rule based mail messaging system which can be transparently implemented for use in electronic mail applications. A rule mechanism is implemented having a "When-If-Then" event-driven, conditional, action-invoking paradigm or "triplet" which permits definition of a repertoire of events considered to be significant events upon which to trigger actions in the electronic mail messaging system. Each particular event may be associated with a specific mail message and/or rules to promote efficient mapping of messages, events and rules so that only rules associated with a specific event are invoked upon occurrence of the event. Only relevant rules, i.e. those associated with a satisfied event, need be further processed. A graphical user interface to a structured rule editor facilitates synthesis of rules by a user via a substantially transparent rule engine.

Claims

1. Apparatus for connection to a network for sending and receiving messages to and from said apparatus and at least one other network connected device in accordance with a plurality of rules, comprising:

a rule processor for processing messages at said apparatus in accordance with at least one of said plurality of rules;

each of said rules having a first portion consisting of an event indicia, a second portion consisting of a condition indicia, and a third portion consisting of an action indicia;

an event generator being operative to indicate an occurrence of one of a plurality of events;

said rule processor being operative to determine which of said rules have an event indicia corresponding to the occurrence of one of the plurality of events, to invoke only the rules for which the event portion corresponds to the occurrence of the event, and to evaluate the second portion of each invoked rule, to determine whether the condition indicia are met by the message;

an action processor operative to invoke an action with respect to any of said messages in accordance with said third portion of each of said invoked rules for which the condition indicia are met; and

an event manager having at least one event queue and operative to create event records in accordance with said plurality of events to store in said at least one event queue, and further operative to retrieve event records from said at least one event queue,

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 sadi rule processor.

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

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

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

5. The apparatus of claim 1 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;

an application startup, an application exiting, a button event and an inter-application communication event.