Event-driven rule-based messaging system

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.

Description

FIELD OF THE INVENTION

The present invention relates to an electronic mail messaging system and in particular to a rule based system and rule editor for directing messages in the electronic mail messaging system.

BACKGROUND OF THE INVENTION

Rule-based systems are known which use rules, typically "If-Then" sequences, to automatically process or "filter" signal groups transmitted as messages in a computer environment or network. Such systems are generally implemented, via object oriented programming techniques, in the context of electronic mail facilities. The application of rules or the occurrence of an action is triggered upon selected criteria being met, i.e. matching of electronically established criteria occurring in a received electronically mailed message. Upon the occurrence of a received and stored mail message satisfying specified conditional criteria set forth in the "If" portion of the statement, such as the mail message being addressed from a selected addressor, the "THEN" portion of the rule or rule set will invoke some action, in some instances directing signal groups comprising the mail message to a designated file or user area. In known systems, the "If-Then" sequences can be constructed using connectors and Boolean operators resulting in relatively complex combinations within and among fields of the sequence.

In one system (ISCREEN), described in A Rule-Based Message Filtering System by Stephen Pollock published in ACM Transactions on Office Information Systems, Vol. 6, No. 3, July 1988, pages 232-254, electronic text mail messages are screened, decisions are made and actions taken in accordance with rules defining procedures typically implemented as part of the manual processing of information generated in an office. A user invokes a rule editor to create rules for providing instructions to the system. The rules include conditions which describe values associated with attributes of a mail message, such as who the mail message is from and/or what it is about. The rules created by the user further include actions which describe what is to be done with mail messages that match the user specified conditions. Typical actions, which in this known implementation are functions of the underlying mail messaging system, include forwarding, filing and deleting the mail message(s).

A special purpose editor invoked by the user to define rules, disadvantageously requires that a specific rule format be learned and adhered to by the user. Specified rules can only be triggered on matching mail message criteria and cannot be triggered based upon the timing of an event, such as the expiration of a time interval. Further, the system requires extensive parsing of user-specified instructions to detect instruction conflicts, completeness and consistency.

Another known system (Object Lens), disclosed in Object Lens: A `Spreadsheet` for Cooperative Work, by Kum-Yew Lai et al published in ACM Transactions on Office Information Systems, 1988, provides various templates for various semi-structured objects which users define and modify to represent information about, among other things, people, tasks, products, and mail messages. Users can create displays to summarize selected information from the semi-structured objects in table or tree formats. A template-based user interface, permits users to interface with an object-oriented data base to see and change objects via interaction with familiar forms or templates. The user, via the templates, constructs conditional rules comprising "If" conditions, which upon satisfaction "Then" result in user-specified actions taking place in accordance with the specified rule(s). The "If-Then" rules can be used to group objects together and can be automatically invoked as "semi-autonomous agents" or methods invoked by the system without user intervention, specified by the user to process information in different ways. Users can create these rule-based agents to be triggered upon the condition of an occurrence, in particular upon receipt of a new mail message. Upon the "If" portion of the rule being satisfied, a further set of rules is applied to a specified collection of objects, semi-autonomously (i.e., automatically but under control by a human user).

However, limited flexibility is provided by this system which only tests occurrences as a conditional ("If") component of a rule. Considerable complexity and inefficiency is also inherent in the system which requires compound conditions ("Ifs") for event triggering, because in addition to every mail message being tested for an occurrence or event which satisfies a first rule, the mail messages must be further tested for other criteria to be satisfied before invoking the action ("Then") portion of the rule.

In addition to having limited event driven capability that results in inflexible and inefficient processing of mail messages, and requiring a user to learn fairly complex rule design and construction schemes, known systems do not have a capability to invoke or "launch" known applications via an event selective rule mechanism.

SUMMARY OF THE INVENTION

The present invention provides a flexible, efficient, event-driven and conditional rule-based system which can be transparently implemented for use, e.g. in electronic mail applications.

