Evaluation method and device of vehicle-mounted control unit and vehicle

Abstract

The invention discloses an evaluation method and device for a vehicle-mounted control unit and a vehicle, and relates to the technical field of automatic testing technologies and intelligent vehicles, and the evaluation method for the vehicle-mounted control unit comprises the steps: obtaining vehicle use scene data corresponding to the vehicle-mounted control unit, the vehicle using scene data is used for representing scene working condition characteristics of the vehicle-mounted control unit in a whole vehicle using process, and the whole vehicle using process comprises a travel preparation stage, a travel advancing stage and a travel ending stage; driving a vehicle-mounted control unit to execute control operation by using the vehicle use scene data to obtain test data; and performing function evaluation on the test data to generate an evaluation result which is used for representing whether the function performance of the vehicle-mounted control unit meets the release standard or not. According to the method and the device, the technical problem of poor accuracy of an evaluation result caused by a method for evaluating the vehicle-mounted control unit based on a modular function case in related technologies is solved.

Description

Technical Field

[0001] The present application relates to the fields of automated testing technology and intelligent vehicle technology, and more specifically, to an evaluation method and device for an on-board control unit and a vehicle. Background Art

[0002] With the continuous development of intelligent connected vehicle technology, the coupling and complexity between multiple onboard control units (ECUs) installed in vehicles are increasing. Consequently, multiple evaluation and testing of ECUs are required during vehicle development. Accurately evaluating ECUs has become a pressing challenge in related technical fields.

[0003] In the related art, the vehicle control unit is usually tested based on modular functional design test cases to verify the availability of multiple functions of the vehicle control unit one by one. However, this method has strong limitations, resulting in poor accuracy of the evaluation results.

[0004] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0005] The embodiments of the present application provide a method, device and vehicle for evaluating an on-board control unit, so as to at least solve the technical problem in the related art of evaluating an on-board control unit based on modular functional use cases, which leads to poor accuracy of the evaluation results.

[0006] According to one aspect of an embodiment of the present application, a method for evaluating an on-board control unit is provided, comprising: obtaining vehicle usage scenario data corresponding to the on-board control unit, wherein the vehicle usage scenario data is used to characterize scenario operating condition characteristics of the on-board control unit in the entire vehicle usage process, the entire vehicle usage process including a trip preparation phase, a trip travel phase, and a trip end phase; utilizing the vehicle usage scenario data to drive the on-board control unit to perform control operations to obtain test data; performing a functional evaluation on the test data to generate an evaluation result, wherein the evaluation result is used to characterize whether the functional performance of the on-board control unit meets the release standards.

[0007] Optionally, the vehicle usage scenario data includes a first number of test cases. The vehicle usage scenario data is used to drive the on-board control unit to perform control operations, and the test data obtained includes: traversing the first number of test cases according to the scenario execution process; based on the target scenario data, driving the on-board control unit to perform control operations on the on-board components, and obtaining the status data corresponding to the on-board components and the log data of the on-board control unit, wherein the target scenario data is the test case currently being tested in the traversal; and generating test data based on the status data and log data.

[0008] Optionally, the evaluation method of the vehicle control unit also includes: generating visualization results based on vehicle usage scenario data and test data, wherein the visualization results include at least a vehicle virtual model, environment rendering data, and fault annotation data; and displaying the visualization results in a display panel within the visualization interface.

[0009] Optionally, the vehicle usage scenario data includes driving operation data and road environment data. Generating visualization results based on the vehicle usage scenario data and test data includes: generating a vehicle virtual model based on the driving operation data and the test data, wherein the vehicle virtual model is used to display the driver's operation and the status of the vehicle components in real time; generating environmental rendering data using the road environment data, wherein the environmental rendering data is used to reflect the dynamic changes of the vehicle's surrounding environment; analyzing the test data according to the warning standards corresponding to the vehicle failure event to obtain fault annotation data, wherein the fault annotation data is used to characterize the control operation that triggers the vehicle failure event.

[0010] Optionally, the visualization results also include the log data of the vehicle control unit, and the display panel includes a main perspective panel, a playback control panel and a data display control panel. Displaying the visualization results in the display panel within the visualization interface includes: displaying the vehicle virtual model and environment rendering data on the main perspective panel; displaying the fault annotation data on the playback control panel; and displaying the log data of the vehicle control unit on the data display control panel.

[0011] Optionally, the playback control panel includes a picture adjustment component and an input component, and the evaluation method of the vehicle control unit also includes: in response to triggering an adjustment event executed on the picture adjustment component, adjusting the test data to obtain reproduction data; in response to triggering an input event executed on the input component, updating the content displayed on the main perspective panel according to the reproduction data and the input tag data corresponding to the input event.

[0012] Optionally, performing a functional evaluation on the test data to generate an evaluation result includes: performing a functional availability evaluation on the test data to obtain a functional availability result, wherein the functional availability result is used to evaluate whether the function of the on-board control unit fails; performing a functional experience evaluation on the test data to obtain a functional experience result, wherein the functional experience result is used to evaluate whether the function of the on-board control unit meets the functional experience index; and generating an evaluation result based on the functional availability result and the functional experience result.

[0013] Optionally, obtaining vehicle usage scenario data includes: obtaining version data and vehicle parameters of the vehicle control unit; and selecting vehicle usage scenario data from a scenario database based on the version data and vehicle parameters.

[0014] According to another aspect of an embodiment of the present application, an evaluation device for a vehicle-mounted control unit is also provided, including: an acquisition module for acquiring vehicle usage scenario data corresponding to the vehicle-mounted control unit, wherein the vehicle usage scenario data is used to characterize the scenario operating condition characteristics of the vehicle-mounted control unit in the entire vehicle usage process, and the entire vehicle usage process includes a trip preparation stage, a trip travel stage, and a trip end stage; a testing module for using the vehicle usage scenario data to drive the vehicle-mounted control unit to perform control operations and obtain test data; a generation module for performing functional evaluation on the test data and generating evaluation results, wherein the evaluation results are used to characterize whether the functional performance of the vehicle-mounted control unit meets the release standards.

[0015] According to another aspect of an embodiment of the present application, a vehicle is further provided, comprising: a memory storing an executable program; and a processor for running the program, wherein when the program is running, any one of the above-mentioned methods for evaluating a vehicle-mounted control unit is executed.

[0016] In an embodiment of the present application, vehicle usage scenario data is obtained, and the vehicle usage scenario data is used to characterize the scenario operating characteristics of the on-board control unit in the entire vehicle usage process, that is, the vehicle usage scenario data can represent the overall level of the entire vehicle usage process; further, the vehicle usage scenario data is used to drive the on-board control unit to perform control operations, so that the functional performance of the on-board control unit can be evaluated from the overall level of the entire vehicle usage process, and test data with higher accuracy can be obtained; further, the test data is functionally evaluated, and an evaluation result with higher accuracy can be generated. In addition, the above-mentioned processes of the present application can all be automatically implemented, without relying on manual recording of test data and manual evaluation, thereby improving the efficiency of the evaluation method of the on-board control unit. Therefore, the present application achieves the purpose of using vehicle usage scenario data to more accurately perform functional evaluation of the on-board control unit, thereby achieving the technical effect of improving the accuracy of the evaluation method of the on-board control unit, and thus solving the technical problem of poor accuracy of the evaluation result of the method of evaluating the on-board control unit based on modular functional use cases in the related art. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] Figure 1 is a flow chart of a method for evaluating a vehicle control unit according to one embodiment of the present application;

[0019] Figure 2 is a schematic diagram of an optional evaluation method for an on-board control unit according to one embodiment of the present application;

[0020] Figure 3is a schematic diagram of an optional visualization module according to one embodiment of the present application;

[0021] Figure 4 is a schematic diagram of an optional performance evaluation module according to one embodiment of the present application;

[0022] Figure 5 is a schematic diagram of an optional scene library module according to one embodiment of the present application;

[0023] Figure 6 4 is a structural block diagram of an evaluation device for a vehicle-mounted control unit according to one embodiment of the present application. DETAILED DESCRIPTION

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

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

[0026] According to an embodiment of the present application, an embodiment of a method for evaluating a vehicle-mounted control unit is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0027] The method embodiment can also be executed in an electronic device including a memory and a processor, a similar control device, or an in-vehicle terminal. Taking an in-vehicle terminal as an example, the in-vehicle terminal may include one or more processors and a memory for storing data. Optionally, the in-vehicle terminal may also include a communication device and a display device for communication functions. It will be understood by those skilled in the art that the above structural description is only illustrative and does not limit the structure of the in-vehicle terminal. For example, the in-vehicle terminal may also include more or fewer components than those described in the above structural description, or have a configuration different from that described in the above structural description.

[0028] The processor may include one or more processing units. For example, the processor may include a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing (DSP) chip, a microcontroller unit (MCU), a field-programmable gate array (FPGA), a neural-network processing unit (NPU), a tensor processing unit (TPU), an artificial intelligence (AI) type processor, and the like. Among them, different processing units may be independent components or integrated into one or more processors. In some instances, the electronic device may also include one or more processors.

[0029] The memory can be used to store computer programs, such as a computer program corresponding to the vehicle control unit evaluation method in the embodiments of the present application. The processor implements the vehicle control unit evaluation method by running the computer program stored in the memory. The memory can include high-speed random access memory (RAM) and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory can further include a memory remotely located relative to the processor, and these remote memories can be connected to the electronic device via a network. Examples of the aforementioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0030] The communication device is used to receive or send data via a grid. Specific examples of the aforementioned grid may include a wireless grid provided by a communication provider of the mobile terminal. In one example, the communication device includes a grid adapter (network interface controller, abbreviated as NIC), which can be connected to other grid devices via a base station to communicate with the Internet. In one example, the communication device can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly. In some embodiments of the present solution, the communication device is used to connect to mobile devices such as mobile phones and tablets, and can send instructions to the vehicle-mounted terminal via the mobile device.

[0031] The display device may be a touchscreen liquid crystal display (LCD) or a touch display (also referred to as a "touch screen" or "touch display"). The LCD may enable a user to interact with the user interface of the vehicle-mounted terminal. In some embodiments, the vehicle-mounted terminal may include a graphical user interface (GUI), and the user may interact with the GUI through finger contact and / or gestures on the touch surface. The human-computer interaction function may include a vehicle gear shifting function, and the executable instructions for executing the human-computer interaction function may be configured / stored in a computer program product or a readable storage medium executable by one or more processors.

[0032] Figure 1 is a flow chart of an evaluation method for a vehicle control unit according to one embodiment of the present application, such as Figure 1 As shown, the method includes the following steps:

[0033] Step S101: Acquire vehicle usage scenario data corresponding to the vehicle control unit, wherein the vehicle usage scenario data is used to characterize the scenario operating condition characteristics of the vehicle control unit in the entire vehicle usage process, and the entire vehicle usage process includes the trip preparation stage, the trip travel stage, and the trip end stage;

[0034] Step S102, using the vehicle usage scenario data, driving the vehicle control unit to perform control operations to obtain test data;

[0035] Step S103 : performing a functional evaluation on the test data to generate an evaluation result, wherein the evaluation result is used to indicate whether the functional performance of the vehicle control unit meets the release standard.

[0036] The vehicle control unit can be responsible for receiving and processing various sensor data from inside and outside the vehicle, as well as controlling the actions of the vehicle's actuators. The vehicle control unit can be an onboard hardware device, and in particular, it can also be a unit that hosts an application for controlling the vehicle's actuators.

[0037] The above sensor data can be collected by vehicle-mounted sensors. The above vehicle-mounted sensors may include, but are not limited to, visual sensors (e.g., cameras), radar sensors, laser sensors, inertial detection sensors, rotation sensors (e.g., Hall effect sensors), speed sensors, acceleration sensors, angular velocity detection sensors, temperature sensors, humidity sensors, tire pressure detection sensors, wheel speed sensors, vibration sensors, and acoustic sensors.

[0038] The above-mentioned vehicle usage scenario data can be obtained through a preset use case data set. The vehicle usage scenario data can also be written in extensible markup language. The vehicle usage scenario data may refer to a data set used to describe the operating condition characteristics of the entire vehicle usage process during the use of the vehicle. The vehicle usage scenario data may represent a single test case, or a test suite containing multiple test cases. The vehicle usage scenario data may include but is not limited to: driving operation data, road environment data, vehicle initial state data, driving mode data, and vehicle multimedia system function data. The above-mentioned trip preparation stage may include approaching the vehicle, entering the vehicle, and starting the vehicle. The above-mentioned trip travel stage may include driving the vehicle. The above-mentioned trip end stage may include parking the vehicle and leaving the vehicle.

[0039] The above test data can be used to characterize the functional execution results and user experience level of the vehicle control unit in a specific scenario. The test data may include but is not limited to: test sequence data, test scenario data, log data of the vehicle control unit, working parameters of multiple vehicle actuators in the vehicle system, sensor data, action feedback information of the vehicle actuator, status information of the vehicle actuator, and user interaction record information. For example, the test data can be specific numerical information such as engine speed, vehicle speed, braking force, steering angle, air conditioning temperature setting, seat position adjustment, etc.; for another example, the test data can be status information such as brake light switch status, wiper switch status, etc.; for another example, the test data can be control process information and control feedback information of the vehicle control unit.

[0040] Exemplarily, the process of using vehicle usage scenario data to drive the on-board control unit to perform control operations can be as follows: in a field experimental environment or in a virtual environment, simulate the vehicle usage scenario corresponding to the vehicle usage scenario data, such as different driving conditions, user operation modes or the vehicle's surrounding environment; further, use the vehicle usage scenario data to generate control signals, which can imitate the user's operations during actual use, such as adjusting the air-conditioning temperature, starting cruise control, switching driving modes, etc., and at the same time convert environmental data (such as weather, road conditions, etc.) into corresponding control signals, which are input to the on-board control unit to enable the on-board control unit to perform corresponding control actions and adjust the working state of the vehicle system, such as adjusting engine output, controlling the braking system, activating safety functions, etc.; during the execution of the control operation, continuously monitor and record the response of the on-board control unit and the vehicle status change information, so as to obtain test data based on the response of the on-board control unit and the vehicle status change information.

[0041] By obtaining vehicle usage scenario data that characterizes the scenario operating conditions of the on-board control unit throughout the entire vehicle usage process, and using this vehicle usage scenario data to drive the on-board control unit to perform control operations, the functional performance of the on-board control unit can be evaluated from the overall level of the entire vehicle usage process, thereby obtaining more accurate test data.

[0042] The above-mentioned evaluation results can be a quantitative evaluation of the functional performance of the vehicle control unit in a specific vehicle usage scenario. The evaluation results may include but are not limited to: functional usability results, functional experience results, and function-vehicle compatibility results. The evaluation results can be obtained through a functional evaluation method. The above-mentioned functional evaluation methods may include but are not limited to: evaluation calculation methods based on functional evaluation indicators, evaluation methods based on deep learning, and evaluation methods based on fuzzy neural networks. The above-mentioned release standards can be set according to vehicle production requirements. The above-mentioned release standards can be obtained through a preset release standard set.

[0043] In particular, the test data can be compared and analyzed with preset standards, such as vehicle stability, response speed, functional integrity, failure rate, etc. of the vehicle control unit, to determine whether the vehicle control unit meets the release standards.

[0044] In an embodiment of the present application, vehicle usage scenario data is obtained, and the vehicle usage scenario data is used to characterize the scenario operating condition characteristics of the on-board control unit in the entire vehicle usage process, that is, the vehicle usage scenario data can represent the overall level of the entire vehicle usage process; further, the vehicle usage scenario data is used to drive the on-board control unit to perform control operations, so that the functional performance of the on-board control unit can be evaluated from the overall level of the entire vehicle usage process, and test data with higher accuracy can be obtained; further, the test data is functionally evaluated, and an evaluation result with higher accuracy can be generated. In addition, the above-mentioned processes of the present application can all be automatically implemented, without relying on manual recording of test data and manual evaluation, thereby improving the efficiency of the evaluation method of the on-board control unit. Thus, the present application achieves the purpose of more accurately performing functional evaluation of the on-board control unit by using the vehicle usage scenario data that characterizes the scenario operating condition characteristics of the on-board control unit in the entire vehicle usage process, thereby achieving the technical effect of improving the accuracy of the evaluation method of the on-board control unit, and thus solving the technical problem of poor accuracy of the evaluation result caused by the method of evaluating the on-board control unit based on modular functional use cases in the related art.

[0045] Optionally, the vehicle usage scenario data includes a first number of test cases. In step S102, the vehicle usage scenario data is used to drive the vehicle control unit to perform a control operation, and the obtained test data includes:

[0046] Step S121, performing traversal testing on a first number of test cases according to the scenario execution process;

[0047] Step S122: driving the vehicle control unit to perform control operations on the vehicle components according to the target scenario data, obtaining status data corresponding to the vehicle components and log data of the vehicle control unit, wherein the target scenario data is the test case currently being tested in the traversal;

[0048] Step S123: Generate test data based on the status data and log data.

[0049] The test cases may include, but are not limited to, input signal parameters, user operation data, diagnostic data identifier parameters, actuator signal parameters, and environmental data (e.g., light intensity, temperature, humidity, road type, etc.). The first number may be the number of test cases included in the vehicle usage scenario data. For example, the first number may be set to 10 or 20. Specifically, the number may be determined based on actual testing requirements, and this application does not limit the specific setting value of the first number.

[0050] The above scenario execution process can be a preset execution process. This scenario execution process can also be generated by a deep learning model. The scenario execution sequence can be a series of operation steps and a time sequence. This scenario execution sequence may include, but is not limited to: the sequence of operation commands, information about changes in environmental parameters, and information about expected system responses. This scenario execution sequence can be used to represent the logical path of user interaction.

[0051] It should be noted that since the three sub-stages of trip preparation, trip progress and trip end can include multiple scenarios, the above scenario execution process only needs to meet the order of trip preparation, trip progress and trip end, and the order of each scenario in each sub-stage can be adjusted.

[0052] In an exemplary application scenario, a first number of test cases are traversed and tested according to the scenario execution process, that is, the first number of test cases contained in the vehicle usage scenario data are tested one by one. For example, the trip preparation stage includes remotely checking the vehicle location and remotely controlling the vehicle using a mobile phone. At this time, the scenario execution process can be to first remotely control the vehicle using a mobile phone and then remotely check the vehicle location.

[0053] The aforementioned in-vehicle components may be hardware devices in the vehicle that are responsible for performing operations. Such in-vehicle components may include, but are not limited to, engine control systems, braking systems, steering systems, air conditioning systems, infotainment systems, airbags, sensors (e.g., radars, cameras), and actuators (e.g., motors, valves, etc.).

[0054] The aforementioned status data can be used to characterize the actual operating state of the vehicle under target scenario data. This status data may include, but is not limited to, vehicle speed, engine speed, battery charge, interior temperature, music playback status, light on / off status, door open / close status, and security system alarm status. This status data can be collected and acquired through onboard sensors, monitored by external test equipment, or obtained through execution feedback data recorded by onboard components.

[0055] The aforementioned log data can be used to characterize the functional execution and internal logic execution flow of the vehicle control unit under target scenario data. This log data can be automatically generated and stored by the vehicle control unit during operation and can be read and analyzed through test diagnostic tools or data interfaces. This log data may include, but is not limited to: the model of the vehicle control unit, the software version information installed in the vehicle control unit, the sending time and receipt confirmation of control instructions, the real-time change curve of sensor signals, feedback information on actuator actions, error codes and their generation time, the time when the fault occurred, and information on the exception handling process.

[0056] The above test data can be obtained through data integration. The collected status data and log data are integrated in chronological order to form a test data set, ensuring the relevance of the data and the integrity of the context.

[0057] In particular, the above-mentioned test data may also include annotated data corresponding to a fault event. The annotated data may be obtained by utilizing a fault detection method. The above-mentioned fault detection method may include, but is not limited to: a fault detection method based on machine vision, a fault detection method based on a machine learning model (for example, using state data and log data as inputs of a machine learning model, using the machine learning model to perform logical reasoning to determine whether a fault event has occurred, and annotating the state data and log data corresponding to the moment of the fault event). Thus, based on the state data and log data, annotated data is generated using a fault detection method, and then the state data, log data, and annotated data are integrated to obtain test data. For example, in the case of a vehicle's misbraking during normal driving on rainy days, a machine learning model is used to perform logical reasoning on the state data and log data, and it can be determined that the cause of the misbraking is: raindrops falling on the camera cause the camera's field of view to be blurred, causing the system to mistakenly judge the shadow of the building as an obstacle, thereby causing misbraking.

[0058] It is easy to understand that through the above steps S121 to S123, in the embodiment of the present application, the first number of test cases are traversed and tested according to the scenario execution process, and the on-board control unit is driven in turn to perform control operations on the on-board components to obtain status data and log data, thereby realizing an overall test of the on-board control unit based on the vehicle usage scenario data including the entire vehicle usage process, improving the comprehensiveness of the test data, and ensuring that the functional performance of the on-board control unit can be evaluated from a holistic level in the future.

[0059] Optionally, the above-mentioned vehicle control unit evaluation method further includes:

