Stateless process engine breakpoint continuous running method and system

Abstract

The invention relates to the technical field of credit risk control, in particular to a stateless process engine breakpoint running continuation method and system, and the method comprises the steps: obtaining a request unique id and a process id of a current breakpoint running continuation request; obtaining process arrangement information; acquiring technical context information; initiating a breakpoint continuous running request; judging whether the current task node is executed or not by adopting an access detector technology so as to identify whether the current task node is a breakpoint or not; assembling execution information of the current task node by adopting a post-processor technology, and storing the execution information in technical context information; and synchronously storing the technical context information and the request unique id of the current breakpoint continuous running request in a non-relational database and a relational database. According to the method, the Redis database and the MySQL database are integrated, and the access detector and the rear processor of the LiteFlow process engine are utilized, so that an efficient and reliable breakpoint continuous running mechanism is realized, and the LiteFlow process engine can accurately recover execution from a breakpoint after the process is interrupted.

Description

Technical Field

[0001] The present invention relates to the field of credit risk control technology, and in particular to a breakpoint resumption method and system for a stateless process engine. Background Art

[0002] In the modern financial field, especially in the credit scenario, risk control (risk control) business is the core link to ensure financial stability and prevent bad loans. The complexity of risk control business lies in the diversity of events involved, the large number of processing nodes and the cumbersome process. These characteristics require that the risk control process must be efficient and flexible. In order to meet these challenges, process engine technology is widely used in the automated orchestration of risk control business processes to improve processing speed and accuracy.

[0003] In the field of credit risk control, process engines are key tools for improving efficiency and controlling risks. Existing process engine technologies, such as Activiti, Flowable, Comanda, and LiteFlow, are relatively comprehensive in terms of functionality, but they have some shortcomings in terms of performance and user experience.

[0004] Activiti is a lightweight open source workflow engine based on BPMN2.0. It is easy to integrate with the Spring framework, but its community activity is relatively low and its concurrent processing capabilities are weak.

[0005] Flowable is a branch of Activiti, with a high level of community activity, but it also suffers from the problem of insufficient concurrent processing capabilities.

[0006] Comanda is developed based on Activiti, with more comprehensive functions and stronger performance, especially suitable for cloud services. Its concurrent processing capability is about twice that of Flowable, and it provides complete UI capabilities, but compared with LiteFlow, it is generally heavier and more complicated to use.

[0007] LiteFlow is a domestic process engine framework that has attracted attention for its lightweight and powerful concurrent processing capabilities. It adopts a workbench mode, has comprehensive basic functions, and has strong component reuse capabilities, making it particularly suitable for scenarios that require high concurrent processing. However, although LiteFlow's stateless design helps improve performance, its stateless design limits its application in breakpoint-resume business scenarios. In the field of credit risk control, breakpoint-resume is an important requirement, because the risk control process may be interrupted for a variety of reasons (such as system maintenance, emergencies, data dependencies, etc.), and the ability to recover the process from the breakpoint after the interruption is crucial to ensuring business continuity and improving customer satisfaction.

[0008] To this end, the present invention provides a stateless process engine breakpoint resumption method and system. Summary of the invention

[0009] Based on this, it is necessary to provide a stateless process engine breakpoint resumption method and system to address the above technical problems. This method aims to solve the problem of maintaining the stateless characteristics of the LiteFlow process engine while realizing the breakpoint resumption function to meet the continuity and stability requirements of credit risk control business.

[0010] According to one aspect of the present invention, a stateless process engine breakpoint resumption method is provided, comprising: obtaining a request unique ID and a process ID of a current breakpoint resumption request according to a breakpoint resumption requirement; obtaining corresponding process orchestration information from a memory buffer based on the process ID; inspecting corresponding technical context information in a non-relational database based on the request unique ID and the process ID of the current breakpoint resumption request, identifying the corresponding technical context information if the corresponding technical context information exists in the non-relational database, and identifying the corresponding technical context information from the relational database if the corresponding technical context information does not exist in the non-relational database; initiating a breakpoint resumption request based on the process orchestration information and the technical context information, and resuming the process execution steps; in response to the breakpoint resumption request, using an access detector technology to retrieve the technical context information from the technical context The step set of the executed task node is obtained from the information, and according to the label id of the current task node, it is determined whether the current task node has been executed to identify whether the current task node is a breakpoint. If the current task node is not executed or fails to execute, the process of the current task node is executed by the LiteFlow process engine and the record of the execution failure is removed. If the current task node has been executed successfully, the process execution step is no longer performed again. After the execution of the current task node is completed, the post-processor technology is used to assemble the execution information of the current task node, and the execution information is stored in the technical context information. After the execution of the process is completed, the technical context information and the request unique id of the current breakpoint continuation request are synchronously stored in the non-relational database and the relational database, and the cache expiration time of the technical context information in the non-relational database is formulated.

