Fault processing method and device

Abstract

The invention discloses a fault processing method and device, and relates to the technical field of network management and control, and the method comprises the steps: after a root alarm in a network element is reported to a management and control system, analyzing and recognizing a fault which causes a non-atomic function to generate the root alarm in the network element, starting a network element fault diagnosis process, and meanwhile, reporting the fault to the management and control system. The management and control system performs a fault identification process based on network connection after receiving the root alarm in the network element, and eliminates the fault causing the root alarm to be generated by the non-atomic function according to the fault diagnosis state of the network element, so that the fault processing efficiency is improved.

Description

Technical Field

[0001] The present application relates to the technical field of network control and management, and in particular to a method and device for fault handling. Background Art

[0002] The traditional fault handling process is that the management and control system analyzes the alarms obtained from the device to obtain the root alarm of the network connection, and then performs fault diagnosis and processing on the faults associated with the root alarm. Alarms generated by non-atomic functions are generally root alarms, which will cause a large-scale business impact.

[0003] At present, the traditional fault handling process is also used for the faults that cause the root alarm of non-atomic functions, which makes it difficult to quickly handle the faults that cause the root alarm of non-atomic functions. In addition, the traditional fault handling method does not provide a fault handling mechanism that links the network element and the management and control system, and the fault handling efficiency is low. Summary of the invention

[0004] The present application provides a method and device for fault handling, which can quickly handle faults that cause root alarms of non-atomic functions, and at the same time provides a fault handling mechanism that links network elements and management and control systems, thereby improving the efficiency of fault handling.

[0005] In a first aspect, an embodiment of the present application provides a method for troubleshooting, the method comprising:

[0006] The network element performs alarm correlation analysis, obtains the root alarm in the network element and reports it to the management and control system. When the root alarm in the network element is generated by a non-atomic function, the network element analyzes the fault that causes the root alarm and starts the network element fault diagnosis process, and reports the fault to the management and control system at the same time;

[0007] After receiving the root alarm in the network element, the management and control system performs a fault identification process based on the network connection, and clears the fault that causes the root alarm of the non-atomic function according to the network element fault diagnosis status.

[0008] In combination with the first aspect, in one implementation, the network element performs alarm correlation analysis to obtain a root alarm in the network element, including:

[0009] Perform correlation analysis on the alarms within the network element to obtain the root alarm within the network element and the corresponding derived alarms. Isolated alarms are also identified as the root alarms within the network element.

[0010] In combination with the first aspect, in one implementation, reporting a root alarm in a network element to a management and control system includes:

[0011] Report the basic information of the root alarms in the network element, the classification of the alarm sources and the diagnostic status to the management and control system;

[0012] The alarm source classification includes atomic function generation and non-atomic function generation;

[0013] The diagnosis status includes not started, diagnosing, and completed.

[0014] In combination with the first aspect, in one implementation, after receiving the root alarm in the network element, the management and control system performs a network connection-based fault identification process, including:

[0015] The management and control system performs alarm correlation analysis based on network connections based on the root alarms reported by each network element, obtains the root alarms of the network connections and the corresponding derivative alarms, and further analyzes the faults that cause the root alarms of the network connections.

[0016] In combination with the first aspect, in one implementation, if the management and control system receives a network element fault diagnosis result before completing a fault identification process based on a network connection, it includes:

[0017] If the fault that caused the non-atomic function to generate a root alarm has been cleared, the corresponding fault in the control system will be included in the historical fault;

[0018] If the fault that causes the non-atomic function to generate a root alarm has not been cleared, the management and control system updates the information of the fault that causes the non-atomic function to generate a root alarm based on the received network element fault diagnosis result, and manually diagnoses the fault until the fault is cleared.

[0019] In combination with the first aspect, in one implementation, if the management and control system receives a network element fault diagnosis result after completing the fault identification process based on the network connection, it includes:

[0020] The management and control system judges each fault that causes the root alarm of the network connection obtained through analysis to determine whether it is the fault that causes the root alarm of the non-atomic function. If so, the management and control system updates the information of the fault that causes the root alarm of the non-atomic function based on the information of the fault that causes the root alarm of the network connection; if not, the management and control system handles this part of the fault that causes the root alarm of the network connection in a traditional manner.

[0021] After receiving the network element fault diagnosis result, the management and control system executes the process that the management and control system executes when receiving the network element fault diagnosis result before completing the fault identification process based on network connection.

[0022] In combination with the first aspect, in one implementation, updating the information of the fault that causes the non-atomic function to generate a root alarm based on the information of the fault that causes the network connection to generate a root alarm includes:

[0023] The fault-associated alarm information in the information about the fault that causes the non-atomic function to generate a root alarm is updated to the fault-associated alarm information in the information about the fault that causes the network connection to generate a root alarm.

[0024] In combination with the first aspect, in one implementation, if the fault that causes the non-atomic function to generate a root alarm is not cleared, the management and control system updates the information of the fault that causes the non-atomic function to generate a root alarm based on the received network element fault diagnosis result, and the updated information includes:

[0025] Fault diagnosis status and fault diagnosis results.

[0026] In combination with the first aspect, in one implementation, the corresponding fault in the management and control system enters a historical fault, including:

[0027] Based on the received network element fault diagnosis results and corresponding alarm clearing messages, the management and control system updates the corresponding fault diagnosis status, diagnosis result information and status information of all associated alarms in the management and control system, fills in the fault recovery time information, and converts the fault from a current fault to a historical fault.

[0028] In a second aspect, an embodiment of the present application provides a device for fault handling based on any one of the above methods, the device comprising:

[0029] The network element layer analysis module is used to perform correlation analysis on the alarms in the network element, obtain the root alarm in the network element and report it to the management and control system; it is also used to analyze the fault that causes the root alarm and execute the network element fault diagnosis process when the root alarm in the network element is generated by a non-atomic function;

[0030] A network layer analysis module, used to perform a fault identification process based on network connections;

[0031] An update module, used for marking the fault that causes the non-atomic function to generate a root alarm as a historical fault when the fault that causes the non-atomic function to generate a root alarm is successfully cleared; and also used for updating the information of the fault that causes the non-atomic function to generate a root alarm based on the information of the fault that causes the network connection to generate a root alarm when the identified fault that causes the network connection to generate a root alarm is the fault that causes the non-atomic function to generate a root alarm;

[0032] The processing module is used to clear the fault that causes the non-atomic function to generate a root alarm according to the completion sequence of the network element fault diagnosis process and the network connection-based fault identification process.

[0033] The beneficial effects brought by the technical solution provided by the embodiment of the present application include at least:

[0034] After reporting the root alarm in the network element to the management and control system, this method directly analyzes the fault that causes the non-atomic function to generate the root alarm in the network element and starts the network element fault diagnosis process, and reports the fault to the management and control system at the same time. Compared with the traditional fault identification and diagnosis process, there is no need to wait for the management and control system to analyze the root and derivative relationships between the alarms reported by each network element before identifying the fault that causes the network connection root alarm (wherein the root alarm includes the root alarm generated by the non-atomic function), and finally diagnose and process the fault, which greatly shortens the identification and diagnosis time of the fault that causes the non-atomic function to generate the root alarm. At the same time, the rapid fault handling mechanism provided by this method does not affect the traditional fault identification and diagnosis process, and cooperates with the traditional fault identification process to improve the fault handling efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 A flowchart of a method for troubleshooting in accordance with the first embodiment of the present application;

[0036] Figure 2 A flowchart of a method for troubleshooting according to a second embodiment of the present application;

[0037] Figure 3 A flowchart of a method for troubleshooting in accordance with the third embodiment of the present application;

[0038] Figure 4 A schematic diagram of the structure of a device for troubleshooting according to an embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0040] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0041] First, please refer to Figure 1 , Figure 1 This is a flowchart of a method for troubleshooting in the first embodiment of the present application. The method for troubleshooting provided in this embodiment includes the following steps:

[0042] Step S1: The network element performs alarm correlation analysis, obtains the root alarm in the network element and reports it to the management and control system.

[0043] Step S2: When the root alarm in the network element is generated by a non-atomic function, the network element analyzes the fault that causes the root alarm in the network element and starts the network element fault diagnosis process, and reports the fault to the management and control system.

[0044] Step S3: The management and control system starts a fault identification process based on network connection.

[0045] Step S4: The management and control system determines the completion status of the network element fault diagnosis process and the network connection-based fault identification process. If the network element fault diagnosis process is completed first, the process proceeds to step S5. Otherwise, the process proceeds to step S8.

[0046] Step S5: The management and control system determines whether the fault that caused the root alarm of the non-atomic function to be generated has been successfully cleared based on the received network element fault diagnosis results and the corresponding alarm clearing message. If so, proceed to step S6; if not, proceed to step S7.

