CN109918079B - Rule updating method and device of rule engine system and computer equipment - Google Patents
Rule updating method and device of rule engine system and computer equipment Download PDFInfo
- Publication number
- CN109918079B CN109918079B CN201910101290.1A CN201910101290A CN109918079B CN 109918079 B CN109918079 B CN 109918079B CN 201910101290 A CN201910101290 A CN 201910101290A CN 109918079 B CN109918079 B CN 109918079B
- Authority
- CN
- China
- Prior art keywords
- executable file
- rule
- service
- updating
- service type
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Information Transfer Between Computers (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a rule updating method, a rule updating device, computer equipment and a storage medium of a rule engine system, wherein the method comprises the following steps: acquiring an updating instruction for updating a service rule in a rule engine system; reading a target executable file with the latest version from a specified database according to an updating instruction, and acquiring a first service type corresponding to a service rule according to the target executable file; calculating an important coefficient corresponding to the first service type according to the weights corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type; judging whether the important coefficient is larger than a preset threshold value or not; if so, the target executable file is updated in the independent server environment, and if not, the target executable file is updated in the public server environment, so that convenience and rapidness are realized, the business rules do not need to be manually deployed by depending on experience, and the cross influence of important business rules can be avoided while the resources are saved.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a rule updating method and apparatus for a rule engine system, a computer device, and a storage medium.
Background
The rule engine is a component for separating the business decision from the application program code and compiling the business decision by using a predefined semantic module, receives data input, explains the business rule and makes the business decision according to the business rule, and can be applied to various businesses.
When the existing rule engine system updates the service rules, firstly a rule set needs to be exported, then the rule set is modified offline, then the modified rule set is packed into a compressed packet, then the compressed packet is uploaded to a rule compiling platform, an executable packet is generated by manually triggering compiling, and finally the executable packet is downloaded to be deployed so as to realize updating.
Disclosure of Invention
The invention mainly aims to provide a rule updating method and device of a rule engine system, computer equipment and a storage medium for improving efficiency, and aims to solve the problem that the business rule updating efficiency in the existing rule engine system is low.
Based on the above object, the present invention provides a rule updating method for a rule engine system, comprising:
acquiring an updating instruction for updating a service rule in a rule engine system;
reading a target executable file of the latest version from a specified database according to the updating instruction, wherein the target executable file is a file which is generated by a preset business rule set and can run in a server;
acquiring a service type corresponding to the service rule according to the target executable file, and recording the service type as a first service type, wherein the same service type comprises a plurality of different services;
calculating an important coefficient corresponding to the first service type according to the weight corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type;
judging whether the important coefficient is larger than a preset threshold value or not;
and if the target executable file is not updated in the public server environment, updating the target executable file in the independent server environment.
Further, the step of calculating an importance coefficient corresponding to the first service type according to the weights corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type includes:
the importance coefficient is calculated using the following formula:
R＝(W1+W2+…+Wn)/(π*W1/2arctan(C1)+π*W2/2arctan(C2)+…+π*Wn/2arctan(Cn))；
n services are preset in the first service type, R is the significant coefficient, W is the weight of each service in the first service type, and C is the usage amount of each service in the first service type.
Further, before the step of calculating the importance coefficient corresponding to the first service type according to the weights corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type, the method includes:
calling a history record of each service used in the first service type each time;
and counting the use times of each service according to the history record, and recording the use times as the use amount.
Further, before the step of obtaining an update instruction for updating the business rule in the rule engine system, the method includes:
receiving rule parameters input by a user in a rule editing interface to form a target rule file;
analyzing the target rule file into a target prl file;
compiling the prl file into the target executable file;
storing the target executable file into the designated database;
defining the target executable file as the latest version in the designated database through a tag according to a history file, wherein the history file is an executable file which is stored in the designated database before the target executable file is stored in the designated database.
Further, the step of updating the target executable file in a separate server environment includes:
replacing the executable file already deployed in the independent server with the target executable file;
and deploying the target executable file to complete the updating.
Further, after the step of updating the target executable file in the independent server environment, the method comprises:
acquiring first feedback information which is returned by the independent server and does not adapt to the updated service rule version, wherein the inadaptation of the updated service rule version comprises that the target executable file cannot be updated in the independent server environment and the target executable file cannot run after the target executable file is updated in the independent server environment;
re-reading the executable file from the designated database according to the first feedback information;
replacing the target executable file with the executable file and deploying the executable file in the independent server environment;
or, after the step of updating the target executable file in the common server environment, the method includes:
acquiring second feedback information which is returned by the public server and does not adapt to the updated service rule version, wherein the inadaptation of the updated service rule version comprises that the target executable file cannot be updated in the public server environment and the target executable file cannot run after the target executable file is updated in the public server environment;
re-reading the executable file from the designated database according to the second feedback information;
replacing the target executable file with the executable file and deploying the executable file in the common server environment.
Further, after the step of obtaining the service type of the service rule according to the target executable file and recording as the first service type, the method includes:
judging whether the updating mode for updating the business rule is according to the important coefficient;
if the updating mode is updating according to the important coefficient, generating a calculation instruction for calculating the important coefficient; if the updating mode is not updating according to the important coefficient, judging whether the operation quantity of the service rule corresponding to the first service type exceeds a preset operation quantity or not;
and if the service rule operation amount exceeds a preset operation amount, updating the target executable file in the independent server environment, and if the service rule operation amount does not exceed the preset operation amount, updating the target executable file in the public server environment.
The present invention also provides a rule updating apparatus of a rule engine system, comprising:
the system comprises an acquisition instruction unit, a rule engine system and a processing unit, wherein the acquisition instruction unit is used for acquiring an updating instruction for updating a service rule in the rule engine system;
a file reading unit, configured to read a target executable file of a latest version from a specified database according to the update instruction, where the target executable file is a file that is generated by a preset service rule set and is capable of running in a server;
the type obtaining unit is used for obtaining a service type corresponding to the service rule according to the target executable file and recording the service type as a first service type, wherein the same service type comprises a plurality of different services;
a calculating coefficient unit, configured to calculate an important coefficient corresponding to the first service type according to weights corresponding to all services in the first service type and usage amounts corresponding to the services in the first service type;
the judgment coefficient unit is used for judging whether the important coefficient is larger than a preset threshold value or not;
and the file updating unit is used for updating the target executable file in an independent server environment when the importance coefficient is judged to be larger than a preset threshold value, and updating the target executable file in a public server environment if the importance coefficient is not judged to be larger than the preset threshold value.
The invention also provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method when executing the computer program.
The invention also provides a computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method.
The invention has the beneficial effects that: the executable file is directly read when the rule is updated, and then the executable file is deployed in the corresponding server environment according to the calculated important coefficient of the rule system, so that the method is convenient and fast, the business rule is not required to be deployed manually by depending on experience, the deployment is targeted, the important business rule can be prevented from being influenced in a cross mode while resources are saved, in addition, the business rule can be modified in real time, and the change of the business market can be responded quickly.
Drawings
FIG. 1 is a diagram illustrating the steps of a rule updating method of a rule engine system according to an embodiment of the present invention;
FIG. 2 is a block diagram of a rule updating apparatus of the rule engine system according to an embodiment of the present invention;
fig. 3 is a block diagram schematically illustrating a structure of a computer apparatus according to an embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, the rule updating method of the rule engine system in the present embodiment includes:
step S1: acquiring an updating instruction for updating a service rule in a rule engine system;
step S2: reading a target executable file of the latest version from a specified database according to the updating instruction, wherein the target executable file is a file which is generated by a preset business rule set and can run in a server;
step S3: acquiring a service type corresponding to the service rule according to the target executable file, and recording the service type as a first service type, wherein the same service type comprises a plurality of different services;
step S4: calculating an important coefficient corresponding to the first service type according to the weight corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type;
step S5: judging whether the important coefficient is larger than a preset threshold value or not;
step S6: and if the target executable file part is in the independent server environment, updating the target executable file part in the public server environment.
As described in step S1, when an update instruction for updating the business rule of the rule engine system is obtained, the current business rule may be updated according to the update instruction, where the business rule is the rule data corresponding to a certain business type, and the rule data includes the rule code. The update instruction may be generated according to an update request initiated by a user, or may be generated by automatically triggering when the rule engine system is restarted.
As described in step S2, the target executable file is a file generated by a preset business rule set and executable in the server, and the target executable file is a jar package capable of being deployed and deployed, and the target executable file is generated by the system according to the rule parameters input by the user and stored in a specified database, such as the MongoDB database.
As described in step S3, the business rules of the rule engine system are applied to different businesses, and part of the different businesses may use the same business rule, so that the different businesses can be classified to obtain a plurality of business types, and each business type includes a plurality of different businesses, and each business type corresponds to one business rule. Since the target executable file is generated from the rule parameter input by the user, and the rule parameter includes the service information, the corresponding service type can be obtained from the information, so that the service type of the corresponding service rule can be obtained according to the target executable file.
As described in step S4, the business rules may be updated according to the importance coefficients by calculating the importance coefficients of the first business type, and the business rules may be deployed in different server environments when updating due to different importance degrees of the business types, and the importance degrees of the business types are determined by the businesses included in the business types, for example, a business type includes four businesses, i.e., a financial transaction, a normal transaction, a core business, and a non-core business, where the financial transaction is important and the weight is relatively high. Therefore, the importance coefficient can be calculated according to the importance degree of all the services in the first service type, namely the preset weight corresponding to each service. Meanwhile, in order to ensure smooth operation after the service rule is deployed, the usage amount of the first service type needs to be known so as to be better distributed and updated to the corresponding server environment, and therefore the important coefficients need to be calculated by the usage amount of each service in the first service type.
As described above in steps S5-S6, the above-described updating of the target executable file in the server environment may be achieved by deploying the target executable file in the server. Because different business rules can be deployed in different server environments during updating, the server environments are divided into independent server environments and public server environments, wherein the business rules deployed in the independent server environments can be independently operated in the independent environments, and the business rules deployed in the public server environments can be deployed with a plurality of different business rules, and a plurality of business rules are operated simultaneously, so that the targeted deployment can save resources and can also avoid that important business rules are cross-influenced by unimportant business rules during operation, so that the important business rules need to be deployed in the independent server environments, the unimportant business rules can be deployed in the public server environments, and after the business types corresponding to the business rules are obtained, the business types can be weighted according to all the businesses in the business types, and calculating an important coefficient corresponding to the service type according to the usage amount corresponding to each service in the service types, wherein the higher the important coefficient is, the more important the service type is, when the important coefficient is larger than a preset threshold value, the service rule corresponding to the service type can be deployed to an independent server environment, otherwise, the service rule can be directly deployed to a public server environment.
In one embodiment, the importance coefficient is calculated using the following formula:
R＝(W1+W2+…+Wn)/(π*W1/2arctan(C1)+π*W2/2arctan(C2)+…+π*Wn/2arctan(Cn))；
n services are preset in the first service type, R is the significant coefficient, W is the weight of each service in the first service type, and C is the usage amount of each service in the first service type.
In this embodiment, the first service type is preset with four services, which are respectively financial transaction, normal transaction, core service, and non-core service, and then W1, W2, W3, and W4 are weights of financial transaction, normal transaction, core service, and non-core service types in sequence, where W1 > W2 > W3 > W4, c1, c2, c3, and c4 are usage amounts of the financial transaction, normal transaction, core service, and non-core service in sequence. The importance coefficient of the first service type is calculated through the above formula, the importance system is between 0 and 1, the higher the importance coefficient is, the more important the first service type is, at this time, the importance coefficient may be compared with a preset threshold, in this embodiment, the preset threshold may be 0.7, when the threshold is exceeded, the target executable file may be deployed in an independent server environment, and if the preset threshold is not exceeded, the rule system is not important, and may be deployed in a public service environment.
In one embodiment, before the step S4, the method includes:
step S41: calling a history record of each service used in the first service type each time;
step S42: and counting the use times of each service according to the history record, and recording the use times as the use amount.
In this embodiment, since the usage amount of each service in the first service type is needed to calculate the important coefficient, the usage amount of each service needs to be obtained before calculation, and it is known that each service is recorded when being used, for example, in a system log, so the usage number of the service can be obtained by calling the corresponding log, looking up the record in the log, and the usage number is recorded as the usage amount, and the usage amount of each service in the first service type can be obtained by calling and looking up the corresponding record.
In one embodiment, before the step S1, the method includes:
step S01: receiving rule parameters input by a user in a rule editing interface to form a target rule file;
step S02: analyzing the target rule file into a target prl file;
step S03: compiling the prl file into the target executable file;
step S04: storing the target executable file into the designated database;
step S05: defining the target executable file as the latest version in the designated database through a tag according to a history file, wherein the history file is an executable file which is stored in the designated database before the target executable file is stored in the designated database.
As described in step S01, the rule editing interface is displayed by a browser, and after receiving a rule parameter input by a user (e.g., a service person), the rule parameter is added to a service rule set preset by a developer to form a target rule file corresponding to the rule parameter, and when filling in different rule parameters by the user, different target rule files are formed, where the target rule files exist in html. In this embodiment, after the user finishes inputting the rule parameters in the rule editing interface, the user can input a forming instruction, and the system can form the target rule file according to the forming instruction and the service rule set added with the rule parameters.
As described in the above step S02, the prl file is a code program corresponding to the rule, and the operation of the code program can implement the service policy corresponding to the service rule, in this embodiment, the step of parsing the target rule file into the target prl file may specifically be as follows: dividing the target rule file into three parts of where, then and else according to the logical relation based on the parameters input by the user, and then packing and combining the three parts in turn to form the target prl file.
As described in the above steps S03 and S04, the target prl file is compiled into the target executable file, that is, the target prl file is packaged into a jar package which can be deployed, the jar package is the target executable file, and then the target executable file is stored in the designated database.
As described in step S05, in the designated database, the target executable file is defined to be the latest version of the target executable file by tag, the version is defined on the basis of the old version corresponding to the history file, the history file is the executable file existing before the target executable file is stored in the designated database, if an executable file is first stored in the MongoDB, the executable file is defined as the first generation version, then the user updates again, the executable file newly stored in the MongoDB is defined as the second generation version, and so on, each update defines the corresponding version on the basis of the previous version, and the target executable file is the latest version in the designated database.
By the method, when the rule needs to be updated, a user can generate the latest version of the current rule directly by filling parameters in the rule editing interface, the user can modify the rule in real time, the updating speed is accelerated, the efficiency is greatly improved, online modification and uploading are not needed during each updating, rule updating steps are reduced, and influence caused by artificial errors is avoided.
In an embodiment, the step of deploying and updating the target executable file in the independent server environment in step S6 includes:
step S601: replacing the executable file already deployed in the independent server with the latest version of the target executable file;
step S602: and deploying the target executable file to complete the updating.
In this embodiment, after the target executable file is sent to the independent server, the old version of the executable file in the independent server is replaced with the latest version of the target executable file, that is, the executable file covering the old version of the executable file, and the target executable file is deployed, so that rule updating is implemented.
In one embodiment, after the step S6, the method further includes:
step S61: acquiring first feedback information which is returned by the independent server and is not suitable for the update service rule version, wherein the first feedback information comprises that the target executable file cannot be updated in the independent server environment and cannot be operated after the target executable file is updated in the independent server environment;
step S62: re-reading the executable file from the designated database according to the first feedback information;
step S63: replacing the target executable file with the executable file and deploying the executable file;
or, after the step of updating the target executable file in the common server environment, the method includes:
step S61': acquiring second feedback information which is returned by the public server and does not adapt to the updated service rule version, wherein the inadaptation of the updated service rule version comprises that the target executable file cannot be updated in the public server environment and the target executable file cannot run after the target executable file is updated in the public server environment;
step S62': re-reading the executable file from the designated database according to the second feedback information;
step S63': replacing the target executable file with the executable file and deploying the executable file in the common server environment.
In this embodiment, because the target executable file is an updated version, the server does not necessarily adapt to and can run the target executable file, so that after an old version of the executable file is replaced with a latest version of the target executable file, when the server updates the version inappropriately, that is, the server updates the corresponding business rule inappropriately, feedback information is returned at this time, where the update business rule does not adapt to the target executable file, the one is a case where the target executable file cannot be updated in a public server environment, the other is a case where the target executable file cannot be run after the update in the public server environment is completed, and the feedback information is information corresponding to the two cases. After the feedback information is obtained, the executable file of the old version board is read from the designated database again, the updated new version in the server is replaced by the original executable file of the old version, and the situation that the updating is not suitable for operation is avoided.
In another embodiment, after the step S3, the method further includes:
step S7: judging whether the updating mode for updating the business rule is according to the important coefficient;
step S8: if the updating mode is updating according to the important coefficient, generating a calculation instruction for calculating the important coefficient; if the updating mode is not updating according to the important coefficient, judging whether the operation quantity of the service rule corresponding to the first service type exceeds a preset operation quantity or not;
step S9: and if the service rule operation amount exceeds a preset operation amount, updating the target executable file in the independent server environment, and if the service rule operation amount does not exceed the preset operation amount, updating the target executable file in the public server environment.
It can be understood that, instead of determining the deployment environment of the service rule by the significant coefficient, the deployment environment of the service rule may be determined directly according to the operation amount, so after the first service type is obtained, the update method of the service rule is first determined, and there are two update methods, that is, updating according to the significant coefficient and updating according to the operation amount, when the update method is updating according to the significant coefficient, the calculation instruction for generating the calculation significant coefficient is directly generated, the significant coefficient is calculated according to the calculation instruction, and then steps S5-S6 are executed. When the updating mode is not updated according to the important coefficient, the updating mode can be judged according to the operation amount, because of different service types and different users, the operation amounts of the corresponding service rules are different, at the moment, the operation amounts sent to the running servers are also different, the operation amount is small and the operation amount is sent to the public server to run, because the operation amount is small, the public server can simultaneously run a plurality of executable files, and the operation amount is large and the operation amount needs to be sent to an independent server to be independently run by one server, so that the normal running of the program is ensured. Therefore, in steps S8-S9, it is first determined whether the operation amount of the target executable file exceeds a preset operation amount, where the preset operation amount may be set with reference to the operation amount of the server, and when the preset operation amount is exceeded, the target executable file may be issued to the individual server, the old version of the executable file may be replaced with the latest version of the target executable file, and the target executable file may be deployed to complete the update, and if the preset operation amount is not exceeded, the target executable file may be issued to the common server, the old version of the executable file may be replaced with the latest version of the target executable file, and the target executable file may be forgotten to be deployed to complete the update.
Referring to fig. 2, the rule updating apparatus of the rule engine system in this embodiment includes:
an obtaining instruction unit 100, configured to obtain an update instruction for updating a service rule in a rule engine system;
a file reading unit 200, configured to read a target executable file of a latest version from a specified database according to the update instruction, where the target executable file is a file that is generated by a preset service rule set and is capable of running in a server;
a type obtaining unit 300, configured to obtain a service type corresponding to the service rule according to the target executable file, and record the service type as a first service type, where a same service type includes multiple different services;
a coefficient calculating unit 400, configured to calculate an important coefficient corresponding to the first service type according to the weights corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type;
a coefficient determining unit 500, configured to determine whether the significant coefficient is greater than a preset threshold;
an update file unit 600, configured to update the target executable file in an independent server environment when it is determined that the importance coefficient is greater than a preset threshold, and update the target executable file in a public server environment if the importance coefficient is not greater than the preset threshold.
As described in the instruction obtaining unit 100, when an update instruction for updating a service rule of a rule engine system is obtained, a current service rule may be updated according to the update instruction, where the service rule is rule data corresponding to a certain service type, and the rule data includes a rule code. The update instruction may be generated according to an update request initiated by a user, or may be generated by automatically triggering when the rule engine system is restarted.
As described in the foregoing document reading unit 200, the target executable file is a file that is generated by a preset business rule set and can be run in a server, and is a jar package that can be run and deployed, and the target executable file is generated by the system according to rule parameters input by a user and is stored in a specified database, such as a MongoDB database.
As described in the type obtaining unit 300, the service rules of the rule engine system are applied to different services, and a part of the services in the different services may adopt the same service rule, so that the different services may be classified to obtain a plurality of service types, each service type includes a plurality of different services, and each service type corresponds to one service rule. Since the target executable file is generated from the rule parameter input by the user, and the rule parameter includes the service information, the corresponding service type can be obtained from the information, so that the service type of the corresponding service rule can be obtained according to the target executable file.
As described in the above type obtaining unit 300, the business rules may be updated according to the importance coefficients by calculating the importance coefficients of the first business type, and since the importance degrees of the business types are different, the business types are deployed in different server environments when updating, and the importance degrees of the business types are determined by the businesses included in the business types, for example, one business type includes four businesses, i.e., a financial transaction, a normal transaction, a core business, and a non-core business, where the financial transaction is important and the weight is relatively high. Therefore, the importance coefficient can be calculated according to the importance degree of all the services in the first service type, namely the preset weight corresponding to each service. Meanwhile, in order to ensure smooth operation after the service rule is deployed, the usage amount of the first service type needs to be known so as to be better distributed and updated to the corresponding server environment, and therefore the important coefficients need to be calculated by the usage amount of each service in the first service type.
As described in the above-mentioned determination coefficient unit 500 and the update file unit 600, the above-mentioned update of the target executable file in the server environment can be implemented by deploying the target executable file in the server. Because different business rules are deployed in different server environments during updating, wherein the server environments are divided into an independent server environment and a public server environment, the business rules deployed in the independent server environment can be independently operated in the independent environment, and the business rules deployed in the public server environment can be deployed with a plurality of different business rules, and the plurality of business rules are operated simultaneously, so that the targeted deployment can save resources and can also avoid the cross influence of important business rules by unimportant business rules during operation, the important business rules need to be deployed in the independent server environment, the unimportant business rules can be deployed in the public server environment, and after the business types corresponding to the business rules are obtained, the corresponding weights of all the businesses in the business types can be obtained, and calculating an important coefficient corresponding to the service type according to the usage amount corresponding to each service in the service types, wherein the higher the important coefficient is, the more important the service type is, when the important coefficient is larger than a preset threshold value, the service rule corresponding to the service type can be deployed to an independent server environment, otherwise, the service rule can be directly deployed to a public server environment.
In one embodiment, the importance coefficient is calculated using the following formula:
R＝(W1+W2+…+Wn)/(π*W1/2arctan(C1)+π*W2/2arctan(C2)+…+π*Wn/2arctan(Cn))；
n services are preset in the first service type, R is the significant coefficient, W is the weight of each service in the first service type, and C is the usage amount of each service in the first service type.
In this embodiment, the first service type is preset with four services, which are respectively financial transaction, normal transaction, core service, and non-core service, and then W1, W2, W3, and W4 are weights of financial transaction, normal transaction, core service, and non-core service types in sequence, where W1 > W2 > W3 > W4, c1, c2, c3, and c4 are usage amounts of the financial transaction, normal transaction, core service, and non-core service in sequence. The importance coefficient of the first service type is calculated through the above formula, the importance system is between 0 and 1, the higher the importance coefficient is, the more important the first service type is, at this time, the importance coefficient may be compared with a preset threshold, in this embodiment, the preset threshold may be 0.7, when the threshold is exceeded, the target executable file may be deployed in an independent server environment, and if the preset threshold is not exceeded, the rule system is not important, and may be deployed in a public service environment.
In one embodiment, the rule updating apparatus of the step rule engine system includes:
the calling recording unit is used for calling the history record used by each service in the first service type each time;
and the usage counting unit is used for counting the usage times of each service according to the history record and recording the usage times as the usage.
In this embodiment, since the usage amount of each service in the first service type is needed to calculate the important coefficient, the usage amount of each service needs to be obtained before calculation, and it is known that each service is recorded when being used, for example, in a system log, so the usage number of the service can be obtained by calling the corresponding log, looking up the record in the log, and the usage number is recorded as the usage amount, and the usage amount of each service in the first service type can be obtained by calling and looking up the corresponding record.
In an embodiment, the rule updating apparatus of the step rule engine system further includes:
the parameter receiving unit is used for receiving rule parameters input by a user in the rule editing interface so as to form a target rule file;
the analysis file unit is used for analyzing the target rule file into a target prl file;
a compiling file unit, configured to compile the prl file into the target executable file;
a file storage unit, configured to store the target executable file in the specified database;
and the version defining unit is used for defining the target executable file as the latest version through a tag label in the specified database according to a history file, wherein the history file is the executable file which is stored in the specified database before the target executable file is stored in the specified database.
As described in the foregoing parameter receiving unit, the rule editing interface is displayed in a browser manner, after receiving a rule parameter input by a user (e.g., a service person), the rule parameter is added to a service rule set preset by a developer to form a target rule file corresponding to the rule parameter, and when the user fills in different rule parameters, different target rule files are formed, where the target rule files exist in html manner. In this embodiment, after the user finishes inputting the rule parameters in the rule editing interface, the user can input a forming instruction, and the system can form the target rule file according to the forming instruction and the service rule set added with the rule parameters.
As described in the foregoing parsing unit, the prl file is a code program corresponding to the rule, and the operation of the code program can implement a service policy corresponding to the service rule, in this embodiment, the parsing of the target rule file into the target prl file may specifically include the following steps: dividing the target rule file into three parts of where, then and else according to the logical relation based on the parameters input by the user, and then packing and combining the three parts in turn to form the target prl file.
As described above, the compiling file unit and the storing file unit compile the target prl file into the target executable file, that is, the target prl file is compiled into a jar package which can be run and deployed, the jar package is the target executable file, and then the target executable file is stored in the specified database.
As described in the version defining unit, in the specified database, the target executable file is defined to be the latest version of the target executable file through the tag, the version is defined on the basis of the old version corresponding to the history file, the history file is the executable file which exists before the target executable file is stored in the specified database, if an executable file is stored in the MongoDB for the first time, the executable file is defined to be the first generation version, then the user updates the executable file again, the executable file stored in the MongoDB again is defined to be the second generation version, and so on, each update defines the corresponding version on the basis of the previous version, and the target executable file is the latest version in the specified database.
By the method, when the rule needs to be updated, a user can generate the latest version of the current rule directly by filling parameters in the rule editing interface, the user can modify the rule in real time, the updating speed is accelerated, the efficiency is greatly improved, online modification and uploading are not needed during each updating, rule updating steps are reduced, and influence caused by artificial errors is avoided.
In an embodiment, the update file unit 600 includes:
a replacement file unit, configured to replace the executable file already deployed in the independent server with the target executable file of the latest version;
and the deployment file unit is used for deploying the target executable file to complete updating.
In this embodiment, after the target executable file is sent to the independent server, the old version of the executable file in the independent server is replaced with the latest version of the target executable file, that is, the executable file covering the old version of the executable file, and the target executable file is deployed, so that rule updating is implemented.
In one embodiment, the rule updating apparatus of the rule engine system includes:
a first obtaining unit, configured to obtain first feedback information that an updated service rule version returned by the independent server does not adapt to the updated service rule version, where the updated service rule version does not adapt to the updated service rule version and the target executable file cannot run after the update of the target executable file in the independent server environment is completed;
the first re-reading unit is used for re-reading the executable file from the specified database according to the first feedback information;
a first replacement unit, configured to replace the target executable file with the executable file, and deploy the executable file;
the rule updating device of the rule engine system further includes:
a second obtaining unit, configured to obtain second feedback information that an update service rule version returned by the public server does not adapt, where the update service rule version does not adapt to include that the target executable file cannot be updated in the public server environment and the target executable file cannot run after the update in the public server environment is completed;
the second re-reading unit is used for re-reading the executable file from the specified database according to the second feedback information;
and the second deployment unit is used for replacing the target executable file with the executable file and deploying the executable file in the public server environment.
In this embodiment, because the target executable file is an updated version, the server does not necessarily adapt to and can run the target executable file, so that after an old version of the executable file is replaced with a latest version of the target executable file, when the server updates the version inappropriately, that is, the server updates the corresponding business rule inappropriately, feedback information is returned at this time, where the update business rule does not adapt to the target executable file, the one is a case where the target executable file cannot be updated in a public server environment, the other is a case where the target executable file cannot be run after the update in the public server environment is completed, and the feedback information is information corresponding to the two cases. After the feedback information is obtained, the executable file of the old version board is read from the designated database again, the updated new version in the server is replaced by the original executable file of the old version, and the situation that the updating is not suitable for operation is avoided.
In another embodiment, the rule updating apparatus of the rule engine system includes:
a judging mode unit, configured to judge whether an updating mode for updating the service rule is updated according to the significant coefficient;
the judgment operation unit is used for generating a calculation instruction for calculating the important coefficient when the updating mode is based on the updating of the important coefficient; if the updating mode is not updating according to the important coefficient, judging whether the operation quantity of the service rule corresponding to the first service type exceeds a preset operation quantity or not;
and the operation updating unit is used for updating the target executable file in the independent server environment if the service rule operation amount exceeds a preset operation amount, and updating the target executable file in the public server environment if the service rule operation amount does not exceed the preset operation amount.
It can be understood that, in addition to determining the deployment environment of the service rule through the important coefficient, the deployment environment of the service rule can be determined directly according to the operation amount, so after the first service type is obtained, the update method of the service rule is first determined, and there are two update methods, that is, updating according to the important coefficient and updating according to the operation amount, when the update method is updating according to the important coefficient, the calculation instruction for generating the calculation important coefficient is directly generated, the important coefficient is calculated according to the calculation instruction, and then the operation is performed according to the above-mentioned determination coefficient unit 500 and the update file unit 600. When the updating mode is not updated according to the important coefficient, the updating mode can be judged according to the operation amount, because of different service types and different users, the operation amounts of the corresponding service rules are different, at the moment, the operation amounts sent to the running servers are also different, the operation amount is small and the operation amount is sent to the public server to run, because the operation amount is small, the public server can simultaneously run a plurality of executable files, and the operation amount is large and the operation amount needs to be sent to an independent server to be independently run by one server, so that the normal running of the program is ensured. Therefore, whether the operation amount of the target executable file exceeds the preset operation amount or not is judged, the preset operation amount can be set by referring to the operation amount of the server, when the preset operation amount is exceeded, the target executable file can be issued to the independent server, the executable file of the old version is replaced by the target executable file of the latest version, deployment is carried out to complete updating, if the preset operation amount is not exceeded, the target executable file is issued to the public server, the executable file of the old version is replaced by the target executable file of the latest version, and the target executable file is forgotten to be deployed to complete updating.
Referring to fig. 3, an embodiment of the present invention further provides a computer device, where the computer device may be a server, and an internal structure of the computer device may be as shown in fig. 3. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the computer designed processor is used to provide computational and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store all the data required to update the rules in the rules engine system. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a rule updating method of a rule engine system.
The processor executes the steps of the rule updating method of the rule engine system: acquiring an updating instruction for updating a service rule in a rule engine system; reading a target executable file of the latest version from a specified database according to the updating instruction, wherein the target executable file is a file which is generated by a preset business rule set and can run in a server; acquiring a service type corresponding to the service rule according to the target executable file, and recording the service type as a first service type, wherein the same service type comprises a plurality of different services; calculating an important coefficient corresponding to the first service type according to the weight corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type; judging whether the important coefficient is larger than a preset threshold value or not; and if the target executable file is not updated in the public server environment, updating the target executable file in the independent server environment.
The step of calculating, by the computer device, an importance coefficient corresponding to the first service type according to the weights corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type includes: the importance coefficient is calculated using the following formula: r ═ W1+W2+…+Wn)/(π*W1/2arctan(C1)+π*W2/2arctan(C2)+…+π*Wn/2arctan(Cn) ); wherein n services are preset in the first service typeR is the importance coefficient, W is the weight of each service in the first service type, and C is the usage amount of each service in the first service type.
In an embodiment, before the step of calculating the importance coefficient corresponding to the first service type according to the weights corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type, the method includes: calling a history record of each service used in the first service type each time; and counting the use times of each service according to the history record, and recording the use times as the use amount.
In an embodiment, before the step of obtaining the update instruction for updating the business rule in the rule engine system, the method includes: receiving rule parameters input by a user in a rule editing interface to form a target rule file; analyzing the target rule file into a target prl file; compiling the prl file into the target executable file; storing the target executable file into the designated database; defining the target executable file as the latest version in the designated database through a tag according to a history file, wherein the history file is an executable file which is stored in the designated database before the target executable file is stored in the designated database.
In an embodiment, the step of updating the target executable file in a separate server environment includes: replacing the executable file already deployed in the independent server with the target executable file; and deploying the target executable file to complete the updating.
In an embodiment, after the step of updating the target executable file in the independent server environment, the method includes: acquiring first feedback information which is returned by the independent server and does not adapt to the updated service rule version, wherein the inadaptation of the updated service rule version comprises that the target executable file cannot be updated in the independent server environment and the target executable file cannot run after the target executable file is updated in the independent server environment; re-reading the executable file from the designated database according to the first feedback information; replacing the target executable file with the executable file and deploying the executable file in the independent server environment; or, after the step of updating the target executable file in the common server environment, the method includes: acquiring second feedback information which is returned by the public server and does not adapt to the updated service rule version, wherein the inadaptation of the updated service rule version comprises that the target executable file cannot be updated in the public server environment and the target executable file cannot run after the target executable file is updated in the public server environment; re-reading the executable file from the designated database according to the second feedback information; replacing the target executable file with the executable file and deploying the executable file in the common server environment.
In an embodiment, after the step of obtaining the service type of the service rule according to the target executable file and recording as the first service type, the method includes: judging whether the updating mode for updating the business rule is according to the important coefficient; if the updating mode is updating according to the important coefficient, generating a calculation instruction for calculating the important coefficient; if the updating mode is not updating according to the important coefficient, judging whether the operation quantity of the service rule corresponding to the first service type exceeds a preset operation quantity or not; and if the service rule operation amount exceeds a preset operation amount, updating the target executable file in the independent server environment, and if the service rule operation amount does not exceed the preset operation amount, updating the target executable file in the public server environment.
Those skilled in the art will appreciate that the architecture shown in fig. 3 is only a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects may be applied.
An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a rule updating method of a rule engine system, and specifically includes: acquiring an updating instruction for updating a service rule in a rule engine system; reading a target executable file of the latest version from a specified database according to the updating instruction, wherein the target executable file is a file which is generated by a preset business rule set and can run in a server; acquiring a service type corresponding to the service rule according to the target executable file, and recording the service type as a first service type, wherein the same service type comprises a plurality of different services; calculating an important coefficient corresponding to the first service type according to the weight corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type; judging whether the important coefficient is larger than a preset threshold value or not; and if the target executable file is not updated in the public server environment, updating the target executable file in the independent server environment.
The computer-readable storage medium, wherein the step of calculating an importance coefficient corresponding to the first service type according to the weights corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type, includes: the importance coefficient is calculated using the following formula: r ═ W1+W2+…+Wn)/(π*W1/2arctan(C1)+π*W2/2arctan(C2)+…+π*Wn/2arctan(Cn) ); n services are preset in the first service type, R is the significant coefficient, W is the weight of each service in the first service type, and C is the usage amount of each service in the first service type.
In an embodiment, before the step of calculating the importance coefficient corresponding to the first service type according to the weights corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type, the method includes: calling a history record of each service used in the first service type each time; and counting the use times of each service according to the history record, and recording the use times as the use amount.
In an embodiment, before the step of obtaining the update instruction for updating the business rule in the rule engine system, the method includes: receiving rule parameters input by a user in a rule editing interface to form a target rule file; analyzing the target rule file into a target prl file; compiling the prl file into the target executable file; storing the target executable file into the designated database; defining the target executable file as the latest version in the designated database through a tag according to a history file, wherein the history file is an executable file which is stored in the designated database before the target executable file is stored in the designated database.
In an embodiment, the step of updating the target executable file in a separate server environment includes: replacing the executable file already deployed in the independent server with the target executable file; and deploying the target executable file to complete the updating.
In an embodiment, after the step of updating the target executable file in the independent server environment, the method includes: acquiring first feedback information which is returned by the independent server and does not adapt to the updated service rule version, wherein the inadaptation of the updated service rule version comprises that the target executable file cannot be updated in the independent server environment and the target executable file cannot run after the target executable file is updated in the independent server environment; re-reading the executable file from the designated database according to the first feedback information; replacing the target executable file with the executable file and deploying the executable file in the independent server environment; or, after the step of updating the target executable file in the common server environment, the method includes: acquiring second feedback information which is returned by the public server and does not adapt to the updated service rule version, wherein the inadaptation of the updated service rule version comprises that the target executable file cannot be updated in the public server environment and the target executable file cannot run after the target executable file is updated in the public server environment; re-reading the executable file from the designated database according to the second feedback information; replacing the target executable file with the executable file and deploying the executable file in the common server environment.
In an embodiment, after the step of obtaining the service type of the service rule according to the target executable file and recording as the first service type, the method includes: judging whether the updating mode for updating the business rule is according to the important coefficient; if the updating mode is updating according to the important coefficient, generating a calculation instruction for calculating the important coefficient; if the updating mode is not updating according to the important coefficient, judging whether the operation quantity of the service rule corresponding to the first service type exceeds a preset operation quantity or not; and if the service rule operation amount exceeds a preset operation amount, updating the target executable file in the independent server environment, and if the service rule operation amount does not exceed the preset operation amount, updating the target executable file in the public server environment.
It will be understood by those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by hardware associated with instructions of a computer program, which may be stored on a non-volatile computer-readable storage medium, and when executed, may include processes of the above embodiments of the methods. Any reference to memory, storage, database, or other medium provided herein and used in the examples may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double-rate SDRAM (SSRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and bus dynamic RAM (RDRAM).
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, apparatus, article, or method that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, apparatus, article, or method. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, apparatus, article, or method that includes the element.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (9)
1. A method for updating rules of a rules engine system, comprising:
acquiring an updating instruction for updating a service rule in a rule engine system;
reading a target executable file of the latest version from a specified database according to the updating instruction, wherein the target executable file is a file which is generated by a preset business rule set and can run in a server;
acquiring a service type corresponding to the service rule according to the target executable file, and recording the service type as a first service type, wherein the same service type comprises a plurality of different services;
calculating an important coefficient corresponding to the first service type according to the weight corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type;
judging whether the important coefficient is larger than a preset threshold value or not;
if yes, updating the target executable file in an independent server environment, and if not, updating the target executable file in a public server environment;
the step of calculating an importance coefficient corresponding to the first service type according to the weights corresponding to all services in the first service type and the usage amount corresponding to each service in the first service type includes:
the importance coefficient is calculated using the following formula:
R＝(W1+W2+…+Wn)/(π*W1/2arctan(C1)+π*W2/2arctan(C2)+…+π*Wn/2arctan(Cn))；
n services are preset in the first service type, R is the significant coefficient, W is the weight of each service in the first service type, and C is the usage amount of each service in the first service type.
2. The method of claim 1, wherein the step of calculating the importance factor corresponding to the first traffic type according to the weight corresponding to all the traffic in the first traffic type and the usage amount corresponding to each of the traffic in the first traffic type is preceded by:
calling a history record of each service used in the first service type each time;
and counting the use times of each service according to the history record, and recording the use times as the use amount.
3. The method according to claim 1, wherein the step of obtaining the update instruction for updating the business rule in the rule engine system comprises:
receiving rule parameters input by a user in a rule editing interface to form a target rule file;
analyzing the target rule file into a target prl file;
compiling the prl file into the target executable file;
storing the target executable file into the designated database;
defining the target executable file as the latest version in the designated database through a tag according to a history file, wherein the history file is an executable file which is stored in the designated database before the target executable file is stored in the designated database.
4. The rule updating method of the rule engine system of claim 3 wherein the step of updating the target executable in a separate server environment comprises:
replacing the executable file already deployed in the independent server with the target executable file;
and deploying the target executable file to complete the updating.
5. The rule updating method of the rule engine system of claim 3 wherein the step of updating the target executable file in a separate server environment is followed by the step of:
acquiring first feedback information which is returned by the independent server and does not adapt to the updated service rule version, wherein the inadaptation of the updated service rule version comprises that the target executable file cannot be updated in the independent server environment and the target executable file cannot run after the target executable file is updated in the independent server environment;
re-reading the executable file from the designated database according to the first feedback information;
replacing the target executable file with the executable file and deploying the executable file in the independent server environment;
or, after the step of updating the target executable file in the common server environment, the method includes:
acquiring second feedback information which is returned by the public server and does not adapt to the updated service rule version, wherein the inadaptation of the updated service rule version comprises that the target executable file cannot be updated in the public server environment and the target executable file cannot run after the target executable file is updated in the public server environment;
re-reading the executable file from the designated database according to the second feedback information;
replacing the target executable file with the executable file and deploying the executable file in the common server environment.
6. The method for updating rules of a rules engine system of claim 1, wherein the step of obtaining the service type of the service rule according to the target executable file and marking as the first service type comprises:
judging whether the updating mode for updating the business rule is according to the important coefficient;
if the updating mode is updating according to the important coefficient, generating a calculation instruction for calculating the important coefficient; if the updating mode is not updating according to the important coefficient, judging whether the operation quantity of the service rule corresponding to the first service type exceeds a preset operation quantity or not;
and if the service rule operation amount exceeds a preset operation amount, updating the target executable file in the independent server environment, and if the service rule operation amount does not exceed the preset operation amount, updating the target executable file in the public server environment.
7. A rule updating apparatus of a rule engine system, comprising:
the acquisition instruction unit is used for acquiring an update instruction for updating the business rules in the rule engine system;
a file reading unit, configured to read a target executable file of a latest version from a specified database according to the update instruction, where the target executable file is a file that is generated by a preset service rule set and is capable of running in a server;
the type obtaining unit is used for obtaining a service type corresponding to the service rule according to the target executable file and recording the service type as a first service type, wherein the same service type comprises a plurality of different services;
a calculating coefficient unit, configured to calculate an important coefficient corresponding to the first service type according to weights corresponding to all services in the first service type and usage amounts corresponding to the services in the first service type;
the judgment coefficient unit is used for judging whether the important coefficient is larger than a preset threshold value or not;
the file updating unit is used for updating the target executable file in an independent server environment when the importance coefficient is judged to be larger than a preset threshold value, and updating the target executable file in a public server environment if the importance coefficient is not judged to be larger than the preset threshold value;
the importance coefficient is calculated using the following formula:
R＝(W1+W2+…+Wn)/(π*W1/2arctan(C1)+π*W2/2arctan(C2)+…+π*Wn/2arctan(Cn))；
n services are preset in the first service type, R is the significant coefficient, W is the weight of each service in the first service type, and C is the usage amount of each service in the first service type.
8. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 6 when executing the computer program.
9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910101290.1A CN109918079B (en) | 2019-01-31 | 2019-01-31 | Rule updating method and device of rule engine system and computer equipment |
| PCT/CN2019/116334 WO2020155735A1 (en) | 2019-01-31 | 2019-11-07 | Rule update method and apparatus for rule engine system, and computer device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910101290.1A CN109918079B (en) | 2019-01-31 | 2019-01-31 | Rule updating method and device of rule engine system and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109918079A CN109918079A (en) | 2019-06-21 |
| CN109918079B true CN109918079B (en) | 2022-03-18 |
Family
ID=66961248
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910101290.1A Active CN109918079B (en) | 2019-01-31 | 2019-01-31 | Rule updating method and device of rule engine system and computer equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN109918079B (en) |
| WO (1) | WO2020155735A1 (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109918079B (en) * | 2019-01-31 | 2022-03-18 | 平安科技（深圳）有限公司 | Rule updating method and device of rule engine system and computer equipment |
| CN110413286B (en) * | 2019-07-31 | 2023-08-22 | 创新先进技术有限公司 | Application deployment method, device and equipment |
| CN110750242B (en) * | 2019-09-19 | 2023-05-02 | 北京字节跳动网络技术有限公司 | File deployment method, system, medium and electronic equipment |
| CN111221550B (en) * | 2019-10-24 | 2022-09-06 | 支付宝(杭州)信息技术有限公司 | Rule updating method and device for streaming computing and streaming computing system |
| CN110851159B (en) * | 2019-10-31 | 2023-01-10 | 浙江大搜车软件技术有限公司 | Business rule updating method and device, computer equipment and storage medium |
| CN113126991A (en) * | 2021-04-26 | 2021-07-16 | 中国邮政储蓄银行股份有限公司 | Service data processing method and device |
| CN113254061B (en) * | 2021-06-02 | 2021-11-09 | 深圳前海大道金融服务有限公司 | Business decision method, system and storage medium based on rule engine |
| CN113485869A (en) * | 2021-06-08 | 2021-10-08 | 上海众言网络科技有限公司 | Database upgrading method and device |
| CN116303475B (en) * | 2023-05-17 | 2023-08-08 | 吉奥时空信息技术股份有限公司 | Management method and device for intelligent storage of multi-source index data |
| CN117453278B (en) * | 2023-11-01 | 2024-05-14 | 国任财产保险股份有限公司 | Rule management system based on business rule |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101739248A (en) * | 2008-11-13 | 2010-06-16 | 国际商业机器公司 | Method and system for executing rule set |
| CN105426748A (en) * | 2014-09-18 | 2016-03-23 | 腾讯科技（深圳）有限公司 | Rule file updating method and device |
| US10162613B1 (en) * | 2017-07-18 | 2018-12-25 | Sap Portals Israel Ltd. | Re-usable rule parser for different runtime engines |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9414305B2 (en) * | 2013-02-04 | 2016-08-09 | Metropcs Wireless, Inc. | Intelligent network selection system |
| CN106126215B (en) * | 2016-06-17 | 2019-06-21 | 深圳市麦斯杰网络有限公司 | Business rule scenario generation method and device |
| CN107656755A (en) * | 2016-07-24 | 2018-02-02 | 平安科技（深圳）有限公司 | The edit methods and device of regulation engine |
| US10942948B2 (en) * | 2017-05-02 | 2021-03-09 | Sap Se | Cloud-based pluggable classification system |
| CN109284106A (en) * | 2018-07-18 | 2019-01-29 | 平安科技（深圳）有限公司 | Method for release management, electronic device and the readable storage medium storing program for executing of business rule |
| CN109918079B (en) * | 2019-01-31 | 2022-03-18 | 平安科技（深圳）有限公司 | Rule updating method and device of rule engine system and computer equipment |
-
2019
- 2019-01-31 CN CN201910101290.1A patent/CN109918079B/en active Active
- 2019-11-07 WO PCT/CN2019/116334 patent/WO2020155735A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101739248A (en) * | 2008-11-13 | 2010-06-16 | 国际商业机器公司 | Method and system for executing rule set |
| CN105426748A (en) * | 2014-09-18 | 2016-03-23 | 腾讯科技（深圳）有限公司 | Rule file updating method and device |
| US10162613B1 (en) * | 2017-07-18 | 2018-12-25 | Sap Portals Israel Ltd. | Re-usable rule parser for different runtime engines |
Non-Patent Citations (2)
| Title |
|---|
| Efficient Rule Engine for Smart Building Systems;Yan Sun等;《IEEE Transactions on Computers》;20140805;第1658 - 1669页 * |
| 朱会兵.基于Drools的信息管理与决策系统的研究与实现.《 中国优秀硕士论文电子期刊网( 中国优秀硕士论文电子期刊网 (信息科技辑)》.2012, * |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2020155735A1 (en) | 2020-08-06 |
| CN109918079A (en) | 2019-06-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109918079B (en) | Rule updating method and device of rule engine system and computer equipment | |
| CN108446116B (en) | Application program page generation method and device, computer equipment and storage medium | |
| CN110708210B (en) | Cloud test configuration method and device, computer equipment and storage medium | |
| AU2018310287A1 (en) | Smart contract processing method and apparatus | |
| CN111984228A (en) | Interface document processing method and device, computer equipment and storage medium | |
| CN115562690B (en) | Algorithm service processing method, device and medium based on Docker container | |
| CN112187713B (en) | Message conversion method, device, computer equipment and storage medium | |
| CN111399860B (en) | Light application deployment method, light application deployment device, computer equipment and storage medium | |
| US11422917B2 (en) | Deriving software application dependency trees for white-box testing | |
| CN113360300B (en) | Interface call link generation method, device, equipment and readable storage medium | |
| CN105468412A (en) | Dynamic packaging method and dynamic packaging device | |
| CN113934425A (en) | Page processing method and device, computer equipment and storage medium | |
| Brada et al. | Practical verification of component substitutability using subtype relation | |
| CN113721973A (en) | Configuration file generation method, device, equipment and medium | |
| CN115794214B (en) | Application module metadata management method, device, storage medium and apparatus | |
| US9378041B2 (en) | Method and system for integrating and implementing virtual service packages across different service virtualization tools | |
| CN111399864B (en) | Android system application program foundation package generation method and generation device | |
| US9936015B2 (en) | Method for building up a content management system | |
| CN113721906A (en) | Common module extraction method, device, equipment and medium for service merging | |
| CN106775629B (en) | Search file generation method and device | |
| CN117312694B (en) | Method, device and storage medium for constructing H5 application based on applet framework | |
| CN113467888B (en) | Cross-chain calling method and device of intelligent contract, electronic equipment and storage medium | |
| CN114911507B (en) | Updating method and equipment of algorithm package | |
| CN116700727B (en) | Cross-platform data processing method and system | |
| CN114610637A (en) | Test case generation method, device, equipment and medium suitable for front-end project |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |