Intermittent fault processing method and device, equipment and storage medium

Abstract

The invention discloses an intermittent fault processing method, apparatus and device, and a storage medium. The method comprises the steps of obtaining current fault data of a target system; the current fault data at least comprises current fault information and current fault time; carrying out storage mark detection on the current fault data, and if the current fault data comprises storage mark information, determining current counting information corresponding to the current fault data; if the current counting information is 1, storing the current fault information, the current fault time and the current counting information in a fault storage database, and displaying the current fault information, the current fault time, storage mark information and the current counting information on a fault display interface; if the current counting information is larger than 1, historical fault time and historical counting information corresponding to the current fault information are updated in a fault storage database and a fault display interface. The problem of repeated recording can be solved, the maintenance efficiency is improved, and the credibility of fault data analysis is improved.

Description

Technical Field

[0001] The present invention relates to the field of aviation technology, and in particular to an intermittent fault processing method, device, equipment and storage medium. Background Art

[0002] With the continuous development of the civil aviation transportation industry, there are higher requirements for aircraft maintenance efficiency. Improving maintenance efficiency can greatly shorten maintenance time and reduce operating costs. After the aircraft lands, the maintenance personnel enter the post-flight summary display page of the onboard maintenance system and conduct fault troubleshooting one by one according to the fault records.

[0003] In the related art, the display page can record all intermittent fault triggers and triggered intermittent faults, which increases the maintenance task and affects the efficiency of intermittent fault troubleshooting. In addition, since the storage of intermittent faults can be set according to different requirements, there is a problem that the displayed fault message is inconsistent with the stored fault data. Summary of the invention

[0004] In view of the above-mentioned defects of the related art, the technical problem to be solved by the present invention is how to improve the reliability of data while reducing the amount of data recorded in fault records.

[0005] In order to solve the above-mentioned technical problems, the present invention discloses an intermittent fault processing method, device, equipment and storage medium.

[0006] According to one aspect of the present disclosure, a method for handling intermittent faults is provided, comprising:

[0007] Acquire current fault data of the target system; the current fault data at least includes current fault information and current fault time;

[0008] Performing storage mark detection on the current fault data to obtain a mark detection result;

[0009] In a case where the mark detection result indicates that the current fault data includes storage mark information, determining current counting information corresponding to the current fault data;

[0010] If the current count information is 1, the current fault information, the current fault time and the current count information are stored in the fault storage database, and the current fault information, the current fault time, the storage mark information and the current count information are displayed on the fault display interface;

[0011] If the current count information is greater than 1, the historical fault time and the historical count information corresponding to the current fault information are updated in the fault storage database, and the historical fault time and the historical count information corresponding to the current fault information are updated on the fault display interface.

[0012] In some possible embodiments, before obtaining the current fault data of the target system, the method includes:

[0013] Acquire a fault storage requirement matching the target system;

[0014] A storage requirement database is constructed based on the fault storage requirement; the storage requirement database includes a mapping relationship between each fault information and the storage mark information.

[0015] In some possible embodiments, performing storage mark detection on the current fault data to obtain a mark detection result includes:

[0016] Based on the storage demand database, searching the current fault information to obtain a fault search result;

[0017] When the fault search result indicates that there is a target mapping relationship corresponding to the current fault information in the storage demand database, determining that the tag detection result is that the current fault data includes the storage tag information, and determining the storage tag information corresponding to the current fault information based on the target mapping relationship;

[0018] When the fault search result indicates that the target mapping relationship corresponding to the current fault information does not exist in the storage demand database, it is determined that the tag detection result is that the current fault data does not include the storage tag information.

[0019] In some possible embodiments, determining current counting information corresponding to the current fault data includes:

[0020] accessing the fault storage database;

[0021] Based on the fault storage database, performing fault matching on the current fault data to obtain a first matching result;

[0022] When the first matching result indicates that the current fault data exists in the fault storage database, determining a first fault interval time based on the historical fault time corresponding to the current fault data in the fault storage database and the current fault time;

[0023] comparing the first fault interval time with a preset interval time, and determining that the first counting information corresponding to the current fault data is greater than 1 when the first fault interval time is less than the preset interval time;

[0024] When the first matching result indicates that the current fault data does not exist in the fault storage database, it is determined that the first counting information corresponding to the current fault data is equal to 1.

[0025] In some possible embodiments, determining current counting information corresponding to the current fault data includes:

[0026] Accessing the fault display interface;

[0027] Based on the fault display interface, performing fault matching on the current fault data to obtain a second matching result;

[0028] In the case where the second matching result indicates that the current fault data exists in the fault display interface, determining a second fault interval time based on the historical fault time corresponding to the current fault data in the fault display interface and the current fault time;

[0029] comparing the second fault interval time with a preset interval time, and determining that the second counting information corresponding to the current fault data is greater than 1 when the second fault interval time is less than the preset interval time;

[0030] When the second matching result indicates that the current fault data does not exist in the fault display interface, it is determined that the second counting information corresponding to the current fault data is equal to 1.

[0031] In some possible embodiments, the method further includes:

[0032] When the number of fault information displayed in the fault display interface is equal to the fault number threshold, at least one piece of fault information in the fault display interface is deleted.

[0033] In some possible embodiments, the method further includes:

[0034] When the number of fault data displayed in the fault display interface is equal to the fault number threshold, sequentially traverse each fault information in the fault display interface and access the fault storage database;

[0035] In the case where there is a piece of fault information stored in the fault storage database, the fault information is deleted from the fault display interface.

[0036] According to a second aspect of the present disclosure, there is provided an intermittent fault processing device, the device comprising:

[0037] A data acquisition module, used to acquire current fault data of the target system; the current fault data at least includes current fault information and current fault time;

[0038] A mark detection module, used for performing storage mark detection on the current fault data to obtain a mark detection result;

[0039] a count determination module, configured to determine current count information corresponding to the current fault data when the mark detection result indicates that the current fault data includes storage mark information;

[0040] A first processing module, configured to store the current fault information, the current fault time, and the current count information in a fault storage database if the current count information is 1, and display the current fault information, the current fault time, the storage mark information, and the current count information on a fault display interface;

[0041] The second processing module is used to update the historical fault time and historical counting information corresponding to the current fault information in the fault storage database if the current counting information is greater than 1, and to update the historical fault time and historical counting information corresponding to the current fault information in the fault display interface.

[0042] There may be other ways of dividing modules. The present application does not limit the way of dividing modules of the device for implementing the above functions. For example, the above-mentioned data acquisition module, mark detection module, count determination module, first processing module and second processing module can be integrated / implemented as one or more processing modules.

[0043] According to a third aspect of the present disclosure, an electronic device is provided, comprising a processor and a memory, wherein the memory stores at least one instruction and at least one program, and the at least one instruction and the at least one program are loaded and executed by the processor to implement the intermittent fault handling method as described above.

[0044] According to a fourth aspect of the present disclosure, a computer storage medium is provided, in which at least one instruction and at least one program are stored, and the at least one instruction and the at least one program are loaded and executed by a processor to implement the intermittent fault handling method as described above.

[0045] According to the fifth aspect of the present disclosure, a chip system is provided, comprising at least one processor and at least one interface circuit, wherein the at least one interface circuit is used to perform transceiver functions and send instructions to at least one processor, and when the at least one processor executes the instructions, the at least one processor executes the intermittent fault handling method as described in the first aspect and any one of the designs thereof.

[0046] According to a sixth aspect of the present disclosure, a computer program product is provided, comprising a computer program / instruction, wherein when the computer program / instruction is executed by a processor, the intermittent fault handling method as described above is implemented.

[0047] The implementation of the present invention has the following beneficial effects:

[0048] In the present invention, after obtaining the current fault data of the target system, the current fault data is firstly subjected to a storage mark detection to determine whether the current fault data needs to be displayed or stored, and then the display and storage of the current fault data can be distinguished according to the storage mark information, and the fault data displayed on the fault display interface can also be distinguished according to the storage mark information, thereby improving the intuitiveness of the fault data distinction, thereby enabling the user to understand the source of the data and improving the confidence in the source of the data; in addition, for the storage and display of intermittent fault data, the addition of new data or the update of data in the fault storage database and the fault display interface is determined according to the current counting information corresponding to the current fault data, which can reduce the repeated recording and redundant display of the same intermittent fault data, thereby reducing the amount of data and improving the efficiency of troubleshooting intermittent faults. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the technical solution of the present invention, the drawings required for use in the embodiments or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0050] Figure 1 A schematic diagram of a flow chart corresponding to an intermittent fault handling method provided by an embodiment of the present invention;

[0051] Figure 2 A schematic diagram of a corresponding process for determining first counting information provided by an embodiment of the present invention;

[0052] Figure 3 A schematic diagram of a corresponding flow chart of second counting information determination provided by an embodiment of the present invention;

[0053] Figure 4 A first schematic diagram corresponding to a fault display interface provided in a specific embodiment of the present invention;

[0054] Figure 5 A second schematic diagram corresponding to a fault display interface provided in a specific embodiment of the present invention;

[0055] Figure 6 A third schematic diagram corresponding to a fault display interface provided in a specific embodiment of the present invention;

[0056] Figure 7 A structural schematic diagram corresponding to an intermittent fault handling method provided in an embodiment of the present invention. DETAILED DESCRIPTION

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

[0058] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

[0059] Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. The same reference numerals in the accompanying drawings represent elements with the same or similar functions. Although various aspects of the embodiments are shown in the accompanying drawings, the drawings are not necessarily drawn to scale unless otherwise specified.

[0060] The word “exemplary” is used exclusively herein to mean “serving as an example, example, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0061] The term "and / or" herein is only a description of the association relationship of the associated objects, indicating that there may be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the term "at least one" herein represents any combination of at least two of any one or more of a plurality of. For example, including at least one of A, B, and C can represent including any one or more elements selected from the set consisting of A, B, and C.

[0062] In addition, in order to better illustrate the present disclosure, numerous specific details are given in the following specific embodiments. It should be understood by those skilled in the art that the present disclosure can also be implemented without certain specific details. In some examples, methods, means, components and circuits well known to those skilled in the art are not described in detail in order to highlight the subject matter of the present disclosure.

[0063] Figure 1 The flowchart corresponding to the intermittent fault handling method provided by the embodiment of the present invention is shown; the execution subject can be any terminal capable of executing the intermittent fault handling method, such as a controller, a server, etc., or can be a corresponding module capable of implementing or cooperating with the implementation of the terminal function, such as a chip. Figure 1 , an intermittent fault processing method, comprising:

[0064] Step S101: obtaining current fault data of the target system; the current fault data at least includes current fault information and current fault time;

[0065] The present invention can be applied to any system that needs to store and / or display fault data. In an embodiment of the present invention, the intermittent fault processing method can be applied to an aircraft, that is, the target system is an aircraft.

[0066] Specifically, it can be considered that the aircraft is composed of multiple devices or structures, and these structures or devices may have faults, and the faults are displayed and / or stored in the form of fault data. According to the specific requirements of different airlines, different aircraft models, different flight segments, etc., some fault data may be displayed and stored, so that users can download the fault data while intuitively seeing the fault data. Some fault data only needs to be displayed. Therefore, the intermittent fault handling method in the present invention can distinguish between fault data that needs to be stored and displayed and fault data that only needs to be displayed. The intermittent fault handling method disclosed in the present invention is mainly applied to intermittent fault data in aircraft. Intermittent fault data is a type of fault in which the system function returns to normal after a fault occurs without the implementation of any external corrective measures, or fault data corresponding to the fault of the maintenance system itself caused by power on and off.

[0067] The current fault data may at least include the current fault time when the target system fails and the current fault information of the specific fault. It is worth noting that the fault data mentioned in the present invention are all the fault data corresponding to the intermittent faults mentioned above. In addition, since the intermittent fault processing method in the present invention can distinguish the fault data, the current fault data may also include storage mark information.

[0068] Furthermore, before obtaining the current fault data of the target system, the method includes:

[0069] Obtain fault storage requirements that match the target system;

[0070] A storage requirement database is constructed based on the fault storage requirement; the storage requirement database includes a mapping relationship between each fault information and storage mark information.

[0071] In a specific embodiment, since the storage requirements for fault data may be different, the fault storage requirements can be predetermined for a specific target system and its flight segment, company, flight model, and other related information, and then a storage requirement database can be constructed according to the fault storage requirements. The storage requirement database may include the fault information to be stored and the storage tag information corresponding to the fault information. It can be considered that there is a mapping relationship between the fault information and the storage tag information, so that the corresponding storage tag information can be found in the storage requirement database based on the fault information.

[0072] By constructing a storage demand database, the fault information that needs to be stored and displayed and the fault information that only needs to be displayed are divided in advance, so that users can distinguish the fault information intuitively, quickly and accurately through storage marking information, thereby increasing the trust of users such as airlines and equipment suppliers in fault data and improving the confidence of fault data.

[0073] Step S102: Perform storage mark detection on current fault data to obtain a mark detection result;

[0074] In a specific embodiment, if a piece of fault information does not need to be stored, there is no corresponding storage mark information, so the current fault data may include storage mark information or may not include storage mark information. It is possible to determine whether the current fault data includes storage mark information by performing storage mark detection on the current fault data, and then determine whether the current fault data needs to be displayed and stored.

[0075] Specifically, the storage mark detection is performed on the current fault data to obtain the mark detection result, including:

[0076] Based on the storage demand database, search for current fault information and obtain fault search results;

[0077] When the fault search result indicates that there is a target mapping relationship corresponding to the current fault information in the storage demand database, determining the tag detection result is that the current fault data includes storage tag information, and determining the storage tag information corresponding to the current fault information based on the target mapping relationship;

[0078] When the fault search result indicates that there is no target mapping relationship corresponding to the current fault information in the storage demand database, it is determined that the tag detection result is that the current fault data does not include storage tag information.

[0079] In a specific embodiment, since the storage requirement database includes a mapping relationship between fault information and storage tag information, a search can be performed in the storage requirement database based on the current fault information to obtain a fault search result; the fault search result is used to indicate whether the storage requirement database includes the current fault information and the storage tag information that has a mapping relationship with the current fault information. The tag detection results include two types, corresponding to the current fault data including the storage tag information and the current fault data not including the storage tag information.

