Test data processing method, device, electronic equipment and medium

Abstract

The present application relates to the field of automotive electrical test verification technology, and in particular to a test data processing method, device, electronic device and medium, the method comprising: determining a current test scenario that meets preset conditions from a plurality of preset test scenarios, and collecting test data of a vehicle to be tested in the current test scenario; judging whether the test data meets the trigger conditions corresponding to the current test scenario; if the test data meets the trigger conditions corresponding to the current test scenario, the test data of the vehicle to be tested is saved to a first storage location and a second storage location, otherwise the test data of the vehicle to be tested is only saved to the second storage location, wherein the priority of the first storage location is higher than that of the second storage location. The test data processing method of the embodiment of the present application locates the problem conditions that occur during the actual vehicle test through the change rules of the data in the data acquisition software, quickly extracts the problem data from a large number of data files and analyzes them, thereby efficiently completing the system function test.

Description

Technical Field

[0001] The present application relates to the technical field of automobile electrical appliance testing and verification, and in particular to a test data processing method, device, electronic equipment and medium. Background Art

[0002] With the rapid development of artificial intelligence and 5G communication technology, intelligent driving of vehicles has become a future trend to improve driving safety and travel efficiency. In intelligent driving, the control of the system is related to the life safety of the user, namely the driver and passengers. Therefore, a large number of real vehicle tests are required in the system function verification stage to ensure the stability and safety of the function.

[0003] In related technologies, vehicle intelligent driving assistance systems have been widely used. Most of these systems are based on cameras, radars and other sensors installed on the vehicle body to collect external environmental parameters and transmit them to the controller. The controller then controls the vehicle based on perception, thereby achieving the function of assisted driving.

[0004] However, due to the complexity of the system, a huge amount of data is often generated, and it takes a lot of time and manpower to process this data, thus reducing the efficiency of the test, which needs to be solved urgently. Summary of the invention

[0005] The present application provides a test data processing method, device, electronic device and medium to solve the problems of long time consumption, high cost and low efficiency when extracting data information of vehicle problem conditions through a driving assistance system.

[0006] The first aspect of the present application provides a test data processing method, comprising the following steps: determining a current test scenario that meets preset conditions from multiple preset test scenarios, and collecting test data of a vehicle to be tested in the current test scenario; judging whether the test data meets the trigger conditions corresponding to the current test scenario; and if the test data meets the trigger conditions corresponding to the current test scenario, saving the test data of the vehicle to be tested to a first storage location and a second storage location, otherwise saving the test data of the vehicle to be tested only to the second storage location, wherein the first storage location has a higher priority than the second storage location.

[0007] According to the above technical means, through the parameter change rules of multiple test scenarios, the problem scenarios in the actual vehicle testing process can be located, so as to complete the test analysis tasks quickly and efficiently.

[0008] Further, in one embodiment of the present application, the plurality of preset test scenarios include at least two of a driver takeover scenario, a missed braking scenario, and an erroneous braking scenario.

[0009] According to the above technical means, data analysis is performed through different test scenarios to improve the accuracy of test data.

[0010] Furthermore, in one embodiment of the present application, before collecting the test data of the vehicle to be tested in the current test scenario, it also includes: if the current test scenario is a driver takeover scenario, determining that the trigger condition corresponding to the current test scenario is that the opening of the brake pedal is greater than a preset opening or the torque of turning the steering wheel is greater than a preset torque; if the current test scenario is a missed braking scenario, then the trigger condition corresponding to the current test scenario is that when the brake pedal is triggered, the deceleration of the vehicle to be tested reaches a first preset deceleration within a first preset time; if the current test scenario is a misbraking scenario, then the trigger condition corresponding to the current test scenario is that when the brake pedal is not triggered, the deceleration of the vehicle to be tested reaches a second preset deceleration within a second preset time.

[0011] According to the above technical means, setting corresponding trigger conditions according to different test scenarios can enable the intelligent driving assistance system to quickly locate the problem scenario conditions, thereby improving the efficiency of test analysis.

[0012] Further, in one embodiment of the present application, the judging whether the test data satisfies the trigger condition corresponding to the current test scenario includes: when the current test scenario is the driver takeover scenario, if the current opening of the brake pedal is greater than the preset opening or the current torque of turning the steering wheel is greater than the preset torque, then the judging that the test data satisfies the trigger condition corresponding to the driver takeover scenario; when the current test scenario is the missed braking scenario, if the brake pedal is triggered and the deceleration of the vehicle to be tested reaches the first preset deceleration within the first preset time, then the judging that the test data satisfies the trigger condition corresponding to the missed braking scenario; when the current test scenario is the misbraking scenario, if the brake pedal is not triggered and the deceleration of the vehicle to be tested reaches the second preset deceleration within the second preset time, then the judging that the test data satisfies the trigger condition corresponding to the misbraking scenario.

[0013] According to the above technical means, by judging whether the test data meets the trigger conditions corresponding to the current test scenario, a specific analysis of the special scenario is carried out, so as to carry out targeted problem scenario working conditions.

[0014] The second aspect of the present application provides a test data processing device, including: an acquisition module, used to determine a current test scenario that meets preset conditions from multiple preset test scenarios, and collect test data of a vehicle to be tested in the current test scenario; a judgment module, used to judge whether the test data meets the trigger condition corresponding to the current test scenario; and a storage module, used to save the test data of the vehicle to be tested to a first storage location and a second storage location if the test data meets the trigger condition corresponding to the current test scenario, otherwise save the test data of the vehicle to be tested only to the second storage location, wherein the priority of the first storage location is higher than that of the second storage location.

[0015] Further, in one embodiment of the present application, the plurality of preset test scenarios include at least two of a driver takeover scenario, a missed braking scenario, and an erroneous braking scenario.

[0016] Furthermore, in one embodiment of the present application, before collecting the test data of the vehicle to be tested in the current test scenario, the collection module also includes: a takeover unit, which is used to determine, if the current test scenario is a driver takeover scenario, that the trigger condition corresponding to the current test scenario is that the opening of the brake pedal is greater than a preset opening or the torque of turning the steering wheel is greater than a preset torque; a leakage braking unit, which is used to determine, if the current test scenario is a leakage braking scenario, that the trigger condition corresponding to the current test scenario is that when the brake pedal is triggered, the deceleration of the vehicle to be tested reaches a first preset deceleration within a first preset time; and a misbraking unit, which is used to determine, if the current test scenario is a misbraking scenario, that the trigger condition corresponding to the current test scenario is that when the brake pedal is not triggered, the deceleration of the vehicle to be tested reaches a second preset deceleration within a second preset time.

[0017] Further, in one embodiment of the present application, the judgment module includes: a first judgment unit, used to determine that the test data meets the trigger condition corresponding to the driver takeover scenario if the current opening of the brake pedal is greater than the preset opening or the current torque of turning the steering wheel is greater than the preset torque when the current test scenario is the driver takeover scenario; a second judgment unit, used to determine that the test data meets the trigger condition corresponding to the missed braking scenario if the brake pedal is triggered and the deceleration of the vehicle to be tested reaches the first preset deceleration within the first preset time when the current test scenario is the missed braking scenario; a third judgment unit, used to determine that the test data meets the trigger condition corresponding to the missed braking scenario if the brake pedal is not triggered and the deceleration of the vehicle to be tested reaches the second preset deceleration within the second preset time when the current test scenario is the misbraking scenario.

[0018] A third aspect of the present application provides a vehicle, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the test data processing method as described in the above embodiment.

[0019] The fourth aspect of the present application provides a computer-readable storage medium on which a computer program is stored. The program is executed by a processor to implement the test data processing method as described in the above embodiment.

[0020] The embodiment of the present application can determine the current test scene that meets the preset conditions from multiple preset test scenes, and collect the test data of the vehicle to be tested, and then determine whether the trigger condition corresponding to the current test scene is met. If the test data meets the trigger condition, the test data of the vehicle to be tested is saved to the first storage location and the second storage location, otherwise it is only saved to the second storage location. In this way, the problems of long time consumption, high cost, and low efficiency when extracting data information of vehicle problem conditions through the driving assistance system are solved.

[0021] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0023] Figure 1 A flowchart of a test data processing method provided according to an embodiment of the present application;

[0024] Figure 2 A specific flow chart of an efficient test data processing method of data acquisition software provided according to an embodiment of the present application;

[0025] Figure 3 is an exemplary diagram of a test data processing device according to an embodiment of the present application;

[0026] Figure 4 It is a schematic diagram of the structure of a vehicle according to an embodiment of the present application.

[0027] Figure numerals: 10 - test data processing device; 100 - acquisition module, 200 - judgment module, 300 - storage module. DETAILED DESCRIPTION

[0028] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0029] The test data processing method, device, electronic device and medium of the embodiment of the present application are described below with reference to the accompanying drawings. In view of the problems mentioned in the above background technology that it takes a long time, is costly and is inefficient to extract data information of vehicle problem conditions through a driving assistance system, the present application provides a test data processing method, in which a current test scene that meets preset conditions is determined from multiple preset test scenes, and test data of the vehicle to be tested is collected, and then it is determined whether the trigger condition corresponding to the current test scene is met. If the test data meets the trigger condition, the test data of the vehicle to be tested is saved to the first storage location and the second storage location, otherwise it is only saved to the second storage location, and the problem conditions that occur during the actual vehicle test are located by the change law of the data in the data acquisition software, and the problem data is quickly extracted from a large number of data files and analyzed, so as to efficiently complete the system function test. Thus, the problems of long time, high cost and low efficiency when extracting data information of vehicle problem conditions through a driving assistance system are solved.

[0030] Specifically, Figure 1 A flowchart of a test data processing method provided in an embodiment of the present application.

[0031] like Figure 1 As shown, the test data processing method includes the following steps:

[0032] In step S101, a current test scene that meets preset conditions is determined from a plurality of preset test scenes, and test data of the vehicle to be tested in the current test scene is collected.

[0033] Among them, multiple preset test scenarios may include at least two of the driver takeover scenario, missed braking scenario and misbraking scenario, and the preset conditions may be conditions pre-set by the user or conditions obtained through multiple simulations by a computer, which are not specifically limited here.

[0034] Specifically, in the efficient test data processing method for vehicle data acquisition software in the embodiment of the present application, the corresponding relationship between the data to be collected in the current test scenario and the target scenario should be determined first. When certain parameters change in a specific regularity, the scenario is the required problem condition target scenario, and the test data of the vehicle to be tested in the current test scenario is collected. Among them, the test data of the vehicle to be tested can be collected by the data acquisition software through CANape18, and the test data change regularity can be recorded by the trigger software to reduce the time required to find the problem data when processing the data later.

[0035] Furthermore, in one embodiment of the present application, before collecting test data of the vehicle to be tested in the current test scenario, it also includes: if the current test scenario is a driver takeover scenario, determining that the trigger condition corresponding to the current test scenario is that the opening of the brake pedal is greater than a preset opening or the torque of turning the steering wheel is greater than a preset torque; if the current test scenario is a missed braking scenario, then the trigger condition corresponding to the current test scenario is that when the brake pedal is triggered, the deceleration of the vehicle to be tested reaches a first preset deceleration within a first preset time; if the current test scenario is an incorrect braking scenario, then the trigger condition corresponding to the current test scenario is that when the brake pedal is not triggered, the deceleration of the vehicle to be tested reaches a second preset deceleration within a second preset time.

[0036] Among them, the preset opening, preset torque, first preset time, first preset deceleration, second preset time and second preset time can all be set by the driver himself, and can also be set through the results of multiple computer simulations, and are not specifically limited here.

[0037] Specifically, before collecting the test data of the vehicle to be tested in the current test scenario, the embodiment of the present application also needs to determine the trigger conditions required for each test scenario. The following will take the driver takeover scenario, missed braking scenario and misbraking scenario as examples.

[0038] Optionally, if the current test scenario is a driver takeover scenario, the system function of the embodiment of the present application must first be in an activated state, and secondly, the parameter change is further defined according to the activated mode ACC (Adaptive Cruise Control) or IACC (Integrated Adapted Cruise Control), such as the parameter of the system function activation will change from 1 to 0, and the trigger condition corresponding to the current test scenario is determined through the parameter change to be the opening of the brake pedal is greater than the preset opening or the torque of turning the steering wheel is greater than the preset torque. That is to say, the system parameter change is defined as the opening of the driver's brake pedal is greater than the preset opening or the torque of turning the steering wheel in ACC or IACC mode is greater than the preset torque. This is used as the trigger condition for the driver takeover scenario. Therefore, the current test scenario can be regarded as a driver takeover scenario.

[0039] Optionally, if the current test scenario is a missed brake scenario, in the embodiment of the present application, under the premise that the system function is activated, since the test personnel will take over the test later than actually is, if the trigger condition corresponding to the current test scenario is that the brake pedal is triggered, it can be directly determined that the deceleration of the vehicle to be tested reaches a first preset deceleration within the first preset time when the driver steps on the brake pedal. For example, the situation where the deceleration reaches -1.5m / s^2 or -2m / s^2 in a short time is a missed brake scenario.

[0040] Optionally, if the current test scenario is a misbraking scenario, under the premise that the system function is activated, in the embodiment of the present application, if the trigger condition corresponding to the current test scenario is that the brake pedal is not triggered, that is, the opposite of the trigger condition of the above-mentioned missed braking scenario, then the deceleration of the vehicle to be tested reaches a second preset deceleration within the second preset time. If the actual response deceleration reaches -1.5m / s^2, it can be defined as a misbraking scenario.

[0041] In step S102, it is determined whether the test data meets the trigger condition corresponding to the current test scenario.

[0042] Further, in one embodiment of the present application, whether the test data satisfies the trigger condition corresponding to the current test scenario is determined, including: when the current test scenario is a driver takeover scenario, if the current opening of the brake pedal is greater than a preset opening or the current torque of turning the steering wheel is greater than a preset torque, then the test data is determined to meet the trigger condition corresponding to the driver takeover scenario; when the current test scenario is a missed braking scenario, if the brake pedal is triggered and the deceleration of the vehicle to be tested reaches a first preset deceleration within a first preset time, then the test data is determined to meet the trigger condition corresponding to the missed braking scenario; when the current test scenario is a misbraking scenario, if the brake pedal is not triggered and the deceleration of the vehicle to be tested reaches a second preset deceleration within a second preset time, then the test data is determined to meet the trigger condition corresponding to the misbraking scenario.

[0043] Specifically, Figure 2 As shown, after the embodiment of the present application collects the test data of the vehicle to be tested in the current test scenario, it is necessary to judge whether the test data of the vehicle to be tested meets the trigger conditions corresponding to the current test scenario. Similarly, the driver takeover scenario, missed braking scenario and misbraking scenario are taken as examples below.

[0044] Optionally, if the current test scenario is a driver takeover scenario, if the current opening of the brake pedal is greater than the preset opening or the current torque of turning the steering wheel is greater than the preset torque, then the test data is determined to meet the trigger conditions corresponding to the driver takeover scenario. For example, the current brake pedal opening is 5 and the preset brake pedal opening is 3. At this time, the current brake pedal opening is greater than the preset opening. Therefore, the test data meets the trigger conditions corresponding to the driver takeover scenario.

[0045] Optionally, if the current test scenario is a missed braking scenario, if the brake pedal is triggered and the deceleration of the vehicle to be tested reaches a first preset deceleration within a first preset time, it is determined that the test data meets the trigger conditions corresponding to the missed braking scenario. For example, in the missed braking scenario, if the system has decelerated, it can be defined as an insufficient braking scenario; if there is a target vehicle No. 1, and the distance between this vehicle and target vehicle No. 1 is gradually shortened, and the expected collision event TTC (Time-To-Collision) is less than a certain value, it can be defined as a missed braking scenario for target vehicle No. 1; if there are target vehicles No. 3, No. 4 or other adjacent lanes, and the lateral distance to this vehicle is gradually shortened, and the information of target vehicle No. 1 jumps to the original information of target vehicle No. 3, No. 4 or other adjacent lanes, it can be defined as a missed braking scenario when the adjacent lane vehicle cuts in, that is, it is determined that the test data meets the trigger conditions corresponding to the missed braking scenario.

[0046] It should also be noted that the definitions of event test scenarios related to vehicle target information must be based on the condition that the sensor outputs correct target information. Therefore, when recognition errors caused by unstable sensor output are unavoidable, there are still options for optimization.

[0047] Optionally, if the current test scenario is a mis-braking scenario, under the premise of activating the system function, if the brake pedal is not triggered, and the deceleration of the vehicle to be tested reaches the second preset deceleration within the second preset time, then the test data is determined to meet the trigger condition corresponding to the mis-braking scenario. For example, based on the above example, if there is no information about target vehicle No. 1 and target vehicles No. 3, No. 4 or other adjacent lanes whose lateral distances are gradually shortened, when the system issues a braking request and the actual response deceleration reaches -1.5m / s^2, then the test data is determined to meet the trigger condition corresponding to the mis-braking scenario.

[0048] It should be noted that after the system has experienced false braking for a long period of time, it will often follow the driver's key press to exit the takeover operation, and can also be used as an accessory item for further screening.

[0049] In step S103, if the test data meets the trigger condition corresponding to the current test scenario, the test data of the vehicle to be tested is saved to the first storage location and the second storage location, otherwise the test data of the vehicle to be tested is only saved to the second storage location, wherein the first storage location has a higher priority than the second storage location.

[0050] Specifically, Figure 2 As shown, through the discussion of the above embodiments, when the data acquisition software determines the current test scenario and collects the test data of the vehicle to be tested under the current test scenario, if the test data meets the trigger condition corresponding to the current test scenario, the test data of the vehicle to be tested is recorded and saved to the first storage location and the second storage location; if the test data does not meet the trigger condition corresponding to the current test scenario, the test data of the vehicle to be tested is recorded separately and saved only to the second storage location, wherein the priority of the first storage location is higher than that of the second storage location.

[0051] Specifically, the embodiment of the present application first collects the test data of the current test scenario through the data acquisition software. If the test data meets the trigger condition corresponding to the current test scenario, the test data collected by multiple test scenarios are recorded simultaneously through the trigger software during the data testing process, and are automatically classified and saved; if the test data does not meet the trigger condition corresponding to the current test scenario, the test data collected by multiple test scenarios are recorded separately through the trigger software during the data testing process, and are automatically classified and saved.

[0052] According to the test data processing method proposed in the embodiment of the present application, the current test scene that meets the preset conditions is determined from multiple preset test scenes, and the test data of the vehicle to be tested is collected to determine whether the trigger condition corresponding to the current test scene is met. If the test data meets the trigger condition, the test data of the vehicle to be tested is saved to the first storage location and the second storage location, otherwise it is only saved to the second storage location. The problem conditions that occur during the actual vehicle test are located through the change rules of the data in the data acquisition software, and the problem data is quickly extracted from a large number of data files and analyzed, so as to efficiently complete the system function test. In this way, the problems of long time consumption, high cost, and low efficiency when extracting data information of vehicle problem conditions through the driving assistance system are solved.

[0053] Next, the test data processing device proposed according to the embodiment of the present application is described with reference to the accompanying drawings.

[0054] Figure 3 It is a block diagram of a test data processing device according to an embodiment of the present application.

[0055] like Figure 3 As shown, the test data processing device 10 includes: a collection module 100 , a judgment module 200 and a storage module 300 .

[0056] The acquisition module 100 is used to determine a current test scenario that meets preset conditions from a plurality of preset test scenarios, and to acquire test data of the vehicle to be tested in the current test scenario;

[0057] A determination module 200 is used to determine whether the test data meets the trigger condition corresponding to the current test scenario; and

[0058] The storage module 300 is used to save the test data of the vehicle to be tested to the first storage location and the second storage location if the test data meets the trigger condition corresponding to the current test scenario, otherwise the test data of the vehicle to be tested is only saved to the second storage location, wherein the priority of the first storage location is higher than that of the second storage location.

[0059] Further, in one embodiment of the present application, the plurality of preset test scenarios include at least two of a driver takeover scenario, a missed braking scenario, and an erroneous braking scenario.

[0060] Furthermore, in one embodiment of the present application, before collecting the test data of the vehicle to be tested in the current test scenario, the collection module 100 further includes: a takeover unit, a missed braking unit and a misbraking unit.

