Patent US5283856A successfully refreshed from Google Patents.
US5283856A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Event-driven rule-based messaging system
Assignee: Banyan Systems Inc
•
Filing: 1991-10-04
•
Granted: 1994-02-01
•
Expires: 2011-10-04
Abstract
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.
Inventors
- 👤 Kevin C. Gross
- 👤 Charles J. Digate
- 👤 Eugene H. Lee
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-25 11:10
CPC Classifications
H; H04; H04L; H04L51/00; H04L51/21; H04L51/212; G; G06; G06N; G06N5/00; G06N5/02; G06N5/022; G06Q; G06Q10/00; G06Q10/10; G06Q10/107; Y; Y10; Y10S; Y10S706/00; Y10S706/902; Y10S706/925
Claims Analysis
Total Claims: 20
Claim 1
Independent Claim
276 words
Apparatus for manipulating information in a rule based messaging system comprising: a rule processor for processing information at said apparatus in accordance with a plurality of rules; at least one 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 operative to indicate an occurrence of one of a plurality of events including physical occurrences relating to said information in said rule based system, said event generator including an event manager prioritizing said plurality of events and at least one event queue storing selected ones of said plurality of events for processing by said event manager; said rule processor being operative to compare each of said plurality of events to said first portion of said at least one of said rules to determine if said event indicia specifies said occurrence of one of said plurality of events which results in further processing of said at least one rule, and said rule processor being operative to evaluate said second portion of each of said plurality of rules for which there is a correspondence between a respective one of said plurality of events and said first portion of a respective rule to determine if said condition indicia specifies conditions that are true resulting in still further processing of said at least one rule; an action processor operative to invoke at least one action with respect to information being processed in accordance with said third portion of said respective rule upon satisfaction of said at least one condition specified n said second portion of said respective rule.
Claim 2
Dependent Claim
276 words
Apparatus for manipulating information in a rule based messaging system comprising: a rule processor for processing information at said apparatus in accordance with a plurality of rules; at least one 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 operative to indicate an occurrence of one of a plurality of events including physical occurrences relating to said information in said rule based system, said event generator including an event manager prioritizing said plurality of events and at least one event queue storing selected ones of said plurality of events for processing by said event manager; said rule processor being operative to compare each of said plurality of events to said first portion of said at least one of said rules to determine if said event indicia specifies said occurrence of one of said plurality of events which results in further processing of said at least one rule, and said rule processor being operative to evaluate said second portion of each of said plurality of rules for which there is a correspondence between a respective one of said plurality of events and said first portion of a respective rule to determine if said condition indicia specifies conditions that are true resulting in still further processing of said at least one rule; an action processor operative to invoke at least one action with respect to information being processed in accordance with said third portion of said respective rule upon satisfaction of said at least one condition specified n said second portion of said respective rule.
Claim 3
Dependent Claim
53 words
The apparatus of claim 1 wherein said one of said plurality of events is an event selected from a group of occurrences consisting of: a new message, a read message, a filed message, a periodic event, a timed event, an application startup, an application exiting, a button event and an inter-application communication event.
Claim 4
Dependent Claim
34 words
The apparatus of claim 1 further comprising a user interface to a rule editor operative to permit editing of said first portion, said second portion and said third portion of said plurality of rules.
Claim 5
Dependent Claim
39 words
The apparatus of claim 3 wherein said user interface comprises a form based interface permitting a rule designer to create rules and edit rules within a predetermined form by selecting at least some predetermined fields and specifying parameters therefor.
Claim 6
Dependent Claim
38 words
The apparatus of claim 3 wherein said user interface comprises a text based user interface permitting a rule designer to create and edit rules within a predetermined form by textually entering rules in accordance with a rule syntax.
Claim 7
Dependent Claim
64 words
The apparatus of claim 3 wherein said user interface comprises an open rule syntax and said apparatus further comprises an importation compiler permitting a rule designer to create and edit at least one externally designed rule and associated graphical user interface as an external file using an application external to said apparatus, said importation compiler facilitating compilation of said external file within said apparatus.
Claim 8
Dependent Claim
76 words
The apparatus of claim 6 wherein said structured rule editor permits a user to invoke said at least one externally designed rule via said associated graphical user interface and said structured rule editor synthesizes and invokes said at least one externally designed rule underlying said associated graphical user interface in response to said users interaction with said associated graphical user interface, whereby said externally designed rules and structured rule editor are substantially transparent to said user.
Claim 9
Dependent Claim
21 words
The apparatus of claim 6 wherein said external file is a text file for importing and compiling by said importation compiler.
Claim 10
Dependent Claim
27 words
The apparatus of claim 1 wherein said event manager comprises an event kind filter operative as a mask to permit selectivity of operation of said event manager.
Claim 11
Dependent Claim
48 words
The apparatus of claim 1 wherein 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.
Claim 12
Dependent Claim
31 words
The apparatus of claim 10 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 13
Dependent Claim
46 words
The apparatus of claim 10 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 14
Dependent Claim
17 words
The apparatus of claim 12 wherein said persistent event queue is resident on a mass storage device.
Claim 15
Dependent Claim
17 words
The apparatus of claim 12 wherein said non-persistent event queue is resident in an apparatus resident memory.
Claim 16
Dependent Claim
27 words
The apparatus of claim 12 wherein said event manager synchronizes said persistent event queue and said non-persistent event queue to effect merger into a virtual single queue.
Claim 17
Dependent Claim
122 words
The apparatus of claim 10 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, and 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.
Claim 18
Dependent Claim
36 words
The apparatus of claim 1 wherein one of said plurality of events is an inter-application communication and said rule processor comprises an event synthesizer which creates an event record from data received from an external application.
Claim 19
Dependent Claim
120 words
The apparatus of claim 1 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 20
Dependent Claim
38 words
The apparatus of claim 1 wherein said rule based system is a messaging system for connection to a network for sending, receiving and manipulating electronic messages sent to and received from at least one other network connected device.
References Cited (Backward Citations)
US4106060A
Cited
US4876711A
Cited
US4646235A
Cited
US4648061A
Cited
US4532588A
Cited
US4768144A
Cited
US4558413A
Cited
US4658370A
Cited
US4849878A
Cited
US4730259A
Cited
US4713780A
Cited
US4860352A
Cited
US4809219A
Cited
US4805207A
Cited
US4713837A
Cited
US4763277A
Cited
US4734931A
Cited
US4831526A
Cited
US4937036A
Cited
US4939507A
Cited
US4899136A
Cited
US4837798A
Cited
US4879648A
Cited
US4827418A
Cited
US4918588A
Cited
US4891766A
Cited
US4866634A
Cited
US4884217A
Cited
US4912648A
Cited
US4914590A
Cited
US4902881A
Cited
US4924408A
Cited
US4890240A
Cited
US5165011A
Cited
US4949278A
Cited
US4931933A
Cited
US4941170A
Cited
US5063523A
Cited
US5204939A
Cited
US5103498A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 1997-01-31 | 1997-08-02 | 1998-02-01 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2001-01-31 | 2001-08-02 | 2002-02-01 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2005-01-31 | 2005-08-02 | 2006-02-01 | $7700.00 | Window Closed / Lapsed |