[0080] When the fault search result indicates that there is a target mapping relationship corresponding to the current fault information in the storage demand database, it means that the current fault data corresponding to the current fault information needs to be displayed and stored, and the tag detection result is that the current fault data includes storage tag information. At this time, the storage tag information corresponding to the current fault information can be determined according to the target mapping relationship. Among them, the target mapping relationship is the mapping relationship that includes the current fault information in the storage demand database.

[0081] On the contrary, when the fault search result indicates that there is no target mapping relationship corresponding to the current fault information in the storage demand database, it means that the current fault data corresponding to the current fault information only needs to be displayed but not stored, and the mark detection result is that the current fault data does not include storage mark information.

[0082] By storing tag information in conjunction with a storage demand database, fault data can be efficiently and accurately divided according to whether it needs to be stored, thereby optimizing the management of fault data, improving data confidence, and improving the convenience and efficiency of data differentiation.

[0083] Step S103: when the mark detection result indicates that the current fault data includes storage mark information, determine current counting information corresponding to the current fault data;

[0084] In a specific embodiment, when the mark detection result indicates that the current fault data includes storage mark information, in order to reduce repeated recording of the same fault information, reduce the amount of data and simplify the fault display interface, the fault data corresponding to the repeated fault information can be counted, that is, the current count information corresponding to the current fault data can be determined.

[0085] Specifically, the current counting information may include first counting information for counting the number of times the current fault data appears in the fault storage database, and second counting information for counting the number of times the current fault data appears in the fault display interface; since the fault display interface has a fault quantity threshold for displaying fault data, when the number of fault data reaches the fault quantity threshold, some fault data will be deleted, so the first counting information of the current fault data may not be equal to the second counting information, and therefore the first counting information and the second counting information need to be calculated separately.

[0086] In another specific embodiment, when the mark detection result indicates that the current fault data does not include storage mark information, it means that the current fault data only needs to be displayed, and the corresponding second counting information is calculated, and based on the second counting information, it is determined whether the current fault data is a new data record in the fault display interface or an update in the historical fault data, and the current fault data is displayed on the fault display interface.

[0087] Step S104: determining whether the current count information is equal to 1 or greater than 1;

[0088] Step S105: if the current count information is 1, the current fault information, the current fault time and the current count information are stored in the fault storage database, and the current fault information, the current fault time, the storage mark information and the current count information are displayed on the fault display interface;

[0089] Step S106: If the current count information is greater than 1, the historical fault time and historical count information corresponding to the current fault information are updated in the fault storage database, and the historical fault time and historical count information corresponding to the current fault information are updated on the fault display interface.

[0090] In a specific embodiment, after determining whether the current fault data needs to be stored, it is also necessary to determine whether the storage and / or display method of the current fault data is to add a new data record or to update the historical data. Compared with choosing to add a new data record for all fault data, it can reduce the amount of data and improve the efficiency of data viewing and reading. Specifically, the above steps S104 to S106 can be implemented according to steps S301 to S306, and the above steps S104 to S106 can also be implemented according to steps S201 to S206 and steps S301 to S306. It should be noted that since the determined current count information corresponds to the current fault data, its current count information cannot be less than 1, so Figure 1 In the judgment step S104, if the judgment condition is met, the current count information is equal to 1, and if the judgment condition is not met, the current count information is greater than 1.

[0091] Figure 2 A schematic diagram of a corresponding flow chart of first counting information determination provided by an embodiment of the present invention; Figure 2 As shown, determining the current counting information corresponding to the current fault data includes:

[0092] Step S201: accessing a fault storage database;

[0093] Step S202: performing fault matching on current fault data based on the fault storage database to obtain a first matching result;

[0094] In a specific embodiment, the fault storage database is first accessed, and the current fault information included in the current fault data is used for fault matching to determine whether the current fault information already exists in the fault storage database, that is, the fault storage database is accessed for fault matching to determine whether the current fault information has been stored, and a first matching result is obtained.

[0095] Step S203: when the first matching result indicates that the current fault data exists in the fault storage database, determine the first fault interval time based on the historical fault time corresponding to the current fault data in the fault storage database and the current fault time;

[0096] In a specific embodiment, when the first matching result indicates that there is current fault data in the fault storage database, it means that the fault corresponding to the current fault information has occurred and been stored, that is, there is historical fault data corresponding to the current fault information in the fault storage database, wherein the historical fault data may include the current fault information, the historical fault time, and the historical count information; in this case, it may be considered not to add a new data record, but to change the historical fault time and the historical count information included in the historical fault data corresponding to the current fault information in the fault storage database, thereby reducing the amount of data in the fault storage database and saving computing resources. It is necessary to combine the current fault time in the current fault data to determine whether to add a new data record for the current fault data or to update it in the historical fault data.

[0097] In another specific embodiment, when the first matching result indicates that the current fault data does not exist in the fault storage database, there is no need to make a judgment in combination with the current fault time, but a new data record is directly added to the fault storage database.

[0098] Step S204: determining whether the first fault interval is greater than a preset interval;

[0099] In a specific embodiment, by comparing the first fault interval time with the preset interval time, the size of the first fault interval time and the preset interval time is determined, and then the first counting information is determined according to the size relationship between the first fault interval time and the preset interval time. The preset time interval can be set and adjusted according to specific needs, such as different fault types, different target systems, etc.

[0100] Step S205: when the first fault interval is less than the preset interval, determining that the first counting information corresponding to the current fault data is greater than 1;

[0101] Step S206: when the first matching result indicates that the current fault data does not exist in the fault storage database, or when the first fault interval is greater than or equal to the preset interval, determine that the first counting information corresponding to the current fault data is equal to 1.

[0102] In a specific embodiment, if the first fault interval is less than the preset interval, indicating that the fault occurs frequently, the first historical counting information is updated in the historical fault data. For example, if the first historical counting information is n, the updated first historical counting information is the first counting information corresponding to the current fault data, which is n + 1. At the same time, the historical fault time in the historical fault data can also be updated to the current fault time.

[0103] If the first fault interval is greater than or equal to the preset interval, it means that the fault does not occur frequently and needs to be determined as a new data record, and the corresponding first counting information is 1.

[0104] In a specific embodiment, by determining the first counting information through the above method, it is possible to avoid adding too many records due to frequent triggering of the same fault in a short period of time, thereby reducing the amount of data in the database and saving data resources. In addition, fault triggers with short time intervals are filtered out and processed as repeated records, while retaining triggers with longer intervals as new fault records, which can not only accurately record important fault data, but also avoid interference in the judgment of fault frequency and severity due to repeated records, and enable maintenance personnel to quickly understand the frequency and impact range of repeated fault triggering, and more efficiently classify and troubleshoot faults.

[0105] Figure 3 A schematic diagram of a flow chart corresponding to the second counting information determination provided by an embodiment of the present invention; Figure 3 As shown, determining the current counting information corresponding to the current fault data includes:

[0106] Step S301: access the fault display interface;

[0107] Step S302: Based on the fault display interface, perform fault matching on the current fault data to obtain a second matching result;

[0108] In a specific embodiment, the fault display interface is first accessed, and the current fault information included in the current fault data is used for fault matching to determine whether the current fault information already exists in the fault display interface, that is, the fault display interface is accessed for fault matching to determine whether the current fault information has been displayed, and a second matching result is obtained.

[0109] Step S303: when the second matching result indicates that there is current fault data in the fault display interface, determine the second fault interval time based on the historical fault time corresponding to the current fault data in the fault display interface and the current fault time;

[0110] In a specific embodiment, when the second matching result indicates that there is current fault data in the fault display interface, it means that the fault corresponding to the current fault information has occurred and been displayed, that is, there is historical fault data corresponding to the current fault information in the fault display interface, wherein the historical fault data may include the current fault information, the historical fault time, and the historical count information; in this case, it may be considered not to add a new data record, but to change the historical fault time and the historical count information included in the historical fault data corresponding to the current fault information in the fault display interface, thereby reducing the amount of data displayed on the fault display interface and optimizing the interface display. It is necessary to combine the current fault time in the current fault data to determine whether to add a new data record for the current fault data or to update it in the historical fault data.

[0111] In another specific embodiment, when the second matching result indicates that the current fault data does not exist in the fault display interface, there is no need to make a judgment in combination with the current fault time, but directly add a new data record in the fault display interface.

[0112] Step S304: determining whether the second fault interval is greater than a preset interval;

[0113] In a specific embodiment, by comparing the second fault interval time with the preset interval time, the size of the second fault interval time and the preset interval time is determined, and then the second counting information is determined according to the size relationship between the second fault interval time and the preset interval time. The preset time interval can be set and adjusted according to specific needs, such as different fault types, different target systems, etc.

[0114] Step S305: when the second fault interval is less than the preset interval, determining that the second counting information corresponding to the current fault data is greater than 1;

[0115] Step S306: when the second matching result indicates that the current fault data does not exist in the fault display interface, or when the second fault interval is greater than or equal to the preset interval, determine that the second counting information corresponding to the current fault data is equal to 1.

[0116] In a specific embodiment, if the second fault interval is less than the preset interval, indicating that the fault occurs more frequently, the second historical counting information is updated in the historical fault data. For example, if the second historical counting information is m, the updated second historical counting information is the second counting information corresponding to the current fault data, which is m+1. At the same time, the historical fault time in the historical fault data can also be updated to the current fault time.

[0117] If the second fault interval is greater than or equal to the preset interval, it means that the fault does not occur frequently and needs to be determined as a new data record, and the corresponding second counting information is 1.

