Rule publishing method and device

Abstract

The embodiment of the invention provides a rule release method and device, and relates to the technical field of data management, and the method comprises the steps that a release system sends a downloading instruction carrying version identification information of a target rule packet to a file processing system in response to a release operation triggered for the target rule packet on an operation interface, the file processing system downloads the target rule packet from the test operation and maintenance workbench based on the version identification information, obtains the target rule packet from the file processing system, calls an interface of the production operation and maintenance workbench, and issues the target rule packet to the production operation and maintenance workbench; and the production operation and maintenance workbench distributes the target rule packet to a rule execution server. By constructing a full-process closed-loop management mechanism, one-button safe release is realized, interaction with each system can be realized, each system can be automatically driven to execute tasks according to a predetermined process, manual operation can be replaced, the efficiency of releasing the rule packet is remarkably improved, and the operation risk is reduced.

Description

Technical Field

[0001] This application relates to the field of data management technology, and in particular to a rule publishing method and apparatus. Background Technology

[0002] Drools is a powerful business rule management system, typically maintained by business personnel, and consists of two parts: Workbench and kieServer. Workbench is a visual workbench for Drools rules, integrating functions such as management, writing, compiling, packaging, and publishing Drools rules; kieServer is the core component that hosts the actual execution of the rules.

[0003] Under the relevant technology, business personnel complete a series of processes such as writing, compiling, packaging, publishing, and verifying in the test environment's Workbench system to obtain the drools rule package; then, they download the drools rule package from the test environment's Workbench system to their local disk; next, the business personnel log in to the production environment's Workbench system and upload the drools rule package from their local disk to the production environment's Workbench database; finally, they deploy the drools rule package to the corresponding kieServer server.

[0004] In the above solution, business personnel need to manually download, upload, and configure rule packages multiple times between the test environment, production environment, and release system, which is complex and has a low fault tolerance rate. Summary of the Invention

[0005] This application provides a rule publishing method and apparatus to automate the entire process of rule package publishing, reduce operational complexity, and improve fault tolerance.

[0006] On the one hand, embodiments of this application provide a rule publishing method, applied to a publishing system, the method comprising: In response to a release operation triggered on the operation interface for a target rule package, a download instruction carrying version identification information of the target rule package is sent to the file processing system, so that the file processing system downloads the target rule package from the test and maintenance workbench based on the version identification information; Obtain the target rule package from the file processing system; The target rule package is published to the production operations and maintenance workbench by calling its interface, so that the production operations and maintenance workbench can distribute the target rule package to the rule execution server.

[0007] On the one hand, embodiments of this application provide a rule publishing method applied to a file processing system, the method comprising: The system receives a download instruction from the publishing system that carries version identification information of the target rule package. The download instruction is sent by the publishing system in response to a publishing operation triggered on the operation interface for the target rule package. Download the target rule package from the test and maintenance workbench based on the version identification information; The target rule package is sent to the publishing system, so that the publishing system calls the interface of the production operation and maintenance workbench to publish the target rule package to the production operation and maintenance workbench, so that the production operation and maintenance workbench distributes the target rule package to the rule execution server.

[0008] On one hand, embodiments of this application provide a rule publishing device for use in a publishing system, the device comprising: The instruction sending module is used to send a download instruction carrying the version identification information of the target rule package to the file processing system in response to a release operation triggered on the operation interface for the target rule package, so that the file processing system downloads the target rule package from the test and maintenance workbench based on the version identification information; The acquisition module is used to acquire the target rule package from the file processing system; The distribution module is used to call the interface of the production operation and maintenance workbench to publish the target rule package to the production operation and maintenance workbench, so that the production operation and maintenance workbench distributes the target rule package to the rule execution server.

[0009] Optionally, the acquisition module is specifically used for: Poll the download task status interface of the file processing system to obtain the download status of the target rule package; When the download status indicates that the download is complete, the target rule package is obtained from the file processing system.

[0010] Optionally, the distribution module is specifically used for: Call the data upload interface of the production operation and maintenance workbench to upload the target rule package to the data warehouse of the production operation and maintenance workbench; When the upload success message is received from the production operations and maintenance workbench, the management interface of the production operations and maintenance workbench is invoked to publish the target rule package in the data warehouse in the production operations and maintenance workbench.

