WO2020155735A1

WO2020155735A1 - Rule update method and apparatus for rule engine system, and computer device

Info

Publication number: WO2020155735A1
Application number: PCT/CN2019/116334
Authority: WO
Inventors: 宋杰
Original assignee: 平安科技（深圳）有限公司
Priority date: 2019-01-31
Filing date: 2019-11-07
Publication date: 2020-08-06
Also published as: CN109918079A; CN109918079B

Abstract

Provided are a rule update method and apparatus for a rule engine system, and a computer device and a storage medium. The method comprises: acquiring an update instruction for updating a service rule in a rule engine system; reading, according to the update instruction and from a specified database, a target executable file of the latest version; acquiring, according to the target executable file, a first service type corresponding to the service rule; calculating an importance coefficient corresponding to the first service type according to weights corresponding to all the services in the first service type and a usage amount corresponding to each service in the first service type; determining whether the importance coefficient is greater than a preset threshold value; and if so, updating the target executable file in an independent server environment, and if not, updating the target executable file in a public server environment. The method is convenient and fast, and there is no need to manually deploy service rules relying on experience, and the cross influence of important service rules can be prevented while resources can be economized.

Description

Rule update method, device and computer equipment of rule engine system

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on January 31, 2019, the application number is 201910101290.1, and the application title is "Rule Update Method, Apparatus and Computer Equipment of the Rule Engine System", the entire content of which is by reference Incorporated in this application.

Technical field

This application relates to the technical field of data processing, in particular to a rule update method, device, computer equipment and storage medium of a rule engine system.

Background technique

The rule engine is a component that separates business decisions from application code and uses predefined semantic modules to write business decisions. It accepts data input, interprets business rules, and makes business decisions based on business rules. The rules engine can be applied In various businesses, but for different businesses, it will be more troublesome to update again after the business rule code is written.

When the existing rule engine system updates business rules, it first needs to export the rule set, then modify the rule set offline, and then zip the modified rule set into a compressed package, then upload it to the rule compilation platform, and manually trigger the compilation to generate the The executable package is downloaded and the executable package is finally deployed to achieve the update. Not only is the steps cumbersome, time-consuming and labor-intensive, but also cannot be updated in real time. For business market changes, the response to business rules adjustment is slow. For different businesses, it can only be artificially Deploying and updating the corresponding business rules to an adapted server environment based on experience is slow and error-prone.

Summary of the invention

The main purpose of this application is to provide a rule updating method, device, computer equipment, and storage medium of a rule engine system that improves efficiency, and aims to solve the problem of slow update efficiency of business rules in the existing rule engine system.

Based on the foregoing invention objectives, this application proposes a rule update method for a rule engine system, including:

Obtain update instructions for updating business rules in the rule engine system;

Reading the latest version of the target executable file from a designated database according to the update instruction, where the target executable file is a file that is generated by a preset business rule set and can be run on the server;

Obtain the business type corresponding to the business rule according to the target executable file, and record it as the first business type, where the same business type includes multiple different businesses;

Calculating an important coefficient corresponding to the first service type according to the weights corresponding to all the services in the first service type and the usage amount corresponding to each of the services in the first service type;

Judging whether the important coefficient is greater than a preset threshold;

If yes, update the target executable file in a standalone server environment, if not, update the target executable file in a public server environment.

This application also provides a rule update device of the rule engine system, including:

The obtaining instruction unit is used to obtain the update instruction for updating the business rules in the rule engine system;

The file reading unit is configured to read the latest version of the target executable file from the designated database according to the update instruction, where the target executable file is a file that is generated by a preset business rule set and can be run on the server;

The obtaining type unit is used to obtain the service type corresponding to the business rule according to the target executable file and record it as the first service type, wherein the same service type includes multiple different services;

The calculation coefficient unit is configured to calculate the important coefficient corresponding to the first service type according to the weights corresponding to all the services in the first service type and the usage amount corresponding to each of the services in the first service type;

The judgment coefficient unit is used to judge whether the important coefficient is greater than a preset threshold;

The update file unit is used to update the target executable file in a stand-alone server environment when it is determined that the important coefficient is greater than a preset threshold; if not, then update the target executable file in a public server environment Update.

The present application also provides a computer device including a memory and a processor, the memory stores computer readable instructions, and the processor implements the steps of the above method when the computer readable instructions are executed.

The present application also provides a computer-readable storage medium on which computer-readable instructions are stored, and when the computer-readable instructions are executed by a processor, the steps of the foregoing method are implemented.

The beneficial effects of this application are: directly read the executable file when updating the rules, and then deploy the executable file in the corresponding server environment according to the calculated important coefficients of the rule system, which is convenient and fast, without artificially relying on experience To deploy business rules and deploy them in a targeted manner, which saves resources while avoiding cross-influence of important business rules. In addition, business rules can be modified in real time to quickly respond to changes in the business market.

Description of the drawings

FIG. 1 is a schematic diagram of the steps of a rule update method of a rule engine system in an embodiment of this application;

2 is a schematic block diagram of the structure of a rule updating device of a rule engine system in an embodiment of the application;

FIG. 3 is a schematic block diagram of the structure of a computer device according to an embodiment of the application.

