Communication equipment fault root cause diagnosis method and system based on troubleshooting tree

Abstract

The invention discloses a communication equipment fault root cause diagnosis method and system based on a troubleshooting tree, and relates to the technical field of rail transit communication equipment fault diagnosis. Comprising the following steps: providing a fault workflow menu, and configuring a troubleshooting process in a tree structure; configuring a topological association relationship of the equipment; presetting an abnormal rule of the equipment; collecting alarm and performance data of the equipment in real time, and storing the alarm and performance data; when a fault alarm is received, executing in sequence according to a fault checking tree preset by the system and the equipment topology, and finally positioning a fault root cause; and recording the condition of the fault, the troubleshooting step and the root cause positioning result, and generating a fault report. According to the invention, through customizing the troubleshooting tree and the equipment topology, in combination with alarm and performance data collected by the equipment and feedback of field maintenance personnel, rapid root cause positioning of the fault is realized, and the fault solving efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of rail transit communication equipment fault diagnosis, and in particular to a communication equipment fault root cause diagnosis method and system based on a fault troubleshooting tree. Background Art

[0002] In the early stages of the development of the rail transit industry, the focus was often on infrastructure construction and the introduction of high-end equipment. However, with the rapid expansion of the rail transit network, the huge scale of the network has led to a surge in the number of operating equipment and facilities, which in turn has led to a sharp increase in the amount of maintenance tasks; at the same time, the existing line equipment has gradually aged due to long-term operation, posing a severe test to the guarantee of service reliability; in addition, the continuous commissioning of new lines and the instability of their initial equipment operation have further aggravated the complexity and difficulty of operation and maintenance.

[0003] Faced with this series of operation and maintenance pressures, the rail transit industry urgently needs to change its traditional operation and maintenance ideas and move towards intelligent, automated, and precise management. This requires us to strengthen the in-depth mining and analysis of data while improving the efficiency of networked operations, and use advanced information technology to achieve intelligent decision-making and automated execution of operation and maintenance work. By accurately identifying potential faults and quickly responding to operation and maintenance needs, it can not only effectively alleviate the pressure of operation and maintenance, but also significantly improve service reliability and passenger satisfaction, and promote the rail transit industry to develop in a more efficient, safe, and sustainable direction.

[0004] Traditional operation and maintenance method: Each line has a control center network management room, equipped with a centralized alarm platform, which is connected to the network management of each subsystem to realize the collection and unified display and analysis of alarm data. When the duty officer finds a fault alarm reported by a subsystem on the centralized alarm platform, he must first go to the subsystem network management side to review the fault and confirm whether the fault really exists. The next step is to notify the maintenance personnel of the work team by phone or DingTalk to handle the fault. The traditional fault operation and maintenance process has the following disadvantages: the centralized alarm platform only collects and summarizes the alarm data of the equipment, but does not provide any fault location and guidance; equipment failures are often not single equipment failures, and they must be located by relying on the networking architecture of the equipment. The traditional multi-subsystem network management is independent of each other, and multiple network management must be analyzed in turn, which seriously affects the speed of fault location; the equipment not only has alarm data, but also a large amount of performance data, which has not been effectively integrated and utilized; after the fault is solved, the fault library is not automatically formed, and knowledge accumulation and transmission cannot be effectively carried out.

[0005] Therefore, it is an urgent problem for those skilled in the art to propose a method and system for diagnosing the root cause of a communication device fault based on a fault troubleshooting tree to solve the difficulties existing in the prior art. Summary of the invention

[0006] In view of this, the present invention provides a method and system for diagnosing the root cause of communication equipment faults based on a troubleshooting tree. By customizing the troubleshooting tree and equipment topology, combined with the alarms and performance data collected by the equipment and the feedback from on-site maintenance personnel, the root cause of the fault can be quickly located, thereby improving the efficiency of fault resolution.

[0007] In order to achieve the above object, the present invention adopts the following technical solution:

[0008] A method for diagnosing root causes of communication equipment faults based on a fault troubleshooting tree, comprising:

[0009] S101. Provide a fault workflow menu and configure the fault troubleshooting process in a tree structure;

[0010] S102, configuring the topological association relationship of the device;

[0011] S103, abnormal rules for prefabricated equipment;

[0012] S104, collecting alarms and performance data of the equipment in real time and storing them;

[0013] S105, when a fault alarm is received, the fault troubleshooting tree and device topology prefabricated by the system are executed in sequence, and the root cause of the fault is finally located;

[0014] S106: Record the details of the fault, troubleshooting steps, and root cause location results, and generate a fault report.

[0015] The above method is optional. In S101, the troubleshooting process is based on the alarm type as a dimension. For each type of alarm, a troubleshooting process is sorted out based on operation and maintenance experience, and maintenance is performed in the system.

[0016] The key nodes for drawing a troubleshooting tree are: start node, end node, test node, and result node. Each test node is configured with two types: system self-collection and on-site manual feedback.

[0017] For nodes collected by the system itself, configure the device type, alarm and performance parameters, determine which performance parameter to use to determine the result of the node, and decide the direction of the execution result.

[0018] In the above method, optionally, in S102, a topological association relationship of devices is configured, and a topology is created automatically or manually with devices as a dimension;

[0019] Automatic mode: supports automatic discovery of new devices and links through the LLDP protocol;

[0020] Manual method: manually maintain the association relationship of devices through the interface, and form a device topology diagram based on the port;

[0021] Each link relationship includes: source device name, source device port, target device name, target device port, and upstream and downstream tags.

[0022] In the above method, optionally, in S103, abnormal rules of the device are preset to determine whether the operation data of the device is normal, and the abnormal rules are set according to the state quantity and the analog quantity respectively.

[0023] The above method may optionally include collecting and storing alarms and performance data of the device in real time in S104;

[0024] Alarm and performance data collection method: For subsystem devices, connect to each subsystem gateway through the http private interface; for general IT equipment, obtain through snmp;

[0025] The core fields of the alarm include: device name, specific alarm board port, alarm description, alarm level, and alarm occurrence time;

[0026] The core fields of performance data include: device name, specific alarm board port, performance parameter name, current value, and collection time.

[0027] The above method is optional. In S105, when a fault alarm is received, the fault troubleshooting tree and device topology prefabricated by the system are executed in sequence to finally locate the root cause of the fault.

[0028] In the troubleshooting step of the troubleshooting tree, check the alarms or performance parameters of the current device type. When analyzing the specific root cause, find the related devices of the same device type based on the topology of the faulty device and convert them into alarms and performance parameters of specific devices.

[0029] The troubleshooting process that cannot be automatically collected by the system is solved through video analysis, and manual feedback is used to record the results on the system.

[0030] The above method is optional, device alarm: check whether there is an alarm in the time period, if yes, it means that the device is abnormal, if no, it means that the device is normal;

[0031] Equipment performance parameters: Configure the exception rules for each type of parameter. The system collects performance data within the time period, matches the exception rules, and gives judgments on whether the equipment is normal or abnormal.

[0032] Manual feedback results: directly judged and stored in the system.

[0033] The above method optionally records the details of the fault, troubleshooting steps, and root cause location results in S106, generates a fault report, and generates a fault database to store fault information to assist in handling the same type of fault next time.

[0034] A communication device fault root cause diagnosis system based on a fault troubleshooting tree, performing any of the above communication device fault root cause diagnosis methods based on a fault troubleshooting tree, comprising:

[0035] Intelligent operation and maintenance platform, visualization interface and subsystem network management;

[0036] The intelligent operation and maintenance platform and subsystem network management obtain fault alarm information and equipment performance status data through interfaces;

[0037] The intelligent operation and maintenance platform provides a fault workflow menu and supports the topological association relationship of the configuration equipment;

[0038] Visual interface to realize the whole process of fault tree arrangement, equipment topology drawing and fault root cause location;

[0039] Subsystem network management: provides equipment failure and performance status data.

[0040] It can be seen from the above technical solution that, compared with the prior art, the present invention provides a method and system for diagnosing the root cause of communication equipment faults based on a fault troubleshooting tree, which has the following beneficial effects: within the framework of the intelligent operation and maintenance platform, the present invention constructs a fault troubleshooting tree for each type of fault, automatically constructs and dynamically adjusts the equipment topology relationship diagram, not only captures and stores the alarm information and performance parameters of the equipment in real time, but also cleverly integrates the information fed back by on-site manual work, forming a comprehensive and multi-dimensional fault analysis perspective; through the comprehensive use of multi-dimensional data, it can quickly and accurately locate the source of the fault, and automatically or assist in formulating efficient fault handling plans; it greatly improves the automation level of system operation, effectively reduces the workload of operation and maintenance personnel, and at the same time significantly shortens the fault response time and improves the fault resolution efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0042] Figure 1 A flow chart of a method for diagnosing root causes of communication equipment faults based on a fault troubleshooting tree provided by the present invention;

[0043] Figure 2 The fault workflow menu interface provided by the present invention;

[0044] Figure 3 The troubleshooting tree program flowchart and execution results provided by the present invention;

[0045] Figure 4 The equipment topology association configuration diagram of the "station hall playback controller" provided by the present invention;

[0046] Figure 5 The device topology diagram of the "station hall playback controller" provided by the present invention;

[0047] Figure 6 This is an exception rule configuration diagram provided by the present invention. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0049] In this application, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of more restrictions, the elements defined by the sentence "comprise one..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0050] Reference Figure 1 As shown, the present invention discloses a method for diagnosing the root cause of a communication device fault based on a fault troubleshooting tree, comprising:

[0051] S101. Provide a fault workflow menu and configure the fault troubleshooting process in a tree structure;

[0052] S102, configuring the topological association relationship of the device;

[0053] S103, abnormal rules for prefabricated equipment;

[0054] S104, collecting alarms and performance data of the equipment in real time and storing them;

[0055] S105, when a fault alarm is received, the fault troubleshooting tree and device topology prefabricated by the system are executed in sequence, and the root cause of the fault is finally located;

[0056] S106: Record the details of the fault, troubleshooting steps, and root cause location results, and generate a fault report.

[0057] Further, see Figure 2 As shown, in S101, the intelligent operation and maintenance platform provides a fault workflow menu, supports the configuration of the fault troubleshooting process in a tree structure, and the fault troubleshooting process is based on the alarm type. For each type of alarm, a fault troubleshooting process is sorted out based on the operation and maintenance experience, and maintained in the system;

[0058] Further, refer to Figure 3 As shown, the key nodes for drawing a troubleshooting tree are: start node (oval), end node (oval), check node (diamond), and result node (rectangle);

[0059] Each inspection node can be configured in two types: system self-collection and on-site manual feedback;

[0060] For nodes that the system collects data for itself, you need to configure the device type, alarm, or performance parameters, that is, determine which performance parameter to use to determine the result of the node and decide the direction of the execution result.

[0061] Further, in S102, the topological association relationship of the devices is configured, and the topology is created automatically or manually with the devices as the dimension;

[0062] Automatic mode: supports automatic discovery of new devices and links through the LLDP protocol;

[0063] Manual method: manually maintain the association relationship of devices through the interface, and form a device topology diagram based on the port;

[0064] Each link relationship includes: source device name, source device port, target device name, target device port, and upstream and downstream tags.

[0065] Further, refer to Figure 4 As shown, the station hall playback controller is associated. It can be seen that the power timing controller provides power supply protection for it, the H3C switch provides network protection for it, and the station server is its upstream equipment. Figure 5 As shown, the device topology diagram of the "station hall playback controller" is finally obtained.

[0066] Further, see Figure 6 As shown, in S103, abnormal rules of the equipment are prefabricated to determine whether the operation data of the equipment is normal, and the abnormal rules are set according to the state quantity and the analog quantity.

[0067] Furthermore, in S104, alarms and performance data of the equipment are collected in real time and stored;

[0068] Alarm and performance data collection method: For subsystem devices, connect to each subsystem gateway through the http private interface; for general IT equipment, obtain through snmp;

[0069] The core fields of the alarm include: device name, specific alarm board port, alarm description, alarm level, and alarm occurrence time;

[0070] The core fields of performance data include: device name, specific alarm board port, performance parameter name, current value, and collection time.

[0071] Furthermore, in S105, when a fault alarm is received, the fault troubleshooting tree and device topology prefabricated by the system are executed in sequence, and the root cause of the fault is finally located.

[0072] Furthermore, the troubleshooting tree is for a class of faults, not for a specific device. Therefore, the troubleshooting steps in the troubleshooting tree can only be defined as: troubleshooting the alarm or performance of a certain device type. When performing a specific root cause analysis, it is necessary to combine the topology of the faulty device, find the related devices of the same device type, and convert them into alarms and performance parameters of specific devices.

[0073] Combined with manual feedback and considering the actual situation on site, some troubleshooting processes cannot be automatically collected by the system, such as checking whether the interface is loose. There are two solutions to this problem: First, solve it through video analysis. The disadvantage is that additional cameras need to be added, which may introduce more fault nodes and increase equipment investment. Second, considering that these troubleshooting steps are few, manual feedback is used to record the results on the system through DingTalk calls.

[0074] The judgment logic of device abnormality is divided into the following categories:

[0075] Manual feedback results: directly judge and store in the system;

[0076] Equipment alarm: Check whether there is an alarm during this time period. If yes, it means the equipment is abnormal. If no, it means the equipment is normal.

[0077] Equipment performance parameters: The intelligent operation and maintenance platform will configure exception rules for each type of parameter, see step C. The system collects performance data within the time period, and then matches the exception rules to make normal or abnormal judgments.

[0078] Furthermore, in S106, the details of the fault, troubleshooting steps, and root cause location results are recorded, a fault report is generated, and a fault database is generated to store fault information to assist in handling the next similar fault.

[0079] A communication equipment fault root cause diagnosis system based on a fault troubleshooting tree, comprising:

[0080] Intelligent operation and maintenance platform, visualization interface and subsystem network management;

[0081] The intelligent operation and maintenance platform and subsystem network management obtain fault alarm information and equipment performance status data through interfaces;

[0082] The intelligent operation and maintenance platform provides a fault workflow menu and supports the topological association relationship of the configuration equipment;

[0083] Visual interface to realize the whole process of fault tree arrangement, equipment topology drawing and fault root cause location;

[0084] Subsystem network management: provides equipment failure and performance status data.

[0085] In a specific embodiment, in the passenger information system, the broadcast controller is offline and it is necessary to check whether the switch network is abnormal. When the station hall broadcast controller (specific device) fails, according to the fault troubleshooting tree, when the diagnostic step is executed, it is necessary to find the device associated with device A, filter the switch type devices, and then check the network parameters to determine whether it is normal.

[0086] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without creative work.

[0087] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for diagnosing the root cause of a communication device fault based on a fault troubleshooting tree, characterized in that: include: S101. Provide a fault workflow menu and configure the fault troubleshooting process in a tree structure; S102, configuring the topological association relationship of the device; S103, abnormal rules for pre-set equipment; S104, collecting alarms and performance data of the equipment in real time and storing them; S105, when a fault alarm is received, the fault troubleshooting tree and device topology preset by the system are executed in sequence, and the root cause of the fault is finally located; S106: Record the fault situation, troubleshooting steps, and root cause location results, and generate a fault report.