A rule mechanism is implemented having a "When-If-Then" event-driven, conditional, action-invoking paradigm or "triplet" which facilitates definition of a repertoire of events considered to be significant events upon which to trigger actions in a system such as an electronic mail messaging system. Particular events may be associated with a specific mail message, and/or rule(s), to promote efficient mapping of messages, events, and rules, so that only rules which monitor a specific event are invoked upon occurrence of the event. Thus, only mail messages and relevant rules (i.e., those having an associated satisfied event) need be further processed.

Further, a graphical interface is presented to the user to permit "point and click" or cursor controlled synthesis or design and invocation of an underlying structured rule editor or rule set(s), via a substantially user transparent rule mechanism. The user can invoke structured rules and rule sets without learning a complex rule language and editor.

Still further, the rule mechanism has a capability to permit a user to invoke or "launch" a concurrent process or application from within the event selective rule mechanism. The action or THEN portion of a rule can specify a launch verb which provides a springboard to off-the-shelf application software, such as a spreadsheet program, word processor or the like, permitting the user to launch automatically into the application via the rule mechanism and to automatically re-enter the messaging system from the launched application.

Features of the invention include a simple user interface to an efficient, powerful and sophisticated rule based messaging system. While simple user interfaces are available which synthesize rules via the underlying structured rule editor, rule syntax permits external text editors to be used to create interfaces for importation into the system. Other features and aspects of the invention are explained in BEYONDMAIL Electronic Mail for Productive Workgroups: Rule Book; User Guide; and Administration Guide, which are incorporated herein by reference.

DESCRIPTION OF THE DRAWING

These and other features and advantages of the present invention will become more apparent in light of the following detailed description of an illustrative embodiment thereof, as illustrated in the accompanying drawing of which:

FIG. 1 is a simplified block diagram of components of a rule based message handling system;

FIG. 2 is a diagrammatic representation of a client-server implementation of the rule based message handling system of FIG. 1;

FIGS. 3a-3h are illustrations of data structures for implementing an event component of a rule in the rule based messaging system of FIG. 1;

FIG. 3i and 3j are a block diagram of an inter-application communication event data structure and associated block diagram, respectively;

FIG. 4 is a diagrammatic representation of an event selective rule mechanism of the message handling system of FIG. 1;

FIG. 5 is a block diagram of the event mechanism of the rule based message handling system of FIG. 1;

FIG. 6 is a system overview block diagram of the rule based message handling system of FIG. 1;

FIG. 7 is a graphic user interface for a tickle feature implementing a structured rule editor;

FIG. 8 is a diagrammatic representation of a tickler graphical user interface and associated event data structure;

FIG. 9 is a block diagram of the rule based system of FIGS. 4 and 5 effecting a tickler feature as depicted in FIG. 8;

FIGS. 10a and 10b are illustrations of form mode and text mode formats for creating rules, respectively;

FIG. 10c is a block diagram of an external structured rule editor mode for rule creation; and

FIG. 11 and 11a are a graphical user interface and underlying structured rule, respectively, for an "out of the office function".

DETAILED DESCRIPTION

A rule based messaging system, as illustrated in FIG. 1, is implemented in computer based systems and typically in networked personal computer systems. The personal computer system, such as an IBM PC or other computer, includes an operating system, such as Novell Netware, upon which an electronic mail application such as MHS is installed to facilitate mail message processing among computers connected via the network facilities. A rule based messaging mechanism 10, comprises a rule mechanism and interface 12 to the electronic mail application. The rule based messaging mechanism 10 is accessible to a user through a user interface 14, such as templates as known in the art or through a graphical user interface as described hereinafter.

In one embodiment, as illustrated in FIG. 2, a client-server architecture is implemented. Various rule mechanism resources 13 and the user interface 14 are served by a messaging transport access layer 16. In conjunction with an integral electronic mail driver component 18 available to the rule based messaging mechanism 10, the message transport access layer 16 serves as an application program interface which integrates the rule mechanism 10 with the particular electronic mail application running with the network software, facilitating mail message access between the rule mechanism resources 13 and the electronic mail application.