[0047] Step S6: The corresponding fault in the management and control system enters the historical fault, and the process ends.

[0048] Step S7: The management and control system updates the information of the fault that causes the non-atomic function to generate the root alarm based on the received network element fault diagnosis result, and performs manual diagnosis on the fault until the fault is cleared, after which the process ends.

[0049] Step S8: The management and control system determines each fault resulting from the analysis that causes the network connection to generate a root alarm, and determines whether it is a fault that causes a non-atomic function to generate a root alarm. If so, proceed to step S9; if not, proceed to step S10.

[0050] Step S9: based on the information about the failure that causes the network connection to generate a root alarm, update the information about the failure that causes the non-atomic function to generate a root alarm, and then proceed to step S5.

[0051] Step S10: The management and control system handles the failure that causes the root alarm of the network connection in a traditional manner, and the process ends.

[0052] It should be noted that the atomic functions in the above steps refer to functions related to signal transmission in the device, including adaptation, termination and connection, etc. Non-atomic functions refer to objects other than atomic functions in the device, such as devices and boards.

[0053] After reporting the root alarm in the network element to the management and control system, this method directly analyzes the fault that causes the non-atomic function to generate the root alarm in the network element and starts the network element fault diagnosis process, and reports the fault to the management and control system at the same time. Compared with the traditional fault identification and diagnosis process, there is no need to wait for the management and control system to analyze the root and derivative relationships between the alarms reported by each network element before identifying the fault that causes the network connection to generate the root alarm (wherein the root alarm includes the root alarm generated by the non-atomic function), and finally diagnose the fault, which greatly shortens the identification and diagnosis time of the fault that causes the non-atomic function to generate the root alarm. At the same time, the rapid fault handling mechanism provided by this method does not affect the traditional fault identification and diagnosis process, and cooperates with the traditional fault identification process to improve the fault handling efficiency.

[0054] In some embodiments, in the above step S1, the network element performs alarm correlation analysis to obtain the root alarm in the network element, including the following steps:

[0055] Perform correlation analysis on the alarms within the network element to obtain the root alarm within the network element and the corresponding derived alarms. Isolated alarms are also identified as the root alarms within the network element.

[0056] In some embodiments, in the above step S1, reporting the root alarm of the network element to the management and control system includes the following steps:

[0057] Report the basic information of the root alarm within the network element, the classification of the alarm source and the diagnostic status to the management and control system.

[0058] Alarm source classification includes atomic function generation and non-atomic function generation.

[0059] The diagnosis status includes Not Enabled, Diagnosing, and Completed.

[0060] It should be noted that when the alarm source of the root alarm is classified as a non-atomic function, the diagnostic status is valid.

[0061] In some embodiments, in the above steps S2-S9, the fault information includes basic fault information, fault handling suggestions, fault-related alarm information, fault diagnosis status and fault diagnosis results, etc.

[0062] The above basic fault information includes fault serial number, fault name, fault status, fault occurrence time and fault recovery time.

[0063] The alarm information associated with the above fault includes the root alarm information and its derived alarm information.

[0064] The above fault diagnosis status includes not started, diagnosing and completed.

[0065] It should be noted that when the fault diagnosis status is not enabled or in diagnosis, the fault diagnosis result is empty.

[0066] In some embodiments, in the above step S6, the corresponding fault in the management and control system enters the historical fault, including the following steps:

[0067] The fault diagnosis status in the information of the fault that causes the root alarm of the non-atomic function will be updated to completed, the network element fault diagnosis results will be added to the fault diagnosis results based on the network connection, all alarm states associated with the fault will be refreshed (cleared), the alarm recovery time will be refreshed, and after the fault recovery time is filled in, the fault will be transferred from the current fault to the historical fault.

[0068] In some embodiments, in the above step S7, the management and control system updates the information of the fault that causes the non-atomic function to generate the root alarm based on the received network element fault diagnosis result, including the following steps:

[0069] The fault diagnosis status is updated to completed, and the network element fault diagnosis result is added to the fault diagnosis result based on the network connection.

[0070] In some embodiments, in the above step S9, updating the information of the fault that causes the non-atomic function to generate the root alarm based on the information of the fault that causes the network connection to generate the root alarm includes the following steps:

[0071] The information of the root alarm and the derived alarm associated in the information of the fault causing the non-atomic function to generate the root alarm is updated to the information of the root alarm and the derived alarm associated in the information of the fault causing the network connection to generate the root alarm.

[0072] In a more specific embodiment, please refer to Figure 2 , Figure 2 This is a flowchart of the method for troubleshooting in the second embodiment of the present application. Assuming that the network element fault diagnosis process in the above step S4 is completed before the fault identification process based on the network connection, the specific implementation steps of this embodiment are as follows:

[0073] Step A01: Each network element monitors the alarms generated by the network element.

[0074] Step A02: For any network element, the network element performs correlation analysis on each alarm generated in the network element, obtains a root alarm in the network element, and determines whether the root alarm is an alarm generated by a non-atomic function.

[0075] Specifically, in this embodiment, there is a networking relationship between the first network element and the second network element, the "temperature is too high" alarm and the "transmitted optical power is too low" alarm are generated in the first network element, and the "received optical power is too low" alarm is generated in the second network element. The first network element and the second network element respectively perform correlation analysis on the alarms generated in the network elements, and the first network element analyzes and concludes that the "temperature is too high" alarm is the root alarm of the "transmitted optical power is too low" alarm, that is, the "temperature is too high" alarm is the root alarm of the first network element, and the "received optical power is too low" alarm in the second network element is an isolated alarm, and the "received optical power is too low" alarm is used as the root alarm of the second network element.

[0076] Subsequently, it is determined that the "overtemperature" root alarm corresponding to the first network element is an alarm generated by a non-atomic function.

[0077] Step A03: Each network element reports the root alarm in the network element to the management and control system.

[0078] Specifically, the first network element reports an "overtemperature" alarm to the control system, and the reported information includes but is not limited to:

[0079] Alarm name: Over temperature alarm.

[0080] Alarm clearing status: Not cleared.

[0081] Alarm location information: first network element.

[0082] Alarm occurrence time: yy-mm-dd hh:mm:ss.

[0083] Alarm clearing time: empty.

[0084] Alarm source classification: non-atomic function.

[0085] Diagnostic status: Under diagnosis.

[0086] The second network element reports the "received optical power is too low" alarm to the management and control system. The reported information includes but is not limited to:

[0087] Alarm name: Received optical power too low alarm.

[0088] Alarm clearing status: Not cleared.

[0089] Alarm location information: second network element-x single disk-y port.

[0090] Alarm occurrence time: yy-mm-dd hh:mm:ss.

[0091] Alarm clearing time: empty.

[0092] Alarm source classification: atomic function.

[0093] Step A04: When the root alarm in the network element is an alarm generated by a non-atomic function, each network element analyzes the fault that causes the root alarm and starts the network element fault diagnosis process, and reports the fault to the management and control system.

[0094] Specifically, the first network element analyzes and finds that the fault that causes the "overtemperature" alarm is a "hardware fault". The network element starts a diagnostic process for the "hardware fault" and reports the "hardware fault" to the management and control system.

[0095] "Hardware failure" information includes but is not limited to:

[0096] Fault serial number: 1222.

[0097] Fault name: Hardware failure.

[0098] Fault status: Not recovered.

[0099] Fault occurrence time: yy-mm-dd hh:mm:ss.

[0100] Failure recovery time: empty.

[0101] Fault-related alarms: "Overtemperature" alarm and the information corresponding to the alarm, "Transmit optical power too low" derived alarm of the first network element corresponding to the "Overtemperature" alarm and the information corresponding to the alarm.

[0102] Fault diagnosis status: in diagnosis.

[0103] Fault diagnosis result: empty.

[0104] Step A05: The management and control system starts a fault identification process based on network connection, and analyzes and obtains the fault that causes the root alarm of the network connection.

[0105] Specifically, the management and control system analyzes the root and derivative relationships between the "temperature is too high" alarm reported by the first network element and the "received optical power is too low" alarm reported by the second network element, and concludes that the "temperature is too high" alarm of the first network element is the root alarm of the "received optical power is too low" of the second network element, that is, the root alarm based on the network connection is the "temperature is too high" alarm. Analysis shows that the fault that causes the root alarm is a "hardware fault."

[0106] Step A06: When the above network element fault diagnosis process is completed before the fault identification process based on network connection, the first network element reports the network element fault diagnosis result to the management and control system after the network element fault diagnosis process is completed.

