Fault record acquisition method and device, electronic equipment and readable storage medium

Abstract

The application discloses a fault record acquisition method and device, electronic equipment and a readable storage medium, and belongs to the technical field of computers. The fault record acquisition method comprises the following steps: acquiring voice information of a fault description. The voice information is converted into text information. The text information is preprocessed to acquire fault key information. Based on the fault key information, a filling mode is acquired. Based on the filling mode and the fault key information, a fault record is acquired.

Description

Technical Field

[0001] This application belongs to the field of computer technology, specifically relating to a method and apparatus for obtaining fault records, an electronic device, and a readable storage medium. Background Technology

[0002] In existing technologies, fault logging is a crucial aspect of asset operation and management. Asset managers and responsible personnel need to promptly record the asset's fault history as a vital basis for future statistical analysis of asset failure rates, downtime rates, and average downtime intervals, enabling the analysis of asset reliability. However, due to the diverse asset categories and the large number of assets managed by asset administrators, the following problems exist:

[0003] (1) In daily inspection work, the asset administrator establishes fault records by manually entering data. However, due to the large number of assets, the work is time-consuming and inefficient.

[0004] (2) Due to the large number of asset categories, asset administrators often cannot directly locate the current asset when selecting an asset. They need to select the category first and then select the asset, which is a cumbersome operation.

[0005] (3) When an asset administrator discovers a fault, there is a need for a more timely way to establish a fault record for urgent situations that require immediate handling. Summary of the Invention

[0006] The purpose of this application is to provide a method and apparatus for obtaining fault records, an electronic device and a readable storage medium, which can solve the problem that manually entering fault records is time-consuming and inefficient due to the large number of assets involved.

[0007] In a first aspect, embodiments of this application provide a method for obtaining fault records, comprising: obtaining voice information describing a fault; converting the voice information into text information; preprocessing the text information to obtain key fault information; obtaining a reporting method based on the key fault information; and obtaining a fault record based on the reporting method and the key fault information.

[0008] Secondly, embodiments of this application provide a fault record acquisition device, including a first acquisition module, a first conversion module, a first preprocessing module, a second acquisition module, and a third acquisition module. The first acquisition module is used to acquire voice information describing the fault. The first conversion module is used to convert the voice information into text information. The first preprocessing module is used to preprocess the text information to acquire key fault information. The second acquisition module is used to acquire a reporting method based on the key fault information. The third acquisition module is used to acquire a fault record based on the reporting method and the key fault information.

[0009] Thirdly, embodiments of this application provide an electronic device including a processor and a memory. The memory stores programs or instructions that can run on the processor. When the programs or instructions are executed by the processor, they implement the steps of the fault record acquisition method of the first aspect.

[0010] Fourthly, embodiments of this application provide a readable storage medium on which a program or instructions are stored, and when the program or instructions are executed by a processor, the steps of the fault record acquisition method as described in the first aspect are implemented.

[0011] This embodiment utilizes intelligent speech recognition technology to convert natural language (voice information describing the fault) into machine language (text information) that can be recognized by a computer. Then, it automatically extracts key information (critical fault information) through intelligent analysis technology, and finally directly establishes fault record information. This embodiment can save labor costs and improve office efficiency. Attached Figure Description

[0012] Figure 1 One of the flowcharts of the fault record acquisition method provided in this application is shown;

[0013] Figure 2 The second schematic flowchart of the fault record acquisition method provided in the embodiment of this application is shown;

[0014] Figure 3 The third schematic flowchart of the fault record acquisition method provided in this application embodiment is shown;

[0015] Figure 4 The fourth flowchart of the fault record acquisition method provided in this application embodiment is shown;

[0016] Figure 5 The fifth flowchart of the fault record acquisition method provided in this application embodiment is shown;

[0017] Figure 6 This is illustrated as a sixth flowchart of the fault record acquisition method provided in an embodiment of this application;

[0018] Figure 7A structural block diagram of the fault record acquisition device provided in an embodiment of this application is shown;

[0019] Figure 8 A structural block diagram of the electronic device provided in an embodiment of this application is shown;

[0020] Figure 9 A schematic diagram of the hardware structure of an electronic device according to an embodiment of this application is shown.

[0021] Figure 10 The seventh flowchart of the fault record acquisition method provided in this application embodiment is shown;

[0022] Figure 11 This illustration shows a multi-dimensional analysis diagram of the intelligent selection algorithm provided in an embodiment of this application;

[0023] Figure 12 A schematic diagram of the skill interface relationships provided in an embodiment of this application is shown.

[0024] in, Figures 1 to 12 The correspondence between the reference numerals and component names in the attached drawings is as follows:

[0025] 100: Fault record acquisition device; 110: First acquisition module; 120: First conversion module; 130: First preprocessing module; 140: Second acquisition module; 150: Third acquisition module; 202: First skill interface; 204: Second skill interface; 1000: Electronic device; 1002: Processor; 1004: Memory; 1100: Electronic device; 1101: Radio frequency unit; 1102: Network module; 1103: Audio output unit; 1104: Input unit; 11041: Graphics processor; 11042: Microphone; 1105: Sensor; 1106: Display unit; 11061: Display panel; 1107: User input unit; 11071: Touch panel; 11072: Other input devices; 1108: Interface unit; 1109: Memory; 1110: Processor. Detailed Implementation

[0026] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0027] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0028] The following is in conjunction with the appendix Figures 1 to 12 The present application provides a detailed description of the fault record acquisition method and apparatus, electronic device and readable storage medium provided in the embodiments of this application through specific implementation methods and application scenarios.

[0029] This application provides a method for obtaining fault records. Figure 1 This document illustrates one of the flowcharts of a fault record acquisition method provided in an embodiment of this application, such as... Figure 1 As shown, the methods for obtaining fault records include:

[0030] Step 102: Obtain the voice information describing the fault.

[0031] Step 104: Convert the voice information into text information.

[0032] Step 106: Preprocess the text information to obtain key fault information.

[0033] Step 108: Based on the key fault information, obtain the reporting method.

[0034] Step 110: Obtain the fault record based on the reporting method and key fault information.

[0035] Understandably, in asset management scenarios, it is necessary to establish asset fault records. The relevant technologies mainly rely on manual handwriting or computer text input to establish fault records. However, for scenarios with a large number of assets, these two methods cannot establish fault data in a timely manner, resulting in poor timeliness. Furthermore, human errors are prone to occur during the establishment process, which can affect asset management.

[0036] In this embodiment, the voice information describing the fault is identified and converted into text information. This process avoids manual input and can effectively reduce human error.

[0037] In this embodiment, the text information is preprocessed to obtain key fault information. Based on this key information, a reporting method is automatically selected. Finally, after determining the reporting method, the key fault information is recorded according to the method to obtain a fault record. Traditional manual reporting methods cannot establish fault data in a timely manner, and the data establishment process is time-consuming. The above-mentioned fault record establishment method is automatic and requires no manual intervention, which can improve the real-time performance of fault reporting. This is beneficial for establishing data with high real-time requirements, such as fault information that needs to be processed promptly.

[0038] The fault record in this embodiment may include the asset name, the fault description corresponding to the asset, etc.

[0039] This embodiment utilizes intelligent speech recognition technology to convert natural language (voice information describing the fault) into machine language (text information) that can be recognized by a computer. Then, it automatically extracts key information (critical fault information) through intelligent analysis technology, and finally directly establishes fault record information. This embodiment can save labor costs and improve office efficiency.

[0040] This embodiment transforms the fault reporting method from manual to automatic reporting, reducing manual reporting costs and improving work efficiency. Furthermore, this embodiment improves the real-time performance of fault reporting. Traditional manual reporting methods cannot establish fault data in a timely manner, and the data establishment process is time-consuming. This embodiment is beneficial for fault data reporting scenarios with high real-time requirements.