The rule mechanism resources 13 implement actions on a mail message (i.e. cause something to be done) based upon an evaluation of a condition, effected upon the occurrence of a particular event. The structure of every rule, whether user specified or invoked under a graphical user interface, can be diagrammed as:

WHEN(event).fwdarw.IF(condition).fwdarw.THEN(action). The WHEN event field permits specification of classes of occurrences and/or various types of mail messages which will invoke the rule defined in the corresponding IF(condition).fwdarw.THEN(action) fields of a specified rule. Events trigger the processing of conditions and actions and enable efficient mapping of messages, events and rules.

The events may be a function of a timer integral with the system, or a function of a folder destination of a particular message, or a function of the form of a mail message according to the mail messaging system. Various events can be specified to trigger evaluation of a condition and invocation of corresponding actions. Preferably event types will accommodate respective operands to permit further specification of relevant messages to be considered for rule invocation, to further enhance the efficiency of the rule mechanism. Event types are created and processed by an event manager using a common set of data structures and routines.

A NEW message event type (WHEN NEW), is used to specify application of rules to a new message which has been received by the electronic mail application over a network mail transport agent (MTA) and placed in a message store. Upon receipt of a message packet from the MTA over the network interface (i.e. a NEW message), a NEW message event is created by the event manager, according to a data structure illustrated in FIG. 3a. The NEW message event is created indicating the date and time of receipt of the new message. A message identifier or unique identifier (UID) is included in the NEW event to point to the message (which may be stored using the host operating system filing facilities) associated with the NEW message event. The NEW message event is stored to an event queue to be processed as discussed hereinafter.

Upon specification for rule invocation, the NEW event can be further limited by including operands which specify a particular kind or FORM of message for application of the corresponding rule. The ultimate functionality is that a rule is triggered upon receipt of a message of a particular FORM in an Inbox or other new message initial repository.

A rule can be triggered in accordance with the event portion of the rule mechanism, when a message has been read for the first time, by specifying a WHEN READ event as a limitation of a rules evaluation and application. A READ message event is created according to the data structure illustrated in FIG. 3b. In addition to the date and time when the message was first read, the READ message event is created by the event manager to have a unique identifier for the associated message. The UID includes specification of a folder, as the message may have been moved previously and reside in a folder other than the Inbox. A WHEN READ limited rule can also be further limited by specification of operands to limit the FORM of the message to which the rule is applied and to limit the application of the rule to messages in a particular FOLDER.

Similarly, a rule can be triggered upon a message being FILED, according to a FILED message event having an associated data structure as illustrated in FIG. 3c, which is substantially the same as the data structure for the READ message event. Optionally, as with the hereinbefore described WHEN NEW and WHEN READ limitations, the WHEN FILED rule can be limited for application to a message of a particular FORM and/or destined for a particular FOLDER.

Rule application limiting message kinds, i.e. FORMs of messages, which can be used to further limit the application of rules when the event occurrence specified is NEW, READ or FILED, is limited by the repertoire of forms (and folders) available in the messaging system. In the present illustrative embodiment, the WHEN NEW, READ and FILED event limitations can be further limited, to limit application of rules to message kinds of a FORM supported by conformance to an MHS system protocol and/or those provided for in the present mail messaging application. Message forms, which are extensible and which can be specified for further limitation of the invocation of corresponding rules include: memo, phone message, reply and request form, among others. Default settings can be established for limitations on events so that operands need not be specified.

Timed events can be used to trigger a rule or rules limiting invocation of the rule mechanism. A timer is integrated with the present rule based messaging system and used to implement PERIODIC, i.e. timed, or tickler rules. Periodic occurrence triggers corresponding rules EVERY once an hour/day/week/month, as specified in the event portion of the rule. A PERIODIC event data structure, illustrated in FIG. 3d, does not point to a message, but has a rule pointer or tag which points to a rule in a rule data base for invocation of an action or sequence of actions. The periodic occurrence is limited to a specified TIMER time by providing a TIMER operand.