The realization, functional characteristics, and advantages of the purpose of this application will be further described in conjunction with the embodiments and with reference to the drawings.

detailed description

It should be understood that the specific embodiments described here are only used to explain the application, and not to limit the application.

1, the rule update method of the rule engine system in this embodiment includes:

Step S1: Obtain an update instruction for updating the business rules in the rule engine system;

Step S2: Read the latest version of the target executable file from the designated database according to the update instruction, where the target executable file is a file that is generated by a preset business rule set and can be run on the server;

Step S3: Obtain the business type corresponding to the business rule according to the target executable file, and record it as the first business type, where the same business type includes multiple different businesses;

Step S4: Calculate the important coefficient corresponding to the first service type according to the weights corresponding to all the services in the first service type and the usage amount corresponding to each of the services in the first service type;

Step S5: Determine whether the important coefficient is greater than a preset threshold;

Step S6: If yes, update the target executable file part in an independent server environment, if not, update the target executable file in a public server environment.

As described in step S1 above, when an update instruction to update the business rules of the rule engine system is obtained, the current business rules can be updated according to the update instructions. The business rules are rule data corresponding to a certain business type. These rule data include rule codes. The aforementioned update instruction can be generated based on an update request initiated by a user, or can be automatically triggered when the rule engine system restarts.

As described in step S2 above, the target executable file is a file that is generated by a preset business rule set and can be run on the server. For example, the file is a jar package that can be run and deployed, and the target executable file is generated by the system It is generated according to the rule parameters entered by the user and stored in a specified database, such as a MongoDB database.

As mentioned in step S3 above, the business rules of the rule engine system are applied to different businesses, and some businesses in different businesses can use the same business rules, so these different businesses can be classified to obtain multiple business types, and Each business type includes multiple different businesses, and each business type corresponds to a business rule. Since the target executable file is generated by the rule parameters entered by the user, and the rule parameters contain business information, the corresponding business type can be obtained from this information, so the corresponding business type of the business rule can be obtained according to the target executable file In this embodiment, for ease of presentation, the service type is recorded as the first service type.

As described in step S4 above, the important coefficient of the first service type can be calculated, and then the above-mentioned business rules can be updated according to the important coefficient. Since the importance of the service type is different, it will be deployed to different server environments when updating. The importance of a business type is determined by the various businesses it contains. For example, a business type includes financial transactions, ordinary transactions, core businesses, and non-core businesses. Among them, financial transactions are more important, and their weights are also relatively important. high. Therefore, the above-mentioned important coefficient can be calculated by the importance of all services in the first service type, that is, the preset weights corresponding to each service. At the same time, in order to ensure the smooth operation of the business rules after deployment, it is necessary to know the usage of the first service type in order to better allocate updates to the corresponding server environment. Therefore, the usage of each service in the first service type is required to calculate the above important coefficients. Before the update, there is no need to manually allocate deployment based on experience, and directly calculate the important coefficient corresponding to the first service type based on the weight of all services in the first service type and the corresponding usage of each service in the first service type. According to the important factor to allocate updates to the applicable server environment.

As described in the above steps S5-S6, the above-mentioned updating of the target executable file in the server environment can be achieved by deploying the target executable file in the server. Due to different business rules, the update will be deployed to different server environments. The server environments are divided into independent server environments and public server environments. The business rules deployed in the independent server environment can be run in the independent environment separately. For business rules deployed in a public server environment, multiple different business rules can be deployed, and multiple business rules run at the same time. This targeted deployment not only saves resources, but also avoids important business rules at runtime. Cross-influenced by unimportant business rules, so important business rules need to be deployed in a separate server environment, and unimportant business rules can be deployed in a public server environment, so after obtaining the business type corresponding to the business rule, you can base it on the business type The corresponding weights of all businesses in the business type and the corresponding usage of each business in the business type calculate the important coefficient corresponding to the business type. The higher the important coefficient, the more important the business type is. When the important coefficient is greater than the preset threshold, you can Deploy the business rules corresponding to the business type to an independent server environment, otherwise it can be directly deployed in a public server environment.

In one embodiment, the important coefficient is calculated using the following formula:

R=(W ₁ +W ₂ +…+W _n )/(π*W ₁ /2arctan(C ₁ )+π*W ₂ /2arctan(C ₂ )+…+π*W _n /2arctan(C _n ) );

Wherein, there are preset n services in the first service type, R is the important coefficient, W is the weight of each service in the first service type, and C is each service in the first service type Usage.

The above-mentioned important coefficients can be calculated by the weight of each service of the above-mentioned service type and the usage of each service. The above-mentioned weight can be preset by the user, and the usage can be obtained through the corresponding service system. In this embodiment, the aforementioned first service type is predicted There are four businesses, namely financial transaction, ordinary transaction, core business and non-core business. W1, W2, W3, W4 are the weights of financial transaction, ordinary transaction, core business and non-core business type in turn, where W1> W2>W3>W4, c1, c2, c3, and c4 are the usage of the above-mentioned financial transactions, ordinary transactions, core business, and non-core business in turn. The important coefficient of the first service type is calculated by the above formula. The important system is between 0 and 1. The higher the important coefficient, the more important the first service type. At this time, the important coefficient can be compared with the preset threshold. In an embodiment, the preset threshold may be 0.7. When the threshold is exceeded, the target executable file can be deployed in an independent server environment. If the threshold is not exceeded, the rule system is not important. It can be deployed in a public service environment.