[0011] Optionally, the distribution module is specifically used for: This enables the production and maintenance workbench to distribute the target rule package to the rule execution server via an internal management channel with the rule execution server.

[0012] Optionally, the distribution module is further configured to: Obtain the decision log data of the old rule package, wherein the decision log data includes: decision input parameters and first decision output parameters; A decision request carrying the decision input parameters is sent to the rule execution server, so that the rule execution server executes a decision based on the decision input parameters and the target rule package to obtain the second decision output parameters; Receive the second decision output parameters returned by the rule execution server; An alarm is triggered when the first decision output parameter and the second decision output parameter are inconsistent.

[0013] Optionally, the distribution module is further configured to: The target rule package is modified to obtain a new version of the rule package.

[0014] Optionally, the distribution module is further configured to: Record the release details of the target rule package, including: release time, release personnel, version identification information, and release content.

[0015] On one hand, embodiments of this application provide a rule publishing device applied to a file processing system, the device comprising: The download module receives a download instruction sent by the publishing system, which carries version identification information of the target rule package. The download instruction is sent by the publishing system in response to a publishing operation triggered on the operation interface for the target rule package. The sending module sends the target rule package to the publishing system, so that the publishing system calls the interface of the production operation and maintenance workbench to publish the target rule package to the production operation and maintenance workbench, so that the production operation and maintenance workbench distributes the target rule package to the rule execution server.

[0016] On one hand, embodiments of this application provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the rule publishing method described above.

[0017] On one hand, embodiments of this application provide a computer-readable storage medium storing a computer program executable by a computer device, which, when run on the computer device, causes the computer device to perform the steps of the rule publishing method described above.

[0018] On one hand, embodiments of this application provide a computer program product, which includes a computer program stored on a computer-readable storage medium. The computer program includes program instructions that, when executed by a computer device, cause the computer device to perform the steps of the rule publishing method described above.

[0019] In this embodiment, in response to a release operation triggered on the operation interface for a target rule package, the release system sends a download instruction carrying version identification information of the target rule package to the file processing system. This enables the file processing system to download the target rule package from the test operation and maintenance workbench based on the version identification information, obtain the target rule package from the file processing system, and then call the interface of the production operation and maintenance workbench to release the target rule package to the production operation and maintenance workbench. The production operation and maintenance workbench then distributes the target rule package to the rule execution server. By constructing a closed-loop management mechanism for the entire process, one-click secure release is achieved, and interaction with various systems is possible. It can automatically drive the execution of tasks in each system according to a predetermined process, replacing manual operation, significantly improving the efficiency of rule package release, and reducing operational risks. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 A schematic diagram of a system architecture provided in an embodiment of this application; Figure 2 A flowchart illustrating a rule publishing method provided in an embodiment of this application; Figure 3 A schematic diagram of the structure of a rule publishing device provided in an embodiment of this application; Figure 4 A schematic diagram of another rule publishing device provided in an embodiment of this application; Figure 5 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0022] To make the objectives, technical solutions, and beneficial effects of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0023] For ease of understanding, the terms used in the embodiments of this invention are explained below.

[0024] A rule package is a static, versioned deliverable. It is a file (usually a KJAR) that contains compiled rule files, decision tables, data models, and dependencies. Essentially, it is a collection of code and data stored in an artifact repository or object store, and can be version controlled and released as a whole.

[0025] Drools Workbench is a web-based, integrated development and control platform for the full lifecycle management of rules and processes. It serves as a unified workbench for rule analysts, developers, and operations administrators, and its core role is the "design and control center" of the Drools rule ecosystem.

[0026] A Maven repository is a dedicated server for storing, versioning, and distributing Drools rule packages (KJARs) and all related dependencies on demand. It is the "sole trusted source" connecting the rule design and development end (Drools Workbench) and the rule execution server (KIE Server cluster).

[0027] The following is a brief introduction to the system architecture diagram applicable to the technical solutions of the embodiments of this application. It should be noted that the system architecture diagram described below is only used to illustrate the embodiments of this application and is not intended to limit the scope of the application.

[0028] refer to Figure 1 This is a system architecture diagram applicable to the embodiments of this application. The system architecture includes at least a publishing system 101, a file processing system 102, a production operation and maintenance workbench 103, a test operation and maintenance workbench 104, and a rule execution server 105. The number of publishing systems 101, file processing systems 102, production operation and maintenance workbench 103, and test operation and maintenance workbench 104 can be one or more, and this application does not specifically limit their number.

[0029] The publishing system 101 can call the file processing system 102 through an interface, and the publishing system 101 can call the production operation and maintenance workbench 103 through an interface. This application does not make any specific limitations on this.

[0030] Among them, the publishing system 101 acts as a "bridge" and "controller" connecting all the above systems. It has the functions of automatically driving each system to execute tasks according to a predetermined process, automatically verifying results, and blocking operations, thus replacing manual operation. At the same time, it can interact with each system through a standardized programming interface (REST Application Programming Interface, or REST API) with a REST architectural style.

[0031] The file processing system 102 serves as a rule package version repository, used to persistently store the rule package binary files (KJAR) compiled by the test and maintenance workbench, and to provide a stable file retrieval interface for subsequent release processes.

[0032] Production Operations Workbench 103 serves as the rule governance and registration center for the production environment. It is responsible for receiving rule packages and deploying them to the rule execution server (KIE Server cluster), while also managing the deployed rule packages in a unified manner.

[0033] Test and Operation Workbench 104 serves as the rule design and development center, allowing business personnel to write, debug, and test rules. Its core output is the compiled rule package (KJAR).

[0034] The rule execution server 105 serves as the rule runtime engine, undertaking the actual execution of deployed rule packages and providing highly available rule decision services for client applications (such as marketing systems).

[0035] The publishing system 101 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0036] The file processing system 102 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0037] The production and maintenance workbench 103 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0038] The test and maintenance workbench 104 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0039] The rule enforcement server 105 can be a standalone physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0040] In this embodiment, the publishing system 101, the file processing system 102, the production operation and maintenance workbench 103, the test operation and maintenance workbench 104, and the rule execution server 105 can communicate directly or indirectly through one or more networks. This network can be a wired network or a wireless network. For example, the wireless network can be a mobile cellular network or a Wireless-Fidelity (WIFI) network, or other possible networks. This embodiment does not limit the types of networks used.

[0041] The following is based on Figure 1 The system architecture diagram shown in this application illustrates the flow of a rule publishing method. Figure 2 As shown, the process of this method involves interaction between the release system, file processing system, production operations and maintenance workbench, test operations and maintenance workbench, and rule execution server, and includes the following steps: In step S201, the publishing system responds to the publishing operation triggered on the operation interface for the target rule package by sending a download instruction carrying the version identifier information of the target rule package to the file processing system.

[0042] Specifically, business personnel enter the version identifier information of the target rule package that has been built in the test and maintenance workbench in the unified operation interface of the release system, and then trigger the release operation for the target rule package in the operation interface; accordingly, the release system sends the version identifier information of the target rule package to the file processing system and issues a download instruction, which instructs to download the file system rule package.

[0043] Among them, the test and maintenance workbench is the design and development center for rules, which allows business personnel to write, debug and test rules. Its core output is the compiled rule package (KJAR).

[0044] Version identification information is used to uniquely identify a specific version of a rule package. Typically, version identification information may include the version number, build time, build number, Git commit hash, etc. This information helps to accurately track rule packages during testing, release, and issue troubleshooting.

[0045] In step S202, the file processing system downloads the target rule package from the test and maintenance workbench based on the version identification information.

[0046] Specifically, the file processing system receives download instructions from the release system through the Application Programming Interface (API). After verifying the legality of the download instructions, it immediately starts an asynchronous download task, calls the interface of the test and maintenance workbench to download the target rule package carrying the specified version identification information, marks the download status as "in progress", and returns the task ID to the release system so that the release system can query the task status later.

[0047] When the file processing system executes a download task, it calls the Maven data repository interface provided by the test operations workbench to send a request to the Drools Workbench Maven data repository to download the target rule package at the specified coordinates. Drools Workbench is the creator of the rule package and the initial data repository manager, serving as the rule development and management platform. As a comprehensive test management platform, the test operations workbench integrates the vertical domain's specialized rule tool, Drools Workbench, as its core rule testing module into a unified test workflow through interface integration or API calls. Drools Workbench typically has a built-in Maven repository for storing built rule packages (KJARs).

[0048] The downloaded target rule package is usually stored on the local disk or distributed file system of the file processing system, and the storage path is recorded.

[0049] In practical applications, the target rule package can be processed according to business needs, such as decompression, verification, repackaging, and encryption. These processing steps are also part of the asynchronous task, and this application does not impose any restrictions on them.

[0050] Step S203: The publishing system obtains the target rule package from the file processing system.

[0051] In some embodiments, the publishing system polls the download task status interface of the file processing system to obtain the download status of the target rule package; when the download status indicates that the download is complete, the target rule package is retrieved from the file processing system.

[0052] Specifically, during the download process, the file processing system updates the download status (e.g., downloading, processing, download complete, download failed) and returns the task ID to the publishing system. The publishing system polls the file processing system's download task status interface to obtain the latest download status of the target rule package. When the download status is updated to download complete, the publishing system retrieves the target rule package from the file processing system.

[0053] Step S204: Publish the system call to the production operation and maintenance workbench interface and publish the target rule package to the production operation and maintenance workbench.

[0054] In some embodiments, the publishing system calls the data upload interface of the production operations and maintenance workbench to upload the target rule package to the data warehouse of the production operations and maintenance workbench; when it receives the upload success message returned by the production operations and maintenance workbench, it calls the management interface of the production operations and maintenance workbench to publish the target rule package in the data warehouse in the production operations and maintenance workbench.

[0055] Specifically, after the deployment system uploads the target rule package to the data warehouse of the production operations workbench, the production operations workbench saves the target rule package in the specified directory and returns the upload result to the deployment system. Then, the deployment system automatically deploys the target rule package in the production operations workbench by calling the RESTful management API of the production operations workbench.

[0056] Among them, the RESTful management API of the production operations and maintenance workbench is a standardized programming interface provided by the production operations and maintenance workbench that follows the REST architecture style.

[0057] In this embodiment, the publishing system automatically deploys target rule packages in a specified directory, eliminating the tedious operation of business personnel manually creating rule containers and filtering version numbers from a large number of rule packages, thus achieving full automation of the rule publishing process.

[0058] Step S205: The production operations and maintenance workbench distributes the target rule package to the rule execution server.

[0059] In some embodiments, the production operations workbench utilizes the internal management channel with the rule enforcement server to distribute target rule packages to the rule enforcement server.

[0060] After receiving the instruction to release the target rule package, the production operations and maintenance workbench uses internal management channels (such as the communication mechanism with KIEServer) to automatically distribute the rule package to the rule execution server (i.e., the KIE Server cluster) to complete the creation or update of the rule container.

[0061] Once the target rule package is loaded, compiled, and put into service, the application can execute the target rule package by calling the container's REST endpoint.

[0062] The rule container refers to a dynamic, isolated runtime environment created within the rule execution server (specifically, the KIE Server cluster). It hosts a loaded and activated instance of a rule package, manages the lifecycle of the rule package (loading, compiling, and executing), maintains the rule engine session, and provides REST or JMS interfaces for external calls.

[0063] In this embodiment, in response to a release operation triggered on the operation interface for a target rule package, the release system sends a download instruction carrying version identification information of the target rule package to the file processing system. This enables the file processing system to download the target rule package from the test operation and maintenance workbench based on the version identification information, obtain the target rule package from the file processing system, and then call the interface of the production operation and maintenance workbench to release the target rule package to the production operation and maintenance workbench. This allows the production operation and maintenance workbench to distribute the target rule package to the rule execution server. Through three core capabilities—automatic environment synchronization, visualized operational status, and real-time feedback of release results—a closed-loop management mechanism is constructed, enabling one-click secure release. It can also interact with various systems, automatically driving tasks in each system according to a predetermined process, replacing manual operation, significantly improving the efficiency of rule package release and reducing operational risks.

[0064] In some embodiments, decision log data of the old rule package is obtained, the decision log data including: decision input parameters and first decision output parameters; a decision request carrying decision input parameters is sent to the rule execution server so that the rule execution server performs a decision based on the decision input parameters and the target rule package to obtain second decision output parameters; the second decision output parameters returned by the rule execution server are received; when the first decision output parameters and the second decision output parameters are inconsistent, an alarm is triggered.

[0065] Specifically, after the rule package is automatically distributed to the rule execution server, the system automatically triggers the Beta dual-run verification process for the target rule package. Specifically, a Beta dual-run task is first created, then the decision log data from previous periods of the old rule package is obtained, and the decision input parameters and the first decision output parameters (including decision request information, decision tags, decision status, etc.) from the decision log data are saved in the data area to be replayed. Then, the publishing system sends a new decision request carrying the decision input parameters to the rule execution server, causing the rule execution server to re-execute the decision in the target rule package based on the decision input parameters, obtain the second decision output parameters of the target rule package, and save them.

[0066] The publishing system receives the second decision parameters returned by the rule execution server, then compares them with the differences between the first decision parameters of the old rule package and the second decision parameters of the target rule package. Based on the combination relationships of different differences in the rule packages, a consistent difference conclusion is formed. The publishing system triggers an alarm and notifies the user of the difference conclusion.

[0067] Specifically, through static analysis, code parsing, and other techniques, the differences between the first and second decision-making parameters are extracted across multiple dimensions, and some differences are quantified (e.g., the proportion of rule changes, the number of dependency conflicts). These multi-dimensional differences are then combined to obtain a conclusion regarding the differences.

[0068] For example, the combined impact of "modifying core risk control rules (business logic difference)" and "upgrading risk calculation model dependencies (dependency difference)" is far greater than the impact of a single difference. An alert should be triggered to notify the user of the difference conclusion, such as: "Risk level: High, manual review required," or "Conclusion: Passed, can be automatically deployed," or "Incompatible: Dependency conflict exists, release prohibited," etc.

[0069] In some embodiments, the publishing system modifies the target rule package to obtain a new version of the rule package.

[0070] Specifically, after the business personnel judge the differences obtained above, if the second decision parameters show an improvement as expected compared to the first decision parameters, the publishing system will modify the old rule package into the target rule package and then pull traffic into it.

[0071] If the second decision parameter does not show the expected improvement compared to the first decision parameter, the release system will not modify the old rule package that is being executed, but will instead modify the target rule package to obtain a new version rule package. Then, the release process of steps S201-S205 will be repeated for the new rule version package until the difference conclusion meets the expectations.

[0072] In this embodiment, the Beta dual-run release function is supported. By recording the decision log data of the old rule package (including decision input parameters and first decision output parameters), the decision of the newly released target rule package is re-made. Then, the decision output parameters of the old rule package and the target rule package are compared. Based on the difference in the decision output parameters, it is determined whether the consistency standard is met. If it fails, the release process is blocked, thereby ensuring system stability and business continuity. At the same time, it reduces the operational risks of native Drools release, solves the problem of unstable decision requests caused by insufficient rule package compatibility after automatic release, and improves release stability.

[0073] In some embodiments, the publishing system records the publishing details of the target rule package, including: publishing time, publisher, version identifier information, and publishing content.

[0074] Specifically, after traffic is successfully drawn in, the publishing system will record detailed information about the rule publication, including the publication time, the publisher, the rule package version number, and the published content, so as to facilitate subsequent version tracking and problem investigation.

[0075] Based on the same technical concept, this application provides a schematic diagram of a rule publishing device, applied to a publishing system, such as... Figure 3 As shown, the device 300 includes: The instruction sending module 301 is used to send a download instruction carrying the version identification information of the target rule package to the file processing system in response to the release operation triggered on the operation interface for the target rule package, so that the file processing system downloads the target rule package from the test and maintenance workbench based on the version identification information; The acquisition module 302 is used to acquire the target rule package from the file processing system; The distribution module 303 is used to call the interface of the production operation and maintenance workbench to publish the target rule package to the production operation and maintenance workbench, so that the production operation and maintenance workbench distributes the target rule package to the rule execution server.

[0076] Optionally, the acquisition module 302 is specifically used for: Poll the download task status interface of the file processing system to obtain the download status of the target rule package; When the download status indicates that the download is complete, the target rule package is obtained from the file processing system.

[0077] Optionally, the distribution module 303 is specifically used for: Call the data upload interface of the production operation and maintenance workbench to upload the target rule package to the data warehouse of the production operation and maintenance workbench; When the upload success message is received from the production operations and maintenance workbench, the management interface of the production operations and maintenance workbench is invoked to publish the target rule package in the data warehouse in the production operations and maintenance workbench.

[0078] Optionally, the distribution module 303 is specifically used for: This enables the production and maintenance workbench to distribute the target rule package to the rule execution server via an internal management channel with the rule execution server.

