Troubleshooting methods, devices and storage media

Abstract

This application provides a fault diagnosis method, apparatus, and storage medium, relating to the field of communication technology, and capable of being used for fault diagnosis. The method includes: acquiring multiple sets of first fault work orders within a first period; each set of first fault work orders corresponds to a network element category; each set of first fault work orders contains multiple fault work orders corresponding to multiple fault types; determining a first probability value corresponding to each fault type in each set of first fault work orders within the first period; acquiring multiple sets of first fault work orders within a second period; the second period being two adjacent periods to the first period; determining a second probability value corresponding to each fault type in each set of first fault work orders within the second period; and determining a troubleshooting priority for each fault type in each set of first fault work orders based on the first and second probability values ​​corresponding to each fault type. This application is used for fault diagnosis.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a fault diagnosis method, apparatus and storage medium. Background Technology

[0002] Currently, when troubleshooting various network elements in 5G networks, the network elements are prioritized, and then potential faults are investigated based on these priorities. However, various network elements encompass multiple fault types, and how to rationally arrange the troubleshooting order for these different fault types has become an urgent technical problem to be solved. Summary of the Invention

[0003] This application provides a troubleshooting method, apparatus, and storage medium capable of troubleshooting.

[0004] To achieve the above objectives, this application adopts the following technical solution:

[0005] Firstly, this application provides a fault diagnosis method, the method comprising: obtaining a first fault work order set and a second fault work order set; wherein, the first fault work order set includes fault work orders for each fault type of the target network element within a first period; the second fault work order set includes fault work orders for each fault type of the target network element within a second period; determining a first probability value for each fault type within the first period based on the fault work orders for each fault type within the first period; determining a second probability value for each fault type within the second period based on the fault work orders for each fault type within the second period; and determining a fault diagnosis priority for each fault type based on the first probability value and the second probability value.

[0006] In conjunction with the first aspect above, in one possible implementation, based on the fault work orders of each fault type in the first period, determining the first probability value of each fault type in the first period includes: determining the first total value of fault work orders in the first fault work order set; determining the first quantity value of fault work orders of each fault type in the first work order set; and determining the first probability value of each fault type in the first period based on the ratio of the first quantity value of each fault type to the first total value.

[0007] In conjunction with the first aspect above, in one possible implementation, based on the fault work orders of each fault type in the second period, a second probability value for each fault type in the second period is determined; this includes: determining a second total value of fault work orders in the second fault work order set; determining a second quantity value of fault work orders for each fault type in the second work order set; and determining a second probability value for each fault type in the second period based on the ratio of the second quantity value to the second total value for each fault type.

[0008] In conjunction with the first aspect above, in one possible implementation, the fault investigation priority of each fault type is determined based on the first probability value and the second probability value of each fault type, including: determining the difference between the first probability value and the second probability value of each fault type; determining whether the difference is greater than or equal to a preset threshold; if it is greater than or equal to the preset threshold, then determining the investigation priority of each fault type based on the magnitude of the difference; if it is less than the preset threshold, then determining the investigation priority of each fault type based on the magnitude of the second probability value.

[0009] In conjunction with the first aspect mentioned above, in one possible implementation, before obtaining the first set of fault work orders and the second set of fault work orders, the method further includes: obtaining multiple fault work orders within the first period and the second period; the fault work order includes: a network element category field and a fault type field; determining the target network element based on the network element category field; and determining each fault type in the target network element based on the fault type field.

[0010] Secondly, this application provides a fault diagnosis device, comprising: a processing unit; the processing unit being configured to acquire a first fault work order set and a second fault work order set; wherein, the first fault work order set includes fault work orders for each fault type of the target network element within a first period; the second fault work order set includes fault work orders for each fault type of the target network element within a second period; the processing unit is further configured to determine a first probability value for each fault type within the first period based on the fault work orders for each fault type within the first period; the processing unit is further configured to determine a second probability value for each fault type within the second period based on the fault work orders for each fault type within the second period; and the processing unit is further configured to determine a fault diagnosis priority for each fault type based on the first probability value and the second probability value for each fault type.

[0011] In conjunction with the second aspect above, in one possible implementation, the processing unit is specifically configured to: determine a first total value of fault work orders in the first fault work order set; determine a first quantity value of fault work orders of each fault type in the first work order set; and determine a first probability value of each fault type within a first period based on the ratio of the first quantity value of each fault type to the first total value.

