Method, apparatus and device for handling pre - plan node failures

Abstract

The present application provides a method, apparatus and device for handling pre-plan node failures, which relates to the field of network security technology. A pre-plan process operation interface is provided by a terminal device, and a plurality of nodes of the pre-plan process are included on the pre-plan process operation interface. The method includes: when there is an operation failure at a first node of the pre-plan process, a failure interface corresponding to the first node is displayed on the pre-plan process operation interface, and failure information of the first node is included on the failure interface; in response to a touch operation on the failure interface, a target handling operation corresponding to the first node is determined; and the target handling operation is executed, where the target handling operation includes one of an abnormal termination operation, a node restart operation, and a node jump operation. The flexibility and efficiency of the failure handling solution for the pre-plan process are improved.

Description

Technical Field

[0001] This application relates to the field of network security technology, and particularly to a method, device and equipment for handling faults of pre - plan nodes. Background Art

[0002] In network security, there are different types of events, such as emergencies, known events, notified events, public opinion events, etc. Among them, emergencies refer to some unpredictable new events, which usually require urgent handling after they occur. Public opinion events are the pre - processing of known events to prevent such events from occurring again during some important activities. Notified events are event handling such as making notifications or setting deadlines for rectification after manual determination of the data obtained by the joint analysis engine.

[0003] In the situation awareness security command platform, for the handling of the above - mentioned types of events, corresponding pre - plans can be cited. During the operation of the cited pre - plan, the execution of multiple nodes is included. In the current pre - plan citation process, when a fault occurs in the operation of a certain node, there is no controllable and operable function for the exceptions that occur in the middle, and only the operation process of the pre - plan can be restarted. The flexibility and efficiency of the fault handling scheme of the above - mentioned pre - plan are relatively low. Summary of the Invention

[0004] This application provides a method, device and equipment for handling faults of pre - plan nodes to improve the flexibility and efficiency of the fault handling scheme of the pre - plan process.

[0005] In a first aspect, this application provides a method for handling faults of pre - plan nodes. A pre - plan process operation interface is provided through a terminal device, and a plurality of nodes of the pre - plan process are included on the pre - plan process operation interface. The method includes:

[0006] When a running fault exists in the first node of the pre - plan process, a fault interface corresponding to the first node is displayed on the pre - plan process operation interface, and the fault information of the first node is included on the fault interface;

[0007] In response to a touch operation on the fault interface, a target handling operation corresponding to the first node is determined;

[0008] The target handling operation is executed, where the target handling operation includes one of an abnormal termination operation, a node restart operation, and a node jump operation.

[0009] In a possible implementation manner, the displaying the fault interface corresponding to the first node on the pre - plan process operation interface includes:

[0010] Obtaining at least one of the exception type, exception content, and business direction of the first node;

[0011] Display the fault interface on the pre - plan process running interface according to at least one of the abnormal type, the abnormal content, and the business direction.

[0012] In a possible implementation manner, the fault interface includes a disposal option area and a determination control. The disposal option area includes at least one disposal option. Responding to a touch operation on the fault interface to determine the target disposal operation corresponding to the first node includes:

[0013] Respond to a touch operation on the disposal option area to determine a target disposal option among the at least one disposal option;

[0014] Respond to a touch operation on the determination control and determine the target disposal operation according to the target disposal option.

[0015] In a possible implementation manner, the target disposal option is an abnormal termination option. Executing the target disposal operation includes:

[0016] Determine the associated process of the pre - plan process. The associated process is a process that has a nested relationship with the pre - plan process;

[0017] Terminate the operation of the pre - plan process and the associated process;

[0018] Update the status of the pre - plan process and the associated process to the end status.

[0019] In a possible implementation manner, the target disposal option is a node restart option. Executing the target disposal operation includes:

[0020] Determine the first execution condition for restarting the first node. The first execution condition includes: the second execution condition for ending the fault interface and the input parameters for restarting the first node;

[0021] Display the first parameter input interface of the first node;

[0022] Respond to an input operation on the first parameter input interface to obtain the input parameters for restarting the first node;

[0023] Generate the first execution condition according to the second execution condition and the input parameters for restarting the first node;

[0024] Restart the first node according to the first execution condition.

[0025] In a possible implementation manner, the target disposal option is a jump option. Executing the target disposal operation includes:

[0026] In response to a touch operation on a second node among the multiple nodes, display a second parameter input interface of the second node, where the second node is the node to which the pre - plan process needs to jump from the first node;

[0027] In response to an input operation on the second parameter input interface, obtain the input parameters of the second node;

[0028] According to the input parameters of the second node, start running the second node so that the pre - plan process jumps from the first node to the second node.

[0029] In a possible implementation manner, the method further includes:

[0030] Display the cause of the failure of the first node on the failure interface;

[0031] And / or,

[0032] When performing the target handling operation, forcibly close the failure interface corresponding to the first node and terminate the operation of the first node.

[0033] In a second aspect, the present application provides a pre - plan node failure handling device. A pre - plan process operation interface is provided through a terminal device, and multiple nodes of the pre - plan process are included on the pre - plan process operation interface. The device includes:

[0034] A display module, configured to display a failure interface corresponding to the first node on the pre - plan process operation interface when there is a running failure in the first node of the pre - plan process, where the failure interface includes the failure information of the first node;

[0035] A determination module, configured to determine a target handling operation corresponding to the first node in response to a touch operation on the failure interface;

[0036] A processing module, configured to execute the target handling operation, where the target handling operation includes one of an abnormal termination operation, a node restart operation, and a node jump operation.

[0037] In a possible implementation manner, the display module is specifically configured to:

[0038] Obtain at least one of the abnormal type, abnormal content, and service direction of the first node;

[0039] According to at least one of the abnormal type, the abnormal content, and the service direction, display the failure interface on the pre - plan process operation interface.

[0040] In a possible implementation, the fault interface includes a disposal option area and a confirmation control. The disposal option area includes at least one disposal option. The confirmation module is specifically configured to:

[0041] In response to a touch operation on the disposal option area, determine a target disposal option from the at least one disposal option;

[0042] In response to a touch operation on the confirmation control, determine the target disposal operation according to the target disposal option.

[0043] In a possible implementation, the target disposal option is an abnormal termination option. The processing module is specifically configured to:

[0044] Determine the associated process of the pre - plan process, where the associated process is a process having a nested relationship with the pre - plan process;

[0045] Terminate the operation of the pre - plan process and the associated process;

[0046] Update the status of the pre - plan process and the associated process to the end status.

[0047] In a possible implementation, the target disposal option is a node restart option. The processing module is specifically configured to:

[0048] Determine the first execution condition for restarting the first node, where the first execution condition includes: the second execution condition for ending the fault interface and the input parameters for restarting the first node;

[0049] Display the first parameter input interface of the first node;

[0050] In response to an input operation on the first parameter input interface, obtain the input parameters for restarting the first node;

[0051] Generate the first execution condition according to the second execution condition and the input parameters for restarting the first node;

[0052] Restart the first node according to the first execution condition.

[0053] In a possible implementation, the target disposal option is a jump option. The processing module is specifically configured to:

[0054] In response to a touch operation on the second node among the multiple nodes, display the second parameter input interface of the second node, where the second node is the node that the pre - plan process needs to jump to from the first node;

[0055] In response to an input operation on the second parameter input interface, obtain the input parameters of the second node;

[0056] According to the input parameters of the second node, start running the second node, so that the pre - plan process jumps from the first node to the second node.

[0057] In a possible implementation manner, the display module is further configured to:

[0058] Display the fault cause of the first node on the fault interface.

[0059] In a third aspect, the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, it implements the pre - plan node fault handling method according to any one of the first aspects.

[0060] In a fourth aspect, the present application provides a computer - readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the pre - plan node fault handling method according to any one of the first aspects.

[0061] In a fifth aspect, the present application provides a computer program product, including a computer program. When the computer program is executed by a processor, it implements the pre - plan node fault handling method according to any one of the first aspects.

[0062] The pre - plan node fault handling method, device, and equipment provided by the embodiments of the present application provide a pre - plan process operation interface through a terminal device. The pre - plan process operation interface includes multiple nodes of the pre - plan process. When there is a running fault in the first node of the pre - plan process, first display the fault interface corresponding to the first node on the pre - plan process operation interface. The fault interface includes the fault information of the first node. Then, in response to a touch operation on the fault interface, determine the target handling operation corresponding to the first node, so that the target handling operation can be executed to solve the running fault of the first node. The solution of the embodiments of the present application can effectively and intuitively view the running conditions of each node of the pre - plan process through the pre - plan process operation interface. At the same time, through the fault interface, the fault handling operation of the first node is provided. When there is a running fault in the first node, the target handling operation can be executed through the interaction with the fault interface to solve the fault, realizing the visualization of the user operation interface and the controllable and operable processing of node faults. The target handling operation includes one of an abnormal termination operation, a node restart operation, and a node jump operation. Therefore, it is not necessary to restart the entire running process of the pre - plan process each time, improving the flexibility and efficiency of the fault handling of the pre - plan process. Description of the Drawings

[0063] To more clearly illustrate the technical solutions in the present application or the prior art, the following will briefly introduce the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other accompanying drawings can also be obtained based on these drawings.

[0064] Figure 1 It is a schematic diagram of a pre - plan process provided by an embodiment of the present application;

[0065] Figure 2 It is a schematic diagram of the process of the pre - plan node fault handling method provided by an embodiment of the present application;

[0066] Figure 3 It is a schematic diagram of the pre - plan process operation interface provided by an embodiment of the present application;

[0067] Figure 4 It is a schematic diagram of the process of displaying a fault interface provided by an embodiment of the present application;

[0068] Figure 5 It is a schematic diagram of the fault interface provided by an embodiment of the present application;

[0069] Figure 6 It is the operation schematic of the fault interface provided by an embodiment of the present application Figure 1 ;

[0070] Figure 7 It is the operation schematic of the fault interface provided by an embodiment of the present application Figure 2 ;

[0071] Figure 8 It is the operation schematic of the fault interface provided by an embodiment of the present application Figure 3 ;

[0072] Figure 9 It is a schematic diagram of the structure of the pre - plan node fault handling device provided by an embodiment of the present application;

[0073] Figure 10 It is a schematic diagram of the physical structure of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0074] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts fall within the scope of protection of the present application.

[0075] Through different business modules, by referring to the pre-plan process, it is possible to achieve process-based office for various security tasks. The pre-plan process usually includes multiple task nodes, which are connected in an orderly manner.

[0076] Figure 1 This is a schematic diagram of a pre-plan process provided for an embodiment of the present application. As Figure 1 shown, the multiple task nodes in the pre-plan process include a start node, a manual judgment node, an emergency duty node, an expert team node, and an end node.

[0077] The various task nodes are connected in an orderly manner. The start node can be used to input parameters, and then the manual judgment node judges the input parameters, and its outputs are respectively input to the emergency duty node and the expert team node. The emergency duty node and the expert team node process in parallel, and finally input to the end node as the output of the pre-plan process.

[0078] The reference to the pre-plan process depends on the normal operation of each task node in the pre-plan process. However, in practice, there may be situations where some task nodes in the pre-plan process fail or operate abnormally, affecting the pre-plan process.

[0079] In the current reference to the pre-plan process, only the pre-plan process can be normally circulated, and the intermediate process is not controllable and operable. Therefore, usually, the pre-plan process can only be restarted, making the original pre-plan process only shelved and abandoned. This fault handling method has low flexibility and efficiency and is relatively inconvenient to operate.

[0080] Furthermore, since the background does not capture and retain abnormal data, problems occur in the operating environment, and visualization is not achieved on the user operation interface, and the user has a blind spot for abnormalities at the operation node. When the user does not know that there are abnormalities in the current environment and performs multiple operations without response, it will increase the pressure on the background server.

[0081] Based on this, the present application provides a pre-plan node fault handling solution. By capturing logical exceptions and business exceptions in the pre-plan process, and then providing corresponding handling operations, timely troubleshooting of faults and promoting the rapid circulation of the pre-plan process are carried out to improve the flexibility and efficiency of fault handling in the pre-plan process. The following combines Figure 2 to introduce the solution of the present application.

[0082] Figure 2 This is a schematic flowchart of the pre-plan node fault handling method provided for an embodiment of the present application. This method provides a pre-plan process operation interface through a terminal device. The pre-plan process operation interface includes multiple nodes of the pre-plan process. As Figure 2 shown, this method may include:

[0083] S21. When there is an operation failure at the first node of the pre - plan process, a fault interface corresponding to the first node is displayed on the pre - plan process operation interface, and the fault information of the first node is included on the fault interface.

[0084] The pre - plan process includes multiple nodes, and the multiple nodes are connected in an orderly manner. In the present application, the multiple nodes in the pre - plan process and the connection relationship between the multiple nodes are all displayed on the pre - plan process operation interface. According to the pre - plan process operation interface, it can be observed which node the pre - plan process is running to and the operation status of the node.

[0085] The first node is any node among the multiple nodes of the pre - plan process. When the pre - plan process proceeds to the first node, the first node is the currently running node. When a failure occurs during the operation of the first node, a fault interface corresponding to the first node will be displayed on the pre - plan process operation interface. The fault interface indicates that a failure has occurred in the operation of the first node, and the fault information of the first node is included on the fault interface. For example, it may include the node name of the first node, it may include the fault prompt of the first node, it may include the possible fault causes of the first node, and so on.

[0086] S22. In response to a touch operation on the fault interface, determine the target handling operation corresponding to the first node.

[0087] Since the fault information of the first node is displayed on the fault interface, the user can perform a touch operation on the fault interface to determine the target handling operation corresponding to the first node. In the embodiments of the present application, the touch operation may be, for example, an operation where the user clicks on the screen of the terminal device with a finger, or may also be an operation where the user clicks on the fault interface by controlling devices such as a mouse and a keyboard.

[0088] Through the touch operation on the fault interface, the target handling operation corresponding to the first node can be determined, and the target handling operation is used to handle the operation failure that occurs at the first node.

[0089] S23. Execute the target handling operation, where the target handling operation includes one of an abnormal termination operation, a node restart operation, and a node jump operation.

[0090] After determining the target handling operation corresponding to the first node, the target handling operation can be executed. In the embodiments of the present application, the target handling operation includes one of an abnormal termination operation, a node restart operation, and a node jump operation.

[0091] Among them, the abnormal termination operation is to terminate the entire current pre - plan process, that is, to end the operation of the pre - plan process; the node restart operation is an operation to re - activate and run the current first node after eliminating the abnormality; the node jump operation is an operation to skip the current first node and enter the next node to continue running.

[0092] The method for handling faults of plan nodes provided in the embodiment of the present application provides a plan process operation interface through a terminal device, and the plan process operation interface includes multiple nodes of the plan process. When there is a running fault in the first node of the plan process, the fault interface corresponding to the first node is first displayed on the plan process operation interface, and the fault interface includes the fault information of the first node; then in response to the touch operation on the fault interface, the target disposal operation corresponding to the first node is determined, so that the target disposal operation can be executed to solve the running fault of the first node. The scheme of the embodiment of the present application can effectively and intuitively view the running status of each node of the plan process through the plan process operation interface, and at the same time, the fault disposal operation of the first node is provided through the fault interface. When there is a running fault in the first node, the target disposal operation can be executed to solve the fault by interacting with the fault interface, realizing the visualization of the user operation interface and the controllable and operable processing of the node fault, wherein the target disposal operation includes one of the abnormal termination operation, the node restart operation, and the node jump operation, so there is no need to re-initiate the entire running process of the plan process every time, which improves the flexibility and efficiency of the fault handling of the plan process.

[0093] The solution of the embodiment of the present application aims at emergency response to sudden incidents and support processing for important activities. After referencing the preset plan process, it can promptly handle the abnormality of the current execution means (i.e., the node operation failure of the plan process) to ensure the correct execution and maintainability of the plan process. On the other hand, when integrating different categories of measures, certain fields that are required for interaction are verified. In the case of multi-means circulation and multi-platform collaboration, in order to ensure the correctness of the circulation of each means, the server monitors the current means operation status, captures the exception when the conditions are not met, throws the means exception in a visual form, and provides corresponding compensation measures.

[0094] Users can handle the problem by completing necessary parameters, modifying corresponding measures configuration, and checking environmental factors, etc., combined with the compensation mechanism. The compensation mechanism includes three solutions: abnormal termination, restarting the current node, and jumping to the subsequent adjacent node. It ensures that when dealing with node failures, the process is flexibly handled and interactive, ensuring that the plan process can run smoothly without blocking. It changes the situation where the plan can only be modified and the process can be re-initiated after the original exception, improves office efficiency, reduces redundant office processes, and fully reflects the efficiency, simplicity and correctness of event tasks. Based on the above embodiments, the scheme of this application is introduced in detail below in conjunction with the accompanying drawings.

[0095] Figure 3 A schematic diagram of the plan process operation interface provided in the embodiment of the present application, such as Figure 3As shown in the figure, the operation interface 30 of the pre-plan process includes multiple nodes of the pre-plan process, namely, the start node, the manual judgment node, the emergency duty node, the expert team node, and the end node.

[0096] Timely handling of node operation failures in the pre-plan process can ensure the correctness and maintainability of the pre-plan process. Among them, the handling of failures is based on the capture of failures and the display to users through a visual interface. For example, in Figure 3 if the manual judgment node fails, the failure needs to be captured and presented to the user for processing. The following will introduce this process in combination with Figure 4 this.

[0097] Figure 4 is a schematic flowchart of the process for displaying a failure interface provided by an embodiment of the present application. As Figure 4 shown, it includes:

[0098] S41, obtaining at least one of the exception type, exception content, and service direction of the first node.

[0099] During the execution of the pre-plan process, the terminal device adopts the observer mode to monitor each node of the pre-plan process. When there is an operation failure in the first node, the terminal device obtains at least one of the exception type, exception content, and service direction of the first node.

[0100] Among them, the exception type refers to the failure type of the first node. For example, an operation failure caused by insufficient permissions, an operation failure caused by missing necessary parameters, and so on. The exception content corresponds to the exception type and is the specific information of the failure. For example, when the exception type is insufficient permissions, the exception content may include the specific permissions of the first node and the permissions required to run the first node; when the exception type is missing necessary parameters, the exception content may include the parameters necessary for the operation of the first node, and so on. The service direction may include the connection relationship between the first node and other nodes, etc.

[0101] S42, displaying a failure interface on the operation interface of the pre-plan process according to at least one of the exception type, exception content, and service direction.

[0102] After obtaining at least one of the exception type, exception content, and business direction of the first node, a fault interface can be displayed on the pre - plan process running interface according to at least one of the exception type, exception content, and business direction. In some embodiments, the fault reason of the first node and corresponding handling options are also displayed on the fault interface, where the handling options correspond to specific handling operations. In some embodiments, the terminal device forcibly closes the fault interface corresponding to the first node and terminates the operation of the first node. The operation of forcibly closing the fault interface and terminating the operation of the first node can be synchronized with the execution of the target handling operation or can be performed after the execution of the target handling operation.

[0103] Figure 5 is a schematic diagram of the fault interface provided by an embodiment of the present application. As Figure 5 shown, when there is an operation fault in the artificial judgment node in the Figure 3 example, the fault interface 50 is displayed.

[0104] The fault reason of the artificial judgment node, that is, "necessary parameters are missing for the exception reason", is included on the fault interface 50. Through the fault reason displayed on the fault interface 50, the user can quickly know the cause of the operation fault of the artificial judgment node, so as to provide a reference for subsequent handling operations and more targeted selection of corresponding processing solutions.

[0105] The handling option area 51 and the confirmation control 52 are also included on the fault interface 50. At least one handling option is included in the handling option area 51. As Figure 5 shown, the at least one handling option may include an abnormal termination option, a node restart option, and a jump option.

[0106] After the handling option area is displayed on the fault interface 50, the user can select the corresponding handling option through a touch operation. The terminal device determines the target handling option among the at least one handling option in response to the touch operation on the handling option area. After determining the target handling option, the corresponding operation can be triggered through the confirmation control 52, that is, the terminal device determines the target handling operation according to the target handling option in response to the touch operation on the confirmation control 52, and then triggers the execution of the target handling operation.

[0107] The following will separately introduce the execution processes of the handling operations corresponding to different handling options in combination with Figures 6 - 8 .

[0108] Figure 6 is an operation schematic diagram of the fault interface provided by an embodiment of the present application Figure 1 As Figure 6As shown, the fault interface 60 corresponding to the first node is displayed. The reason for the operation fault of the first node is incorrect user task configuration. At this time, the entire plan process needs to be terminated. It should be noted that incorrect user task configuration is only one possible factor leading to the need to terminate the plan process, and other factors that may lead to the need to terminate the plan process may also be included, such as the plan process does not need to be executed, and so on.

[0109] Therefore, the abnormal termination option can be selected in the disposal option area of the fault interface 60, and the confirmation control on the fault interface 60 can be clicked. In response to the touch operation on the confirmation control, the terminal device determines that the target disposal operation for the first node is the abnormal termination operation. Then, the terminal device determines whether there is an associated process nested with the plan process. Here, the associated process being nested with the plan process means that the plan process is a part of the associated process. The terminal device terminates the running plan process and updates the status of the plan process to the end status. Further, if there is an associated process of the plan process, the terminal device will also terminate the running associated process and update the status of the associated process to the end status.

[0110] As Figure 6 shown, an example shows multiple nodes included in the entire plan process and the ordered connection relationships between the nodes (including the first node, the second node, and the third node). When a running fault occurs in the first node, since the target disposal operation for the first node is the abnormal termination operation, the corresponding abnormal handling means is to terminate the running plan process. After the process is terminated, the plan process can also be deleted to release storage space.

[0111] For example, the termination of the plan process can be achieved by calling the camunda workflow engine. Through the camunda workflow engine, first stop running the first node (i.e., the currently running node with a fault), and end the entire plan process. The nested processes or stages (i.e., associated processes) are also ended together to complete the termination operations of the plan process and the associated process, so as to ensure that the underlying tasks of the plan process and the associated process no longer occupy additional storage space in the task list. At the same time, the business status of the first node can also be synchronized to the end status.

[0112] Combined with Figure 6 the embodiments, it can be seen that the solution of the embodiments of the present application, when a fault occurs in the first node, for incorrect user task configuration or a plan process that does not need to be continued, can terminate the entire plan process and the corresponding associated process through the abnormal termination option to end the current plan process and associated process. On the one hand, it can avoid wasting server resources caused by continuously re-executing the plan process or the associated process, and on the other hand, it can also effectively control the faults caused by such uncontrollable factors.

[0113] Figure 7 Schematic diagram of fault interface operation provided by the embodiment of this application Figure 2 As shown Figure 7 in, on the fault interface 70 corresponding to the first node, the operation fault of the first node is displayed.

[0114] Therefore, the node restart option can be selected in the disposal option area of the fault interface 70, and the confirmation control on the fault interface 70 can be clicked. In response to the touch operation on the confirmation control, the terminal device determines that the target disposal operation for the first node is the node restart operation. Then, the terminal device determines the first execution condition for restarting the first node, where the first execution condition includes: ending the second execution condition of the fault interface 70 and the input parameters for restarting the first node. Only when the second execution condition is met can the fault interface 70 be ended. For different fault causes, the corresponding second execution conditions may be different. For example, when the fault cause of the first node is insufficient permissions, the second execution condition is that the corresponding permissions need to be opened.

[0115] After determining the first execution condition, the first parameter input interface of the first node is displayed, and the user can input the corresponding parameters on the first parameter input interface. In response to the input operation on the first parameter input interface, the terminal device obtains the input parameters for restarting the first node.

[0116] After obtaining the input parameters for restarting the first node, the first execution condition can be generated according to the second execution condition and the input parameters for restarting the first node, and the first node is restarted according to the first execution condition. As Figure 7 shown, it exemplifies the multiple nodes included in the entire plan process and the ordered connection relationships between the nodes (including the first node, the second node, and the third node). When there is an operation fault in the first node, since the target disposal operation for the first node is the node restart operation, the corresponding exception handling method is to restart the first node. After generating the first execution condition, the first node is restarted according to the first execution condition, the process state is reactivated, and the means type is judged. For the means that need to be automatically executed, the necessary parameters need to be supplemented before continuing to initiate the process. When the first node is restarted, the subsequent running process in the plan process can continue to run based on the first node.

[0117] Combined with Figure 7 the embodiment, it can be seen that the solution of the embodiment of this application, when there is a fault in the first node, for the faults caused by controllable factors, after means such as modifying the corresponding configuration parameters and eliminating environmental factors, the entire plan process can be reactivated by restarting the first node, so that the entire plan process can continue to run normally without having to re-run the entire process because of such controllable factors, reducing the repeated running of the nodes and also reducing the waste of server resources, and can also effectively control the faults caused by such controllable factors.

[0118] Figure 8 Schematic diagram of operation on the fault interface provided by the embodiment of the present application Figure 3 , as Figure 8 shown, on the fault interface 80 corresponding to the first node, it is shown that the first node has an operation fault, but the importance of the first node is relatively low.

[0119] Therefore, the jump option can be selected in the handling option area of the fault interface 80, and the confirmation control on the fault interface 80 can be clicked. In response to the touch operation on the confirmation control, the terminal device determines that the target handling operation for the first node is the node jump operation.

[0120] As Figure 8 shown in, it exemplifies multiple nodes included in the entire pre - plan process and the ordered connection relationship between each node (including the first node, the second node, and the third node). When there is an operation fault in the first node, since the target handling operation for the first node is the node jump operation, the corresponding exception handling means is the node jump operation.

[0121] When node jump is selected, the next node needs to be selected through the page. Since multiple nodes of the pre - plan process are shown on the operation interface of the pre - plan process, the next node can be selected through the interaction operation with the operation interface of the pre - plan process.

[0122] For example, a certain node in the operation interface of the pre - plan process can be clicked as the next node (i.e., the second node). In response to the touch operation on the second node, the terminal device determines the node that the pre - plan process needs to jump from the first node to, and then displays the second parameter input interface for the second node, and the second parameter input interface is used for inputting parameters of the second node.

[0123] Since Figure 8 the exemplified handling operation is to jump from the first node to the second node, the second node has no input parameters, and the output parameters after the end of the previous node need to be supplemented as the input parameters of the second node. After inputting the input parameters of the second node, the terminal device, in response to the input operation on the second parameter input interface, obtains the input parameters of the second node, and starts to run the second node according to the input parameters of the second node, so that the pre - plan process jumps from the first node to the second node.

[0124] For example, the camunda underlying engine can be called to handle the process jump service, and operations such as parameter verification of node flow transfer and business status update in the business layer can be controlled to ensure that the normal operation of the subsequent nodes is not affected after jumping to the node. Functionally, simulate the actions of the means and measures to normally end the first node, and achieve seamless jump.

[0125] Combined with Figure 8As can be seen from the embodiments, in the solution of the embodiments of the present application, when a failure occurs in the first node, for nodes with relatively low importance or nodes that have been executed but not successfully recorded, the node jump option can skip the first node that appears and continue to execute the subsequent nodes, so that the entire pre-plan process can continue to run normally without having to re-run the entire process due to such controllable factors, reducing the repeated operation of nodes, reducing the waste of server resources, and effectively controlling the failures caused by such controllable factors.

[0126] In summary, the solution of the embodiments of the present application provides a pre-plan process operation interface through a terminal device. The pre-plan process operation interface includes multiple nodes of the pre-plan process. By capturing the operation status of each node of the pre-plan process, the visual monitoring of the health status of the pre-plan process is realized and presented through the pre-plan process operation interface, which has a certain promoting effect on improving the discovery and handling of node failures. At the same time, this visual interface provides the cumbersome console logs to the user in a visual interactive form, reducing the cumbersome degree for the user to handle failures. When a running failure occurs in the first node of the pre-plan process, first, a failure interface corresponding to the first node is displayed on the pre-plan process operation interface, and the failure information of the first node is included on the failure interface; then, in response to a touch operation on the failure interface, a target handling operation corresponding to the first node is determined, and thus the target handling operation can be executed to solve the running failure of the first node. Different handling options are also provided for failures caused by different factors, making the handling of failures more convenient without the need for the user to view the logs tediously to troubleshoot the failure situation. For example, for failures caused by uncontrollable factors, an abnormal termination option is provided to terminate the entire pre-plan process and the corresponding associated processes, avoiding the waste of server resources caused by continuously re-executing the pre-plan process or associated processes; for failures caused by controllable factors, a node restart option is provided to reactivate the first node; for nodes of types such as low importance, a jump option is provided to skip the failed first node, so that the entire pre-plan process can continue to run normally. Therefore, the flexibility and efficiency of the failure handling of the pre-plan process are improved, and in terms of resource allocation, the running space and storage space are saved, the storage of abnormal redundant data on the server side is reduced, and the resources occupied by hanging tasks on the server side are reduced.

[0127] Figure 9 The following is a schematic structural diagram of a pre-plan node failure handling device provided by the embodiments of the present application. A pre-plan process operation interface is provided through a terminal device. The pre-plan process operation interface includes multiple nodes of the pre-plan process, as Figure 9 shown. The device includes:

[0128] A display module 91, configured to display a fault interface corresponding to the first node on the operation interface of the contingency plan process when a running fault occurs at the first node of the contingency plan process, where the fault interface includes fault information of the first node;

[0129] A determination module 92, configured to determine a target handling operation corresponding to the first node in response to a touch operation on the fault interface;

[0130] A processing module 93, configured to execute the target handling operation, where the target handling operation includes one of an abnormal termination operation, a node restart operation, and a node jump operation.

[0131] In a possible implementation manner, the display module 91 is specifically configured to:

[0132] Obtain at least one of the abnormal type, abnormal content, and service direction of the first node;

[0133] Display the fault interface on the operation interface of the contingency plan process according to at least one of the abnormal type, the abnormal content, and the service direction.

[0134] In a possible implementation manner, the fault interface includes a handling option area and a determination control, and the handling option area includes at least one handling option; the determination module 92 is specifically configured to:

[0135] Determine a target handling option from the at least one handling option in response to a touch operation on the handling option area;

[0136] Determine the target handling operation according to the target handling option in response to a touch operation on the determination control.

[0137] In a possible implementation manner, the target handling option is an abnormal termination option; the processing module 93 is specifically configured to:

[0138] Determine an associated process of the contingency plan process, where the associated process is a process having a nested relationship with the contingency plan process;

[0139] Terminate the operation of the contingency plan process and the associated process;

[0140] Update the statuses of the contingency plan process and the associated process to an end status.

[0141] In a possible implementation manner, the target handling option is a node restart option; the processing module 93 is specifically configured to:

[0142] Determine a first execution condition for restarting the first node, where the first execution condition includes: an end second execution condition for the fault interface and input parameters for restarting the first node;

[0143] Display a first parameter input interface for the first node;

[0144] In response to an input operation on the first parameter input interface, obtain input parameters for restarting the first node;

[0145] Generate the first execution condition according to the second execution condition and the input parameters for restarting the first node;

[0146] Restart the first node according to the first execution condition.

[0147] In a possible implementation manner, the target handling option is a jump option; the processing module 93 is specifically configured to:

[0148] In response to a touch operation on a second node among the multiple nodes, display a second parameter input interface for the second node, where the second node is the node that the pre - plan process needs to jump to from the first node;

[0149] In response to an input operation on the second parameter input interface, obtain input parameters for the second node;

[0150] Start running the second node according to the input parameters of the second node, so that the pre - plan process jumps from the first node to the second node.

[0151] In a possible implementation manner, the display module 91 is further configured to:

[0152] Display the fault cause of the first node on the fault interface;

[0153] And / or,

[0154] When performing the target handling operation, forcibly close the fault interface corresponding to the first node and terminate the operation of the first node.

[0155] The pre - plan node fault handling device provided by the embodiments of the present application is used to execute the above - mentioned method embodiments, and its implementation principle and technical effects are similar, which will not be elaborated here in this embodiment.

[0156] Figure 10 Illustrates a schematic physical structure diagram of an electronic device, as Figure 10As shown in the figure, the electronic device may include: a processor 1010, a communications interface 1020, a memory 1030, and a communication bus 1040. Among them, the processor 1010, the communications interface 1020, and the memory 1030 communicate with each other through the communication bus 1040. The processor 1010 may call the logical instructions in the memory 1030 to execute the method for handling the failure of the pre-plan node, and provide a running interface for the pre-plan process through the terminal device. The running interface of the pre-plan process includes multiple nodes of the pre-plan process. The method includes: when there is a running failure in the first node of the pre-plan process, displaying a failure interface corresponding to the first node on the running interface of the pre-plan process, and the failure information of the first node is included on the failure interface; in response to a touch operation on the failure interface, determining a target handling operation corresponding to the first node; and executing the target handling operation, where the target handling operation includes one of an abnormal termination operation, a node restart operation, and a node jump operation.

[0157] In addition, when the logical instructions in the above-mentioned memory 1030 can be implemented in the form of a software functional unit and sold or used as an independent product, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: various media such as a USB flash drive, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc that can store program codes.