In one embodiment, before step S4, the method includes:

Step S41: Invoke the historical record of each of the services used in the first service type;

Step S42: Count the usage times of each service according to the historical records, and record the usage times as the usage amount.

In this embodiment, since the usage amount of each service in the first service type is needed to calculate the above important coefficients, it is necessary to obtain the usage amount of each service before calculating. It is known that each service is being used. It will be recorded, for example, in the system log. Therefore, by calling the corresponding log and checking the record in the log, you can get the number of uses of this type of business. The number of uses is recorded as the amount of use mentioned above. Check the corresponding record to get the usage of each service in the first service type.

In an embodiment, before step S1, the method includes:

Step S01: receiving the rule parameters input by the user in the rule editing interface to form a target rule file;

Step S02: Parse the target rule file into a target prl file;

Step S03: Compile the prl file into the target executable file;

Step S04: Store the target executable file in the designated database;

Step S05: Define the target executable file as the latest version through a tag tag in the designated database according to a historical file, the historical file being stored before storing the target executable file in the designated database The executable file in the specified database.

As described in step S01 above, the rule editing interface is displayed through a browser. After receiving the rule parameters input by the user (such as a business person), the rule parameters are added to the set of business rules preset by the developer to form For the target rule file corresponding to the above rule parameters, the user fills in different rule parameters to form different target rule files, where the target rule file exists in the form of html. In this embodiment, after the user finishes inputting the rule parameters on the rule editing interface, he can input the formation instruction, and the system can form the target rule file according to the formation instruction to the business rule set added to the rule parameters.

As described in the above step S02, the above prl file is the code program corresponding to the rule, and running the code program can realize the business strategy corresponding to the business rule. In this embodiment, parsing the target rule file into the target prl file can be specifically as follows Steps: According to the parameters input by the user, the target rule file is logically divided into three parts: when, then, and else, and then these three parts are packaged and merged 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 marked into a jar package that can be run and deployed, the jar package is the target executable file, and then the target can be The execution file is stored in the specified database.

As mentioned in step S05 above, in the above-mentioned designated database, the latest version of the target executable file is defined through the tag tag of the above-mentioned target executable file, and this version is defined on the basis of the old version corresponding to the historical file. The history file is an executable file that exists before the target executable file is stored in the specified database. For example, when an executable file is stored in MongoDB for the first time, it is defined as the first generation version, and the user updates it again afterwards. The executable file stored in the MongoDB is defined as the second-generation version, and so on, each update defines its corresponding version on the basis of the previous version, and the target executable file mentioned above is in the specified database The latest version in.

Through the above method, when the rule needs to be updated, the user can directly generate the latest version of the current rule by filling in the parameters in the rule editing interface. The user can modify the rule in real time, the update speed is accelerated, and the efficiency is greatly improved. There is no need to go offline for each update. Modify and upload it to reduce the rule update steps and avoid the impact of human error.

In one embodiment, in the above step S6, the step of deploying and then updating the target executable file in a stand-alone server environment includes:

Step S601: Replace the executable file that has been deployed in the independent server with the target executable file of the latest version;

Step S602: Deploy the target executable file to complete the update.

In this embodiment, after the target executable file is distributed 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 old version of the executable file is overwritten, and the target executable file is Executable files are deployed to implement rule updates, such as replacing the first-generation rules in the server with second-generation rules according to user requests. Similarly, when updating in a public server environment, you can update the old version of the public server The executable file is replaced with the latest version of the target executable file, and the target executable file is deployed to complete the update.

In an embodiment, after the above step S6, the method includes:

Step S61: Obtain the first feedback information returned by the independent server indicating that the updated business rule version is not compatible, including that the target executable file cannot be updated in the independent server environment, and The target executable file cannot run after the update is completed in the independent server environment;

Step S62: Re-read the executable file from the designated database according to the first feedback information;

Step S63: Replace the target executable file with the executable file, and deploy the executable file;

Alternatively, after the step of updating the target executable file in a public server environment, the method includes:

Step S61': Obtain the second feedback information returned by the public server that the updated business rule version is not suitable, and the updated business rule version is not suitable, including that the target executable file cannot be updated in the public server environment, And the target executable file cannot run after the update is completed in the public server environment;

Step S62': re-read the executable file from the designated database according to the second feedback information;

Step S63': Replace the target executable file with the executable file, and deploy the executable file in the public server environment.

In this embodiment, since the target executable file is an updated version, the server may not necessarily adapt to and be able to run the target executable file, so after replacing the old version executable file with the latest version of the target executable file , When the server is not suitable for updating the version, that is, the update corresponding business rules are not suitable, then feedback information is returned. The above-mentioned updating business rules are not suitable for two situations, one is that the target executable file is in the public server environment The update cannot be completed in the middle, one is the case where the target executable file cannot run after the update is completed in the public server environment, and the above feedback information is information corresponding to these two cases. After obtaining the feedback information, the executable file of the old version of the board will be re-read from the specified database, and the updated new version in the server will be replaced with the original old version of the executable file to avoid the situation that the update is not suitable for running, as mentioned above The server can be an independent server or a public server.