[0107] Specifically, in this embodiment, the diagnosis result of the "hardware failure" of the first network element is a fan failure, and the fan disk needs to be replaced.

[0108] Step A07: The management and control system determines whether the fault of the first network element and the associated alarms are successfully cleared according to the received network element fault diagnosis results and the status of the associated alarms. If so, it proceeds to step A08; if not, it proceeds to step A09.

[0109] Step A08: The corresponding fault in the management and control system enters the historical fault.

[0110] Specifically, the fault diagnosis status (completed), fault diagnosis result, fault recovery time and clearing time of each alarm in the fault-related alarm in the fault information corresponding to the "hardware fault" are updated to convert the fault from a current fault to a historical fault.

[0111] Step A09: The management and control system updates the fault information of the fault based on the received network element fault diagnosis result, and starts manual diagnosis of the fault in the management and control system.

[0112] Specifically, the fault diagnosis status and fault diagnosis results in the fault information corresponding to the "hardware fault" are updated. At the same time, the management and control system initiates a manual diagnosis operation for the fault, which in this embodiment involves manually going down to the station to replace the fan disk.

[0113] In a more specific embodiment, please refer to Figure 3 , Figure 3 This is a flowchart of a method for troubleshooting in the third embodiment of the present application. Assuming that the network element fault diagnosis process in step S4 is completed after the fault identification process based on network connection, the specific implementation steps of this embodiment are as follows:

[0114] Steps B01-B05 are the same as steps A01-A05 in the second embodiment, and thus will not be described again.

[0115] Step B06: When the network connection-based fault identification process is completed before the network element fault diagnosis process, the management and control system judges each fault analyzed that causes the network connection to generate a root alarm to determine whether it is a fault that causes a non-atomic function to generate a root alarm. If so, go to step B07; if not, go to step B11.

[0116] Step B07: Update the information of the fault causing the non-atomic function to generate the root alarm based on the information of the fault causing the network connection to generate the root alarm.

[0117] Specifically, the derived alarm information of "received optical power is too low" of the second network element is added to the alarm associated with "hardware failure".

[0118] Step B08: After the network element fault diagnosis process is completed, determine whether the faults that cause the non-atomic function to generate the root alarm are all cleared successfully. If so, go to step B09; if not, go to step B10.

[0119] Step B09: The corresponding fault in the management and control system enters the historical fault.

[0120] Specifically, the fault diagnosis status (completed), fault diagnosis result, fault recovery time, and clearing time of each alarm in the fault-related alarms in the fault information corresponding to the "hardware fault" are updated.

[0121] Step B10: The management and control system updates the fault diagnosis status (completed) and fault diagnosis results in the fault information that causes the non-atomic function to generate a root alarm, and starts manual diagnosis of the fault in the management and control system.

[0122] Step B11: The management and control system handles the failure that causes the root alarm of the network connection in a traditional manner.

[0123] Second, please refer to Figure 4 , Figure 4 This is a schematic diagram of the structure of the device for fault handling in the embodiment of the present application. The device for fault handling provided in this embodiment includes the following modules:

[0124] The network element layer analysis module is used to perform correlation analysis on the alarms within the network element, obtain the root alarm within the network element and report it to the management and control system; it is also used to analyze the fault that causes the root alarm when the root alarm in the network element is generated by a non-atomic function and execute the network element fault diagnosis process.

[0125] The network layer analysis module is used to perform the fault identification process based on network connections.

[0126] An update module is used to mark the fault that causes the root alarm of the non-atomic function as a historical fault when the fault that causes the root alarm of the non-atomic function is successfully cleared; and is also used to update the information of the fault that causes the root alarm of the non-atomic function based on the information of the fault that causes the root alarm of the network connection when the identified fault that causes the root alarm of the network connection is the fault that causes the root alarm of the non-atomic function.

[0127] The processing module is used to clear the fault that causes the non-atomic function to generate a root alarm according to the completion of the network element fault diagnosis process and the fault identification process based on the network connection.

[0128] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

[0129] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.

[0130] In the description of the embodiments of the present application, "exemplary", "for example" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary", "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.

[0131] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; the “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0132] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0133] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.

[0134] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A method for troubleshooting, characterized in that: The method comprises: The network element performs alarm correlation analysis, obtains the root alarm in the network element and reports it to the management and control system. When the root alarm in the network element is generated by a non-atomic function, the network element analyzes the fault that causes the root alarm and starts the network element fault diagnosis process, and reports the fault to the management and control system at the same time; After receiving the root alarm in the network element, the management and control system performs a fault identification process based on the network connection, and clears the fault that causes the root alarm of the non-atomic function according to the network element fault diagnosis status.