2. A method for diagnosing root causes of communication equipment faults based on a fault troubleshooting tree according to claim 1, characterized in that: In S101, the troubleshooting process is based on the alarm type. For each type of alarm, a troubleshooting process is sorted out based on operation and maintenance experience and maintained in the system; The key nodes for drawing a troubleshooting tree are: start node, end node, test node, and result node. Each test node is configured with two types: system self-collection and on-site manual feedback. For nodes collected by the system itself, configure the device type, alarm and performance parameters, determine which performance parameter to use to determine the result of the node, and decide the direction of the execution result.

3. A method for diagnosing root causes of communication equipment faults based on a fault troubleshooting tree according to claim 1, characterized in that: In S102, the topological association relationship of the devices is configured, and the topology is created automatically or manually with the devices as the dimension; Automatic mode: supports automatic discovery of new devices and links through the LLDP protocol; Manual method: manually maintain the association relationship of devices through the interface, and form a device topology diagram based on the port; Each link relationship includes: source device name, source device port, target device name, target device port, and upstream and downstream tags.

4. A method for diagnosing root causes of communication equipment faults based on a fault troubleshooting tree according to claim 1, characterized in that: In S103, abnormal rules of the equipment are prefabricated to determine whether the operation data of the equipment is normal. The abnormal rules are set according to the state quantity and the analog quantity.

5. A method for diagnosing root causes of communication equipment faults based on a fault troubleshooting tree according to claim 1, characterized in that: In S104, alarms and performance data of the equipment are collected in real time and stored; Alarm and performance data collection method: For subsystem devices, connect to each subsystem gateway through the http private interface; for general IT equipment, obtain through snmp; The core fields of the alarm include: device name, specific alarm board port, alarm description, alarm level, and alarm occurrence time; The core fields of performance data include: device name, specific alarm board port, performance parameter name, current value, and collection time.

6. A method for diagnosing root causes of communication equipment faults based on a fault troubleshooting tree according to claim 1, characterized in that: In S105, when a fault alarm is received, the fault troubleshooting tree and device topology prefabricated by the system are executed in sequence, and the root cause of the fault is finally located. In the troubleshooting step of the troubleshooting tree, check the alarms or performance parameters of the current device type. When analyzing the specific root cause, find the related devices of the same device type based on the topology of the faulty device and convert them into alarms and performance parameters of specific devices. The troubleshooting process that cannot be automatically collected by the system is solved through video analysis, and manual feedback is used to record the results on the system.

7. A method for diagnosing root causes of communication equipment faults based on a fault troubleshooting tree according to claim 6, characterized in that: Equipment alarm: Check whether there is an alarm during this time period. If yes, it means the equipment is abnormal. If no, it means the equipment is normal. Equipment performance parameters: Configure the exception rules for each type of parameter. The system collects performance data within the time period, matches the exception rules, and gives judgments on whether the equipment is normal or abnormal. Manual feedback results: directly judged and stored in the system.

8. A method for diagnosing root causes of communication equipment faults based on a fault troubleshooting tree according to claim 1, characterized in that: In S106, the situation, troubleshooting steps, and root cause location results of the fault are recorded, a fault report is generated, and a fault database is generated to store fault information to assist in handling the next similar fault.

9. A communication device fault root cause diagnosis system based on a troubleshooting tree, executing a communication device fault root cause diagnosis method based on a troubleshooting tree according to any one of claims 1 to 8, comprising: Intelligent operation and maintenance platform, visualization interface and subsystem network management; The intelligent operation and maintenance platform and subsystem network management obtain fault alarm information and equipment performance status data through interfaces; The intelligent operation and maintenance platform provides a fault workflow menu and supports the topological association relationship of the configuration equipment; Visual interface to realize the whole process of fault tree arrangement, equipment topology drawing and fault root cause location; Subsystem network management: provides equipment failure and performance status data.

Images