[0061] Wherein, the takeover unit is used to determine, if the current test scenario is a driver takeover scenario, that the trigger condition corresponding to the current test scenario is that the opening of the brake pedal is greater than a preset opening or the torque of turning the steering wheel is greater than a preset torque;

[0062] A leakage brake unit, used for, if the current test scenario is a leakage brake scenario, the trigger condition corresponding to the current test scenario is that when the brake pedal is triggered, the deceleration of the vehicle to be tested reaches a first preset deceleration within a first preset time;

[0063] The misbraking unit is used to, if the current test scenario is a misbraking scenario, then the trigger condition corresponding to the current test scenario is that when the brake pedal is not triggered, the deceleration of the vehicle to be tested reaches a second preset deceleration within a second preset time.

[0064] Further, in an embodiment of the present application, the judgment module 200 includes: a first judgment unit, a second judgment unit and a third judgment unit.

[0065] The first judgment unit is used to determine that the test data meets the trigger condition corresponding to the driver takeover scenario if the current opening of the brake pedal is greater than a preset opening or the current torque of turning the steering wheel is greater than a preset torque when the current test scenario is a driver takeover scenario;

[0066] A second judgment unit is used to determine that the test data meets the trigger condition corresponding to the missed brake scenario if the brake pedal is triggered and the deceleration of the vehicle to be tested reaches a first preset deceleration within a first preset time when the current test scenario is a missed brake scenario;

[0067] The third judgment unit is used to determine that the test data meets the trigger condition corresponding to the misbraking scenario when the current test scenario is a misbraking scenario, if the brake pedal is not triggered and the deceleration of the vehicle to be tested reaches a second preset deceleration within a second preset time.

[0068] According to the test data processing device proposed in the embodiment of the present application, the current test scene that meets the preset conditions is determined from multiple preset test scenes, and the test data of the vehicle to be tested is collected, and then it is determined whether the trigger condition corresponding to the current test scene is met. If the test data meets the trigger condition, the test data of the vehicle to be tested is saved to the first storage location and the second storage location, otherwise it is only saved to the second storage location. The problem conditions that occur during the actual vehicle test are located through the change rules of the data in the data acquisition software, and the problem data is quickly extracted and analyzed from a large number of data files, so as to efficiently complete the system function test. In this way, the problems of long time consumption, high cost, and low efficiency when extracting data information of vehicle problem conditions through the driving assistance system are solved.

[0069] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. The electronic device may include:

[0070] Memory 401 , processor 402 , and a computer program stored in the memory 401 and executable on the processor 402 .

[0071] When the processor 402 executes the program, the test data processing method provided in the above embodiment is implemented.

[0072] Furthermore, the electronic device further comprises:

[0073] The communication interface 403 is used for communication between the memory 401 and the processor 402 .

[0074] The memory 401 is used to store computer programs that can be executed on the processor 402 .

[0075] The memory 401 may include a high-speed RAM (Random Access Memory) memory, and may also include a non-volatile memory, such as at least one disk memory.

[0076] If the memory 401, the processor 402 and the communication interface 403 are implemented independently, the communication interface 403, the memory 401 and the processor 402 can be connected to each other through a bus and communicate with each other. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0077] Optionally, in a specific implementation, if the memory 401, the processor 402 and the communication interface 403 are integrated on a chip, the memory 401, the processor 402 and the communication interface 403 can communicate with each other through an internal interface.

[0078] The processor 402 may be a CPU (Central Processing Unit), or an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application.

[0079] An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the test data processing method as described above is implemented.

[0080] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms are not necessarily directed to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or N embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0081] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0082] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0083] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiment, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array, a field programmable gate array, etc.