[0060] Step S104: generating a visualization result based on the vehicle usage scenario data and the test data, wherein the visualization result at least includes a vehicle virtual model, environment rendering data, and fault annotation data;

[0061] Step S105: Display the visualization result in a display panel within the visualization interface.

[0062] The above visualization results can be generated by using a visualization processing algorithm. The visualization results can reflect the process and results of the vehicle control unit executing control operations driven by the vehicle usage scenario. The visualization processing algorithm is used to process the vehicle usage scenario data and test data (for example, data extraction, data preprocessing, data conversion, etc.) to generate the visualization results.

[0063] The aforementioned vehicle virtual model can refer to a simulated reproduction of a physical vehicle in a digital environment. The vehicle virtual model can include a 3D model of the vehicle's exterior, a 3D model of the vehicle's interior, the dynamic response of the vehicle's systems, and the driver's behavior.

[0064] The aforementioned environmental rendering data may refer to a data set used to reproduce and visualize the environmental conditions in the vehicle test scenario. This environmental rendering data may include, but is not limited to, road conditions, weather conditions (e.g., sunny, rainy, foggy, etc.), lighting conditions, obstacle locations, surrounding vehicles, and surrounding pedestrians.

[0065] The above-mentioned fault annotation data may refer to information that marks and / or describes the data of abnormalities or faults that occur during the testing of the vehicle control unit. The fault annotation data may include but is not limited to: fault type, time point of fault occurrence, fault location, analysis of the cause of the fault (such as system misjudgment, software crash, function activation delay, etc.). The fault annotation data can be used to characterize the performance defects of the vehicle control unit in a specific vehicle usage scenario. In particular, during the test and evaluation of the vehicle control unit, if no fault occurs, the content of the fault annotation data can be set to "none" to ensure that the test can run normally.

[0066] The above-mentioned visualization interface can be used to present the vehicle status, environmental simulation, test process data and test results in real time. The above-mentioned display panel can be the area in the visualization interface used to present the visualization results.

[0067] It is easy to understand that through the above-mentioned steps S104 to S150, in the embodiment of the present application, by generating visualization results and displaying the visualization results in the display panel within the visualization interface, the process and results of driving the on-board control unit to perform control operations can be more intuitively presented on the display panel, which is convenient for testers to intuitively understand the functional performance of the on-board control unit and the situation where the fault exists, thereby accelerating problem location.

[0068] Optionally, the vehicle usage scenario data includes driving operation data and road environment data. In the above step S104, generating a visualization result based on the vehicle usage scenario data and the test data includes:

[0069] Step S141, generating a vehicle virtual model based on the driving operation data and the test data, wherein the vehicle virtual model is used to display the driver's operation and the status of the vehicle components in real time;

[0070] Step S142, using the road environment data to generate environment rendering data, wherein the environment rendering data is used to reflect the dynamic changes of the vehicle's surrounding environment;

[0071] Step S143 : analyzing the test data according to the warning standard corresponding to the vehicle fault event to obtain fault annotation data, wherein the fault annotation data is used to characterize the control operation that triggers the vehicle fault event.

[0072] The driving operation data can be used to characterize the driver's operating behavior. The driving operation data may include, but is not limited to, steering wheel angle information, accelerator pedal degree information, vehicle braking information, visual image information, and control command information.

[0073] The vehicle virtual model can not only display the vehicle's appearance in real time, but also simulate the real-time motion state of the real vehicle in different vehicle usage scenarios (such as the vehicle is in steering state, the vehicle is in accelerating state, the vehicle is in braking state, etc.), driver operations (such as the driver turning the steering wheel, stepping on the accelerator, turning on the turn signal, talking to the smart voice assistant, etc.) and the status of vehicle components (such as steering wheel angle, door status, accelerator pedal angle, brake pedal angle, etc.).

[0074] The above-mentioned road environment data may include but is not limited to: data of surrounding vehicles (such as the speed of surrounding vehicles, acceleration of surrounding vehicles, distance between surrounding vehicles, etc.), climate information data (such as temperature, humidity, light intensity, etc.).

[0075] The above-mentioned environmental rendering data can be generated through three-dimensional image modeling technology and real-time rendering algorithms. The environmental rendering data can represent the specific environmental background during the test, provide background information for the test results, and help engineers understand the performance of the vehicle control unit in a specific environment.

[0076] The aforementioned warning criteria can be a pre-set alarm mapping table. By comparing and analyzing test data with the warning criteria, it is determined whether a vehicle failure event has been triggered, thereby determining the control operation that triggered the vehicle failure event and obtaining fault annotation data. Furthermore, the aforementioned warning criteria can also be generated using a warning model. By using vehicle failure events and corresponding test data to train the warning model, the warning model is used to generate warning criteria corresponding to the vehicle failure event.

[0077] In an exemplary application scenario, Figure 2As shown, the present application can be regarded as a functional performance evaluation system for an on-board control unit based on a user's car usage scenario, in which the functional performance evaluation system for the on-board control unit based on a user's car usage scenario includes a visualization module, which at least displays a vehicle virtual model, environmental rendering data, and fault annotation data. The above-mentioned vehicle virtual model may refer to a three-dimensional vehicle model that restores the actual state of the vehicle in a one-to-one ratio. By integrating a physical engine and a vehicle dynamics algorithm, the vehicle virtual model can simulate the dynamic changes of the vehicle in real time according to the input driving operation data and test data. The vehicle virtual model can display the driver's operation and the status of multiple on-board components in the car in real time, and is used to intuitively characterize the execution effect of the function of the on-board control unit in the virtual environment. In addition, the controller corresponding to the vehicle virtual model can also transmit the data corresponding to the driver's operation and the status of multiple on-board components in the car (including video data and audio data) to the storage area for recording.

[0078] Still in the aforementioned application scenario, the environmental rendering data can be real-time, three-dimensional rendering data of the vehicle's surroundings, including road conditions, information about road users, and weather conditions such as rain, fog, and snow. Specifically, this environmental rendering data can be displayed dynamically. Road environment data is collected via onboard sensors, processed using real-time rendering algorithms, and generated using 3D image modeling technology to ensure accurate reproduction of the test scene.

[0079] Still in the above application scenario, the pre-set warning standards corresponding to the vehicle failure event are obtained, and by comparing and analyzing the test data with the warning standards, it is determined whether the vehicle failure event is triggered, for example, automatic emergency braking (Automatic Emergency Braking, abbreviated as AEB) is triggered, and the system issues an alarm (such as abnormal tire pressure, collision warning, fault alarm, etc.). Furthermore, the control operation data that triggers the vehicle failure event is determined from the test data, and the control operation that triggers the vehicle failure event is automatically marked and annotated to obtain fault annotation data.

[0080] It is easy to understand that through the above steps S141 to S143, in an embodiment of the present application, various types of visualization results can be generated based on the vehicle usage scenario data and test data, such as vehicle virtual models, environment rendering data, and fault annotation data, which can improve the sophistication of the visualization results and help testers quickly analyze the test results.

[0081] Optionally, the visualization result also includes log data of the vehicle control unit, and the display panel includes a main viewing angle panel, a playback control panel, and a data display control panel. In the above step S105, displaying the visualization result in the display panel within the visualization interface includes:

[0082] Step S151, displaying the vehicle virtual model and environment rendering data on the main viewing panel;

[0083] Step S152, displaying the fault annotation data on the playback control panel;

[0084] Step S153: Display the log data of the vehicle control unit on the data display control panel.

[0085] The main view panel can refer to the core area of ​​the visualization interface, typically occupying the largest area. The main view panel can be used to display a three-dimensional vehicle model and a rendering of the vehicle's environment. In particular, the vehicle virtual model and environment rendering data can be organized in chronological order to obtain test video data, which is then displayed on the main view panel. The playback control panel can be used to control the image displayed in the main view, and the playback control panel can also be used to mark and annotate the test data.

[0086] The aforementioned log data may include, but is not limited to, positioning system data, ultrasonic radar data, Ethernet data, and communication bus data. The aforementioned data display control panel may also include a display control component, such as a data selection box. The data display control panel can be used to control the log data displayed on the vehicle control unit. Specifically, by operating the data selection box in the data display control panel, the user can select to display or hide certain vehicle control unit log data, for example, disabling Ethernet data.

[0087] In an exemplary application scenario, Figure 2 As shown, the display panel in the visualization module may include a main viewing angle panel, a playback control panel, and a data display control panel. Figure 3 As shown, the status of the vehicle in different vehicle usage scenarios can be displayed in real time or played back through the main perspective panel; the playback control panel can be used to flexibly record, play back and annotate the images displayed in the main perspective, thereby enhancing the tester's controllability over the display of the test process and improving the tester's efficiency in analyzing problems that arise during the test process; by using the data display control panel, the data that the tester focuses on can be selected to display, so as to simplify the content of the display interface and enhance the user-friendliness of the interface.

[0088] It is easy to understand that through the above steps S151 to S153, in the embodiment of the present application, the visualization system includes multiple panels, which can partition and display the different contents contained in the visualization results, helping testers to quickly view the data of interest and improving the user-friendliness of the display interface.

[0089] Optionally, the playback control panel includes a picture adjustment component and an input component, and the evaluation method of the vehicle-mounted control unit further includes:

[0090] Step S106, in response to the adjustment event that triggers the image adjustment component to be executed, adjusting the test data to obtain reproduced data;

[0091] Step S107 , in response to the input event that triggers the input component to be executed, the content displayed on the main viewing panel is updated according to the recurrence data and the input tag data corresponding to the input event.

[0092] The above-mentioned picture adjustment components may include but are not limited to: a play component, a pause component, a progress adjustment component, and a play speed adjustment component. The above-mentioned input components may include but are not limited to: a text box component, a picture insertion component, and a mark component.

[0093] The above-mentioned reproduction data can be used to characterize the response results of the adjustment event operation. For example, by operating the playback speed adjustment component, the test data can be adjusted so that the picture displayed in the main perspective can be played at the speed expected by the tester.

[0094] In an exemplary application scenario, the test data (including video data and audio data) is transferred to the storage area for recording in the main perspective panel. The playback control panel includes a video selection component, a picture adjustment component and an input component, wherein the picture adjustment component includes a playback component, a pause component and a progress adjustment component. The video data stored in the storage area is displayed in real time by using the video selection component in the playback control panel. Furthermore, in response to the adjustment event triggered by the picture adjustment component, the test data is adjusted to obtain the reproduction data. For example, the playback component / pause component in the playback control panel can be used to control the play / pause of the picture displayed in real time in the main perspective window to obtain the corresponding reproduction data. The progress adjustment component can also be used to control the progress of the picture displayed in real time in the main perspective window by dragging the progress to obtain the corresponding reproduction data.

[0095] Still in the above application scenario, in response to the input event that triggers the execution of the input component, for example, the annotation text "voice false wake-up occurs here" or "autonomous driving crosses the solid line lane change occurs here" is added using the text box component, and the annotation text added by the text box component is used as the input mark data corresponding to the input event. For example, the marking component is used to perform a dot marking operation on the test data to obtain event dot data, and the event dot data is used as the input mark data corresponding to the input event. Then, according to the reproduced data and the input mark data corresponding to the input event, the content displayed on the main perspective panel is updated. In particular, when the input event executed on the input component is not triggered, the content displayed on the main perspective panel can be updated only based on the reproduced data.

[0096] It is easy to understand that through the above steps S106 to S107, in the embodiment of the present application, the screen adjustment component and input component in the playback control panel can be used to realize the multi-dimensional reproduction test process and manual annotation functions, which can enhance the tester's controllability over the display screen.

[0097] Optionally, in step S103, performing a functional evaluation on the test data to generate an evaluation result includes:

[0098] Step S131, performing a function availability evaluation on the test data to obtain a function availability result, wherein the function availability result is used to evaluate whether the function of the vehicle control unit fails;

[0099] Step S132: Perform a function experience evaluation on the test data to obtain a function experience result, wherein the function experience result is used to evaluate whether the function of the vehicle control unit meets the function experience index;

[0100] Step S133: Generate an evaluation result based on the function availability result and the function experience result.

[0101] The above-mentioned functional availability results may include but are not limited to: functional response status (i.e., confirming whether the function is activated normally, for example, whether AEB is correctly started when it should be triggered), exception handling capabilities (for example, when the positioning signal is lost, whether the navigation system can provide alternative solutions or error prompts), and operation command execution status (for example, whether the temperature adjustment instructions of the voice-controlled air conditioner are accurately executed). The functional availability results can be obtained using a test tool. By using the test tool to evaluate the functional availability of the test data, it is determined whether there is any failure in the function of the on-board control unit to obtain the functional availability results. The functional availability results can also be obtained through a functional availability evaluation algorithm based on deep learning. The functional availability results can be set as a continuous value or as a binary value, for example, 0 and 1.

[0102] The above functional experience results can be obtained using a deep learning-based functional experience evaluation algorithm. In particular, the functional experience results can also be obtained using manually annotated data from the test data. The above functional experience indicators may include but are not limited to: freeze duration, delay duration, sensitivity, and functional design rationality indicators. The functional experience results can be set as continuous values ​​or as binary values, for example, 0 and 1.

[0103] The evaluation results may include at least an evaluation score. The evaluation score may be obtained by an evaluation calculation method. The evaluation calculation method may include, but is not limited to, a summation calculation method, an arithmetic mean calculation method, a weighted average calculation method, and a calculation method combined with manual scoring.

[0104] In an exemplary application scenario, Figure 2 As shown in FIG, the functional performance evaluation system of the vehicle control unit based on the user's vehicle usage scenario includes a performance evaluation module. Specifically, Figure 4 As shown, the vehicle usage scenario data includes a first number (for example, 100) of test cases, and each test case has corresponding test data. The primary function availability result can be set as a binary value (including 0 and 0.5), and the test data corresponding to each test case is evaluated for functional availability in turn to determine whether the vehicle control unit function fails under the test case. If the vehicle control unit function fails, the primary function availability result corresponding to the test case is recorded as 0. If the vehicle control unit function does not fail, the primary function availability result corresponding to the test case is recorded as 0.5. In this way, the functional availability result corresponding to each test case can be obtained. The primary function availability results corresponding to each test case are added together to obtain the functional availability result corresponding to the vehicle usage scenario data.