In another embodiment, after the above step S3, the method includes:

Step S7: Determine whether the update method for updating the business rule is based on the important coefficient;

Step S8: If the update method is to update based on the important coefficient, generate a calculation instruction for calculating the important coefficient; if the update method is not to update based on the important coefficient, then determine whether the business rule operation volume corresponding to the first business type is Exceed the preset operating volume;

Step S9: If the running volume of the business rule exceeds the preset running volume, update the target executable file in the independent server environment, and if the running volume of the business rule does not exceed the preset running volume, then The target executable file is updated in the public server environment.

It is understandable that in addition to determining the deployment environment of business rules through important factors, the deployment environment of business rules can also be determined directly based on the running volume. Therefore, after obtaining the first business type, first determine the update method of the business rule and the update method There are two types: update based on important coefficients and update based on operating volume. When the update method is based on important coefficients, directly generate calculation instructions for calculating important coefficients, calculate the important coefficients according to the calculation instructions, and then execute step S5- S6. When the update method is not updated based on the important coefficient, it can be judged based on the running volume. Because of the different business types and different users, the running volume of the corresponding business rules is also different. At this time, the running server can also be different. , The small running volume is sent to the public server to run. Because the running volume is small, the public server can run multiple executable files at the same time, while the large running volume needs to be sent to a separate server, which is run by a server alone. Ensure that the program runs normally. Therefore, in steps S8-S9, first determine whether the running volume of the target executable file exceeds the preset running volume. The preset running volume can be set with reference to the running volume of the server. When the preset running volume is exceeded, the target executable can be set The file is distributed to a separate server, the old version of the executable file is replaced with the latest version of the target executable file, and the deployment is performed to complete the update. If the preset running volume is not exceeded, the target executable file is distributed to the public server , Replace the old version of the executable file with the latest version of the target executable file, and forget to deploy the target executable to complete the update.

Referring to Fig. 2, the rule updating device of the rule engine system in this embodiment includes:

The obtaining instruction unit 100 is configured to obtain an update instruction for updating business rules in the rule engine system;

The file reading unit 200 is configured to read a target executable file of the latest version from a designated database according to the update instruction, the target executable file being a file generated by a preset business rule set and that can be run on a server;

The obtaining type unit 300 is configured to obtain the service type corresponding to the business rule according to the target executable file, and record it as the first service type, wherein the same service type includes multiple different services;

The calculation coefficient unit 400 is configured to calculate an important coefficient corresponding to the first service type according to the weights corresponding to all the services in the first service type and the usage amount corresponding to each of the services in the first service type;

The judging coefficient unit 500 is used to judge whether the important coefficient is greater than a preset threshold;

The update file unit 600 is used to update the target executable file in an independent server environment when it is determined that the important coefficient is greater than a preset threshold; if not, update the target executable file in a public server environment To be updated.

As described in the above-mentioned acquisition instruction unit 100, when an update instruction for updating the business rules of the rule engine system is acquired, the current business rules can be updated according to the update instructions, and the foregoing business rules are rules corresponding to a certain business type. Data, these rule data include rule codes. The aforementioned update instruction can be generated based on an update request initiated by a user, or can be automatically triggered when the rule engine system restarts.

As described in the above-mentioned file reading unit 200, the above-mentioned target executable file is a file that is generated by a preset set of business rules and can be run on the server. If the above-mentioned file is a jar package that can be run and deployed, the target executable file is The file is generated by the system according to the rule parameters entered by the user, and stored in a specified database, such as a MongoDB database.

As described in the above-mentioned acquisition type unit 300, the business rules of the above-mentioned rule engine system are applied to different businesses, and some of the different businesses can use the same business rules, so these different businesses can be classified to obtain multiple business types , And each business type includes multiple different businesses, and each business type corresponds to a business rule. Since the target executable file is generated by the rule parameters entered by the user, and the rule parameters contain business information, the corresponding business type can be obtained from this information, so the corresponding business type of the business rule can be obtained according to the target executable file In this embodiment, for ease of presentation, the service type is recorded as the first service type.

As described in the above-mentioned obtaining type unit 300, the important coefficient of the first service type can be calculated, and then the above-mentioned business rules can be updated according to the important coefficient. As the importance of the service type is different, it will be deployed to different In the server environment, the importance of a business type is determined by the various businesses it contains. For example, a business type contains four businesses: financial transactions, ordinary transactions, core businesses, and non-core businesses. Among them, financial transactions are more important. Also relatively high. Therefore, the above-mentioned important coefficient can be calculated by the importance of all services in the first service type, that is, the preset weights corresponding to each service. At the same time, in order to ensure the smooth operation of the business rules after deployment, it is necessary to know the usage of the first service type so as to better allocate and update to the corresponding server environment. Therefore, the usage of each service in the first service type is required to calculate the above important coefficients. In summary, before the update, there is no need to allocate deployment based on human experience, and directly calculate the important coefficient corresponding to the first service type based on the weight of all services in the first service type and the corresponding usage of each service in the first service type. Then according to the important factor to allocate updates to the applicable server environment.