A TIMER event is defined in a data structure as illustrated in FIG. 3e which includes a date and time when the event is to get noticed. A UID identifies a message associated with the event and a rule pointer points to a rule in the rule data base which contains an action or sequence of actions to be taken on the message. Ticklers can be implemented in the present rule based messaging system using TIMER events. For example, the system can be instructed to move a message to a "today" folder on a specific date.

Messaging system application start-up and exiting can be specified as events to trigger rules, in accordance with data structures illustrated in FIGS. 3f and 3g. STARTUP and EXITING events are only initiated upon an event queue search at the respective occurrence. Neither occurrence requires nor permits the specification of an operand. The STARTUP event is queued and invokes corresponding rules when the messaging system processes the in-queue STARTUP event at messaging system application start-up. Similarly, the EXITING event causes rules, which match the event type, to be invoked when the messaging system is being exited.

An event called a "BUTTON" event is created to sense user interface actions, such as mouse pointing and clicking. A BUTTON event type, having a data structure as illustrated in FIG. 3h, includes a user interface management system parameter, which is specified to invoke an associated rule when a user interface management system, as known in the art, senses the event occurrence or parameter specified. The data structure includes a pointer to the associated rule or rule set which contains the conditional tested and action executed upon occurrence of the BUTTON event.

Events, according to the present invention, can be implemented to invoke IF.fwdarw.THEN sequences upon external occurrences. As illustrated in FIG. 3i and 3j, an event can be synthesized based on inter-application communication (IAC). Facilities are known, such as Microsoft's Windows Dynamic Data Exchange (DDE), which permit the exchange of data between disparate applications programs. Other applications, such as any client application 70 can exchange data or parameters with a DDE interface 72 which receives the data for introduction to the messaging system 10. An event synthesizer 74 component of the event manager, responsive to the DDE, creates an IAC event according to the data structure illustrated.

The data structure, FIG. 3i, of the IAC event synthesized, uses an event record which includes client information, i.e. identification of the other application 70 in communication with the DDE 72 and the event mechanism. The other application 70 typically will pass parameters to the DDE 72 which will be included in the IAC event data structure. Further, the IAC event synthesized is processed by the event manager 24 with other events as discussed hereinafter. An associated rule in the rule data base will be found and will invoke action(s) upon the occurrence of the IAC event being processed and satisfying specified conditional criteria.

The present messaging system, illustrated in FIG. 4, permits users 30 accessing the messaging application 10 through a network mail transport agent or a user interface 32 to use a rule editor 34 or structured rule editor 34, (discussed hereinafter), respectively, to invoke the event mechanism 36 which facilitates efficient mapping of messages, events and rules and assures that only relevant rules and associated messages are further processed by a rule engine 38. Selected rules 40 are then applied to selected message objects 42 to quickly and efficiently control the flow of information for the user of the mail messaging application.

The event mechanism, illustrated in FIG. 5, facilitates the flexible selectivity and efficient processing of rules. The event mechanism comprises an event manager 24 which provides an application program interface for producing and storing events in accordance with the data structures discussed hereinbefore. The events described consist of two basic types, persistent and non-persistent events. Certain event kinds, including STARTUP and EXITING events, are short lived non-persistent events which will not persist across instances of messaging system application execution. Non-persistent events are implemented using a memory based technique, as illustrated in FIG. 5, in which a queue of event records 20 is maintained in memory via an in-memory event manager 22 component of the event manager 24. The non-persistent event records are fetched from and posted to the non-persistent queue 20. The in-memory event manager 22 management of the non-persistent queue assures that the in-memory non-persistent queue 20 can grow and shrink as needed.

Persistent events, such as FILED, READ, NEW, PERIODIC, and TIMER, which are likely to persist across messaging system application invocations, require a separate storage mechanism. Persistent events are stored in a persistent event queue 28 preferably maintained on disk which is accessed only by a persistent event manager 26 component of the event manager 24.

