Fault repair strategy determination method and device and readable storage medium

Abstract

The invention discloses a fault repair strategy determination method and device and a readable storage medium. The method comprises the following steps: acquiring fault alarm information of a to-be-repaired system; based on the fault alarm information, determining a fault identification code corresponding to the fault alarm information, the fault identification code being used for identifying the fault alarm information; based on the fault identification code and the fault alarm information, event object information corresponding to the fault alarm information is determined, and the event object information is used for indicating historical fault identification codes stored in a database and / or object information corresponding to historical fault alarm information; and based on the event object information, determining a fault repair strategy which is used for indicating a repair rule of a fault corresponding to the fault alarm information. The technical problem that the fault processing efficiency of the to-be-repaired system is low is solved.

Description

Technical Field

[0001] The present invention relates to the field of fault repair technology, and in particular to a method, device and readable storage medium for determining a fault repair strategy. Background Art

[0002] At present, due to the large number and complex business of the current civil aviation system, each fault alarm is different, and the actual handler is also different. When the system fails, the purpose of quickly locating and repairing the fault is not achieved. The existing fault handling process is that when the operation and maintenance personnel receive the fault alarm in the system, they manually log in to the operation and maintenance management platform, enter the current fault information into the knowledge base module for matching, and then use the matching results to find the most relevant business direction through subjective analysis, and finally manually call to contact the colleague as the event manager to lead the fault investigation and processing.

[0003] In the related art, the operation and maintenance personnel determine the personnel of the event manager based on their personal experience and subjective judgment, which leads to the risk of subjective judgment errors by the operation and maintenance personnel, and the manual phone call greatly reduces the efficiency of the event manager confirmation process and increases the time for fault handling. Therefore, there is a technical problem of low fault handling efficiency of the system to be repaired.

[0004] With respect to the above-mentioned technical problem of low efficiency in fault handling of the system to be repaired, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present invention provide a method, an apparatus and a readable storage medium for determining a fault repair strategy, so as to at least solve the technical problem of low fault processing efficiency of a system to be repaired.

[0006] According to one aspect of an embodiment of the present invention, a method for determining a fault repair strategy is provided. The method may include: obtaining fault alarm information of a system to be repaired; determining a fault identification code corresponding to the fault alarm information based on the fault alarm information, wherein the fault identification code is used to identify the fault alarm information; determining event object information corresponding to the fault alarm information based on the fault identification code and the fault alarm information, wherein the event object information is used to indicate object information corresponding to historical fault identification codes and / or historical fault alarm information stored in a database; determining a fault repair strategy based on the event object information, wherein the fault repair strategy is used to indicate a repair rule for the fault corresponding to the fault alarm information.

[0007] Optionally, based on the fault alarm information, determining the fault identification code corresponding to the fault alarm information includes: disassembling the fault alarm information, and classifying and integrating the disassembled fault alarm information to obtain multiple fault alarm sub-information; and determining the fault identification codes of the multiple fault alarm sub-information according to the coding strategy, wherein the coding strategy is used to indicate the rules for determining the fault identification code.

[0008] Optionally, based on the fault identification code and the fault alarm information, the event object information corresponding to the fault alarm information is determined, including: matching the fault identification code and the fault alarm information with the historical fault identification code and the historical fault alarm information stored in the database respectively to obtain a matching result; and determining the event object information based on the matching result.

[0009] Optionally, based on the matching results, event object information is determined, including: in response to the matching results being a fault identification code and a fault alarm information, successfully matching the historical fault identification code and the historical fault alarm information stored in the database respectively, and determining the historical event object information corresponding to the historical fault identification code and the historical fault alarm information as the event object information.

[0010] Optionally, determining a fault repair strategy based on the event object information includes: extracting an event object identification code from the event object information, wherein the event object identification code is used to identify the event object information; and determining a fault repair strategy based on the event object identification code.

[0011] Optionally, the method for determining a fault repair strategy further includes: outputting the fault repair strategy, and converting the fault repair strategy into storage data and storing it in a database.

[0012] According to another aspect of an embodiment of the present invention, a device for determining a fault repair strategy is also provided. The device may include: an acquisition unit, configured to acquire fault alarm information of a system to be repaired; a first determination unit, configured to determine a fault identification code corresponding to the fault alarm information based on the fault alarm information, wherein the fault identification code is used to identify the fault alarm information; a second determination unit, configured to determine event object information corresponding to the fault alarm information based on the fault identification code and the fault alarm information, wherein the event object information is used to indicate object information corresponding to historical fault identification codes and / or historical fault alarm information stored in a database; and a third determination unit, configured to determine a fault repair strategy based on the event object information, wherein the fault repair strategy is used to indicate the repair of the fault corresponding to the fault alarm information.

[0013] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein when the program is executed by a processor, the device where the storage medium is located is controlled to execute the method for determining the fault repair strategy in an embodiment of the present invention.

[0014] According to another aspect of an embodiment of the present invention, a processor is provided, which is used to run a program, wherein the method for determining a fault repair strategy in an embodiment of the present invention is executed when the program is running.

[0015] According to another aspect of the embodiment of the present invention, a computer program product is provided, which includes computer instructions, and when the computer instructions are executed by a processor, the method for determining the fault repair strategy in the embodiment of the present invention is implemented.

[0016] In an embodiment of the present invention, the fault alarm information of the system to be repaired is obtained; based on the fault alarm information, the fault identification code corresponding to the fault alarm information is determined, wherein the fault identification code is used to identify the fault alarm information; based on the fault identification code and the fault alarm information, the event object information corresponding to the fault alarm information is determined, wherein the event object information is used to indicate the object information corresponding to the historical fault identification code and / or historical fault alarm information stored in the database; based on the event object information, the fault repair strategy is determined, wherein the fault repair strategy is used to indicate the repair rules of the fault corresponding to the fault alarm information. That is to say, the embodiment of the present invention determines the corresponding fault identification code by analyzing the fault alarm information, thereby determining the event object information according to the fault identification code and the fault alarm information, and then obtaining the fault repair strategy. Since the present invention can automatically process the fault alarm information and obtain the fault repair strategy, the problem of long fault handling time caused by human intervention is avoided, the technical problem of low fault handling efficiency of the system to be repaired is solved, and the technical effect of improving the fault handling efficiency of the system to be repaired is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0018] Figure 1 is a flow chart of a method for determining a fault repair strategy according to an embodiment of the present invention;

[0019] Figure 2 is a schematic diagram of an information system fault alarm automatic processing and voice dialing system according to an embodiment of the present invention;

[0020] Figure 3 is a flow chart of an automated event manager confirmation and telephone voice dialing method according to an embodiment of the present invention;

[0021] Figure 4 2 is a schematic diagram of a device for determining a fault repair strategy according to an embodiment of the present invention. DETAILED DESCRIPTION

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

[0023] 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 interchanged 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, functional component or device 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, functional components or devices.

[0024] According to an embodiment of the present invention, an embodiment of a method for determining a fault repair strategy is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0025] Figure 1 is a flow chart of a method for determining a fault repair strategy according to an embodiment of the present invention. Figure 1 As shown, the method may include the following steps:

[0026] Step S101, obtaining fault alarm information of the system to be repaired.

[0027] In the technical solution provided in the above step S101 of the present invention, the fault alarm information is a type of fault information, which is used to indicate the fault existing in the system to be repaired.

[0028] In this embodiment, the fault alarm information of the system to be repaired is obtained. For example, the fault alarm information of the system to be repaired is obtained through a fault analysis module. This is only an illustrative example and does not limit the specific method of obtaining the fault alarm information of the system to be repaired.

[0029] For example, the fault analysis module of the fault alarm platform receives the alarm fault information through the Kafka queue (Apache Kafka, referred to as Kafka).

[0030] Step S102: determining a fault identification code corresponding to the fault alarm information based on the fault alarm information.

[0031] In the technical solution provided in the above step S102 of the present invention, the fault identification code is used to identify the fault alarm information. The fault identification code may also be called a fault identity document (ID for short), a fault type ID or a fault identification ID.

[0032] In this embodiment, after the fault alarm information of the system to be repaired is obtained in step S101, the fault identification code corresponding to the fault alarm information is determined according to the fault alarm information. For example, the fault identification code corresponding to the fault alarm information is determined by an event analysis module, and the event analysis module can be used to assign a unique fault identification ID to the fault alarm information. This is only an illustrative example, and the specific method for determining the fault identification code corresponding to the fault alarm information is not limited.

[0033] Step S103: determining event object information corresponding to the fault alarm information based on the fault identification code and the fault alarm information.

[0034] In the technical solution provided in the above step S103 of the present invention, the event object information is used to indicate the object information corresponding to the historical fault identification code and / or historical fault alarm information stored in the database. The event object information may also be referred to as event manager information.

[0035] In this embodiment, after the fault identification code corresponding to the fault alarm information is determined in step S102, the event object information corresponding to the fault alarm information is determined according to the fault identification code and the fault alarm information. For example, the event object information corresponding to the fault alarm information is determined by the event manager positioning engine. This is only an illustrative example and does not limit the specific method for determining the event object information corresponding to the fault alarm information.

[0036] For example, the event analysis module outputs the fault type ID to the knowledge base module. The knowledge base module matches the fault alarm information in the knowledge base with the most similar historical records based on the fault type ID input, and outputs the unique ID of the event manager of the historical fault to the event manager location engine. The event manager location engine is responsible for locating accurate event manager information.

[0037] Step S104: determine a fault repair strategy based on the event object information.

[0038] In the technical solution provided in the above step S104 of the present invention, the fault repair strategy is used to indicate the repair rule of the fault corresponding to the fault alarm information.

[0039] In this embodiment, after determining the event object information corresponding to the fault alarm information in step S103, the fault repair strategy is determined according to the event object information. For example, the telephone information of the event object is determined according to the event object information, so as to make a call and obtain the fault repair strategy according to the voice content. This is only an illustrative example and does not limit the specific method of determining the fault repair strategy.

[0040] For example, after the knowledge base module outputs the matched event manager unique identification ID to the event manager location engine, the event manager location engine will perform personnel matching based on the received event manager information unique ID, output the searched telephone information to the automated voice dialing engine, and feed the final result information back to the knowledge base module for recording, and determine the fault repair strategy based on the recorded content.

[0041] It should be noted that the above embodiment can be executed through the automatic processing of information system fault alarm and voice dialing device.

[0042] In the above steps S101 to S104 of the present invention, the fault alarm information of the system to be repaired is obtained; based on the fault alarm information, the fault identification code corresponding to the fault alarm information is determined, wherein the fault identification code is used to identify the fault alarm information; based on the fault identification code and the fault alarm information, the event object information corresponding to the fault alarm information is determined, wherein the event object information is used to indicate the object information corresponding to the historical fault identification code and / or historical fault alarm information stored in the database; based on the event object information, the fault repair strategy is determined, wherein the fault repair strategy is used to indicate the repair rule of the fault corresponding to the fault alarm information. That is to say, the embodiment of the present invention determines the corresponding fault identification code by analyzing the fault alarm information, thereby determining the event object information according to the fault identification code and the fault alarm information, and then obtaining the fault repair strategy. Since the present invention can automatically process the fault alarm information and obtain the fault repair strategy, the problem of long fault handling time caused by human intervention is avoided, the technical problem of low fault handling efficiency of the system to be repaired is solved, and the technical effect of improving the fault handling efficiency of the system to be repaired is achieved.

[0043] The above method of this embodiment is further introduced below.

[0044] As an optional implementation method, step S102, based on the fault alarm information, determines the fault identification code corresponding to the fault alarm information, including: disassembling the fault alarm information, and classifying and integrating the disassembled fault alarm information to obtain multiple fault alarm sub-information; according to the coding strategy, determining the fault identification codes of the multiple fault alarm sub-information, wherein the coding strategy is used to indicate the rules for determining the fault identification code.

[0045] In this embodiment, the fault alarm information is preprocessed to obtain multiple fault alarm sub-information. For example, the fault alarm information is disassembled by a fault analysis module, and the disassembled contents are classified and integrated to obtain multiple fault alarm sub-information.

[0046] Optionally, since the current fault alarm information contains a lot of content, but the field information that has matching value to the system is limited, the fault alarm information needs to be automatically analyzed and disassembled before being input into the knowledge base module.

[0047] Optionally, after obtaining the plurality of fault alarm sub-information, the fault identification codes of the plurality of fault alarm sub-information are determined according to a coding strategy, wherein the coding strategy may be a digital sequence numbering method.

[0048] For example, a digital serial numbering method is used to assign a fault identification ID in the module.

[0049] As an optional implementation method, based on the fault identification code and the fault alarm information, the event object information corresponding to the fault alarm information is determined, including: matching the fault identification code and the fault alarm information with the historical fault identification code and the historical fault alarm information stored in the database, respectively, to obtain a matching result; based on the matching result, determining the event object information.

[0050] In this embodiment, the fault identification code and the fault alarm information are matched with the historical fault identification code and the historical fault alarm information stored in the database to obtain a matching result. For example, after receiving the fault information, the knowledge base module needs to use the two field information of product / software and fault phenomenon to match and compare the historical data in the library to obtain a matching result.

[0051] Optionally, after obtaining the matching result, the event object information is determined according to the matching result. The specific determination method is as shown below.

[0052] As an optional implementation method, event object information is determined based on the matching results, including: in response to the matching results being a fault identification code and a fault alarm information, successfully matching the historical fault identification code and the historical fault alarm information stored in a database respectively, and determining the historical event object information corresponding to the historical fault identification code and the historical fault alarm information as the event object information.

[0053] In this embodiment, when the matching result is a fault identification code and a fault alarm information, and they are respectively successfully matched with the historical fault identification code and the historical fault alarm information stored in the database, it is explained that the historical event object information corresponding to the historical fault identification code and the historical fault alarm information can be the event object information corresponding to the fault identification code and the fault alarm information, based on which the historical event object information corresponding to the historical fault identification code and the historical fault alarm information can be determined as the event object information. For example, by ranking the similarity, the historical fault identification code and the historical fault alarm information that are successfully matched are determined.

[0054] For example, the similarity ranking is output based on the matching results, and the historical fault information with the highest similarity is automatically selected as the final target information, and the event manager personnel information in the target information is used as the event manager for this fault handling. There are two conditions for a successful match: 1. The fault information must be ranked first in the matching results; 2. The matching similarity must be above the matching threshold; if the above two conditions cannot be met at the same time, the match fails. Because if the matching symbol is lower than the matching threshold, it means that there is no highly similar information in the knowledge base. Even if this information is output as a search result, it is likely to cause inaccurate positioning of the event manager, and the actual effect will be greatly reduced.

[0055] As an optional implementation method, determining a fault repair strategy based on event object information includes: extracting an event object identification code from the event object information, wherein the event object identification code is used to identify the event object information; and determining a fault repair strategy based on the event object identification code.

[0056] In this embodiment, an event object identification code is extracted from the event object information, wherein the event object identification code may also be referred to as an event manager identification ID.

[0057] For example, the knowledge base module outputs the searched event manager personnel information and online conference number information to the event manager positioning engine, and the event manager positioning engine extracts the event manager identification ID from the event manager personnel information.

[0058] Optionally, the fault repair strategy is determined based on the event object identification code. For example, the telephone number information of the event manager is determined based on the event object identification code, and the telephone number information of the event manager is output to the automatic voice dialing engine, which completes the automatic voice dialing and feeds back the dialed voice content to the knowledge base module, which determines the fault repair strategy based on the content.

[0059] As an optional implementation manner, the method for determining a fault repair strategy further includes: outputting the fault repair strategy and storing the fault repair strategy in a database.

[0060] In this embodiment, the fault repair strategy is output and stored in a database. For example, the knowledge base module outputs the fault repair strategy and records it in a database.

[0061] Optionally, by recording the fault repair strategy, when the same fault problem occurs subsequently, the fault repair strategy corresponding to the fault problem can be quickly determined.

[0062] It should be noted that the above embodiment can be executed through the automatic processing of information system fault alarm and voice dialing device.

[0063] In this embodiment, the fault alarm information of the system to be repaired is obtained; based on the fault alarm information, the fault identification code corresponding to the fault alarm information is determined, wherein the fault identification code is used to identify the fault alarm information; based on the fault identification code and the fault alarm information, the event object information corresponding to the fault alarm information is determined, wherein the event object information is used to indicate the object information corresponding to the historical fault identification code and / or historical fault alarm information stored in the database; based on the event object information, the fault repair strategy is determined, wherein the fault repair strategy is used to indicate the repair rules of the fault corresponding to the fault alarm information. That is to say, the embodiment of the present invention determines the corresponding fault identification code by analyzing the fault alarm information, thereby determining the event object information according to the fault identification code and the fault alarm information, and then obtaining the fault repair strategy. Since the present invention can automatically process the fault alarm information and obtain the fault repair strategy, the problem of long fault handling time caused by human intervention is avoided, the technical problem of low fault handling efficiency of the system to be repaired is solved, and the technical effect of improving the fault handling efficiency of the system to be repaired is achieved.

[0064] The technical solution of the embodiment of the present invention is illustrated below in conjunction with preferred implementation modes.

[0065] At present, due to the large number and complex business of the current civil aviation system, each fault alarm is different, and the actual handler is also different. When the system fails, the purpose of quickly locating and repairing the fault is not achieved. The existing fault handling process is that when the operation and maintenance personnel receive the fault alarm in the system, they manually log in to the operation and maintenance management platform, enter the current fault information into the knowledge base module for matching, and then use the matching results to find the most relevant business direction through subjective analysis, and finally manually call to contact the colleague as the event manager to lead the fault investigation and processing.

[0066] In the related technology, the operation and maintenance personnel determine the event manager based on their personal experience and subjective judgment. This poses the risk of subjective misjudgment by the operation and maintenance personnel, and manually dialing the phone greatly reduces the efficiency of the event manager confirmation process and increases the time required for fault handling. At the same time, the company currently relies entirely on manual processing in the process of locating the event manager. When a fault occurs, the front-line operation and maintenance personnel need to respond to the fault on the first platform, search and locate the event manager on the second platform, and then search for the event manager's phone number on the third platform, and finally pick up the phone and manually dial the event manager's phone number to let him serve as the event manager and participate in the online troubleshooting meeting. This process takes about 10 minutes to complete, which consumes too much time and affects the efficiency of troubleshooting. At the same time, there will also be situations where the operation and maintenance personnel have to make a second confirmation of the event manager due to misjudgment during the event manager confirmation process, which is even more time-consuming; fault handling races against time, and the current event manager confirmation method greatly increases the fault recovery time and seriously affects the fault handling process. In summary, the present invention combines the company's business development direction and the characteristics of fault occurrence, based on the mainstream architecture of information system microservices and Python development language, to construct a method and device for automatic voice dialing of fault alarms, eliminate the hidden dangers of inaccurate positioning of event managers, and realize automatic dialing of event managers, thereby improving work efficiency and production system security.

[0067] At the same time, when a fault occurs, the existing company event manager confirmation method is to determine the event manager based solely on the work experience of the operation and maintenance personnel. The processing process is completely manual, the processing method is too backward, and there is a great risk of the accuracy of the event manager confirmation, and the efficiency of manual phone calls is extremely low. First of all, this event manager confirmation method is too dependent on the experience and work status of the operation and maintenance personnel, and the risk is extremely high. Whether the operation and maintenance personnel make subjective or non-subjective operational errors, it will have irreparable serious consequences for the company's production safety plan, and it is more likely to cause customer complaints, which will have an extremely bad impact on the company; secondly, the manual event manager confirmation method can no longer meet the company's business system processing volume. The manual processing method has not kept up with the development of the times in terms of production safety and fault recovery timeliness, and can no longer meet the company's requirements for fault recovery within the specified time. Therefore, there is a technical problem of low fault handling efficiency in the system to be repaired.

[0068] With respect to the above-mentioned technical problem of low efficiency in fault handling of the system to be repaired, no effective solution has been proposed yet.

[0069] However, the embodiment of the present invention proposes a method for automatic processing of information system fault alarms and voice dialing, in which fault alarm information is received through a fault analysis module, the received fault alarm is disassembled and integrated, and each integrated information of the fault analysis module is given a unique fault ID. The integrated information of the fault alarm is transmitted to the knowledge base module through the kafka message queue. After receiving the incoming information, the knowledge base module searches and records the historical process. The knowledge base module outputs the searched event manager personnel information and online conference number information to the event manager positioning engine, including the personnel unique identification ID. After the event manager positioning engine accurately matches the event manager, it outputs the event manager personnel information and online conference number information to the automated voice dialing engine module. According to the execution order of the scheduling program, the automated voice dialing program is executed in sequence. The voice dialing result record is returned to the knowledge base module. Finally, the knowledge base module displays the detailed information of the full process results. The technical problem of low fault handling efficiency of the system to be repaired is solved, and the technical effect of improving the fault handling efficiency of the system to be repaired is achieved.

[0070] The embodiments of the present invention are further described below.

[0071] Figure 2 Schematic diagram of an information system fault alarm automatic processing and voice dialing system according to an embodiment of the present invention. Figure 2 As shown, the information system fault alarm automatic processing and voice dialing system 200 includes: a fault analysis module 201, a knowledge base module 202, an event manager positioning engine 203, an automatic voice dialing engine 204 and a fault alarm platform 205.

[0072] Fault analysis module 201: It is the only output port of fault alarm platform 205. After receiving the alarm through Kafka, fault analysis module 201 disassembles and integrates the fault information, and then outputs the analyzed field information to knowledge base module 202 through Kafka. Since the current fault alarm information contains a lot of content, but the field information with matching value to the system is limited, it is necessary to automatically analyze and disassemble the fault alarm information before inputting it into the knowledge base module 202.

[0073] Knowledge base module 202: The knowledge base module 202 records the association between fault alarms and event manager history. When an event occurs, after the fault analysis module 201 completes the fault information analysis and disassembly, the event analysis module outputs the fault type ID and other valuable information to the knowledge base module 202. The knowledge base module 202 will match the most similar information of the fault alarm in the knowledge base based on the input information, and output the event manager unique identification ID of the historical fault to the event manager positioning engine 203.

[0074] Event manager location engine 203: This engine is mainly responsible for locating accurate event manager information. Currently, there are hundreds of event manager candidates in the company. When the knowledge base module 202 outputs the matched event manager unique identification ID to the event manager location engine 203, the engine will match the personnel based on the received event manager information unique ID, output the searched phone information to the automatic voice dialing engine 204, and feed back the final result information to the knowledge base module 202 for recording, so as to help the knowledge base module 202 to update and record the corresponding information of the fault alarm and the event manager.

[0075] Automatic voice dialing engine 204: Automatic voice dialing engine 204 is mainly responsible for dialing and information feedback. When the event manager positioning engine 203 transmits the event manager information personnel ID to the automatic voice dialing engine 204, the engine implements automatic voice dialing and records the feedback information after dialing.

[0076] Figure 3 FIG. 1 is a flow chart of an automated event manager confirmation and telephone voice dialing method according to an embodiment of the present invention. Figure 3 As shown, the automated event manager confirmation and telephone voice dialing method includes the following steps:

[0077] Step S301, disassemble and integrate the received fault alarm.

[0078] In this embodiment, the fault analysis module receives fault alarm information, disassembles and integrates the received fault alarm, and assigns a unique fault ID to each integrated information of the fault analysis module.

[0079] Step S302: Transmit the integrated fault alarm information to the knowledge base module.

[0080] In this embodiment, the integrated information of the fault alarm is transmitted to the knowledge base module through the Kafka message queue.

[0081] Step S303, searching and recording the historical process according to the input information.

[0082] In this embodiment, the knowledge base module searches and records the historical process after receiving the incoming information.

[0083] Step S304, determining the event manager information and online conference number information.

[0084] In this embodiment, the knowledge base module outputs the searched event manager personnel information and online conference number information to the event manager positioning engine, including the personnel unique identification ID.

[0085] Step S305, matching event managers.

[0086] In this embodiment, after the event manager positioning engine accurately matches the event manager, it outputs the event manager personnel information and online conference number information to the automated voice dialing engine module.

[0087] Step S306, executing the automated voice dialing procedure.

[0088] In this embodiment, the automated voice dialing program is executed sequentially according to the execution order of the scheduled programs.

[0089] Step S307, obtaining the voice dialing result.

[0090] In this embodiment, the voice dialing result record is returned to the knowledge base module.

[0091] Step S308, display detailed information of the whole process results.

[0092] In this embodiment, the knowledge base module displays detailed information on the results of the entire process.

[0093] The embodiments of the present invention are further described below through specific examples.

[0094] The fault alarm information of the fault alarm platform is as follows:

[0095]

XXX information

[0096] Report a problem! 22:16 Received reports from agent users (user 1, user 2, user 3)

[0097]

[0098] Fault phenomenon: In a certain system, the first ticket fails and the ticket extraction status is the first status

[0099] Fault error: None

[0100] Optionally, after receiving the fault alarm from the fault alarm platform, the fault analysis module disassembles and integrates the alarm information, extracts the information content of the product / software and fault phenomenon fields, and ignores all other alarm information, because the fault information in the knowledge base module only uses the above two fields for similarity matching; then the information extracted from the fault is assigned a unique identification ID, and then output to the knowledge base module. For example, the fields of the fault information are: fault reporting information, time, software / product, software attributes, fault phenomenon, and fault error. The fault analysis module discards all other fields, leaving only the product / software and fault phenomenon fields, and extracts the content information in the two fields; the unique identification ID does not exist in the original fault information, and it is necessary to assign a fault identification ID in the module, which can be assigned using a digital serial numbering method.

[0101] Optionally, after receiving the fault information, the knowledge base module needs to use the two field information of product / software and fault phenomenon to compare the historical data in the library. After the matching is completed, the similarity ranking is output according to the matching results. The program automatically selects the historical fault information with the highest similarity as the final target information, and uses the event manager personnel information in the target information as the event manager for this fault handling.

[0102] Optionally, each piece of information in the program must have a unique identification symbol, and the searched target information is no exception, so the searched event manager personnel information is used as the unique identification ID, and then output to the event manager positioning engine module, and the online meeting number information is also sent together; after the knowledge base module completes the match and outputs the information, the knowledge base module needs to record the current output information history record into the knowledge base search history, and record the full process status of the search in the database.

[0103] Optionally, the knowledge base module focuses on the historical fault similarity matching. Each search will search out many results, which are arranged in descending order according to different matching degrees. However, the knowledge base outputs only one search result, so the information with the highest matching symbol needs to be output as the result to the event manager positioning engine module. The knowledge base needs to meet two conditions at the same time when searching and outputting the matching results internally: 1. It must be the fault information ranked first in the matching result; 2. The matching similarity must be above 80%; if the above two conditions cannot be met at the same time, the match fails. Because if the matching symbol is lower than 80%, it means that there is no highly similar information in the knowledge base. Even if this information is output as a search result, it is likely to cause inaccurate positioning of the event manager, and the actual effect will be greatly reduced. Among them, the number 80% will also be slightly adjusted according to the actual situation, and a threshold that best suits the actual situation will be found and set in the program to better meet the business needs of the event manager's automated voice dialing.

[0104] Optionally, the event manager locating engine stores the event manager's information in advance in the database. When the event manager locating engine receives the event manager's information, it uses the event manager's unique identification ID to perform a matching search in the database. After searching for the event manager's information, it outputs the event manager's phone number information to the automated voice dialing engine, which then completes the automatic voice dialing.

[0105] Optionally, the automated voice dialing engine will make a voice call after receiving the information. When designing the program, we will design two rules for the automated voice dialing engine when making voice calls based on the current company business status and actual situation: 1. The person being dialed must listen to all the voice messages of the automated voice after answering the call to be considered a successful call, otherwise it will be dialed again; 2. If no one answers or the call is not connected, a second call will be made every 1 minute until the call is successful.

[0106] Optionally, when the event manager receives an automated voice call, he needs to listen to the message completely, and the voice message only needs to include the product / software and fault phenomenon output by the fault analysis module, because the event manager will receive a mobile phone text message related to the fault before receiving the call. If the event manager wants to know the detailed information of the fault, he can check his mobile phone text message after hanging up the phone; when the event manager receives a call, it means that the fault is strongly related to the area he is responsible for, and he needs to immediately enter the online troubleshooting meeting. The meeting number is stored in the knowledge base module database and will be sent to the event manager's mobile phone text message along with the automated voice. If the event manager's call is not answered or not connected, this situation is not considered a successful automated voice call, and the event manager's positioning engine program will call again after an interval of 1 minute until the call is successful.

[0107] Optionally, the historical results of both the event manager location engine and the automated voice dialing engine will be fed back to the knowledge base module, which will receive and record them in the database. At the same time, the operation and maintenance personnel will view the running status of the entire process of current fault search and matching on the knowledge base page, so that each automation and voice dialing process can be controlled by the operation and maintenance personnel. Among them, the information transmission between the fault analysis module, knowledge base module, event manager location engine, and automated voice dialing engine all adopts the transmission method of kafka queue.

[0108] In this embodiment, the fault alarm information is received by the fault analysis module, and the received fault alarm is disassembled and integrated, and each integrated information of the fault analysis module is given a unique fault ID. The integrated information of the fault alarm is transmitted to the knowledge base module through the kafka message queue. After receiving the incoming information, the knowledge base module searches and records the historical process. The knowledge base module outputs the searched event manager personnel information and online conference number information to the event manager positioning engine, including the personnel unique identification ID. After the event manager positioning engine accurately matches the event manager, it outputs the event manager personnel information and online conference number information to the automated voice dialing engine module. According to the execution order of the scheduling program, the automated voice dialing program is executed in sequence. The voice dialing result record is returned to the knowledge base module. Finally, the knowledge base module displays the detailed information of the full process results. The technical problem of low fault handling efficiency of the system to be repaired is solved, and the technical effect of improving the fault handling efficiency of the system to be repaired is achieved.

[0109] According to an embodiment of the present invention, a device for determining a fault repair strategy is also provided. It should be noted that the device for determining a fault repair strategy can be used to execute the method for determining a fault repair strategy in the method embodiment.

[0110] Figure 4 FIG. 1 is a schematic diagram of a device for determining a fault repair strategy according to an embodiment of the present invention. Figure 4 As shown, the apparatus 400 for determining a fault repair strategy may include: an acquisition unit 401 , a first determination unit 402 , a second determination unit 403 , and a third determination unit 404 .

[0111] The acquisition unit 401 is used to acquire the fault alarm information of the system to be repaired.

[0112] The first determining unit 402 is configured to determine a fault identification code corresponding to the fault alarm information based on the fault alarm information, wherein the fault identification code is used to identify the fault alarm information.

[0113] The second determination unit 403 is used to determine event object information corresponding to the fault alarm information based on the fault identification code and the fault alarm information, wherein the event object information is used to indicate object information corresponding to historical fault identification codes and / or historical fault alarm information stored in the database.

[0114] The third determining unit 404 is configured to determine a fault repair strategy based on the event object information, wherein the fault repair strategy is used to indicate the repair of the fault corresponding to the fault alarm information.

[0115] Optionally, the first determination unit 402 may include: a preprocessing module, used to disassemble the fault alarm information, and classify and integrate the disassembled fault alarm information to obtain multiple fault alarm sub-information; a first determination module, used to determine the fault identification code of the multiple fault alarm sub-information according to the coding strategy, wherein the coding strategy is used to indicate the rules for determining the fault identification code.

[0116] Optionally, the second determination unit 403 may include: a matching module, used to match the fault identification code and the fault alarm information with the historical fault identification code and the historical fault alarm information stored in the database respectively to obtain a matching result; and a second determination module, used to determine the event object information based on the matching result.

[0117] Optionally, the second determination module may include: a determination sub-module, which is used to respond to the matching result being a fault identification code and a fault alarm information, and successfully match the historical fault identification code and the historical fault alarm information stored in the database, respectively, and determine the historical event object information corresponding to the historical fault identification code and the historical fault alarm information as the event object information.

[0118] Optionally, the third determination unit 404 may include: an extraction module, used to extract an event object identification code from the event object information, wherein the event object identification code is used to identify the event object information; and a third determination module, used to determine a fault repair strategy based on the event object identification code.

[0119] Optionally, the apparatus 400 for determining a fault repair strategy may further include: a storage unit, configured to output the fault repair strategy and store the fault repair strategy in a database.

