Fault processing method and device

Abstract

The invention relates to the technical field of artificial intelligence, in particular to a fault processing method and device. The method comprises the following steps: receiving a fault processing capability scheduling request sent by a fault server; according to scheduling request parameters carried by the fault handling capacity scheduling request, information verification of fault handling capacity and alarm network element equipment is carried out, and a verification result is obtained; under the condition that the verification result indicates that verification succeeds and the fault level of a main fault node is higher than a preset level, a processing flow corresponding to the main fault node is started, and the processing flow is used for conducting fault processing on the main fault node and a related node set of the main fault node; under the condition that the verification result indicates that verification fails, a fault work order is distributed to target equipment, and the fault work order is used for indicating the target equipment to carry out fault processing according to a received manual instruction. According to the invention, the fault processing accuracy and the fault processing efficiency can be improved.

Description

Technical Field

[0001] The present disclosure relates to the field of artificial intelligence technology, and in particular to a fault handling method and device. Background Art

[0002] With the development of network intelligence, network operation and maintenance can make more use of artificial intelligence, big data and other technical means to realize the automation and intelligence of operation and maintenance work. Among them, network operation and maintenance refers to a series of activities to maintain, manage, optimize and troubleshoot network systems, network equipment, network applications, etc. to ensure the stable, efficient and safe operation of the network. For example, the generated faults can be handled through the expert experience library, but with the increasing number and types of network equipment, the accuracy of fault handling is poor and the timeliness of fault handling is poor. Summary of the invention

[0003] The present disclosure provides a fault handling method and device, which can improve the accuracy and efficiency of fault handling. The technical solution of the present disclosure is as follows:

[0004] According to a first aspect of an embodiment of the present disclosure, a fault handling method is provided, including:

[0005] Receiving a fault handling capacity scheduling request sent by a faulty server;

[0006] According to the scheduling request parameters carried in the fault handling capability scheduling request, verify the fault handling capability and the information of the alarm network element device, and obtain the verification result;

[0007] When the verification result indicates that the verification is successful and the fault level of the main fault node is higher than the preset level, starting a processing flow corresponding to the main fault node, wherein the processing flow is used to perform fault processing on the main fault node and a set of nodes related to the main fault node;

[0008] In the case where the verification result indicates that the verification has failed, a fault work order is dispatched to the target device, wherein the fault work order is used to instruct the target device to perform fault processing according to the received manual instruction.

[0009] According to some embodiments, when the verification result indicates that the verification is successful and the fault level of the main fault node is higher than a preset level, starting a processing flow corresponding to the main fault node includes:

[0010] When the verification result indicates that the verification is successful, obtaining fault alarm information corresponding to the main fault node;

[0011] According to the fault alarm information, obtaining the fault level corresponding to the main fault node;

[0012] A fault handling strategy corresponding to the fault level is executed on the main fault node and a set of nodes related to the main fault node.

[0013] According to some embodiments, executing a fault handling strategy corresponding to the fault level on the main fault node and a set of nodes related to the main fault node includes:

[0014] When the fault level is higher than a preset level, obtaining a set of related nodes corresponding to the main fault node, wherein the set of related nodes includes at least one node whose association relationship with the main fault node is greater than a relationship threshold;

[0015] According to the relevant node set, issuing alarm information or providing a fault handling solution to a target device corresponding to the relevant node set;

[0016] A fault handling strategy corresponding to the fault level is executed on the main fault node.

[0017] According to some embodiments, the acquiring a set of related nodes corresponding to the primary faulty node includes:

[0018] According to the fault alarm information, obtaining the diffusion range and fault propagation path corresponding to the main fault node;

[0019] According to the fault propagation path and the diffusion range, acquiring a node set corresponding to the main fault node, wherein the node set includes at least one node covered by the diffusion range;

[0020] Using an interconnection function to verify the association relationship between each node in the node set, and obtaining the association relationship between each node and the main fault node;

[0021] According to the association relationship, a related node set in the node set is obtained.

[0022] According to some embodiments, acquiring the diffusion range and the fault propagation path corresponding to the main fault node according to the fault alarm information includes:

[0023] Clustering the historical fault data set using a clustering algorithm to obtain a fault category set corresponding to the historical fault data set;

[0024] Classify each fault category in the fault category set to obtain a classification result;

[0025] According to the network asset information, obtain the current network status information;

[0026] Predict the current network state information and the historical fault data set by using a fault propagation prediction model to obtain a diffusion path corresponding to the main fault node;

[0027] According to the current network status information, obtain the target node and associated links of the network topology where the main fault node is located;

[0028] The classification result, the target node and the associated link are simulated using a fault diffusion rule to obtain a diffusion range and a fault propagation path corresponding to the main fault node.

[0029] According to some embodiments, acquiring a related node set in the node set according to the association relationship includes:

[0030] Obtaining the network topology structure corresponding to each node in the node set by using a K-truss algorithm;

[0031] According to the network topology, obtaining the medium centrality and closeness centrality of each node;

[0032] According to the medium centrality and the closeness centrality, obtaining a k-truss value between each of the nodes and the main fault node;

[0033] Adding nodes whose k-truss values ​​are greater than a preset value to the related node set;

[0034] or

[0035] A preset number of nodes are added to the related node set in descending order of the k-truss values.

[0036] According to some embodiments, providing a fault handling solution to a target device corresponding to the set of related nodes according to the set of related nodes includes:

[0037] Determine a fault handling solution corresponding to each relevant node in the relevant node set according to the relevant node set, fault handling experience and the fault propagation path;

[0038] The fault handling solution is provided to the target device corresponding to each related node in the related node set.

[0039] According to a second aspect of the present disclosure, there is provided

[0040] A request receiving unit, used for receiving a fault handling capacity scheduling request sent by a fault server;

[0041] A result acquisition unit, configured to perform information verification of the fault handling capability and the alarm network element device according to the scheduling request parameters carried in the fault handling capability scheduling request, and obtain a verification result;

[0042] a fault processing unit, configured to start a processing flow corresponding to the main fault node when the verification result indicates that the verification is successful and the fault level of the main fault node is higher than a preset level, wherein the processing flow is used to perform fault processing on the main fault node and a set of nodes related to the main fault node;

[0043] The fault handling unit is used to dispatch a fault work order to the target device when the verification result indicates that the verification fails, wherein the fault work order is used to instruct the target device to perform fault handling according to the received manual instruction.

[0044] According to a third aspect of an embodiment of the present disclosure, a network device is provided, including:

[0045] processor;

[0046] a memory for storing instructions executable by the processor;

[0047] The processor is configured to execute the instructions to implement the fault handling method described in any one of the aforementioned aspects.

[0048] According to a fourth aspect of an embodiment of the present disclosure, a storage medium is provided. When instructions in the storage medium are executed by a processor of a network device, the network device is enabled to execute the fault handling method described in any one of the preceding aspects.

[0049] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, including a computer program, wherein the computer program implements any one of the methods described in the preceding aspects when executed by a processor.

[0050] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:

[0051] In some or related embodiments, a fault handling capacity scheduling request sent by a fault server is received; according to the scheduling request parameters carried by the fault handling capacity scheduling request, the information verification of the fault handling capacity and the alarm network element device is performed to obtain the verification result; when the verification result indicates that the verification is successful and the fault level of the main fault node is higher than the preset level, the processing flow corresponding to the main fault node is started, wherein the processing flow is used to perform fault processing on the main fault node and the node set related to the main fault node; when the verification result indicates that the verification fails, a fault work order is dispatched to the target device, wherein the fault work order is used to instruct the target device to perform fault processing according to the received manual instruction. Therefore, the fault can be processed by the scheduling request parameters, and different fault processing measures can be adopted for different verification results, the limitation of the expert experience library on the analysis ability of fault propagation can be reduced, and the nodes related to the main fault node can be determined, the fault of the main fault node can be restricted on the propagation path, and the impact of the fault on the system can be reduced, and it can be applied to the scene where the number and types of network devices are increasing. The technical solution can be applied to a variety of scenes, can improve the accuracy and efficiency of fault processing, and can improve the node update capability of the network operation and maintenance fault processing process.

[0052] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0054] Figure 1 is a flow chart of a fault handling method according to an exemplary embodiment;

[0055] Figure 2 is a flow chart of a fault handling method according to an exemplary embodiment;

[0056] Figure 3 is an exemplary schematic diagram of a fault handling system according to an exemplary embodiment;

[0057] Figure 4 is a block diagram of a fault processing device according to an exemplary embodiment;

[0058] Figure 5 The invention is a block diagram of a network device according to an exemplary embodiment. DETAILED DESCRIPTION

[0059] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0060] The embodiments of the present disclosure provide a fault handling method and device. In some embodiments, the terms such as fault handling method, information processing method, communication method, etc. can be interchangeable, the terms such as fault handling device, information processing device, communication device, etc. can be interchangeable, and the terms such as information processing system, communication system, etc. can be interchangeable.

[0061] The embodiments of the present disclosure are not exhaustive, but are only illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined, for example, some or all of the steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0062] In each embodiment of the present disclosure, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment based on their internal logical relationships.

[0063] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0064] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular form, such as "a", "an", "the", "above", "said", "aforementioned", "this", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun after the article may be understood as a singular expression or a plural expression.

[0065] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0066] In some embodiments, the terms “at least one,” “one or more,” “a plurality of,” “multiple,” etc. may be used interchangeably.

[0067] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects, and do not constitute restrictions on the position, order, priority, quantity or content of the description objects. The statement of the description object refers to the description in the context of the claims or embodiments, and should not constitute unnecessary restrictions due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields", and the "first" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number, and can be one or more. Taking the "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes may be the same or different. For example, if the description object is "device", then the "first device" and the "second device" may be the same device or different devices, and their types may be the same or different. For another example, if the description object is "information", then the "first information" and the "second information" may be the same information or different information, and their contents may be the same or different.

[0068] In some embodiments, "terminal" or "terminal device" can be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0069] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0070] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0071] Figure 1 is a flowchart of a fault handling method according to an exemplary embodiment. Figure 1 As shown, the fault handling method can be used in a scenario where fault information is scheduled to be processed when a fault occurs, and includes the following steps:

[0072] In step S11, a fault handling capacity scheduling request sent by a fault server is received;

[0073] According to some embodiments, the execution subject of the embodiments of the present disclosure is a network device. The name of the network device is not limited. For example, the network device can also be called a server, or a server cluster, or an operation server in a fault handling system.

[0074] According to some embodiments, the fault server may be, for example, a server that can obtain fault information. The name of the fault server is not limited. The fault server may also be, for example, called a fault center. The fault server does not specifically refer to a fixed server. For example, when the server identifier of the fault server changes, the fault server may also change accordingly. For example, when the server that has a fault changes, the fault server may also change accordingly.

[0075] In some embodiments, the fault handling capacity scheduling request may be, for example, a request for processing fault information sent by a fault server. The fault handling capacity scheduling request may be, for example, a request sent by a fault server to an operation server. The fault handling capacity scheduling request does not specifically refer to a fixed request. For example, when the request time point corresponding to the fault handling capacity scheduling request changes, the fault handling capacity scheduling request may also change accordingly. For example, when the parameters included in the fault handling capacity scheduling request change, the fault handling capacity scheduling request may also change accordingly.

[0076] According to some embodiments, when performing fault handling, a fault handling capacity scheduling request sent by a fault server may be received.

[0077] In step S12, according to the scheduling request parameters carried in the fault handling capability scheduling request, the information of the fault handling capability and the alarm network element device is verified to obtain the verification result;

[0078] According to some embodiments, the scheduling request parameter may be, for example, a parameter carried by the fault handling capability scheduling request, which is used to operate the server to schedule fault information. The scheduling request parameter may also be referred to as a scheduling request parameter set, or a scheduling request parameter set. The embodiments of the present disclosure are not limited to this. The scheduling request parameter does not specifically refer to a fixed parameter. For example, when the number of parameters corresponding to the scheduling request parameter changes, the scheduling request parameter may also change accordingly. For example, when a parameter included in the scheduling request parameter changes, the scheduling request parameter may also change accordingly.

[0079] In some embodiments, the fault handling capability is used to indicate the capability of each fault target device to handle the fault. The fault handling capability does not specifically refer to a fixed capability. The name of the fault handling capability does not specifically refer to a fixed name. For example, the fault handling capability can also be called a fault handling capability, or a fault handling capability, etc.

[0080] According to some embodiments, the alarm network element device may be used to indicate a device that generates an alarm for a fault. The alarm network element device may include a variety of different devices. For example, different alarm information may correspond to different alarm network element devices.

[0081] In some embodiments, information verification may be used, for example, to indicate a verification method for processing fault information.

[0082] According to some embodiments, the verification result can be used to indicate the result of the information verification of the fault handling capability and the alarm network element device. The verification result does not specifically refer to a fixed result. For example, when the verification method changes, the verification result can also change accordingly. For example,

[0083] According to some embodiments, for example, the information verification of the fault handling capability and the alarm network element device may be performed based on the scheduling request parameters carried in the fault handling capability scheduling request to obtain the verification result.

[0084] In step S13, when the verification result indicates that the verification is successful and the fault level of the main fault node is higher than the preset level, a processing flow corresponding to the main fault node is started, wherein the processing flow is used to perform fault processing on the main fault node and a set of nodes related to the main fault node;

[0085] According to some embodiments, the processing flow is a flow for processing the fault of the main fault node. The processing flow does not specifically refer to a fixed flow. For example, when the fault type corresponding to the main fault node changes, the processing flow may also change accordingly. For example, when a modification instruction for the processing flow is received, the processing flow may also change accordingly.

[0086] According to some embodiments, the main fault node may be used to refer to the fault node corresponding to the fault alarm information, for example, the node where the fault alarm information appears. The main fault node does not specifically refer to a fixed node. For example, when the node identifier corresponding to the main fault node changes, the main fault node may also change accordingly.

[0087] According to some embodiments, the related node set of the main fault node may be, for example, a group formed by at least one related node. The related node set does not specifically refer to a fixed set. The related nodes may, for example, be used to indicate nodes related to the main fault node and nodes affected by the main fault node. For example, when the number of related nodes included in the related node set changes, the related node set may also change accordingly. For example, when any related node in the related node set changes, the related node set may also change accordingly.

[0088] In some embodiments, when the verification result indicates that the verification is successful and the fault level of the main fault node is higher than a preset level, the processing flow corresponding to the main fault node is started, wherein the processing flow is used to perform fault processing on the main fault node and a set of related nodes of the main fault node.

[0089] In step S14, when the verification result indicates that the verification has failed, a fault work order is dispatched to the target device, wherein the fault work order is used to instruct the target device to perform fault processing according to the received manual instruction.

[0090] In some embodiments, the manual instruction may be, for example, an instruction sent through a terminal. The manual instruction does not specifically refer to a fixed instruction. The manual instruction includes, but is not limited to, a manual voice instruction, a manual click instruction, or a manual gesture instruction. The manual instruction is used to instruct the device to handle the current fault.

[0091] According to some embodiments, a fault work order may be used to refer to fault alarm information, for example. The fault work order does not specifically refer to a fixed work order. For example, when the fault information corresponding to the fault work order changes, the fault work order may also change accordingly. For example, when the time of the fault work order changes, the fault work order may also change accordingly.

[0092] In some embodiments, the target device may be used to indicate a device that receives a fault work order. The target device may be determined, for example, based on the fault type corresponding to the fault work order. For example, when the fault work order changes, the target device may also change accordingly. The name of the target device is not limited. For example, the target device may also be called a fault target device, a processing device, etc. For example, when the device identification of the target device changes, the target device may also change accordingly. For example, when the manual instruction changes, the target device may also change accordingly.

[0093] When the target device receives the fault work order, the target device may process the fault work order. For example, the target device may process the fault work order according to the received fault handling instruction. The target device may process the fault work order alone, or may interact with other devices to process the fault work order. The other devices may include, for example, at least one network element or at least one terminal, which is not limited in the embodiments of the present disclosure.

