A contract rule management engine

Abstract

The present application provides a contract rule management engine, which includes a receiving module configured to receive service data and perform identification to obtain input information items and corresponding input values; a rule module includes a first database configured to store multiple information item sets, each information item set including preset information items and preset values; a screening module is configured to screen out the information item set corresponding to the input information item as the target information item set and send it to the rule engine; the rule engine includes a second database configured to store a rule framework; a processing module is configured to combine the received target information item set and the corresponding rule framework to form a verification rule; and verify the input information item and the input value. The contract rule management engine provided by the present application divides the original verification rules into the information item sets stored in the rule module and the rule framework stored in the rule engine, greatly reducing the number of verification rules originally stored in the rule engine.

Description

Technical Field

[0001] This application relates to the technical field of rule management, and in particular to a contract rule management engine. Background Art

[0002] In relevant institutions and enterprises in fields such as finance and insurance, it is necessary to process multiple tasks through relatively complex business logics. In related technologies, logical operations can be implemented by a rule engine executing business rules. Business rules can be understood as a set of conditions and operations under these conditions.

[0003] For existing rule engines, they store a large number of similar business rules, wasting a lot of resources. At the same time, the creation and maintenance methods of business rules are both relatively cumbersome. Summary of the Invention

[0004] In view of this, the purpose of this application is to propose a contract rule management engine.

[0005] Based on the above purpose, this application provides a contract rule management engine, including: a receiving module, a rule module, and a rule engine. The receiving module is configured to receive business data and perform identification to obtain input information items and corresponding input values; the rule module includes: a first database and a screening module; the first database is configured to store multiple information item sets, each information item set includes at least one preset information item and a preset value corresponding to the preset information item; the screening module is configured to screen out the information item set corresponding to the input information item from the first database as the target information item set and send the target information item set to the rule engine; the rule engine includes: a second database and a processing module; the second database is configured to store rule frameworks corresponding to the information item sets one by one; the processing module is configured to combine the received target information item set and the corresponding rule framework to form a verification rule; and verify the input information item and the input value according to the verification rule.

[0006] Optionally, there are multiple input information items, and the preset information items included in the target information item set are the same as the input information items.

[0007] Optionally, the rule framework includes a trigger logic and a preset action. The trigger logic, the preset information item, and the preset value are combined to form a trigger condition; in response to determining that the input information item and the input value meet the trigger condition, the preset action corresponding to the trigger condition is executed.

[0008] Optionally, it further includes a setting module configured to obtain a setting instruction and execute the setting action included in the setting instruction.

[0009] Optionally, the setting action includes:

[0010] Adding a new preset information item, and / or a new preset value, and / or a new rule framework;

[0011] Deleting an original preset information item, and / or an original preset value, and / or an original rule framework;

[0012] Changing the original preset value.

[0013] Optionally, the setting instruction further includes a scope of effectiveness, and the setting module is further configured to perform the setting action according to the scope of effectiveness.

[0014] Optionally, the scope of effectiveness includes an effective institution and / or an effective start and end time.

[0015] Optionally, it further includes a front-end setting interface, which is configured to collect and send the setting instruction.

[0016] Optionally, it further includes an approval module, which is configured to obtain an approval instruction and the setting instruction sent by the front-end setting interface, and in response to determining that the approval instruction is passed, send the setting instruction to the setting module.

[0017] Optionally, it further includes an approval interface, which is configured to display the setting instruction and collect the approval instruction.

[0018] As can be seen from the above, the contract rule management engine provided by this application divides the original verification rules into an information item set stored in the rule module and a rule framework stored in the rule engine, greatly reducing the number of verification rules originally stored in the rule engine. At the same time, through the information item set and the rule framework, verification rules can be dynamically assembled to personalize the originally fixed-format verification rules. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in this application or related technologies, the following will briefly introduce the drawings required for use in the embodiments or related technology descriptions. Obviously, the drawings in the following description are only the embodiments of this application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0020] Figure 1 It is a schematic structural diagram of the contract rule management engine according to an embodiment of this application;

[0021] Figure 2 It is a schematic diagram of the front-end setting interface of the contract rule management engine according to an embodiment of this application;

[0022] Figure 3Schematic diagram of the start and end times for the settings of the contract rule management engine in the embodiments of this application;

[0023] Figure 4 Schematic diagram of the approval interface of the contract rule management engine in the embodiments of this application. Detailed implementation manners

[0024] To make the objectives, technical solutions, and advantages of this application clearer and more understandable, the following further elaborates on this application in detail with reference to specific embodiments and the accompanying drawings.