[0011] In some optional implementations of some embodiments, the acquiring corresponding process orchestration information from a memory buffer based on a process ID includes: acquiring corresponding process orchestration information from a FlowBus memory buffer based on a process ID.

[0012] In some optional implementations of some embodiments, when responding to a breakpoint resume request, the access detector technology is used to obtain a set of steps of the executed task node from the technical context information, and judge whether the current task node has been executed based on the label id of the current task node to identify whether the current task node is a breakpoint. If the current task node is not executed or fails to execute, it is executed through the LiteFlow process engine and the record of the failed execution is removed. If the current task node has been executed, the re-process execution step is no longer performed, including: when responding to a breakpoint resume request, the access detector is called to obtain the executed task from the technical context information. The step set of the task node is determined, and whether the label id of the current task node exists in the step set of the executed task node is determined to identify whether the current task node is a breakpoint. If not, the current task node is identified as a breakpoint and the current task node is not executed, and the process of the current task node is executed through the LiteFlow process engine. If it exists, it is determined whether the current task node has been executed successfully. If the execution has been executed successfully, the process execution step is no longer performed again; if the execution fails, the process of the current task node is re-executed through the LiteFlow process engine, and the record of the failed execution of the current task node is deleted from the technical context information.

[0013] In some optional implementation methods of some embodiments, after the current task node is executed, the postprocessor technology is used to assemble the execution information of the current task node, and the execution information is stored in the technical context information, including: after the current task node is executed, the postprocessor is called to assemble the execution information of the current task node, the execution information includes the running status and execution results of the current task node, and the execution information is stored in the technical context information.

[0014] In some optional implementations of some embodiments, the technical context information is used to store key information during the process execution, including a set of steps of executed task nodes, the operating status of each task node, and the corresponding execution results.

[0015] In some optional implementation methods of some embodiments, after the process execution is completed, the technical context information and the request unique id of the current breakpoint resume request are synchronously stored in a non-relational database and a relational database, and a cache expiration time of the technical context information in the non-relational database is formulated, including: storing the technical context information and the request unique id of the current breakpoint resume request in a non-relational database, and formulating a cache expiration time for the corresponding technical context information in the non-relational database; and synchronously storing the technical context information and the request unique id of the current breakpoint resume request in a relational database.

[0016] In some optional implementations of some embodiments, the non-relational database is a Redis database, and the relational database is a MySQL database.

[0017] According to a second aspect of the present invention, a stateless process engine breakpoint resume system is provided, comprising: a first data acquisition module, used to obtain the request unique ID and process ID of the current breakpoint resume request according to the breakpoint resume requirement; a second data acquisition module, used to obtain the corresponding process orchestration information from the memory buffer based on the process ID; a third data acquisition module, used to inspect the corresponding technical context information in the non-relational database based on the request unique ID and process ID of the current breakpoint resume request, and if the corresponding technical context information exists in the non-relational database, identify the corresponding technical context information; if the corresponding technical context information does not exist in the non-relational database, identify the corresponding technical context information from the relational database; a breakpoint resume request module, used to initiate a breakpoint resume request based on the process orchestration information and the technical context information, and restore the process execution steps; an access detector calling module, used to When responding to a breakpoint resume request, the access detector technology is used to obtain the step set of the executed task node from the technical context information, and judge whether the current task node has been executed based on the label id of the current task node. If the current task node has not been executed or the execution fails, the process of the current task node is executed through the LiteFlow process engine and the record of the execution failure is removed. If the current task node has been executed successfully, the process execution step will no longer be performed again; the post-processor calling module is used to assemble the execution information of the current task node by using the post-processor technology after the current task node is executed, and store the execution information in the technical context information; the storage module is used to synchronously store the technical context information and the request unique id of the current breakpoint resume request in the non-relational database and the relational database after the process execution is completed, and formulate the cache expiration time of the technical context information in the non-relational database.

