Rule-based electronic agent system and method thereof

• US 5,586,025 A
• Filed: 10/05/1992
• Issued: 12/17/1996
• Est. Priority Date: 10/07/1991
• Status: Expired due to Fees

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: Wakayama, Satoshi, Aoyama, Toyozo, Tomohiro, Shuzo, Tsuji, Hiroshi, Taniguchi, Yoji, Hirose, Tadashi
• Primary Examiner(s): Weinhardt, Robert A.
• Application Number:
  US07/956,303
• Time in Patent Office: 1,534 Days
• Field of Search: 395/926, 395/934, 395/909, 395/51, 395/61, 395/76, 364/419.1
• US Class Current: 715/207
• CPC Class Codes: G06N 5/046 Forward inferencing; Production systems

Abstract

Rules registered in the electronic secretary system are defined by separating each of them into a trigger descriptor part, a condition part for object data retrieval, and an action part, and a flag indicating whether or not to fire a rule and a flag indicating whether or not to suppress firing of a rule after it is fired once are installed in each rule, and a flag for selecting whether to automatically activate the action when object data is retrieved or to activate the action after the user confirms it is installed, and an area for storing the period and timing for judging success or failure of the condition when necessary is referred to so as to change the corresponding flag to ON or OFF or to change the period and, whether to automatically execute the electronic secretary system or to execute it after a human confirms it, can be selected freely.

Claims

1. A method of executing a rule in a system having a rule base for storing rules each including a condition part, an action descriptor part, files for storing object data, and a user interface means comprising the steps of:

setting a value to a flag indicating whether a rule having said flag is to be automatically activated or not, said flag being included in a trigger descriptor part provided in at least one rule of the rules stored in said rule base, said trigger descriptor part being a third part included in the rule in addition to said condition part and said action descriptor part;

specifying timing data to said at least one rule, for retrieving object data through said user interface means;

fetching, when a current timing matches with the specified timing data a rule whose flag indicates the value that the rule having said flag to be automatically activated;

fetching object data which satisfies the condition part defined in the fetched rule; and

executing a process defined in the action descriptor part of the rule with the fetched object data.

2. The method as stated in claim 1 further comprising the steps of:

specifying a confirmation value in a confirmation flag included in said action descriptor part of said at least one rule, for confirming whether a process defined in said action descriptor part is to be automatically executed, or executed after a user confirms it through said user interface means;

fetching the rule whose flag indicates the value that the rule having said flag is to be automatically activated;

fetching object data which satisfies a retrieval condition defined in the fetched rule; and

executing said process defined in said action descriptor part, according to said confirmation value in said confirmation flag, with the fetched object data.

3. A method as stated in claim 2, wherein each rule stored in said rule base has said condition part for object data retrieval, further comprising the steps of:

checking binding of the object data included in software resources, with said process defined in the action descriptor part, in accordance with said condition part for object data retrieval being specified;

specifying an operation command of said software resources for said process; and

performing said operation command.

4. A method stated in claim 1, further comprising the step of:

specifying, through said user interface means, a repetition flag as said timing data, indicating a value at which to fire each of said at least a rule for repetitively executing said process after said rule is once fired.

5. A method as stated in claim 1, wherein each rule stored in said rule base includes said condition part for retrieving object data, the method further comprising the steps of:

checking binding of the object data included in files, with said process defined in the action descriptor part, in accordance with said condition part for retrieving object data being specified;

specifying an operation command of said software resources for said process; and

performing said operation command.

6. A method as stated in claim 1 further comprising the step of:

activating said process defined in the action descriptor part, by specification of a user through said interface means., irrespective of said timing data.

7. A system for executing a rule, in a system having a rule base for storing rules each including a condition part and an action descriptor part, files for storing object data, and a user interface means comprising:

means for setting a value to a flag indicating whether a rule having said flag is to be automatically activated or not, the at least one rule being configured to provide a trigger descriptor part being a third part included in the rule in addition to said condition part and said action descriptor part, said flag being included in said trigger descriptor part in at least one rule stored in said rule base;

means for specifying timing data to said at least one rule, for retrieving object data through said user interface means;

means for fetching at least one rule whose flag indicates the value that the rule having said flag is to be automatically activated, when a current timing matches with the specified timing data;

means for fetching object data which satisfies the condition part defined in the fetched rule; and

means for executing a process defined in the action descriptor part of the rule with the fetched object data.

8. The system for executing a rule as stated in claim 7 further comprising:

means for setting a specific value to a flag for indicating whether a rule having said flag is to be automatically activated or not, said flag being included in said trigger descriptor part in at least a rule in the rules stored in said rule base;

means for specifying a confirmation value in a confirmation flag included in said action descriptor part of said at least a rule, for confirming whether a process defined in said action descriptor part is to be automatically executed, or executed after a user confirms it through said user interface means;

means for fetching the rule whose flag is set with said specific value;

means for fetching object data which satisfies retrieval condition defined in the fetched rule; and

means for executing said process defined in said action descriptor part, according to said confirmation value in said confirmation flag, with the fetched object data.