[0041] In some embodiments of this application, Figure 2 This illustrates a second flowchart of the fault record acquisition method provided in an embodiment of this application, as shown below. Figure 2 As shown, the voice information describing the fault is obtained, specifically including:

[0042] Step 202: Wake up the voice recognition system.

[0043] Step 204: Describe the fault based on the prompts from the voice recognition system.

[0044] Step 206: Control the voice recognition system to collect voice information describing the fault.

[0045] Understandably, the voice recognition system can function as a voice robot. When a user performs an operation, they first access the fault reporting system, activate the voice robot, and directly converse with it, describing the fault based on prompts. The voice robot then collects the voice information describing the fault for subsequent recognition and conversion into text information.

[0046] In this embodiment, the voice robot can recognize key fault information described by the user. Key fault information may include assets, fault descriptions, etc. Subsequently, fault records are established based on the recognized key fault information, reducing the cost of manual data entry and improving office efficiency.

[0047] In some embodiments of this application, Figure 3 The third schematic flowchart of the fault record acquisition method provided in this application embodiment is shown, as follows: Figure 3 As shown, the text information is preprocessed to obtain key fault information, specifically including:

[0048] Step 302: Perform data error correction on the text information.

[0049] Step 304: Filter the text information after data correction to obtain key fault information.

[0050] In this embodiment, data error correction is performed on the text information to improve its accuracy. The corrected text information is then filtered to obtain key fault information. This embodiment improves the accuracy of key fault information through data error correction and filtering.

[0051] In some embodiments of this application, Figure 4 The fourth flowchart of the fault record acquisition method provided in this application embodiment is shown. Figure 4 As shown, the text information after data correction is filtered to obtain key fault information, specifically including:

[0052] Step 402: Set up multiple skill interfaces and combine them into a skill chain.

[0053] Step 404: Use the skill link to filter the text information and obtain the key fault information.

[0054] It is understandable that when users manually enter data, the selectable asset information has already been filtered by data permissions. However, when entering data via voice recognition, it is often possible to bypass data permission controls and identify asset information outside the authorized scope. This embodiment solves the above problem through skill interfaces. First, a series of skill interfaces are defined, each responsible for a data processing task. Then, related skill interfaces are combined into a skill chain. Only after being filtered through the skill chain can useful data be obtained. Figure 12 As shown, the system identifies five asset information entries, from asset A to asset E. These five asset information entries are filtered sequentially through the first skill interface 202 (error correction interface) and the second skill interface 204 (data permission interface), leaving only asset C and asset E as useful data.

[0055] This embodiment solves the problem of data access control for voice data by setting up multiple energy-saving interfaces, making it more adaptable to various application scenarios in asset management.

[0056] In some embodiments of this application, Figure 5 The fifth flowchart illustrating the fault record acquisition method provided in this application is shown in the embodiment. Figure 5 As shown, based on key fault information, the reporting method is obtained, specifically including:

[0057] Step 502: Identify the identification markers in the critical fault information.

[0058] Step 504: If the identification mark is the same as the preset mark, set the filling method to require secondary confirmation.

[0059] Step 506: If the identified identifier is different from the preset identifier, set the filling method to "no secondary confirmation required".

[0060] This embodiment provides two methods for establishing fault records: one that can be established directly without asset administrator confirmation, and another that requires asset administrator confirmation. By setting an identification identifier, the identifier is compared with a preset representation; if they match, a second confirmation is performed, i.e., manual verification.

[0061] This embodiment can intelligently select the reporting method. The first method directly creates a fault record without manual verification. The second method requires secondary confirmation, that is, the fault information is first automatically filled in, and then a secondary confirmation is performed, i.e., manual verification and supplementation of detailed information, before the fault record is created.

[0062] For specialized assets and equipment, users may want to verify or supplement the fault information after it has been automatically entered by the system. This embodiment addresses this by employing an intelligent selection algorithm. Based on multi-dimensional analysis of the identified identifier, the algorithm intelligently selects the appropriate reporting method. The intelligent selection algorithm is described below:

[0063] (1) Specify the dimension of the algorithm analysis (i.e., the identification identifier).

[0064] (2) Set algorithm matching rules, for example: when the identification mark is the same as the preset mark, manual confirmation is required, i.e., secondary confirmation.

[0065] (3) During the algorithm operation, when the identification mark is found to be the same as the preset mark, the user will be triggered to confirm the second time.

[0066] This embodiment provides several flexible automatic fault reporting methods, including a method that directly creates fault records without manual verification, and a method that first automatically fills in fault information and then allows the user to supplement detailed information before creating the fault record. This embodiment can use two methods to create fault records for different asset and fault situations, making it more convenient for users and improving the user experience.

[0067] In some embodiments of this application, the identification identifier includes one or a combination of the following:

[0068] Criticality of assets, technical parameters of assets, types of failures, symptoms of failures, and special equipment.

[0069] In this embodiment, the identification mark can be set according to the application scenario. For example, the identification mark can be the asset criticality level. When the asset criticality level is the fault information of the critical asset, a secondary confirmation action will be triggered to perform manual confirmation.

[0070] This embodiment provides a variety of identification markers, which can analyze assets and faults from multiple dimensions, thereby better identifying situations where users need to make secondary confirmations.

[0071] In some embodiments of this application, Figure 6 The sixth schematic flowchart of the fault record acquisition method provided in this application embodiment is shown, as follows: Figure 6 As shown, based on the reporting method and key fault information, fault records are obtained, specifically including:

[0072] Step 602: Based on the fact that the filling method does not require secondary confirmation, generate a fault record according to the key fault information.

[0073] Step 604: Based on the fact that the filling method requires secondary confirmation, trigger secondary confirmation, fill in the key fault information, add the information after secondary confirmation, and generate a fault record.

[0074] This embodiment provides two flexible automatic fault reporting methods. For faults that do not require secondary confirmation, a fault record is directly created based on key fault information. For faults that require secondary confirmation, key fault information is first automatically filled in, and then the fault record is created after the user adds detailed information (i.e., information for secondary confirmation). This embodiment can better meet user needs, expand its application scope, and meet various application scenarios.

[0075] The fault record acquisition method provided in this application can be executed by a fault record acquisition device. This application uses the execution of the fault record acquisition method by a fault record acquisition device as an example to illustrate the fault record acquisition device provided in this application.

[0076] In some embodiments of this application, a fault record acquisition device is provided. Figure 7 A structural block diagram of the fault record acquisition device provided in an embodiment of this application is shown, such as... Figure 7 As shown, the fault record acquisition device 100 includes a first acquisition module 110, a first conversion module 120, a first preprocessing module 130, a second acquisition module 140, and a third acquisition module 150. The first acquisition module 110 acquires voice information describing the fault. The first conversion module 120 converts the voice information into text information. The first preprocessing module 130 preprocesses the text information to acquire key fault information. The second acquisition module 140 acquires the reporting method based on the key fault information. The third acquisition module 150 acquires the fault record based on the reporting method and the key fault information.

[0077] This embodiment utilizes intelligent speech recognition technology to convert natural language (voice information describing the fault) into machine language (text information) that can be recognized by a computer. Then, it automatically extracts key information (critical fault information) through intelligent analysis technology, and finally directly establishes fault record information. This embodiment can save labor costs and improve office efficiency.

[0078] The fault record acquisition device 100 provided in this application embodiment can implement all the processes of the above-described fault record acquisition method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0079] The fault record acquisition device in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the device.

[0080] The fault record acquisition device in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit it.

[0081] The fault record acquisition device provided in this application embodiment can implement all the processes implemented in the above method embodiment, and will not be described again here to avoid repetition.

