Fault processing method and device, electronic equipment and readable storage medium

Abstract

The application provides a fault processing method and device, electronic equipment and a readable storage medium, and relates to the field of fault processing. The method comprises the following steps: every first preset time length, repeatedly performing the following steps: obtaining the fault occurrence time and the fault type of each fault data; according to the fault occurrence time of each fault data, eliminating each job fault data from all fault data to determine all first fault data; according to the fault type of each first fault data, eliminating the fault data corresponding to the repeated fault type from all first fault data to determine all second fault data, and generating a first display instruction; the job fault data is generated by the fault data caused by the equipment failure due to construction and maintenance within a preset time period; and the first display instruction is used for indicating to display all second fault data. The application can reduce the server load, improve the result display accuracy, provide more accurate fault cause analysis, and thus improve the fault troubleshooting efficiency.

Description

Technical Field

[0001] This invention relates to the field of fault handling, and more particularly to a fault handling method, apparatus, electronic device, and readable storage medium. Background Technology

[0002] Existing fault statistics methods typically categorize all faults and then display the results. However, the displayed results often include a large number of redundant and invalid faults, which affects decision-makers' judgment of the cause of the fault and reduces the efficiency of fault diagnosis. Summary of the Invention

[0003] This invention provides a fault handling method, apparatus, electronic device, and readable storage medium to solve the technical problem that the prior art cannot accurately count real faults, and provides a technical solution for eliminating redundant faults and invalid faults.

[0004] In a first aspect, the present invention provides a fault handling method, comprising:

[0005] Repeat the following steps every first preset time interval:

[0006] Obtain the time of occurrence and type of each fault;

[0007] Based on the time of occurrence of each fault data, remove each job fault data from all fault data to determine all first fault data;

[0008] Based on the fault type of each first fault data, remove the fault data corresponding to the duplicate fault type from all the first fault data, determine all the second fault data, and generate the first display instruction;

[0009] The operational fault data refers to the fault data generated due to equipment failures caused by construction and maintenance within a preset time period;

[0010] The first display instruction is used to instruct the display of all second fault data.

[0011] According to the fault handling method provided by the present invention, the time of occurrence of fault 5 in acquiring each fault data includes:

[0012] Obtain the timestamp of any fault data and determine the time of fault occurrence based on the timestamp; iterate through the timestamps of all fault data to determine the time of fault occurrence for all fault data.

[0013] According to the fault handling method provided by the present invention, when acquiring each fault data, the fault occurrence...

[0014] Before the occurrence time and fault type, it also includes: 0. Obtain all initial fault data, and obtain the fault type of each initial fault data;

[0015] Match the fault type of each initial fault data in the preset shielding library to determine all fault data to be shielded;

[0016] Remove all fault data to be masked from all initial fault data;

[0017] The preset shielding library is constructed based on preset fault types.

[0018] 5. According to the fault handling method provided by the present invention, each fault is removed from all fault data.

[0019] Before the job failure data, it also includes:

[0020] Obtain every historical construction and maintenance period for all historical construction and maintenance work;

[0021] The average value of all historical construction time periods is used to determine the preset time period.

[0022] According to the fault handling method provided by the present invention, the average processing of all historical construction time periods to determine the preset time period includes:

[0023] Obtain the start and end times of each historical construction period;

[0024] Average all start times to determine the average start time, and average all end times to determine the average end time.

[0025] The preset time period is determined based on the average start time and average end time of construction.

[0026] According to the fault handling method provided by the present invention, the step of removing fault data corresponding to duplicate fault types from all first fault data to determine all second fault data includes:

[0027] For each first fault data, if there is a fault data that is identical to the first fault data, the fault data is marked as duplicate fault data;

[0028] Iterate through all first-fault data, remove all duplicate fault data, and determine all second-fault data.

[0029] According to the fault handling method provided by the present invention, after determining all second fault data, the method further includes:

[0030] Every second preset time interval, acquire all second fault data sets within each first preset time interval;

[0031] In all second fault datasets, count the number of faults occurring for each fault type.

[0032] A preset number of fault types are determined based on the number of fault occurrences in descending order, and a second display instruction is generated;

[0033] The second display instruction is used to indicate the display of a preset number of fault types and the number of times the faults occur corresponding to the fault types.

[0034] According to the fault handling method provided by the present invention, after counting the number of faults of all fault types, the method further includes:

[0035] If the number of occurrences of any fault type is greater than or equal to the preset number, an alarm command is generated.

[0036] The alarm command is used to instruct and notify the user terminal.

[0037] Secondly, a fault handling device is provided, comprising:

[0038] Acquisition Unit: Used to acquire the time of occurrence and type of each fault data;

[0039] Determination Unit: Used to remove each job failure data from all failure data based on the failure occurrence time of each failure data, and determine all first failure data;

[0040] Generation unit: used to remove fault data corresponding to duplicate fault types from all first fault data according to the fault type of each first fault data, determine all second fault data, and generate a first display instruction;

[0041] The operational fault data refers to the fault data generated due to equipment failures caused by construction and maintenance within a preset time period;

[0042] The first display instruction is used to instruct the display of all second fault data.

[0043] Thirdly, the present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement any of the fault handling methods described above.

[0044] Fourthly, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the fault handling method as described above.

[0045] The fault handling method, apparatus, electronic device, and readable storage medium provided by this invention use the fault occurrence time and fault type corresponding to the fault data as the determining factors for elimination. Starting from fault data caused by equipment failure due to construction and maintenance, and multiple repeated faults occurring within a preset time, this invention filters the fault data collected within a preset time, thereby reducing the server load, improving the accuracy of result display, providing decision-makers with more accurate fault cause analysis, and thus improving fault troubleshooting efficiency. Attached Figure Description

[0046] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0047] Figure 1 This is one of the flowcharts illustrating the fault handling method provided by the present invention;

[0048] Figure 2 This is a flowchart illustrating the process of obtaining the time of fault occurrence provided by the present invention;

[0049] Figure 3 This is the second flowchart of the fault handling method provided by the present invention;

[0050] Figure 4 This is the third flowchart of the fault handling method provided by the present invention;

[0051] Figure 5 This is a flowchart illustrating the process of determining the preset time period provided by the present invention;

[0052] Figure 6 This is a flowchart illustrating the process of determining all second fault data provided by the present invention;

[0053] Figure 7 This is the fourth flowchart of the fault handling method provided by the present invention;

[0054] Figure 8 This is a schematic diagram of the fault handling device provided by the present invention;

[0055] Figure 9 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0056] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0057] Figure 1 This is one of the flowcharts illustrating the fault handling method provided by the present invention. The present invention provides a fault handling method, including:

[0058] Repeat the following steps every first preset time interval:

[0059] Obtain the time of occurrence and type of each fault;

[0060] Based on the time of occurrence of each fault data, remove each job fault data from all fault data to determine all first fault data;

[0061] Based on the fault type of each first fault data, remove the fault data corresponding to the duplicate fault type from all the first fault data, determine all the second fault data, and generate the first display instruction;

[0062] The operational fault data refers to the fault data generated due to equipment failures caused by construction and maintenance within a preset time period;

[0063] The first display instruction is used to instruct the display of all second fault data.

[0064] In step 101, the fault occurrence time and fault type of each fault data are obtained. In this invention, at regular intervals, all fault data within the interval are statistically analyzed and redundant and duplicate faults are removed. The first preset duration can be 2 hours, 3 hours, 10 hours, etc. The fault occurrence time is the specific time when the fault occurs, such as 13:51:11 on January 2, 2005, or 2:29:34 on July 23, 2021. Taking equipment fault as an example, the fault type can be different fault problems in different equipment systems at different sites. For example, the offline fault of the "Interlocking I System Status" of the computer interlocking subsystem in site A, or the communication interruption fault of the "Interlocking and MSS Communication Status" of the computer interlocking subsystem in site C. This invention can obtain the fault occurrence time and fault type of each fault data from real-time fault monitoring.

[0065] In step 102, based on the fault occurrence time of each fault data, each operational fault data is removed from all fault data to determine all first fault data. Since the equipment will choose to perform equipment repair, maintenance, replacement or other operations when the impact on the user is relatively small, the impact of construction period on fault generation will not be considered for fault display. Therefore, invalid faults will be generated. That is, the fault data is not generated by the equipment due to real faults, but is passively generated due to construction and maintenance. The present invention needs to eliminate the impact of construction period on fault generation based on the fault occurrence time of each fault data. Therefore, each operational fault data is removed from all fault data to determine all first fault data after removing all operational fault data.

[0066] In step 103, based on the fault type of each first fault data, fault data corresponding to duplicate fault types are removed from all first fault data to determine all second fault data and generate a first display instruction. Since the present invention sets a first preset time, if multiple duplicate faults are triggered repeatedly within a unit time, for example, if the same device generates 10 consecutive fault data of the same type within one second, a large amount of redundant fault data will be generated, which will seriously affect the display of fault results. Therefore, in step 103, it is necessary to deduplicate the duplicate faults within a unit time. As an embodiment, step 103 can be executed first and then step 102 can be executed, or step 102 can be executed first and then step 103 can be executed, so that the influence of the fault caused by the construction period and the influence of the large amount of fault data generated by duplicate fault types on the display results are eliminated from all fault data. Finally, all second fault data are determined and a first display instruction is generated. The first display instruction is used to instruct the display terminal to display all second fault data.

[0067] This invention can be applied to rail transit equipment. In existing technologies, firstly, due to the large number of rail transit devices, the massive amount of real-time monitoring data, and the numerous alarm notifications, accurate fault analysis and maintenance suggestions cannot be provided without data analysis. The sheer volume of alarm information makes it impossible to distinguish between genuine fault alarms and accurately locate faults, leading to high maintenance costs and hindering precise fault analysis in fault handling, thus affecting real-time and accurate fault monitoring. Secondly, the acquisition of online equipment status data is passive, typically obtained offline and then imported into a database in file form for analysis. This lack of timeliness and fault early warning means that major faults cannot be prevented in advance. To address these practical problems in rail transit equipment, this invention enables real-time data analysis, accurate judgment of equipment status, prediction of future risks, timely acquisition of actual fault data, faster response times, and delivery of the most accurate equipment status to on-site maintenance personnel to guide on-site repairs, thereby significantly improving operational efficiency.

[0068] The fault handling method, apparatus, electronic device, and readable storage medium provided by this invention use the fault occurrence time and fault type corresponding to the fault data as the determining factors for elimination. Starting from fault data caused by equipment failure due to construction and maintenance, and multiple repeated faults occurring within a preset time, this invention filters the fault data collected within a preset time, thereby reducing the server load, improving the accuracy of result display, providing decision-makers with more accurate fault cause analysis, and thus improving fault troubleshooting efficiency.

[0069] Figure 2 This is a flowchart illustrating the process of obtaining the time of fault occurrence provided by the present invention. The process of obtaining the time of fault occurrence for each fault data point includes:

[0070] Obtain the timestamp of any fault data and determine the time of fault occurrence based on the timestamp;

[0071] Iterate through the timestamps of all fault data to determine the time when the fault occurred for each fault.

[0072] In step 1011, since a corresponding timestamp is generated during the fault data generation process, the present invention needs to convert the timestamp data into fault occurrence time data.

[0073] In step 1012, the timestamps of all fault data are converted into corresponding fault occurrence times. This invention can determine the fault occurrence time of all fault data by collecting the timestamps of all fault data at first preset intervals, or by determining the corresponding fault occurrence time for each time fault data is generated.

[0074] Figure 3 This is a second flowchart illustrating the fault handling method provided by the present invention. Before acquiring the fault occurrence time and fault type for each fault data, it further includes:

[0075] Obtain all initial fault data, and obtain the fault type for each initial fault data;

[0076] Match the fault type of each initial fault data in the preset shielding library to determine all fault data to be shielded;

[0077] Remove all fault data to be masked from all initial fault data;

[0078] The preset shielding library is constructed based on preset fault types.

[0079] In step 201, all initial fault data are obtained, and the fault type of each initial fault data is obtained. Those skilled in the art will understand that when fault data is generated, the fault data is stored in a memory. When analyzing the fault data, all fault data in the memory is extracted to obtain the initial fault data. The fault type of each initial fault data can be the module in which the fault occurred, the cause of the fault, the description of the fault, the measures taken on site after the fault occurred, or the fault status, etc.

[0080] In step 202, the fault type of each initial fault data is matched in the preset shielding library to determine all fault data to be shielded. In this invention, since users may have known historical faults, false alarms, or faults with very little impact, and users do not need to include these faults in the final result display, the preset fault types of these faults can be input into the preset shielding library. The preset shielding library is constructed based on preset fault types so that all fault data existing in the preset shielding library will be shielded. That is, the fault type of each initial fault data is matched in the preset shielding library. If the fault type of an initial fault data matches the preset fault type in the preset shielding library, then the fault data is considered to be fault data to be shielded.

[0081] In step 203, all fault data to be masked is removed from all initial fault data. Before obtaining the fault occurrence time and fault type of each fault data, the present invention first pre-screens all initial fault data to remove the fault types preset by the user, so that all the acquired fault data are data that need to be statistically analyzed, need to be monitored, and need to be displayed.

[0082] Figure 4 This is the third flowchart of the fault handling method provided by the present invention. Before removing each job fault data from all fault data, it also includes:

[0083] Obtain every historical construction and maintenance period for all historical construction and maintenance work;

[0084] The average value of all historical construction time periods is used to determine the preset time period.

[0085] In step 301, the present invention actually provides a technical solution for dynamically determining work failure data. Specifically, the present invention can adjust the preset time period in real time according to different historical construction time periods. For example, each historical construction time period of historical construction and maintenance can be the time period of each construction in the previous month, or it can be the time period of each construction in the previous three months. For example, in the previous three months, a total of three constructions were carried out. The first construction started at 12:00 am and ended at 5:00 am. The second construction started at 1:00 am and ended at 4:00 am. The third construction started at 12:30 am and ended at 6:00 am.

[0086] In step 302, all historical construction time periods are averaged to determine the preset time period. In this embodiment, the preset time period can also be determined by comprehensively analyzing the construction time of each construction within the historical preset time period, thus making the determination of the preset time period more reasonable.

[0087] Figure 5 This is a flowchart illustrating the process of determining the preset time period provided by the present invention. The step of averaging all historical construction time periods to determine the preset time period includes:

[0088] Obtain the start and end times of each historical construction period;

[0089] Average all start times to determine the average start time, and average all end times to determine the average end time.

[0090] The preset time period is determined based on the average start time and average end time of construction.

[0091] In step 3021, in conjunction with the embodiment in step 301, a total of three construction projects were carried out in the first three months. The first construction project started at 12:00 AM and ended at 5:00 AM. The second construction project started at 1:00 AM and ended at 4:00 AM. The third construction project started at 12:30 AM and ended at 6:00 AM. Therefore, the start time of the first construction project was 0:00 AM and the end time was 5:00 AM. The start time of the second construction project was 1:00 AM and the end time was 4:00 AM. The start time of the third construction project was 0:30 AM and the end time was 6:00 AM.

[0092] In step 3022, all start construction times are averaged to determine the average start construction time. All end construction times are averaged to determine the average end construction time. In conjunction with the embodiment in step 3021, all start construction times are averaged to determine the average start construction time as 12:30 am. All end construction times are averaged to determine the average end construction time as 5:00 am.

[0093] In step 3023, the preset time period is determined based on the average start time and average end time of construction. In conjunction with the embodiments in steps 3021 to 3022, the start time of construction for the preset time period is 12:30 am and the end time of construction is 5:00 pm.

[0094] Figure 6 This is a flowchart illustrating the process of determining all second fault data provided by the present invention. The step of removing fault data corresponding to duplicate fault types from all first fault data to determine all second fault data includes:

[0095] For each first fault data, if there is a fault data that is identical to the first fault data, the fault data is marked as duplicate fault data;

[0096] Iterate through all first-fault data, remove all duplicate fault data, and determine all second-fault data.

[0097] In step 1031, for each first fault data, if there is a fault data that is the same as the first fault data, the fault data is marked as duplicate fault data. For example, during the process of eliminating duplicate fault types, all first fault data are traversed in turn. When the current first fault data is obtained, it is compared with all the previously obtained first fault data. If there is a fault type that is the same, the fault data is marked as duplicate fault data to ensure that the fault types of all first fault data are different.

[0098] In step 1032, after traversing all first fault data, all marked fault data are identified, that is, all duplicate fault data are identified. All duplicate fault data are removed from all first fault data, and then all second fault data are obtained.

[0099] Figure 7 This is the fourth flowchart of the fault handling method provided by the present invention. After determining all the second fault data, it further includes:

[0100] Every second preset time interval, acquire all second fault data sets within each first preset time interval;

[0101] In all second fault datasets, count the number of faults occurring for each fault type.

[0102] A preset number of fault types are determined based on the number of fault occurrences in descending order, and a second display instruction is generated;

[0103] The second display instruction is used to indicate the display of a preset number of fault types and the number of times the faults occur corresponding to the fault types.

[0104] In step 401, every second preset time interval, all second fault data sets within each first preset time interval are acquired. The second preset time interval is longer than the first preset time interval. For example, if the first preset time interval is 3 hours and the second preset time interval is 24 hours, then in step 401, the fault data processing of steps 101 to 103 is repeated 8 times, thereby merging all the second fault data and determining all the second fault data sets.

[0105] In step 402, the number of occurrences of all fault types is counted in all second fault data sets. Since the second fault data within each first preset time period may contain the same fault type or fault cause, the second preset time period is used as a statistical summary to determine the number of occurrences of each fault type during continuous monitoring within the first preset time period. For example, in the fault data acquired for the first preset time period, fault type X and fault type Z both fail; in the fault data acquired for the second preset time period, fault type X and fault type Y both fail; in the fault data acquired for the third preset time period, fault type X, fault type Q, and fault type P both fail; and in the fault data acquired for the fourth preset time period, fault type X and fault type S both fail. The statistics are then compiled based on the faults occurring for the aforementioned fault types.

[0106] In step 403, a preset number of fault types are determined according to the order of the number of fault occurrences from largest to smallest, and a second display instruction is generated. In conjunction with the embodiment in step 402, the second display instruction is used to indicate the display of the preset number of fault types and the number of fault occurrences corresponding to the fault types. It can be determined that fault type X has occurred 4 times, and fault types Y, Z, P, Q and S have each occurred once.

[0107] Optionally, after counting the number of failures for all failure types, the method also includes:

[0108] An alarm command is generated if the number of occurrences of any fault type is greater than or equal to the preset number.

[0109] The alarm command is used to instruct and notify the user terminal.

[0110] The preset number of times can be 3 times. In combination with the embodiment in step 403, if fault type X occurs 4 times, and fault types Y, Z, P, Q and S each occur 1 time, then fault type X occurs 4 times, which is greater than the preset number of times. Therefore, an alarm command is generated and sent to the user terminal. The alarm command can be sent to the user terminal via SMS, application push, or telephone.

[0111] In other embodiments, light alarms, vibration alarms, or sound alarms can be used to remind decision-makers to address the current fault situation.

[0112] Those skilled in the art will understand that, in addition to displaying the number of occurrences of all fault types, the present invention can also retrieve stored files from the fault database in the final result display to show the fault number, alarm level, alarm station, subsystem, alarm device, alarm content, occurrence time, whether the fault has been recovered, fault recovery time, fault duration, and on-site personnel operation content corresponding to the fault type.

[0113] More specifically, the corresponding display interface can also display the equipment failure trend based on the failure status of each device, such as the daily failure distribution of the device, and the failure quantity of the device failure trend, such as the actual number of failures of the device daily, weekly, and monthly. It can also display site analysis, such as the distribution of the site locations where the device has failures. The distribution of these failures can be displayed in the form of curves, histograms, etc.