As described in the aforementioned determination coefficient unit 500 and the update file unit 600, the aforementioned update of the target executable file in the server environment can be implemented by deploying the target executable file in the server. Due to different business rules, the update will be deployed to different server environments. The server environments are divided into independent server environments and public server environments. The business rules deployed in the independent server environment can be separately deployed in the independent environment For business rules deployed in a public server environment, multiple different business rules can be deployed, and multiple business rules run at the same time. This targeted deployment not only saves resources but also avoids runtime, important Business rules are cross-influenced by unimportant business rules, so important business rules need to be deployed in an independent server environment, unimportant business rules can be deployed in a public server environment, so after obtaining the business type corresponding to the business rule, you can follow The corresponding weights of all services in the business type and the corresponding usage of each business in the business type calculate the important coefficient corresponding to the business type. The higher the important coefficient, the more important the business type. When the important coefficient is greater than the preset threshold, Then the business rules corresponding to the business type can be deployed to the independent server environment, otherwise it can be directly deployed in the public server environment.

In an embodiment, the rule update device of the above-mentioned step rule engine system includes:

A call recording unit, which is used to call a historical record of each of the services used in the first service type;

The statistical usage unit is used to count the usage times of each type of service according to the historical records, and record the usage times as the usage amount.

In an embodiment, the rule updating device of the aforementioned step rule engine system further includes:

The parameter receiving unit is used to receive the rule parameters input by the user in the rule editing interface to form a target rule file;

A parsing file unit for parsing the target rule file into a target prl file;

A compiling file unit for compiling the prl file into the target executable file;

The file storage unit is used to store the target executable file in the designated database;

The definition version unit is used to define the target executable file as the latest version through a tag tag in the specified database according to a history file, where the history file is before storing the target executable file in the specified database , The executable file that has been stored in the specified database.

In an embodiment, the aforementioned update file unit 600 includes:

The file replacement unit is used to replace the executable file deployed in the independent server with the target executable file of the latest version;

The deployment file unit is used to deploy the target executable file to complete the update.

In an embodiment, the rule updating device of the above-mentioned rule engine system includes:

The first acquiring unit is configured to acquire the first feedback information returned by the independent server that the updated business rule version is not compatible, and the updated business rule version is not compatible, including that the target executable file cannot be updated in the independent server environment , And the target executable file cannot run after the update is completed in the independent server environment;

The first reread unit is configured to reread the executable file from the designated database according to the first feedback information;

The first replacement unit is configured to replace the target executable file with the executable file, and deploy the executable file;

The rule update device of the above rule engine system also includes:

The second obtaining unit is configured to obtain the second feedback information returned by the public server that the updated business rule version is not suitable, and the updated business rule version is not suitable for including the target executable file cannot be found in the public server environment. The update is completed, and the target executable file cannot run after the update is completed in the public server environment;

A second reread unit, configured to reread the executable file from the designated database according to the second feedback information;

The second deployment unit is configured to replace the target executable file with the executable file, and deploy the executable file in the public server environment.

In another embodiment, the rule updating device of the above-mentioned rule engine system includes:

A judging mode unit for judging whether the update mode for updating the business rule is based on the important coefficient;

The judging operation unit is configured to generate a calculation instruction for calculating important coefficients when the update mode is to update based on the important coefficient; if the update mode is not to update based on the important coefficient, determine the business corresponding to the first service type Whether the running volume of the rule exceeds the preset running volume;

An operation update unit, configured to update the target executable file in the independent server environment if the operation volume of the business rule exceeds the preset operation volume, and if the operation volume of the business rule does not exceed the preset operation volume , The target executable file is updated in the public server environment.

Referring to FIG. 3, an embodiment of the present application also provides a computer device. The computer device may be a server, and its internal structure may be as shown in FIG. 3. The computer equipment includes a processor, a memory, a network interface and a database connected by a system bus. Among them, the computer designed processor is used to provide calculation and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer readable instructions, and a database. The memory provides an environment for the operation of the operating system and computer readable instructions in the non-volatile storage medium. The database of the computer equipment is used to store all the data required to update the rules in the rule engine system. The network interface of the computer device is used to communicate with an external terminal through a network connection. The computer readable instruction is executed by the processor to realize a rule update method of the rule engine system.

The processor executes the steps of the rule update method of the rule engine system: obtains an update instruction for updating the business rules in the rule engine system; reads the latest version of the target executable file from the designated database according to the update instruction, so The target executable file is a file that is generated by a preset business rule set and can be run on the server; the business type corresponding to the business rule is obtained according to the target executable file, and is recorded as the first business type, where the same A service type includes multiple different services; according to the weights corresponding to all services in the first service type, and the corresponding usage of each service in the first service type, the corresponding first service is calculated The important coefficient of the type; determine whether the important coefficient is greater than the preset threshold; if yes, update the target executable file in a stand-alone server environment; if not, update the target executable file in a public server environment To be updated.

In the above-mentioned computer equipment, the step of calculating the important coefficient corresponding to the first service type according to the weights corresponding to all the services in the first service type and the usage amount corresponding to each of the services in the first service type, Including: use the following formula to calculate the important coefficient: R=(W ₁ +W ₂ +…+W _n )/(π*W ₁ /2arctan(C ₁ )+π*W ₂ /2arctan(C ₂ )+ …+π*W _n /2arctan(C _n )); wherein, there are preset n services in the first service type, R is the important coefficient, and W is the value of each service in the first service type Weight, C is the usage amount of each service in the first service type.

In an embodiment, the above-mentioned calculation of the important coefficient corresponding to the first service type is based on the weights corresponding to all the services in the first service type and the usage amount corresponding to each of the services in the first service type. Before the step, it includes: invoking the historical record of each of the services used in the first service type; counting the number of uses of each service according to the historical record, and recording the number of uses as the amount of use .

In one embodiment, before the step of obtaining the update instruction for updating the business rules in the rule engine system, the step includes: receiving the rule parameters input by the user in the rule editing interface to form a target rule file; The rule file is parsed into a target prl file; the prl file is compiled into the target executable file; the target executable file is stored in the designated database; the target is stored in the designated database according to the historical file The executable file is defined as the latest version through a tag, and the history file is an executable file that has been stored in the specified database before the target executable file is stored in the specified database.

In one embodiment, the above step of updating the target executable file in an independent server environment includes: replacing the executable file already deployed in the independent server with the target executable file; The target executable file is deployed to complete the update.

In one embodiment, after the above step of updating the target executable file in an independent server environment, it includes: obtaining the first feedback information returned by the independent server that the updated business rule version is not suitable, and the update service The rule version incompatibility includes that the target executable file cannot be updated in the independent server environment, and the target executable file cannot run after the update is completed in the independent server environment; according to the first feedback information from Re-read the executable file in the designated database; replace the target executable file with the executable file, and deploy the executable file in the independent server environment; or After the step of updating the target executable file in the public server environment, it includes: acquiring the second feedback information returned by the public server that the updated business rule version is not suitable, and the updated business rule version is not suitable for including the target The executable file cannot be updated in the public server environment, and the target executable file cannot be run after the update is completed in the public server environment; re-read all files from the designated database according to the second feedback information The executable file; replace the target executable file with the executable file, and deploy the executable file in the public server environment.

In one embodiment, after the step of obtaining the business type of the business rule based on the target executable file and recording it as the first business type, it includes: judging whether the update method of the business rule is based on The important coefficient is updated; if the update method is based on the important coefficient, a calculation instruction for calculating the important coefficient is generated; if the update method is not based on the important coefficient, the business rule corresponding to the first business type is determined Whether the running volume exceeds the preset running volume; if the running volume of the business rules exceeds the preset running volume, the target executable file is updated in the independent server environment, and if the running volume of the business rules does not exceed the preset running volume, Assuming the running volume, the target executable file is updated in the public server environment.

Those skilled in the art can understand that the structure shown in FIG. 3 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied.

An embodiment of the present application further provides a computer-readable storage medium. The computer-readable storage medium is, for example, a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. There are computer-readable instructions stored thereon, and when the computer-readable instructions are executed by the processor, a rule update method of the rule engine system is realized, specifically: obtaining an update instruction for updating business rules in the rule engine system; The update instruction reads the latest version of the target executable file from the specified database. The target executable file is a file that is generated by a preset business rule set and can be run on the server; and the corresponding target executable file is obtained according to the target executable file. The business type of the business rule is recorded as the first business type, where the same business type includes multiple different businesses; based on the weights corresponding to all businesses in the first business type, and the first business type Calculate the important coefficient corresponding to the first service type according to the usage amount corresponding to each of the services; determine whether the important coefficient is greater than a preset threshold; if so, perform the target executable file in an independent server environment Update, if not, update the target executable file in the public server environment.

The above-mentioned computer-readable storage medium, the above-mentioned calculation of an important coefficient corresponding to the first service type based on the weights corresponding to all the services in the first service type and the usage amount corresponding to each of the services in the first service type The steps include: using the following formula to calculate the important coefficient: R=(W ₁ +W ₂ +…+W _n )/(π*W ₁ /2arctan(C ₁ )+π*W ₂ /2arctan(C ₂ )+...+π*W _n /2arctan(C _n )); wherein, there are preset n services in the first service type, R is the important coefficient, and W is the value in the first service type The weight of each service, C is the usage amount of each service in the first service type.

The above are only the preferred embodiments of this application, and do not limit the scope of this application. Any equivalent structure or equivalent process transformation made using the content of the description and drawings of this application, or directly or indirectly applied to other related The technical field is equally included in the scope of patent protection of this application.

Claims

A rule update method of a rule engine system is characterized in that it includes:

Obtain update instructions for updating business rules in the rule engine system;

Reading the latest version of the target executable file from a designated database according to the update instruction, where the target executable file is a file that is generated by a preset business rule set and can be run on the server;

Obtain the business type corresponding to the business rule according to the target executable file, and record it as the first business type, where the same business type includes multiple different businesses;

Calculating an important coefficient corresponding to the first service type according to the weights corresponding to all the services in the first service type and the usage amount corresponding to each of the services in the first service type;

Judging whether the important coefficient is greater than a preset threshold;

If yes, update the target executable file in a standalone server environment, if not, update the target executable file in a public server environment.
The rule update method of the rule engine system according to claim 1, wherein the weights corresponding to all services in the first service type and the corresponding usage of each of the services in the first service type are used. The step of calculating the important coefficient corresponding to the first service type by quantity includes:

Use the following formula to calculate the important factor:

R=(W 1 +W 2 +…+W n )/(π*W 1 /2arctan(C 1 )+π*W 2 /2arctan(C 2 )+…+π*W n /2arctan(C n ) );

Wherein, there are preset n services in the first service type, R is the important coefficient, W is the weight of each service in the first service type, and C is each service in the first service type Usage.
The rule update method of the rule engine system according to claim 1, wherein the weights corresponding to all services in the first service type and the corresponding usage of each of the services in the first service type are used. Before the step of calculating the important coefficient corresponding to the first service type, the step includes:

Invoking the historical record of each of the services used in the first service type;

Count the usage times of each service according to the historical records, and record the usage times as the usage amount.
The rule update method of the rule engine system according to claim 1, characterized in that, before the step of obtaining an update instruction for updating business rules in the rule engine system, the method comprises:

Receive rule parameters entered by the user in the rule editing interface to form a target rule file;

Parse the target rule file into a target prl file;

Compiling the prl file into the target executable file;

Storing the target executable file in the designated database;

In the designated database, the target executable file is defined as the latest version through the tag tag according to the historical file, and the historical file is stored in the target executable file before the target executable file is stored in the designated database. Specify the executable file in the database.
The rule update method of the rule engine system according to claim 4, wherein the step of updating the target executable file in an independent server environment comprises:

Replacing the executable file that has been deployed in the independent server with the target executable file;

The target executable file is deployed to complete the update.
The rule updating method of the rule engine system according to claim 4, characterized in that, after the step of updating the target executable file in an independent server environment, it comprises:

Obtain the first feedback information returned by the independent server that the updated business rule version is not suitable, and the updated business rule version is not suitable, including that the target executable file cannot be updated in the independent server environment, and the target can be updated The executable file cannot run after the update is completed in the independent server environment;

Re-read 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;

Alternatively, after the step of updating the target executable file in a public server environment, the method includes:

Obtain the second feedback information returned by the public server that the updated business rule version is not suitable, and the updated business rule version is not suitable including that the target executable file cannot be updated in the public server environment, and the target can The executable file cannot run after the update is completed in the public server environment;

Re-read the executable file from the designated database according to the second feedback information;

Replace the target executable file with the executable file, and deploy the executable file in the public server environment.
The rule update method of the rule engine system according to claim 1, wherein after the step of obtaining the business type of the business rule according to the target executable file and recording it as the first business type, it comprises:

Judging whether the update method for updating the business rules is based on the important coefficient;

If the update method is to update based on the important coefficient, a calculation instruction for calculating the important coefficient is generated; if the update method is not to update based on the important coefficient, it is determined whether the operation volume of the business rule corresponding to the first business type exceeds the preset Running volume

If the running volume of the business rules exceeds the preset running volume, the target executable file is updated in the independent server environment. If the running volume of the business rules does not exceed the preset running volume, the target executable file is updated The executable file is updated in the public server environment.
A rule updating device of a rule engine system is characterized in that it comprises:

The obtaining instruction unit is used to obtain an update instruction for updating the business rules in the rule engine system;

The file reading unit is configured to read the latest version of the target executable file from the designated database according to the update instruction, where the target executable file is a file that is generated by a preset business rule set and can be run on the server;

The obtaining type unit is used to obtain the service type corresponding to the business rule according to the target executable file and record it as the first service type, wherein the same service type includes multiple different services;

The calculation coefficient unit is configured to calculate the important coefficient corresponding to the first service type according to the weights corresponding to all the services in the first service type and the usage amount corresponding to each of the services in the first service type;

The judgment coefficient unit is used to judge whether the important coefficient is greater than a preset threshold;

The update file unit is used to update the target executable file in a stand-alone server environment when it is determined that the important coefficient is greater than a preset threshold; if not, then update the target executable file in a public server environment Update.
The rule updating device of the rule engine system according to claim 8, characterized in that it further comprises:

A call recording unit, which is used to call a historical record of each of the services used in the first service type;

The statistical usage unit is used to count the usage times of each type of service according to the historical records, and record the usage times as the usage amount.
The rule updating device of the rule engine system according to claim 8, characterized in that it further comprises:

The parameter receiving unit is used to receive the rule parameters input by the user in the rule editing interface to form a target rule file;

A parsing file unit for parsing the target rule file into a target prl file;

A compiling file unit for compiling the prl file into the target executable file;

The file storage unit is used to store the target executable file in the designated database;

The definition version unit is used to define the target executable file as the latest version through a tag tag in the specified database according to a history file, where the history file is before storing the target executable file in the specified database , The executable file that has been stored in the specified database.
The rule updating device of the rule engine system according to claim 10, wherein the updating file unit comprises:

The file replacement unit is used to replace the executable file deployed in the independent server with the target executable file of the latest version;

The deployment file unit is used to deploy the target executable file to complete the update.
The rule updating device of the rule engine system according to claim 10, further comprising:

The first acquiring unit is configured to acquire the first feedback information returned by the independent server that the updated business rule version is not compatible, and the updated business rule version is not compatible, including that the target executable file cannot be updated in the independent server environment , And the target executable file cannot run after the update is completed in the independent server environment;

The first reread unit is configured to reread the executable file from the designated database according to the first feedback information;

