Vehicle abnormal condition recording method, system and device and electronic equipment

Abstract

The embodiment of the invention relates to a vehicle abnormal condition recording method, system and device and electronic equipment, and the method comprises the steps: obtaining an abnormal description voice file for recording the abnormal condition of a tested vehicle when the tested vehicle runs; identifying the exception description voice file to obtain an exception description text; based on a preset exception description template, extracting at least one exception description item from the exception description text; and generating an exception description form based on the at least one exception description item and the exception description template. According to the embodiment of the invention, when the road test is carried out on the vehicle, the abnormity description form is automatically generated in a voice recognition manner, and manual recording by a tester is not needed, so that the timeliness of recording the test result and the test efficiency are improved, and the risk of omission and errors when the abnormal condition of the vehicle is recorded is reduced.

Description

Technical Field

[0001] The present application relates to the field of intelligent vehicle technology, and in particular to a method, system, device and electronic device for recording abnormal conditions of a vehicle. Background Art

[0002] With the rapid development of intelligent vehicle technology, especially autonomous driving technology, many companies have invested a lot of energy in the research and development and testing of intelligent driving technology. In the process of developing intelligent driving technology, it is usually necessary to test the vehicle in order to find the defects of intelligent driving technology. These defects include abnormalities of various sensor components, errors in intelligent driving algorithms and programs, etc.

[0003] During the testing process, there are a large number of testers and test vehicles, and some problems will be found from time to time. During the driving process of the vehicle, the tester needs to record the abnormal information immediately after discovering the problem, including the time when the abnormality occurred, the section of the road where it occurred, the current road information and road condition information, the specific abnormality description, etc. At present, testers generally record the problems manually, and then collect version information and log files. After the daily road test task is completed, the recorded problems are summarized and sorted out, and then a single defect ticket is submitted for each problem in the bill of lading system. This method is prone to description differences, omissions, untimely recording of problems, and large testing workload, difficulty, and low efficiency. Summary of the invention

[0004] In view of this, in order to solve some or all of the above-mentioned technical problems, the embodiments of the present application provide a vehicle abnormal condition recording method, system, device, electronic device and storage medium.

[0005] In a first aspect, an embodiment of the present application provides a method for recording abnormal conditions of a vehicle, the method comprising: obtaining an abnormal description voice file that records abnormal conditions that occur in a vehicle under test when the vehicle under test is driving; recognizing the abnormal description voice file to obtain an abnormal description text; extracting at least one abnormal description item from the abnormal description text based on a preset abnormal description template; and generating an abnormal description form based on at least one abnormal description item and the abnormal description template.

[0006] In one possible implementation, an exception description form is generated based on at least one exception description item and an exception description template, including: determining the type of abnormal event based on the exception description text; obtaining abnormal function-related information corresponding to the abnormal event type; filling at least one exception description item and abnormal function-related information into corresponding positions in the exception description template to obtain the exception description form.

[0007] In a possible implementation, determining the abnormal event type based on the abnormal description text includes: determining a scene label and / or an event label from the abnormal description text; and determining the abnormal event type according to the scene label and / or the event label.

[0008] In one possible implementation, obtaining abnormal function-related information corresponding to the abnormal event type includes: obtaining function version information corresponding to the abnormal event type based on a preset correspondence table, and obtaining log information corresponding to the abnormal event type; generating abnormal function-related information based on the function version information and the log information.

[0009] In one possible implementation, obtaining functional version information corresponding to the abnormal event type includes: determining a controller version information interface and / or a server version information interface corresponding to the abnormal event type from a correspondence table; and based on the controller version information interface and / or the server version information interface, obtaining the controller version information and / or the server version information as the functional version information corresponding to the abnormal event type.

[0010] In a possible implementation, obtaining log information corresponding to the abnormal event type includes: obtaining a log path corresponding to the abnormal event type from a corresponding relationship table; and obtaining log information corresponding to the abnormal event type based on the log path.

[0011] In a second aspect, an embodiment of the present application provides a vehicle abnormal condition recording system, the system comprising: a vehicle under test, a vehicle testing device, and a server, the vehicle testing device being arranged on the vehicle, and the vehicle testing device and the server being communicatively connected; the vehicle testing device being used to execute the method described in the first aspect above, and sending the generated abnormality description form to the server; the server being used to receive abnormality description information after organizing the abnormality description form, and based on the abnormality description information, generating a defect ticket indicating a functional defect of the vehicle under test.

[0012] In a third aspect, an embodiment of the present application provides a vehicle abnormal condition recording device, which includes: an acquisition module, used to acquire an abnormal description voice file that records abnormal conditions occurring in a vehicle under test when the vehicle under test is driving; a recognition module, used to recognize the abnormal description voice file to obtain an abnormal description text; an extraction module, used to extract at least one abnormal description item from the abnormal description text based on a preset abnormal description template; and a generation module, used to generate an abnormal description form based on at least one abnormal description item and an abnormal description template.

[0013] In a fourth aspect, an embodiment of the present application provides an electronic device, comprising: a memory for storing a computer program; a processor for executing the computer program stored in the memory, and when the computer program is executed, the method of any embodiment of the vehicle abnormal condition recording method of the above-mentioned first aspect of the present application is implemented.

[0014] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, a method as in any embodiment of the method for recording abnormal vehicle conditions of the first aspect described above is implemented.

[0015] In a sixth aspect, an embodiment of the present application provides a computer program, which includes a computer-readable code. When the computer-readable code runs on a device, the processor in the device implements a method as in any embodiment of the vehicle abnormal condition recording method of the first aspect mentioned above.

[0016] The vehicle abnormal condition recording method, system, device and electronic device provided in the embodiments of the present application, by describing the abnormal condition of the tested vehicle by voice when the tested vehicle is driving, recognizing the abnormal description voice file, obtaining the abnormal description text, extracting at least one abnormal description item from the abnormal description text based on a preset abnormal description template, and finally generating an abnormal description form based on at least one abnormal description item and the abnormal description template. The embodiments of the present application realize that when conducting road tests on vehicles, the abnormal description form is automatically generated by voice recognition, without the need for manual recording by the tester, thereby improving the timeliness of the test result recording and the test efficiency, and reducing the risk of omissions and errors when recording abnormal conditions of the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0018] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0019] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0020] Figure 1A flow chart of a method for recording abnormal conditions of a vehicle provided in an embodiment of the present application;

[0021] Figure 2 A flowchart of another method for recording abnormal vehicle conditions provided in an embodiment of the present application;

[0022] Figure 3 A flowchart of another method for recording abnormal vehicle conditions provided in an embodiment of the present application;

[0023] Figure 4 A flowchart of another method for recording abnormal vehicle conditions provided in an embodiment of the present application;

[0024] Figure 5 A schematic diagram of the structure of another vehicle abnormal condition recording system provided in an embodiment of the present application;

[0025] Figure 6 A schematic diagram of the structure of a vehicle abnormal condition recording device provided in an embodiment of the present application;

[0026] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] Various exemplary embodiments of the present application will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. It should be noted that unless otherwise specifically stated, the relative arrangement of the components and steps, the numerical expressions and the numerical values ​​described in these embodiments do not limit the scope of the present application.

[0028] Those skilled in the art will understand that the terms "first" and "second" in the embodiments of the present application are only used to distinguish between different steps, devices, modules and other objects, and do not represent any specific technical meanings, nor do they indicate the logical order between them.

[0029] It should also be understood that in this embodiment, “plurality” may refer to two or more than two, and “at least one” may refer to one, two or more than two.

[0030] It should also be understood that any component, data or structure mentioned in the embodiments of the present application can generally be understood as one or more, unless explicitly limited or otherwise indicated in the context.

[0031] In addition, the term "and / or" in this application is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this application generally indicates that the associated objects before and after are in an "or" relationship.

[0032] It should also be understood that the description of the various embodiments in this application focuses on the differences between the various embodiments, and the same or similar aspects thereof can be referenced to each other, and for the sake of brevity, they will not be described one by one.

[0033] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present application, its application, or uses.

[0034] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the above-mentioned technologies, methods, and equipment should be considered as part of the specification.

[0035] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0036] It should be noted that, in the absence of conflict, the embodiments in this application and the features in the embodiments can be combined with each other. To facilitate the understanding of the embodiments of the present application, the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0037] In order to solve the technical problem in the prior art of inefficient and untimely recording of abnormal information when testing abnormal conditions of a moving vehicle, the present application provides a vehicle abnormal condition recording method, which can automatically record abnormal description forms through voice recognition, thereby improving test efficiency and reducing the risk of errors and omissions in abnormal recording.

[0038] Figure 1 A flowchart of a method for recording abnormal vehicle conditions provided in an embodiment of the present application. The method can be applied to a vehicle and executed by a controller on the vehicle, or by other electronic devices connected to the vehicle, for example, by one or more electronic devices such as a smart phone, a laptop, a portable computer, a server, etc.

[0039] In addition, the execution subject of the present method may be hardware or software. When the execution subject is hardware, the execution subject may be one or more of the electronic devices. For example, a single electronic device may execute the present method, or a plurality of electronic devices may cooperate with each other to execute the present method. When the execution subject is software, the present method may be implemented as a plurality of software or software modules, or as a single software or software module. No specific limitation is made herein.

[0040] like Figure 1 As shown, the method specifically includes:

[0041] Step 101, obtaining an abnormality description voice file that records abnormal conditions that occur in the tested vehicle when the tested vehicle is traveling.

[0042] In this embodiment, the tester can record the abnormal conditions of the tested vehicle in real time by voice when the tested vehicle is driving. When the tester finds that the actual state of the vehicle is inconsistent with the expected state, the recording function can be triggered to describe the abnormal state and obtain an abnormal description voice file. The format of the abnormal description voice file is not limited, for example, it can be wav, mp3, pcm, etc.

[0043] As an example, when the vehicle under test is driving in an automatic driving state and an abnormal situation occurs in the vehicle under test, the tester can trigger the in-car recording function by clicking a button on the human-computer interaction interface (which can be set on the screen of the vehicle or on other devices connected to the vehicle) or a steering wheel button to start recording the in-car voice. The tester needs to describe the details of the problem, including but not limited to the time when the problem occurred, the scene of occurrence (urban area / highway / elevated road / rural road / ramp / tunnel / construction section / winding mountain road / bridge, etc.), the section where the problem occurred (xx Avenue / xx Road / xx Highway x Section, etc.), road condition information (flat road / uphill and downhill / bumpy section / flooded section, etc.), specific abnormal situation, etc. After the description is completed, click the button or key to end the voice recording and generate an abnormal description voice file.

[0044] Step 102: Recognize the abnormality description voice file to obtain the abnormality description text.

[0045] In this embodiment, speech recognition technology can be used to recognize the abnormal description voice file. The device that performs speech recognition can be a local device or a remote device. For example, the abnormal description voice file can be sent to a speech recognition server through an interface provided by a speech recognition engine, and the speech recognition server can use the speech recognition engine to recognize the abnormal description voice file, and the obtained text is the abnormal description text.

[0046] Step 103: extract at least one exception description item from the exception description text based on a preset exception description template.

[0047] In this embodiment, the exception description template is a table of a preset fixed format. The exception description template may include multiple fields, each field corresponding to an exception description item. As an example, at least one exception description item includes the time of occurrence of the exception, the scene of occurrence, a specific description of the abnormal situation, the abnormal classification, the section of the road where the abnormality occurred, etc.

[0048] The electronic device executing the method can extract at least one abnormal description item from the abnormal description text by using text recognition technology. For example, a pre-trained language model can be used, the abnormal description text can be input into the language model, the language model performs semantic analysis on the abnormal description text, and classifies the sentences in the text, thereby extracting at least one abnormal description item.

[0049] Step 104: Generate an exception description form based on at least one exception description item and the exception description template.

[0050] In this embodiment, the above-mentioned at least one abnormal description item can be directly filled into the corresponding position in the abnormal description template to obtain the abnormal description form. Optionally, after the above-mentioned at least one abnormal description item is filled into the abnormal description template, other information can be added to the abnormal description template to obtain the abnormal description form. For example, the file name of the corresponding abnormal description voice file, the software and hardware version information of the abnormal function, and other attachments (such as the log file corresponding to the abnormal function) can be filled into the corresponding position of the abnormal description template to obtain the abnormal description form.

[0051] The vehicle abnormal condition recording method provided in the embodiment of the present application, when the tested vehicle is driving, describes the abnormal condition of the tested vehicle by voice, recognizes the abnormal description voice file, obtains the abnormal description text, extracts at least one abnormal description item from the abnormal description text based on a preset abnormal description template, and finally generates an abnormal description form based on at least one abnormal description item and the abnormal description template. The embodiment of the present application realizes the automatic generation of the abnormal description form by voice recognition when conducting road tests on the vehicle, without the need for manual recording by the tester, thereby improving the timeliness of the test result recording and the test efficiency, and reducing the risk of omissions and errors when recording abnormal conditions of the vehicle.

[0052] In some optional implementations of this embodiment, such as Figure 2 As shown, step 104 includes:

[0053] Step 1041, determining the abnormal event type based on the abnormal description text.

[0054] Specifically, the abnormal description text may include a description of at least one abnormal event type. Optionally, the electronic device may match the abnormal description text according to the key words and phrases corresponding to the pre-set abnormal event type. If a key word and phrase representing a certain abnormal event type is matched, it can be determined that the abnormal description text includes a description of a certain abnormal event type. Optionally, a pre-trained language model may be used to perform semantic analysis and classification on the content in the abnormal description text, so as to obtain the abnormal event type.

[0055] As an example, the above abnormal event type may be unavailable cruise control function, unstable lateral control, etc.

[0056] Step 1042, obtaining abnormal function related information corresponding to the abnormal event type.

[0057] The abnormal function related information refers to various types of information associated with the abnormal function, such as the version information of the software and hardware executing the abnormal function, the log file corresponding to the abnormal function, etc.

[0058] Step 1043, fill in the corresponding position in the exception description template with at least one exception description item and abnormal function related information to obtain an exception description form.

[0059] Among them, the exception description template may include corresponding fields for one less exception description item and information related to the abnormal function. The exception description form can be obtained by filling the one less exception description item and information related to the abnormal function into the corresponding fields.

[0060] This embodiment can enrich the content of the abnormal event form by determining the abnormal event type and obtaining the corresponding abnormal function related information, which helps to analyze the abnormal phenomenon more targetedly according to the abnormal event description form and further improve the measurement and test efficiency.

[0061] In some optional implementations of this embodiment, such as Figure 3 As shown, step 1041 includes:

[0062] Step 10411, determine the scene label and / or event label from the exception description text.

[0063] The scene label and event label are words and phrases representing the scene characteristics of the vehicle driving and the abnormal phenomenon characteristics. The electronic device can use a text recognition method (such as a language model) to determine the words and phrases representing the scene characteristics and the words and phrases representing the abnormal phenomenon characteristics from the abnormal description text.

[0064] Generally, in order to improve the recognition efficiency and accuracy of scene labels and event labels, standard terms for describing abnormal phenomena can be set in advance. The standard terms include scene labels and / or event labels, so that during actual vehicle testing, scene labels and / or event labels can be quickly determined from the abnormal description text.

[0065] As examples, scene labels include the following words and phrases: single-vehicle cruising, following vehicle cruising, curve cruising, tunnel cruising, congestion cruising, large vehicle parallel driving, cutting in, lane line missing / unclear / interlaced, entry and exit ramps, ramp cruising, merging and diverging, navigation lane changing, efficient lane changing, safe lane changing, vehicle temporary stop, accident / construction, pedestrian / cyclist mixed traffic, objects left on the road, function stuck and module crash.

[0066] Event tags include the following words:

[0067] Functionality abnormality (function unavailable, cannot be activated, function abnormally degraded).

[0068] Longitudinal abnormalities: incorrect braking (including point braking, light braking, medium braking, and heavy braking), missed braking, insufficient braking, heavy braking (excessive braking), following a vehicle too close, following a vehicle too far, sudden acceleration, and slow acceleration.

[0069] Lateral abnormalities: steering deviation, dragon drawing, control out, sudden steering wheel movement, steering wheel vibration.

[0070] Strategy abnormality: (xx function) false triggering, (xx function) missed triggering, ramp entry failure, ramp exit failure.

[0071] Abnormal lane change: dangerous lane change, abnormal lane change reversal, lane change too early, lane change too late, invalid lane change.

[0072] Step 10412, determine the abnormal event type based on the scene label and / or event label.

[0073] After obtaining the scene label and the event label, the current abnormal event type can be determined according to the preset correspondence between the scene label, the event label and the abnormal event type.

[0074] This embodiment can quickly determine the type of abnormal event based on the abnormal description text by determining the scene label and / or event label, thereby improving the efficiency of collecting vehicle abnormality information.

[0075] In some optional implementations of this embodiment, such as Figure 4 As shown, step 1042 includes:

[0076] Step 10421, based on the preset correspondence table, obtain the function version information corresponding to the abnormal event type, and obtain the log information corresponding to the abnormal event type.

[0077] The function version information is the version information of the software or hardware that implements a certain function of the vehicle. The log information is the status of the vehicle at each moment that is automatically recorded when the function is implemented. The above correspondence table can be pre-set locally or remotely, and the electronic device executing the method can find the function version information and log information corresponding to the abnormal event type from the correspondence table.

[0078] Step 10422, based on the function version information and log information, generate abnormal function related information.

[0079] Specifically, the function version information and log information can be directly determined as information related to the abnormal function, or the function version information and log information can be processed in a certain way (for example, determining the latest version from the function version information, and extracting information of a specific time period from the log information), and then the processed information can be determined as information related to the abnormal function.

[0080] This embodiment obtains information related to the abnormal function based on the function version information and log information, and realizes the addition of the software and hardware version information and the recorded log information of the abnormal function in the abnormal description form, which is conducive to more targeted recording of the function where the abnormal function occurs, so that technical personnel can improve the function where the abnormal function occurs more efficiently based on the software and hardware version information and log information, thereby improving the efficiency of solving abnormal phenomena.

[0081] In some optional implementations of this embodiment, step 10421 may include:

[0082] First, the controller version information interface and / or the server version information interface corresponding to the abnormal event type is determined from the correspondence table.

[0083] The controller version information interface is used to call the corresponding controller version information, and the server version information interface is used to call the corresponding server version information.

[0084] Then, based on the controller version information interface and / or the server version information interface, the controller version information and / or the server version information is obtained as the function version information corresponding to the abnormal event type.

[0085] The controller version information and the server version information may include software version information and / or hardware version information set on the controller and the server, respectively.

[0086] This embodiment determines the controller version information and / or server version information corresponding to the abnormal event type by using the controller version information interface and / or server version information interface in the correspondence table, and can add the software and hardware version information of the controller and / or server related to the abnormal function in the abnormal description form, thereby helping technical personnel to quickly locate the position of the abnormal software and hardware according to the abnormal description form, and improve the efficiency and accuracy of targeted processing of abnormal phenomena.

[0087] In some optional implementations of this embodiment, step 10421 may include:

[0088] First, obtain the log path corresponding to the abnormal event type from the corresponding relationship table.

[0089] Then, based on the log path, obtain the log information corresponding to the abnormal event type.

[0090] As an example, the corresponding relationship table is shown in Table 1 below, which includes multiple abnormal event types, each abnormal event type corresponds to a controller or server, and a log file, and also includes the corresponding version information interface and log path.

[0091] Table 1

[0092]

[0093]

[0094] When determining the type of an abnormal event, assuming it is exception 1, you need to determine the related controller A, server A, and log file A, and then obtain the version information of controller A and server A through the corresponding interface, and pull log file A through log path A. Log file A contains the required log information.

[0095] This embodiment can realize rapid extraction of log information according to the log path by setting the log path in the correspondence table, thereby improving the efficiency of obtaining the exception description form.

[0096] Figure 5 A schematic diagram of the structure of a vehicle abnormal condition recording system provided in an embodiment of the present application. Specifically comprising: a tested vehicle 501, a vehicle test device 502 and a server 503, wherein the vehicle test device 502 is arranged on the vehicle, and the vehicle test device 502 and the server 503 are connected in communication (connected via a network as shown in the figure). The vehicle test device 502 can be a controller on the vehicle, or other electronic device connected to the vehicle via a vehicle-computer interface, such as a mobile phone, a laptop computer, etc.

[0097] The vehicle testing device 502 is used for the above-mentioned vehicle abnormal condition recording method, and sends the generated abnormality description form to the server 503 .

[0098] The server 503 is used to receive the exception description information after the exception description form is sorted, and generate a defect sheet indicating the functional defect of the tested vehicle 501 based on the exception description information.

[0099] Specifically, after receiving the exception description form, the server 503 can push the exception description form to the terminal used by the tester. The tester can log in to the server 503 to further organize the exception description form, and then obtain a defect sheet.

[0100] As an example, the content of the exception description form can include:

[0101] (1) Are there any duplicate questions? If so, only one valid question will be kept;

[0102] (2) Are there any known problems? If so, delete the problems in the current table;

[0103] (3) the severity of the problem;

[0104] (4) Whether the problem is bound to occur.

[0105] After organizing the contents in the table, you can also add information such as the corresponding responsible person, expected resolution event, etc. to obtain a complete defect ticket.

[0106] Optionally, the vehicle testing device 502 may also send the exception description voice file and the exception description form to the server 503 to facilitate the tester to check and modify the exception description form.

[0107] Typically, the server 503 can save the exception description forms obtained from multiple real vehicle tests, and the tester can log in to the server 503 to sort out the multiple exception description forms, thereby realizing batch defect ticket submission.

[0108] The vehicle abnormal condition recording system provided in the embodiment of the present application, after the above method is executed by the vehicle testing equipment, a defect ticket is generated by the server, and the defect ticket can be generated without too much human participation, thereby realizing fast and efficient processing of recorded vehicle abnormal conditions and improving the efficiency of solving vehicle abnormal problems.

[0109] Figure 6 A schematic diagram of the structure of a vehicle abnormal condition recording device provided in an embodiment of the present application. Specifically comprising:

[0110] The acquisition module 601 is used to acquire an abnormality description voice file that records an abnormal condition that occurs in the tested vehicle when the tested vehicle is driving;

[0111] Recognition module 602, used to recognize the abnormality description voice file to obtain the abnormality description text;

[0112] An extraction module 603 is used to extract at least one abnormal description item from the abnormal description text based on a preset abnormal description template;

[0113] The generating module 604 is used to generate an exception description form based on at least one exception description item and an exception description template.

[0114] In one possible implementation, the generation module includes: a determination unit, used to determine the type of abnormal event based on the abnormal description text; an acquisition unit, used to obtain abnormal function-related information corresponding to the abnormal event type; and a generation unit, used to fill at least one abnormal description item and abnormal function-related information into a corresponding position in the abnormal description template to obtain an abnormal description form.