Event users or clients, such as the messaging transport access layer 16 invoking the event manager 24 via a NEW message event or such as the user interface invoking the event manager 24 via a STARTUP or EXITING event, call the event manager 24 to create events and to fetch events in the system as illustrated in the system overview of FIG. 6. The event manager 24 centralizes policy effecting event creation, consumption and storage, while minimizing the burden placed on clients.

When a new message packet is received over a network at a host having the mail messaging system according to the invention, the network informs the electronic mail application program interface (e-mail API) 18 that there is a packet of information. The e-mail API informs the messaging transport access layer 16 that there is a packet of information comprising a message. The messaging transport access layer 16 receives the information and stores the message, via the host operating system 50, as a file in a message store using the file services of the host. The message access transport layer 16 also calls the event manager 24 which creates a NEW message event in accordance with the data structure discussed hereinbefore, having the date and time received and a UID identifying the message stored. The event manager 24 invokes the persistent event manager 26 which stores the created NEW message event in the persistent event queue 28 for processing by the event manager substantially on a first-in first-out basis.

Other persistent events, i.e. FILED, READ, PERIODIC and BUTTONS, are similarly created and queued via the event manager 24 and persistent event manager 26, to be pulled off the first-in first-out persistent event queue 28 to be processed. However, in these cases the user interface 14 is the client of the event manager 24. The user interface 14, in conjunction with a user interface management system 52 (UIMS) as known in the art, monitors occurrences such as the keystrokes or buttons indicative of filing, reading or otherwise manipulating a message, and invokes the event manager 24 and persistent event manager 26 accordingly. In the case of the user interface 14 invoking the event manager 24 to create an event such as a non-persistent STARTUP or EXITING event, the in-memory event manager 22 is invoked which maintains an in-memory first-in, first-out non-persistent event queue 20. Created events are added at the first-in end of the queue 20 and existing events being processed by the event manager 24 are fetched from the first-out end of the queue 20.

The event manager 24 interfaces with the rest of the system and initializes the in-memory (non-persistent) event queue 20, locates and opens the disk based persistent event queue 28 and synchronizes the non-persistent and persistent queues, effectively merging the queues. The event manager 24 centralizes event policies and transparently implements event prioritization. When an event record is fetched by the event manager 24 for processing, the events are fetched from the queues in accordance with a fixed prioritization, subject to an event-kind filter 54. The event record, used for both posting and fetching events from the queue, comprises various fields including bits indicative of event kind, date/time when the event was posted, type of object for which the event was created and a variant field permitting a memory based non-persistent event to hold a handle to an appropriate object or permitting a disk based persistent event to hold an identifier for an object, e.g. a message in the message store maintained in host memory. The event-kind filter 54 effects an event or bit mask which permits the event manager 24 to fetch events of a certain kind from the queues, limiting the kind of events sought.

Events are fetched from the queue(s) using a priority scheme. Among the events enabled by the event mask (event-kind filter), the oldest event of the highest priority is returned to the event manager for processing first. Highest priority is given to STARTUP and EXITING events, while lesser priority is given the persistent events. Alternative event prioritization is possible as the primary consideration for prioritization is subtleties of the application design.

As indicated and illustrated hereinbefore, the ultimate functionality of the WHEN.fwdarw.IF.fwdarw.THEN rule based application is that: under the control of the user interface 14, the occurrence of events causes selected conditions to be tested; when satisfied, the conditions cause actions to be taken; and actions in turn may lead to the occurrence of new events. Little or no understanding of the rule mechanism and its rule language is needed by the ultimate user where a structured rule editor is designed and implemented through a graphical user interface. Structured rule editors are designed and implemented by a designer or programmer familiar with a WHEN.fwdarw.IF.fwdarw.THEN associated rule syntax. The structured rule editor implements rules so that the rule syntax and constructs are not presented to the user (i.e. the rule language, and editor, is transparent to the ultimate user), but appear to be embedded in the system beneath the graphical user interface which affects them.

An illustrative embodiment of one such structured rule editor is implemented in the context of a system resident tickler feature which enables the user to deal with received messages at a later time specified by the user. The system processes the message(s) and event(s) through automatic invocation of the rule mechanism so that the user is presented with the message to deal with at an appropriate time. Rule mechanism invocation is effected by the user through a graphical user interface.