[0012] In conjunction with the second aspect above, in one possible implementation, the processing unit is further specifically configured to: determine a second total value of fault work orders in the second fault work order set; determine a second quantity value of fault work orders of each fault type in the second work order set; and determine a second probability value of each fault type in the second period based on the ratio of the second quantity value of each fault type to the second total value.

[0013] In conjunction with the second aspect above, in one possible implementation, the processing unit is further specifically configured to: determine the difference between a first probability value and a second probability value for each fault type; determine whether the difference is greater than or equal to a preset threshold; if it is greater than or equal to the preset threshold, determine the investigation priority of each fault type based on the magnitude of the difference; if it is less than the preset threshold, determine the investigation priority of each fault type based on the magnitude of the second probability value.

[0014] In conjunction with the second aspect above, in one possible implementation, the processing unit is further configured to: acquire multiple fault work orders within a first cycle and a second cycle; the fault work order includes: a network element category field and a fault type field; determine the target network element based on the network element category field; and determine each fault type in the target network element based on the fault type field.

[0015] Thirdly, this application provides a fault diagnosis device, which includes a processor and a memory; wherein the memory is used to store computer execution instructions, and when the fault diagnosis device is running, the processor executes the computer execution instructions stored in the memory to cause the fault diagnosis device to perform the fault diagnosis method as described in the first aspect and any possible implementation thereof.

[0016] Fourthly, this application provides a computer-readable storage medium storing instructions that, when executed by a processor of a troubleshooting device, enable the troubleshooting device to perform the troubleshooting method described in the first aspect and any possible implementation thereof.

[0017] Fifthly, this application provides a computer program product containing instructions that, when run on a troubleshooting device, cause the troubleshooting device to perform the troubleshooting method as described in the first aspect and any possible implementation thereof.

[0018] In a sixth aspect, this application provides a chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run computer programs or instructions to implement the troubleshooting method as described in the first aspect and any possible implementation thereof.

[0019] Specifically, the chip provided in this application embodiment also includes a memory for storing computer programs or instructions.

[0020] In this application, the name of the aforementioned troubleshooting device does not limit the equipment or functional module itself. In actual implementation, these devices or functional modules may appear under other names. As long as the function of each device or functional module is similar to that of this application, it falls within the scope of the claims of this application and its equivalents.

[0021] These or other aspects of this application will become more readily apparent in the following description.

[0022] The technical solution provided in this application brings at least the following beneficial effects: The fault work order investigation device acquires a first set of fault work orders and a second set of fault work orders for the target network element within a first period and a second period. The first set of work orders includes fault work orders for each fault type of the target network element within the first period, and the second set of work orders includes fault work orders for each fault type of the target network element within the second period. The fault work order investigation device determines a first probability value corresponding to each fault type in the first set of fault work orders within the first period, and a second probability value corresponding to each fault type in the second set of fault work orders within the second period. Based on the first and second probability values ​​corresponding to each fault type, the fault work order investigation device determines the investigation priority corresponding to each fault type. Thus, by comparing the changes in the probability values ​​corresponding to each fault type within the same network element category in two adjacent time periods, the fault work order investigation device determines the investigation priority of each fault type within the same network element. This solves the technical problem of rationally arranging the investigation order of various fault types for the same network element. Attached Figure Description

[0023] Figure 1 A schematic diagram of the hardware structure of a fault diagnosis device provided in this application embodiment;

[0024] Figure 2 A flowchart illustrating a troubleshooting method provided in an embodiment of this application;

[0025] Figure 3 This is another flowchart illustrating a troubleshooting method provided in an embodiment of this application;

[0026] Figure 4 This is another flowchart illustrating a troubleshooting method provided in an embodiment of this application;

[0027] Figure 5 This is another flowchart illustrating a troubleshooting method provided in an embodiment of this application;

[0028] Figure 6 This is another flowchart illustrating a troubleshooting method provided in an embodiment of this application;

[0029] Figure 7 This is a schematic diagram of a fault diagnosis device provided in an embodiment of this application. Detailed Implementation

[0030] The troubleshooting methods, apparatus, and storage media provided in this application are described in detail below with reference to the accompanying drawings.

[0031] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0032] The terms "first" and "second," etc., used in the specification and drawings of this application are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.

[0033] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0034] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0035] In related technologies, the enterprise safety management risk dynamic monitoring system determines the initial risk level by classifying the risks of each work site in each enterprise, and obtains the potential risks in each work site through the risk adjustment module. Then, it adjusts the risk level in each work site and notifies the relevant staff to conduct safety inspections and supervision based on the adjusted risk level.

[0036] Currently, the troubleshooting methods described above are used when diagnosing faults in various network elements in 5G networks. These elements are prioritized, and potential faults are then investigated based on their priorities. However, since various network elements encompass multiple fault types, how to rationally arrange the order of troubleshooting these different fault types has become a pressing technical problem.

[0037] To address the aforementioned technical problems, this application provides a fault diagnosis method. In this method, a fault work order diagnosis device acquires a first set of fault work orders and a second set of work orders for a target network element within a first period and a second period. The first set of work orders includes fault work orders for each fault type of the target network element within the first period, and the second set of work orders includes fault work orders for each fault type of the target network element within the second period. The fault work order diagnosis device determines a first probability value corresponding to each fault type in the first set of fault work orders within the first period, and a second probability value corresponding to each fault type in the second set of fault work orders within the second period. Based on the first and second probability values ​​corresponding to each fault type, the fault work order diagnosis device determines the diagnosis priority for each fault type within the same network element. Thus, by comparing the changes in the probability values ​​corresponding to each fault type within the same network element category in two adjacent time periods, the fault work order diagnosis device determines the diagnosis priority for each fault type within the same network element. This solves the technical problem of rationally arranging the diagnosis sequence of various fault types for the same network element.

[0038] Figure 1 This is a schematic diagram of a fault diagnosis device provided in an embodiment of this application. The fault diagnosis device 100 includes at least one processor 101, a communication line 102, and at least one communication interface 104, and may also include a memory 103. The processor 101, memory 103, and communication interface 104 can be connected to each other via the communication line 102.

[0039] The processor 101 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0040] Communication line 102 may include a path for transmitting information between the aforementioned components.

[0041] The communication interface 104 is used to communicate with other devices or communication networks. It can use any transceiver-like device, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc.

[0042] The memory 103 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of including or storing desired program code having the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0043] In one possible design, the memory 103 can exist independently of the processor 101, meaning the memory 103 can be an external memory of the processor 101. In this case, the memory 103 can be connected to the processor 101 via the communication line 102 to store execution instructions or application code, and its execution is controlled by the processor 101 to implement the space measurement determination method provided in the following embodiments of this application. In another possible design, the memory 103 can also be integrated with the processor 101, meaning the memory 103 can be an internal memory of the processor 101. For example, the memory 103 can be a cache, which can be used to temporarily store some data and instruction information.

[0044] As one possible implementation, processor 101 may include one or more CPUs, for example Figure 1 CPU0 and CPU1 in the example. Alternatively, the troubleshooting device 100 may include multiple processors, such as... Figure 1 The processors 101 and 107 are included. Alternatively, the troubleshooting device 100 may also include an output device 105 and an input device 106.

[0045] Through the above description of the implementation methods, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the network node can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, modules, and network nodes described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0046] Figure 2 The troubleshooting method provided in the embodiments of this application, such as Figure 2 As shown, the troubleshooting method provided in this application embodiment can be implemented through the following steps 201 to 204.

[0047] Step 201: The fault diagnosis device obtains the first set of fault work orders and the second set of fault work orders.

[0048] In one possible implementation, the fault diagnosis device acquires a first set of fault work orders within a first period and a second set of fault work orders within a second period. The first set of fault work orders includes fault work orders for each fault type of the target network element within the first period; the second set of fault work orders includes fault work orders for each fault type of the target network element within the second period. For example, the first set of fault work orders might correspond to a network element category such as: terminal network element, network device network element, media network element, boundary network element, intelligent network element, etc.

[0049] One example is that the fault types of a bandwidth access server, such as a network element classified as a boundary network element, include, but are not limited to: "single point of failure," "configuration error failure," "backup unavailability failure," and "unreliable backup mechanism failure." "Single point of failure" refers to a network element lacking a backup network element; "configuration error failure" refers to a network element having a backup network element, but failing to switch over when the primary network element fails due to a configuration error; "backup unavailability failure" refers to a failure of the backup network element itself, preventing a switchover; and "unreliable backup mechanism failure" refers to a failure of the primary network element, with the backup network element switching time exceeding a preset duration.

[0050] Step 202: The fault diagnosis device determines the first probability value of each fault type in the first cycle based on the fault work orders of each fault type in the first cycle.

[0051] In one possible implementation, the fault diagnosis device determines a first probability value for each fault type in the first fault work order set corresponding to the network element category within a first period. The first probability value refers to the probability of that fault type occurring within the network element category within the first period.

[0052] For example, in the first period, among network elements classified as boundary network elements, the first probability value for "single point of failure" occurring in the first period is 10%; the first probability value for "configuration error failure" occurring in the first period is 12%; the first probability value for "standby unavailability failure" occurring in the first period is 14%; the first probability value for "standby mechanism unreliability failure" occurring in the first period is 16%; the first probability value for "Class A failure" occurring in the first period is 18%; and the first probability value for "Class B failure" occurring in the first period is 20%, etc.

[0053] Step 203: The fault diagnosis device determines the second probability value of each fault type in the second cycle based on the fault work orders for each fault type in the second cycle.

[0054] In one possible implementation, the fault diagnosis device determines a second probability value for each fault type in the first set of fault work orders corresponding to the network element category within the second period. The second probability value refers to the probability of that fault type occurring within the network element category within the second period.

[0055] For example, in the second cycle, among network elements classified as boundary network elements, the first probability value for "single point of failure" occurring in the first cycle is 12%; the first probability value for "configuration error failure" occurring in the first cycle is 16%; the first probability value for "standby unavailability failure" occurring in the first cycle is 17%; the first probability value for "standby mechanism unreliability failure" occurring in the first cycle is 18%; the first probability value for "Class A failure" occurring in the first cycle is 20%; and the first probability value for "Class B failure" occurring in the first cycle is 22%, etc.

[0056] Step 204: The fault diagnosis device determines the fault diagnosis priority for each fault type based on the first probability value and the second probability value of each fault type.

[0057] In one possible implementation, the fault diagnosis device determines the difference in probability value for each fault type between a first period and a second period. The device compares this difference with a preset threshold, adjusts the priority of each fault type in the first fault work order set, and determines the corresponding diagnosis priority for each fault type in each first fault work order set.

[0058] In one example, the fault diagnosis device adjusts the diagnosis priority of each fault type within each network element category based on the change in probability of each type of fault within the first and second periods, and by judging the relationship between the change in probability and a preset threshold, thus determining the final diagnosis priority. Table 1 shows the diagnosis priority of each fault type within a boundary network element, taking the boundary network element category as an example.

[0059] Table 1. Priority of Fault Diagnosis for Boundary Network Elements

[0060]

[0061] The above scheme brings at least the following beneficial effects: The fault work order investigation device acquires a first set of fault work orders and a second set of fault work orders for the target network element within a first period and a second period. The first set of work orders includes fault work orders for each fault type of the target network element within the first period, and the second set of work orders includes fault work orders for each fault type of the target network element within the second period. The fault work order investigation device determines a first probability value corresponding to each fault type in the first set of fault work orders within the first period, and a second probability value corresponding to each fault type in the second set of fault work orders within the second period. Based on the first and second probability values ​​corresponding to each fault type, the fault work order investigation device determines the investigation priority for each fault type. In this way, by comparing the changes in the probability values ​​corresponding to each fault type within the same network element category in two adjacent time periods, the fault work order investigation device determines the investigation priority for each fault type within the same network element. This solves the technical problem of rationally arranging the investigation order of various fault types for the same network element.

[0062] Combination Figure 2 ,like Figure 3 As shown, step 202 above, namely, the fault diagnosis device determining the first probability value of each fault type in the first cycle based on the fault work orders of each fault type in the first cycle, can be specifically implemented through the following steps 301-303:

[0063] Step 301: The fault diagnosis device determines the first total value of fault work orders in the first fault work order set.

[0064] In one possible implementation, the fault diagnosis device determines the total number of fault work orders in the first fault work order set, i.e., the first total value.

[0065] In one example, the network element category corresponding to the first set of fault work orders is a boundary network element, and the first total value of the fault work orders in the first set of fault work orders is 1000.

[0066] Step 302: The fault diagnosis device determines the first quantity value of fault work orders for each fault type in the first work order set.

[0067] In one possible implementation, the fault diagnosis device determines the number of fault work orders corresponding to each fault type in each first fault work order set.

[0068] In one example, the network element category corresponding to the first set of fault work orders is a boundary network element. The number of fault work orders for each fault type within the boundary network element set is as follows: 100 work orders for "single point of failure"; 120 work orders for "configuration error failure".

[0069] The number of fault work orders corresponding to "backup unavailability risk" is 140; the number of fault work orders corresponding to "backup mechanism unreliable risk" is 160; the number of fault work orders corresponding to "Category A risk" is 180; and the number of fault work orders corresponding to "Category B risk" is 200.

[0070] Step 303: The fault diagnosis device determines the first probability value of each fault type within the first period based on the ratio of the first quantity value to the first total value of each fault type.

[0071] In one possible implementation, the fault sequencing device calculates the ratio of the number of fault work orders corresponding to each fault type in each first fault work order set, i.e., the first quantity value, to the total number of fault work orders in the first fault work order set, and determines the first probability value corresponding to each fault type in each first fault work order set, i.e., the first probability value corresponding to each fault type = the first quantity value ÷ the first total value.

[0072] In one example, the network element category corresponding to the first set of fault work orders is a boundary network element. Then, the probability of a "single point of failure" occurring within the first period is 10%; the probability of a "configuration error" occurring within the first period is 12%; the probability of a "standby unavailability" occurring within the first period is 14%; the probability of a "standby mechanism unreliable" occurring within the first period is 16%; the probability of a "Class A failure" occurring within the first period is 18%; and the probability of a "Class B failure" occurring within the first period is 20%, etc.

[0073] The above scheme brings at least the following beneficial effects: The fault diagnosis device determines the total number of fault work orders in each first fault work order set within the first period. The fault diagnosis device determines the number of fault work orders corresponding to each fault type in the first fault work order set within the first period. Furthermore, the fault diagnosis device determines a first probability value corresponding to each fault type in each first fault work order set based on the ratio of the number of fault work orders corresponding to each fault type to the total number of fault work orders in the first fault work order set. In this way, the fault diagnosis device performs preliminary priority ranking for each fault type in each first fault set based on the first probability value. This improves the efficiency and accuracy of subsequent fault type priority determination.

[0074] Combination Figure 2 ,like Figure 4 As shown, step 203 above, which is the fault diagnosis device determining the second probability value of each fault type in the second cycle based on the fault work orders of each fault type in the second cycle, can be specifically implemented through the following steps 401-403:

[0075] Step 401: The fault diagnosis device determines the second total value of fault work orders in the second fault work order set.

[0076] In one possible implementation, the fault diagnosis device determines the total number of fault work orders in each first fault work order set within the second cycle, i.e., the second total value.

[0077] In one example, the network element category corresponding to the first set of fault work orders is a boundary network element. The fault investigation device determines that the total number of fault work orders in the boundary network element set during the second period is 3500.

[0078] Step 402: The fault diagnosis device determines the second quantity value of fault work orders for each fault type in the second work order set.

[0079] In one possible implementation, the fault diagnosis device determines the number of fault work orders corresponding to each fault type in each first fault work order set within the second cycle, i.e., the second quantity value.

[0080] In one example, the network element category corresponding to the first set of fault work orders is a boundary network element. The number of fault work orders for each fault type within the boundary network element set is as follows: 420 work orders for "single point of failure"; 560 work orders for "configuration error failure".

[0081] The number of fault work orders corresponding to "backup unavailability risk" is 595; the number of fault work orders corresponding to "backup mechanism unreliable risk" is 630; the number of fault work orders corresponding to "Category A risk" is 700; and the number of fault work orders corresponding to "Category B risk" is 770.

[0082] Step 403: The fault diagnosis device determines the second probability value of each fault type in the second period based on the ratio of the second quantity value to the second total value of each fault type.

[0083] In one possible implementation, the fault diagnosis device calculates the ratio of the second quantity value to the second total value corresponding to each fault type, and determines the second probability value corresponding to each fault type in each first fault work order set within the second period, that is, the second probability value corresponding to each fault type = the second quantity value ÷ the second total value.

[0084] In one example, the network element category corresponding to the first set of fault work orders is a boundary network element. Then, the second probability value for a "single point of failure" occurring within the second period is 12%; the second probability value for a "configuration error" occurring within the second period is 16%; the first probability value for a "backup unavailability" occurring within the second period is 17%; and the first probability value for a "backup mechanism unreliable" occurring within the second period is 18%.

[0085] The probability of a "Category A hazard" occurring within the second period is 20%; the probability of a "Category B hazard" occurring within the second period is 22%, etc.

[0086] The above scheme brings at least the following beneficial effects: The fault diagnosis device determines the total number of fault work orders in each first fault work order set within the second period. The fault diagnosis device determines the number of fault work orders corresponding to each fault type in each first fault work order set within the second period, and a second quantity value. The fault diagnosis device calculates the second probability value corresponding to each fault type in each first fault work order set within the second period. In this way, based on the second probability value corresponding to each fault type in each first fault work order set within the second period, the fault diagnosis device provides data support for subsequent adjustments to the priority ranking of fault types in each first fault work order set, improving the accuracy of the priority ranking of fault types corresponding to each network element category.

[0087] Combination Figure 2 ,like Figure 5 As shown, step 204 above, where the fault diagnosis device determines the fault diagnosis priority for each fault type based on the first and second probability values ​​of each fault type, can be further implemented through the following steps 501-504:

[0088] Step 501: The fault diagnosis device determines the difference between the first probability value and the second probability value for each fault type.

[0089] In one possible implementation, the fault diagnosis device determines the difference between the probability value of each fault class in the first fault work order set during a first time period and the probability value during a second time period.

[0090] In one example, the network element category corresponding to the first set of fault work orders is a boundary network element. Within this network element category, the difference between the first and second probability values ​​for "single point of failure" is 2%; the difference between the first and second probability values ​​for "configuration error failure" is 4%; the difference between the first and second probability values ​​for "backup unavailability failure" is 3%; the difference between the first and second probability values ​​for "unreliable backup mechanism failure" is 2%; the difference between the first and second probability values ​​for "Class A failure" is 2%; and the difference between the first and second probability values ​​for "Class B failure" is 2%.

[0091] Step 502: The fault diagnosis device determines whether the difference is greater than or equal to a preset threshold.

[0092] In one possible implementation, the fault diagnosis device obtains a preset threshold for prioritizing fault diagnosis.

[0093] In one example, the preset threshold is set to 3%. It should be noted that this preset threshold can be dynamically adjusted according to the importance of the network element category.

[0094] Step 503: If the value is greater than or equal to the preset threshold, the fault diagnosis device determines the diagnosis priority of each fault type based on the magnitude of the difference.

[0095] In one possible implementation, if the difference corresponding to a fault type is greater than or equal to a preset threshold, the fault investigation device prioritizes the investigation of that fault type based on the difference corresponding to that fault type.

[0096] In one example, the probability difference for "configuration error risk" is 4%, and the probability difference for "backup unavailability risk" is 3%. The troubleshooting device prioritizes fault types based on the magnitude of the probability difference, meaning "configuration error risk" has a higher priority than "backup unavailability risk".

[0097] Step 504: If the value is less than the preset threshold, the fault diagnosis device determines the troubleshooting priority of each fault type based on the magnitude of the second probability value.

[0098] In one possible implementation, if the difference between the fault types is less than a preset threshold, the fault diagnosis device sorts the priority of the fault types according to the probability value of the fault type in the second period.

[0099] In one example, the probability difference for "single point of failure" is 2%; the probability difference for "unreliable backup mechanism failure" is 2%; the probability difference for "Class A failure" is 2%; and the probability difference for "Class B failure" is 2%. Since the probability differences for all of the above failure types are less than a preset threshold, the fault diagnosis device prioritizes these failures based on the magnitude of the second probability value corresponding to each failure type. The order of these failure priorities from highest to lowest is: "Class B failure," "Class A failure," "unreliable backup mechanism failure," and "single point of failure."

[0100] The above scheme brings at least the following beneficial effects: The fault diagnosis device determines the difference between the first probability value and the second probability value corresponding to each fault type in each first fault work order set. The fault diagnosis device determines whether the difference is greater than a preset threshold. If the difference is greater than or equal to the preset threshold, the fault diagnosis device determines the diagnosis priority of the fault type corresponding to the difference based on the magnitude of the difference. If the difference is less than the preset threshold, the fault diagnosis device determines the diagnosis priority of the fault type based on the magnitude of the second probability value of the fault type. In this way, the fault diagnosis device sorts the priority of each fault type in each network element category according to the probability values ​​of multiple fault types corresponding to each network element category in two consecutive periods, and the difference in probabilities in the two periods, thus improving the accuracy of fault diagnosis priority sorting. At the same time, it also improves the diagnosis efficiency of maintenance personnel.

[0101] Combination Figure 2 ,like Figure 6 As shown, before step 201 above, i.e., before the fault diagnosis device obtains the first fault work order set and the second fault work order set, the following steps 601-603 are also included:

[0102] Step 601: The fault diagnosis device obtains multiple fault work orders within the first and second cycles.

[0103] The fault work order includes: network element category field and fault type field.

[0104] In one possible implementation, the fault diagnosis device acquires multiple fault work orders within a first cycle and a second cycle. Each fault work order contains key fields, including but not limited to, the following: network element ID field, network element category field, fault type field, backup network element information field, and backup network element switching remarks field.

[0105] In one example, the network element ID field is used to distinguish different network elements; the network element category field is used to distinguish the category of network elements; the fault type field is used to characterize the fault type of the fault work order of the network element; the backup network element information field is used to characterize whether the network element has a backup network element; and the backup network element switching remarks field is used to indicate the reason for the failure of the network element to switch to a backup network element.