[0120] In this embodiment, the fault alarm information of the system to be repaired is obtained; based on the fault alarm information, the fault identification code corresponding to the fault alarm information is determined, wherein the fault identification code is used to identify the fault alarm information; based on the fault identification code and the fault alarm information, the event object information corresponding to the fault alarm information is determined, wherein the event object information is used to indicate the object information corresponding to the historical fault identification code and / or historical fault alarm information stored in the database; based on the event object information, the fault repair strategy is determined, wherein the fault repair strategy is used to indicate the repair rules of the fault corresponding to the fault alarm information. That is to say, the embodiment of the present invention determines the corresponding fault identification code by analyzing the fault alarm information, thereby determining the event object information according to the fault identification code and the fault alarm information, and then obtaining the fault repair strategy. Since the present invention can automatically process the fault alarm information and obtain the fault repair strategy, the problem of long fault handling time caused by human intervention is avoided, the technical problem of low fault handling efficiency of the system to be repaired is solved, and the technical effect of improving the fault handling efficiency of the system to be repaired is achieved.

[0121] According to an embodiment of the present invention, a computer-readable storage medium is further provided. The storage medium includes a stored program, wherein the program executes the method for determining the fault repair strategy in the method embodiment.

[0122] According to an embodiment of the present invention, a processor is further provided. The processor is used to run a program, wherein the method for determining a fault repair strategy in the method embodiment is executed when the program is running.

[0123] According to an embodiment of the present invention, a computer program product is further provided. The computer program product includes computer instructions. When the computer instructions are executed by a processor, the method for determining the fault repair strategy in the method embodiment is implemented.

[0124] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0125] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0126] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0127] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed over multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0128] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0129] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent functional component, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software functional component, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc., which can store program codes.

[0130] The above are only preferred embodiments of the present invention. It should be pointed out that, for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for determining a fault repair strategy, characterized in that: include: Obtain fault alarm information of the system to be repaired; Based on the fault alarm information, determining a fault identification code corresponding to the fault alarm information, wherein the fault identification code is used to identify the fault alarm information; Based on the fault identification code and the fault alarm information, determining event object information corresponding to the fault alarm information, wherein the event object information is used to indicate object information corresponding to historical fault identification codes and / or historical fault alarm information stored in a database; Based on the event object information, a fault repair strategy is determined, wherein the fault repair strategy is used to indicate a repair rule for the fault corresponding to the fault alarm information.

2. The method according to claim 1, characterized in that Determining a fault identification code corresponding to the fault alarm information based on the fault alarm information includes: Disassembling the fault alarm information, and classifying and integrating the disassembled fault alarm information to obtain a plurality of fault alarm sub-information; The fault identification codes of the plurality of fault alarm sub-information are determined according to a coding strategy, wherein the coding strategy is used to indicate a rule for determining the fault identification codes.

3. The method according to claim 1, characterized in that: Determining event object information corresponding to the fault alarm information based on the fault identification code and the fault alarm information includes: Matching the fault identification code and the fault alarm information with the historical fault identification code and the historical fault alarm information stored in the database to obtain a matching result; Based on the matching result, the event object information is determined.

4. The method according to claim 3, characterized in that Based on the matching result, determining the event object information includes: In response to the matching result being the fault identification code and the fault alarm information, which are successfully matched with the historical fault identification code and the historical fault alarm information stored in the database respectively, the historical event object information corresponding to the historical fault identification code and the historical fault alarm information is determined as the event object information.

5. The method according to claim 1, characterized in that: Determine a fault repair strategy based on the event object information, including: Extracting an event object identification code from the event object information, wherein the event object identification code is used to identify the event object information; Based on the event object identifier, the fault repair strategy is determined.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The fault recovery strategy is output, and the fault recovery strategy is converted into storage data and stored in a database.

7. A device for determining a fault repair strategy, characterized in that: include: An acquisition unit, used for acquiring fault alarm information of the system to be repaired; A first determining unit, configured to determine a fault identification code corresponding to the fault alarm information based on the fault alarm information, wherein the fault identification code is used to identify the fault alarm information; A second determining unit, configured to determine event object information corresponding to the fault alarm information based on the fault identification code and the fault alarm information, wherein the event object information is used to indicate object information corresponding to historical fault identification codes and / or historical fault alarm information stored in a database; The third determining unit is used to determine a fault repair strategy based on the event object information, wherein the fault repair strategy is used to indicate the repair of the fault corresponding to the fault alarm information.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed by a processor, the device where the storage medium is located is controlled to execute the method according to any one of claims 1 to 6.

9. A processor, characterized in that: The processor is used to run a program, wherein the program executes the method according to any one of claims 1 to 6 when running.

10. A computer program product, characterized in that The computer program product comprises computer instructions, which implement the method according to any one of claims 1 to 6 when executed by a processor.

Images