[0115] In one possible implementation, the determination unit includes: a first determination subunit, used to determine a scene label and / or an event label from the abnormal description text; and a second determination subunit, used to determine the abnormal event type based on the scene label and / or the event label.

[0116] In one possible implementation, the acquisition unit includes: an acquisition subunit, used to acquire function version information corresponding to the abnormal event type based on a preset correspondence table, and to acquire log information corresponding to the abnormal event type; and a generation subunit, used to generate abnormal function related information based on the function version information and log information.

[0117] In one possible embodiment, the acquisition sub-unit is further used to: determine the controller version information interface and / or server version information interface corresponding to the abnormal event type from the correspondence table; based on the controller version information interface and / or server version information interface, acquire the controller version information and / or server version information as the functional version information corresponding to the abnormal event type.

[0118] In a possible implementation, the acquisition subunit is further used to: acquire the log path corresponding to the abnormal event type from the correspondence table; and acquire the log information corresponding to the abnormal event type based on the log path.

[0119] The vehicle abnormal condition recording device provided in this embodiment can be as follows Figure 6 The vehicle abnormal condition recording device shown in can execute all steps of the above vehicle abnormal condition recording methods, thereby achieving the technical effects of the above vehicle abnormal condition recording methods. Please refer to the above related description for details. For the sake of brevity, it will not be repeated here.

[0120] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application, Figure 7 The electronic device 700 shown includes: at least one processor 701, a memory 702, at least one network interface 704 and other user interfaces 703. The various components in the electronic device 700 are coupled together via a bus system 705. It is understood that the bus system 705 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 705 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, the bus system 705 is not described in detail. Figure 7 Various buses are labeled as bus system 705.

[0121] The user interface 703 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touch pad, or a touch screen).

[0122] It can be understood that the memory 702 in the embodiment of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as 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 RAM bus random access memory (DRRAM). The memory 702 described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0123] In some implementations, the memory 702 stores the following elements, executable units or data structures, or a subset thereof, or an extended set thereof: an operating system 7021 and an application 7022 .

[0124] The operating system 7021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application 7022 includes various application programs, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services. The program for implementing the method of the embodiment of the present application can be included in the application 7022.

[0125] In this embodiment, by calling the program or instruction stored in the memory 702, specifically, the program or instruction stored in the application 7022, the processor 701 is used to execute the method steps provided by each method embodiment, for example, including:

[0126] Acquire an abnormal description voice file that records abnormal conditions that occur to the tested vehicle when the tested vehicle is driving; recognize the abnormal description voice file to obtain an abnormal description text; extract at least one abnormal description item from the abnormal description text based on a preset abnormal description template; generate an abnormal description form based on the at least one abnormal description item and the abnormal description template.

[0127] The method disclosed in the above embodiment of the present application can be applied to the processor 701, or implemented by the processor 701. The processor 701 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 701 or the instruction in the form of software. The above processor 701 can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to execute, or the hardware and software units in the decoding processor can be executed. The software unit can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 702, and the processor 701 reads the information in the memory 702 and completes the steps of the above method in combination with its hardware.

[0128] It is understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPDevice, DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the above functions of the present application, or a combination thereof.

[0129] For software implementation, the technology described above in this article can be implemented by a unit that performs the functions described above in this article. The software code can be stored in a memory and executed by a processor. The memory can be implemented in the processor or outside the processor.

[0130] The electronic device provided in this embodiment may be Figure 7 The electronic device shown in can execute all the steps of the above-mentioned vehicle abnormal condition recording methods, thereby achieving the technical effects of the above-mentioned vehicle abnormal condition recording methods. Please refer to the above related description for details. For the sake of brevity, it will not be repeated here.

[0131] The embodiment of the present application also provides a storage medium (computer-readable storage medium). The storage medium here stores one or more programs. The storage medium may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a read-only memory, a flash memory, a hard disk or a solid-state drive; the memory may also include a combination of the above-mentioned types of memory.