[0084] A person skilled in the art may understand that all or part of the steps in the above-mentioned embodiment method may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0085] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A test data processing method, characterized in that: The following steps are involved: Determining a current test scenario that meets preset conditions from a plurality of preset test scenarios, and collecting test data of the vehicle to be tested in the current test scenario; Determine whether the test data meets the trigger condition corresponding to the current test scenario; as well as If the test data meets the trigger condition corresponding to the current test scenario, the test data of the vehicle to be tested is saved to a first storage location and a second storage location; otherwise, the test data of the vehicle to be tested is only saved to the second storage location, wherein the first storage location has a higher priority than the second storage location; The determining whether the test data satisfies a trigger condition corresponding to the current test scenario includes: When the current test scenario is a driver takeover scenario, if the current opening of the brake pedal is greater than a preset opening or the current torque of turning the steering wheel is greater than a preset torque, it is determined that the test data meets the trigger condition corresponding to the driver takeover scenario; When the current test scenario is a leaky brake scenario, if the brake pedal is triggered and the deceleration of the vehicle to be tested reaches a first preset deceleration within a first preset time, it is determined that the test data meets the trigger condition corresponding to the leaky brake scenario; When the current test scenario is a misbraking scenario, if the brake pedal is not triggered and the deceleration of the vehicle to be tested reaches a second preset deceleration within a second preset time, it is determined that the test data meets the trigger condition corresponding to the misbraking scenario.

2. The method according to claim 1, characterized in that: The plurality of preset test scenarios include at least two of a driver takeover scenario, a missed braking scenario, and a misbraking scenario.

3. The method according to claim 2, characterized in that Before collecting the test data of the vehicle to be tested in the current test scenario, the method further includes: If the current test scenario is a driver takeover scenario, determining that the trigger condition corresponding to the current test scenario is that the opening of the brake pedal is greater than a preset opening or the torque of turning the steering wheel is greater than a preset torque; If the current test scenario is a leaky brake scenario, the trigger condition corresponding to the current test scenario is that when the brake pedal is triggered, the deceleration of the vehicle to be tested reaches a first preset deceleration within a first preset time; If the current test scenario is a misbraking scenario, the trigger condition corresponding to the current test scenario is that when the brake pedal is not triggered, the deceleration of the vehicle to be tested reaches a second preset deceleration within a second preset time.

4. A test data processing device, characterized in that: include: A collection module, used to determine a current test scene that meets preset conditions from a plurality of preset test scenes, and collect test data of the vehicle to be tested in the current test scene; A judgment module, used to judge whether the test data meets the trigger condition corresponding to the current test scenario; as well as A storage module, configured to save the test data of the vehicle to be tested to a first storage location and a second storage location if the test data meets a trigger condition corresponding to the current test scenario, and to save the test data of the vehicle to be tested only to the second storage location otherwise, wherein the first storage location has a higher priority than the second storage location; The judging module comprises: A first judgment unit is used to determine that the test data meets the trigger condition corresponding to the driver takeover scenario if the current opening of the brake pedal is greater than a preset opening or the current torque of turning the steering wheel is greater than a preset torque when the current test scenario is a driver takeover scenario; A second judgment unit is used to determine that the test data meets the trigger condition corresponding to the missed brake scenario if the brake pedal is triggered and the deceleration of the vehicle to be tested reaches a first preset deceleration within a first preset time when the current test scenario is a missed brake scenario; The third judgment unit is used to determine that the test data meets the trigger condition corresponding to the misbraking scenario when the current test scenario is a misbraking scenario if the brake pedal is not triggered and the deceleration of the vehicle to be tested reaches a second preset deceleration within a second preset time.

5. The device according to claim 4, characterized in that The plurality of preset test scenarios include at least two of a driver takeover scenario, a missed braking scenario, and a misbraking scenario.

6. The device according to claim 5, characterized in that Before collecting the test data of the vehicle to be tested in the current test scenario, the collection module further includes: a takeover unit, configured to determine, if the current test scenario is a driver takeover scenario, that a trigger condition corresponding to the current test scenario is that an opening of a brake pedal is greater than a preset opening or a torque of turning a steering wheel is greater than a preset torque; A leakage brake unit, used for, if the current test scenario is a leakage brake scenario, the trigger condition corresponding to the current test scenario is that when the brake pedal is triggered, the deceleration of the vehicle to be tested reaches a first preset deceleration within a first preset time; The misbraking unit is used for, if the current test scenario is a misbraking scenario, the trigger condition corresponding to the current test scenario is that when the brake pedal is not triggered, the deceleration of the vehicle to be tested reaches a second preset deceleration within a second preset time.

7. An electronic device, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the test data processing method according to any one of claims 1 to 3.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: The program is executed by a processor to implement the test data processing method according to any one of claims 1 to 3.

Images