[0106] It should be noted that the reasons for backup network element switching failure can be classified and defined according to the actual operation of the network element, and no specific limitation is made here.

[0107] Step 602: The fault diagnosis device determines the target network element based on the network element category field.

[0108] In one possible implementation, the fault diagnosis device categorizes multiple fault work orders according to the network element category field. Each network element category corresponds to a first set of fault work orders.

[0109] As an example, network element categories include, but are not limited to, the following: terminal network elements, network device network elements, media network elements, boundary network elements, and intelligent network elements.

[0110] Step 603: The fault diagnosis device determines each fault type in the target network element based on the fault type field.

[0111] In one possible implementation, the fault diagnosis device further classifies the fault work orders in each first fault set according to the fault type field in the fault work order.

[0112] As an example, the fault types corresponding to each first fault set include, but are not limited to, the following: "single point of failure", "configuration error failure", "standby unavailability failure", "standby mechanism unreliability failure", etc.

[0113] It should be noted that the classification of fault types can be done differently depending on the actual application scenario.

[0114] The above scheme brings at least the following benefits: The fault diagnosis device acquires multiple fault work orders within the first cycle. The device categorizes these work orders based on the network element category field, and further classifies the fault types within each network element category. This classification of work orders according to network element category and fault type improves the accuracy of subsequent priority assessment for fault types within the same network element category.

[0115] The above provides a detailed description of the fault diagnosis device involved in the embodiments of this application, as well as the functions of each device in the fault diagnosis device and the interaction between the devices.

[0116] As can be seen, the above mainly describes the technical solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the modules and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0117] This application embodiment can divide the fault diagnosis device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0118] This application provides a fault diagnosis device for executing the method required by any device in the above-described fault diagnosis system. This fault diagnosis device may be the fault diagnosis device involved in this application, or a module within a fault diagnosis device; it may also be a chip within a fault diagnosis device, or other devices used to execute fault diagnosis methods; this application does not limit the specific device used.

[0119] Figure 7 The diagram shown is a structural schematic of a fault diagnosis device provided in an embodiment of this application. The device includes a processing unit 701 and a communication unit 702.

[0120] Processing unit 701 is configured to acquire a first set of fault work orders and a second set of fault work orders; wherein, the first set of fault work orders includes fault work orders for each fault type of the target network element within a first period; the second set of fault work orders includes fault work orders for each fault type of the target network element within a second period; processing unit 701 is further configured to determine a first probability value for each fault type within the first period based on the fault work orders for each fault type within the first period; processing unit 701 is further configured to determine a second probability value for each fault type within the second period based on the fault work orders for each fault type within the second period; processing unit 701 is further configured to determine the fault investigation priority for each fault type based on the first probability value and the second probability value for each fault type.

[0121] Optionally, the processing unit 701 is specifically used to: determine a first total value of fault work orders in the first fault work order set; determine a first quantity value of fault work orders of each fault type in the first work order set; and determine a first probability value of each fault type in the first period based on the ratio of the first quantity value of each fault type to the first total value.

[0122] Optionally, the processing unit 701 is further configured to: determine a second total value of fault work orders in the second fault work order set; determine a second quantity value of fault work orders of each fault type in the second work order set; and determine a second probability value of each fault type in the second period based on the ratio of the second quantity value of each fault type to the second total value.

[0123] Optionally, the processing unit 701 is further configured to: determine the difference between a first probability value and a second probability value for each fault type; determine whether the difference is greater than or equal to a preset threshold; if it is greater than or equal to the preset threshold, determine the investigation priority of each fault type based on the magnitude of the difference; if it is less than the preset threshold, determine the investigation priority of each fault type based on the magnitude of the second probability value.

[0124] Optionally, the processing unit 701 is further configured to: acquire multiple fault work orders within a first cycle and a second cycle; the fault work order includes: a network element category field and a fault type field; determine the target network element based on the network element category field; and determine each fault type in the target network element based on the fault type field.

[0125] This application provides a fault diagnosis device for executing the method required by any device in the above-described fault diagnosis system. This fault diagnosis device may be the fault diagnosis device involved in this application, or a module within a fault diagnosis device; it may also be a chip within a fault diagnosis device, or other devices used to execute fault diagnosis methods; this application does not limit the specific device used.

[0126] This application also provides a computer-readable storage medium storing instructions. When a computer executes these instructions, the computer performs each step of the method flow shown in the above-described method embodiments.