[0118] In a specific embodiment, by determining the second counting information through the above method, it is possible to avoid adding too many records due to frequent triggering of the same fault in a short period of time, thereby reducing the amount of data and improving the simplicity of the fault display interface, thereby improving the efficiency of users viewing fault data. In addition, fault triggers with a short time interval are filtered out and processed as repeated records, while retaining triggers with a long time interval as new fault records, which can not only accurately record important fault data, but also avoid interference in the judgment of fault frequency and severity due to repeated records, and enable maintenance personnel to quickly understand the frequency and impact range of repeated fault triggering, and more efficiently classify and troubleshoot faults.

[0119] Furthermore, the fault display interface corresponds to a fault quantity threshold;

[0120] The method also includes:

[0121] When the number of fault information displayed in the fault display interface is equal to the fault number threshold, at least one piece of fault information in the fault display interface is deleted.

[0122] Or, when the number of fault data displayed in the fault display interface is equal to the fault number threshold, each fault information in the fault display interface is sequentially traversed, and the fault storage database is accessed;

[0123] In the case where there is a piece of fault information stored in the fault storage database, the fault information is deleted from the fault display interface.

[0124] In a specific embodiment, when the number of fault data displayed on the fault display interface is equal to the fault quantity threshold, the data in the fault display interface needs to be deleted to ensure that the next fault data can be displayed normally. The fault quantity threshold can be determined according to the actual data display capability of the fault display interface.

[0125] As for the specific deletion method, random deletion, deletion based on the first-in-first-out principle, or deletion of stored data after searching, the preferred method is to delete the fault data that has been stored in the fault storage database, so as to ensure the comprehensiveness of the fault data. As for the number of fault data to be deleted, at least one or more can be deleted, and adaptive adjustment can be made according to actual needs and the frequency of fault occurrence.

[0126] In a specific embodiment, deleting the data in the fault display interface can ensure the normal display of new fault data, thereby ensuring the real-time display and update of fault data. Selecting to delete the fault data that has been stored in the fault storage database can ensure the comprehensiveness of the fault data while ensuring the real-time display and update of the data.

[0127] Figure 4 The first schematic diagram corresponding to the fault display interface provided by a specific embodiment of the present invention. Figure 4 As shown, the fault display interface only distinguishes between stored data and unstored data, but does not process duplicate records in combination with counting information. Figure 4 The * shown is the storage mark information, that is, the fault data with * is the data that has been stored. Figure 4 The time interval between the two triggering of Failure 2 marked with a light pink frame line is less than the preset interval threshold, so these two Failure 2 can be aggregated and merged. Figure 5 , increase the number of times and highlight Failure2 in gray.

[0128] Figure 5 A second schematic diagram corresponding to a fault display interface provided in a specific embodiment of the present invention; Figure 5 As shown in the figure, the fault display interface only distinguishes between stored data and unstored data, and processes the fault data for duplicate records in combination with the counting information, where * is the storage mark information, that is, the fault data with * is the data that has been stored. Figure 4 and Figure 5 By comparison, it can be seen that the amount of data on the fault display interface is significantly reduced after processing the duplicate records.

[0129] Figure 6 A third schematic diagram corresponding to a fault display interface provided in a specific embodiment of the present invention; when selecting Figure 5 Failure2 is highlighted in medium gray. Click Select to enter Figure 6 The fault information details page can display detailed information such as the recording time and flight stage triggered by Failure2.

[0130] The embodiment of the present invention also provides an intermittent fault processing device, such as Figure 7 As shown, the device comprises:

[0131] The data acquisition module 710 is used to acquire the current fault data of the target system; the current fault data at least includes the current fault information and the current fault time;

[0132] A tag detection module 720 is used to perform storage tag detection on the current fault data to obtain a tag detection result;

[0133] A count determination module 730, configured to determine current count information corresponding to the current fault data when the mark detection result indicates that the current fault data includes storage mark information;

[0134] The first processing module 740 is configured to store the current fault information, the current fault time, and the current count information in a fault storage database if the current count information is 1, and display the current fault information, the current fault time, the storage mark information, and the current count information on a fault display interface;

[0135] The second processing module 750 is used to update the historical fault time and historical count information corresponding to the current fault information in the fault storage database if the current count information is greater than 1, and to update the historical fault time and historical count information corresponding to the current fault information in the fault display interface.

[0136] In some other embodiments, the device further comprises:

[0137] A requirement acquisition module, used to acquire a fault storage requirement matching the target system;

[0138] A database construction module is used to construct a storage requirement database based on the fault storage requirement; the storage requirement database includes a mapping relationship between each fault information and the storage mark information.

[0139] In some other embodiments, the marker detection module 720 further includes:

[0140] A fault finding module, used to search the current fault information based on the storage demand database to obtain a fault finding result;

[0141] A first detection result determination module is used to determine that the tag detection result is that the current fault data includes the storage tag information when the fault search result indicates that there is a target mapping relationship corresponding to the current fault information in the storage demand database, and determine the storage tag information corresponding to the current fault information based on the target mapping relationship;

[0142] A second detection result determination module is configured to determine that the tag detection result is that the current fault data does not include the storage tag information when the fault search result indicates that the target mapping relationship corresponding to the current fault information does not exist in the storage demand database.

[0143] In some other embodiments, the count determination module 730 further includes:

[0144] A first access module, used for accessing the fault storage database;

[0145] A first matching module, configured to perform fault matching on the current fault data based on the fault storage database to obtain a first matching result;

[0146] A first fault time determination module, configured to determine a first fault interval time based on a historical fault time corresponding to the current fault data in the fault storage database and the current fault time, when the first matching result indicates that the current fault data exists in the fault storage database;

[0147] A first comparison module, configured to compare the first fault interval time with a preset interval time, and determine that the first counting information corresponding to the current fault data is greater than 1 when the first fault interval time is less than the preset interval time;

[0148] A first determining module is configured to determine that the first counting information corresponding to the current fault data is equal to 1 when the first matching result indicates that the current fault data does not exist in the fault storage database.

[0149] In some other embodiments, the count determination module 730 further includes:

[0150] A second access module, used to access the fault display interface;

[0151] A second matching module, configured to perform fault matching on the current fault data based on the fault display interface to obtain a second matching result;

[0152] A second fault time determination module, configured to determine a second fault interval time based on a historical fault time corresponding to the current fault data in the fault display interface and the current fault time, when the second matching result indicates that the current fault data exists in the fault display interface;

[0153] A second comparison module, configured to compare the second fault interval time with a preset interval time, and determine that the second counting information corresponding to the current fault data is greater than 1 when the second fault interval time is less than the preset interval time;

[0154] A second determination module is configured to determine that the second counting information corresponding to the current fault data is equal to 1 when the second matching result indicates that the current fault data does not exist in the fault display interface.

[0155] In some other embodiments, the device further comprises:

[0156] The first deleting module is used to delete at least one piece of fault information in the fault display interface when the number of fault information displayed in the fault display interface is equal to the fault number threshold.

[0157] In some other embodiments, the device further comprises:

[0158] A fault traversal module, used for sequentially traversing each fault information in the fault display interface and accessing the fault storage database when the number of fault data displayed in the fault display interface is equal to the fault number threshold;

[0159] The second deleting module is used to delete the fault information from the fault display interface when there is a piece of fault information stored in the fault storage database.

[0160] The device and method embodiments in the device embodiment are based on the same inventive concept and are used to implement the above-mentioned intermittent fault handling method.

[0161] An embodiment of the present invention also provides an electronic device, comprising: a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement an intermittent fault handling method as described in any one of the method embodiments.

[0162] An embodiment of the present invention also provides a computer storage medium, which can be set in a server to store at least one instruction, at least one program, a code set or an instruction set for implementing the intermittent fault handling method in the method embodiment. The at least one instruction, the at least one program, the code set or the instruction set are loaded and executed by the processor to implement the intermittent fault handling method as described in any one of the method embodiments.

[0163] Optionally, in an embodiment of the present invention, the above-mentioned storage medium may be located in at least one of a plurality of network servers of a computer network. Optionally, in an embodiment of the present invention, the above-mentioned storage medium may include, but is not limited to, various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0164] An embodiment of the present invention further provides a computer program product, including a computer program and / or instructions, which, when executed by a processor, implements the intermittent fault handling method as described in any one of the method embodiments.

[0165] It can be seen from the embodiments provided by the present invention that in the present invention, after obtaining the current fault data of the target system, the current fault data is firstly subjected to a storage mark detection to determine whether the current fault data needs to be displayed, or needs to be displayed or stored, and then the fault data displayed on the fault display interface can be distinguished according to the storage mark information, thereby improving the intuitiveness of the fault data distinction, thereby enabling the user to understand the source of the data and improving the confidence in the source of the data; in addition, for the storage and display of the fault data, the new data or updated data in the fault storage database and the fault display interface is determined according to the current counting information corresponding to the current fault data, which can reduce the repeated recording and redundant display of the same fault data, thereby reducing the amount of data and improving the efficiency of troubleshooting.

[0166] It should be noted that various embodiments of the present disclosure have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes are obvious to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The choice of terms used in this article is intended to best explain the principles of the embodiments, practical applications, or technical improvements in the market, or to enable other ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A method for handling intermittent faults, characterized in that: The method comprises: Acquire current fault data of the target system; the current fault data at least includes current fault information and current fault time; Performing storage mark detection on the current fault data to obtain a mark detection result; In a case where the mark detection result indicates that the current fault data includes storage mark information, determining current counting information corresponding to the current fault data; If the current count information is 1, the current fault information, the current fault time and the current count information are stored in the fault storage database, and the current fault information, the current fault time, the storage mark information and the current count information are displayed on the fault display interface; If the current count information is greater than 1, the historical fault time and the historical count information corresponding to the current fault information are updated in the fault storage database, and the historical fault time and the historical count information corresponding to the current fault information are updated on the fault display interface.