[0079] Optionally, the distribution module 303 is further configured to: Obtain the decision log data of the old rule package, wherein the decision log data includes: decision input parameters and first decision output parameters; A decision request carrying the decision input parameters is sent to the rule execution server, so that the rule execution server executes a decision based on the decision input parameters and the target rule package to obtain the second decision output parameters; Receive the second decision output parameters returned by the rule execution server; An alarm is triggered when the first decision output parameter and the second decision output parameter are inconsistent.

[0080] Optionally, the distribution module 303 is further configured to: The target rule package is modified to obtain a new version of the rule package.

[0081] Optionally, the distribution module 303 is further configured to: Record the release details of the target rule package, including: release time, release personnel, version identification information, and release content.

[0082] Based on the same technical concept, this application provides a schematic diagram of a rule publishing device, applied to a file processing system, such as... Figure 4 As shown, the rule issuing device 400 includes: The download module 401 receives a download instruction sent by the publishing system, which carries version identification information of the target rule package. The download instruction is sent by the publishing system in response to a publishing operation triggered on the operation interface for the target rule package. The sending module 402 sends the target rule package to the publishing system, so that the publishing system calls the interface of the production operation and maintenance workbench to publish the target rule package to the production operation and maintenance workbench, so that the production operation and maintenance workbench distributes the target rule package to the rule execution server.

[0083] In this embodiment, in response to a release operation triggered on the operation interface for a target rule package, the release system sends a download instruction carrying version identification information of the target rule package to the file processing system. This enables the file processing system to download the target rule package from the test operation and maintenance workbench based on the version identification information, obtain the target rule package from the file processing system, and then call the interface of the production operation and maintenance workbench to release the target rule package to the production operation and maintenance workbench. The production operation and maintenance workbench then distributes the target rule package to the rule execution server. By constructing a closed-loop management mechanism for the entire process, one-click secure release is achieved, and interaction with various systems is possible. It can automatically drive the execution of tasks in each system according to a predetermined process, replacing manual operation, significantly improving the efficiency of rule package release, and reducing operational risks.

[0084] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0085] Based on the same technical concept, embodiments of this application provide a computer device, which can be... Figure 1 The terminal devices and / or servers shown, such as Figure 5 As shown, it includes at least one processor 501 and a memory 502 connected to at least one processor. In this embodiment, the specific connection medium between the processor 501 and the memory 502 is not limited. Figure 5 Taking the connection between processor 501 and memory 502 via a bus as an example, the bus can be divided into address bus, data bus, control bus, etc.

[0086] In this embodiment of the application, the memory 502 stores instructions that can be executed by at least one processor 501. By executing the instructions stored in the memory 502, at least one processor 501 can perform the steps of the rule publishing method described above.

[0087] The processor 501 is the control center of the computer device. It can connect to various parts of the computer device using various interfaces and lines, and implements rule publishing by running or executing instructions stored in the memory 502 and calling data stored in the memory 502. Optionally, the processor 501 may include one or more processing units. The processor 501 may integrate an application processor and a modem processor. The application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 501. In some embodiments, the processor 501 and the memory 502 may be implemented on the same chip; in some embodiments, they may also be implemented on separate chips.

[0088] Processor 501 can be a general-purpose processor, such as a central processing unit (CPU), digital signal processor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0089] Memory 502, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. Memory 502 may include at least one type of storage medium, such as flash memory, hard disk, multimedia card, card-type memory, random access memory (RAM), static random access memory (SRAM), programmable read-only memory (PROM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic memory, magnetic disk, optical disk, etc. Memory 502 can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer device, but is not limited thereto. In the embodiments of this application, memory 502 can also be a circuit or any other device capable of implementing storage functions for storing program instructions and / or data.

[0090] Based on the same inventive concept, embodiments of this application provide a computer-readable storage medium storing a computer program executable by a computer device, which, when run on the computer device, causes the computer device to perform the steps of the above-described rule publishing method.

[0091] Based on the same inventive concept, this application provides a computer program product, which includes a computer program stored on a computer-readable storage medium. The computer program includes program instructions that, when executed by a computer device, cause the computer device to perform the steps of the rule publishing method described above.

[0092] Those skilled in the art will understand that embodiments of the present invention can be provided as methods or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0093] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer apparatus or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0094] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer device or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0095] These computer program instructions may also be loaded onto a computer device or other programmable data processing equipment to cause a series of operational steps to be performed on the computer device or other programmable equipment to produce a process implemented by the computer device, thereby providing instructions that execute on the computer device or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0096] Although preferred embodiments of the invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including both the preferred embodiments and all changes and modifications falling within the scope of the invention.