2. The method for troubleshooting according to claim 1, characterized in that: The network element performs alarm correlation analysis to obtain a root alarm in the network element, including: Perform correlation analysis on the alarms within the network element to obtain the root alarm within the network element and the corresponding derived alarms. Isolated alarms are also identified as the root alarms within the network element.

3. The method for troubleshooting according to claim 1, characterized in that: Report root alarms in network elements to the management and control system, including: Report the basic information of the root alarms in the network element, the classification of the alarm sources and the diagnostic status to the management and control system; The alarm source classification includes atomic function generation and non-atomic function generation; The diagnosis status includes not started, diagnosing, and completed.

4. The method for troubleshooting according to claim 1, characterized in that: After receiving the root alarm in the network element, the management and control system performs a fault identification process based on the network connection, including: The management and control system performs alarm correlation analysis based on network connections based on the root alarms reported by each network element, obtains the root alarms of the network connections and the corresponding derivative alarms, and further analyzes the faults that cause the root alarms of the network connections.

5. The method for troubleshooting according to claim 1, characterized in that: If the management and control system receives the network element fault diagnosis results before completing the network connection-based fault identification process, including: If the fault that caused the non-atomic function to generate a root alarm has been cleared, the corresponding fault in the control system will be included in the historical fault; If the fault that causes the non-atomic function to generate a root alarm has not been cleared, the management and control system updates the information of the fault that causes the non-atomic function to generate a root alarm based on the received network element fault diagnosis result, and manually diagnoses the fault until the fault is cleared.

6. The method for troubleshooting according to claim 1, characterized in that: If the management and control system receives the network element fault diagnosis results after completing the fault identification process based on network connection, including: The management and control system judges each fault resulting from the analysis that causes the network connection to generate a root alarm, and if it is the fault that causes the non-atomic function to generate a root alarm, the management and control system updates the information of the fault that causes the non-atomic function to generate a root alarm based on the information of the fault that causes the network connection to generate a root alarm; After receiving the network element fault diagnosis result, the management and control system executes the process that the management and control system executes when receiving the network element fault diagnosis result before completing the fault identification process based on network connection.

7. The method for troubleshooting according to claim 6, characterized in that: The updating of the information of the fault causing the non-atomic function to generate the root alarm based on the information of the fault causing the network connection to generate the root alarm includes: The fault-associated alarm information in the information about the fault that causes the non-atomic function to generate a root alarm is updated to the fault-associated alarm information in the information about the fault that causes the network connection to generate a root alarm.

8. The method for troubleshooting according to claim 5, characterized in that: If the fault that causes the non-atomic function to generate a root alarm has not been cleared, the management and control system updates the information of the fault that causes the non-atomic function to generate a root alarm based on the received network element fault diagnosis result, and the updated information includes: Fault diagnosis status and fault diagnosis results.

9. The method for troubleshooting according to claim 5, characterized in that: The corresponding faults in the control system are entered into historical faults, including: Based on the received network element fault diagnosis results and corresponding alarm clearing messages, the management and control system updates the corresponding fault diagnosis status, diagnosis result information and status information of all associated alarms in the management and control system, fills in the fault recovery time information, and converts the fault from a current fault to a historical fault.

10. A device for handling faults based on the method according to any one of claims 1 to 9, characterized in that: The device comprises: The network element layer analysis module is used to perform correlation analysis on the alarms in the network element, obtain the root alarm in the network element and report it to the management and control system; it is also used to analyze the fault that causes the root alarm and execute the network element fault diagnosis process when the root alarm in the network element is generated by a non-atomic function; A network layer analysis module, used to perform a fault identification process based on network connections; An update module, used for marking the fault causing the non-atomic function to generate a root alarm as a historical fault when the fault causing the non-atomic function to generate a root alarm is successfully cleared; and also used for updating the information of the fault causing the non-atomic function to generate a root alarm based on the information of the fault causing the network connection to generate a root alarm when the identified fault causing the network connection to generate a root alarm contains the fault causing the non-atomic function to generate a root alarm; The processing module is used to clear the fault that causes the non-atomic function to generate a root alarm according to the completion sequence of the network element fault diagnosis process and the network connection-based fault identification process.

Images