[0025] It should be noted that unless otherwise defined, the technical terms or scientific terms used in the embodiments of this application should have the ordinary meanings understood by those of ordinary skill in the field to which this application belongs. The "first", "second", and similar terms used in the embodiments of this application do not indicate any order, quantity, or importance, but are only used to distinguish different components. The terms such as "including" or "comprising" mean that the elements or objects appearing before this word cover the elements or objects listed after this word and their equivalents, without excluding other elements or objects. The terms such as "connected" or "coupled" are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The terms such as "upper", "lower", "left", "right", etc. are only used to represent relative positional relationships, and when the absolute position of the object being described changes, the relative positional relationship may also change accordingly.

[0026] For ease of understanding, the following explains the nouns involved in the embodiments of this application:

[0027] Backend: Provides a channel for data request interaction between the front end of the contract rule management engine and the server, and processes business logic.

[0028] Front end: The application part that interacts with business personnel in the contract rule management engine, used to receive data from business personnel, request data from the backend, receive return data from the backend, display data to business personnel, and process rendering logic, etc.

[0029] The applicant found that the IBM rule engine (ILog) adopted in the prior art cannot be reused for different verification rules during use, the verification values cannot change dynamically, and the underlying verification logic needs to be continuously updated.

[0030] Example 1:

[0031] Dual-recording collection rule package

[0032] Province-specific dual-recording rule package

[0033] Anhui Bengbu dual-recording rule package

[0034] BB0001 - Anhui Bengbu Annual Unit Dual Recording Rules.brl

[0035] BB0002 - Anhui Bengbu Monthly Unit Dual Recording Rules.brl

[0036] BB0003 - Anhui Bengbu Daily Unit Dual Recording Rules.brl

[0037] BB0004 - Anhui Bengbu Other Unit Dual Recording Rules.brl

[0038] Dalian Dual Recording Rules Package

[0039] DL0001 - Dalian Annual Unit Dual Recording Rules.brl

[0040] DL0002 - Dalian Monthly Unit Dual Recording Rules.brl

[0041] DL0003 - Dalian Daily Unit Dual Recording Rules.brl

[0042] DL0004 - Dalian Other Unit Dual Recording Rules.brl

[0043] As can be seen from the above content, even if the content of the verification rules is the same, due to being used in different time ranges or geographical ranges, it is necessary to rewrite them repeatedly, and a unified rule cannot be abstracted, and dynamic variables cannot be used for verification.

[0044] Example 2:

[0045] If

[0046] Any one of the following conditions is satisfied:

[0047] - The management agency of 'Relevant Information on Dual Recording of Insurance Application Forms' is "340303"

[0048] - The management agency of 'Relevant Information on Dual Recording of Insurance Application Forms' is "340305"

[0049] - The management agency of 'Relevant Information on Dual Recording of Insurance Application Forms' is "340306"

[0050] - The management agency of 'Relevant Information on Dual Recording of Insurance Application Forms' is "340307"

[0051] - The management agency of 'Relevant Information on Dual Recording of Insurance Application Forms' is "340308"

[0052] - The management agency of 'Relevant Information on Dual Recording of Insurance Application Forms' is "340309"

[0053] - The management agency of 'Relevant Information on Dual Recording of Insurance Application Forms' is "340312"

[0054] - The management institution of 'Relevant Information on Dual Recording of Insurance Application Forms' is "340314"

[0055] - The management institution of 'Relevant Information on Dual Recording of Insurance Application Forms' is "340316"

[0056] - The management institution of 'Relevant Information on Dual Recording of Insurance Application Forms' is "340321"

[0057] - The management institution of 'Relevant Information on Dual Recording of Insurance Application Forms' is "340322"

[0058] - The management institution of 'Relevant Information on Dual Recording of Insurance Application Forms' is "340323",

[0059] and the current system time is later than 2020-10-01 00:00:00 +0800

[0060] and the insurance period of 'Insurance Type Information' is greater than 1

[0061] and the unit of the insurance period of 'Insurance Type Information' is Y - year

[0062] then the return information of 'Output Parameters' is "The current insurance policy hits the dual recording collection rule, please conduct dual recording collection"

[0063] The above content is a verification rule. When the 'Management Institution' or 'System Time' needs to be changed or adjusted, it is necessary to contact the back-end rule engine developers for implementation, and it is impossible to respond in a timely manner.