[0018] According to a third aspect of the present invention, an electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.

[0019] According to a fourth aspect of the present invention, there is provided a computer-readable storage medium storing a computer program, wherein the computer program implements the steps of the above method when executed by a processor.

[0020] The advantages and beneficial effects of the present invention are: the stateless process engine breakpoint resume method and system provided by the present invention integrates Redis and MySQL databases, and utilizes the admission detector and post-processor of the LiteFlow process engine to realize an efficient and reliable breakpoint resume mechanism, so that the LiteFlow process engine can accurately resume execution from the breakpoint after the process is interrupted, which not only improves the continuity and stability of the risk control business, but also maintains the high performance and lightweight characteristics of the LiteFlow process engine, significantly improving the management efficiency of the risk control process and the overall performance of the system. In addition, the method has the characteristics of high efficiency, reliability, flexibility and ease of use, wherein, by caching technical context information in Redis, the response speed of breakpoint resume can be effectively improved, and the reliability of technical context information can be ensured by asynchronous persistent storage of the MySQL database. The expiration time of the Redis cache can be flexibly set according to different business scenarios to automatically clear outdated technical context information, and can also be seamlessly integrated with the LiteFlow process engine without making a lot of modifications to the existing business process, thereby simplifying the maintenance and upgrade of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 The present invention is a flowchart of a method for resuming a stateless process engine from a breakpoint in an embodiment of the present invention.

[0022] Figure 2 It is a schematic diagram of a stateless process engine breakpoint resumption system in an embodiment of the present invention.

[0023] Figure 3 Schematic diagram of an electronic device in an embodiment of the present invention. DETAILED DESCRIPTION

[0024] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below through specific implementation methods in conjunction with the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0025] Embodiment 1 Attached Figure 1 A flowchart of a stateless process engine breakpoint resumption method provided in this application.

[0026] For application scenarios in which the breakpoint resumption function is realized while maintaining the stateless characteristics of the LiteFlow process engine to meet the continuity and stability requirements of the credit risk control business, the present invention proposes a stateless process engine breakpoint resumption method.

[0027] Reference Figure 1, a stateless process engine breakpoint resumption method, the method specifically includes the following steps.

[0028] Step S1: According to the breakpoint resume requirement, obtain the request unique ID and process ID of the current breakpoint resume request.

[0029] In some embodiments, when breakpoint resumption is required, it is first necessary to obtain the unique request ID (ie, requestId) and process ID (ie, chainId) of the current breakpoint resumption request in the workflow.

[0030] Step S2: Based on the process ID, obtain the corresponding process scheduling information from the memory buffer.

[0031] In some embodiments, the process orchestration information is obtained from the FlowBus memory buffer through the process id.

[0032] Step S3: Based on the request unique ID and process ID of the current breakpoint resume request, check the corresponding technical context information in the non-relational database. If the corresponding technical context information exists in the non-relational database, identify the corresponding technical context information. If the corresponding technical context information does not exist in the non-relational database, identify the corresponding technical context information from the relational database.

[0033] In some embodiments, after each process execution ends, regardless of whether the process execution process ends normally or abnormally, the technical context information and the requestId (request unique id) of the current breakpoint resume request are synchronously stored in the Redis non-relational database, and a preset cache expiration time can be set according to business needs to automatically clear outdated technical context information.

[0034] In some embodiments, after each process execution is completed, the technical context information and the requestId (request unique id) of the current breakpoint resume request are also synchronously stored in the MySQL relational database as persistent storage, which realizes the persistent approval process while ensuring the timeliness of process approval.

[0035] Step S4: Based on the process orchestration information and technical context information, a breakpoint resume request is initiated and the process execution steps are resumed.