[0127] Embodiments of this application provide a computer program product containing instructions that, when executed on a computer, cause the computer to perform the troubleshooting method described in the above method embodiments.

[0128] Embodiments of this application provide a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled together. The processor is used to run computer programs or instructions to implement the troubleshooting method as described in the above method embodiments.

[0129] The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), registers, hard disks, optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing, or any other form of computer-readable storage medium in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may reside in an application-specific integrated circuit (ASIC). In the embodiments of this application, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0130] Since the apparatus, device, computer-readable storage medium, and computer program product in the embodiments of this application can be applied to the above methods, the technical effects that can be obtained can also be referred to the above method embodiments. The embodiments of this application will not be repeated here.

[0131] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A troubleshooting method characterized by, The method comprises: obtaining a first fault work order set and a second fault work order set; wherein the first fault work order set comprises fault work orders of each fault type of a target network element in a first period; and the second fault work order set comprises fault work orders of the each fault type of the target network element in a second period; determining a first probability value of the each fault type in the first period based on the fault work orders of the each fault type in the first period; determining a second probability value of the each fault type in the second period based on the fault work orders of the each fault type in the second period; determining a difference value between the first probability value and the second probability value of the each fault type; determining whether the difference value is greater than or equal to a preset threshold value; if greater than or equal to the preset threshold value, determining the troubleshooting priority of the each fault type based on the size of the difference value; if less than the preset threshold value, determining the troubleshooting priority of the each fault type based on the size of the second probability value.

2. The method of claim 1, wherein, The method comprises: determining a first total quantity value of the fault work orders in the first fault work order set; determining a first quantity value of the fault work orders of the each fault type in the first fault work order set; determining the first probability value of the each fault type in the first period based on a ratio of the first quantity value of the each fault type to the first total quantity value.

3. The method of claim 1, wherein, The method comprises: determining a second total quantity value of the fault work orders in the second fault work order set; determining a second quantity value of the fault work orders of the each fault type in the second fault work order set; determining the second probability value of the each fault type in the second period based on a ratio of the second quantity value of the each fault type to the second total quantity value.

4. The method of claim 1, wherein, Before the method comprises: obtaining a plurality of the fault work orders in the first period and the second period; the fault work order comprises a network element category field and a fault type field; determining the target network element based on the network element category field; determining the each fault type in the target network element based on the fault type field.

5. A troubleshooting device, characterized by The device comprises a processing unit The processing unit is configured to obtain a first fault work order set and a second fault work order set; wherein the first fault work order set comprises fault work orders of each fault type of a target network element in a first period; and the second fault work order set comprises fault work orders of the each fault type of the target network element in a second period; the processing unit is further configured to determine a first probability value of the each fault type in the first period based on the fault work orders of the each fault type in the first period; The processing unit is further configured to determine a second probability value of each fault type in the second period based on the fault work orders of the fault type in the second period; The processing unit is further configured to determine a difference between the first probability value and the second probability value of each fault type, determine whether the difference is greater than or equal to a preset threshold, and if the difference is greater than or equal to the preset threshold, determine the troubleshooting priority of each fault type based on the size of the difference, and if the difference is less than the preset threshold, determine the troubleshooting priority of each fault type based on the size of the second probability value.

6. The apparatus of claim 5, wherein, The processing unit is specifically configured to: determine a first total value of the fault work orders in the first fault work order set; determine a first quantity value of the fault work orders of each fault type in the first fault work order set; determine the first probability value of each fault type in the first period based on a ratio of the first quantity value of the fault type to the first total value.

7. The apparatus of claim 5, wherein, The processing unit is further specifically configured to: determine a second total value of the fault work orders in the second fault work order set; determine a second quantity value of the fault work orders of each fault type in the second fault work order set; determine the second probability value of each fault type in the second period based on a ratio of the second quantity value of the fault type to the second total value.

8. The apparatus of claim 5, wherein, The processing unit is further configured to: obtain a plurality of the fault work orders in the first period and the second period; the fault work order includes a network element category field and a fault type field; determine the target network element based on the network element category field; determine each fault type in the target network element based on the fault type field.

9. A troubleshooting device, characterized by comprise: a processor and a communication interface; the communication interface and the processor are coupled, and the processor is configured to run computer programs or instructions to implement the troubleshooting method as claimed in any one of claims 1-4.

10. A computer-readable storage medium having stored therein instructions, the computer-readable storage medium comprising: When a computer executes the instructions, the computer executes the troubleshooting method as claimed in any one of claims 1-4.

Images