2. The intermittent fault processing method according to claim 1, characterized in that: Before obtaining the current fault data of the target system, the method includes: Acquire a fault storage requirement matching the target system; A storage requirement database is constructed based on the fault storage requirement; the storage requirement database includes a mapping relationship between each fault information and the storage mark information.

3. The intermittent fault processing method according to claim 2, characterized in that: The performing storage mark detection on the current fault data to obtain a mark detection result includes: Based on the storage demand database, searching the current fault information to obtain a fault search result; When the fault search result indicates that there is a target mapping relationship corresponding to the current fault information in the storage demand database, determining that the tag detection result is that the current fault data includes the storage tag information, and determining the storage tag information corresponding to the current fault information based on the target mapping relationship; When the fault search result indicates that the target mapping relationship corresponding to the current fault information does not exist in the storage demand database, it is determined that the mark detection result is that the current fault data does not include the storage mark information.

4. The intermittent fault processing method according to claim 1, characterized in that: The current counting information includes first counting information for counting the number of times the current fault data appears in the fault storage database, and second counting information for counting the number of times the current fault data appears in the fault display interface; The determining current counting information corresponding to the current fault data includes: accessing the fault storage database; Based on the fault storage database, performing fault matching on the current fault data to obtain a first matching result; When the first matching result indicates that the current fault data exists in the fault storage database, determining a first fault interval time based on the historical fault time corresponding to the current fault data in the fault storage database and the current fault time; comparing the first fault interval time with a preset interval time, and determining that the first counting information corresponding to the current fault data is greater than 1 when the first fault interval time is less than the preset interval time; When the first matching result indicates that the current fault data does not exist in the fault storage database, it is determined that the first counting information corresponding to the current fault data is equal to 1.

5. The intermittent fault processing method according to claim 4, characterized in that: The determining current counting information corresponding to the current fault data includes: Accessing the fault display interface; Based on the fault display interface, performing fault matching on the current fault data to obtain a second matching result; In the case where the second matching result indicates that the current fault data exists in the fault display interface, determining a second fault interval time based on the historical fault time corresponding to the current fault data in the fault display interface and the current fault time; comparing the second fault interval time with a preset interval time, and determining that the second counting information corresponding to the current fault data is greater than 1 when the second fault interval time is less than the preset interval time; When the second matching result indicates that the current fault data does not exist in the fault display interface, it is determined that the second counting information corresponding to the current fault data is equal to 1.

6. The intermittent fault processing method according to claim 1, characterized in that: The fault display interface corresponds to a fault quantity threshold; The method further comprises: When the number of fault information displayed in the fault display interface is equal to the fault number threshold, at least one piece of fault information in the fault display interface is deleted.

7. The intermittent fault processing method according to claim 1, characterized in that: The fault display interface corresponds to a fault quantity threshold; The method further comprises: When the number of fault data displayed in the fault display interface is equal to the fault number threshold, sequentially traverse each fault information in the fault display interface and access the fault storage database; In the case where there is a piece of fault information stored in the fault storage database, the fault information is deleted from the fault display interface.

8. An intermittent fault handling device, characterized in that: The device comprises: A data acquisition module, used to acquire current fault data of the target system; the current fault data at least includes current fault information and current fault time; A mark detection module, used for performing storage mark detection on the current fault data to obtain a mark detection result; a count determination module, configured to determine current count information corresponding to the current fault data when the mark detection result indicates that the current fault data includes storage mark information; A first processing module, configured to store the current fault information, the current fault time, and the current count information in a fault storage database if the current count information is 1, and display the current fault information, the current fault time, the storage mark information, and the current count information on a fault display interface; The second processing module is used to update the historical fault time and historical counting information corresponding to the current fault information in the fault storage database if the current counting information is greater than 1, and to update the historical fault time and historical counting information corresponding to the current fault information in the fault display interface.

9. An electronic device, characterized in that: The electronic device includes a processor and a memory, wherein the memory stores at least one instruction and at least one program, and the at least one instruction and the at least one program are loaded and executed by the processor to implement the intermittent fault handling method as described in any one of claims 1-7.

10. A computer storage medium, characterized in that: The computer storage medium stores at least one instruction and at least one program, and the at least one instruction and the at least one program are loaded and executed by the processor to implement the intermittent fault handling method as described in any one of claims 1-7.

11. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the intermittent fault handling method as described in any one of claims 1-7 is implemented.

Images