CN117632539A - Rule engine-oriented adaptation middleware device, configuration method and matching method - Google Patents
Rule engine-oriented adaptation middleware device, configuration method and matching method Download PDFInfo
- Publication number
- CN117632539A CN117632539A CN202311622320.6A CN202311622320A CN117632539A CN 117632539 A CN117632539 A CN 117632539A CN 202311622320 A CN202311622320 A CN 202311622320A CN 117632539 A CN117632539 A CN 117632539A
- Authority
- CN
- China
- Prior art keywords
- rule
- fact
- interface
- operator
- unit
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 35
- 230000006978 adaptation Effects 0.000 title claims abstract description 21
- 238000004364 calculation method Methods 0.000 claims abstract description 43
- 238000004458 analytical method Methods 0.000 claims abstract description 24
- 238000012795 verification Methods 0.000 claims description 36
- 238000012545 processing Methods 0.000 claims description 9
- 238000007405 data analysis Methods 0.000 claims description 6
- 238000006243 chemical reaction Methods 0.000 claims description 5
- 238000013507 mapping Methods 0.000 claims description 5
- 230000008569 process Effects 0.000 claims description 3
- 230000009466 transformation Effects 0.000 claims 1
- 238000012423 maintenance Methods 0.000 abstract description 5
- 238000011161 development Methods 0.000 abstract description 4
- 230000000875 corresponding effect Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 150000001875 compounds Chemical class 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000004900 laundering Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses an adaptation middleware device, a configuration method and a matching method for a rule engine. The device comprises: the system comprises an interface calling unit, a rule engine routing unit, a rule fact generating unit and a rule calculation calling unit; the interface calling unit is used for providing a fact execution interface and a rule configuration interface to the outside, providing a general interface service to the outside and automatically updating the execution interface; the rule engine routing unit is used for identifying and analyzing the interface call request transmitted by the interface call unit, distributing the analyzed interface call request to the corresponding rule fact generation unit, and updating the routing configuration in real time according to the rule upgrading condition; the rule fact generation unit is used for analyzing the type of the rule engine requested by the interface call and generating facts or rules of the rule engine according to the analysis result; the rule calculation calling unit is used for interacting with the underlying rule engine node. The operation and maintenance development burden of the middleware device can be greatly reduced.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to an adaptation middleware device facing a rule engine, a configuration method and a matching method.
Background
Rule engines are often used to set a software behavior criterion within specific parameters to make fast and reliable decisions based on a large amount of information data. The rule engine realizes reasoning through three elements of facts (face), conditions (conditions) and actions (actions), and performs Condition retrieval and matching in a rule base according to the input facts (or events), so that corresponding actions are selected to be executed.
The rule engine allows a non-technical software user to quickly and timely change the software behavior according to the service requirement of the non-technical software user without changing the bottom code, so that the non-technical software user can better adapt to the market requirement of frequent iteration of an IT system; for developers, the rule engine can reduce hard coding, decouple business rules and software codes, realize automation of management flow, improve system execution efficiency and reduce maintenance and expansion cost of application programs. Examples of more typical applications of a rules engine include: automatic approval decisions, risk management, credit rating, product marketing and recommendation, money laundering and accounting reporting, etc.
The rule engines can be classified into lightweight rule engines, and compound event processing engines according to business scenarios. Different rule engine platforms require different fact messages to be input, so that when the rule engine platforms are switched, the fact messages need to be rewritten, and the cost is high.
Disclosure of Invention
The embodiment of the invention provides an adaptation middleware device, a configuration method and a matching method for a rule engine, which can greatly reduce the operation and maintenance development burden of the middleware device.
In a first aspect, an embodiment of the present invention provides a rule engine-oriented adaptation middleware device, including: the system comprises an interface calling unit, a rule engine routing unit, a rule fact generating unit and a rule calculation calling unit;
the interface calling unit is used for providing a fact execution interface and a rule configuration interface to the outside, providing a general interface service to the outside and automatically updating the execution interface;
the rule engine routing unit is used for identifying and analyzing the interface call request transmitted by the interface call unit, distributing the analyzed interface call request to the corresponding rule fact generation unit, and updating the routing configuration in real time according to the rule upgrading condition; wherein the interface call request comprises a fact call request and a rule configuration request;
the rule fact generation unit is used for analyzing the type of the rule engine for calling the request, and generating facts or rules of the rule engine according to the analysis result;
the rule calculation calling unit is used for interacting with the bottom layer rule engine node; wherein, different rule engines need to be configured with different rule calculation calling units.
In a second aspect, an embodiment of the present invention further provides a rule configuration method, where the method is executed by the rule engine-oriented adaptation middleware device according to the embodiment of the present invention, and includes:
receiving a rule configuration request sent by an upper layer service;
verifying the rule configuration request;
if the verification is passed, analyzing key rule information in the rule configuration request, and updating a fact execution interface based on the key rule information;
compiling the rule in the rule configuration request, and deploying or updating the compiled rule to the rule engine node.
In a third aspect, an embodiment of the present invention further provides a fact rule matching method, where the method is performed by the rule engine-oriented adaptation middleware device according to the embodiment of the present invention, including:
receiving a fact call request sent by an upper layer service;
verifying the fact call request;
and if the verification is passed, matching the target fact rule to the rule engine node according to the fact call request.
The embodiment of the invention discloses a rule engine-oriented adaptation middleware device, a configuration method and a matching method. The device comprises: the system comprises an interface calling unit, a rule engine routing unit, a rule fact generating unit and a rule calculation calling unit; the interface calling unit is used for providing a fact execution interface and a rule configuration interface to the outside, providing a general interface service to the outside and automatically updating the execution interface; the rule engine routing unit is used for identifying and analyzing the interface call request transmitted by the interface call unit, distributing the analyzed interface call request to the corresponding rule fact generation unit, and updating the routing configuration in real time according to the rule upgrading condition; the interface call request comprises a fact call request and a rule configuration request; the rule fact generation unit is used for analyzing the type of the rule engine requested by the interface call and generating facts or rules of the rule engine according to the analysis result; the rule calculation calling unit is used for interacting with the bottom layer rule engine node; wherein, different rule engines need to be configured with different rule calculation calling units. The operation and maintenance development burden of the middleware device can be greatly reduced.
Drawings
FIG. 1 is a schematic diagram of an adaptation middleware device for a rule engine according to a first embodiment of the present invention;
FIG. 2 is a schematic structural diagram of an adaptation middleware device facing a rule engine according to a first embodiment of the present invention;
FIG. 3 is a flow chart of a rule configuration method in a second embodiment of the present invention;
fig. 4 is a flowchart of a fact rule matching method in the third embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.
Example 1
Fig. 1 is a schematic structural diagram of an adaptation middleware device for a rule engine according to a first embodiment of the present invention, where, as shown in fig. 1, the device includes: an interface calling unit 110, a rule engine routing unit 120, a rule fact generating unit 130, and a rule calculation calling unit 140.
The interface calling unit 110 is used for providing a fact execution interface and a rule configuration interface to the outside, providing a general interface service to the outside, and automatically updating the execution interface. The rule engine routing unit 120 is configured to identify and parse the interface call request sent by the interface call unit, and distribute the parsed interface call request to the corresponding rule fact generating unit 130, and update the routing configuration in real time according to the rule upgrading situation. The rule fact generation unit 130 is configured to parse the rule engine type of the interface call request, and generate facts or rules of the rule engine according to the parsing result. The rule calculation invoking unit 140 is configured to interact with the underlying rule engine node.
The interface call request comprises a fact call request and a rule configuration request, and different rule engines of different types need to be configured with different rule calculation call units.
On the basis of the above embodiment, fig. 2 is a schematic structural diagram of an adaptation middleware device for a rule engine according to a first embodiment of the present invention. As shown in fig. 2, the interface call unit includes an interface wrapper, a fact parser, and a rule parser.
The interface package is used for providing a rule configuration interface and a fact execution interface; the fact analyzer is used for analyzing and checking parameters of the fact message; the rule parser is used for parsing and checking the rules.
The rule configuration interface comprises a rule deployment interface and a rule update interface.
Optionally, the interface wrapper includes a fact executor and a rule configurator. The fact executor is used for receiving a fact call request sent by the upper layer service through the fact execution interface, and calling the fact analyzer to verify the fact call request; if the verification is passed, the fact call request is sent to a rule engine routing unit; the fact executor is further configured to receive an execution result returned by the rule engine routing unit, and return the execution result to the upper layer service. The rule configurator is used for receiving a rule configuration request sent by the upper layer service through the rule configuration interface, and calling the rule analyzer to verify the rule configuration request; if the verification is passed, a rule configuration request is sent to a rule engine routing unit; the rule configurator is also used for receiving the execution result returned by the rule engine routing unit, returning the execution result to the upper layer service, and validating the newly added or updated fact execution interface.
Specifically, the rule configurator is used for processing call requests such as initial deployment, updating and upgrading of rules, checking call parameters and generating a rule configuration request for newly adding or updating a rule package, and completing automatic updating of the fact execution interface according to an analysis result of the rule analyzer.
Optionally, the fact parser includes a fact parser operator and a fact checker operator; the rule parser includes a rule validation operator and a rule parsing operator. The fact analysis operator is used for formatting and formalizing verification of the fact call request and analyzing the fact call request; the fact check operator is used for performing content check on the fact call request with the analysis completed. The rule verification operator is used for carrying out format verification and formalization verification on the rule to be deployed or updated in the rule configuration request; the rule analysis operator is used for analyzing the rules passing the format verification and the formalization verification so as to dynamically update the fact execution interface.
The fact that the real parsing operator is used for formatting and formalizing verification of the fact that the fact calls requests is called is verified whether a problem or a bug exists in the format can be understood. The fact check operator is used for verifying the content of the parsed fact call request, which can be understood as verifying the transmission parameters and the transmission information of the content verification of the parsed fact call request. The rule verification operator is used for performing format verification and formalization verification on the rule to be deployed or updated in the rule configuration request, and can be understood as verifying whether the rule to be deployed or updated has a problem or vulnerability in code format.
Alternatively, as shown in FIG. 2, the rule engine routing unit includes a route resolver and a route distributor. The route parser includes a route mapping operator and a route updating operator. The route mapping operator is used for analyzing the interface call request sent by the interface call unit and identifying a target address according to the route configuration information; the route update operator is used for automatically updating the route configuration in real time after rule deployment or updating; the route distributor is used for distributing the interface call request to the rule fact generating unit corresponding to the target address according to the analysis result of the route analyzer.
Specifically, the rule engine routing unit analyzes the received interface call request to obtain a target address, and distributes the interface call request to the rule fact generation unit corresponding to the target address. And the device is also used for receiving the execution result returned by the rule fact generating unit and forwarding the execution result to the interface calling unit. When the interface call request is a rule configuration request, the routing mapping operator analyzes rule facts in the execution result to generate unit addresses, and the routing configuration information in the routing updating operator is updated.
Alternatively, as shown in fig. 2, the rule fact generation unit includes a fact rule selector, a fact match generator, a rule match generator, and an engine adapter. The fact rule selector is used for analyzing the operation type of the interface call request and distributing the interface call request to the fact match generator or the rule match generator. The fact match generator is used for processing the fact call request; the rule matching generator user processes the rule configuration request. The engine adapter is used for distributing the fact call request processed by the fact match generator or the rule configuration request generated by the rule match generator to the corresponding rule calculation call unit and receiving the rule calculation result returned by the rule calculation call unit.
Optionally, the fact matching generator includes a data parsing operator and a message converting operator; the rule matching generator comprises a data analysis operator, a rule compiling operator, a rule deployment operator and a rule upgrading operator. The data analysis operator is used for a fact call request; the message conversion operator is used for carrying out format conversion on the fact call request according to the message format required by the rule engine. The data analysis operator is used for analyzing the rule configuration request and transmitting the analysis result into the rule compiling operator. The rule compiling operator is used for compiling the parsed rule configuration request to generate a rule file package. The rule deployment operator is used for deploying the rule file package to the rule engine node; the rule update operator is used to update the rule file package to the rule engine node.
Specifically, the fact matching generator may work as follows: and receiving a fact execution request sent by the fact rule selector, completing the analysis of the fact execution request through a data analysis operator, generating a fact message conforming to the rule engine specification through a message conversion operator, packaging the fact message into the fact execution request message, and sending a processing result to an engine adapter.
Specifically, the working process of the rule matching generator may be: receiving and analyzing a rule configuration request sent by a fact rule selector; calling a rule compiling operator to complete the compiling operation of the rule; according to the request type, calling a corresponding rule deployment operator or a rule update operator to encapsulate a rule configuration operation request, and completing the new addition or upgrading of the rule through an engine adapter; 4. and returning the processing result to the rule engine routing unit.
Optionally, as shown in fig. 2, the rule calculation invoking unit includes a rule calculation driver and a message processor. The rule calculation driver is used for completing rule deployment and fact rule calculation on the rule engine point nodes; the message processor is used for returning the execution result to the upper-layer rule fact generating unit.
Specifically, the working procedure of the rule calculation calling unit may be: receiving a rule configuration request sent by a rule fact generating unit; according to the request type, the rule calculation driver upgrades rule deployment to the rule engine node or completes rule calculation through the rule engine node; the processing result is returned to the rule calculation calling unit via the message processor.
The embodiment discloses an adaptation middleware device facing a rule engine. Comprising the following steps: the system comprises an interface calling unit, a rule engine routing unit, a rule fact generating unit and a rule calculation calling unit; the interface calling unit is used for providing a fact execution interface and a rule configuration interface to the outside, providing a general interface service to the outside and automatically updating the execution interface; the rule engine routing unit is used for identifying and analyzing the interface call request transmitted by the interface call unit, distributing the analyzed interface call request to the corresponding rule fact generation unit, and updating the routing configuration in real time according to the rule upgrading condition; the interface call request comprises a fact call request and a rule configuration request; the rule fact generation unit is used for analyzing the type of the rule engine requested by the interface call and generating facts or rules of the rule engine according to the analysis result; the rule calculation calling unit is used for interacting with the bottom layer rule engine node; wherein, different rule engines need to be configured with different rule calculation calling units. The operation and maintenance development burden of the middleware device can be greatly reduced.
Example two
Fig. 3 is a flowchart of a rule configuration method provided in the second embodiment of the present invention, where the method is performed by the rule engine oriented adaptation middleware device in the foregoing embodiment, as shown in fig. 3, and the method includes the following steps:
s310, a rule configuration request sent by an upper layer service is received.
S320, verifying the rule configuration request.
S330, if the verification is passed, analyzing key rule information in the rule configuration request, and updating a fact execution interface based on the key rule information;
s340, compiling the rule in the rule configuration request, and deploying or updating the compiled rule to the rule engine node.
Specifically, the rule configuration method comprises the following steps:
1. the upper layer business application sends the rule configuration request to the rule configurator through a rule configuration interface externally provided by the calling device.
2. After receiving the rule configuration request, the rule configurator performs validity and validity check on the rule configuration request, and if the verification fails, the subsequent operation is terminated;
3. the verification is passed, the rule configurator calls a rule verification operator in the rule analyzer to complete format verification and formalization verification of rule codes in the rule configuration request, and if the verification fails, the subsequent operation is terminated;
4. and the verification is passed, the rule configurator calls the rule analysis operator in the rule analyzer to analyze the key information of the rule, realizes the automatic updating configuration of the fact execution interface, and sends a rule configuration request to the rule engine routing unit. The rule configuration operation comprises a full life cycle operation flow of initial deployment or updating of rules, and can realize the new addition or updating of the rule engine on the bottom node of the rule engine.
5. The rule configuration request is distributed by the rule engine routing unit to the specified rule fact generation unit.
6. After receiving a rule configuration request, the corresponding rule fact generating unit calls a corresponding rule matching generator to complete compiling and configuration of rules, and the engine adapter sends a processing result to the rule calculation calling unit;
7. the rule calculation calling unit deploys or upgrades the rule to the bottom layer rule engine node through the rule calculation driver, obtains the engine address information after deployment and update, returns the engine address information to the rule engine routing unit through the message processor, updates the routing configuration information in the routing matching operator by means of the routing updating operator, and realizes automatic updating configuration of the routing information;
8. after receiving the successful configuration result of the rule, the rule configurator takes effect of automatic update configuration of the fact executor on the external interface, and the subsequent upper-layer business application can directly call the newly added or updated fact external execution interface.
According to the technical scheme, the rule is automatically configured through the rule engine-oriented adaptation middleware device, and the rule configuration efficiency and convenience are improved.
Example III
Fig. 4 is a flowchart of a fact rule matching method provided by the third embodiment of the present invention, where the method is performed by the rule engine oriented adaptation middleware device according to the foregoing embodiment, as shown in fig. 4, and the method includes:
s410, receiving a fact call request sent by an upper layer service.
S420, verifying the fact call request.
S430, if the verification is passed, matching the target fact rule to the rule engine node according to the fact call request.
Specifically, the implementation procedure of the fact rule matching method in this embodiment may be:
1. the upper layer business application sends a fact calling request to a fact executor through a fact executing interface externally provided by the calling device;
2. after receiving the fact call request, the fact executor calls a fact analyzer to perform validity check on the fact call request;
3. the fact analysis operator in the fact analyzer completes the message analysis of the fact call request, if the analysis fails, the subsequent operation is terminated;
4. the analysis is completed, a fact checking operator in the fact analyzer completes the key information check of the fact message, if the check fails, the subsequent operation is terminated;
5. the analysis and verification are completed, a fact execution operation request is created and distributed to a specified rule fact generation unit through a rule engine routing unit;
6. the corresponding rule fact generating unit calls a corresponding fact matching generator to generate an adapted fact message after receiving a fact executing operation request, and the intelligent engine adapter sends a processing result to the rule calculation calling unit;
7. the rule calculation calling unit sends the processed fact message to the bottom layer rule engine through the rule calculation driver, and the rule engine returns a calculation result through the message processor after completing rule calculation.
According to the technical scheme, the fact rule is matched through the rule engine-oriented adaptation middleware device, so that the matching efficiency and accuracy can be improved.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (10)
1. A rule engine oriented adaptation middleware apparatus comprising: the system comprises an interface calling unit, a rule engine routing unit, a rule fact generating unit and a rule calculation calling unit;
the interface calling unit is used for providing a fact execution interface and a rule configuration interface to the outside, providing a general interface service to the outside and automatically updating the execution interface;
the rule engine routing unit is used for identifying and analyzing the interface call request transmitted by the interface call unit, distributing the analyzed interface call request to the corresponding rule fact generation unit, and updating the routing configuration in real time according to the rule upgrading condition; wherein the interface call request comprises a fact call request and a rule configuration request;
the rule fact generation unit is used for analyzing the type of the rule engine for calling the request, and generating facts or rules of the rule engine according to the analysis result;
the rule calculation calling unit is used for interacting with the bottom layer rule engine node; wherein, different rule engines need to be configured with different rule calculation calling units.
2. The apparatus of claim 1, wherein the interface call unit comprises an interface wrapper, a fact parser, and a rule parser;
the interface package is used for providing a rule configuration interface and a fact execution interface; the fact analyzer is used for analyzing and checking parameters of the fact message; the rule analyzer is used for analyzing and checking the rule; the rule configuration interface comprises a rule deployment interface and a rule update interface.
3. The apparatus of claim 2, wherein the interface wrapper comprises a fact executor and a rule configurator;
the fact executor is used for receiving a fact call request sent by the upper layer service through the fact execution interface, and calling the fact analyzer to check the fact call request; if the verification is passed, the fact call request is sent to the rule engine routing unit; the fact executor is further configured to receive an execution result returned by the rule engine routing unit, and return the execution result to an upper layer service;
the rule configurator is used for receiving a rule configuration request sent by the upper layer service through the rule configuration interface and calling the rule analyzer to verify the rule configuration request; if the verification is passed, the rule configuration request is sent to the rule engine routing unit; the rule configurator is also used for receiving the execution result returned by the rule engine routing unit, returning the execution result to the upper layer service, and validating the newly added or updated fact execution interface.
4. The apparatus of claim 3, wherein the fact parser comprises a fact parser operator and a fact verifier operator; the rule analyzer comprises a rule verification operator and a rule analysis operator;
the fact analysis operator is used for formatting and formalizing verification of the fact call request and analyzing the fact call request; the fact check operator is used for performing content check on the fact call request after analysis is completed;
the rule verification operator is used for carrying out format verification and formalization verification on the rule to be deployed or updated in the rule configuration request; the rule analysis operator is used for analyzing the rules passing the format verification and the formalization verification so as to dynamically update the fact execution interface.
5. The apparatus of claim 1, wherein the rule engine routing unit comprises a route resolver and a route distributor; the route analyzer comprises a route mapping operator and a route updating operator;
the route mapping operator is used for analyzing the interface call request sent by the interface call unit and identifying a target address according to the route configuration information; the route update operator is used for automatically updating the route configuration in real time after rule deployment or updating; the route distributor is used for distributing the interface calling request to the rule fact generating unit corresponding to the target address according to the analysis result of the route analyzer.
6. The apparatus of claim 1, wherein the rule fact generation unit comprises a fact rule selector, a fact match generator, a rule match generator, and an engine adapter;
the fact rule selector is used for analyzing the operation type of the interface call request and distributing the interface call request to a fact match generator or a rule match generator;
the fact match generator is used for processing the fact call request; the rule matching generator user processes the rule configuration request;
the engine adapter is used for distributing the fact call request processed by the fact match generator or the rule configuration request generated by the rule match generator to the corresponding rule calculation call unit and receiving the rule calculation result returned by the rule calculation call unit.
7. The apparatus of claim 6, wherein the fact match generator comprises a data parsing operator and a message transformation operator; the rule matching generator comprises a data analysis operator, a rule compiling operator, a rule deployment operator and a rule upgrading operator;
wherein the data parsing operator is used for the fact call request; the message conversion operator is used for carrying out format conversion on the fact call request according to the message format required by the rule engine;
the data analysis operator is used for analyzing the rule configuration request and transmitting the analysis result into the rule compiling operator; the rule compiling operator is used for compiling the parsed rule configuration request to generate a rule file package; the rule deployment operator is used for deploying the rule file package to a rule engine node; the rule updating operator is used for updating the rule file package to a rule engine node.
8. The apparatus of claim 1, wherein the rule calculation invoking unit comprises a rule calculation driver and a message processor;
the rule calculation driver is used for completing rule deployment and fact rule calculation on the rule engine point nodes; the message processor is used for returning the execution result to the upper-layer rule fact generation unit.
9. A rule configuration method, characterized in that the method is performed by a rule engine oriented adaptation middleware device according to any of claims 1-8, comprising:
receiving a rule configuration request sent by an upper layer service;
verifying the rule configuration request;
if the verification is passed, analyzing key rule information in the rule configuration request, and updating a fact execution interface based on the key rule information;
compiling the rule in the rule configuration request, and deploying or updating the compiled rule to the rule engine node.
10. A fact rule matching method, characterized in that the method is performed by a rule engine oriented adaptation middleware device according to any of claims 1-8, comprising:
receiving a fact call request sent by an upper layer service;
verifying the fact call request;
and if the verification is passed, matching the target fact rule to the rule engine node according to the fact call request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311622320.6A CN117632539A (en) | 2023-11-30 | 2023-11-30 | Rule engine-oriented adaptation middleware device, configuration method and matching method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311622320.6A CN117632539A (en) | 2023-11-30 | 2023-11-30 | Rule engine-oriented adaptation middleware device, configuration method and matching method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117632539A true CN117632539A (en) | 2024-03-01 |
Family
ID=90024833
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311622320.6A Pending CN117632539A (en) | 2023-11-30 | 2023-11-30 | Rule engine-oriented adaptation middleware device, configuration method and matching method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117632539A (en) |
-
2023
- 2023-11-30 CN CN202311622320.6A patent/CN117632539A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110795078B (en) | Architecture method of APP engineering operation system based on IOS system | |
| CN108845940B (en) | Enterprise-level information system automatic function testing method and system | |
| CN112306881B (en) | Analog data generation method, device, equipment and storage medium | |
| CN111258900A (en) | Interface test script generation method, system, equipment and storage medium | |
| US20170003939A1 (en) | Code generation | |
| CN106897153B (en) | Method and system for calling application programming interface | |
| CN111290958A (en) | Method and device for debugging intelligent contract | |
| CN111158741A (en) | Method and device for monitoring change of dependency relationship of business module on third-party class library | |
| CN112433722A (en) | Modular system code development method, device, equipment and system | |
| CN114398293A (en) | Interface test case generation method, electronic device and storage medium | |
| CN112148343A (en) | Rule issuing method and device and terminal equipment | |
| CN111782526A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN114844814A (en) | Pressure testing method and device | |
| Mahmood et al. | A framework for automated API fuzzing at enterprise scale | |
| CN112132530B (en) | Visual dynamic flow arranging method and system | |
| CN113885876A (en) | Parameter checking method, device, storage medium and computer system | |
| CN111651169B (en) | Block chain intelligent contract operation method and system based on web container | |
| CN113590465A (en) | Method for automatically generating mock service based on SDK | |
| CN115525534A (en) | Test case generation method and platform based on swagger interface test | |
| US10606569B2 (en) | Declarative configuration elements | |
| US9058313B2 (en) | Test method for distributed processing system and distributed processing system | |
| WO2023125755A1 (en) | Service request processing method and apparatus based on large-scale cluster, and device and medium | |
| Rahman et al. | A Framework for Modelling Blockchain based Supply Chain Management System to ensure soundness of Smart Contract Workflow. | |
| CN117632539A (en) | Rule engine-oriented adaptation middleware device, configuration method and matching method | |
| CN116414774A (en) | File migration method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |