Automatic operation and maintenance method, device, server and storage medium

Abstract

The present application relates to the field of network operation and maintenance, and in particular to an automatic operation and maintenance method, device, server and storage medium. The method includes: when determining that a task node group is a faulty node group, determining the average task volume of the faulty node group within a target time period, and determining whether the standby link meets the task execution requirements based on the average task volume and the benchmark task volume of the standby link carrying the task; if the standby link does not meet the task execution requirements, determining the transit node, and establishing a temporary communication link between the faulty node groups based on the transit node; based on the task type and / or task data in the task attributes, determining the target link of each target task from the standby link and the temporary communication link, and executing the target task based on the target link of each target task. The technical solution of the present application enables the corresponding data to be transmitted in a timely manner when a fault occurs.

Description

Technical Field

[0001] The present application relates to the field of network operation and maintenance, and in particular to an automatic operation and maintenance method, device, server and storage medium. Background Art

[0002] In the current airport business system, the amount of business data generated by airport sites is increasing, and the data transmission between each airport site and the data center is also very frequent. Under the large data load, various failures often occur in the communication network, such as data packet loss, communication link interruption and communication delay.

[0003] In the related art, the usual operation and maintenance method is to reversely and step by step troubleshoot the cause of the fault on the faulty node when a network system fails, or to determine the cause of the fault based on the experience of the operation and maintenance personnel. Since the efficiency of reverse step-by-step troubleshooting is low, and the judgment based on the experience of the operation and maintenance personnel is relatively subjective, the probability of error is also high. Therefore, in the related art, some worthless actions may be performed when troubleshooting and solving the fault, resulting in low efficiency in troubleshooting and solving the fault. In the related art, when troubleshooting and solving the fault, the corresponding data is suspended from transmission, which will affect the efficiency of the business system, and then cause the relevant data to not be transmitted in time.

[0004] Therefore, how to ensure that the corresponding data can be transmitted in time when a failure occurs is an urgent problem that needs to be solved. Summary of the invention

[0005] Based on this, it is necessary to provide an automatic operation and maintenance method, device, server and storage medium in which corresponding data can be transmitted in time when a failure occurs, in order to address the above technical problems.

[0006] In a first aspect, the present application provides an automatic operation and maintenance method, comprising:

[0007] When determining that the task node group is a fault node group, determining an average task amount of the fault node group within a target time period, the target time period being a time period before the fault event occurs, the task node group including an initiating node and a receiving node of the fault event;

[0008] Determining whether the backup link meets the task execution requirement based on the average task amount and the benchmark task amount of the task carried by the backup link;

[0009] If the backup link does not meet the task execution requirements, determine a transfer node, and establish a temporary communication link between the faulty node group based on the transfer node;

[0010] Based on the task type and / or task data in the task attributes of the target task, the target link of each target task is determined from the backup link and the temporary communication link, and the target task is executed based on the target link of each target task; the target task includes the tasks to be executed between the fault node groups, and the new task established based on the task attributes of the fault event, and the task attributes include the task type, the task data and the task node group composed of the initiating node and the receiving node.

[0011] In one embodiment, determining whether the task node group is a faulty node group includes:

[0012] Establishing a test task based on the task attribute of the fault event, wherein the fault event is a task characterized by a failed execution status;

[0013] A test task is executed between the task node groups of the fault event, and whether the task node group is a faulty node group is determined according to the test result, wherein the test result includes the transmission network speed and the execution status of each of the test tasks.

[0014] In one embodiment, the establishing of the test task based on the task attribute of the fault event includes:

[0015] Establishing a plurality of task templates based on the task node group of the fault event, and setting a task type for each of the task templates; wherein each of the task types corresponds to at least one of the task templates;

[0016] For each of the task types, test data is extracted from the test data lake based on the task type, and the test data is filled into the task template corresponding to the task type to obtain a test task.

[0017] In one of the embodiments, determining whether the task node group is a faulty node group according to the test result includes at least one of the following:

[0018] If the transmission network speed is less than the reference network speed, determining that the task node group is a faulty node group;

[0019] If it is determined that the execution success rate is less than a set threshold, the task node group is determined to be a faulty node group; wherein the execution success rate is the ratio of the number of the test tasks whose execution status is characterized as successful to the total number of the test tasks.

[0020] In one embodiment, determining the transfer node includes:

[0021] Determine a node whose number of tasks to be executed is less than a first threshold as a candidate node;

[0022] Determine the comprehensive transmission rate of each candidate node with the faulty node group, and determine the candidate node with the largest comprehensive transmission rate as the transit node, wherein the comprehensive transmission rate is the sum of the transmission rates of the candidate nodes with each node in the faulty node group.

[0023] In one embodiment, the method further comprises at least one of the following:

[0024] setting a threshold as a validity period, and setting a validity period for the temporary communication link;

[0025] A validity period is determined based on the number of the target tasks, and a validity period is set for the temporary communication link.

[0026] In one embodiment, the method further comprises:

[0027] Processing the task attribute of the fault event based on the fault analysis model to determine a first fault cause;

[0028] Determine an estimated fault cause based on the first fault cause and the test result, and match a solution strategy based on the estimated fault cause;

[0029] Generate an execution instruction based on the solution strategy, and send the execution instruction to the corresponding target device for execution;

[0030] The fault analysis model is obtained by training the initial network model based on a plurality of training samples, and each of the training samples includes the task attributes of a historical fault event and the fault cause corresponding to the historical fault event.

[0031] In a second aspect, the present application further provides an automatic operation and maintenance device, the device comprising an average task volume determination module, a demand determination module, a temporary communication link establishment module and a task allocation module, wherein:

[0032] An average task amount determination module is used to determine the average task amount of the faulty node group within a target time period when determining that the task node group is a faulty node group, wherein the target time period is a time period before the fault event occurs, and the task node group includes an initiating node and a receiving node of the fault event;

[0033] A demand determination module, used to determine whether the backup link meets the task execution demand based on the average task amount and the benchmark task amount of the task carried by the backup link;

[0034] A temporary communication link establishment module, used for determining a transfer node if the backup link does not meet the task execution requirements, and establishing a temporary communication link between the faulty node groups based on the transfer node;

[0035] A task allocation module is used to determine the target link of each target task from the backup link and the temporary communication link based on the task type and / or task data in the task attributes of the target task, and execute the target task based on the target link of each target task; the target task includes the tasks to be executed between the fault node groups, and the new task established based on the task attributes of the fault event, and the task attributes include the task type, task data and the task node group composed of the initiating node and the receiving node.

[0036] In a third aspect, the present application further provides a server, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0037] When determining that the task node group is a fault node group, determining an average task amount of the fault node group within a target time period, the target time period being a time period before the fault event occurs, the task node group including an initiating node and a receiving node of the fault event;

[0038] Determining whether the backup link meets the task execution requirement based on the average task amount and the benchmark task amount of the task carried by the backup link;

[0039] If the backup link does not meet the task execution requirements, determine a transfer node, and establish a temporary communication link between the faulty node group based on the transfer node;

[0040] Based on the task type and / or task data in the task attributes of the target task, the target link of each target task is determined from the backup link and the temporary communication link, and the target task is executed based on the target link of each target task; the target task includes the tasks to be executed between the fault node groups, and the new task established based on the task attributes of the fault event, and the task attributes include the task type, the task data and the task node group composed of the initiating node and the receiving node.

[0041] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0042] When determining that the task node group is a fault node group, determining an average task amount of the fault node group within a target time period, the target time period being a time period before the fault event occurs, the task node group including an initiating node and a receiving node of the fault event;

[0043] Determining whether the backup link meets the task execution requirement based on the average task amount and the benchmark task amount of the task carried by the backup link;

[0044] If the backup link does not meet the task execution requirements, determine a transfer node, and establish a temporary communication link between the faulty node group based on the transfer node;

[0045] Based on the task type and / or task data in the task attributes of the target task, the target link of each target task is determined from the backup link and the temporary communication link, and the target task is executed based on the target link of each target task; the target task includes the tasks to be executed between the fault node groups, and the new task established based on the task attributes of the fault event, and the task attributes include the task type, the task data and the task node group composed of the initiating node and the receiving node.

[0046] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0047] When determining that the task node group is a fault node group, determining an average task amount of the fault node group within a target time period, the target time period being a time period before the fault event occurs, the task node group including an initiating node and a receiving node of the fault event;

[0048] Determining whether the backup link meets the task execution requirement based on the average task amount and the benchmark task amount of the task carried by the backup link;

[0049] If the backup link does not meet the task execution requirements, determine a transfer node, and establish a temporary communication link between the faulty node group based on the transfer node;

[0050] Based on the task type and / or task data in the task attributes, the target link of each target task is determined from the backup link and the temporary communication link, and the target task is executed based on the target link of each target task; the target task includes the tasks to be executed between the fault node groups, and the new task established based on the task attributes of the fault event, and the task attributes include the task type, the task data and the task node group composed of the initiating node and the receiving node.

[0051] In the above-mentioned automatic operation and maintenance method, device, server and storage medium, the average task volume of the faulty node group in the target time period before the fault event occurs is determined, and then compared with the baseline task volume of the backup link between the faulty node groups, so as to determine whether the backup link can meet the execution requirements of the tasks between the faulty node groups; and when it is determined that the backup link cannot meet the task execution requirements, by determining the transit node and establishing a temporary communication link through the transit node, the temporary communication link and the backup link are used to execute the tasks to be executed (target tasks) between the faulty node groups, so that it can be determined that the corresponding task data can be transmitted in real time; and, the target link for executing each target task is determined by the task type and / or task data, so that the backup link and the temporary communication link can only execute target tasks of fixed task types and / or data types, thereby improving the execution efficiency of each link. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0053] Figure 1 An application environment diagram of an automatic operation and maintenance method in an embodiment;

[0054] Figure 2 A flowchart of an automatic operation and maintenance method in one embodiment;

[0055] Figure 3 is a schematic diagram of a temporary communication link in one embodiment;

[0056] Figure 4 A schematic diagram of a process for determining whether a task node group is a fault node group in one embodiment;

[0057] Figure 5 A schematic diagram of a process for determining a transfer node in an embodiment;

[0058] Figure 6 A schematic diagram of a process for determining a fault cause in an embodiment;

[0059] Figure 7 is a structural block diagram of an automatic operation and maintenance device in an embodiment;

[0060] Figure 8 FIG. 4 is a diagram showing the internal structure of a server in one embodiment. DETAILED DESCRIPTION

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

[0062] The automatic operation and maintenance method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, any two terminals 102 can communicate through the network for data transmission, and each terminal can transmit data with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. Among them, the terminal 102 includes but is not limited to various personal computers, laptops, smart phones, tablets, Internet of Things devices and portable wearable devices, and can also be terminal devices used in certain scenarios, such as self-service guidance and inquiry self-service terminals in hospitals, such as self-service terminals for self-service ticket purchase and ticket collection at airports, etc.; Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The server 104 can be implemented with an independent server or a server cluster consisting of multiple servers.

[0063] In an exemplary embodiment, an automatic operation and maintenance method is provided, which is applied to a target network (target system) and executed by a server in the target network. For the embodiment of the present application, the target network is a communication network (communication system) composed of multiple terminals and servers. In the target network, any two terminals can communicate through the network for data transmission, and each terminal can transmit data with the server through the network. Among them, each terminal can correspond to one node or multiple nodes, which is not specifically limited in the embodiment of the present application.

[0064] In the embodiment of the present application, each task corresponds to a status label, wherein: a task that has been established but not yet executed is a task to be executed, and its status label is to be executed; a task that is already being executed is a task event, and its status label can be any one of executing, suspended execution, execution error, execution failure, and successful execution; wherein, execution error and execution failure both indicate that the task has failed to execute. The task that has been executed has a corresponding status label of ended; if it is a cyclic task, the status label of each task that has been executed also contains the cyclic round of the task. For a task event that fails to execute, it will be selected to execute again until it is executed N times, and the task event is determined to be a failure event; wherein, N is greater than or equal to 2.

[0065] Each terminal is configured to be able to send status information of each task event to the server in real time or in a triggered state, wherein the trigger state can be every preset time, whenever a new task event is generated in the terminal, when the status information of any task event in the terminal changes, and when the terminal receives a query request sent by the server; of course, the trigger state can also be other pre-set conditional states, which are not specifically limited in the embodiments of the present application, as long as the server can monitor the status information of each task event in the target network.

[0066] Furthermore, the terminal adjusts the status information of the task event based on the execution status of the task event. For example, the terminal adjusts the status information of the task event to an execution error. Some of the reasons for the execution error are temporary and some are continuous. The fault event in the embodiment of the present application is a fault that can be reproduced and persists, such as a communication link interruption, a continuously low transmission rate, etc.

[0067] An automatic operation and maintenance method in the embodiment of the present application is applied to Figure 1 The server 104 in FIG. 1 is used as an example to illustrate. Figure 2 The automatic operation and maintenance method provided in the embodiment of the present application includes the following steps 10 to 40, wherein:

[0068] Step 10: When it is determined that the task node group is a faulty node group, determine the average task volume of the faulty node group within the target time period.

[0069] The target time period is a time period before the fault event occurs, and the task node group includes the initiating node and the receiving node of the fault event. The length of the target time period can be preset, for example, 10 minutes, or 30 minutes, which is not specifically limited in the embodiments of the present application.

[0070] The task node group in which the number of fault events occurring in a unit cycle is greater than the set fault threshold can be determined as a fault node group; the fault node group can also be a fault node group determined based on the test results of executing a test task on two nodes in the task node group; the specific method for determining the fault node group is not specifically limited in the embodiments of the present application. The average task volume is the number of tasks executed by the fault node group in a unit cycle; the average task volume represents the load-bearing pressure of tasks between fault node groups, and also represents the task execution requirements for the backup link.

[0071] Step 20: Determine whether the backup link meets the task execution requirement based on the average task volume and the benchmark task volume of the task carried by the backup link.

[0072] For the embodiments of the present application, a main communication link can be established between any two nodes, and a backup link can also be established; when there is a fault in the main communication link, the task to be executed can be executed through the backup link. Furthermore, the backup link can also be established only between nodes with more frequent communications. For example, for two nodes whose number of completed tasks is always greater than a set threshold in each unit cycle, they are called frequent node groups, and a backup link is established between the frequent node groups. There will be a corresponding backup mark between the two nodes with a backup link. The backup mark is embedded in the code. By querying whether there is a backup mark in the code, it can be determined whether there is a backup link between the faulty node groups corresponding to the faulty node.

[0073] If there is no backup link between the faulty node groups, then directly execute step 30 to establish a temporary communication link between the faulty node groups. If there is a backup link between the faulty node groups, then execute this step.

[0074] For the embodiments of the present application, when it is determined that there is a backup link between the faulty node groups, the tasks to be executed between the faulty node groups can be executed through the backup link; the benchmark task volume is the maximum number of tasks that can be executed by the backup link within a unit period. Since the task event will be repeated N times when the execution fails, it is necessary to leave a certain redundancy for the backup link, and the utilization rate of the backup link will not be set to 100%; that is, the task execution requirement to be met is that the average task volume must be less than R% of the benchmark task volume of the task carried by the backup link. Of course, the R here is a value that can be set and modified, and this is not specifically limited in the embodiments of the present application.

[0075] For example, if R is 80, if the average task volume at this time is 81% of the benchmark task volume, it is determined that the backup link does not meet the task execution requirements; if the average task volume at this time is 70% of the benchmark task volume, it is determined that the backup link meets the task execution requirements.

[0076] Step 30: If the backup link does not meet the task execution requirement, a transit node is determined, and a temporary communication link is established between the faulty node groups based on the transit node.

[0077] For the embodiment of the present application, when it is determined that the backup link between the faulty node groups does not meet the task execution requirements, a temporary communication link can be established by determining a transit node, and the pending tasks between the faulty node groups are executed together through the temporary communication link and the backup link. The temporary communication link is implemented by relaying data between two nodes in the faulty node group through a transit node; a schematic diagram of a temporary communication link is shown in FIG. Figure 3As shown: the faulty node group corresponding to the fault event includes the initiating node A, the receiving node B, and the communication link failure between A and B; a transit node C can be determined, and it is necessary to first determine that nodes A and B can communicate with the transit node C, and then establish a new communication link between A, C and B as a temporary communication link. At this time, the role of the transit node C is to receive the data sent by the A node and forward it to the B node, and to receive the data sent by the B node and forward it to the A node; at the same time, the data sent by the receiving node B can also be forwarded by the transit node C to the sending node A.

[0078] Step 40: Based on the task type and / or task data in the task attributes of the target task, determine the target link of each target task from the backup links and the temporary communication links, and execute the target task based on the target link of each target task.

[0079] For the embodiment of the present application, the target task includes the task to be performed between the fault node groups, and the new task established based on the task attributes of the fault event, and the task attributes include the task type, the task data and the task node group composed of the initiating node and the receiving node. The target task between the fault node groups is jointly executed by the standby link and the temporary communication link. Generally, the more task types a link performs and the more data types are transmitted, the lower the execution efficiency of the link; and when the task types performed by a link are less and the data types transmitted are relatively fixed, the execution efficiency of the link will be higher. Therefore, after the temporary communication link is established, it is necessary to allocate the corresponding task types and / or data types of the task data to the temporary communication link and the standby link.

[0080] In one possible implementation, the target link of each target task can be determined based on a pre-defined task type allocation rule and a data type allocation rule. For example, the target link of a target task whose task type is a request type and a query type and the target link of a target task whose task data is a video and image type can be set as a standby link; the target link of a target task whose task type is a storage type and the target link of a target task whose task data is text data can also be set as a standby link. The task type allocation rule and the data type allocation rule are not specifically limited in the embodiments of the present application, as long as the set task type allocation rule and the data type allocation rule can improve the task execution efficiency of the standby link and the temporary communication link.

[0081] In an embodiment of the present application, when determining a faulty node group, the server determines the average task volume of the faulty node group within a target time period before the fault event occurs, and then compares it with the baseline task volume of the backup link between the faulty node groups, thereby determining whether the backup link can meet the execution requirements of the tasks between the faulty node groups; and when it is determined that the backup link cannot meet the task execution requirements, by determining a transit node and establishing a temporary communication link through the transit node, the temporary communication link and the backup link are used to execute the tasks to be executed (target tasks) between the faulty node groups, thereby determining that the corresponding task data can be transmitted in real time; and, the target link for executing each target task is also determined by the task type and / or task data, so that the backup link and the temporary communication link can only execute target tasks of fixed task types and / or data types, thereby improving the execution efficiency of each link.

[0082] The server can determine the fault event by detecting the status information of each task event in execution, and then establish a new task for execution based on the task attributes of the fault event, and judge whether there is a backup link based on the fault node group in the task attributes of the fault event. When there is a backup link, the established new task can be executed through the backup link. When there is no backup link, the new task can also be executed based on the newly established temporary communication link, so that the task data corresponding to the fault event can be transmitted in time.

[0083] Furthermore, when there is a fault event, the transmission data corresponding to the fault event has not yet started to be transmitted, and there may be parts that have been transmitted and parts that have not been transmitted; in order to enable the fault event to be executed smoothly and not affect the transmission of data, a new task is established based on the fault event. Specifically, the corresponding initiating node and receiving node are determined based on the task attributes of the fault event, and it is determined whether the receiving node has received incomplete task data; if the receiving node has incomplete task data, a new task is established based on the task attributes of the fault event and the partial task data received by the receiving node, wherein the task data of the new task is the data obtained by eliminating the incomplete task data based on the task data of the fault event, and the other items in the task attributes of the new task are consistent with the task attributes of the fault event, that is, the function of breakpoint resumption of data can be realized. If there is no incomplete task data on the receiving node, that is, when the fault event starts to execute but has not transmitted any data, its status information is modified to an execution fault; at this time, the task attributes of the established new task are consistent with the various items of the task attributes of the fault event.

[0084] In one embodiment, referring to Figure 4 The process of determining whether the task node group is a faulty node group may specifically include step 01-step 02, wherein:

[0085] Step 01: Create a test task based on the task attributes of a fault event, where the fault event is a task whose execution status is characterized as failure.

[0086] When the status information of a task event is an execution failure or an execution error, it is not necessarily a continuous and reproducible failure caused by a communication link failure between the sending node and the receiving node; there are usually many reasons for execution errors and execution failures, and it can also be a temporary non-reproducible failure such as a format error of the task data to be transmitted in the task event and a temporary reduction in the transmission rate caused by network fluctuations; and for temporary non-reproducible failures, some will recover by themselves in a short period of time, such as a temporary reduction in the transmission rate caused by network fluctuations, which will usually recover within a delay of a few seconds; and a format error in the task data will return a corresponding message to prompt a data format error. In the embodiment of the present application, the fault event determined by the server refers to a continuous and reproducible fault event, which is usually a communication link interruption between two nodes or a communication that maintains a low transmission rate for a long period of time.

[0087] Therefore, in order to more accurately determine the fault event, further, in the embodiment of the present application, determining whether a fault event exists can specifically include: analyzing the status information of each task event based on the exception matching rule to determine whether there is an abnormal event; if there is an abnormal event, establishing an event test task based on the task attributes of the abnormal event, and executing the event test task; based on the execution result of the event test task, determining whether the abnormal event is a fault event.

[0088] Specifically, the status information of the task event can be in execution, suspended execution, execution error, and execution failure. Exception matching rules include: task events whose execution time is greater than the time threshold are abnormal events; task events whose transmission rate is less than the rate threshold are abnormal events; task events whose execution status label is an abnormal label are abnormal events. Among them, task events in execution and suspended execution are normal events, and suspended execution can be a state caused by a response to an instruction triggered by the user, or it can be a state caused by the event execution rules based on the terminal. The abnormal labels are error and failure. For task events whose status information is execution error or execution failure, it is determined to be an abnormal event. Furthermore, it is necessary to determine whether the abnormal event is a reproducible and continuous fault event.

[0089] Any mismatch between the task attributes of a task event and the event execution rules of the terminal may cause the status information to be changed to an execution error or execution failure. For example, if the format of the task data in the task attributes of a task event is incorrect, the task data cannot be subpackaged, which may cause the status information of the task event to be changed to an execution error. Therefore, in order to eliminate abnormal events caused by the mismatch between task attributes and event execution rules, after obtaining the task attributes of the abnormal event, the server establishes an event test task based on the task attributes and sends the execution instruction of the event test task to the sending node of the abnormal event, so that the event test task is executed at the sending node; wherein, the task attributes of the event test task should be in accordance with the event execution rules of the terminal. If the event test task is successfully executed, it is determined that the abnormal event is not a fault event; if the time test task is not successfully executed, the abnormal time is determined to be a fault event.

[0090] Step 02: Execute a test task between the task node groups of the fault event, and determine whether the task node group is a faulty node group based on the test results. The test results include the transmission network speed and the execution status of each test task.

[0091] Specifically, the process of establishing a test task is to establish multiple task templates based on the task node group of the fault event, and to set a task type for each task template after establishing the task template. It should be noted that each task type corresponds to at least one task template, thereby improving the comprehensiveness and reliability of the test.

[0092] Furthermore, for each task type, test data is extracted from the test data lake based on the task type, and the test data is filled into the task template corresponding to the task type to obtain the test task. That is, the test data lake stores various data types for testing, and the matching relationship between the task type and the data type of the test data is pre-set. Then, based on the task type corresponding to each task template, the corresponding task data is matched from the test data lake and filled into the template, thereby obtaining each test task after the test data is filled.

[0093] Execute each test task between the task node groups, and record the execution status of each test task; for each test task characterized by a successful execution status, determine it as a successful task; for each test task characterized by a failed execution status, determine it as a failed task. Record the start time and end time of each successful task, and determine the task network speed of each successful task through the start time and end time and the volume of test data in the successful task; and determine the average network speed as the transmission network speed in the test results through the task network speed corresponding to each successful task. Then determine whether the task node group is a faulty node group based on the transmission network speed in the test results and the execution status of each test task.

[0094] Further, in one of the embodiments, in step 02, determining whether the task node group is a faulty node group is based on the test results, which may specifically include: if the transmission network speed is less than the reference network speed, determining that the task node group is a faulty node group; and / or, if the execution success rate is determined to be less than a set threshold, determining that the task node group is a faulty node group; wherein the execution success rate is the ratio of the number of test tasks whose execution status is characterized as successful to the total number of test tasks.

[0095] Specifically, the reference network speed can be pre-set or determined by the average value of the transmission network speeds between multiple other nodes; the reference network speed is used to evaluate whether the transmission network speed meets the average network quality. In one possible implementation, when the transmission network speed in the test result is less than the reference network speed, the task node group can be determined to be a faulty node group. In any possible implementation, in the test result, when the ratio of the number of successful tasks to the number of test tasks, that is, the execution success rate of the test task is less than or equal to the set threshold, the task node group is determined to be a faulty node group.

[0096] However, if there are many task types and data types in the test tasks executed between the faulty node groups, the transmission network speed value in the test results may be relatively low; therefore, in order to further improve the accuracy of determining the faulty node group, in another possible situation, if it is determined that the transmission network speed is less than the benchmark network speed, and the execution success rate is determined to be less than the set threshold, then the task node group is determined to be a faulty node group.

[0097] In one embodiment, referring to Figure 5 The process of determining the transfer node in step 30 may specifically include steps 31 and 32, wherein:

[0098] Step 31: Determine the node whose number of tasks to be executed is less than a first threshold as a candidate node;

[0099] Step 32: determine the comprehensive transmission rate of each candidate node with the faulty node group, and determine the candidate node with the largest comprehensive transmission rate as the transit node. The comprehensive transmission rate is the sum of the transmission rates of the candidate node with each node in the faulty node group.

[0100] Specifically, for any node, the tasks to be executed are temporarily stored in the queue to be executed. The server sends a request to each node to obtain the number of tasks to be executed of each node except the nodes in the faulty node group, and determines the nodes whose number of tasks to be executed is less than the first threshold as the candidate nodes, and obtains the IP of each candidate node. The server sends the IP of each candidate node to the sending node and the receiving node in the faulty node group, and enables the sending node and the receiving node to send test data to each candidate node based on the IP of each candidate node, and then determines the comprehensive transmission rate of each candidate node with the faulty node group, which is the sum of the transmission rates of the candidate node with each node in the faulty node group; further, the candidate node with the largest comprehensive transmission rate is determined as the transit node.

[0101] In the embodiment of the present application, when establishing a temporary communication link, a node whose number of tasks to be executed is less than a first threshold is selected as a candidate node, and then a transfer node is determined from the candidate nodes; since the number of tasks to be executed at the transfer node is small, even if a certain amount of tasks is added to the transfer node, it will not cause congestion at the transfer node, thereby enabling the tasks to be executed at the transfer node to be executed quickly. Moreover, since the transfer node is the node with the highest comprehensive transmission rate determined from the candidate nodes, when executing a new task through the temporary communication link established by the transfer node, a higher execution efficiency can be obtained.

[0102] Furthermore, the target link, in addition to being used to execute a new task established based on a fault event, can also be used for any task to be executed (target task) between two nodes of the faulty node group.

[0103] Furthermore, in one of the embodiments, the automatic operation and maintenance method also includes the step of setting a validity period for the temporary communication link, which may specifically include: setting a threshold as the validity period, and setting a validity period for the temporary communication link; or, determining the validity period based on the number of target tasks, and setting a validity period for the temporary communication link.

[0104] Specifically, the validity period of the target link can be a preset duration, such as one hour or two hours, and the specific duration of the validity period is not specifically limited in the embodiments of the present application. In another possible implementation, the validity period can also be determined based on the number of target tasks between the faulty node groups, for example, a mapping relationship table between the number and the duration is set, and then the validity period is determined based on the number of target tasks and the mapping relationship table, and the validity period is set for the target link.

[0105] Further, in one embodiment, referring to Figure 6 The automatic operation and maintenance method further includes a step of determining the cause of the fault event, including steps 50 to 70, wherein:

[0106] Step 50: Process the task attributes of the fault event based on the fault analysis model to determine the first fault cause;

[0107] Step 60: Determine an estimated fault cause based on the first fault cause and the test result, and match a solution strategy based on the estimated fault cause;

[0108] Step 70: Generate an execution instruction based on the solution strategy, and send the execution instruction to the corresponding target device for execution.

[0109] Specifically, the fault analysis model can be obtained through pre-training; the fault analysis model is obtained by training the initial network model based on multiple training samples, each training sample includes the task attributes of the historical fault event and the fault cause corresponding to the historical fault event. The specific type of the initial network model is not limited in the embodiment of the present application, as long as the fault analysis can be realized.

[0110] Among them, since the test results for the task node group include the transmission network speed and the execution status of each test task, the test results can also be used to analyze whether the fault type is a hardware fault between the faulty node groups, and whether it is a business data fault between the faulty node groups. For example, when the transmission network speed is low, it can be determined that the fault type is a hardware fault between the faulty node groups; when the execution status of each test task only indicates that all test tasks of a certain type of task have failed to execute, it can be determined that there is a business data fault for that type of task between the faulty node groups.

[0111] Furthermore, the first fault cause output by the fault analysis model may include all possible causes of inter-node faults, including hardware-related fault causes and business-level fault causes. Therefore, combined with the fault type analyzed by the test results, the possible causes of the fault are further analyzed as the estimated fault causes.

[0112] Furthermore, the solution strategy corresponding to the estimated fault cause is matched from the pre-established knowledge graph for the target network, and then the server generates the corresponding execution instruction based on the solution strategy, and sends the execution instruction to the corresponding target device for execution. The knowledge graph includes the connection relationship between each node, each node, the corresponding fault cause between any two nodes, and the solution strategy corresponding to each fault cause.

[0113] Furthermore, when a fault event is determined, the server generates an alarm instruction and sends an alarm message to the alarm device for alarm. The alarm message includes the confirmation time of the fault event, the task attributes of the fault event, and the status information. Furthermore, when the estimated fault cause and solution strategy are determined, the server also generates a prompt message based on the fault cause and solution prediction and sends it to the alarm device for prompt.

[0114] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0115] Based on the same inventive concept, the embodiment of the present application also provides an automatic operation and maintenance device for implementing the automatic operation and maintenance method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more automatic operation and maintenance device embodiments provided below can refer to the limitations on the automatic operation and maintenance method above, and will not be repeated here.

[0116] In an exemplary embodiment, Figure 7 As shown, an automatic operation and maintenance device is provided, which includes an average task amount determination module 701, a demand determination module 702, a temporary communication link establishment module 703 and a task allocation module 704, wherein:

[0117] The average task amount determination module 701 is used to determine the average task amount of the faulty node group within a target time period when the task node group is determined to be a faulty node group. The target time period is a time period before the fault event occurs. The task node group includes the initiating node and the receiving node of the fault event.

[0118] A demand determination module 702, configured to determine whether the backup link meets the task execution demand based on the average task quantity and the benchmark task quantity of the task carried by the backup link;

[0119] A temporary communication link establishing module 703 is used to determine a transit node if the backup link does not meet the task execution requirement, and to establish a temporary communication link between the faulty node groups based on the transit node;

[0120] The task allocation module 704 is used to determine the target link of each target task from the backup links and the temporary communication links based on the task type and / or task data in the task attributes of the target task, and execute the target task based on the target link of each target task; the target task includes the tasks to be executed between the fault node groups, and the new tasks established based on the task attributes of the fault event, and the task attributes include the task type, task data and the task node group composed of the initiating node and the receiving node.

[0121] In the above-mentioned automatic operation and maintenance device, the average task volume of the faulty node group in the target time period before the fault event occurs is determined, and then compared with the baseline task volume of the backup link between the faulty node groups, so as to determine whether the backup link can meet the execution requirements of the tasks between the faulty node groups; and when it is determined that the backup link cannot meet the task execution requirements, by determining the transit node and establishing a temporary communication link through the transit node, the temporary communication link and the backup link are used to execute the tasks to be executed (target tasks) between the faulty node groups, so that it can be determined that the corresponding task data can be transmitted in real time; and, the target link for executing each target task is determined by the task type and / or task data, so that the backup link and the temporary communication link can only execute target tasks of fixed task types and / or data types, thereby improving the execution efficiency of each link.

[0122] In one of the embodiments, the automatic operation and maintenance device further includes a fault node group determination module, and the fault node group determination module is specifically used to:

[0123] Establish a test task based on the task attributes of a fault event, where a fault event is a task whose execution status is characterized as a failure;

[0124] A test task is executed between the task node groups of the fault event, and whether the task node group is a faulty node group is determined based on the test result. The test result includes the transmission network speed and the execution status of each test task.

[0125] In one embodiment, the fault node group determination module is specifically used to:

[0126] Establish multiple task templates based on the task node group of the fault event, and set the task type of each task template; wherein each task type corresponds to at least one task template;

[0127] For each task type, test data is extracted from the test data lake based on the task type, and the test data is filled into the task template corresponding to the task type to obtain the test task.

[0128] In one embodiment, the faulty node group determination module is specifically used for at least one of the following:

[0129] If the transmission network speed is less than the reference network speed, the task node group is determined to be a faulty node group;

[0130] If it is determined that the execution success rate is less than the set threshold, the task node group is determined to be a faulty node group; wherein the execution success rate is the ratio of the number of test tasks characterized by successful execution status to the total number of test tasks.

[0131] In one embodiment, the temporary communication link establishing module 703 is specifically configured to:

[0132] Determine a node whose number of tasks to be executed is less than a first threshold as a candidate node;

[0133] Determine the comprehensive transmission rate of each candidate node with the faulty node group, and determine the candidate node with the largest comprehensive transmission rate as the transit node. The comprehensive transmission rate is the sum of the transmission rates of the candidate node with each node in the faulty node group.

[0134] In one embodiment, the automatic operation and maintenance device further includes a validity period setting module, and the validity period setting module is specifically used for at least one of the following:

[0135] A threshold value is set as a validity period, and a validity period is set for the temporary communication link;

[0136] A validity period is determined based on the number of target tasks, and a validity period is set for the temporary communication link.

[0137] In one embodiment, the automatic operation and maintenance device further includes a fault analysis module, which is specifically used to:

[0138] Processing the task attributes of the fault event based on the fault analysis model to determine the first fault cause;

[0139] Determine an estimated fault cause based on the first fault cause and the test result, and match a solution strategy based on the estimated fault cause;

[0140] Generate execution instructions based on the solution strategy, and send the execution instructions to the corresponding target device for execution;

[0141] The fault analysis model is obtained by training the initial network model based on multiple training samples, and each training sample includes the task attributes of the historical fault event and the fault cause corresponding to the historical fault event.

[0142] Each module in the above automatic operation and maintenance device can be implemented in whole or in part by software, hardware and their combination. Each module can be embedded in or independent of the processor in the server in hardware form, or can be stored in the memory in the server in software form, so that the processor can call and execute the operations corresponding to each module above.

[0143] In an exemplary embodiment, a server is provided, whose internal structure diagram can be as follows: Figure 8 As shown. The server includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the server is used to provide computing and control capabilities. The memory of the server includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the server is used to exchange information between the processor and an external device. The communication interface of the server is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, an automatic operation and maintenance method is implemented.

[0144] Those skilled in the art will understand that Figure 8 The structure shown in the figure is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied. The specific server may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0145] In an exemplary embodiment, a server is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0146] When determining that the task node group is a fault node group, determining an average task amount of the fault node group in a target time period, the target time period is a time period before the fault event occurs, and the task node group includes an initiating node and a receiving node of the fault event;

[0147] Determine whether the backup link meets the task execution requirements based on the average task volume and the benchmark task volume of the task carried by the backup link;

[0148] If the backup link does not meet the task execution requirements, a transit node is determined, and a temporary communication link is established between the faulty node groups based on the transit node;

[0149] Based on the task type and / or task data in the task attributes of the target task, the target link of each target task is determined from the backup links and the temporary communication links, and the target task is executed based on the target link of each target task; the target task includes tasks to be executed between faulty node groups, and new tasks established based on the task attributes of the fault event, and the task attributes include task type, task data, and a task node group consisting of an initiating node and a receiving node.

[0150] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0151] When determining that the task node group is a fault node group, determining an average task amount of the fault node group in a target time period, the target time period is a time period before the fault event occurs, and the task node group includes an initiating node and a receiving node of the fault event;

[0152] Determine whether the backup link meets the task execution requirements based on the average task volume and the benchmark task volume of the task carried by the backup link;

[0153] If the backup link does not meet the task execution requirements, a transit node is determined, and a temporary communication link is established between the faulty node groups based on the transit node;

[0154] Based on the task type and / or task data in the task attributes of the target task, the target link of each target task is determined from the backup links and the temporary communication links, and the target task is executed based on the target link of each target task; the target task includes tasks to be executed between faulty node groups, and new tasks established based on the task attributes of the fault event, and the task attributes include task type, task data, and a task node group consisting of an initiating node and a receiving node.

[0155] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0156] When determining that the task node group is a fault node group, determining an average task amount of the fault node group in a target time period, the target time period is a time period before the fault event occurs, and the task node group includes an initiating node and a receiving node of the fault event;

[0157] Determine whether the backup link meets the task execution requirements based on the average task volume and the benchmark task volume of the task carried by the backup link;

[0158] If the backup link does not meet the task execution requirements, a transit node is determined, and a temporary communication link is established between the faulty node groups based on the transit node;

[0159] Based on the task type and / or task data in the task attributes of the target task, the target link of each target task is determined from the backup links and the temporary communication links, and the target task is executed based on the target link of each target task; the target task includes tasks to be executed between faulty node groups, and new tasks established based on the task attributes of the fault event, and the task attributes include task type, task data, and a task node group consisting of an initiating node and a receiving node.

[0160] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0161] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0162] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0163] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. An automatic operation and maintenance method, characterized in that: The method comprises: When determining that the task node group is a fault node group, determining an average task amount of the fault node group within a target time period, the target time period being a time period before the fault event occurs, the task node group including an initiating node and a receiving node of the fault event; Determining whether the backup link meets the task execution requirement based on the average task amount and the benchmark task amount of the task carried by the backup link; If the backup link does not meet the task execution requirements, determine a transfer node, and establish a temporary communication link between the faulty node group based on the transfer node; Based on the task type and / or task data in the task attributes of the target task, determine the target link of each target task from the backup link and the temporary communication link, and execute the target task based on the target link of each target task; the target task includes the tasks to be executed between the fault node groups, and the new tasks established based on the task attributes of the fault event, the task attributes including the task type, the task data and the task node group consisting of the initiating node and the receiving node; Wherein, determining whether the task node group is a faulty node group includes: Establishing a plurality of task templates based on the task node group of the fault event, and setting a task type for each of the task templates; wherein each of the task types corresponds to at least one of the task templates; and the fault event is a task whose execution status is characterized as a failure; For each of the task types, test data is extracted from the test data lake based on the task type, and the test data is filled into the task template corresponding to the task type to obtain a test task; A test task is executed between the task node groups of the fault event, and whether the task node group is a faulty node group is determined according to the test result, wherein the test result includes a transmission network speed and an execution status of each of the test tasks.

2. The method according to claim 1, characterized in that Determining whether the task node group is a faulty node group according to the test result includes at least one of the following: If the transmission network speed is less than the reference network speed, determining that the task node group is a faulty node group; If it is determined that the execution success rate is less than a set threshold, the task node group is determined to be a faulty node group; wherein the execution success rate is the ratio of the number of the test tasks whose execution status is characterized as successful to the total number of the test tasks.

3. The method according to claim 1 or 2, characterized in that: The step of determining the transfer node comprises: Determine a node whose number of tasks to be executed is less than a first threshold as a candidate node; Determine the comprehensive transmission rate of each candidate node with the faulty node group, and determine the candidate node with the largest comprehensive transmission rate as the transit node, wherein the comprehensive transmission rate is the sum of the transmission rates of the candidate nodes with each node in the faulty node group.

4. The method according to claim 3, characterized in that The method further comprises: Using a fixed threshold as the validity period and setting the validity period for the temporary communication link; or A validity period is determined based on the number of the target tasks, and a validity period is set for the temporary communication link.

5. The method according to claim 2, characterized in that: The method further comprises: Processing the task attribute of the fault event based on the fault analysis model to determine a first fault cause; Determine an estimated fault cause based on the first fault cause and the test result, and match a solution strategy based on the estimated fault cause; Generate an execution instruction based on the solution strategy, and send the execution instruction to the corresponding target device for execution; The fault analysis model is obtained by training the initial network model based on a plurality of training samples, and each of the training samples includes the task attributes of a historical fault event and the fault cause corresponding to the historical fault event.

6. An automatic operation and maintenance device, characterized in that: The device includes an average task amount determination module, a demand determination module, a temporary communication link establishment module and a task allocation module, wherein: An average task amount determination module is used to determine the average task amount of the faulty node group within a target time period when the task node group is determined to be a faulty node group, wherein the target time period is a time period before the fault event occurs, and the task node group includes an initiating node and a receiving node of the fault event; A demand determination module, used to determine whether the backup link meets the task execution demand based on the average task amount and the benchmark task amount of the task carried by the backup link; A temporary communication link establishment module, used for determining a transfer node if the backup link does not meet the task execution requirements, and establishing a temporary communication link between the faulty node groups based on the transfer node; A task allocation module, configured to determine a target link of each target task from the backup link and the temporary communication link based on a task type and / or task data in a task attribute of the target task, and execute the target task based on the target link of each target task; the target task includes tasks to be executed between the fault node groups, and new tasks established based on the task attributes of the fault event, wherein the task attributes include a task type, task data, and the task node group consisting of an initiating node and a receiving node; A fault node group determination module is used to: establish multiple task templates based on the task node group of the fault event, and set the task type of each task template; wherein each task type corresponds to at least one task template; the fault event is a task whose execution status is characterized as a failure; For each of the task types, test data is extracted from the test data lake based on the task type, and the test data is filled into the task template corresponding to the task type to obtain a test task; A test task is executed between the task node groups of the fault event, and whether the task node group is a faulty node group is determined according to the test result, wherein the test result includes a transmission network speed and an execution status of each of the test tasks.

7. The device according to claim 6, characterized in that The fault node group determination module is specifically used for at least one of the following: If the transmission network speed is less than the reference network speed, the task node group is determined to be a faulty node group; If it is determined that the execution success rate is less than the set threshold, the task node group is determined to be a faulty node group; The execution success rate is the ratio of the number of test tasks whose execution status is characterized as successful to the total number of test tasks.

8. The device according to claim 6 or 7, characterized in that The temporary communication link establishment module is specifically used for: Determine a node whose number of tasks to be executed is less than a first threshold as a candidate node; Determine the comprehensive transmission rate of each candidate node with the faulty node group, and determine the candidate node with the largest comprehensive transmission rate as the transit node. The comprehensive transmission rate is the sum of the transmission rates of the candidate node with each node in the faulty node group.

9. A server, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 5 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, 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 5 are implemented.

Images