[0094] In some or related embodiments, a fault handling capacity scheduling request sent by a fault server is received; according to the scheduling request parameters carried in the fault handling capacity scheduling request, the information of the fault handling capacity and the alarm network element device is verified to obtain the verification result; when the verification result indicates that the verification is successful and the fault level of the main fault node is higher than the preset level, the processing flow corresponding to the main fault node is started, wherein the processing flow is used to perform fault processing on the main fault node and the node set related to the main fault node; when the verification result indicates that the verification fails, a fault work order is dispatched to the target device, wherein the fault work order is used to instruct the target device to perform fault processing according to the received manual instruction. Therefore, the fault can be processed by the scheduling request parameters, and different fault processing measures can be adopted for different verification results, the limitation of the expert experience library on the analysis ability of fault propagation can be reduced, and the nodes related to the main fault node can be determined, and the fault of the main fault node can be restricted on the propagation path, reducing the impact of the fault on the system, and the technical solution can be applied to a variety of scenarios, and the accuracy and efficiency of fault processing can be improved.

[0095] Figure 2 is a flowchart of a fault handling method according to an exemplary embodiment. Figure 2 As shown, the fault handling method can be used in the scenario of intelligently handling faults in network operation and maintenance, and includes the following steps:

[0096] In step S21, a fault handling capacity scheduling request sent by a fault server is received;

[0097] According to some embodiments, the execution subject of the embodiments of the present disclosure is a network device. The name of the network device is not limited. For example, the network device can also be called a server, or a server cluster, etc.

[0098] in, Figure 3 FIG. 1 is an example diagram of a fault handling system according to an exemplary embodiment. Figure 3As shown, the fault handling system may include, for example, a fault server and an operation server. The operation server may, for example, use a fault handling capability query interface to satisfy the subscriber's query of the fault handling capability list before performing fault operation scheduling, and may receive fault handling scheduling interface request information and record it in the fault handling scheduling information table. The fault server may send a fault handling capability scheduling request to the operation server.

[0099] In step S22, according to the scheduling request parameters carried in the fault handling capability scheduling request, the information of the fault handling capability and the alarm network element device is verified to obtain the verification result;

[0100] The specific process is as described above and will not be repeated here.

[0101] In step S23, when the verification result indicates that the verification is successful, the fault alarm information corresponding to the main fault node is obtained;

[0102] The specific process is as described above and will not be repeated here.

[0103] According to some embodiments, the operation server may obtain the fault alarm information monitored in the faulty server through an interface, and the fault alarm information includes the time, location, category and initial impact range of the fault. The time of the fault occurrence is the specific date and time when the fault occurs. The location of the fault may include, for example, the computer room number, the rack location, or the fault coverage area. The category of the fault may be confirmed, for example, by analyzing the fault code and the system log. The initial impact range of the fault is confirmed by the existing fault level standard of the faulty server.

[0104] In step S24, according to the fault alarm information, the fault level corresponding to the main fault node is obtained;

[0105] The specific process is as described above and will not be repeated here.

[0106] In some embodiments, the fault type and location information can be used to analyze the number of business systems and users affected, determine the impact range, and compare the fault alarm information with the fault history data to obtain the fault level corresponding to the current main fault.

[0107] The fault level does not refer to a specific fixed level. For example, the fault level can be determined by the fault server's current classification standard for fault information, combined with the importance of the fault information to the service and the network type of the fault server. According to the classification of faults by the 5GC core network, the fault level can include, for example:

[0108] Level 1 failure: affects the services provided by the system and requires immediate action, such as when a device or resource is completely unavailable and needs to be restored immediately.

[0109] Level 2 failure: affects the service quality, such as the service quality of a certain device or resource deteriorates, and needs to be processed to restore full capabilities;

[0110] Level 3 fault: The service quality has not been affected within the preset time, but in order to avoid more serious faults, it needs to be processed or further observed at the preset time point;

[0111] Level 4 fault: indicates that there may be potential errors that may affect the services provided, and different measures should be taken according to the corresponding errors.

[0112] According to some embodiments, for example, the severity of the fault can be divided according to the fault level, for example, a level 1 fault corresponds to an urgent fault severity, a level 2 fault corresponds to an important fault severity, a level 3 fault corresponds to a minor fault severity, and a level 4 fault corresponds to a general fault severity.

[0113] In step S25, when the fault level is higher than a preset level, a fault handling strategy corresponding to the fault level is executed on the main fault node and a set of nodes related to the main fault node;

[0114] The specific process is as described above and will not be repeated here.

[0115] According to some embodiments, executing a fault handling strategy corresponding to the fault level on the main fault node and a set of nodes related to the main fault node includes:

[0116] When the fault level is higher than a preset level, obtaining a set of related nodes corresponding to the main fault node, wherein the set of related nodes includes at least one node whose association relationship with the main fault node is greater than a relationship threshold;

[0117] According to the relevant node set, issuing alarm information or providing a fault handling solution to a target device corresponding to the relevant node set;

[0118] The fault handling strategy corresponding to the fault level is executed on the main fault node. Therefore, when the fault level is higher than the preset level, the nodes that are strongly associated with the current main fault node can be analyzed. Through the analysis of strongly associated nodes, the related nodes affected by the main fault node can be obtained, and alarm information can be issued or a fault handling solution can be provided. The fault propagation risk of the related nodes can be controlled, the fault handling time can be reduced, and the fault handling efficiency can be improved.

[0119] According to some embodiments, the preset level may be, for example, a level at which the impact of the fault is greater than a threshold value of the impact. The preset level does not specifically refer to a fixed level. For example, the preset level may be, for example, a secondary fault. For example, when a modification instruction for the preset level is received, the preset level may also change accordingly. For example, when the specific level corresponding to the preset level changes, the preset level may also change accordingly.

[0120] Among them, when the fault level is less than the preset level, only the main fault node can be processed, and there is no need to process the related node set of the main fault node.

[0121] In some embodiments, the related node set may be, for example, a group formed by at least one related node. The related node set does not specifically refer to a fixed set. The related nodes may, for example, be used to indicate nodes related to the main fault node and nodes affected by the main fault node. For example, when the number of related nodes included in the related node set changes, the related node set may also change accordingly. For example, when any related node in the related node set changes, the related node set may also change accordingly.

[0122] According to some embodiments, the acquiring a set of related nodes corresponding to the primary faulty node includes:

[0123] According to the fault alarm information, obtaining the diffusion range and fault propagation path corresponding to the main fault node;

[0124] According to the fault propagation path and the diffusion range, acquiring a node set corresponding to the main fault node, wherein the node set includes at least one node covered by the diffusion range;

[0125] Using an interconnection function to verify the association relationship between each node in the node set, and obtaining the association relationship between each node and the main fault node;

[0126] According to the association relationship, the related node set in the node set is obtained. Therefore, the node range covered by the fault can be determined according to the fault propagation path and diffusion range, and the association relationship between each node can be determined through the interconnection function to determine the related node set, thereby improving the accuracy of determining the related node set, reducing the impact range of the fault, and improving the efficiency of fault handling.

[0127] According to some embodiments, acquiring the diffusion range and the fault propagation path corresponding to the main fault node according to the fault alarm information includes:

[0128] Clustering the historical fault data set using a clustering algorithm to obtain a fault category set corresponding to the historical fault data set;

[0129] Classify each fault category in the fault category set to obtain a classification result;

[0130] According to the network asset information, obtain the current network status information;

[0131] Predict the current network state information and the historical fault data set by using a fault propagation prediction model to obtain a diffusion path corresponding to the main fault node;

[0132] According to the current network status information, obtain the target node and associated links of the network topology where the main fault node is located;

[0133] The fault propagation rule is used to simulate the classification results, the target node and the associated link to obtain the diffusion range and fault propagation path corresponding to the main fault node. Therefore, the fault propagation prediction model and the key nodes strongly related to the main fault node can be combined to determine the fault handling process and improve the fault handling efficiency.

[0134] According to some embodiments, acquiring a related node set in the node set according to the association relationship includes:

[0135] Obtaining the network topology structure corresponding to each node in the node set by using a K-truss algorithm;

[0136] According to the network topology, obtaining the medium centrality and closeness centrality of each node;

[0137] According to the medium centrality and the closeness centrality, obtaining a k-truss value between each of the nodes and the main fault node;

[0138] Adding nodes whose k-truss values ​​are greater than a preset value to the related node set;

[0139] or

[0140] According to the order of k-truss values ​​from large to small, a preset number of nodes are added to the related node set. Therefore, the Louvain algorithm can be used to detect the community of the network, identify several closely connected node groups, form the community structure of the network, and analyze the average k-truss value of the nodes within each community, as well as the connection density between communities, determine the target node according to the connection strength within the community, improve the accuracy of the target node determination, and improve the accuracy of fault handling.

[0141] According to some embodiments, for example, a fault propagation prediction model may be used to predict the trend and scope of possible fault propagation. The fault propagation prediction model may, for example, analyze historical fault data and current network status information to obtain a propagation path, which may specifically include:

[0142] Obtain a collection of historical fault data and extract the fault alarm information of each fault, which may include time, location, category and impact range. Improve the availability and consistency of data through data cleaning and formatting. Cluster the historical fault data to obtain multiple fault category sets, and use clustering algorithms to analyze the processed historical fault data to obtain fault categories.

[0143] According to some embodiments, a K-means clustering algorithm can be used to analyze the processed historical fault data set. For example, the number of clusters k=5, the number of iterations can be set to 100, and the convergence threshold can be set to 001 to obtain classification results of fault categories, including hardware failure, software failure, transmission and relay failure, power environment failure, equipment performance alarm, configuration failure, etc.

[0144] Among them, hardware failures may include, for example, failures caused by hardware devices such as devices, boards, ports, etc.; software failures may include, for example, failures caused by equipment system software problems; transmission and relay failures may include, for example, failures caused by network connection problems such as various links; power environment failures may include, for example, failures caused by the operating environment of the equipment in the computer room including power supply, temperature, etc.; equipment performance alarms may include, for example, failures related to equipment operating performance; configuration failures may include, for example, failures related to equipment system resource configuration.

[0145] According to some embodiments, the operation server can call network asset information from the network management system to obtain current network status information, including network topology structure and equipment operation status as well as equipment model and importance level, and identify important nodes and associated links in the network topology where the main fault node is located in combination with the current network status. The important node can be, for example, a target node.

[0146] Among them, network status data includes indicators such as network topology, device CPU utilization, memory occupancy, link bandwidth utilization, etc., which are collected every 5 minutes. For example, the PageRank algorithm can use the connection relationship between each node in the network topology as an edge, and calculate the importance score of the network node through the PageRank algorithm based on multiple indicators such as the number of edges connected to the node and network status data, and find out the important nodes with high importance scores and the associated links composed of multiple important node links.

[0147] According to some embodiments, based on the classification results of the fault categories and the target nodes, a fault diffusion rule is used to perform simulation to predict the possible propagation path and diffusion range of the fault of the main fault node in the network topology.

[0148] For example, the SIR propagation model can be used to simulate fault diffusion, setting the propagation probability to 6, the maximum propagation hop count to 5, simulating 1000 times, and counting the fault propagation path and impact range. By analyzing the simulation results, it is found that the fault mainly propagates along the direction from the core switch to the aggregation switch and then to the access switch, affecting 2-3 downstream nodes on average. Evaluate the confidence of the prediction results: set the prior probability of the fault occurrence and the posterior probability predicted by the model, and use the predict function to calculate the confidence of the prediction results. When the confidence is greater than 8, it is judged that the current simulated fault diffusion path is valid, and all nodes covered by the valid fault paths may be fault-associated nodes of the main fault node.

[0149] According to some embodiments, the network topology of the fault coverage nodes of the current main fault node can be analyzed by the K-truss algorithm to obtain the connection strength and structure between different nodes in the network topology associated with the main fault node, thereby finding the key node that is strongly associated with the main fault node. The key node can be, for example, a related node.

[0150] Among them, each node in the network element topology is connected to each other through an interconnection function. Specifically, the change trend of the expected value of the failure of two nodes is analyzed by the time series similarity algorithm. If there is a follow-up relationship between the two nodes, the two nodes are connected to each other through the interconnection function, that is, the two nodes are strongly associated nodes. When one of the nodes is in a fault state, the state of the other node connected to it is affected by its fault state and tends to fail, and the influence of the two can be unidirectional.

[0151] According to some embodiments, when the network topology is obtained, the K-truss algorithm can be used to perform a preliminary analysis of the network to obtain the maximum k-truss value between each pair of nodes. The connection strength of each node in the network is determined by analyzing the obtained k-truss value, wherein a higher k-truss value is used to indicate a tighter connection between nodes. If the k-truss value between nodes is high, these nodes may constitute the core layer of the network, and the hierarchical structure of the network can be identified through the connection mode of these core nodes. After obtaining the hierarchical structure data, for the nodes in the core layer, the network intermediary and control power of these nodes are further analyzed to determine the key nodes.

[0152] According to some embodiments, in a network topology consisting of 100 nodes, the K-truss algorithm analysis found that 80% of the node pairs have k-truss values ​​greater than or equal to 5, indicating that the connection between these nodes is very close and may constitute the core layer of the network. The network intermediary and control power of these core nodes are further analyzed, and the top 10% of key nodes are determined by calculating the betweenness centrality and closeness centrality of the nodes. These nodes play an important intermediary and control role in the network.

[0153] The betweenness centrality BCi can be used to indicate the number of shortest paths passing through a node in a network, for example. The calculation formula of BCid can be, for example, as shown in formula (1):

[0154]

[0155] Among them, Nist represents the number of paths passing through node i and are the shortest paths; gst represents the number of shortest paths connecting s and t.

[0156] The closeness centrality CCi can be used to indicate, for example, the importance of a node, wherein the calculation formula of CCi can be, for example, as shown in formula (2), and the calculation formula of di can be, for example, as shown in formula (3):

[0157]

[0158] Among them, di represents the average distance from node i to the rest of the points, and the reciprocal of the average distance is the closeness centrality.

[0159] According to some embodiments, providing a fault handling solution to a target device corresponding to the set of related nodes according to the set of related nodes includes:

[0160] Determine a fault handling solution corresponding to each relevant node in the relevant node set according to the relevant node set, fault handling experience and the fault propagation path;

[0161] The fault handling solution is provided to the target device corresponding to each related node in the related node set.

[0162] According to some embodiments, for example, if a related node has a hardware failure, a fault handling solution corresponding to the related node may be determined based on hardware performance parameters, fault handling experience, and the fault propagation path.

[0163] In some embodiments, for example, if the target node has a software defect, a software configuration file of the node is obtained, and a fault handling solution corresponding to the target node is obtained, for example, code review and generation of a repair solution.

[0164] In step S26, when the verification result indicates that the verification has failed, a fault work order is dispatched to the target device, wherein the fault work order is used to instruct the target device to perform fault processing according to the received manual instruction.

[0165] The specific process is as described above and will not be repeated here.

[0166] According to some embodiments, the operation server receives a request for scheduling fault handling capacity and can perform scheduling verification rule matching. If the verification rule matching is successful, the automatic processing flow of the main fault node is executed; if the verification rule matching is unsuccessful, the fault information is marked as requiring manual intervention, and a work order is automatically dispatched to the corresponding operation and maintenance team through the fault handling system to ensure that the fault is handled in a timely manner.

[0167] In one or related embodiments, when the verification result indicates that the verification is successful, the fault alarm information corresponding to the main fault node is obtained; based on the fault alarm information, the fault level corresponding to the main fault node is obtained; and the fault handling strategy corresponding to the fault level is executed on the main fault node and the related node set of the main fault node. Therefore, the fault handling strategy can be determined according to the fault level, and the accuracy of determining the fault handling strategy can be improved.

[0168] A block diagram of a fault processing device is shown according to an exemplary embodiment. Figure 4 , the device 400 comprises:

[0169] The request receiving unit 401 is used to receive a fault handling capacity scheduling request sent by a fault server;

[0170] A result acquisition unit 402 is used to perform information verification of the fault handling capability and the alarm network element device according to the scheduling request parameters carried in the fault handling capability scheduling request, and obtain a verification result;