The first replacement unit is configured to replace the target executable file with the executable file, and deploy the executable file;

The rule update device of the above rule engine system also includes:

The second obtaining unit is configured to obtain the second feedback information returned by the public server that the updated business rule version is not suitable, and the updated business rule version is not suitable for including the target executable file cannot be found in the public server environment. The update is completed, and the target executable file cannot run after the update is completed in the public server environment;

A second reread unit, configured to reread the executable file from the designated database according to the second feedback information;

The second deployment unit is configured to replace the target executable file with the executable file, and deploy the executable file in the public server environment.
The rule updating device of the rule engine system according to claim 8, characterized in that it further comprises:

A judging mode unit for judging whether the update mode for updating the business rule is based on the important coefficient;

The judging operation unit is configured to generate a calculation instruction for calculating important coefficients when the update mode is to update based on the important coefficient; if the update mode is not to update based on the important coefficient, determine the business corresponding to the first service type Whether the running volume of the rule exceeds the preset running volume;

An operation update unit, configured to update the target executable file in the independent server environment if the operation volume of the business rule exceeds the preset operation volume, and if the operation volume of the business rule does not exceed the preset operation volume , The target executable file is updated in the public server environment.
A computer device includes a memory and a processor, the memory stores computer readable instructions, and is characterized in that when the processor executes the computer readable instructions, a rule update method of a rule engine system is implemented, and the rule engine system The rule update methods include:

Obtain update instructions for updating business rules in the rule engine system;

Reading the latest version of the target executable file from a designated database according to the update instruction, where the target executable file is a file that is generated by a preset business rule set and can be run on the server;

Obtain the business type corresponding to the business rule according to the target executable file, and record it as the first business type, where the same business type includes multiple different businesses;

Calculating an important coefficient corresponding to the first service type according to the weights corresponding to all the services in the first service type and the usage amount corresponding to each of the services in the first service type;

Judging whether the important coefficient is greater than a preset threshold;

If yes, update the target executable file in a standalone server environment, if not, update the target executable file in a public server environment.
The computer device according to claim 14, wherein the corresponding weight is calculated based on the weights corresponding to all the services in the first service type and the usage amount corresponding to each of the services in the first service type. The steps to describe the important coefficients of the first business type include:

Use the following formula to calculate the important factor:

R=(W 1 +W 2 +…+W n )/(π*W 1 /2arctan(C 1 )+π*W 2 /2arctan(C 2 )+…+π*W n /2arctan(C n ) );

Wherein, there are preset n services in the first service type, R is the important coefficient, W is the weight of each service in the first service type, and C is each service in the first service type Usage.
The computer device according to claim 14, wherein the corresponding weight is calculated based on the weights corresponding to all the services in the first service type and the usage amount corresponding to each of the services in the first service type. Before describing the important factors of the first business type, the steps include:

Invoking the historical record of each of the services used in the first service type;

Count the usage times of each service according to the historical records, and record the usage times as the usage amount.
The computer device according to claim 14, characterized in that, before the step of obtaining the update instruction for updating the business rules in the rule engine system, it comprises:

Receive rule parameters entered by the user in the rule editing interface to form a target rule file;

Parse the target rule file into a target prl file;

Compiling the prl file into the target executable file;

Storing the target executable file in the designated database;

In the designated database, the target executable file is defined as the latest version through the tag tag according to the historical file, and the historical file is stored in the target executable file before the target executable file is stored in the designated database. Specify the executable file in the database.
A computer-readable storage medium having computer-readable instructions stored thereon, wherein the computer-readable instructions are executed by a processor to implement a rule update method of a rule engine system, and the rule update method of the rule engine system includes :

Obtain update instructions for updating business rules in the rule engine system;

Reading the latest version of the target executable file from a designated database according to the update instruction, where the target executable file is a file that is generated by a preset business rule set and can be run on the server;

Obtain the business type corresponding to the business rule according to the target executable file, and record it as the first business type, where the same business type includes multiple different businesses;

Calculating an important coefficient corresponding to the first service type according to the weights corresponding to all the services in the first service type and the usage amount corresponding to each of the services in the first service type;

Judging whether the important coefficient is greater than a preset threshold;

If yes, update the target executable file in a standalone server environment, if not, update the target executable file in a public server environment.
The computer-readable storage medium according to claim 18, wherein the calculation is performed based on the weights corresponding to all services in the first service type and the usage amount corresponding to each of the services in the first service type The step of calculating the important coefficient corresponding to the first service type includes:

Use the following formula to calculate the important factor:

R=(W 1 +W 2 +…+W n )/(π*W 1 /2arctan(C 1 )+π*W 2 /2arctan(C 2 )+…+π*W n /2arctan(C n ) );

Wherein, there are preset n services in the first service type, R is the important coefficient, W is the weight of each service in the first service type, and C is each service in the first service type Usage.
The computer-readable storage medium according to claim 18, wherein the calculation is performed based on the weights corresponding to all services in the first service type and the usage amount corresponding to each of the services in the first service type Before the step of deriving the important coefficient corresponding to the first service type, it includes:

Invoking the historical record of each of the services used in the first service type;

Count the usage times of each service according to the historical records, and record the usage times as the usage amount.