[0114] For decision-makers, the displayed fault results allow them to determine the equipment's health based on the fault's occurrence time and frequency. Furthermore, the system can comprehensively analyze the fault's occurrence time, frequency, and type to obtain the real-time status value of the operating equipment, indicating whether the fault is a "real fault" or a "false fault." If it is a real fault, this is reflected in the monitoring equipment in real time. This invention can display the most frequent faults and other faults, along with their frequency and percentage. Faults can be sorted from most frequent to least frequent. If faults have the same number of occurrences, they are sorted alphabetically by their names. Based on the final fault results, this invention can calculate the equipment's failure rate and health within a preset timeframe.

[0115] This invention can also comprehensively evaluate equipment health indicators by integrating factors such as online monitoring data of various equipment components, real-time anomaly and fault analysis of online monitoring data, historical trend changes of online monitoring data, design fault curves of various equipment components, usage time and frequency of various equipment components, historical fault conditions, and historical maintenance records, thereby realizing equipment health calculation and life prediction.

[0116] Figure 8 This is a schematic diagram of the fault handling device provided by the present invention. The present invention provides a fault handling device, including an acquisition unit 1: used to acquire the fault occurrence time and fault type of each fault data. The working principle of the acquisition unit 1 can be referred to the aforementioned step 101, and will not be repeated here.

[0117] The fault handling device further includes a determination unit 2: used to remove each operation fault data from all fault data according to the fault occurrence time of each fault data, and determine all first fault data. The working principle of the determination unit 2 can be referred to the aforementioned step 102, and will not be repeated here.

[0118] The fault handling device further includes a generation unit 3: based on the fault type of each first fault data, it removes fault data corresponding to duplicate fault types from all first fault data, determines all second fault data, and generates a first display instruction. The working principle of the generation unit 3 can be referred to the aforementioned step 103, and will not be repeated here.

[0119] The operational fault data refers to the fault data generated due to equipment failures caused by construction and maintenance within a preset time period;

[0120] The first display instruction is used to instruct the display of all second fault data.

[0121] The fault handling method, apparatus, electronic device, and readable storage medium provided by this invention use the fault occurrence time and fault type corresponding to the fault data as the determining factors for elimination. Starting from fault data caused by equipment failure due to construction and maintenance, and multiple repeated faults occurring within a preset time, this invention filters the fault data collected within a preset time, thereby reducing the server load, improving the accuracy of result display, providing decision-makers with more accurate fault cause analysis, and thus improving fault troubleshooting efficiency.

[0122] Figure 9 This is a schematic diagram of the structure of the electronic device provided by the present invention. For example... Figure 9As shown, the electronic device may include a processor 910, a communication interface 920, a memory 930, and a communication bus 940, wherein the processor 910, the communication interface 920, and the memory 930 communicate with each other through the communication bus 940. The processor 910 can call logical instructions in the memory 930 to execute a fault handling method, which includes: repeatedly executing the following steps every first preset time interval: acquiring the fault occurrence time and fault type of each fault data; based on the fault occurrence time of each fault data, removing each work fault data from all fault data to determine all first fault data; based on the fault type of each first fault data, removing fault data corresponding to the same fault type from all first fault data to determine all second fault data, and generating a first display instruction; the work fault data are fault data generated due to equipment failure caused by construction and maintenance within a preset time period; the first display instruction is used to indicate the display of all second fault data.

[0123] Furthermore, the logical instructions in the aforementioned memory 930 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, essentially, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0124] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute a fault handling method provided by the above methods. The method includes: repeatedly executing the following steps every first preset time interval: acquiring the fault occurrence time and fault type of each fault data; removing each work fault data from all fault data according to the fault occurrence time of each fault data to determine all first fault data; removing fault data corresponding to repeated fault types from all first fault data according to the fault type of each first fault data to determine all second fault data, and generating a first display instruction; wherein the work fault data is fault data generated due to equipment failure caused by construction and maintenance within a preset time period; and the first display instruction is used to instruct the display of all second fault data.