The user selects the automatic tickle feature during reading, creating, replying or forwarding a message. A graphic user interface, as illustrated in FIG. 7, is presented having various fields available for the user to specify, which effect construction of a rule or rules according to the WHEN.fwdarw.IF.fwdarw.THEN construct discussed hereinbefore. The user is prompted by the tickler interface to specify a date and time on which the tickler will take action and to specify a folder into which the message is to be moved at the specified date and time. Optionally, the user can provide a textual reminder or note relating to the tickled message.

The user specified information entered into the tickler interface for the associated message, is used by the user interface 14 to construct a data structure, illustrated in FIG. 8, which defines an action to be invoked upon occurrence of the event, i.e. the tickle date and time. The messaging application 10 as discussed hereinbefore and illustrated in FIG. 9, processes the tickler data structure, including a pointer to the appropriate rule(s) or rule set(s), to construct the rule. The rule, including event, condition and action, is synthesized by the structured rule editor. The rule constructed by the user interface 14, via the structured rule editor 34', is stored in the rule data base 60 accessible on the host operating system 62. The rule constructed by the user interface has an event associated with it, in this case a TIMER event, which is stored by the event manager 24 in the persistent event queue 28 on disk. The event record stored in the queue points to the associated message, stored in the message store via the message access transport layer 16 and host operating system facilities 62.

When the event occurs (i.e. the specified tickler date and time arrive), the event manager 24 fetches the event from the event queue 28 and passes it to the user interface 14, which polled for the occurrence of the event(s). The user interface 14 passes the event to the rule engine 38. The rule engine 38, receiving the event data structure, illustrated in FIG. 8, looks up the event's corresponding condition-action in the rule data base 60 through the host operating system. The rule engine 38 also calls the message store via the message transport access layer 16 and host operating system, to retrieve the message associated with the event. The rule engine 38, given the event occurrence and having the rule and associated message, then executes the rule by effecting performance of the specified action, which in the case of the tickler is an action generated by the structured rule editor to move the message to the folder specified by the user in the tickler graphical user interface.

Structured rule editors can be designed within the system to reference a message (as with the tickler), or the rule syntax can be adhered to in structured rule editor designs using known external text editors (which obviously cannot reference a specific system resident message).

Within the system, rules are created in two ways according to the WHEN.fwdarw.IF.fwdarw.THEN construct. A form version of rules, as illustrated in FIG. 10a, provides the rule designer or user with a form having specific fields for the designer to fill in by selection, to create the rule(s). Field selection in the form permits the designer to interact with a user interface which partially hides syntax details from the rule designer.

An alternative rule design format, illustrated in FIG. 10b, uses a text mode within the rule editor, in which the rule designer must have familiarity with rule syntax. The more sophisticated user or rule designer can write more complicated rules using expressions having operators not available for selection in the form mode of rule design.

Still further, rule designers have an extensive open rule syntax, as set forth in Appendix I attached hereto and incorporated herein by reference, available externally for rule design. Rules can be created externally by the rule designer, via the syntax, using a text editor and then can be imported into the system for use in message manipulation by the user.

As illustrated in FIG. 10c, a file 80 can be created and edited using an application external to the messaging system, such as Toolbook by Asymetrix Corp. The file 80, created using the referenced syntax, can include graphics and prompts to elicit responses by a messaging system user invoking the externally created rule application. The file 80 represents a structured rule editor which permits the user to invoke rules by interaction with the graphical interface and without any appreciation of rule syntax particularities. The externally text edited file 80 preferably results in an ASCII representation of the structured rule editor written according to the prescribed syntax. A messaging system importation facility 82 acts as a compiler which compiles the ASCII/syntax file 80 into a rule file 84 in accord with internally created rules. The rule file 84 is imported into the rule data base 86 for storage with other rules and for invocation upon occurrence of the event specified in the externally created rule.