[0064] In view of this, as Figure 1 shown, this embodiment provides a contract rule management engine, including: a receiving module 1, a rule module 2, and a rule engine 3. The receiving module 1 is configured to receive business data and perform identification to obtain input information items and corresponding input values; the rule module 2 includes: a first database 21 and a screening module 22; the first database 21 is configured to store multiple information item sets, each information item set includes at least one preset information item and a preset value corresponding to the preset information item; the screening module 22 is configured to screen out the information item set corresponding to the input information item from the first database 21 as the target information item set and send the target information item set to the rule engine 3; the rule engine 3 includes: a second database 31 and a processing module 32; the second database 31 is configured to store rule frameworks corresponding one-to-one with the information item sets; the processing module 32 is configured to combine the received target information item set and the corresponding rule framework to form a verification rule; and verify the input information item and the input value according to the verification rule.

[0065] Based on the existing verification rules, the core logic is abstracted. That is, the verification rules are divided into a rule framework, preset information items (i.e., preset verification information items), and preset values (i.e., preset verification values) according to the business logic. The rule framework is stored in the second database 31 in the rule engine 3, and the preset information items and preset values are combined into an information item set and stored in the first database 21 in the rule module 2.

[0066] For example, the verification rule in Example 2 can be disassembled as follows:

[0067] 01 Rule information item set:

[0068] Preset information item: The management agency of the 'double-recording related information of the insurance application form'; Agency preset values: "340303", "340305", "340306", "340307", "340308", "340309", "340312", "340314", "340316", "340321", "340322", and "340323".

[0069] Preset information item: The current system time; Time preset value: 2020-10-01 00:00:00 +0800.

[0070] Preset information item: The insurance period of the 'insurance type information'; Insurance period preset value: 1.

[0071] Preset information item: The insurance period unit of the 'insurance type information'; Unit preset value: Y - year.

[0072] The above content is stored in the first database 21.

[0073] 01 Rule framework: If the management agency of the 'double-recording related information of the insurance application form' is any one of the agency preset values; and the current system time is later than the time preset value; and the insurance period of the 'insurance type information' is greater than the insurance period preset value; and the insurance period unit of the 'insurance type information' is the unit preset value; then the return information of 'output parameter' is "The current insurance policy hits the double-recording collection rule, please conduct double-recording collection"

[0074] The above content is stored in the second database 31.

[0075] Suppose the business data received by the receiving module 1 is: The management agency of the 'double-recording related information of the insurance application form': 340303; The current system time: 2021-01-01 10:10:24; The insurance period of the 'insurance type information': 2; The insurance period unit of the 'insurance type information': Y - year.

[0076] The receiving module 1 identifies it and extracts the input information items and input values:

[0077] Extract the management institution of the input information item: 'Relevant information on dual recording of insurance application forms'; input value: 340303;

[0078] Extract the input information item: current system time; input value: 2021-01-01 10:10:24;

[0079] Extract the insurance period of the input information item: 'Insurance type information'; input value: 2;

[0080] Extract the insurance period unit of the input information item: 'Insurance type information'; input value: Y - year

[0081] After the recognition is completed, the screening module 22 selects the 01 rule information item set from the first database 21 as the target information item set according to the above input information items and input values, and sends it to the rule engine 3.

[0082] After receiving the 01 rule information item set, the rule engine 3 retrieves the 01 rule framework from the second database 31, combines the two, forms the verification rule of the above Example 2, and verifies the input information item and the input value. It can be seen that the input values all meet the preset values, so execute: the return information of 'output parameter' is "The current insurance policy hits the dual recording collection rule, please conduct dual recording collection".

[0083] The contract rule management engine provided by the embodiment of the present application divides the original verification rule into the information item set stored in the rule module 2 and the rule framework stored in the rule engine 3, which greatly reduces the number of verification rules originally stored in the rule engine 3. Optimize the overall business processing process, improve the business processing efficiency, and realize the centralized management of rules for the verification of business information such as insurance application materials, images, and dual recordings in the business process. At the same time, the verification rule can be dynamically assembled through the information item set and the rule framework, and the originally fixed-format verification rule can be personalized.

[0084] In some embodiments, there are multiple input information items, and the preset information items included in the target information item set are the same as the input information items.

[0085] For example, assume the input information items are n1, n2, n3, and n4, then the preset information items included in the selected target information item set 01 can be n1 and n2, and the preset information items included in the target information item set 02 can be n1, n2, n3, n4. The information item set can be flexibly retrieved according to the business data.

[0086] In some embodiments, the rule framework includes a trigger logic and a preset action. The trigger logic, the preset information item, and the preset value are combined to form a trigger condition; in response to determining that the input information item and the input value meet the trigger condition, the preset action corresponding to the trigger condition is executed.

[0087] For the logical framework in the above example

[0088] The triggering logic is as follows: if the management institution of the "relevant information on dual recording of insurance application forms" is any one of the institution preset values; and the current system time is later than the time preset value; and the insurance period of the "insurance type information" is greater than the insurance period preset value; and the insurance period unit of the "insurance type information" is the unit preset value