[0125] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program is implemented to perform the fault handling methods provided by the above methods. The method includes: repeatedly executing the following steps every first preset time interval: acquiring the fault occurrence time and fault type of each fault data; based on the fault occurrence time of each fault data, removing each work fault data from all fault data to determine all first fault data; based on the fault type of each first fault data, removing fault data corresponding to duplicate fault types from all first fault data to determine all second fault data, and generating a first display instruction; wherein the work fault data is fault data generated due to equipment failure caused by construction and maintenance within a preset time period; and the first display instruction is used to instruct the display of all second fault data.

[0126] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0127] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0128] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A fault handling method, characterized in that, include: Repeat the following steps every first preset time interval: Obtain the time of occurrence and type of each fault; Based on the time of occurrence of each fault data, remove each job fault data from all fault data to determine all first fault data; Based on the fault type of each first fault data, remove the fault data corresponding to the duplicate fault type from all the first fault data, determine all the second fault data, and generate the first display instruction; The operational fault data refers to the fault data generated due to equipment failures caused by construction and maintenance within a preset time period; The first display instruction is used to instruct the display of all second fault data; Before removing each job failure data from all failure data, the process also includes: Obtain every historical construction and maintenance period for all historical construction and maintenance work; Obtain the start and end times of each historical construction period; Average all start times to determine the average start time, and average all end times to determine the average end time. The preset time period is determined based on the average start time and average end time of construction.

2. The fault handling method according to claim 1, characterized in that, The time of occurrence of the fault for acquiring each fault data includes: Obtain the timestamp of any fault data and determine the time of fault occurrence based on the timestamp; Iterate through the timestamps of all fault data to determine the time when the fault occurred for each fault.

3. The fault handling method according to claim 1, characterized in that, Before obtaining the fault occurrence time and fault type for each fault, the following is also included: Obtain all initial fault data, and obtain the fault type for each initial fault data; Match the fault type of each initial fault data in the preset shielding library to determine all fault data to be shielded; Remove all fault data to be masked from all initial fault data; The preset shielding library is constructed based on preset fault types.

4. The fault handling method according to claim 1, characterized in that, The step of removing fault data corresponding to duplicate fault types from all first fault data to determine all second fault data includes: For each first fault data, if there is a fault data that is identical to the first fault data, the fault data is marked as duplicate fault data; Iterate through all first-fault data, remove all duplicate fault data, and determine all second-fault data.

5. The fault handling method according to claim 1, characterized in that, After determining all the second fault data, the following is also included: Every second preset time interval, acquire all second fault data sets within each first preset time interval; In all second fault datasets, count the number of faults occurring for each fault type. A preset number of fault types are determined based on the number of fault occurrences in descending order, and a second display instruction is generated; The second display instruction is used to indicate the display of a preset number of fault types and the number of times the faults occur corresponding to the fault types.

6. The fault handling method according to claim 5, characterized in that, After counting the number of failures for all failure types, the following is also included: An alarm command is generated if the number of occurrences of any fault type is greater than or equal to the preset number. The alarm command is used to instruct and notify the user terminal.

7. A fault handling device, characterized in that, include: Acquisition Unit: Used to acquire the time of occurrence and type of each fault data; Determination Unit: Used to remove each job failure data from all failure data based on the failure occurrence time of each failure data, and determine all first failure data; Generation unit: used to remove fault data corresponding to duplicate fault types from all first fault data according to the fault type of each first fault data, determine all second fault data, and generate a first display instruction; The operational fault data refers to the fault data generated due to equipment failures caused by construction and maintenance within a preset time period; The first display instruction is used to instruct the display of all second fault data; Before removing each job failure data from all failure data, the process also includes: Obtain every historical construction and maintenance period for all historical construction and maintenance work; Obtain the start and end times of each historical construction period; Average all start times to determine the average start time, and average all end times to determine the average end time. The preset time period is determined based on the average start time and average end time of construction.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the fault handling method as described in any one of claims 1 to 6.

9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the fault handling method as described in any one of claims 1 to 6.

Images