Externally "prefabricated" rule sets associated with a respective graphical user interface (i.e. structured rule editors) can be used to implement various features in a rule based messaging system, such as an "out of the office" feature. The out of the office feature is a prefabricated set of rules which a user invokes to process electronic mail messages received when the user is not in the office. A simple graphical user interface and associated rule sequence are illustrated in FIGS. 11 and 11a.

When the user selects "out of the office," an interface prompts the user for information including an indication of an "until date", i.e. a date and time until which the user wants the associated rule set invoked upon occurrence of a specified event type. The user can specify a source of messages which will invoke the out of the office rule(s) and can indicate a message that should be transmitted in response to messages from the specified source(s). The out of the office interface, while apparently not a rule specification, results in the synthesis of a rule set, as illustrated in FIG. 11a.

The underlying rule set is event driven according to the invention and operative on NEW type message events only. The conditional (IF) portion of the rule is filled with parameters specified by the user in the interaction with the interface. As illustrated, the structured rule invokes an action (THEN) which creates and sends a message in reply to the messages satisfying the event and condition.

Launching of known application programs, such as spreadsheet programs, word processing programs and other applications known in the art, can also be achieved from the rule based messaging system according to the invention. Launching, or spawning another application from the executing messaging application is integrated into the rule language by the use of a "launch" verb or action specified in the THEN(condition) portion of the WHEN.fwdarw.IF.fwdarw.THEN triplet.

A file sent or received as an attachment to a mail message, can be viewed and edited in the appropriate off-the-shelf program format by invoking the application program, i.e. launching into the attachment while maintaining the rule based messaging system for re-entry. A launchable attachment is made by making a file, in an off-the-shelf application format (such as Lotus 1-2-3), an attachment to a mail message. Such a file is attached by appending a copy of the file to the desired base message.

The messaging system according to the invention has a launch action which can be specified in the triplet, such as by:

WHEN(event).fwdarw.IF(condition).fwdarw.THEN launch "application". The launch facility executes a known in the art memory switching program called HOLD EVERYTHING by South Mountain Software Inc., described in the Hold Everything user's manual which is incorporated herein by reference. The "application" specified with the launch verb is run on top of the messaging system, which is swapped to extended memory or disk while the application runs. Hold Everything restores the messaging system when the launched application is done. The launch verb, which can be specified for messages received having particular types of attached files for which the relevant application programs are available to the system, can be specified with parameters (i.e. "with keys") that are required as parameters or operands for the application program to be launched.

Although the invention is described in the context of a PC networked via Netware and running MHS electronic mail system, it will be appreciated by those of ordinary skill in the art that the messaging system according to the invention can be implemented via drivers and application program interfaces to various other electronic mail systems, such as DaVinci, 3+Open Mail, Banyan Vines Mail and the like.

While a particular set of "events", such as timer events, startup and exiting, etc, is disclosed herein for triggering rules for invocation, it can be appreciated that additional occurrences can be identified for establishing relevancy of a message for application of a rule, in accordance with the particulars of the underlying messaging system. Events, such as the changing of a message or the meeting of a quota, among others, can be used to trigger the application of a rule. Additionally, the system can be implemented so that user defined events can be specified.

Message objects are disclosed herein as significant data formats for implementing the present invention. However it will be appreciated that while object data structures are suitable for use in the system described, and those known in the art, other methodologies and data structures, such as structured language data records, can be used in implementing a system according to the invention.

While graphical user interfaces and structured rule editors for tickler features and out of the office replying are illustrated and described herein, it can be appreciated that other structured rule editors, created either within the messaging system or externally, can be effected to implement other features such as scheduling, resource management and the like.

While a launch verb is discussed as integrating a known memory swapping program into the messaging system according to the invention, it will be appreciated that other launching mechanisms could be implemented and that various other verbs could be used to invoke various known application programs.

Although the invention has been shown and described with respect to an illustrative embodiment thereof, it should be understood by those skilled in the art that the foregoing and various other changes, additions and omissions in the form and detail thereof may be made without departing from the spirit and scope of the invention as delineated in the claims. ##SPC1##

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.