[0089] The triggering condition is that any one of the following conditions is satisfied:

[0090] - The management institution of the "relevant information on dual recording of insurance application forms" is "340303"

[0091] - The management institution of the "relevant information on dual recording of insurance application forms" is "340305"

[0092] - The management institution of the "relevant information on dual recording of insurance application forms" is "340306"

[0093] - The management institution of the "relevant information on dual recording of insurance application forms" is "340307"

[0094] - The management institution of the "relevant information on dual recording of insurance application forms" is "340308"

[0095] - The management institution of the "relevant information on dual recording of insurance application forms" is "340309"

[0096] - The management institution of the "relevant information on dual recording of insurance application forms" is "340312"

[0097] - The management institution of the "relevant information on dual recording of insurance application forms" is "340314"

[0098] - The management institution of the "relevant information on dual recording of insurance application forms" is "340316"

[0099] - The management institution of the "relevant information on dual recording of insurance application forms" is "340321"

[0100] - The management institution of the "relevant information on dual recording of insurance application forms" is "340322"

[0101] - The management institution of the "relevant information on dual recording of insurance application forms" is "340323"

[0102] And the current system time is later than 2020-10-01 00:00:00 +0800

[0103] And the insurance period of the "insurance type information" is greater than 1

[0104] And the insurance period unit of the "insurance type information" is Y - year

[0105] The preset action is that the return information of "output parameter" is "The current insurance policy hits the dual recording collection rule. Please conduct dual recording collection."

[0106] In some embodiments, the contract rule management engine further includes a setting module 6, which is configured to obtain a setting instruction and execute the setting actions included in the setting instruction.

[0107] In some embodiments, the setting actions include:

[0108] Adding a new preset information item, and / or a new preset value, and / or a new rule framework.

[0109] Deleting the original preset information item, and / or the original preset value, and / or the original rule framework.

[0110] Changing the original preset value.

[0111] Optionally, the setting module 6 can add or delete the original verification rules according to the setting instruction.

[0112] Optionally, the setting module 6 can add or delete the preset information items abstracted from the original verification rules according to the setting instruction.

[0113] Optionally, the setting module 6 can add, delete or modify the preset values corresponding to the original preset information items according to the setting instruction.

[0114] In the contract rule management engine of this embodiment, since the verification rules are divided into a rule framework, preset information items and preset values, the modification method of the verification rules is more convenient and flexible.

[0115] In some embodiments, the setting instruction further includes a scope of effectiveness, and the setting module 6 is further configured to execute the setting actions according to the scope of effectiveness.

[0116] Such as Figure 3 shown, in some embodiments, the scope of effectiveness includes the effective institution and / or the start and end time of effectiveness.

[0117] Optionally, each effective institution is provided with an institution code, such as "414002", etc. When setting the rule framework, preset information item or preset value, the effective institution for this setting can be selected. For some branch companies, the need to formulate personalized verification rules can be realized.

[0118] Optionally, for the effective time, immediate effectiveness can be selected or a date can be selected for timed effectiveness, enabling the person setting to fully control the effective time of the setting action, which is more intelligent and convenient.

[0119] Such as Figure 2 and Figure 3 shown, in some embodiments, the contract rule management engine further includes a front-end setting interface 7, which is configured to collect and send the setting instruction.

[0120] Even without the help of professional rule engine developers, front-end business personnel can modify and set the preset information items, preset values, and rule frameworks by themselves, effectively reducing the threshold for configuring verification rules. On the one hand, it can reduce the workload of professional rule engine developers and lower the costs for enterprises. On the other hand, it can also quickly modify the verification rules, streamline the execution process, and reduce the time cost.

[0121] In the front-end setting interface 7, when the original information item set is selected, it displays the rule ID, rule code, rule description, rule enabling institution, effective configuration elements (i.e., the effective verification information items), etc.

[0122] When editing and setting the configuration elements (i.e., verification information items), it is possible to set the name, write a brief description, select whether to configure by province, edit the upper and lower limits of the verification values corresponding to this configuration element, and select the effective institution, etc.

[0123] In some embodiments, the contract rule management engine further includes an approval module 5, which is configured to obtain the approval instruction and the setting instruction sent by the front-end setting interface 7, and in response to determining that the approval instruction is passed, send the setting instruction to the setting module 6.

[0124] After the front-end business personnel complete the editing of the setting instruction through the front-end setting interface 7, the setting instruction will first go through the approval module 5 for manual approval or system-assisted manual approval. Only when the approval is passed will the setting instruction be sent to the setting module 6 to further perform the setting action. This can largely avoid generating incorrect verification rules due to the misoperation of front-end business personnel and reduce the usage risk of the contract rule management engine in this embodiment.