[0097] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

Claims

1. A rule publishing method, characterized in that, Applied to publishing systems, including: In response to a release operation triggered on the operation interface for a target rule package, a download instruction carrying version identification information of the target rule package is sent to the file processing system, so that the file processing system downloads the target rule package from the test and maintenance workbench based on the version identification information; Obtain the target rule package from the file processing system; The target rule package is published to the production operations and maintenance workbench by calling its interface, so that the production operations and maintenance workbench can distribute the target rule package to the rule execution server.

2. The method as described in claim 1, characterized in that, Obtaining the target rule package from the file processing system includes: Poll the download task status interface of the file processing system to obtain the download status of the target rule package; When the download status indicates that the download is complete, the target rule package is obtained from the file processing system.

3. The method as described in claim 1, characterized in that, The step of calling the interface of the production operations and maintenance workbench to publish the target rule package to the production operations and maintenance workbench includes: Call the data upload interface of the production operation and maintenance workbench to upload the target rule package to the data warehouse of the production operation and maintenance workbench; When the upload success message is received from the production operations and maintenance workbench, the management interface of the production operations and maintenance workbench is invoked to publish the target rule package in the data warehouse in the production operations and maintenance workbench.

4. The method as described in claim 1, characterized in that, The step of enabling the production operations and maintenance workbench to distribute the target rule package to the rule execution server includes: This enables the production and maintenance workbench to distribute the target rule package to the rule execution server via an internal management channel with the rule execution server.

5. The method as described in claim 1, characterized in that, Also includes: Obtain the decision log data of the old rule package, wherein the decision log data includes: decision input parameters and first decision output parameters; A decision request carrying the decision input parameters is sent to the rule execution server, so that the rule execution server executes a decision based on the decision input parameters and the target rule package to obtain the second decision output parameters; Receive the second decision output parameters returned by the rule execution server; An alarm is triggered when the first decision output parameter and the second decision output parameter are inconsistent.

6. The method as described in claim 5, characterized in that, After triggering an alarm when the first decision output parameter and the second decision output parameter are inconsistent, the method further includes: The target rule package is modified to obtain a new version of the rule package.

7. The method as described in claim 1, characterized in that, Also includes: Record the release details of the target rule package, including: release time, release personnel, version identification information, and release content.

8. A rule publishing method, characterized in that, Applied to file processing systems, including: The system receives a download instruction from the publishing system that carries version identification information of the target rule package. The download instruction is sent by the publishing system in response to a publishing operation triggered on the operation interface for the target rule package. Download the target rule package from the test and maintenance workbench based on the version identification information; The target rule package is sent to the publishing system, so that the publishing system calls the interface of the production operation and maintenance workbench to publish the target rule package to the production operation and maintenance workbench, so that the production operation and maintenance workbench distributes the target rule package to the rule execution server.

9. A rule publishing device, characterized in that, Applied to publishing systems, including: The instruction sending module is used to send a download instruction carrying the version identification information of the target rule package to the file processing system in response to a release operation triggered on the operation interface for the target rule package, so that the file processing system downloads the target rule package from the test and maintenance workbench based on the version identification information; The acquisition module is used to acquire the target rule package from the file processing system; The distribution module is used to call the interface of the production operation and maintenance workbench to publish the target rule package to the production operation and maintenance workbench, so that the production operation and maintenance workbench distributes the target rule package to the rule execution server.

10. A rule publishing device, characterized in that, Applied to file processing systems, including: The download module receives a download instruction sent by the publishing system, which carries version identification information of the target rule package. The download instruction is sent by the publishing system in response to a publishing operation triggered on the operation interface for the target rule package. The sending module sends the target rule package to the publishing system, so that the publishing system calls the interface of the production operation and maintenance workbench to publish the target rule package to the production operation and maintenance workbench, so that the production operation and maintenance workbench distributes the target rule package to the rule execution server.

Images