System for implementing rules

• US 6,473,748 B1
• Filed: 05/28/1999
• Issued: 10/29/2002
• Est. Priority Date: 08/31/1998
• Status: Expired due to Term

• Current Assignee: Callidus Software, Inc. (SAP SE), Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: WorldCom, Inc. (Verizon Communications Inc.)
• Inventors: Archer, Jack L.
• Primary Examiner(s): Black, Thomas
• Assistant Examiner(s): Holmes, Michael B.
• Application Number:
  US09/321,895
• Time in Patent Office: 1,250 Days
• Field of Search: 707/104, 707/103.R, 705/8, 705/26, 709/203, 709/208, 709/310, 709/320, 379/91, 706/45, 706/47
• US Class Current: 706/45
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A method, system and computer program product for implementing rules. More specifically, a method, system and computer program product for implementing rules is developed by separating business rules from application logic. This architecture effects the implementation of software business rules in a single location, for sharing across software applications as needed. Software business rules are created and maintained by business experts directly, rather than requiring programmers to translate the rules to software code. Thus, programmers are free to concentrate on programming issues and software business rules (new logic, not just new values/ranges) may be added or changes may be made to existing rules without modifying the software applications which use the business rules. Software business rules are written to implement business logic, which does not perform any kind of computer systems manipulation to obtain the data that it works on, nor does it include any logic to manipulate the underlying computer system in general such as memory allocations and network communications, etc. In this architecture, software application logic is a purely computer system operational piece of logic such as, for example, data access, inter-process communications, screen rendering, network communications or data base access, or any type of computer systems manipulation, and is not included in the same physical software module as business logic. Pure application logic, and range checking, are included in software application modules, which are distinct from the software modules which include business logic.

Claims

1. An apparatus for implementing rules comprising:

a client;

an application server configured to receive an application data request from the client;

an application object coupled to the application server, the application object configured to service an application object request from the application server;

a rule engine coupled to the application object, the rule engine configured to service a request for executing business-type logic from the application object; and

a rule base coupled to the rule engine, the rule base including the business-type logic that does not perform computer systems manipulation on data.

2. The apparatus of claim 1, further comprising an object request broker coupled to the application object, the rule engine, and the application server for directing one or more client requests and returned values.

3. The apparatus of claim 1, further comprising services and other application objects coupled to the object request broker, the services and other application objects including software for executing the application-type logic.

4. The apparatus of claim 3, further comprising a relational data base management system coupled to the object request broker for tracking the application-type logic and the business-type logic.

5. The apparatus of claim 1, further comprising a web server and a web processor coupled to the application server and the client.

6. The apparatus of claim 1, wherein the business-type logic in the rule base includes policies, procedures, limits, and ranges.

7. The apparatus of claim 1, wherein the application object includes an application-type logic for invoking a rule session via on interface operation invocation method.

8. A system for implementing rules comprising:

a client;

an application server configured to receive an application data request from the client;

an application object coupled to the application server, the application object configured to service an application object request from the application server;

inference engines coupled to the application object, each of the inference engines configured to service a request for executing business-type logic from the application object; and

a rule base coupled to the inference engines, the rule base includes the business-type logic that does not perform computer systems manipulation on data.

9. The apparatus of claim 8, further comprising an object request broker coupled to the application object, the inference engines, and the application server for directing one or more client requests and returned values.

10. The apparatus of claim 9, further comprising services and other application objects coupled to the object request broker, the services and other application objects including a software for executing the application-type logic.

11. The apparatus of claim 9, further comprising a connectivity server coupled to the object request broker, wherein the connectivity server includes a Java data base.

12. The apparatus of claim 10, further comprising a relational data base management system coupled to the connectivity server for tracking the application-type logic and the business-type logic.

13. The apparatus of claim 8, further comprising a web server and a web processor coupled to the application server and the client.

14. The apparatus of claim 8, wherein the business-type logic in the rule base includes policies, procedures, limits, and ranges.

15. The apparatus of claim 8, wherein the application object includes an application-type logic for invoking a rule session via an interface operation invocation method.

16. A method of implementing rules based on an application data request from a client comprising the steps of:

receiving the application data request from the client by using one or more distributed server interfaces;

processing application data requests through application logic;

invoking a rule session based on a request for executing business-type logic; and

processing the business-type logic through a rule engine in communication with a rule base.

17. The method of claim 16, wherein said application logic comprises a java data base connectivity input/output, software object instantiation, and service invocation.

18. The method of claim 16, wherein said rule engine comprises policies, procedures, limits, and ranges.

19. The method of claim 16, wherein the rule session controls access to the rule base, and instantiates software objects as required by the rule base.

20. A computer-readable medium containing instructions for implementing rules, the instructions causing a computer to:

receive an application data request from a client by using one or more distributed server interfaces;

process application data requests through application logic;

invoke a rule session based on a request for executing business-type logic; and

process the business-type logic through a rule engine in communication with a rule base.

21. The computer-readable medium of claim 20, wherein said application logic comprises a java data base connectivity input/output, software object instantiation, and service invocation.

22. The computer-readable medium of claim 20, wherein said rule engine comprises policies, procedures, limits, and ranges.

23. The computer-readable medium of claim 20, wherein the rule session controls access to the rule base, and instantiates software objects as required by the rule base.