[0171] A fault processing unit 403 is used to start a processing flow corresponding to the main fault node when the verification result indicates that the verification is successful and the fault level of the main fault node is higher than a preset level, wherein the processing flow is used to perform fault processing on the main fault node and a set of nodes related to the main fault node;

[0172] The fault handling unit 403 is further configured to dispatch a fault work order to the target device when the verification result indicates that the verification has failed, wherein the fault work order is configured to instruct the target device to perform fault handling according to the received manual instruction.

[0173] The fault processing unit 403 may also include an automatic fault processing sub-unit 4031, which is used to start the processing flow corresponding to the main fault node when the verification result indicates that the verification is successful and the fault level of the main fault node is higher than a preset level, wherein the processing flow is used to perform fault processing on the main fault node and a set of related nodes of the main fault node.

[0174] According to some embodiments, the fault processing unit 403 is used to start the processing flow corresponding to the main fault node when the verification result indicates that the verification is successful and the fault level of the main fault node is higher than the preset level, specifically to:

[0175] When the verification result indicates that the verification is successful, obtaining fault alarm information corresponding to the main fault node;

[0176] According to the fault alarm information, obtaining the fault level corresponding to the main fault node;

[0177] A fault handling strategy corresponding to the fault level is executed on the main fault node and a set of nodes related to the main fault node.

[0178] According to some embodiments, the fault processing unit 403 is configured to execute a fault processing strategy corresponding to the fault level on the main fault node and a set of nodes related to the main fault node, specifically to:

[0179] When the fault level is higher than a preset level, obtaining a set of related nodes corresponding to the main fault node, wherein the set of related nodes includes at least one node whose association relationship with the main fault node is greater than a relationship threshold;

[0180] According to the relevant node set, issuing alarm information or providing a fault handling solution to a target device corresponding to the relevant node set;

[0181] A fault handling strategy corresponding to the fault level is executed on the main fault node.

[0182] According to some embodiments, the fault processing unit 403, when used to obtain the set of related nodes corresponding to the main fault node, is specifically used to:

[0183] According to the fault alarm information, obtaining the diffusion range and fault propagation path corresponding to the main fault node;

[0184] According to the fault propagation path and the diffusion range, acquiring a node set corresponding to the main fault node, wherein the node set includes at least one node covered by the diffusion range;

[0185] Using an interconnection function to verify the association relationship between each node in the node set, and obtaining the association relationship between each node and the main fault node;

[0186] According to the association relationship, a related node set in the node set is obtained.

[0187] According to some embodiments, the fault processing unit 403 is configured to obtain the diffusion range and the fault propagation path corresponding to the main fault node according to the fault alarm information, specifically to:

[0188] Clustering the historical fault data set using a clustering algorithm to obtain a fault category set corresponding to the historical fault data set;

[0189] Classify each fault category in the fault category set to obtain a classification result;

[0190] According to the network asset information, obtain the current network status information;

[0191] Predict the current network state information and the historical fault data set by using a fault propagation prediction model to obtain a diffusion path corresponding to the main fault node;

[0192] According to the current network status information, obtain the target node and associated links of the network topology where the main fault node is located;

[0193] The classification result, the target node and the associated link are simulated using a fault diffusion rule to obtain a diffusion range and a fault propagation path corresponding to the main fault node.

[0194] According to some embodiments, the fault processing unit 403 is used to obtain the related node set in the node set according to the association relationship, specifically to:

[0195] Obtaining the network topology structure corresponding to each node in the node set by using a K-truss algorithm;

[0196] According to the network topology, obtaining the medium centrality and closeness centrality of each node;

[0197] According to the medium centrality and the closeness centrality, obtaining a k-truss value between each of the nodes and the main fault node;

[0198] Adding nodes whose k-truss values ​​are greater than a preset value to the related node set;

[0199] or

[0200] A preset number of nodes are added to the related node set in descending order of the k-truss values.

[0201] According to some embodiments, the fault processing unit 403 is used to provide a fault processing solution to a target device corresponding to the related node set according to the related node set, specifically to:

[0202] Determine a fault handling solution corresponding to each relevant node in the relevant node set according to the relevant node set, fault handling experience and the fault propagation path;

[0203] The fault handling solution is provided to the target device corresponding to each related node in the related node set.

[0204] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0205] In some or related embodiments, a request receiving unit is used to receive a fault handling capacity scheduling request sent by a fault server; a result obtaining unit is used to perform information verification of the fault handling capacity and the alarm network element device according to the scheduling request parameters carried by the fault handling capacity scheduling request, and obtain the verification result; a fault handling unit is used to start the processing flow corresponding to the main fault node when the verification result indicates that the verification is successful; and a fault handling unit is used to dispatch a fault work order to a target device when the verification result indicates that the verification fails, wherein the fault work order is used to instruct the target device to perform fault processing according to the received manual instruction. Therefore, the fault can be processed by the scheduling request parameters, and different fault processing measures can be adopted for different verification results, which can reduce the limitation of the expert experience library on the analysis ability of fault propagation, and can determine the nodes related to the main fault node, and can limit the fault of the main fault node on the propagation path, reduce the impact of the fault on the system, and the technical solution can be applied to a variety of scenarios, which can improve the accuracy and efficiency of fault processing.