[0036] In some embodiments, after obtaining the process orchestration information and the technical context information, these two parts of information are combined, and a breakpoint resume request is initiated to resume the process execution steps.

[0037] Step S5: In response to a breakpoint resume request, the access detector technology is used to obtain the step set of the executed task node from the technical context information, and judge whether the current task node has been executed based on the label id of the current task node to identify whether the current task node is a breakpoint. If the current task node is not executed or fails to execute, the process of the current task node is executed through the LiteFlow process engine and the record of the failed execution is removed. If the current task node has been executed successfully, the process execution step will no longer be performed again.

[0038] In some embodiments, in response to a breakpoint resume request, an admission detector technology is used to obtain a step set of an executed task node from the technical context information, and based on the label id of the current task node, it is determined whether the current task node has been executed to identify whether the current task node is a breakpoint. If the current task node is not executed or fails to execute, it is executed by the LiteFlow process engine and the record of the failed execution is removed. If the current task node has been executed, the re-process execution step is no longer performed, including: in response to a breakpoint resume request, the admission detector is called to obtain a step set of an executed task node from the technical context information, and it is determined whether the label id of the current task node exists in the step set of the executed task node to identify whether the current task node is a breakpoint. If not, the current task node is identified as a breakpoint and the current task node is not executed. The process of the current task node is executed by the LiteFlow process engine. If it exists, it is determined whether the current task node has been executed successfully. If the execution has been executed successfully, the re-process execution step is no longer performed; if the execution fails, the process of the current task node is re-executed by the LiteFlow process engine, and the record of the failed execution of the current task node is deleted from the technical context information.

[0039] In some embodiments, the present application implements the process of node execution judgment and technical context information processing by calling an access detector, namely, the isAccess() method, which specifically includes: (1) calling the isAccess() method (access detector) at each business node in the process; (2) obtaining a set of steps of the executed node from the technical context information; (3) judging whether the tagId (i.e., label id) of the current task node already exists in the step set; (4) if not, allowing the process of the current task node to be executed through the LiteFlow process engine; (5) if it exists, further judging whether the task node has been successfully executed; (6) if successful, no longer performing the process re-execution step; (7) if failed, allowing the process of the current task node to be re-executed through the LiteFlow process engine, and deleting the record of the failed execution of the task node in the technical context information.

[0040] Step S6: After the current task node is executed, the post-processor technology is used to assemble the execution information of the current task node, and the execution information is stored in the technical context information.

[0041] In some embodiments, after the current task node is executed, a postprocessor technology is used to assemble the execution information of the current task node, and the execution information is stored in the technical context information, including: after the current task node is executed, the postprocessor is called to assemble the execution information of the current task node, the execution information includes the running status and execution results of the current task node, and the execution information is stored in the technical context information.

[0042] In some embodiments, the present application implements the assembly process of the current task node execution information by calling a post-processor, namely, the after Process() method, and stores it in the technical context information.

[0043] Step S7: After the process execution is completed, the technical context information and the request unique ID of the current breakpoint resume request are synchronously stored in the non-relational database and the relational database, and a cache expiration time of the technical context information in the non-relational database is set.

[0044] In some embodiments, after the execution of the process is completed, the technical context information and the request unique id of the current breakpoint resume request are synchronously stored in a non-relational database and a relational database, and a cache expiration time of the technical context information in the non-relational database is set, including: storing the technical context information and the request unique id of the current breakpoint resume request in a non-relational database, and setting a cache expiration time for the corresponding technical context information in the non-relational database; and synchronously storing the technical context information and the request unique id of the current breakpoint resume request in a relational database.

[0045] In some embodiments, the non-relational database is a Redis database, and the relational database is a MySQL database.