[0132] When one or more programs in the storage medium can be executed by one or more processors, the vehicle abnormal condition recording method executed on the electronic device side can be implemented.

[0133] The processor is used to execute the program stored in the memory to implement the following steps of the vehicle abnormal condition recording method executed on the electronic device side:

[0134] Acquire an abnormal description voice file that records abnormal conditions that occur to the tested vehicle when the tested vehicle is driving; recognize the abnormal description voice file to obtain an abnormal description text; extract at least one abnormal description item from the abnormal description text based on a preset abnormal description template; generate an abnormal description form based on the at least one abnormal description item and the abnormal description template.

[0135] The professionals should also be further aware that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0136] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0137] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0138] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.

Claims

1. A method for recording abnormal conditions of a vehicle, characterized in that: The method comprises: Acquire an abnormality description voice file that records an abnormal condition that occurs when the tested vehicle is driving; Recognizing the abnormality description voice file to obtain the abnormality description text; Based on a preset exception description template, extract at least one exception description item from the exception description text; An exception description form is generated based on the at least one exception description item and the exception description template.

2. The method according to claim 1, characterized in that The generating an exception description form based on the at least one exception description item and the exception description template includes: Determine the type of abnormal event based on the abnormal description text; Obtaining abnormal function related information corresponding to the abnormal event type; Fill the at least one abnormal description item and the abnormal function related information into the corresponding position in the abnormal description template to obtain the abnormal description form.

3. The method according to claim 2, characterized in that The determining the type of abnormal event based on the abnormal description text includes: Determine a scene label and / or an event label from the abnormal description text; The abnormal event type is determined according to the scene label and / or the event label.

4. The method according to claim 2, characterized in that: The obtaining of abnormal function related information corresponding to the abnormal event type includes: Based on a preset correspondence table, obtain function version information corresponding to the abnormal event type, and obtain log information corresponding to the abnormal event type; Based on the function version information and the log information, the abnormal function related information is generated.

5. The method according to claim 4, characterized in that The obtaining of function version information corresponding to the abnormal event type includes: Determine, from the correspondence table, a controller version information interface and / or a server version information interface corresponding to the abnormal event type; Based on the controller version information interface and / or the server version information interface, the controller version information and / or the server version information is acquired as the function version information corresponding to the abnormal event type.

6. The method according to claim 4, characterized in that The obtaining log information corresponding to the abnormal event type includes: Obtaining the log path corresponding to the abnormal event type from the corresponding relationship table; Based on the log path, log information corresponding to the abnormal event type is obtained.

7. A vehicle abnormal condition recording system, characterized in that: The system comprises: a tested vehicle, a vehicle testing device and a server, wherein the vehicle testing device is arranged on the vehicle, and the vehicle testing device and the server are in communication connection; The vehicle testing device is used to execute the method according to any one of claims 1 to 6, and send the generated exception description form to the server; The server is used to receive the exception description information after the exception description form is sorted, and generate a defect sheet indicating the functional defects of the tested vehicle based on the exception description information.

8. A vehicle abnormal condition recording device, characterized in that: The device comprises: An acquisition module, used to acquire an abnormality description voice file that records an abnormal condition that occurs in the tested vehicle when the tested vehicle is traveling; A recognition module, used for recognizing the abnormality description voice file to obtain the abnormality description text; An extraction module, configured to extract at least one abnormal description item from the abnormal description text based on a preset abnormal description template; A generating module is used to generate an exception description form based on the at least one exception description item and the exception description template.

9. An electronic device, characterized in that: include: Memory for storing computer programs; The processor is used to execute the computer program stored in the memory, and when the computer program is executed, the vehicle abnormal condition recording method described in any one of claims 1 to 6 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the vehicle abnormal condition recording method described in any one of claims 1 to 6 is implemented.

Images