[0082] Optionally, such as Figure 8 As shown, this application embodiment also provides an electronic device 1000, which includes a processor 1002 and a memory 1004. The memory 1004 stores a program or instructions that can run on the processor 1002. When the program or instructions are executed by the processor 1002, they implement the various steps of the above method embodiments and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0083] It should be noted that the electronic devices in the embodiments of this application include the aforementioned mobile electronic devices and non-mobile electronic devices.

[0084] Figure 9 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of this application.

[0085] The electronic device 1100 includes, but is not limited to, components such as: radio frequency unit 1101, network module 1102, audio output unit 1103, input unit 1104, sensor 1105, display unit 1106, user input unit 1107, interface unit 1108, memory 1109, and processor 1110.

[0086] Those skilled in the art will understand that the electronic device 1100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 9 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0087] The processor 1110 is used to acquire voice information describing the fault.

[0088] Processor 1110 is used to convert voice information into text information.

[0089] Processor 1110 is used to preprocess text information and obtain key fault information.

[0090] Processor 1110 is used to obtain the reporting method based on critical fault information.

[0091] Processor 1110 is used to obtain fault records based on the reporting method and key fault information.

[0092] This embodiment utilizes intelligent speech recognition technology to convert natural language (voice information describing the fault) into machine language (text information) that can be recognized by a computer. Then, it automatically extracts key information (critical fault information) through intelligent analysis technology, and finally directly establishes fault record information. This embodiment can save labor costs and improve office efficiency.

[0093] The processor 1110 provided in this application embodiment can implement the various processes of the above-described fault record acquisition method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0094] It should be understood that, in this embodiment, the input unit 1104 may include a graphics processing unit (GPU) 11041 and a microphone 11042. The GPU 11041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1106 may include a display panel 11061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1107 includes at least one of a touch panel 11071 and other input devices 11072. The touch panel 11071 is also called a touch screen. The touch panel 11071 may include a touch detection device and a touch controller. Other input devices 11072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0095] The memory 1109 can be used to store software programs and various data. The memory 1109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1109 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1109 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0096] Processor 1110 may include one or more processing units; optionally, processor 1110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1110.

[0097] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described fault record acquisition method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0098] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0099] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described fault record acquisition method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0100] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0101] This application provides a computer program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the fault record acquisition method embodiment described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here. Specific implementation examples:

[0103] Figure 10 The seventh flowchart of the fault record acquisition method provided in this application embodiment is shown, as follows: Figure 10 As shown, the fault record acquisition method includes:

[0104] Step 702: The user enters the fault reporting system and wakes up the robot;

[0105] Step 704: The user describes the fault information, the robot extracts key information, and converts it into text;

[0106] Based on the prompts, the robot describes the fault information, collects the voice, recognizes the voice information, and converts it into text.

[0107] Step 706: Perform data correction, analysis, and filtering;

[0108] After data processing, extract the necessary key fault information;

[0109] Step 708: Intelligent selection of data entry method;

[0110] (1) No manual verification is required; fault records are created directly. (2) The system first automatically fills in the fault information, and then the information is manually verified and supplemented before the fault record is created.

[0111] Step 710: Establish a fault record.

[0112] In this embodiment, for certain specialized assets and equipment, users may want to receive secondary confirmation or supplementary, more detailed fault information after the system automatically fills in the fault information. To address this, the intelligent selection reporting method in this embodiment implements an intelligent selection algorithm. For example... Figure 11 As shown, the algorithm analyzes multiple dimensions, including asset criticality, asset technical parameters, fault type, and fault symptoms, and intelligently selects the reporting method. The algorithm description is as follows:

[0113] (1) Specify the dimensions of the algorithm analysis, such as: asset criticality, fault category.

[0114] (2) Set algorithm matching rules, such as: assets with criticality level need to be manually confirmed.

[0115] (3) During the algorithm operation, when fault information of an asset with a critical level is identified, a user confirmation action will be triggered.

[0116] This embodiment also involves data filtering and access control. When users manually enter data, the selectable asset information has already been filtered by data permissions. However, when entering data via voice recognition, it is often possible to bypass data permission control and identify asset information outside the authorized scope. This embodiment solves the above problem through skill interfaces. First, a series of skill interfaces are defined, each responsible for a data processing task. Then, related skill interfaces are combined into a skill chain. Only after being filtered through the skill chain can useful data be obtained.