[0046] In summary, this application proposes a stateless process engine breakpoint resumption method, which obtains the corresponding process scheduling information from the memory buffer through the process id, obtains the technical context information from the Redis database or MySQL database through the request unique id and process id of the current breakpoint resumption request, initiates a breakpoint resumption request based on the obtained process scheduling information and technical context information, uses the admission detector of the LiteFlow process engine to implement the node execution judgment and technical context information processing process, and uses the post-processor of the LiteFlow process engine to implement the assembly of the execution information of the current task node, and stores the execution information in the technical context information. After the process execution is completed, the technical context information and the unique request ID of the current breakpoint resume request are synchronously stored in the Redis database and the MySQL database, and the cache expiration time of the technical context information in the non-relational database is set. Therefore, this method has the following advantages: (1) It improves the continuity of the business. Through the breakpoint resume mechanism, it ensures that the risk control process can continue from the last interruption point when it encounters an interruption, avoiding delays and resource waste caused by starting the process from the beginning; (2) It enhances the compatibility of the business. This method can adapt to different business scenarios. Whether it ends normally or is interrupted abnormally, it can ensure the integrity and accuracy of the business process; (3) It improves the approval process. (4) It optimizes resource utilization. By quickly resuming process execution, it reduces waiting time and improves the efficiency of risk control approval, which is particularly important for credit business that requires rapid response. (5) It ensures data reliability. By writing to the MySQL database, it ensures the persistent storage of technical context information, which ensures that data is not lost even in the event of a system failure. (6) It simplifies system maintenance and can be seamlessly integrated with the LiteFlow process engine, eliminating the need to make extensive modifications to existing business processes, thus simplifying system maintenance. and upgrade work; (7) Improved system stability. By performing intelligent data synchronization between Redis and MySQL, the stability and reliability of the system in a high-concurrency environment are ensured; (8) Enhanced user experience. Users can quickly restore to the previous working state after a process interruption without restarting the process, which improves user satisfaction and work efficiency; (9) Supports business expansion and future expansion of business processes. New business nodes can be easily added to existing processes without making major changes to the breakpoint resumption mechanism; (10) Reduced operating costs. By improving the level of automation in process execution and reducing the need for manual intervention, the operating costs of the enterprise are reduced.

[0047] Embodiment 2 This embodiment provides a stateless process engine breakpoint resumption system 200 based on the above embodiment 1. Figure 2 , used to implement the steps of a stateless process engine breakpoint resumption method described in the above-mentioned embodiment 1, the device mainly includes: according to the workflow breakpoint resumption requirement 201, the second data acquisition module 202, the third data acquisition module 203, the breakpoint resumption request module 204, the access detector calling module 205, the post-processor calling module 206 and the storage module 207.

[0048] In some embodiments, the first data acquisition module 201 is used to obtain the request unique ID and process ID of the current breakpoint resume request according to the breakpoint resume requirement.

[0049] In some embodiments, the second data acquisition module 202 is used to acquire corresponding process orchestration information from the memory buffer based on the process ID.

[0050] In some embodiments, the third data acquisition module 203 is used to inspect the corresponding technical context information in the non-relational database based on the request unique ID and process ID of the current breakpoint resume request. If the corresponding technical context information exists in the non-relational database, the corresponding technical context information is identified; if the corresponding technical context information does not exist in the non-relational database, the corresponding technical context information is identified from the relational database.

[0051] In some embodiments, the breakpoint resume request module 204 is used to initiate a breakpoint resume request based on the process orchestration information and the technical context information, and to resume the process execution steps.

[0052] In some embodiments, the admission detector calling module 205 is used to respond to a breakpoint resumption request by using the admission detector technology to obtain a set of steps of the executed task node from the technical context information, and judge whether the current task node has been executed based on the label id of the current task node to identify whether the current task node is a breakpoint. If the current task node is not executed or fails to execute, the process of the current task node is executed through the LiteFlow process engine and the record of the execution failure is removed. If the current task node has been executed successfully, the process execution step will no longer be performed again.

[0053] In some embodiments, the post-processor calling module 206 is used to assemble the execution information of the current task node using the post-processor technology after the current task node is executed, and store the execution information in the technical context information.

[0054] In some embodiments, the storage module 207 is used to synchronously store the technical context information and the request unique ID of the current breakpoint resume request in a non-relational database and a relational database after the process execution is completed, and to formulate a cache expiration time for the technical context information in the non-relational database.