[0206] Figure 5 is a block diagram of a network device 500 provided in an embodiment of the present disclosure. For example, the network device 500 may be provided as a network device. Figure 5The network device 500 includes a processing component 522, which further includes at least one processor, and a memory resource represented by a memory 532 for storing instructions executable by the processing component 522, such as an application. The application stored in the memory 532 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 522 is configured to execute instructions to perform any of the methods described above in the network device.

[0207] The network device 500 may also include a power supply component 527 configured to perform power management of the network device 500, a wired or wireless network interface 550 configured to connect the network device 500 to a network, and an input / output (I / O) interface 558. The network device 500 may operate based on an operating system stored in the memory 532, such as Windows Server TM, Mac OS X TM, Unix TM, Linux TM, Free BSD TM or the like.

[0208] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0209] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0210] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0211] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0212] The systems and techniques described herein can be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), the Internet, and a blockchain network.

[0213] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services ("Virtual Private Server", or "VPS" for short). The server may also be a server of a distributed system, or a server combined with a blockchain.

[0214] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.

[0215] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A fault handling method, characterized in that: include: Receiving a fault handling capacity scheduling request sent by a faulty server; According to the scheduling request parameters carried in the fault handling capability scheduling request, verify the fault handling capability and the information of the alarm network element device, and obtain the verification result; When the verification result indicates that the verification is successful and the fault level of the main fault node is higher than the preset level, starting a processing flow corresponding to the main fault node, wherein the processing flow is used to perform fault processing on the main fault node and a set of nodes related to the main fault node; In the case where the verification result indicates that the verification has failed, a fault work order is dispatched to the target device, wherein the fault work order is used to instruct the target device to perform fault processing according to the received manual instruction.

2. The method according to claim 1, characterized in that: When the verification result indicates that the verification is successful and the fault level of the main fault node is higher than the preset level, starting the processing flow corresponding to the main fault node includes: When the verification result indicates that the verification is successful, obtaining fault alarm information corresponding to the main fault node; According to the fault alarm information, obtaining the fault level corresponding to the main fault node; A fault handling strategy corresponding to the fault level is executed on the main fault node and a set of nodes related to the main fault node.

3. The method according to claim 2, characterized in that The executing a fault handling strategy corresponding to the fault level on the main fault node and a set of nodes related to the main fault node includes: When the fault level is higher than a preset level, obtaining a set of related nodes corresponding to the main fault node, wherein the set of related nodes includes at least one node whose association relationship with the main fault node is greater than a relationship threshold; According to the relevant node set, issuing alarm information or providing a fault handling solution to a target device corresponding to the relevant node set; A fault handling strategy corresponding to the fault level is executed on the main fault node.

4. The method according to claim 3, characterized in that: The acquiring of a set of related nodes corresponding to the main fault node includes: According to the fault alarm information, obtaining the diffusion range and fault propagation path corresponding to the main fault node; According to the fault propagation path and the diffusion range, acquiring a node set corresponding to the main fault node, wherein the node set includes at least one node covered by the diffusion range; Using an interconnection function to verify the association relationship between each node in the node set, and obtaining the association relationship between each node and the main fault node; According to the association relationship, a related node set in the node set is obtained.

5. The method according to claim 4, characterized in that The acquiring, according to the fault alarm information, a diffusion range and a fault propagation path corresponding to the main fault node includes: Clustering the historical fault data set using a clustering algorithm to obtain a fault category set corresponding to the historical fault data set; Classify each fault category in the fault category set to obtain a classification result; According to the network asset information, obtain the current network status information; Predict the current network state information and the historical fault data set by using a fault propagation prediction model to obtain a diffusion path corresponding to the main fault node; According to the current network status information, obtain the target node and associated links of the network topology where the main fault node is located; The classification result, the target node and the associated link are simulated using a fault diffusion rule to obtain a diffusion range and a fault propagation path corresponding to the main fault node.

6. The method according to claim 4, characterized in that The acquiring, according to the association relationship, a related node set in the node set includes: Obtaining the network topology structure corresponding to each node in the node set by using a K-truss algorithm; According to the network topology, obtaining the medium centrality and closeness centrality of each node; According to the medium centrality and the closeness centrality, obtaining a k-truss value between each of the nodes and the main fault node; Adding nodes whose k-truss values ​​are greater than a preset value to the related node set; or A preset number of nodes are added to the related node set in descending order of the k-truss values.

7. The method according to claim 5, characterized in that The providing a fault handling solution to a target device corresponding to the relevant node set according to the relevant node set includes: Determine a fault handling solution corresponding to each relevant node in the relevant node set according to the relevant node set, fault handling experience and the fault propagation path; The fault handling solution is provided to the target device corresponding to each related node in the related node set.

8. A fault handling device, characterized in that: include: A request receiving unit, used for receiving a fault handling capacity scheduling request sent by a fault server; A result acquisition unit, configured to perform information verification of the fault handling capability and the alarm network element device according to the scheduling request parameters carried in the fault handling capability scheduling request, and obtain a verification result; a fault processing unit, configured to start a processing flow corresponding to the main fault node when the verification result indicates that the verification is successful and the fault level of the main fault node is higher than a preset level, wherein the processing flow is used to perform fault processing on the main fault node and a set of nodes related to the main fault node; The fault handling unit is used to dispatch a fault work order to the target device when the verification result indicates that the verification fails, wherein the fault work order is used to instruct the target device to perform fault handling according to the received manual instruction.

9. A network device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the fault handling method according to any one of claims 1 to 7.

10. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device is caused to execute the fault handling method according to any one of claims 1 to 7.

Images