[0117] This embodiment enables automatic fault reporting based on intelligent voice recognition. Utilizing intelligent voice recognition technology, it automatically extracts key fault information and, through data analysis and filtering, achieves automatic fault reporting, solving various problems associated with traditional manual reporting. Specifically:

[0118] (1) This embodiment realizes a new type of fault reporting method, which changes from manual reporting to automatic reporting, reduces the cost of manual reporting and improves work efficiency.

[0119] (2) This embodiment improves the real-time nature of fault reporting. Traditional manual reporting methods cannot establish fault data in a timely manner, and the data establishment process is relatively time-consuming. This solution is beneficial for establishing data with high real-time requirements, such as fault information that needs to be processed in a timely manner.

[0120] (3) This embodiment provides a variety of flexible automatic fault reporting methods. First, fault records are created directly without manual verification. Second, the system automatically fills in the fault information first, and then the fault record is created after the user adds detailed information.

[0121] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0122] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods of the various embodiments of this application.

[0123] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for acquiring fault records, characterized in that, include: Obtain the voice information describing the fault; Convert the voice information into text information; The text information is preprocessed to obtain key fault information; Based on the aforementioned key fault information, the reporting method is obtained; Based on the reported method and the key fault information, fault records are obtained; The method for obtaining the reporting information based on the key fault information specifically includes: Identify the identification markers in the key fault information; When the identification mark is the same as the preset mark, the filling method is set to require secondary confirmation. The secondary confirmation is to first automatically fill in the fault information, then manually verify it, supplement the detailed information, and then create the fault record. If the identification mark differs from the preset mark, the filling method is set to require no secondary confirmation; Specifically, the preprocessing of the text information to obtain key fault information includes: Perform data error correction on the text information; The text information after data correction is filtered to obtain the key fault information; Specifically, the step of filtering the text information after data correction to obtain the key fault information includes: Multiple skill interfaces are defined, and these multiple skill interfaces are combined into a skill link; The text information after data correction is filtered to obtain the key fault information; Each skill interface is responsible for one data processing task.

2. The fault record acquisition method according to claim 1, characterized in that, The acquisition of voice information describing the fault specifically includes: Wake up the voice recognition system; Based on the prompts from the voice recognition system, a fault description is performed; The voice recognition system is controlled to collect the voice information describing the fault.

3. The fault record acquisition method according to claim 1, characterized in that, The identification identifier includes one or a combination of the following: Criticality of assets, technical parameters of assets, types of failures, symptoms of failures, and special equipment.

4. The fault record acquisition method according to claim 1, characterized in that, The process of obtaining fault records based on the reporting method and the key fault information specifically includes: Based on the fact that the reporting method does not require secondary confirmation, a fault record is generated according to the key fault information. Based on the fact that the filling method requires secondary confirmation, the secondary confirmation is triggered, the key fault information is filled in, the information after the secondary confirmation is added, and a fault record is generated.

5. A fault record acquisition device, characterized in that, The fault record acquisition device, using the fault record acquisition method as described in any one of claims 1 to 4, comprises: The first acquisition module is used to acquire voice information describing the fault. The first conversion module is used to convert the voice information into text information; The first preprocessing module is used to preprocess the text information to obtain key fault information; The second acquisition module is used to acquire the reporting method based on the key fault information; The third acquisition module is used to acquire fault records based on the filling method and the key fault information.

6. An electronic device, characterized in that, include: A memory that stores programs or instructions; A processor, configured to implement the steps of the fault record acquisition method as described in any one of claims 1 to 4 when executing the program or instructions.

7. A readable storage medium having a program or instructions stored thereon, characterized in that, When the program or instructions are executed by the processor, they implement the steps of the fault record acquisition method as described in any one of claims 1 to 4.

Images