[0055] Embodiment 3 This embodiment further provides an electronic device based on the above embodiment 1. Figure 3 , Figure 3 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0056] like Figure 3 As shown, the electronic device may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 301, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 302 or a program loaded from a storage device 308 to a random access memory (RAM) 303. In the RAM 303, various programs and data required for the operation of the electronic device are also stored. The processing device 301, the ROM 302, and the RAM 303 are connected to each other via a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.

[0057] Typically, the following devices may be connected to the I / O interface 305: an input device 306 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, etc., an output device 307 including, for example, a liquid crystal display (LCD), a speaker, etc., a storage device 308 including, for example, a magnetic tape, a hard disk, etc., and a communication device 309. The communication device 309 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Figure 3 An electronic device having various devices is shown, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead. Figure 3 Each block shown in the figure may represent one device, or may represent multiple devices as required.

[0058] In particular, according to some embodiments of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, some embodiments of the present disclosure include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In some such embodiments, the computer program can be downloaded and installed from the network through the communication device 309, or installed from the storage device 308, or installed from the ROM 302. When the computer program is executed by the processing device 301, the above-mentioned functions defined in the method of some embodiments of the present disclosure are executed.

[0059] Embodiment 4 Based on the above-mentioned embodiment 1, this embodiment further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of the above-mentioned method are implemented.

[0060] It should be noted that the computer-readable medium mentioned above in some embodiments of the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In some embodiments of the present disclosure, the computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, device or device. In some embodiments of the present disclosure, the computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer readable signal media may also be any computer readable medium other than computer readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0061] In this embodiment, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperTextTransferProtocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0062] The computer-readable medium may be included in the device, or may exist independently without being installed in the electronic device. The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: obtains training data, converts the training data into initial data; determines an initial rule base based on the initial data, and optimizes the parameters of the initial rule base to obtain a target rule base; calculates the rules in the target rule base according to a preset activation weight calculation formula to obtain activation weights; determines abnormal information according to the test data and the activation weights.

[0063] Computer program code for performing the operations of some embodiments of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0064] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0065] The units described in some embodiments of the present disclosure may be implemented by software or hardware. The units described may also be provided in a processor, for example, may be described as: a processor including a data acquisition unit, a rule determination unit, a weight calculation unit, and an anomaly determination unit. The names of these units do not, in some cases, constitute limitations on the units themselves, for example, the data acquisition unit may also be described as a "unit for acquiring training data".

[0066] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that may be used include, without limitation, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), etc.

[0067] Obviously, it should be understood by those skilled in the art that the above-mentioned various steps of the present invention can be performed in a manner different from the present invention, and the simulation method and experimental equipment include but are not limited to the above description. The above-mentioned various steps of the present invention can be performed in an order different from that here in some cases, and the steps shown or described above can be performed separately. Therefore, the present invention is not limited to any specific combination of hardware and software.

[0068] The above contents are further detailed descriptions of the present invention in combination with specific implementation methods, and it cannot be determined that the specific implementation of the present invention is limited to these descriptions. For ordinary technicians in the technical field to which the present invention belongs, several simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as falling within the scope of protection of the present invention.

Claims

1. A method for resuming a stateless process engine breakpoint, characterized in that: include: According to the breakpoint resume requirement, obtain the unique request ID and process ID of the current breakpoint resume request; Based on the process ID, obtain the corresponding process scheduling information from the memory buffer; Based on the unique request ID and process ID of the current breakpoint resume request, the corresponding technical context information in the non-relational database is inspected. If the corresponding technical context information exists in the non-relational database, the corresponding technical context information is identified. If the corresponding technical context information does not exist in the non-relational database, the corresponding technical context information is identified from the relational database. Based on process orchestration information and technical context information, initiate a breakpoint resume request and resume process execution steps; In response to a breakpoint resume request, the admission detector technology is used to obtain the step set of the executed task node from the technical context information, and judge whether the current task node has been executed according to the label id of the current task node to identify whether the current task node is a breakpoint. If the current task node is not executed or fails to execute, the process of the current task node is executed through the LiteFlow process engine and the record of execution failure is removed. If the current task node has been executed successfully, the process execution step will not be repeated. After the current task node is executed, the post-processor technology is used to assemble the execution information of the current task node and store the execution information in the technical context information; After the process execution is completed, the technical context information and the unique request ID of the current breakpoint resume request are synchronously stored in the non-relational database and the relational database, and the cache expiration time of the technical context information in the non-relational database is set.