[0105] Still in the above application scenario, the primary functional experience result can be set as a binary value (including 0 and 0.5), and the functional experience evaluation can be performed on the test data corresponding to each test case in turn to determine whether the vehicle control unit function meets the functional experience index under the test case. For example, for the delay time in the functional experience index, if the vehicle control unit function is turned on within the preset time, it is regarded as whether the vehicle control unit function meets the delay time in the functional experience index. If the vehicle control unit function does not meet the functional experience index under the test case, the primary functional experience result corresponding to the test case is recorded as 0. If the vehicle control unit function meets the functional experience index under the test case, the primary functional experience result corresponding to the test case is recorded as 0.5. In this way, the functional experience result corresponding to each test case can be obtained. By adding the primary functional experience results corresponding to each test case, the functional experience result corresponding to the vehicle usage scenario data can be obtained.

[0106] Still in the above application scenario, the evaluation calculation method is used to calculate the functional availability results and the functional experience results to obtain an evaluation score, which can be directly used as the evaluation result. In particular, a full score value can be set (the full score value can be determined based on the above-mentioned first number, for example, the above-mentioned first number is 100, and the full score value is 100), a first threshold value and a second threshold value, wherein the first threshold value is less than the second threshold value (for example, the first threshold value can be set to 80%, and the second threshold value can be set to 100%). Further, the ratio of the evaluation score to the full score value is calculated, and the ratio is compared with the first threshold value and the second threshold value.

[0107] Still in the above application scenario, if the ratio of the above evaluation score to the full score is less than the first threshold value (that is, the evaluation score is less than 80), it is considered that the functional performance of the on-board control unit does not meet the release standard, and text data corresponding to "not allowed to be released to the outside" is generated, and the text data and the evaluation score are used as the evaluation result; if the ratio of the above evaluation score to the full score is greater than or equal to the first threshold value and the ratio of the above evaluation score to the full score is less than the second threshold value (that is, the evaluation score is greater than or equal to 80 and the evaluation score is less than 100), it is considered that the functional performance of the on-board control unit can be conditionally passed (for example, the functional experience result corresponding to the vehicle usage scenario data is 50), and text data corresponding to "conditional release to the outside" is generated, and the text data and the evaluation score are used as the evaluation result; if the ratio of the above evaluation score to the full score value is equal to the second threshold value (that is, the evaluation score is equal to 100), it is considered that the functional performance of the on-board control unit meets the release standard, and text data corresponding to "allowed to be released to the outside" is generated, and the text data and the evaluation score are used as the evaluation result.

[0108] It is easy to understand that through the above steps S131 to S133, in the embodiment of the present application, the functional performance of the on-board control unit is evaluated from the two dimensions of functional performance and functional experience, which can more comprehensively evaluate the functional performance of the on-board control unit and improve the accuracy of the evaluation results.

[0109] Optionally, in step S101 above, obtaining vehicle usage scenario data includes:

[0110] Step S111, obtaining the version data of the vehicle control unit and vehicle parameters;

[0111] Step S112: Select vehicle usage scenario data from the scenario database based on the version data and vehicle parameters.

[0112] The aforementioned version data may refer to the specific version information of the control software installed on the vehicle control unit. This version data may include, but is not limited to, the software's major version number, minor version number, revision number, and build time. Obtaining the vehicle control unit's version data can help determine the software version currently running on the vehicle, enabling testers to quickly troubleshoot and perform compatibility testing.

[0113] The aforementioned vehicle parameters may include the vehicle's hardware configuration and feature list. These vehicle parameters may include, but are not limited to, engine model, sensor type, and actuator specifications. These vehicle parameters can be used to determine the vehicle's capabilities and performance indicators, ensuring that software functions match the hardware configuration, avoiding incompatibilities or redundant features. The aforementioned scenario database may be a predefined scenario dataset.

[0114] In an exemplary application scenario, Figure 2 As shown in FIG, the functional performance evaluation system of the vehicle control unit based on the user's vehicle usage scenario includes a scenario library module. Specifically, Figure 5 As shown, the above-mentioned scenario database may include scenario data of three sub-stages: the trip preparation stage, the trip travel stage and the trip end stage. The above-mentioned trip preparation stage may include 3 first-level vehicle use scenarios (i.e., approaching the vehicle, entering the vehicle, and starting the vehicle), wherein the first-level vehicle use scenario of approaching the vehicle includes 3 second-level vehicle use scenarios (i.e., checking the vehicle status, remote vehicle control, and finding the vehicle), further, checking the vehicle status (especially, it can also be remotely using a mobile phone to check the vehicle status) the second-level vehicle use scenario includes 3 third-level vehicle use scenarios (i.e., remotely checking the vehicle location, checking the remaining power / fuel / mileage, and remotely checking tire pressure operations), the second-level vehicle use scenario of remote vehicle control includes 2 third-level vehicle use scenarios (i.e., using the vehicle control program on the mobile phone to turn on the air conditioner, and using the vehicle control program on the mobile phone to remotely schedule the air conditioner operation), the second-level vehicle use scenario of finding the vehicle includes 2 third-level vehicle use scenarios (i.e., using the vehicle control program on the mobile phone to find the vehicle, using a remote control key or using a Bluetooth key to find the vehicle); the first-level vehicle use scenario of entering the vehicle includes 2 The second-level car use scenario (i.e., unlocking the vehicle and opening and closing the trunk). Further, the second-level car use scenario of unlocking the vehicle includes 3 third-level car use scenarios (i.e., unlocking with the remote control key, unlocking with the digital key, and performing an approach unlocking operation). The second-level car use scenario of opening and closing the trunk includes 4 third-level car use scenarios (i.e., using the trunk button outside the vehicle to control, using the trunk button inside the vehicle to control, using the remote control key to control, and performing a trunk sensing unlocking operation). The first-level car use scenario of starting the vehicle includes 2 second-level car use scenarios (i.e., instrument panel check and driving preference adjustment). Further, the second-level car use scenario of instrument panel check includes 3 third-level car use scenarios (i.e., checking the remaining power and cruising range, checking the warning lights / indicator lights, and checking the status of the four doors and two lids). The second-level car use scenario of driving preference adjustment includes 5 third-level car use scenarios (i.e., easy getting on and off the vehicle, seat adjustment, rearview mirror adjustment, steering column adjustment, and head-up display adjustment operations).