[0158] On the other hand, the present invention also provides a computer program product, which includes a computer program. The computer program can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the pre-plan node fault handling method provided by the above-mentioned various methods, and provide a pre-plan process operation interface through a terminal device. The pre-plan process operation interface includes multiple nodes of the pre-plan process. The method includes: when there is an operation fault in the first node of the pre-plan process, displaying a fault interface corresponding to the first node on the pre-plan process operation interface, where the fault interface includes the fault information of the first node; in response to a touch operation on the fault interface, determining a target handling operation corresponding to the first node; and executing the target handling operation, where the target handling operation includes one of an abnormal termination operation, a node restart operation, and a node jump operation.

[0159] In another aspect, the present invention also provides a non-transitory computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it is implemented to execute the pre-plan node fault handling method provided by the above-mentioned various methods, and provide a pre-plan process operation interface through a terminal device. The pre-plan process operation interface includes multiple nodes of the pre-plan process. The method includes: when there is an operation fault in the first node of the pre-plan process, displaying a fault interface corresponding to the first node on the pre-plan process operation interface, where the fault interface includes the fault information of the first node; in response to a touch operation on the fault interface, determining a target handling operation corresponding to the first node; and executing the target handling operation, where the target handling operation includes one of an abnormal termination operation, a node restart operation, and a node jump operation.

[0160] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without creative labor.

[0161] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on such an understanding, the essence of the above technical solution, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0162] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for processing a pre - plan node failure, characterized in that, Provide an operation interface for the pre - plan process through a terminal device. The operation interface for the pre - plan process includes multiple nodes of the pre - plan process. The method includes: When there is an operation failure at the first node of the pre - plan process, display a failure interface corresponding to the first node on the operation interface for the pre - plan process. The failure interface includes the failure information of the first node; In response to a touch operation on the failure interface, determine the target handling operation corresponding to the first node; Execute the target handling operation, where the target handling operation includes one of an abnormal termination operation, a node restart operation, and a node jump operation.

2. The method according to claim 1, characterized in that, The step of displaying the failure interface corresponding to the first node on the operation interface for the pre - plan process includes: Obtain at least one of the abnormal type, abnormal content, and business direction of the first node; According to at least one of the abnormal type, the abnormal content, and the business direction, display the failure interface on the operation interface for the pre - plan process.

3. The method according to claim 1 or 2, characterized in that, The failure interface includes a handling option area and a confirmation control. The handling option area includes at least one handling option; The step of, in response to a touch operation on the failure interface, determining the target handling operation corresponding to the first node includes: In response to a touch operation on the handling option area, determine a target handling option among the at least one handling option; In response to a touch operation on the confirmation control, determine the target handling operation according to the target handling option.

4. The method according to claim 3, characterized in that, The target handling option is an abnormal termination option; The step of executing the target handling operation includes: Determine the associated process of the pre - plan process. The associated process is a process that has a nested relationship with the pre - plan process; Terminate the operation of the pre - plan process and the associated process; Update the status of the pre - plan process and the associated process to an end status.

5. The method according to claim 3, characterized in that, The target handling option is a node restart option; The step of executing the target handling operation includes: Determine the first execution condition for restarting the first node. The first execution condition includes: the second execution condition for ending the failure interface and the input parameters for restarting the first node; Display the first parameter input interface of the first node; In response to an input operation on the first parameter input interface, obtain the input parameters for restarting the first node; Generate the first execution condition according to the second execution condition and the input parameters for restarting the first node; Restart the first node according to the first execution condition.

6. The method according to claim 3, characterized in that, The target handling option is a jump option. The step of executing the target handling operation includes: In response to a touch operation on the second node among the multiple nodes, display the second parameter input interface of the second node. The second node is the node that the pre - plan process needs to jump to from the first node; In response to an input operation on the second parameter input interface, obtain the input parameters of the second node; Start the operation of the second node according to the input parameters of the second node, so that the pre - plan process jumps from the first node to the second node.

7. The method according to claim 1 or 2, characterized in that, The method further includes: Display the cause of the failure of the first node on the failure interface; and / or When performing the target handling operation, forcibly close the failure interface corresponding to the first node and terminate the operation of the first node.

8. A device for processing a pre - plan node failure, characterized in that, Provide a pre-plan process operation interface through a terminal device. The pre-plan process operation interface includes multiple nodes of the pre-plan process. The device includes: A display module, configured to display a failure interface corresponding to the first node on the pre-plan process operation interface when there is an operation failure in the first node of the pre-plan process. The failure interface includes the failure information of the first node; A determination module, configured to determine a target handling operation corresponding to the first node in response to a touch operation on the failure interface; A processing module, configured to execute the target handling operation, where the target handling operation includes one of an abnormal termination operation, a node restart operation, and a node jump operation.

9. An electronic device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein, When the processor executes the program, it implements the pre-plan node failure handling method according to any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, wherein, When the computer program is executed by a processor, it implements the pre-plan node failure handling method according to any one of claims 1-7.

11. A computer program product, comprising a computer program, wherein, When the computer program is executed by a processor, it implements the pre-plan node failure handling method according to any one of claims 1-7.

Images