2. A stateless process engine breakpoint resumption method according to claim 1, characterized in that: The obtaining corresponding process scheduling information from the memory buffer based on the process ID includes: Based on the process id, get the corresponding process orchestration information from the FlowBus memory buffer.

3. A stateless process engine breakpoint resumption method according to claim 1, characterized in that: In response to the breakpoint resume request, the access detector technology is used to obtain the step set of the executed task node from the technical context information, and judge whether the current task node has been executed according to the label id of the current task node to identify whether the current task node is a breakpoint. If the current task node is not executed or fails to execute, it is executed by the LiteFlow process engine and the record of the failed execution is removed. If the current task node has been executed, the re-process execution step is no longer performed, including: In response to a breakpoint resume request, the access detector is called to obtain the step set of the executed task node from the technical context information, and it is determined whether the label id of the current task node exists in the step set of the executed task node to identify whether the current task node is a breakpoint. If not, the current task node is identified as a breakpoint and the current task node is not executed. The process of the current task node is executed through the LiteFlow process engine. If it exists, it is determined whether the current task node has been executed successfully. If the execution has been successfully executed, the process execution step will no longer be performed again. If the execution fails, the process of the current task node is re-executed through the LiteFlow process engine, and the record of the failed execution of the current task node is deleted from the technical context information.

4. A stateless process engine breakpoint resumption method according to claim 1, characterized in that: After the current task node is executed, the post-processor technology is used to assemble the execution information of the current task node, and the execution information is stored in the technical context information, including: After the current task node is executed, the postprocessor is called to assemble the execution information of the current task node, the execution information including the running status and execution result of the current task node, and the execution information is stored in the technical context information.

5. A stateless process engine breakpoint resumption method according to claim 4, characterized in that: The technical context information is used to store key information during the process execution, including the step set of the executed task node, the running status of each task node and the corresponding execution result.

6. A stateless process engine breakpoint resumption method according to claim 1, characterized in that: After the process execution is completed, the technical context information and the request unique ID of the current breakpoint resume request are synchronously stored in the non-relational database and the relational database, and the cache expiration time of the technical context information in the non-relational database is formulated, including: The technical context information and the unique request ID of the current breakpoint resume request are stored in a non-relational database, and a cache expiration time of the corresponding technical context information is set in the non-relational database; and the technical context information and the unique request ID of the current breakpoint resume request are synchronously stored in a relational database.

7. A stateless process engine breakpoint resumption method according to claim 6, characterized in that: The non-relational database is a Redis database, and the relational database is a MySQL database.

8. A stateless process engine breakpoint resumption system, characterized in that: include: The first data acquisition module is used to obtain the unique request ID and process ID of the current breakpoint resume request according to the breakpoint resume requirement; A second data acquisition module is used to acquire corresponding process scheduling information from the memory buffer based on the process ID; A third data acquisition module is used to inspect the corresponding technical context information in the non-relational database based on the request unique ID and process ID of the current breakpoint resume request, and if the corresponding technical context information exists in the non-relational database, identify the corresponding technical context information; if the corresponding technical context information does not exist in the non-relational database, identify the corresponding technical context information from the relational database; The breakpoint-resume request module is used to initiate a breakpoint-resume request and resume the process execution steps based on the process orchestration information and technical context information; The admission detector calling module is used to respond to the breakpoint resumption request, use the admission detector technology to obtain the step set of the executed task node from the technical context information, and judge whether the current task node has been executed according to the label id of the current task node to identify whether the current task node is a breakpoint. If the current task node is not executed or fails to execute, the process of the current task node is executed through the LiteFlow process engine and the record of execution failure is removed. If the current task node has been executed successfully, the process execution step will not be repeated; The post-processor calling module is used to assemble the execution information of the current task node by using the post-processor technology after the current task node is executed, and store the execution information in the technical context information; The storage module is used to synchronously store the technical context information and the request unique ID of the current breakpoint resume request in the non-relational database and the relational database after the process execution is completed, and to set the cache expiration time of the technical context information in the non-relational database.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images