[0115] Still in the above application scenario, the above journey stage can include one first-level car use scenario (i.e., driving the vehicle), wherein the first-level car use scenario of driving the vehicle includes 16 second-level car use scenarios (i.e., weather query, navigation, smart device charging, head-up display, lighting control, door lock control, window control, wiper control, seat comfort control, air conditioning control, phone control, network and hotspot control, multimedia control, driving record, driving assistance, and scene mode control). Furthermore, the second-level car use scenario of weather query includes two third-level car use scenarios (i.e., manual weather query and voice weather query operation), and the second-level car use scenario of navigation includes three third-level car use scenarios (i.e., seamless navigation, initiating navigation, and voice-controlled navigation operation). , the second-level car use scenario of smart device charging includes 2 third-level car use scenarios (i.e., wireless charging and wired charging operations), the second-level car use scenario of head-up display includes 3 third-level car use scenarios (i.e., head-up display switch, head-up display parameter adjustment, gear position / vehicle speed / remaining power and other information viewing operations), the second-level car use scenario of light control includes 14 third-level car use scenarios (i.e., Auto lights, position lights, low beam lights, high beam lights, rear fog lights, turn signals, hazard warning lights, reversing lights, brake lights, footlights, vanity mirror lights, glove box lights, reading lights, and ambient light operations), the second-level car use scenario of door lock control includes 2 third-level car use scenarios (i.e., high-speed automatic locking and child lock control operations), the second-level car use scenario of window control includes 2 Level 3 car use scenarios (i.e., in-car button control of windows, voice control of window operation), wiper control, a second-level car use scenario, includes 3 Level 3 car use scenarios (i.e., manual front wiper control, front windshield washing control, automatic front wiper control operation), seat comfort control, a second-level car use scenario, includes 2 Level 3 car use scenarios (i.e., manual control of seat comfort function, voice control of seat comfort function operation), air conditioning control, a second-level car use scenario, includes 2 Level 3 car use scenarios (i.e., manual control of air conditioning, voice control of air conditioning operation), phone control, a second-level car use scenario, includes 5 Level 3 car use scenarios (i.e., VIP dedicated line call, emergency rescue call, Bluetooth address book and call record synchronization, making Bluetooth calls, answering Bluetooth calls), network The second-level car use scenario of hotspot control includes 2 third-level car use scenarios (i.e., wireless network switch / search / connection, hotspot switch / search / connection operations), the second-level car use scenario of multimedia control includes 4 third-level car use scenarios (i.e., playing online music, playing online radio, playing Bluetooth music, playing radio operations), the second-level car use scenario of driving record includes 2 third-level car use scenarios (i.e., automatic recording, manual recording operations), the second-level car use scenario of driving assistance includes 7 third-level car use scenarios (i.e., driving mode adjustment, head-up display information viewing, adaptive cruise control, advanced cruise control, lever lane change, intelligent speed limit, navigation assistance operations), the second-level car use scenario of scene mode control includes 7 third-level car use scenarios (i.e.,Rain mode, smoking mode, smog mode, rest mode, baby mode, refreshment mode, car wash mode).

[0116] Still in the above application scenario, the above trip end stage can include 2 first-level car use scenarios (i.e., parking the vehicle and leaving the vehicle), among which the first-level car use scenario of parking the vehicle includes 2 second-level car use scenarios (i.e., parking and parking operation), further, the second-level car use scenario of parking includes 4 third-level car use scenarios (i.e., panoramic image, automatic parking, remote parking, and memory parking operation), and the second-level car use scenario of parking operation includes 3 third-level car use scenarios (i.e., software upgrade, watching videos, and playing games); the first-level car use scenario of leaving the vehicle includes 3 second-level car use scenarios (i.e., forgetting reminder, charging, and locking the vehicle), further, the second-level car use scenario of forgetting reminder includes 3 third-level car use scenarios (i.e., panoramic image, automatic parking, and remote parking operation), the second-level car use scenario of charging includes 3 third-level car use scenarios (i.e., charging customization, DC charging, and AC charging operation), and the second-level car use scenario of locking the vehicle includes 3 third-level car use scenarios (i.e., remote key locking, digital key locking, and away locking operation).

[0117] Still in the above application scenario, the version data and vehicle parameters of the vehicle control unit are obtained; based on the version data and vehicle parameters, vehicle usage scenario data is selected from the scenario database. It should be noted that when different vehicle usage scenario data is selected, different evaluation criteria can be set for functional evaluation of the test data obtained to ensure the accuracy of the evaluation results.

[0118] It is easy to understand that through the above steps S111 to S112, in the embodiment of the present application, different vehicle usage scenario data are selected from the scenario database according to the version data of the vehicle control unit and the vehicle parameters, ensuring that the evaluation method of the vehicle control unit can be used for various types of vehicles and multiple versions of vehicle control units, thereby improving the applicability of the evaluation method.

[0119] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or grid device, etc.) to execute the methods of each embodiment of the present application.

[0120] According to an embodiment of the present application, a device embodiment for implementing the above-mentioned vehicle control unit evaluation method is also provided. Please refer to Figure 6 The evaluation device 600 of the vehicle-mounted control unit includes: an acquisition module 601, used to obtain vehicle usage scenario data corresponding to the vehicle-mounted control unit, wherein the vehicle usage scenario data is used to characterize the scenario operating condition characteristics of the vehicle-mounted control unit in the entire vehicle usage process, and the entire vehicle usage process includes the trip preparation stage, the trip travel stage and the trip end stage; a testing module 602, used to use the vehicle usage scenario data to drive the vehicle-mounted control unit to perform control operations and obtain test data; a generation module 603, used to perform functional evaluation on the test data and generate evaluation results, wherein the evaluation results are used to characterize whether the functional performance of the vehicle-mounted control unit meets the release standards.

[0121] Optionally, the vehicle usage scenario data includes a first number of test cases, and the above-mentioned test module 602 is also used to perform traversal testing on the first number of test cases according to the scenario execution process; based on the target scenario data, drive the on-board control unit to perform control operations on the on-board components, and obtain the status data corresponding to the on-board components and the log data of the on-board control unit, wherein the target scenario data is the test case currently being tested in the traversal; generate test data based on the status data and log data.

[0122] Optionally, the evaluation device of the above-mentioned vehicle-mounted control unit also includes a visualization module (not shown in the figure), which is used to generate visualization results based on vehicle usage scenario data and test data, wherein the visualization results include at least a vehicle virtual model, environment rendering data, and fault annotation data; and the visualization results are displayed in a display panel within the visualization interface.

[0123] Optionally, the vehicle usage scenario data includes driving operation data and road environment data. The above-mentioned visualization module is used to generate a vehicle virtual model based on the driving operation data and test data, wherein the vehicle virtual model is used to display the driver's operation and the status of the vehicle components in real time; use the road environment data to generate environmental rendering data, wherein the environmental rendering data is used to reflect the dynamic changes of the vehicle's surrounding environment; according to the early warning standards corresponding to the vehicle fault event, the test data is analyzed to obtain fault annotation data, wherein the fault annotation data is used to characterize the control operation that triggers the vehicle fault event.

[0124] Optionally, the visualization results also include the log data of the vehicle control unit. The display panel includes a main perspective panel, a playback control panel and a data display control panel. The above-mentioned visualization module is used to display the vehicle virtual model and environment rendering data on the main perspective panel; display the fault annotation data on the playback control panel; and display the log data of the vehicle control unit on the data display control panel.

[0125] Optionally, the playback control panel includes a picture adjustment component and an input component. The above-mentioned visualization module is used to adjust the test data in response to an adjustment event triggered to be executed on the picture adjustment component to obtain reproduction data; in response to an input event triggered to be executed on the input component, update the content displayed on the main perspective panel according to the reproduction data and the input tag data corresponding to the input event.

[0126] Optionally, the above-mentioned generation module 603 is used to perform a functional availability evaluation on the test data to obtain a functional availability result, wherein the functional availability result is used to evaluate whether the function of the vehicle control unit fails; perform a functional experience evaluation on the test data to obtain a functional experience result, wherein the functional experience result is used to evaluate whether the function of the vehicle control unit meets the functional experience index; and generate an evaluation result based on the functional availability result and the functional experience result.

