Providing results from external rule engines based on rule engine vocabularies

• US 7,937,354 B2
• Filed: 10/15/2007
• Issued: 05/03/2011
• Est. Priority Date: 10/15/2007
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Ziegler, Carsten, Brelage, Christian, Rieke, Tobias
• Primary Examiner(s): Holmes; Michael B.
• Assistant Examiner(s): Hill; Stanley K
• Application Number:
  US11/872,328
• Publication Number:
  US 20090099994A1
• Time in Patent Office: 1,296 Days
• Field of Search: None
• US Class Current: 706/47
• CPC Class Codes: G06N 5/025 Extracting rules from data

Abstract

An enhanced rule engine, in which a rule-evaluated result that is received from an external rule engine based on a context transmitted to the external rule engine for evaluation by the rule and on a schema document serializing an automatically generated vocabulary transmitted to the external rule engine is output. The schema document defines the business rule based on a context description and a result description included in the vocabulary, and the context and the result are respectively specified according to the context description and the result description.

Claims

1. A computer-implemented method comprising:

automatically generating, at a local rule engine, a rule engine vocabulary comprising a context description and a result description that respectively define an input to and an output of an external rule engine, the rule engine vocabulary defining a data type of a result;

serializing the rule engine vocabulary in a schema document that, when received at the external rule engine, allows a rule to be defined by the external rule engine based on the context description and the result description;

transmitting the schema document to the external rule engine;

transmitting a context specified according to the context description as the input to the external rule engine, for evaluation by the rule to provide the result corresponding to the data type;

receiving, at the local rule engine, the result specified according to the result description as the output of the external rule engine; and

outputting the result.

2. The method of claim 1, wherein the rule engine vocabulary is generated based on using generic data structures.

3. The method of claim 2, wherein the generic data structures further comprise a field, structure, or table data element.

4. The method of claim 1, further comprising:

defining an expression including a connection to the external rule engine; and

passing the context to the expression, thereby causing the schema document and the context to be transmitted via the connection, and the result to be received via the connection.

5. The method of claim 4, wherein defining the expression further comprises:

querying the rule engine to determine connection parameters; and

selecting the defined expression from a list of possible expressions based on the determined connection parameters.

6. The method of claim 4, wherein the context is automatically transmitted to the external rule engine via a remote procedure call, if the expression is triggered.

7. The method of claim 6, wherein the result is received via the remote procedure call.

8. The method of claim 6, wherein the remote procedure call is a SUN MICROSYSTEMS®

JAVA®

programming language remote procedure call.

9. The method of claim 1, wherein the context description further comprises a context data type.

10. The method of claim 9, wherein the context data type is native to the external rule engine.

11. The method of claim 1, wherein the schema document expresses a set of rules to which a document must conform to be considered a valid document according to an underlying schema.

12. The method of claim 1, wherein the context is transmitted as an eXtensible Markup Language (XML) Schema Document (XSD).

13. The method of claim 1, wherein the rule is a business rule that is proprietary to an operator of the external rule engine.

14. The method of claim 1, wherein the schema document is an eXtensible Markup Language (XML) Schema Document (XSD).

15. The method of claim 1, wherein the external rule engine comprises a Business Rule Management System (BRMS).

16. The method of claim 1, wherein the rule engine vocabulary is a business vocabulary.

17. The method of claim 1, wherein the external rule engine is a business rule engine.

18. The method of claim 1, wherein the rule is a business rule.

19. A computer program product, tangibly embodied in a non-transitory machine-readable storage device, the computer program product comprising instructions that, when read by a machine, operate to cause a data processing apparatus to:

automatically generate, at a local rule engine, a rule engine vocabulary comprising a context description and a result description that respectively define an input to and an output of an external rule engine, the rule engine vocabulary defining a data type of a result;

serialize the rule engine vocabulary in a schema document that, when received at the external rule engine, allows a rule to be defined by the external rule engine based on the context description and the result description;

transmit the schema document to the external rule engine;

transmit a context specified according to the context description as the input to the external rule engine, for evaluation by the rule to provide the result corresponding to the data type;

receive, at the local rule engine, the result specified according to the result description as the output of the external rule engine; and

output the result.

20. A device comprising:

a processor configured to;

automatically generate, at a local rule engine, a rule engine vocabulary comprising a context description and a result description that respectively define an input to and an output of an external rule engine, the rule engine vocabulary defining a data type of a result, and

serialize the rule engine vocabulary in a schema document that, when received at the external rule engine, allows a rule to be defined by the external rule engine based on the context description and the result description;

an interface configured to;

transmit the schema document to the external rule engine,

transmit a context specified according to the context description as the input to the external rule engine, for evaluation by the rule to provide the result corresponding to the data type, and

receive, at the local rule engine, the result specified according to the result description as the output of the external rule engine; and

an output module configured to output the result.