[0125] Such as Figure 4 shown, in some embodiments, the contract rule management engine further includes an approval interface 4, which is configured to display the setting instruction and collect the approval instruction.

[0126] Optionally, the contract rule management engine further includes a query module 8, which is configured to query and display the generated configuration instructions. There are multiple query condition setting items preset in the query module 8, and users can input the corresponding query condition values in the query condition setting items to obtain the query results.

[0127] Optionally, the query condition setting items include rule category, change rule description, effective type, application status, application date range, etc.

[0128] For the selected configuration instructions, all or some of the following multiple attributes can be displayed in the approval interface 4: task ID, rule category, change rule name, change rule code, change status, applicant name, applicant ID number, applicant organization number, reviewer name, reviewer ID number, reviewer organization number, effective type, effective time, application date, etc.

[0129] Finally, the approval interface 4 also includes operation items, and the reviewer can select to pass or cancel the setting instruction within the operation items.

[0130] Those of ordinary skill in the art should understand that: the discussion of any of the above embodiments is only exemplary and is not intended to imply that the scope of the present application (including the claims) is limited to these examples; within the concept of the present application, the technical features between the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations in different aspects of the embodiments of the present application as described above, and they are not provided in detail for the sake of brevity.

[0131] In addition, for the sake of simplicity of description and discussion, and in order not to make the embodiments of the present application difficult to understand, the well-known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided drawings. In addition, the device may be shown in block diagram form in order not to make the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform on which the embodiments of the present application will be implemented (i.e., these details should be fully within the understanding of those skilled in the art). In the case where specific details (such as circuits) are set forth to describe the exemplary embodiments of the present application, it will be apparent to those skilled in the art that the embodiments of the present application can be implemented without these specific details or with variations of these specific details. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0132] Although the present application has been described in connection with specific embodiments of the present application, many alternatives, modifications, and variations of these embodiments will be apparent to those of ordinary skill in the art based on the foregoing description. For example, other memory architectures (such as dynamic RAM (DRAM)) can be used with the embodiments discussed.

[0133] The embodiments of the present application are intended to cover all such alternatives, modifications, and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application shall be included within the protection scope of the present application.

Claims

1. A contract rule management engine, characterized in that, Including: a receiving module, a rule module, and a rule engine The receiving module is configured to receive service data and perform identification to obtain input information items and corresponding input values; The rule module includes: a first database and a screening module; the first database is configured to store multiple information item sets, each information item set includes at least one preset information item and a preset value corresponding to the preset information item; the screening module is configured to screen out the information item set corresponding to the input information item from the first database as a target information item set and send the target information item set to the rule engine; The rule engine includes: a second database and a processing module; the second database is configured to store rule frameworks corresponding to the information item sets one by one; the processing module is configured to combine the received target information item set and the corresponding rule framework to form a verification rule; and verify the input information item and the input value according to the verification rule, wherein the rule framework includes a trigger logic and a preset action, and the trigger logic, the preset information item and the preset value are combined to form a trigger condition; in response to determining that the input information item and the input value meet the trigger condition, the preset action corresponding to the trigger condition is executed.

2. The contract rule management engine according to claim 1, characterized in that There are multiple input information items, and the preset information items included in the target information item set are the same as the input information items.

3. The contract rule management engine according to claim 1, characterized in that, It further includes a setting module, which is configured to obtain a setting instruction and execute the setting action included in the setting instruction.

4. The contract rule management engine according to claim 3, characterized in that, The setting action includes: adding a new preset information item, and / or a new preset value, and / or a new rule framework; deleting an original preset information item, and / or an original preset value, and / or an original rule framework; changing the original preset value.

5. The contract rule management engine according to claim 3, characterized in that, The setting instruction further includes an effective scope, and the setting module is further configured to execute the setting action according to the effective scope.

6. The contract rule management engine according to claim 5, characterized in that, The effective scope includes an effective institution and / or an effective start and end time.

7. The contract rule management engine according to claim 3, wherein It further includes a front-end setting interface, which is configured to collect and send the setting instruction.

8. The contract rule management engine according to claim 7, characterized in that It further includes an approval module, which is configured to obtain an approval instruction and the setting instruction sent by the front-end setting interface, and in response to determining that the approval instruction is passed, send the setting instruction to the setting module.

9. The contract rule management engine according to claim 8, characterized in that, It further includes an approval interface, which is configured to display the setting instruction and collect the approval instruction.

Images