[0127] Optionally, the acquisition module 601 is configured to acquire version data of the vehicle control unit and vehicle parameters; and select vehicle usage scenario data from a scenario database based on the version data and vehicle parameters.

[0128] An embodiment of the present application further provides a vehicle, comprising: a memory storing an executable program; and a processor for running the program, wherein when the program is running, any one of the above-mentioned methods for evaluating a vehicle-mounted control unit is executed.

[0129] An embodiment of the present application further provides a computer-readable storage medium, which includes a stored executable program, wherein when the executable program is running, the device where the storage medium is located is controlled to execute the evaluation method of the vehicle control unit of any of the above embodiments.

[0130] Optionally, in this embodiment, the above-mentioned executable program can be configured to store an executable program for executing the following steps: obtaining vehicle usage scenario data corresponding to the on-board control unit, wherein the vehicle usage scenario data is used to characterize the scenario operating condition characteristics of the on-board control unit in the entire vehicle usage process, and the entire vehicle usage process includes the trip preparation stage, the trip travel stage, and the trip end stage; using the vehicle usage scenario data, driving the on-board control unit to perform control operations to obtain test data; performing functional evaluation on the test data to generate evaluation results, wherein the evaluation results are used to characterize whether the functional performance of the on-board control unit meets the release standards.

[0131] An embodiment of the present application further provides a computer program product, including a computer program, which implements the evaluation method of the vehicle control unit of any of the above embodiments when executed by a processor.

[0132] Optionally, in this embodiment, the above-mentioned computer program implements the following steps when executed by the processor: obtaining vehicle usage scenario data corresponding to the on-board control unit, wherein the vehicle usage scenario data is used to characterize the scenario operating condition characteristics of the on-board control unit in the entire vehicle usage process, and the entire vehicle usage process includes the trip preparation stage, the trip travel stage, and the trip end stage; using the vehicle usage scenario data, driving the on-board control unit to perform control operations to obtain test data; performing functional evaluation on the test data to generate evaluation results, wherein the evaluation results are used to characterize whether the functional performance of the on-board control unit meets the release standards.

[0133] Optionally, specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0134] In the above embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

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

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

[0137] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0138] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM), random access memory (RAM), mobile hard disk, magnetic disk or optical disk, etc., various media that can store program codes.

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

Claims

1. A method for evaluating a vehicle control unit, characterized in that: include: Obtaining vehicle usage scenario data corresponding to the vehicle control unit, wherein the vehicle usage scenario data is used to characterize the scenario operating condition characteristics of the vehicle control unit in the entire vehicle usage process, wherein the entire vehicle usage process includes a trip preparation phase, a trip travel phase, and a trip end phase; Using the vehicle usage scenario data, driving the vehicle-mounted control unit to perform a control operation to obtain test data; Perform a functional evaluation on the test data to generate an evaluation result, wherein the evaluation result is used to indicate whether the functional performance of the on-board control unit meets the release standard.

2. The evaluation method of the vehicle control unit according to claim 1, characterized in that: The vehicle usage scenario data includes a first number of test cases. The vehicle usage scenario data is used to drive the vehicle control unit to perform a control operation, and the test data obtained includes: Performing traversal testing on the first number of test cases according to the scenario execution process; According to the target scenario data, the vehicle control unit is driven to perform a control operation on the vehicle component to obtain status data corresponding to the vehicle component and log data of the vehicle control unit, wherein the target scenario data is the test case currently being tested in the traversal; The test data is generated based on the status data and the log data.

3. The evaluation method of the vehicle control unit according to claim 1, characterized in that: The vehicle control unit evaluation method further includes: Generate a visualization result based on the vehicle usage scenario data and the test data, wherein the visualization result at least includes a vehicle virtual model, environment rendering data, and fault annotation data; The visualization result is displayed in a display panel within the visualization interface.

4. The evaluation method of the vehicle control unit according to claim 3, characterized in that: The vehicle usage scenario data includes driving operation data and road environment data. Generating the visualization result according to the vehicle usage scenario data and the test data includes: generating the vehicle virtual model based on the driving operation data and the test data, wherein the vehicle virtual model is used to display the driver's operation and the status of the vehicle components in real time; Using the road environment data, generating the environment rendering data, wherein the environment rendering data is used to reflect dynamic changes in the environment surrounding the vehicle; The test data is analyzed according to the early warning standard corresponding to the vehicle fault event to obtain fault annotation data, wherein the fault annotation data is used to characterize the control operation that triggers the vehicle fault event.

5. The evaluation method of the vehicle control unit according to claim 3, characterized in that: The visualization result also includes the log data of the vehicle control unit. The display panel includes a main viewing angle panel, a playback control panel, and a data display control panel. Displaying the visualization result in the display panel within the visualization interface includes: Displaying the vehicle virtual model and the environment rendering data on the main viewing panel; Displaying the fault annotation data on the playback control panel; The log data of the vehicle-mounted control unit is displayed on the data display control panel.

6. The evaluation method of the vehicle control unit according to claim 5, characterized in that: The playback control panel includes a picture adjustment component and an input component, and the evaluation method of the vehicle-mounted control unit further includes: In response to an adjustment event that triggers execution of the image adjustment component, adjusting the test data to obtain reproduced data; In response to an input event that triggers execution of the input component, the content displayed on the main viewing panel is updated according to the reproduction data and the input tag data corresponding to the input event.

7. The evaluation method of a vehicle control unit according to claim 1, characterized in that: Performing a functional evaluation on the test data to generate the evaluation result includes: Performing a functional availability evaluation on the test data to obtain a functional availability result, wherein the functional availability result is used to evaluate whether the function of the vehicle-mounted control unit fails; Performing a functional experience evaluation on the test data to obtain a functional experience result, wherein the functional experience result is used to evaluate whether the function of the vehicle-mounted control unit meets the functional experience index; The evaluation result is generated according to the function availability result and the function experience result.

8. The method for evaluating a vehicle-mounted control unit according to any one of claims 1 to 7, wherein: Acquiring the vehicle usage scenario data includes: Obtaining version data of the onboard control unit and vehicle parameters; The vehicle usage scenario data is selected from a scenario database according to the version data and the vehicle parameters.

9. An evaluation device for a vehicle-mounted control unit, characterized in that: include: an acquisition module, configured to acquire vehicle usage scenario data corresponding to the vehicle-mounted control unit, wherein the vehicle usage scenario data is used to characterize the scenario operating condition characteristics of the vehicle-mounted control unit in the entire vehicle usage process, wherein the entire vehicle usage process includes a trip preparation phase, a trip travel phase, and a trip end phase; A test module, configured to utilize the vehicle usage scenario data to drive the vehicle-mounted control unit to perform a control operation and obtain test data; A generating module is used to perform a functional evaluation on the test data and generate an evaluation result, wherein the evaluation result is used to indicate whether the functional performance of the vehicle-mounted control unit meets the release standard.

10. A vehicle, characterized in that: include: a memory storing an executable program; A processor, configured to run the program, wherein the program executes the method according to any one of claims 1 to 8 when running.

Images